From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: direct mount from NFS-mounted directories issue
Date: Wed, 07 Mar 2007 10:27:57 +0100 [thread overview]
Message-ID: <45EE859D.8020407@inria.fr> (raw)
In-Reply-To: <1173200232.3629.27.camel@raven.themaw.net>
Ian Kent wrote:
> This behavior was changed because the NFS client in recent kernels
> return EACCESS before it returned EEXIST. It would have been fine to
> just use stat(2) and then create the mount point directory but that
> attracted much criticism regarding the security aspects of "root" owned
> code to attempting to create directories on a remote NFS server. And so
> this is the way it is now.
I'm not a security expert, but it seems for me than allowing root owned
code to create anything on the server is rather a question of
configuring the export writability and trustability on root uid than
enforcing it on client side. Anyway, could the client behaviour be
configurable also, with current (secure) behaviour as default ?
next prev parent reply other threads:[~2007-03-07 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 13:06 direct mount from NFS-mounted directories issue Guillaume Rousse
2007-03-06 16:57 ` Ian Kent
2007-03-07 9:27 ` Guillaume Rousse [this message]
2007-03-08 10:46 ` Ian Kent
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=45EE859D.8020407@inria.fr \
--to=guillaume.rousse@inria.fr \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.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.