HP3000-L Archives

May 1999, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lars Appel <[log in to unmask]>
Reply To:
Lars Appel <[log in to unmask]>
Date:
Sat, 15 May 1999 16:12:42 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
One of the major obstacles of the Posix KILL command seems to be
that the killer process needs to run under the same user ID as the
victim in spe -ahem- target.

I wonder if it would be helpful if someone took some time to create
a little MYKILL program that essentially uses setuid() before kill()
to release that restriction...

Of course, such a utility would need to use PM capability and the
GETPRIVMODE() intrinsic to be able to successfully setuid(), or
AIFCHANGELOGON, if you prefer non-C coding. And thus it should not
only lookup the target process' user ID but also implement some
type of security restriction (unless you would want to enable every
user to send KILL signals to every process on the system).

But with some reasonably careful design it might become useful.

It does not seem to be tied into the OS very closely, so it could
probably be created by any volunteer (preferably in the Open Source
model for peer review of the PM actions, for example). And it might
be implemented without having to wait for CSY to allocate some of
the sparse lab resources.

Don't forget the power of the Freeware / Open Source donation model.

Lars.

(no, do not look at me, I just donated the idea ;-)

ATOM RSS1 RSS2