Module id = Net::SSH::Perl
    CPAN_USERID  SCHWIGON (Steffen Schwigon <schwigon@cpan.org>)
    CPAN_VERSION 2.01
    CPAN_FILE    S/SC/SCHWIGON/Net-SSH-Perl-2.01.tar.gz
    MANPAGE      Net::SSH::Perl - Perl client Interface to SSH
    INST_FILE    /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/Net/SSH/Perl.pm
    INST_VERSION 1.34

##</code><code>##

XS_Tk__Callback_Call error:Protocol error: expected packet type 91, got 80 at /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/Net/SSH/Perl/Packet.pm line 222

##</code><code>##

Tk::Error: Protocol error: expected packet type 91, got 80 at /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/Net/SSH/Perl/Packet.pm line 224
 Carp::croak at /opt/exp/perl/perl5.8/lib/5.8.8/Carp.pm line 269
 Net::SSH::Perl::fatal_disconnect at /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/Net/SSH/Perl.pm line 255
 Net::SSH::Perl::Packet::read_expect at /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/Net/SSH/Perl/Packet.pm line 224
 Net::SSH::Perl::SSH2::login at /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/Net/SSH/Perl/SSH2.pm line 78
 Auth::sshKeys::SetupKeys at lib/Auth/sshKeys.pm line 154
 remExec::SetupSSH at lib/remExec.pm line 161
 PCMDtrace::_runCmd at lib/PCMDtrace.pm line 657
 PCMDtrace::StatusUpdate at lib/PCMDtrace.pm line 138
 Ui::winTrace::_displayStatus at lib/Ui/winTrace.pm line 788
 Ui::winTrace::__ANON__ at lib/Ui/winTrace.pm line 176
 Tk::Widget::Callback at /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/darwin/Tk/Widget.pm line 1156
 Tk::Optionmenu::setOption at /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/darwin/Tk/Optionmenu.pm line 72
 Tk callback for .frame.optionmenu.menu
 Tk::__ANON__ at /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/darwin/Tk.pm line 251
 Tk::Menu::Invoke at /opt/exp/perl/perl5.8/lib/site_perl/5.8.8/darwin/Tk/Menu.pm line 532
 <ButtonRelease>
 (command bound to event)

##</code><code>##

217 sub read_expect {
218     my $class = shift;
219     my($ssh, $type) = @_;
220     my $pack = $class->read($ssh);
221     if ($pack->type != $type) {
222         $ssh->fatal_disconnect(sprintf
223           "Protocol error: expected packet type %d, got %d",
224             $type, $pack->type);
225     }
226     $pack;
227 }

##</code><code>##

caller DUMP:
$VAR1 = 'Net::SSH::Perl::SSH2';
$VAR2 = '/opt/exp/perl/perl5.8/lib/site_perl/5.8.8/Net/SSH/Perl/SSH2.pm';
$VAR3 = 78;

##</code><code>##

 65 sub login {
 66     my $ssh = shift;
 67     $ssh->SUPER::login(@_);
 68     my $suppress_shell = $_[2];
 69     $ssh->_login or $ssh->fatal_disconnect("Permission denied");
 70
 71     $ssh->debug("Login completed, opening dummy shell channel.");
 72     my $cmgr = $ssh->channel_mgr;
 73     my $channel = $cmgr->new_channel(
 74         ctype => 'session', local_window => 0,
 75         local_maxpacket => 0, remote_name => 'client-session');
 76     $channel->open;
 77
 78     my $packet = Net::SSH::Perl::Packet->read_expect($ssh,
 79         SSH2_MSG_CHANNEL_OPEN_CONFIRMATION);
 80     $cmgr->input_open_confirmation($packet);
 81
 82     unless ($suppress_shell) {
 83         $ssh->debug("Got channel open confirmation, requesting shell.");
 84         $channel->request("shell", 0);
 85     }
 86 }

##</code><code>##

80        SSH_MSG_GLOBAL_REQUEST

##</code><code>##

4.  Global Requests

   There are several kinds of requests that affect the state of the
   remote end globally, independent of any channels.  An example is a
   request to start TCP/IP forwarding for a specific port.  Note that
   both the client and server MAY send global requests at any time, and
   the receiver MUST respond appropriately.

##</code><code>##

All such requests use the
   following format.

      byte      SSH_MSG_GLOBAL_REQUEST
      string    request name in US-ASCII only
      boolean   want reply
      ....      request-specific data follows

   The value of 'request name' follows the DNS extensibility naming
   convention outlined in [SSH-ARCH].

   The recipient will respond to this message with
   SSH_MSG_REQUEST_SUCCESS or SSH_MSG_REQUEST_FAILURE if 'want reply' is
   TRUE.

      byte      SSH_MSG_REQUEST_SUCCESS
      ....     response specific data

   Usually, the 'response specific data' is non-existent.

   If the recipient does not recognize or support the request, it simply
   responds with SSH_MSG_REQUEST_FAILURE.

      byte      SSH_MSG_REQUEST_FAILURE

   In general, the reply messages do not include request type
   identifiers.  To make it possible for the originator of a request to
   identify to which request each reply refers, it is REQUIRED that
   replies to SSH_MSG_GLOBAL_REQUESTS MUST be sent in the same order as
   the corresponding request messages.  For channel requests, replies
   that relate to the same channel MUST also be replied to in the right
   order.  However, channel requests for distinct channels MAY be
   replied to out-of-order.