You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a new CA in "System -> Trust -> Authorities" using "Create an internal Certificate Authority", the resulting CA certificate has no KeyUsage Extension. It should have one of type "critical" with values "Certificate Sign, CRL Sign" as otherwise third party software might not accept the CA as valid.
To Reproduce
Steps to reproduce the behavior:
Go to "System -> Trust -> Authorities"
Click "Create an internal Certificate Authority" and fill in the form
Hi
could you please give an example when such a cert is not considered valid? I thought that this extension is optional (although it is marked critical if present) and is intended to limit the scope of the key (if there is no need to limit the scope, then the extension may be absent) https://www.rfc-editor.org/rfc/rfc5280.html#section-4.2.1.3
@fichtner@AdSchellevis@goodomens42@barzog
I must apologize if my previous post misled anyone, after taking the time to read the slightly ambiguous text of the rfc5280 again and digging around a bit, I agree with the users that the text of the standard is rightly treated keyUsage Extension as necessary for (root) CA's that used to validate other certs or crls Conforming CAs MUST include this extension in certificates that contain public keys that are used to validate digital signatures on other public key certificates or CRLs. When present, conforming CAs SHOULD mark this extension as critical
a possible fix is mentioned at #5629
although I think it would be more correct with: keyUsage = critical, cRLSign, digitalSignature, keyCertSign
Description
When creating a new CA in "System -> Trust -> Authorities" using "Create an internal Certificate Authority", the resulting CA certificate has no KeyUsage Extension. It should have one of type "critical" with values "Certificate Sign, CRL Sign" as otherwise third party software might not accept the CA as valid.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
See Description
Environment
OPNsense 22.1.10-amd64
FreeBSD 13.0-STABLE
OpenSSL 1.1.1q 5 Jul 2022
The text was updated successfully, but these errors were encountered: