From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Howells <dhowells@redhat.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
keyrings@linux-nfs.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, dmitry.kasatkin@intel.com,
alan@lxorguk.ukuu.org.uk
Subject: Re: [Keyrings] [GIT PULL] Crypto keys and module signing
Date: Fri, 09 Dec 2011 14:41:58 -0500 [thread overview]
Message-ID: <4EE26486.8090904@fifthhorseman.net> (raw)
In-Reply-To: <2762.1323456423@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
On 12/09/2011 01:47 PM, David Howells wrote:
> Arjan van de Ven <arjan@linux.intel.com> wrote:
>
>> ... the temp key can use /dev/urandom.
>> seriously, /dev/urandom for one time, temp keys is not bad
>> (if you care about the difference, you better provide your own real key)
>
> Can you tell gpg which random device to use?
Depending on the version of gpg, supplying either --quick-random or
--debug-quick-random should use a cheaper PRNG.
I think this is an undocumented feature, though.
hth,
--dkg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]
next prev parent reply other threads:[~2011-12-09 19:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 14:47 David Howells
2011-12-09 4:05 ` James Morris
2011-12-09 9:17 ` David Howells
2011-12-09 9:35 ` James Morris
2011-12-09 14:20 ` Arjan van de Ven
2011-12-09 14:31 ` James Morris
2011-12-09 18:06 ` David Howells
2011-12-09 18:18 ` Arjan van de Ven
2011-12-09 18:47 ` David Howells
2011-12-09 18:49 ` Arjan van de Ven
2011-12-09 18:59 ` David Howells
2011-12-09 19:41 ` Daniel Kahn Gillmor [this message]
2011-12-10 9:49 ` Geert Uytterhoeven
2011-12-10 11:42 ` Arkadiusz Miśkiewicz
2011-12-10 18:54 ` Arjan van de Ven
2011-12-10 12:50 ` David Howells
2011-12-12 14:12 ` Nick Bowler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE26486.8090904@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome