On Oct 22, 2013, at 11:54 PM, Ted Unangst <t...@tedunangst.com> wrote:
> On Tue, Oct 22, 2013 at 22:05, William Orr wrote:
>
>>
>> I guess I misunderstood, as I thought that /dev/random dumped the entropy
>> pool, and that /dev/arandom put the random data through a stream cipher so
>> that grabbing random data would never block.
>
> That was true some time ago, but since at least 2011 everything
> behaves identically to what was once /dev/arandom. Assorted other
> names are kept in /dev for compatibility, their behavior is not
> different.
>
Thanks for the heads up, guess I'm still thinking in terms of Solaris and
Linux. Sorry for the confusion.
That doesn't change that there was a significant time difference between
writing out entropy with and without my driver:
With octrng:
# time dd if=/dev/random of=random/out count=1M
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 354.696 secs (1513605 bytes/sec)
5m59.52s real 0m3.30s user 2m50.23s system
Without octrng:
# time dd if=/dev/random of=random/out count=1M
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 1187.522 secs (452093 bytes/sec)
19m49.70s real 0m2.55s user 1m48.99s system
signature.asc
Description: Message signed with OpenPGP using GPGMail
