(tooling-llmao) branch main updated: Update mkcert browser trust instructions

[gs...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

gstein pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tooling-llmao.git


The following commit(s) were added to refs/heads/main by this push:
     new e33f7dd  Update mkcert browser trust instructions
e33f7dd is described below

commit e33f7dd32ec33e9a12d113469d984e7d4c948e3d
Author: Greg Stein <gs...@gmail.com>
AuthorDate: Sun Aug 16 14:52:03 2026 -0500

    Update mkcert browser trust instructions
    
    Clarify instructions for importing mkcert certificates into browser trust store.
---
 certs/README.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/certs/README.md b/certs/README.md
index 5c5cbf4..f34119f 100644
--- a/certs/README.md
+++ b/certs/README.md
@@ -39,9 +39,14 @@ Then open `https://localhost.apache.org:<port>/` (port from `config.yaml`).
 
 ## Browser trust
 
-If the browser still warns, import the **mkcert root CA** (not only the site
-cert) into the browser trust store. On Chrome: Settings → Privacy and security
+If the browser still warns, import the **mkcert** site
+cert into the browser trust store (usually named something like
+`${HOSTNAME}+2.pem`). On Chrome: Settings → Privacy and security
 → Security → Manage certificates [^1] → Local Certificates → Installed by you -> {Import}
 the `.pem` file created by mkcert (plain `.pem`, not `*-key.pem`).
 
-[^1]: or jump straight there with [chrome://certificate-manager/](chrome://certificate-manager/)
+There may be a way to import just the CAROOT, but the site.pem file should have
+the entire trust chain, which Chrome can properly use.
+
+
+[^1]: or jump straight there with `chrome://certificate-manager/`


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@tooling.apache.org
For additional commands, e-mail: commits-help@tooling.apache.org