[poky] Introduction and Request for HTTP Git Access

[Darren Hart]

On 11/09/2010 10:06 AM, Denys Dmytriyenko wrote:
> On Tue, Nov 09, 2010 at 11:34:48AM -0600, Ryan D Phillips wrote:
>> On 11/9/2010 11:22 AM, Darren Hart wrote:
>>> On 11/09/2010 09:02 AM, Denys Dmytriyenko wrote:
>>>> On Tue, Nov 09, 2010 at 10:31:37AM -0600, Ryan_D_Phillips at Dell.com wrote:
>>>>> Good Day!
>>>>>
>>>>> My name is Ryan Phillips (irc: rphillips), a former Gentoo Linux
>>>>> Developer,
>>>>> currently a software developer architecting an embedded firmware
>>>>> solution on
>>>>> OE for my employer. With the release of Yocto, we are extremely
>>>>> interested
>>>>> in trying it out and possibly contributing to the project. My cohort
>>>>> working
>>>>> with me is Sean Hudson (irc: darknighte), and is someone who you may see
>>>>> contributions from as well.
>>>>>
>>>>> A major stumbling block we must work around is the restrictive firewall
>>>>> and
>>>>> git checkouts. We have found out the git-http-backend works extremely
>>>>> well,
>>>>> and are requesting this support on git.pokylinux.org. We suspect other
>>>>> people within larger corporations would have a similar problem, and by
>>>>> adding this support would help the community at large.
>>>>
>>>> Ryan,
>>>>
>>>> It's nice to see another Gentooist!
>>>>
>>>> Have you looked at core.gitProxy setting or GIT_PROXY_COMMAND environment
>>>> in
>>>> git-config(1)? People behind strict firewalls been using that for years
>>>> to
>>>> tunnel their git access through proxies. Used together with things like
>>>> netcat, socat or corkscrew work miracles even with HTTP-only proxies!
>>>
>>> It is certainly sub-ideal (but so is git over http), but it should
>>> provide the functionality you need. Please give the above a shot and if
>>> for some reason it is insufficient, please let us know.
>>>
>>
>> I don't understand the comment that git over http is sub-ideal (see github
>> using https for git by default), but the issue we have is the proxy server
>> restricts outbound ports to 80 and 443, and doesn't allow CONNECT.
>
> git-over-http used to be sub-ideal until version 1.6.6 of git, as it only
> provided "dumb" read-only access. Now, with git-http-backend(1) there is a
> "smart" transport available, which can also handle pushing over https...
>
> http://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
> http://progit.org/2010/03/04/smart-http.html

Aha, I didn't realize that. My concern would be how that would tie in 
with the ssh key based user auth we currently use. I'll have to leave 
that to Richard or perhaps someone else that knows the backend setup 
better than I do.


-- 
Darren Hart
Embedded Linux Kernel