[Pkg-gnupg-commit] [gnupg2] 08/205: doc: Note that rngd can also be used to quickly generate insecure keys.

[Daniel Kahn Gillmor]

This is an automated email from the git hooks/post-receive script.

dkg pushed a commit to branch experimental
in repository gnupg2.

commit 75311cfe18071b94c66121a9785b133b6df345a3
Author: Neal H. Walfield <neal at g10code.com>
Date:   Tue Feb 2 11:50:08 2016 +0100

    doc: Note that rngd can also be used to quickly generate insecure keys.
    
    * doc/gpg-agent.texi (Agent Options): Add comment to the description
    of --debug-quick-random that rngd can also be used to quickly generate
    key.
    
    --
    Signed-off-by: Neal H. Walfield <neal at g10code.com>
---
 doc/gpg-agent.texi | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/doc/gpg-agent.texi b/doc/gpg-agent.texi
index f4da9cf..5a387d4 100644
--- a/doc/gpg-agent.texi
+++ b/doc/gpg-agent.texi
@@ -243,9 +243,15 @@ debugger.
 This option inhibits the use of the very secure random quality level
 (Libgcrypt’s @code{GCRY_VERY_STRONG_RANDOM}) and degrades all request
 down to standard random quality.  It is only used for testing and
-shall not be used for any production quality keys.  This option is
+should not be used for any production quality keys.  This option is
 only effective when given on the command line.
 
+On GNU/Linux, another way to quickly generate insecure keys is to use
+ at command{rngd} to fill the kernel's entropy pool with lower quality
+random data.  @command{rngd} is typically provided by the
+ at command{rng-tools} package.  It can be run as follows: @samp{sudo
+rngd -f -r /dev/urandom}.
+
 @item --debug-pinentry
 @opindex debug-pinentry
 This option enables extra debug information pertaining to the

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-gnupg/gnupg2.git