Nils Breunese (Lemonbit) wrote:
>
>>
>> I m waiting for ur best response.
>
> There are several problems here:
>
> 1) Generate the passphraseless keypair for the backuppc user on the
> server, not for root. BackupPC needs to be able to use it. (You could
> generate it on another machine (your workstation), but be sure to
> transfer the keypair to the backuppc account on the BackupPC server
> and give it the right owner and permissions there.)
> 2) Copy the public key to ~/.ssh/authorized_keys on the clients (not
> authorized_keys.swt-ws5 or something like that)
> 3) Try to login using the passphraseless key at least once before
> giving BackupPC a go, because you need to manually OK the fingerprint
> of the client the first time you login.
>
Remember that the object is to allow commands from the backuppc user on
the server to execute as root on the client machines. The steps above
should work, but if anyone already is using ssh with authorized keys,
you should append your key to the client file instead of overwriting it.
If this is the only key it won't matter. I usually test the setup by
running as the backuppc user on the server with the command:
ssh -l root client_name id
the first time you should be prompted for a confirmation since it is a
new host and after that it should complete and show the output for root
on the client.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
