From e954686e5a05cdc3028ceed4b853a1ca26a39db3 Mon Sep 17 00:00:00 2001 From: George Hartzell Date: Mon, 21 May 2018 13:57:03 -0700 Subject: Add info about haveged to gpg/randomness note (#8227) --- lib/spack/docs/getting_started.rst | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/lib/spack/docs/getting_started.rst b/lib/spack/docs/getting_started.rst index 407c1774b8..09ae4b5ec3 100644 --- a/lib/spack/docs/getting_started.rst +++ b/lib/spack/docs/getting_started.rst @@ -1064,9 +1064,12 @@ Secret keys may also be later exported using the Key creation speed The creation of a new GPG key requires generating a lot of random numbers. Depending on the entropy produced on your system, the entire process may - take a long time (even a few minutes). To speed it up you may install - tools like ``rngd``, which is usually available as a package in the host OS. - On e.g. an Ubuntu machine you need to give the following commands: + take a long time (*even appearing to hang*). Virtual machines and cloud + instances are particularly likely to display this behavior. + + To speed it up you may install tools like ``rngd``, which is + usually available as a package in the host OS. On e.g. an + Ubuntu machine you need to give the following commands: .. code-block:: console @@ -1075,6 +1078,18 @@ Secret keys may also be later exported using the before generating the keys. + Another alternative is ``haveged``, which can be installed on + RHEL/CentOS machines as follows: + + .. code-block:: console + + $ sudo yum install haveged + $ sudo chkconfig haveged on + + `This Digital Ocean tutorial + `_ + provides a good overview of sources of randomness. + ^^^^^^^^^^^^ Listing keys ^^^^^^^^^^^^ -- cgit v1.2.3-60-g2f50