linux-kernel - Re: [Keyrings] [GIT PULL] Crypto keys and module signing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 09 Dec 2011 14:41:58 -0500
From:	Daniel Kahn Gillmor <dkg@...thhorseman.net>
To:	David Howells <dhowells@...hat.com>
CC:	Arjan van de Ven <arjan@...ux.intel.com>, keyrings@...ux-nfs.org,
	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org, dmitry.kasatkin@...el.com,
	alan@...rguk.ukuu.org.uk
Subject: Re: [Keyrings] [GIT PULL] Crypto keys and module signing

On 12/09/2011 01:47 PM, David Howells wrote:
> Arjan van de Ven <arjan@...ux.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


Download attachment "signature.asc" of type "application/pgp-signature" (1031 bytes)