sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] IPv4 vs. IPv6? -- Reconciliation attempt from unauthoriz


From: Phil Pennock
Subject: Re: [Sks-devel] IPv4 vs. IPv6? -- Reconciliation attempt from unauthorized host, but host is authorized
Date: Wed, 27 Nov 2013 16:30:12 -0500

On 2013-11-27 at 12:57 -0500, Daniel Kahn Gillmor wrote:
> i'm running sks 1.1.4 on Debian GNU/Linux, wheezy, amd64 (x86_64)
> platform.
> 
> I see the following situation in the logs of the recon process (this is
> just an example, it seems to happen to all my IPv4 peers):
> 
> 2013-11-27 12:37:17 address for sks-peer.spodhuis.org:11370 changed from [] 
> to [<ADDR_INET [2a02:898:31:0:48:4558:73:6b73]:11370>, <ADDR_INET 
> [94.142.241.93]:11370>]
> 2013-11-27 12:37:17 Reconciliation attempt from unauthorized host <ADDR_INET 
> [::ffff:94.142.241.93]:54518>.  Ignoring

This to me smells of a binding issue, where your v6 sockets are
accepting IPv4 addresses but SKS isn't handling that pattern.

If you're free to do so on this box, you can change the global state
with the `net.ipv6.bindv6only` sysctl; set it to 1 from 0.

If my recollection is accurate, when we were discussing IPv6 in SKS and
I provided my patches and commented upon Kim's (the ones which went in),
the O'Caml runtime did not support accessing the `setsockopt(2)` call
needed to tune this on a per-socket basis.  You're looking for the
`IPV6_V6ONLY` socket option at `IPPROTO_IPV6` level.

google(SKS IPV6_V6ONLY) yields:
  https://lists.nongnu.org/archive/html/sks-devel/2009-03/msg00170.html

So, if I was right in 2009, then with O'Caml 3.11 you can fix this.

-Phil



reply via email to

[Prev in Thread] Current Thread [Next in Thread]