-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scope of reasons for revocation #104
Comments
The restriction is from X.509 (08/2005), clause 8.5.2.2:
Thus, the |
I have a question. What is the range of pkix in the error message pkix.xxx written in your code? For example At first I thought the scope of pkix refers to rfc, but now you say that the scope of cACompromise comes from itu's x509, which confuses me. |
Your understanding of the finding code classifications is correct. This finding code should be prefixed with "itu" instead of "pkix". I'll mark this as a bug and look into getting this fixed. |
Keeping this open so the finding code can be fixed. |
Why are there only
keyCompromise
,affiliationChanged
,superseded
,cessationOfOperation
, andprivilegeWithdrawn
reasons for revocation? I did not find such a revocation range restriction in RFC 5280.And why can revocation reason
cACompromise
only exist in CA crl? My point is that if a leaf certificate is revoked because the CA is compromised, then its revocation reason should also be cACompromise.The text was updated successfully, but these errors were encountered: