All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@kernel.org>
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.6
Date: Thu, 20 Feb 2020 14:46:03 -0500	[thread overview]
Message-ID: <1582227963.19057.17.camel@kernel.org> (raw)

Hi Linus,

Here are two bug fixes and an associated change for each.  The one
that adds SM3 to the IMA list of supported hash algorithms is a simple
change, but could be considered a new feature.

thanks,

Mimi


The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:

  Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity

for you to fetch changes up to 5780b9abd530982c2bb1018e2c52c05ab3c30b45:

  ima: add sm3 algorithm to hash algorithm configuration list (2020-02-18 07:35:49 -0500)

----------------------------------------------------------------
Ard Biesheuvel (1):
      x86/ima: use correct identifier for SetupMode variable

Javier Martinez Canillas (1):
      efi: Only print errors about failing to get certs if EFI vars are found

Tianjia Zhang (2):
      crypto: rename sm3-256 to sm3 in hash_algo_name
      ima: add sm3 algorithm to hash algorithm configuration list

 arch/x86/kernel/ima_arch.c                    |  6 ++--
 crypto/hash_info.c                            |  2 +-
 security/integrity/ima/Kconfig                |  5 ++++
 security/integrity/platform_certs/load_uefi.c | 40 +++++++++++++++++----------
 4 files changed, 34 insertions(+), 19 deletions(-)

             reply	other threads:[~2020-02-20 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 19:46 Mimi Zohar [this message]
2020-02-21 20:00 ` [GIT PULL] integrity subsystem fixes for v5.6 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=1582227963.19057.17.camel@kernel.org \
    --to=zohar@kernel.org \
    --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.