1 <samba:parameter xmlns:samba="http://samba.org/common">
2 <term><anchor id="PASSWORDLEVEL"/>password level (G)</term>
3 <listitem><para>Some client/server combinations have difficulty
4 with mixed-case passwords. One offending client is Windows for
5 Workgroups, which for some reason forces passwords to upper
6 case when using the LANMAN1 protocol, but leaves them alone when
7 using COREPLUS! Another problem child is the Windows 95/98
8 family of operating systems. These clients upper case clear
9 text passwords even when NT LM 0.12 selected by the protocol
10 negotiation request/response.</para>
12 <para>This parameter defines the maximum number of characters
13 that may be upper case in passwords.</para>
15 <para>For example, say the password given was "FRED". If <parameter moreinfo="none">
16 password level</parameter> is set to 1, the following combinations
17 would be tried if "FRED" failed:</para>
19 <para>"Fred", "fred", "fRed", "frEd","freD"</para>
21 <para>If <parameter moreinfo="none">password level</parameter> was set to 2,
22 the following combinations would also be tried: </para>
24 <para>"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..</para>
26 <para>And so on.</para>
28 <para>The higher value this parameter is set to the more likely
29 it is that a mixed case password will be matched against a single
30 case password. However, you should be aware that use of this
31 parameter reduces security and increases the time taken to
32 process a new connection.</para>
34 <para>A value of zero will cause only two attempts to be
35 made - the password as is and the password in all-lower case.</para>
37 <para>Default: <command moreinfo="none">password level = 0</command></para>
38 <para>Example: <command moreinfo="none">password level = 4</command></para>