netdev - Re: [net-next PATCH 14/16] iptables socket match

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]

Date:	Fri, 3 Oct 2008 10:04:23 -0400 (EDT)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Patrick McHardy <kaber@...sh.net>
cc:	KOVACS Krisztian <hidden@....bme.hu>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	netfilter-devel@...r.kernel.org
Subject: Re: [net-next PATCH 14/16] iptables socket match


On Thursday 2008-10-02 05:26, Patrick McHardy wrote:

> KOVACS Krisztian wrote:
>> Add iptables 'socket' match, which matches packets for which a TCP/UDP
>> socket lookup succeeds.
>
> It seems sufficiently different from what xt_owner does to justify a separate
> module.

I am with you on that. However, I would have had liked — already last year —
to have xt_owner revision 1 be called socket, because it is much more than just
ownage that xt_owner currently plays with, and because it could have saved now
running around with yet another module.
Well, xt_socket at last! ;-)
--
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