From owner-freebsd-security Sun Dec 22 17:52:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA02175 for security-outgoing; Sun, 22 Dec 1996 17:52:04 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA02153 for ; Sun, 22 Dec 1996 17:52:00 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA15361; Mon, 23 Dec 1996 12:21:33 +1030 (CST) From: Michael Smith Message-Id: <199612230151.MAA15361@genesis.atrad.adelaide.edu.au> Subject: Re: seems like procfs bug... In-Reply-To: <199612230047.QAA23206@root.com> from David Greenman at "Dec 22, 96 04:47:02 pm" To: dg@root.com Date: Mon, 23 Dec 1996 12:21:32 +1030 (CST) Cc: vitjok@fasts.com, cschuber@uumail.gov.bc.ca, freebsd-security@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-security@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk David Greenman stands accused of saying: > > 2.1.5 had the 'file' disabled because it didn't work right. We should > probably kill it in 2.2, too, but only because it isn't very useful and > (as you've pointed out) creates a security hole. It should perhaps be replaced with a 'path' item, which contains the path to the executable, so that things like debuggers which might want to access the disk file in conjunction with the memory image can still access this information. > David Greenman -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[