netdev - Re: [PATCH net-next] ipv6: raw: use IPv4 raw_sendmsg on v4-mapped IPv6 destinations

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: <20180125.120712.993712764993225765.davem@davemloft.net>
Date:   Thu, 25 Jan 2018 12:07:12 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     colona@...sta.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next] ipv6: raw: use IPv4 raw_sendmsg on v4-mapped
 IPv6 destinations

From: Ivan Delalande <colona@...sta.com>
Date: Wed, 24 Jan 2018 17:43:43 -0800

> Make IPv6 SOCK_RAW sockets operate like IPv6 UDP and TCP sockets with
> respect to IPv4 mapped addresses by calling IPv4 raw_sendmsg from
> rawv6_sendmsg to send those messages out.
> 
> Signed-off-by: Travis Brown <travisb@...sta.com>
> Signed-off-by: Ivan Delalande <colona@...sta.com>

For RAW sockets this doesn't make any sense.

Especially when header-include is enabled, one expects the application
to provide an address-family appropriate protocol header in it's
buffer.

Which means ipv4 for ipv4 sockets and ipv6 for ipv6 sockets.

So we should interpret the request as an ipv6 one regardless of
whether the ipv6 destination is ipv4 mapped or not.

Thank you.