Date: Fri, 17 Feb 2012 21:02:41 +0300 From: Sergey Kandaurov <pluknet@gmail.com> To: Roger Marquis <marquis@roble.com> Cc: freebsd-security@freebsd.org Subject: Re: periodic security run output gives false positives after 1 year Message-ID: <CAE-mSO%2Bsa2Cu0aQksEXGyMnyns3=aAL8odmzQNMEJ77dpUAgmw@mail.gmail.com> In-Reply-To: <20120217152400.261AC106564A@hub.freebsd.org> References: <20120217120034.201EB106574C@hub.freebsd.org> <20120217152400.261AC106564A@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 February 2012 19:04, Roger Marquis <marquis@roble.com> wrote: > Sergey Kandaurov wrote: >> >> In IETF this RFC is marked obsolete and replaced with RFC 5424 with >> different timestamp format in ISO 8601 form. FreeBSD doesn't implement >> 5424 yet. Almost complete implementation was done in NetBSD in that >> regard in 2008. NetBSD before RFC 5424 changes has had pretty similar >> syslogd source, so if one could analyze and port that changes to FreeBSD, >> that would be pretty nice. > > > Problem with that would be backwards compatibility, and it's not IMO > worth breaking everyone's syslog parsing scripts to fix an issue that > really isn't due to the date format as much as it is to log rotation. > That is not a showstopper. Nothing prevents to merge both formats in one daemon and introduce a new syslogd option to choose the desired format. -- wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-mSO%2Bsa2Cu0aQksEXGyMnyns3=aAL8odmzQNMEJ77dpUAgmw>