News for hackers. Stuff that matters.
Re:Linux syslog on the way out? by dredmorbius on Tuesday November 22, 2011 @02:22PM (#3266944)
My first (shallow) read of the proposal is that it solves one relatively high-risk, low-probability case by throwing a great deal of complexity at standard operations on which a great deal of existing infrastructure exists: log analyzers, summarizers, rotation systems (broken as they may be), and just simple shell tools.

Immediately prior to launching myself into Linux, I briefly toyed with Windows NT 4.0 WS, and among the bigger disappointments of it was the system logging facility and its user interfaces. While *nix logging has its bugaboos, the ability to chain simple tools together to perform tasks (example: grep, cut, and uniq -c on a postfix logfile to give a per-hour summary of mail delivery status by various classifications) provides tremendous flexibility. As compared with the single GUI interface Microsoft provided. I'd hope that Poettering et al won't repeat this bone-headed mistake, but the simple observation that their sample log event lacks ... a date stamp??!!! ... doesn't inspire me.

If there's a useful element from this it's the list of horribles against current syslog weaknesses. Many of these could be addressed by amending syslog and/or providing a bolt-on solution. I don't see a need for a total replacement.

As to the observation that there are currently several (incompatible) logging systems on Linux systems, ob xkcd: http://xkcd.com/927/

Re:Linux syslog on the way out? by rbanffy on Tuesday November 22, 2011 @02:59PM (#3267083)
A second read makes me believe it solves no problem except disk space usage. The fact it's binary and signed protects against nothing - whoever has control of the machine also controls the signing keys of the log and can generate whatever log they want, with whatever event they want.

Are we doomed to repeat every stupid mistake Microsoft made? Is the "if you don't know Windows you are doomed to reimplement its bugs" the new thing?

Re:Linux syslog on the way out? by dredmorbius on Tuesday November 22, 2011 @03:12PM (#3267122)
The solution to integrity, IMO, is distributing the log (multiple independent logservers). You can hash individual line items if you want, or sign them, or do any number of other things to make it easier to find discrepancies. There's the problem of log lossieness in general, which is a tough nut to crack. Some form of log entry UUID might also be useful (though hostname + millisecond/jiffy timestamp comes close).

And count me in among those who find the bug-for-bug reimplementation of Microsoft's fatal errors just a tad annoying.

Re:Linux syslog on the way out? by rbanffy on Tuesday November 22, 2011 @10:37PM (#3268647)
> The solution to integrity, IMO, is distributing the log (multiple independent logservers).

Isn't this already solved by rsyslogd?

Re:Linux syslog on the way out? by dredmorbius on Wednesday November 23, 2011 @02:06AM (#3269138)
Yes.