website/blog/systemd-insecurity.html

89 lines
3.0 KiB
HTML
Raw Normal View History

2022-06-27 00:35:36 +01:00
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Blog - systemd Insecurity</title>
<link rel="stylesheet" href="../infnet.css">
2022-06-27 00:35:36 +01:00
</head>
2022-10-29 03:26:53 +01:00
<div class="sidebar">
<a class="title">Inferencium Network</a><br>
<br>
<br>
<div><a href="../about.html">About</a></div>
<div><a href="../contact.html">Contact</a></div>
<div><a href="../blog.html">Blog</a></div>
<div><a href="../source.html">Source</a></div>
2022-10-29 03:26:53 +01:00
</div>
2022-06-27 00:35:36 +01:00
<body>
<h1>Blog - #1</h1>
<br>
<h2>systemd Insecurity</h2>
<br>
2022-10-29 03:26:53 +01:00
<p>Posted: 2022-01-29 (UTC+00:00)</p>
<p>Updated: 2022-10-29 (UTC+00:00)</p>
2022-06-27 00:35:36 +01:00
<br>
<br>
2022-10-29 03:26:53 +01:00
<p>Anyone who cares about security may want to switch from systemd as soon as
possible; its lead developer doesn't care about your security at all.</p>
2022-06-27 00:35:36 +01:00
<br>
<p>Poettering:<br>
"You don't assign CVEs to every single random bugfix we do, do you?"</p>
<br>
<p>My thoughts:<br>
2022-10-29 03:26:53 +01:00
Yes, if they're security related.</p>
2022-06-27 00:35:36 +01:00
<br>
<p>Source:<br>
2022-10-29 03:26:53 +01:00
<a class="body-link" href="https://github.com/systemd/systemd/pull/5998">https://github.com/systemd/systemd/pull/5998</a></p>
2022-06-27 00:35:36 +01:00
<br>
<br>
<br>
<p>Poettering:<br>
2022-10-29 03:26:53 +01:00
"Humpf, I am not convinced this is the right way to announce this.
We never did that, and half the CVEs aren't useful anyway, hence I am not
sure we should start with that now, because it is either inherently
incomplete or blesses the nonsensical part of the CVE circus which we
2022-06-27 00:35:36 +01:00
really shouldn't bless..."</p>
<br>
<p>My thoughts:<br>
2022-10-29 03:26:53 +01:00
CVEs are supposed to be for security, and a log of when they were
found and their severity, so yes, it *is* the correct way to announce it.
It seems as if over 95 security-concious people think the same.</p>
2022-06-27 00:35:36 +01:00
<br>
<p>Source:<br>
2022-10-29 03:26:53 +01:00
<a class="body-link" href="https://github.com/systemd/systemd/pull/6225">https://github.com/systemd/systemd/pull/6225</a></p>
2022-06-27 00:35:36 +01:00
<br>
<br>
<br>
<p>Poettering:<br>
2022-10-29 03:26:53 +01:00
"I am not sure I buy enough into the security circus to do that though for
2022-06-27 00:35:36 +01:00
any minor issue..."</p>
<br>
<p>Source:<br>
2022-10-29 03:26:53 +01:00
<a class="body-link" href="https://github.com/systemd/systemd/issues/5144">https://github.com/systemd/systemd/issues/5144</a></p>
2022-06-27 00:35:36 +01:00
<br>
<br>
<br>
<p>Poettering:<br>
2022-10-29 03:26:53 +01:00
"Yes, as you found out "0day" is not a valid username. I wonder which tool
permitted you to create it in the first place. Note that not permitting
numeric first characters is done on purpose: to avoid ambiguities between
2022-06-27 00:35:36 +01:00
numeric UID and textual user names.<br>
<br>
2022-10-29 03:26:53 +01:00
systemd will validate all configuration data you drop at it, making it hard
to generate invalid configuration. Hence, yes, it's a feature that we don't
permit invalid user names, and I'd consider it a limitation of xinetd that
2022-06-27 00:35:36 +01:00
it doesn't refuse an invalid username.<br>
<br>
2022-10-29 03:26:53 +01:00
So, yeah, I don't think there's anything to fix in systemd here. I<
2022-06-27 00:35:36 +01:00
understand this is annoying, but still: the username is clearly not valid."</p>
<br>
<p>My thoughts:<br>
2022-10-29 03:26:53 +01:00
systemd was the thing that allowed root access just because a username
started with a number, then Poettering blamed the user.</p>
2022-06-27 00:35:36 +01:00
<br>
<p>Source:<br>
2022-10-29 03:26:53 +01:00
<a class="body-link" href="https://github.com/systemd/systemd/issues/6237">https://github.com/systemd/systemd/issues/6237</a></p>
2022-06-27 00:35:36 +01:00
<br>
<br>
</body>
</html>