Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-unix!sri-spam!ames!sdcsvax!ucbvax!CICGJ.RPI.EDU!MADISON
From: MADISON@CICGJ.RPI.EDU.UUCP
Newsgroups: comp.os.vms
Subject: $SETPRV and image privileges
Message-ID: <870917.17953@CICGJ.RPI.EDU>
Date: Thu, 17-Sep-87 19:13:12 EDT
Article-I.D.: CICGJ.870917.17953
Posted: Thu Sep 17 19:13:12 1987
Date-Received: Sun, 20-Sep-87 15:00:11 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 24

>From: umbc3!dave@umd5.umd.edu  (David A Freeman)
>
>Sorry if you've already heard about this. 
>
>
>1: Turning off an installed image's privs with the sys$setprv does not work
>	(Try it from a non-privileged account)

 It's worked all right for my images.  For every image I write and install
 with privs (which usually includes SYSPRV), I include as the first thing:

    STS$VALUE = LIB$GETJPI (JPI$_PROCPRIV,,,PROCESS_PRIVILEGES);
    IF ^ STS$SUCCESS THEN STOP;
    STS$VALUE = SYS$SETPRV ('0'B, 'FFFFFFFFFFFFFFFF'B4,,);
    STS$VALUE = SYS$SETPRV ('1'B, PROCESS_PRIVILEGES,,);

 This code has, for my images, acheived the desired effect of preventing
 the user from defining SYS$OUTPUT to some place he or she doesn't normally
 have access to and actually creating a file there.

 Matt Madison, Systems Programmer
 Center for Interactive Computer Graphics
 Rensselaer Polytechnic Institute
 Troy, New York