From: mna.news <mna...@fr...> - 2005-08-24 19:55:08
|
Le mercredi 24 Ao=FBt 2005 21:27, Mark Cockrell a =E9crit=A0: >> [..} > >is, the private /home/backuppc/.ssh/id_rsa didn't go with the > >copy of id_rsa.pub that you should have appended to the > >remote /root/.ssh/authorized_keys2. If you think you did this > >right, I'd start over from scratch and generate new keys > >by running ssh-keygen as user backuppc, then copy the public > >key over again. (Note that this will break access to other > >servers if you have any working. > > Les, > I have done that repeatedly. I even went so far as to physically > copy the id_rsa file from the BackupPC server to the client rename it > authorized_keys2. I don't know why it's not able to match them up. > Mark, i give here just some idea : on the machine you want to backup=20 =2D> your distribution is not configure with "/root/.ssh/authorized_keys2" = but=20 "/root/.ssh/authorized_keys" have a look in /etc/ssh/sshd_config to verify this point and you should see= =20 something like : RSAAuthentication yes PubkeyAuthentication yes AuthorizedKeysFile .ssh/authorized_keys =2D> the file's permission isn't good (chmod 600 "/root/.ssh/authorized_key= s" verify also the .ssh directory which should be 700 and be sur that the owner of all those files is "root:root" =2D> and my last remark is : you say " copy the id_rsa file from ... " you shoud copy the id_rsa.pub (you have to put the public key on the machine you want to backup) Michael. |