From owner-freebsd-security Mon Jan 24 3:23:26 2000 Delivered-To: freebsd-security@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id ACA5614F68 for ; Mon, 24 Jan 2000 03:23:23 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id MAA21986; Mon, 24 Jan 2000 12:21:12 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Mike Tancsa , freebsd-security@FreeBSD.ORG Subject: Re: Fwd: *BSD procfs vulnerability In-reply-to: Your message of "Mon, 24 Jan 2000 18:34:41 +0800." <20000124103441.D88561C03@overcee.netplex.com.au> Date: Mon, 24 Jan 2000 12:21:12 +0100 Message-ID: <21984.948712872@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20000124103441.D88561C03@overcee.netplex.com.au>, Peter Wemm writes : >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. I belive killall needs a minor fix to use ps(1)... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message