- From: Roman Shpount via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 May 2020 22:19:12 +0000
- To: public-webrtc-logs@w3.org
How is this different then just issuing an HTTP request to a DNS name which resolves to different IP based on the DNS server used? This is not a new problem. Whatever is used to obfuscate browser location when doing DNS resolution for HTTP requests should also be used for FQDN candidates. I agree that it does make sense to ignore ".local" candidates when in relay mode. Another way this specific issue occurs is when DNS name for the relay server is resolved. This can also be location specific. Once again, general DNS resolution obfuscation procedures should apply here. -- GitHub Notification of comment by rshpount Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2533#issuecomment-634310758 using your GitHub account
Received on Tuesday, 26 May 2020 22:19:14 UTC