update-ca-certificates error. ca-certificates.crt empty (with pt_BR locale)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Server |
Fix Released
|
Medium
|
Unassigned | ||
ca-certificates (Debian) |
Fix Released
|
Unknown
|
|||
ca-certificates (Ubuntu) |
Fix Released
|
High
|
James Westby | ||
Dapper |
Fix Released
|
High
|
James Westby | ||
Edgy |
Won't Fix
|
High
|
Unassigned | ||
Feisty |
Fix Released
|
High
|
Unassigned | ||
Gutsy |
Fix Released
|
High
|
Unassigned |
Bug Description
Installing ca-certificates would leave Brazilian users with an empty certificates
file due to an error in the tranlations for that locale.
This can be reproduced by installing the current version of ca-certificates
in dapper, edgy, feisty or gutsy in a pt_BR locale, i.e.
$ sudo locale-gen pt_BR.UTF-8
$ export LC_ALL=pt_BR.UTF-8
$ sudo aptitude install ca-certificates
you will find that the /etc/ssl/
zero size.
If you do nothing more than install a fixed version of the package then you
should find that the file is no longer empty, and you were given no debconf
prompts.
The following things should also be true:
* Running "dpkg-reconfigure ca-certifcates" before installing a fixed version
will mean that you are shown a debconf prompt with all of the certificates
pre-selected, and your choices will be reflected in the generated ca-certificates.crt
file. (e.g. deselecting all the certificates will leave you with an empty file again).
* Changing out of the pt_BR locale before upgrading will leave you with
an empty file and no questions will be asked.
Also, exactly the same behaviour should be observed after installing a fixed version,
when upgrading to a new release.
-- Original report:
fernando@
[sudo] password for fernando:
Updating certificates in /etc/ssl/
unable to load certificate
11081:error:
WARNING: ca-certificates.crt does not contain a certificate or CRL: skipping
ssl-cert-
done.
fernando@
/etc/ssl/
Changed in ca-certificates: | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
Changed in ca-certificates: | |
status: | Unknown → New |
description: | updated |
Changed in ca-certificates: | |
status: | Fix Released → In Progress |
Changed in ca-certificates: | |
status: | Fix Committed → In Progress |
status: | Fix Committed → In Progress |
status: | Fix Committed → In Progress |
status: | Fix Committed → In Progress |
Changed in ca-certificates: | |
status: | New → Fix Released |
In /etc/ca- certificates. conf is normal all certificates disabled (!) ?