mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Roberto Sassu <roberto.sassu@huaweicloud.com>
Subject: [GIT PULL] integrity: subsystem fixes for v6.18
Date: Fri, 03 Oct 2025 15:45:56 -0400	[thread overview]
Message-ID: <235aaef81ca206c9ac1f69ece17dd9a15f826d85.camel@linux.ibm.com> (raw)

Hi Linus,

There's just a couple of changes: 2 crypto code cleanup and 1 IMA xattr bug fix.

thanks,

Mimi

The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:

  Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git/ tags/integrity-v6.18

for you to fetch changes up to 88b4cbcf6b041ae0f2fc8a34554a5b6a83a2b7cd:

  ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr (2025-10-03 07:50:56 -0400)

----------------------------------------------------------------
integrity-v6.18

----------------------------------------------------------------
Coiby Xu (1):
      ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr

Eric Biggers (2):
      integrity: Select CRYPTO from INTEGRITY_ASYMMETRIC_KEYS
      lib/digsig: Use SHA-1 library instead of crypto_shash

 lib/Kconfig                           |  3 +--
 lib/digsig.c                          | 46 +++++------------------------------
 security/integrity/Kconfig            |  1 +
 security/integrity/ima/ima_appraise.c | 23 ++++++++++++++----
 4 files changed, 26 insertions(+), 47 deletions(-)


             reply	other threads:[~2025-10-03 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 19:45 Mimi Zohar [this message]
2025-10-05 19:45 ` 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=235aaef81ca206c9ac1f69ece17dd9a15f826d85.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roberto.sassu@huaweicloud.com \
    --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®