I posted a little while ago about a proposed Net::SSH2 module that would le=
ave=20
SSH1 behind, and allow access to SSH2 features such as channels. =A0(This d=
oes=20
not imply that I plan to stop fixing/supporting Net::SSH::Perl.)
I'm considering rather than doing everything from scratch in perl (as=20
Net::SSH::Perl does), having it use either libssh or libssh2. =A0I've looke=
d at=20
and installed both libraries and there are pros/cons to each:
* libssh - http://0xbadc0de.be/wiki/doku.php?id=3Dlibssh:libssh (API:=20
http://0xbadc0de.be/wiki/doku.php?id=3Dlibssh:documentation)
* libssh2 - http://www.libssh2.org/ (API: http://www.libssh2.org/doc)
libssh has been around longer, but libssh2 has cleaner code (IMO), and alre=
ady=20
has PHP and Python bindings.
Naturally this introduces a dependency, but as anyone that's installed=20
Net::SSH::Perl can tell you, one dependency is probably better than the ten=
s=20
that exist now (Math::PARI, Crypt::*, etc.), and it can probably be mitigat=
ed=20
by including a fallback version of the library with the distribution (libss=
h=20
is LGPL, libssh2 is BSD licensed). =A0Both libraries classify themselves as=
=20
'beta' on freshmeat.net, both have a good list of features (and some missin=
g=20
features can probably be back-ported from Net::SSH::Perl), including SFTP=20
support "for free".
I'm looking for opinions as to which library should be used for Net::SSH2, =
or,=20
opinions against using a library at all and keeping it as purely perl as=20
possible, or any other advice people see fit to post.
Other note: I haven't had that many fixes/patches to Net::SSH::Perl/Net::SF=
TP=20
lately, but there have been a couple, so I'm considering another release; i=
f=20
anyone has any particular concerns or patches lying around, please send the=
m=20
in.
Thanks,
=2D-=20
Dave
Isa. 40:31
|