From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Westphal Subject: Re: [PATCH 4/4] netfilter: xtables: inclusion of xt_SYSRQ Date: Thu, 12 Jul 2012 22:35:41 +0200 Message-ID: <20120712203541.GB9927@breakpoint.cc> References: <1341964350-13809-1-git-send-email-jengelh@inai.de> <1341964350-13809-5-git-send-email-jengelh@inai.de> <20120712154957.GE18793@1984> <20120712202608.GA9927@breakpoint.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Florian Westphal , Pablo Neira Ayuso , netfilter-devel@vger.kernel.org To: Jan Engelhardt Return-path: Received: from Chamillionaire.breakpoint.cc ([80.244.247.6]:49097 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756290Ab2GLUfm (ORCPT ); Thu, 12 Jul 2012 16:35:42 -0400 Content-Disposition: inline In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: Jan Engelhardt wrote: > >Jan Engelhardt wrote: > >> David Miller has stated his opinion already last year, and he's > >> for the Netfilter variant: > >> http://markmail.org/message/d7kpczdbtpcxwli6 > > > >We now have udp encap support also for ipv6, so this could now > >be solved outside of netfilter without impacting the ability to > >filter sysreq packets. > > How does xt_SYSRQ inhibit filtering sysrq packets? Not at all. But the last 'do it outside of netfilter' approaches suffered from that. With encap sockets this should no longer be a problem.