https://stackoverflow.com/questions/17278796
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianShort answer
If you are accessing the repository over HTTPS, then you can use the http.sslKey configuration or the GIT_SSL_KEY environment variable to specify its location (see the git config docs).
Long answer
Usually it doesn't matter where your private keys are, because ideally they are stored in a key agent, and what you need to figure out is how to make Git use the key agent.
(The thing is, ideally a private should have a passphrase, and so re-entering it every time would not be practical. The key agent is to simplify this.)
Since everyone should be using private keys protected by a passphrase, and thus a key agent to make that practical, it is not common to have to configure the location of the key file.
In windows I use pageant as the key agent, which is part of the PuTTY tools. Simply run pageant.exe and add your private key. Next, to make Git use pageant to get your private key, you need to set the GIT_SSH environment variable to point to plink.exe, for example /c/path/to/putty/plink.exe. You can set it like this in your environment variables, even though it uses UNIX-style path separators.
I am not familiar with TortoiseGit, but I guess it probably has it's own plink.exe, you can use that too. And since you already have TortoiseGit working, I guess you might not even need the key agent at all, just set GIT_SSH. But these are just guesses. The setup I described with PuTTY and pagent should work, as I use it myself. In any case you should use a key agent, and protect your keys with a passphrase, etc etc etc.
