From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] scripts/oe-buildenv-internal: Add SOCKS5_{USER, PASSWD} to BB_ENV_EXTRAWHITE
Date: Wed, 03 Aug 2011 10:30:48 -0700 [thread overview]
Message-ID: <4E3985C8.9070000@linux.intel.com> (raw)
In-Reply-To: <37BC502A-3FEA-4059-85FB-F6A3F401C3F9@kernel.crashing.org>
On 08/03/2011 10:00 AM, Kumar Gala wrote:
>
> On Jul 28, 2011, at 8: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>
>> ---
>> * Fixes issue with a git fetch request failing to get pass a firewall
>>
>> scripts/oe-buildenv-internal | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/scripts/oe-buildenv-internal b/scripts/oe-buildenv-internal
>> index c13fc40..b223292 100755
>> --- a/scripts/oe-buildenv-internal
>> +++ b/scripts/oe-buildenv-internal
>> @@ -55,4 +55,4 @@ unset BITBAKEDIR
>> export BUILDDIR
>> export PATH
>>
>> -export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND"
>> +export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND SOCKS5_PASSWD SOCSK5_USER"
>> --
>> 1.7.3.4
>
> Ping on this patch
>
Kumar,
I think you were asked to modify this patch so that the additinal
SOCKS5_* do not get into sstate, Paul Eggleton provided the
BB_HASHSPACE_WHITELIST info.
Please update this patch
Thanks
Sau!
> - k
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-08-03 17:35 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
2011-08-03 17:00 ` Kumar Gala
2011-08-03 17:30 ` Saul Wold [this message]
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=4E3985C8.9070000@linux.intel.com \
--to=sgw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox