Date: Tue, 27 Feb 1996 08:46:14 -0800 From: David Greenman <davidg@Root.COM> To: Bruce Evans <bde@zeta.org.au> Cc: msmith@comtch.iea.com, nlawson@kdat.csc.calpoly.edu, security@FreeBSD.org Subject: Re: Suspicious symlinks in /tmp Message-ID: <199602271646.IAA07339@Root.COM> In-Reply-To: Your message of "Wed, 28 Feb 1996 02:03:09 %2B1100." <199602271503.CAA03513@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
>>However, the bug that I have seen for quite a while and complained about is >>that a symlink is owned by the owner of the file it points to, not by the >>creator of the symlink. That is a bad idea and I really can't see the logic >>behind doing that. > >>Could someone explain this behavior? > >The symlink is owned by the owner of its parent directory. > >I think this is to conform to future POSIX standards. Many other things >involving symlinks changed in 4.4lite. See `man 7 symlink'. NetBSD recently went back to the previous/traditional behavior for symlinks. I think we should too - the "new" model is incompatible with sticky bit directories. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602271646.IAA07339>