All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martijn de Gouw <martijn.de.gouw-BHYAuTpL47qEVqv0pETR8A@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/1] cifs: set MAY_SIGN when sec=krb5
Date: Wed, 13 Feb 2013 15:55:05 +0100	[thread overview]
Message-ID: <511BA949.2020100@prodrive.nl> (raw)
In-Reply-To: <CAH2r5mvc6tYze0TC2Ets9=7Fg5b3OJTk_dyONTvYLxswt1jN7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 02/01/2013 06:51 AM, Steve French wrote:
> I would like to trace this to check - I will try to resetup some DFS
> share referrals tomorrow

Did you manage to trace to check this?

>
> On Thu, Jan 31, 2013 at 8:31 AM, Martijn de Gouw
> <martijn.de.gouw-BHYAuTpL47qEVqv0pETR8A@public.gmane.org> wrote:
>>
>> On 01/31/2013 05:53 AM, Steve French wrote:
>>>
>>> On Wed, Oct 24, 2012 at 4:45 AM, Martijn de Gouw
>>> <martijn.de.gouw-BHYAuTpL47qEVqv0pETR8A@public.gmane.org> wrote:
>>>>
>>>> Setting this secFlg allows usage of dfs where some servers require
>>>> signing and others don't.
>>>>
>>>> Signed-off-by: Martijn de Gouw <martijn.de.gouw-BHYAuTpL47qEVqv0pETR8A@public.gmane.org>
>>>> ---
>>>> :100644 100644 b39bb4a... 4da9dd3... M  fs/cifs/connect.c
>>>>    fs/cifs/connect.c |    2 +-
>>>>    1 files changed, 1 insertions(+), 1 deletions(-)
>>>>
>>>> diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
>>>> index b39bb4a..4da9dd3 100644
>>>> --- a/fs/cifs/connect.c
>>>> +++ b/fs/cifs/connect.c
>>>> @@ -994,7 +994,7 @@ static int cifs_parse_security_flavors(char *value,
>>>>
>>>>           switch (match_token(value, cifs_secflavor_tokens, args)) {
>>>>           case Opt_sec_krb5:
>>>> -               vol->secFlg |= CIFSSEC_MAY_KRB5;
>>>> +               vol->secFlg |= CIFSSEC_MAY_KRB5 | CIFSSEC_MAY_SIGN;
>>>>                   break;
>>>>           case Opt_sec_krb5i:
>>>>                   vol->secFlg |= CIFSSEC_MAY_KRB5 | CIFSSEC_MUST_SIGN;
>>>
>>>
>>> Wouldn't this same problem occur if ntlm or ntlmv2 were authenticated
>>> and a dfs referral sent us to a server which required signing - if
>>> that is the case then it is not just Opt_sec_krb5 which needs to OR in
>>> CIFSSEC_MAY_SIGN but also Opt_sec_ntlmssp and Opt_ntlm (also why do we
>>> call this Opt_ntlm instead of Opt_sec_ntlm like the other 10?) and
>>> Opt_sec_ntlmv2?
>>>
>>>
>>
>> Using sec=ntlm on the same dfs I did not see this problem. So I guess not.
>>
>>
>> --
>> Martijn de Gouw
>> Engineer
>> Prodrive B.V.
>> Mobile: +31 63 17 76 161
>> Phone:  +31 40 26 76 200
>
>
>
>
> --
> Thanks,
>
> Steve
>

Regards,
Martijn
-- 
Martijn de Gouw
Engineer
Prodrive B.V.
Mobile: +31 63 17 76 161
Phone:  +31 40 26 76 200

  parent reply	other threads:[~2013-02-13 14:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24  9:45 [PATCH 1/1] cifs: set MAY_SIGN when sec=krb5 Martijn de Gouw
     [not found] ` <1351071946-21458-1-git-send-email-martijn.de.gouw-BHYAuTpL47qEVqv0pETR8A@public.gmane.org>
2012-10-24 11:37   ` Jeff Layton
     [not found]     ` <20121024073723.2e5063db-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-01-30 19:03       ` Martijn de Gouw
2013-01-31  4:53   ` Steve French
     [not found]     ` <CAH2r5muToSW5VW3KkazpakQdPBb3ptC0a75FK1+KswzVAvCCkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-31 14:31       ` Martijn de Gouw
     [not found]         ` <510A802A.5000904-BHYAuTpL47qEVqv0pETR8A@public.gmane.org>
2013-02-01  5:51           ` Steve French
     [not found]             ` <CAH2r5mvc6tYze0TC2Ets9=7Fg5b3OJTk_dyONTvYLxswt1jN7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-13 14:55               ` Martijn de Gouw [this message]
     [not found]                 ` <511BA949.2020100-BHYAuTpL47qEVqv0pETR8A@public.gmane.org>
2013-02-14  5:58                   ` Steve French

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=511BA949.2020100@prodrive.nl \
    --to=martijn.de.gouw-bhyautpl47qevqv0petr8a@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.