[148051] in cryptography@c2.net mail archive
Re: [Cryptography] randomness +- entropy
daemon@ATHENA.MIT.EDU (Matt Johnston)
Wed Nov 6 14:02:39 2013
X-Original-To: cryptography@metzdowd.com
Date: Wed, 6 Nov 2013 20:55:06 +0800
From: Matt Johnston <matt@ucc.asn.au>
To: Theodore Ts'o <tytso@mit.edu>
Mail-Followup-To: Theodore Ts'o <tytso@mit.edu>,
John Kelsey <crypto.jmk@gmail.com>,
Watson Ladd <watsonbladd@gmail.com>,
Cryptography <cryptography@metzdowd.com>,
RNG mlist <rng@lists.bitrot.info>, John Denker <jsd@av8n.com>
In-Reply-To: <20131105230949.GF14235@thunk.org>
Cc: John Kelsey <crypto.jmk@gmail.com>, Watson Ladd <watsonbladd@gmail.com>,
Cryptography <cryptography@metzdowd.com>,
RNG mlist <rng@lists.bitrot.info>, John Denker <jsd@av8n.com>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
On Tue, Nov 05, 2013 at 06:09:49PM -0500, Theodore Ts'o wrote:
> I could add an ioctl which returns the state of the pool initialized
> flag, or which blocked until the pool is considered initialized, but
> I'm not convinced that enough programs would really use it. And if I
As a small data point, I'd use it. At first boot a SSH
server could slowly poll the ioctl in the background until
it's ready, then generate host keys. Saves having a delay on
first connection which will lead to mystified users.
I don't know if it would get used at a system level - for
upstart/systemd/whatever they'd probably prefer something
they wait for asynchronously?
Of course the systems that most need it probably won't get a
bleeding edge kernel for quite a while :-\
Cheers,
Matt
Dropbear SSH developer
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
