Content deleted Content added
Adding short description: "Test for a valid public key certificate" (Shortdesc helper) |
link revocation status |
||
| (One intermediate revision by one other user not shown) | |||
Line 14:
* The public key algorithm and parameters are checked;
* The current date/time is checked against the validity period of the certificate;
* The [[revocation status]] is checked, whether by [[Certificate revocation list|CRL]], [[Online Certificate Status Protocol|OCSP]], or some other mechanism, to ensure the certificate is not revoked;
* The issuer name is checked to ensure that it equals the subject name of the previous certificate in the path;
* Name constraints are checked, to make sure the subject name is within the permitted subtrees list of all previous CA certificates and not within the excluded subtrees list of any previous CA certificate;
* The asserted [[certificate policy]] [[object identifier|OIDs]] are checked against the permissible OIDs as of the previous certificate, including any policy mapping equivalencies asserted by the previous certificate;
* Policy constraints and basic constraints are checked, to ensure that any explicit policy requirements are not violated and that the certificate is a CA certificate, respectively. This step is crucial in preventing some [[man in the middle attack]]s;<ref>[[Moxie Marlinspike]], [https://www.blackhat.com/presentations/bh-dc-09/Marlinspike/BlackHat-DC-09-Marlinspike-Defeating-SSL.pdf New Tricks For Defeating SSL In Practice], [[Black Hat Briefings|Black Hat]] DC Briefings 2009 conference.</ref>
* The path length is checked to ensure that it does not exceed any maximum path length asserted in this or a previous certificate;
* The key usage extension is checked to ensure that is allowed to sign certificates; and
| |||