We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Scenario: You have multiple existing keys, but don't specify one on the commandline
Requested feature: Give you a choice of keys to use for this host (perhaps even the choice to create one specifically for this host? )
The creation of new keys could even be extended to create a single purpose key using COMMAND="XYZ" <--key --> on the remote box.
Opinions?
The text was updated successfully, but these errors were encountered:
Sounds useful. Care to submit a patch?
Sorry, something went wrong.
I'll definitely look into it :)
I think the changes in my pull request implement this:
Say key A exists, as ~/.ssh/id_rsa_a:
~/.ssh/id_rsa_a
ssh-forever hedge@desktop -p 22 -i ~/.ssh/id_rsa_a -n cuken -a -q
Should not create a new key, but will add to your ~/.ssh/config
~/.ssh/config
Host cuken HostName desktop User hedge PreferredAuthentications publickey IdentityFile /home/hedge/.ssh/id_rsa_a StrictHostKeyChecking false HostKeyAlias cuken
Let me know if that is what you had in mind.
No branches or pull requests
Scenario: You have multiple existing keys, but don't specify one on the commandline
Requested feature: Give you a choice of keys to use for this host (perhaps even the choice to create one specifically for this host? )
The creation of new keys could even be extended to create a single purpose key using COMMAND="XYZ" <--key --> on the remote box.
Opinions?
The text was updated successfully, but these errors were encountered: