• kenkenken@sh.itjust.worksEnglish
    831·
    3 days ago

    I will use it. I don’t care what others think. People can use su, sudo, doas, run0 by their choice, and I don’t see why we need a common opinion about it.

      • Skull giver@popplesburger.hilciferous.nl
        103·
        3 days ago

        A lot of people are afraid of systemd expanding because systemd handles a lot of stuff, so distros are likely to support it rather than the mishmash of tools they personally prefer. It all started with the System-V/Upstart replacement and now very few distros have the patience to customise and roll out the 90s style service management anymore. Their preferences used to align with the mainstream, but no longer do these days, and that causes friction.

        This process pushes people who prefer old tools to fringe distros, and newer software is less likely to work on their setups. They’re still free to use whatever system they like, of course, but the burden for developing and maintaining daemon management scripts is now on their fringe distro or themselves if their distro doesn’t have anything yet. I’d find that pretty annoying too, especially with how convoluted many older system management scripts are and how many moving parts are typically involved. Plus, some stuff like socket activation can’t even be done with some of the older init systems so people have to find alternatives.

        I doubt anyone reeling against run0 was ever going to consider it anyway.

  • mexicancartel@lemmy.dbzer0.comEnglish
    144·
    2 days ago

    su is the best. I mean, i should be using the admin (root) password for admin things, not the user password of user who is already logged in. And there needs to be a root service already running to make user have root previlages which is dumb imo. Sudo vulnerability could cause previlage escalation but if there is no root process managing this, then it can’t leak the root access. Only kernel security issue(or other root processes) will leak root access if that was the case, which i think is better.

    • Cryxtalix@programming.dev
      3·
      1 day ago

      The permission to do admin things is given by the root user, to your account. So you have to verify your identity by entering your password.

      Isn’t that how it is? I though that was analogous to how almost everything worked IRL. Whether withdrawing funds from a bank or engaging government services, you prove your identity as a customer/citizen to get the relevant services. At no point do you login to bank or government computers with full privileges.

      • mexicancartel@lemmy.dbzer0.comEnglish
        2·
        19 hours ago

        If you own your own bank, then i think you login as the one with full previlages. Yes when doing administrator things, you have to use sudo. The problem with root with sudo is, you authenticate as a user, then gain full permission from root, i.e analogous to login in to bank with full previlages.

        As a person who need to run sudo command its better to just verify yourself as root user to gain “full access”. I’m not saying about partial previlages. That is i just need a script which is just su -c with environment variables being copied

  • AndrewZabar@lemmy.world
    10·
    2 days ago

    I’m surprised they would implement having just run0 effectively log you in as root. For the super security conscious constrictions of the command versus sudo, it would seem that the very notion of elevating your privilege beyond the single command to be carried out, would be anathema to the whole goal of this new command. Evidently not, but it’s surprising to me.

    • Vilian@lemmy.ca
      1·
      2 days ago

      you can run a command using run0 it’s only elevating that commads, sometimes it’s needed to login as root, it’s life

        • LeFantome@programming.dev
          4·
          1 day ago

          They did not miss anything. They just used commas where periods should be.

          You can run a command using run0. It’s only elevating that command. Sometimes it’s needed to login as root. It’s life.

          The way it is written, semi-colons may be more appropriate but that would be a lot of them.

          • laughterlaughter@lemmy.world
            1·
            1 day ago

            You actually pointed out that they did, indeed, do miss a period (the one after “run0.”)

            you can run a command using run0 it’s only elevating that commads,

      • Vilian@lemmy.ca
        52·
        2 days ago

        ok them go suffer alone in your 2004 distro that can’t update bash because it break the 400 scripts that it use to boot lmao

  • onlooker@lemmy.ml
    15·
    3 days ago

    I don’t know, we’ll just have to see. But personally, I am not a fan of tying so many functionalities to systemd.

  • steeznson@lemmy.world
    145·
    2 days ago

    I’m going to continue to keep avoiding Poettering software for as long as he continues to act like a jackass. Even his commit messages are dripping with condescension.

    • shapis@lemmy.ml
      192·
      2 days ago

      Funny. I didn’t know a single thing about the person. But that commit message made me like him more.

      Ofc assuming he was just making a light-hearted joke in it.

      • steeznson@lemmy.world
        131·
        2 days ago

        Users were complaining that their terminal transparency was being broken by the nspawn container and that the colour for other applications like tmux were being affected by it. For example tmux was appearing in the same navy blue in the terminal emulator instead of its usual green.

        Idk he’s just a hot take merchant basically. He has a particular hate-boner for distros that don’t use systemd as the default init system like void and gentoo (usually these are troll tweets as opposed to commit messages though).

        • Vilian@lemmy.ca
          210·
          2 days ago

          Idk he’s just a hot take merchant basically. He has a particular hate-boner for distros that don’t use systemd as the default init system like void and gentoo (usually these are troll tweets as opposed to commit messages though).

          shut up, wtf that has todo with the commit, people who don’t use systemd it’s not going to complain about the color of something that they don’t use

  • LainTrain@lemmy.dbzer0.com
    641·
    3 days ago

    If you make users sign in too much, they will just make their passwords short and easy to remember, even 24hrs is too much and people bitch about it all the time, especially since we have password managers enforced, meaning every time they need to Auth they need to Auth into their system, Auth into their password manager, copy the password, auth into their phone, look at the 2FA code and type that in.

    Doing this every day just to open email is understandably fucking enraging even to me as a security “”“engineer”“”/analyst/${bullshitblueteamemailreaderjob}

    Press it harder and they will use simple passwords that will inevitably be passed through to something external (e.g. cockpit which even I can bruteforce) or reused somewhere at some point, and then someone just has to get lucky once and run whatever run0 sudo su <reverse shell bs here> to bypass all protections.

    • TBi@lemmy.world
      7·
      3 days ago

      I agree with you. If i had to add my password everytime I’d just add my personal account to sudo group.

      Good security works with people, not against them.

  • exu@feditown.comEnglish
    40·
    3 days ago

    I might try run0 for fun, but I don’t think it’ll replace sudo any time soon.
    The biggest issue I see is run0 purposely not copying any environment variables except for TERM.
    You’d have to specify which editor to use, the current directory, stuff like PATH and HOME every time you run a command.

    • Skull giver@popplesburger.hilciferous.nl
      15·
      3 days ago

      sudo had several severe security bugs caused by copying env variables so I’m not surprised run0 isn’t doing much of that. I’ve had to help a whole bunch of people fix the permissions/ownership on their Jo. E directory after running sudo so I can even see the point of jot copying $HOME by default.

      I don’t think it’ll replace sudo necessarily, or doas would’ve done that already. It’s still useful as a shorthand for systemd-run and in some locked down system configurations I can see it being useful (i.e. when minimising the amount of SUID binaries). Maybe some elaborate enterprise setups will switch to it for security reasons, especially if they’re already leveraging PolKit heavily.

    • kbal@fedia.io
      61·
      3 days ago

      I’m not a fan of the idea at all, but come on, it can’t really be that bad. There’s got to be somewhere you can tell it what environment variables to use. Probably something like run0 systemd-edit /usr/system/systemd/systemrun/run0-environment --system-default=system

    • velox_vulnus@lemmy.ml
      72·
      3 days ago

      Wouldn’t it be better to just use containers then? Nix and Guix has the exact thing - you get to control what variables you want to pass in.

      • exu@feditown.comEnglish
        2·
        3 days ago

        You can’t really install packages or modify configs on the host without root. Containers can only do some parts.

      • exu@feditown.comEnglish
        1·
        3 days ago

        Maybe, but now I still need to remember the alias or distribute it to any machine I’m working on.
        Not that difficult if you have everything managed with Ansible or similar anyways, but lots of people likely don’t have that setup.

    • qaz@lemmy.world
      142·
      3 days ago

      sudo has more than 220k lines of code, I can definitely see the use of a simpler alternative.

        • TMP_NKcYUEoM7kXg4qYe@lemmy.world
          4·
          3 days ago

          run0 is just an alias for a part of systemd, so installing doas too would be useless bloat. Another thing to note is that doas is just smaller sudo, you still wouldn’t use 99 % of its features.

          edit: also from my totally surface level understanding both sudo and doas “elevate your privileges” which is supposedly unnecessary attack surface. run0 does it in a better way which I do not understand.

          • Laser@feddit.org
            7·
            2 days ago

            also from my totally surface level understanding both sudo and doas “elevate your privileges” which is supposedly unnecessary attack surface. run0 does it in a better way which I do not understand.

            sudo and doasare setuid binaries, a special privileged bit to tell the kernel that this binary is not run as the user starting it, but as the owner. A lot of care has to be incorporated into these to make sure you don’t escalate your privileges as the default interface is very limited, being a single bit.

            Another issue with this approach is that since you’re running this from your shell, the process will by default inherit all environment variables, which can be convenient, but also annoying (since a privileged process might write into your $HOME) or upright dangerous.

            run0doesn’t use that mechanism. systemd is, being a service manager at its core, something launching binaries in specialized environments, e.g. it will start an nginx process under the nginx user with a private tmp, protecting the system from writes by that service, maybe restrict it to a given address family etc. So the infrastructure to launch processes – even for users via systemd-run– is already there. run0 just goes one step further and implements an interface to request to start elevated (or rather with permissions different from their own) processes from a user’s shell.

            Classic solutions do it like this:

            1. user starts binary with setuid (let’s say sudo) that runs with root (because that’s the owner of the binary) privileges in their shell. Since this is a child process of their shell, it inherits all environment variables by default.
            2. sudochecks /etc/sudoers if that user is authorized to perform the requested action and either denies the request, performs it or asks for authentication.
            3. a new process is spawned from it, again inheriting the environment variables that were not cleaned, as you can’t get rid of variables by forking (this is often an issue if you have services that have their secrets configured via environment variables)

            With run0:

            1. user starts run0 binary as a user process. This process inherits the environment variables.
            2. run0 forwards the user’s request via interface to the running systemd process (pid 1 I guess). That process however does not inherit any variables by default, since it was started outside the user’s shell.
            3. systemd checks if the user who started the run0 binary is allowed to perform the requested operation and again, either denies the request, performs it or asks for authentication.
            4. a new process is spawned from it, but it will only receive the environment variables that were explicitly requested as there’s no inheritance.

            At least that’s my understanding, I haven’t looked too much into it or used it yet.

            • Vilian@lemmy.ca
              2·
              2 days ago

              the pid1 part is wrong, only the systemd-init run in pid1, in it’s own process, own binary etc, it’s sole purpose is being an init system, after that it start the rest of the system, including the others systemd binaries

              the rest is perfect thanks!, in the lennart he made a comparation with ssh were you “forward the commad to run as root”, i think it’s a good analogy

          • Vilian@lemmy.ca
            2·
            2 days ago

            . run0 does it in a better way which I do not understand.

            it does that in a “ssh like” that i read in the blog, they foward your commands, they don’t elevate your user, they also use polkit for security intead of sudoers

    • TMP_NKcYUEoM7kXg4qYe@lemmy.world
      2·
      3 days ago

      The original problem was to automagically prompt the user for password, if he tried to run some systemd executable without the wheel privileges. At some point they decided to reuse the code for [a command that allows you to run stuff as root] replacement because sudo is too bloated and vulnerable.

    • wer2@lemm.ee
      241·
      3 days ago

      Also, you can configure sudo to prompt every time if you really want.

      I was on a system that was configured that way for “security”, so I would just ‘sudo bash’ which is obviously much safer /s.

      • MadMaurice@discuss.tchncs.de
        5·
        3 days ago

        My system is configured that way (by me) and I regularly use sudo -s.

        I just want to see if there’s a root shell and not rely on some hidden timeout 🙄

        • wer2@lemm.ee
          1·
          2 days ago

          The beauty of Linux at home, you get to choose what works best for you.

    • TMP_NKcYUEoM7kXg4qYe@lemmy.world
      21·
      3 days ago

      Yeah I mean at that point it’s redundant because you might as well type su -c “some command here”. On the other hand having such alias does no harm if you’re already using systemd.

    • PoorPocketsMcNewHold@lemmy.mlEnglish
      3·
      3 days ago

      Speaking of doas, is there any advantage of using it when… sudo is still available to be used? I agree that most of the stuff we require to use doesn’t need all the options sudo as, but if it is for the sake of security, maintenance, and stability… is there any reason to use doas ON TOP of the already setup sudo or su? In the past, I even tried to just apply a simple alias to replace sudo with doas, but numerous scripts and programs when trying to request explicit super-user permissions, just didn’t know what to do with doas as expected, so this ain’t it.

      • Samueru@lemmy.ml
        4·
        2 days ago

        Speaking of doas, is there any advantage of using it when… sudo is still available to be used?

        I like that its configuration file is very very simple.

      • Titou@sh.itjust.works
        3·
        3 days ago

        I agree that most of the stuff we require to use doesn’t need all the options sudo as

        Main reason of using doas

        but numerous scripts and programs when trying to request explicit super-user permissions, just didn’t know what to do with doas as expected

        I’ve only found one software like that and it’s tipi, and it’s kinda dumb for a software to require such a easily replacable software. Also how openbsd users are supposed to do ? Having both doas and sudo on their machine which is unnecessary bloat ?

  • electricprism@lemmy.ml
    103·
    3 days ago

    Sometimes I really hate the utility names people come up with.

    I would love to see chatgpt rename all the core utils in a way that summarizes their function.