curl-library
error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
Date: Mon, 30 Mar 2009 11:54:48 +0530
Hi,
I have installed curl library on Solaris 10 machine. I am trying to connect using curl to VSFTPD server using ssl. When i use Single authentication(Server presenting certificates to client) i am able to connect to VSFTPD server, but when i switch to mutual authentication(Both Server and Client presenting certificates) i get the following error.
I have setup VSFTPD to accept all certificates.
require_cert=YES
validate_cert=YES
Please help me in pointing out what could be the problem.
bash-3.00$ curl -3 -v --ftp-ssl -T "encoder.out" --key client.key --cacert cacert.pem --insecure ftp://lis:lis@172.31.107.132:11600
* About to connect() to 172.31.107.132 port 11600 (#0)
* Trying 172.31.107.132... connected
* Connected to 172.31.107.132 (172.31.107.132) port 11600 (#0)
< 220 (vsFTPd 2.0.7)
> AUTH SSL
< 234 Proceed with negotiation.
* successfully set certificate verify locations:
* CAfile: cacert.pem
CApath: none
* SSLv3, TLS handshake, Client hello (1):
} [data not shown]
* SSLv3, TLS handshake, Server hello (2):
{ [data not shown]
* SSLv3, TLS handshake, CERT (11):
{ [data not shown]
* SSLv3, TLS handshake, Request CERT (13):
{ [data not shown]
* SSLv3, TLS handshake, Server finished (14):
{ [data not shown] * SSLv3, TLS alert, Client hello (1):
} [data not shown]
* SSLv3, TLS handshake, Client key exchange (16):
} [data not shown]
* SSLv3, TLS change cipher, Client hello (1):
} [data not shown]
* SSLv3, TLS handshake, Finished (20):
} [data not shown]
* SSLv3, TLS alert, Server hello (2):
{ [data not shown]
* error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
* Closing connection #0
curl: (35) error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
bash-3.00$
Thanks,
Vamsi.
_________________________________________________________________
Windows Live Messenger. Multitasking at its finest.
http://www.microsoft.com/india/windows/windowslive/messenger.aspx
Received on 2009-03-30