in reply to Net::SSH::Perl pty problem with SSH2? SOLVED

SSH2 is far a more restrictive protocol than SSH1, so I'm not altogether surprised at and indeed, have seen for myself, the same, or very similar, problems.

The only solution we came up with was to ensure that the appropriate satellite machines all had perl installed along with the latest Net::SSH and then use perl, not the shell, to communicate with the furthest machines.

We encountered a further similar problem when attempting to use the GNU screen utility...

A user level that continues to overstate my experience :-))

Replies are listed 'Best First'.
Re^2: Net::SSH::Perl pty problem with SSH2?
by cmv (Chaplain) on Dec 22, 2008 at 22:40 UTC
    What I'm trying to do will work from unix machines with the SSH2 protocol, using the stock ssh command: 
    $ ssh -2  -t machineB "ssh -2 -t userC@machineC uname -a"
usrB@machineB's password: 
Password: 
Mon Dec 22 16:34:45 CST 2008
Connection to machineC closed.
Connection to machineB closed.

    [download]
    Taking the -t off of machineB's ssh will cause the error to occur.

    I would think that we should be able to make Net::SSH::Perl do the same thing, shouldn't we?

    -Craig

[reply]
[d/l]
      What I'm trying to do will work from unix machines with the SSH2 protocol

      You'll possibly find that you get better mileage (on both Windows and Linux) with Net::SSH2 than you do with Net::SSH::Perl/Net::SSH::W32Perl. Of course, you're then limited to the SSH2 protocol.

      Cheers,
      Rob
[reply]
      I can't see why not - but that, like most of perl (& indeed CPAN), is down to 'us' to change if we see fit. Let us know how your work progresses cmv - I look forward to seeing the Net:SSH update :-D

      A user level that continues to overstate my experience :-))
[reply]

In Section Seekers of Perl Wisdom