> Yes; I don't recall seeing Net::SSH discussed here before it ws released,
> but when I noticed it on the CPAN, I was bothered by the fact that it was
> just a wrapper, not an implementation. I think people have come to expect
> Net::${PRTOTOCOL} modules to be Perl/XS/etc. implementations of tha
At 12:09 -0800 01.25.2001, Benjamin Trott wrote:
>> How about coordinating with the author of Net::SSH, and integrating
>> both your codebases?
>
>This is an option. Some of the downsides:
>
>* Since the current Net::SSH on CPAN is basically a wrapper around the ssh
>command line client, and mine
On Thu, Jan 25, 2001 at 12:09:49PM -0800, Benjamin Trott wrote:
> > How about coordinating with the author of Net::SSH, and integrating
> > both your codebases?
>
> This is an option. Some of the downsides:
>
> * Since the current Net::SSH on CPAN is basically a wrapper around the ssh
> command
> How about coordinating with the author of Net::SSH, and integrating
> both your codebases?
This is an option. Some of the downsides:
* Since the current Net::SSH on CPAN is basically a wrapper around the ssh
command line client, and mine is a Perl implementation of an ssh client, the
code base
On Wed, Jan 24, 2001 at 02:09:59PM -0800, Benjamin Trott wrote:
> I've written a Net::SSH module that's an all-Perl interface to an ssh
> daemon. Currently 3 encryption ciphers are working (IDEA, DES, and 3DES),
> and one authentication method (password auth). (I also have rhosts-RSA
> authenticat
Hi--
I've written a Net::SSH module that's an all-Perl interface to an ssh
daemon. Currently 3 encryption ciphers are working (IDEA, DES, and 3DES),
and one authentication method (password auth). (I also have rhosts-RSA
authentication working, but it requires running on a privileged port and
read
