Re:Chromium based browsers leak user local IP via WebRTC fou...
by kornhole on Tuesday October 25, 2022 @12:00PM
(#33332384)
I also use similar browser isolation strategy. I use one browser for real-ID activity such as banks, domain registrars.. and avoid entering real creds in the private browser to keep an anonymous fingerprint. This is one of those gray areas though where I don't always want to share my IP over Jitsi.
Re:Chromium based browsers leak user local IP via WebRTC fou...
by lxgr on Tuesday October 25, 2022 @04:24PM
(#33335653)
> The former also runs a myriad of other addons which increase privacy.
Unfortunately, the more custom your browser behavior gets, the more finger-print-able you are :/
And that's not even considering potentially harmful plugins (either inherently so, or via browser store account takeovers).
Re:Chromium based browsers leak user local IP via WebRTC fou...
by whatismybrowser on Tuesday October 25, 2022 @06:58PM
(#33337327)
It used to be available to detect, but they changed it a long time ago.
It made it easy to help someone find their local ip address, without having to click around in settings or the command line:
https://www.whatismybrowser.com/detect/what-is-my-local-ip-a...
But I understand the fingerprinting/privacy concerns, so it's for the best that it's not available.
I use two browsers. One with WebRTC disabled (Firefox) and one with WebRTC enabled (Safari/Chromium). The former also runs a myriad of other addons which increase privacy. The latter I use to connect to PiKVM.