HP3000-L Archives

August 2004, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Walter Murray <[log in to unmask]>
Reply To:
Walter Murray <[log in to unmask]>
Date:
Mon, 2 Aug 2004 17:17:47 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
 "Baker, Mike L." <[log in to unmask]> wrote:
> Does anyone know if VESoft Security/3000 will allow (well, force is a
better word) users to be required to use strong passwords (*&^%$#@
characters and such) ??

I like $VEPASS-FORBID, which is much more flexible than $PASS-EDIT.  It
allows you to set up any number of rules (for example, must be a minimum
length, must begin and end with a letter, must contain a numeric digit, and
so forth), and issue a custom-tailored error message about any rule that the
user neglects.

Quoting from the SECURITY/3000 manual:

"Note the syntax of each $VEPASS-FORBID line:
   $VEPASS-FORBID "expression" "error message" [usersets]
This means "forbid people from setting up passwords that match the given
expression; if such a password is tried, print the given error message".  By
default, this prohibition applies to all SECURITY users; however, you can
restrict this to particular usersets, e.g.
   $VEPASS-FORBID "ALPHA(P)"
      "Password must not be entirely alphabetic"  @.AP
would apply the prohibition only to users in the AP account."

What makes it really powerful is that the expression you specify can be an
arbitrary function and can access the user profile attribute variables and
functions.  See the manual or on-line help for examples.

Walter

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2