Confirmed this is the case which this should be classified as a security hole as the behavior does not read dconf db anymore for the users.
Security for dconf needs to be set but is unable to be read when dconf update issued with UMASK. DISA STIG USG fix applies UMASK in this manner which is how I found this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072586 Title: Running "dconf update" with different umask affects the permissions of dconf databases in /etc/dconf/db/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/2072586/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
