From: Mike Waychison <mikew@google.com>
To: "Andrew G. Morgan" <agm@google.com>,
Maximilian Attems <max@stro.at>,
Eric Northup <digitaleric@google.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: Eric Paris <eparis@parisplace.org>,
klibc@zytor.com, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] Support dropping of capabilities from early userspace.
Date: Tue, 19 Jul 2011 13:38:43 -0700 [thread overview]
Message-ID: <20110719203843.646.73383.stgit@mike2.sea.corp.google.com> (raw)
This patchset applies to klibc mainline. As is it will probably collide
with Maximilian's recent patch to rename run-init to switch_root posted
last week.
To boot an untrusted environment with certain capabilities locked out,
we'd like to be able to drop the capabilities up front from early
userspace, before we actually transition onto the root volume.
This patchset implements this by adding a "drop capabilities" ability to
both kinit and run-init in the klibc package. For kinit, it now
understands a new kernel command line option, "drop_capabilities" that
specifies a comma separated list of capability names that should be
dropped right before execing the next init binary on the next root
device.
run-init also has the ability to use this drop_capabilities function by
specifying capabilities that should be dropped with a new command line
flag, '-d'.
Given that this patchset is meant to help secure boots, we treat any
errors as total failure to boot by exiting the process with a failing
exit code.
Thanks,
Mike Waychison
Related discussions
===================
- Thread discussing my wanting to compile out kernel interfaces that
we do not want to expose to the userspace environment, with Alan
Cox convincing me that I really just want to disable certain
capabilities:
https://lkml.org/lkml/2011/7/15/412
Patchset summary
================
syscalls: Add capset and capget
run-init: Add drop_capabilities support.
next reply other threads:[~2011-07-19 20:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 20:38 Mike Waychison [this message]
2011-07-19 20:38 ` [PATCH v1 1/2] syscalls: Add capset and capget Mike Waychison
2011-07-29 20:41 ` Maximilian Attems
2011-07-29 23:06 ` Maximilian Attems
2011-07-19 20:38 ` [PATCH v1 2/2] run-init: Add drop_capabilities support Mike Waychison
2011-07-29 20:45 ` Maximilian Attems
2011-07-29 20:46 ` Mike Waychison
2011-08-02 21:09 ` Maximilian Attems
2011-08-02 21:42 ` Mike Waychison
2011-08-02 22:50 ` Andrew G. Morgan
2011-08-02 22:56 ` Mike Waychison
2011-08-02 23:37 ` Mike Waychison
2011-08-03 0:48 ` H. Peter Anvin
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=20110719203843.646.73383.stgit@mike2.sea.corp.google.com \
--to=mikew@google.com \
--cc=agm@google.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=digitaleric@google.com \
--cc=eparis@parisplace.org \
--cc=hpa@zytor.com \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome