Thanks Mantas!!! In my case, metadata "cmdline" had sensitive information
which I am not intended to store. Is there any way to disable collecting
metadata?
Thanks,
Divya
On Wed, Aug 17, 2016 at 12:55 PM, Mantas Mikulėnas
wrote:
> On Wed, Aug 17, 2016 at 10:10 PM, Divya
On Wed, Aug 17, 2016 at 10:10 PM, Divya Thaluru
wrote:
> Hi,
>
> Journalctl stores metadata like "_UID,_GID,_CMDLINE,_SYSTEMD_CGROUP etc…"
> for each message. Is there any way, can we encrypt metadata (commandline
> info) so sensitive information wont be stored.
>
> If
Jóhann B. Guðmundsson schreef op 16-08-2016 18:58:
I personally recommend the project should stick with the original line
drew in the sand, for the master branch and all the "experimental"
stuff which may or may not come to pass, be kept in it's own
experimental branch which would be the best
Hi,
according to the official documentation from upstream systemd [1] it is
possible to override a package generator by placing a custom generator
(with the same name) into /etc/system/system-generator.
Since there is no manual page for systemd.generator on debian stable, I
tried the paths
On Wed, Aug 17, 2016 at 04:02:00PM +, nusenu wrote:
> Hi,
>
> according to the official documentation from upstream systemd [1] it is
> possible to override a package generator by placing a custom generator
> (with the same name) into /etc/system/system-generator.
>
> Since there is no
Hi,
Journalctl stores metadata like "_UID,_GID,_CMDLINE,_SYSTEMD_CGROUP etc…"
for each message. Is there any way, can we encrypt metadata (commandline
info) so sensitive information wont be stored.
If encryption of metadata is not possible, can we disable collecting the
metadata?
_UID=0
On Wed, 17 Aug 2016 21:51:27 +
Zbigniew Jędrzejewski-Szmek wrote:
> Overriding of generators was added in systemd 219
> (https://github.com/systemd/systemd/commit/e801700e9a). I don't think
> there's an easy solution for older systemds.
In case of Debian stable, one can