Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964877AbbBBSsM (ORCPT ); Mon, 2 Feb 2015 13:48:12 -0500 Received: from e23smtp09.au.ibm.com ([202.81.31.142]:58546 "EHLO e23smtp09.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752822AbbBBSsI (ORCPT ); Mon, 2 Feb 2015 13:48:08 -0500 Message-ID: <1422902826.30131.38.camel@dhcp-9-2-203-236.watson.ibm.com> Subject: Re: [capabilities] Allow normal inheritance for a configurable set of capabilities From: Mimi Zohar To: Serge Hallyn Cc: Casey Schaufler , Christoph Lameter , Serge Hallyn , Andy Lutomirski , Jonathan Corbet , Aaron Jones , "Ted Ts'o" , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, akpm@linuxfoundation.org Date: Mon, 02 Feb 2015 13:47:06 -0500 In-Reply-To: <20150202180806.GE24351@ubuntumail> References: <54CFB9B8.8020701@schaufler-ca.com> <20150202180806.GE24351@ubuntumail> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4 (3.6.4-3.fc18) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15020218-0033-0000-0000-00000101FFF3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1557 Lines: 34 On Mon, 2015-02-02 at 18:08 +0000, Serge Hallyn wrote: > Quoting Casey Schaufler (casey@schaufler-ca.com): > > I'm game to participate in such an effort. The POSIX scheme > > is workable, but given that it's 20 years old and hasn't > > developed real traction it's hard to call it successful. > > Over the years we've several times discussed possible reasons for this > and how to help. I personally think it's two things: 1. lack of > toolchain and fs support. The fact that we cannot to this day enable > ping using capabilities by default because of cpio, tar and non-xattr > filesystems is disheartening. We're working on resolving the CPIO issue. tar currently supports xattrs. At this point, how many non-xattr filesystems are there really? Mimi > 2. It's hard for users and applications > to know what caps they need. yes the API is a bear to use, but we can > hide that behind fancier libraries. But using capabilities requires too > much in-depth knowledge of precisely what caps you might need for > whatever operations library may now do when you asked for something. > -- > To unsubscribe from this list: send the line "unsubscribe linux-security-module" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- 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/