git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lev <leventelist@gmail.com>
To: git@vger.kernel.org
Subject: git https and github
Date: Wed, 25 Apr 2018 02:32:08 +0200	[thread overview]
Message-ID: <20180425023208.5e76e93d@jive> (raw)

Hi list,


I'm struggling with git connecting to Github.

The problem might be SSL/TLS related.

https://githubengineering.com/crypto-removal-notice/

I suspect that my setup still uses tlsv1 or tlsv1.1.

I've tried to explicitly set git to use tlsv1.2 in my .gitconfig file
like this:

[http]
	sslVersion = tlsv1.2

I've tried to re-compile git with OpenSSL and GnuTLS. All give the
same error.

git clone https://github.com/OnionIoT/source.git
Cloning into 'source'...
* Couldn't find host github.com in the .netrc file; using defaults
*   Trying 192.30.253.112...
* TCP_NODELAY set
* Connected to github.com (192.30.253.112) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection:
ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol
version
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
fatal: unable to access 'https://github.com/OnionIoT/source.git/':
error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol
version lev@jive:~/git$ unset GIT_SSL_VERSION lev@jive:~/git$ git clone
https://github.com/OnionIoT/source.git Cloning into 'source'...
* Couldn't find host github.com in the .netrc file; using defaults
*   Trying 192.30.253.112...
* TCP_NODELAY set
* Connected to github.com (192.30.253.112) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection:
ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol
version
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
fatal: unable to access 'https://github.com/OnionIoT/source.git/':
error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version


I can connect to other git servers without any error. This is a debian
stable system with the following components:

	git version 2.11.0

	libcurl 7.52.1

	OpenSSL 1.0.2l


Is there any way to know what is the exact protocol used? Are there any
workaround, fix for this issue?

Any help welcome. Thank you,
Levente

-- 
Levente Kovacs
Senior Electronic Engineer

W: http://levente.logonex.eu

             reply	other threads:[~2018-04-25  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25  0:32 Lev [this message]
2018-04-25 17:44 ` git https and github Beat Bolli

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=20180425023208.5e76e93d@jive \
    --to=leventelist@gmail.com \
    --cc=git@vger.kernel.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.
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).