Robust port-rebinding check #426
Open
Conversation
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
RFC does not require PATH_CHALLENGE frame in a first packet to new path. Instead of requiring it, verify that PATH_CHALLENGE frame is sent to new path before a packet containing non-probing packet is sent. PATH_CHALLENGE can be in a same packet that contains non-probing frame.
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.
RFC does not require PATH_CHALLENGE frame in a first packet to new path. Instead of requiring it, verify that PATH_CHALLENGE frame is sent to new path before a packet containing non-probing packet is sent. PATH_CHALLENGE can be in a same packet that contains non-probing frame.
Fixes #424