On Thu, 3 Nov 2011 13:19:17 -0700 Steve Jenkins <[email protected]> wrote:
> As far as I can tell, the way to do this is to put the contents of: > > "/var/lib/amanda/.ssh/client_authorized_keys" on the server box > (Tapper) into "/var/lib/amanda/.ssh/authorized_keys" on the client box > (CarbonFiber), which I've also done. The > /var/lib/amanda/.ssh/authorized_keys file didn't exist on the client, > so I created it. I've tested amservice with the authorized_keys file > on the client being owned by root as well as the amandabackup user, > and the file permissions are 600. > > Google hasn't been much help in solving this issue. I'd appreciate any > nudges in the right direction. Permissions? Ownership? Something else? Correct so far. I usually name the file "....ssh/authorized_keys2", a holdover from when SSH protocols 1 and 2 lived side by side. So that's something to try. When logging in for the first time, the name of the target computer must be exactly the name and domain name used in the relevant disklist entries. On my system, disklist shows: yendi.localdomain /boot comp-root-tar so I log in like so: ssh [email protected] For DNS purposes, yendi != yendi.localdomain On client yendi, my perms are as follows: root@yendi:~# ll /var/backups/.ssh/ total 12 drwx------ 2 backup backup 4096 2011-06-03 13:14 ./ drwxr-xr-x 3 root root 4096 2011-11-03 04:35 ../ -rw-r--r-- 1 backup backup 408 2011-05-30 16:28 authorized_keys2 root@yendi:~# -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
