[Bug 1953610] Re: cnf-update-db creates unreadable database if wrong umask

[Kellen Renshaw]

Bionic is affected if the system is configured with a non-default
repository that provides CNF metadata. The same fix works for Bionic in
this situation as well.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to command-not-found in Ubuntu.
https://bugs.launchpad.net/bugs/1953610

Title:
  cnf-update-db creates unreadable database if wrong umask

Status in command-not-found package in Ubuntu:
  Fix Released
Status in command-not-found source package in Bionic:
  Confirmed
Status in command-not-found source package in Focal:
  Confirmed
Status in command-not-found source package in Impish:
  Confirmed
Status in command-not-found source package in Jammy:
  Fix Released

Bug description:
  [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.

  This fix ensures databases are created with the correct permissions,
  but it does not automatically reset permissions for broken databases.

  [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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1953610/+subscriptions