systemd VS elogind

No, the OP was not sent any harassment, the OP _did_ the harassment as it can be seen in the tweets. I mean, they are right there, just click on the links you shared. One of the OP's followers even openly called for the assassination of the project maintainer, and you have the galls to defend him? This is truly deranged stuff.

And again, there is no "vulnerability", there is simply a person that doesn't know how Linux works and has learned something new. Which again it's fine, nobody knows everything and we all learn new things everyday, it's just that normal and sensible people don't use that to make grand claims on social media and start harassment campaigns culminating in death threats.

Professional security researchers responsibly report real issues using the appropriate channels, such as defined at: https://github.com/systemd/systemd/security/policy this is not the work of a researcher, this is a grifter looking for self-promotion on social media.

> 3. even `adduser` will not allow it by default

5. useradd does allow it (as noted in a comment). 6. Local users are not the only source, there things like LDAP and AD.

7. POSIX allows it:

* https://github.com/systemd/systemd/issues/6237#issuecomment-...

> I for one love to type out 13 extra characters

FWIW, systemd is normally pretty good at providing autocomplete suggestions, so even if you don't want to set up an alias you'll probably just have to type `--b ` to set it.

> I wonder what random ASCII escape sequences we can send.

According to the man page source[0]:

> The color specified should be an ANSI X3.64 SGR background color, i.e. strings such as `40`, `41`, …, `47`, `48;2;…`, `48;5;…`

and a link to the relevant Wikipedia page[1]. Given systemd's generally decent track record wrt defects and security issues, and the simplicity of valid colour values, I expect there's a fairly robust parameter verifier in there.

In fact, given the focus on starting the elevated command in a highly controlled environment, I'd expect the colour codes to be output to the originating terminal, not forwarded to the secure pty. That way, the only thing malformed escapes can affect is your own process, which you already have full control over anyway.

(Happy to be shown if that's a mistaken expectation though.)

[0] https://github.com/systemd/systemd/blob/main/man/run0.xml

[1] https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_(Select_G...

bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completio...

the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237

PS: https://pwnies.com/systemd-bugs/

https://github.com/systemd/systemd/issues/32028#issuecomment...

There are some very compelling arguments made there if you care to read them

Maybe it was because you weren't pointing out anything new?

There was a pull request to stop linking libzma to systemd before the attack even took place

https://github.com/systemd/systemd/pull/31550

This was likely one of many things that pushed the attackers to work faster, and forced them into making mistakes.

The PR for changing compression libraries to use dlopen() was opened several weeks before the xz-utils backdoor was revealed.

https://github.com/systemd/systemd/pull/31550

I think it was at one point. But then the part of systemd where that happened got forked so that's not been the case for years now.

elogind and eudev are forks of logind and udev respectively in order to remove systemd as a dependency and are not part of systemd itself. In the links above there are also a pretty clear reasoning behind making those forks.

Same problem here with Void. Nvidia drivers work fine on systemd distros like Arch and Fedora. I'm assuming you're using elogind for handling acpi events? If yes then I'm in a similar boat. I compared Fedora's suspend process to Void's and apparently nvidia package on Void doesn't install nvidia-sleep.sh to /usr/bin. So, I copied nvidia-sleep.sh from Fedora manually to Void's /usr/bin and added a script for pre and post suspend events that elogind handles (these events are handled by systemd services on Fedora). I found the script on this github issue.

This is technically not true. The hard dependency was only on systemd-logind which is part of the systemd project.The elogind project extracted systemd-logind from systemd and made it usable under non-systemd inits. With elogind, it's possible to run GNOME under other init systems.

I'm just going to throw out an easy example here, but there's more than one. This is elogind's github: https://github.com/elogind/elogind

How come Gentoo has to extract logind into a separate program, elogind, into its own package? Into its own repo? Why can't it just have logind directly?

Now there's elogind to replace logind, but I haven't tried if it actually works with systemd. Back in the day you could also just have used ConsoleKit on arch to launch your desktop session, but I don't know if that still works.