mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #11] Installing certs for Firefox/Chromium on Linux #8
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#8
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 @fd0 on GitHub (Jun 28, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/11
Hi, while I don't have a use case for
mkcert, I've just recently written a shell script which inserts a CA into all browser profiles for a user, and I thought I just leave some hints here:~/.mozilla/firefox, usingcertutil. The code intruststore_firefox.golooks good already~/.pki/nssdbinto which the certificate can be added viacertutil, very similar to FirefoxThat should do the trick for Linux for the most widely used browsers at least (which should cover like 90% of the use cases out there).
Adding the certificate to the system's trust store depends on the Linux distribution, it's a lot more complex. For Fedora, the browsers also trust certificates in the system-wide trust store in
/etc, on Debian that's not the case: browsers just ignore all system ca certificates.@FiloSottile commented on GitHub (Jul 4, 2018):
Thanks @fd0!