All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS FAQ updates
Date: Sun, 13 Mar 2005 17:19:38 -0500	[thread overview]
Message-ID: <20050313221938.GA13667@fieldses.org> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C61130853986D@lavender-fe.eng.netapp.com>

On Sun, Mar 13, 2005 at 01:41:36PM -0800, Lever, Charles wrote:
> hmmm.  so what's the difference between not having access to a file, and
> having access but not being able to read the file?

I was trying to differentiate between the ability to perform IO to the
file and the ability to just get a filehandle for it, but didn't come up
with a good way to say that....

> is it just the ability to know the file is there?  wouldn't that be
> prevented by not having access to its parent?

Lack of access to the parent doesn't prevent guessing the filehandle of
the children.

> or, since the file handle is still good, lack of permission to look
> the file up in the new parent would be inconsequential?

Right.

Kerberos allows us to trust that the permissions on files will be
enforced, because (under certain assumptions) the server enforcing the
permissions knows who is trying to access files.

But it doesn't do anything in particular to enforce exports.

> to my mind, this is a very fine hair to split.  why, in your opinion, is
> it worth mentioning?  ie do you have a particular case in mind where
> this kind of thing could be important?

Hm.  Someone on a single-user system that just wanted to export their
homework project might assume that they could safely export
/home/joeuser/compsci101/ without needing to tighten down permissions on
the rest of the filesystem, not realizing that this gives anyone in
their Kerberos realm the ability to read any file in their filesystem
that's world-readable.

Thinking about it a little more, I think I'd just leave out discussion
of kerberos from this section.  It really solves a different problem,
and we should still be encouraging people to export only whole
partitions.

--b.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2005-03-13 22:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-13 21:41 NFS FAQ updates Lever, Charles
2005-03-13 22:10 ` Trond Myklebust
2005-03-13 22:45   ` J. Bruce Fields
2005-03-13 22:19 ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-14 18:19 Lever, Charles
2005-03-14 18:25 ` J. Bruce Fields
2005-03-14 17:48 Lever, Charles
2005-03-14 18:09 ` J. Bruce Fields
2005-03-13 19:37 Lever, Charles
2005-03-13 20:05 ` J. Bruce Fields
2004-09-20 18:29 Lever, Charles
2004-08-31 14:11 Lever, Charles
2004-08-31 14:22 ` Quentin Fennessy
2004-08-31 12:36 Lever, Charles
2004-09-01  0:24 ` Greg Banks

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=20050313221938.GA13667@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Charles.Lever@netapp.com \
    --cc=nfs@lists.sourceforge.net \
    /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.