Date: Tue, 8 Jul 1997 22:20:33 +0200 From: Ollivier Robert <roberto@keltia.freenix.fr> To: security@FreeBSD.ORG Subject: Re: Security Model/Target for FreeBSD or 4.4? Message-ID: <19970708222033.09272@keltia.freenix.fr> In-Reply-To: <Pine.BSF.3.95q.970708114608.4712B-100000@cyrus.watson.org>; from Robert Watson on Tue, Jul 08, 1997 at 11:58:43AM -0400 References: <9707072348.AA21807@communica.com.au> <Pine.BSF.3.95q.970708114608.4712B-100000@cyrus.watson.org>
index | next in thread | previous in thread | raw e-mail
According to Robert Watson:
> Symlinks don't have the same problem in that they aren't suid (or such),
> but still cannot be deleted by a regular user if created in a sticky-bit
> environment.
Just to clarify, they can now be deleted in CURRENT as of 3/31/97 because
Peter changed them back (yeah!)
peter 97/03/31 04:03:04
Modified: sys/kern vfs_syscalls.c
sys/ufs/ufs ufs_lookup.c ufs_vnops.c
Log:
Treat symlinks as first class citizens with their own uid/gid rather than
as shadows of their containing directory. This should solve the problem
of users not being able to delete their symlinks from /tmp once and for
all.
Symlinks do not have modes though, they are accessable to everything that
can read the directory (as before). They are made to show this fact at
lstat time (they appear as mode 0777 always, since that's how the the
lookup routines in the kernel treat them).
More commits will follow, eg: add a real lchown() syscall and man pages.
--
Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970708222033.09272>