mkcert
mkcert copied to clipboard
A simple zero-config tool to make locally trusted development certificates with any names you'd like.
Since name-constrained certs don't work everywhere, leaving the signing key lying around still exposes you to risk of having all of your secure traffic intercepted. My first thought was that...
Please, consider using names without version numbers in the files that get published as GitHub Release assets (https://github.com/FiloSottile/mkcert/releases). GitHub has a very nice feature that converts this URL: ``` https://github.com/FiloSottile/mkcert/releases/latest/download/${FILENAME}...
C:\WINDOWS\system32>mkcert -install Using the local CA at "C:\Users\pwn\AppData\Local\mkcert" ✨ ERROR: add cert: Failed adding cert: The access control list (ACL) structure is invalid. I tried to search for google-related unsolvable...
The default mkcert commad's cert info is: Subject: /O=mkcert development certificate/OU=root@myosname Issuer: mkcert root@myosname How can i to chage the root@myosname info to www.myhost.com?
If the user wants to give mkcert the ability to run as root via sudo then they should explicitly do so. Having a process fallback to running via sudo automatically...
mkcert currently sets the name of the Root CA certificate to "mkcert user@host"; at least that's what I see in my Trusted Root Certification Authorities on Windows. Would it be...
Hi, Thanks to mkcert for providing us a great tool for multiple environments. Anyone, could you please give me a hint why I am getting the below error. The background...
When "The dynamic CA configuration feature is in the disabled state" `mkcert -install` put certificate to the appropriate place and call `update-ca-trust extract` (for Linux / CentOS 6 for example)....
``` $ go test ./... ? github.com/FiloSottile/mkcert [no test files] ```
This is not usable as a library dependency for others via `go get`. Can keep the CLI iface the same, just pull the code into a package and expose things...