On 03/21/2012 01:20 PM, Benji York wrote: > Since we have to map the file anyway, we can try mapping /dev/random to > /dev/urandom. If that works, we can set up the containers so their > /dev/random is really /dev/urandom and hope no one ever tries to > generate keys on them.
I've used rng-tools to feed /dev/random with data from /dev/urandom in the slave host. apt-get install rng-tools echo "HRNGDEVICE=/dev/urandom" >> /etc/default/rng-tools /etc/init.d/rng-tools start You can the check /dev/random does not block (in the host): for i in $(seq 1000); do head -1 /dev/random > /dev/null; done -- Francesco Banconi -- Mailing list: https://launchpad.net/~yellow Post to : [email protected] Unsubscribe : https://launchpad.net/~yellow More help : https://help.launchpad.net/ListHelp
