[mod.computers.vax] Locking up Command Procedures

JOHNC%CAD2.DECnet@GE-CRD.ARPA.UUCP (02/18/87)

Subject: Re: Password Verification via DECnet kludge

>> 1) It's harder to keep the innards of the verification command procedure
>> secret since you can still enter 'F$VERIFY(1) at the $INQUIRE prompt and
>> turn on verify mode. Another reason to use $READ instead - you don't need a
>> $SET NOVERIFY after each one. 

That is a really grand trick - very startling to see it the first time,
particularly when a user shows it to you!  Note though that VERIFY does
no good without read access to the command procedure.  If you make all 
public command procedures Execute access only then the F$VER trick doesn't
work.

-------------------------------------------------------------------------

"Under capitalism man exploits man,           		John Child
 while under communism it's the        			GE Aircraft Engines
 other way around"					Lynn MA