Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > Basic Question about User Permissions

Basic Question about User Permissions
Thread Tools
Mac Enthusiast
Join Date: Feb 2005
Status: Offline
Reply With Quote
Feb 9, 2005, 06:36 PM
 
Hi,

I've been using OS X for a while now (currently 10.3.6) and I feel pretty comfortable with it, but every so often something comes up that freaks me out...

Here is the issue:

If another creates a folder in his home directory I am able to access his folder when I am logged into my account (and vice versa)

This does not apply to the standard user folders such as Documents, Library, Pictures, Movies etc. which

Is this normal?
     
Professional Poster
Join Date: Oct 1999
Location: :ИOITAↃO⅃
Status: Offline
Reply With Quote
Feb 9, 2005, 06:53 PM
 
A created folder inherits the permissions of the "parent" folder. Home directories are readable, so that you can get to someone's Shared folder. So yes, new directories created under the home folder will be world-readable unless you change them.

Of course, one might ask why someone is creating new folders in the top of their homedir. Probably they should be putting things under ~/Documents or ~/Library, no?

Also, you can change the permissions by clicking once on the folder in the Finder, the selecting File:Get Info, and opening the Permissions triangle.
     
Mac Enthusiast
Join Date: Feb 2005
Status: Offline
Reply With Quote
Feb 9, 2005, 10:58 PM
 
Thanks very much for the explanation!
     
Clinically Insane
Join Date: Nov 1999
Status: Offline
Reply With Quote
Feb 10, 2005, 08:54 AM
 
If you don't want someone to be able to access your Home folder, set its permissions to 700 (everything for the owner, nothing for anyone else).

If you do this, however, you should be aware that Personal Web Sharing will no longer work for you, because the Web server won't be able to access your Sites folder either. The machine's own server (in /Library/WebServer) will continue to work just fine, as will Personal Web Sharing for any users who haven't done this.

As an alternate solution, you could lock down only your Documents and Library folders (and any other folders you deem appropriate) and leave your Home and Sites folders unlocked. This will allow the Web server to get at your Sites folder, so Personal Web Sharing will continue to work. The disadvantage to this is that other users will still be able to see what's in your Home folder (though depending on the permissions, they may not be able to actually access any of it). If you only keep sensitive stuff in folders you've locked down, however, this should not be much of a problem.
You are in Soviet Russia. It is dark. Grue is likely to be eaten by YOU!
     
Dedicated MacNNer
Join Date: Jan 2001
Location: Badfort
Status: Offline
Reply With Quote
Feb 11, 2005, 03:16 AM
 
Originally posted by Mithras:
A created folder inherits the permissions of the "parent" folder. Home directories are readable, so that you can get to someone's Shared folder. So yes, new directories created under the home folder will be world-readable unless you change them.
This is incorrect. A created folder has permissions set by the system umask, which by default is 022 in Mac OS X. meaning that a folder is read/write by the owner, and readable by group and everyone. You can change the umask either with tinkertool, or system-wide using the tip here. Be warned that this may affect the operation of some applications.
You see, my friends, pirates are the key. - thalo
     
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status: Offline
Reply With Quote
Feb 11, 2005, 04:35 AM
 
Originally posted by Jellytussle:
This is incorrect. A created folder has permissions set by the system umask, which by default is 022 in Mac OS X. meaning that a folder is read/write by the owner, and readable by group and everyone. You can change the umask either with tinkertool, or system-wide using the tip here. Be warned that this may affect the operation of some applications.
I have never heard of the system umask, but unless there's a miscommunication here, your post incorrect. Sub-folders certainly do inherent the permissions of their parents. Create a new folder within your Documents folder and you'll see that Group and Others have No Access. Even if the OS created every folder to be readable by Group and Others, a parent folder that had access for only Owner would override the sub-folder's permissions.

"The natural progress of things is for liberty to yield and government to gain ground." TJ
     
Dedicated MacNNer
Join Date: Jan 2001
Location: Badfort
Status: Offline
Reply With Quote
Feb 11, 2005, 08:14 AM
 
Originally posted by Big Mac:
I have never heard of the system umask, but unless there's a miscommunication here, your post incorrect. Sub-folders certainly do inherent the permissions of their parents. Create a new folder within your Documents folder and you'll see that Group and Others have No Access. Even if the OS created every folder to be readable by Group and Others, a parent folder that had access for only Owner would override the sub-folder's permissions.
No, no they don't. Just try what you described, either in the Finder, or by using mkdir in a shell - the behaviour is as i described, i just confirmed this on 10.3.8. Are you using some kind of Finder replacement, or do you have a network home directory?
You see, my friends, pirates are the key. - thalo
     
Professional Poster
Join Date: Oct 1999
Location: :ИOITAↃO⅃
Status: Offline
Reply With Quote
Feb 11, 2005, 10:16 AM
 
Originally posted by Jellytussle:
This is incorrect. A created folder has permissions set by the system umask, which by default is 022 in Mac OS X. meaning that a folder is read/write by the owner, and readable by group and everyone. You can change the umask either with tinkertool, or system-wide using the tip here. Be warned that this may affect the operation of some applications.
I stand corrected. I thought the parent-dir rule applied to directories and the umask to files, but I was wrong. I guess set-guid is the only inherited property.
     
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status: Offline
Reply With Quote
Feb 11, 2005, 03:21 PM
 
Originally posted by Jellytussle:
No, no they don't. Just try what you described, either in the Finder, or by using mkdir in a shell - the behaviour is as i described, i just confirmed this on 10.3.8. Are you using some kind of Finder replacement, or do you have a network home directory?
No, no Finder replacement, no strange installations or modifications. Maybe we're confusing each other's statements.

"The natural progress of things is for liberty to yield and government to gain ground." TJ
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 07:10 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2