#146 TLS error on git push.

None
open
nobody
git (6) push (1)
2014-10-17
2014-10-16
Micheal Crotty
No
0 up votes | 0 down votes | 0%
6 comments

On pushing to a project repo, I get the following message.

fatal: unable to access 'https://pristinewiki2@opensourceprojects.eu/git/p/pristine/rawwiki/': gnutls_handshake() failed: A TLS packet with unexpected length was received.

Discussion

  • Miguel Ponce de Leon
    Miguel Ponce de Leon
    2014-10-16

    Support from OSP requested on this issue: Have indicated that

    MAC running git version 1.9.3 (works fine)
    Ubuntu 14.04 git version 1.9.1 (get's this TLS error)
    Ubuntu 14.04 version 2.0.0 (get's this TLS error)

     
    Link

  • Rui Ferreira
    Rui Ferreira
    2014-10-16

    That bit of info helps. Any idea on what version of gnutls is being used in those ubuntu machines?

     
    Link

  • Micheal Crotty
    Micheal Crotty
    2014-10-16

    On Ubuntu 14.04: Recompiled git with openssl and it now works.
    git : 1.9.1
    libcurl4: 7.35.0

    Old version was build with:
    git : 1.9.1
    libcurl4: 7.35.0
    libgnutls26: 2.12.23

    Googling seems to indicate that gnutls does not behave well behind a proxy .. was there a change in the setup?

     
    Last edit: Micheal Crotty 2014-10-16
    Link

  • Rui Ferreira
    Rui Ferreira
    2014-10-16

    So it is an issue with gnutls (or libcurl that is using it in git)

    There was no change in setup, besides the proxy comes after the SSL connection handling.

    Can you check if updating libcurl3-gnutls helps fixing the issue?

     
    Link

  • Rui Ferreira
    Rui Ferreira
    2014-10-17

    Some more digging, the bug is reported in Ubuntu 12/14 https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1111882

    I am NOT able to replicate this for Git in my ubuntu machines though, I can only replicate using other apps related to curl/gnutls (e.g. via pycurl).

    I cannot be sure of the following, but there was an update to the Ubuntu libcurl3-gnutls (07-10-2014 here) and some of my colleagues saw this issue recently on other tools (uptrack-upgrade).

     
    Link