linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Lukas Hejtmanek <xhejtman@ics.muni.cz>,
	Zdenek Salvet <salvet@ics.muni.cz>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 backchannel authentication
Date: Thu, 9 Aug 2012 12:38:46 -0400	[thread overview]
Message-ID: <20120809163846.GA8230@fieldses.org> (raw)
In-Reply-To: <1344529851.25447.33.camel@lade.trondhjem.org>

On Thu, Aug 09, 2012 at 04:30:53PM +0000, Myklebust, Trond wrote:
> On Thu, 2012-08-09 at 18:28 +0200, Lukas Hejtmanek wrote:
> > On Thu, Aug 09, 2012 at 03:53:01PM +0000, Myklebust, Trond wrote:
> > > How is this any different to requiring that the user start rpc.statd
> > > before launching an NFSv3 mount? Just document the requirement if it
> > > isn't already clear enough, and we can move on.
> > > 
> > > The other source of confusion here, was that the rpc.svcgssd was
> > > delivered through a nfs-kernel-server package, which indicates that we
> > > first and foremost need to educate the distro packagers.
> > 
> > hmm, if both rpc.gssd and rpc.svcgssd are needed on clients and servers, isn't
> > it worth of merging them into a single process?
> 
> You don't need rpc.gssd to use rpcsec_gss with NFSv3, nor do you need it
		 ^^^^^^^^

You meant rpc.svcgssd, unless you were thinking about the nfsd side.

> if you're not intending on using delegations with NFSv4.

Though the default should be to support delegations.

--b.

  reply	other threads:[~2012-08-09 16:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 13:55 NFSv4 backchannel authentication Lukas Hejtmanek
2012-08-07 15:41 ` J. Bruce Fields
2012-08-07 15:59   ` Myklebust, Trond
2012-08-07 16:12     ` Lukas Hejtmanek
2012-08-08  7:58     ` Zdenek Salvet
2012-08-08 13:18       ` Myklebust, Trond
2012-08-09  8:06         ` Zdenek Salvet
2012-08-09 14:45           ` J. Bruce Fields
2012-08-09 15:53             ` Myklebust, Trond
2012-08-09 16:28               ` Lukas Hejtmanek
2012-08-09 16:30                 ` Myklebust, Trond
2012-08-09 16:38                   ` J. Bruce Fields [this message]
2012-08-09 16:49                     ` Myklebust, Trond
2012-08-09 16:50               ` J. Bruce Fields
2012-08-09 17:58                 ` Zdenek Salvet
2012-08-09 18:01                 ` [PATCH] README: note gssd/svcgssd may be needed on both sides J. Bruce Fields
2012-08-10  5:20               ` NFSv4 backchannel authentication NeilBrown
2012-08-10 17:23                 ` J. Bruce Fields

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=20120809163846.GA8230@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=salvet@ics.muni.cz \
    --cc=xhejtman@ics.muni.cz \
    /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;
as well as URLs for NNTP newsgroup(s).