netdev - Re: [PATCH 1/3] net: introduce SO

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: <CAJieiUi_Pn8VU=PmYyy-+A5D+G2ynoofhHEgKtTOaOjKd8A48Q@mail.gmail.com>
Date:   Thu, 10 Jan 2019 08:39:27 -0800
From:   Roopa Prabhu <roopa@...ulusnetworks.com>
To:     David Ahern <dsahern@...il.com>
Cc:     David Herrmann <dh.herrmann@...il.com>,
        netdev <netdev@...r.kernel.org>,
        David Miller <davem@...emloft.net>, teg@...m.no
Subject: Re: [PATCH 1/3] net: introduce SO_BINDTOIF sockopt

On Thu, Jan 10, 2019 at 8:38 AM David Ahern <dsahern@...il.com> wrote:
>
> On 1/10/19 7:25 AM, David Herrmann wrote:
> > This introduces a new generic SOL_SOCKET-level socket option called
> > SO_BINDTOIF. It behaves similar to SO_BINDTODEVICE, but takes a network
> > interface index as argument, rather than the network interface name.
>
> SO_BINDTOIF is not very descriptive related to SO_BINDTODEVICE.
>
> SO_BINDTOINDEX, SO_BINDTODEVINDEX or SO_BINDTODEVIDX would be clearer
> about this option versus SO_BINDTODEVICE.
>

+1 , also SO_BINDTOIFINDEX