For a strictly confined snap such as chromium, /etc/ssl/certs is provided by the core snap, not by the host system, which explains why your local CA isn't being recognized.
As a workaround, and to understand better the problem, can you manually import the certificate from chrome://settings/certificates? Does this make your CA recognized? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1901586 Title: [snap] CA Certificates from /usr/local/share/ca-certificates are not used Status in chromium-browser package in Ubuntu: New Bug description: We have a company internal CA and placed its root CA certificate in /usr/local/share/ca-certificates and ran update-ca-certificates. This always worked for chromium based browsers. With chromium-browser as snap in Ubuntu 20.04 this seems to not work any more. Chromium reports invalid certificates as it cannot validate the chain any more. PLease make the snap version of Chromium use the certificates from the system (out of /etc/ssl/certs etc). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Oct 26 18:51:29 2020 InstallationDate: Installed on 2020-09-26 (30 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1901586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
