|
|
10.5: Use public keys with SSH in 10.5
This didn't work for me by default on both my FreeBSD and CentOS servers. You have to first put a public key on the servers you want to connect to. A friend suggested the following which worked great:
Be sure to change username@myserver.com to your remote username and server address. If you are doing this for multiple servers, you only need to repeat step 4 for each server. Also check these pages for more info if you're having problems, especially if you had SSHKeyChain installed: - Tim from ProMacBlog.com
10.5: Use public keys with SSH in 10.5
A few corrections. You can't simply cat the public key over to a server if you haven't created the
And you're right, the key needs to be on the other end first, before you get this dialog because this is add the key to the running ssh-agent. If there is no pubkey negotiation, ssh-agent isn't consulted at all, you're providing a straight password to the remote sshd server. A good primer on using OpenSSH is here: Optimizing OpenSSH [linsec.ca]. I wrote it, it's a few years old, but still really relevant for OS X or Linux (servers or clients).
10.5: Use public keys with SSH in 10.5
Oh, I also forgot to mention that if you're calling ssh-agent directly from a .bashrc or similar file on terminal startup, you may also not get this prompt. You'll know whether or not this is the case by doing:
If you see something like
10.5: Use public keys with SSH in 10.5
If you have yr umask correctly set, the chmod issue isn't an issue. I use tcsh with backslash_quote on, and here's the alias that's served me quite well:
10.5: Use public keys with SSH in 10.5
Here's the line in my rc file, with all the nasty backslashes and quotes:
--- |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|