Openembedded Core Discussions
 help / color / mirror / Atom feed
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 20:54:59 -0700	[thread overview]
Message-ID: <4E3A1813.3010906@linux.intel.com> (raw)
In-Reply-To: <0BDD06D6-757A-4F43-B38E-95C857324D14@kernel.crashing.org>

On 08/03/2011 07:56 PM, Kumar Gala wrote:
>
> On Aug 3, 2011, at 5:34 PM, Richard Purdie wrote:
>
>> On Wed, 2011-08-03 at 14:41 -0500, Kumar Gala wrote:
>>> On Aug 3, 2011, at 12:30 PM, Saul Wold wrote:
>>>
>>>> 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!
>>>
>>>  From the thread it sounded as if that was NOT needed.  As nothing
>>> refers to SOCKS5_* we didn't need to add it.  Much like how it doesn't
>>> have SSH_AGENT_PID or SSH_AUTH_SOCK in it.
>>
>> It would be good is someone could confirm it but its in the environment
>> so it likely is needed.
>
> Not sure I follow.  Confirm what?
>
Kumar,

I think Richard wants you to confirm that the SSH_* and SOCKS5_* 
information is not stored in the shared state hash.

Sau!

> - k
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2011-08-04  3: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
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 [this message]
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=4E3A1813.3010906@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