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

This is a discussion on ssh keys for remote executeion (local to remote) but can it work the other way. - SSH ; 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 ...

+ Reply to Thread
Results 1 to 7 of 7

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

  1. 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


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

    >>>>> "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


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

    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 ?


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

    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 ?


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

    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 ?


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

    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

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

    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.


+ Reply to Thread