| 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
| ||
|
Message-ID: <55d8a82d-34f6-7b76-8ca6-f8154ce1bca1@ucloud.cn> Date: Fri, 18 Jan 2019 23:41:25 +0800 From: wenxu <wenxu@...oud.cn> To: Pablo Neira Ayuso <pablo@...filter.org> Cc: netfilter-devel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [PATCH v2] netfilter: x_tables: add xt_tunnel match On 2019/1/18 下午10:18, Pablo Neira Ayuso wrote: > On Thu, Jan 10, 2019 at 01:16:08PM +0800, wenxu@...oud.cn wrote: >> From: wenxu <wenxu@...oud.cn> >> >> This patch allows us to match on the tunnel metadata that is available >> of the packet. We can use this to validate if the packet comes from/goes >> to tunnel and the corresponding tunnel ID in the iptables. > One more question, we already have support for this in nft_tunnel.c, > would it be good if we just add the missing pieces to userspace there? > I have some patches here I need to push out for this... > Yes, nftables can do this. I just want the people also can get it through iptables. Anyway It's fine for me.
Powered by blists - more mailing lists