search for: ssh_msg_channel_extended_data

I have an application that uses a 1-byte OOB packet for a heartbeat signal. It appears that openssh blocks these packets when I use it to forward to a remote port. The application works fine when connected to the server using the port forward, but all heartbeat packets are stripped out from the socket data. Is this intentional? Is it a bug? I've tried several versions of openssh without

In SSHv2, the data that consumes window space is that sent in the channel data and channel data extended messages. My question is, how is the data that consumes window space reckoned? One would have thought that it is the total length of the message itself, but the standard seems to imply that only the data contained in the data string field in the messages above is to be taken into account. That