Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
cyberduck opened this issue Jan 23, 2006 · 7 comments
Closed

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

cyberduck opened this issue Jan 23, 2006 · 7 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 23, 2006

6a6740f created the issue

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 27, 2006

@dkocher commented

Milestone 2.7 deleted
bachelorette party favors

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 23, 2008

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?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 28, 2008

@dkocher commented

In 6d4a4b5.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 28, 2008

@dkocher commented

Also read username from configuration. In c8e27a8.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2009

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

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 16, 2009

@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.

Loading

@cyberduck cyberduck closed this Mar 16, 2009
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 4, 2010

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants