Cyberduck Mountain Duck CLI

Changes between Version 9 and Version 10 of Ticket #2865, comment 38


Ignore:
Timestamp:
Apr 24, 2017 3:36:59 PM (3 years ago)
Author:
yourwebclient
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2865, comment 38

    v9 v10  
    1 I found myself desperately needing to access a VPN that was connected to on a remote host, from my localhost (Mac). Specifically, I wanted CyberDuck on my Mac to have access to hosts on a VPN that only a remote (but locally accessible) host had access to. But I found the ProxyCommand setting that works perfectly with BBEdit's SFTP infrastructure, doesn't work with Cyberduck, and the ProxyCommand option is apparently unsupported by CyberDuck.
     1I found myself desperately needing to access a VPN that was connected to on a remote host, from my localhost (Mac). Specifically, I wanted CyberDuck on my Mac to have access to hosts on a VPN that only a remote (but locally accessible) host had access to. But I found the ProxyCommand setting that works perfectly with BBEdit's SFTP infrastructure, doesn't work with Cyberduck.
    22
    33WORKAROUND:  I set up an ssh tunnel daemon using the Mac "SSH Tunnel" app (paid app) from the App Store, using the app as convenient way to track and manage tunnels (in my case, all one of them), but no magic there, it's just uses ssh -L ...  (many examples of setting up that kind of tunnel, online).  Once a  tunnel is running that bridges the Mac to a host on VPN via the the VPN-connected remote host (lets call it the proxy), I connect with Cyberduck running on the mac to the tunnel port on same mac Cyberduck running on  (e.g. to localhost:<tunnel port>), and whalla - CyberDuck now has access to a host on the  VPN.  The downside of this workaround might be an avoidable performance hit (e.g. redundant ssh encryption of the I/O streams). 
swiss made software