Re: SFTP Server implementation

[elijah baley]

There is not SFTP implementation per-se - all you need to do is to create an 
SSH server instance, register the SFTP subsystem and start the server. See more 
details in the https://github.com/apache/mina-sshd/ main page README

[https://avatars1.githubusercontent.com/u/47359?v=3&s=400]

apache/mina-sshd
github.com
mina-sshd - Mirror of Apache MINA SSHD





From: vikram guni 
Sent: Wednesday, July 12, 2017 4:00 PM
To: dev@mina.apache.org
Subject: SFTP Server implementation

HI Team,

could you please point me to any SFTP server implementations. pls

--
Vikram Pappula
+919866905444
"Live Your Dream"

[jira] [Commented] (SSHD-755) Nio2Connector leaks socket if address is unresolvable or unreachable

[Matthew S Havener (JIRA)]

[ 
https://issues.apache.org/jira/browse/SSHD-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086278#comment-16086278
 ] 

Matthew S Havener commented on SSHD-755:


Awesome, thank you!

> Nio2Connector leaks socket if address is unresolvable or unreachable
> 
>
> Key: SSHD-755
> URL: https://issues.apache.org/jira/browse/SSHD-755
> Project: MINA SSHD
>  Issue Type: Bug
>Affects Versions: 1.4.0
> Environment: openjdk 1.8.0_111
>Reporter: Matthew S Havener
>Assignee: Goldstein Lyor
> Fix For: 1.7.0
>
> Attachments: mina.patch
>
>
> During an async client connect (with ClientChannel.Streaming.Async), if the 
> hostname is not resolvable, an UnresolvedAddressException is thrown from the 
> "socket.connect(...)" call in Nio2Connector.java. The socket was allocated 
> before the connect, but it is not closed in the "catch" block. This causes 
> the socket to leak, and can eventually exhaust the file descriptors in the 
> system.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SSHD-700) SSHD does not suppot agent forwarding for XShell and XAgent

[Li Fangning (JIRA)]

[ 
https://issues.apache.org/jira/browse/SSHD-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086756#comment-16086756
 ] 

Li Fangning commented on SSHD-700:
--

Hi Goldstein,

I have made changes based on your suggestions.
Please re-check the codes.
Thanks

> SSHD does not suppot agent forwarding for XShell and XAgent
> ---
>
> Key: SSHD-700
> URL: https://issues.apache.org/jira/browse/SSHD-700
> Project: MINA SSHD
>  Issue Type: New Feature
>Affects Versions: 1.2.0
> Environment: Windows 10 and CentOS 7
> XShell 5.0
>Reporter: Li Fangning
>Priority: Minor
> Attachments: block.png, debug.log, environment.png, log1.txt, 
> log2.txt, sshd-core.zip, SshdTest2.java, SshdTest3.java, stacktrace.png
>
>
> I use MINA SSHD for both server side and client side:
> SSH client  --> MINA SSHD Server - MINA SSHD Client --> Target Linux Server
> I use XShell (http://www.netsarang.com/) as SSH client, and use XAgent with 
> XShell for target server authentication (Public Key Access with Agent 
> Forwarding).
> I have tried PuTTY (with pagent), SecureCRT, and openssh client in linux, 
> they are all passed. But when I try XShell with XAgent, the agent forwarding 
> phase is failed.
> When I check the debug log and source code of MINA SSHD, I find that SSHD 
> only handle the "auth-agent-...@openssh.com" request type (in 
> org.apache.sshd.server.channel.ChannelSession#handleInternalRequest), which 
> is OK for PuTTY, SecureCRT and openssh client. But XShell send a 
> "auth-agent-req" request (without "@openssh.com"), so SSHD not handle the 
> request.
> I have try to change the source code, add "auth-agent-req" to the 
> "switch-case" in handleInternalRequest, but the authentication is blocked.
> I have attached my code, please help me solve the problem.
> Thanks a lot.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)