Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: VAX/VMS V4.1 - Logical Names
Message-ID: <8923@ucbvax.ARPA>
Date: Tue, 9-Jul-85 20:49:28 EDT
Article-I.D.: ucbvax.8923
Posted: Tue Jul  9 20:49:28 1985
Date-Received: Thu, 11-Jul-85 07:35:50 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 19

From: Richard Garland 


The privileged program that translates the logical name should specify
which table (SYSTEM, JOB, GROUP etc) and which access mode (USER, SUPER,
EXEC) to be used in the translation.  Documentation on SYS$TRNLNM tells
how to do this.  The unprivileged user will (presumably) not be able
to define names in the SYSTEM table so you will be safe.

Another possible loophole to protect is when RMS opens a file using
a logical name.   Say a program reads SYS$SYSTEM:SYSUAF.DAT and
gets the file via the logical name SYSUAF.  RMS can be told to use
only privileged mode logical names in such a case if you set a bit
in one of the control blocks using a USEROPEN (from fortran) or
directly when you do the $OPEN from Macro.  The bit is documented
in the RMS manual which describes all those RMS bits.

					Rg
-------