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
And if we look into spec we will see exactly these two options:
id-ce-basicConstraints OBJECT IDENTIFIER ::= { id-ce 19 }
BasicConstraints ::= SEQUENCE {
cA BOOLEAN DEFAULT FALSE,
pathLenConstraint INTEGER (0..MAX) OPTIONAL }
and extension identifies two aspects:
Subject type: is the certificate a CA certificate or it is an end entity certificate;
[Optionally] How many CAs are allowed in the chain below current CA certificate. This setting has no meaning for end entity certificates.
And for sure Ca(x) case generate something like:
SubjectType=CA
Path length Constraint = x
But in case of SelfSignedOnly it didn't generate anything.
Empty
Despite spec said: "If Basic Constraints extension is not included in certificate, it is automatically treated as end entity certificate."
Right now the only way to implement it in the API is to do a custom extension and serialize it yourself, but we could have native support by e.g. having a EndEntity variant of the enum.
For Basic Constraints certificate extension currently rcgen support two options:
And if we look into spec we will see exactly these two options:
And for sure
Ca(x)
case generate something like:But in case of SelfSignedOnly it didn't generate anything.
Despite spec said: "If Basic Constraints extension is not included in certificate, it is automatically treated as end entity certificate."
Is it possible to force writing this field?
The text was updated successfully, but these errors were encountered: