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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ssl->buffers.certificate->buffer
is only dereferenced ifcertSz > 0
. I can imagine there's code somewhere relying on nullbuffer
being tolerated whenssl->buffers.certificate->length
is zero, so this nullness check should only be done whenssl->buffers.certificate->length > 0
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree its a bit redundant, but is consistent with the rest of the code. Search for
!ssl->buffers.certificate
and you will see every single check in internal.c, ssl.c and tls13.c useif (!ssl->buffers.certificate || !ssl->buffers.certificate->buffer)
If we want to address that redundancy check separately I am on board, but I think at least for this PR its best to have the checks be consistent.