fix: don't throw exception on invalid BitString and Utf8String #70
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now the error is added as a note to invalid BitStrings and Utf8Strings, so we can see where and what caused the malformed ASN.1 DER
|
Hi! I'm very sorry, I didn't properly read your PR until today. 😢 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So there is an ISO/RFC example with 2 invalid ASN.1 values: BIT STRING and UTF8String
All the other tags are valid.
With
throw new Error(...)the ASN.1 JS Decoder wouldn't show anything.And yes, they really put an invalid example in kinda-new ISO/IEC from 2016.
Thanks for the awesome project.
Here's how it looks like parsed now: