curl-library
Re: SFTP support in curl library.
Date: Mon, 23 Mar 2009 14:23:33 +0530
On 20-Mar-09, at 7:44 PM, Daniel Stenberg wrote:
Thanks for your effort in helping me to solve this issue.
> Note that the name of the lib used for this is "libssh2".
Sorry that I missed to mention that I had used libssh2 and as I
mentioned I could build curl command line tool could do SFTP, but
libcurl generated in the build process does not detect SFTP.
My observation is that the build process generate curl command line
tool with SFTP support but does not generate SFTP supported library.
Please let me know, Is that I am missing some thing to get curl
library(libcurl) with SFTP support, or is there any alternate solution
to get libcurl with SFTP support.
Thanks for your support.
Regards
Girish Kolari
> On Fri, 20 Mar 2009, Girish Kolari wrote:
>
>> Since SFTP support for curl require libssh I built curl source with
>> libssh support. The generated curl application is supporting SFTP
>> but library built for curl does not support SFTP.
>
> Note that the name of the lib used for this is "libssh2". The number
> 2 in there is vital. www.libssh2.org is the place. There's another
> project using the name you mention and while that is a library with
> a similar purpose, it can't be used with libcurl.
>
>> 1. Build libssh.
>> 2. Configured curl with libssh.
>> 3. Build curl
>>
>> Result: built curl executable support SFTP but libcurl built does
>> not detect SFTP protocol(It returns unsupported protocol).
>
> You should be able to note this already at step 2 where the
> configure script failed to detect and use the SSH library.
>
> --
>
> / daniel.haxx.se
>
-----------------------------------------------
Robosoft Technologies - Come home to Technology
Disclaimer: This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. Emails to and from our network may be logged and monitored. This email and its attachments are scanned for virus by our scanners and are believed to be safe. However, no warranty is given that this email is free of malicious content or virus.
Received on 2009-03-23