[jira] [Closed] (SSHD-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susmit Sarkar closed SSHD-1176. --- > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susmit Sarkar resolved SSHD-1176. - Resolution: Fixed > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354600#comment-17354600 ] Susmit Sarkar commented on SSHD-1176: - Thank you have a nice day, i have few questions with respect to SOCKS5 will ask in separate thread closing this one > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354497#comment-17354497 ] Guillaume Nodet commented on SSHD-1176: --- The changelog has been updated. SSH jumps ([http://issues.apache.org/jira/browse/SSHD-1047)] are not related to SOCKS proxies and those were implemented in 2.6.0. > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354491#comment-17354491 ] Susmit Sarkar commented on SSHD-1176: - [~gnodet] [~lgoldstein] What about the ssh jumps: [https://github.com/apache/mina-sshd/blob/sshd-2.7.0/docs/internals.md] Isn't it a new feature wrt SOCKS5 Proxy > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354438#comment-17354438 ] Susmit Sarkar edited comment on SSHD-1176 at 5/31/21, 2:41 PM: --- [~lgoldstein]: Your guidance will be appreciated was (Author: susmit07): [~lgoldstein]: Your guidance will be appretiated > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354484#comment-17354484 ] Guillaume Nodet commented on SSHD-1176: --- The only issue I know about SOCKS5 is https://issues.apache.org/jira/browse/SSHD-1008 which is not resolved, so it's definitely not part of any release atm. > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354483#comment-17354483 ] Susmit Sarkar commented on SSHD-1176: - changes.md is alos not availble for 2.6.0 to 2.7.0 in git > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354481#comment-17354481 ] Susmit Sarkar commented on SSHD-1176: - Thank you, Guillaume ... any help with the above question of mine? wrt SOCKS5 mainly > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1735#comment-1735 ] Guillaume Nodet commented on SSHD-1176: --- 2.7.0 is now available in central. > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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] [Created] (SSHD-1176) Upgrade from 2.5.1 to 2.7.0
Susmit Sarkar created SSHD-1176: --- Summary: Upgrade from 2.5.1 to 2.7.0 Key: SSHD-1176 URL: https://issues.apache.org/jira/browse/SSHD-1176 Project: MINA SSHD Issue Type: Question Reporter: Susmit Sarkar Hello Team, We are currently in 2.5.1 and it's pretty stable, but we are planning to upgrade to 2.7.0. Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? Do we expect any new features with respect to SOCKS5 proxy support that will help us. I checked the changes.md but couldn't find any, although there were few features related to forwarding port and filter. I didn't found 2.7.0 listed in maven repository, when can we expect the same Thank you, Best Regards, Susmit -- 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-1176) Upgrade from 2.5.1 to 2.7.0
[ https://issues.apache.org/jira/browse/SSHD-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354438#comment-17354438 ] Susmit Sarkar commented on SSHD-1176: - [~lgoldstein]: Your guidance will be appretiated > Upgrade from 2.5.1 to 2.7.0 > --- > > Key: SSHD-1176 > URL: https://issues.apache.org/jira/browse/SSHD-1176 > Project: MINA SSHD > Issue Type: Question >Reporter: Susmit Sarkar >Priority: Critical > > Hello Team, > We are currently in 2.5.1 and it's pretty stable, but we are planning to > upgrade to 2.7.0. > Is it justified to update to 2.7.0 or 2.6.0 w.r.t stability? > Do we expect any new features with respect to SOCKS5 proxy support that will > help us. I checked the changes.md but couldn't find any, although there were > few features related to forwarding port and filter. > I didn't found 2.7.0 listed in maven repository, when can we expect the same > Thank you, > Best Regards, > Susmit > -- 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-1173) SFTP worker threads got stuck while processing PUT methods against one specific SFTP server
[
https://issues.apache.org/jira/browse/SSHD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354432#comment-17354432
]
Guillaume Nodet commented on SSHD-1173:
---
Yes, using a configurable timeout would be better indeed.
The {{send}} method is calling {{verify}} to make sure that the message has
actually been written. If the thread is never released, it should indicate
that the packet has not been written yet. The most probable cause is that the
server does not handle the SSH window correctly and never sends
{{SSH_MSG_CHANNEL_WINDOW_ADJUST}} to tell the client it can send more data. If
you know the target server, maybe you can perform a test transfer (bit enough)
and see if the server ever sends those messages ?
> SFTP worker threads got stuck while processing PUT methods against one
> specific SFTP server
> ---
>
> Key: SSHD-1173
> URL: https://issues.apache.org/jira/browse/SSHD-1173
> Project: MINA SSHD
> Issue Type: Question
>Affects Versions: 2.6.0
>Reporter: Pavel Pohner
>Priority: Critical
> Labels: SFTP, mina, sshd
>
> Hey guys,
> Recently I've encountered one remote SFTP server, that causes SFTP worker
> threads to enter TIMED_WAITING state, from which they do not recover. Please,
> take a look into this thread dump:
> {code:java}
> SFTP-worker-3 #2155 prio=5 os_prio=0 cpu=61692.09ms elapsed=1136151.86s
> tid=0x7fe41c005800 nid=0x18808 in Object.wait()
> [0x7fe145b1d000]SFTP-worker-3" #2155 prio=5 os_prio=0 cpu=61692.09ms
> elapsed=1136151.86s tid=0x7fe41c005800 nid=0x18808 in Object.wait()
> [0x7fe145b1d000] java.lang.Thread.State: TIMED_WAITING (on object
> monitor) at java.lang.Object.wait(java.base@11.0.10/Native Method) - waiting
> on at
> org.apache.sshd.common.future.DefaultSshFuture.await0(DefaultSshFuture.java:69)
> - waiting to re-lock in wait() <0x0006e3bbc420> (a
> org.apache.sshd.common.channel.IoWriteFutureImpl) at
> org.apache.sshd.common.future.AbstractSshFuture.verifyResult(AbstractSshFuture.java:109)
> at
> org.apache.sshd.common.io.AbstractIoWriteFuture.verify(AbstractIoWriteFuture.java:39)
> at
> org.apache.sshd.common.io.AbstractIoWriteFuture.verify(AbstractIoWriteFuture.java:30)
> at
> org.apache.sshd.common.future.VerifiableFuture.verify(VerifiableFuture.java:43)
> at
> org.apache.sshd.sftp.client.impl.DefaultSftpClient.send(DefaultSftpClient.java:292)
> at
> org.apache.sshd.sftp.client.impl.SftpOutputStreamAsync.flush(SftpOutputStreamAsync.java:210)
> at
> org.apache.sshd.sftp.client.impl.SftpOutputStreamAsync.write(SftpOutputStreamAsync.java:141)
> at java.io.InputStream.transferTo(java.base@11.0.10/InputStream.java:705) at
> com.mina.command.Put.replyInto(Put.java:55) at
> com.sftpserver.MinaSftpHandler.channelReadInternal(MinaSftpHandler.java:251)
> at
> com.sftpserver.MinaSftpHandler.lambda$channelRead$0(MinaSftpHandler.java:125)
> at com.sftpserver.MinaSftpHandler$$Lambda$392/0x000800764040.run(Unknown
> Source) at
> java.util.concurrent.Executors$RunnableAdapter.call(java.base@11.0.10/Executors.java:515)
> at
> java.util.concurrent.FutureTask.run(java.base@11.0.10/FutureTask.java:264) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@11.0.10/ThreadPoolExecutor.java:1128)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@11.0.10/ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(java.base@11.0.10/Thread.java:834)
> {code}
> Seems like the thread is waiting for lock in
> org.apache.sshd.common.future.DefaultSshFuture.await0(DefaultSshFuture.java),
> I'm currently not sure what thread holds the lock and why it's not ever
> released.
> Also, I'm not able to reproduce this, but it constantly happens to all the
> PUT methods targeting one specific remote server (which I don't own), so I
> suppose there would be something odd with the remote server, but it doesn't
> mean, that we shouldn't be able to deal with that.
> Have you ever seen such behavior? Could it be Mina sshd's bug? (seems like
> verify() in
> org.apache.sshd.sftp.client.impl.DefaultSftpClient.send(DefaultSftpClient.java:292)
> is called without any timeout, which then defaults to LONG.MAX here: at
> org.apache.sshd.common.future.VerifiableFuture.verify(VerifiableFuture.java:43),
> shouldn't we have configurable timeout here? or what's the point of default
> timeout? what are we really waiting for in at
> org.apache.sshd.common.future.DefaultSshFuture.await0(DefaultSshFuture.java:69)?)
--
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...@min
[jira] [Comment Edited] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354427#comment-17354427
]
Thomas Wolf edited comment on DIRMINA-1143 at 5/31/21, 12:09 PM:
-
The server identifies as SSH2.0-PaloAltoNetworks_0.2. So (probably) not SSH v1
(unless it's lying). A firewall, and then a 0.x version number? Hmm... for me
"0.x" indicates "not production-ready". No idea what kind of SSH server that
really is, or whether it can be trusted.
It appears to be a (decrypting) SSH proxy.
Other people apparently also [ran into
trouble|https://slacker.ro/2018/11/28/troubleshooting-obscure-openssh-failures/]
with that.
was (Author: wolft):
The server identifies as SSH2.0-PaloAltoNetworks_0.2. So (probably) not SSH v1
(unless it's lying). A firewall, and then a 0.x version number? Hmm... for me
"0.x" indicates "not production-ready". No idea what kind of SSH server that
really is, or whether it can be trusted.
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
> Attachments: good.pcap, packetlog2.cat
>
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354427#comment-17354427
]
Thomas Wolf commented on DIRMINA-1143:
--
The server identifies as SSH2.0-PaloAltoNetworks_0.2. So (probably) not SSH v1
(unless it's lying). A firewall, and then a 0.x version number? Hmm... for me
"0.x" indicates "not production-ready". No idea what kind of SSH server that
really is, or whether it can be trusted.
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
> Attachments: good.pcap, packetlog2.cat
>
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354418#comment-17354418
]
Frits Jalvingh commented on DIRMINA-1143:
-
Thanks a lot ;)
I will try to find out what server is being used; it's probably something
Windows based. I also have a dump of the start of a "working" connection; there
we at least see the ident of the remote server. It looks indeed like something
is now well there
See [^good.pcap].
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
> Attachments: good.pcap, packetlog2.cat
>
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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] [Updated] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frits Jalvingh updated DIRMINA-1143:
Attachment: good.pcap
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
> Attachments: good.pcap, packetlog2.cat
>
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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] [Updated] (SSHD-1173) SFTP worker threads got stuck while processing PUT methods against one specific SFTP server
[
https://issues.apache.org/jira/browse/SSHD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pohner updated SSHD-1173:
---
Description:
Hey guys,
Recently I've encountered one remote SFTP server, that causes SFTP worker
threads to enter TIMED_WAITING state, from which they do not recover. Please,
take a look into this thread dump:
{code:java}
SFTP-worker-3 #2155 prio=5 os_prio=0 cpu=61692.09ms elapsed=1136151.86s
tid=0x7fe41c005800 nid=0x18808 in Object.wait()
[0x7fe145b1d000]SFTP-worker-3" #2155 prio=5 os_prio=0 cpu=61692.09ms
elapsed=1136151.86s tid=0x7fe41c005800 nid=0x18808 in Object.wait()
[0x7fe145b1d000] java.lang.Thread.State: TIMED_WAITING (on object
monitor) at java.lang.Object.wait(java.base@11.0.10/Native Method) - waiting on
at
org.apache.sshd.common.future.DefaultSshFuture.await0(DefaultSshFuture.java:69)
- waiting to re-lock in wait() <0x0006e3bbc420> (a
org.apache.sshd.common.channel.IoWriteFutureImpl) at
org.apache.sshd.common.future.AbstractSshFuture.verifyResult(AbstractSshFuture.java:109)
at
org.apache.sshd.common.io.AbstractIoWriteFuture.verify(AbstractIoWriteFuture.java:39)
at
org.apache.sshd.common.io.AbstractIoWriteFuture.verify(AbstractIoWriteFuture.java:30)
at
org.apache.sshd.common.future.VerifiableFuture.verify(VerifiableFuture.java:43)
at
org.apache.sshd.sftp.client.impl.DefaultSftpClient.send(DefaultSftpClient.java:292)
at
org.apache.sshd.sftp.client.impl.SftpOutputStreamAsync.flush(SftpOutputStreamAsync.java:210)
at
org.apache.sshd.sftp.client.impl.SftpOutputStreamAsync.write(SftpOutputStreamAsync.java:141)
at java.io.InputStream.transferTo(java.base@11.0.10/InputStream.java:705) at
com.mina.command.Put.replyInto(Put.java:55) at
com.sftpserver.MinaSftpHandler.channelReadInternal(MinaSftpHandler.java:251) at
com.sftpserver.MinaSftpHandler.lambda$channelRead$0(MinaSftpHandler.java:125)
at com.sftpserver.MinaSftpHandler$$Lambda$392/0x000800764040.run(Unknown
Source) at
java.util.concurrent.Executors$RunnableAdapter.call(java.base@11.0.10/Executors.java:515)
at java.util.concurrent.FutureTask.run(java.base@11.0.10/FutureTask.java:264)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@11.0.10/ThreadPoolExecutor.java:1128)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@11.0.10/ThreadPoolExecutor.java:628)
at java.lang.Thread.run(java.base@11.0.10/Thread.java:834)
{code}
Seems like the thread is waiting for lock in
org.apache.sshd.common.future.DefaultSshFuture.await0(DefaultSshFuture.java),
I'm currently not sure what thread holds the lock and why it's not ever
released.
Also, I'm not able to reproduce this, but it constantly happens to all the PUT
methods targeting one specific remote server (which I don't own), so I suppose
there would be something odd with the remote server, but it doesn't mean, that
we shouldn't be able to deal with that.
Have you ever seen such behavior? Could it be Mina sshd's bug? (seems like
verify() in
org.apache.sshd.sftp.client.impl.DefaultSftpClient.send(DefaultSftpClient.java:292)
is called without any timeout, which then defaults to LONG.MAX here: at
org.apache.sshd.common.future.VerifiableFuture.verify(VerifiableFuture.java:43),
shouldn't we have configurable timeout here? or what's the point of default
timeout? what are we really waiting for in at
org.apache.sshd.common.future.DefaultSshFuture.await0(DefaultSshFuture.java:69)?)
was:
Hey guys,
Recently I've encountered one remote SFTP server, that causes SFTP worker
threads to enter TIMED_WAITING state, from which they do not recover. Please,
take a look into this thread dump:
{code:java}
SFTP-worker-3 #2155 prio=5 os_prio=0 cpu=61692.09ms elapsed=1136151.86s
tid=0x7fe41c005800 nid=0x18808 in Object.wait()
[0x7fe145b1d000]SFTP-worker-3" #2155 prio=5 os_prio=0 cpu=61692.09ms
elapsed=1136151.86s tid=0x7fe41c005800 nid=0x18808 in Object.wait()
[0x7fe145b1d000] java.lang.Thread.State: TIMED_WAITING (on object
monitor) at java.lang.Object.wait(java.base@11.0.10/Native Method) - waiting on
at
org.apache.sshd.common.future.DefaultSshFuture.await0(DefaultSshFuture.java:69)
- waiting to re-lock in wait() <0x0006e3bbc420> (a
org.apache.sshd.common.channel.IoWriteFutureImpl) at
org.apache.sshd.common.future.AbstractSshFuture.verifyResult(AbstractSshFuture.java:109)
at
org.apache.sshd.common.io.AbstractIoWriteFuture.verify(AbstractIoWriteFuture.java:39)
at
org.apache.sshd.common.io.AbstractIoWriteFuture.verify(AbstractIoWriteFuture.java:30)
at
org.apache.sshd.common.future.VerifiableFuture.verify(VerifiableFuture.java:43)
at
org.apache.sshd.sftp.client.impl.DefaultSftpClient.send(DefaultSftpClient.java:292)
at
org.apache.sshd.sftp.client.impl.SftpOutputStreamAsync.flush(SftpOutputStreamAsync.java:210)
at
org.apache.sshd.sftp.client.impl.SftpOutputStreamAsync.write(SftpOutputStr
[jira] [Commented] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354380#comment-17354380
]
Thomas Wolf commented on DIRMINA-1143:
--
In this packet trace, I only see in packet 4 the client announcing its SSH
identification. In packet 6 it sends its KEX negotiation proposal. The server
never sends back its own SSH identification, instead it replies in packet 8
directly with its own KEX negotiation message.
What server is this? This looks broken in the server. Or is this an SSH v1
server? In that case, see SSHD-930 and SSHD-947. See the constructor of
{{AbstractClientSession}}. There are two properties
{{SEND_IMMEDIATE_IDENTIFICATION}} and {{SEND_IMMEDIATE_KEXINIT}} that you can
use to influence what is sent when (immediately, or only once the server's
corresponding message has been received).
With this wire trace, perhaps setting one of them (or both) to {{false}} helps.
Compare also [this
comment|https://issues.apache.org/jira/browse/SSHD-930?focusedCommentId=16883907&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16883907].
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
> Attachments: packetlog2.cat
>
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354369#comment-17354369
]
Frits Jalvingh commented on DIRMINA-1143:
-
I forgot: the corresponding dump from within the mina code is this:
{{>> BAD IDENT:}}
{{: 00 00 01 d4 0b 14 3c 78 19 50 32 fb ca 7e bc 6d .. sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
> Attachments: packetlog2.cat
>
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354367#comment-17354367
]
Frits Jalvingh commented on DIRMINA-1143:
-
I checked the source code and it appears that a class line Nio2Session only
logs things like #bytes send/received, no data.
I could do a packet trace of a failed connection as a pcap file which I will
attach [^packetlog2.cat]
Enabling DEBUG level as trace seems to influence the occurrence of the issue; I
tried 20 times and could not reproduce with debug on. Switching it off made it
fail again immediately. Not sure it is a valid data point but just FYI.
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
> Attachments: packetlog2.cat
>
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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] [Updated] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frits Jalvingh updated DIRMINA-1143:
Attachment: packetlog2.cat
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
> Attachments: packetlog2.cat
>
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354345#comment-17354345
]
Thomas Wolf commented on DIRMINA-1143:
--
Log level DEBUG should show also handling of incoming requests. Don't know
off-hand if TRACE might show raw buffer contents. Otherwise, a network capture
of the first few exchanges might help; these requests are before the key
exchange and thus still un-encrypted.
BTW: perhaps related: OpenSSH7.4p1 [had a
bug|https://stackoverflow.com/questions/65777501/connecting-with-ssh-net-to-openssh-7-4p1-fails-with-the-server-response-contain]
that could lead to similar error messages. But from looking at the MINA sshd
code, I don't think it would be affected by that. Probably it's something
different here.
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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
Re: [ANNOUNCE] Apache SSHD 2.7.0 released
Does this support SSH version 1 and version 2 both? Regards, Vishnupriya On Mon, 31 May 2021 at 2:52 PM, Guillaume Nodet wrote: > The Apache Mina team is pleased to announce the release of SSHD 2.7.0 > version. > > Apache SSHD is a 100% pure java library to support the SSH protocols on > both the client and server side. This library can leverage NIO2, Apache > MINA and > also Netty - scalable and high performance asynchronous IO libraries. SSHD > does not really aim at being a replacement for the SSH client or SSH server > from Unix operating systems, but rather provides support for Java based > applications requiring SSH support. > > The major issues addressed in this release are: > > ** Bug > * [SSHD-] - wrong command line interpretation > * [SSHD-1123] - ChannelAsyncOutputStream breaks downloads of sftp > client by not chunking when the remote window is smaller than the packet > size > * [SSHD-1125] - Provide a boundary on BufferedIoOutputStream writing to > avoid memory overflow > * [SSHD-1136] - Diffie Hellmann group exchange falls back to insecure > DHG1 if agreement on modulo size is not possible > * [SSHD-1137] - IOException for unsupported NOFOLLOW_LINKS on AIX when > accessing with OpenSSH SFTP client > * [SSHD-1146] - Missing Import-Package header in sshd-osgi-2.6.0 > * [SSHD-1154] - userauth_pubkey: unsupported public key algorithm: > rsa-sha2-512 > * [SSHD-1158] - Channel closed by peer: extra SSH_MSG_CHANNEL_EOF sent > > > ** New Feature > * [SSHD-1097] - Provide an 'endlessh' tarpit capability > > > ** Improvement > * [SSHD-525] - Add support for "posix-ren...@openssh.com" SFTP > extension > * [SSHD-1083] - The nio2 connector/acceptor implementation should not > be tied to the FactoryManager > * [SSHD-1105] - Use all possible signatures for a public key type in > public key authentication > * [SSHD-1109] - Replace log4j with logback as the slf4j logger > implementation for tests > * [SSHD-1114] - Add client-side detailed authentication progress > callbacks > * [SSHD-1116] - Provide session context to the various XXXProvider(s) > * [SSHD-1132] - Add support for SFTP "filename-charset" extension > * [SSHD-1133] - Provide non-UTF8 charset encoding capability to SCP > implementation > * [SSHD-1141] - Implement server-sig-algs > * [SSHD-1145] - EdDSASecurityProviderRegistrar#isSupported() should > check more classloaders > > > ** Wish > * [SSHD-1147] - SftpClient is not able to download file from > proprietory SFTP servers (IBM) with a one time download policy > > The distributions are available from the Apache Software Foundation > distribution mirrors http://mina.apache.org/sshd-project/downloads.html > and > from maven central. > > On behalf of the Apache Mina team, > Guillaume Nodet > -- Regards, Vishnupriya R&D Engineer Hewlett Packard Enterprise
[ANNOUNCE] Apache SSHD 2.7.0 released
The Apache Mina team is pleased to announce the release of SSHD 2.7.0 version. Apache SSHD is a 100% pure java library to support the SSH protocols on both the client and server side. This library can leverage NIO2, Apache MINA and also Netty - scalable and high performance asynchronous IO libraries. SSHD does not really aim at being a replacement for the SSH client or SSH server from Unix operating systems, but rather provides support for Java based applications requiring SSH support. The major issues addressed in this release are: ** Bug * [SSHD-] - wrong command line interpretation * [SSHD-1123] - ChannelAsyncOutputStream breaks downloads of sftp client by not chunking when the remote window is smaller than the packet size * [SSHD-1125] - Provide a boundary on BufferedIoOutputStream writing to avoid memory overflow * [SSHD-1136] - Diffie Hellmann group exchange falls back to insecure DHG1 if agreement on modulo size is not possible * [SSHD-1137] - IOException for unsupported NOFOLLOW_LINKS on AIX when accessing with OpenSSH SFTP client * [SSHD-1146] - Missing Import-Package header in sshd-osgi-2.6.0 * [SSHD-1154] - userauth_pubkey: unsupported public key algorithm: rsa-sha2-512 * [SSHD-1158] - Channel closed by peer: extra SSH_MSG_CHANNEL_EOF sent ** New Feature * [SSHD-1097] - Provide an 'endlessh' tarpit capability ** Improvement * [SSHD-525] - Add support for "posix-ren...@openssh.com" SFTP extension * [SSHD-1083] - The nio2 connector/acceptor implementation should not be tied to the FactoryManager * [SSHD-1105] - Use all possible signatures for a public key type in public key authentication * [SSHD-1109] - Replace log4j with logback as the slf4j logger implementation for tests * [SSHD-1114] - Add client-side detailed authentication progress callbacks * [SSHD-1116] - Provide session context to the various XXXProvider(s) * [SSHD-1132] - Add support for SFTP "filename-charset" extension * [SSHD-1133] - Provide non-UTF8 charset encoding capability to SCP implementation * [SSHD-1141] - Implement server-sig-algs * [SSHD-1145] - EdDSASecurityProviderRegistrar#isSupported() should check more classloaders ** Wish * [SSHD-1147] - SftpClient is not able to download file from proprietory SFTP servers (IBM) with a one time download policy The distributions are available from the Apache Software Foundation distribution mirrors http://mina.apache.org/sshd-project/downloads.html and from maven central. On behalf of the Apache Mina team, Guillaume Nodet
[jira] [Commented] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354332#comment-17354332
]
Frits Jalvingh commented on DIRMINA-1143:
-
Thanks a lot for your help, and I'm sorry for posting at the wrong project 8-/.
No proxies. I have enabled logging on mina but that does not show any input; it
just logs what it sends. Is there a way to enable packet logging or at least to
see what input we get?
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354327#comment-17354327
]
Thomas Wolf commented on DIRMINA-1143:
--
Any proxies involved?
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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
[GitHub] [mina-site] gnodet merged pull request #4: Added Jenkinsfile to put deployment configuration in version control
gnodet merged pull request #4: URL: https://github.com/apache/mina-site/pull/4 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
[
https://issues.apache.org/jira/browse/DIRMINA-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354300#comment-17354300
]
Thomas Wolf commented on DIRMINA-1143:
--
Interesting. We had a similar bug report in [Eclipse bug
545939|https://bugs.eclipse.org/bugs/show_bug.cgi?id=545939] two years ago, but
we never identified the root cause. We just made that
{{doReadIdentification()}} more lenient and since then that problem seems to
have disappeared. (See [JGit commit
b8a514f|https://git.eclipse.org/r/c/jgit/jgit/+/146047/].) At least we never
had any report about this problem anymore.
JGit didn't submit this upstream at MINA sshd since we never figured out what
the real cause of the problem was, so it's unclear whether the JGit "fix" for
this is really the right fix.
If you can reproduce this easily: what kind of server is this? Does it send any
preamble lines before its SSH identification string? Do you have any traces for
cases when the problem occurs vs. cases when the problem does _not_ occur? Why
is that server sending NULs before its SSH identification?
Off-topic: there's a separate Jira project "MINA SSHD". Unfortunately I cannot
move this issue to the correct project. Normally Jira has a "Move Issue"
command, but here I don't see it.
> sftp authentication fails with "Incorrect identification (null characters not
> allowed) - at line 1 character #1 after ''
>
>
> Key: DIRMINA-1143
> URL: https://issues.apache.org/jira/browse/DIRMINA-1143
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu Linux 18.04, Java 11.
>Reporter: Frits Jalvingh
>Priority: Major
>
> I am having this intermittent error when authenticating to an sftp server. It
> is always the same server and always the same program; connecting fails about
> once every 5 times with this error coming from SessionHelper.java, method
> doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
> maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
> runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
> debugging and for that I changed SessionHelper so that it dumps the
> information that it is trying to read at that time from its buffer. Because
> that always died with that NUL character as the first character read I made
> the code continue to read a bit so that there might be some context.. What is
> present in that buffer at this time is this:
>
> {{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
> {{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
> {{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
> {{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
> {{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
> {{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
> {{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
> {{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
> {{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
> {{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
> {{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
> {{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
> {{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
> {{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
> {{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
> {{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
>
> The error occurs when reading that 00 at offset ; the rest of the data is
> there by looking into the rest of that buffer..
> I can quite easily reproduce this, so if more data is needed I should be able
> to provide it..
>
--
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
[RESULT] [VOTE] Release Apache Mina SSHD 2.7.0 (2nd try)
Closing this vote with 4 +1s I'll publish the release asap. Cheers, Guillaume Nodet Le mar. 11 mai 2021 à 16:21, Guillaume Nodet a écrit : > I've staged another release candidate built on JDK 1.8: > * maven repo: > https://repository.apache.org/content/repositories/orgapachemina-1057 > * Distributions: https://dist.apache.org/repos/dist/dev/mina/sshd/2.7.0/ > * Git tag: https://github.com/apache/mina-sshd/releases/tag/sshd-2.7.0 > > This release contains a number of changes: > https://github.com/apache/mina-sshd/blob/master/docs/changes/2.7.0.md > > Please review and vote ! > > -- > > Guillaume Nodet > >
[jira] [Created] (DIRMINA-1143) sftp authentication fails with "Incorrect identification (null characters not allowed) - at line 1 character #1 after ''
Frits Jalvingh created DIRMINA-1143:
---
Summary: sftp authentication fails with "Incorrect identification
(null characters not allowed) - at line 1 character #1 after ''
Key: DIRMINA-1143
URL: https://issues.apache.org/jira/browse/DIRMINA-1143
Project: MINA
Issue Type: Bug
Components: Core
Environment: Ubuntu Linux 18.04, Java 11.
Reporter: Frits Jalvingh
I am having this intermittent error when authenticating to an sftp server. It
is always the same server and always the same program; connecting fails about
once every 5 times with this error coming from SessionHelper.java, method
doReadIdentification. I had this error before and upgraded to Mina 2.6.0 from
maven (org.apache.sshd, sshd-core et al) but that changed nothing. The code
runs on Ubuntu Linux 18.04 (Azure, sigh) with Java 11.I tried to do some
debugging and for that I changed SessionHelper so that it dumps the information
that it is trying to read at that time from its buffer. Because that always
died with that NUL character as the first character read I made the code
continue to read a bit so that there might be some context.. What is present in
that buffer at this time is this:
{{: 00 00 01 d4 0b 14 8a e8 5f 65 22 7b 97 4f 2d 61 _e"{.O-a}}
{{0010: 12 75 19 81 6e 1a 00 00 00 47 64 69 66 66 69 65 .u..nGdiffie}}
{{0020: 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 -hellman-group-e}}
{{0030: 78 63 68 61 6e 67 65 2d 73 68 61 32 35 36 2c 64 xchange-sha256,d}}
{{0040: 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 iffie-hellman-gr}}
{{0050: 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 oup-exchange-sha}}
{{0060: 31 00 00 00 0f 73 73 68 2d 72 73 61 2c 73 73 68 1ssh-rsa,ssh}}
{{0070: 2d 64 73 73 00 00 00 41 61 65 73 31 32 38 2d 63 -dss...Aaes128-c}}
{{0080: 74 72 2c 61 65 73 31 39 32 2d 63 74 72 2c 61 65 tr,aes192-ctr,ae}}
{{0090: 73 32 35 36 2d 63 74 72 2c 61 65 73 31 32 38 2d s256-ctr,aes128-}}
{{00a0: 63 62 63 2c 61 65 73 31 39 32 2d 63 62 63 2c 61 cbc,aes192-cbc,a}}
{{00b0: 65 73 32 35 36 2d 63 62 63 00 00 00 41 61 65 73 es256-cbc...Aaes}}
{{00c0: 31 32 38 2d 63 74 72 2c 61 65 73 31 39 32 2d 63 128-ctr,aes192-c}}
{{00d0: 74 72 2c 61 65 73 32 35 36 2d 63 74 72 2c 61 65 tr,aes256-ctr,ae}}
{{00e0: 73 31 32 38 2d 63 62 63 2c 61 65 73 31 39 32 2d s128-cbc,aes192-}}
{{00f0: 63 62 63 2c 61 65 73 32 35 36 2d 63 62 63 00 cbc,aes256-cbc.}}
The error occurs when reading that 00 at offset ; the rest of the data is
there by looking into the rest of that buffer..
I can quite easily reproduce this, so if more data is needed I should be able
to provide it..
--
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
