![]() The -i option will automatically add it to the SSH agent for you. Tower allows to assign a Private Key file per remote connection - in a very convenient way: Tower will pass the key file as -i KEYFILE to the ssh command. If you are already using SSH keys for authentication, there is nothing to configure - as long as your key is added to the local SSH agent. The remote URL needs to contain the username, since connection information is derived from the URL: with SSH Keys an ssh-agent or the Git Credential Manager for Windows. If the connection requires username and password, Tower will store a combination of password and remote URL in it's credential manager if it isn't provided by other means, e.g. Authenticating with Username and Password Both pieces of information are displayed when starting the SSH agent. ![]() For both cases, please activate the "Use local SSH settings" flag in Tower's preferences.įor Plink the environment variable "GIT_SSH" needs to point to the "plink.exe".įor an existing SSH agent, the environment variable "SSH_AGENT_PID" needs to point to a process id, and the variable "SSH_AUTH_SOCK" must hold the authentication socket. Tower can support using Plink or an already running SSH agent. If, on the other hand, a connection requires user interaction, you have to configure the remote connection in Tower once.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |