mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Pawlowski <beepy@netapp.com>
To: trond.myklebust@fys.uio.no (Trond Myklebust)
Cc: dax@gurulabs.com, torvalds@transmeta.com, kmsmith@umich.edu,
	linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] Re: Will NFSv4 be accepted?
Date: Wed, 14 Aug 2002 15:34:57 -0700 (PDT)	[thread overview]
Message-ID: <200208142234.g7EMYvQ21700@tooting-fe.eng> (raw)
In-Reply-To: <shs8z39dr15.fsf@charged.uio.no> from Trond Myklebust at "Aug 15, 2 00:17:10 am"

> RPCSEC_GSS is not an argument for NFSv4...

yes.

But ACL support over the wire is an argument for V4 - and fine grained
authorization coupled to strong authentication makes for a flexible 
security package.

  reply	other threads:[~2002-08-14 22:31 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
2002-08-14 22:34     ` Brian Pawlowski [this message]
2002-08-14 23:21       ` [NFS] " 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=200208142234.g7EMYvQ21700@tooting-fe.eng \
    --to=beepy@netapp.com \
    --cc=dax@gurulabs.com \
    --cc=kmsmith@umich.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=torvalds@transmeta.com \
    --cc=trond.myklebust@fys.uio.no \
    /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

all inboxes | Powered by JetHome®