Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@redhat.com>,
	"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: long delay when mounting due to SETCLIENTID AUTH_GSS attempts
Date: Fri, 3 May 2013 17:18:10 -0400	[thread overview]
Message-ID: <20130503211810.GF5715@fieldses.org> (raw)
In-Reply-To: <A2E5B3F1-A8F1-4731-A66C-548B9C8FD429@oracle.com>

On Fri, May 03, 2013 at 02:48:59PM -0400, Chuck Lever wrote:
> We should always use krb5i if a GSS context can be established with
> our machine cred.  As I said before, SETCLIENTID and
> GETATTR(fs_locations) really should use an integrity-protecting
> security flavor no matter what flavor is in effect on the mount points
> themselves.

Can you give an example of a threat that could be avoided by this?

My suspicion is that in most cases an attacker with the ability to
subvert auth_sys could *also* DOS gssd, and hence force the fallback to
auth_sys.

krb5i plus a fallback to auth_sys on failure to authenticate doesn't
sound to me much more secure than just auth_sys.

If we really want much security benefit from krb5i on state operations,
I think we need to really *require* krb5i.

So I'm inclined towards Jeff's solution: don't do this unless userspace
somehow affirmatively states that it requires krb5i on state operations.

I agree that we should default to this when we can.  But the way to move
towards that default is then to get distributions to turn on the new
module parm (or whatever it is) by default.  As they do so, they can
also ensure that e.g. gssd is started.

--b.

> > Instead of using AUTH_GSS for SETCLIENTID by default, would it make
> > sense to add a switch (module parm?) that turns it on so that it can be
> > an opt-in thing rather than doing this by default?
> 
> Why add another tunable when we really should just fix the delay?
> 
> Besides, if gssd is running and no keytab exists, then the fallback to AUTH_SYS should be fast. Is that not an effective workaround until we address the delay problem?
> 
> -- 
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
> 
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-05-03 21:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 17:25 long delay when mounting due to SETCLIENTID AUTH_GSS attempts Jeff Layton
2013-05-03 17:56 ` Chuck Lever
2013-05-03 18:24   ` Jeff Layton
2013-05-03 18:33     ` Myklebust, Trond
2013-05-03 18:44       ` Jeff Layton
2013-05-03 18:48         ` Chuck Lever
2013-05-03 19:17           ` Jeff Layton
2013-05-03 19:26             ` Chuck Lever
2013-05-03 19:39               ` Jeff Layton
2013-05-05 22:49                 ` Chuck Lever
2013-05-03 21:18           ` J. Bruce Fields [this message]
2013-05-03 21:50             ` Chuck Lever
2013-05-06 22:33               ` Chuck Lever
2013-05-07 21:02                 ` J. Bruce Fields
2013-05-07 21:21                   ` Chuck Lever
2013-05-07 21:26                     ` J. Bruce Fields
2013-05-07 21:36                   ` Myklebust, Trond
2013-05-07 21:44                     ` J. Bruce Fields
2013-05-07 20:53               ` J. Bruce Fields
2013-05-07 21:00                 ` Jeff Layton
2013-05-07 21:27                 ` Chuck Lever

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=20130503211810.GF5715@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.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