Re: strong passwords

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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

Date: Mon, 17 Jan 2005 11:54:16 -0600

Agreed.

Also note, that a truly complex password with well educated
users who will NEVER share their password and who understand
the NEED for security might better be left for a LONGER period.

A good password that is never shared does not (really) need
to be changed very often. 

-- 
Herb Martin
"Ryan Hanisco" <rhanisco@flagshipis.com> wrote in message
news:uhFAHuL$EHA.4004@tk2msftngp13.phx.gbl...
> Flavio,
>
> You will not see an impact to your end users until they are forced to
change
> their passwords.  Then the complexity requirements will go into effect.
> Brace yourself for the helpdesk calls and public outcry. Do yourself a
favor
> and send out a notice, e-mail, newsletter, whatever outlining the change,
> and give them warning.
>
> Make sure you understand what a strong password is.  Most people, not in
IT,
> will be shocked at the requirements and take it personally that you are
> making their lives harder.  Also, you may actually see a reduction in
> security as people write these things down and store them under their
> keyboards.
>
> Good PR and management buy in are the only way to really effect this
change.
>
> -- 
> Ryan Hanisco
> MCSE, MCDBA
> Flagship Integration Services
>
> "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: Linking Password Length to Write-down probability
    ... And take the first character of each word, ... outrageous complexity requirements) as The Solution. ... bordering to "stupid security". ... It is for the intended recipient only. ...
    (Security-Basics)
  • Re: Good password change fails due to complexity.
    ... > that it doesn't meet complexity requirements. ... > security or passwords. ... you don't understand how Group Policy works. ... settings to disabled means, "I won't make any changes to those policy ...
    (microsoft.public.security)