>>>>> "fearban" == fearban 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
res@qoxp.net

On Jun 13, 5:17 pm, "Richard E. Silverman" wrote:
> >>>>> "fearban" == fearban writes:
>
> 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

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" wrote:
> >>>>> "fearban" == fearban writes:
>
> 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

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:
> On Jun 13, 5:17 pm, "Richard E. Silverman" wrote:
>
>
>
> > >>>>> "fearban" == fearban writes:
>
> > 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
>
> Does this mean that you have to send the private key accross to second
> machine ? using scp ?


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

gerry.brennan@gmail.com wrote:
> On Jul 11, 10:36 am, gerry.bren...@gmail.com wrote:
>> On Jun 13, 5:17 pm, "Richard E. Silverman" wrote:
>>
>>
>>
>> > >>>>> "fearban" == fearban writes:
>>
>> > 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
>>
>> Does this mean that you have to send the private key accross to second
>> machine ? using scp ?
>
>
> What if there is more machines involved ? how do you copy several
> id_dsa 's to one computer ?
>

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 wrote:
> gerry.bren...@gmail.com wrote:
> > On Jul 11, 10:36 am, gerry.bren...@gmail.com wrote:
> >> On Jun 13, 5:17 pm, "Richard E. Silverman" wrote:
>
> >> > >>>>> "fearban" == fearban writes:
>
> >> > 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
>
> >> Does this mean that you have to send the private key accross to second
> >> machine ? using scp ?
>
> > What if there is more machines involved ? how do you copy several
> > id_dsa 's to one computer ?
>
> 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


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.