Date: Tue, 27 Feb 1996 20:49:37 -0800 (PST) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: davidg@Root.COM Cc: bde@zeta.org.au, msmith@comtch.iea.com, nlawson@kdat.csc.calpoly.edu, security@freebsd.org Subject: Re: Suspicious symlinks in /tmp Message-ID: <199602280449.UAA16688@GndRsh.aac.dev.com> In-Reply-To: <199602271646.IAA07339@Root.COM> from "David Greenman" at Feb 27, 96 08:46:14 am
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. I wish we would have done this last time this discussion came up, I think it is way past due. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602280449.UAA16688>