mirror of
https://github.com/hardkernel/linux.git
synced 2026-03-25 20:10:23 +09:00
cifs: set server->cipher_type to AES-128-CCM for SMB3.0
commit 6d2fcfe6b5 upstream.
SMB3.0 doesn't have encryption negotiate context but simply uses
the SMB2_GLOBAL_CAP_ENCRYPTION flag.
When that flag is present in the neg response cifs.ko uses AES-128-CCM
which is the only cipher available in this context.
cipher_type was set to the server cipher only when parsing encryption
negotiate context (SMB3.1.1).
For SMB3.0 it was set to 0. This means cipher_type value can be 0 or 1
for AES-128-CCM.
Fix this by checking for SMB3.0 and encryption capability and setting
cipher_type appropriately.
Signed-off-by: Aurelien Aptel <aaptel@suse.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Steve French <stfrench@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
020b6b0dc7
commit
3e5b48d9e7
@@ -951,6 +951,13 @@ SMB2_negotiate(const unsigned int xid, struct cifs_ses *ses)
|
||||
/* Internal types */
|
||||
server->capabilities |= SMB2_NT_FIND | SMB2_LARGE_FILES;
|
||||
|
||||
/*
|
||||
* SMB3.0 supports only 1 cipher and doesn't have a encryption neg context
|
||||
* Set the cipher type manually.
|
||||
*/
|
||||
if (server->dialect == SMB30_PROT_ID && (server->capabilities & SMB2_GLOBAL_CAP_ENCRYPTION))
|
||||
server->cipher_type = SMB2_ENCRYPTION_AES128_CCM;
|
||||
|
||||
security_blob = smb2_get_data_area_len(&blob_offset, &blob_length,
|
||||
(struct smb2_sync_hdr *)rsp);
|
||||
/*
|
||||
|
||||
Reference in New Issue
Block a user