From 48e7d200ae203621d90742f31f3032942d5ab499 Mon Sep 17 00:00:00 2001 From: Adam Shannon Date: Thu, 25 Oct 2018 14:15:37 -0700 Subject: [PATCH] docs: clarify mkcert doens't configure servers (#82) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0f62dbb..111757c 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ The certificate is at "./example.com+5.pem" and the key at "./example.com+5-key. 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. +mkcert automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates. mkcert does not automatically configure servers to use the certificates, though, that's up to you. ## Installation