<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
<A HREF="http://blog.gerhards.net/2011/11/what-i-dont-like-about-journald.html">http://blog.gerhards.net/2011/11/what-i-dont-like-about-journald.html</A> - the true how systemd owner handles the cases<BR>
<A HREF="http://blog.gerhards.net/2011/11/journald-log-hash-chaining-is-broken.html">http://blog.gerhards.net/2011/11/journald-log-hash-chaining-is-broken.html</A> - What Lennart said is bullshit. If someone break in your system and can edit your syslogs it means the attacker has root access. Then who cares? Seriously? once the hacker has root rights it will run this # > /var/log/journal/<unique string>/*<BR>
and the all logs attacker's fingerprints gone at once. So the security purpose is bullshit.<BR>
<BR>
and finally:<BR>
<A HREF="http://blog.gerhards.net/2011/11/journald-and-rsyslog.html">http://blog.gerhards.net/2011/11/journald-and-rsyslog.html</A><BR>
<BR>
Everyone who reads this can decide wants to use the 'proper awesome systemd-journal' or just tolerates it on his system because it must to be on it (for reason just search in the archive).<BR>
<BR>
Balint<BR>
<BR>
</BODY>
</HTML>