Thanks!
I also tried on another machine, that also error.
It looks like a server configuration issue.
I will report to kernel.org later.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnutls26 in Ubuntu.
https://bugs.launchpa
git.kernel.org is configured to only allow TLS with elliptic curve
ciphersuites. Given that gnutls 2.12.x doesn't support elliptic curves,
it cannot connect to that site.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnutls2
I also encountered similar problem when run:
$ git clone -v
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Cloning into 'linux-firmware'...
* Couldn't find host git.kernel.org in the .netrc file; using defaults
* Hostname was NOT found in DNS cache
* Trying 199.204.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnutls28 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnutls26 in Ubuntu.
https://bugs.launchpad
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnutls26 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnutls26 in Ubuntu.
https://bugs.launchpad
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: git (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnutls26 in Ubuntu.
https://bugs.launchpad.net/
There are several issues with TLS connections and the F5 firewall, and
that looks like the case. That firewall terminates a TLS session if the
client hello is between 256 and 512 bytes. If that is the case you can
verify using wireshark.
The solution we adopted in later versions of gnutls is to ad
@xnox I followed your procedure. Here is the result of the last command. Seems
worse than before..
(utopic-ppc64el)root@ubuntu14ppcel:/tmp# git clone --no-checkout
https://git.fedorahosted.org/git/lvm2.git lvm2
Cloning into 'lvm2'...
fatal: unable to access 'https://git.fedorahosted.org/git/lvm2.
@Erez Hadad can you please try to reproduce this problem in 14.10 Utopic
as well? This will then rule-out whether gnutls 3.x is affected as well
or not.
This can be done from a Trusty 14.04 host like so:
$ mk-sbuild utopic
$ schroot -u root -c utopic-ppc64el
$ apt-get install git
$ cd /tmp; git c
Performing https configuration verfication on git.fedorahosted.org:
On Trusty 14.04 LTS, the default gnutls implementation is old 2.6 based:
$ gnutls-cli -V --print-cert -p 443 git.fedorahosted.org https://bugs.launchpad.net/bugs/1397685
Title:
git gnutls_handshake() failed: A TLS packet with
This will need further investigations / tests as to what is the problem
in the TLS protocol.
It's most likely not git specific but rather TLS implementation specific
- that is one can recompile curl utility against (openssl, gnutls, nss)
to verify with each one that lts access works.
We cannot re
11 matches
Mail list logo