Date: Thu, 1 Dec 2011 01:46:45 -0800 From: Garrett Cooper <yanegomi@gmail.com> To: Zhihao Yuan <lichray@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: To implement RFC 5848 (Signed Syslog Messages)? Message-ID: <CAGH67wQpLt5OM-N_xMciQ=fETkC2uVFCPTh6RkCP4mzZi0XrLg@mail.gmail.com> In-Reply-To: <CAGsORuCg2VEZ=zaHS%2BLGCecusUDZxyy3wB9wHQqC_XcPjwdpSg@mail.gmail.com> References: <CAGsORuCg2VEZ=zaHS%2BLGCecusUDZxyy3wB9wHQqC_XcPjwdpSg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 1, 2011 at 1:01 AM, Zhihao Yuan <lichray@gmail.com> wrote: > Hi, hackers: > > Red Hat's "star" developer, Lennart Poettering, is porting Windows > Event Log to GNU/Linux :) > https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBAGRL6wl97tFxgjLUEHIX3MSTs&pli=1 > > Regardless of his stupid arguments, let's talk about something > trivial. How about to implement RFC 5848 in our syslogd? It adds the > encryption to the existing syslog message layer, and increase the > security in transferring. > http://tools.ietf.org/html/rfc5848 > > Albert Mietus made a nice presentation in 2002 > http://www.slideshare.net/SoftwareBeterMaken.nl/securing-syslog-on-freebsd > > Not sure whether his code is accessible or not. I agree that encryption and tcp (reliable) transport of logs should be a must for syslogd in FreeBSD. It's going to be interesting how things with Lennart's 'journald' play out -- without defining an industry standard for how messages are presented and categorized, I predict that things will turn into a mess (I could be proved wrong, but given past experience, this is how things evolve unless framework adoption lags standardization). Thanks :), -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wQpLt5OM-N_xMciQ=fETkC2uVFCPTh6RkCP4mzZi0XrLg>