e3e4679693efc60bc7a25983909ddfa6883ab2ec
9312d1892c611d9f0e814cb915488182da2b76cc
The X509v3 extension is defined as
Extension ::= SEQUENCE { extnID OBJECT IDENTIFIER, critical BOOLEAN DEFAULT FALSE, extnValue OCTET STRING -- contains the DER encoding of an ASN.1 value -- corresponding to the extension type identified -- by extnID }
Since the critical element has a default value of FALSE, a DER encoder must not encode the value. Only TRUE value must be encoded.
critical
FALSE
TRUE
Fixes: https://pagure.io/certmonger/issue/223 Signed-off-by: Christian Heimes cheimes@redhat.com
1 new commit added
Use extensions template from NSS
Change looks ok. Can the commits be squashed? The first one updates the existing template and the second eliminates it.
rebased onto 9312d1892c611d9f0e814cb915488182da2b76cc
I'm still seeing BOOLEAN: 0 in the generated CSR:
402:d=7 hl=2 l= 3 prim: OBJECT :X509v3 Subject Alternative Name 407:d=7 hl=2 l= 1 prim: BOOLEAN :0 410:d=7 hl=3 l= 161 prim: OCTET STRING [HEX DUMP]:....
Use implicit, empty FALSE for extensions
OK, this drops the critical extension altogether as desired.
asn1crypto.csr still fails to parse the CSR with a very similar failure as reported in the ticket.
Can you update the commit message on the new commit to include the ticket # and I think the 1st comment from this PR would be good to context to include as well.
I tested this on F35 with and without this patch applied. An IPA replica is installable with the patch.
2 new commits added
Metadata Update from @rcritten: - Request assigned
LGTM, thanks.
Pull-Request has been merged by rcritten
The X509v3 extension is defined as
Since the
criticalelement has a default value ofFALSE, a DERencoder must not encode the value. Only
TRUEvalue must be encoded.Fixes: https://pagure.io/certmonger/issue/223
Signed-off-by: Christian Heimes cheimes@redhat.com