This was solved upstream last June:
https://dev.gnupg.org/T2990#98557
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849845
Getting 2.2.4 from bionic-proposed into bionic (and backporting for
others) would be a way forward.
** Bug watch added: Debian Bug tracker #849845
https://bugs.debian
Yeah and not helping much if you're one of those few weird people who
are on an IPv6-only network like I am :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625845
Title:
dirmngr doesn't handle IPv
hm, however surely using ipv4/6 pools is a bandaid workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625845
Title:
dirmngr doesn't handle IPv6 properly
To manage notifications about this b
Hm
dirmngr[3638.0]: can't connect to 'squid.internal': no IP address for host
dirmngr[3638.0]: error connecting to 'http://ams3.sks.heypete.com:11371':
Unknown host
dirmngr[3638.0]: marking host 'ams3.sks.heypete.com' as dead
--
You received this bug notification because you are a member of
Figuring out what dirmngr is doing in these cases, can be aided with
cranking up verbosity and logging the output, e.g.:
keyserver hkp://ipv6.pool.sks-keyservers.net
log-file /tmp/tmp.pVKaTIdXs8/.gnupg/dirmngr.log
debug-level guru
Options in $GNUPGHOME/dirmngr.conf. Followed by gpgconf --kill dir
Using [ipv6] address form seems to have regressed upstream. From logs,
it appears that '[' ']' are dropped, and request is attempted to the
2a03 host for [2a03:4000:6:40af::1]. I shall report that upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
