Discussion Locked

password policy

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
How can I force my users to login to an NT 4.0 domain using a mix of alpha and numeric characters. I have looked at passfilt.dll, but only want to force two of the three policies, instead of 3.

9 replies

by craig haunch

Found this on ms website. What 2 do you want to implement as the 3rd one says coannot contain username, thought that would be standard if wanting to enforce strong passwords so effectively you are only using the other 2.

Passfilt.dll implements the following password policy:

Passwords must be at least six (6)characters long.

Passwords must contain characters from at least three (3) of the following four (4) classes:
Description English upper case letters
A, B, C, ... Z
English lower case letters
a, b, c, ... z
Westernized Arabic numerals
0, 1, 2, ... 9
Non-alphanumeric ("special characters") such as punctuation symbols

Passwords may not containyour user name or any part of your full name.

These requirements are hard-coded in the Passfilt.dll file and cannot be changed through the user interface or registry. If you wish to raise or lower these requirements, you must write your own .dll and implement it in the same fashion.When strong password functionality is enabled on a Windows NT 4.0 computer, an Administrator will still be able to change a password, with the User Manager tool, in such a way that it no longer meets the criteria for strong passwords.

Also found this

MORE INFORMATION
This behavior is by design. Strong password filtering is performed when password change requests arrive over the network, and weak passwords are rejected at that time. Direct changes to the security account manager (SAM) database are not filtered.

So passwords changed by the admin in usermanager don;t have to comply, it is when they are changed over the network.

Hope this helps

by liteswitch

If your clients are using Win9x machines, then by using System Policy editor, you can sprecify that they have to use alphanumeric passwords. Look in the win9x cd under admin tools and find poledit.exe. Add/remove programs, then have disk, and pointto the cd, and sytem policies should be installed.

by mebudman

Forcing users to use all available characters is self defeating. Having recently gone through the pain of trying to enforce a strong password policy at our company. The complaints from the field forced (means the upper management did not care about security) us to change the password life to 1 year. The problem with passwords is the LAN Manager Hash that breaks a password into 7byte blocks and encrypts those blocks. This is for Win9x logons. If you are using Nt/2000 all around then you canforce all logon/authentication traffic to use the NTLMv2 authentication scheme which encrypts the whole password as one packet. By using the passfilt.dll the number of characters available per password character is at least 72, so the possible combinations of passwords is 72*72*72*72*72*72 (10030613004288) which given a reasonable password life, a password list could not be brute forced before all the passwords had to be changed. Make them use a upper,lower and either a number or special character. The trick is trying to get uses (if you are using win9x) to use passwords that are either 7 or 14 characters exactly.

by bkinsey1

Depends on what you mean by only wanting two of the three policies. One option is to write your own filter, which is all passfilt.dll really is. But I wouldn't recommend that unless you're an experienced developer.

Just to get alpha-numeric passwords with a secure length, use passprop. Passprop.exe (in the Resource Kit) forces the use of complex passwords. Combine that with setting the minimum length to 7 with the basic NT functionality and you've may have what you're looking for.

This discussion is closed to new replies.