Security/Safe Browsing/V4 Implementation: Difference between revisions

Security/Safe Browsing/V4 Implementation (view source)

936 bytes added , 3 October 2016

no edit summary

Confirmed users

158

edits

@@ Line 10: / Line 10: @@
 When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)
+= Use custom API key =
+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 are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepared a key file and add the path to mozconfig:
+# Obtain a Safe Browsing google API key from https://console.developers.google.com
+#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
+# Create a key file which only contains the API key.
+# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
+# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'
 = Milestones =