curl-library
RE: ftps using curl to filezilla server
Date: Tue, 10 Oct 2006 14:11:45 +0530
In Filezilla there is an option
“Force PROT P to encrypt data channel in SSL/TLS mode”
Should I check this option.
* the technic is to use simple ftp:// then upgrade with PROT P
How can I do this through curl. Please help with some options .
Thanks in advance.
_____
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Armel Asselin
Sent: Tuesday, October 10, 2006 1:00 PM
To: libcurl development
Subject: Re: ftps using curl to filezilla server
for some reason, libcurl ftps expects data connection to be encrypted
without telling PROT P, but FileZilla expects the contrary.
the technic is to use simple ftp:// then upgrade with PROT P, and there it
works.
in fact from what I could read here and there, implicit protection (ftps) is
rather obsolete, however, like you, I would have found that cool to have
this works directly [one way could be to send PROT P unconditionnaly in ftps
mode, it would not be understood by very old ftp implemtentations other SSL,
and would be by newer ones, which consequently would make the server and
libcurl expect the same thing]
Armel
----- Original Message -----
From: kuriakose <mailto:kuriakose_at_huawei.com>
To: curl-library_at_cool.haxx.se
Sent: Tuesday, October 10, 2006 7:01 AM
Subject: ftps using curl to filezilla server
Hi,
While connecting to filezilla server 0.9.19 through curl using ftps , iam
getting the following error .
I am setting the CAPATH and CAINFO.
Please help!!!
Doing the SSL/TLS handshake on the data stream
successfully set certificate verify locations:
CAfile: certificate.crt
CApath: .
SSL re-using session ID
error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
DO-MORE phase ends
Connection #0 to host localhost left intact
Closing connection #0
----------------------------------------------------------------------------
-----------
Orange vous informe que cet e-mail a été contrôlé par l'anti-virus mail.
Aucun virus connu à ce jour par nos services n'a été détecté.
Received on 2006-10-10