[Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found
Launchpad Bug Tracker
1764848 at bugs.launchpad.net
Wed Apr 25 20:57:55 UTC 2018
This bug was fixed in the package openssl - 1.1.0g-2ubuntu4
---------------
openssl (1.1.0g-2ubuntu4) bionic; urgency=medium
* debian/patches/rehash-pass-on-dupes.patch: Don't return 1 when a duplicate
certificate is found. (LP: #1764848)
-- Brian Murray <brian at ubuntu.com> Wed, 25 Apr 2018 10:03:48 -0700
** Changed in: openssl (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1764848
Title:
Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to
be removed if duplicate certs found
Status in Ubuntu Single Sign On Client:
New
Status in ca-certificates package in Ubuntu:
Confirmed
Status in openssl package in Ubuntu:
Fix Released
Status in ca-certificates source package in Bionic:
Confirmed
Status in openssl source package in Bionic:
Fix Released
Status in ca-certificates package in Debian:
New
Bug description:
The certificate /usr/share/ca-
certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-
certificates is conflicting with /etc/ssl/certs/UbuntuOne-
Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client.
This results in the postinst trigger for ca-certificates to remove the
/etc/ssl/certs/ca-certificates.crt file. This happens because the
postinst trigger runs update-ca-certificates --fresh.
If I run update-ca-certificates without the --fresh flag, the conflict
is a non-issue and the ca-certificates.crt file is restored.
If I understand some of the postinst code correctly, --fresh should
only be run if called directly or if upgrading from a ca-certificates
version older than 2011.
Running bionic with daily -updates channel and ran into this this
morning due to the release of ca-certificates version 20180409.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions
More information about the foundations-bugs
mailing list