Daniel Stenberg wrote:
> > You can force settings on the server side.
> >
> > Also enable lots of logging on the server side, to learn what the
> > client is using.
>
> Sure, but that's no longer "easily"
e.g.:
/usr/sbin/sshd '-oport 222' '-omacs hmac-sha1,umac...@openssh.com' \
'-ociphers aes
On Sun, 14 Jun 2009, Peter Stuge wrote:
> You can force settings on the server side.
>
> Also enable lots of logging on the server side, to learn what the client is
> using.
Sure, but that's no longer "easily" and quite honestly I'm not *that*
interested. I've already made my choice and investe
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
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 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 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
693M bytes file took 21.89 seconds. Sp
2009/6/11 Daniel Stenberg :
> On Thu, 11 Jun 2009, Alexander Lamaison wrote:
>
>> One major limitation of libssh at the time was that it required the GNU
>> toolchain (Cygwin/MinGW) so I couldn't use it my Visual Studio project. I
>> have no reason to believe this has changed.
>
> They've switched
On Thu, 11 Jun 2009, Alexander Lamaison wrote:
> One major limitation of libssh at the time was that it required the GNU
> toolchain (Cygwin/MinGW) so I couldn't use it my Visual Studio project. I
> have no reason to believe this has changed.
They've switched to cmake now for all platforms, an
2009/6/11 Daniel Stenberg :
> I noticed our "competitor" libssh[*] released a 0.3 version not too long ago,
> and I felt the need to try to help the world by pointing out differences
> between our two merry projects:
>
>http://libssh2.haxx.se/libssh2-vs-libssh.html
>
> [*] = http://www.libs
