From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mail.openembedded.org (Postfix) with ESMTP id E7D49608B6 for ; Tue, 16 Jun 2015 22:16:54 +0000 (UTC) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga102.fm.intel.com with ESMTP; 16 Jun 2015 15:16:56 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,628,1427785200"; d="scan'208";a="747956422" Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by orsmga002.jf.intel.com with ESMTP; 16 Jun 2015 15:16:57 -0700 Received: from orsmsx153.amr.corp.intel.com (10.22.226.247) by ORSMSX106.amr.corp.intel.com (10.22.225.133) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 16 Jun 2015 15:16:55 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.217]) by ORSMSX153.amr.corp.intel.com ([169.254.12.177]) with mapi id 14.03.0224.002; Tue, 16 Jun 2015 15:16:54 -0700 From: "Rifenbark, Scott M" To: "Rifenbark, Scott M" , "Howlett, Liam (Wind River)" Thread-Topic: [bitbake-devel] [PATCH v3] fetch2: Add BB_ALLOWED_NETWORKS support Thread-Index: AQHQqDpGfojCq1JbGUCMjb89gsHvrJ2vQKRwgAC4WYD//4rDoIAAL8BQ Date: Tue, 16 Jun 2015 22:16:53 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB123798D203E58@ORSMSX101.amr.corp.intel.com> References: <1429121824-31200-2-git-send-email-Liam.Howlett@WindRiver.com> <41DEA4B02DBDEF40A0F3B6D0DDB123798D203356@ORSMSX101.amr.corp.intel.com> <1FDE9321-AA20-49D9-A4BE-A4B4514439DB@gmail.com> <1946263.B0TEDLLAIC@peggleto-mobl.ger.corp.intel.com> <20150616134205.GG26078@yow-lhowlett-d0.wrs.com> <41DEA4B02DBDEF40A0F3B6D0DDB123798D203C80@ORSMSX101.amr.corp.intel.com> <20150616192423.GL26078@yow-lhowlett-d0.wrs.com> <41DEA4B02DBDEF40A0F3B6D0DDB123798D203D7F@ORSMSX101.amr.corp.intel.com> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123798D203D7F@ORSMSX101.amr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.138] MIME-Version: 1.0 Cc: Paul Eggleton , "bitbake-devel@lists.openembedded.org" , Gary Thomas Subject: Re: [PATCH v3] fetch2: Add BB_ALLOWED_NETWORKS support X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussion that advance bitbake development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2015 22:16:55 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Ok - I am done with this thread. The description for BB_ALLOWED_NETWORKS i= s now in the BitBake User Manual and the YP Reference Manual. The commit h= as been pushed to my contrib area for bitbake and Richard has been notified= . Scott >-----Original Message----- >From: bitbake-devel-bounces@lists.openembedded.org [mailto:bitbake- >devel-bounces@lists.openembedded.org] On Behalf Of Rifenbark, Scott M >Sent: Tuesday, June 16, 2015 12:26 PM >To: Howlett, Liam (Wind River) >Cc: Paul Eggleton; bitbake-devel@lists.openembedded.org; Gary Thomas >Subject: Re: [bitbake-devel] [PATCH v3] fetch2: Add >BB_ALLOWED_NETWORKS support > > > >>-----Original Message----- >>From: Liam R. Howlett [mailto:Liam.Howlett@windriver.com] >>Sent: Tuesday, June 16, 2015 12:24 PM >>To: Rifenbark, Scott M >>Cc: Paul Eggleton; Bernhard Reutner-Fischer; Gary Thomas; bitbake- >>devel@lists.openembedded.org >>Subject: Re: [bitbake-devel] [PATCH v3] fetch2: Add >BB_ALLOWED_NETWORKS >>support >> >>* Rifenbark, Scott M [150616 11:25]: >>> >>> >>> >-----Original Message----- >>> >From: Liam R. Howlett [mailto:Liam.Howlett@windriver.com] >>> >Sent: Tuesday, June 16, 2015 6:42 AM >>> >To: Paul Eggleton >>> >Cc: Bernhard Reutner-Fischer; Rifenbark, Scott M; Gary Thomas; >>> >bitbake- devel@lists.openembedded.org >>> >Subject: Re: [bitbake-devel] [PATCH v3] fetch2: Add >>> >BB_ALLOWED_NETWORKS support >>> > >>> >* Paul Eggleton [150616 04:40]: >>> >> On Monday 15 June 2015 23:47:29 Bernhard Reutner-Fischer wrote: >>> >> > On June 15, 2015 4:03:11 PM GMT+02:00, "Rifenbark, Scott M" >>> >> wrote: >>> >> > >Hi, >>> >> > > >>> >> > >Here is a first draft of documenting the BB_ALLOWED_NETWORKS >>> >> > >variable in the BitBake User Manual. I re-wrote the original >>> >> > >text to be active voice and applied some different organization >>> >> > >of the facts to help the flow out. Regarding Gary's input >>> >> > >about BB_NO_NETWORK..... I took a half guess at incorporating it. >>> >> > >Please look this new description over and let me know of any >>> >> > >corrections I need >>> >to make. >>> >> > >http://www.yoctoproject.org/docs/1.9/bitbake-user-manual/bitbak >>> >> > >e >>> >> > >-us >>> >> > >er-manua >>> >> > >l.html#var-BB_ALLOWED_NETWORKS. >>> > >>> >Hi, >>> > >>> >The documentation looks correct, however it might be worth noting >>> >that adding the host you'd like to use to PREMIRROR will result in >>> >the source code being fetched from an allowed location and avoid >>> >raising an error when a host that is not allowed is in a SRC_URI >>> >because the fetcher will not attempt to use the SRC_URI host after a >>> >successful fetch from the PREMIRROR. Using BB_ALLOWED_NETWORK in >>> >conjunction with PREMIRROR is where this feature is very useful. >>> >>> Check the link to the variable description out now Liam. Let me know >>> if this >>addition is okay. >> >>This looks good! >> >>Thanks, >>Liam > >Awesome... I will get the commit into the Bitbake repo and then duplicate = the >entry in the YP ref-manual. > >Thanks, >Scott > >> >>> >>> > >>> > >>> >> > Was the v3 fixed / extended to allow for netmasks, btw? >>> >> > Think >>> >> > /etc/hosts >>> >> > foo.example.com 10.0.0.1 >>> >> > bar.example.com 10.0.0.254 >>> >> > baz.example.com ::1 >>> >> > >>> >> > BB_ALLOWED_NETWORKS =3D 10.0.0.0/24 1.1.1.1/31 ::1/127 >>> >> >>> >> I don't believe so. You can see what actually went in here: >>> >> >>> >> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=3D59ce7d02 >>> >> a >>> >> 57e >>> >> 0a642d839ab48677f6ac1886180f >>> >> >>> >> Cheers, >>> >> Paul >>> > >>> > >>> >There isn't netmask support, but you can achieve the same result in >>> >your example above by using BB_ALLOWED_NETWORKS =3D >>"*.example.com" >>> > >>> >Version 2 updated the host matching and added a few more tests. >>> > >>> >Version 3 changed the name from BB_TRUSTED_NETWORKS to >>> >BB_ALLOWED_NETWORKS. >>> > >>> > >>> >Thanks, >>> >Liam R. Howlett >>> > >>> >> >>> >> -- >>> >> >>> >> Paul Eggleton >>> >> Intel Open Source Technology Centre >-- >_______________________________________________ >bitbake-devel mailing list >bitbake-devel@lists.openembedded.org >http://lists.openembedded.org/mailman/listinfo/bitbake-devel