mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] hwrng: dev-random: always use /dev/urandom
Date: Wed, 23 Oct 2019 09:07:09 +0200	[thread overview]
Message-ID: <20191023070709.dqsg5msny5tyi7e4@pengutronix.de> (raw)
In-Reply-To: <20191021122047.12204-1-a.fatoum@pengutronix.de>

On Mon, Oct 21, 2019 at 02:20:46PM +0200, Ahmad Fatoum wrote:
> /dev/random can block long after boot time. It seems there's a consensus
> that /dev/urandom is safe to use except for very early boot, which isn't
> when barebox sandbox is usually run. To make the HWRNG more useful,
> always use /dev/urandom.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  arch/sandbox/board/dev-random.c                | 7 +------
>  arch/sandbox/mach-sandbox/include/mach/linux.h | 1 -
>  drivers/hw_random/Kconfig                      | 6 +++---
>  3 files changed, 4 insertions(+), 10 deletions(-)

Applied, thanks

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2019-10-23  7:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 12:20 Ahmad Fatoum
2019-10-21 12:20 ` [PATCH 2/2] commands: passwd: suggest sandbox for offline password generation Ahmad Fatoum
2019-10-23  7:07 ` Sascha Hauer [this message]

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=20191023070709.dqsg5msny5tyi7e4@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox