From owner-freebsd-security  Sun Aug 10 13:14:20 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA11697
          for security-outgoing; Sun, 10 Aug 1997 13:14:20 -0700 (PDT)
Received: from terror.hungry.com (fn@terror.hungry.com [169.131.1.215])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11688
          for <freebsd-security@freebsd.org>; Sun, 10 Aug 1997 13:14:16 -0700 (PDT)
Received: (from fn@localhost)
          by terror.hungry.com (8.8.6/8.8.4)
	  id NAA02862; Sun, 10 Aug 1997 13:14:15 -0700 (PDT)
To: freebsd-security@freebsd.org
Subject: Re: procfs hole
References: <Pine.NEB.3.96.970810052824.3287A-100000@apocalypse.saturn.net>
From: Faried Nawaz <fn@Hungry.COM>
Date: 10 Aug 1997 13:14:15 -0700
In-Reply-To: brian@firehouse.net's message of 10 Aug 1997 03:08:30 -0700
Message-ID: <lwafiphk2w.fsf@terror.hungry.com>
Lines: 10
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-freebsd-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

brian@firehouse.net (Brian Mitchell) writes:

  
  There is a major hole in procfs under FreeBSD 2.2.1 (2.1 is not affected,
  I have not tested 3.x but I believe it to be vulnerable as well) along
  with OpenBSD (not tested by me, but by someone else -- believe it was
  2.1-RELEASE although obsd doesnt mount procfs by default like freebsd
  does).

This doesn't work for me (as-is) on 2.2-STABLE.