• neonred@lemmy.world
    link
    fedilink
    arrow-up
    48
    arrow-down
    10
    ·
    edit-2
    1 year ago

    sudo chmod -R 777 /

    Edit: don’t do this, it will allow everyone and everything to read and modify all files of all mounted filesystems, this includes your personal files, system wide passwords, config files, everything and might break the whole system as not all files are meant to have these permissions, e.g. mapped hardware settings or your ssh key store.

    sudo comes with immense power, do not, under any circumstances, enter commands you found on the internet without an intense look about what they do and what their implications could be. Never sudo or doas, etc., without a strong and valid reason.

        • SorteKanin@feddit.dk
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Actually curious how though - I mean won’t it just let all programs/users access everything? Or do some system stuff rely on permissions for certain behavior?

          • Tekhne@sh.itjust.works
            link
            fedilink
            arrow-up
            4
            ·
            1 year ago

            SSH will definitely break, I’ve had this issue before. If your private key in the .ssh dir is too open, ssh won’t let you use it.

          • palordrolap@kbin.social
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            Theoretically yes, but yes, in that order.

            I’ve worked with Linux for decades at this point and I’m still not 100% sure exactly what breaks; it’s a mistake you make once, if at all, and you’ll only get a little way into even trying to figure out how to fix things before you throw your hands up in disgust and reinstall / restore the OS (or whatever subdir was affected).

            If I was to hazard a guess, it’s the kernel itself that balks, but there are other, almost as fundamental things (lib*.so files and the like) that may also be deliberately fussy.

            • nixcamic@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              I think it’s systemd not the kernel. If only Linux had “repair permissions” like vintage MacOS.

              • Synthead@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year ago

                You don’t typically have permissions “become defective” or need them to be “repaired” in a Linux system. Nearly all system files, with their permissions, are included in packages. Everything else should be considered user data.

                If you logged in as root and did something dumb, you could attempt to fix the permissions by reinstating packages.

              • palordrolap@kbin.social
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                Recursive chmod (or chown) has been breaking things since before systemd was a thing, so even if systemd is now responsible for stopping things from working, it can’t have been that previously, especially at the time I might have done something silly.

                As for repairing permissions only, I suppose it would be possible, assuming the system still works (or can somehow be encouraged to do so) to copy only the permissions (or at least infer them) from a backup or something rather than the whole files.

                • nixcamic@lemmy.world
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  1 year ago

                  Probably init before that then. I don’t think the kernel cares unless explicitly told to care, I’ve seen some embedded Linux with interesting permissions.

          • Phrodo_00@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            I actually don’t know how many programs do this, but several check that file permissions are correct or refuse to work. Sudo and ash are 2 of them. I could see /etc/shadow being readable and writable by everyone being a problem too, but I don’t know.

    • lseif@sopuli.xyz
      link
      fedilink
      arrow-up
      23
      ·
      1 year ago

      the 777 stands for ‘lucky jackpot number’, as in ‘youre lucky if you dont break your entire system’

    • MTK@lemmy.world
      link
      fedilink
      arrow-up
      21
      arrow-down
      1
      ·
      1 year ago

      This is so useful! Now I can just run:

      rm -rf /

      Without the sudo!

    • drdiddlybadger@pawb.social
      link
      fedilink
      arrow-up
      7
      ·
      1 year ago

      I set 777 to my whole file system on a install of Ubuntu back in the day and it does indeed fuck the install in lovely ways. I didn’t bother attempting recovery. Nice learning experience.