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>
Subject: [GIT PULL] integrity: subsystem fixes for v5.18
Date: Mon, 21 Mar 2022 14:37:53 -0400	[thread overview]
Message-ID: <a47c4a2bdc27d1a66ae09b9a07a851d6b27e6a5c.camel@linux.ibm.com> (raw)

Hi Linus,

Except for extending the "encrypted" key type to support user provided
data, the rest is code cleanup, __setup() usage bug fix, and a trivial
change.

thanks,

Mimi


The following changes since commit 754e0b0e35608ed5206d6a67a791563c631cec07:

  Linux 5.17-rc4 (2022-02-13 12:13:30 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 4a48b4c428dc92b5e0b19de83e7eb8d530dddd48:

  MAINTAINERS: add missing security/integrity/platform_certs (2022-02-28 21:08:54 -0500)

----------------------------------------------------------------
integrity-v5.18

----------------------------------------------------------------
Austin Kim (1):
      ima: Fix trivial typos in the comments

Mimi Zohar (4):
      MAINTAINERS: add missing "security/integrity" directory
      ima: rename IMA_ACTION_FLAGS to IMA_NONACTION_FLAGS
      ima: define ima_max_digest_data struct without a flexible array variable
      MAINTAINERS: add missing security/integrity/platform_certs

Randy Dunlap (1):
      EVM: fix the evm= __setup handler return value

Stefan Berger (1):
      ima: Return error code obtained from securityfs functions

Yael Tzur (1):
      KEYS: encrypted: Instantiate key with user-provided decrypted data

 Documentation/security/keys/trusted-encrypted.rst | 25 ++++++--
 MAINTAINERS                                       | 11 ++++
 security/integrity/evm/evm_main.c                 |  2 +-
 security/integrity/ima/ima_api.c                  | 12 ++--
 security/integrity/ima/ima_fs.c                   | 31 +++++++---
 security/integrity/ima/ima_init.c                 |  5 +-
 security/integrity/ima/ima_main.c                 |  9 +--
 security/integrity/ima/ima_policy.c               |  4 +-
 security/integrity/ima/ima_template_lib.c         |  7 +--
 security/integrity/integrity.h                    | 14 ++++-
 security/keys/Kconfig                             | 19 ++++--
 security/keys/encrypted-keys/encrypted.c          | 71 +++++++++++++++++------
 12 files changed, 146 insertions(+), 64 deletions(-)


             reply	other threads:[~2022-03-21 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 18:37 Mimi Zohar [this message]
2022-03-22  3:56 ` 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=a47c4a2bdc27d1a66ae09b9a07a851d6b27e6a5c.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®