Can someone justify why the "umask(007);" line was removed from
sample.cf in 1.94? It was there to set the default umask for all Mj
processes. The $config_umask variable I introduced is only to specify
a (possibly) distinct umask for list configuration files (it should
probably be used for everything but list files, or at least for .passwd
files too) to protect them from unnecessarily broad access.
Without the default umask getting set, it appears that the umask
defaults to 000 on at least one system, resulting all files created by
Mj getting marked by the Beast (666 permissions).
--
Dave Wolfe
Follow-Ups:
|
|
