All of lore.kernel.org
 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>
Subject: [GIT PULL] integrity: susbystem updates for v6.7
Date: Tue, 31 Oct 2023 10:38:46 -0400	[thread overview]
Message-ID: <205e07e901e695f4986bf0e4071168302fbf59bc.camel@linux.ibm.com> (raw)

Hi Linus,

Four integrity changes: two IMA-overlay updates, an integrity Kconfig
cleanup, and a secondary keyring update.

Stephen Rothwell is carrying an overlay merge conflict resolution:
https://lore.kernel.org/linux-next/20231027131137.3051da98@canb.auug.org.au/

thanks,

Mimi

The following changes since commit 94f6f0550c625fab1f373bb86a6669b45e9748b3:

  Linux 6.6-rc5 (2023-10-08 13:49:43 -0700)

are available in the Git repository at:

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

for you to fetch changes up to b836c4d29f2744200b2af41e14bf50758dddc818:

  ima: detect changes to the backing overlay file (2023-10-31 08:22:36 -0400)

----------------------------------------------------------------
integrity-v6.7

----------------------------------------------------------------
Amir Goldstein (1):
      ima: annotate iint mutex to avoid lockdep false positive warnings

Mimi Zohar (2):
      certs: Only allow certs signed by keys on the builtin keyring
      ima: detect changes to the backing overlay file

Prasad Pandit (1):
      integrity: fix indentation of config attributes

 certs/Kconfig                     | 16 ++++++++++++-
 crypto/asymmetric_keys/restrict.c |  4 ++++
 fs/overlayfs/super.c              |  2 +-
 security/integrity/Kconfig        | 44 +++++++++++++++++------------------
 security/integrity/iint.c         | 48 ++++++++++++++++++++++++++++++---------
 security/integrity/ima/ima_api.c  |  5 ++++
 security/integrity/ima/ima_main.c | 16 ++++++++++++-
 security/integrity/integrity.h    |  2 ++
 8 files changed, 101 insertions(+), 36 deletions(-)


             reply	other threads:[~2023-10-31 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 14:38 Mimi Zohar [this message]
2023-11-02 18:37 ` [GIT PULL] integrity: susbystem updates for v6.7 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=205e07e901e695f4986bf0e4071168302fbf59bc.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 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.