search

ungoogled-software / ungoogled-chromium

Google Chromium, sans integration with Google
BSD 3-Clause "New" or "Revised" License
20.69k stars 835 forks source link

Force Chromium to Use Proxy IP Address in WebRTC instead of Public IP #2059

Open nirazv opened 2 years ago

nirazv commented 2 years ago

Description

Force Chromium to Use Proxy IP Address in WebRTC instead of Public IP while using VPN

Who's implementing?

The problem

Browsers leaks Public IP through WebRTC protocols while routing traffics through browser specific proxies such as chrome vpn extensions. but using Native VPN Application (OS Specific) doesn't produce public ip through WebRTC.

How to overcome this problem and force chromium to use proxy IP instead of public IP for WebRTC communication.

Note- Blocking WebRTC from Browser does hide the public ip but many websites eg. google.com, godaddy.com treats you as a bot and blacklist you from using some of their services.

This issue is more related to browser fingerprinting than ungoogling stuffs..

No Extensions available to solve this problem till now but some of the automation tools such as Kameleo.com is able to do such things but those are pricy.

Possible solutions

Force chromium to use proxy ip through ICE Framework TURN/STUN signaling services

Alternatives

No response

Additional context

No response

madhattertea commented 1 year ago

This feature would be pinnacle to anti-tracking. The most sophisticated fingerprinting services can detect if your browser explicitly disabled WebRTC versus the UDP traffic timing out or request failing. So I've resolved to just disable UDP traffic at the network interface level unless a feature like this is available.

PF4Public commented 1 year ago

Should this be fixed by https://github.com/ungoogled-software/ungoogled-chromium/pull/2359?

madhattertea commented 1 year ago

That request is related to setting the default behavior using features and settings already built into the webrtc system. This request is a whole other level, not supported by webrtc, ultra hacky. You'd need to rewrite webrtc ICE connection data on the fly to detect the IP string sent and rewrite it. Other browsers have done this like multi login, but they have a team of devs dedicated to hacks like this.

iamkhalidbashir commented 1 year ago

This is really important feature for us Multi login is pricy