public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Simo Sorce <simo@redhat.com>
Cc: Steve Dickson <SteveD@redhat.com>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/2] Use the gssproxy damon for GSSAPI credentials
Date: Fri, 19 Sep 2014 14:11:22 -0400	[thread overview]
Message-ID: <20140919181122.GC16658@fieldses.org> (raw)
In-Reply-To: <20140919130752.2ac3372e@willson.usersys.redhat.com>

On Fri, Sep 19, 2014 at 01:07:52PM -0400, Simo Sorce wrote:
> On Fri, 19 Sep 2014 12:36:17 -0400
> "J. Bruce Fields" <bfields@fieldses.org> wrote:
> 
> > On Fri, Sep 19, 2014 at 12:31:17PM -0400, Steve Dickson wrote:
> > > 
> > > 
> > > On 09/19/2014 11:57 AM, J. Bruce Fields wrote:
> > > > On Fri, Sep 19, 2014 at 08:51:41AM -0400, Steve Dickson wrote:
> > > >> The gssproxy(8) daemon is now how the managing of GSSAPI 
> > > >> credentials should be done. 
> > > >>
> > > >> These to patches has the nfs-server systemd script start 
> > > >> gssproxy instead of rpc.svcgssd and removes the building 
> > > >> and installation of rpc.svcgssd.
> > > >>
> > > >> For now I'm leaving the source files... Just in case... ;-)
> > > > 
> > > > If nothing else, we'd like to keep support for older kernels for a
> > > > while.
> > > Good point... I should probably make this a configurable...
> > > something like --enable_svcgssd and have it off by default...
> > 
> > Sounds fine.
> 
> +1, it will be very useful for transitions in distributions, not all of
> them will align identically I guess.

If we wanted to be *very* nice, we could try to detect and run one or
the other at run-time.  It's nice for people trying to boot old kernels
to track down (probably unrelated) regressions.  But I think it would be
too complicated.

It might be simple enough for gss-proxy to log some kind of warning when
it starts up on an old kernel.

--b.

  reply	other threads:[~2014-09-19 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 12:51 [PATCH 0/2] Use the gssproxy damon for GSSAPI credentials Steve Dickson
2014-09-19 12:51 ` [PATCH 1/2] nfs-server: Replace rpc.svcgssd with gssproxy Steve Dickson
2014-09-19 12:51 ` [PATCH 2/2] svcgssd: Remove rules from the Makefile.am Steve Dickson
2014-09-19 15:57 ` [PATCH 0/2] Use the gssproxy damon for GSSAPI credentials J. Bruce Fields
2014-09-19 16:31   ` Steve Dickson
2014-09-19 16:36     ` J. Bruce Fields
2014-09-19 17:07       ` Simo Sorce
2014-09-19 18:11         ` J. Bruce Fields [this message]
2014-09-19 18:15           ` Simo Sorce

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=20140919181122.GC16658@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=simo@redhat.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