From: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
"Howlett, Liam (Wind River)" <liam.howlett@windriver.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH v3] fetch2: Add BB_ALLOWED_NETWORKS support
Date: Mon, 15 Jun 2015 13:30:24 +0000 [thread overview]
Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB123798D203305@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <2131793.ifvVUYI7Oy@peggleto-mobl.ger.corp.intel.com>
Liam,
I will take your raw information and create a new variable description in both the BitBake manual and the YP reference manual. I will send out a review link to you when it is ready.
Thanks,
Scott
>-----Original Message-----
>From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
>Sent: Monday, June 15, 2015 6:28 AM
>To: Howlett, Liam (Wind River)
>Cc: Richard Purdie; Rifenbark, Scott M; bitbake-
>devel@lists.openembedded.org
>Subject: Re: [bitbake-devel] [PATCH v3] fetch2: Add
>BB_ALLOWED_NETWORKS support
>
>On Tuesday 12 May 2015 10:28:08 Liam R. Howlett wrote:
>> * Richard Purdie <richard.purdie@linuxfoundation.org> [150512 07:18]:
>> > On Thu, 2015-04-16 at 13:23 -0400, Liam R. Howlett wrote:
>> > > BB_ALLOWED_NETWORKS is a list of hosts that the fetcher will be
>> > > allowed to use when BB_NO_NETWORK is not set.
>> > >
>> > > If BB_NO_NETWORK is set, then networking is still disabled.
>> > >
>> > > If BB_ALLOWED_NETWORKS is not set, the behaviour remains the same
>> > > as today.
>> > >
>> > > If BB_NO_NETWORK is NOT set, and BB_ALLOWED_NETWORKS is
>> > > configured, then only the hosts in the list are usable by the fetcher.
>> > >
>> > > eg:
>> > > BB_ALLOWED_NETWORKS="yoctoproject.org git.gnu.org"
>> > > The fetcher will be able to download from yoctoproject.org,
>> > > git.gnu.org, but not ftp.gnu.org or any other hostname that is not in the
>list.
>> > >
>> > > There is also limited support for wildcards on the beginning of
>> > > the hosts, so BB_ALLOWED_NETWORKS="*.gnu.org" with match
>> > > git.gnu.org and ftp.gnu.org as well as foo.git.gnu.org
>> > >
>> > > Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
>> > > ---
>> > >
>> > > lib/bb/fetch2/__init__.py | 53
>> > > +++++++++++++++++++++++++++++++++++++++++++++++
>lib/bb/tests/fetch.py
>> > > | 37 +++++++++++++++++++++++++++++++++
>> > > 2 files changed, 90 insertions(+)
>> >
>> > I've merged this, however, one of the things we're trying to do is
>> > improve the documentation of bitbake. Would you be able to work with
>> > Scott (cc'd) to ensure this is documented in the manual please?
>> >
>> > Cheers,
>> >
>> > Richard
>>
>> Absolutely, Thanks Richard.
>>
>> Hello Scott,
>>
>> If you don't have anything started, we can work from the text below if
>> you'd like.
>>
>> --------
>>
>> BB_ALLOWED_NETWORKS
>>
>> Specifies a space delimited list of hosts which are allowed to be used
>> by the fetcher to obtain the required source code. This list is only
>> used if BB_NO_NETWORK is not set. Wildcard matching at the beginning
>> of hosts is supported. Mirrors that are not in the list will be
>> skipped and logged in debug. Attempts to access networks that are not
>> in the BB_ALLOWED_NETWORKS will cause a failure.
>>
>> --------
>>
>> Thanks,
>> Liam
>
>Replying to add Scott on CC - I think he has something for review.
>
>Cheers,
>Paul
>
>--
>
>Paul Eggleton
>Intel Open Source Technology Centre
next prev parent reply other threads:[~2015-06-15 13:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 18:39 [PATCH] fetch2: Add BB_TRUSTED_NETWORK support Liam R. Howlett
2015-03-31 18:39 ` Liam R. Howlett
2015-04-15 18:17 ` [PATCH v2] " Liam R. Howlett
2015-04-15 18:17 ` Liam R. Howlett
2015-04-16 17:06 ` [PATCH v3] fetch2: Add BB_ALLOWED_NETWORKS support Liam R. Howlett
2015-04-16 17:23 ` Liam R. Howlett
2015-05-12 11:17 ` Richard Purdie
2015-05-12 14:28 ` Liam R. Howlett
2015-06-15 13:28 ` Paul Eggleton
2015-06-15 13:30 ` Rifenbark, Scott M [this message]
2015-06-15 13:38 ` Gary Thomas
2015-06-15 14:03 ` Rifenbark, Scott M
2015-06-15 21:47 ` Bernhard Reutner-Fischer
2015-06-16 8:40 ` Paul Eggleton
2015-06-16 13:42 ` Liam R. Howlett
2015-06-16 15:25 ` Rifenbark, Scott M
2015-06-16 19:24 ` Liam R. Howlett
2015-06-16 19:25 ` Rifenbark, Scott M
2015-06-16 22:16 ` Rifenbark, Scott M
2015-04-15 19:37 ` [PATCH] fetch2: Add BB_TRUSTED_NETWORK support Christopher Larson
2015-04-15 19:42 ` Bernhard Reutner-Fischer
2015-04-16 14:16 ` Liam R. Howlett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41DEA4B02DBDEF40A0F3B6D0DDB123798D203305@ORSMSX101.amr.corp.intel.com \
--to=scott.m.rifenbark@intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=liam.howlett@windriver.com \
--cc=paul.eggleton@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.