1377987 - Ensure that Linux distros get Google API keys for Safe Browsing in time for 56

Status: RESOLVED FIXED

(Toolkit :: Safe Browsing, enhancement, P2)

Description

[François Marier [:francois]]

Each distro will have to:

1. register a new project on https://console.developers.google.com/
2. create a new credential (API key)
3. enable the Safe Browsing API from https://console.developers.google.com/apis/api/safebrowsing.googleapis.com/overview

I can help distros get these flagged properly with Google so that they are allocated enough quota.

Comment 1

[François Marier [:francois]]

Mike, as discussed in SF, can we do this in Debian first so that we confirm that the process works?

Comment 2

[François Marier [:francois]]

Distros will have to add this to their build config:

  ac_add_options --with-google-api-keyfile=/somewhere/.gapi.key

Comment 3

[François Marier [:francois]]

It turns out many of the distros already have a Google API Key for the geolocation API. In that case, all they need to do is enable the Safe Browsing API (as per comment 0) and then share their Project ID with me.

Comment 4

[François Marier [:francois]]

Mike, you could use the same API key as the chromium-browser package: https://anonscm.debian.org/cgit/pkg-chromium/pkg-chromium.git/tree/debian/apikeys?id=refs/heads/master

I have verified that it has access to the new Safe Browsing lists.

Comment 5

[François Marier [:francois]]

All distros are green, except for Debian.