Re: MOO-Cows Digest V1 #306

• Date: Fri, 19 Jan 1996 16:30:30 PST
• From:
  "David J. Chiodo" <djc@microwave.com>
• cc: sysop@calbbs.com
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-To: <96Jan19.143944pst.162728@mu.parc.xerox.com>

> 
> From: sysop@calbbs.com
> Date: Fri, 19 Jan 1996 12:26:56 -0800
> Subject: kill_task(task_id())
> 
> How can one prevent someone from killing a task that they shouldn't be
> killing?  Denying prog-bits is not an option in many situations, and
> using fork() for every call to a verb that might possible kill the task
> would be inefficient and would probably spam the living heck out of the
> poor server.  Anyone got any ideas?  Pavel, do you think you could
> squeeze some kind of countermeasure against this into the server before
> your time is up?  Perhaps some method of designating a task unkillable by
> verbs down the line?  (kill_task(task_id()); being functionally eqivilant
> to return; when this mode is in effect, except for calls with wizard
> perms)
> 
> TIA,
> 
> Brian
> - ---

How about $server_options.protect_kill_task == 1,

and #0:kill_task() ?

and #0:register_unkillable()

Any task that shouldnt be killed, could call #0:register_unkillable, 
which would save the task_id() in #0.unkillable

#0:kill_task, would check the args[1] against this list, and only kill 
the task if it wasnt there..

Wizards, of course, could still use the builtin to kill any task.

• Re: kill_task(task_id())
• From: Pavel Curtis <pavel@parc.xerox.com>

• Prev: Re: MOO-1.7.9p2 Memory leak in match() still?
• Next: Re: MOO-Cows Digest V1 #306
• Index: MOO-cows
• Thread: MOO-cows