From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] security subsystem: Integrity updates for v4.19
Date: Thu, 16 Aug 2018 08:48:59 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1808160842350.19586@namei.org> (raw)
From Mimi Zohar:
"This pull request adds support for EVM signatures based on larger
digests, contains a new audit record AUDIT_INTEGRITY_POLICY_RULE to
differentiate the IMA policy rules from the IMA-audit messages,
addresses two deadlocks due to either loading or searching for crypto
algorithms, and cleans up the audit messages."
The following changes since commit 87ea58433208d17295e200d56be5e2a4fe4ce7d6:
security: check for kstrdup() failure in lsm_append() (2018-07-17 21:27:06 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-integrity
for you to fetch changes up to 3dd0f18c70d94ca2432c78c5735744429f071b0b:
EVM: fix return value check in evm_write_xattrs() (2018-07-22 14:49:11 -0400)
----------------------------------------------------------------
Matthew Garrett (2):
evm: Don't deadlock if a crypto algorithm is unavailable
evm: Allow non-SHA1 digital signatures
Mikhail Kurinnoi (1):
integrity: prevent deadlock during digsig verification.
Stefan Berger (4):
ima: Call audit_log_string() rather than logging it untrusted
ima: Use audit_log_format() rather than audit_log_string()
ima: Do not audit if CONFIG_INTEGRITY_AUDIT is not set
ima: Differentiate auditing policy rules from "audit" actions
Sudeep Holla (1):
integrity: silence warning when CONFIG_SECURITYFS is not enabled
Wei Yongjun (1):
EVM: fix return value check in evm_write_xattrs()
crypto/api.c | 2 +-
include/linux/crypto.h | 5 ++++
include/linux/integrity.h | 13 +++++++++
include/uapi/linux/audit.h | 1 +
security/integrity/digsig_asymmetric.c | 23 ++++++++++++++++
security/integrity/evm/Kconfig | 1 +
security/integrity/evm/evm.h | 10 +++++--
security/integrity/evm/evm_crypto.c | 50 ++++++++++++++++++----------------
security/integrity/evm/evm_main.c | 19 ++++++++-----
security/integrity/evm/evm_secfs.c | 4 +--
security/integrity/iint.c | 9 ++++--
security/integrity/ima/Kconfig | 1 +
security/integrity/ima/ima_policy.c | 9 ++++--
security/integrity/integrity.h | 15 ++++++++++
security/integrity/integrity_audit.c | 6 +---
security/security.c | 7 ++++-
16 files changed, 128 insertions(+), 47 deletions(-)
reply other threads:[~2018-08-15 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LRH.2.21.1808160842350.19586@namei.org \
--to=jmorris@namei.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 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®