On Tue, May 08, 2012 at 11:51:20PM +0800, Matt Johnston wrote: > > The RFC is fairly clear that there should be only one > SSH_MSG_CHANNEL_CLOSE for a channel. See > https://www.ietf.org/rfc/rfc4254.txt section 5.3.
Hello Matt, I think you are right, although it is (IMHO) not explicitly stated. With a short scan for keywords I did not find a specification what to do when SSH_MSG_CHANNEL_CLOSE is received with a wrong channel number, so the behaviour in this case is at least undefined. > I'd prefer to avoid workarounds in this case. It was not intended as a request for a workaround, only as a question for discussion or an idea to make future versions more robust. According to the activity in the bugtracker, SSH.NET is not yet in a stable state, so I will mainly fix this library. Another reason is that the software which uses this library is still in development, so we can do whatever is necessary here. I would not use a newer version of dropbear (with possible changes) unless I cannot solve my problem in any other way. I'm developing software for an industrial device which should be based on a well defined and tested operating system and build environment, so I avoid changing anything in the base system. Thanks for your help. Bodo
signature.asc
Description: Digital signature
