On Thu, Oct 16, 2003 at 04:48:13PM +0200, Daniel Stenberg wrote:
> On Thu, 16 Oct 2003, Georg Horn wrote:

> > * SSL read error: 1
> > * Connection #0 left intact
> > curl: (56) SSL read error: 1
> > * Closing connection #0
> >
> > I think here we have a problem/bug?
>
> It certainly appears to be a bug, I agree. I'm afraid I don't have any useful
> work-around or shortcuts but to fire up the debugger and run the command line
> using it and single-step through lib/sendf.c:Curl_read() to figure how
> exactly how and why this fails.

Ok, I'll try this.

> > And adding --cacert instead of -k again results in:
>
> > * SSL certificate problem, verify that the CA cert is OK
> > curl: (60) SSL certificate problem, verify that the CA cert is OK
>
> This is SSL_connect() returning failure... (see
> lib/ssluse.c:Curl_SSLConnect()) I don't see why though, as the openssl tool
> worked... What if you force it to talk sslv3?

As far as i understand the openssl tool, this must be done with:

    $ openssl s_client [...] -ssl3 -no_ssl2 -no_tls1

That works too and indeed prints in the output: "Protocol : SSLv3"

Bye,
Georg

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
Received on 2003-10-16