summaryrefslogtreecommitdiff
path: root/docs-xml/smbdotconf/security
diff options
context:
space:
mode:
authorAndrew Bartlett <abartlet@samba.org>2013-06-03 10:02:39 +1000
committerSimo Sorce <idra@samba.org>2013-06-11 08:35:21 -0400
commit26279a969879bfbd943dfda03c511ed7e14057ba (patch)
treed8510cc1e4d9bec8b036421e514b401b56a018c9 /docs-xml/smbdotconf/security
parent3fba9ba7ea85e33faac2718d2463c5d0cd2d85f4 (diff)
downloadsamba-26279a969879bfbd943dfda03c511ed7e14057ba.tar.gz
samba-26279a969879bfbd943dfda03c511ed7e14057ba.tar.bz2
samba-26279a969879bfbd943dfda03c511ed7e14057ba.zip
auth: Remove "password level"
We now only lowercase the password, we do not attempt to find another case combination that the password might be in. This option is already depricated, so it is now time to remove it. Andrew Bartlett Reviewed-by: Simo Sorce <idra@samba.org>
Diffstat (limited to 'docs-xml/smbdotconf/security')
-rw-r--r--docs-xml/smbdotconf/security/passwordlevel.xml48
1 files changed, 0 insertions, 48 deletions
diff --git a/docs-xml/smbdotconf/security/passwordlevel.xml b/docs-xml/smbdotconf/security/passwordlevel.xml
deleted file mode 100644
index eee838f65c..0000000000
--- a/docs-xml/smbdotconf/security/passwordlevel.xml
+++ /dev/null
@@ -1,48 +0,0 @@
-<samba:parameter name="password level"
- context="G"
- type="integer"
- advanced="1" developer="1"
- xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
-<description>
- <para>Some client/server combinations have difficulty
- with mixed-case passwords. One offending client is Windows for
- Workgroups, which for some reason forces passwords to upper
- case when using the LANMAN1 protocol, but leaves them alone when
- using COREPLUS! Another problem child is the Windows 95/98
- family of operating systems. These clients upper case clear
- text passwords even when NT LM 0.12 selected by the protocol
- negotiation request/response.</para>
-
- <para>This deprecated parameter defines the maximum number of characters
- that may be upper case in passwords.</para>
-
- <para>For example, say the password given was &quot;FRED&quot;. If <parameter moreinfo="none">
- password level</parameter> is set to 1, the following combinations
- would be tried if &quot;FRED&quot; failed:</para>
-
- <para>&quot;Fred&quot;, &quot;fred&quot;, &quot;fRed&quot;, &quot;frEd&quot;,&quot;freD&quot;</para>
-
- <para>If <parameter moreinfo="none">password level</parameter> was set to 2,
- the following combinations would also be tried: </para>
-
- <para>&quot;FRed&quot;, &quot;FrEd&quot;, &quot;FreD&quot;, &quot;fREd&quot;, &quot;fReD&quot;, &quot;frED&quot;, ..</para>
-
- <para>And so on.</para>
-
- <para>The higher value this parameter is set to the more likely
- it is that a mixed case password will be matched against a single
- case password. However, you should be aware that use of this
- parameter reduces security and increases the time taken to
- process a new connection.</para>
-
- <para>A value of zero will cause only two attempts to be
- made - the password as is and the password in all-lower case.</para>
-
- <para>This parameter is used only when using plain-text passwords. It is
- not at all used when encrypted passwords as in use (that is the default
- since samba-3.0.0). Use this only when <smbconfoption name="encrypt passwords">No</smbconfoption>.</para>
-</description>
-
-<value type="default">0</value>
-<value type="example">4</value>
-</samba:parameter>