Skip to content
Discussion options

You must be logged in to vote

Thanks for writing this up — the migration doc says to identify the old CA by fingerprint but never shows how, which is exactly the gap you hit.

Does certkit uninstall touch anything that isn't certkit's CA?

No. certkit matches its CA by SHA-256 fingerprint rather than display name, and removes only entries whose fingerprint matches. uninstall clears certkit's CA from detected and previously recorded targets and then deletes certkit-owned files, preserving unrelated files and foreign CAs. A leftover mkcert or devcert root is left alone.

Telling certkit's CA apart from a leftover mkcert root

certkit's NSS nickname is certkit development CA <12 hex>; mkcert's is mkcert development CA <serial>…

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by spencermbawe
Comment options

spencermbawe
Oct 2, 2026
Collaborator Author

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
type:docs Documentation
2 participants