Is Slackware affected by the Linux vulnerability discovered by Microsoft?
 

I've been skimming through https://www.microsoft.com/security/b...ity-nimbuspwn/ which mentions d-bus (which I know nothing about, except that Slackware has it) and also something related to systemd (which I know even less about, since Slackware is systemd free and I've no time to spend learning a systemd distro, albeit I should).

Can anyone provide some feedback on this?

Slackware doesn't use this networkd-dispatcher program so no Slackware is not affected.

Please check the below url for infos regarding your queries.

http://www.slackware.com/security/

Protest!
 

Sorry, but that vulnerability is not in Linux, but in a third-party app... :rolleyes:

Not related at all to Linux - only found in distros who choose to include that app collection.

Go to Red Hat.


The Linux part of the environment can't possible be stronger monitored, can it? If you have any suggestions, I'm sure you'll be welcomed with open arms. Kernel land seems unknown to you?

And... :D reg. growing numbers, they can only go up, can't they? You can't really un-discover things once found... sigh.

Rant-mode off.


Have a nice evening! :hattip:


/edit: forgot to complement you for the fine work. Good read!

Thank you, but, I'll pass on your suggestion. :)
Good to know that Slackware is unaffected.

That is funny, wonder if those tech journalist also mislabel a chrome bug as windows vulnerability.
Probably not though, likely because there isn't anyone who would profit from that sort of FUD.

My Son is a rather confirmed Windows user who thinks I'm crazy for running Linux and despite being employed in the security of utilities software field. Anyway, he sent me an online "study" that claimed that Linux had orders of magnitude more vulnerabilities than Windows 10 had.... and it DOES !!! .... IF, as the "study" did, you compare just Windows 10 to every Linux kernel that has ever existed and enumerated the total number of vulnerabilities of all Linux kernels for comparison.

8 ^ D

Yeah Microslop hasn't evolved much from "Linux, that virus"

A security hole in systemd??? Say it ain't so!

At least once every few months, I'm reminded of how grateful I am for the fact that Slackware has steadfastly refused to adopt that bucket of worms.

enorbet, please feel free to tell your son on my behalf that he is wrong. :D Windows is nowhere near as secure as Linux. I can't believe anyone working in IT security would use Windows.

Perhaps you could ask your son why it is that so much internet infrastructure hardware runs on Linux and not Windows?

Also: "The United States Department of Defense recognizes the key benefits associated with open-source development and trusts Linux as its operating system. In fact, the US Army is the single largest installed base for RedHat Linux and the US Navy nuclear submarine fleet runs on Linux, including their sonar systems. Moreover, the Department of Defense just recently enlisted Red Hat, Inc., the world’s largest provider of open-source solutions, to help improve squadron operations and flight training."

source: https://linuxsecurity.com/features/l...ding-into-2020

And... The world's current top 500 supercomputers all run on Linux: https://www.top500.org/statistics/details/osfam/1/

Would that really be so if it were not secure? The same OS kernel also powers more than 87% of the world's cell phones.

OK. I'll stop now.

Edit: Can't help myself: https://www.zdnet.com/article/micros...un-on-windows/

"Microsoft's Voyager-EUS2, which runs from its Azure East US 2 region, is notable for several reasons. First, but not surprisingly, it's running a Linux distribution, namely the Ubuntu 18.04 long term servicing (LTS) edition. It's got 253,440 cores on AMD EPYC CPUs."

L O L

It's just like saying that the COVID pandemic is not related at all to Human species because they discovered an Amazon tribe which members is immune to it. And in this story we we are that Amazon tribe, buddy... ;)

I believe that IF we really want to keep our Way of Life, we should stop laughing our asses out to any issue vaguely related to systemd in the Linux World. Contrary, we should become specialists on how systemd works and behave. To get the ability to fine emulate its features and behavior.

PS. From what I know, the WPA3 is still supported by Linux exclusively via systemd-networkd - which is not a big issue, as 99% of today distros ships and uses it. BUT, this means that you may not be able to connect your brand new Wireless router with your fancy Slackware 16.0 unless someone (at least vaguely related to Slackware) would understand how those things are done. Just saying ...

Both wpa_supplicant and NetworkManager support WPA3, what do you think is then the issue in Slackware?

Thank you! Would have hated to see you leave because of my rambling rant! :D

Especially as the remark was to the "Microsoft 365 Defender Research Team" (see link in op).


Before ending up with Slackware, I had a long journey digging deep into even the oldest mails re. Linux and the SystemD team... big help in deciding how I would run my kernel btw. but based on that experience, I would like to see how Lennart has responded to that bug report.

Anyone got a link?


The bug report in question is solely, completely, entirely a systemD issue... not at all related to Linux.

But... but... that's why we have you! :D :hattip:

And I refuse to believe nobody in the team can't solve whatever issues may arise.

You're welcome. :)
I'm not a fan of systemd, the closest I'll get to it is to install a distro in a VM. I do credit Red Hat for getting me started on my Slackware adventure in 2004. Red Hat discontinued the free to use Red Hat 9 and moved to the pay per view RHEL. That brought me to Slackware 10.0 and I've never looked back.

From what I'm seeing with WSL Microsoft isn't evolving away from linux, more like evolving into it.

Giving Windows the ability to natively execute binary code from a "less secure OS" is going to make them sooooooo much more secure. Now Windows users get to suffer from our bugs as well as theirs. </sarcasm>


Maybe they think that if they build an OS vulnerable to both win32 AND linux exploits, they will cancel each other out.

I've been using WPA3 Personal on Slackware current for some time now. The WAP is running Openwrt.
No issues whatsoever

Then they are 'up-sh1t-creek' aren't they...
(Please note: Not starting a flame war here, there is enough of that going around)
For something that critical, I would have expected the Mil to run one of the BSD variants. Perhaps even a Linux distro that is unaffected by the Linux version of the registry aka systemd.