From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Takashi Iwai <tiwai@suse.de>
Subject: [PULL] fw-restrict update (3.17)
Date: Fri, 25 Jul 2014 11:50:48 -0700 [thread overview]
Message-ID: <20140725185048.GA27939@www.outflux.net> (raw)
Hi James,
Please pull these fw-restrict changes for 3.17. Thanks!
-Kees
The following changes since commit 7d8b6c63751cfbbe5eef81a48c22978b3407a3ad:
CAPABILITIES: remove undefined caps from all processes (2014-07-24 21:53:47 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/fw-restrict-3.17
for you to fetch changes up to 5a9196d715607f76d6b7d96a0970d6065335e62b:
ima: add support for measuring and appraising firmware (2014-07-25 11:47:46 -0700)
----------------------------------------------------------------
Firmware validation hooks
----------------------------------------------------------------
Kees Cook (2):
security: introduce kernel_fw_from_file hook
firmware_class: perform new LSM checks
Mimi Zohar (1):
ima: add support for measuring and appraising firmware
Documentation/ABI/testing/ima_policy | 4 +++-
drivers/base/firmware_class.c | 30 ++++++++++++++++++++++++++----
include/linux/ima.h | 6 ++++++
include/linux/security.h | 17 +++++++++++++++++
security/capability.c | 6 ++++++
security/integrity/ima/ima.h | 3 ++-
security/integrity/ima/ima_appraise.c | 8 ++++++++
security/integrity/ima/ima_main.c | 11 +++++++++++
security/integrity/ima/ima_policy.c | 7 +++++++
security/integrity/integrity.h | 9 +++++++--
security/security.c | 11 +++++++++++
11 files changed, 104 insertions(+), 8 deletions(-)
--
Kees Cook
Chrome OS Security
next reply other threads:[~2014-07-25 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 18:50 Kees Cook [this message]
2014-08-05 21:46 ` Kees Cook
2014-08-05 22:59 ` Mimi Zohar
2014-08-05 23:39 ` Kees Cook
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=20140725185048.GA27939@www.outflux.net \
--to=keescook@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=zohar@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®