5 ms·

A trivial Google search answers that. run0 requires systemd-type OS.

• ranger207 1y ago
  Given that Ubuntu uses systemd like the vast majority of Linux systems nowadays, how does sudo-rs differ from run0?
  • fweimer 1y ago
    You might not have a systemd instance inside a container, but you still might want to switch user IDs there.
    • Vilian 1y ago
      Podman has systemd inside, you can run0 in it
      • yjftsjthsd-h 1y ago
        Not all containers are on podman
      • fweimer 1y ago
        Surely that depends on the container? Podman doesn't artificially inject a systemd process as PID 1 by default.
  • hedora 1y ago
    sudo-rs doesn’t gratuitously require a root privilege daemon that regularly ships filesystem destruction and remote unauthenticated arbitrary code execution bugs. If your bar is “I’ll tolerate such crap”, you may as well run your desktop session as root.
    • zahlman 1y ago
      If sudo does this, as you imply, why do Linux system still exist that are not part of a botnet?
      • paulddraper 1y ago
        Implication is that systemd does this, not sudo.
    • Vilian 1y ago
      Nice technical argument, did Lennart bite you while you where sleeping?
  • paulddraper 1y ago
    sudo-rs uses setuid. run0 does not (and instead relies on systemd). --- To answer your next question: setuid, while historic, is a bit weird, and is disabled in some environments, e.g. NoNewPrivileges.
  • Vilian 1y ago
    The Lennart post about it explain it https://mastodon.social/@pid_eins/112353324518585654 https://mastodon.social/@pid_eins/112353324518585654 He was comparing to "normal" sudo, but sudo-rs have the same problems he highlighted anyway
• postepowanieadm 1y ago
  No one is rewriting systemd in rust?
  • steveklabnik 1y ago
    I'm not aware of any serious project to do so, there's been some small projects, nothing on the scale of uutils or sudo-rs.