From owner-freebsd-chromium@FreeBSD.ORG Wed May 29 20:03:47 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6C9F5EF7; Wed, 29 May 2013 20:03:47 +0000 (UTC) (envelope-from lkchen@k-state.edu) Received: from ksu-out.merit.edu (ksu-out.merit.edu [207.75.117.133]) by mx1.freebsd.org (Postfix) with ESMTP id 27AB8629; Wed, 29 May 2013 20:03:46 +0000 (UTC) X-Merit-ExtLoop1: 1 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AosGADtdplHPS3TT/2dsb2JhbABagwkwgzu+SYEKFnSCIwEBBSNWDA8aAg0ZAlkGEwmIBAynXolwiC6BJoxAeoJ9gRQDqHuDK4FOPQ X-IronPort-AV: E=Sophos;i="4.87,766,1363147200"; d="scan'208";a="926278968" X-MERIT-SOURCE: KSU Received: from ksu-sfpop-mailstore02.merit.edu ([207.75.116.211]) by sfpop-ironport05.merit.edu with ESMTP; 29 May 2013 16:00:00 -0400 Date: Wed, 29 May 2013 16:00:00 -0400 (EDT) From: "Lawrence K. Chen, P.Eng." To: =?utf-8?B?UmVuw6k=?= Ladan Message-ID: <805142494.21026729.1369857600745.JavaMail.root@k-state.edu> In-Reply-To: <51A5F67F.3010706@freebsd.org> Subject: Re: using API keys in the FreeBSD Chromium port MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [129.130.0.181] X-Mailer: Zimbra 7.2.2_GA_2852 (ZimbraWebClient - GC27 ([unknown])/7.2.2_GA_2852) Cc: freebsd-chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 20:03:47 -0000 So, is this why sometimes chromium says I need to sign in again, but then l= eaves me endlessly trying to sign in? =20 I did see that gentoo has it in their ebuild file, with a note: # Note: these are for Gentoo use ONLY. For your own distribution, # please get your own set of keys. Feel free to contact chromium@ge= ntoo.org # for more info. I can't think of any way to avoid including the keys (in the clear or parti= ally obscured) in the ports tree....and avoid making it a RESTRICTED port a= nd having some hassle in providing an out-of-band means to control the dist= ribution of the info. ----- Original Message ----- > Hi, >=20 > the patch at [1] enables the use of FreeBSD API keys which allows > things > like Google Sync to work. However [3] states that these keys "are > not > for distribution purposes and must not be shared with other users". > There has been some discussion about this on how to deal with this > for > source-based at [2], but it seems no consensus has been reached. Is > it > permitted to include these keys in the FreeBSD Ports Tree, and if > not, > are there any alternatives? >=20 > Thanks, > Ren=C3=A9 o behalf of freebsd-chromium >=20 > [1] > https://github.com/gliaskos/freebsd-chromium/commit/8701e94cc54126d6907d7= 665b5181e5d53705d90 >=20 > [2] > https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromiu= m-dev/Qks4W0xLxqc >=20 > [3] http://www.chromium.org/developers/how-tos/api-keys