From: Mimi Zohar <zohar@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
linux-integrity <linux-integrity@vger.kernel.org>
Subject: [GIT PULL] integrity subsystem fixes for v5.2
Date: Fri, 31 May 2019 11:58:45 -0400 [thread overview]
Message-ID: <1559318325.4280.13.camel@linux.ibm.com> (raw)
Hi Linus,
Included in this pull request are four bug fixes, which are not
specific to 5.2. The first two are related to the architecture
specific IMA policy support. The other two patches, one is related to
EVM signatures, based on additional hash algorithms, and the other is
related to displaying the IMA policy.
At least Scott's patch should have been included in the last open
window, but I sent the v5.2 pull request a bit earlier than normal.
thanks,
Mimi
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-fixes-for-5.2-rc
for you to fetch changes up to 8cdc23a3d9ec0944000ad43bad588e36afdc38cd:
ima: show rules with IMA_INMASK correctly (2019-05-29 23:18:25 -0400)
----------------------------------------------------------------
Petr Vorel (1):
ima: fix wrong signed policy requirement when not appraising
Roberto Sassu (2):
evm: check hash algorithm passed to init_desc()
ima: show rules with IMA_INMASK correctly
Scott Wood (1):
x86/ima: Check EFI_RUNTIME_SERVICES before using
arch/x86/kernel/ima_arch.c | 5 +++++
security/integrity/evm/evm_crypto.c | 3 +++
security/integrity/ima/ima_policy.c | 28 ++++++++++++++++------------
3 files changed, 24 insertions(+), 12 deletions(-)
next reply other threads:[~2019-05-31 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 15:58 Mimi Zohar [this message]
2019-05-31 18:15 ` [GIT PULL] integrity subsystem fixes for v5.2 pr-tracker-bot
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=1559318325.4280.13.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.