> if you would have posted the whole file, or at least the following few
lines, we would at once have known the correct things:

> version : 7.23.1 RTMP SSH2 SSL SSPI LIBZ WINIDN
requires : OpenSSL 1.0.0e DLLs (included) normaliz.dll (with Windows
Vista or higher included)
license : http://curl.haxx.se/docs/copyright.html
built by : G. Knauf <info_at_gknw.de>

> curl 7.23.1 (x86_64-pc-win32) libcurl/7.23.1 OpenSSL/1.0.0e zlib/1.2.5
IDN-Windows-native libssh2/1.3.0 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap pop3
pop3s rtmp rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN Largefile NTLM SSL SSPI libz

Sorry, the output was a little bit confusing, "1.2.5
IDN-Windows-native libssh2". I thought 1.2.5 is the version of libssh2.

> We are using c# to call the cURL exe by starting a process and pass in arguments in the same manner as a command line prompt:
thats fine, and makes things more simple:

Unfortuanately I can't include sensitive info such as username and the sftp server's address, and I can't run a command line test because I don't have the keys to do them. I am merely relaying the problems and info given to me by our customer deployment team, who have the keys. In any case, the client doesn't like people sending files to their production server without first getting permission.

In general, this is the format we are using to send files:

curl -v -u myusername: --key C:\temp2\keys\id_rsa --pubkey C:\temp2\keys\id_rsa.pub -T c:\temp2\test4.txt sft
p://serveraddress/ --insecure

Thanks.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-01-05