RE: the API to load X509 from char*

Yes, it's quite easy. This works for me in 0.9.4: (char *buf; int len; values should already be set) ... BIO *bi = BIO_new(BIO_s_mem()); BUF_MEM bf; X509 *x; bf.length = len; bf.data = buf; bf.max = bf.length; BIO_set_mem_buf(bi, bf, 0); x = PEM_read_bio_X509(bi, NULL, NULL, NULL); -- Howard

SSL_read Access violation

Hi, Has anybody got acces violations when doin SSL_read. I come across them pretty regularly, but they are difficult to debug because they happen randomly when servicing hundreds of connections. A second question was about the counterpart to SSL_library_init(). Is there a deinit function?

Re: RSA_generate_key() without /dev/urandom

There should be some workaround for systems without /dev/urandom ! I posted a pointer to a to a secure random mechanism which is portable and does not rely on the user input and because of the continuous number of complaints on the subject, I am quite surprised that no one asked for this or a

Re: the API to load X509 from char*

Howard Chu wrote: Yes, it's quite easy. This works for me in 0.9.4: (char *buf; int len; values should already be set) ... BIO *bi = BIO_new(BIO_s_mem()); BUF_MEM bf; X509 *x; bf.length = len; bf.data = buf; bf.max = bf.length; BIO_set_mem_buf(bi, bf, 0); x = PEM_read_bio_X509(bi,

Read-ahead code doesn't quite work (including current CVS version)

Hi folks, Following came up when I saw problems at feeding TLS wrapped SMTP connection over the network to Stalker Software's CommuniGate Pro server, which does implement two recent SMTP extensions: PIPELINING STARTTLS The pipelining they do isn't *quite* fully optimized

RE: Source code == free speech?

I personally would prefer to step carefully here. The ruling of a circuit court is a precedence not a law. In particular, it is not binding on another circuit court. See if the government appeals and what the supreme court says. Shmuel Siegel -Original Message- From: Richard Levitte -

Re: An urgent question, please sirs

On Wed, Apr 05, 2000 at 07:06:02PM +0200, pgold wrote: Sir, can you help us in our problem? How to set and choose the session id, and how to choose the cypher file. How to use the SSL in general? We are running out of time and we need your answer very soon. If you wish to get SSL going first

RE: the API to load X509 from char*

-Original Message- From: [EMAIL PROTECTED] Howard Chu wrote: Yes, it's quite easy. This works for me in 0.9.4: (char *buf; int len; values should already be set) ... BIO *bi = BIO_new(BIO_s_mem()); BUF_MEM bf; X509 *x; bf.length = len; bf.data = buf; bf.max =

Re: Still have a problem in SSL, please help me

pgold wrote: Dear all, So far I recieved 2 mails. One of them is a question about our project, and the other was recommending me to try s_server.c and s_client.c in apps/ However, I think that these files are about specifing the options from the command line argument. May be I

Re: Still have a problem in SSL, please help me

Hi, You can take a look at the s_server and s_client sources to find out how they communicate. I did that myself and its pretty neat. Good luck. Amit. pgold wrote: X-EXP32-SerialNo: 2917 Sender: [EMAIL PROTECTED] Precedence: bulk Reply-To: [EMAIL PROTECTED] X-Sender: pgold [EMAIL

Why is dso a part of openssl?

The new dso stuff looks like a general purpose portable interface to shared libraries. If that is really all it is then there's no real connection to OpenSSL at all and it seems like it should be a library on it's own, outside OpenSSL. What am I missing?