You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Goldstein Lyor (JIRA)" <ji...@apache.org> on 2017/10/11 17:40:00 UTC

[jira] [Resolved] (SSHD-776) SSHD local port forwarding close session unexpectedly

     [ https://issues.apache.org/jira/browse/SSHD-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Goldstein Lyor resolved SSHD-776.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.0

Thanks a lot for the contribution - merged (after few minor changes - please review just in case I missed something) with [appropriate credit|https://github.com/apache/mina-sshd/commit/0e99597aceb035d271f0140348df23d32b5e3bcd].

{quote}
checking RFC there is the same level of ambiguity
{quote}
I also re-read the RFC and I noticed the strangest thing - there is no recommendation (at least that I noticed) as to what to do if receiving *any* message intended for a channel that does not exist. Theoretically, we could ignore *all* such messages...

> SSHD local port forwarding close session unexpectedly
> -----------------------------------------------------
>
>                 Key: SSHD-776
>                 URL: https://issues.apache.org/jira/browse/SSHD-776
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Fulvio Cavarretta
>            Assignee: Goldstein Lyor
>              Labels: channel, eof, forwarding, sshd
>             Fix For: 1.7.0
>
>         Attachments: dmzagent-1.7.0-snapshot.trc, dmzagent-WriteAbortException.trc, dmzagent.trc, dmzagent.trc.2, sshd.SSHD-776.patch
>
>
> Apache SSHD used in local port forwarding mode.
> A client is connecting to a remote FTP server through Apache SSHD via a custom software.
> When a new logical channel inside a single SSHD session get an IO error (e.g. the remote destination close the connection suddenly, the whole session is shut down causing all other logical channel to be closed (see line 8861of attached trace file).
> It seems like the _exceptionCaught_ mathod should not be called in this case



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)