From: "Liam R. Howlett" <Liam.Howlett@windriver.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: Christopher Larson <clarson@kergoth.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] fetch2: Add BB_TRUSTED_NETWORK support
Date: Thu, 16 Apr 2015 10:16:44 -0400 [thread overview]
Message-ID: <20150416141644.GK924@yow-lhowlett-d0.wrs.com> (raw)
In-Reply-To: <BFA1A96F-292A-434A-8510-E19BE343A6B9@gmail.com>
* Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> [150415 15:43]:
> On April 15, 2015 9:37:38 PM GMT+02:00, Christopher Larson <clarson@kergoth.com> wrote:
> >On Tue, Mar 31, 2015 at 11:39 AM, Liam R. Howlett <
> >Liam.Howlett@windriver.com> wrote:
> >
> >> This patch adds support for a new local.conf variable called
> >> BB_TRUSTED_NETWORK. BB_TRUSTED_NETWORK holds a list of hostnames
> >that the
> >> user
> >> trusts as a source for downloading content. If network access is
> >enabled
> >> and
> >> the user has configured trusted hosts, then any hosts that are not in
> >the
> >> list
> >> will cause an error to occur at fetch. Any mirrors and pre-mirrors
> >that
> >> are
> >> not in the list will result in warnings that these locations will not
> >be
> >> used.
> >>
> >> The BB_NO_NETWORK variable still stops all network access.
> >>
> >> Please see the comments in the patch for more details and example
> >usage.
> >>
> >
> >Hmm, looks like this might be useful with an internal mirror coupled
> >with
> >PREMIRRORS, so fetches from the internal host are allowed, but anything
> >missing from there would be immediately caught?
>
Yes, limiting to a local mirror is the main driving force behind this
patch. It will also catch any packages getting pulled in from undesired
locations through dependencies, etc.
> That was my thought, too.
> I would find BB_ALLOWED_NETWORKS more intuitive though.
>
> Cheers,
>
>
I had BB_LIMITED_NETWORKS before, but I think BB_ALLOWED_NETWORKS is
better than both of my suggestions.
Please note that I did send v2 of this patch with minor cleanup & a fix
yesterday, 2015-04-15.
Thanks,
Liam
prev parent reply other threads:[~2015-04-16 14:16 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
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 [this message]
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=20150416141644.GK924@yow-lhowlett-d0.wrs.com \
--to=liam.howlett@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
--cc=rep.dot.nop@gmail.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.