From owner-freebsd-security  Fri Jan 21  6: 8:51 2000
Delivered-To: freebsd-security@freebsd.org
Received: from cairo.anu.edu.au (cairo.anu.edu.au [150.203.224.11])
	by hub.freebsd.org (Postfix) with ESMTP id 652D4152EF
	for <freebsd-security@FreeBSD.ORG>; Fri, 21 Jan 2000 06:08:45 -0800 (PST)
	(envelope-from avalon@cairo.anu.edu.au)
Received: (from avalon@localhost)
	by cairo.anu.edu.au (8.9.3/8.9.3) id BAA12379;
	Sat, 22 Jan 2000 01:08:45 +1100 (EST)
From: Darren Reed <avalon@coombs.anu.edu.au>
Message-Id: <200001211408.BAA12379@cairo.anu.edu.au>
Subject: Re: bugtraq posts: stream.c - new FreeBSD exploit?
To: fpscha@via-net-works.net.ar
Date: Sat, 22 Jan 2000 01:08:45 +1100 (Australia/NSW)
Cc: freebsd-security@FreeBSD.ORG
In-Reply-To: <200001211344.KAA01087@ns1.via-net-works.net.ar> from "Fernando Schapachnik" at Jan 21, 2000 10:44:33 AM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In some mail from Fernando Schapachnik, sie said:
> 
> En un mensaje anterior, Darren Reed escribió:
> > 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
> 
> I usually work with ipfw, so I'm a newbie with ipfilter.
> 
> I loaded a 3.3-R with an ipfilter enabled kernel.
> 
> Then ipf -l block -f /file_with_rules
> 
> Suprisingly:
[...]

That's to be expected.  It only lets through `new' connections.
You may (or may not) want to reboot.

Darren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message