3 ms·
The Apple/Google protocol does randomize: > The advertiser address type shall be Random Non-resolvable. > The advertiser address, RollingProximityIdentifier,
by tgsovlerkhgsel 7y ago
The Apple/Google protocol does randomize:
> The advertiser address type shall be Random Non-resolvable.
> The advertiser address, RollingProximityIdentifier, and Associated Encrypted Metadata shall be changed synchronously so that they cannot be linked.
(page 5, https://covid19-static.cdn-apple.com/applications/covid19/current/static/contact-tracing/pdf/ExposureNotification-BluetoothSpecificationv1.1.pdf https://covid19-static.cdn-apple.com/applications/covid19/cu...)
I assume you can use your "regular" Bluetooth address for any communication with paired devices (which is then just as trackable as it would be otherwise), while still using this at the same time for the BTLE announcements.
However, I suspect these APIs may not be available to non-OS applications.
- rstuart4133 7y agoYou made me look, and my times have changed. > I assume you can use your "regular" Bluetooth address for any communication with paired devices It turns out even that's not true. It's normal to use a different mac each time you connect to the same paired device: https://www.lairdconnect.com/support/faqs/why-does-ble-mac-address-keep-changing-my-smartphone https://www.lairdconnect.com/support/faqs/why-does-ble-mac-a... I don't know whether it multiple mac's in flight at the same time, but given the the effort they've put into it, it's entirely possible.