netdev - Re: [PATCH net-next v2 04/10] net: provide a sysctl raw_l3mdev

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: <1cf46bce-8346-c688-45a0-40ea40299cc0@gmail.com>
Date:   Tue, 2 Oct 2018 13:39:23 -0600
From:   David Ahern <dsahern@...il.com>
To:     Mike Manning <mmanning@...tta.att-mail.com>, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 04/10] net: provide a sysctl raw_l3mdev_accept
 for raw socket lookup with VRFs

On 10/1/18 2:43 AM, Mike Manning wrote:
> Add a sysctl raw_l3mdev_accept to control raw socket lookup in a manner
> similar to use of tcp_l3mdev_accept for stream and of udp_l3mdev_accept
> for datagram sockets. Have this default to off as this is what users
> expect, given that there is no explicit mechanism to set unmodified
> VRF-unaware application into a default VRF.

It needs to default to on to avoid breaking existing users. With the
raw_l3mdev_accept sysctl set to 0 both 'ping -I <vrf> <addr>' and 'ping
-I <dev> <addr>' fail when they succeed today.