WebRTC & DNS leaks in Firefox.

[clawside]

By default, Firefox has DNS & WebRTC leaks, so, we can clarify them in the firefox section, also, the mullvad page is showing incorrect information, so i suggest to use dnsleaktest.com, also DNSCrypt can be easily configured to correct them.

[fxbrit]

Firefox has DNS & WebRTC leaks

source?

[dngray]

Both Chromium and Firefox don't leak private addresses anymore https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/

[fxbrit]

yup both adopted mDNS, except on android:

• https://searchfox.org/mozilla-central/source/modules/libpref/init/all.js#497
• https://bugzilla.mozilla.org/show_bug.cgi?id=1581947

and on win7 where mDNS is not supported natively.

[dngray]

and on win7 where mDNS is not supported natively.

Well Windows 7 is unsupported unless you have a lot of money.

[TommyTran732]

@dngray kinda another reason I don't feel comfortable recommending Firefox on Android right now tbh

[fxbrit]

@TommyTran732 if you actually read the bugzilla link it says that it isn't a firefox problem, it is an android problem and other browsers have the same exact behavior. there's a chrome ticket linked inside, and it was updated in 2021.

[Thorin-Oakenpants]

Well Windows 7 is unsupported unless you have a lot of money

doesn't negate

• FF will support win7 for another two years: ESR104 will likely be the last win7 FF standing and that will EOL around November 2023
  • they'll follow chrome's support cycle
• currently 20% of users are using win7

Edit: FYI the ticket to watch is 1594270

[TommyTran732]

@TommyTran732 if you actually read the bugzilla link it says that it isn't a firefox problem, it is an android problem and other browsers have the same exact behavior. there's a chrome ticket linked inside, and it was updated in 2021.

Ah, my bad then