From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frank Cusack Subject: Re: nfs root directory security Date: Wed, 18 Jun 2003 14:16:15 -0700 Sender: nfs-admin@lists.sourceforge.net Message-ID: <20030618141615.A22386@google.com> References: <1055946469.16259.81.camel@sleerssen.racemi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Bogdan Costescu , Neil Brown , nfs@lists.sourceforge.net Return-path: Received: from 216-239-45-4.google.com ([216.239.45.4]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 19SkIK-0006E0-00 for ; Wed, 18 Jun 2003 14:16:40 -0700 To: Scott Leerssen In-Reply-To: <1055946469.16259.81.camel@sleerssen.racemi.com>; from scott@leerssen.com on Wed, Jun 18, 2003 at 10:27:50AM -0400 Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: On Wed, Jun 18, 2003 at 10:27:50AM -0400, Scott Leerssen wrote: > I agree with everything you say here, and in a controlled and fairly > unchanging environment with clients you trust, exporting to specific > clients is a perfectly acceptable solution. The only solution. What you need to do is automate, not obfuscate. /fc ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs