docs: Remove confusing reference to smb signing and client use spnego

This section is more confusing than helpful, as client support for both is on by default.

Andrew Bartlett

diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml b/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
index fb81ac0b34d3e9485aaf3a267413c2fde2cf02e2..5cb2a43db637b2dc4fc677f2b1e557c42be51d78 100644 (file)
--- a/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
@@ -1286,24 +1286,5 @@ account to which the Samba backend database account can be mapped.
 </para>
 
 </sect2>
-
-<sect2>
-       <title>I Can't Join a Windows 2003 PDC</title>
-
-       <para>
-<indexterm><primary>SMB signing</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>Windows 2003</primary></indexterm>
-<indexterm><primary>SMB/CIFS</primary></indexterm>
-       Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0.
-       Set <smbconfoption name="client use spnego">yes</smbconfoption> when communicating 
-       with a Windows 2003 server. This will not interfere with other Windows clients that do not
-       support the more advanced security features of Windows 2003 because the client will simply
-       negotiate a protocol that both it and the server suppport. This is a well-known fall-back facility
-       that is built into the SMB/CIFS protocols.
-       </para>
-
-</sect2>
-
 </sect1>
 </chapter>