From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Charles Lever <Charles.Lever@netapp.com>, nfs@lists.sourceforge.net
Subject: Re: NFS FAQ updates
Date: Sun, 13 Mar 2005 17:45:22 -0500 [thread overview]
Message-ID: <20050313224522.GB13667@fieldses.org> (raw)
In-Reply-To: <1110751811.23876.19.camel@lade.trondhjem.org>
On Sun, Mar 13, 2005 at 05:10:11PM -0500, Trond Myklebust wrote:
> The subtree_check option attempts to decide whether or not a file lies
> within an exported subtree. If you turn it off, then people can
> theoretically try to guess filehandles and gain access to the files
> (assuming the access permissions on the file itself allow that).
I wouldn't put too much emphasis on that "theoretically". The root
directory on all my ext2/3 filesystems has inode number 2, and as far as
I can tell guessing the rest of the rest of the filehandle just comes
down to guessing the root device, which on my machines is always
/dev/hdaN for some very small N. Add a few more for people with scsi
and so on, and I bet you could cover most linux NFS servers with a dozen
guesses. Now just lookup and readdir down to wherever you want. Am I
missing anything here?
If the administrator tightened down directory permissions a bit, you'll
be forced to guess filehandles for objects deeper in the filesystem,
which may be a little harder. I wouldn't count on it.
--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
next prev parent reply other threads:[~2005-03-13 22:44 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 [this message]
2005-03-13 22:19 ` J. Bruce Fields
-- 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=20050313224522.GB13667@fieldses.org \
--to=bfields@fieldses.org \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--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 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.