[
https://issues.apache.org/jira/browse/SSHD-506?focusedWorklogId=439879=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-439879
]
ASF GitHub Bot logged work on SSHD-506:
---
Author: ASF GitHub Bot
jvz commented on pull request #132:
URL: https://github.com/apache/mina-sshd/pull/132#issuecomment-637256088
Based on what I'm finding online, it does seem like the RFC specifies the
all caps version. I'm going to try adding that as well.
[
https://issues.apache.org/jira/browse/SSHD-506?focusedWorklogId=439874=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-439874
]
ASF GitHub Bot logged work on SSHD-506:
---
Author: ASF GitHub Bot
jvz edited a comment on pull request #132:
URL: https://github.com/apache/mina-sshd/pull/132#issuecomment-637249935
I can't seem to find any official documentation on what the RFC 5647 cipher
names are supposed to be unless they meant to literally use `AEAD_AES_128_GCM`
and
jvz commented on pull request #132:
URL: https://github.com/apache/mina-sshd/pull/132#issuecomment-637249935
I can't seem to find any official documentation on what the RFC 5647 cipher
names are supposed to be unless they meant to literally use `AEAD_AES_128_GCM`
and `AEAD_AES_256_GCM` as
[
https://issues.apache.org/jira/browse/SSHD-506?focusedWorklogId=439873=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-439873
]
ASF GitHub Bot logged work on SSHD-506:
---
Author: ASF GitHub Bot
jvz commented on pull request #132:
URL: https://github.com/apache/mina-sshd/pull/132#issuecomment-63708
Also tested with FileZilla so far. It even defaulted to selecting
aes256-gcm! Seems to work.
This is an automated
[
https://issues.apache.org/jira/browse/SSHD-506?focusedWorklogId=439852=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-439852
]
ASF GitHub Bot logged work on SSHD-506:
---
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/SSHD-506?focusedWorklogId=439844=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-439844
]
ASF GitHub Bot logged work on SSHD-506:
---
Author: ASF GitHub Bot
jvz commented on pull request #132:
URL: https://github.com/apache/mina-sshd/pull/132#issuecomment-637216880
I merged the latest changes from master and did some basic smoketesting
using the following:
Server: OpenSSH_8.1p1, LibreSSL 2.7.3
Command: `./ssh.sh -c
[
https://issues.apache.org/jira/browse/SSHD-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121296#comment-17121296
]
Thomas Wolf commented on SSHD-1008:
---
[~ssmali1505]: Lyor's answer is for making the server support
[
https://issues.apache.org/jira/browse/SSHD-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lyor Goldstein resolved SSHD-1009.
--
Resolution: Information Provided
> SSHD SCP does not work with WinSCP
>
[
https://issues.apache.org/jira/browse/SSHD-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121202#comment-17121202
]
Lyor Goldstein commented on SSHD-1009:
--
{quote}
I get a error saying Server could not start the
[
https://issues.apache.org/jira/browse/SSHD-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lyor Goldstein updated SSHD-1009:
-
Priority: Minor (was: Major)
> SSHD SCP does not work with WinSCP
>
[
https://issues.apache.org/jira/browse/SSHD-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lyor Goldstein updated SSHD-1009:
-
Issue Type: Question (was: Bug)
> SSHD SCP does not work with WinSCP
>
Hi,
i am trying out Apache SSHD SFTP/Server setup . using the command line, I
am able to transfer the file using SCP, but when I use the WinSCP, it does
not work. After authentication, WinSCP get's message saying Server refused to
start the shell.
15:44:06.956 [NioProcessor-2] DEBUG
Sreedhar J created SSHD-1009:
Summary: SSHD SCP does not work with WinSCP
Key: SSHD-1009
URL: https://issues.apache.org/jira/browse/SSHD-1009
Project: MINA SSHD
Issue Type: Bug
Affects
17 matches
Mail list logo