Rationale for backporting is that this can allow CSRs to be generated which are not valid (mismatching subject) which has security implications to the revocation process. There is also no work-around, meaning no way to write a Go program that works with these certificates within a revocation list.
dmitshur
changed the title
crypto/x509: Incorrect TBSCertificateList.Issuer field when using non-pkix.Name-encodable Issueraffected/package [1.19 backport]
crypto/x509: Incorrect TBSCertificateList.Issuer field when using non-pkix.Name-encodable Issuer [1.19 backport]
Aug 3, 2022
Issue to track potentially backporting an eventual CL for #53754
The text was updated successfully, but these errors were encountered: