By default the public and private keys are stored inĬ:\Documents and Settings\\.ssh\ or c:\Users\\.ssh\. You will be asked where if you want to protect the private Use the same email address as the email address used in git. Type the following command: ssh-keygen -C -t rsa Open the separate Git bash or the console tab. I recommend to use the git bash because the path to To generate a key pair in OpenSSH you need to go to the command line. Reason PuTTY is the preferred SSH client in GitExtensions. GitExtensions will show the command line window for every command that might require a SSH connection. Therefore it is slightly more complex to use.Īnother drawback is that GitExtensions cannot control OpenSSH and needs to show the command line dialogs when OpenSSH mightīe used. OpenSSH is the best SSH client there is but it lacks Windows support. To configure GitExtensions to use OpenSSH, see SSH. This is done in the Manage remote repositories dialog. GitExtensions can load the private keys automatically for you when communicating with a remote. Load the private key into the PuTTY authentication agent in Clone dialoge or by starting the PuTTY authentication agent and choose add key in the context menu in the system tray. You can add multiple keys here, but you only need one key for all repositories.Īfter telling github what public key to use to decrypt, you need to tell GitExtensions what private key to use to encrypt. This can be done in Account Settings in the tab Now you have a key pair you need to give github the public key. You can choose to protect the private key with a password but this is not necessary. When the key is generated you can save the public and PuTTY will ask you to move the mouse around to generate a more random key. In this paragraph I will show how to generate a key for github using putty.įirst make sure GitExtensions is configured to use PuTTY and all paths are correct, see SSHĬan choose Generate or import key to start the key generator. Unfortunately PuTTY does not work withĪll servers. PuTTY is SSH client that for Windows that is a bit more user friendly then OpenSSH. Instead you can checkout the remoteīranch and choose to create a local tracking branch. Throw away remote branches that do not exist on the remote anymore.Īfter cloning a repository you do not need to configure all remote branches manually. There are two buttons on this dialog: Prune remote branches If youĬonfigure this correctly you will not need to choose a branch when you pull or push. In the Default pull behaviour tab you can configure the branches that need to be pulled and merged by default. How to create a private key file is described Git Extensions will load the key when needed. If you use PuTTY as SSH client you can also enter the The default name after cloning a remote is origin. You can rename each remote forĮasy recognition. When you cloned your repository from a public repository, this remote is already configured. You can manage the remote repositories in the Remotes menu.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |