• 0 Posts
  • 5 Comments
Joined 2 years ago
Cake day: August 25th, 2023
  • it_a_me@literature.cafetoRust@programming.dev•The First Stable Release of a Memory Safe sudo Implementation
    2·
    2 years 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.

  • it_a_me@literature.cafetoRust@programming.dev•The First Stable Release of a Memory Safe sudo Implementation
    63·
    2 years 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