Closed Bug 1663746 Opened 4 years ago Closed 3 years ago

Don't resolve DNS ICE candidates if IceTransportPolicy is set to RelayOnly

Categories

(Core :: WebRTC: Networking, defect, P2)

defect

Tracking

()

RESOLVED FIXED
94 Branch
Tracking Status
firefox94 --- fixed

People

(Reporter: drno, Assigned: bwc)

Details

Attachments

(2 files)

The Chrome folks fixed an issue on their side where trying to resolve DNS names in ICE host candidates can potentially reveal some location information to an attacker:
https://bugs.chromium.org/p/webrtc/issues/detail?id=11597

There is also a spec bug for that issue https://github.com/w3c/webrtc-pc/issues/2533

We should look into doing the same thing on our end as well.

Byron can you take a look at this please?

Assignee: nobody → docfaraday
Severity: -- → S3
Flags: needinfo?(docfaraday)
Priority: -- → P2
Summary: Don't resolve DNS ICE candidates if IceTransportPolicy is set to RealyOnly → Don't resolve DNS ICE candidates if IceTransportPolicy is set to RelayOnly
Flags: needinfo?(docfaraday)
Attachment #9240682 - Attachment description: WIP: Bug 1663746: (WIP) Test-case for bug. → Bug 1663746: Test-case for bug. r?ng
Pushed by bcampen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1b331e4650de
Test-case for bug. r=ng
https://hg.mozilla.org/integration/autoland/rev/61b0103d25a8
Do not resolve mDNS candidates if the relay ICE policy is being used. r=ng
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 94 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: