You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WebRTC-Direct transport at risk due to Chrome changes (ICE credential munging): alignment and next steps #3499
WebRTC-Direct v2 (no ICE ufrag munging) is ready across all three repos.
If it helps, I tested it end to end by hand using below revisions (so when in doubt, know this was the state that worked):
The end-to-end test I did: a JS v2 dialer in Chrome for Testing 150.0.7871.24 run with --force-fieldtrials=WebRTC-NoSdpMangleUfrag/Enabled/ against the Go v2 server. v1 fails (Chrome rejects the munged ufrag), v2 connects and is Noise-authenticated on both sides.
Activity
lidel commentedon Jun 20, 2026
WebRTC-Direct v2 (no ICE ufrag munging) is ready across all three repos.
If it helps, I tested it end to end by hand using below revisions (so when in doubt, know this was the state that worked):
mainat libp2p/js-libp2p@691a5e4c) implements and hardens the v2 path.The end-to-end test I did: a JS v2 dialer in Chrome for Testing 150.0.7871.24 run with
--force-fieldtrials=WebRTC-NoSdpMangleUfrag/Enabled/against the Go v2 server. v1 fails (Chrome rejects the munged ufrag), v2 connects and is Noise-authenticated on both sides.