Date: Sun, 19 Feb 2012 09:24:13 -0800 From: freebsd@johnea.net To: freebsd-security@freebsd.org Subject: Re: periodic security run output gives false positives after 1 year Message-ID: <4F41303D.8060409@johnea.net> In-Reply-To: <4F412850.3020705@mschuette.name> References: <20120217120034.201EB106574C@hub.freebsd.org> <20120217152400.261AC106564A@hub.freebsd.org> <CAE-mSO%2Bsa2Cu0aQksEXGyMnyns3=aAL8odmzQNMEJ77dpUAgmw@mail.gmail.com> <20120217194851.D76DE1065670@hub.freebsd.org> <4F412850.3020705@mschuette.name>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-02-19 08:50, Martin Schütte wrote: > On 17.02.2012 20:48, Roger Marquis wrote: >> and difficult to change without breaking more than it fixes. The current >> syslog syntax timestamp has been reliable now for what, 25+ years? I >> don't personally see any measurable ROI from changing it. YMMV of >> course. > > I really understand the concern, but some requirements do change over > time. Staying at the lowest common denominator for 25+ years may > indicate robustness, but it may also indicate obsolence. > What seems obsolete is this thread. Can you at least prepended [OT RANT] to the subject? Some people monitor this list to be informed of possible FreeBSD security issues, of which this isn't. Please, get a motel room or something... johnea
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F41303D.8060409>