From owner-freebsd-stable Fri Jan 21 8:55:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jason04.u.washington.edu (jason04.u.washington.edu [140.142.78.5]) by hub.freebsd.org (Postfix) with ESMTP id 5ECE11555C; Fri, 21 Jan 2000 08:55:34 -0800 (PST) (envelope-from kraemer@u.washington.edu) Received: from mead2.u.washington.edu (kraemer@mead2.u.washington.edu [140.142.12.164]) by jason04.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA17764; Fri, 21 Jan 2000 08:55:32 -0800 Received: from localhost (kraemer@localhost) by mead2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA118496; Fri, 21 Jan 2000 08:55:32 -0800 Date: Fri, 21 Jan 2000 08:55:32 -0800 (PST) From: Brian Kraemer To: Darren Reed Cc: freebsd-security@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: bugtraq posts: stream.c - new FreeBSD exploit? In-Reply-To: <200001210421.PAA25285@cairo.anu.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, Darren Reed wrote: > btw, I think the better way to write the 3 rules is: > > block in quick proto tcp from any to any head 100 > pass in quick proto tcp from any to any flags S keep state group 100 > pass in all If I'm not mistaken, this ruleset (and no other rules) will also effectively block any outgoing TCP sessions initiated from this machine. The machine will send a SYN, and then get blocked because the input rules never saw an incoming SYN to start keeping state. I assume a rule that keeps state on the outgoing would fix this? -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message