From: "Serge E. Hallyn" <serge.hallyn@canonical.com>
To: Eric Paris <eparis@parisplace.org>
Cc: Eric Paris <eparis@redhat.com>,
"Andrew G. Morgan" <morgan@kernel.org>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>,
Steve Grubb <sgrubb@redhat.com>,
"Serge E. Hallyn" <serge@canonical.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] System Wide Capability Bounding Set
Date: Mon, 14 Feb 2011 15:24:53 -0600 [thread overview]
Message-ID: <20110214212453.GA6582@localhost> (raw)
In-Reply-To: <AANLkTin701rA70UzDYK21nSmUAYz62Xg=-Rtxg8nebWw@mail.gmail.com>
Quoting Eric Paris (eparis@parisplace.org):
> On Mon, Feb 7, 2011 at 9:55 PM, Eric Paris <eparis@redhat.com> wrote:
> >
> > Below is what I'm working on. I've asked dhowells to review the creds
> > code, since commit_creds() does not take const. Maybe that's just an
> > oversight. Basically I've exposed two new sysctls.
> >
> > /proc/sys/kernel/usermodehelper/bset
> > /proc/sys/kernel/usermodehelper/inheritable
> >
> > You must have CAP_SYS_MODULE to change these (changes are &= ONLY).
> > When the kernel launches a usermodehelper it will do so with these as
> > the bset and pI. I haven't attempted securebits and uid (since I didn't
> > really need them I don't think) But will if anyone can think of a use
> > case.
> >
> > Is this what you were thinking?
>
>
> Anything? Problems with this patch/approach?
Sorry, I've just not had a chance to take a close enough look. I'll
try to do so tonight.
-serge
next prev parent reply other threads:[~2011-02-14 21:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 22:25 [PATCH] System Wide Capability Bounding Set Eric Paris
2011-01-06 11:30 ` Tetsuo Handa
2011-01-06 16:44 ` Theodore Tso
2011-01-11 22:02 ` Serge E. Hallyn
2011-01-11 22:12 ` Serge E. Hallyn
2011-01-14 19:50 ` Eric Paris
2011-01-17 3:16 ` Andrew G. Morgan
2011-01-21 21:25 ` Eric Paris
2011-01-23 3:39 ` Andrew G. Morgan
2011-01-24 21:40 ` Serge Hallyn
2011-01-26 23:34 ` Eric Paris
2011-01-27 14:02 ` Serge E. Hallyn
2011-01-27 14:42 ` Steve Grubb
2011-01-27 16:43 ` Andrew G. Morgan
[not found] ` <AANLkTi=k5QeE_-iNuW3-M5K3BnBtRxk-QYO5624HKrpE@mail.gmail.com>
2011-01-27 16:50 ` Steve Grubb
2011-01-28 18:19 ` Eric Paris
2011-01-28 18:49 ` Serge E. Hallyn
2011-01-28 19:10 ` Steve Grubb
2011-01-28 19:38 ` Serge E. Hallyn
2011-01-28 22:24 ` Eric Paris
2011-02-01 18:17 ` Eric Paris
2011-02-01 21:26 ` Serge E. Hallyn
2011-02-02 4:02 ` Andrew G. Morgan
2011-02-08 2:55 ` Eric Paris
2011-02-14 20:45 ` Eric Paris
2011-02-14 21:24 ` Serge E. Hallyn [this message]
2011-02-18 0:29 ` Serge E. Hallyn
2011-01-27 14:26 ` Andrew G. Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110214212453.GA6582@localhost \
--to=serge.hallyn@canonical.com \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=serge@canonical.com \
--cc=sgrubb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.