public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Simo Sorce <simo@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: NeilBrown <neilb@suse.de>, Steve Dickson <SteveD@redhat.com>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] nfs-service: Added the starting of gssproxy
Date: Tue, 23 Sep 2014 12:57:58 -0400	[thread overview]
Message-ID: <20140923125758.3aa66211@willson.usersys.redhat.com> (raw)
In-Reply-To: <20140923161214.GF29932@fieldses.org>

On Tue, 23 Sep 2014 12:12:14 -0400
"J. Bruce Fields" <bfields@fieldses.org> wrote:

> On Tue, Sep 23, 2014 at 12:00:54PM -0400, Simo Sorce wrote:
> > On Tue, 23 Sep 2014 11:20:00 -0400
> > "J. Bruce Fields" <bfields@fieldses.org> wrote:
> > 
> > > On Tue, Sep 23, 2014 at 08:48:54AM -0400, Simo Sorce wrote:
> > > > On Tue, 23 Sep 2014 12:08:04 +1000
> > > > NeilBrown <neilb@suse.de> wrote:
> > > > > I don't think you want an install section.  That means the
> > > > > service has to be explicitly enabled, which is a pain.
> > > > > I think nfs-server.service should Want= this.
> > > > > I also think 
> > > > > 
> > > > >   ConditionPathExists=/etc/krb5.keytab
> > > > > 
> > > > > would be appropriate.
> > > > 
> > > > If GSS-Proxy is in use the administrator may choose to use a
> > > > keytab in a different location, so I am not entirely sure we
> > > > should depend on /etc/krb5.keytab, however it is also ok to
> > > > decide that if the admin wants to use a different place that
> > > > they create a custom unit file. Up to you.
> > > 
> > > Note we're already using the same line in rpc-gssd.service and
> > > rpc-svcgssd.service.
> > > 
> > > Can you suggest a better "does this host have krb5 configured?"
> > > test?
> > > 
> > > I think false positives are OK, but not false negatives.
> > > 
> > > (So, if we run those daemons unnecessarily it may annoy some
> > > people, but if we fail to run them when they're needed then
> > > things really don't work.)
> > 
> > I would simply not test for presence of a keytab if it were my call.
> > 
> > If the admin decided to start nfs-secure I assume he already got the
> > proper key material, ie I am not so sure that double-checking the
> > admin in the unit files is right for gssproxy, because gssproxy has
> > directives that allow the admin to put the keytab elsewhere.
> 
> I believe nfs-secure is being removed (there's none under
> nfs-utils/systemd).
> 
> We'd rather not require unnecessary configuration steps.  Configuring
> NFS and krb5 should be enough.
> 
> So the point is to start the daemons automatically.

I see, I can live with that for now.

Simo.


-- 
Simo Sorce * Red Hat, Inc * New York

  reply	other threads:[~2014-09-23 16:58 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 19:20 [PATCH 0/2] Use the gssproxy damon for GSSAPI credentials (v3) Steve Dickson
2014-09-22 19:20 ` [PATCH 1/2] nfs-service: Added the starting of gssproxy Steve Dickson
2014-09-22 19:26   ` Simo Sorce
2014-09-22 19:43     ` Steve Dickson
2014-09-22 20:44       ` J. Bruce Fields
2014-09-22 21:14         ` Steve Dickson
2014-09-22 21:32           ` Simo Sorce
2014-09-22 22:57             ` Steve Dickson
2014-09-23  0:19               ` Simo Sorce
2014-09-23  1:19                 ` Steve Dickson
2014-09-23 12:52                   ` Simo Sorce
2014-09-23 14:58                     ` Steve Dickson
2014-09-23 15:08                       ` Simo Sorce
2014-09-23 19:29                     ` J. Bruce Fields
2014-09-23 19:40                       ` Simo Sorce
2014-09-23 19:51                         ` J. Bruce Fields
2014-09-22 22:34           ` J. Bruce Fields
2014-09-22 23:58             ` Steve Dickson
2014-09-23  0:26               ` Simo Sorce
2014-09-23  1:55                 ` J. Bruce Fields
2014-09-23  2:08                   ` NeilBrown
2014-09-23  2:11                     ` J. Bruce Fields
2014-09-23 19:23                       ` J. Bruce Fields
2014-09-23 20:17                         ` Steve Dickson
2014-09-23 20:25                           ` J. Bruce Fields
2014-09-23 21:15                             ` Steve Dickson
2014-09-24 15:07                               ` Steve Dickson
2014-09-24 15:15                                 ` J. Bruce Fields
2014-09-24 15:23                                 ` J. Bruce Fields
2014-09-24 15:30                                   ` Steve Dickson
2014-09-23 12:48                     ` Simo Sorce
2014-09-23 15:20                       ` J. Bruce Fields
2014-09-23 16:00                         ` Simo Sorce
2014-09-23 16:12                           ` J. Bruce Fields
2014-09-23 16:57                             ` Simo Sorce [this message]
2014-09-23 12:46                   ` Simo Sorce
2014-09-23 15:06                   ` Steve Dickson
2014-09-23 15:16                     ` J. Bruce Fields
2014-09-23 15:52                       ` Steve Dickson
2014-09-23 16:05                         ` J. Bruce Fields
2014-09-23  2:01             ` NeilBrown
2014-09-22 19:40   ` J. Bruce Fields
2014-09-22 19:46     ` Simo Sorce
2014-09-22 19:53       ` Steve Dickson
2014-09-22 20:00         ` Simo Sorce
2014-09-22 20:02           ` Steve Dickson
2014-09-23  1:42           ` NeilBrown
2014-09-23  2:09             ` J. Bruce Fields
2014-09-23  2:55               ` NeilBrown
2014-09-23 12:45             ` Simo Sorce
2014-09-22 19:20 ` [PATCH 2/2] rpc.svcgssd: the build of rpc.svcgssd is off by default Steve Dickson
2014-09-22 19:43   ` J. Bruce Fields
2014-09-22 19:50     ` Steve Dickson
2014-09-22 20:21       ` 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=20140923125758.3aa66211@willson.usersys.redhat.com \
    --to=simo@redhat.com \
    --cc=SteveD@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    /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