Re,
On 11/28/2014 11:04 PM, Sven Hartge wrote:
On 28.11.2014 22:57, Thomas Liske wrote:
So please add a blacklist entry to avoid restarting systemd-journald
under any circumstances.
We should wait until systemd-journald's RC bug got closed. Maybe we
should add systemd-journald to the override_rc list if the bug is
non-fixable.
The bug is non-fixable, as far as I understand the IRC-log.
So systems will run outdated systemd-journald after (security) updates
until the systems got rebootet? Since journald owns stdout/stderr of all
the services there seems to be many (remote) attack vectors. This sounds
awful to me.
If journald is restarted the stdout/stderr of running daemons got lost -
is this a bigger problem than running a vulnerable journald?
Grüße,
Thomas
--
:: WWW: http://fiasko-nw.net/~thomas/ ::
::: Jabber: xmpp:tho...@jabber.fiasko-nw.net :::
:: flickr: http://www.flickr.com/photos/laugufe/ ::
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
