netdev - Re: [PATCH net-next] inet_diag: Add equal-operator for ports

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: <20180102.135423.1243941734307734099.davem@davemloft.net>
Date:   Tue, 02 Jan 2018 13:54:23 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     kristian.evensen@...il.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next] inet_diag: Add equal-operator for ports

From: Kristian Evensen <kristian.evensen@...il.com>
Date: Wed, 27 Dec 2017 18:27:58 +0100

> inet_diag currently provides less/greater than or equal operators for
> comparing ports when filtering sockets. An equal comparison can be
> performed by combining the two existing operators, or a user can for
> example request a port range and then do the final filtering in
> userspace. However, these approaches both have drawbacks. Implementing
> equal using LE/GE causes the size and complexity of a filter to grow
> quickly as the number of ports increase, while it on busy machines would
> be great if the kernel only returns information about relevant sockets.
> 
> This patch introduces source and destination port equal operators.
> INET_DIAG_BC_S_EQ is used to match a source port, INET_DIAG_BC_D_EQ a
> destination port, and usage is the same as for the existing port
> operators.  I.e., the port to match is stored in the no-member of the
> next inet_diag_bc_op-struct in the filter.
> 
> Signed-off-by: Kristian Evensen <kristian.evensen@...il.com>

Applied, thank you.