git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lars Schneider <larsxschneider@gmail.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git-for-windows@googlegroups.com, git@vger.kernel.org
Subject: Re: [git-for-windows] [ANNOUNCE] Git for Windows 2.14.0
Date: Sun, 6 Aug 2017 13:16:46 +0200	[thread overview]
Message-ID: <978038E7-74E8-4F9F-A3B9-0BAD82C80FFE@gmail.com> (raw)
In-Reply-To: <20170805230001.3232-1-johannes.schindelin@gmx.de>


> On 06 Aug 2017, at 01:00, Johannes Schindelin <johannes.schindelin@gmx.de> wrote:
> 
> Dear Git users,
> 
> It is my pleasure to announce that Git for Windows 2.14.0 is available from:

Thank you :-)


>  * It is now possible to switch between Secure Channel and OpenSSL for
>    Git's HTTPS transport by setting the http.sslBackend config
>    variable to "openssl" or "schannel"; This is now also the method
>    used by the installer (rather than copying libcurl-4.dll files
>    around).

Does anyone have a pros/cons list for this option? AFAIK OpenSSL is still
the default in the GfW installer and I wonder why. My gut feeling would be to 
go with the SSL implementation shipped with the OS. However, I don't have enough 
knowledge of either implementation to make an assessment.

On macOS Git uses the Apple Security Framework instead of OpenSSL by default.

- Lars


  parent reply	other threads:[~2017-08-06 11:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-05 23:00 [ANNOUNCE] Git for Windows 2.14.0 Johannes Schindelin
2017-08-06  8:34 ` [git-for-windows] " Johannes Sixt
2017-08-07 10:02   ` Johannes Schindelin
2017-08-07 17:31     ` Johannes Sixt
2017-08-07 19:35       ` Johannes Schindelin
2017-08-06 11:16 ` Lars Schneider [this message]
2017-08-07  8:21   ` Konstantin Khomoutov
2017-08-07  9:20     ` Johannes Schindelin

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=978038E7-74E8-4F9F-A3B9-0BAD82C80FFE@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).