netdev - Re: [PATCH net] ipv6: protect protocols not handling ipv4 from v4 connection/bind attempts

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]

Message-Id: <20140121.165941.1593478240200500821.davem@davemloft.net>
Date:	Tue, 21 Jan 2014 16:59:41 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	hannes@...essinduktion.org
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net] ipv6: protect protocols not handling ipv4 from v4
 connection/bind attempts

From: Hannes Frederic Sowa <hannes@...essinduktion.org>
Date: Mon, 20 Jan 2014 05:16:39 +0100

> Some ipv6 protocols cannot handle ipv4 addresses, so we must not allow
> connecting and binding to them. sendmsg logic does already check msg->name
> for this but must trust already connected sockets which could be set up
> for connection to ipv4 address family.
> 
> Per-socket flag ipv6only is of no use here, as it is under users control
> by setsockopt.
> 
> Signed-off-by: Hannes Frederic Sowa <hannes@...essinduktion.org>

Applied.  Is the plan to add support to at least ping?

Thanks.
--
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