Ticket #152 (closed defect: fixed)

Opened 5 years ago

Last modified 3 months ago

Read IdentityFile setting from OpenSSH configuration in ~/.ssh/config

Reported by: chris@… Owned by: dkocher
Priority: normal Milestone: 3.1
Component: sftp Version:
Severity: normal Keywords:
Cc: Platform:
Architecture:

Description

I'd love to have my ~/.ssh/config host aliases work in Cyberduck, and it would be sweet to have it already know the right identity files too.

Change History

comment:1 Changed 5 years ago by dkocher

  • Status changed from new to assigned
  • Milestone set to 2.6

comment:2 Changed 5 years ago by dkocher

  • Priority changed from normal to low
  • Milestone changed from 2.6 to 2.7

comment:3 Changed 4 years ago by dkocher

  • Milestone 2.7 deleted

Milestone 2.7 deleted

comment:4 Changed 21 months ago by anonymous

  • Priority changed from low to normal
  • Milestone set to 3.1

This is pretty important for SFTP. As a web dev with multiple clients with multiple environments, SSH aliases are the only way to be efficient. Any news?

comment:5 Changed 20 months ago by dkocher

  • Status changed from assigned to closed
  • Resolution set to fixed

In r4402.

comment:6 Changed 20 months ago by dkocher

  • Summary changed from Could use ~/.ssh/config for SFTP connections to Read IdentityFile setting from OpenSSH configuration in ~/.ssh/config

comment:7 Changed 20 months ago by dkocher

Also read username from configuration. In r4408.

comment:8 follow-up: ↓ 9 Changed 18 months ago by hegewald@…

  • Status changed from closed to reopened
  • Type changed from enhancement to defect
  • Version 2.5.4 deleted
  • Resolution fixed deleted
  • Milestone 3.1 deleted

Dear Caberduck Team, there seems to be a little glitch with this nice feature. I will try to explain what I observe here (Cyberduck 3.1.2, Mac OS 10.5.6): I use a ~/ssh/config to allow multiple keys. In the config I have Host * and then lines setting IdentityFile. This works pretty well with plain ssh. Cyberduck seems to ignore the default key files (i.e. id_dsa), which is not in my ~/ssh/config. If I remove the Host * and replace it with Host <full.host.name>, then Cyberduck seems to behave and also uses the id_dsa. I would expect to see the same behaviour as if connecting via plain ssh. Cheers, -- Jan

comment:9 in reply to: ↑ 8 Changed 18 months ago by dkocher

  • Status changed from reopened to closed
  • Resolution set to fixed
  • Milestone set to 3.1

Replying to hegewald@…:

Dear Caberduck Team, there seems to be a little glitch with this nice feature. I will try to explain what I observe here (Cyberduck 3.1.2, Mac OS 10.5.6): I use a ~/ssh/config to allow multiple keys. In the config I have Host * and then lines setting IdentityFile. This works pretty well with plain ssh. Cyberduck seems to ignore the default key files (i.e. id_dsa), which is not in my ~/ssh/config. If I remove the Host * and replace it with Host <full.host.name>, then Cyberduck seems to behave and also uses the id_dsa. I would expect to see the same behaviour as if connecting via plain ssh. Cheers, -- Jan

There is currently no support for wildcards in the config. Must be tracked in a separate ticket.

Note: See TracTickets for help on using tickets.