On my Linux system, I decrypt a private ssh key every time when I boot the system. Once booted I open a terminal and issue:
and I am ready to perform git operations, like
git clone <git-url>,
git pull -a and so on. When I open another terminal and issue such commands again, no prompt will pop up that asks to enter the password of the encrypted ssh-key. In summary, on my linux system I only have to enter the password once.
On my work I have a Windows system. Once booted, I open git-bash and issue:
ssh-add ~/.ssh/private_key, enter the password and issue git commands that are able to communicate with the git repository. In contrast to my Linux system, when I open a new git-bash and issue git commands, then a prompt appears that asks to enter the password. In summary, when the private key has been decrypted in a git-bash terminal, then it is possible to interact with git repository, but when a new terminal is opened the ssh-key should be decrypted again.
What did I try
I tried to use pageant. This first problem is that the id_rsa was not suitable. A new key had to be created using puttygen, but then it turned out that it will not be possible to use the ssh git url that starts with git@. It had to be replaced with the https url, but that is not what I want.
What answer do I prefer
I prefer an answer that satisfies the following criteria:
- Ssh key has to be decrypted once when the Windows system has been booted and a terminal is opened to perform git actions
- When a new terminal is opened, one could continue to interact with the git repository, i.e. no prompt will pop up that requests to enter the password.
- I am not devoted to git-bash. If there is another terminal on windows that matches the first two criteria then it is fine by me.