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

Support for multiple SSH keys/certs #147

Closed
oskar456 opened this issue Apr 8, 2017 · 3 comments
Closed

Support for multiple SSH keys/certs #147

oskar456 opened this issue Apr 8, 2017 · 3 comments
Assignees

Comments

@oskar456
Copy link

oskar456 commented Apr 8, 2017

For a few servers, I use OpenSSH certificate for authentication. That means I use not only private key file id-rsa but also certificate file id-rsa-cert.pub. It works very well with OpenSSH or with Chrome SSH app. But for Mosh app, there is no way how to add the private key and the certificate at the same time.

It would be nice if there were such option, as well as option to have more than one identity or custom SSH config file. Ideally in a similar way it works in the Secure Shell Chrome app.

@rpwoodbu
Copy link
Owner

rpwoodbu commented Apr 9, 2017

I do know that Mosh for Chrome supports SSH certificates. So the issue here is how to have more than one credential at a time. This shouldn't be too hard to do; the keys/certs are in PEM format, which is well-delineated. I should be able to permit adding multiple keys/certs, and the code can go through them all to find one suitable for the remote server (similar to how OpenSSH works).

It would definitely be better to have multiple identities like the Secure Shell app, as you say. Having a way to manage connection profiles has been on my to-do list (Issue #29) since the beginning, but it is just enough UI work that I've never bothered (nor has anyone stepped up to contribute that feature).

@rpwoodbu rpwoodbu self-assigned this Apr 9, 2017
@rpwoodbu rpwoodbu changed the title Support for client SSH certificates Support for multiple SSH keys/certs Dec 4, 2017
@rpwoodbu
Copy link
Owner

In light of learning that there's an SSH agent implementation for Chrome, I am inclined not to build any more functionality into Mosh for Chrome's internal SSH key management. I think I'll keep what we have, just so you don't have to use an external agent for simple usage (and to avoid breaking existing users).

Closing this in favor of Issue #78.

@oskar456
Copy link
Author

Well, this doesn't really solve the issue with SSH certificates, as there is no way how to load SSH certificate to the Agent app either. But I understand that now it is a someone else's problem, so let's report it there! ;)

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

No branches or pull requests

2 participants