Fix i2d behavior for i2d_SSL_SESSION #1966
Merged
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.
Issues:
Addresses
CryptoAlg-2700
Description of changes:
i2d_SSL_SESSION
wasn't exactly following the correct behavior of the legacyi2d
functions whenpp
is non-NULL, but*pp
is NULL. This caused issues with functions expecting a newly allocated buffer when callingi2d_SSL_SESSION
with the recommended documented behavior. Seei2d_SAMPLE
for more details.aws-lc/include/openssl/asn1.h
Lines 254 to 266 in 48a4057
Call-outs:
N/A
Testing:
New test below usage of
i2d_SSL_SESSION
to verify the behavior.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.