Re: “Localhost tracking” explained. It could cost Meta 32 billion.

Liste des GroupesRevenir à m android 
Sujet : Re: “Localhost tracking” explained. It could cost Meta 32 billion.
De : usenet (at) *nospam* arnowelzel.de (Arno Welzel)
Groupes : comp.mobile.android
Date : 14. Jun 2025, 23:32:59
Autres entêtes
Message-ID : <mb6bkpFklhqU1@mid.individual.net>
References : 1 2
VanguardLH, 2025-06-14 08:03:

[...]
So, we're back to how WebRTC can be abused to identify you.  While the
desktop web browsers let you disable WebRTC through settings, the
deliberately crippled mobile web browsers do not.  Alas, even the
desktop web browsers are taking away the option to disable WebRTC, so
you need an add-on for them, too.
 
You can test by visiting:
 
https://webbrowsertools.com/test-webrtc-leak/

False positive.

It reports "N/A" for my private IP address and still says "Your browser
is leaking webrtc ip-address!". My *public* IP address is not a secret,
when I visit a website.

https://ipleak.net/
(look under "Your IP addresses - WebRTC detection")

Same - just showing my public address which is not a secret anyway.

Be aware that disabling the WebRTC API can break some web sites.

Yes - especially those which offer video calls and live video streaming
using WebRTC. HLS ist not really suitable for video calls.

[...]
Even if using a VPN, WebRTC could still expose your IP addresses, so you
should test and a leak test site while using your VPN.

I did - both testsites above did *not* show my private IP address. And
no, I did not disable WebRTC.


--
Arno Welzel
https://arnowelzel.de

Date Sujet#  Auteur
13 Jun 25 * “Localhost tracking” explained. It could cost Meta 32 billion.42Carlos E.R.
13 Jun 25 +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.3Andy Burns
13 Jun 25 i`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Carlos E.R.
13 Jun 25 i `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
14 Jun 25 `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.38VanguardLH
14 Jun 25  +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.36Carlos E.R.
14 Jun 25  i+* Re: “Localhost tracking” explained. It could cost Meta 32 billion.10VanguardLH
14 Jun 25  ii+* Re: “Localhost tracking” explained. It could cost Meta 32 billion.6Jörg Lorenz
14 Jun 25  iii`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.5Andy Burns
14 Jun 25  iii +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Java Jive
14 Jun 25  iii i`- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Jörg Lorenz
14 Jun 25  iii +- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Jörg Lorenz
14 Jun 25  iii `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Arno Welzel
14 Jun 25  ii`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.3Carlos E.R.
14 Jun 25  ii `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Jörg Lorenz
14 Jun 25  ii  `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
14 Jun 25  i`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.25Jörg Lorenz
14 Jun 25  i `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.24Carlos E.R.
14 Jun 25  i  +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.14Marion
14 Jun 25  i  i`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.13Carlos E.R.
15 Jun 25  i  i +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.10Richmond
15 Jun 25  i  i i+- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Bob Henson
17 Jun 25  i  i i+* Re: “Localhost tracking” explained. It could cost Meta 32 billion.3Carlos E.R.
18 Jun 25  i  i ii`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Richmond
18 Jun 25  i  i ii `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
22 Jun 25  i  i i`* Re: ?Localhost tracking? explained. It could cost Meta 32 billion.5Frank Slootweg
22 Jun 25  i  i i +* Re: ?Localhost tracking? explained. It could cost Meta 32 billion.3Carlos E.R.
22 Jun 25  i  i i i`* Re: ?Localhost tracking? explained. It could cost Meta 32 billion.2Frank Slootweg
22 Jun 25  i  i i i `- Re: ?Localhost tracking? explained. It could cost Meta 32 billion.1Carlos E.R.
22 Jun 25  i  i i `- Re: ?Localhost tracking? explained. It could cost Meta 32 billion.1Richmond
15 Jun 25  i  i `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Marion
17 Jun 25  i  i  `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
14 Jun 25  i  +* Re: “Localhost tracking” explained. It could cost Meta 32 billion.5Richmond
14 Jun 25  i  i+* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Jörg Lorenz
14 Jun 25  i  ii`- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Richmond
15 Jun 25  i  i`* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Marion
15 Jun 25  i  i `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Richmond
14 Jun 25  i  `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.4Jörg Lorenz
14 Jun 25  i   `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.3Carlos E.R.
15 Jun 25  i    `* Re: “Localhost tracking” explained. It could cost Meta 32 billion.2Jörg Lorenz
17 Jun 25  i     `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Carlos E.R.
14 Jun 25  `- Re: “Localhost tracking” explained. It could cost Meta 32 billion.1Arno Welzel

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal