2 !== Passwords.txt for Samba release 2.2.0-alpha1 23 Nov 2000
5 Date: Updated April 19th 1999.
8 Subject: NOTE ABOUT PASSWORDS
9 =============================================================================
11 Unix systems use a wide variety of methods for checking the validity
12 of a password. This is primarily controlled with the Makefile defines
13 mentioned in the Makefile.
15 Also note that some clients (notably WfWg) uppercase the password
16 before sending it. The server tries the password as it receives it and
17 also after lowercasing it.
19 The Samba server can also be configured to try different
20 upper/lowercase combinations. This is controlled by the [global]
21 parameter "password level". A level of N means to try all combinations
22 up to N uppercase characters in the password. A high value can chew a
23 fair bit of CPU time and can lower the security of your system. Do not
24 use this options unless you really need it - the time taken for
25 password checking can become so high that clients time out.
27 If you do use the "password level" option then you might like to use
28 -DUFC_CRYPT in your Makefile. On some machine this makes password
29 checking _much_ faster. This is also useful if you use the @group
30 syntax in the user= option.
32 If your site uses AFS (the Andrew File System), you can use the AFS section
33 in the Makefile. This will first attempt to authenticate a username and
34 password to AFS. If that succeeds, then the associated AFS rights will be
35 granted. Otherwise, the password checking routine falls back to whatever
36 Unix password checking method you are using. Note that the AFS code is
37 only written and tested for AFS 3.3 and later.
40 SECURITY = SERVER or DOMAIN
41 ===========================
43 Samba can use a remote server to do its username/password
44 validation. This allows you to have one central machine (for example a
45 NT box) control the passwords for the Unix box.
47 See the section on "security =" in smb.conf(5) for details.