[EMAIL PROTECTED] wrote: > I would like to have some informations about this connection via ssh. > I know that it's possible to establish this connection either by > password or by public/private keys. But is it necessary to enter the > password every time, with each connection, or to configure for each > Windows client (in my case) the public / private key and relate them > with the SSH server ?
This is how I add a ssh-based client to my backup system: * On the backup server, the user backuppc generates a ssh-key (ssh-keygen -t rsa -f clientname) inside .ssh of the backuppc home directory. Passphrase is empty. * On the backup server, the file .ssh/config belonging to the backuppc user is updated with some needed info for the client (user to connect, ssh-key to use, port to use, ...) * The key is copied to the client (ssh-copyid -i clientname.pub client.domain.com) This action will ask if you trust this host. Answer 'yes' to add it to the know_hosts list. Finished. The user 'backuppc' has now root access to the client through SSH. Setting up BackupPC is now the most easy part: use rsync, set the clients directories to backup. Done. Why do I use a separate key for every client? Security! If someone can get 1 private key from my backup server, he/she can only connect to 1 client instead of all my clients (70 at this moment). Yes it is a bit more work, but security is always more work. Good luck. -- Toni Van Remortel [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
