Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 3 Nov 2002 10:06:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 3 Nov 2002 10:06:31 -0500 Received: from quechua.inka.de ([193.197.184.2]:4567 "EHLO mail.inka.de") by vger.kernel.org with ESMTP id ; Sun, 3 Nov 2002 10:06:30 -0500 From: Bernd Eckenfels To: linux-kernel@vger.kernel.org Subject: Re: Filesystem Capabilities in 2.6? In-Reply-To: X-Newsgroups: ka.lists.linux.kernel User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (Linux/2.0.39 (i686)) Message-Id: Date: Sun, 3 Nov 2002 16:13:03 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 852 Lines: 18 In article you 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. *Note* - binary _is_ marked suid, > mask tells which capabilities _not_ to gain. the suid bit is important, I agree. this will make most security checks not fail. Problem: runtime checks depend on euid. PErhaps we should even return a different effective uid (or 0?) if a program is runnign with increased capabilities? Greetings Bernd - 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/