git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: Robert Labrie <robert.labrie@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: SChannel support in Git for Windows
Date: Fri, 15 Jan 2016 18:59:23 +0300	[thread overview]
Message-ID: <20160115185923.1e9fe5220b623625fdbc8041@domain007.com> (raw)
In-Reply-To: <CA+1xWaokgVthDv-up76RP+s+r4pSv5ntmePtDVND+rsKuo+-YA@mail.gmail.com>

On Fri, 15 Jan 2016 10:04:17 -0500
Robert Labrie <robert.labrie@gmail.com> wrote:

[...]
> But it would be more awesome if git just supported schannel on
> Windows. I think cURL does already.

On the one hand, yes -- that would mean tighter integration into the
system which is a good thing from the administrative standpoint.

On the other hand, IIUC, this artifically limits the capabilities of
Git to whatever set of features the schannel implementation in a
particular version of Windows supports.  As a glaring example, support
for TLS 1.1 and TLS 1.2 had never made it into Windows XP (and
supposedly Windows Server 2003, though I may be wrong) despite its
serious entrenchment.  Among other things, that included IE (6, then 7,
then 8).  I do understand the reasons MS validly has for its push on its
customers for upgrades, but ubiquitous OSes nearing their EOL become
prone to lacking of certain features in their stacks.  This well might
be true for Windows 7 some 5 years down the road or so: from where I
sit, it looks like corporate users have zero reasons to upgrade to 10.

Hence ideally there would be some switch which would make libCURL pick
the implementation at runtime.  But I'm afraid it's hardly doable.

  parent reply	other threads:[~2016-01-15 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 15:04 SChannel support in Git for Windows Robert Labrie
2016-01-15 15:06 ` Daniel Stenberg
2016-01-15 15:53 ` Johannes Schindelin
2016-01-15 15:59 ` Konstantin Khomoutov [this message]
2016-01-15 16:11   ` Robert Labrie
2016-01-15 16:47     ` Konstantin Khomoutov

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=20160115185923.1e9fe5220b623625fdbc8041@domain007.com \
    --to=kostix+git@007spb.ru \
    --cc=git@vger.kernel.org \
    --cc=robert.labrie@gmail.com \
    /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 NNTP newsgroup(s).