1. devstack
  2. Commit 499315fb655680a97042d09787d377c754b28fc3
Browse code

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

Attila Fazekas authored on 2014/03/25 18:42:14
Showing 1 changed files
lib/heat
History View file @ 499315f
... ... 
@@ -96,7 +96,7 @@ function configure_heat {
96 96 
     iniset $HEAT_CONF DEFAULT heat_waitcondition_server_url http://$HEAT_API_CFN_HOST:$HEAT_API_CFN_PORT/v1/waitcondition
97 97 
     iniset $HEAT_CONF DEFAULT heat_watch_server_url http://$HEAT_API_CW_HOST:$HEAT_API_CW_PORT
98 98 
     iniset $HEAT_CONF database connection `database_connection_url heat`
99 
-    iniset $HEAT_CONF DEFAULT auth_encryption_key `hexdump -n 16 -v -e '/1 "%02x"' /dev/random`
99 
+    iniset $HEAT_CONF DEFAULT auth_encryption_key `hexdump -n 16 -v -e '/1 "%02x"' /dev/urandom`
100 100
101 101 
     # logging
102 102 
     iniset $HEAT_CONF DEFAULT debug $ENABLE_DEBUG_LOG_LEVEL