ca-certificates pops a bad debconf prompt on upgrade to disco
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ca-certificates (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
On upgrade from cosmic to disco, I get a debconf prompt from ca-certificates:
New certificates to activate:
mozilla/
mozilla/
Neither of these two new certificates are selected by default.
Looking at the config script, I see that this question is being asked at critical priority.
It also appears that this is only being asked because ca-certificates
But having decided for 'ask', the UX here is still pretty bad.
- If the package's recommendation (and default behavior) is to enable these new certs on upgrade, then the debconf prompt should also have them preselected. Otherwise, this prompt looks like something the package maintainer is NOT recommending that you do, so then why prompt for it at all.
- Presenting only the certificate filenames is not a great basis for anyone making a decision about whether or not to enable these certs. If I actually wanted to manage which certs are enabled, in order to make an informed decision I would expect to see things like the CN of the cert and possibly some EKU information, not a filename.
Changed in ca-certificates (Ubuntu): | |
importance: | Undecided → Medium |