Page MenuHome GnuPG

Missing support for IPv4 may lead to problems.
Open, NormalPublic

Description

See https://lists.gnupg.org/pipermail/gnupg-users/2015-May/053586.html

Although reported for kernels without IPv6 support it is very likely that we
have the same problem on kerneles without legacy IP support. Dirmngr should
detect this case and retry without considering the retry limit in this case.

Details

Version
2.1

Event Timeline

Werner, in https://lists.gnupg.org/pipermail/gnupg-users/2015-May/053617.html you wrote:

The real bug is that dirmngr does not mark the v6 address dead and
retry anotyer server (or the v4 address).

I cannot reproduce this. I pointed dirnmngr to ipv6.pool.sks-keyservers.net and servers
got marked as dead as expected.

May this be related to you fix for

if(ai->family != AF_INET6)

commit 23ea641b ?

I'm not sure, I reverted said change, and it still works for me:

% echo -e "KEYSERVER hkp://ipv6.pool.sks-keyservers.net/\nKS_SEARCH CADE3658\n"

dirmngr/dirmngr 2>&1grep dead

dirmngr[10105.0]: marking host '[2a01:4f8:192:f5::3]' as dead
dirmngr[10105.0]: marking host '[2001:41d0:2:a8b4::10]' as dead
dirmngr[10105.0]: marking host '[2001:67c:2050:1000::3:4]' as dead
dirmngr[10105.0]: marking host 'hufu.ki.iif.hu' as dead