Clarification to the channel closure procedure in Secure Shell (SSH)
draft-sgtatham-secsh-closure-race-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Simon Tatham , Damien Miller | ||
| Last updated | 2016-11-14 (Latest revision 2016-05-04) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo identifies an ambiguity in the Secure Shell (SSH) connection protocol defined by RFC 4254 regarding the handling of channel closure in combination with channel requests requiring a reply, and issues a clarification specifying the correct interpretation of the ambiguous point.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)