On Tue, Mar 21, 2006 at 08:45:47AM -0500, Henry Hertz Hobbit wrote:
> Stef Caunter <[EMAIL PROTECTED]> wrote:
> >Is this just the way it is on FreeBSD (4.11-RELEASE)? There is
> >plenty of randomness in /dev/urandom, and none in /dev/random...
Definitely ask on [EMAIL PROTECTED]
> Can you ask yo
On Thu, 16 Mar 2006 01:10:25 -0500 (EST), Stef Caunter said:
> I've started a child process that continually writes to a disk file during
> the --gen-key --batch job...
That won't help much. A better thing is
find /usr -type f | xargs cat >dev/null
> Is this just the way it is on FreeBSD (4
Hi,
Stef Caunter wrote:
I have populated ~/.gnupg/random_seed with 600 bytes from /dev/urandom
This is generally a very *bad* idea in terms of cryptography:
/dev/urandom uses a pseudo-random generator with predictable results,
(relatively) low random quality that is not suitable at all for
Stef Caunter <[EMAIL PROTECTED]> wrote:
>I'm sure I have just missed this in the archives, but I cannot see
>mention of a way to get sufficient randomness when running gpg
>remotely in a shell account to batch generate key pairs, i.e.
>
>gpg --gen-key --batch tmp
>
>where tmp is populated accordi
I'm sure I have just missed this in the archives, but I cannot see mention of a
way to get sufficient randomness when running gpg remotely in a shell account
to batch generate key pairs, i.e.
gpg --gen-key --batch tmp
where tmp is populated according to doc/DETAILS example. Here is what I've d
