From: NeilBrown <neilb@suse.de>
To: Steve Dickson <SteveD@redhat.com>
Cc: NFS <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH nfs-utils/systemd] systemd: convert secure services to start without explicit configuration.
Date: Fri, 14 Feb 2014 08:52:55 +1100 [thread overview]
Message-ID: <20140214085255.47f84b8b@notabene.brown> (raw)
In-Reply-To: <52FD2017.4050403@RedHat.com>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
On Thu, 13 Feb 2014 14:42:15 -0500 Steve Dickson <SteveD@redhat.com> wrote:
>
>
> On 02/04/2014 10:18 PM, NeilBrown wrote:
> >
> >
> > This patch removes nfs-secure.target.
> > Instead, rpc.gssd and rpc.svcgssd start started if they appear to be needed.
> >
> > For rpc.gssd, this means if the file /etc/krb5.keytab exists.
> > As the only security mechanism supported is krb5, that file must exist
> > for rpc.gssd to be useful. Conversely, if it does exist, it seems very
> > likely that krb5 is configured on the system an may be used for NFS.
> >
> > For rpc.svcgssd, it also means checking if gss-proxy might be performing
> > the equivalent task instead. So we check if it is running, and if the kernel
> > is able to talk to it.
> >
> > Signed-off-by: NeilBrown <neilb@suse.de>
> Committed to the systemd branch of my git tree...
>
> I would like to more testing before I move them on
> to the master branch...
Thanks Steve. And I totally agree with more testing, and also more
development, tidying up, documentation, and integration with "make install".
This is still a WIP and doesn't belong on master yet.
I'll be sending more patches over the coming weeks.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2014-02-13 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 3:18 [PATCH nfs-utils/systemd] systemd: convert secure services to start without explicit configuration NeilBrown
2014-02-13 19:42 ` Steve Dickson
2014-02-13 21:52 ` NeilBrown [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=20140214085255.47f84b8b@notabene.brown \
--to=neilb@suse.de \
--cc=SteveD@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