> I don't see how you could have a real argument against this unless you are a privacy extremist.
The authors of DP-3T (which seems quite similar to this spec) have a huge list of privacy caveats in their whitepaper [1], in section "5.4 Summary of centralised/decentralised design trade-offs".
I haven't seen any analysis on how the Apple/Google spec prevents those problems.
The Apple/Google design drops this DP-3T requirement:
2) Enable epidemiologists to analyse the spread of SARS-CoV-2
So anything in that table with epidemiologists is gone.
The remaining caveats are pretty boring:
To do so, the attacker uses strategically placed Bluetooth receivers
and recording devices to receive EphIDs. The app’s Bluetooth broadcasts of non-infected
people and infected people outside the infectious window remain unlinkable.
...
On the other end, a proactive tech-savvy person can abuse any proximity tracing
mechanism to narrow down the group of individuals they have been in contact with to
infected individuals. To do so they must, 1) they keep a detailed log of who they saw when.
2) they register many accounts in the proximity tracing system, and use each account for
proximity tracing during a short time window. When one of these accounts is notified, the
attacker can link the account identifier back to the time-window in which the contact with an
infected individual occurred.
So, yeah, these vulnerabilities still exist and have been pointed out on this thread... but I find it hard to care about these at all.
> The app’s Bluetooth broadcasts of non-infected people and infected people outside the infectious window remain unlinkable.
The group of non-infected people is getting smaller and smaller. The infectious window is presumably weeks long (times the number of diseases this system will track). These risks don't seem that easy to downplay, even before we get into the "security concerns" section.
The authors of DP-3T (which seems quite similar to this spec) have a huge list of privacy caveats in their whitepaper [1], in section "5.4 Summary of centralised/decentralised design trade-offs".
I haven't seen any analysis on how the Apple/Google spec prevents those problems.
[1] https://github.com/DP-3T/documents/raw/master/DP3T%20White%2...