systemd VS dracut

It isn't cleaned up at boot IIRC. Unless you leave your computer off for 30 days and then come back [1] :).

But it shouldn't be too hard to write a relativly simple systemd.unit file that does that at boot. After all the main part would be `Requires/After=local-fs.target` and something like `ExecStart=bash -c 'rm -rf /var/tmp/*'` I think (you'd need to double check what exactly to do if you want to do this).

[1] https://github.com/systemd/systemd/issues/33162

Email: v[at]vda.io

Hi HN! I'm a Linux security engineer looking for work on Open Source software. I've done some security work in the Linux Kernel (containerization primitives), in systemd as well as some work on Secure Boot.

Notably I've implemented auto-enrollment of secure boot keys in systemd. See (https://github.com/systemd/systemd/pull/20255 & https://lpc.events/event/16/contributions/1259/).

Lately, I've been very interested in MicroVMs and minimizing the Linux Kernel attack surface.

Message me if any of that sounds interesting!

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...

Upstream has been telling people not to use a central configuration file for 8 years so nobody should really be putting anything in there to begin with. One can make a reasonable argument that ZFSBootMenu ought to override the configuration file just like it overrides the configuration drop-in directory, but another can make a reasonable argument that people who really know what they want may wish to load common configuration options for both their system and ZBM images in /etc/dracut.conf.

I absolutely have no idea... Seems like somehow something is not supported. You should create an issue in the dracut repo: https://github.com/dracutdevs/dracut/issues. That's something you should probably everywhere like I did in my issue: https://www.reddit.com/r/voidlinux/comments/11ofqt2/booting_with_dinit. The void community can sometimes be really unhelpful so I hope you will get help there.

bug 1529311 is closed as duplicate of bug 1476039 which was fixed by https://access.redhat.com/errata/RHBA-2018:0964 included in dracut-033-535.el7. These patches were mentioned in 1476039: https://github.com/dracutdevs/dracut/commit/19453dc8744e6a59725c43b61b2e3db01cb4c57c and https://github.com/dracutdevs/dracut/pull/261. Also it was mentioned that it was fixed in

It's a shell script that sets up some basics and runs an event loop to run hooks that eventually lead to the availability of your root device.

dracut can build initrd with bluetooth support

The documentation is super minimal, but the livenet module supports torrent files using the live:torrent: URL syntax.

Nope, all these environments are missing initial device configuration required for keyboard to be able to connect. (There was an attempt to add bluetooth support into dracut, that didn't go well)

I get exactly this error. So it turns out, the decryption depends on a systemd unitsystemd-cryptsetup-generator, which will not read any embedded cmdline parameters, only ones passed in the commandline so when the commandline parameter is asking to decrypt things, it is not generated.