diff --git a/README.md b/README.md
index e10fc54..2ff02b8 100644
--- a/README.md
+++ b/README.md
@@ -3,11 +3,14 @@
All content is licensed under BSD 3-Clause Clear License.
+All content is licensed under BSD 3-Clause Clear license.
Exceptions: All content outside of code, including personal content
+
Exceptions:
+
To contribute to the project, submit a pull request. All pull requests
-are subject to approval.
-
-Code must follow the standard style for Inferencium Network code:
-- 80 character column limit.
-- Tab indents.
-- 1 tab indent equals 4 columns.
-- Comments must be used for each different block of code.
-- Comments must be concise. Do not make comments longer than necessary.
-- Code and comments must be professional. No funny or vulgar code or
-comments.
-
-Files must be stored in their related directories.
-
-Text files must be stored as plain text (.txt) or Markdown (.md) files.
-
-All dates and times must be ISO 8601 compliant (YYYY-MM-DD HH:MM).
-
-All filenames must be most significant to least significant, lowercase, and
-hyphens must be used instead of spaces.
Development branch. All pre-alpha development and alpha testing happens
here.
-Merge requests must be made to the dev branch.
Beta branch. All beta testing of the software happens here.
+Beta branch. All beta testing happens here.
Stable branch. Complete and stable versions of the software are stored
-here.
+
Stable branch. Complete and stable versions are stored here.
diff --git a/blog/systemd-insecurity.html b/blog/systemd-insecurity.html
index 64660d0..cfafc80 100644
--- a/blog/systemd-insecurity.html
+++ b/blog/systemd-insecurity.html
@@ -19,23 +19,29 @@
Posted: 2022-01-29 (UTC+00:00)
-Updated: 2022-10-29 (UTC+00:00)
+Updated: 2022-11-14 (UTC+00:00)
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.
Poettering:
"You don't assign CVEs to every single random bugfix we do, do you?"
My thoughts:
-Yes, if they're security related.
Source:
-https://github.com/systemd/systemd/pull/5998
Poettering:
"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
@@ -49,19 +55,25 @@ 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.
Source:
-https://github.com/systemd/systemd/pull/6225
Poettering:
"I am not sure I buy enough into the security circus to do that though for
any minor issue..."
Source:
-https://github.com/systemd/systemd/issues/5144
Poettering:
"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
@@ -73,7 +85,7 @@ 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<
+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."
My thoughts:
@@ -81,7 +93,8 @@ systemd was the thing that allowed root access just because a username
started with a number, then Poettering blamed the user.
Source:
-https://github.com/systemd/systemd/issues/6237