XBR1YD14@DDATHD21.BITNET (YD14@BR1.THDNET) (01/31/86)
I'm starting a command procedure as a subprocess
PROGRAM PRIVPROC
INTEGER STATUS,SYS$CREPRC
STATUS = SYS$CREPRC( , ! PID
* 'SYS$SYSTEM:LOGINOUT.EXE' , ! Image
* 'WORK:[YD14]TEST.COM' , ! SYS$INPUT
* 'TEST.OUT' , ! SYS$OUTPUT
* 'NL:' , ! SYS$ERROR
* , ! Privilegien
* , ! Quotas
* 'A' , ! Procname
* , ! Prioritaet
* , ! No Uic
* , ! No Term.-Mbx
* ) ! No Sts
WRITE(*,*) STATUS
END
Program PRIVPROC is installed with "/EXEC/PRIV=CMKRNL"
WORK01:<WORK.YD14>.EXE
PRIVPROC;4 Open Prv Xonly
Entry access count = 3
Current / Maximum shared = 1 / 1
Privileges = CMKRNL
The procedure is executed with CMKNRL privilege.
So an unprivileged user can execute a special procedure with CMKRNL.
But with
$ DEFINE /JOB SYS$SYSTEM MYDISK:[MYDIR]
it's possible to redefine SYS$SYSTEM and instead of SYS$SYSTEM:LOGINOUT.EXE
the user activates MYDISK:[MYDIR]LOGINOUT.EXE with CMKRNL.
Under VMS V3.x the problem was solved by specifying _DRA0:[SYSEXE] instead
of SYS$SYSTEM. But since V4.x this doesn't work.
So my question is:
How can I start a special image as an subprocess without the
possibilty of redefining the image name by an logical name?
Reinhard Goeth (Techn. Univ. of Darmstadt)
BITNET: XBR1YD14@DDATHD21
ARPA: XBR1YD14%DDATHD21.BITNET@WISCVM.WISC.EDU