[Bug 1818] SSH2_MSG_CHANNEL_FAILURE on closed channel

[bugzilla-daemon at bugzilla.mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=1818

--- Comment #5 from Simon Tatham <anakin at pobox.com> 2010-09-14 17:37:42 EST ---
Because if you send anything that arrives at the other side when _it_
thinks the channel is fully closed, that's definitely in violation of
5.3. So if you send stuff after you've sent CLOSE, then it _might_
cross in transit with the other side's CLOSE, in which case it would
arrive at the other side when that side had already both sent and
received CLOSE.

I discussed this last night with a friend, and he pointed out that
there is an alternative protocol fix which also works, but it's more
clearly contradictory of explicit text in the RFC. Instead of ruling
that requests received after we send CLOSE may not be responded to, we
could instead rule that all requests are responded to and modify
section 5.3 to state that a channel number may be reused after you have
both sent and received CLOSE _and_ received replies to all outstanding
channel requests.

However, it's clear that the current situation leads to a problem, so
_something_ needs fixing one way or the other. If you don't agree with
my analysis, should we take this to ietf-secsh and see if we can get a
consensus?

-- 
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.