From owner-freebsd-gecko@freebsd.org Sat Aug 26 00:57:16 2017 Return-Path: Delivered-To: freebsd-gecko@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34316DE5841 for ; Sat, 26 Aug 2017 00:57:16 +0000 (UTC) (envelope-from francois@mozilla.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0EA4C7798A for ; Sat, 26 Aug 2017 00:57:16 +0000 (UTC) (envelope-from francois@mozilla.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0B0FFDE5840; Sat, 26 Aug 2017 00:57:16 +0000 (UTC) Delivered-To: gecko@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08638DE583F for ; Sat, 26 Aug 2017 00:57:16 +0000 (UTC) (envelope-from francois@mozilla.com) Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D3BB277988 for ; Sat, 26 Aug 2017 00:57:15 +0000 (UTC) (envelope-from francois@mozilla.com) Received: by mail-pg0-x236.google.com with SMTP id 83so6860022pgb.4 for ; Fri, 25 Aug 2017 17:57:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=subject:to:cc:references:from:openpgp:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=RVT2qVHtql2b6RqMVMpqeV3Ay2PrAKgaxLWjS/fBM7k=; b=H8VSZuATx2q0jvQUgJCns4EpPLycHFW1Lep29Kb+YdikeqXtY8A3yalUvhvG1sFhQu jT73yLp0VsEGJZ5pRG8EBkZvXNq5o81IOK7xKwCb0kRW9+9KzTyeYMvNBuXnpNO1yXnk AyDec+0yiHh1AnZqwUKIaSVrxgLCrkKebChS0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=RVT2qVHtql2b6RqMVMpqeV3Ay2PrAKgaxLWjS/fBM7k=; b=Ig/g736aR3zhlu1zD6UTOR3rXJj60RNyLot0qCUParghfgw97YyftJNsUKeprG5o6m Ng2FDvZTG86BTq8ZQCcL94p/aR6NOjGJ8o0XKlCSz3/kcM0QGN8ax0yMB/FxmD6eAd3h OO+1P4HmNvc+R/UE06Hk+qAqug/FokE+sZ7/LWlDmEHIp6+iH4pN83t0UDYuTJlZRSDd JFOllqFRznnThEVaIZo+KwgvqPtMGqJDaeUmXgaj2nVQmL6k9ZR0+u6sW+a7GSEc20aB LHy/YTBgfN2t/q/goSkye+u1eny/olfFPTXV9QDMFzeihf2CXVWhVngCRGqhlkW3IZ/K OJhg== X-Gm-Message-State: AHYfb5iT1TXJaJRG6PNmtNrEOAIIyreRKujis/LRo0Akf/wUYTFvQqPw xY+7jPwRk6U46iBL X-Received: by 10.84.139.129 with SMTP id 1mr338192plr.122.1503709034795; Fri, 25 Aug 2017 17:57:14 -0700 (PDT) Received: from ?IPv6:2607:ffb0:3001:224:dcba:18a4:73b3:d70e? ([2607:ffb0:3001:224:dcba:18a4:73b3:d70e]) by smtp.googlemail.com with ESMTPSA id n11sm15304665pfg.15.2017.08.25.17.57.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Aug 2017 17:57:13 -0700 (PDT) Subject: Re: Firefox 56 in FreeBSD: Safe Browsing API key required To: Jan Beich Cc: gecko@FreeBSD.org, =?UTF-8?Q?Ren=c3=a9_Ladan?= References: <7a098f0b-2412-5ea5-5378-eb36c68fee2a@mozilla.com> From: Francois Marier Openpgp: url=https://people.mozilla.org/~fmarier/francois_marier.asc Message-ID: Date: Fri, 25 Aug 2017 17:57:13 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Aug 2017 00:57:16 -0000 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