OS X wide open permissions

home | blog | Teh Internet | guest blog |rants | placeholder | political | projects | Gwen and Liam | Citadel patched | Tools | Scouts


- Careful Chrome users, this search box might be "Not secure"



Here is how to set a umask for apps on OS X:
http://support.apple.com/kb/HT2202
Here it is again (jucy bits) in case the link above goes away:
Umask for user applications

In Mac OS X v10.5.3 and later, you can create the file /etc/launchd-user.conf with the
contents "umask nnn". Do not include the quotation marks and replace nnn with the
desired umask value, such as 027 or 002.

This will set the user's umask for all applications they launch, such as Finder, TextEdit,
or Final Cut Pro, and control the permissions set on new files created by any of these applications.

Umask for system processes

In Mac OS X v10.4 and later, create the file /etc/launchd.conf with the contents "umask nnn". Do not
include the quotation marks and replace nnn with the desired umask value, such as 027 or 002.

This will set the umask for all processes. Changing this value is strongly discouraged because it
changes the permissions on files used by the system software. If the permissions are too restrictive,
dependent software may not work. If the permissions are too open, they may introduce security issues.


Don't forget about ACL lists. Check them with
ls -le (to list them)
chmod -N (to remove) - (or -E to edit)




[æ]