[jira] [Commented] (SSHD-1215) WinsCP transfer failure to Apache SSHD Server
[ https://issues.apache.org/jira/browse/SSHD-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443610#comment-17443610 ] Roberto Deandrea commented on SSHD-1215: Hi Thomas, I know that this is not the right place to ask this kind of question but I did not find any right place for that. Do you know when is scheduled the release of next Apache SSHD version (a.k.a 2.7.1) ? Kind Regards Roberto > WinsCP transfer failure to Apache SSHD Server > - > > Key: SSHD-1215 > URL: https://issues.apache.org/jira/browse/SSHD-1215 > Project: MINA SSHD > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Roberto Deandrea >Assignee: Thomas Wolf >Priority: Blocker > Fix For: 2.7.1 > > Attachments: logs.zip > > Time Spent: 10m > Remaining Estimate: 0h > > Hi > I have a failure transferring small files from a WinSCP SFTP client version > 5.19.2 to a front-end Apache SSHD Server 2.6.0. > The front-end Apache SSHD server is configured with a Filesystem built upon > SFTPFileSystemProvider to proxy files to an Apache SSHD back-end server. > WinSCP SFTP transfer files successfully directly to back-end Apache SSHD > Server. > I traced the SFTP file transfer on the front-end server and back-end server > and it seems that something get wrong in the remote FileSystem set on the > front-end server. > From traces it seems that the first chunk of file is received correctly by > the back-end server, but something is wrong on the second chuck of file > transmitted. > - > First SSH_FXP_WRITE chunk received from front-end server : > [16/09/21 09:18:26:364 CEST] 0175 id= > org.apache.sshd.sftp.server.AbstractSftpSubsystemHelper 1 process > process(ServerSessionImpl[allfuser1@/172.18.202.33:55400])[length=32757, > type=SSH_FXP_WRITE, id=19718] processing > [16/09/21 09:18:26:364 CEST] 0175 id= > org.apache.sshd.sftp.server.SftpSubsystem 3 doWrite > doWrite(ServerSessionImpl[allfuser1@/172.18.202.33:55400])[id=19718] > *SSH_FXP_WRITE > (handle=de6fcf635cb34b0e6d3d56643b7539a3[[/upload/rsa.key|https://issues.apache.org/upload/rsa.key]], > offset=0, data=byte[32704])* > First SSH_FXP_WRITE chunk sent by front-end SFTP client to back.end-server : > [16/09/21 09:18:26:913 CEST] 0175 id= > org.apache.sshd.sftp.client.impl.DefaultSftpClient 3 send > send(SftpChannelSubsystem[id=0, > recipient=0]-ClientSessionImpl[DMZ/172.18.202.33/allfuser1@/10.6.6.22:6471][sftp]) > cmd=SSH_FXP_WRITE, len=32752, id=139 > [16/09/21 09:18:27:010 CEST] 0175 id= > org.apache.sshd.sftp.client.impl.AbstractSftpClient 3 checkResponseStatus > checkResponseStatus(SftpChannelSubsystem[id=0, > recipient=0]-ClientSessionImpl[DMZ/172.18.202.33/allfuser1@/10.6.6.22:6471][sftp])[id=139] > cmd=SSH_FXP_WRITE status=SSH_FX_OK lang= msg= > > First SSH_FXP_WRITE chunk received succesfully from back-end server : > [16/09/21 09:18:27:007 CEST] 5c15 id= > org.apache.sshd.sftp.server.SftpSubsystem 3 doWrite > doWrite(ServerSessionImpl[DMZ/172.18.202.33/allfuser1@/10.6.6.22:34445])[id=139] > *SSH_FXP_WRITE > (handle=c88cfd55dd514ccdd0428571191f5ea1[[/upload/rsa.key|https://issues.apache.org/upload/rsa.key]], > offset=0, data=byte[32704])* > [16/09/21 09:18:27:545 CEST] 5c15 id= > org.apache.sshd.sftp.server.AbstractSftpSubsystemHelper 1 process > process(ServerSessionImpl[DMZ/172.18.202.33/allfuser1@/10.6.6.22:34445])[length=32757, > > - > Second SSH_FXP_WRITE chunk received from front-end server: > [16/09/21 09:18:27:012 CEST] 0175 id= > org.apache.sshd.sftp.server.AbstractSftpSubsystemHelper 1 process > process(ServerSessionImpl[allfuser1@/172.18.202.33:55400])[length=32757, > type=SSH_FXP_WRITE, id=19974] processing > [16/09/21 09:18:27:013 CEST] 0175 id= > org.apache.sshd.sftp.server.SftpSubsystem 3 doWrite > doWrite(ServerSessionImpl[allfuser1@/172.18.202.33:55400])[id=19974] > *SSH_FXP_WRITE > (handle=de6fcf635cb34b0e6d3d56643b7539a3[[/upload/rsa.key|https://issues.apache.org/upload/rsa.key]], > offset=32704, data=byte[32704])* > > Second SSH_FXP_WRITE chunk sent by front-end SFTP client to back-end server: > [16/09/21 09:18:27:473 CEST] 0175 id= > org.apache.sshd.sftp.client.impl.DefaultSftpClient 3 send > send(SftpChannelSubsystem[id=0, > recipient=0]-ClientSessionImpl[DMZ/172.18.202.33/allfuser1@/10.6.6.22:6471][sftp]) > cmd=SSH_FXP_WRITE, len=32752, *id=141* > > Second SSH_FXP_WRITE chunk received from back-end server: > type=SSH_FXP_WRITE,
[jira] [Created] (SSHD-1226) Need help for SFTP LS directory with custom attributes
Sandeep created SSHD-1226: - Summary: Need help for SFTP LS directory with custom attributes Key: SSHD-1226 URL: https://issues.apache.org/jira/browse/SSHD-1226 Project: MINA SSHD Issue Type: Question Reporter: Sandeep Attachments: image-2021-11-15-12-45-02-715.png, image-2021-11-15-12-47-37-334.png Hi Team, Our requirement is to customize native *LS with directory response* to custom attributes as follows, can anyone help me to give some context on how to implement it? !image-2021-11-15-12-47-37-334.png|width=644,height=98! -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443496#comment-17443496 ] Christoph John commented on DIRMINA-1144: - [~johnnyv] Sorry, my bad. Did not see that the filter has been renamed to SSLFilter later on. > Deadlock with SSL + Proxy > - > > Key: DIRMINA-1144 > URL: https://issues.apache.org/jira/browse/DIRMINA-1144 > Project: MINA > Issue Type: Bug > Components: SSL >Affects Versions: 2.1.3, 2.1.4 >Reporter: Giuseppe Persico >Assignee: Jonathan Valliere >Priority: Critical > Fix For: 2.2.0 > > Attachments: thread-dump-clean.txt > > > You will find the thread dump attached. This seems to be a problem that > occurs using SSL in combination with proxy. I found the problem in the 2.1.4 > and 2.1.3 versions. The 2.0.20, instead, seems to work, -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443495#comment-17443495 ] Jonathan Valliere commented on DIRMINA-1144: [~chrjohn] bugfix/DIRMINA1132 was [merged into the 2.2.X branch|https://gitbox.apache.org/repos/asf?p=mina.git;a=commit;h=656426159477b4c1e6c64c80b16c7bea16bde3d6] please use 2.2.0-SNAPSHOT > Deadlock with SSL + Proxy > - > > Key: DIRMINA-1144 > URL: https://issues.apache.org/jira/browse/DIRMINA-1144 > Project: MINA > Issue Type: Bug > Components: SSL >Affects Versions: 2.1.3, 2.1.4 >Reporter: Giuseppe Persico >Assignee: Jonathan Valliere >Priority: Critical > Fix For: 2.2.0 > > Attachments: thread-dump-clean.txt > > > You will find the thread dump attached. This seems to be a problem that > occurs using SSL in combination with proxy. I found the problem in the 2.1.4 > and 2.1.3 versions. The 2.0.20, instead, seems to work, -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443494#comment-17443494 ] Christoph John commented on DIRMINA-1144: - [~johnnyv] Just realised that the 2.2.0-SNAPSHOT is probably not what I want if it is built from the main 2.2.x branch. If I am not mistaken then I really need the build from this branch https://github.com/apache/mina/tree/bugfix/DIRMINA1132 to test the SSL2Filter, correct? Thanks, Chris. > Deadlock with SSL + Proxy > - > > Key: DIRMINA-1144 > URL: https://issues.apache.org/jira/browse/DIRMINA-1144 > Project: MINA > Issue Type: Bug > Components: SSL >Affects Versions: 2.1.3, 2.1.4 >Reporter: Giuseppe Persico >Assignee: Jonathan Valliere >Priority: Critical > Fix For: 2.2.0 > > Attachments: thread-dump-clean.txt > > > You will find the thread dump attached. This seems to be a problem that > occurs using SSL in combination with proxy. I found the problem in the 2.1.4 > and 2.1.3 versions. The 2.0.20, instead, seems to work, -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443493#comment-17443493 ] Jonathan Valliere commented on DIRMINA-1144: [~sebb] I think using Jenkins is a good idea but anyway for the purpose of the issue at hand the 2.2.0-SNAPSHOT is now up on the repo. > Deadlock with SSL + Proxy > - > > Key: DIRMINA-1144 > URL: https://issues.apache.org/jira/browse/DIRMINA-1144 > Project: MINA > Issue Type: Bug > Components: SSL >Affects Versions: 2.1.3, 2.1.4 >Reporter: Giuseppe Persico >Assignee: Jonathan Valliere >Priority: Critical > Fix For: 2.2.0 > > Attachments: thread-dump-clean.txt > > > You will find the thread dump attached. This seems to be a problem that > occurs using SSL in combination with proxy. I found the problem in the 2.1.4 > and 2.1.3 versions. The 2.0.20, instead, seems to work, -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443221#comment-17443221 ] Christoph John edited comment on DIRMINA-1144 at 11/14/21, 11:47 PM: - [~sebb] [~johnnyv] for https://github.com/quickfix-j/quickfixj/pull/441 I tried to access the 2.2.0-SNAPSHOT from the Apache Repo but it cannot be found: https://repository.apache.org/content/groups/snapshots/org/apache/mina/mina-core/ Seems like 2.2.0-SNAPSHOT is missing there, but other snapshots are there. Am I missing something? Thanks, Chris. was (Author: chrjohn): [~sebb] [~johnnyv] for https://github.com/quickfix-j/quickfixj/pull/440 I tried to access the 2.2.0-SNAPSHOT from the Apache Repo but it cannot be found: https://repository.apache.org/content/groups/snapshots/org/apache/mina/mina-core/ Seems like 2.2.0-SNAPSHOT is missing there, but other snapshots are there. Am I missing something? Thanks, Chris. > Deadlock with SSL + Proxy > - > > Key: DIRMINA-1144 > URL: https://issues.apache.org/jira/browse/DIRMINA-1144 > Project: MINA > Issue Type: Bug > Components: SSL >Affects Versions: 2.1.3, 2.1.4 >Reporter: Giuseppe Persico >Assignee: Jonathan Valliere >Priority: Critical > Fix For: 2.2.0 > > Attachments: thread-dump-clean.txt > > > You will find the thread dump attached. This seems to be a problem that > occurs using SSL in combination with proxy. I found the problem in the 2.1.4 > and 2.1.3 versions. The 2.0.20, instead, seems to work, -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443325#comment-17443325 ] Sebb commented on DIRMINA-1144: --- Please don't. But ... if you do put your password in the file, make very very very sure the file is protected against snooping by anyone else. [Maven does offer password obfuscation, but it is pretty easy to reverse.] Jenkins used to offer snapshot uploads as part of the build process and may still do so. I suggest the project contact Infra as to how to best publish snapshot builds. This will avoid the need for any committers to store passwords. > Deadlock with SSL + Proxy > - > > Key: DIRMINA-1144 > URL: https://issues.apache.org/jira/browse/DIRMINA-1144 > Project: MINA > Issue Type: Bug > Components: SSL >Affects Versions: 2.1.3, 2.1.4 >Reporter: Giuseppe Persico >Assignee: Jonathan Valliere >Priority: Critical > Fix For: 2.2.0 > > Attachments: thread-dump-clean.txt > > > You will find the thread dump attached. This seems to be a problem that > occurs using SSL in combination with proxy. I found the problem in the 2.1.4 > and 2.1.3 versions. The 2.0.20, instead, seems to work, -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (DIRMINA-1144) Deadlock with SSL + Proxy
[
https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443310#comment-17443310
]
Emmanuel Lécharny commented on DIRMINA-1144:
Hi Jonathan,
you just have to update the {{~/.m2/settings.xml}} file and add your
credentials in the {{server}} part:
{code:xml}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd";>
apache.snapshots.https
--- your ASF ID ---
--- your ASF password ---
...
{code}
> Deadlock with SSL + Proxy
> -
>
> Key: DIRMINA-1144
> URL: https://issues.apache.org/jira/browse/DIRMINA-1144
> Project: MINA
> Issue Type: Bug
> Components: SSL
>Affects Versions: 2.1.3, 2.1.4
>Reporter: Giuseppe Persico
>Assignee: Jonathan Valliere
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: thread-dump-clean.txt
>
>
> You will find the thread dump attached. This seems to be a problem that
> occurs using SSL in combination with proxy. I found the problem in the 2.1.4
> and 2.1.3 versions. The 2.0.20, instead, seems to work,
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443309#comment-17443309 ] Jonathan Valliere commented on DIRMINA-1144: Okay are there instructions somewhere where I can setup my credentials so I can do that in the future? On Sun, Nov 14, 2021 at 2:33 AM Emmanuel Lécharny (Jira) CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. > Deadlock with SSL + Proxy > - > > Key: DIRMINA-1144 > URL: https://issues.apache.org/jira/browse/DIRMINA-1144 > Project: MINA > Issue Type: Bug > Components: SSL >Affects Versions: 2.1.3, 2.1.4 >Reporter: Giuseppe Persico >Assignee: Jonathan Valliere >Priority: Critical > Fix For: 2.2.0 > > Attachments: thread-dump-clean.txt > > > You will find the thread dump attached. This seems to be a problem that > occurs using SSL in combination with proxy. I found the problem in the 2.1.4 > and 2.1.3 versions. The 2.0.20, instead, seems to work, -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
