From: matthias.bgg at kernel.org <matthias.bgg@kernel.org>
To: u-boot@lists.denx.de
Subject: [PATCH 0/2] Use RNG to get random behaviour
Date: Wed, 16 Dec 2020 11:41:15 +0100 [thread overview]
Message-ID: <20201216104117.10836-1-matthias.bgg@kernel.org> (raw)
From: Matthias Brugger <mbrugger@suse.com>
For now bootp and uuid code use a weak seed for generating random data.
U-Boot as support for RNG devices now, so we should change to code to
use them if they are present. This will help mitigate issues like seen
in CVE-2019-11690.
Matthias Brugger (2):
lib: uuid: use RNG device if present
net: Use NDRNG device in srand_mac()
lib/uuid.c | 20 +++++++++++++++++---
net/net_rand.h | 18 +++++++++++++++++-
2 files changed, 34 insertions(+), 4 deletions(-)
--
2.29.2
next reply other threads:[~2020-12-16 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 10:41 matthias.bgg at kernel.org [this message]
2020-12-16 10:41 ` [PATCH 1/2] lib: uuid: use RNG device if present matthias.bgg at kernel.org
2020-12-16 13:22 ` Torsten Duwe
2020-12-16 10:41 ` [PATCH 2/2] net: Use NDRNG device in srand_mac() matthias.bgg at kernel.org
2020-12-16 13:20 ` Torsten Duwe
2020-12-16 15:56 ` Matthias Brugger
2020-12-16 13:17 ` [PATCH 0/2] Use RNG to get random behaviour Torsten Duwe
2020-12-16 13:42 ` Peter Robinson
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=20201216104117.10836-1-matthias.bgg@kernel.org \
--to=matthias.bgg@kernel.org \
--cc=u-boot@lists.denx.de \
/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