Update webpage "Blog - #1" from version 5.0.0+30 to 5.0.1
This commit is contained in:
parent
a4330c5548
commit
ca42e8831e
SSH Key Fingerprint:
SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
@ -5,7 +5,7 @@
|
|||||||
<!-- Copyright 2022 Jake Winters -->
|
<!-- Copyright 2022 Jake Winters -->
|
||||||
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
||||||
|
|
||||||
<!-- Version: 5.0.0+30 -->
|
<!-- Version: 5.0.1 -->
|
||||||
|
|
||||||
|
|
||||||
<html>
|
<html>
|
||||||
@ -14,7 +14,7 @@
|
|||||||
<link rel="stylesheet" href="../main.css">
|
<link rel="stylesheet" href="../main.css">
|
||||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||||
</head>
|
</head>
|
||||||
<!-- Navigation bar -->
|
<body>
|
||||||
<div class="sidebar">
|
<div class="sidebar">
|
||||||
<a href="../index.html"><img src="../asset/img/logo-inferencium-no_text.png" width="110px" height="110px"></a>
|
<a href="../index.html"><img src="../asset/img/logo-inferencium-no_text.png" width="110px" height="110px"></a>
|
||||||
<a href="../index.html" class="title">Inferencium</a><br>
|
<a href="../index.html" class="title">Inferencium</a><br>
|
||||||
@ -28,72 +28,70 @@
|
|||||||
<div><a href="../key.html">Key</a></div>
|
<div><a href="../key.html">Key</a></div>
|
||||||
<div><a href="../changelog.html">Changelog</a></div>
|
<div><a href="../changelog.html">Changelog</a></div>
|
||||||
</div>
|
</div>
|
||||||
<body>
|
|
||||||
<h1>Blog - #1</h1>
|
<h1>Blog - #1</h1>
|
||||||
<h2>systemd Insecurity</h2>
|
<h2>systemd Insecurity</h2>
|
||||||
<p class="update_date">Posted: 2022-01-29 (UTC+00:00)</p>
|
<p class="update_date">Posted: 2022-01-29 (UTC+00:00)</p>
|
||||||
<p class="update_date">Updated: 2022-11-14 (UTC+00:00)</p>
|
<p class="update_date">Updated: 2023-10-31 (UTC+00:00)</p>
|
||||||
<!-- Table of contents -->
|
|
||||||
<section id="toc">
|
<section id="toc">
|
||||||
<h2 id="toc"><a href="#toc">Table of Contents<a/></h2>
|
<h2 id="toc"><a href="#toc">Table of Contents<a/></h2>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="#issue0">Issue #0 - Against CVE Assignment</a></li>
|
<li><a href="#issue-0">Issue #0 - Against CVE Assignment</a></li>
|
||||||
<li><a href="#issue1">Issue #1 - CVEs Are Not Useful</a></li>
|
<li><a href="#issue-1">Issue #1 - CVEs Are Not Useful</a></li>
|
||||||
<li><a href="#issue2">Issue #2 - Security is a Circus</a></li>
|
<li><a href="#issue-2">Issue #2 - Security is a Circus</a></li>
|
||||||
<li><a href="#issue3">Issue #3 - Blaming the User</a></li>
|
<li><a href="#issue-3">Issue #3 - Blaming the User</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
</section>
|
</section>
|
||||||
<p>Anyone who cares about security may want to switch from systemd as soon as possible; its lead
|
<p>Anyone who cares about security may want to switch from systemd as soon as possible;
|
||||||
developer doesn't care about your security at all.</p>
|
its lead developer doesn't care about your security at all.</p>
|
||||||
<section id="issue0">
|
<section id="issue-0">
|
||||||
<h2 id="issue0"><a href="#issue0">Issue #0 - Against CVE Assignment</a></h2>
|
<h2 id="issue-0"><a href="#issue-0">Issue #0 - Against CVE Assignment</a></h2>
|
||||||
<br>
|
<blockquote>"You don't assign CVEs to every single random bugfix we do, do
|
||||||
<blockquote>"You don't assign CVEs to every single random bugfix we do, do you?"</blockquote>
|
you?"</blockquote>
|
||||||
<p>- Lennart Poettering, systemd lead developer</p>
|
<p>- Lennart Poettering, systemd lead developer</p>
|
||||||
<p>My thoughts:<br>
|
<p><b>My thoughts:</b> Yes, if they're security-related.</p>
|
||||||
Yes, if they're security-related.</p>
|
<p>Source:
|
||||||
<p>Source:<br>
|
|
||||||
<a href="https://github.com/systemd/systemd/pull/5998#issuecomment-303782334">systemd GitHub Issue 5998</a></p>
|
<a href="https://github.com/systemd/systemd/pull/5998#issuecomment-303782334">systemd GitHub Issue 5998</a></p>
|
||||||
</section>
|
</section>
|
||||||
<section id="issue1">
|
<section id="issue-1">
|
||||||
<h2 id="issue1"><a href="#issue1">Issue #1 - CVEs Are Not Useful</a></h2>
|
<h2 id="issue-1"><a href="#issue-1">Issue #1 - CVEs Are Not Useful</a></h2>
|
||||||
<blockquote>"Humpf, I am not convinced this is the right way to announce this. We never did that, and half the
|
<blockquote>"Humpf, I am not convinced this is the right way to announce this.
|
||||||
CVEs aren't useful anyway, hence I am not sure we should start with that now, because it is either
|
We never did that, and half the CVEs aren't useful anyway, hence I am not sure
|
||||||
inherently incomplete or blesses the nonsensical part of the CVE circus which we really shouldn't
|
we should start with that now, because it is either inherently incomplete or
|
||||||
|
blesses the nonsensical part of the CVE circus which we really shouldn't
|
||||||
bless..."</blockquote>
|
bless..."</blockquote>
|
||||||
<p>- Lennart Poettering, systemd lead developer</p>
|
<p>- Lennart Poettering, systemd lead developer</p>
|
||||||
<p>My thoughts:<br>
|
<p><b>My thoughts:</b> CVEs are supposed to be for security, and a log of when they
|
||||||
CVEs are supposed to be for security, and a log of when they were found and their severity, so yes,
|
were found and their severity, so yes, it <em>is</em> the correct way to
|
||||||
it *is* the correct way to announce it. It seems as if over 95 security-concious people think the
|
announce it. It seems as if over 95 security-concious people think the same.</p>
|
||||||
same.</p>
|
<p>Source:
|
||||||
<p>Source:<br>
|
|
||||||
<a href="https://github.com/systemd/systemd/pull/6225#issuecomment-311739869">systemd GitHub Issue 6225</a></p>
|
<a href="https://github.com/systemd/systemd/pull/6225#issuecomment-311739869">systemd GitHub Issue 6225</a></p>
|
||||||
</section>
|
</section>
|
||||||
<section id="issue2">
|
<section id="issue-2">
|
||||||
<h2 id="issue2"><a href="#issue2">Issue #2 - Security is a Circus</a></h2>
|
<h2 id="issue-2"><a href="#issue-2">Issue #2 - Security is a Circus</a></h2>
|
||||||
<blockquote>"I am not sure I buy enough into the security circus to do that though for any minor
|
<blockquote>"I am not sure I buy enough into the security circus to do that
|
||||||
issue..."</blockquote>
|
though for any minor issue..."</blockquote>
|
||||||
<p>- Lennart Poettering, systemd lead developer</p>
|
<p>- Lennart Poettering, systemd lead developer</p>
|
||||||
<p>Source:<br>
|
<p>Source:
|
||||||
<a href="https://github.com/systemd/systemd/issues/5144#issuecomment-276740654">systemd GitHub Issue 5144</a></p>
|
<a href="https://github.com/systemd/systemd/issues/5144#issuecomment-276740654">systemd GitHub Issue 5144</a></p>
|
||||||
</section>
|
</section>
|
||||||
<section id="issue3">
|
<section id="issue-3">
|
||||||
<h2 id="issue3"><a href="#issue3">Issue #3 - Blaming the User</a></h2>
|
<h2 id="issue-3"><a href="#issue-3">Issue #3 - Blaming the User</a></h2>
|
||||||
<blockquote>"Yes, as you found out "0day" is not a valid username. I wonder which tool permitted you to create
|
<blockquote>"Yes, as you found out "0day" is not a valid username. I wonder
|
||||||
it in the first place. Note that not permitting numeric first characters is done on purpose: to
|
which tool permitted you to create it in the first place. Note that not
|
||||||
avoid ambiguities between numeric UID and textual user names.
|
permitting numeric first characters is done on purpose: to avoid ambiguities
|
||||||
|
between numeric UID and textual user names.<br>
|
||||||
<br>
|
<br>
|
||||||
systemd will validate all configuration data you drop at it, making it hard to generate invalid
|
systemd will validate all configuration data you drop at it, making it hard to
|
||||||
configuration. Hence, yes, it's a feature that we don't permit invalid user names, and I'd consider
|
generate invalid configuration. Hence, yes, it's a feature that we don't permit
|
||||||
it a limitation of xinetd that it doesn't refuse an invalid username.<br>
|
invalid user names, and I'd consider it a limitation of xinetd that it doesn't
|
||||||
|
refuse an invalid username.<br>
|
||||||
<br>
|
<br>
|
||||||
So, yeah, I don't think there's anything to fix in systemd here. I understand this is annoying, but
|
So, yeah, I don't think there's anything to fix in systemd here. I understand
|
||||||
still: the username is clearly not valid."</blockquote>
|
this is annoying, but still: the username is clearly not valid."</blockquote>
|
||||||
<p>- Lennart Poettering, systemd lead developer</p>
|
<p>- Lennart Poettering, systemd lead developer</p>
|
||||||
<p>My thoughts:<br>
|
<p><b>My thoughts:</b> systemd was the thing that allowed root access just because a
|
||||||
systemd was the thing that allowed root access just because a username started with a number, then
|
username started with a number, then Poettering blamed the user.</p>
|
||||||
Poettering blamed the user.</p>
|
<p>Source:
|
||||||
<p>Source:<br>
|
|
||||||
<a href="https://github.com/systemd/systemd/issues/6237#issuecomment-311900864">systemd GitHub Issue 6237</a></p>
|
<a href="https://github.com/systemd/systemd/issues/6237#issuecomment-311900864">systemd GitHub Issue 6237</a></p>
|
||||||
</section>
|
</section>
|
||||||
</body>
|
</body>
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user