You can use ssh-agent and have all your keys there, or you can still use .ssh/config, just list your keys in IdentityFile entries without tying them to specific hosts.
As a third option, you can use wildcards on hostnames in .ssh/config, so you can create an umbrella host for something like ec2*.aws.com (don't recall the hostname that amazon sets for those right now). Specifying user@host is the least secure of all options, so I would avoid that. -- Cassiano Leal On Tuesday, 21 August 2012 at 21:41, smartnut007 wrote: > Playing around with Capistrano. I couldn't find any specific documentation on > situations with multiple keys. > > Its good one is able to specify the username with the user@host syntax. But, > i want to be able to do that for ssh keys too, at least at the cap file level. > > using .ssh/config to maps keys to hosts is not an option because of the > dynamic nature of the hosts ( ec2 machines ) involved. > > Appreciate the help. > > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to [email protected] > (mailto:[email protected]) > * To unsubscribe from this group, send email to > [email protected] For more options, visit this group at > http://groups.google.com/group/capistrano?hl=en > > -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
