From: Mimi Zohar <zohar@linux.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: [GIT PULL] linux-integrity patches for Linux 5.2
Date: Thu, 11 Apr 2019 21:21:29 -0400 [thread overview]
Message-ID: <1555032089.4914.4.camel@linux.ibm.com> (raw)
Hi James,
This pull request contains just three patches, the remainder are
either included in other pull requests (eg. audit, lockdown) or will
be upstreamed via other subsystems (eg. kselftests, Power). Included
in this pull request is one bug fix, one documentation update, and
extending the x86 IMA arch policy rules to coordinate the different
kernel module signature verification methods.
Thanks,
Mimi
The following changes since commit 8d93e952fba216cd0811247f6360d97e0465d5fc:
LSM: lsm_hooks.h: fix documentation format (2019-03-26 16:46:22 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity-for-james
for you to fetch changes up to 41475a3ebaceb270e47a77356ddc30960354cb00:
doc/kernel-parameters.txt: Deprecate ima_appraise_tcb (2019-04-10 16:41:01 -0400)
----------------------------------------------------------------
Mimi Zohar (2):
x86/ima: require signed kernel modules
x86/ima: add missing include
Petr Vorel (1):
doc/kernel-parameters.txt: Deprecate ima_appraise_tcb
Documentation/admin-guide/kernel-parameters.txt | 5 ++---
arch/x86/kernel/ima_arch.c | 10 +++++++++-
include/linux/module.h | 5 +++++
kernel/module.c | 5 +++++
4 files changed, 21 insertions(+), 4 deletions(-)
next reply other threads:[~2019-04-12 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 1:21 Mimi Zohar [this message]
2019-04-12 22:22 ` [GIT PULL] linux-integrity patches for Linux 5.2 James Morris
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=1555032089.4914.4.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).