git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Perry Hutchison <perryh@pluto.rain.com>
Cc: ikorot01@gmail.com, git@vger.kernel.org, sunshine@sunshineco.us
Subject: Re: Is support for 10.8 dropped?
Date: Sun, 22 Apr 2018 17:49:03 +0000	[thread overview]
Message-ID: <20180422174902.GJ14631@genre.crustytoothpaste.net> (raw)
In-Reply-To: <5adc355c.rJrv6ddtapM9C9H5%perryh@pluto.rain.com>

[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]

On Sun, Apr 22, 2018 at 12:10:20AM -0700, Perry Hutchison wrote:
> Eric Sunshine <sunshine@sunshineco.us> wrote:
> > On Sun, Apr 22, 2018 at 1:15 AM, Igor Korot <ikorot01@gmail.com> wrote:
> > > MyMac:git-2.17.0 igorkorot$ cat config.mak
> > > NO_GETTEXT=Yes
> > > NO_OPENSSL=Yes
> > >
> > > MyMac:dbhandler igorkorot$ /Users/igorkorot/git-2.17.0/git pull
> > > fatal: unable to access
> > > 'https://github.com/oneeyeman1/dbhandler.git/': error:1407742E:SSL
> > > routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
> > > MyMac:dbhandler igorkorot$
> >
> > Try re-building with OpenSSL enabled (remove NO_OPENSSL from
> > config.make). You may need to build/install OpenSSL yourself to get
> > this to work.
> 
> Explanation:  "tlsv1 alert protocol version" means that the server
> requires its clients to use a newer version of TLS than what was
> used in the local build of git.

I think the issue here is that you're using a crypto library which may
only support TLS 1.0 on 10.8[0].  GitHub requires TLS 1.2 as of
recently.  So this isn't really a problem with Git, so much as it's an
incompatibility between the version of the crypto library you're using
and GitHub.

I expect that due to the PCI DSS rules prohibiting new deployment of TLS
1.0, you'll continue to run into this issue more and more unless you
upgrade to an OS or crypto library that supports TLS 1.2.  As of June
30, TLS 1.0 will be pretty much dead on the Internet.

[0] I surmised this from https://www.ssllabs.com/ssltest/clients.html,
but I don't use macOS so can't speak for certain.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]

  reply	other threads:[~2018-04-22 17:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 19:48 Is support for 10.8 dropped? Igor Korot
2018-04-05 21:46 ` Eric Sunshine
2018-04-07  2:20   ` Igor Korot
2018-04-07  7:32     ` Eric Sunshine
2018-04-08 21:10       ` Igor Korot
2018-04-08 22:37         ` Igor Korot
2018-04-08 23:23           ` Eric Sunshine
     [not found]             ` <CA+FnnTwvnA90nDARKW9r7p5iraoOGTvfDJ26n6Udc68bDSUASw@mail.gmail.com>
2018-04-08 23:59               ` Eric Sunshine
2018-04-11  4:28                 ` Igor Korot
2018-04-11  9:44                   ` Eric Sunshine
2018-04-22  5:15                     ` Igor Korot
2018-04-22  5:37                       ` Eric Sunshine
2018-04-22  7:10                         ` Perry Hutchison
2018-04-22 17:49                           ` brian m. carlson [this message]
2018-04-23 16:39                             ` Igor Korot
2018-04-23 16:31                         ` Igor Korot
2018-04-23 16:53                           ` Eric Sunshine
2018-04-23 19:58                             ` Totsten Bögershausen
2018-04-23 21:04                               ` Eric Sunshine
2018-04-23 21:21                                 ` Igor Korot
2018-04-23 23:16                                   ` Perry Hutchison
2018-05-07 15:20                                     ` Igor Korot

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=20180422174902.GJ14631@genre.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=ikorot01@gmail.com \
    --cc=perryh@pluto.rain.com \
    --cc=sunshine@sunshineco.us \
    /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).