Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!LLL-ICDC.ARPA!oberman
From: oberman@LLL-ICDC.ARPA ("Oberman, Kevin")
Newsgroups: mod.computers.vax
Subject: RE: MAIL Enhancement To Eliminate SPAWN Command
Message-ID: <8703180730.AA01285@ucbvax.Berkeley.EDU>
Date: Tue, 17-Mar-87 12:54:00 EST
Article-I.D.: ucbvax.8703180730.AA01285
Posted: Tue Mar 17 12:54:00 1987
Date-Received: Thu, 19-Mar-87 05:24:39 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "Oberman, Kevin" <oberman@lll-icdc.arpa>
Distribution: world
Organization: The ARPA Internet
Lines: 22
Approved: info-vax@sri-kl.arpa

>I can live with, to a limited degree, this attitude if the user can never
>get to the DCL prompt. Alas this is (was) my beef with the VMS MAIL program,
>and its providing the SPAWN command.
>
>...
>
>I hope that these patches help anyone that is having problems with MAIL and
>inquisitive people with time on their hands.

A very useful patch for VMS V4.2 and V4.3. But the VMS developers fixed
this problem in V4.4. If the CAPTIVE flag is set in the account's UAF record
the SPAWN command is disabled with a message that SPAWNing is not permitted
from CAPTIVE accounts. If you want to keep users out of DCL, their accounts
should ALWAYS be captive.

By the way - TPU also has a SPAWN command. (As does CALLABLE_TPU.)

					R. Kevin Oberman
					LLNL
					arpa: oberman@lll-icdc.arpa
					(415) 42222eahORNORNOt