Re: [ProgSoc] a question and update

[Matt <matt@nospam.progsoc.uts.edu.au>]

On Sun, Jan 20, 2002 at 08:54:57PM +1100, marauder@nospam.marauder.tm wrote:
> On Sun, Jan 20, 2002 at 05:06:49PM +1100, Matt wrote:
>> On Sat, Jan 19, 2002 at 11:50:50PM +1100, marauder@nospam.marauder.tm wrote:
>>> On Sat, Jan 19, 2002 at 05:37:42PM +1000, esydav@nospam.tig.com.au wrote:
>>>> Secondly a problem that i surehas a blatently obvious solution that 
>>>> i have just missed.  I cannot manage to change the owner of some 
>>>> files to nobody using chown, i need to do this so i can use the 
>>>> working uplink fuction.  It doesn't seam to work, is this not possible 
>>>> because of security ?  

>>> Only the superuser can chown, on any system.  But explain more fully
>>> what you're trying to do, because there's sure to be some other way.


>> not true, on BSD style systems anyone can chown(), meaning you can
>> give files away. not true on sysv. not sure what posix/sus symatics
>> are though.

> On my BSD-style system only the superuser can.  The man page claims
> that this is POSIX.1 compliant.

whoops had the the wrong way around. sysv allows it. POSIX.1 allows
either form of operation, depending on the values
_POSIX_CHOWN_RESTRICTED. FIPS 151-1 (a US govt standard issued by
NIST) requires _POSIX_CHOWN_RESTRICTED.

with svr4 this functionality is a configuration option, while 4.3+BSD
always enforces the chown restriction.

Advanced programming in the UNIX environment; W. Richard Stevens..

	matt
-
You are subscribed to the progsoc mailing list. To unsubscribe, send a
message containing "unsubscribe" to progsoc-request@nospam.progsoc.uts.edu.au.
If you are having trouble, ask owner-progsoc@nospam.progsoc.uts.edu.au for help.