@dkocher commented

Milestone 2.7 deleted
bachelorette party favors

anonymous commented

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?

@dkocher commented

In 6d4a4b5.

@dkocher commented

Also read username from configuration. In c8e27a8.

4dfa714 commented

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

@dkocher commented

Replying to [comment:8 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.

anonymousdd commented

https://netdot.uoregon.edu/trac/ticket/288#comment:16