News for hackers. Stuff that matters.

A comment on Ubuntu Systemd Vulnerability. Parent comment

Re:Ubuntu Systemd Vulnerability by interestingemu on Wednesday June 28, 2017 @08:31AM (#14653513)
> I believe systemd-resolved, however, is one of those components that is entirely optional, and which nothing explicitly depends on...

Yet. Wouldn't be the first time some "optional" component became mandatory.

[ Parent | on HN ]
Re:Ubuntu Systemd Vulnerability by icebraining on Wednesday June 28, 2017 @08:34AM (#14653524)
Which optional systemd components became mandatory?
[ Parent | on HN ]
Re:Ubuntu Systemd Vulnerability by dijit on Wednesday June 28, 2017 @08:38AM (#14653538)
Journald
[ Parent | on HN ]
Re:Ubuntu Systemd Vulnerability by icebraining on Wednesday June 28, 2017 @08:44AM (#14653563)
When was journald optional?
[ Parent | on HN ]
Re:Ubuntu Systemd Vulnerability by dijit on Wednesday June 28, 2017 @09:06AM (#14653699)
When systemd first landed in Fedora 16.

You could use syslog or journald (or both. But journald was optional)

[ Parent | on HN ]
Re:Ubuntu Systemd Vulnerability by icebraining on Wednesday June 28, 2017 @09:19AM (#14653791)
Journald didn't even exist when Fedora 16 was released, so how could it be optional?

Meanwhile, from the first public document of journald[1], it was always designed as an indispensable component of systemd.

[1] https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBA...

[ Parent | on HN ]
Re:Ubuntu Systemd Vulnerability by dijit on Wednesday June 28, 2017 @02:23PM (#14656839)
I have strong memories of installing it on fedora 16 long before the 17 release was announced. I don't know about intent but I was a very avid fedora user and I was pro-journald before it was forced down my throat.
[ Parent | on HN ]