Details
-
Suggestion
-
Resolution: Done
-
P2: Important
-
None
-
None
Description
WebRTC can leak user's private IPs when they're using a proxy.
Chromium exposes a webRTCIPHandlingPolicy property to control that behavior via its extension API.
If this is also easily accessible via the content API somehow, it'd be great if it could be exposed via QWebEngineSettings.
Alternatively, a way to disable WebRTC completely at runtime would work too.