dealing with multiple ssh keys and configuring ssh key in capfile - Capistrano

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion dealing with multiple ssh keys and configuring ssh key in capfile
Date: Wed, 22 Aug 2012 14:28:44 -0700 (PDT)
From: smartnut007 <sinchronized.a...@gmail.com>
To: capistrano@googlegroups.com
Message-Id: <08eb9b6b-1cc3-48e7-8e3e-bb019c268c11@googlegroups.com>
In-Reply-To: <76B36FB134564313AE9A84292314F545@gmail.com>
References: <5ea4e938-2b28-426f-a604-b5f71ba2ecb8@googlegroups.com>
 <76B36FB134564313AE9A84292314F545@gmail.com>
Subject: Re: [capistrano] dealing with multiple ssh keys and configuring ssh
 key in capfile
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_58_21647980.1345670924559"

------=_Part_58_21647980.1345670924559
Content-Type: multipart/alternative; 
	boundary="----=_Part_59_6907771.1345670924559"

------=_Part_59_6907771.1345670924559
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Thanks. All of those options seem workable for me.

On Wednesday, August 22, 2012 3:45:13 AM UTC-7, Cassiano Leal wrote:
>
>  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 capis...@googlegroups.com<javascript:>
> * To unsubscribe from this group, send email to 
> capistrano+...@googlegroups.com <javascript:> For more options, visit 
> this group at http://groups.google.com/group/capistrano?hl=en
>
>  
>  
------=_Part_59_6907771.1345670924559
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Thanks. All of those options seem workable for me.<br><br>On Wednesday, Aug=
ust 22, 2012 3:45:13 AM UTC-7, Cassiano Leal wrote:<blockquote class=3D"gma=
il_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid=
;padding-left: 1ex;">
                <div>
                    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.</div><div><br></div><div>As a third o=
ption, you can use wildcards on hostnames in .ssh/config, so you can create=
 an umbrella host for something like ec2*.<a href=3D"http://aws.com" target=
=3D"_blank">aws.com</a> (don't recall the hostname that amazon sets for tho=
se right now).
                </div><div><br></div><div>Specifying user@host is the least=
 secure of all options, so I would avoid that.</div>
                <div><div><br></div><div>--&nbsp;</div><div>Cassiano Leal</=
div><div><br></div></div>
                =20
                <p style=3D"color:#a0a0a8">On Tuesday, 21 August 2012 at 21=
:41, smartnut007 wrote:</p>
                <blockquote type=3D"cite" style=3D"border-left-style:solid;=
border-width:1px;margin-left:0px;padding-left:10px">
                    <span><div><div><div>Playing around with Capistrano. I =
couldn't find any specific documentation on situations with multiple keys. =
</div><div><br></div><div>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.</div><div><br></div><div>using .ssh/config =
to maps keys to hosts is not an option because of the dynamic nature of the=
 hosts ( ec2 machines ) involved. </div><div><br></div><div>Appreciate the =
help.</div><div><br></div><div>-- </div><div>* You received this message be=
cause you are subscribed to the Google Groups "Capistrano" group.</div><div=
>* To post to this group, send email to <a href=3D"javascript:" target=3D"_=
blank" gdf-obfuscated-mailto=3D"4lYsbjlXv78J">capis...@googlegroups.com</a>=
</div><div>* To unsubscribe from this group, send email to <a href=3D"javas=
cript:" target=3D"_blank" gdf-obfuscated-mailto=3D"4lYsbjlXv78J">capistrano=
+...@<wbr>googlegroups.com</a> For more options, visit this group at <a hre=
f=3D"http://groups.google.com/group/capistrano?hl=3Den" target=3D"_blank">h=
ttp://groups.google.com/<wbr>group/capistrano?hl=3Den</a></div></div></div>=
</span>
                =20
                =20
                =20
                =20
                </blockquote>
                =20
                <div>
                    <br>
                </div>
</blockquote>
------=_Part_59_6907771.1345670924559--

------=_Part_58_21647980.1345670924559--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
