From: Jeremy Allison <jra@samba.org>
To: Steve French <smfrench@austin.rr.com>
Cc: jra@samba.org, samba-technical@samba.org,
linux-cifs-client@lists.samba.org, linux-kernel@vger.kernel.org
Subject: Re: Problem with CIFS
Date: Thu, 19 Aug 2004 13:28:16 -0700 [thread overview]
Message-ID: <20040819202816.GB13368@legion.cup.hp.com> (raw)
In-Reply-To: <1092882981.2822.12.camel@smfhome.smfdom>
On Wed, Aug 18, 2004 at 09:36:21PM -0500, Steve French wrote:
> >Can you show me where the problem is ?
> >Currently in smbd/negprot.c we have :
> >
> > /* do spnego in user level security if the client
> > supports it and we can do encrypted passwords*/
> >
> > if (global_encrypted_passwords_negotiated &&
> > (lp_security() != SEC_SHARE) &&
> > lp_use_spnego() &&
> > (SVAL(inbuf, smb_flg2) & FLAGS2_EXTENDED_SECURITY)) {
> > negotiate_spnego = True;
> > capabilities |= CAP_EXTENDED_SECURITY;
> > }
>
> I think Samba is just missing the else clause in smbd/negprot.c(since
> reply_common sets FLAGS2_EXTENDED_SECURITY otherwise). Something like:
>
> else {
> remove_from_common_flags2(FLAGS2_EXTENDED_SECURITY);
> SSVAL(outbuf,smb_flg2,(SVAL(outbuf,smb_flg2) &
> (~FLAGS2_EXTENDED_SECURITY)));
> }
>
> but in any case I have to workaround it in the Linux cifs client by
> paying more attention to the capability bit than to the actual smb flag
FYI: I just fixed this in the 3.x SVN tree. It won't be in 3.0.6
but should be in 3.0.7 and above. Thanks !
Jeremy.
next prev parent reply other threads:[~2004-08-19 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 2:36 Problem with CIFS Steve French
2004-08-19 20:28 ` Jeremy Allison [this message]
[not found] <20040818120033.9DD101638C1@lists.samba.org>
2004-08-19 10:09 ` Steve French (IBM LTC)
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 10:08 Daniel Paschka
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=20040819202816.GB13368@legion.cup.hp.com \
--to=jra@samba.org \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@samba.org \
--cc=smfrench@austin.rr.com \
/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