• tiramichu@lemm.ee
      link
      fedilink
      arrow-up
      33
      ·
      edit-2
      3 months ago

      Read/write/execute file permissions.

      Having them set incorrectly can cause problems, such as creating a file as root then leaving you unable to modify it as user, being unable to execute a script because execute is not set, or being unable to use your SSH keyfile because you left the permissions too open.

      It’s more actually like “Why is it, when something doesn’t happen, is it always you three”

    • tofu@lemmy.nocturnal.garden
      link
      fedilink
      English
      arrow-up
      8
      ·
      3 months ago

      It’s the Linux file permissions. If something doesn’t work properly, it’s often due to wrong permissions because the app can’t save/read it’s stuff

    • nerdovic
      link
      fedilink
      Deutsch
      arrow-up
      6
      ·
      3 months ago

      Maybe the recent events had something to do with ye good olde chmod 777

      • amorpheus@lemmy.worldOP
        link
        fedilink
        arrow-up
        3
        ·
        3 months ago

        Was 700, should have been 755… 777 is more like the “just put sudo in front of the command” nuclear option.

        • nerdovic
          link
          fedilink
          Deutsch
          arrow-up
          2
          ·
          3 months ago

          I had a fuckup by qualys recently that basically did what you described on many of our RHEL machines, broke a few things.

  • enumerator4829@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 months ago
    # echo ”SELINUX=enforcing” > /etc/selinux/conf
    # echo ”SELINUXTYPE=mls >> /etc/selinux/conf
    # reboot
    

    Come on, it will be fun!