From: Ian Kent Subject: Re: direct mount from NFS-mounted directories issue Date: Thu, 08 Mar 2007 19:46:04 +0900 Message-ID: <1173350764.3467.7.camel@raven.themaw.net> References: <45ED676E.8020904@inria.fr> <1173200232.3629.27.camel@raven.themaw.net> <45EE859D.8020407@inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45EE859D.8020407@inria.fr> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autofs-bounces@linux.kernel.org Errors-To: autofs-bounces@linux.kernel.org To: autofs@linux.kernel.org On Wed, 2007-03-07 at 10:27 +0100, Guillaume Rousse wrote: > 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 ? Maybe but the criticism was that autofs was attempting to create remote directories "at all". Is it such a big ask that if mounts within remote filesystems have mount point directories already? Ian