ubuntu-webapps-bugs team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

Public bug reported:

According to Jamie in
https://bugs.launchpad.net/oxide/+bug/1260048/comments/10:

  « Furthermore, upstream will be moving away from nss at some point
anyway. For the time being we can initialize nss without user db. »

Currently oxide patches chromium to disable loading a shared user nss
database from $HOME/.pki/nssdb.

Whether it is using NSS or another mechanism, we are going to need a way
to manage custom certificates in oxide, for webbrowser-app to offer a UI
to do that.

As a temporary solution until we add a proper API for certificates
management, it would be useful to allow oxide to load custom
certificates from an application-specific place (this would at least
help fixing bug #1505995).

** Affects: oxide
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1522513

Title:
  Load custom certificates from an application-specific directory

Status in Oxide:
  New

Bug description:
  According to Jamie in
  https://bugs.launchpad.net/oxide/+bug/1260048/comments/10:

    « Furthermore, upstream will be moving away from nss at some point
  anyway. For the time being we can initialize nss without user db. »

  Currently oxide patches chromium to disable loading a shared user nss
  database from $HOME/.pki/nssdb.

  Whether it is using NSS or another mechanism, we are going to need a
  way to manage custom certificates in oxide, for webbrowser-app to
  offer a UI to do that.

  As a temporary solution until we add a proper API for certificates
  management, it would be useful to allow oxide to load custom
  certificates from an application-specific place (this would at least
  help fixing bug #1505995).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1522513/+subscriptions