Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: RE: privileges and spawning....
Message-ID: <6143@ucbvax.ARPA>
Date: Wed, 10-Apr-85 22:40:31 EST
Article-I.D.: ucbvax.6143
Posted: Wed Apr 10 22:40:31 1985
Date-Received: Thu, 11-Apr-85 07:29:10 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 30

From: (Stephen Tihor) <TIHOR@NYU-CMCL1.ARPA>

My install priv image code seems under V4 without problem.

They all follow a general rule which I developed from observing the system's
behavior that at the time of a SPAWN the Images CURRENT PRIVs become
the Subprocess's AUTHORIZED PRIVs, while the subprocess's CURRENT Process
PRIVs seem ~=~ the spawning processes CURRENT Process PRIVs.
Thus if I wished a command procedure to run with privs I would wrap it with
an installed image with the appropriate priv and start the command procedure
with a SET PROCESS/PRIV command to turn on the appropriate privs.

Example:						PrivTest.for
	Program PrivTest
	call exit ( LIB$SPAWN('@SAFEPLACE:PrivTestC') )
	end
							PrivTestC.com
	$ Set NoON
	$ Show Process/Priv
	$ Set Process/Priv=all
	$ Show Process/Priv

Compile, link, and install the program with the desired priv.  Run it.
Examine the output.

 \\   Stephen Tihor / CIMS / NYU / 251 Mercer Street  / New York, NY 10012  //
((  DEC Enet: RHEA::DECWRL::"""TIHOR@NYU-CMCL1.ARPA"""  NYUnet: TIHOR.CMCL1  ))
 // ARPAnet: Tihor@NYU-CMCL1   UUCPnet address: ...!ihnp4!cmcl2!cmcl1!tihor \\

-------