From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
keyrings@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: [GIT PULL] KEYS: keys-next-6.18
Date: Sat, 4 Oct 2025 17:46:43 +0300 [thread overview]
Message-ID: <aOEzU7dRErEmbUqN@kernel.org> (raw)
The following changes since commit fec734e8d564d55fb6bd4909ae2e68814d21d0a1:
Merge tag 'riscv-for-linus-v6.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux (2025-09-26 14:39:12 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/keys-next-6.18
for you to fetch changes up to 8be70a8fc667c33e69257a72e8092f07c828241e:
security: keys: use menuconfig for KEYS symbol (2025-10-04 17:25:35 +0300)
----------------------------------------------------------------
Hi,
A few minor updates/fixes for keys.
BR, Jarkko
----------------------------------------------------------------
Eric Biggers (4):
KEYS: trusted_tpm1: Compare HMAC values in constant time
KEYS: trusted_tpm1: Use SHA-1 library instead of crypto_shash
KEYS: trusted_tpm1: Move private functionality out of public header
KEYS: encrypted: Use SHA-256 library instead of crypto_shash
Randy Dunlap (1):
security: keys: use menuconfig for KEYS symbol
include/keys/trusted_tpm.h | 79 ---------
security/keys/Kconfig | 17 +-
security/keys/encrypted-keys/encrypted.c | 63 ++-----
security/keys/trusted-keys/Kconfig | 5 +-
security/keys/trusted-keys/trusted_tpm1.c | 284 +++++++++++-------------------
5 files changed, 117 insertions(+), 331 deletions(-)
next reply other threads:[~2025-10-04 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 14:46 Jarkko Sakkinen [this message]
2025-10-04 22:30 ` [GIT PULL] KEYS: keys-next-6.18 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=aOEzU7dRErEmbUqN@kernel.org \
--to=jarkko@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@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.