www.libssh2.org | Daily snapshots | Mailing list archive | Docs | Examples | github

Archive Index This month's Index

Subject: Re: client-side only vs. libssh?

Re: client-side only vs. libssh?

From: Daniel Stenberg <daniel_at_haxx.se>
Date: Fri, 22 Jan 2010 21:25:19 +0100 (CET)

On Fri, 22 Jan 2010, Lawson wrote:

> I have been working with libssh for a while and was looking to switch over
> to libssh2, primarily because of the claims that libssh2 can do all things
> in a non-blocking style (I have run into some blocking issues with libssh)
> plus I no longer have a requirement to support SSHv1.

If libssh2 can't do everything non-blocking, it would be a bug we should fix.
But I'm not aware of anything particular in that way right now.

> However I am now realizing that libssh2 may only be a client-side library.
> Is this still true? If so, you need to be way more upfront about that. It
> is not obvious from the description on the website.

It is true and I've updated the front page of the site to make it more

We wouldn't object to make it do server-side too of course, and I've heard a
few people in the past express interest to work on that. But unfortunately we
haven't yet seen any work towards that. Would you be interested to work on it?

> Especially in your "comparison against libssh" because that one does
> server-side also.

I didn't know it did. I'll update the comparison as well!

> Are these two the only choices for an SSH library (with a decent API) ?

To my knowledge these two are the only free and open SSH libraries that are
written in C, yes.

  / daniel.haxx.se
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2010-01-22

the libssh2 team