netdev - Re: [PATCH net-next v2] fou: Support binding FoU socket

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: <20190327.133443.2204856008505238916.davem@davemloft.net>
Date:   Wed, 27 Mar 2019 13:34:43 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     kristian.evensen@...il.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2] fou: Support binding FoU socket

From: Kristian Evensen <kristian.evensen@...il.com>
Date: Wed, 27 Mar 2019 11:16:03 +0100

> An FoU socket is currently bound to the wildcard-address. While this
> works fine, there are several use-cases where the use of the
> wildcard-address is not desirable. For example, I use FoU on some
> multi-homed servers and would like to use FoU on only one of the
> interfaces.
> 
> This commit adds support for binding FoU sockets to a given source
> address/interface, as well as connecting the socket to a given
> destination address/port. udp_tunnel already provides the required
> infrastructure, so most of the code added is for exposing and setting
> the different attributes (local address, peer address, etc.).
> 
> The lookups performed when we add, delete or get an FoU-socket has also
> been updated to compare all the attributes a user can set. Since the
> comparison now involves several elements, I have added a separate
> comparison-function instead of open-coding.
 ...
> Signed-off-by: Kristian Evensen <kristian.evensen@...il.com>

Applied.