How to disable SPAWN in MAIL> in a restricted (not captive) user account

How to disable SPAWN in MAIL> in a restricted (not captive) user account

Post by Frits A.M. Storm » Sat, 16 Oct 1999 04:00:00



OSversion: Alpha OpenVMS V7.1-2
Have searched in the FAQ for this (I know this question has risen in the
past) but have not found it.
In the past I always used the captive flag, but due to limitations in the
application "Restricted" is the best I can do.
thanks in advance !
Frits A.M. Storms
 
 
 

How to disable SPAWN in MAIL> in a restricted (not captive) user account

Post by Jack Fortun » Sat, 16 Oct 1999 04:00:00



> OSversion: Alpha OpenVMS V7.1-2
> Have searched in the FAQ for this (I know this question has risen in the
> past) but have not found it.
> In the past I always used the captive flag, but due to limitations in the
> application "Restricted" is the best I can do.
> thanks in advance !
> Frits A.M. Storms

This is how we currently accomplish this at our site:

$       ON CONTROL_Y THEN GOTO BYE
$       ON ERROR THEN GOTO BYE
$       SET DEFAULT SYS$LOGIN
$       SET PROCESS/PRIVILEGE=NOTMPMBX
$       DEFINE/USER SYS$INPUT SYS$COMMAND
$       MAIL
$       SET PROCESS/PRIVILEGE=TMPMBX
$BYE:
$       EXIT 1

Jack Fortune
Tower Group International, Inc.
Atlanta, Georgia USA

 
 
 

How to disable SPAWN in MAIL> in a restricted (not captive) user account

Post by Larry Kilgall » Sat, 16 Oct 1999 04:00:00



Quote:> In the past I always used the captive flag, but due to limitations in the
> application "Restricted" is the best I can do.

Have you tried setting their quotas to prevent subprocesses ?

"Restricted" merely means "Login Command Procedures are mandatory",
so it seems an improbably substitute for "Captive".

Larry Kilgallen

 
 
 

How to disable SPAWN in MAIL> in a restricted (not captive) user account

Post by Pat Rank » Mon, 18 Oct 1999 04:00:00






[...]
>> $       SET PROCESS/PRIVILEGE=NOTMPMBX
>> $       DEFINE/USER SYS$INPUT SYS$COMMAND
>> $       MAIL
>> $       SET PROCESS/PRIVILEGE=TMPMBX
[...]

> This also blocks the use of an editor which makes it VERY user unfriendly...

     It only blocks using an editor in a spawned subprocess,
which is probably a very good thing if you're trying to block
spawning out of mail since editors generally have a spawn
capability too.  But disabling TMPMBX privilege does not block
using CALLABLE_TPU (or CALLABLE_anthing_else for that matter)
as your editor, and it does prevent using EVE's SPAWN command
while editing your mail message.


 
 
 

How to disable SPAWN in MAIL> in a restricted (not captive) user account

Post by Frits A.M. Storm » Tue, 19 Oct 1999 04:00:00







> [...]
> >> $       SET PROCESS/PRIVILEGE=NOTMPMBX
> >> $       DEFINE/USER SYS$INPUT SYS$COMMAND
> >> $       MAIL
> >> $       SET PROCESS/PRIVILEGE=TMPMBX
> [...]

> > This also blocks the use of an editor which makes it VERY user
unfriendly...

>      It only blocks using an editor in a spawned subprocess,

It seems using an editor from mail ALWAYS creates a subprocess:
MAIL> SEND/EDIT
To:            SYSTEM
Subj:        Test editor in MAIL in main process
%MAIL-E-EDITPROC, error creating or executing editor subprocess
-SYSTEM-F-NOPRIV, insufficient privilege or object protection violation

Quote:> which is probably a very good thing if you're trying to block
> spawning out of mail since editors generally have a spawn
> capability too.

I meant to supply a special application editor which does not support SPAWN
Using EVE would inevitably lead to a next question "How to disable SPAWN in
TPU ...."

>But disabling TMPMBX privilege does not block
> using CALLABLE_TPU (or CALLABLE_anthing_else for that matter)
> as your editor, and it does prevent using EVE's SPAWN command
> while editing your mail message.




 
 
 

How to disable SPAWN in MAIL> in a restricted (not captive) user account

Post by Arthur E. Ragost » Tue, 19 Oct 1999 04:00:00



> Alas, the account needs spawns in other sections...

Set the process count to 2.  SPAWN a dummy subprocess before calling
MAIL.  Kill the subprocess after MAIL exits.
 
 
 

How to disable SPAWN in MAIL> in a restricted (not captive) user account

Post by Richard D. Piccar » Wed, 20 Oct 1999 04:00:00


The Open VMS Users Manual, on-line at

        http://www.veryComputer.com/:8000/72final/6489/6489pro_012.html

includes the following:

=======
6.12.7 Overriding Your Selected Editor

If you wish to temporarily override your selected editor, you can define
MAIL$EDIT to be the string "CALLABLE_" with the desired editor
name appended. For example, to use callable EDT rather than callable EVE, you
can type the following command:

 $ DEFINE MAIL$EDIT CALLABLE_EDT
=======

I have not done the experiment, but I would think that the callable_* editing
is done without spawning.  If you have disabled, or used up all your allowed
subprocesses, then you wouldn't be able to spawn out of the called editor.

Neither the VMS nor the MAIL on-line help files included any discussion that I
could find of the possible definitions of MAIL$EDIT and what they would do.

                                        RDP








> > [...]
> > >> $       SET PROCESS/PRIVILEGE=NOTMPMBX
> > >> $       DEFINE/USER SYS$INPUT SYS$COMMAND
> > >> $       MAIL
> > >> $       SET PROCESS/PRIVILEGE=TMPMBX
> > [...]

> > > This also blocks the use of an editor which makes it VERY user
> unfriendly...

> >      It only blocks using an editor in a spawned subprocess,

> It seems using an editor from mail ALWAYS creates a subprocess:
> MAIL> SEND/EDIT
> To:            SYSTEM
> Subj:        Test editor in MAIL in main process
> %MAIL-E-EDITPROC, error creating or executing editor subprocess
> -SYSTEM-F-NOPRIV, insufficient privilege or object protection violation

> > which is probably a very good thing if you're trying to block
> > spawning out of mail since editors generally have a spawn
> > capability too.

> I meant to supply a special application editor which does not support SPAWN
> Using EVE would inevitably lead to a next question "How to disable SPAWN in
> TPU ...."

> >But disabling TMPMBX privilege does not block
> > using CALLABLE_TPU (or CALLABLE_anthing_else for that matter)
> > as your editor, and it does prevent using EVE's SPAWN command
> > while editing your mail message.




--
==================================================================
* Piccard                           Academic Technology Manager

http://www.veryComputer.com/~piccard/                Ohio University
 
 
 

How to disable SPAWN in MAIL> in a restricted (not captive) user account

Post by Frits A.M. Storm » Wed, 20 Oct 1999 04:00:00





zero?

> > Alas, the account needs spawns in other sections...

> Set the process count to 2.  SPAWN a dummy subprocess before calling
> MAIL.  Kill the subprocess after MAIL exits.

Thanks for your reaction.
Perhaps you missed my reply that a subprocess is needed for the use of an
editor ?
--Frits Storms
 
 
 

How to disable SPAWN in MAIL> in a restricted (not captive) user account

Post by Pat Rank » Thu, 21 Oct 1999 04:00:00




Quote:> Perhaps you missed my reply that a subprocess is needed for the use of an
> editor ?

     Using a callable editor from within MAIL does not require
any subprocess.


 
 
 

1. Disable spawn from Mail>

How do I disable the ability to spawn from the VMS Mail process. We are
running OpenVMS 6.2 (not sure what eco ver. ... Y2K fix installed).

What privs are responsible for spawning processes? Is there a way to control
the number of subprocesses?

Any help appreciated.

Jason

2. help with impos2

3. Sounds like the INS needs VMS ...

4. MIDI on Mac -- Newbie has some questions

5. Sounds like INS needs VMS ...

6. ext 4x scsi cdrom- black case

7. Restricted, Captive, Mail & TPU

8. Help! Default Line Width

9. images safe to exclude from INS

10. Restricted, Captive, Mail & TPU

11. images safe to exclude from INS

12. Plug ins for Netscape Navigator 3.03 for OpenVMS

13. How can I disable 'Spawn' function from FTP users?