Re: [BackupPC-users] Achiving localhost using tar

[Les M. <les...@gm...>]

On Mon, Jan 23, 2012 at 10:07 PM, Kenneth L. Owen
<tx8...@be...> wrote:
> Hi Les,
>
> I'm not getting something about setting up to use rsync to backup /home
> on localhost.  The instructions that I filed for generating keys is:
>
> Setting up BackupPC software to run rsync using visudo:
>
> Create user backuppc on the server and each client.
>
> Then generate keys for your server backuppc user:
> backuppc$> ssh-keygen -t rsa
> use ssh-copy-id to copy the pub key to each of the clients
> backuppc$>ssh-copy-id client
>
> Likewise, on each client generate keys for backuppc user:
> backuppc$> ssh-keygen -t rsa
> use ssh-copy-id to copy the pub key to the server:
> backuppc$>ssh-copy-id archive-server
>
> On the archiving server, backuppc would ssh-copy-id localhost ??
> Where does the reciprocal key come from ??

You don't need to generate new keys.  The keys are a public/private
pair that identify the backuppc user and you should have already had a
set.   You copy the public side of the key (this is what the
ssh-copy-id command does...) _from_ the user/host where the command
will originate (i.e. backuppc on the server) to the user/host where
the execution will be allowed (normally root on the target hosts
unless you are using a more complicated sudo command).    The way ssh
works is that the receiving end of the connection will use the public
key that you added to the authorized_hosts file to make the
originating side prove that it has read access to the private side of
the same key.   If you overwrote the original backuppc user's private
key, you'll have to update the matching public side on all the
targets.

-- 
   Les Mikesell
      les...@gm...