2

Can I run chmod o=- -R / ?

I don't want a newly created user to be able to cat /etc/passwd, just because of its default permissions. And I want to understand why these defaults were chosen for permissions on all (well most) system files as well as for other files.

Cian
  • 5,838
  • 1
  • 28
  • 40
Devrim
  • 1,187
  • 4
  • 16
  • 29
  • thanks for the answers, /etc/passwd was just an example to illustrate the issue. we were just looking for an appArmor, grSecurity kind of solution without using any. now we know that we have to. – Devrim Sep 14 '09 at 23:59
  • Great question and answers, great reference. I attempt to now resolve the "flip side" of the above question by asking: [do "best practices" call for disabling world/other system-files access for any reason beyond private keys or passwords](https://serverfault.com/q/988854/104173)? – Johnny Utahh Oct 21 '19 at 18:11

4 Answers4

10

Because many programs might need access to those files. As an example, whenever you do an 'ls -l', the system will look up /etc/passwd to translate between numerical uid and the username. This wouldn't work if the user didn't have any rights to read that file.

Even more important, if you would take the read rights for every file, you couldn't even login anymore, because you were not allowed to read the shell binary.

freiheit
  • 14,544
  • 1
  • 47
  • 69
Sven
  • 98,649
  • 14
  • 180
  • 226
10

Why not leave system files readable?

  • Obscurity is not security

    Your system should be just as secure even if people know how it works. If you're relying on details being kept secret to keep your system secure it's just a matter of time before it's broken.

  • How will you work?

    It is generally accepted that you should use the root account as little as possible. If you have to use the root account for the most basic of tasks you'll end up just using it all the time.

  • System functionality

    In many cases the system can't function if certain important conf files can't be read by non root users, as others have illustrated with the /etc/passwd example.

can i do chmod o=- -R / ?

Not if you want to actually be able to login and use the system. Nothing's perfect, but for the most part most distributions have relatively sensible default permissions in most cases. Some of these may need to be changed depending on your circumstances, but it should be discussed on a file by file basis, where the affects of changing the file permissions are known.

theotherreceive
  • 8,365
  • 1
  • 31
  • 44
  • I loved your answer. It would be ideal without the tone. "Obscurity is not security": We weren't aiming at just hiding files, this question with it's answer was going to solve the riddle, as such, it didn't nonetheless. – Devrim Sep 15 '09 at 00:06
6

password file is readable for use by a number of standard utility programs, this is why exists the /etc/shadow file, that is instead not readable by normal users and actually stores encrypted password.

NOTE: Passwords are stored in a non-readable file (/etc/shadow) even if encrypted, in order to avoid brute force attacks by local users.

drAlberT
  • 10,949
  • 7
  • 39
  • 52
1

The ls command and many others use the /etc/password file to convert user IDs to user names. Don't change it.

Chris Nava
  • 1,147
  • 1
  • 7
  • 9