[jira] [Commented] (SSHD-1037) private openssh key parsing error
[ https://issues.apache.org/jira/browse/SSHD-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160877#comment-17160877 ] Sandeep commented on SSHD-1037: --- [~lgoldstein] & [~wolft] Thanks for the clarification. I will consider all the above points and will do needful. > private openssh key parsing error > - > > Key: SSHD-1037 > URL: https://issues.apache.org/jira/browse/SSHD-1037 > Project: MINA SSHD > Issue Type: Question >Reporter: Sandeep >Priority: Major > Attachments: KeyGenerationTest.java, console_log, junit_test_output, > parsing_java_method > > > Hi Team, > I am not able to parse openssh key with the help of > *OpenSSHKeyPairResourceParser* class > Java code and log is attached. > Passwork of key is : RoldWtzuRB089Dztx7MmsIxe799c2MIL > Key is as follows, > -BEGIN OPENSSH PRIVATE KEY- > b3BlbnNzaC1rZXktdjEACmFlczEyOC1jYmMGYmNyeXB0GBAM > JEJgXHPG6QrP1OWVzu6TEAEAAACXB3NzaC1yc2EDAQAB > gQCqpdnaIOxhfmKQbiM3TtJPOofzCeQ0tC5jUyB/jEo2BLg8FZ0I/LNm0gSVD9DP > o/EJbFsHHGtX8iSB2t2mdszaJd1PX3e/5qEFm7P0tbqhp4sI+dgV+X3wvjADYBND > 6PS44vTgd9MY8zyB24wDoj5gRM/w/FW67EtgwTdYzmExtwAAAfFLV4x18tC9tXX1 > 5nBqQuHpZezdrY3z2MS5cq8eb8o/+CdHvlBtjvcob8Stm8+3QXx7HMRDhoZhn+Pa > EufIsRZ5Ta4XseJ2ukDeEzVZSa7hRrR56B3UUGhvKPEyMcQu33xH0/wsqoO8cmBs > GxqDKSRBw26lj7OFZT7cIgsv/zAr67Q+ycX7OpXa8TlKZw3qrO1HZXNkZtY4ooO/ > nDuDfmOKVlbZ4HWcPXpcbojI6r0LLOhte4czLv3sQskEkJkzlnG62oLA2zrpvGlw > 7u/uOtvuWNTwwFxJfQwwpiZRuACJIpyEJsTA+156SG0X+AIpAy8b6l3cOTLo00EP > JbW20l8K+DdMvT0RWr895KaI7vcs30JeFmysm8eMKTUdVDgu2Sy8Qd/1GMhi1AZy > peUWzvQNjauSwDoyJka5go0gUOa1biCl9o67Oy07estHnfeoK8NGcjmv14U1BP2a > 0KzazesOxvbalr6hlgq1DAVTvpSRw1vAAx4xE1RrVA3qNMcFf3W8tOf7WQCO9J5m > +o31L5Wiuh9uvPGN7tLbR1eOuwYMH7ICz0Ydvfkg5UFaFIYz8pUInLFFFle/YUMw > KEtFrJKYItON25XcpqciorilWXJw0BdK7w/aeHoOVxOQer2PSj36J/jn0oC64guP > g6SHko7U4Q== > -END OPENSSH PRIVATE KEY- > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (SSHD-1020) SSH connections getting closed abruptly with timeout exceptions. java.nio.channels.InterruptedByTimeoutException
[
https://issues.apache.org/jira/browse/SSHD-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160819#comment-17160819
]
Guillermo Grandes edited comment on SSHD-1020 at 7/19/20, 9:23 PM:
---
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 22:58:58,571 [::] WARN
org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.X.CLI:22])[state=Opened]
InterruptedByTimeoutException: null
{code}
tcpdump:
{code:none}
22:58:35.977985 length 138: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [P.],
seq 1804:1888, ack 2254, win 510, length 84
22:58:35.978117 length 54: 192.168.X.SRV.22 > 192.168.X.CLI.50651: Flags [.],
ack 1888, win 501, length 0
22:58:45.975468 length 138: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [P.],
seq 1888:1972, ack 2254, win 510, length 84
22:58:45.975506 length 54: 192.168.X.SRV.22 > 192.168.X.CLI.50651: Flags [.],
ack 1972, win 501, length 0
22:58:55.984296 length 138: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [P.],
seq 1972:2056, ack 2254, win 510, length 84
22:58:55.984333 length 54: 192.168.X.SRV.22 > 192.168.X.CLI.50651: Flags [.],
ack 2056, win 501, length 0
22:58:56.341180 length 60: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [R.],
seq 2056, ack 2254, win 0, length 0
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
My first question was there is alternative to HeartbeatType.IGNORE that
force response from server?
{code:java}
// This don't work eigther:
PropertyResolverUtils.updateProperty(client,
ClientFactoryManager.HEARTBEAT_INTERVAL, TimeUnit.SECONDS.toMillis(10L));
{code}
was (Author: technobcn):
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 22:58:58,571 [::] WARN
org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.X.CLI:22])[state=Opened]
InterruptedByTimeoutException: null
{code}
tcpdump:
{code:none}
22:58:35.977985 length 138: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [P.],
seq 1804:1888, ack 2254, win 510, length 84
22:58:35.978117 length 54: 192.168.X.SRV.22 > 192.168.X.CLI.50651: Flags [.],
ack 1888, win 501, length 0
22:58:45.975468 length 138: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [P.],
seq 1888:1972, ack 2254, win 510, length 84
22:58:45.975506 length 54: 192.168.X.SRV.22 > 192.168.X.CLI.50651: Flags [.],
ack 1972, win 501, length 0
22:58:55.984296 length 138: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [P.],
seq 1972:2056, ack 2254, win 510, length 84
22:58:55.984333 length 54: 192.168.X.SRV.22 > 192.168.X.CLI.50651: Flags [.],
ack 2056, win 501, length 0
22:58:56.341180 length 60: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [R.],
seq 2056, ack 2254, win 0, length 0
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
My first question was there is alternative to HeartbeatType.IGNORE that
force response from server?
> SSH connections getting closed abruptly with timeout exceptions.
> java.nio.channels.InterruptedByTimeoutException
>
>
> Key: SSHD-1020
> URL: https://issues.apache.org/jira/browse/SSHD-1020
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sivanagarajup
>Priority: Blocker
> Attachments: image-2020-06-26-15-18-58-509.png,
> image-2020-06-26-15-22-17-259.png, server.log
>
>
> Hi Team
> SSH sessions are closing with timeout exceptions as mentioned below
> {code:java}
> 2020-06-18 03:07:11,942 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,942 DEBUG
> [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,943 WARN
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](p
[jira] [Comment Edited] (SSHD-1020) SSH connections getting closed abruptly with timeout exceptions. java.nio.channels.InterruptedByTimeoutException
[
https://issues.apache.org/jira/browse/SSHD-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160819#comment-17160819
]
Guillermo Grandes edited comment on SSHD-1020 at 7/19/20, 9:02 PM:
---
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 22:58:58,571 [::] WARN
org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.X.CLI:22])[state=Opened]
InterruptedByTimeoutException: null
{code}
tcpdump:
{code:none}
22:58:35.977985 length 138: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [P.],
seq 1804:1888, ack 2254, win 510, length 84
22:58:35.978117 length 54: 192.168.X.SRV.22 > 192.168.X.CLI.50651: Flags [.],
ack 1888, win 501, length 0
22:58:45.975468 length 138: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [P.],
seq 1888:1972, ack 2254, win 510, length 84
22:58:45.975506 length 54: 192.168.X.SRV.22 > 192.168.X.CLI.50651: Flags [.],
ack 1972, win 501, length 0
22:58:55.984296 length 138: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [P.],
seq 1972:2056, ack 2254, win 510, length 84
22:58:55.984333 length 54: 192.168.X.SRV.22 > 192.168.X.CLI.50651: Flags [.],
ack 2056, win 501, length 0
22:58:56.341180 length 60: 192.168.X.CLI.50651 > 192.168.X.SRV.22: Flags [R.],
seq 2056, ack 2254, win 0, length 0
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
My first question was there is alternative to HeartbeatType.IGNORE that
force response from server?
was (Author: technobcn):
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 22:58:58,571 [::] WARN
org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.X.CLI:22])[state=Opened]
InterruptedByTimeoutException: null
{code}
tcpdump:
{code:none}
22:58:35.977985 length 138: 192.168.X.CLIENT.50651 > 192.168.X.SERVER.22: Flags
[P.], seq 1804:1888, ack 2254, win 510, length 84
22:58:35.978117 length 54: 192.168.X.SERVER.22 > 192.168.X.CLIENT.50651: Flags
[.], ack 1888, win 501, length 0
22:58:45.975468 length 138: 192.168.X.CLIENT.50651 > 192.168.X.SERVER.22: Flags
[P.], seq 1888:1972, ack 2254, win 510, length 84
22:58:45.975506 length 54: 192.168.X.SERVER.22 > 192.168.X.CLIENT.50651: Flags
[.], ack 1972, win 501, length 0
22:58:55.984296 length 138: 192.168.X.CLIENT.50651 > 192.168.X.SERVER.22: Flags
[P.], seq 1972:2056, ack 2254, win 510, length 84
22:58:55.984333 length 54: 192.168.X.SERVER.22 > 192.168.X.CLIENT.50651: Flags
[.], ack 2056, win 501, length 0
22:58:56.341180 length 60: 192.168.X.CLIENT.50651 > 192.168.X.SERVER.22: Flags
[R.], seq 2056, ack 2254, win 0, length 0
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
My first question was there is alternative to HeartbeatType.IGNORE that
force response from server?
> SSH connections getting closed abruptly with timeout exceptions.
> java.nio.channels.InterruptedByTimeoutException
>
>
> Key: SSHD-1020
> URL: https://issues.apache.org/jira/browse/SSHD-1020
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sivanagarajup
>Priority: Blocker
> Attachments: image-2020-06-26-15-18-58-509.png,
> image-2020-06-26-15-22-17-259.png, server.log
>
>
> Hi Team
> SSH sessions are closing with timeout exceptions as mentioned below
> {code:java}
> 2020-06-18 03:07:11,942 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,942 DEBUG
> [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,943 WARN
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> InterruptedByT
[jira] [Comment Edited] (SSHD-1020) SSH connections getting closed abruptly with timeout exceptions. java.nio.channels.InterruptedByTimeoutException
[
https://issues.apache.org/jira/browse/SSHD-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160819#comment-17160819
]
Guillermo Grandes edited comment on SSHD-1020 at 7/19/20, 9:02 PM:
---
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 22:58:58,571 [::] WARN
org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.X.CLI:22])[state=Opened]
InterruptedByTimeoutException: null
{code}
tcpdump:
{code:none}
22:58:35.977985 length 138: 192.168.X.CLIENT.50651 > 192.168.X.SERVER.22: Flags
[P.], seq 1804:1888, ack 2254, win 510, length 84
22:58:35.978117 length 54: 192.168.X.SERVER.22 > 192.168.X.CLIENT.50651: Flags
[.], ack 1888, win 501, length 0
22:58:45.975468 length 138: 192.168.X.CLIENT.50651 > 192.168.X.SERVER.22: Flags
[P.], seq 1888:1972, ack 2254, win 510, length 84
22:58:45.975506 length 54: 192.168.X.SERVER.22 > 192.168.X.CLIENT.50651: Flags
[.], ack 1972, win 501, length 0
22:58:55.984296 length 138: 192.168.X.CLIENT.50651 > 192.168.X.SERVER.22: Flags
[P.], seq 1972:2056, ack 2254, win 510, length 84
22:58:55.984333 length 54: 192.168.X.SERVER.22 > 192.168.X.CLIENT.50651: Flags
[.], ack 2056, win 501, length 0
22:58:56.341180 length 60: 192.168.X.CLIENT.50651 > 192.168.X.SERVER.22: Flags
[R.], seq 2056, ack 2254, win 0, length 0
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
My first question was there is alternative to HeartbeatType.IGNORE that
force response from server?
was (Author: technobcn):
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 22:58:58,571 [::] WARN
org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.X.CLI:22])[state=Opened]
InterruptedByTimeoutException: null
{code}
tcpdump:
{code:none}
22:58:35.977985 length 138: 192.168.X.SRV.50651 > 192.168.X.CLI.22: Flags [P.],
seq 1804:1888, ack 2254, win 510, length 84
22:58:35.978117 length 54: 192.168.X.CLI.22 > 192.168.X.SRV.50651: Flags [.],
ack 1888, win 501, length 0
22:58:45.975468 length 138: 192.168.X.SRV.50651 > 192.168.X.CLI.22: Flags [P.],
seq 1888:1972, ack 2254, win 510, length 84
22:58:45.975506 length 54: 192.168.X.CLI.22 > 192.168.X.SRV.50651: Flags [.],
ack 1972, win 501, length 0
22:58:55.984296 length 138: 192.168.X.SRV.50651 > 192.168.X.CLI.22: Flags [P.],
seq 1972:2056, ack 2254, win 510, length 84
22:58:55.984333 length 54: 192.168.X.CLI.22 > 192.168.X.SRV.50651: Flags [.],
ack 2056, win 501, length 0
22:58:56.341180 length 60: 192.168.X.SRV.50651 > 192.168.X.CLI.22: Flags [R.],
seq 2056, ack 2254, win 0, length 0
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
My first question was there is alternative to HeartbeatType.IGNORE that
force response from server?
> SSH connections getting closed abruptly with timeout exceptions.
> java.nio.channels.InterruptedByTimeoutException
>
>
> Key: SSHD-1020
> URL: https://issues.apache.org/jira/browse/SSHD-1020
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sivanagarajup
>Priority: Blocker
> Attachments: image-2020-06-26-15-18-58-509.png,
> image-2020-06-26-15-22-17-259.png, server.log
>
>
> Hi Team
> SSH sessions are closing with timeout exceptions as mentioned below
> {code:java}
> 2020-06-18 03:07:11,942 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,942 DEBUG
> [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,943 WARN
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> InterruptedByT
[jira] [Comment Edited] (SSHD-1020) SSH connections getting closed abruptly with timeout exceptions. java.nio.channels.InterruptedByTimeoutException
[
https://issues.apache.org/jira/browse/SSHD-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160819#comment-17160819
]
Guillermo Grandes edited comment on SSHD-1020 at 7/19/20, 9:00 PM:
---
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 22:58:58,571 [::] WARN
org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.X.CLI:22])[state=Opened]
InterruptedByTimeoutException: null
{code}
tcpdump:
{code:none}
22:58:35.977985 length 138: 192.168.X.SRV.50651 > 192.168.X.CLI.22: Flags [P.],
seq 1804:1888, ack 2254, win 510, length 84
22:58:35.978117 length 54: 192.168.X.CLI.22 > 192.168.X.SRV.50651: Flags [.],
ack 1888, win 501, length 0
22:58:45.975468 length 138: 192.168.X.SRV.50651 > 192.168.X.CLI.22: Flags [P.],
seq 1888:1972, ack 2254, win 510, length 84
22:58:45.975506 length 54: 192.168.X.CLI.22 > 192.168.X.SRV.50651: Flags [.],
ack 1972, win 501, length 0
22:58:55.984296 length 138: 192.168.X.SRV.50651 > 192.168.X.CLI.22: Flags [P.],
seq 1972:2056, ack 2254, win 510, length 84
22:58:55.984333 length 54: 192.168.X.CLI.22 > 192.168.X.SRV.50651: Flags [.],
ack 2056, win 501, length 0
22:58:56.341180 length 60: 192.168.X.SRV.50651 > 192.168.X.CLI.22: Flags [R.],
seq 2056, ack 2254, win 0, length 0
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
My first question was there is alternative to HeartbeatType.IGNORE that
force response from server?
was (Author: technobcn):
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 12:57:22,465 WARN org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.x.x:22]) [state=Opened]
InterruptedByTimeoutException: null
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
My first question was there is alternative to HeartbeatType.IGNORE that
force response from server?
> SSH connections getting closed abruptly with timeout exceptions.
> java.nio.channels.InterruptedByTimeoutException
>
>
> Key: SSHD-1020
> URL: https://issues.apache.org/jira/browse/SSHD-1020
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sivanagarajup
>Priority: Blocker
> Attachments: image-2020-06-26-15-18-58-509.png,
> image-2020-06-26-15-22-17-259.png, server.log
>
>
> Hi Team
> SSH sessions are closing with timeout exceptions as mentioned below
> {code:java}
> 2020-06-18 03:07:11,942 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,942 DEBUG
> [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,943 WARN
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> InterruptedByTimeoutException: null2020-06-18 03:07:11,943 DEBUG
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> details: java.nio.channels.InterruptedByTimeoutException at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_231]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [rt.jar:1.8.0
[jira] [Comment Edited] (SSHD-1020) SSH connections getting closed abruptly with timeout exceptions. java.nio.channels.InterruptedByTimeoutException
[
https://issues.apache.org/jira/browse/SSHD-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160819#comment-17160819
]
Guillermo Grandes edited comment on SSHD-1020 at 7/19/20, 8:56 PM:
---
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 12:57:22,465 WARN org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.x.x:22]) [state=Opened]
InterruptedByTimeoutException: null
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
My first question was there is alternative to HeartbeatType.IGNORE that
force response from server?
was (Author: technobcn):
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 12:57:22,465 WARN org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.x.x:22]) [state=Opened]
InterruptedByTimeoutException: null
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
> SSH connections getting closed abruptly with timeout exceptions.
> java.nio.channels.InterruptedByTimeoutException
>
>
> Key: SSHD-1020
> URL: https://issues.apache.org/jira/browse/SSHD-1020
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sivanagarajup
>Priority: Blocker
> Attachments: image-2020-06-26-15-18-58-509.png,
> image-2020-06-26-15-22-17-259.png, server.log
>
>
> Hi Team
> SSH sessions are closing with timeout exceptions as mentioned below
> {code:java}
> 2020-06-18 03:07:11,942 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,942 DEBUG
> [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,943 WARN
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> InterruptedByTimeoutException: null2020-06-18 03:07:11,943 DEBUG
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> details: java.nio.channels.InterruptedByTimeoutException at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_231]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_231] at java.lang.Thread.run(Thread.java:748)
> [rt.jar:1.8.0_231]
> 2020-06-18 03:07:11,945 DEBUG
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionException(ServerSessionImpl[clientNBI@/20.24.16.108:41480])
> InterruptedByTimeoutException: null2020-06-18 03:07:11,945 TRACE
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionException(ServerSessionImpl[clientNBI@/20.24.16.108:41480]) details:
> java.nio.channels.InterruptedByTimeoutException at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
> [rt.jar:1.8.0_231] at
[jira] [Commented] (SSHD-1020) SSH connections getting closed abruptly with timeout exceptions. java.nio.channels.InterruptedByTimeoutException
[
https://issues.apache.org/jira/browse/SSHD-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160819#comment-17160819
]
Guillermo Grandes commented on SSHD-1020:
-
Hi, I have same problem with 2.5.1:
{code:none}
2020-07-19 12:57:22,465 WARN org.apache.sshd.client.session.ClientSessionImpl
exceptionCaught(ClientSessionImpl[test@/192.168.x.x:22]) [state=Opened]
InterruptedByTimeoutException: null
{code}
Steps to reproduce (same SSHClient#test() from SSHD-1033) with:
{code:java}
// Client Side (SSHD-CORE)
client.setSessionHeartbeat(HeartbeatType.IGNORE, TimeUnit.SECONDS, 10);
PropertyResolverUtils.updateProperty(client, FactoryManager.NIO2_READ_TIMEOUT,
TimeUnit.SECONDS.toMillis(30L));
{code}
Server Side (openssh):
{code:none}
ClientAliveInterval 0
{code}
> SSH connections getting closed abruptly with timeout exceptions.
> java.nio.channels.InterruptedByTimeoutException
>
>
> Key: SSHD-1020
> URL: https://issues.apache.org/jira/browse/SSHD-1020
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sivanagarajup
>Priority: Blocker
> Attachments: image-2020-06-26-15-18-58-509.png,
> image-2020-06-26-15-22-17-259.png, server.log
>
>
> Hi Team
> SSH sessions are closing with timeout exceptions as mentioned below
> {code:java}
> 2020-06-18 03:07:11,942 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,942 DEBUG
> [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,943 WARN
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> InterruptedByTimeoutException: null2020-06-18 03:07:11,943 DEBUG
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> details: java.nio.channels.InterruptedByTimeoutException at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_231]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_231] at java.lang.Thread.run(Thread.java:748)
> [rt.jar:1.8.0_231]
> 2020-06-18 03:07:11,945 DEBUG
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionException(ServerSessionImpl[clientNBI@/20.24.16.108:41480])
> InterruptedByTimeoutException: null2020-06-18 03:07:11,945 TRACE
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionException(ServerSessionImpl[clientNBI@/20.24.16.108:41480]) details:
> java.nio.channels.InterruptedByTimeoutException at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_231]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_231] at java.lang.Thread.run(Thread.java:748)
> [rt.jar:1.8.0_231]
> 2020-06-18 03:07:11,946 DEBUG
> [org.a
[jira] [Commented] (SSHD-1020) SSH connections getting closed abruptly with timeout exceptions. java.nio.channels.InterruptedByTimeoutException
[
https://issues.apache.org/jira/browse/SSHD-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160811#comment-17160811
]
Guillaume Nodet commented on SSHD-1020:
---
Actually, this is not possible, as the channel is not recoverable after a
failure, so I guess the best option would be to the *nio2-read-timeout* to a
very big value.
> SSH connections getting closed abruptly with timeout exceptions.
> java.nio.channels.InterruptedByTimeoutException
>
>
> Key: SSHD-1020
> URL: https://issues.apache.org/jira/browse/SSHD-1020
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sivanagarajup
>Priority: Blocker
> Attachments: image-2020-06-26-15-18-58-509.png,
> image-2020-06-26-15-22-17-259.png, server.log
>
>
> Hi Team
> SSH sessions are closing with timeout exceptions as mentioned below
> {code:java}
> 2020-06-18 03:07:11,942 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,942 DEBUG
> [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,943 WARN
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> InterruptedByTimeoutException: null2020-06-18 03:07:11,943 DEBUG
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> details: java.nio.channels.InterruptedByTimeoutException at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_231]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_231] at java.lang.Thread.run(Thread.java:748)
> [rt.jar:1.8.0_231]
> 2020-06-18 03:07:11,945 DEBUG
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionException(ServerSessionImpl[clientNBI@/20.24.16.108:41480])
> InterruptedByTimeoutException: null2020-06-18 03:07:11,945 TRACE
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionException(ServerSessionImpl[clientNBI@/20.24.16.108:41480]) details:
> java.nio.channels.InterruptedByTimeoutException at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_231]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_231] at java.lang.Thread.run(Thread.java:748)
> [rt.jar:1.8.0_231]
> 2020-06-18 03:07:11,946 DEBUG
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionClosed(ServerSessionImpl[clientNBI@/20.24.16.108:41480])
> un-tracked2020-06-18 03:07:11,946 DEBUG
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> close(ServerSessionImpl[clientNBI@/20.24.16.108:41480]) Closing
> immediately2020-06-18 03:07:11,946 TR
[jira] [Commented] (SSHD-1032) java.lang.ArrayIndexOutOfBoundsException arraycopy
[
https://issues.apache.org/jira/browse/SSHD-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160809#comment-17160809
]
Evgeny Pasynkov commented on SSHD-1032:
---
Nope, the buffer is not reused. The write loop looks like this (in Kotlin): -
it just reads data portion from pipe and sends it into SSH channel
{code:java}
do {
val buffer = ByteArray(8192)
val read = pipe.read(buffer)
if (read > 0) {
try {
ioOut.writePacket(ByteArrayBuffer(buffer, 0, read,
true)).awaitWrite()
} catch (ex: Throwable) {
throw IOException("Error writing $read bytes. Channel: ${ioOut}",
ex)
}
}
} while (read > 0)
{code}
I will do exhaustive testing tomorrow with debug logging enabled, and hopefully
will provide logs with more details
> java.lang.ArrayIndexOutOfBoundsException arraycopy
> --
>
> Key: SSHD-1032
> URL: https://issues.apache.org/jira/browse/SSHD-1032
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Evgeny Pasynkov
>Priority: Major
>
> When invoking writePacket, I quite often get the following exception:
> {noformat}
> Caused by: java.lang.ArrayIndexOutOfBoundsException arraycopy: last source
> index 32768 out of bounds for byte[8192]
> at java.base/java.lang.System.arraycopy(Native Method)
> at
> org.apache.sshd.common.util.buffer.ByteArrayBuffer.putRawBytes(ByteArrayBuffer.java:230)
>
> at
> org.apache.sshd.common.channel.ChannelAsyncOutputStream.createSendBuffer(ChannelAsyncOutputStream.java:229)
>
> at
> org.apache.sshd.common.channel.ChannelAsyncOutputStream.doWriteIfPossible(ChannelAsyncOutputStream.java:164)
>
> at
> org.apache.sshd.common.channel.ChannelAsyncOutputStream.writePacket(ChannelAsyncOutputStream.java:70){noformat}
> This never happened in 2.4.0, so it is definitely a regression
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (SSHD-1020) SSH connections getting closed abruptly with timeout exceptions. java.nio.channels.InterruptedByTimeoutException
[
https://issues.apache.org/jira/browse/SSHD-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160804#comment-17160804
]
Guillaume Nodet commented on SSHD-1020:
---
I don't really understand why the read timeout should cause the session to
close. It looks like such exception is recoverable and we should perform the
read operation again instead of closing the connection. Do you agree
[~lgoldstein] ?
> SSH connections getting closed abruptly with timeout exceptions.
> java.nio.channels.InterruptedByTimeoutException
>
>
> Key: SSHD-1020
> URL: https://issues.apache.org/jira/browse/SSHD-1020
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sivanagarajup
>Priority: Blocker
> Attachments: image-2020-06-26-15-18-58-509.png,
> image-2020-06-26-15-22-17-259.png, server.log
>
>
> Hi Team
> SSH sessions are closing with timeout exceptions as mentioned below
> {code:java}
> 2020-06-18 03:07:11,942 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,942 DEBUG
> [org.apache.sshd.common.io.nio2.Nio2Session]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(Nio2Session[local=/10.1.2.3:8345,
> remote=/20.24.16.108:41480]) caught InterruptedByTimeoutException[null] -
> calling handler2020-06-18 03:07:11,943 WARN
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> InterruptedByTimeoutException: null2020-06-18 03:07:11,943 DEBUG
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> exceptionCaught(ServerSessionImpl[clientNBI@/20.24.16.108:41480])[state=Opened]
> details: java.nio.channels.InterruptedByTimeoutException at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_231]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_231] at java.lang.Thread.run(Thread.java:748)
> [rt.jar:1.8.0_231]
> 2020-06-18 03:07:11,945 DEBUG
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionException(ServerSessionImpl[clientNBI@/20.24.16.108:41480])
> InterruptedByTimeoutException: null2020-06-18 03:07:11,945 TRACE
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionException(ServerSessionImpl[clientNBI@/20.24.16.108:41480]) details:
> java.nio.channels.InterruptedByTimeoutException at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_231]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_231] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_231] at java.lang.Thread.run(Thread.java:748)
> [rt.jar:1.8.0_231]
> 2020-06-18 03:07:11,946 DEBUG
> [org.apache.sshd.common.session.helpers.SessionTimeoutListener]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> sessionClosed(ServerSessionImpl[clientNBI@/20.24.16.108:41480])
> un-tracked2020-06-18 03:07:11,946 DEBUG
> [org.apache.sshd.server.session.ServerSessionImpl]
> (sshd-SshServer[6c96892e](port=8345)-nio2-thread-1)
> close(ServerSessionImpl[clientN
[jira] [Commented] (SSHD-1032) java.lang.ArrayIndexOutOfBoundsException arraycopy
[
https://issues.apache.org/jira/browse/SSHD-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160802#comment-17160802
]
Guillaume Nodet commented on SSHD-1032:
---
[~xvost] I suspect you are reusing the buffer passed to \{{writePacket}}.
Could that be the case ?
> java.lang.ArrayIndexOutOfBoundsException arraycopy
> --
>
> Key: SSHD-1032
> URL: https://issues.apache.org/jira/browse/SSHD-1032
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Evgeny Pasynkov
>Priority: Major
>
> When invoking writePacket, I quite often get the following exception:
> {noformat}
> Caused by: java.lang.ArrayIndexOutOfBoundsException arraycopy: last source
> index 32768 out of bounds for byte[8192]
> at java.base/java.lang.System.arraycopy(Native Method)
> at
> org.apache.sshd.common.util.buffer.ByteArrayBuffer.putRawBytes(ByteArrayBuffer.java:230)
>
> at
> org.apache.sshd.common.channel.ChannelAsyncOutputStream.createSendBuffer(ChannelAsyncOutputStream.java:229)
>
> at
> org.apache.sshd.common.channel.ChannelAsyncOutputStream.doWriteIfPossible(ChannelAsyncOutputStream.java:164)
>
> at
> org.apache.sshd.common.channel.ChannelAsyncOutputStream.writePacket(ChannelAsyncOutputStream.java:70){noformat}
> This never happened in 2.4.0, so it is definitely a regression
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Resolved] (SSHD-1037) private openssh key parsing error
[ https://issues.apache.org/jira/browse/SSHD-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SSHD-1037. --- Resolution: Won't Fix > private openssh key parsing error > - > > Key: SSHD-1037 > URL: https://issues.apache.org/jira/browse/SSHD-1037 > Project: MINA SSHD > Issue Type: Question >Reporter: Sandeep >Priority: Major > Attachments: KeyGenerationTest.java, console_log, junit_test_output, > parsing_java_method > > > Hi Team, > I am not able to parse openssh key with the help of > *OpenSSHKeyPairResourceParser* class > Java code and log is attached. > Passwork of key is : RoldWtzuRB089Dztx7MmsIxe799c2MIL > Key is as follows, > -BEGIN OPENSSH PRIVATE KEY- > b3BlbnNzaC1rZXktdjEACmFlczEyOC1jYmMGYmNyeXB0GBAM > JEJgXHPG6QrP1OWVzu6TEAEAAACXB3NzaC1yc2EDAQAB > gQCqpdnaIOxhfmKQbiM3TtJPOofzCeQ0tC5jUyB/jEo2BLg8FZ0I/LNm0gSVD9DP > o/EJbFsHHGtX8iSB2t2mdszaJd1PX3e/5qEFm7P0tbqhp4sI+dgV+X3wvjADYBND > 6PS44vTgd9MY8zyB24wDoj5gRM/w/FW67EtgwTdYzmExtwAAAfFLV4x18tC9tXX1 > 5nBqQuHpZezdrY3z2MS5cq8eb8o/+CdHvlBtjvcob8Stm8+3QXx7HMRDhoZhn+Pa > EufIsRZ5Ta4XseJ2ukDeEzVZSa7hRrR56B3UUGhvKPEyMcQu33xH0/wsqoO8cmBs > GxqDKSRBw26lj7OFZT7cIgsv/zAr67Q+ycX7OpXa8TlKZw3qrO1HZXNkZtY4ooO/ > nDuDfmOKVlbZ4HWcPXpcbojI6r0LLOhte4czLv3sQskEkJkzlnG62oLA2zrpvGlw > 7u/uOtvuWNTwwFxJfQwwpiZRuACJIpyEJsTA+156SG0X+AIpAy8b6l3cOTLo00EP > JbW20l8K+DdMvT0RWr895KaI7vcs30JeFmysm8eMKTUdVDgu2Sy8Qd/1GMhi1AZy > peUWzvQNjauSwDoyJka5go0gUOa1biCl9o67Oy07estHnfeoK8NGcjmv14U1BP2a > 0KzazesOxvbalr6hlgq1DAVTvpSRw1vAAx4xE1RrVA3qNMcFf3W8tOf7WQCO9J5m > +o31L5Wiuh9uvPGN7tLbR1eOuwYMH7ICz0Ydvfkg5UFaFIYz8pUInLFFFle/YUMw > KEtFrJKYItON25XcpqciorilWXJw0BdK7w/aeHoOVxOQer2PSj36J/jn0oC64guP > g6SHko7U4Q== > -END OPENSSH PRIVATE KEY- > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (SSHD-1037) private openssh key parsing error
[ https://issues.apache.org/jira/browse/SSHD-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160788#comment-17160788 ] Thomas Wolf commented on SSHD-1037: --- [~ssmali1505], this is a bug in the library you're using, which appears to be maverick-common 2.0.4. The key file they write is not a valid OpenSSH modern format key file. As Lyor has pointed out several times, maverick does not pad the private key. Apache MINA sshd and OpenSSH are correctly refusing to extract a key from that invalid file. > private openssh key parsing error > - > > Key: SSHD-1037 > URL: https://issues.apache.org/jira/browse/SSHD-1037 > Project: MINA SSHD > Issue Type: Question >Reporter: Sandeep >Priority: Major > Attachments: KeyGenerationTest.java, console_log, junit_test_output, > parsing_java_method > > > Hi Team, > I am not able to parse openssh key with the help of > *OpenSSHKeyPairResourceParser* class > Java code and log is attached. > Passwork of key is : RoldWtzuRB089Dztx7MmsIxe799c2MIL > Key is as follows, > -BEGIN OPENSSH PRIVATE KEY- > b3BlbnNzaC1rZXktdjEACmFlczEyOC1jYmMGYmNyeXB0GBAM > JEJgXHPG6QrP1OWVzu6TEAEAAACXB3NzaC1yc2EDAQAB > gQCqpdnaIOxhfmKQbiM3TtJPOofzCeQ0tC5jUyB/jEo2BLg8FZ0I/LNm0gSVD9DP > o/EJbFsHHGtX8iSB2t2mdszaJd1PX3e/5qEFm7P0tbqhp4sI+dgV+X3wvjADYBND > 6PS44vTgd9MY8zyB24wDoj5gRM/w/FW67EtgwTdYzmExtwAAAfFLV4x18tC9tXX1 > 5nBqQuHpZezdrY3z2MS5cq8eb8o/+CdHvlBtjvcob8Stm8+3QXx7HMRDhoZhn+Pa > EufIsRZ5Ta4XseJ2ukDeEzVZSa7hRrR56B3UUGhvKPEyMcQu33xH0/wsqoO8cmBs > GxqDKSRBw26lj7OFZT7cIgsv/zAr67Q+ycX7OpXa8TlKZw3qrO1HZXNkZtY4ooO/ > nDuDfmOKVlbZ4HWcPXpcbojI6r0LLOhte4czLv3sQskEkJkzlnG62oLA2zrpvGlw > 7u/uOtvuWNTwwFxJfQwwpiZRuACJIpyEJsTA+156SG0X+AIpAy8b6l3cOTLo00EP > JbW20l8K+DdMvT0RWr895KaI7vcs30JeFmysm8eMKTUdVDgu2Sy8Qd/1GMhi1AZy > peUWzvQNjauSwDoyJka5go0gUOa1biCl9o67Oy07estHnfeoK8NGcjmv14U1BP2a > 0KzazesOxvbalr6hlgq1DAVTvpSRw1vAAx4xE1RrVA3qNMcFf3W8tOf7WQCO9J5m > +o31L5Wiuh9uvPGN7tLbR1eOuwYMH7ICz0Ydvfkg5UFaFIYz8pUInLFFFle/YUMw > KEtFrJKYItON25XcpqciorilWXJw0BdK7w/aeHoOVxOQer2PSj36J/jn0oC64guP > g6SHko7U4Q== > -END OPENSSH PRIVATE KEY- > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (SSHD-1030) Provide support for NoFileSystemFactoryProvider
[
https://issues.apache.org/jira/browse/SSHD-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160723#comment-17160723
]
Lyor Goldstein commented on SSHD-1030:
--
Implemented {{NoneFileSystemFactory}} - see
https://github.com/lgoldstein/mina-sshd/tree/SSHD-1030. Let me know if it
satisfies your needs.
> Provide support for NoFileSystemFactoryProvider
> ---
>
> Key: SSHD-1030
> URL: https://issues.apache.org/jira/browse/SSHD-1030
> Project: MINA SSHD
> Issue Type: New Feature
>Affects Versions: 2.5.1
>Reporter: David Ostrovsky
>Assignee: Lyor Goldstein
>Priority: Minor
>
> Prior to 2.5.0 release Gerrit was using this was to initialize
> {{FileSystemFactoryProvider}}:
>
> {code:java}
> private void initFileSystemFactory() {
> setFileSystemFactory(
> session ->
> new FileSystem() {
> @Override
> public void close() throws IOException {}
> @Override
> public Iterable getFileStores() {
> return null;
> }
> @Override
> public Path getPath(String arg0, String... arg1) {
> return null;
> }
> @Override
> public PathMatcher getPathMatcher(String arg0) {
> return null;
> }
> @Override
> public Iterable getRootDirectories() {
> return null;
> }
> @Override
> public String getSeparator() {
> return null;
> }
> @Override
> public UserPrincipalLookupService
> getUserPrincipalLookupService() {
> return null;
> }
> @Override
> public boolean isOpen() {
> return false;
> }
> @Override
> public boolean isReadOnly() {
> return false;
> }
> @Override
> public WatchService newWatchService() throws IOException {
> return null;
> }
> @Override
> public FileSystemProvider provider() {
> return null;
> }
> @Override
> public Set supportedFileAttributeViews() {
> return null;
> }
> });
> }
> {code}
> After the migration to release 2.5.1 it doesn't compile any more, because the
> {{FileSystemFactory}} factory is not \{{FunctionalInterface}} any more, as it
> has two methods now.
> We could do something like this:
> {code:java}
> private void initFileSystemFactory() {
> setFileSystemFactory(NativeFileSystemFactory.INSTANCE);
> }
> {code}
> But given that we are not using sftp, it could be even safer to just say:
> {code:java}
> private void noFileSystemFactory() {
> setFileSystemFactory(NoFileSystemFactory.INSTANCE);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (SSHD-1037) private openssh key parsing error
[
https://issues.apache.org/jira/browse/SSHD-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160713#comment-17160713
]
Lyor Goldstein commented on SSHD-1037:
--
{quote}Not able to identify root cause.
{quote}
It would seem the code you use to generate the key pair does not align it on a
multiple of the cipher (as previously indicated).
Please note that the fact the code you use to encrypt the key also decrypts it
does not mean the encryption is correct - it only means that the code is
consistent. I would be curious to see the following:
* Generate an OpenSSH key using e.g. {{ssh-keygen -o -t rsa -b 2048}} (can
choose other types for {{-t}} and other key sizes for {{-b}}) and then try to
decode it with our {{OpenSSHKeyPairResourceParser}} and also with the code you
claim works.
* Generate an OpenSSH key using your code and try to decode it using
{{ssh-keygen -y -f ...}} - if it fails (as it did for us) then I believe it is
a good indication that the result does not conform to the expected format - see
[this
link|http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/PROTOCOL.key?rev=1.1&content-type=text/x-cvsweb-markup]
> private openssh key parsing error
> -
>
> Key: SSHD-1037
> URL: https://issues.apache.org/jira/browse/SSHD-1037
> Project: MINA SSHD
> Issue Type: Question
>Reporter: Sandeep
>Priority: Major
> Attachments: KeyGenerationTest.java, console_log, junit_test_output,
> parsing_java_method
>
>
> Hi Team,
> I am not able to parse openssh key with the help of
> *OpenSSHKeyPairResourceParser* class
> Java code and log is attached.
> Passwork of key is : RoldWtzuRB089Dztx7MmsIxe799c2MIL
> Key is as follows,
> -BEGIN OPENSSH PRIVATE KEY-
> b3BlbnNzaC1rZXktdjEACmFlczEyOC1jYmMGYmNyeXB0GBAM
> JEJgXHPG6QrP1OWVzu6TEAEAAACXB3NzaC1yc2EDAQAB
> gQCqpdnaIOxhfmKQbiM3TtJPOofzCeQ0tC5jUyB/jEo2BLg8FZ0I/LNm0gSVD9DP
> o/EJbFsHHGtX8iSB2t2mdszaJd1PX3e/5qEFm7P0tbqhp4sI+dgV+X3wvjADYBND
> 6PS44vTgd9MY8zyB24wDoj5gRM/w/FW67EtgwTdYzmExtwAAAfFLV4x18tC9tXX1
> 5nBqQuHpZezdrY3z2MS5cq8eb8o/+CdHvlBtjvcob8Stm8+3QXx7HMRDhoZhn+Pa
> EufIsRZ5Ta4XseJ2ukDeEzVZSa7hRrR56B3UUGhvKPEyMcQu33xH0/wsqoO8cmBs
> GxqDKSRBw26lj7OFZT7cIgsv/zAr67Q+ycX7OpXa8TlKZw3qrO1HZXNkZtY4ooO/
> nDuDfmOKVlbZ4HWcPXpcbojI6r0LLOhte4czLv3sQskEkJkzlnG62oLA2zrpvGlw
> 7u/uOtvuWNTwwFxJfQwwpiZRuACJIpyEJsTA+156SG0X+AIpAy8b6l3cOTLo00EP
> JbW20l8K+DdMvT0RWr895KaI7vcs30JeFmysm8eMKTUdVDgu2Sy8Qd/1GMhi1AZy
> peUWzvQNjauSwDoyJka5go0gUOa1biCl9o67Oy07estHnfeoK8NGcjmv14U1BP2a
> 0KzazesOxvbalr6hlgq1DAVTvpSRw1vAAx4xE1RrVA3qNMcFf3W8tOf7WQCO9J5m
> +o31L5Wiuh9uvPGN7tLbR1eOuwYMH7ICz0Ydvfkg5UFaFIYz8pUInLFFFle/YUMw
> KEtFrJKYItON25XcpqciorilWXJw0BdK7w/aeHoOVxOQer2PSj36J/jn0oC64guP
> g6SHko7U4Q==
> -END OPENSSH PRIVATE KEY-
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
