mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@samba.org>
To: "Lorenz Bucher" <Lorenz.Bucher@gmx.de>
Cc: sfrench@samba.org, linux-cifs@vger.kernel.org,
	samba-technical@lists.samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: connect: added option krb5mi which may allow package signing
Date: Thu, 27 Feb 2014 07:03:24 -0800	[thread overview]
Message-ID: <20140227070324.0861fb3a@corrin.poochiereds.net> (raw)
In-Reply-To: <trinity-0877060f-29cb-4f1f-885e-f0d1c09a0a31-1393492393926@3capp-gmx-bs47>

On Thu, 27 Feb 2014 10:13:14 +0100
"Lorenz Bucher" <Lorenz.Bucher@gmx.de> wrote:

> 
>  
>  
> 
> Gesendet: Mittwoch, 26. Februar 2014 um 21:26 Uhr
> Von: "Jeff Layton" <jlayton@samba.org>
> An: "Lorenz Bucher" <Lorenz.Bucher@gmx.de>
> Cc: sfrench@samba.org, linux-cifs@vger.kernel.org, samba-technical@lists.samba.org, linux-kernel@vger.kernel.org
> Betreff: Re: [PATCH] cifs: connect: added option krb5mi which may allow package signing
> On Wed, 26 Feb 2014 14:46:47 +0100
> "Lorenz Bucher" <Lorenz.Bucher@gmx.de> wrote:
> 
> > Solves an issue with dfs where servers using package signing are
> > mixed with servers which don't use package signing.
> >
> > Signed-off-by: Lorenz Bucher <lorenz.bucher@gmx.de>
> > ---
> > fs/cifs/connect.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
> > index 56c152d..9d06dd8 100644
> > --- a/fs/cifs/connect.c
> > +++ b/fs/cifs/connect.c
> > @@ -1104,6 +1104,9 @@ cifs_parse_mount_options(const char *mountdata, const char *devname,
> > if (!value || !*value) {
> > cERROR(1, "no security value specified");
> > continue;
> > + } else if (strnicmp(value, "krb5mi", 6) == 0) {
> > + vol->secFlg |= CIFSSEC_MAY_KRB5 |
> > + CIFSSEC_MAY_SIGN;
> > } else if (strnicmp(value, "krb5i", 5) == 0) {
> > vol->secFlg |= CIFSSEC_MAY_KRB5 |
> > CIFSSEC_MUST_SIGN;
> 
> This looks like it applies to a really old kernel. I think that problem
> was what commit 0b7bc84000d71f3647ca33ab1bf5bd928535c846 was intended
> to fix.
> 
> --
> Jeff Layton <jlayton@samba.org>
> 
> Its the current kernel from LTS Ubuntu 12.04
> 3.2.0-59-generic #90-Ubuntu SMP Tue Jan 7 22:43:51 UTC 2014
> 

Yep, that kernel is pretty old.

You're probably best off asking the ubuntu kernel maintainers to take
that patch (or asking them to backport 0b7bc84000d). It should
be reasonably safe but they'll have to make that call.

-- 
Jeff Layton <jlayton@samba.org>

      reply	other threads:[~2014-02-27 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 13:46 Lorenz Bucher
2014-02-26 20:26 ` Jeff Layton
2014-02-27  9:13   ` Aw: " Lorenz Bucher
2014-02-27 15:03     ` Jeff Layton [this message]

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=20140227070324.0861fb3a@corrin.poochiereds.net \
    --to=jlayton@samba.org \
    --cc=Lorenz.Bucher@gmx.de \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.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

all inboxes | Powered by JetHome®