[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse
Subject:    Re: [opensuse] Re: Why are systemd's logs stored as binaries?
From:       "Carlos E. R." <robin.listas () telefonica ! net>
Date:       2016-12-23 22:16:33
Message-ID: c2befa96-9940-b1ad-0e56-613232df2db2 () telefonica ! net
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2016-12-23 23:05, John Andersen wrote:
> On 12/23/2016 01:46 PM, Greg Freemyer wrote:

> None of that is at question here.
> 
> What is at question is that carlos is arguing that the simple act
> of dumping a binary log to a text one renders it unacceptable.

As you see from Greg response, that is so. It is only acceptable if
/he/ does it and certifies in court that he did it in a controlled
environment. This requires that we have tools to extract the text data
several years later, and that those binary logs can be kept reliably
for many years in the running machines.

> I think he is also arguing (unstated) that passing logs through
> journald on their way to oldschool syslog also renders them
> unacceptable by mere extension of the above.

I did not say so, but the systemd developer himself would say so. It
is obvious. One of the goals of the systemd journal is authenticity
and integrity. The journal can not make this guarantee if a second
party is in the mix this way.


To be valid in a legal environment the binary logs have to arrive
intact to the people doing the investigation.

- -- 
Cheers / Saludos,

		Carlos E. R.

  (from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAlhdokEACgkQja8UbcUWM1yG0gD+P9BMEar8QObM47M0eF9XxUez
+o5ceRarXQTRbu5RrpIBAIW3Fgq+zgYjBMvMc5KTBnYSfRvQ+mVg4YlEpTKPbAk5
=xSJX
-----END PGP SIGNATURE-----

-- 
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse+owner@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]