Date: Tue, 08 Aug 2017 06:37:02 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: Francois Marier <francois@mozilla.com> Cc: gecko@FreeBSD.org, =?utf-8?Q?Ren=C3=A9?= Ladan <rene@FreeBSD.org> Subject: Re: Firefox 56 in FreeBSD: Safe Browsing API key required Message-ID: <o9rq-isk1-wny@FreeBSD.org> In-Reply-To: <7a098f0b-2412-5ea5-5378-eb36c68fee2a@mozilla.com> (Francois Marier's message of "Mon, 7 Aug 2017 19:38:18 -0700") References: <7a098f0b-2412-5ea5-5378-eb36c68fee2a@mozilla.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Francois Marier <francois@mozilla.com> writes: > Hi, > > I'm responsible for Safe Browsing in Firefox and I am reaching out to > make sure that FreeBSD is ready for Firefox 56 (to be released on > 2017-09-26). > > In that version, we will be switching to the latest version of the Safe > Browsing API for our malware/phishing protection and that requires a > valid API key from Google. Do you mean "google" or "google4" in about:url-classifier? Both seem to be available in FF55 and FF56. However, "google4" currently fails as "cannot update" or "download error (400)" e.g., $ firefox -new-instance -profile $(mktemp -d) about:url-classifier Safe Browsing server returned a 400 during update: request = https://safebrowsing.googleapis.com/v4/threatListUpdates:fetch?$ct=application/x-protobuf&key=<...>&$httpMethod=POST&$req=<...>; > > You seem to be passing it as an environment variable: > > https://svnweb.freebsd.org/ports/head/www/firefox/files/patch-env-api-keys?view=markup The patch is just a workaround to avoid having to generate a temporary file. The API key is in another file, see https://svnweb.freebsd.org/ports/head/Mk/bsd.gecko.mk?view=markup#l276 > If you are indeed already including a Google API key in your builds, > then all you need to do is to add the Safe Browsing API to it, see > https://bugzilla.mozilla.org/show_bug.cgi?id=1377987#c0. Does SafeBrowsing require defining MOZILLA_OFFICIAL during build which would also enable Telemetry pings? > > Afterwards, if you send me the project ID (not the API key), I can > liaise with Google to make sure it has the right access and appropriate > quota. Our gecko@ team shares Google API key with chromium@ team. rene@ was the one who originally obtained the key, so maybe he still has the project ID. I can't really help with anything that requires a Google Account as signing up for one doesn't work via Tor.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?o9rq-isk1-wny>