#Linux or #unix Permission just gives more trouble. Let us fix it. 🤣
@nixCraft sudo rm -rf /

@gulfie Only on non-GNU systems, or old enough GNU systems :-) (and that is if no other system implements something similar to what #GNU has in the rm utility)

For GNU rm, I think you need

rm -rf --no-preserve-root /

@nixCraft

#UNIX

@nixCraft Funny, but I really got an user who did it.
It broke the entire VM because several services refused starting with wrong permissions on critical files.
@dawnaur @nixCraft ssh will give you bombastic side eye if your ~/.ssh folder is 777.
@nixCraft `chmod +s /usr/bin/*`
@nixCraft sudo usermod -u 0 $USER
@nixCraft I remember doing 777 on my iPhone when I was a kid. It was jailbroken.

@nixCraft When I first installed Linux, I was coming off Windows 95, and I was frustrated that some files needed permissions so I gave everything 777

It was a learning experience, for sure. From the resulting chaos, I decided to actually read a book on using Linux instead of just winging it.

@nixCraft Can relate. Had to log into root for a very specific task today.
chmod -R +s /usr/bin /usr/sbin
@nixCraft
@nixCraft I would like to know more about strategies people use setting privileges. At one point I made some kind of rbac model with groups but that was a lot of work and difficult to explain to peers. What is the strategy you use? Just keeping distro defaults?
@nixCraft you forgot the setuid bit in the last panel 😈
@nixCraft One set chmod -R / 777 in my production server.
That was a shitty day