Respondants, thank you:
Matt White
Degerness, Mandell
Davis, Alan
Thomas M. Payerle
Dave Massaro
Lucio Chiappetti
Summary:
-Accepted by several people as a method to handle various
situations/processes:
--Have a root account with different shells
--Track root account usage by ordinary users
--Use it on ordinary user accounts to control their machine access
-Observations:
--Valid only in Base security
--It's another account/password to maintain
--The duplicate root account should be after "root" in /etc/passwd so
file/dir listings show the owner as "root"
--May not work in OSF 3.x
--Remote login as root2 will still be refused as it will be recognized
as uid 0
Original question:
> TruGurus,
>
> What would be the implications of adding an account local to one
machine
> ( /etc/passwd ) that has root's uid & gid, a root2 if you will?
> I'm trying to get around a problem of samba's swat not allowing root
> login and login as root2 works. I have root2 at the end of passwd
just
> before the NIS entry.
> Nothing listed with ls is owned by root2, but a find for -user root2
> will get hits on all root owned files. Neither one of these surprise
me,
> but I don't know much about the inner workings of uid related stuff
and
> what else may be affected.
--
Toby Bluhm
tkb_at_mr.marconimed.com
440-483-5323
Received on Fri Nov 03 2000 - 13:50:17 NZDT