[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.02.1303201603380.9518@tundra.namei.org>
Date: Wed, 20 Mar 2013 16:07:58 +1100 (EST)
From: James Morris <jmorris@...ei.org>
To: Casey Schaufler <casey@...aufler-ca.com>
cc: Vivek Goyal <vgoyal@...hat.com>, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, zohar@...ux.vnet.ibm.com,
dmitry.kasatkin@...el.com, akpm@...ux-foundation.org,
ebiederm@...ssion.com
Subject: Re: [PATCH 3/4] capability: Create a new capability CAP_SIGNED
On Fri, 15 Mar 2013, Casey Schaufler wrote:
> Capabilities aren't just random attribute bits. They
> indicate that a task has permission to violate a
> system policy (e.g. change the mode bits of a file
> the user doesn't own).
Casey's right here, as well he should be.
--
James Morris
<jmorris@...ei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists