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

["Goldstein Lyor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SSHD-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Goldstein Lyor reassigned SSHD-700:
-----------------------------------

    Assignee: Goldstein Lyor

> 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
>            Assignee: Goldstein Lyor
>            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-req@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)