Path: utzoo!attcan!uunet!munnari!otc!metro!basser!usage!elecvax!spinifex!lambert
From: lambert@spinifex.eecs.unsw.oz (Timothy Lambert)
Newsgroups: comp.sys.apollo
Subject: Re: process protection
Message-ID: <331@spinifex.eecs.unsw.oz>
Date: 9 Dec 88 08:05:08 GMT
References: <8812051341.AA04086@umix.cc.umich.edu>
Organization: EE & CS, Uni N.S.W., Sydney, Australia
Lines: 19



From article <8812051341.AA04086@umix.cc.umich.edu>, by GBOPOLY1@NUSVM.BITNET (fclim):
> 
> problem now is that if a user create a server process via the dm
> cps command, then the next person using that node will be unable to
> sigp or kill it, (processes started thro' cps are immuned to hangups).
> unless he knows the sys_admin or root passwords.
> 
Not true.  You can only kill processes that belong to you.  The cps command
creates a process that runs as user.server, so to kill one of these you have
to say something like "xdmc cps /bin/kill -9 1232".  See the manual entry on
"/etc/server" for more details.

Unfortunately this also means that anyone can kill processes belonging to
the person logged into the display manager if they can crp (or telnet or
rlogin) onto that node.  (just make that a "cpo" above instead of a "cps")

Tim