From owner-freebsd-security Thu Jul 19 14: 0:15 2001 Delivered-To: freebsd-security@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 01EAD37B401 for ; Thu, 19 Jul 2001 14:00:11 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA09309; Thu, 19 Jul 2001 23:00:07 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Ralph Huntington Cc: "Sergey N. Voronkov" , Nick Maschenko , security@FreeBSD.ORG Subject: Re: Fw: Re: A question about FreeBSD security References: From: Dag-Erling Smorgrav Date: 19 Jul 2001 23:00:06 +0200 In-Reply-To: Message-ID: Lines: 23 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ralph Huntington writes: > My understanding (someone please correct me if I am wrong) is that IPFW > relies on the incoming packets' own headers to infer the established > state, whereas IPF keeps a table of outgoing packets (when told to keep > state) and matches incoming packets to the entries in the table to > determine if they are actually in response to an outgoing packet. Both. It all depends on how you set up your rule set - you can do # ipfw add pass tcp from any to me 22 in setup # ipfw add pass tcp from me 22 to any out tcpflags syn,ack keep-state instead of # ipfw add pass tcp from any to me 22 in setup keep-state The first variant will only store state for incoming connections to which you actually respond, while the second will store state for all incoming connections. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message