From owner-freebsd-chromium@FreeBSD.ORG Mon Jun 3 11:06:22 2013 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7563648A for ; Mon, 3 Jun 2013 11:06:22 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 67FEF136E for ; Mon, 3 Jun 2013 11:06:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r53B6MAn014521 for ; Mon, 3 Jun 2013 11:06:22 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r53B6MuX014519 for chromium@FreeBSD.org; Mon, 3 Jun 2013 11:06:22 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Jun 2013 11:06:22 GMT Message-Id: <201306031106.r53B6MuX014519@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: chromium@FreeBSD.org Subject: Current problem reports assigned to 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: Mon, 03 Jun 2013 11:06:22 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f ports/175369 chromium www/chromium: Chromimum Desktop Integration doesn't op o ports/165635 chromium www/chromium: 17.0.963.56: proxy isn't read by chrome f ports/165634 chromium www/chromium : 17.0.963.56 doesn't show physical print 3 problems total. From owner-freebsd-chromium@FreeBSD.ORG Tue Jun 4 09:21:08 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 9D23EE63 for ; Tue, 4 Jun 2013 09:21:08 +0000 (UTC) (envelope-from kaltheat@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id 737D613C0 for ; Tue, 4 Jun 2013 09:21:08 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=date:from:to:subject:message-id:mime-version:content-type:user-agent:sender; b=gVGrn2DR4tCruL55KtAcvT2q3Yr4FIxH6xWx/qTtKzdnC2IPW0grhzFZ/92PJrEHupgnMX9Zwp4P Km9qQ+++3d4l3lOEjI1OdVZpoxjR2ci67GDP+WTaH9/+KiVI2pfV Received: from sol (35-156-103-86.dynamic.dsl.tng.de [86.103.156.35]) by mx.zohomail.com with SMTPS id 1370337662120662.6596693789078; Tue, 4 Jun 2013 02:21:02 -0700 (PDT) Date: Tue, 4 Jun 2013 11:20:54 +0200 From: kaltheat@googlemail.com To: freebsd-chromium@freebsd.org Subject: capsicum support plans Message-ID: <20130604092054.GA1185@sol> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: kaltheat@zoho.com X-ZohoMailClient: External X-Zoho-Virus-Status: 2 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: Tue, 04 Jun 2013 09:21:08 -0000 Hi, are there any plans to provide chromium for FreeBSD with capsicum support? If I am right Mr. Watson already did it for a previous chromium-version and it was "little" effort to do so. It seems that since August, 2012 Mr. Dawidek is improving capsicum. His work seems to be funded by Google. Does this mean that they want to use it in base-chromium so that there is no need for FreeBSD-chromium-port to support capsicum on its own? Regards, kaltheat From owner-freebsd-chromium@FreeBSD.ORG Tue Jun 4 17:30:39 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2751EA4D for ; Tue, 4 Jun 2013 17:30:39 +0000 (UTC) (envelope-from lkchen@k-state.edu) Received: from ksu-out.merit.edu (ksu-out.merit.edu [207.75.117.132]) by mx1.freebsd.org (Postfix) with ESMTP id E9240109A for ; Tue, 4 Jun 2013 17:30:38 +0000 (UTC) X-Merit-ExtLoop1: 1 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ag0FAPkirlHPS3TT/2dsb2JhbABZgwkwgzy8ZBZ0giMBAQUjVgwPGgINGQJZiCYMq2OJZIgdBIEmjDGBaoIxgRQDqH+DK4IL X-IronPort-AV: E=Sophos;i="4.87,801,1363147200"; d="scan'208";a="224036452" X-MERIT-SOURCE: KSU Received: from ksu-sfpop-mailstore02.merit.edu ([207.75.116.211]) by sfpop-ironport07.merit.edu with ESMTP; 04 Jun 2013 13:30:30 -0400 Date: Tue, 4 Jun 2013 13:30:30 -0400 (EDT) From: "Lawrence K. Chen, P.Eng." To: kaltheat@googlemail.com Message-ID: <746998042.22481637.1370367030598.JavaMail.root@k-state.edu> In-Reply-To: <20130604092054.GA1185@sol> Subject: Re: capsicum support plans MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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: Tue, 04 Jun 2013 17:30:39 -0000 ----- Original Message ----- > > Hi, > > are there any plans to provide chromium for FreeBSD with capsicum > support? If I > am right Mr. Watson already did it for a previous chromium-version > and it was > "little" effort to do so. > It seems that since August, 2012 Mr. Dawidek is improving capsicum. > His work seems > to be funded by Google. Does this mean that they want to use it in > base-chromium > so that there is no need for FreeBSD-chromium-port to support > capsicum on its own? > > Regards, > kaltheat > Hmmm, suppose I need to read up on capsicum... Google is matching the funding from The FreeBSD Foundation on capsicum, with Google working on the Linux version. Sounds like they want it for Chrome OS, so ... Well, there's a wiki entry on ChromiumCapsicum -- https://wiki.freebsd.org/ChromiumCapsicum Suppose the question is who wants to do it, and will it be part of the current port or as a slave port? Lawrence From owner-freebsd-chromium@FreeBSD.ORG Wed Jun 5 12:28:14 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 BB57973B for ; Wed, 5 Jun 2013 12:28:14 +0000 (UTC) (envelope-from kaltheat@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id A87C516C0 for ; Wed, 5 Jun 2013 12:28:14 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=date:from:to:cc:subject:message-id:references:mime-version:content-type:in-reply-to:user-agent:sender; b=IoHk+ErQWso5/9E+oMyDXSxnP3mb3NKO0BwWVcjc3xvqzMGoUpJ3jv0RsitL7axH6kgwkQiNLZFn xNKAyYBkAEcTAOknpFbtrWMgF6TcuejlIlhmRTqP4bKSNo6mXWHT Received: from sol (240-147-103-86.dynamic.dsl.tng.de [86.103.147.240]) by mx.zohomail.com with SMTPS id 137043527935431.25266289106446; Wed, 5 Jun 2013 05:27:59 -0700 (PDT) Date: Wed, 5 Jun 2013 14:27:55 +0200 From: kaltheat@googlemail.com To: "Lawrence K. Chen, P.Eng." Subject: Re: capsicum support plans Message-ID: <20130605122755.GB67864@sol> References: <20130604092054.GA1185@sol> <746998042.22481637.1370367030598.JavaMail.root@k-state.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <746998042.22481637.1370367030598.JavaMail.root@k-state.edu> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: kaltheat@zoho.com X-ZohoMailClient: External X-Zoho-Virus-Status: 2 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, 05 Jun 2013 12:28:14 -0000 On Tue, Jun 04, 2013 at 01:30:30PM -0400, Lawrence K. Chen, P.Eng. wrote: > > ----- Original Message ----- > > > > Hi, > > > > are there any plans to provide chromium for FreeBSD with capsicum > > support? If I > > am right Mr. Watson already did it for a previous chromium-version > > and it was > > "little" effort to do so. > > It seems that since August, 2012 Mr. Dawidek is improving capsicum. > > His work seems > > to be funded by Google. Does this mean that they want to use it in > > base-chromium > > so that there is no need for FreeBSD-chromium-port to support > > capsicum on its own? > > > > Regards, > > kaltheat > > > > Hmmm, suppose I need to read up on capsicum... > > Google is matching the funding from The FreeBSD Foundation on capsicum, with > Google working on the Linux version. Sounds like they want it for Chrome OS, > so ... > > Well, there's a wiki entry on ChromiumCapsicum -- > https://wiki.freebsd.org/ChromiumCapsicum > > Suppose the question is who wants to do it, and will it be part of the > current port or as a slave port? > > Lawrence Well, this wasn't exactly my question. But if this means that there are currently no plans among the chromium-porters to implement capsicum-support, then you're right: this would be the next question ... ;) Sadly, I'm not able to help with it, but nonetheless I would appreciate to use it ... Regards, kaltheat From owner-freebsd-chromium@FreeBSD.ORG Wed Jun 5 17:13:53 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EEDC8D89 for ; Wed, 5 Jun 2013 17:13:53 +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 BD0211471 for ; Wed, 5 Jun 2013 17:13:53 +0000 (UTC) X-Merit-ExtLoop1: 1 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFAIBwr1HPS3TT/2dsb2JhbABZgwmDbLxtFnSCIwEBBAEjVgUHDxoCDRkCWYggBqwUiT6IB4EmjiKCMYEUA6h/gyuCCw X-IronPort-AV: E=Sophos;i="4.87,808,1363147200"; d="scan'208";a="224365585" X-MERIT-SOURCE: KSU Received: from ksu-sfpop-mailstore02.merit.edu ([207.75.116.211]) by sfpop-ironport07.merit.edu with ESMTP; 05 Jun 2013 13:13:47 -0400 Date: Wed, 5 Jun 2013 13:13:47 -0400 (EDT) From: "Lawrence K. Chen, P.Eng." To: kaltheat@googlemail.com Message-ID: <228289102.22862677.1370452427317.JavaMail.root@k-state.edu> In-Reply-To: <20130605122755.GB67864@sol> Subject: Re: capsicum support plans MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [70.179.144.108] 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, 05 Jun 2013 17:13:54 -0000 ----- Original Message ----- > Well, this wasn't exactly my question. But if this means that there > are > currently no plans among the chromium-porters to implement > capsicum-support, > then you're right: this would be the next question ... ;) > Sadly, I'm not able to help with it, but nonetheless I would > appreciate to > use it ... > > Regards, > kaltheat > > > Well, I'm not among the chromium-porters, but I have contributed ... ;) Lawrence From owner-freebsd-chromium@FreeBSD.ORG Thu Jun 6 02:19:17 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D9AD3583 for ; Thu, 6 Jun 2013 02:19:17 +0000 (UTC) (envelope-from bounces+551257-deab-freebsd-chromium=freebsd.org@sendemail.dealstrain.com) Received: from o1.sendemail.dealstrain.com (o1.sendemail.dealstrain.com [198.37.153.151]) by mx1.freebsd.org (Postfix) with SMTP id 9B3EC1EFB for ; Thu, 6 Jun 2013 02:19:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendemail.dealstrain.com; h=content-type:mime-version:from:to:reply-to:subject :list-unsubscribe; s=smtpapi; bh=pKZV3MnB1W6WSQb2/rmi+p1DVxI=; b= lnTtAetZcVKhqgMkUZdFyvUHF5CAQ+7uuwFG5smlxT51hX2W6I4zHxxYaKcD2dUR Ms7h9qqA6F7cEQNF/eG3aJQFN56ycSpZJ/Mc9988WvVgl/Y5+OalrBMQkkAfXIL9 pZccNr71nnyDEIsyd1te56bl9kUSjYIpsAdGRYRDlQA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=dealstrain.com; h= content-type:mime-version:from:to:reply-to:subject :list-unsubscribe; q=dns; s=smtpapi; b=eLrKpaAaDKE5mIdaILktVrqyj w2rb74kwzXQ/omiYTbQfCUEZxxQfGYMYzquhCm5FsZUHKqeb1Q3nKCzgrkwlKTJO ZNfdiIRa71VCe443MXedl5i1QX05H4whlADgdIE1/YuN76BaJvn70Hf6KxIPHLa4 0fSbPz2gSsTkJZEYHc= Received: by 10.16.69.96 with SMTP id mf29.7263.51AFF0AA7 Thu, 06 Jun 2013 02:15:06 +0000 (UTC) Received: from NTUxMjU3 (174.37.65.4-static.reverse.softlayer.com [174.37.65.4]) by mi18.sendgrid.net (SG) with HTTP id 13f17441b19.1445.879b6b for ; Wed, 05 Jun 2013 21:15:06 -0500 (CST) MIME-Version: 1.0 From: Deals Train To: freebsd-chromium@freebsd.org Subject: Increase Sales, Get More Leads & Reach To New Customers Message-ID: <1370484906.84354084987770215@mf29.sendgrid.net> Date: Thu, 06 Jun 2013 02:15:06 +0000 (UTC) X-SG-EID: XhyBwObMhraAR+zdwMupjVGEs/UG/hkvmklqQBd8XaaIkG0Nv7CoPVT5tL6RiX3o29Dxe3+XJqviocV5DIRtBxD9RSVc3P4wjhAfEqc/57Jygo8xE0AA0/me4QeYIeNyNtlBYfVOSiiKimClir+BIw== X-SG-ID: VPWZYjw6GOzHdwkwPeoX9QiEbzQXX/gF9P8njHP5+LAIpdABybyq0uT9Od0+0BydZdvPBWqV+nvATWvePBCwhO0AQ3lBODKRLidnWPe0Y/a6HykqnEb8XnmCzS9PBcFrWoMk9xmBwQVn9ESF6Y67Wjt80r5T2eluDUzNHogNkrxFzbTmoWaog6Za7eoa1Dw6 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendemail.dealstrain.com; h=content-type:mime-version:from:to:reply-to:subject :list-unsubscribe; s=smtpapi; bh=vDpxYgL7AXJd3EHYIuLQaWulYHo=; b= ZhMnesA4L9F60Qla/WVhhG6vDl+uiDu+60dPL/UEOaDTakNDBhbriWTcXBaiJw5e F1Gmwvy368StsueZL+TQgatYa4JP+D3pTvJDH6+GS3ths7MryYzz8eplNBueb3EN 31Dq2sJPZnDSKEth/twHyoJYVzldF/7KOL8Pp2UuaX8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=dealstrain.com; h= content-type:mime-version:from:to:reply-to:subject :list-unsubscribe; q=dns; s=smtpapi; b=fYWgbtT0GfCMJ5qwj662K3B2D wczu/ZCAtybG9gnGP2H46D1M4H/536WPGnUEjzPYBRceHbkDUfxrIVejJ3D8gvL8 bXoNSG1OMJptzYAfeXGApa40SYs+6j0JdeVCDd4OpPspY5U+sL588hsettM0xeH4 jFJWoRQMJS3thF3zh8= Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: admin@dealstrain.com List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jun 2013 02:19:17 -0000 Email not displaying correctly? View it ( http://sendgrid.org/wf/webmail?rp= =3DZTI1bGQzTnNaWFIwWlhKZmFXUTZNVEl6TkN4MWMyVnlYMmxrT2pJMU5qVTBmUWV5SnVaWGR6= YkdWMGRHVnlYMmxrSWpvaU1UWTJOVEF4TmlJc0ltNWxkM05zWlhSMFpYSmZkWE5sY2w5cFpDSTZ= Nall4T1RReU5EZzJOalI5 ) in your browser Increase Sales, Get More Leads & Reach To New Customers ( http://sendgrid.c= om/newsletter/editNewsletter/id/1494080 ) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D DealsTrain.com is determined to promote best deals, products & promotions i= n Singapore. =C2=A0 We will be promoting your Deals (on our website) through advertisement in t= op daily newspapers, social networking sites and through our dedicated 8 pa= ge brochure (contains best deals with full description,click here to see th= e brochure ( http://www.dealstrain.com/images/brochure2.pdf )). We are also= advertising on TV and in=C2=A0various newspapers, which will benefit your = brand as well. =C2=A0 =C2=A0We will always try our best to make your deal much more attractive (B= y adding goodies/freebies from our side). =C2=A0 Commission :=C2=A0=C2=A015% commission of discounted value [Limited Offer]. Payment Terms: Highly Flexible ( as adjusted by merchant). =C2=A0 If we don=E2=80=99t bring any business, you will not pay but your business = will get noticed by tons of our customers for free...=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0 Please provide us following information to discuss further: =C2=A0 1.=C2=A0=C2=A0=C2=A0=C2=A0 Authorize Person Name/Phone: 2.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Store Name & Address: 3.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Website: 4.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Deals/Promotions you want to offer: =C2=A0 Always=C2=A0a good opportunity to associate with us. You will gain access t= o our tons of customers and exposure through our advertisement and promotio= ns. =C2=A0 Best Regards, DealsTrain http://www.dealstrain.com ( http://www.dealstrain.com/ ) contact@dealstrain.com +65-65995001 =C2=A0 =C2=A0 To unsubscribe please click here ( http://sendemail.dealstrain.com/wf/unsub= scribe?upn=3DQ1G7K8cYCrLWsp3rtsmPRnVEcs1nNJblUJ9MbT8uitlk9sFPgAPN0F-2FSJqSm= AohnYwQAwrZnTqFdtj8UuuSrYI-2Be88AxnOXFWn-2FbsnR0LWg5bULJBbTQoDaeG52LvqtAdba= PaRdTBrEHKX94PjhwAb-2F1dpzIoLb3DuMv6upLRqmbahWWHO9SoA2QS0kJWWKhIHU4g49qkByK= 2CssEs5iIW8DN-2FRJ01CzTlKtYVE-2BT9IBqw-2FQ1t3R1f2SrkvdZYTJB8-2FWwIYOwjq4I-2= FdHEB8opRaCJFxQ779-2FDdReiIDANcgVh-2FdGBYKxtKLoH3Tok1AjLzdw8hR30CcLt5P693D8= jI8v2rkYFYVp62pLf9b-2FVFU-3D ) Deals Train #26-04, 10 Anson Road, Singapore, Singapore, 079903= From owner-freebsd-chromium@FreeBSD.ORG Thu Jun 6 19:53:45 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 0A20C632 for ; Thu, 6 Jun 2013 19:53:45 +0000 (UTC) (envelope-from david@code.davidpcaldwell.com) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id D460B1092 for ; Thu, 6 Jun 2013 19:53:44 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id 17so8473913iea.3 for ; Thu, 06 Jun 2013 12:53:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:content-type:x-gm-message-state; bh=5hXdnGO/nlreuA9zEpTQ87S3umS8N8220weAVWNtZXM=; b=TlNgTLrYPAhKAhDvO1xUDG3rqjz8erlFJN70mxfOBDaW5mm0KWpquowjgnSNlVrGk2 p6/gLZl9YiAOk7oPBtx2CTjzzcpIziR1woCikod8bLnZanGy8wokZC90IgnHhk3+SeWX WO5N5o+XaQB4l7LHLbNVxFPGWaHDAZlCeyq0zu8207J0hEQCTDw9evSXg/4JTXCr6mb2 fNGWStOJ+IqgtZ4IIKfcGvH34Q0j2JrPmXgX89GODcyqwcJ877oQ5xLbUmCdh3z5/cjA AW7/cHkvGbpz+RicREiSyrudh6N2fxS0i84kW/MOMOk6llfFuiLzeQ8k/EkcTZCQQsjy YoBg== X-Received: by 10.50.61.141 with SMTP id p13mr6575960igr.9.1370547949991; Thu, 06 Jun 2013 12:45:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.24.166 with HTTP; Thu, 6 Jun 2013 12:45:29 -0700 (PDT) X-Originating-IP: [74.97.25.177] In-Reply-To: <1239531525.21357067.1369952880052.JavaMail.root@k-state.edu> References: <1239531525.21357067.1369952880052.JavaMail.root@k-state.edu> From: "David P. Caldwell" Date: Thu, 6 Jun 2013 15:45:29 -0400 Message-ID: Subject: Re: using API keys in the FreeBSD Chromium port To: freebsd-chromium@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQn4kBPNRpk2kyj9uGcAJ0bn7n53GeElucJulAkwFilN161BBGDMfgXG4ouSp6TZgFxsA25k 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: Thu, 06 Jun 2013 19:53:45 -0000 Thanks for doing this! I was a bit mystified as to why sync had broken, and stumbled here, eventually. I've used some of the other Google APIs and, at least for those, I'm pretty sure these are intended to be per-application (not per-user) keys, so I think including them in the build is consistent with what they are "normally" for. See https://code.google.com/apis/console/ where you "create a project" and get an API key that your application uses when issuing requests. See also https://developers.google.com/api-client-library/python/guide/aaa_apikeys I agree the language "don't share with other users" is confusing, so I'm not 100% sure. -- David Caldwell http://www.davidpcaldwell.com/ On Thu, May 30, 2013 at 6:28 PM, Lawrence K. Chen, P.Eng. wrote: > > > ----- Original Message ----- >> > >> > >> > - Don't ship the port with a key. Instead, require the builder >> > (currently everyone who runs FreeBSD) to acquire one for >> > themselves. >> > When the key is not present, don't build the features that requires >> > an >> > API key. >> > - On FreeBSD package building cluster (as well as PC-BSD ones), >> > deploy the "official" key and make binaries there. >> > >> > I don't see how this would even work as expected, though: the key >> > is >> > embedded in the binary and thus anyone who can run the binary and >> > have >> > debugging tools would be able to extract it. This situation is >> > totally different from normal OAuth scenario, where API key is >> > deployed on servers and protected from being accessed by average >> > users, and the API provider can easily block misbehaving client >> > when >> > the key is "stolen". >> >> >> I may be wrong but i don't think that this is feasible, you can not >> expect >> every enduser to generate keys so he can use the browser. >> >> We just need a key that will be "blessed" as official for FreeBSD, >> just >> like Debian [0], Gentoo [1], Arch [2] and others have done. >> >> [0] >> http://anonscm.debian.org/gitweb/?p=pkg-chromium/pkg-chromium.git;a=blob;f=debian/rules;hb=HEAD >> [1] >> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/chromium/chromium-9999-r1.ebuild?view=markup >> [2] >> https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/chromium > > And, presumably > > https://github.com/gliaskos/freebsd-chromium/commit/8701e94cc54126d6907d7665b5181e5d53705d90 > > is the official FreeBSD one. > > But the question is whether how Debian/Gentoo/Arch, and now FreeBSD, are distributing the keys in violation of > > http://www.chromium.org/developers/how-tos/api-keys > > "Note that the keys you have now acquired are not for distribution purposes and must not be shared with other users." > > I see geolocation is part api keys..is that why it hasn't been working since 23? > > Wonder if everybody who runs FreeBSD could just join the FreeBSD team and see the key? > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org" From owner-freebsd-chromium@FreeBSD.ORG Thu Jun 6 20:21:57 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0EF69E06 for ; Thu, 6 Jun 2013 20:21:57 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by mx1.freebsd.org (Postfix) with ESMTP id 9BC4811F1 for ; Thu, 6 Jun 2013 20:21:56 +0000 (UTC) Received: by mail-we0-f177.google.com with SMTP id m19so2399717wev.22 for ; Thu, 06 Jun 2013 13:21:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Jon0cDb+0lUiIgoLaECtsJqJH2B+BXdbk8fPVPFKh6A=; b=LZjVBRLHXKOfSR0YT2G3R8RtjYAIWunFTuZBuRdPszxandtz9TATGC6Z35wf4BA3Cl 5OlWZNM9/uPj0mK68U57GAsTi6GnMbkpS/vIxEM/3IWfRzfAi7c62XJ8ViHd/3z7OeIV HKlBUHGNCb96hYnspf3lJ1CUMDkovw/ptJ7fO2iGm8T6GWfzg1Br/sfnOQEAonZEEByH HlHSG47ECzWai+oUDRTfRwWBKOpUhbhPsIO3CKt3yJ9pPdTLwcfq0aomzVnWIijSJcfr Cg7dep8QNwnt3zCkm72GYdl57d1X9nCnNHYMVCJTmDwcn14LyI7ym64RojW+LipzOtW0 8gKw== MIME-Version: 1.0 X-Received: by 10.194.110.169 with SMTP id ib9mr33661205wjb.12.1370550115777; Thu, 06 Jun 2013 13:21:55 -0700 (PDT) Received: by 10.217.139.202 with HTTP; Thu, 6 Jun 2013 13:21:55 -0700 (PDT) In-Reply-To: References: <1239531525.21357067.1369952880052.JavaMail.root@k-state.edu> Date: Thu, 6 Jun 2013 23:21:55 +0300 Message-ID: Subject: Re: using API keys in the FreeBSD Chromium port From: George Liaskos To: "David P. Caldwell" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Thu, 06 Jun 2013 20:21:57 -0000 Ren=C3=A9@ got an official response [0] concerning they key, nothing to wor= ry about. Just Enjoy [0] http://svnweb.freebsd.org/ports?view=3Drevision&revision=3D319796 From owner-freebsd-chromium@FreeBSD.ORG Fri Jun 7 13:36:45 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7A798CA for ; Fri, 7 Jun 2013 13:36:45 +0000 (UTC) (envelope-from beastie@tardisi.com) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by mx1.freebsd.org (Postfix) with ESMTP id 507E41F72 for ; Fri, 7 Jun 2013 13:36:44 +0000 (UTC) Received: from ip70-179-144-108.fv.ks.cox.net ([70.179.144.108] helo=zen.lhaven.homeip.net) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1UkwqS-000NTn-6M for freebsd-chromium@freebsd.org; Fri, 07 Jun 2013 13:36:44 +0000 Received: from lhaven.homeip.net (localhost [127.0.0.1]) by zen.lhaven.homeip.net (8.14.7/8.14.5) with ESMTP id r57DafFp057640 for ; Fri, 7 Jun 2013 08:36:41 -0500 (CDT) (envelope-from beastie@tardisi.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 70.179.144.108 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19gJNntxbrzqL3+m/pxTArRmygQH2Tflb4= X-Authentication-Warning: zen.lhaven.homeip.net: Host localhost [127.0.0.1] claimed to be lhaven.homeip.net MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 07 Jun 2013 08:36:36 -0500 From: The BSD Dreamer To: freebsd-chromium@freebsd.org Subject: Re: using API keys in the FreeBSD Chromium port In-Reply-To: <1239531525.21357067.1369952880052.JavaMail.root@k-state.edu> References: <1239531525.21357067.1369952880052.JavaMail.root@k-state.edu> Message-ID: <1519f56f8f81f3b1659f41226780662a@lhaven.homeip.net> X-Sender: beastie@tardisi.com User-Agent: Roundcube Webmail/0.8.6 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on zen.lhaven.homeip.net 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: Fri, 07 Jun 2013 13:36:45 -0000 On 2013-05-30 17:28, Lawrence K. Chen, P.Eng. wrote: > > I see geolocation is part api keys..is that why it hasn't been working since > 23? > Oh look...after updating to the latest chromium, the chrome apps "currently" and "full screen weather" now know where I am. Lawrence From owner-freebsd-chromium@FreeBSD.ORG Fri Jun 7 15:05:30 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 C5E21CA0 for ; Fri, 7 Jun 2013 15:05:30 +0000 (UTC) (envelope-from beastie@tardisi.com) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by mx1.freebsd.org (Postfix) with ESMTP id 9F06D13B8 for ; Fri, 7 Jun 2013 15:05:30 +0000 (UTC) Received: from ip70-179-144-108.fv.ks.cox.net ([70.179.144.108] helo=zen.lhaven.homeip.net) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1UkyEG-0002rb-DK for freebsd-chromium@freebsd.org; Fri, 07 Jun 2013 15:05:24 +0000 Received: from lhaven.homeip.net (localhost [127.0.0.1]) by zen.lhaven.homeip.net (8.14.7/8.14.5) with ESMTP id r57F5LNo089548 for ; Fri, 7 Jun 2013 10:05:21 -0500 (CDT) (envelope-from beastie@tardisi.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 70.179.144.108 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18jrDuumaJ/3MbV+gtgTNvGAYVVwoO8oAc= X-Authentication-Warning: zen.lhaven.homeip.net: Host localhost [127.0.0.1] claimed to be lhaven.homeip.net MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 07 Jun 2013 10:05:16 -0500 From: The BSD Dreamer To: Freebsd chromium Subject: xorg.conf and flash Message-ID: <79fbaa44405c3a416ef1d1eb82cda3dd@lhaven.homeip.net> X-Sender: beastie@tardisi.com User-Agent: Roundcube Webmail/0.8.6 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on zen.lhaven.homeip.net 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: Fri, 07 Jun 2013 15:05:30 -0000 Some last fall, flash started asking weird in Chromium - seemed to also start with 24...suspect its how chromium uses shared memory now? Basically flash would render and then whiteout...scrolling the page would force it to redraw correctly, but could whiteout immediately. I think I've mentioned it in passing before, but hadn't seen anything else on the list about it. So, I decided that maybe its a problem specific to my setup....first I played around to see if there were flash settings to play with....had turned off hardware acceleration long ago to solve the blue skin tone problem. Didn't look like there was anything else that would do anything. Then I decided to look at my xorg.conf....after a long process of trial and error, I found that removing the option "AllowSHMPixmaps" "True" fixed the whiteout. Though now when flash first renders on the screen its garbage that looks like it might be a mash of the unexposed output from various terminals on my desktop. Kind of distracting, but it eventually shows right and is usable again. Wondering if anybody knows off hand of what parameters are good or bad that I might look to next, otherwise...I'm inclined to just put up with this issue... here's what my "Screen" section looks like now: Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 Option "NoLogo" "true" Option "RenderAccel" "True" Option "Overlay" "True" Option "AddARGBGLXVisuals" "True" Option "DisableGLXRootClipping" "True" Option "Coolbits" "1" Option "CursorShadow" "True" Option "DamageEvents" "True" Option "UseEvents" "True" # Option "AllowSHMPixmaps" "True" Option "BackingStore" "on" Option "TripleBuffer" "on" SubSection "Display" Viewport 0 0 Depth 24 Modes "1920x1080" EndSubSection EndSection My xorg.conf was largely lifted from a friend's setup after he had finally gotten X working on his system. Who was also suffering from the same problem, but also has 2 other computers on his desk...so had a work around :) Keeps telling me that I should get Mac.... speaking of which, wonder if somebody can figure out a way to use the flash 11.7 for the Mac on FreeBSD? -- Name: Lawrence "The Dreamer" Chen Call: W0LKC Snail: 1530 College Ave, A5 Email: beastie@tardisi.com Manhattan, KS 66502-2768 Blog: http://lawrencechen.net