Consider blocking even more ports for TURN
Categories
(Core :: WebRTC: Networking, defect, P3)
Tracking
()
People
(Reporter: annevk, Unassigned)
Details
As per https://github.com/w3c/webrtc-pc/issues/2625 (I think 1024 there should be 1023 by the way) Chrome started blocking more ports for TURN connections. We should probably follow them?
As I understand it it concerns any port in the range 0 to 1023, excluding 53, 80, and 443. The exclusions are interesting as I think we might block 53 per a recent change so maybe we have to undo that?
|
||
Comment 1•5 years ago
|
||
It seems like port 53 has been on the block list in netwerk/base/nsIOService.cpp for quite some time (at least as far back as late 2019), unless I'm looking at the wrong places, here[1] and here[2].
[1] https://searchfox.org/mozilla-central/rev/b7b156e53643f0237f3e98a76e5fc7fa9e3b4e71/dom/media/webrtc/transport/nr_socket_prsock.cpp#1642-1644
[2] https://searchfox.org/mozilla-central/rev/b7b156e53643f0237f3e98a76e5fc7fa9e3b4e71/dom/media/webrtc/jsapi/MediaTransportHandler.cpp#365-378
|
||
Updated•1 year ago
|
Description
•