mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 21:45:59 +03:00
[GH-ISSUE #116] [Question] How to add Root CA with chromium installed by snap #64
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AlexandrePavy on GitHub (Jan 10, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/116
Hello,
Nice project work as a charm 👍,
I have a little question, I use chromium with snapcraft.
When i do
mkcert -installthis 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/nssdbbut 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?
@adamdecaf commented on GitHub (Jan 10, 2019):
Can you try adding support for that path in the NSS code? We should support both options.
$HOME/.pki/nssdb$HOME/snap/chromium/current/.pki/nssdbhttps://github.com/FiloSottile/mkcert/blob/master/truststore_nss.go#L16
@AlexandrePavy commented on GitHub (Jan 10, 2019):
Yes add snap path should be great.
as workaround, you can add manually Root CA with this command
certutil -d sql:/home/<HomeName>/snap/chromium/current/.pki/nssdb -A -t "C,," -n 'mkcert dev' -i /home/<HomeName>/.local/share/mkcert/rootCA.pem@adamdecaf commented on GitHub (Jan 17, 2019):
@AlexandrePavy would you be able to pull down this Pull Request and try?
Branch: https://github.com/adamdecaf/mkcert/tree/more-nss-locations
@AlexandrePavy commented on GitHub (Jan 17, 2019):
👍 nice i will have a look soon,
i need to build this for test
@AlexandrePavy commented on GitHub (Feb 10, 2019):
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?
@shaal commented on GitHub (May 16, 2019):
Using Ubuntu 18.10
On a DDEV 1.8.0 project, I installed
mkcert -install.It works great on Google Chrome and Firefox.
But does NOT work on Chromium and on Firefox Nightly.
@adamdecaf commented on GitHub (May 22, 2019):
@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?