From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] scripts/oe-buildenv-internal: Add SOCKS5_{USER, PASSWD} to BB_ENV_EXTRAWHITE
Date: Thu, 28 Jul 2011 16:55:17 +0100 [thread overview]
Message-ID: <201107281655.17755.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <F026FC6D-A5BD-4F72-B3D2-76463F21779F@kernel.crashing.org>
On Thursday 28 July 2011 16:40:34 Kumar Gala wrote:
> On Jul 28, 2011, at 10:09 AM, Tom Rini wrote:
> > On 07/28/2011 06:10 AM, Kumar Gala wrote:
> >> If a SOCKS5 gateway is needed for a proxy access like git it might also
> >> require authentication to the proxy via a password and username. Adding
> >> SOCKS5_USER & SOCKS5_PASSWD to BB_ENV_EXTRAWHITE allow for automation
> >> of the authentication request to occur when something like a git fetch
> >> is going through the proxy.
> >>
> >> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> >
> > We also need to make sure these variables do NOT make it into the sstate
> > signature, which I think means one more change somewhere else (but I
> > don't recall where off-hand).
>
> Yeah, I didn't find anything obvious while grepping.
I think what you're looking for is BB_HASHBASE_WHITELIST; however IIRC it's
only really necessary if another variable refers to SOCKS5_*, or it is used in
some bit of python/shell script; otherwise it shouldn't appear in the variable
dependencies and thus won't make it's way into the sstate signature.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-07-28 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 13:10 [PATCH] scripts/oe-buildenv-internal: Add SOCKS5_{USER, PASSWD} to BB_ENV_EXTRAWHITE Kumar Gala
2011-07-28 15:09 ` Tom Rini
2011-07-28 15:40 ` Kumar Gala
2011-07-28 15:55 ` Paul Eggleton [this message]
2011-08-03 17:00 ` Kumar Gala
2011-08-03 17:30 ` Saul Wold
2011-08-03 19:41 ` Kumar Gala
2011-08-03 22:34 ` Richard Purdie
2011-08-04 2:56 ` Kumar Gala
2011-08-04 3:54 ` Saul Wold
2011-08-04 4:20 ` Kumar Gala
2011-08-05 16:52 ` Kumar Gala
2011-08-09 13:47 ` Kumar Gala
2011-08-31 5:06 ` Kumar Gala
2011-09-02 14:32 ` Kumar Gala
2011-09-07 17:04 ` Richard Purdie
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=201107281655.17755.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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.