From 18c8cdbec27a8753286ab2f316b34e7d3e7b6e3e Mon Sep 17 00:00:00 2001 From: inference Date: Mon, 5 Jun 2023 00:20:13 +0100 Subject: [PATCH] Update Blog #1 from version 4.0.0.14 to 4.0.2.16. --- blog/systemd_insecurity.html | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/blog/systemd_insecurity.html b/blog/systemd_insecurity.html index 4d5a90a..59b4f8e 100644 --- a/blog/systemd_insecurity.html +++ b/blog/systemd_insecurity.html @@ -5,7 +5,7 @@ - + @@ -69,8 +69,8 @@

Issue #0 - Against CVE Assignment


-

Poettering:
- "You don't assign CVEs to every single random bugfix we do, do you?"

+
"You don't assign CVEs to every single random bugfix we do, do you?"
+

- Lennart Poettering, systemd lead developer


My thoughts:
Yes, if they're security-related.

@@ -85,11 +85,11 @@

Issue #1 - CVEs Are Not Useful


-

Poettering:
- "Humpf, I am not convinced this is the right way to announce this. We never did that, and half the +

"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 really shouldn't - bless..."

+ bless..."
+

- Lennart Poettering, systemd lead developer


My thoughts:
CVEs are supposed to be for security, and a log of when they were found and their severity, so yes, @@ -106,8 +106,9 @@

Issue #2 - Security is a Circus


-

Poettering:
- "I am not sure I buy enough into the security circus to do that though for any minor issue..."

+
"I am not sure I buy enough into the security circus to do that though for any minor + issue..."
+

- Lennart Poettering, systemd lead developer


Source:
Issue #3 - Blaming the User
-

Poettering:
- "Yes, as you found out "0day" is not a valid username. I wonder which tool permitted you to create +

"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 numeric UID and textual user names.
+ avoid ambiguities between numeric UID and textual user names.
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 it doesn't refuse an invalid username.

So, yeah, I don't think there's anything to fix in systemd here. I understand this is annoying, but - still: the username is clearly not valid."

+ still: the username is clearly not valid."
+

- Lennart Poettering, systemd lead developer


My thoughts:
systemd was the thing that allowed root access just because a username started with a number, then