Obviously I have misunderstood the manpage for RAND_bytes. What is says
is:
int RAND_bytes(unsigned char *buf, int num);
int RAND_pseudo_bytes(unsigned char *buf, int num);
DESCRIPTION
RAND_bytes() puts num cryptographically strong pseudo-random
bytes into buf. An error o
From: Louis LeBlanc <[EMAIL PROTECTED]>
leblanc> Anyway, this is what I did:
leblanc> unsigned char entropy[4096];
[...]
leblanc> RAND_bytes(entropy, 4000);
leblanc> RAND_seed(entropy, 3000);
And what do you think this gives you? Have you actually thought of
checking the returned status code?
> Anyway, this is what I did:
> unsigned char entropy[4096];
>
> /* Then I call the SSL_load_error_strings() and
> OpenSSL_add_all_algorithms()
> * routines, and create my context. Then, . . .
> */
>
> RAND_bytes(entropy, 4000);
> RAND_seed(entropy, 3000);
you've just seeded with bytes g
> My code miraculously worked without modification when building against
> 0.9.4.
> 0.9.5a and the snapshot broke the same code at the handshake, giving the
> 'PRNG not seeded' message.
...
> the cert creation and translation tests and
> suggested that I set the RANDFILE environment variable
On Fri, Jun 30, 2000, Louis LeBlanc wrote:
> RAND_bytes(entropy, 4000);
> RAND_seed(entropy, 3000);
> /* just giving myself some room until the code is working */
>
> And everything works.
No, nothing works, as you would have noticed, had you checked the RAND_bytes()
return value. You still
Thank you so much. Your message cleared up a problem I wrestled with for
some time. Once you pointed me in the right direction, I found everything
in the manpages, and it all fell into context (I have to admit to being a
little thick from time to time :).
Anyway, this is what I did:
unsigned ch
From: Louis LeBlanc <[EMAIL PROTECTED]>
leblanc> The project involved an https load generator - primarily used
leblanc> for correctness testing of another project. I had the worst
leblanc> time getting the initial handshake to work. The dreaded
leblanc> 'PRNG not seeded' message kept plaguing m
I have to admit that I am just putting my 2 cents in at the tail of this
discussion, and I did miss some of the earlier posts in
this thread, but my recent experience with OpenSSL client coding may shed
some light here.
The project involved an https load generator - primarily used for
correctness
From: Lutz Jaenicke <[EMAIL PROTECTED]>
Lutz.Jaenicke> To the OpenSSL-Administrators: please update the
Lutz.Jaenicke> stunnel entry (considering this to be the new official
Lutz.Jaenicke> home of stunnel!?).
*clicketiclick*
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman
> Here is "below" :-)
>
> Until now I did not know of "www.stunnel.org". My bookmarks still contained
> the old(?) address in Poland, as does the OpenSSL home page.
> The latest version listed there is 3.8 (without p1 etc) and there is no link
> to the new site
It does contain a link to 'a
On Wed, Jun 28, 2000 at 07:24:41AM -0700, Brian Hatch wrote:
> > > Before anyone says it's in the FAQ, I've checked this out long and hard
> > > and I'm pretty sure this is a bug.
>
> not terribly hard, its on the stunnel.org page and older
> stunnel web faq since march. Yeah, it's a bug.
See b
11 matches
Mail list logo
