*BSD News Article 82697


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news-peer.gsl.net!news.gsl.net!news-dc.gsl.net!news.gsl.net!news.sprintlink.co.za!panacea.insight.co.za!tony
From: tony@panacea.insight.co.za (Tony Harverson)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Why chown(2) is privileged?
Date: 12 Nov 1996 08:03:56 GMT
Organization: Insight Technologies
Lines: 19
Message-ID: <847786081.259851@panacea.insight.co.za>
References: <CANDY.96Oct24222129@xxx.fct.kgc.co.jp> <w7iv7cjv2t.fsf@mud.imperium.net>
NNTP-Posting-Host: panacea.insight.co.za
X-Newsreader: TIN [version 1.2 PL2]

Mark Lehrer (edge@mud.imperium.net) wrote:
: candy@fct.kgc.co.jp (Toshihiro Kanda) writes:

: >    Hello.  Chown(2) fails if non super-user try to change the owner
: > uid of his/her files.  Why does BSD disallow non super-user to
: > transfer ownership of files to the others?

: Ok, i figured it out - in order for non-root users to use this
: command, this would have to be a setuid root program... so it
: is probably not worth the security risk; especially with a
: program like chown!!

chmod 4777 my_copy_of_csh
chown root my_copy_of_csh 

Useful ne ?

T :>