openssh vs. commercial ssh1 port forwarding

Jarno Huuskonen jhuuskon at messi.uku.fi
Tue Oct 17 03:13:45 EST 2000


> I have already mentioned this a few times before but here I go again:
> Commercial ssh1 can send SSH_SMSG_FAILURE when client tries to do remote
> portforwarding. Openssh only handles SSH_SMSG_SUCCESS and ends in 
> protocol error if server sends FAILURE.

The latest snapshot with the AllowTcpForwarding patch also sends 
SSH_SMSG_FAILURE if port forwarding is disabled ->
protocol error: expecting 14 got 15 (or something like that). 

IMO handling the FAILURE message should go to openssh or at least print a more
informational error message.

> To 'correctly' handle FAILURE the code in channels.c (around line 1566) needs
> minor modifications (instead of packet_read_expect use packet_read etc.). This
> modification is in the (protocol2 -R support) patches I've sent to the list.

-- 
Jarno Huuskonen - System Administrator   |  Jarno.Huuskonen at uku.fi
University of Kuopio - Computer Centre   |  Work:   +358 17 162822
PO BOX 1627, 70211 Kuopio, Finland       |  Mobile: +358 40 5388169





More information about the openssh-unix-dev mailing list