[mbedTLS] Keep reading/writing partial until "would block" #98995
+35
−27
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
Them mbedTLS read and write functions will never read or write more than the negotiated fragment length at every iteration (which usually depends on MBEDTLS_SSL_IN_CONTENT_LEN and MBEDTLS_SSL_OUT_CONTENT_LEN). For this reason, when reading or writing partial data, we must always keep retrying until we receive a "would block" (no bytes read or wrote), or we have fulfilled the read or write.
akien-mga
approved these changes
Nov 12, 2024
|
Thanks! |
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.
Them mbedTLS read and write functions will never read or write more than the negotiated fragment length at every iteration (which usually depends on MBEDTLS_SSL_IN_CONTENT_LEN and MBEDTLS_SSL_OUT_CONTENT_LEN).
For this reason, when reading or writing partial data, we must always keep retrying until we receive a "would block" (no bytes read or wrote), or we have fulfilled the read or write.
Fixes #98176