I thought the new openSSL did the pool hence why I started this post as I
wanted to assure that
use of the function is correct for key generation effect; then next step to
figure out some entropy.
thanks a whole bunch
--
Sent from: http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html
--
ope
On 23. maí 2018, at 10:08 f.h., redpath wrote:
> SO if I add this RAND usage below, em I seeding to assure a different RSA key
> pair each time run of creating a RSA pair.
>
> I would certainly replace the time with the UUID of the device to be unique
> to the device. You would have to acquire t
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of redpath
> Sent: Wednesday, May 23, 2018 16:02
> To: openssl-users@openssl.org
> Subject: Re: [openssl-users] PEM_write_bio_RSAPrivateKey assure
> Randomness of PK
>
> Oh I am using
Oh I am using openssl-1.0.2o just for development
But I certainly will take a recommendation of version.
Thats always appreciated.
--
Sent from: http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/open
>Well what I was alluding to is this the correct use of the RAND_add
> function
to seed the Key generation. Its a bit confusing certainly.
You are calling the API correctly. That should have been clear from the
manpage.
You still did not tell us what version of OpenSSL you are using.
Well what I was alluding to is this the correct use of the RAND_add function
to seed the Key generation. Its a bit confusing certainly. I will use more
than the UUID
of the device but you have to have the device in hand to know that and know
it came from
a device.
I certainly will use better tha
On 23.05.2018 20:39, Michael Wojcik wrote:
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
Of redpath
Sent: Wednesday, May 23, 2018 13:08
To: openssl-users@openssl.org
Subject: Re: [openssl-users] PEM_write_bio_RSAPrivateKey assure
Randomness of PK
SO if I add this RAND
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of redpath
> Sent: Wednesday, May 23, 2018 13:08
> To: openssl-users@openssl.org
> Subject: Re: [openssl-users] PEM_write_bio_RSAPrivateKey assure
> Randomness of PK
>
> SO if I add this RAND usag
What version of OpenSSL are you using?
Using the time to seed the RNG is horrible; DO NOT DO THAT.
Not trying to be insulting, but if you think time is a good source, then you
really don't know what you're doing for RNG's. Consider looking at the master
branch, with its highly-improve seeding
> On May 23, 2018, at 1:08 PM, redpath wrote:
>
> SO if I add this RAND usage below, em I seeding to assure a different RSA key
> pair each time run of
> creating a RSA pair.
>
> I would certainly replace the time with the UUID of the device to be unique
> to the device.
> You would have to ac
SO if I add this RAND usage below, em I seeding to assure a different RSA key
pair each time run of
creating a RSA pair.
I would certainly replace the time with the UUID of the device to be unique
to the device.
You would have to acquire the device to know the seeding. Hey keep the Time
one too.
My question is:
I have this handy function to create a Private and Public key
But what is the magic I put around it to make sure it is random not the same
Private and Public key when I run this program each time?
I am using openSSL on OSX and Android. I am not familiar with the random API
seedi
12 matches
Mail list logo
