When you add SSH keys in the background of GitHub, if you have some problems with local git clone git://www.somesite.com/test.git, instead of access denied, you need to test this locally:
Ssh-t git@github.com
If the return is:
Permission denied (PublicKey).
Then you might want to ssh-add it locally, but before you do, you can use SSH-VT git@github.com to see what caused the failure.
Ssh-add ~/.ssh/youraccount_rsa
It will then return as follows:
Enter Passphrase For/users/andy/.ssh/youraccount_rsa:
Identity added:/users/andy/.ssh/youraccount_rsa (/USERS/ANDY/.SSH/YOURACCOUNT_RSA)
Then use Ssh-t git@github.com
will return to success:
Hi youraccount! You've successfully authenticated, but GitHub does not provide shell access.
Indicates that your current local SSH has switched to the Youraccount account,
Then you can make Git clone to Local:
git clone git@github.com:youraccount/yourproject.git
Another: If you have the app for the kitten that uses GitHub, then when you git-t git@github.com you will be logged in using the GitHub account you set up in the GitHub program, not SSH's RSA account.
2014.12.12, it was found that the public key information in the Known_hosts file caused the
Delete the original public key information in the/root/.ssh/known_hosts file.
But it hasn't been verified yet.