From: Eric Blake <eblake@redhat.com>
To: overseers@sourceware.org
Subject: Re: https access to git repo?
Date: Fri, 02 Nov 2018 14:37:00 -0000 [thread overview]
Message-ID: <32804d18-e9d4-5cd4-fca5-d3d9274ec3b1@redhat.com> (raw)
In-Reply-To: <6b35da7f-91bc-92d2-6ea3-71cbe5d3d768@gmail.com>
Forwarding a message from cygwin-developers:
On 11/2/18 9:32 AM, cyg Simple wrote:
> On 11/2/2018 9:20 AM, Eric Blake wrote:
>> https://cygwin.com/git.html recommends the use of git:// for accessing
>> the cygwin git repo. However, git:// suffers from man-in-the-middle
>> attacks, in comparison to https://. On the other hand, performance of
>> https:// is much worse than git:// UNLESS the git server is running a
>> new enough version of git, such that it advertises
>> application/x-git-upload-pack-advertisement support.
>>
>> Alas, the current sourceware server is running an old version of git:
>>
>> $ wget -S
>> 'http://sourceware.org/git/newlib-cygwin.git/info/refs?service=git-upload-pack'
>> 2>&1 | grep Content-Type
>> Â Content-Type: text/plain; charset=UTF-8
>>
>> Contrast that with other git repos:
>>
>> $ wget -S
>> 'https://repo.or.cz/qemu.git/info/refs?service=git-upload-pack' 2>&1 |
>> grep Content-Type
>> Â Content-Type: application/x-git-upload-pack-advertisement
>>
>> Is there a chance we can get sourceware to upgrade to a newer git
>> server, and then update our recommendations to point people to https://
>> clones instead of insecure git://, and without the current speed penalty
>> that current https:// access through our non-upgraded server provides?
>
> You'll need to ask overseerers@sourceware.org. They may have it on
> there radar already but it doesn't hurt to ask.
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
parent reply other threads:[~2018-11-02 14:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6b35da7f-91bc-92d2-6ea3-71cbe5d3d768@gmail.com>]
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=32804d18-e9d4-5cd4-fca5-d3d9274ec3b1@redhat.com \
--to=eblake@redhat.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).