[
https://issues.apache.org/jira/browse/SSHD-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor resolved SSHD-777.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.7.0
> Make the code handling channels more error tolerant
> ---------------------------------------------------
>
> Key: SSHD-777
> URL: https://issues.apache.org/jira/browse/SSHD-777
> Project: MINA SSHD
> Issue Type: Improvement
> Affects Versions: 1.6.0
> Reporter: Goldstein Lyor
> Assignee: Goldstein Lyor
> Labels: channel, exception-handling, session, ssh, sshd
> Fix For: 1.7.0
>
>
> h5. Background
> [RFC 4254|https://tools.ietf.org/html/rfc4254] describes the channels
> protocol, but it does not seem to contain any clear recommendation as to how
> to handle protocol errors - except for the channel setup phase. In other
> words, once a channel is established, there is no way to signal to the peer
> that it has violated the protocol by sending a malformed message, an
> unexpected one or even one that references an unknown channel.
> The current code usually throws an exception that causes the *session* to
> terminate as well (except for EOF, CLOSE and WINDOW_ADJUST) - as demonstrated
> by SSHD-776. The discussions of this issue have also raised the claim that
> the code should be "tolerant" as to such channel exception and not affect the
> whole session.
> h5. Implementation details
> * Consider adding a {{ChannelErrorMessageHandler}} that users can register
> that can regulate this behavior and let the user decide how to handle the
> exception.
> * Provide some built-in implementations - e.g., IGNORE (default ?) and FAIL
> (closes the session)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
