Path: ...!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Andrews <andrews@spam.net>
Newsgroups: comp.mobile.android,alt.internet.wireless
Subject: Re: Was Google Location Accuracy (now is How to Spoof Wi-Fi Location)
Date: Wed, 30 Oct 2024 14:43:24 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <vftgmb$1ldn$1@nnrp.usenet.blueworldhosting.com>
References: <vfhvpo$18uv$1@nnrp.usenet.blueworldhosting.com> <1gynl5ogj1mk6.dlg@v.nguard.lh> <vfjmu0$2kk1$1@nnrp.usenet.blueworldhosting.com> <upbfoijutktx.dlg@v.nguard.lh> <lo6f8sF7ecuU1@mid.individual.net> <vflees$1qt$1@nnrp.usenet.blueworldhosting.com> <pqushj5bcbb63hco2vmkfkbvull8961ksf@4ax.com> <vfmf57$s71$1@nnrp.usenet.blueworldhosting.com> <lo92jiFjd13U1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 30 Oct 2024 14:43:24 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="54711"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2
Cancel-Lock: sha1:Y+F4fp5x1newvopKBWaG8b6Hi4c= sha256:13j8Eim+bk+USNtxthlLVyRJXCtS14YvofDPm6XtUjw=
	sha1:jdEaMH5fSaKDVxDHCkTFkSo9zZA= sha256:ObJbgi5qoelSKlkotmx1TcLcXDFpoJ9CKrvABzc4ESM=
Bytes: 3425
Lines: 42

Andy Burns wrote on Mon, 28 Oct 2024 09:08:01 +0000 :

>> I just have to figure out HOW to tell what the heck they're spoofing.
> 
> I doubt anything goes over the wire to be wiresharked, it's a local API 
> on the phone.
> 
> There's sample code on github/stack overflow etc, or just use an 
> existing mock app?

I realize I told Jeff Liebermann a slight mistruth when I said in the post
that Andy is responding to...

  "I just have to figure out HOW to tell what the heck they're spoofing.
   Maybe WireShark, Netstumbler, WiGle, etc., might tell me. Dunno.

   You're the Wi-Fi expert who taught me everything I know, way back in the
   day when I was trying to spoof my MAC address (now the AP MAC addresses 
   are spoofed by default on iOS and Android).

   You told me, long ago, that you can't spoof the ROUTER's WAN-facing MAC
   address though - which - unfortunately - is the one we'd want to spoof!"

Since this thread wasn't about randomizing a MAC address, I didn't notice
that what I said above is slightly wrong in "what" MAC address is
randomized.

To be clear on the current state of Android MAC address randomization:

1. The home router's outward-facing (WAN) MAC address is NOT randomized
   (unless the router software allows that - which I don't know about).

2. What's randomized by default now is the mobile device MAC address
   that connects to the router's LAN-facing access point. This default
   mobile device (iOS & Android) randomization is per access point.

3. For Android only in Developer options" is another privacy setting 
   to randomize #2 per connection (so it changes every time you connect).

When Jeff Liebermann and I last spoke about MAC randomization (oh, maybe
ten or fifteen years ago or so), this default randomization didn't exist.

Now both iOS & Android do MAC randomization (per AP) by default.