David Zhang <dzhang21@...> writes: > On the server, it's actually ~/.ssh/authorized_keys2. That serves the same purpose, right?
To tell you the truth - I do not know. I would assume so. > Also, do the id_rsa, id_rsa.pub, and known_hosts files in the ~/.ssh/ on *the server* matter at all? They do for the user account they belong to. > I noticed that the id_rsa.pub file on the server has the exact same key as I do on my machine except for the email at the end. That should not happen. RSA keys are in pairs - private and public. The private key (id_rsa) MUST remain a secret only known to the user. The public key (id_rsa.pub) can be spread and wide. When someone wants to encrypt something that ONLY you can see, they use your public key. The only private key in existence that can decode the message is your id_rsa. If the keys are exactly the same except the email address, something bad has happened. I would rename the folder and generate a new key pair: ssh-keygen Then copy around the public key as required, placing it into authorised_key where needed. > It also has the same key as one listed in authorized_keys2, except for the email at the end (the email at the end in the authorized_keys2 file is actually my old email... I asked above if the email at the end matters, and I'm still curious if it does. Should the email at the correspond to my git config global email or something? Because it's changed... :/) As before, the email address is different, so the key will not match. You cannot simply edit the email address either - it will not work. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
