UNIX/Linux Files/Folders where 777 Permissions is a No No

on
Running “chmod -R 777 /” on a UNIX/Linux system is destructive (see Why is “chmod -R 777 /” destructive? for a very good write up). The following post is an attempt to list all the Files/Folders where having 777 permissions on them will stop certain things working.

Note: I don’t say break since by design certain UNIX/Linux applications will simply not work if they see the 777 - maximum permissive - permission on certain files/folders, to keep the user safe.

Please feel free to add comments with other Files/Folders, and I will endeavour to update the list.

Files/Folders [Sources]

/usr/bin/sudo [2][3]
/etc/mail (SendMail) [3]
/.ssh [3][4][5][7]
/tmp [3]
/var/tmp [3]
/dev [3]
/proc [3]
~ [4][6]
/home/{your_user} [4]
authorized_keys [4][5][13]
authorized_keys2 [7]
sssd.conf [8]
/authorizedkeys [9]
authorized-keys [9]
$HOME/.ssh [10]
id_dsa [10]
id_rsa [10]
id_dsa.pub [10]
id_rsa.pub [10]
known_hosts [10]
/var/www/RESTRICTED_DIR [11]
/root [12]

+ sockets [3]
+ pipes [3]

References

[1] What UNIX/LINUX applications break if they see 777 permissions? [on hold]
[2] How to fix sudo after “chmod -R 777 /usr/bin”?
[3] Why is "chmod -R 777/" destructive?
[4] SSH Authentication Refused: Bad Ownership or Modes for Directory
[5] Authentication refused: bad ownership or modes for file /var/git/.ssh/authorized_keys
[6] Fixing Authentication refused: bad ownership or modes for directory
[7] SSH Authentication refused: bad ownership or modes for file /home/user/.ssh/authorized_keys2
[8] JP
[9] Openssh Connection does not work with AuthorizedKeysCommand
[10] Authentication refused: bad ownership or modes for file
[11] bad ownership or modes for chroot directory component
[12] OpenSSH server Authentication refused
[13] Authentication refused: bad ownership or modes for file .ssh/authorized_keys

Comments

Post a Comment