The branch, master has been updated
via 35a4a1e build: Fix build on systems without ldap development headers
via 7ef7ec7 docs: update for modern kerberos libs
via f84893a docs: remove references to security=server
via 963664e docs: Remove distinction between server and domain accounts
via c5151b6 docs: Update docs to the modern age of Samba 4.0
from 58e62ae s4:torture: fix error reporting in the raw.oplock-brl3 test
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit 35a4a1ed1f0fc6f1cbccd31bb7db9431b2518a5b
Author: Andrew Bartlett <[email protected]>
Date: Fri Sep 14 11:58:02 2012 -0700
build: Fix build on systems without ldap development headers
Autobuild-User(master): Andrew Bartlett <[email protected]>
Autobuild-Date(master): Fri Sep 14 22:53:30 CEST 2012 on sn-devel-104
commit 7ef7ec7be88f365ebd0c9da425283375188be2d1
Author: Andrew Bartlett <[email protected]>
Date: Fri Sep 14 11:57:38 2012 -0700
docs: update for modern kerberos libs
commit f84893a54b27828946ca75e72542116a560315d6
Author: Andrew Bartlett <[email protected]>
Date: Fri Sep 14 11:57:05 2012 -0700
docs: remove references to security=server
commit 963664eccce0e7e221ab2c465a430b4d8e2e081b
Author: Andrew Bartlett <[email protected]>
Date: Fri Sep 14 09:29:51 2012 -0700
docs: Remove distinction between server and domain accounts
Accounts on a server become accounts on the DC when upgraded. If they do
not
then this is simply a bug (in say tdbsam), not a feature to be documented.
Andrew Bartlett
commit c5151b62679edd11940023e757378c7aac66933a
Author: Andrew Bartlett <[email protected]>
Date: Fri Sep 14 09:28:06 2012 -0700
docs: Update docs to the modern age of Samba 4.0
This removes references to security=share, security=server and other
outdated things.
It also updates to a world where encrypted passwords are the norm.
Andrew Bartlett
-----------------------------------------------------------------------
Summary of changes:
docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml | 40 +---
docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml | 118 +----------
docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml | 272 +-----------------------
source3/wscript_build | 1 +
4 files changed, 18 insertions(+), 413 deletions(-)
Changeset truncated at 500 lines:
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml
b/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml
index 951c879..5ea2db2 100644
--- a/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml
@@ -130,9 +130,9 @@ configuration file is faulty.
<note><para>
<indexterm><primary>/etc/samba</primary></indexterm>
-<indexterm><primary>/usr/local/samba/lib</primary></indexterm>
+<indexterm><primary>/usr/local/samba/etc</primary></indexterm>
Your &smb.conf; file may be located in <filename>/etc/samba</filename>
-or in <filename>/usr/local/samba/lib</filename>.
+or in <filename>/usr/local/samba/etc</filename>.
</para></note>
</step>
@@ -431,8 +431,9 @@ If it says <quote><errorname>bad
password,</errorname></quote> then the likely c
<orderedlist>
<listitem>
<para>
- You have shadow passwords (or some other password system) but didn't
- compile in support for them in &smbd;.
+ Password encryption is enabled by default, but you have not
+ yet set a password for your samba user. Run
+ <command>smbpasswd -a username</command>
</para>
</listitem>
@@ -444,7 +445,8 @@ If it says <quote><errorname>bad
password,</errorname></quote> then the likely c
<listitem>
<para>
- You have a mixed-case password and you haven't enabled the
<smbconfoption name="password level"/> option at a high enough level.
+ You have explicitly disabled encrypted passwords with
+ <smbconfoption name="encrypt passwords">no</smbconfoption> have a
mixed-case password and you haven't enabled the <smbconfoption name="password
level"/> option at a high enough level.
</para>
</listitem>
@@ -454,12 +456,6 @@ If it says <quote><errorname>bad
password,</errorname></quote> then the likely c
</para>
</listitem>
-<listitem>
- <para>
- You enabled password encryption but didn't map UNIX to Samba users. Run
- <command>smbpasswd -a username</command>
- </para>
-</listitem>
</orderedlist>
<para>
@@ -544,17 +540,7 @@ and other config lines in &smb.conf; are correct.
</para>
<para>
-It's also possible that the server can't work out what username to connect you
as.
-To see if this is the problem, add the line
-<smbconfoption name="user">username</smbconfoption> to the
-<smbconfsection name="[tmp]"/> section of
-&smb.conf; where <parameter>username</parameter> is the
-username corresponding to the password you typed. If you find this
-fixes things, you may need the username mapping option.
-</para>
-
-<para>
-It might also be the case that your client only sends encrypted passwords
+By default, most clients only sends encrypted passwords
and you have <smbconfoption name="encrypt passwords">no</smbconfoption> in
&smb.conf;.
Change this setting to `yes' to fix this.
</para>
@@ -587,13 +573,9 @@ From file manager, try to browse the server. Your Samba
server should
appear in the browse list of your local workgroup (or the one you
specified in &smb.conf;). You should be able to double-click on the name
of the server and get a list of shares. If you get the error message
<quote>invalid password,</quote>
- you are probably running Windows NT and it
-is refusing to browse a server that has no encrypted password
-capability and is in user-level security mode. In this case, either set
-<smbconfoption name="security">server</smbconfoption> and
-<smbconfoption name="password server">Windows_NT_Machine</smbconfoption> in
your
-&smb.conf; file or make sure <smbconfoption name="encrypt passwords"/> is
-set to <quote>yes</quote>.
+your client may be refusing to browse a server that has no encrypted password
+capability. In this case make sure <smbconfoption name="encrypt passwords"/> is
+set to <quote>yes</quote> and repeat the steps in this gude.
</para>
</step>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
b/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
index d017863..fb81ac0 100644
--- a/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
@@ -797,72 +797,6 @@ but in most cases the following will suffice:
</sect2>
-<sect2>
-<title>Why Is This Better Than <parameter>security =
server</parameter>?</title>
-
-<para>
-<indexterm><primary>domain security</primary></indexterm>
-<indexterm><primary>UNIX users</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
-Currently, domain security in Samba does not free you from having to create
local UNIX users to represent the
-users attaching to your server. This means that if domain user
<constant>DOM\fred</constant> attaches to your
-domain security Samba server, there needs to be a local UNIX user fred to
represent that user in the UNIX file
-system. This is similar to the older Samba security mode <smbconfoption
-name="security">server</smbconfoption>, where Samba would pass through the
authentication request to a Windows
-NT server in the same way as a Windows 95 or Windows 98 server would.
-</para>
-
-<para>
-<indexterm><primary>winbind</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-Please refer to <link linkend="winbind">Winbind: Use of Domain
Accounts</link>, for information on a system
-to automatically assign UNIX UIDs and GIDs to Windows NT domain users and
groups.
-</para>
-
-<para>
-<indexterm><primary>domain-level</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
-<indexterm><primary>RPC</primary></indexterm>
-The advantage of domain-level security is that the authentication in
domain-level security is passed down the
-authenticated RPC channel in exactly the same way that an NT server would do
it. This means Samba servers now
-participate in domain trust relationships in exactly the same way NT servers
do (i.e., you can add Samba
-servers into a resource domain and have the authentication passed on from a
resource domain PDC to an account
-domain PDC).
-</para>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>connection resources</primary></indexterm>
-In addition, with <smbconfoption name="security">server</smbconfoption>, every
Samba daemon on a server has to
-keep a connection open to the authenticating server for as long as that daemon
lasts. This can drain the
-connection resources on a Microsoft NT server and cause it to run out of
available connections. With
-<smbconfoption name="security">domain</smbconfoption>, however, the Samba
daemons connect to the PDC or BDC
-only for as long as is necessary to authenticate the user and then drop the
connection, thus conserving PDC
-connection resources.
-</para>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>authentication reply</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>NT groups</primary></indexterm>
-Finally, acting in the same manner as an NT server authenticating to a PDC
means that as part of the
-authentication reply, the Samba server gets the user identification
information such as the user SID, the list
-of NT groups the user belongs to, and so on.
-</para>
-
-<note>
-<para>
-Much of the text of this document was first published in the Web magazine
-<ulink url="http://www.linuxworld.com";><emphasis>LinuxWorld</emphasis></ulink>
as the article <ulink
-url="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html"/>
-<emphasis>Doing the NIS/NT Samba</emphasis>.
-</para>
-</note>
-
-</sect2>
</sect1>
<sect1 id="ads-member">
@@ -979,11 +913,7 @@ When manually configuring <filename>krb5.conf</filename>,
the minimal configurat
<screen>
[libdefaults]
default_realm = YOUR.KERBEROS.REALM
-
-[realms]
- YOUR.KERBEROS.REALM = {
- kdc = your.kerberos.server
- }
+ dns_lookup_kdc = true
[domain_realms]
.kerberos.server = YOUR.KERBEROS.REALM
@@ -991,13 +921,10 @@ When manually configuring <filename>krb5.conf</filename>,
the minimal configurat
</para>
<para>
-<indexterm><primary>Heimdal</primary></indexterm>
-When using Heimdal versions before 0.6, use the following configuration
settings:
+If you must specify the KDC directly, the minimal configuration is:
<screen>
[libdefaults]
default_realm = YOUR.KERBEROS.REALM
- default_etypes = des-cbc-crc des-cbc-md5
- default_etypes_des = des-cbc-crc des-cbc-md5
[realms]
YOUR.KERBEROS.REALM = {
@@ -1017,19 +944,6 @@ Test your config by doing a <userinput>kinit
making sure that your password is accepted by the Win2000 KDC.
</para>
-<para>
-<indexterm><primary>Heimdal</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>KDC</primary></indexterm>
-<indexterm><primary>Windows 2003</primary></indexterm>
-With Heimdal versions earlier than 0.6.x you can use only newly created
accounts
-in ADS or accounts that have had the password changed once after migration, or
-in case of <constant>Administrator</constant> after installation. At the
-moment, a Windows 2003 KDC can only be used with Heimdal releases later than
0.6
-(and no default etypes in krb5.conf). Unfortunately, this whole area is still
-in a state of flux.
-</para>
-
<note><para>
<indexterm><primary>realm</primary></indexterm>
<indexterm><primary>uppercase</primary></indexterm>
@@ -1055,25 +969,6 @@ Clock skew limits are configurable in the Kerberos
protocols. The default settin
</para>
<para>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>KDC</primary></indexterm>
-<indexterm><primary>hostname</primary></indexterm>
-<indexterm><primary>realm</primary></indexterm>
-You also must ensure that you can do a reverse DNS lookup on the IP address of
your KDC. Also, the name that
-this reverse lookup maps to must either be the NetBIOS name of the KDC (i.e.,
the hostname with no domain
-attached) or it can be the NetBIOS name followed by the realm.
-</para>
-
-<para>
-<indexterm><primary>/etc/hosts</primary></indexterm>
-<indexterm><primary>KDC</primary></indexterm>
-<indexterm><primary>realm</primary></indexterm>
-The easiest way to ensure you get this right is to add a
<filename>/etc/hosts</filename> entry mapping the IP
-address of your KDC to its NetBIOS name. If you do not get this correct, then
you will get a <errorname>local
-error</errorname> when you try to join the realm.
-</para>
-
-<para>
<indexterm><primary>Kerberos</primary></indexterm>
<indexterm><primary>Create the Computer Account</primary></indexterm>
<indexterm><primary>Testing Server Setup</primary></indexterm>
@@ -1160,15 +1055,6 @@ name, it may need to be quadrupled to pass through the
shell escape and ldap esc
<replaceable>USERNAME</replaceable>@<replaceable>REALM</replaceable></userinput>.
<replaceable>USERNAME</replaceable> must be a user who has rights to
add a machine to the domain.
</para></listitem></varlistentry>
-
- <varlistentry><term>Unsupported encryption/or checksum types</term>
- <listitem><para>
- <indexterm><primary>/etc/krb5.conf</primary></indexterm>
- <indexterm><primary>unsupported encryption</primary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm>
- Make sure that the <filename>/etc/krb5.conf</filename> is correctly
configured
- for the type and version of Kerberos installed on the system.
- </para></listitem></varlistentry>
</variablelist>
</para>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml
b/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml
index 0b90c92..f0c07d2 100644
--- a/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml
@@ -177,24 +177,10 @@ protocol. Since some time around 1996 the protocol has
been better known as the
<indexterm><primary>security levels</primary></indexterm>
<indexterm><primary>security modes</primary></indexterm>
<indexterm><primary>user-level</primary></indexterm>
-<indexterm><primary>share-level</primary></indexterm>
-In the SMB/CIFS networking world, there are only two types of security:
<emphasis>user-level</emphasis> and
-<emphasis>share level</emphasis>. We refer to these collectively as
<emphasis>security levels</emphasis>. In
-implementing these two security levels, Samba provides flexibilities that are
not available with MS Windows
-NT4/200x servers. In fact, Samba implements <emphasis>share-level</emphasis>
security only one way, but has
-four ways of implementing <emphasis>user-level</emphasis> security.
Collectively, we call the Samba
+Samba has three ways of implementing <emphasis>user-level</emphasis> security.
Collectively, we call the Samba
implementations of the security levels <emphasis>security modes</emphasis>.
They are known as
-<emphasis>share</emphasis>, <emphasis>user</emphasis>,
<emphasis>domain</emphasis>, <emphasis>ADS</emphasis>,
-and <emphasis>server</emphasis> modes. They are documented in this chapter.
-</para>
-
-<para>
-An SMB server informs the client, at the time of a session setup, the security
level the server is running.
-There are two options: share-level and user-level. Which of these two the
client receives affects the way the
-client then tries to authenticate itself. It does not directly affect (to any
great extent) the way the Samba
-server does security. This may sound strange, but it fits in with the
client/server approach of SMB. In SMB
-everything is initiated and controlled by the client, and the server can only
tell the client what is
-available and whether an action is allowed.
+<emphasis>user</emphasis>, <emphasis>domain</emphasis> and
+<emphasis>ADS</emphasis> modes. They are documented in this chapter.
</para>
<para>
@@ -268,71 +254,6 @@ This is the default setting since Samba-2.2.x.
</sect2>
<sect2>
-<title>Share-Level Security</title>
-
-<para>
-<indexterm><primary>share-level</primary></indexterm>
-<indexterm><primary>mount</primary></indexterm>
-In share-level security, the client authenticates itself separately for each
share. It sends a password along
-with each tree connection request (share mount), but it does not explicitly
send a username with this
-operation. The client expects a password to be associated with each share,
independent of the user. This means
-that Samba has to work out what username the client probably wants to use,
-because the username is not explicitly sent to the SMB server. Some commercial
SMB servers such as NT actually associate passwords directly with shares
-in share-level security, but Samba always uses the UNIX authentication scheme
where it is a username/password
-pair that is authenticated, not a share/password pair.
-</para>
-
-<para>
-To understand the MS Windows networking parallels, think in terms of MS
Windows 9x/Me where you can create a
-shared folder that provides read-only or full access, with or without a
password.
-</para>
-
-<para>
-Many clients send a session setup request even if the server is in share-level
security. They normally send a valid
-username but no password. Samba records this username in a list of possible
usernames. When the client then
-issues a tree connection request, it also adds to this list the name of the
share they try to connect to (useful for
-home directories) and any users listed in the <smbconfoption name="user"/>
parameter in the &smb.conf; file.
-The password is then checked in turn against these possible usernames. If a
match is found, then the client is
-authenticated as that user.
-</para>
-
-<para>
-<indexterm><primary>name service switch</primary><see>NSS</see></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>nsswitch.conf</primary></indexterm>
-Where the list of possible user names is not provided, Samba makes a UNIX
system call to find the user
-account that has a password that matches the one provided from the standard
account database. On a system that
-has no name service switch (NSS) facility, such lookups will be from the
<filename>/etc/passwd</filename>
-database. On NSS enabled systems, the lookup will go to the libraries that
have been specified in the
-<filename>nsswitch.conf</filename> file. The entries in that file in which the
libraries are specified are:
-<screen>
-passwd: files nis ldap
-shadow: files nis ldap
-group: files nis ldap
-</screen>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>/etc/group</primary></indexterm>
-<indexterm><primary>NIS</primary></indexterm>
-In the example shown here (not likely to be used in practice) the lookup will
check
-<filename>/etc/passwd</filename> and <filename>/etc/group</filename>, if not
found it will check NIS, then
-LDAP.
-</para>
-
-<sect3>
-<title>Example Configuration</title>
-
-<para>
-The &smb.conf; parameter that sets share-level security is:
-</para>
-
-<para><smbconfblock>
-<smbconfoption name="security">share</smbconfoption>
-</smbconfblock></para>
-
-</sect3>
-</sect2>
-
-<sect2>
<title>Domain Security Mode (User-Level Security)</title>
<para>
@@ -418,32 +339,12 @@ security domain. This is done as follows:
<procedure>
- <step><para>On the MS Windows NT domain controller, using
- the Server Manager, add a machine account for the Samba server.
- </para></step>
-
<step><para>On the UNIX/Linux system execute:</para>
<para><screen>&rootprompt;<userinput>net rpc join -U
administrator%password</userinput></screen></para>
</step>
</procedure>
-<note><para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-Samba-2.2.4 and later Samba 2.2.x series releases can autojoin a Windows
NT4-style domain just by executing:
-<screen>
-&rootprompt;<userinput>smbpasswd -j <replaceable>DOMAIN_NAME</replaceable> -r
<replaceable>PDC_NAME</replaceable> \
- -U Administrator%<replaceable>password</replaceable></userinput>
-</screen>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
-Samba-3 can do the same by executing:
-<screen>
-&rootprompt;<userinput>net rpc join -U
Administrator%<replaceable>password</replaceable></userinput>
-</screen>
-It is not necessary with Samba-3 to specify the
<replaceable>DOMAIN_NAME</replaceable> or the
-<replaceable>PDC_NAME</replaceable>, as it figures this out from the
&smb.conf; file settings.
-</para></note>
-
<para>
<indexterm><primary>invalid shell</primary></indexterm>
<indexterm><primary>/etc/passwd</primary></indexterm>
@@ -481,7 +382,7 @@ For more information regarding domain membership, <link
linkend="domain-member">
<para>
<indexterm><primary>ADS</primary></indexterm>
<indexterm><primary>native mode</primary></indexterm>
-Both Samba-2.2, and Samba-3 can join an Active Directory domain using NT4
style RPC based security. This is
+Samba can join an Active Directory domain using NT4 style RPC based security.
This is
possible if the domain is run in native mode. Active Directory in native mode
perfectly allows NT4-style
domain members. This is contrary to popular belief.
</para>
@@ -527,103 +428,6 @@ ADS Domain Membership</link> for more information
regarding this configuration o
</sect3>
</sect2>
-<sect2>
-<title>Server Security (User Level Security)</title>
-
-<para>
-Server security mode is left over from the time when Samba was not capable of
acting
-as a domain member server. It is highly recommended not to use this feature.
Server
-security mode has many drawbacks that include:
-</para>
-
-<itemizedlist>
- <listitem><para>Potential account lockout on MS Windows NT4/200x
password servers.</para></listitem>
- <listitem><para>Lack of assurance that the password server is the one
specified.</para></listitem>
- <listitem><para>Does not work with Winbind, which is particularly
needed when storing profiles remotely.</para></listitem>
- <listitem><para>This mode may open connections to the password server
and keep them open for extended periods.</para></listitem>
- <listitem><para>Security on the Samba server breaks badly when the
remote password server suddenly shuts down.</para></listitem>
- <listitem><para>With this mode there is NO security account in the
domain that the password server belongs to for the Samba
server.</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>session setup</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-In server security mode the Samba server reports to the client that it is in
user-level security. The client
-then does a session setup as described earlier. The Samba server takes the
username/password that the client
-sends and attempts to log into the <smbconfoption name="password server"/> by
sending exactly the same
-username/password that it got from the client. If that server is in user-level
security and accepts the
-password, then Samba accepts the client's connection. This parameter allows
the Samba server to use another
-SMB server as the <smbconfoption name="password server"/>.
-</para>
-
-<para>
-<indexterm><primary>security level</primary></indexterm>
-<indexterm><primary>encryption</primary></indexterm>
-You should also note that at the start of all this, when the server tells the
client
-what security level it is in, it also tells the client if it supports
encryption. If it
-does, it supplies the client with a random cryptkey. The client will then send
all
-passwords in encrypted form. Samba supports this type of encryption by default.
-</para>
-
-<para>
-The parameter <smbconfoption name="security">server</smbconfoption> means that
Samba reports to clients that
-it is running in <emphasis>user mode</emphasis> but actually passes off all
authentication requests to another
-user mode server. This requires an additional parameter <smbconfoption
name="password server"/> that points to
-the real authentication server. The real authentication server can be another
Samba server, or it can be a
-Windows NT server, the latter being natively capable of encrypted password
support.
-</para>
-
-<note><para>
-<indexterm><primary>password server</primary></indexterm>
-<indexterm><primary>workgroup</primary></indexterm>
-When Samba is running in <emphasis>server security mode</emphasis>, it is
essential that the parameter
-<emphasis>password server</emphasis> is set to the precise NetBIOS machine
name of the target authentication
-server. Samba cannot determine this from NetBIOS name lookups because the
choice of the target authentication
-server is arbitrary and cannot be determined from a domain name. In essence, a
Samba server that is in
-<emphasis>server security mode</emphasis> is operating in what used to be
known as workgroup mode.
-</para></note>
-
-<sect3>
-<title>Example Configuration</title>
-<para><emphasis>
-Using MS Windows NT as an Authentication Server
-</emphasis></para>
-
-<para>
-This method involves the additions of the following parameters in the
&smb.conf; file:
-</para>
-
-<para><smbconfblock>
-<smbconfoption name="encrypt passwords">Yes</smbconfoption>
-<smbconfoption name="security">server</smbconfoption>
-<smbconfoption name="password server">"NetBIOS_name_of_a_DC"</smbconfoption>
-</smbconfblock></para>
-
-
-<para>
-There are two ways of identifying whether or not a username and password pair
is valid.
-One uses the reply information provided as part of the authentication messaging
-process, the other uses just an error code.
-</para>
-
-<para>
-<indexterm><primary>bogus</primary></indexterm>
-<indexterm><primary>lockout</primary></indexterm>
-The downside of this mode of configuration is that for security reasons Samba
-will send the password server a bogus username and a bogus password, and if
the remote
-server fails to reject the bogus username and password pair, then an
alternative mode of
-identification or validation is used. Where a site uses password lockout,
after a
-certain number of failed authentication attempts, this will result in user
lockouts.
-</para>
-
-<para>
-Use of this mode of authentication requires a standard UNIX account for the
user.
-This account can be blocked to prevent logons by non-SMB/CIFS clients.
-</para>
-
-</sect3>
-</sect2>
--
Samba Shared Repository
