Confirmed users, Administrators
5,526
edits
CA/Revocation Reasons: Difference between revisions
Jump to navigation
Jump to search
continued drafting text
(continued drafting text) |
(continued drafting text) |
||
| Line 87: | Line 87: | ||
* Request revocation using [https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment ACME] and the certificate's private key | * Request revocation using [https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment ACME] and the certificate's private key | ||
** Different [https://letsencrypt.org/docs/client-options/ ACME implementations] have different means to accomplish this. For example: | ** Different [https://letsencrypt.org/docs/client-options/ ACME implementations] have different means to accomplish this. For example: | ||
** certbot revoke --cert-path /PATH/TO/ | ** certbot revoke --cert-path /PATH/TO/certificate.pem --key-path /PATH/TO/privateKey.pem --reason keyCompromise | ||
* Use one of these scripts/tools: | * Use one of these scripts/tools: | ||
** [https://blog.hboeck.de/archives/888-How-I-tricked-Symantec-with-a-Fake-Private-Key.html Hanno Böck's script]: https://github.com/hannob/tlshelpers/blob/master/matchcertkey | ** [https://blog.hboeck.de/archives/888-How-I-tricked-Symantec-with-a-Fake-Private-Key.html Hanno Böck's script]: https://github.com/hannob/tlshelpers/blob/master/matchcertkey | ||