public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] um: seed rng using host OS rng
Date: Wed, 13 Jul 2022 09:03:31 +0200	[thread overview]
Message-ID: <9a028efb77ae662fe8eabcf2ffb5a64214f07418.camel@sipsolutions.net> (raw)
In-Reply-To: <d20a629c-8c15-ca8a-c34a-c5c084dbee03@cambridgegreys.com>

On Wed, 2022-07-13 at 07:58 +0100, Anton Ivanov wrote:
> 
> IIRC UML RNG device reads directly from host.

Yes, but that's a /dev/hwrng device, so you still need some userspace to
feed entropy from that into /dev/random.

> If you are using UMLs own /dev/random you are effectively using the host 
> one.

> So unless I am mistaken, you need extra randomness only if you do not 
> have UMLs /dev/random compiled in.

No, neither of those is true.

johannes



  reply	other threads:[~2022-07-13  7:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 23:27 [PATCH] um: seed rng using host OS rng Jason A. Donenfeld
2022-07-13  6:58 ` Anton Ivanov
2022-07-13  7:03   ` Johannes Berg [this message]
2022-07-13  7:05 ` Johannes Berg
2022-07-13  9:53   ` Jason A. Donenfeld
2022-07-13  9:58     ` [PATCH v2] " Jason A. Donenfeld
2022-07-17  8:46       ` [PATCH v3] " Jason A. Donenfeld
2022-07-17 10:50         ` [PATCH v4] " Jason A. Donenfeld
2022-07-17 10:51           ` Johannes Berg
2022-07-13  7:06 ` [PATCH] " Anton Ivanov

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=9a028efb77ae662fe8eabcf2ffb5a64214f07418.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Jason@zx2c4.com \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=stable@vger.kernel.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