-
Notifications
You must be signed in to change notification settings - Fork 1k
Preserve DTLS association on invalid record headers during handshake #10826
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
Open
yosuke-wolfssl
wants to merge
1
commit into
wolfSSL:master
Choose a base branch
from
yosuke-wolfssl:fix/f_6539
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+141
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
Test is build-sensitive to a single-datagram first flight
The corrupt/re-inject model here assumes the peer's flight is a single datagram — enforced by
ExpectIntEQ(... c_msg_count : s_msg_count, 1)and the fixedrec[2048]size. That holds for default builds, but a PQC-default build with a largekey_sharefragments the first flight across multiple datagrams. When that happensc_msg_count/s_msg_count != 1and this case fails (loudly, not unsafely — theExpectIntLE(recSz)guard prevents any overflow) rather than exercising the drop path.Rather than only documenting the assumption, consider pinning a non-PQC group on both CTXs right after
test_memio_setupso the single-datagram invariant holds regardless of build defaults. Something like a file-scopestatic const int secp256r1_group[] = { WOLFSSL_ECC_SECP256R1 };and then:This keeps the clean corrupt/re-inject logic and makes the test deterministic across CI matrices that change DTLS defaults. Non-blocking — the drop-path validation is header-level and doesn't depend on whether the flight was fragmented.