-
Notifications
You must be signed in to change notification settings - Fork 60
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
174,940 certificates that fail to parse: Left/Exception #66
Comments
Many certificates in failed-certificates.txt.bz2 are not signed, it just a raw TBSCertificate (https://tools.ietf.org/html/rfc5280, section 4.1), without any signature Algorithm Identifier, nor Signature Value (BitArray of signaure_bits, 2048 when RSA-2048 is used). I.E.: ( ex2 is one of the failing certificate in failed-certificates.txt.bz2. )
As you can see, there's nothing left for parsing. While with X509 signed certificate, there're should be
If you try fromASN1 and parse it as a Certificate only, it should return success. Thanks |
Further to #27 , I have a bunch more certificates that fail to parse on hs-certificate.
The 174,940 certificates and code to reproduce the failures is available at https://gist.github.com/tomfitzhenry/9124641 .
In addition to Left error cases, I've included the few certificates that cause exceptions to be thrown too.
The certificates fail to parse for a variety of reasons. Here they are with the number of failures per group:
The text was updated successfully, but these errors were encountered: