Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 15 Aug 2002 19:04:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 15 Aug 2002 19:04:23 -0400 Received: from mons.uio.no ([129.240.130.14]:22698 "EHLO mons.uio.no") by vger.kernel.org with ESMTP id ; Thu, 15 Aug 2002 19:04:23 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15708.13368.625078.207115@charged.uio.no> Date: Fri, 16 Aug 2002 01:07:36 +0200 To: Linus Torvalds Cc: Dax Kelson , Alan Cox , "Kendrick M. Smith" , "linux-kernel@vger.kernel.org" , "nfs@lists.sourceforge.net" , Subject: Re: Will NFSv4 be accepted? In-Reply-To: References: X-Mailer: VM 7.00 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid Reply-To: trond.myklebust@fys.uio.no From: Trond Myklebust Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1020 Lines: 23 >>>>> " " == Linus Torvalds writes: > I personally doubt that NFS would be the thing driving > this. Judging by past performance, NFS security issues don't > seem to bother people. I'd personally assume that the thing > that would be important enough to people for vendors to add it > is VPN or encrypted (local) disks. As I said: one of the main motivations for NFSv4 is WAN support, and in those environments, strong authentication is a must. That said, the plan is to also prepare a 'null' authentication scheme for RPCSEC_GSS (basically using RPCSEC_GSS as a wrapper for AUTH_UNIX) so that the strong auth can be provided as a simple plugin in case its inclusion in the kernel would not be acceptable. Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/