From: marius aamodt eriksen <marius@umich.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Brian Pawlowski <beepy@netapp.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
dax@gurulabs.com, Linus Torvalds <torvalds@transmeta.com>,
kmsmith@umich.edu, linux-kernel@vger.kernel.org,
nfs@lists.sourceforge.net
Subject: Re: [NFS] Re: Will NFSv4 be accepted?
Date: Thu, 15 Aug 2002 02:18:48 -0400 [thread overview]
Message-ID: <20020815061848.GA9122@umich.edu> (raw)
In-Reply-To: <1029373829.28240.16.camel@irongate.swansea.linux.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> [020814 21:13]:
> On Wed, 2002-08-14 at 23:34, Brian Pawlowski wrote:
> > 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.
>
> ACL works in NFSv2 and nicely in NFSv3 - again the problems Linux has
> are the client failing to respect basic NFS rules of operation.
there is no over-the-wire specification for sending or receving ACLs
on NFSv{2,3} - hence the server may choose to obey them, but an
arbitrary client cannot set them, or view them.
marius.
--
> marius@umich.edu > http://www.citi.umich.edu/u/marius
next prev parent reply other threads:[~2002-08-15 6:14 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 ` [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 [this message]
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=20020815061848.GA9122@umich.edu \
--to=marius@umich.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=beepy@netapp.com \
--cc=dax@gurulabs.com \
--cc=kmsmith@umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marius@citi.umich.edu \
--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