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"
10 Comments
exu@feditown.com · 16 pts · 1y
I'm too octal to understand this meme
RustyNova@lemmy.world · 8 pts · 1y
I don't get it
tiramichu@lemm.ee · 33 pts · 1y
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 · 8 pts · 1y
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@discuss.tchncs.de · 6 pts · 1y
Maybe the recent events had something to do with ye good olde
chmod 777amorpheus@lemmy.world · 3 pts · 1y
Was 700, should have been 755... 777 is more like the "just put sudo in front of the command" nuclear option.
nerdovic@discuss.tchncs.de · 2 pts · 1y
I had a fuckup by qualys recently that basically did what you described on many of our RHEL machines, broke a few things.
veniasilente@lemm.ee · 7 pts · 1y
Hermione being
rmakes sense.enumerator4829@sh.itjust.works · 4 pts · 1y
Come on, it will be fun!
Ferroto@lemmy.world · 2 pts · 1y
Where's my 777 homies at