From: Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org>
To: Shirish Pargaonkar
<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Amit Haval (India Bangalore)"
<amit.haval-ZIEO9HjW1UBWk0Htik3J/w@public.gmane.org>
Subject: Re: Problem with connecting to SMB server in 3.9.11 kernel.
Date: Mon, 03 Feb 2014 09:54:11 -0800 [thread overview]
Message-ID: <52EFD7C3.9020505@candelatech.com> (raw)
In-Reply-To: <CADT32eL4na+eduUmmWKHe5usN+S2aN+mCUQqU5j8RHaq-3ZVwQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 01/26/2014 10:07 PM, Shirish Pargaonkar wrote:
> Can you try this patch and see if it works?
We have verified that this works in our test systems.
We are just passing user=foo,password=bar in our
mount options, so hopefully that is sufficient to exercise this
code?
Thanks,
Ben
> diff --git a/fs/cifs/sess.c b/fs/cifs/sess.c
> index e87387d..ac14d71 100644
> --- a/fs/cifs/sess.c
> +++ b/fs/cifs/sess.c
> @@ -450,9 +450,8 @@ int build_ntlmssp_auth_blob(unsigned char *pbuffer,
> sec_blob->WorkstationName.MaximumLength = 0;
> tmp += 2;
>
> - if (((ses->ntlmssp->server_flags & NTLMSSP_NEGOTIATE_KEY_XCH) ||
> - (ses->ntlmssp->server_flags & NTLMSSP_NEGOTIATE_EXTENDED_SEC))
> - && !calc_seckey(ses)) {
> + if ((ses->ntlmssp->server_flags & NTLMSSP_NEGOTIATE_KEY_XCH) &&
> + !calc_seckey(ses)) {
> memcpy(tmp, ses->ntlmssp->ciphertext, CIFS_CPHTXT_SIZE);
> sec_blob->SessionKey.BufferOffset = cpu_to_le32(tmp - pbuffer);
> sec_blob->SessionKey.Length = cpu_to_le16(CIFS_CPHTXT_SIZE);
--
Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-02-03 17:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 17:17 Problem with connecting to SMB server in 3.9.11 kernel Ben Greear
[not found] ` <52DAB72C.9030305-my8/4N5VtI7c+919tysfdA@public.gmane.org>
2014-01-20 12:56 ` Jeff Layton
[not found] ` <20140120075657.0e61ecb2-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2014-01-20 13:47 ` Tom Talpey
[not found] ` <fb5a5a794f9d46ffb3bafd4a7f9f5a88-GeMU99GfrruUGfbpEvpFbeO6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2014-01-20 15:15 ` Amit Haval (India Bangalore)
2014-01-20 15:54 ` Shirish Pargaonkar
[not found] ` <CADT32eK5_duGPjJy2Q=2-SOfN1R+Msx10RJ7wk+Zzsz+xt_-Rw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-20 17:34 ` Amit Haval (India Bangalore)
[not found] ` <0DF7592FDA7A4C428E3B3D14C1D69BDAADCF8D-CrrBPKKMyPMSwlxDF3k49UfXCdDtWGEhlw3VODuhjLzR7s880joybQ@public.gmane.org>
2014-01-21 3:12 ` Shirish Pargaonkar
[not found] ` <CADT32eKGPu_3bNRL9bar+3RO74KXD=YKQvsC49635drWFL+63A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-24 5:41 ` Ben Greear
[not found] ` <52E1FCF4.5040504-my8/4N5VtI7c+919tysfdA@public.gmane.org>
2014-01-25 15:03 ` Shirish Pargaonkar
2014-01-26 14:04 ` Shirish Pargaonkar
2014-01-27 6:07 ` Shirish Pargaonkar
[not found] ` <CADT32eL4na+eduUmmWKHe5usN+S2aN+mCUQqU5j8RHaq-3ZVwQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-03 17:54 ` Ben Greear [this message]
[not found] ` <52EFD7C3.9020505-my8/4N5VtI7c+919tysfdA@public.gmane.org>
2014-02-03 17:59 ` Steve French
2014-02-03 18:51 ` Shirish Pargaonkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52EFD7C3.9020505@candelatech.com \
--to=greearb-my8/4n5vti7c+919tysfda@public.gmane.org \
--cc=amit.haval-ZIEO9HjW1UBWk0Htik3J/w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox