-
Notifications
You must be signed in to change notification settings - Fork 159
Negative test case for constructed, definite-length octet string #1931
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
Negative test case for constructed, definite-length octet string #1931
Conversation
This is incomplete, but here’s an attempt at ensuring that constructed, definite-length method encoded octet strings are detected and rejected. Seeking feedback; I made a few attempts but finally realized what you, @dishmaker, meant by your comment As the I thought it might be fair game to draft a change to the |
94e1198
to
78a3118
Compare
Propagating the original |
78a3118
to
544e397
Compare
544e397
to
0c5789e
Compare
fa5700c
to
0d37f57
Compare
Ensure octet strings with constructed, definite-length method return an error, rather than an incorrect decoding.
0d37f57
to
86da1ac
Compare
Ensure octet strings with constructed, definite-length method return an error, rather than an incorrect decoding.