To add HTTPS capabilities to the autopilot test suite, we need a way to inject custom root certificates into oxide. Oxide has a test helper called oxideSetNSSDbPath(…) but it’s not a public API, so it can’t be used by webbrowser-app. There is also a patch in oxide that removes the ability to load a shared NSS database from $HOME/.pki/nssdb/, so we can’t point $HOME to a temporary directory and add custom certificates there.
To add HTTPS capabilities to the autopilot test suite, we need a way to inject custom root certificates into oxide. Oxide has a test helper called oxideSetNSSDbPa th(…) but it’s not a public API, so it can’t be used by webbrowser-app. There is also a patch in oxide that removes the ability to load a shared NSS database from $HOME/.pki/nssdb/, so we can’t point $HOME to a temporary directory and add custom certificates there.
According to https:/ /bugs.launchpad .net/oxide/ +bug/1260048/ comments/ 10, chromium is going to move away from NSS at some point in the future anyway.
This bug is now blocked on oxide using a custom, application- specific place to store custom certificates.