From owner-freebsd-security  Sun Aug 10 13:44:39 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA13584
          for security-outgoing; Sun, 10 Aug 1997 13:44:39 -0700 (PDT)
Received: from netrail.net (netrail.net [205.215.10.3])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA13579
          for <freebsd-security@FreeBSD.ORG>; Sun, 10 Aug 1997 13:44:36 -0700 (PDT)
Received: from localhost (jonz@localhost)
	by netrail.net (8.8.6/8.8.6) with SMTP id QAA05995;
	Sun, 10 Aug 1997 16:43:57 GMT
Date: Sun, 10 Aug 1997 16:43:57 +0000 (GMT)
From: "Jonathan A. Zdziarski" <jonz@netrail.net>
To: Brian Mitchell <brian@firehouse.net>
cc: bugtraq@netspace.org, freebsd-security@FreeBSD.ORG
Subject: Re: procfs hole
In-Reply-To: <Pine.NEB.3.96.970810052824.3287A-100000@apocalypse.saturn.net>
Message-ID: <Pine.BSF.3.95q.970810164246.5848A-100000@netrail.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I'm curious.  With this bug in the proc filesystem, is it possible that
there is a similar problem with "memory permissions" - I'm not very
experienced with how memory works in FreeBSD, however I've wondered if
it's possible for the memory to be modified as well in instances like
this.


-------------------------------------------------------------------------
Jonathan A. Zdziarski                                NetRail Incorporated
Server Engineering Manager                    230 Peachtree St. Suite 500
jonz@netrail.net                                        Atlanta, GA 30303
http://www.netrail.net                                    (888) - NETRAIL
-------------------------------------------------------------------------