• luciferofastora@feddit.org
    link
    fedilink
    arrow-up
    8
    ·
    5 hours 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.

  • blaue_Fledermaus@olio.cafe
    link
    fedilink
    English
    arrow-up
    12
    ·
    6 hours 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
      12
      ·
      edit-2
      5 hours 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
        3
        ·
        5 hours 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
          5 hours ago

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

        • B-TR3E@feddit.org
          link
          fedilink
          arrow-up
          9
          arrow-down
          1
          ·
          8 hours ago

          Some people think before they type. They also do not think mindlessly typing “sudo” before every fucking line in bash is a valid substitute for knowing what they do. Many of them have been doing so for decades on HPUX, Solaris, BSDs and IRIX on their own and other people’s/companies machines, not just on their single bedroom machine.

      • nieceandtows@programming.dev
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        10 hours ago

        It’s easier to just call su once and run every single command as root rather than having to randomly use sudo for some commands and not for others (/s if it’s not obvious)

  • Samsy@lemmy.ml
    link
    fedilink
    arrow-up
    34
    arrow-down
    1
    ·
    11 hours 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
      ·
      7 hours 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!

  • Snot Flickerman@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    39
    ·
    edit-2
    12 hours 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
      ·
      edit-2
      8 hours 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.