From: "J. Bruce Fields" <bfields@fieldses.org>
To: David Greaves <david@dgreaves.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS wiki : NFSv4 Enduser doc kerberos
Date: Tue, 25 May 2010 16:37:42 -0400 [thread overview]
Message-ID: <20100525203742.GL7085@fieldses.org> (raw)
In-Reply-To: <4BFBCF77.2070702@dgreaves.com>
On Tue, May 25, 2010 at 02:24:07PM +0100, David Greaves wrote:
> FYI I've made an attempt to update this page:
> http://wiki.linux-nfs.org/wiki/index.php/Enduser_doc_kerberos
>
> If someone could please take a look and correct any errors I've made that
> would be nice.
>
> Some questions:
> * should a client have an nfs/<fqdn> principal (it works without)
I'm actually not sure what the latest client requires--I thought it
still needed some kind of machine credential on the client.
> * Is the "allow_weak_crypto=true" part still correct?
Yes, unless you're running the very latest (unreleased) upstream kernel
and nfs-utils, which includes support for stronger crypto.
--b.
next prev parent reply other threads:[~2010-05-25 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 13:24 NFS wiki : NFSv4 Enduser doc kerberos David Greaves
2010-05-25 20:37 ` J. Bruce Fields [this message]
2010-05-25 21:02 ` Kevin Coffman
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=20100525203742.GL7085@fieldses.org \
--to=bfields@fieldses.org \
--cc=david@dgreaves.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.