Public bug reported:
On a fresh Ubuntu 14.04 Vagrant box from the official image, I get:
root@libcurl-test:~# apt-key adv --keyserver keys.gnupg.net --recv-keys
EAD883AFExecuting: gpg --ignore-time-conflict --no-options --no-default-keyring
--homedir /tmp/tmp.LdMxFoGqvp --no-auto-check-trustdb --trust-model always
--keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg
--keyserver keys.gnupg.net --recv-keys EAD883AF
gpg: requesting key EAD883AF from hkp server keys.gnupg.net
?: keys.gnupg.net: Host not found
gpgkeys: HTTP fetch error 7: couldn't connect: Success
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
I've attached a minimal Vagrantfile which demonstrates the bug, at least
when run on a host which does not have working ipv6 connectivity.
There is obviously something environment dependent here, in that the
same gpg command works OK when tun on the metal. I think this is to do
with Vagrant giving the virtual machine an ipv6 local address, while
ipv6 routing to the broader net is not available.
root@libcurl-test:~# ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
link/ether 08:00:27:81:50:54 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:fe81:5054/64 scope link
valid_lft forever preferred_lft forever
I suspect this may be the same bug as #1205185, and/or
https://bugzilla.redhat.com/show_bug.cgi?id=548269, though the age of
those makes me wonder if this has been coming and going.
A bunch of ipv6 related bugs have been fixed in libcurl since 7.35.0
which is in Ubuntu 14.04. I suspect the particular bug involved here is
http://sourceforge.net/p/curl/bugs/1451/ , so the problem can presumably
be solved by backporting that fix, or the whole of a later version of
libcurl.
While others don't seem to have tracked this back to libcurl and the
packaging thereof, a LOT of people are reporting this bug pointing at
other projectsr. e.g. google "keys.gnupg.net: Host not found", though
of course libcurl is much more widely used than just that keyserver.
** Affects: curl (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Minimal demonstration of the fault with vagrant."
https://bugs.launchpad.net/bugs/1457192/+attachment/4401215/+files/Vagrantfile
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1457192
Title:
libcurl3 tries to use ipv6 when it's not available
Status in curl package in Ubuntu:
New
Bug description:
On a fresh Ubuntu 14.04 Vagrant box from the official image, I get:
root@libcurl-test:~# apt-key adv --keyserver keys.gnupg.net --recv-keys
EAD883AFExecuting: gpg --ignore-time-conflict --no-options --no-default-keyring
--homedir /tmp/tmp.LdMxFoGqvp --no-auto-check-trustdb --trust-model always
--keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg
--keyserver keys.gnupg.net --recv-keys EAD883AF
gpg: requesting key EAD883AF from hkp server keys.gnupg.net
?: keys.gnupg.net: Host not found
gpgkeys: HTTP fetch error 7: couldn't connect: Success
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
I've attached a minimal Vagrantfile which demonstrates the bug, at
least when run on a host which does not have working ipv6
connectivity.
There is obviously something environment dependent here, in that the
same gpg command works OK when tun on the metal. I think this is to
do with Vagrant giving the virtual machine an ipv6 local address,
while ipv6 routing to the broader net is not available.
root@libcurl-test:~# ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 08:00:27:81:50:54 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:fe81:5054/64 scope link
valid_lft forever preferred_lft forever
I suspect this may be the same bug as #1205185, and/or
https://bugzilla.redhat.com/show_bug.cgi?id=548269, though the age of
those makes me wonder if this has been coming and going.
A bunch of ipv6 related bugs have been fixed in libcurl since 7.35.0
which is in Ubuntu 14.04. I suspect the particular bug involved here
is http://sourceforge.net/p/curl/bugs/1451/ , so the problem can
presumably be solved by backporting that fix, or the whole of a later
version of libcurl.
While others don't seem to have tracked this back to libcurl and the
packaging thereof, a LOT of people are reporting this bug pointing at
other projectsr. e.g. google "keys.gnupg.net: Host not found", though
of course libcurl is much more widely used than just that keyserver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1457192/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
