Re: strong passwords

From: Herb Martin (news_at_LearnQuick.com)
Date: 01/18/05 

Date: Mon, 17 Jan 2005 19:48:05 -0600

I also would say that trying for secure passwords
shorter than 15 characters is a futile effort.

I have personally seen 14 character, semi-complex
passwords broken in 10-20 seconds on demand. 

-- 
Herb Martin
"Cary Shultz [A.D. MVP]" <cwshultz@mvps.org> wrote in message
news:ublViJP$EHA.2156@TK2MSFTNGP10.phx.gbl...
> Flavio,
>
> In addition to what Ryan and Herb ( Howdy, Guys! ) have stated I would
> suggest that you have a minimum password age of at least 10 days.  Why?
> Because without a minimum password age your smarter users will quickly
find
> out that they can change their password xx number of times ( in your case,
> 14 ) in rapid succession to get back to their favorite password.  Thus,
your
> password policy will not really be that effective.  With 10 days as the
> minimum password age most - hopefully all! - users will have given up!
>
> I would also suggest that you contact the MS PSS and get the fix ( for
> free ) and install it on all of your computers ( Domain Controllers,
Member
> Servers, Workstations ) as your users will most likely NOT come up with a
> password that will met with the complexity requirements.  This will result
> in an error message that is quite generic and not very informative.  With
> this hot fix the users will be given an error message that spells out
> exactly what they need to do ( assuming that they read it! ).
>
> Here is the link:
>
> http://support.microsoft.com/?id=821425
>
>
> You might also want to take a look at this MSKB Article:
>
> http://support.microsoft.com/?id=309799
>
> -- 
> Cary W. Shultz
> Roanoke, VA  24014
> Microsoft Active Directory MVP
>
> http://www.activedirectory-win2000.com
> http://www.grouppolicy-win2000.com
>
>
>
> "Flavio Alves" <FlavioAlves@discussions.microsoft.com> wrote in message
> news:3454A86B-CEC4-4463-969F-C0A302B86C69@microsoft.com...
> > In my company , we are applicating strong passwords and i have the
> > following
> > consiguration
> > - enforce password history = 12
> > - maximum password age = 90 days
> > - minimum password age = 0
> > - minimum password lenght = 6
> > - password must meet complexity ... = disable
> > - store passwords using .... = disable
> > Now , after changes will to stay of following form .
> > - enforce password history = 14
> > - maximum password age = 45 days
> > - minimum password age = 0
> > - minimum password lenght = 8
> > - password must meet complexity ... = enable
> > - store passwords using .... = disable
> >
> > What´s the impact in my ambient, that  will occur with all workstation
im
> > my
> > company ?
> >
>
>

Relevant Pages

  • Re: strong passwords
    ... Because without a minimum password age your smarter users will quickly find ... I would also suggest that you contact the MS PSS and get the fix (for ... Workstations) as your users will most likely NOT come up with a ... in an error message that is quite generic and not very informative. ...
    (microsoft.public.win2000.active_directory)
  • Re: New-Line in Regular Expression
    ... really good responses. ... > # Open the file for reading and if cannot die and give error message. ... > # While the file is open read through it and remove new line characters. ... > # For each item in the array print it out. ...
    (perl.beginners)
  • Re: New-Line in Regular Expression
    ... reason: POP3 Host did not acknowlege ... > # While the file is open read through it and remove new line characters. ... > # For each item in the array print it out. ... match the date field and the time field, and stored the exact log error message ...
    (perl.beginners)
  • Re: Access 2003 Combo problem
    ... that's why your getting the error message "Too Long" ... What's happening is that you are attempting to insert the Name, not the Abv ... characters long) and the two letter combination in the other field (2 ... Chuck Buckley ...
    (microsoft.public.access.formscoding)
  • RE: Repost - RunTime Error - Field too small
    ... Jet won't store changes to the external database in the table ... Here is the DLookup statement in the AfterUpdate event of the FacilityNumber ... If the name is longer that 30 characters, I get the error message. ...
    (microsoft.public.access.formscoding)