Path: num2.nntp.dca.giganews.com!number1.nntp.dca.giganews.com!border2.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!npeer.de.kpn-eurorings.net!newsfeed.tpinternet.pl!newsfeed.atman.pl!news.intercom.pl!f124.n480!f127.n480!f112.n480!f200.n2432!f605.n774!f500.n123!f2000.n106!f1.n140!f307.n153!f401.n153!not-for-mail
Newsgroups: fido.unix
Distribution: fido
From: Pascal Schmidt 
Date: Sun, 22 Aug 04 18:29:58 +0200
Subject: This is why FreeBSD...
Message-ID: 
References: 
Organization: sed s/$(echo $HOME | sed 's/[[:punct:]]/\\&/g')/~/
 2432/0
Lines: 15
Xref: number1.nntp.dca.giganews.com fido.unix:74

Hi Angus! :-)

 AM> What rubbish!  So the OWNER of the file is not allowed to give it to 
 AM> someone
 AM> else?  WTF is write permissions for if not to decide who can modify 
 AM> the file,
 AM> such as changing ownership?
Yeah, so then you could create a 5 GB file and chown it to someone, and they'd
be over their disk quota. Or create a setuid shell binary and chown it to
someone else, voila, you now can use their account. Or... there's a couple of
scenarios where allowing normal users to chown is bad.

Ciao
Pascal