Comment 0 for bug 1953610

[Impact]
If a non-default umask is set for the root user, then the database created by cnf-update-db is not readable by users.

[Test plan]
The umask changes have little regression potential, are tested in a smoke test, and there is a larger test suite that ensures it does not regress other bits (which again, it really shouldn't)

[Where problems could occur]
We could have the wrong umask? Admins actually liked c-n-f to crash on them?