Question

When I set up Git, I did it while using a dsl modem, and my ip isn’t static, so when I generated the ssh keys for Git, it was based on that ip.

When I’m assigned an ip other than the one used to generate the ssh Git keys, I can manually change the ip address to the one used to generate the keys. What are my other options to bypass this step? Dynamic DNS? Is there another way?

Update:

OK, so the key isn’t influenced by the ip address. I did a git push origin master and got a not recognized key error and thought it was the ip address. I’ll have to try and regenerate that error.

Answer 1

I should have been clearer in my question, I wasn’t using GitHub – the Git server in question is my own laptop, not GitHub, so it was the server ip that was changing on the whim of the modem/router.

What I did to resolve this was for each ip, to puttygen a key pair. I then added the public key to the authorized_keys file, kept a copy of the private key for my other machines and did a putty for each ip address to add the key to putty’s cache. Now I just do this for each ip assigned by the modem. A pain, but only once rather than changing ips all the time.

I do have to update the remote section of the config file in the .git directory to the ip address though. I guess I could add a separate section for each ip address in the remote section based on the ip address, plus a corresponding branch section.

This was the error I was getting:

The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:...
Connection abandoned.
fatal: The remote end hung up unexpectedly

My setup is on Windows 7 and consists of Cygwin (ssh only), msysgit and the putty suite.