Backuppc : ssh always ask for password

Hello
I'm trying to backup a linux box (etch) on a backuppc server (etch too) but ssh always ask me for a password.
I've followed your howto as others (backuppc's faq...), and I don't know where I missed.
Any Idea ?
Tx
Vincent

Hi Falko,
I have the exact same problem as Trollineto. I've tried your hint, but no success.
I've gone thru your backuppc 4 times scupolously, with my colleagues controlling me to be sure I didn't make any mistakes or typos, and I end up always with the same issue. Strangely when i did it the first time it worked perfectly, then all of a sudden backuppc stopped working because it can't establish the ssh connection anymore. So i've tried to rebuild the ssh tunnel again, following your instructions on point 5 of your how-to, but no luck. It's like the backuppc server not being able to find the authorized key entry on the client.
Is there any log I can check to find out the problem?

I'm losing my mind on this damn ssh key exchange!
I've reinstalled both the openssh server and client on both the server and the client to be backed up, config files included. Still, I can't get to have it working.

Here's is the output of the ssh -vvvv command: please, do help me understand what's wrong.

Looking at auth.log on my server revealed the problem: sshd was
refusing to use my public key because my home directory was
group-writable. In order to do pubkey auth, both the home directory
and the .ssh directory must writable only by the owner.

hi,
as stated earlier, the client is a 'Perfect' Ubuntu Server 6.06.1, called efbujagateway.
Backuppc is installed on a fileserver.
When I look at backuppc's error log for efbujagateway, here's what I read:

I repeat that the client machine is running in recovery mode, because permissions have been accidentally screwed up (sudo chmod 777 / ).
Plus I'm wondering whether some needed services are off and should be on.

i've restored the entire / in the target machine, which means even the /root/.ssh folders, which led to an unmatching couple of ssh-rsa keys, and consequently the backup is not working after the restore.

I've successfully created 2 new ssh-rsa keys, following your tutorial, and now I get to log password-less as backuppc becoming root:
$ ssh -l root 192.168.1.1 whoami
$ root

Ok, back on again.
Apparently the problem resides on the fact that despite the backuppc server asks for a machine fingerprint when connecting for the first time to the target machine when doing the ssh-rsa key exchange via scp, this is not enough. In fact, I've tried a manual dump as suggested in the backuppc troubleshooting hits, and ssh did ask once more to add the client's fingerprint to known_hosts before performing the dump. After that, everything started to work normally again.