• @[email protected]
    link
    fedilink
    English
    929 months ago

    Real pros shuffle across the carpet to build a static charge and do their system administration by electrical fault injection.

    • @[email protected]
      link
      fedilink
      English
      69 months ago

      Jesus, every time I have to run glx or vaapi under a container I end up having to do this then cringe.

        • @[email protected]
          link
          fedilink
          English
          19 months ago

          Nah, there’s something broken, I think it’s because group render under the container has a different GID than the container so the acl fails and you either sudo or chmod.

          Lxc is still a little wobbly in places.

          • Possibly linux
            link
            fedilink
            English
            3
            edit-2
            9 months ago

            I use podman and since it runs as my user it has exactly same same permissions as me. I just add my user to the proper group and it works.

            Anyway for LXC you could just passthough a folder and then create a file. From there you can look at the file on the host to see who owns it. That will give you the needed information to set permissions correctly

            • @[email protected]
              link
              fedilink
              English
              39 months ago

              Ahh, I’m running priveleged containers, I wrote my own scripted framework for containers around lxc in mostly python.

              Basically I fell head over heels in love with freebsd jails and wanted them on Linux, then started running x11 apps in them, it’s my heroin.

              Haven’t used podman outside proper k8s for work, did proxmox for a bit, but it was just a webgui for the same thing.

              There were a bunch of online bug reports about the /dev/dri issue, maybe there’s a better solution now, but since this is my workstation I wasn’t as worried about security.

    • masterofn001
      link
      fedilink
      259 months ago

      As a one time noob I may have done this once or more.

      To get one thing working I borked everything.

      Understanding permissions is pretty basic. But understanding permission requirements for system and user apps and their config and dirs can be a bit overwhelming at first.

      Thinking a little change to make your life simpler will break something else doesn’t always register immediately.

      Shit, even recently, wondering why my SSH keys were being refused and realising that somehow i set my private keys world readable.

      Thank god SSH checks file and dir permission.

    • Dhs92
      link
      fedilink
      299 months ago

      Once had a friend run sudo chmod -R 777 / on a (public) Minecraft server we were running back in highschool. It made me die a bit on the inside.

      • Rikudou_Sage
        link
        fedilink
        239 months ago

        Doesn’t it break a lot of things? Half the stuff refuses to work when some specific files have too permissive chmod.

        • Dhs92
          link
          fedilink
          179 months ago

          Really only SSH and sudo broke. sudo would still work but you’d have to re-enter your password every time. It was a painful experience and I’m glad I know better now.

  • Kairos
    link
    fedilink
    49 months ago

    Can’t programs steal sudo access if the timeout isn’t 0?

        • @[email protected]OP
          link
          fedilink
          English
          2
          edit-2
          9 months ago

          Oh, sorry, I misread programs as programmers 😁.

          And no, I don’t think so. Credentials need to be cleared before exectution.

          • Kairos
            link
            fedilink
            19 months ago

            Okay. So you must invoke sudo fr on the exact same shell? It cant be taken from a subsequent script?

            • @[email protected]OP
              link
              fedilink
              English
              2
              edit-2
              9 months ago

              Credentials are inherited by every child process that the parent process invokes. Thus, if you give root credentials to a command, every subsequent command that the original one invokes will have root credentials.

              There are some exceptions, but these are special case scenarios and are literally only a few.

              • Kairos
                link
                fedilink
                19 months ago

                That doesnt at all answer my concern but I’ll interpret the answer as no it doesn’t do that.

                • @[email protected]OP
                  link
                  fedilink
                  English
                  2
                  edit-2
                  9 months ago

                  Sorry (again 😂, this happens quite a lot with you, lol), it’s early in the morning here, didn’t have my coffee yet.

                  If the question is can privileges be escalate later on while a command or a script is executing, the answer is yes. You can also deescalate them once the root creds stuff is done executing. You just have to make it clear in the script or the command that “you do this with root creds, but then you continue with user creds”.

                  The point I was trying to make with my previous comment was that, if a process (command, script, whatever) is ran with root privileges, every program, command, script it invokes later on is ran with root privileges, unless it’s specifically noted to run this or that part with some other privileges.

  • @[email protected]
    link
    fedilink
    139 months ago

    Reminds me of software saying to put your docker socket into the docker container you are starting for convenience.

  • @[email protected]
    link
    fedilink
    39 months ago

    Use Sudo -i instead. Sudo su is like cat file | grep pattern vs grep pattern file. You’re wasting resources.

  • @[email protected]
    link
    fedilink
    English
    149 months ago

    Our crappy vendor software will only function if IPv6 is disabled network wide. Even if one machine has it enabled, the whole thing breaks

    Lol our former crappy vendor solution required to be run directly from AD Administrator. Pure luck the entire business didn’t collapse before we replaced it.

    A thread I read a long time ago on r/sysadmin

    • Laurel Raven
      link
      fedilink
      English
      39 months ago

      “You’re absolutely right, we wouldn’t want to take too long to break the network or open god rights vulnerabilities”