SuSe 10.1 and filePro 5.0.14D4

[Jay R. Ashworth]

On Tue, Jul 18, 2006 at 12:45:33PM -0400, Kenneth Brody wrote:
> The problem is that chown will reset the setuid bit.  This is for
> security reasons, to prevent the setuid bit from applying to the
> new uid, and is probably documented on the chown man page.
> 
> As I recall, a non-root user used to be able to chown a file that
> he owned to another uid.  Ignoring the disk quota implications,
> imagine creating an executable, setting the setuid bit, and then
> chowning it to root.  I believe that this "feature" of chown is
> disallowed nowadays as well.

I'm pretty sure that the "chown clears the SUID bit" fix happened way
back in v7, and hasn't been seen since...  I could check my paper v7
manuals (damn, that was the most fun $75 I ever spent when I was 16;
yes, I'm a geek).

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274

	Fanfic: read enough, and you'll loose your mind.  --me