Matthew.van.Eerdehbinc.com
Date: Thu Aug 26 2004 - 19:16:06 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Aviles wrote:
> Arthur thanks,
> Well, is for documentation purposes. For audit and documentation
> purposes it needs to be done. The client is on AD already but if we
> enable strong password doesn't that mean that all the passwords that
do
> not meet the criteria get disabled? That has been my experience in
> the past..
>
> Thanks
> -pa

One possibility is to email the new password requirement to the users
ahead of time and request that everyone change their password to
something that meets the requirements (unless their password already
meets the requirements.)
A somewhat more risky possibility is to generate a static HTML page
with some javascript that will run a series of regular expression tests
on the input. Then they could use this to see whether their password
meets the requirements. But that could be a very bad precedent to
set.

Matthew.van.Eerdehbinc.com 805.964.4554 x902
Hispanic Business Inc./HireDiversity.com Software Engineer
perl -e"map{y/a-z/l-za-k/;print}shift" "Jjhi pcdiwtg Ptga wprztg,"
-----BEGIN PGP SIGNATURE-----
Comment: pub key http://matthew.vaneerde.com/pgp-public-key.asc

iD8DBQFBLn1CUQQr0VWaglwRAmmvAKDsvy/UqEGeRdOui38CkuWElgVmLACfaQSs
fTF48Pf0HImBrf+Pm6gzF24=
=9QsW
-----END PGP SIGNATURE-----

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

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]