On Wed, 2005-08-24 at 14:27, Mark Cockrell wrote:
> 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.
You want to keep the id_rsa file private and copy the contents of
the corresponding id_rsa.pub file into the remote authorized_keys2
file (actually append it, but if there is only one it doesn't matter).
Your local ssh reads the private key to prove who you are to the
remote server that has the public key. The remote server may be
logging problems that keep it from working like incorrect permissions
somewhere in the path to the key. Also, this is for sshv2. If the
remote sshd is very old it might want the keys in the identity and
authorized_hosts files (but in that case you should probably update it).
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
