Unable to establish remote connection to GH via git command

[PeterBowman]

Log in into ASIBOT's onboard CPU and perform any kind of remote request to GitHub, e.g. git pull or git clone. The command hangs, but it prints the following output if the GIT_TRACE and GIT_CURL_VERBOSE environment variables are set (docs):

asibot2@asibot:~/yarp-devices$ GIT_TRACE=1 GIT_CURL_VERBOSE=1 git pull --verbose
trace: exec: 'git-pull' '--verbose'
trace: run_command: 'git-pull' '--verbose'
trace: built-in: git 'rev-parse' '--git-dir'
trace: built-in: git 'rev-parse' '--show-toplevel'
trace: built-in: git 'ls-files' '-u'
trace: built-in: git 'symbolic-ref' '-q' 'HEAD'
trace: built-in: git 'config' '--bool' 'branch.develop.rebase'
trace: built-in: git 'rev-parse' '-q' '--verify' 'HEAD'
trace: built-in: git 'fetch' '-v' '--update-head-ok'
trace: run_command: 'git-remote-https' 'origin' 'https://github.com/roboticslab-uc3m/yarp-devices'
* Couldn't find host github.com in the .netrc file; using defaults
* About to connect() to github.com port 443 (#0)
*   Trying 192.30.253.112... * Connected to github.com (192.30.253.112) port 443 (#0)
* found 141 certificates in /etc/ssl/certs/ca-certificates.crt
* gnutls_handshake() failed: A TLS fatal alert has been received.
* gnutls_handshake() failed: The specified session has been invalidated for some reason.
[...last line gets printed indefinitely...]

This used to work a few months ago.

[PeterBowman]

Per https://support.cloudbees.com/hc/en-us/articles/218154647:

On Thursday, 22nd February 2018 19:00 UTC (11:00 am PST), Github disabled access to their service using weak cryptographic ciphers, after this change, it is not possible to access to GitHub by https using SSLv3, TLSv1, TLSv1.1

Per gnutls-cli -l (gnutls-bin package):

Protocols: SSL3.0, TLS1.0, TLS1.1, TLS1.2

[PeterBowman]

Possibly useful links:

• https://stackoverflow.com/questions/29245292/how-can-i-make-git-tell-curl-to-use-openssl-instead-of-gnutls-without-rebuilding/34645007#34645007
• https://serverfault.com/questions/348815/how-to-change-libcurl-ssl-backend-from-gnutls-to-openssl-on-ubuntu-server
• https://www.gnutls.org/manual/html_node/gnutls_002dcli-Invocation.html
• https://answers.launchpad.net/ubuntu/+source/git/+question/255855
• https://askubuntu.com/questions/186847/error-gnutls-handshake-failed-when-connecting-to-https-servers
• https://stackoverflow.com/questions/13524242/error-gnutls-handshake-failed-git-repository
• https://bugzilla.redhat.com/show_bug.cgi?id=1217477
• https://stackoverflow.com/questions/5794337/libcurl-gnutls-handshake-failed-a-tls-warning-alert-has-been-received

[PeterBowman]

Probably going to throw the old Debian 6.0 through a huge window and move on to a (hopefully) modern SO, see last comments at roboticslab-uc3m/questions-and-answers#20.

[PeterBowman]

Happily marking this as WONTFIX. Per roboticslab-uc3m/questions-and-answers#20, we have developed a Debian 8.0 jessie (Linux kernel 3.16.0) image ready to use. On the next round of hardware tweaks (September?), the internal SD card will be replaced.

PS all ASIBOT OS images are stored in this gdrive folder.