Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!apollo!apollo.hp.com!pato
From: pato@apollo.HP.COM (Joe Pato)
Newsgroups: comp.sys.apollo
Subject: Re: Unable to update /etc/passwd or registry. Not owner
Message-ID: <508085fb.20b6d@apollo.HP.COM>
Date: 21 Mar 91 19:43:00 GMT
References: <rtb.668960287@cernapo.cern.ch> <738@bcstec.boeing.com> <HANCHE.91Mar20170827@hufsa.imf.unit.no>
Sender: root@apollo.HP.COM
Reply-To: pato@apollo.HP.COM (Joe Pato)
Organization: Hewlett-Packard Apollo Division - Chelmsford, MA
Lines: 29

In article <HANCHE.91Mar20170827@hufsa.imf.unit.no>, hanche@imf.unit.no
(Harald Hanche-Olsen) writes:
|> In article <738@bcstec.boeing.com> randall@bcstec.boeing.com (Michael
Randall) writes:
|> 
|>    There is one thing you haven't mentioned. Did you check to see if you
. . .
|> 
|> All our accounts are owned by root.staff.none, and anybody can change
|> their password, full name, gecos information, and shell.  JLRU.
|> 
|> - Harald Hanche-Olsen <hanche@imf.unit.no>
|>   Division of Mathematical Sciences
|>   The Norwegian Institute of Technology
|>   N-7034 Trondheim, NORWAY

Actually, users cannot change their fullname - only the rest of the GECOS
field.  The fullname is actually stored in the person record.  If you
use chfn and try to change this field, you will generally get the 
unauthorized to update error (unless of course you are the administrator
for your own account).

In the OSF DCE version of the registry each object contains a more complete
acl and it is possible to indicate that a user can modify their own fullname.

                    -- Joe Pato
                       Cooperative Computing Division
                       Hewlett-Packard Company
                       pato@apollo.hp.com