Hi Daniel,
Daniel Stenberg schrieb:
On Thu, 25 Aug 2011, Sumukh Anantha Manohar wrote:
Libraries: libssh2-1.2.9
This turned out to be a flaw in libssh2 and I just now pushed a fix there:
http://git.libssh2.org/?p=libssh2.git;a=commitdiff;h=900c90ccbe9;js=1
I haven't yet actually tested
On Sat, 27 Aug 2011, Guenter wrote:
since this sounds like an important fix do you plan a libssh2 1.2.10 release
shortly before next libcurl release so that binaries will be able to be
build against a fixed libssh2?
Seems like a good idea with another release, yes. Let's make it a 1.3.0
On Thu, 25 Aug 2011, Sumukh Anantha Manohar wrote:
Libraries: libssh2-1.2.9
This turned out to be a flaw in libssh2 and I just now pushed a fix there:
http://git.libssh2.org/?p=libssh2.git;a=commitdiff;h=900c90ccbe9;js=1
I haven't yet actually tested this with (lib)curl, but I could
Daniel Stenberg skrev 2011-08-26 12:01:
I haven't yet actually tested this with (lib)curl, but I could easily
repeat this problem with only libssh2 before the fix.
I'm interested in feedback.
Just gave it a test run with the fix applied to libssh2 1.2.8 (which I
had lying around, so quick
Hi,
As i had posted earlier,
Do you always get this same error (and byte amount) no matter how large
file
you get? If not, do you get the same error and byte amount for the same
file
if you retry the exact same transfer?
Eh, so does it work for _any_ sftp files at all? If so, which?
Even
On Thu, 25 Aug 2011, Sumukh Anantha Manohar wrote:
Eh, so does it work for _any_ sftp files at all? If so, which?
Even if i try to download a 2MB file with sftp protocol, sometimes it will
download completely and sometimes it will show the error : **curl: (18)
transfer closed with 574
