• Snot Flickerman@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    30
    ·
    2 months ago

    Shut the front door!


    In a lot of situations it’s actually bad to use sudo because it can impact settings that make programs or file ownership go to root instead of the user.

    • B-TR3E@feddit.org
      link
      fedilink
      arrow-up
      1
      arrow-down
      2
      ·
      2 months ago

      You’ve got to be a damn idiot jumping over his own shadow to get that done. How would you even do that? Running

      chown -R root.root
      

      over directories or mount points? Deleting files in /dev or /run and recreating them using “touch” without looking up ownerships before? I wrote “touch” because anyone proceeding to “mknod” would at least have read some man pages. BTW, you’d need su for that rather than sudo.

  • Samsy@lemmy.ml
    link
    fedilink
    arrow-up
    25
    arrow-down
    1
    ·
    2 months ago

    But rm -fr / * seems not to work for removing the French language pack. Can someone confirm if it works with sudo?

    • plateee@piefed.social
      link
      fedilink
      English
      arrow-up
      14
      ·
      2 months ago

      Ah, I see your problem, you need to add --no-preserve-root.

      See the French are super into wine - and grape vines are notoriously hard to get rid of, so if you want to really get rid of the French language pack, you need to rip that grapevine out by the root (e.g. don’t preserve the root). Otherwise, the French language pack will just grow back harder and Frenchier than before.

      Sacrebleu!

  • SilentObserver@lemmy.world
    link
    fedilink
    arrow-up
    14
    ·
    2 months ago

    Don’t need sudo if you’re always root.

    Now excuse me. I need to call the bank and find out why my checking account is suddenly $0.

    • shane@feddit.nl
      link
      fedilink
      arrow-up
      4
      ·
      2 months ago

      And yet half the time when I’m root I preface with sudo. I can’t stop myself!

  • blaue_Fledermaus@olio.cafe
    link
    fedilink
    English
    arrow-up
    12
    ·
    2 months ago

    IMO the “year of the Linux desktop” will come when distros are designed for people who shouldn’t even be allowed to use sudo.

    • WFH@lemmy.zip
      link
      fedilink
      arrow-up
      14
      ·
      edit-2
      2 months ago

      Let me introduce you to atomic distros.

      I moved my father on Bluefin 1.5 years ago from his antique MacBook Air. He doesn’t know sudo exists. He has never heard of ujust. He doesn’t even command line. He hasn’t had to do a single update because it all happens in the background. He just… uses it.

      • Skullgrid@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        doesn’t even have to be atomic, I rescued my wife’s shit laptop using Ubuntu Mate (snaps booing in background) and she has never seen the command line unless I open it. It’s been like that for over a year at least.

        • WFH@lemmy.zip
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          2 months ago

          Yes, but contrary to atomic distros, it’s not explicitely designed to be as administration free as possible.

  • luciferofastora@feddit.org
    link
    fedilink
    arrow-up
    9
    ·
    2 months ago

    I once did a HackTheBox where the privilege escalation weakness was a cronjob running a script. I’m not sure if I correctly remember all the details, but I think it read some parameters from a file and fed them to some other script. Since it had something to do with the webserver the user was administrating, they needed write access to the file, granted via ACL. That took me a while to spot, actually. Not sure why, but ACL is a constant blind spot for me. As for passing the parameters, you can just append the contents of the file to the command and pipe it to bash.

    I don’t recall what the normal script did, but it needed writing permissions for something. The proper way to do this would be ACL, but I guess I’m not the only one with a blind spot. The easy way to ensure the script can do whatever it needs to is to sudo the whole thing.

    So what do you do if you have a script running every ten minutes, reading the first line of a file you can edit, then executing it with superuser privileges?

    Whatever the fuck you want.

  • Pommes_für_dein_Balg@feddit.org
    link
    fedilink
    arrow-up
    4
    ·
    2 months ago

    Unpopular opinion:
    On 99% of all Linux systems, you don’t need sudo.
    It’s not like you have hundreds of users with varying levels of access logging into your PC.
    Just use root for admin tasks.

    • Allero@lemmy.today
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      Su often takes more time and is more involved, even if it’s a difference between very little effort and no effort at all.

      For example, I update and install apps through CLI about once a week, and I’d rather just bang the sudo <update command> than go su, enter root credentials, and only then go for what I wanted in the first place.

      • Pommes_für_dein_Balg@feddit.org
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        su [Enter] [Password] [Command] doesn’t take longer than sudo [Command] [Enter] [Password]
        And after you’ve done it once, you can just keep the terminal open and do all other admin tasks without typing sudo
        Open another terminal (or tab) for user stuff.