From owner-freebsd-security  Mon Jan 24  3: 7:19 2000
Delivered-To: freebsd-security@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id 9870F150E1
	for <freebsd-security@FreeBSD.ORG>; Mon, 24 Jan 2000 03:07:15 -0800 (PST)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id D88561C03; Mon, 24 Jan 2000 18:34:41 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.1.1 10/15/1999
To: Mike Tancsa <mike@sentex.net>
Cc: freebsd-security@FreeBSD.ORG
Subject: Re: Fwd: *BSD procfs vulnerability 
In-Reply-To: Message from Mike Tancsa <mike@sentex.net> 
   of "Sun, 23 Jan 2000 20:35:45 EST." <4.2.2.20000123203515.00a506c0@mail.sentex.net> 
Date: Mon, 24 Jan 2000 18:34:41 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <20000124103441.D88561C03@overcee.netplex.com.au>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Mike Tancsa wrote:
> 
> 
> What are the implications on unmounting procfs ?

Under -current, practically nothing.  Under 3.x, ps(1) won't work right.
I'm not sure about gdb(1), it seems to use ptrace(2) these days.

Cheers,
-Peter



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message