I got my client working, and it seems that the problem was I wasn't calling
SSL_set_connect_state prior to SSL_connect. cli.cpp doesn't use this, but
s_client.c does.
Is it necessary to set the connect state prior to SSL_connect?
-- Jeff.
-----
Jeff Magnusson ([EMAIL PROTECTED])
River Styx Internet
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Magnusson
> Sent: April 28, 2000 1:55 PM
> To: [EMAIL PROTECTED]
> Subject: Probs compiling apps using BC4
>
>
> Hi, I'm trying to use openssl for a windows client and I have two probs:
>
> -- 1 --
> I have a test prog that is a replica of cli.c using winsock (SSLTest.cpp
> attached) and SSL_connect is returning this error: 'error:00000001::lib(0)
> :func(0) :reason(1)'.
> No matter how I set the cipher list this always happens. The
> cli.c compiled
> on unix works fine. It must be a difference in how the libs are
> compiled on
> windows. I've tried this with 0.9.5a and 0.9.4 with the same results.
> The server shows error '14650:error:1407D0E5:SSL routines:SSL2_READ:ssl
> handshake failure:s2_pkt.c:99' on SSL_read.
>
>
> -- 2 --
> In order to get more info on what goes wrong, I'm trying to compile the
> openssl command-line tool in the apps dir, but I can't figure out
> how to do
> this with bcc32.
>
>
> Any help would be appreciated, I'm out of ideas.
>
> -- Jeff.
>
> -----
> Jeff Magnusson ([EMAIL PROTECTED])
> River Styx Internet
>
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
