lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54FB8358.6040406@baanhofman.nl>
Date:	Sun, 08 Mar 2015 00:01:44 +0100
From:	Wilco Baan Hofman <wilco@...nhofman.nl>
To:	Ben Hutchings <ben@...adent.org.uk>
CC:	netdev@...r.kernel.org
Subject: Re: IPv6 GRE sending to undefined destinations

On 07/03/15 18:51, Ben Hutchings wrote:
>> > With the following patch I am able to make it work, but I'm not sure
>> > about the implications of changing the size of the sll_addr buffer.
> We can't do that as it will break binary compatibility with existing
> applications.  It sounds like there is a need for a new, larger
> structure but I don't know all the compatibility implications of that.
>
I'm not so sure. Existing applications will know the old size, 8 bytes
and will only read and set these 8 bytes.
Newer applications can use 16 bytes. It only messes up when newer
headers are used on an older kernel, not the other way around.

The problem is, with the old size, running multipoint tunnels over IPv6
will not work (at least not without an sll netlink interface overhaul).
The NBMA size and interface seems to work, given that the neighbour list
is updated correctly.

$ ip -6 neigh list
fe80::3 dev gre1 lladdr fc:00:00:00:00:00:00:00:00:00:00:00:00:00:00:03
REACHABLE

I can understand not wanting to break newer userspace/older kernel in
this case, though. Any pointers on how to best approach a clean kernel
interface update to make sll netlink work over IPv6 transport?

-- Wilco
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ