Public bug reported:

Until Ubuntu 16.04 to add a certificate authority (CA) I would put the
files in '/usr/local/share/ca-certificates' and then run the 'sudo
update-ca-certificates'

After that, Chrome and Firefox browsers started to identify sites signed
with the new CA added as secure.

With Ubuntu 18.04 this behavior has changed. After adding the new
certificate authority (CA) to '/usr/local/share/ca-certificates' and
running the sudo command sudo update-ca-certificates the Firefox and
Chrome browsers continue to indicate that the sites are not secure.

I am required to manually import the CAs into each of the browsers.

Is there any new command that has the same behavior as Ubuntu 16.04 in
adding new CAs?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_24_26_generic_42
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 21:48:32 2018
InstallationDate: Installed on 2018-03-30 (142 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
PackageArchitecture: all
SourcePackage: ca-certificates
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug bionic wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1787871

Title:
  update-ca-certificates does not update browsers

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Until Ubuntu 16.04 to add a certificate authority (CA) I would put the
  files in '/usr/local/share/ca-certificates' and then run the 'sudo
  update-ca-certificates'

  After that, Chrome and Firefox browsers started to identify sites
  signed with the new CA added as secure.

  With Ubuntu 18.04 this behavior has changed. After adding the new
  certificate authority (CA) to '/usr/local/share/ca-certificates' and
  running the sudo command sudo update-ca-certificates the Firefox and
  Chrome browsers continue to indicate that the sites are not secure.

  I am required to manually import the CAs into each of the browsers.

  Is there any new command that has the same behavior as Ubuntu 16.04 in
  adding new CAs?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_24_26_generic_42
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 21:48:32 2018
  InstallationDate: Installed on 2018-03-30 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1787871/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to