ssh keys for remote executeion (local to remote) but can it work the other way.

Hi,

Generating ssh keys for for local and remote on a two node
configuration. is fine and works fine

Can do things like ssh tom@remote ps -ef ---------------> from local

However can remote execution of scripts be executed from the remote to
the local with the same keys.

eg ssh tom@local ps -ef -------------------> from remote.

Or do a whole new bunch of keys have to be generated.

GB

>>>>> "fearban" == fearban <Fearban@gmail.com> writes:

fearban> Hi, Generating ssh keys for for local and remote on a two
fearban> node configuration. is fine and works fine

fearban> Can do things like ssh tom@remote ps -ef --------------->
fearban> from local

fearban> However can remote execution of scripts be executed from the
fearban> remote to the local with the same keys.

fearban> eg ssh tom@local ps -ef -------------------> from remote.

fearban> Or do a whole new bunch of keys have to be generated.

fearban> GB

You don't need new keys, but you need to move them around. The situation
is asymmetric: the source needs the private key, and the destination needs
the public key in authorized_keys.

--
Richard Silverman
[email]res@qoxp.net[/email]

On Jun 13, 5:17 pm, "Richard E. Silverman" <r...@qoxp.net> wrote:[color=blue][color=green][color=darkred]
> >>>>> "fearban" == fearban <Fear...@gmail.com> writes:[/color][/color]
>
> fearban> Hi, Generatingsshkeys for for local and remote on a two
> fearban> node configuration. is fine and works fine
>
> fearban> Can do things likesshtom@remote ps -ef --------------->
> fearban> from local
>
> fearban> However can remote execution of scripts be executed from the
> fearban> remote to the local with the same keys.
>
> fearban> egsshtom@local ps -ef -------------------> from remote.
>
> fearban> Or do a whole new bunch of keys have to be generated.
>
> fearban> GB
>
> You don't need new keys, but you need to move them around. The situation
> is asymmetric: the source needs the private key, and the destination needs
> the public key in authorized_keys.
>
> --
> Richard Silverman
> r...@qoxp.net[/color]

Does this mean that you have to send the private key accross to second
machine ? using scp ?

On Jun 13, 5:17 pm, "Richard E. Silverman" <r...@qoxp.net> wrote:[color=blue][color=green][color=darkred]
> >>>>> "fearban" == fearban <Fear...@gmail.com> writes:[/color][/color]
>
> fearban> Hi, Generatingsshkeys for for local and remote on a two
> fearban> node configuration. is fine and works fine
>
> fearban> Can do things likesshtom@remote ps -ef --------------->
> fearban> from local
>
> fearban> However can remote execution of scripts be executed from the
> fearban> remote to the local with the same keys.
>
> fearban> egsshtom@local ps -ef -------------------> from remote.
>
> fearban> Or do a whole new bunch of keys have to be generated.
>
> fearban> GB
>
> You don't need new keys, but you need to move them around. The situation
> is asymmetric: the source needs the private key, and the destination needs
> the public key in authorized_keys.
>
> --
> Richard Silverman
> r...@qoxp.net[/color]

Does this mean that you have to send the private key accross to second
machine ? using scp ?

On Jul 11, 10:36 am, gerry.bren...@gmail.com wrote:[color=blue]
> On Jun 13, 5:17 pm, "Richard E. Silverman" <r...@qoxp.net> wrote:
>
>
>[color=green][color=darkred]
> > >>>>> "fearban" == fearban <Fear...@gmail.com> writes:[/color][/color]
>[color=green]
> > fearban> Hi, Generatingsshkeys for for local and remote on a two
> > fearban> node configuration. is fine and works fine[/color]
>[color=green]
> > fearban> Can do things likesshtom@remote ps -ef --------------->
> > fearban> from local[/color]
>[color=green]
> > fearban> However can remote execution of scripts be executed from the
> > fearban> remote to the local with the same keys.[/color]
>[color=green]
> > fearban> egsshtom@local ps -ef -------------------> from remote.[/color]
>[color=green]
> > fearban> Or do a whole new bunch of keys have to be generated.[/color]
>[color=green]
> > fearban> GB[/color]
>[color=green]
> > You don't need new keys, but you need to move them around. The situation
> > is asymmetric: the source needs the private key, and the destination needs
> > the public key in authorized_keys.[/color]
>[color=green]
> > --
> > Richard Silverman
> > r...@qoxp.net[/color]
>
> Does this mean that you have to send the private key accross to second
> machine ? using scp ?[/color]


What if there is more machines involved ? how do you copy several
id_dsa 's to one computer ?

[email]gerry.brennan@gmail.com[/email] wrote:[color=blue]
> On Jul 11, 10:36 am, gerry.bren...@gmail.com wrote:[color=green]
>> On Jun 13, 5:17 pm, "Richard E. Silverman" <r...@qoxp.net> wrote:
>>
>>
>>[color=darkred]
>> > >>>>> "fearban" == fearban <Fear...@gmail.com> writes:[/color]
>>[color=darkred]
>> > fearban> Hi, Generatingsshkeys for for local and remote on a two
>> > fearban> node configuration. is fine and works fine[/color]
>>[color=darkred]
>> > fearban> Can do things likesshtom@remote ps -ef --------------->
>> > fearban> from local[/color]
>>[color=darkred]
>> > fearban> However can remote execution of scripts be executed from the
>> > fearban> remote to the local with the same keys.[/color]
>>[color=darkred]
>> > fearban> egsshtom@local ps -ef -------------------> from remote.[/color]
>>[color=darkred]
>> > fearban> Or do a whole new bunch of keys have to be generated.[/color]
>>[color=darkred]
>> > fearban> GB[/color]
>>[color=darkred]
>> > You don't need new keys, but you need to move them around. The
>> > situation is asymmetric: the source needs the private key, and the
>> > destination needs the public key in authorized_keys.[/color]
>>[color=darkred]
>> > --
>> > Richard Silverman
>> > r...@qoxp.net[/color]
>>
>> Does this mean that you have to send the private key accross to second
>> machine ? using scp ?[/color]
>
>
> What if there is more machines involved ? how do you copy several
> id_dsa 's to one computer ?
>[/color]

Use only one private key per machine.. You Just need to add each public
key into all the authorized_keys of all the machines, including it own
public key. You can do this authorized_keys file for one computer first
and copy it on the other computers if you want.

--
Martin

On Jul 11, 7:46 pm, Martin Gagnon <mar...@NoSpAm.yanos.org> wrote:[color=blue]
> gerry.bren...@gmail.com wrote:[color=green]
> > On Jul 11, 10:36 am, gerry.bren...@gmail.com wrote:[color=darkred]
> >> On Jun 13, 5:17 pm, "Richard E. Silverman" <r...@qoxp.net> wrote:[/color][/color]
>[color=green][color=darkred]
> >> > >>>>> "fearban" == fearban <Fear...@gmail.com> writes:[/color][/color]
>[color=green][color=darkred]
> >> > fearban> Hi, Generatingsshkeys for for local and remote on a two
> >> > fearban> node configuration. is fine and works fine[/color][/color]
>[color=green][color=darkred]
> >> > fearban> Can do things likesshtom@remote ps -ef --------------->
> >> > fearban> from local[/color][/color]
>[color=green][color=darkred]
> >> > fearban> However can remote execution of scripts be executed from the
> >> > fearban> remote to the local with the same keys.[/color][/color]
>[color=green][color=darkred]
> >> > fearban> egsshtom@local ps -ef -------------------> from remote.[/color][/color]
>[color=green][color=darkred]
> >> > fearban> Or do a whole new bunch of keys have to be generated.[/color][/color]
>[color=green][color=darkred]
> >> > fearban> GB[/color][/color]
>[color=green][color=darkred]
> >> > You don't need new keys, but you need to move them around. The
> >> > situation is asymmetric: the source needs the private key, and the
> >> > destination needs the public key in authorized_keys.[/color][/color]
>[color=green][color=darkred]
> >> > --
> >> > Richard Silverman
> >> > r...@qoxp.net[/color][/color]
>[color=green][color=darkred]
> >> Does this mean that you have to send the private key accross to second
> >> machine ? using scp ?[/color][/color]
>[color=green]
> > What if there is more machines involved ? how do you copy several
> > id_dsa 's to one computer ?[/color]
>
> Use only one private key per machine.. You Just need to add each public
> key into all the authorized_keys of all the machines, including it own
> public key. You can do this authorized_keys file for one computer first
> and copy it on the other computers if you want.
>
> --
> Martin[/color]


You don't need new keys, but you need to move them around. The
situation
is asymmetric: the source needs the private key, and the destination
needs
the public key in authorized_keys.