From 499315fb655680a97042d09787d377c754b28fc3 Mon Sep 17 00:00:00 2001 From: Attila Fazekas Date: Tue, 25 Mar 2014 10:42:14 +0100 Subject: [PATCH] Use urandom for heat key generation Reading from /dev/random can block an virtual machine even for several minutes, when the entropy pool is empty at the read time. I have doubts we really need to use /dev/random here. Even the ssh-keygen uses /dev/urandom by default, so the /dev/random is a little bit overkill here. Change-Id: I6d2c6364c2b445304a33b0140e3cdc6804404b63 --- lib/heat | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/heat b/lib/heat index f66f0a8454..26d58e0d7c 100644 --- a/lib/heat +++ b/lib/heat @@ -96,7 +96,7 @@ function configure_heat { iniset $HEAT_CONF DEFAULT heat_waitcondition_server_url http://$HEAT_API_CFN_HOST:$HEAT_API_CFN_PORT/v1/waitcondition iniset $HEAT_CONF DEFAULT heat_watch_server_url http://$HEAT_API_CW_HOST:$HEAT_API_CW_PORT iniset $HEAT_CONF database connection `database_connection_url heat` - iniset $HEAT_CONF DEFAULT auth_encryption_key `hexdump -n 16 -v -e '/1 "%02x"' /dev/random` + iniset $HEAT_CONF DEFAULT auth_encryption_key `hexdump -n 16 -v -e '/1 "%02x"' /dev/urandom` # logging iniset $HEAT_CONF DEFAULT debug $ENABLE_DEBUG_LOG_LEVEL