From: Rob Kendrick <rjek@rjek.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Bought an "entropy-key" - very happy
Date: Fri, 26 Mar 2010 15:19:05 +0000 [thread overview]
Message-ID: <20100326151905.55ba1743@trite.i.flarn.net.i.flarn.net> (raw)
In-Reply-To: <20100326141518.GN10118@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
On Fri, 26 Mar 2010 09:15:19 -0500
Brian Kroth <bpkroth@gmail.com> wrote:
> This probably won't actually happen until some distant point in the
> future, but I'm especially interested in getting it to virtual
> machines. Unfortunately, from what I can find there's no nice
> interface between the host's rng and the vm for vmware esx like there
> is for kvm (eg: virtio_rng). Anyone know of one?
The tool you previously mentioned, Entropy Broker, is amongst the
better choices.
> With the entropy broker the thing I'm not totally clear on is how
> entropy bits transferred over the network (presumably without
> encryption as that might require entropy) would be worthwhile
> entropy?
I believe Entropy Broker encrypts, so it should be safe in that
respect. Not that it's much of a problem on a VM where the network
cable in question is a completely virtual one.
> What makes it different from the situation where you're
> using the network device interrupts as an source of entropy?
> Couldn't both be observable?
Such interrupts aren't great choices for entropy because they're so
easily manipulable, anyway.
> Another question - I keep seeing people suggesting to hook rngd (from
> rng-tools) up to /dev/urandom. Doesn't that just feed your system
> entropy with an prng most of the time? I feel like this just gives
> the illusion of a decent sized entropy pool. Might as well hook your
> app up to /dev/urandom instead, correct?
Yep.
B.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-03-26 16:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 20:39 [gentoo-hardened] Bought an "entropy-key" - very happy Ed W
2010-03-23 21:02 ` lists
2010-03-25 13:10 ` Rob Kendrick
2010-03-25 17:50 ` pageexec
2010-03-25 20:12 ` Rob Kendrick
2010-03-25 19:38 ` pageexec
2010-03-25 23:53 ` Ed W
2010-03-26 0:36 ` Rob Kendrick
2010-03-25 20:17 ` Ed W
2010-03-25 20:21 ` Rob Kendrick
2010-03-25 13:30 ` Ed W
2010-03-25 19:23 ` lists
2010-03-25 19:34 ` Tóth Attila
2010-03-25 20:11 ` Rob Kendrick
2010-03-25 20:34 ` Ed W
2010-03-25 20:41 ` RB
2010-03-25 21:08 ` Tom Hendrikx
2010-03-26 14:15 ` Brian Kroth
2010-03-26 15:19 ` Rob Kendrick [this message]
2010-03-27 13:11 ` Ed W
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=20100326151905.55ba1743@trite.i.flarn.net.i.flarn.net \
--to=rjek@rjek.com \
--cc=gentoo-hardened@lists.gentoo.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