Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#14350 - login.defs has wrong UMASK
Attached to Project:
Arch Linux
Opened by héctor (hacosta) - Friday, 17 April 2009, 15:09 GMT
Last edited by Allan McRae (Allan) - Sunday, 19 April 2009, 04:25 GMT
Opened by héctor (hacosta) - Friday, 17 April 2009, 15:09 GMT
Last edited by Allan McRae (Allan) - Sunday, 19 April 2009, 04:25 GMT
|
DetailsDescription:
login.defs UMASK value for the shadow package in core is: 077 (same as the one in testing) thing is, with the package in testing the disired value is 0077 Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Comment by Allan McRae (Allan) -
Saturday, 18 April 2009, 00:55 GMT
The default upstream /etc/login.def that is distributed with shadow uses the three digit format. What is actually wrong with it?
Comment by Allan McRae (Allan) -
Sunday, 19 April 2009, 04:25 GMT
pam overrides this anyway so this really does not actually do anything