From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-efi@vger.kernel.org, linux-crypto@vger.kernel.org,
patches@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH v2 0/5] Use EFI variables for random seed
Date: Fri, 18 Nov 2022 14:32:34 +0100 [thread overview]
Message-ID: <20221118133239.2515648-1-Jason@zx2c4.com> (raw)
EFI has a rather unique benefit that it has access to some limited
non-volatile storage, where the kernel can store a random seed. This
series wires that up, with EFISTUB reading the seed and passing it to
the kernel, and with the kernel writing a new seed when the RNG is
initialized.
Patches 1 and 2 are to go through Ard's EFI tree, while patches 3, 4,
and 5 are to go through my RNG tree.
Jason A. Donenfeld (5):
efi: vars: prohibit reading random seed variables
efi: stub: use random seed from EFI variable
random: add back async readiness notifier
vsprintf: initialize siphash key using notifier
efi: random: refresh non-volatile random seed when RNG is initialized
drivers/char/random.c | 20 +++++++++
drivers/firmware/efi/efi.c | 19 +++++++++
drivers/firmware/efi/libstub/random.c | 59 +++++++++++++++++++++------
fs/efivarfs/inode.c | 4 ++
fs/efivarfs/super.c | 3 ++
include/linux/efi.h | 1 +
include/linux/random.h | 1 +
lib/vsprintf.c | 14 +++----
8 files changed, 100 insertions(+), 21 deletions(-)
--
2.38.1
next reply other threads:[~2022-11-18 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 13:32 Jason A. Donenfeld [this message]
2022-11-18 13:32 ` [PATCH v2 1/5] efi: vars: prohibit reading random seed variables Jason A. Donenfeld
2022-11-18 13:32 ` [PATCH v2 2/5] efi: stub: use random seed from EFI variable Jason A. Donenfeld
2022-11-18 13:32 ` [PATCH v2 3/5] random: add back async readiness notifier Jason A. Donenfeld
2022-11-18 13:32 ` [PATCH v2 4/5] vsprintf: initialize siphash key using notifier Jason A. Donenfeld
2022-11-18 13:32 ` [PATCH v2 5/5] efi: random: refresh non-volatile random seed when RNG is initialized Jason A. Donenfeld
2022-11-22 13:39 ` Ard Biesheuvel
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=20221118133239.2515648-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
/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