I see people talking about doas saying it’s just like sudo but with less features. I’m just wondering if there is any situation where you should use doas or if it’s just personal preference.

  • Kalcifer@sh.itjust.works
    link
    fedilink
    arrow-up
    2
    ·
    8 months ago

    doas, afaik, was originally made for FreeBSD, so some of its features aren’t compatible with/haven’t been implemented for Linux. That may or may not be an important issue for you to consider.

  • lily33@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    8 months ago

    On the one hand, doas is simpler. Less code means less bugs, and lower chance someone manages to hack it and gain admin rights. On the other hand, sudo is more popular, and so has a lot more people double-checking its security. Ultimately, I don’t think it matters - when someone unauthorized gains admin rights, usually it’s not due to bug in sudo or doas, but other problems.

    • tetris11@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      Well said. Check your firewalls, check your ssh config, liberally use user repositories, and always tip the guard (donate to GNU)

  • MonkderZweite@feddit.ch
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    Doas has about 90% of features with 10% of code size of sudo.

    And rdo/ssu have ~140 lines of C code. Anyone knows similiar?

  • PoorPocketsMcNewHold@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    Well, i believe in all showcased cases from people here, they are NOT replacing sudo entirely (Except if some are from BSD or if I’m incorrect with this assumption). They are just replacing their user habit with doas and use that command instead. In the end, all unix scripts or apps expect using sudo (If not, su) so… ### What’s even the need to ?

    • Size : Installed on top of the already system present sudo.
    • Security : Only perhaps if you made a sudo alias to doas (But since it isn’t entirely 1:1 identical, if anyone have a cleaner way of implementing that, I’m all hear)
    • Simplicity : You now have two tools. A easy to use keycard, and a key. The second is more complicated to use, so you use it rarely but it’s still two tools instead of one.
    • Less dependencies : Again, unless you can actually replace it ENTIRELY, it’s just an added tool (Still almost dependency free)

    Really looking to corrections if i do some

  • jimbolauski@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    Security may be more likely to approve some users having doas, sudo is a no go in many restricted environment.

  • WalrusByte@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    From what I hear, doas is more secure. I don’t think it matters though, as long as you keep your system updated. I use sudo still.

  • Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    8 months ago

    Doas is more secure, sudo has had a few critical vulnerabilities in the past, because the codebase is much larger. Sudo has like a million features that most people don’t need, but they significantly increase attack surface.

    • corsicanguppy@lemmy.ca
      link
      fedilink
      arrow-up
      3
      ·
      8 months ago

      Doas is more secure, sudo has had a few critical vulnerabilities in the past, because

      … it’s newer. You wanted to say “it’s newer.” It has nowhere near the history, and looks better because it’s newer.

      Please, now, trot out the “use sudo if you’re old” memes, because we grew that skin extra thick over the systemd counter-hate.