Re:On the Road to WebRTC 1.0, Including VP8
by kmlx on Tuesday March 12, 2019 @06:15PM
(#19373626)
isn’t webrtc by default off on all browsers? aren’t websites asking for permssion before the js is allowed access? and won’t it stay off when you deny the request?
[ Parent
| on HN ]
Re:On the Road to WebRTC 1.0, Including VP8
by SahAssar on Tuesday March 12, 2019 @07:04PM
(#19373977)
Nope, the audio/video capture requires permission, but the rest should work without a permission prompt.
Re:On the Road to WebRTC 1.0, Including VP8
by kmlx on Wednesday March 13, 2019 @11:15AM
(#19379468)
"but the rest should work without a permission prompt"
what "rest" are you referring to?
Re:On the Road to WebRTC 1.0, Including VP8
by sempron64 on Wednesday March 13, 2019 @01:06PM
(#19380845)
Connections can be made to other computers without explicit permission.
Re:On the Road to WebRTC 1.0, Including VP8
by kmlx on Wednesday March 13, 2019 @05:44PM
(#19384193)
ah, i believe you are referring to the webrtc data channel. it leaks local IPs, but the severity depends on several factors, including whether you're running VPN and what you're using the VPN for, or just running behind a regular local network.
if you're running behind a regular local network then I wouldn't consider the local IP leakage as a "privacy hazard". local IPs are compromised already. everywhere. they are easy to guess. they are easy to obtain in native apps. etc.
there are issues when it comes to places where VPN access is crucial/vital. thankfully, very few VPN providers leak your IP nowadays, and with drafts such as what the poster above mentioned (https://datatracker.ietf.org/doc/draft-ietf-rtcweb-mdns-ice-...) this problem will be history soon enough.