Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 2 Nov 2002 19:59:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 2 Nov 2002 19:59:16 -0500 Received: from oak.sktc.net ([208.46.69.4]:43214 "EHLO oak.sktc.net") by vger.kernel.org with ESMTP id ; Sat, 2 Nov 2002 19:59:16 -0500 Message-ID: <3DC47659.4060006@sktc.net> Date: Sat, 02 Nov 2002 19:05:29 -0600 From: "David D. Hagood" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021012 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Linus Torvalds CC: Rik van Riel , "Theodore Ts'o" , Dax Kelson , Rusty Russell , linux-kernel@vger.kernel.org, davej@suse.de Subject: Re: Filesystem Capabilities in 2.6? References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 657 Lines: 17 Linus Torvalds wrote: > > And pathnames are a _hell_ of a lot better and straightforward interface > than inode numbers are. It's confusing when you change the permission on > one path to notice that another path magically changed too. Would this not allow a user to add permissions to a file, by creating a new directory entry and linking it to an existing inode? Would that not be a greater security hole? - 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/