From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Dax Kelson <dax@gurulabs.com>
Cc: torvalds@transmeta.com, "Kendrick M. Smith" <kmsmith@umich.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: Will NFSv4 be accepted?
Date: 15 Aug 2002 00:17:10 +0200 [thread overview]
Message-ID: <shs8z39dr15.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0208141435210.30333-100000@mooru.gurulabs.com>
>>>>> " " == Dax Kelson <dax@gurulabs.com> writes:
> I for one would REALLY like to see NFSv4 (actually, Kerberized
> NFSv4 is what I'm after). I just finished setting up a
> Kerberized Solaris NFS environment with home directories
> automounted from the clients with strong user authentication.
> Frankly, the stock (non-Kerberized) NFS security model blows.
Note: The RPCSEC_GSS (and accompanying kerberos) stuff is completely
independent of NFSv4. It is still in the process of being finalized,
but when it is, it will apply to NFSv2/v3 as well as v4.
RPCSEC_GSS is not an argument for NFSv4...
Cheers,
Trond
next prev parent reply other threads:[~2002-08-14 22:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 23:01 patch 14/38: CLIENT: add ->setup_read() nfs_rpc_op for async read, part 1 Kendrick M. Smith
2002-08-14 20:49 ` Will NFSv4 be accepted? Dax Kelson
2002-08-14 22:17 ` Trond Myklebust [this message]
2002-08-14 22:34 ` [NFS] " Brian Pawlowski
2002-08-14 23:21 ` Alexander Viro
2002-08-15 1:10 ` Alan Cox
2002-08-15 6:18 ` marius aamodt eriksen
2002-08-15 11:08 ` Alan Cox
2002-08-15 6:23 ` marius aamodt eriksen
2002-08-15 14:19 ` Trond Myklebust
2002-08-15 1:09 ` Alan Cox
2002-08-15 1:27 ` Dax Kelson
2002-08-15 1:35 ` Alan Cox
2002-08-15 1:51 ` Dax Kelson
2002-08-15 4:07 ` J. Bruce Fields
2002-08-15 17:35 ` Linus Torvalds
2002-08-15 18:20 ` Dax Kelson
2002-08-15 19:52 ` Roger Luethi
2002-08-15 23:07 ` Trond Myklebust
2002-08-16 14:54 ` Oliver Xymoron
2002-08-16 19:44 ` Linus Torvalds
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=shs8z39dr15.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=dax@gurulabs.com \
--cc=kmsmith@umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=torvalds@transmeta.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