Date: Fri, 25 Aug 2017 17:57:13 -0700 From: Francois Marier <francois@mozilla.com> To: Jan Beich <jbeich@FreeBSD.org> 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: <e46b8037-a08c-4dfd-c682-e6cff051d174@mozilla.com> In-Reply-To: <o9rq-isk1-wny@FreeBSD.org> References: <7a098f0b-2412-5ea5-5378-eb36c68fee2a@mozilla.com> <o9rq-isk1-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/08/17 09:37 PM, Jan Beich wrote: >> 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? Are you defining MOZILLA_OFFICIAL in your builds? >> 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 just verified your API key in a custom build of Firefox and it will work for basic Safe Browsing V4 support as long as you don't set MOZILLA_OFFICIAL. Francois
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e46b8037-a08c-4dfd-c682-e6cff051d174>