Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 2 Nov 2002 22:44:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 2 Nov 2002 22:44:11 -0500 Received: from waste.org ([209.173.204.2]:9184 "EHLO waste.org") by vger.kernel.org with ESMTP id ; Sat, 2 Nov 2002 22:44:10 -0500 Date: Sat, 2 Nov 2002 21:50:17 -0600 From: Oliver Xymoron To: Linus Torvalds Cc: Alexander Viro , Olaf Dietsche , "Theodore Ts'o" , Dax Kelson , Rusty Russell , linux-kernel@vger.kernel.org, davej@suse.de Subject: Re: Filesystem Capabilities in 2.6? Message-ID: <20021103035017.GD18884@waste.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1245 Lines: 37 On Sat, Nov 02, 2002 at 07:23:11PM -0800, Linus Torvalds wrote: > > On Sat, 2 Nov 2002, Alexander Viro wrote: > > > > that can be done without doing anything to filesystem. > > Namely, turn current "nosuid" of vfsmount into a mask of capabilities. > > Then use bindings instead of links. > > I like that idea. It's very explicit, and clearly name-based, and we do > have 99% of the support for it already. Bindings are cool, but once you start talking about doing a lot of them, they're rather ungainly due to not actually being persisted on the filesystem, no? A better approach is to just make a user-space capabilities-wrapper that's setuid, drops capabilities quickly and safely and calls the real app. Something like: # mv ping ping.real # chmod -s ping.real # mkcapwrap +net_raw ping.real # chmod +s ping # showcapwrap ping invokes /bin/ping grants net_raw # No fs magic, no persistence issues, all user-space. -- "Love the dolphins," she advised him. "Write by W.A.S.T.E.." - 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/