[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABsxX9JWK1qVubuYt0+HoZy-Lhz0kp6a3MxyT7ny5YzLS2rMJQ@mail.gmail.com>
Date: Fri, 18 May 2012 16:09:15 -0700
From: "Kok, Auke-jan H" <auke-jan.h.kok@...el.com>
To: richard -rw- weinberger <richard.weinberger@...il.com>
Cc: Serge Hallyn <serge.hallyn@...onical.com>,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, Eric Paris <eparis@...hat.com>
Subject: Re: [PATCH] Trace event for capable().
On Fri, May 18, 2012 at 3:33 PM, richard -rw- weinberger
<richard.weinberger@...il.com> wrote:
>
> On Thu, May 17, 2012 at 9:50 PM, Auke Kok <auke-jan.h.kok@...el.com>
> wrote:
> > Add a simple trace event for capable().
> >
> > There's been a lot of discussion around capable(), and there
> > are plenty of tools to help reduce capabilities' usage from
> > userspace. A major gap however is that it's almost impossible
> > to see or verify which bits are requested from either userspace
> > or in the kernel.
> >
> > This patch adds a minimal tracer that will print out which
> > CAPs are requested and whether the request was granted.
>
> Can we please have support for user namespaces?
> At least idicate whether the current namespace is init_user_ns or not.
that was the main reason for sending this out already - that should be
trivial to add to the trace event, but I haven't looked at namespaces
yet myself. I'll check it out.
Auke
--
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