Comment # 26 on bug 1096072 from Franck Bui

Ok I'm re-assigning this bug to Pedro as he's the maintainer of libgcrypt.

So basically there're 2 issues here:

 - FIPS mode has been unexpectedly activated (via the creation 
   of /etc/gcrypt/fips_enabled). Would be interesting to figure out how IMHO.

 - When the FIPS mode is activated, it exhausts /dev/urandom pool which
   may lead to such issues during the boot process.