What Linux kernel configuration options are required by GPG for --refresh-keys?

[Daniel Bomar]

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.  I'm not sure what the difference is there
where I can disable it in one kernel and have it work but not the
other.

In any case, is this a bug?  I don't see why I should have to have
IPV6 support compiled in when my ISP only gives me an IPV4 address so
I explicitly left it out.

On Thu, May 14, 2015 at 1:33 AM, mark hellewell
<mark.hellewell at gmail.com> wrote:
> Smells like something to do with IPv6
>
> On 14 May 2015 at 12:41, Daniel Bomar <dbdaniel42 at gmail.com> 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
>> (also version 4.0.2) it works fine.  It's only my custom kernel that
>> has this issue.  I need to know what configuration options GPG
>> requires so I can compile in the required features.
>>
>> Here is the error I'm getting.
>>
>> #  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
>>
>> _______________________________________________
>> Gnupg-users mailing list
>> Gnupg-users at gnupg.org
>> http://lists.gnupg.org/mailman/listinfo/gnupg-users