All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Tangnianyao <tangnianyao@huawei.com>,
	Will Deacon <will@kernel.org>,
	oliver.upton@linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
	"guoyang (C)" <guoyang2@huawei.com>
Subject: Re: Question on get random long worse in VM than on host
Date: Sat, 31 Aug 2024 09:14:20 +0100	[thread overview]
Message-ID: <86y14dun1f.wl-maz@kernel.org> (raw)
In-Reply-To: <CAMj1kXGocnZPe4EfzsB6xd2QZacp-a45R5f5f6FDpVtVEXCcGQ@mail.gmail.com>

On Sat, 31 Aug 2024 08:56:23 +0100,
Ard Biesheuvel <ardb@kernel.org> wrote:
> 
> As for RNDR/RNDRRS vs TRNG: the former is not a raw entropy source, it
> is a DRBG (or CSPRNG) which provides cryptographically secure random
> numbers whose security strength is limited by the size of the seed.
> TRNG does not have this limitation in principle, although non-p KVM
> happily seeds it from the kernel's entropy pool, which has the same
> limitation in practice.

Is that something we should address? I assume that this has an impact
on the quality of the provided random numbers?

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2024-08-31  8:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31  3:34 Question on get random long worse in VM than on host Tangnianyao
2024-08-31  7:42 ` Marc Zyngier
2024-08-31  7:56   ` Ard Biesheuvel
2024-08-31  8:14     ` Marc Zyngier [this message]
2024-09-02 21:26       ` Ard Biesheuvel
2024-09-03  1:39         ` Tangnianyao
2024-09-03 15:04           ` Ard Biesheuvel
2024-09-05  3:12             ` Tangnianyao
2024-09-05  8:17               ` Marc Zyngier
2024-09-06  3:42                 ` Tangnianyao

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=86y14dun1f.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=ardb@kernel.org \
    --cc=guoyang2@huawei.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=tangnianyao@huawei.com \
    --cc=will@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 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.