From owner-freebsd-bugs Mon Jun 17 22: 3:18 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 20B1737B400; Mon, 17 Jun 2002 22:03:16 -0700 (PDT) Received: (from cjc@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g5I53Gc23978; Mon, 17 Jun 2002 22:03:16 -0700 (PDT) (envelope-from cjc) Date: Mon, 17 Jun 2002 22:03:16 -0700 (PDT) From: Message-Id: <200206180503.g5I53Gc23978@freefall.freebsd.org> To: rneswold@ameritech.net, cjc@FreeBSD.org, freebsd-bugs@FreeBSD.org, cjc@FreeBSD.org Subject: Re: kern/39396: firewall security loophole Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: firewall security loophole State-Changed-From-To: open->analyzed State-Changed-By: cjc State-Changed-When: Mon Jun 17 22:00:11 PDT 2002 State-Changed-Why: Yeah, yeah, this is an ancient and well known security hole. But since securelevel(8) is kinda a joke, no one has bothered to fix it. It's simple enough to get this category of sysctl(8) knobs locked up. Responsible-Changed-From-To: freebsd-bugs->cjc Responsible-Changed-By: cjc Responsible-Changed-When: Mon Jun 17 22:00:11 PDT 2002 Responsible-Changed-Why: I'll take this. http://www.freebsd.org/cgi/query-pr.cgi?pr=39396 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message