Repository navigation
reject an EOF without close_notify in the Mbed TLS and wolfSSL read - #2649
Merged
yhirose merged 2 commits intoOct 27, 2026
Merged
Conversation
Owner
|
Thanks! |
This file contains hidden or 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
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.
TLS EOF without close_notify read as a clean end on Mbed TLS and wolfSSL
The Mbed TLS transport callback turned a bare TCP EOF into a close_notify and the wolfSSL read returned 0 for one without asking wolfSSL_get_error, so a response delimited by the connection close could be cut short on the path and still come back complete, where the OpenSSL backend reports a read error. Both reads now end cleanly only on a close_notify, and the new test fails on the unpatched Mbed TLS and wolfSSL builds and passes on all three backends.