Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example of covid notification #43

Open
markusb opened this issue Apr 30, 2020 · 2 comments
Open

Example of covid notification #43

markusb opened this issue Apr 30, 2020 · 2 comments

Comments

@markusb
Copy link

markusb commented Apr 30, 2020

Is there a screen shot of the message you get if your app detects a contact with an infected person ?

I'd like to know what exactly gets reported. There is a huge difference between 'there was proximity with an infected person detected' and 'you were in proximity with infected person with id xxxxx, on at '.

I think displaying the id if the person may be problematic for privacy reason (despite it being impossible to trace back). But the timestamp and place is pretty important. There is a huge difference between time and date to correspond to a visit to a friend or a visit to a supermarket.

@KentShikama
Copy link

KentShikama commented May 2, 2020

Just a random person who read the spec, so take this with a grain of salt.

In short, the protocol (both design 1 and design 2) does not support what you're suggesting by design. "Smartphones locally store each observed EphID together with the corresponding proximity, duration, and a coarse time indication (e.g., “April 2”)." The protocol (design 1) intentionally shuffles generated EphIDs so that it makes it difficult to detect the exact X minute interval you came in contact with an infected person. Note as a "tech-savvy person" you can modify the app (even with design 2) to do this but you would be considered an "abuser" by the spec:

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. The attacker can correlate this information with the detailed log to narrow down who in their list of contacts is now infected.

That said your computed risk score should be a lot higher if you spend a few hours with an infected friend versus passing by someone at the grocery store based on number of unique infected EphIDs that have been observed, duration, and signal strength.

@markusb
Copy link
Author

markusb commented May 14, 2020

I know that the mayor selling point of the app is to protect the privacy by design.

I still would like to know what I get told by the app when the app detects that I'm at risk.

After all the mayor motivation for me to run the app (and give up valuable battery life to do so) is to get warned about a COVID-19 risk to me.

Your remarks, while interesting don't really answer my question: What info do I get when the app signals me that I'm at risk / met a infected person.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants