So, you believe that you are smarter than the entire US Army?

Man you really are just a PITA.

The US Army is one of the groups you keep referring to as systemd "hatters". If anyone here thinks they are smarter than our military... it's you.

What? I've never did this. Show me where I said this!

And WHY I should blame them to be systemd "hatters" when they "recently enlisted Red Hat, Inc., the world’s largest provider of open-source solutions, to help improve squadron operations and flight training." ?

As probably you do (not yet?) noticed, I asked the one forum member who started to have fantasies regarding BSD while literally quoting this:

The guy responded this:

Definitively they (US Army) does not look like being systemd "hatters" and I never believed that them will believe otherwise.

The Military, (almost certainly) no matter from what country, has the legs on ground and looks for efficiency and robustness, not for what some minority of thousands profess on Internet.

And THIS, boys and girls, is what a gaslighting troll looks like.

He lurks under digital bridges, picking fights because he has nothing better to do.

I would offer some tangible knowledge in this area since I have had this discussion with actual DoD customers but it's all an excercise in futility when the lucky robot man starts wall-posting.

Didn't I say 'Not starting a flame war here!' ( ͡° ͜ʖ ͡°)

Deploying systemd in submarines makes me hopeful for the planet vs a nuclear holocaust.
When the sardines hit the ballistic missile buttons, it will be something like that on the screens
#systemd: Freezing execution.
# reboot

I accidentally pressed "helpful" on your post. I did not meant to, thus this post.

I respectively disagree and I understand why the Army would use RHEL. But I do not want to say more since I think this thread is on its way to becoming one of those mega flamefests we sometimes see here when systemd is brought up

Regards
John

1 members found this post helpful.

All good John
I probably am not the only one who appreciates your honesty

From my above posts it might seem I'm not a fan of systemD. Which is correct. I'm not. For my personal computer I want "raw access" to the kernel. Not encapsulating it...

But should I run a larger install and especial something as serious as The Army or The Navy I definitely would look for a system backed up by some big muscles. Red Hat/IBM absolutely tops the list. Of course.

So no hatred here.

It just won't get installed here...

1 members found this post helpful.

Although I am a fan of the BSDs I can understand why the US military opted for RHEL. Red Hat has a well established IT support team to help corporate clients.

1 members found this post helpful.

Serious question though:
At work, we have this one guru that is literally the last man standing in the Linux (RH) admin team, the others have been poached and moved on due to career progression.
Is there such a thing as mutant virus/worm/malware/etc that could take advantage of systemd, spread to every RH server and make his life more difficult than it should be?

I too am seriously thinking of a BSD for migrating an old server to.
ATM, I'm looking at OpenBSD.

That's what this is. As I understand it a single feature within the systemd ecosystem can be used to run arbitrary scripts, as root. So the attacker could do anything root can do.

But this particular attack involves leveraging a single feature that is technically optional. This concept isn't unique to systemd - I'm sure the BSDs have their own collection of exploits.

Quite simply: Turn off all services you don't use. That is old advice, but is still one of the best methods for reducing your attack surface.

Contrary to the poster above, the problem which is the subject of this thread is not a "worm" as such. It's an old-school root exploit which could be used by a worm. It is also a "systemd-only" problem. If you have any systems with systemd, and you use networkd-dispatcher, then you should upgrade that package ASAP.

The relevant part is in the second paragraph of the article which was linked:

"We discovered the vulnerabilities by listening to messages on the System Bus while performing code reviews and dynamic analysis on services that run as root, noticing an odd pattern in a systemd unit called networkd-dispatcher. Reviewing the code flow for networkd-dispatcher revealed multiple security concerns, including directory traversal, symlink race, and time-of-check-time-of-use race condition issues, which could be leveraged to elevate privileges and deploy malware or carry out other malicious activities. We shared these vulnerabilities with the relevant maintainers through Coordinated Vulnerability Disclosure (CVD) via Microsoft Security Vulnerability Research (MSVR). Fixes for these vulnerabilities, now identified as CVE-2022-29799 and CVE-2022-29800, have been successfully deployed by the maintainer of the networkd-dispatcher, Clayton Craft. We wish to thank Clayton for his professionalism and collaboration in resolving those issues. Users of networkd-dispatcher are encouraged to update their instances."

Since it is not possible for non-systemd systems to use networkd-dispatcher, I fail to see how this could affect anything else.
There could be, but he just needs to ensure that he keeps the systems up to date with all of the latest security patches... as with everything else really.
The first question I have is: What services does that machine provide?

2 members found this post helpful.

Sound advice for anyone running servers and desktops.
Keep patching.

Usual network administration server for networking devices, remote backups, python scripts, etc...
Primarily scp, rsync and a lot of files (small to huge) from literally hundreds of concurrent sources every night.
A few select users that auth against a remote radius server for access, perhaps radsec if supported.
But that's a different topic that I've asked at https://www.linuxquestions.org/quest...sd-4175711539/