I created a new user with: adduser [username]
As I understood, adduser is higher level frontend which uses useradd, so USERGROUPS_ENAB should be processed. >From the debian umask wiki, UMASK in /etc/login.defs should finally work since Trixie, it never worked in Bookworm and earlier versions. https://wiki.debian.org/Debate/umask The same seems to apply to Arch linux. Arch recently (2023) changed umask configuration from /etc/profile to /etc/login.defs. https://archlinux.org/news/changes-to-default-password-hashing-algorithm-and-umask-settings/ Bob > * Bob Rosbag <[email protected]> [250831 22:20]: >>I tried the two variables separately and once combined. In all three >>instances, I created a new user, logged in on tty4, ran "touch test" >>and checked the user/group name and its permissions. All had the same >>group name as the username and the same file permissions (664). > > Can you explain -how- you created the new user? useradd is supposed > to look at USERGROUPS_ENAB, but other tools might not. > >> [..umask..] > > If PAM ignores UMASK in /etc/login.defs, I'll delete it from > /etc/login.defs. I think pam_umask is supposed to read it? > login(1) ignores it. > > I'll wait for Sam to chime in here. > > Chris > > >
