Gary Hennigan said: > After the keygen you'll have a file called ~/.ssh/identity.pub. Copy > the contents of that file and add it to the file on remote machines > called ~/.ssh/authorized_keys.
Worked great - thanks! At this point, I only have one authorized key; I presume that I'll want to set up separate keys for other source machines. What is the preferred method for adding new keys to the file? `cat identity.pub >> authorized_keys`? > It's not quite as easy as the method you used, but it's certainly more > secure. Actually, now that I know what I'm doing, I'd have to say that it's about as easy on my home machines. _Much_ easier on a box where you don't have root access and can't modify shosts.equiv, though... > > Suggestions, anyone? > [sorry, no idea on #2 and #3] I think those were due to stale NFS handles. The client machine I was working from as I upgraded the server has /home NFS-mounted from that server. NFS became unavailable temporarily during the upgrade process (since it was one of the things upgraded) and I suspect that made my X session think ~ was unavailable even after NFS was back up. In any case, logging completely out of the (client) system and back in fixed those two problems. Everything seems to be fully functional again. (Although when I do an apt-get from the command line, it seems to think I only have 32 packages installed...) -- "Two words: Windows survives." - Craig Mundie, Microsoft senior strategist "So does syphillis. Good thing we have penicillin." - Matthew Alton Geek Code 3.1: GCS d- s+: a- C++ UL++$ P+>+++ L+++>++++ E- W--(++) N+ o+ !K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI++++ D G e* h+ r++ y+
