Why 42 Days

Why 42 Days

Secure Home | Search | About
 Microsoft Applications Security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
Why 42 Days Pa55w0rd 10-04-2007
| ---> Re: Why 42 Days Mostly Gizzards10-04-2007
|   ---> Re: Why 42 Days microsoft news10-05-2007
|     `--> Re: Why 42 Days Eric Denekamp10-05-2007
`--> Re: Why 42 Days Roger Abell [MV...10-04-2007
Posted by =?Utf-8?B?UGE1NXcwcmQ=?= on October 4, 2007, 2:42 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Reviewing our domain security policy and wonder why microsoft recommend
42days as a "Maximum Password Age" ?

Posted by Alun Jones on October 4, 2007, 4:05 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
> Reviewing our domain security policy and wonder why microsoft recommend
> 42days as a "Maximum Password Age" ?

Because that's what the dice rolled?

Seriously, consider what your own password requirements are, and why aging
them will help or hinder your operation. Then figure out how you can best
achieve that, and at what stage passwords should become stale.

Also consider how many pitchforks and torches your users can assemble should
you set the aging period too low.

Alun.
~~~~



Posted by Mostly Gizzards on October 4, 2007, 4:25 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Alun Jones wrote:
>> Reviewing our domain security policy and wonder why microsoft recommend
>> 42days as a "Maximum Password Age" ?
>
> Because that's what the dice rolled?
>
> Seriously, consider what your own password requirements are, and why aging
> them will help or hinder your operation. Then figure out how you can best
> achieve that, and at what stage passwords should become stale.
>
> Also consider how many pitchforks and torches your users can assemble should
> you set the aging period too low.
>
> Alun.
> ~~~~
>
>

Because 42 is the answer.

Posted by microsoft news on October 5, 2007, 8:09 am
If you were  Registered and logged in, you could reply and use other advanced thread options

> Alun Jones wrote:
>>> Reviewing our domain security policy and wonder why microsoft recommend
>>> 42days as a "Maximum Password Age" ?
>>
>> Because that's what the dice rolled?
>>
>> Seriously, consider what your own password requirements are, and why
>> aging them will help or hinder your operation. Then figure out how you
>> can best achieve that, and at what stage passwords should become stale.
>>
>> Also consider how many pitchforks and torches your users can assemble
>> should you set the aging period too low.
>>
>> Alun.
>> ~~~~
>
> Because 42 is the answer.

so it is................



Posted by Eric Denekamp on October 5, 2007, 8:57 am
If you were  Registered and logged in, you could reply and use other advanced thread options
The answer to the ultimate question about life the....
hmmm did the universe change just now?

--
Good luck

Eric Denekamp
http://blogs.infosupport.com/ericd

=============================
>
>> Alun Jones wrote:
>>>> Reviewing our domain security policy and wonder why microsoft recommend
>>>> 42days as a "Maximum Password Age" ?
>>>
>>> Because that's what the dice rolled?
>>>
>>> Seriously, consider what your own password requirements are, and why
>>> aging them will help or hinder your operation. Then figure out how you
>>> can best achieve that, and at what stage passwords should become stale.
>>>
>>> Also consider how many pitchforks and torches your users can assemble
>>> should you set the aging period too low.
>>>
>>> Alun.
>>> ~~~~
>>
>> Because 42 is the answer.
>
> so it is................
>


Similar ThreadsPosted
Network shutdowns every 6 days at 5:00 PM....... July 20, 2006, 3:07 pm
Permission is missing after 2-3 days April 25, 2007, 12:44 am
Need logon and Logoff data for 30 days September 14, 2005, 2:10 pm

The site map in XML format XML site map

Contact Us | Privacy Policy