Tidak Ada Deskripsi

Filippo Valsorda bf29b706fc Add a canary file to suggest Go 1.10 is required 6 tahun lalu
HomebrewFormula 6a3cad1731 Homebrew and usage 6 tahun lalu
vendor 75a36a6de4 Add punycode support 6 tahun lalu
AUTHORS c3ffec658a Add LICENSE 6 tahun lalu
CONTRIBUTORS c3ffec658a Add LICENSE 6 tahun lalu
Gopkg.lock 75a36a6de4 Add punycode support 6 tahun lalu
Gopkg.toml 75a36a6de4 Add punycode support 6 tahun lalu
LICENSE c3ffec658a Add LICENSE 6 tahun lalu
Makefile ce28959c70 Ahem... a different project leaked into the Makefile 6 tahun lalu
PATENTS c3ffec658a Add LICENSE 6 tahun lalu
README.md 941dfcf755 docs: add CA definition and remove some redundant text (#27) 6 tahun lalu
cert.go c4f873a371 Add a warning for second-level wildcards 6 tahun lalu
go110min.go bf29b706fc Add a canary file to suggest Go 1.10 is required 6 tahun lalu
main.go e9ef9b3787 Add mkcert -CAROOT 6 tahun lalu
truststore_darwin.go e4c5c312a7 Add Firefox support 6 tahun lalu
truststore_firefox.go 1bc392c3cc Use explicit prefix for dbm NSS databases 6 tahun lalu
truststore_linux.go 073ee25396 On linux don't declare we installed to the system store (#18) 6 tahun lalu

README.md

mkcert

mkcert is a simple tool for making locally-trusted development certificates. It requires no configuration.

$ mkcert -install
Created a new local CA at "/Users/filippo/Library/Application Support/mkcert" 💥
The local CA is now installed in the system trust store! ⚡️
The local CA is now installed in the Firefox trust store (requires restart)! 🦊

$ mkcert example.com '*.example.org' myapp.dev localhost 127.0.0.1 ::1
Using the local CA at "/Users/filippo/Library/Application Support/mkcert" ✨

Created a new certificate valid for the following names 📜
 - "example.com"
 - "*.example.org"
 - "myapp.dev"
 - "localhost"
 - "127.0.0.1"
 - "::1"

The certificate is at "./example.com+5.pem" and the key at "./example.com+5-key.pem" ✅

Chrome screenshot

Using certificates from real certificate authorities (CAs) for development can be dangerous or impossible (for hosts like localhost or 127.0.0.1), but self-signed certificates cause trust errors. Managing your own CA is the best solution, but usually involves arcane commands, specialized knowledge and manual steps.

mkcert automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates.

Installation

On macOS, use Homebrew.

brew install --HEAD https://github.com/FiloSottile/mkcert/raw/master/HomebrewFormula/mkcert.rb
brew install nss # if you use Firefox

On Linux (-install support coming soon!), use the pre-built binaries (again, coming soon), or build from source (requires Go 1.10+).

go get -u github.com/FiloSottile/mkcert
$(go env GOPATH)/bin/mkcert

Windows will be supported next. (PRs welcome!)

Warning: the rootCA-key.pem file that mkcert automatically generates gives complete power to intercept secure requests from your machine. Do not share it.

Advanced topics

Changing the location of the CA files

The CA certificate and its key are stored in an application data folder in the user home. You usually don't have to worry about it, as installation is automated, but the location is printed by mkcert -CAROOT.

If you want to manage separate CAs, you can use the environment variable $CAROOT to set the folder where mkcert will place and look for the local CA files.

Installing the CA on other systems

Installing in the trust store does not require the CA key, so you can export the CA certificate and use mkcert to install it in other machines.

  • Look for the rootCA.pem file in mkcert -CAROOT
  • copy it to a different machine
  • set $CAROOT to its directory
  • run mkcert -install

Remember that mkcert is meant for development purposes, not production, so it should not be used on end users' machines, and that you should not export or share rootCA-key.pem.


This is not an official Google project, just some code that happens to be owned by Google.