fix(s2n-quic-dc): handle possible secret control packet correctly #2280
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
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.
Description of changes:
Currently, we only invoke
on_possible_secret_control_packetif the datagram payload was not decoded as a valid packet. Sincedcpackets are formatted as valid short header packets, this meant theon_possible_secret_control_packetfunction was never called. This change moves the call to ``on_possible_secret_control_packet` after it is determined the packet does not belong to any known connection.Testing:
I added new integration tests to confirm
on_possible_secret_control_packetis called. I also verified the new tests fail with the existing code.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.