Prossimo is pleased to announce the first stable release of sudo-rs, our Rust rewrite of the critical sudo utility. The sudo utility is one of the most common ways for engineers to cross the privacy boundary between user and administrative accounts in the ubiquitous Linux operating system. As such, its security is of the utmost importance. The sudo-rs project improves on the security of the original sudo by: Using a memory safe language (Rust), as it's estimated that one out of three security bugs in the original sudo have been memory management issues
    • snaggen@programming.devEnglish
      10·
      1 year ago

      If that works for you and you are happy with it, fine. But sudo-rs seems to have a bit of a different usecase since it is intended as a drop in replacement for sudo, hence it must be able to handle the sudoers file aso. It still removes some of the never-used obscure functionality that sudo had, so it is probably a lot smaller code base than original sudo.

      • lysdexic@programming.devEnglish
        41·
        1 year ago

        But sudo-rs seems to have a bit of a different usecase since it is intended as a drop in replacement for sudo, hence it must be able to handle the sudoers file aso.

        Other than being yet another “standard tool X clone written in Rust” project, does it actually provide any tangible value?

      • it_a_me@literature.cafe
        52·
        1 year ago

        1. Opendoas has a significantly smaller codebase. It only has 4397 lines of code compared to Sudo-rs’s staggering 35990 lines.

        2. It has a very simple config file which can do everything I want in less than 6 words.

        3. It is a soft fork of BSD’s doas package and receives frequent audits(something I find reassuring since it is a method to gain root access on my system.

        4. I don’t want or need 99% of the features sudo provides so I appreciate the simplicity and lightness of opendoas

        • RunAwayFrog@sh.itjust.works
          51·
          1 year ago

          Opendoas has a significantly smaller codebase. It only has 4397 lines of code compared to Sudo-rs’s staggering 35990 lines.

          Hmm.

          % tokei src | rg ' (Language|Total)'
 Language            Files        Lines         Code     Comments       Blanks
 Total                  76        16243        13468          682         2093

          % tokei src test-framework | rg ' (Language|Total)'
 Language            Files        Lines         Code     Comments       Blanks
 Total                 196        34274        27742         1072         5460

          % git grep '#\[cfg(test)\]' src |wc
     40      44    1387

          I too love making unaware “Tests Considered Harmful” arguments based on some blind analysis.

          Funnily enough, one could easily do some actually potentially useful shallow analysis, instead of a completely blind one, simply by noticing the libc crate dependency, then running:

          git grep -Enp -e libc:: --and --not -e '(libc::(c_|LOG)|\b(type|use)\b)'

          Ignoring the usage in test modules, use of raw libc appears to be more than you would think from the title. One can also argue that some of that usage would be better served by using rustix instead of raw libc.

          Of course authors can counter with arguments why using rustix* is not feasible or would complicate things, and would argue that the use of unsafe+libc is required for this kind of project, and it’s still reasonably limited and contained.

          And a little bit more informed back-and-forth discussion can go from there.

          * Searching for rustix in the sudo-rs repo returned this. So this predictably has been brought up before.

          • it_a_me@literature.cafe
            2·
            1 year ago

            I’m sorry but I don’t understand whatever argument you’re making. I did the line count on my phone via termux because I was in a rush, so i’m aware the counts may be inaccurate. I should have made that clear in my earlier reply.

            I do, however, hold to the fact that any sudo implementation will be more complicated than doas. Sudo, as a project, has more options and usecases than doas so it also has more posibilities for bugs or misconfiguration for the user.

            I’m unable to tell what codebase your are refering to with you’re grep arguments, sorry.

            • RunAwayFrog@sh.itjust.works
              1·
              1 year ago

              I do, however, hold to the fact that any sudo implementation will be more complicated than doas. Sudo, as a project, has more options and usecases than doas so it also has more posibilities for bugs or misconfiguration for the user.

              Fair.

              I’m unable to tell what codebase your are refering to with you’re grep arguments, sorry.

              sudo-rs

  • ck_@discuss.tchncs.de
    3·
    1 year ago

    It might be a drop in replacement to sudo, but I would not use it as such for a while. If you look at the bugs that sudo had over the years, only a fraction of them have been caused by unsafe memory operations. The majority has been caused be its own complexity and the complexity of the sudoers file. These problem classes are not going away by porting the tool over to Rust or any other language. Since this is a rewrite, it will have its own security bugs that need to be found and fixed first. So until sudo-rs has had a couple of years of people fixing security issues, I’d rather not adopt it.

    Given that, I have a hard time imagining why someone would pour time and resources into a rewrite of sudo for years to come instead of working towards a simpler solution.