.profile: Remove comment about setting mask.
It's generally a bad idea, leave it a profile_hook.master
parent
1274046f6c
commit
7460469f42
19
.profile
19
.profile
|
@ -3,25 +3,6 @@
|
|||
## .bash_profile does not exist. If this file is not automatically sourced,
|
||||
## do it from the shell config to me sure it applies to TTY as well.
|
||||
|
||||
## Mask
|
||||
## Result for 027 is "rwxr-x---". 022 is the popular default.
|
||||
##
|
||||
## As a result applications make the bad assumption that "others" have access.
|
||||
## Another drawback of 027 is that is behaves badly with default sudo config: for
|
||||
## instance "sudo mkdir foo" will effectively create a "foo" folder whose owner
|
||||
## is root and with permission 027, even if root's umask is 022. This is
|
||||
## usually very bad.
|
||||
## See https://wiki.archlinux.org/index.php/Sudo#Permissive_umask.
|
||||
##
|
||||
## It is possible to override sudo's umask by adding the following to the
|
||||
## sudoers file:
|
||||
##
|
||||
## Defaults umask = 0022
|
||||
## Defaults umask_override
|
||||
# umask 027
|
||||
|
||||
|
||||
|
||||
## Preliminary path definitions. For security reasons (and bad programming
|
||||
## assumptions) you should always append entries to PATH, not prepend them.
|
||||
appendpath () {
|
||||
|
|
Loading…
Reference in New Issue