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 2015/12/07 10:51:10 UTC

[jira] [Updated] (SSHD-609) Session does not disconnect if unknown compression factory requested

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

Goldstein Lyor updated SSHD-609:
--------------------------------
    Description: The current code does not distinguish between a non-existing compression factory and the 'none' compression value. More specifically, if the selected compression factory no longer exists, or it does not create a _Compression_ instance it will assume a 'none' compression. In normal operation such a flow is unlikely since the negotiation phase usually fails long before the negotiated parameters are translated into implementations. However, due to the many new exposed APIs the user can intervene and / or override some methods so that (inadvertently) the negotiated compression seems to be 'none' when in effect it isn't.  (was: The current code does not distinguish between a non-existing compression factory and the 'none' compression value.)

> Session does not disconnect if unknown compression factory requested
> --------------------------------------------------------------------
>
>                 Key: SSHD-609
>                 URL: https://issues.apache.org/jira/browse/SSHD-609
>             Project: MINA SSHD
>          Issue Type: Bug
>            Reporter: Goldstein Lyor
>            Assignee: Goldstein Lyor
>            Priority: Minor
>
> The current code does not distinguish between a non-existing compression factory and the 'none' compression value. More specifically, if the selected compression factory no longer exists, or it does not create a _Compression_ instance it will assume a 'none' compression. In normal operation such a flow is unlikely since the negotiation phase usually fails long before the negotiated parameters are translated into implementations. However, due to the many new exposed APIs the user can intervene and / or override some methods so that (inadvertently) the negotiated compression seems to be 'none' when in effect it isn't.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)