1 <samba:parameter name="password level"
4 advanced="1" developer="1"
5 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
7 <para>Some client/server combinations have difficulty
8 with mixed-case passwords. One offending client is Windows for
9 Workgroups, which for some reason forces passwords to upper
10 case when using the LANMAN1 protocol, but leaves them alone when
11 using COREPLUS! Another problem child is the Windows 95/98
12 family of operating systems. These clients upper case clear
13 text passwords even when NT LM 0.12 selected by the protocol
14 negotiation request/response.</para>
16 <para>This deprecated parameter defines the maximum number of characters
17 that may be upper case in passwords.</para>
19 <para>For example, say the password given was "FRED". If <parameter moreinfo="none">
20 password level</parameter> is set to 1, the following combinations
21 would be tried if "FRED" failed:</para>
23 <para>"Fred", "fred", "fRed", "frEd","freD"</para>
25 <para>If <parameter moreinfo="none">password level</parameter> was set to 2,
26 the following combinations would also be tried: </para>
28 <para>"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..</para>
30 <para>And so on.</para>
32 <para>The higher value this parameter is set to the more likely
33 it is that a mixed case password will be matched against a single
34 case password. However, you should be aware that use of this
35 parameter reduces security and increases the time taken to
36 process a new connection.</para>
38 <para>A value of zero will cause only two attempts to be
39 made - the password as is and the password in all-lower case.</para>
41 <para>This parameter is used only when using plain-text passwords. It is
42 not at all used when encrypted passwords as in use (that is the default
43 since samba-3.0.0). Use this only when <smbconfoption name="encrypt passwords">No</smbconfoption>.</para>
46 <value type="default">0</value>
47 <value type="example">4</value>