On 31/01/08 20:23 -0500, John Mort wrote: > Ah, okay. So there's no way to get around having to manually point > out the location of the private key when I'm making the ssh > connection?
Its worth noting that this has nothing to do with PGP or GPG; this is purely ssh. Both types use "public key encryption", so its sometimes easy to mix up. Anyhow, here's a session I did on my laptop to my shell machine. (I don't actually do this personally, possibly because of "if my laptop goes missing and I dont notice" fears? Either way, to undo this, all you need to do is delete the relevent line from ~/.ssh/authorized_keys on the remote host.) freedom:~ porkchop$ ls .ssh known_hosts freedom:~ porkchop$ ssh-keygen -t dsa Generating public/private dsa key pair. Enter file in which to save the key (/Users/porkchop/.ssh/id_dsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /Users/porkchop/.ssh/id_dsa. Your public key has been saved in /Users/porkchop/.ssh/id_dsa.pub. The key fingerprint is: e2:33:39:e0:ae:4e:1a:b6:63:97:ad:24:9e:00:36:d4 [EMAIL PROTECTED] freedom:~ porkchop$ ls .ssh id_dsa id_dsa.pub known_hosts freedom:~ porkchop$ scp id_dsa.pub porkchop.net:.ssh/authorized_keys [EMAIL PROTECTED]'s password: id_dsa.pub 100% 612 0.6KB/s 00:00 freedom:~ porkchop$ ssh porkchop.net This is lostcause. [EMAIL PROTECTED]:~$ Cheers, -porkchop _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Feb 6 - DBUS Mar 5 - Setting up a platform-independent home/small office network using Linux
