[clug] Apple-Google Contact Tracing API. V1 released May 20, 2020

Hugh Fisher hugo.fisher at gmail.com
Mon May 25 03:16:46 UTC 2020

On Mon, May 25, 2020 at 8:16 AM steve jenkin via linux
<linux at lists.samba.org> wrote:
> The Apple-Google notification service is designed to be anonymous & tracking-resistant, without a central database of user details or central processing of contacts.
> There is a central database of rapidly (15-30 min) keys generated on devices.
> Unclear to me who runs the DB? On what hardware?
> Google’s tech spec page contains sample code for an “Exposure Notifications server” - presumably the local public health authority runs one of these, known to its App.

Intent is that each country runs its own DB, on whatever hardware it wants.
And Apple/Google aren't building the app(s) either.

> App users who are diagnosed Covid-19 positive, notify the App, which uploads the last 14 days of keys ’seen’ by the device. The devices with those keys are sent notifications.
> It’s unclear to me how the keys-device connection is made within the server database.
> The Notification side of the server must push a notification to devices (presumably when they connect to upload keys).
> Currently, App developers - presumably public health authorities - have to build local Apps for users to download & ‘accept’. This allows local ’tuning’ of what constitutes a ‘contact’.
> In coming months, this interface will be baked into the O/S of both Android and iOS.

The advantage of the Apple/Google API is that the proximity detection is built
into the kernel as a background task. Don't have to worry about the app being
foreground or not, and it can be left running without draining the battery.


        Hugh Fisher

More information about the linux mailing list