On Fri, Sep 16, 2011 at 11:58 AM, Viet H. Phan <hoangvietp...@yahoo.com>wrote:
> Hi,
>
> I am using JSch to do SFTP with a partner. The partner asks me to connect
> to their SFTP server through SSH tunneling:
>
> Metlife Security Policy mandates that Trading Partners connect to MetLife’s
> Transmission servers via SSH tunneling. The following configuration steps
> must be performed in the client environment:
> ** ***I. Create a tunnel connection:*
> ** **ssh2 –S –L <*port_num*>:<*target_svr*>:22 <*tunnel_user*>@<*
> tunnel_svr*>
> ** ***II. Use the tunnel to connect:*
> ** **sftp2 <*target_svr_user*>@localhost#<*port_num*>
> ** ***Where:*
> port_num - any local port number customer may specify.
> target_svr - ****
>
> tunnel_user - will be provided by MetLife External Transmission Admin Team.
> ****
> tunnel_svr - ****
>
> target_svr_user - will be provided by MetLife External Transmission Admin
> Team.
>
> My opinion is that this is unnecessary because SFTP is SSH-based already
> (but the partner insists on their requirement).
>
I agree with you.
> I don't see JSch supports this. I see WinSCP supports this. Do you think
> this should be supported by JSch?
>
> I don't see why not, it's just a two step process, just as in the example
provided by MetLife -- first establish a normal ssh session with local
forwarding, and then establish a separate sftp session over the tunnel using
the specified local port. Did you try this? If so can you provide sample
code which fails to achieve this?
Shai
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users
