Does this randomize the Bluetooth address too? I saw the README (from the dissection) mention a function that hides the name "so the other side only gets the address", which would defeat the entire purpose of rotating identifiers. If it does randomize the Bluetooth address, does it use a separate identifier, and if so, does it rotate both at the same time? Otherwise, you can use an identifier that changes at time 1 t…
It's OpenTrace [0]. OpenTrace is GPLv3, and is based on a published specification that's not too difficult understand. The fact that it is dervived from OpenTrace and they haven't published the source is the whole basis of this story. To answer your direct questions: - randomize Bluetooth addresses: I expect not, as that would screw any existing bluetooth connections, like headsets. - does it use a separate randomise…
> 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/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.