On Fri, 15 May 2015 16:36, d...@fifthhorseman.net said:
> shouldn't dirmngr know enough to stop trying v6 addresses when v6 isn't
> available?
Adding v6 support at runtime would then require a restart. The real bug
is that dirmngr does not mark the v6 address dead and retry anotyer
server (or th
I verified this to be the case in Wireshark. It's sending both A and
queries for hostname vod.ohai.su (not sure how it got that from
pool.sks-keyservers.net but whatever probably not relevant.) However
it's only GPG that seems to do this. If I ping either of those
hostnames it sends only an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/15/2015 04:20 PM, Daniel Bomar wrote:
> I verified this to be the case in Wireshark. It's sending both A
> and queries for hostname vod.ohai.su (not sure how it got that
> from pool.sks-keyservers.net but whatever probably not relevant.)
Hello,
Am 15.05.2015 um 16:20 schrieb Daniel Bomar:
> If I ping either of those hostnames it sends only an A query
that’s normal, because the ping-command works only for IPv4.
Sincerely,
DaB.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http:
On Fri 2015-05-15 07:43:12 -0400, Werner Koch wrote:
> On Thu, 14 May 2015 04:41, dbdanie...@gmail.com said:
>
>> # gpg --homedir /etc/pacman.d/gnupg --refresh-keys
>> gpg: refreshing 80 keys from hkp://pool.sks-keyservers.net
>> gpg: keyserver refresh failed: Address family not supported by proto
On Thu, 14 May 2015 04:41, dbdanie...@gmail.com said:
> # gpg --homedir /etc/pacman.d/gnupg --refresh-keys
> gpg: refreshing 80 keys from hkp://pool.sks-keyservers.net
> gpg: keyserver refresh failed: Address family not supported by protocol
DNS tells that there are v6 keyservers but your kernel
Looks to be the case. The strange thing is I thought that as well and
tested by passing "ipv6.disable=1" to my distribution kernel and it
still worked. Then I compiled IPV6 support into my custom kernel and
that got it working BUT when I pass "ipv6.disable=1" to my custom
kernel it does NOT work.
Smells like something to do with IPv6
On 14 May 2015 at 12:41, Daniel Bomar wrote:
> I'm using Arch Linux and running a custom kernel (version 4.0.2) and
> I'm unable to use the --refresh-keys function. I know the kernel is
> the problem because when I reboot into the ARCH distribution kernel
>
I'm using Arch Linux and running a custom kernel (version 4.0.2) and
I'm unable to use the --refresh-keys function. I know the kernel is
the problem because when I reboot into the ARCH distribution kernel
(also version 4.0.2) it works fine. It's only my custom kernel that
has this issue. I need
