![]() ![]() ![]() Unix was used a lot in academic environments such as universities where security was a lesser concern, at least lesser than seamless collaboration. In this scenario your point was an issue - sometimes. Back in the old days Unix machines were truly multi-user systems with several hundred users logged in concurrently via serial terminals (such as a DEC VT-220). How the permissions should be set depend on the overall security policy and the use case. That seems a little off as a default setting. I would have thought by default all files were private unless specifically shared but with two Ubuntu boxes (admittedly server boxes) everyone can read all newly created files. I can manually make the folder 711, set ~/.ssh/authorized_keys to 644 but remembering to do that every time for every config is prone to (my) mistakes. Is there some way to set up the folders / directories so SSH can access authorized_keys, postfix / mail can access files it requires, the system can access config files but without all and sundry walking the system? This is required if you have authorized_keys for SSH - without it the SSH gives errors when trying to access the system using a public key. However that lets other users wander into your home folder and look at stuff.Ĭhanging the permissions to 711 (rwx-x-x) means they can traverse folders but not see anything. This question Unix & Linux: permissions 755 on /home/ covers part of my question but:ĭefault permissions on a home directory are 755 in many instances. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |