[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6038462.HIH9pGNYO7@positron.chronox.de>
Date: Tue, 21 Jun 2016 19:23:19 +0200
From: Stephan Mueller <smueller@...onox.de>
To: "Austin S. Hemmelgarn" <ahferroin7@...il.com>
Cc: Tomas Mraz <tmraz@...hat.com>, Theodore Ts'o <tytso@....edu>,
David Jaša <djasa@...hat.com>,
Andi Kleen <andi@...stfloor.org>, sandyinchina@...il.com,
Jason Cooper <cryptography@...edaemon.net>,
John Denker <jsd@...n.com>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
Joe Perches <joe@...ches.com>, Pavel Machek <pavel@....cz>,
George Spelvin <linux@...izon.com>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/5] /dev/random - a new approach
Am Dienstag, 21. Juni 2016, 13:18:33 schrieb Austin S. Hemmelgarn:
Hi Austin,
> > You have to trust the host for anything, not just for the entropy in
> > timings. This is completely invalid argument unless you can present a
> > method that one guest can manipulate timings in other guest in such a
> > way that _removes_ the inherent entropy from the host.
>
> When dealing with almost any type 2 hypervisor, it is fully possible for
> a user other than the one running the hypervisor to manipulate
> scheduling such that entropy is reduced. This does not imply that the
Please re-read the document: Jitter RNG does not rest on scheduling.
Ciao
Stephan
Powered by blists - more mailing lists