All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	fsverity@lists.linux.dev, apparmor@lists.ubuntu.com,
	Ard Biesheuvel <ardb@kernel.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	John Johansen <john.johansen@canonical.com>
Subject: [GIT PULL] Crypto library conversions for 6.17
Date: Sun, 27 Jul 2025 16:45:42 -0700	[thread overview]
Message-ID: <20250727234542.GC1261@sol> (raw)

Note: this depends on the "Crypto library updates" pull request and
should be merged after it.

The following changes since commit c76ed8790b3018fe36647d9aae96e0373f321184:

  crypto: sha1 - Remove sha1_base.h (2025-07-14 11:28:38 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git tags/libcrypto-conversions-for-linus

for you to fetch changes up to 998646b3c1129188f1fdffac3779feb9708b4b4a:

  fsverity: Switch from crypto_shash to SHA-2 library (2025-07-14 11:29:32 -0700)

----------------------------------------------------------------

Convert fsverity and apparmor to use the SHA-2 library functions
instead of crypto_shash. This is simpler and also slightly faster.

----------------------------------------------------------------
Eric Biggers (3):
      apparmor: use SHA-256 library API instead of crypto_shash API
      fsverity: Explicitly include <linux/export.h>
      fsverity: Switch from crypto_shash to SHA-2 library

 Documentation/filesystems/fsverity.rst |   3 +-
 fs/verity/Kconfig                      |   6 +-
 fs/verity/enable.c                     |   9 +-
 fs/verity/fsverity_private.h           |  24 ++--
 fs/verity/hash_algs.c                  | 194 +++++++++++----------------------
 fs/verity/measure.c                    |   1 +
 fs/verity/open.c                       |  37 +++----
 fs/verity/read_metadata.c              |   1 +
 fs/verity/verify.c                     |   8 +-
 security/apparmor/Kconfig              |   3 +-
 security/apparmor/crypto.c             |  85 ++-------------
 11 files changed, 120 insertions(+), 251 deletions(-)

             reply	other threads:[~2025-07-27 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-27 23:45 Eric Biggers [this message]
2025-07-29  1:12 ` [GIT PULL] Crypto library conversions for 6.17 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=20250727234542.GC1261@sol \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=apparmor@lists.ubuntu.com \
    --cc=ardb@kernel.org \
    --cc=fsverity@lists.linux.dev \
    --cc=john.johansen@canonical.com \
    --cc=linux-crypto@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.