> I can't find this anywhere in the documentation CD > that came with this release but will the latest VM:Secure > force users to these above password requirements or do I have > to write a "front end" > script to be legal? There's a file on VM:Secure's 191 disk > called PASSEXIT EXEC which does some of this (pw length and > reuse control) on our current release (2.5A) and I figure > this is the EXEC which will need to be modified to do the new > stuff if it's even possible.
Do it in PASSEXIT rather than front-ending the VMSECURE command. That's what it's for. There are some limitations on what you can do, but it shouldn't be a problem to do what you described -- it's just a REXX exec. Read the directions on making local mods to CA code carefully, though. Caution: make sure you either turn off the CP line editing characters in SYSTEM CONFIG or filter them out in your password exit as invalid password characters. VMSECURE will allow you to set a password containing the line editing characters, which you can't type on the logo screen (and thus can't log in to fix the problem). Ask me sometime how I discovered this. 8-) -- db
