> Of course people have been harvesting entropy, or trying to, from network
> sources for decades. There's a famous paragraph regarding it in RFC 4086,
> which is an expanded version of a similar statement from RFC 1750 (1994):
>
> Other external events, such as network packet arrival times and
On 06/06/2018 09:12 PM, openssl-users-requ...@openssl.org digestributed:
> Date: Wed, 6 Jun 2018 16:12:59 +
> From: Michael Wojcik
>
>> Hence my solution of using a hardware TRNG shared over the
>> network with devices that lack the ability to have one added
>> locally.
>
> Yes, I think that
> From: openssl-users on behalf of Jakob
> Bohm
> Sent: Tuesday, June 5, 2018 02:46
> Hence my solution of using a hardware TRNG shared over the
> network with devices that lack the ability to have one added
> locally.
Yes, I think that's a good approach. It reduces the attack surface, since t
On 04/06/2018 15:56, Michael Wojcik wrote:
Of course people have been harvesting entropy, or trying to, from network
sources for decades. There's a famous paragraph regarding it in RFC 4086, which
is an expanded version of a similar statement from RFC 1750 (1994):
Other external events, s
Of course people have been harvesting entropy, or trying to, from network
sources for decades. There's a famous paragraph regarding it in RFC 4086, which
is an expanded version of a similar statement from RFC 1750 (1994):
Other external events, such as network packet arrival times and
le
On 31/05/2018 19:14, Jochen Bern wrote:
On 05/31/2018 03:03 PM, openssl-users-requ...@openssl.org distributed:
Date: Thu, 31 May 2018 18:45:02 +1000
From: FooCrypt
Place a teaspoon of fine grade white sand onto the skin of a snare drum
Macroscopic hardware TRNGs are a *tad* yesteryear
https:
As it happens I am the proud owner of a made-in-UK Mathmos Lava Lamp and a
couple of their Space Projectors : however I don't use them as a RNG.
I am thinking more about the fact that there are a lot of devices which
* have no hardware TRNG on board
* do have one or more connections to wired or
On 05/31/2018 03:03 PM, openssl-users-requ...@openssl.org distributed:
> Date: Thu, 31 May 2018 18:45:02 +1000
> From: FooCrypt
>
> Place a teaspoon of fine grade white sand onto the skin of a snare drum
Macroscopic hardware TRNGs are a *tad* yesteryear
https://en.wikipedia.org/wiki/Lavarand
b
Are you a Dr Who fan ?
Place a teaspoon of fine grade white sand onto the skin of a snare drum
Place an isolating isoscrope above the snare drum that can measure the
fractional movements of the grains of sand based on the ambient noise.
Do something that moves the sand so you can measure the fa
I've also encountered this quite often, and I have a feeling that on
today's connected devices there may be a lot of entropy "in the air"
(quite literally) which is not being captured. Does any one know of
research in this area?
> Hi Scott
>
> I donât know your OS or environment, have you tried
> Either way, trying to use OpenSSL's PRNGD to seed OpenSSL's PRNGD is an
> exercise in futility.
Oh, I agree on that.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
In message
on Wed, 30 May 2018 15:37:47 +, Scott Neugroschl said:
scott_n> The platform in question is an HPE NonStop.
NonStop isn't the only platform with this sort of problem... I'd
suggest asking in places dedicated to NonStop if they know of good
enough ways to gather enough entropy,
> On 31 May 2018, at 1:35 AM, Michael Wojcik
> wrote:
>
>> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
>> Of FooCrypt
>> Sent: Wednesday, May 30, 2018 10:46
>> To: openssl-users@openssl.org
>> Subject: Re: [openssl-users] PR
>>> I’m using PRNGD to seed my random numbers (I’m on a system without
>>> /dev/random and /dev/urandom). I occasionally get the dreaded “PRNG is
>>> not seeded” error.
>>
>> I don’t know your OS or environment, have you tried the ‘openssl rand’
>> functionality as a random source to seed your en
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of FooCrypt
> Sent: Wednesday, May 30, 2018 10:46
> To: openssl-users@openssl.org
> Subject: Re: [openssl-users] PRNG is not seeded
>
> > On 30 May 2018, at 11:55 PM, Michael Wojcik
> wrote:
> On 30 May 2018, at 11:55 PM, Michael Wojcik
> wrote:
>
>> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
>> Of FooCrypt
>> Sent: Tuesday, May 29, 2018 21:41
>> To: openssl-users@openssl.org
>> Subject: Re: [openssl-users] PR
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of FooCrypt
> Sent: Tuesday, May 29, 2018 21:41
> To: openssl-users@openssl.org
> Subject: Re: [openssl-users] PRNG is not seeded
>
> > On 30 May 2018, at 8:58 AM, Scott Neugroschl
> wrote:
Hi Scott
I don’t know your OS or environment, have you tried the ‘openssl rand’
functionality as a random source to seed your entropy issues ?
openssl rand 102400 > some named pipe file that you can call as your random
source.
perhaps rather than pseudo random, try a hardware device ?
> On
>I know this is caused by a lack of available entropy in the system; but what
>can I do to address this? Is it just a matter of waiting until enough entropy
>has been collected? Is there any kind of workaround?
Assuming you don’t have another source of randomness that you can add in, then
you
Hi,
I'm using PRNGD to seed my random numbers (I'm on a system without /dev/random
and /dev/urandom). I occasionally get the dreaded "PRNG is not seeded" error.
I know this is caused by a lack of available entropy in the system; but what
can I do to address this? Is it just a matter of waiti
20 matches
Mail list logo
