Repository navigation
Migrating off devcert/mkcert: what cleanup did the docs miss? #26
BackgroundI still run devcert for local HTTPS and I'm planning to move one project at a time to certkit. Coming from devcert? covers coexistence, fingerprint-based identification, and manual removal per store. What I'm unsure about
QuestionFor those who migrated: how did you verify the old CA was really gone — which fingerprint commands, per store/profile? Would a short "fingerprint audit" recipe (list every store/profile where a development CA exists) be worth adding to the migration doc, or to a |
Replies: 3 comments
|
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
|
|
Thanks — that answers all four. I ran the audit commands from #29 on a throwaway Linux container and |
|
Corrected the answer above — the system-store snippet now pairs each subject with its own fingerprint ( If that resolves things on your side, marking the answer above will surface it for anyone else migrating. |
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 uninstalltouch 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.
uninstallclears 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 ismkcert development CA <serial>…