cifs: Fix regression during share-level security mounts (Repost)
NTLM response length was changed to 16 bytes instead of 24 bytes that are sent in Tree Connection Request during share-level security share mounts. Revert it back to 24 bytes. Reported-and-Tested-by: Grzegorz Ozanski <grzegorz.ozanski@intel.com> Acked-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Shirish Pargaonkar <shirishpargaonkar@gmail.com> Acked-by: Suresh Jayaraman <sjayaraman@suse.de> Cc: stable@kernel.org Signed-off-by: Steve French <sfrench@us.ibm.com>
This commit is contained in:
parent
1cd3508d5e
commit
540b2e3777
1 changed files with 2 additions and 2 deletions
|
@ -2927,7 +2927,7 @@ CIFSTCon(unsigned int xid, struct cifsSesInfo *ses,
|
||||||
bcc_ptr++; /* skip password */
|
bcc_ptr++; /* skip password */
|
||||||
/* already aligned so no need to do it below */
|
/* already aligned so no need to do it below */
|
||||||
} else {
|
} else {
|
||||||
pSMB->PasswordLength = cpu_to_le16(CIFS_SESS_KEY_SIZE);
|
pSMB->PasswordLength = cpu_to_le16(CIFS_AUTH_RESP_SIZE);
|
||||||
/* BB FIXME add code to fail this if NTLMv2 or Kerberos
|
/* BB FIXME add code to fail this if NTLMv2 or Kerberos
|
||||||
specified as required (when that support is added to
|
specified as required (when that support is added to
|
||||||
the vfs in the future) as only NTLM or the much
|
the vfs in the future) as only NTLM or the much
|
||||||
|
@ -2945,7 +2945,7 @@ CIFSTCon(unsigned int xid, struct cifsSesInfo *ses,
|
||||||
#endif /* CIFS_WEAK_PW_HASH */
|
#endif /* CIFS_WEAK_PW_HASH */
|
||||||
SMBNTencrypt(tcon->password, ses->server->cryptkey, bcc_ptr);
|
SMBNTencrypt(tcon->password, ses->server->cryptkey, bcc_ptr);
|
||||||
|
|
||||||
bcc_ptr += CIFS_SESS_KEY_SIZE;
|
bcc_ptr += CIFS_AUTH_RESP_SIZE;
|
||||||
if (ses->capabilities & CAP_UNICODE) {
|
if (ses->capabilities & CAP_UNICODE) {
|
||||||
/* must align unicode strings */
|
/* must align unicode strings */
|
||||||
*bcc_ptr = 0; /* null byte password */
|
*bcc_ptr = 0; /* null byte password */
|
||||||
|
|
Loading…
Add table
Reference in a new issue