Fix the documentation of --encrypt to explain SMB3 encryption for smbclient.

Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Michael Adam <obnox@samba.org>
(cherry picked from commit 4044e2beb7145afb261c98e100574e4e842e1b9e)

diff --git a/docs-xml/manpages/smbclient.1.xml b/docs-xml/manpages/smbclient.1.xml
index 2ed53574d7000ae7457b13979db18bd62f527de1..6717f18fd89ab8c785a3dd69b59523c6b5b20b02 100644 (file)
--- a/docs-xml/manpages/smbclient.1.xml
+++ b/docs-xml/manpages/smbclient.1.xml
@@ -331,13 +331,14 @@
                
                <varlistentry>
                <term>-e|--encrypt</term>
-               <listitem><para>This command line parameter requires the remote
-               server support the UNIX extensions. Request that the connection be
-               encrypted. This is new for Samba 3.2 and will only work with Samba
-               3.2 or above servers. Negotiates SMB encryption using GSSAPI. Uses
-               the given credentials for the encryption negotiation (either kerberos
-               or NTLMv1/v2 if given domain/username/password triple. Fails the
-               connection if encryption cannot be negotiated.
+               <listitem><para>
+               This command line parameter requires the remote
+               server support the UNIX extensions or that the SMB3 protocol has been selected.
+               Requests that the connection be encrypted. Negotiates SMB encryption using either
+               SMB3 or POSIX extensions via GSSAPI. Uses the given credentials for
+               the encryption negotiation (either kerberos or NTLMv1/v2 if given
+               domain/username/password triple. Fails the connection if encryption
+               cannot be negotiated.
                </para></listitem>
                </varlistentry>