On Sun, Dec 18, 2005 at 08:48:35PM +0100, Florian Weimer wrote: > * Wichert Akkerman: > > debug1: Remote protocol version 2.0, remote software version mpSSH_0.0.1 > > debug1: no match: mpSSH_0.0.1 > > Find out what (Open)SSH version this actually is, we can then add a > regexp to set the proper compatibility flags.
I suspect that this will not be enough, although it would certainly be useful on general principles. The message on which we're getting dispatch_protocol_error is SSH2_MSG_CHANNEL_FAILURE. We've discovered that disabling SendEnv is a workaround. My initial reaction was that this meant that the OpenSSH client is not prepared for the possibility of a server that does not support the "env" channel request. However, on further investigation I discovered that OpenSSH sets the "want reply" flag in that channel request to false; mpSSH appears not to be honouring that flag the way that http://www.ietf.org/internet-drafts/draft-ietf-secsh-connect-25.txt (expired draft though it is) says it should. I don't see any bug-compatibility handling for this case in OpenSSH at the moment. For further head-scratching value, when I deliberately break an OpenSSH server so that it doesn't understand the "env" channel request and fails to honour the "want reply" flag, the client emits the dispatch_protocol_error messages noted by Wichert but manages to connect anyway; so something more is going on here. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
