From owner-freebsd-security Thu Dec 2 14:13:40 1999 Delivered-To: freebsd-security@freebsd.org Received: from eastwood.aldigital.algroup.co.uk (eastwood.aldigital.algroup.co.uk [194.128.162.193]) by hub.freebsd.org (Postfix) with ESMTP id B13B914C0D; Thu, 2 Dec 1999 14:13:34 -0800 (PST) (envelope-from adam@algroup.co.uk) Received: from algroup.co.uk ([192.168.192.2]) by eastwood.aldigital.algroup.co.uk (8.8.8/8.6.12) with ESMTP id WAA01197; Thu, 2 Dec 1999 22:10:14 GMT Message-ID: <3846EE48.558E53A5@algroup.co.uk> Date: Thu, 02 Dec 1999 22:10:16 +0000 From: Adam Laurie X-Mailer: Mozilla 4.7 [en-gb] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "Rodney W. Grimes" Cc: John Baldwin , freebsd-security@FreeBSD.ORG Subject: Re: rc.firewall revisited References: <199912021807.KAA73912@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Rodney W. Grimes" wrote: > > ... > > > > > > # Allow all outgoing UDP > > > $fwcmd add pass udp from any to any > > The comment for this does not match what the rule actually does, > this rule has not ``outgoing'' about it at all.... > > > OK, well this more or less matches my own current iteration, so I have > > no problem with that... > > The above rule set reduces to nothing more than a deny to low ports > and NFS due to missing via/in/out clauses.. Errr... That's all it's meant to be... Bear in mind that the stock rc.firewall has several sections (simple, client, etc.)- this example is appropriate only for one of the sections and is being used as an example just to agree the basis. Once that's done, a proper rule will need to be constructed for each section. cheers, Adam -- Adam Laurie Tel: +44 (181) 742 0755 A.L. Digital Ltd. Fax: +44 (181) 742 5995 Voysey House Barley Mow Passage http://www.aldigital.co.uk London W4 4GB mailto:adam@algroup.co.uk UNITED KINGDOM PGP key on keyservers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message