News for hackers. Stuff that matters.
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.