X From:	HENRY::IN%"spear%afwl-vax.arpa%sri-kl.ARPA%relay.cs.net@rca.com" 17-FEB-1987 19:01# To:	info-vax <info-vax@sri-kl.arpa> 1 Subj:	Re: Password Verification via DECnet kludge   L While we are giving an earlier poster the keyboard lashing of his life (manyN with bad info since $SET TERM/NOECHO, $INQUIRE no longer (as of VMS 4.4? 4.5?)I stores the response in the DCL recall buffer), let me mention yet another I problem or two with his scheme of using a DECnet file access (with access - control string) to verify a user's password.    O 1) It's harder to keep the innards of the verification command procedure secret I since you can still enter 'F$VERIFY(1) at the $INQUIRE prompt and turn on H verify mode. Another reason to use $READ instead - you don't need a $SET NOVERIFY after each one.    I 2) If the user has an account on another system on the DECnet (perhaps he K carries around a MicroVAX-2000 disguised as a lunchbox), he might really be N using the UAF file on a remote machine over which you have no control. He needM only $DEFINE LOCAL_NODE_NAME REMOTE_NODE:: and/or $DEFINE 0 REMOTE_NODE:: and G the file access is rerouted. To fix this, see if F$TRNLNM("0") turns up 
 anything.    Capt Jon L. Spear  AFWL/NTC, KAFB, NM 87117-6008   K Disclaimer: This information is provided for comparison purposes only. Your   actual mileage may be different. ------