Public bug reported:
(initially reported at https://askubuntu.com/questions/1202861/chromium-
does-not-show-certificates-from-pki-nssdb)
Chromium can theoretically use the shared NSS db at ~/.pki/nssdb, but
the snap confinement prevents it from actually using the shared db (it
reads and writes to $SNAP/.pki/nssdb instead).
Shared certificates can be inspected by browsing to
chrome://settings/certificates.
Really accessing the shared db would require an additional read/write
personal-files plug on $HOME/.pki/nssdb, and patching
GetDefaultConfigDirectory() in crypto/nss_util.cc.
** Affects: chromium-browser (Ubuntu)
Importance: Medium
Assignee: Olivier Tilloy (osomon)
Status: Triaged
** Tags: snap
--
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/1859643
Title:
[snap] cannot use shared NSS db
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
(initially reported at https://askubuntu.com/questions/1202861
/chromium-does-not-show-certificates-from-pki-nssdb)
Chromium can theoretically use the shared NSS db at ~/.pki/nssdb, but
the snap confinement prevents it from actually using the shared db (it
reads and writes to $SNAP/.pki/nssdb instead).
Shared certificates can be inspected by browsing to
chrome://settings/certificates.
Really accessing the shared db would require an additional read/write
personal-files plug on $HOME/.pki/nssdb, and patching
GetDefaultConfigDirectory() in crypto/nss_util.cc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1859643/+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
