From owner-freebsd-hackers  Mon Jun 14 23:31:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id A0087153DE
	for <hackers@FreeBSD.ORG>; Mon, 14 Jun 1999 23:31:58 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA02747;
	Mon, 14 Jun 1999 23:33:24 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: Stephen McKay <syssgm@detir.qld.gov.au>
Cc: "Chuck Youse" <cyouse@cybersites.com>, hackers@FreeBSD.ORG,
	"Marc Ramirez" <mrami@gbtb.com>
Subject: Re: symlink question 
In-reply-to: Your message of "Tue, 15 Jun 1999 16:20:36 +1000."
             <199906150620.QAA03507@nymph.detir.qld.gov.au> 
Date: Mon, 14 Jun 1999 23:33:24 -0700
Message-ID: <2743.929428404@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> symlinks have caused me grief (Pyramid OSx) and never joy.  I hope it fails
> yet again to appear in FreeBSD.  Just think of the new security holes for a
> start.

Name one, please.  You can currently point a symlink anyplace you
like; whether the user has permission to *read* or execute the target
of the link, however, is where the genuine system administration takes
over.  How the actual value is derived shouldn't make that much
difference. :)

- Jordan


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