From: Rusty Russell Subject: Re: Security flaw in Stateful filtering ?????? Date: Fri, 07 Jun 2002 09:31:12 +1000 Sender: netfilter-devel-admin@lists.samba.org Message-ID: References: <20020606220914.A14542@groar.org> Cc: Mikkel Christiansen , Mikkel Refsgaard Bech , Torben Vinther Schmidt , Carsten Stiborg , Emmanuel Fleury , netfilter-devel@lists.samba.org Return-path: To: Denis Ducamp In-Reply-To: Your message of "Thu, 06 Jun 2002 22:09:14 +0200." <20020606220914.A14542@groar.org> Errors-To: netfilter-devel-admin@lists.samba.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: netfilter-devel.vger.kernel.org In message <20020606220914.A14542@groar.org> you write: > > iptables -A FORWARD -p tcp -m state --state ESTABLISHED -j ACCEPT > > iptables -A FORWARD -p tcp -m state --state NEW -j ACCEPT > > iptables -A FORWARD -p tcp -j DROP > > The meaning of --state NEW is the number one misunderstanding of netfilter's > dynamic filtering (*). Hi all, I disagree. Consider the original complaint: that --state NEW allowed TCP ACK packets through, which allowed an ack scan. This surprised the observers, who then blocked acks. Of course, you can still use SYNs to scan the network, so they haven't actually won anything here, except that if their firewall reboots, established connections will die. The confusion here comes from the "TCP connection" vs "connection tracking connection" distinction, which is subtle and usually harmless. Hope that helps, Rusty. -- Anyone who quotes me in their sig is an idiot. -- Rusty Russell.