diff options
author | Steve French <stfrench@microsoft.com> | 2019-03-22 22:31:17 -0500 |
---|---|---|
committer | Steve French <stfrench@microsoft.com> | 2019-03-22 22:42:49 -0500 |
commit | 8c11a607d1d9cd6e7f01fd6b03923597fb0ef95a (patch) | |
tree | 36bf4f8f48560f48a482976fe0c70dec9f5d057f /block/blk-softirq.c | |
parent | 68ddb496800acdb46172b4981dc3753ea9b39c25 (diff) | |
download | linux-stable-8c11a607d1d9cd6e7f01fd6b03923597fb0ef95a.tar.gz linux-stable-8c11a607d1d9cd6e7f01fd6b03923597fb0ef95a.tar.bz2 linux-stable-8c11a607d1d9cd6e7f01fd6b03923597fb0ef95a.zip |
SMB3: Fix SMB3.1.1 guest mounts to Samba
Workaround problem with Samba responses to SMB3.1.1
null user (guest) mounts. The server doesn't set the
expected flag in the session setup response so we have
to do a similar check to what is done in smb3_validate_negotiate
where we also check if the user is a null user (but not sec=krb5
since username might not be passed in on mount for Kerberos case).
Note that the commit below tightened the conditions and forced signing
for the SMB2-TreeConnect commands as per MS-SMB2.
However, this should only apply to normal user sessions and not for
cases where there is no user (even if server forgets to set the flag
in the response) since we don't have anything useful to sign with.
This is especially important now that the more secure SMB3.1.1 protocol
is in the default dialect list.
An earlier patch ("cifs: allow guest mounts to work for smb3.11") fixed
the guest mounts to Windows.
Fixes: 6188f28bf608 ("Tree connect for SMB3.1.1 must be signed for non-encrypted shares")
Reviewed-by: Ronnie Sahlberg <lsahlber@redhat.com>
Reviewed-by: Paulo Alcantara <palcantara@suse.de>
CC: Stable <stable@vger.kernel.org>
Signed-off-by: Steve French <stfrench@microsoft.com>
Diffstat (limited to 'block/blk-softirq.c')
0 files changed, 0 insertions, 0 deletions