Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!ted@cgl.ucsf.edu@blia.UUCP
From: ted@cgl.ucsf.edu@blia.UUCP
Newsgroups: mod.computers.vax
Subject: Re: Priveleges: The Answer
Message-ID: <8702181833.AA17545@blia.BLI>
Date: Wed, 18-Feb-87 13:33:59 EST
Article-I.D.: blia.8702181833.AA17545
Posted: Wed Feb 18 13:33:59 1987
Date-Received: Sat, 21-Feb-87 01:34:11 EST
References: <12278831839.8.STEINBERGER@SRI-KL.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27
Approved: info-vax@sri-kl.arpa
Summary: $SETPRV condition codes

In article <12278831839.8.STEINBERGER@SRI-KL.ARPA>, STEINBERGER@SRI-KL.ARPA (Richard Steinberger) writes:
> 
> The Answer to my previous querry is:  The entire image, and not just a
> subroutine, must be installed with the desired priveleges.  Apparently
> this is for security purposes - prevents users from linking to subs
> with known privs and the interrupting the program while maintaining the
> privileges.  I suppose I can live with this.

The other question was why the subroutine that did the $SETPRV didn't detect
the error when it couldn't set the requested privilege. The answer is that
the condition code returned in that case is SS$_NOTALLPRIV which has a
severity value of 1 (success) just like SS$_NORMAL. Thus, the test of
<.not. return-code> was false even though the return code wasn't SS$_NORMAL.
For this, the correct test would be <return-code .neq. SS$_NORMAL>.

===============================================================================
            Ted Marshall
            Britton Lee, Inc.
p-mail:     14600 Winchester Blvd, Los Gatos, Ca 95030
voice:      (408)378-7000
uucp:       ...!ucbvax!mtxinu!blia!ted
ARPA:       mtxinu!blia!ted@Berkeley.EDU
disclaimer: These opinions are my own and may not reflect those of my employer;
            I leave them alone and they leave me alone.
fortune for today:
A door is what a dog is perpetually on the wrong side of.
		-- Ogden Nash