[Cyberduck-trac] [Cyberduck] #11227: Using .ssh/config with Cyberduck

[Cyberduck]

#11227: Using .ssh/config with Cyberduck
-------------------------+-------------------------
 Reporter:  mbaciarello  |         Owner:
     Type:  defect       |        Status:  reopened
 Priority:  normal       |     Milestone:  7.7
Component:  core         |       Version:  7.6.2
 Severity:  normal       |    Resolution:
 Keywords:               |  Architecture:  Intel
 Platform:  macOS 11     |
-------------------------+-------------------------
Changes (by mbaciarello):

 * status:  closed => reopened
 * resolution:  worksforme =>


Comment:

 Hi!

 Thanks for your reply. I got version 7.7.0 (33716) running but the bastion
 connection still isn’t working for me. I think I may be misunderstanding
 part of the terminology. Allow me to explain my setup:

 .ssh/config:

 {{{
 Host Winnie
         [various settings]
         HostName winnie.address.com

 Host RedCapNew
         [settings]
         HostName redcap.address.com
         ProxyJump Winnie
 }}}

 When I use ssh, I can just `ssh RedCapNew` and everything works fine.

 Cyberduck fails without errors—which is what I’d expect from an app trying
 to connect to RedCapNew directly, without a bastion…

 In Cyberduck, I’ve entered redcap.address.com in the `Server:` field of
 the bookmark. Is this correct, in order for CyberDuck to match with the
 config file? Or should I use the Host value in Cyberduck (as opposed to
 HostName) ?

 Thanks again for your help,

 —Marco

--
Ticket URL: <https://trac.cyberduck.io/ticket/11227#comment:3>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows