From owner-freebsd-security  Mon Aug 11 10:24:49 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA17567
          for security-outgoing; Mon, 11 Aug 1997 10:24:49 -0700 (PDT)
Received: from super-g.inch.com (super-g.com [207.240.140.161])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA17544
          for <freebsd-security@FreeBSD.ORG>; Mon, 11 Aug 1997 10:24:46 -0700 (PDT)
Received: from localhost (spork@localhost)
	by super-g.inch.com (8.8.5/8.8.5) with SMTP id RAA04343;
	Mon, 11 Aug 1997 17:27:59 -0400 (EDT)
Date: Mon, 11 Aug 1997 17:27:59 -0400 (EDT)
From: spork <spork@super-g.com>
X-Sender: spork@super-g.inch.com
To: Brian Mitchell <brian@firehouse.net>
cc: "Jonathan A. Zdziarski" <jonz@netrail.net>, bugtraq@netspace.org,
        freebsd-security@FreeBSD.ORG
Subject: Re: procfs hole
In-Reply-To: <Pine.BSI.3.95.970810143501.19099B-100000@shell.firehouse.net>
Message-ID: <Pine.BSF.3.96.970811172705.4290A-100000@super-g.inch.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Sun, 10 Aug 1997, Brian Mitchell wrote:

> any setuid program. As noted, the easiest way to avoid the problem is just
> to disable procfs -- nobody really uses it anyways.

Would anyone be willing to give a short explanation of the /proc
filesystem and what the original conception of it accomplished?

Thanks,

Charles