Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Allocating your own terminal
Message-ID: <7879@ucbvax.ARPA>
Date: Thu, 6-Jun-85 18:27:34 EDT
Article-I.D.: ucbvax.7879
Posted: Thu Jun  6 18:27:34 1985
Date-Received: Fri, 7-Jun-85 04:08:45 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 21

From: "Brand Hal"@LLL-MFE.ARPA


   We recently got a software package that attempts to ALLOCATE a terminal
line to do some special I/O.   The ALLOCATE always failed because the
SYSTARTUP.COM file had set all the terminal lines
   SET PROT=(S:R,O,G,W)/DEVICE/OWNER=[1,4] T???:
Thus, it was not surprise that when attempting to ALLOCATE some other terminal,
the code failed.   However, what was a surprise was that you can't even
ALLOCATE your own terminal!   Try it!   Make sure the terminal is set as
shown above, log into an account without SYSPRV, and try ALLOCATE TT: or
even ALLOCATE SYS$OUTPUT, etc.   Using SHOW DEV T???/FULL you will see that
your process "owns" the terminal, by the owner_uic is still [1,4].
   Now, DEC recommends setting the terminal in the manner shown above to stop
"password pirates" (Vol. 2, page DCL-620).   We can't modify the software
package cause we didn't get sources.   So... anyone got any ideas?   I can't
find a way to maintain security and allow this software to run even when it
is using the user's terminal for the special I/O.

						Hal Brand
						BRAND#HAL@LLL-MFE