Browser.safebrowsing.provider.*.keyURL

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is browser.safebrowsing.provider.*.keyURL.

This article describes the preference browser.safebrowsing.provider.*.keyURL. To add, delete, or modify this preference, you will need to edit your configuration — do not edit this article.

1 Background
2 Possible values and their effects
3 Caveats
4 First checked in
5 Has an effect in
6 Related bugs
7 Related preferences
8 External links

[edit]

Background

Firefox 2.0 incorporates the Google Safe Browsing extension in its own Phishing Protection feature to detect and warn users of phishy web sites.

When Safe Browsing is set to compare visited URLs against a remote blacklist, the URLs are encrypted with a key before they are transmitted. The key is requested from the URL in this preference each time the browser starts if this Safe Browsing service is selected in browser.safebrowsing.dataProvider.

This is an enumerated preference: all preferences whose names start with browser.safebrowsing.provider. are read to generate the list of Safe Browsing providers. The * in the preference name is a non-negative integer, and matches the number in the other preferences needed to describe a provider. It also determines the order in which the providers appear in the options dialog.

[edit]

Possible values and their effects

The URL from which the key for encrypting URLs is retrieved.

By default, the following preference and value exists:

browser.safebrowsing.provider.0.keyURL: https://sb-ssl.google.com/safebrowsing/getkey?client={moz:client}&

Trunk builds:

browser.safebrowsing.provider.0.keyURL: https://sb-ssl.google.com/safebrowsing/newkey?client={moz:client}&appver={moz:version}&pver=2.1

(The string {moz:client} is replaced by 'navclient-auto-ffox' plus the version number for official builds.)

[edit]

Caveats

browser.safebrowsing.enabled must be true for this preference to have an effect.
This preference only has an effect if browser.safebrowsing.remoteLookups is true (when “advanced mode” is on).
If this preference does not refer to an HTTPS URL, submissions to the Safe Browsing server should be considered insecure.

[edit]