From b8f0f5ef3d92275c180b8c2043dd92c440b3ade6 Mon Sep 17 00:00:00 2001 From: Karolin Seeger Date: Fri, 16 May 2008 11:56:03 +0200 Subject: [PATCH] man pages: Remove documentation for 'smb encrypt'. Parameter new in 3.2. Karolin --- docs-xml/smbdotconf/security/smbencrypt.xml | 45 ----------------------------- 1 file changed, 45 deletions(-) delete mode 100644 docs-xml/smbdotconf/security/smbencrypt.xml diff --git a/docs-xml/smbdotconf/security/smbencrypt.xml b/docs-xml/smbdotconf/security/smbencrypt.xml deleted file mode 100644 index eb91ce51fa3..00000000000 --- a/docs-xml/smbdotconf/security/smbencrypt.xml +++ /dev/null @@ -1,45 +0,0 @@ - - - - This is a new feature introduced with Samba 3.2 and above. It is an - extension to the SMB/CIFS protocol negotiated as part of the UNIX extensions. - SMB encryption uses the GSSAPI (SSPI on Windows) ability to encrypt - and sign every request/response in a SMB protocol stream. When - enabled it provides a secure method of SMB/CIFS communication, - similar to an ssh protected session, but using SMB/CIFS authentication - to negotiate encryption and signing keys. Currently this is only - supported by Samba 3.2 smbclient, and hopefully soon Linux CIFSFS - and MacOS/X clients. Windows clients do not support this feature. - - - This controls whether the server offers or requires - the client it talks to to use SMB encryption. Possible values - are auto, mandatory - and disabled. This may be set on a per-share - basis, but clients may chose to encrypt the entire session, not - just traffic to a specific share. If this is set to mandatory - then all traffic to a share must must - be encrypted once the connection has been made to the share. - The server would return "access denied" to all non-encrypted - requests on such a share. Selecting encrypted traffic reduces - throughput as smaller packet sizes must be used (no huge UNIX - style read/writes allowed) as well as the overhead of encrypting - and signing all the data. - - - If SMB encryption is selected, Windows style SMB signing (see - the option) is no longer necessary, - as the GSSAPI flags use select both signing and sealing of the data. - - - When set to auto, SMB encryption is offered, but not enforced. - When set to mandatory, SMB encryption is required and if set - to disabled, SMB encryption can not be negotiated. - - -auto - -- 2.11.4.GIT