-
Notifications
You must be signed in to change notification settings - Fork 227
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
Feature idea: support ASN.1 (DER/BER) #20
Comments
Hi, yes that is a good idea. It would also require figuring out a nice way of passing in a grammar file to the decoder. |
Thanks. I will take a look if I have time in January. |
Hey, some update. I have a basic BER decoder working now, also working on adding support for arbitrary large integer to the decoder which will be useful for ASN.1. and make it more useful for certificates and crypto related things i think. Hope i can push something in the next few days. |
Basic support, can also do CER and DER but without any extra validation. No schema support. Redo format doc.md usage a bit, now format/<dir>/<format>.md instead. Related to #20
Hey, now there is basic ASN1 BER support in master and also some kind of To make it a bit easer to work with PEM there is also Any feedback what could be done differently or bugs are much appreciated. Example reading PEM file, decode it and display it as decode tree, JSON and torepr JSON:
|
Hey, it would be pretty cool with fq supported decoding binary¹ ASN.1 (Abstract Syntax Notation One) as it is used in various communication protocols.
¹ ASN.1 has many encoding options but pretty much everything that is binary encoded seems to be either BER or DER.
The main problem I see is that the field names are not included in the actual files, so either the user would have to point to an ASN.1 grammar/spec file or the output would be "nameless".
The text was updated successfully, but these errors were encountered: