-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] How to add Root CA with chromium installed by snap #116
Comments
Can you try adding support for that path in the NSS code? We should support both options.
https://github.com/FiloSottile/mkcert/blob/master/truststore_nss.go#L16 |
Yes add snap path should be great. as workaround, you can add manually Root CA with this command
|
@AlexandrePavy would you be able to pull down this Pull Request and try? Branch: https://github.com/adamdecaf/mkcert/tree/more-nss-locations |
👍 nice i will have a look soon, i need to build this for test |
Hello @adamdecaf, I have just tried PR, sorry for the delay ! firstly I delete the existing certificate Then when I reinstall the certificat, I have no added certificate for the chrome snap : it does not seem to work or did something wrong? |
Using Ubuntu 18.10 It works great on Google Chrome and Firefox. |
@shaal can you confirm if the above additional paths would work to install and trust the certificate on your machine? If not, do you know where mkcert should install the certificate into? |
Hello,
Nice project work as a charm 👍,
I have a little question, I use chromium with snapcraft.
When i do
mkcert -install
this add Root CA in default path for chrome (and work fine this default chrome on linux) but not with chromium browser installed by snapDefault path for Root CA is
sql:$HOME/.pki/nssdb
but with snap issql:/home/alexandre/snap/chromium/current/.pki/nssdb
.Do you have an idea for it to work in my case ? Can we change the default path of root CA? What is the certutils command for add the root ca in my chromium?
The text was updated successfully, but these errors were encountered: