News for hackers. Stuff that matters.
Re:How Apple And Google Are Going To Enable Contact Tracing by Aeolun on Monday April 13, 2020 @08:06AM (#22855079)
Installing bluetooth receivers throughout a city is only feasible if you plan to use it for way more than just coronapatient tracking.
Re:How Apple And Google Are Going To Enable Contact Tracing by taborj on Monday April 13, 2020 @09:21AM (#22855574)
I think that was the point. This is useful for coronavirus patient tacking, yes, but it's also useful for people tracking in general, and malcontent (whomever defines that) tracking in particular.
Re:How Apple And Google Are Going To Enable Contact Tracing by DagAgren on Monday April 13, 2020 @09:34AM (#22855680)
But it's not. There are far better ways to do that, if that is the path you're going down. This is specifically designed to make that kind of thing much harder.
Re:How Apple And Google Are Going To Enable Contact Tracing by mikece on Monday April 13, 2020 @08:09AM (#22855092)
It will compliment CCTV quite nicely... and since the former can do biometric identification then cross referencing that ID# 04d07402e5a502fb7ae0a7847853f1ac5d2a280729901a29738fb3b017135934 is really Bob Smith who lives at 1234 Main Street will be easy enough.
Re:How Apple And Google Are Going To Enable Contact Tracing by rfoo on Monday April 13, 2020 @08:25AM (#22855209)
I recommend actually reading the specification before imagine how to abuse it. There is no fixed, per-user ID being broadcast.

Or if you don't want to, a tl;dr is:

1. Your phone broadcasts a message via BLE every X milliseconds with a "random" ID. The ID is only predictable with a secret key which never leaves user device before "voluntarily revealing" (I agree this can be shaddy). The "random" ID is rotated every Y minutes.

2. The secret key will be rotated daily. The user device only reveals last 14 keys if user voluntarily do so.

3. Note that every BLE advertisement already contains a hardware address and your phone does this regularly. Guess how they mitigate this privacy issue? Rotating the hardware address every Y minutes. So no additional entropy being leaked here, unless you have the user's secret key.