On Fri, 12 Jun 2009, Phillip Wu wrote:
> I have looked at the code for channel_read and it appears that it returns 0
> when the remote end has closed the channel:
...
> I think that the channel_read routine should return
> LIBSSH2_ERROR_CHANNEL_CLOSED rather than 0.
But isn't a return code of
Daniel Stenberg writes:
> On Thu, 11 Jun 2009, Daniel Stenberg wrote:
>
>> This said, I even failed to build this on Linux... I was tempted to do a
>> speed comparison but I'll put that on hold for now.
>
> libssh2 test:
>
> $ ./scp_nonblock 127.0.0.1 [user] [password] [big file] >/dev/null
>
On Sat, 13 Jun 2009, Simon Josefsson wrote:
>> 693M bytes file took 21.89 seconds. Speed: 31.6MB/sec
>> 693M bytes file took 50.96 seconds. Speed: 13.6MB/sec
>
> I'm curious if there is any difference in encryption/MAC algorithm choice
> between these libraries?
Hm, yes that's indeed a sensible
Daniel Stenberg wrote:
> > encryption/MAC algorithm
>
> I'm not sure I can figure that out easily.
You can force settings on the server side.
Also enable lots of logging on the server side, to learn what the
client is using.
//Peter
\giermang\Desktop\libssh2-1.1.1-20090613\include\libssh2.h
2009-06-12 21:02:23.0 -0500
+++ C:\Users\giermang\new\libssh2-1.1\include\libssh2.h 2009-06-13
18:59:35.0 -0500
@@ -76,12 +76,19 @@
typedef __int64 libssh2_int64_t;
typedef unsigned int uint32_t;
#ifndef
