netdev - Re: [[NET-NEXT]] Added dump function to recognise rpl extension header option(63)

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] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 4 May 2017 14:51:01 +0200
From:   Stefan Schmidt <stefan@....samsung.com>
To:     Florian Westphal <fw@...len.de>
Cc:     Stefan Schmidt <stefan@....samsung.com>,
        Andreas Bardoutsos <bardoutsos@...d.upatras.gr>,
        netdev <netdev@...r.kernel.org>,
        Michael Richardson <mcr@...delman.ca>,
        "linux-wpan@...r.kernel.org" <linux-wpan@...r.kernel.org>
Subject: Re: [[NET-NEXT]] Added dump function to recognise rpl extension
 header option(63)

Hello.

On Thu, 2017-05-04 at 14:33, Florian Westphal wrote:
> Stefan Schmidt <stefan@....samsung.com> wrote:
> > ipv6: ext_header: add function to handle RPL option 0x63
> 
> But its not handled, is it?

Its not handled in the kernel. The RPL daemon would run in userspace in this
case.

>From my understanding unstrung (or any other RPL implementation) needs this
packet. Right now the kernel silently drops it. Michael would know best
about the details here and if we need some more logic in the kernel itself.
Maybe just some sanity checking of the TLV.

> The kernel tosses it because the RPL option/RFC says so
> ('nodes that do not understand this option on a received
>  packet MUST discard the packet.').

What we might need is a way to let the kernel know we have a RPL running with
support for this option. Would that meet your concern?

regards
Stefan Schmidt