From: Mimi Zohar <zohar@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] integrity: subsystem fixes for v5.17
Date: Sun, 06 Feb 2022 18:32:45 -0500 [thread overview]
Message-ID: <3a988ebfffe725e3172a6850c3b2b603d16c2330.camel@linux.ibm.com> (raw)
Hi Linus,
These are fixes for recently found bugs. One was found/noticed while
reviewing IMA support for fsverity digests and signatures. Two of them
were found/noticed while working on IMA namespacing. Plus two other bu
gs. All of them are for previous kernel releases.
thanks,
Mimi
The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git tags/integrity-v5.17-fix
for you to fetch changes up to 89677197ae709eb1ab3646952c44f6a171c9e74c:
ima: Do not print policy rule with inactive LSM labels (2022-02-02 11:59:54 -0500)
----------------------------------------------------------------
integrity-v5-17-fix
----------------------------------------------------------------
Eric Biggers (1):
ima: fix reference leak in asymmetric_verify()
Roberto Sassu (1):
ima: Allow template selection with ima_template[_fmt]= after ima_hash=
Stefan Berger (2):
ima: Remove ima_policy file before directory
ima: Do not print policy rule with inactive LSM labels
Xiaoke Wang (1):
integrity: check the return value of audit_log_start()
security/integrity/digsig_asymmetric.c | 15 +++++++++------
security/integrity/ima/ima_fs.c | 2 +-
security/integrity/ima/ima_policy.c | 8 ++++++++
security/integrity/ima/ima_template.c | 10 +++++++---
security/integrity/integrity_audit.c | 2 ++
5 files changed, 27 insertions(+), 10 deletions(-)
next reply other threads:[~2022-02-07 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 23:32 Mimi Zohar [this message]
2022-02-07 20:14 ` 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=3a988ebfffe725e3172a6850c3b2b603d16c2330.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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®