mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #186] Mkcert doesn't work properly with firefox nightly? #116
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#116
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 @sereymongkol on GitHub (Aug 10, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/186
I am trying to generate some certificate for testing purpose and i could not make it work on firefox, only chrome is working. I have tried:
But I got some error:
And So i tried it with root permission:
And I got this output.
After that, I tried to execute:
And i got output:
From the first command, i believe there is something wrong already because in the main page from github, it should include:
I am sure my JAVA_HOME is working properly. I have set it by:
And verify it:
I am not sure if i have to set TRUST_STORES in my environment variable too or not and i did not set it yet.
So, in summary, how can I solve this problem? To make firefox-nightly trust this certificate, and mkcert automatically add the certificate into something like trust store (i am not sure if this is the one it should be) so java application trust this certificate. Thank you.
Note: I am using Arch Linux, and Open JDK 12.
@FiloSottile commented on GitHub (Nov 9, 2019):
The first command probably failed due to "sudo" not being in the $PATH. The second one worked but didn't find keytool, which indeed is confusing. Does
$JAVA_HOME/bin/keytoolexist?@FiloSottile commented on GitHub (Oct 25, 2020):
Timing out in "waiting for info".