-
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
Parse embedded SCTs #10
Comments
I believe, SCT data decoding is out of ASN.1 Editor scope. A different tool that supports SCT data types shall be used to decode SCT data. |
Well, SCT data is ASN1 data included in the certificate.
https://letsencrypt.org/2018/04/04/sct-encoding.html As this is |
so..how it is related to ASN editor? Don't get me wrong, I would like to allow the editor to determine decoded message type and provide more details, but it is a hell of work to make every single X.509 data type recognizable. So I'm positioning the tool as a general-purpose ASN viewer/editor which may or may not be strictly X.509 or whatever else. |
Got it - you were right. The SCTs are not encoded in ASN1 :-( https://tools.ietf.org/html/rfc5246#section-4 |
Never the less, it would be great, if there would be a way to decode like SAN entries or SCTs. Any idea how this could be implemented in a way that doesn't break the design of you tool? |
It would be great, if the tool could parse SCT log entries as described here: https://letsencrypt.org/2018/04/04/sct-encoding.html . Probably doing so has the same problems as solving this issue #5 ?
The text was updated successfully, but these errors were encountered: