On 18 Jan, Stephen Bolinger wrote:
> I have setup SSHD-2.0.13 on many Solaris machines, but I'm running into a
> problem getting it to work on a RedHat 6.1 machine. Here's the error I get:
>
> Jan 18 17:39:51 localhost sshd2[7785]: Starting daemon in inetd mode.
> Jan 18 17:39:51 localhost sshd2[7785]: connection from "10.10.110.222"
> Jan 18 17:39:51 localhost sshd2[7785]: Daemon is running.
> Jan 18 17:39:52 localhost sshd2[7785]: Remote host disconnected: Protocol
> error: packet too long: 1684365945.
> Jan 18 17:39:52 localhost sshd2[7785]: Protocol error: 'Protocol error:
> packet too long: 1684365945.'
Decimal 1684365945 = hex 64656279 = ascii "deby"
Do an truss on the ssh-client on the local machine and watch for
plaintext writes to the encrypted channel. Probably some part of it
writes an error message which ends up in the encrypted stream. I just
traced one such problem in our locally enchanced version of the sshd2
where a linked module (sdiclient) wrote a debugging message to stdout
which actually was the encrypted stream.
/MaF
