From: Steve Dickson <SteveD@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: ANNOUNCE: nfs-utils-1.3.1 released.
Date: Fri, 26 Sep 2014 10:05:07 -0400 [thread overview]
Message-ID: <54257293.2060604@RedHat.com> (raw)
Hello,
The major feature in this release is the addition
of gssproxy support in the systemd scripts.
When gssproxy is installed and and a key tab
(/etc/krb5.keytab) exists, the gssproxy daemon
will be started and the NFS server will use
that daemon to manage the GSSAPI creds instead
of rpc.svcgssd.
Rpc.svcgssd will continue to be used when gssproxy
does not exist and a key tab does.
One thing not addressed in this release is the tcp wrapper
changes to the mountd man page. I'm going to let distros
deal with that as they may.... I'm in favor of ripping
all that code out, but I didn't want that to get in the
way of this release.
The tarballs can be found in
http://kernel.org/pub/linux/utils/nfs-utils/1.3.1/
or
http://sourceforge.net/projects/nfs/files/nfs-utils/1.3.1
The change log is in
http://kernel.org/pub/linux/utils/nfs-utils/1.3.1/1.3.1-ChangeLog
or
http://sourceforge.net/projects/nfs/files/nfs-utils/1.3.1/
The git tree is at:
git://linux-nfs.org/nfs-utils
Please send comments/bugs to linux-nfs@vger.kernel.org
steved.
reply other threads:[~2014-09-26 14:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54257293.2060604@RedHat.com \
--to=steved@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--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