Date: Fri, 1 Sep 2017 16:53:17 -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: <1369fb5d-b860-ddd2-a8d0-196ce33b4efa@mozilla.com> In-Reply-To: <lgly-aszi-wny@FreeBSD.org> References: <7a098f0b-2412-5ea5-5378-eb36c68fee2a@mozilla.com> <o9rq-isk1-wny@FreeBSD.org> <e46b8037-a08c-4dfd-c682-e6cff051d174@mozilla.com> <lgly-aszi-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/09/17 04:39 PM, Jan Beich wrote: > No, for now. Other downstream maintainers do, see > https://bugzilla.mozilla.org/show_bug.cgi?id=1352981 Good. Your API key will work fine as long as you build with MOZILLA_OFFICIAL=0. If you ever need to change that, let me know and we can figure out a work-around. >> 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. > > Doesn't seem to work, at least on firefox-56.0b6. We need to uplift https://bugzilla.mozilla.org/show_bug.cgi?id=1394053 to Beta to fix this. Essentially, you can't use download protection on non-official builds (it wouldn't be of any value on BSD anyways, it's mostly for Windows malware), and you need to use a different phishing list. Francois
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1369fb5d-b860-ddd2-a8d0-196ce33b4efa>