Date: Wed, 07 Jan 2015 01:42:35 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 196581] security/silktools 3.9.0 timestamp issue Message-ID: <bug-196581-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196581 Bug ID: 196581 Summary: security/silktools 3.9.0 timestamp issue Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: lx@FreeBSD.org Reporter: mworld@twbc.net Assignee: lx@FreeBSD.org Flags: maintainer-feedback?(lx@FreeBSD.org) I've noticed an issue with silktools 3.9.0 which has also been mentioned on the silk website. https://tools.netsa.cert.org/silk/releasenotes.html 3.10.0 fixed: "Fix a bug when decoding the IPFIX elements flowStartMicroseconds and flowEndMicroseconds where the wrong epoch was being used" Issue: custom C/C++ code that utilizes the silk library incorrectly reads the sTime value from a silk record which means any filters that rely on the date of the flow come up empty. SiLK tools 3.10.0 compiles and runs nicely on systems I've tested: FreeBSD 8.x and 9.x. This version does indeed fix the issue. See here for an example: https://lists.sei.cmu.edu/pipermail/netsa-tools-discuss/2014-December/000045.html --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Auto-assigned to maintainer lx@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196581-13>