systemd VS systemd

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

Retrieve the archive containing the JBoss Web Server from the Red Hat Customer Portal and install the files on the system. Configure the Red Hat Enterprise Linux (RHEL) operating system including the users, groups, and the required setup files to enable JBoss Web Server as a systemd service. Ensure the required Java Virtual Machine is installed Fine-tune the configuration of the JBoss Web Server server, such as binding it to the appropriate interface and port. Deploy web applications along with enabling and starting the JBoss Web Server as a [systemd](https://www.freedesktop.org/wiki/Software/systemd/) service. Perform a health check to ensure that the deployed application is accessible.

A systemd-free fork from Debian Linux+GNU

Devuan is a fork of Debian GNU+Linux without systemd.

This post shows how to install and run Docker on Devuan, a systemd-free fork of Debian.

I built the dev env on Devuan GNU+Linux, a fork of Debian without systemd. It resembles my past trial on Artix Linux.

Devuan GNU+Linux is a fork of Debian without systemd and hence Snaps (Snapd). Even on it, it's easy to install Android Studio and start to develop Android mobile apps.

[root@rocky-8-lxc ~]# rpm -qf /etc/rc.d/rc.local systemd-239-68.el8_7.4.x86_64 [root@rocky-8-lxc ~]# rpm -qi systemd Name : systemd Version : 239 Release : 68.el8_7.4 Architecture: x86_64 Install Date: Fri 07 Apr 2023 02:11:42 AM UTC Group : Unspecified Size : 11306123 License : LGPLv2+ and MIT and GPLv2+ Signature : RSA/SHA256, Tue 21 Feb 2023 05:04:34 PM UTC, Key ID 15af5dac6d745a60 Source RPM : systemd-239-68.el8_7.4.src.rpm Build Date : Tue 21 Feb 2023 04:52:49 PM UTC Build Host : ord1-prod-x86build004.svc.aws.rockylinux.org Relocations : (not relocatable) Packager : [email protected] Vendor : Rocky URL : http://www.freedesktop.org/wiki/Software/systemd Summary : System and Service Manager Description : systemd is a system and service manager that runs as PID 1 and starts the rest of the system. It provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux control groups, maintains mount and automount points, and implements an elaborate transactional dependency-based service control logic. systemd supports SysV and LSB init scripts and works as a replacement for sysvinit. Other parts of this package are a logging daemon, utilities to control basic system configuration like the hostname, date, locale, maintain a list of logged-in users, system accounts, runtime directories and settings, and daemons to manage simple network configuration, network time synchronization, log forwarding, and name resolution.