[jira] [Resolved] (SSHD-638) Use smart buffer HEX data dump logging to accommodate large buffers

[ https://issues.apache.org/jira/browse/SSHD-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goldstein Lyor resolved SSHD-638. - Resolution: Fixed Fix Version/s: 1.2.0 > Use smart buffer HEX data dump logging to

[jira] [Commented] (SSHD-634) Suspicious read buffer re-use in write command

[ https://issues.apache.org/jira/browse/SSHD-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129814#comment-15129814 ] Goldstein Lyor commented on SSHD-634: - In _AbstractSession#decode()_ method locate the following lines:

[jira] [Work started] (SSHD-635) potential hang in AuthFuture.verify(Long.MAX_VALUE) on error

[ https://issues.apache.org/jira/browse/SSHD-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SSHD-635 started by Goldstein Lyor. --- > potential hang in AuthFuture.verify(Long.MAX_VALUE) on error >

[jira] [Assigned] (SSHD-635) potential hang in AuthFuture.verify(Long.MAX_VALUE) on error

[ https://issues.apache.org/jira/browse/SSHD-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goldstein Lyor reassigned SSHD-635: --- Assignee: Goldstein Lyor > potential hang in AuthFuture.verify(Long.MAX_VALUE) on error >

[jira] [Work stopped] (SSHD-635) potential hang in AuthFuture.verify(Long.MAX_VALUE) on error

[ https://issues.apache.org/jira/browse/SSHD-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SSHD-635 stopped by Goldstein Lyor. --- > potential hang in AuthFuture.verify(Long.MAX_VALUE) on error >

[jira] [Assigned] (SSHD-635) potential hang in AuthFuture.verify(Long.MAX_VALUE) on error

[ https://issues.apache.org/jira/browse/SSHD-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goldstein Lyor reassigned SSHD-635: --- Assignee: (was: Goldstein Lyor) > potential hang in AuthFuture.verify(Long.MAX_VALUE) on

[jira] [Created] (SSHD-639) Review code and reduce buffer re-use

Goldstein Lyor created SSHD-639: --- Summary: Review code and reduce buffer re-use Key: SSHD-639 URL: https://issues.apache.org/jira/browse/SSHD-639 Project: MINA SSHD Issue Type: Improvement

[jira] [Work stopped] (SSHD-638) Use smart buffer HEX data dump logging to accommodate large buffers

[ https://issues.apache.org/jira/browse/SSHD-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SSHD-638 stopped by Goldstein Lyor. --- > Use smart buffer HEX data dump logging to accommodate large buffers >

[jira] [Commented] (SSHD-634) Suspicious read buffer re-use in write command

[ https://issues.apache.org/jira/browse/SSHD-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128314#comment-15128314 ] Eugene Petrenko commented on SSHD-634: -- What is the best place to add a workaround in current (1.0.0)

Re: [VOTE] MINA 2.0.12 release

+1 (non-binding) On Sun, Jan 31, 2016 at 11:37 PM, Ashish wrote: > +1 > > Build works fine, all test cases passing > > On Sat, Jan 30, 2016 at 11:27 PM, Emmanuel Lécharny > wrote: >> Hi, >> >> Here is a vote for a new bug fix release of Mina :

[jira] [Commented] (SSHD-635) potential hang in AuthFuture.verify(Long.MAX_VALUE) on error

[ https://issues.apache.org/jira/browse/SSHD-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128021#comment-15128021 ] Oliver Stöneberg commented on SSHD-635: --- Unfortunately it's a different issue and I am using 1.1 (or

[jira] [Created] (DIRMINA-1026) Session may be removed twice from the removedSession queue

Emmanuel Lecharny created DIRMINA-1026: -- Summary: Session may be removed twice from the removedSession queue Key: DIRMINA-1026 URL: https://issues.apache.org/jira/browse/DIRMINA-1026 Project:

[jira] [Commented] (SSHD-635) potential hang in AuthFuture.verify(Long.MAX_VALUE) on error

[ https://issues.apache.org/jira/browse/SSHD-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129903#comment-15129903 ] Goldstein Lyor commented on SSHD-635: - I have looked into it and tried to create conditions that can

Cancel, was: [VOTE] MINA 2.0.12 release

Hi guys, I'm trully sorry to have to cancel this vote :/ Radovan found a new corner case where a server might block for ever when using a SSL connection and if the remote peer does not end the connection properly. What happen in this case is that we remove the session from the IoProcessor, and

[jira] [Commented] (SSHD-635) potential hang in AuthFuture.verify(Long.MAX_VALUE) on error

[ https://issues.apache.org/jira/browse/SSHD-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128191#comment-15128191 ] Goldstein Lyor commented on SSHD-635: - You are right - I think I can see where something like this could

[jira] [Work stopped] (SSHD-634) Suspicious read buffer re-use in write command

[ https://issues.apache.org/jira/browse/SSHD-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SSHD-634 stopped by Goldstein Lyor. --- > Suspicious read buffer re-use in write command >

[jira] [Resolved] (SSHD-634) Suspicious read buffer re-use in write command

[ https://issues.apache.org/jira/browse/SSHD-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goldstein Lyor resolved SSHD-634. - Resolution: Fixed Fix Version/s: 1.2.0 > Suspicious read buffer re-use in write command >

[jira] [Commented] (SSHD-634) Suspicious read buffer re-use in write command

[ https://issues.apache.org/jira/browse/SSHD-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128181#comment-15128181 ] Goldstein Lyor commented on SSHD-634: - The problem does exist and it seems to be related to the re-use