lp://staging/ubuntu/natty-updates/ca-certificates

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

14. By Micah Gersten on 2011-09-01

* SECURITY UPDATE: Blacklist "DigiNotar Root CA" due to fraudulent
  certificate issuance (LP: #837557)
  - update mozilla/blacklist.txt

13. By Maximiliano Curia on 2010-08-13

* Non-maintainer upload.
* Fixes buggy shell functions included in the postinst script.
  (Closes: #591607)

12. By Maximiliano Curia on 2010-07-30

* Non-maintainer upload.
* Preserve user changes to the /etc/ca-certificates.conf.
  (Closes: #514220)

11. By Philipp Kern on 2009-08-14

Call Debconf and its db_purge as early as possible in postrm.
(Closes: #541275)

10. By Philipp Kern on 2009-07-09

Fix purge by checking for `/etc/ssl/certs' first. (Closes: #536331)

9. By Philipp Kern on 2008-11-27

Remove /etc/ssl{,/certs} in postrm to please piuparts. (Closes:
#454334)

8. By Philipp Kern on 2008-08-09

* New cacert.org.pem joining both CACert Class 1 and Class 3 certificates.
  This file can be used for proper certificate chaining if CACert
  server certificates are used. The old class3.pem and root.pem
  certificates are deprecated. This new file could safely serve as
  a replacement for both. (Closes: #494343)
* This also reintroduces the old name for the CACert certificate,
  thus closing a long-standing bug about its rename to root.crt.
  (Closes: #413766)

7. By Matthias Klose on 2008-06-03

* Merge with Debian; remaining changes:
  - debian/templates: Do not mark the choices as translatable.

6. By James Westby on 2008-04-08

Prevent the debconf question being forced twice for users we
suspect to be affected. Also clean up the debconf value we
use to do this in the postinst as it will not be needed post-hardy.

5. By James Westby on 2008-04-01

* Improve on the last fix by trying to fix up the problem for
  those that were affected. (LP: #153625)
  - If upgrading from a broken version and the file is empty,
    then
    - if the question was never seen then act like a default
      install
    - if the question was seen and we are in pt_BR locale then
      ask the question again defaulting to selected for all
      certificates.
    - else do nothing.
  - This covers the common cases well, but may require people
    who changed their locales to either answer a question they
    already answered, or to run dpkg-reconfigure manually.
  - All of this code should be dropped after hardy, as all upgrades
    must go through hardy, and everyone will have a fixed version
    then.