webrtc: fix ufrag prefix for dialing #2832
Merged
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
MarcoPolo
approved these changes
Jun 11, 2024
sukunrt
added a commit
that referenced
this pull request
Jun 12, 2024
sukunrt
added a commit
that referenced
this pull request
Jun 12, 2024
MarcoPolo
added a commit
that referenced
this pull request
Jun 12, 2024
* identify: Don't filter addr if remote is neither public nor private (#2820) Updates the filterAddrs logic to no-op if the address is neither public nor private. This fixes an issue in mocknet that assigns each node an address in the IPv6 discard prefix space. That doesn't interact well with this logic in identify. The issue mocknet hits is that it filters out all received listen addresses and then doesn't remember any address for the peer. * identify: fix bug in observed address handling (#2825) * identify: add test for observed address handling (#2828) This modifies TestObservedAddrManager to verify the fix in #2825 * libp2phttp: workaround for ResponseWriter's CloseNotifier (#2821) * libp2phttp: workaround for CloseNotifier * Add lintignore * circuitv2: improve voucher validation (#2826) * webrtc: fix ufrag prefix for dialing (#2832) * webrtc: add a test for establishing many connections (#2801) Update pion/ice to include the fix for out of order ConnectionState update callbacks * release v0.35.1 --------- Co-authored-by: Marco Munizaga <git@marcopolo.io> Co-authored-by: Ivan Shvedunov <ivan4th@users.noreply.github.com>
MarcoPolo
pushed a commit
that referenced
this pull request
Jun 13, 2024
MarcoPolo
pushed a commit
that referenced
this pull request
Jun 13, 2024
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.
Closes: #2827
Should we reject connections attempts with ufrag that don't have this prefix?
I think it is fine to accept all attempts. The purpose of this prefix is to allow us to extend this in the future. So when we do v2 we can make that check aggressive and consider all ufrags without any prefix to be v1.