Bug #3591
closed
A fix is coming but ideally you'd create a whole new CA and Cert structure if you believe yours has been compromised. Re-using the CA + Revoking certs should only be done if the CA's key had no chance of being compromised.
New CA + New certs is also faster than Revoking eleventy hundred certs plus regenerating them all. If you have to reissue all new clients anyway, there's little benefit to taking the revocation path.
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:d22169cfd68a26c04ca6d1aa997575f1b3e4cc80.
Applied in changeset commit:80f48850307dea4ceb08dc1a785dd24322b5283d.
OK, fix works, thanks. It is indeed correct that starting with a completely new CA is best solution in this case, but I'd still like to keep track of the revoked certificates.
- Status changed from Feedback to Resolved
- Target version set to 2.1.2
Also available in: Atom
PDF