Path: utzoo!attcan!uunet!husc6!bloom-beacon!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Re: making xload(1) susceptible to kill(1) by the invoker
Message-ID: <19881001135108.4.RWS@KILLINGTON.LCS.MIT.EDU>
Date: 1 Oct 88 13:51:00 GMT
References: <23160@tut.cis.ohio-state.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 20


    Date: 30 Sep 88 21:11:30 GMT
    From: allosaur.cis.ohio-state.edu!bob@ohio-state.arpa  (Bob Sutterfield)

    My rationale was that any application that uses that widget would need
    to be setuid root (or at least setgid kmem), and it would be
    appropriate for that application to setuid back to its invoker, so why
    not do it in the widget?

Because you don't know how many other setuid or setgid functions there
might be in other widgets in the same application, that haven't yet been
executed.

    I
    have repented, and backed that change out of my libXaw, and changed my
    xload thusly instead:

    Is that a more tasteful way of going about it?

Yes.