Confirmed users
908
edits
Security/Safe Browsing/V4 Implementation: Difference between revisions
Jump to navigation
Jump to search
Security/Safe Browsing/V4 Implementation (view source)
Revision as of 21:09, 18 July 2017
, 18 July 2017→Using custom API key: simplify API key instructions
(→Quick Links: Add target dates and deadlines) |
(→Using custom API key: simplify API key instructions) |
||
| Line 24: | Line 24: | ||
= Using custom API key = | = Using custom API key = | ||
We are required to have a API key to access | We are required to have a API key to access Google services like geolocation and Safe Browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with Mozilla. However, if you build your own Firefox, the API key will be substituted with the string <tt>"no-google-api-key"</tt>, which is not a valid key. | ||
# Obtain a Safe Browsing | Here's how to get your own key: | ||
# Obtain a Safe Browsing Google API key from https://console.developers.google.com and put it in <tt>~/.gapi.data</tt> | |||
# Add | # Add <tt>ac_add_options --with-google-api-keyfile=/home/foobar/.gapi.data</tt> to your <tt>.mozconfig</tt> | ||
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx' | # Rebuild and check if <tt>config.status</tt> has something like <tt>'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'</tt> | ||
= Try Google Safe Browsing v4! = | = Try Google Safe Browsing v4! = | ||