From: Ed W <lists@wildgooses.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Bought an "entropy-key" - very happy
Date: Sat, 27 Mar 2010 13:11:35 +0000 [thread overview]
Message-ID: <4BAE0407.5040205@wildgooses.com> (raw)
In-Reply-To: <20100326141518.GN10118@gmail.com>
On 26/03/2010 14:15, Brian Kroth wrote:
> Here's another graphing tool I started using since whoever started this
> thread got me hooked on the subject :)
> http://collectd.org/wiki/index.php/Plugin:Entropy
>
Nice
For those using snmpd (eg cacti) all I did was add this line to my
/etc/snmp/snmpd.conf file:
exec .1.3.6.1.4.1.2021.60 entropy /bin/cat
/proc/sys/kernel/random/entropy_avail
Then I used a template from the cacti mailing list to easily pull that
into a graph in cacti and plot it
> Things are much worse, even for physical machines, than I originally
> suspected, so I'm now thinking about trying to setup something like this
> in conjunction with both the entropy key and the timer_entropyd so that
> I can provide an entropy service to various clients.
> http://www.vanheusden.com/entropybroker/
>
I don't have audio, video or builtin hw rand on my servers, so I could
only user timer_entropyd. This chewed about 2-5% CPU on one very
lightly loaded quad core intel board and kept the entropy at about
80-100%. On my other AMD dual core live server, it chewed more like
5-15% cpu (not sure why) and mostly it keeps entropy at 70-100%, but
with regular dips to zero (server is pretty lightly loaded, load average
around 0.2). Unless you are a complete tinfoil hatter then this is
probably plenty
The ekeyd keeps the machine at 100% entropy (actually it keeps it at
slightly *over* 15,000 bytes which is the pool size - I'm not quite sure
how/why it's keeping the pool at 101% filled, but there you go). CPU
load is zero
For distributing entropy around, the entropykey comes with a basic egd
compatible socket and you simply setup an egd client (also supplied) to
read from that socket. I don't believe this is encrypted, so
entropybroker looks better over a real network, but it's also not yet in
portage (anyone got some time to contribute an ebuild?)
So from a "it's done" point of view, the entropy key really is a very
simple and low CPU solution.
Ed W
prev parent reply other threads:[~2010-03-27 14: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
2010-03-27 13:11 ` Ed W [this message]
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=4BAE0407.5040205@wildgooses.com \
--to=lists@wildgooses.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