From owner-freebsd-hackers Sat Nov 6 23:31:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 280A614FC4; Sat, 6 Nov 1999 23:31:44 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.153]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id QAA11257; Sun, 7 Nov 1999 16:31:42 +0900 (JST) Message-ID: <38252A5C.2C388485@newsguy.com> Date: Sun, 07 Nov 1999 16:29:32 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Brian Fundakowski Feldman Cc: Warner Losh , David Malone , freebsd-hackers@FreeBSD.org Subject: Re: Procfs' pointers to files. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > > It sounds to me that what you really want are the semantics of a > symbolic link and not the semantics of a hard link. Is it just me, > or does it seem as if the pathname of the executable being stored as > a virtual symlink in procfs as "file" would solve these security > problems? Mmmmm... I like that... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message