From owner-freebsd-current Sun Dec 15 11: 3:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50E5537B401; Sun, 15 Dec 2002 11:03:39 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECC0D43ED8; Sun, 15 Dec 2002 11:03:38 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.5) with ESMTP id gBFJ3aOM081741; Sun, 15 Dec 2002 11:03:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.5/Submit) id gBFJ3abr081740; Sun, 15 Dec 2002 11:03:36 -0800 (PST) (envelope-from dillon) Date: Sun, 15 Dec 2002 11:03:36 -0800 (PST) From: Matthew Dillon Message-Id: <200212151903.gBFJ3abr081740@apollo.backplane.com> To: "M. Warner Losh" Cc: sam@errno.com, mux@FreeBSD.ORG, obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ipfw userland breaks again. References: <200212150015.gBF0FlbS066547@apollo.backplane.com> <20021215.111441.05985858.imp@bsdimp.com> <200212151826.gBFIQMpo081407@apollo.backplane.com> <20021215.115657.90648628.imp@bsdimp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :: This is complete BULLSHIT, Warner. : :Your attitude it totally unacceptible. Learn to play well with :others, or get the fuck out of the project. : :I am *NOT* blocking you. I'm telling you you need to get the SO's :sign off to make sure that there isn't a security issue because the :current defaults were set by the so. If you don't like that, then I :suggest that you get over yourself and find someplace else to play. : :Warner This is not a security issue. Why do you think it is? How is 'ipfw unbreak' any different from 'ipfw add 2 allow all from any to any'? (Other then the fact that unbreak is immune from API changes). Have you even bothered to read the patch? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message