![]() ![]() ![]() Without Pagent you can only use one key at a time and change the settings when you need to change keys. In Windows if you aren't using Pagent (from PuTTY) then you shouldn't select "use local agent" in GitKraken. switch these from to these steps are done then you can start changing GitKraken's ssh settings. This will open a sub-window that that will have two text boxes you can edit. Click options and select "Edit Origin".Hovering over this item reveals a vertical ".", that is the options button. With the remote group expanded you should see a source called Origin.This panel may be hidden, if so you'll need to click the right facing arrow symbol that should appear under the folder icon in the top left. In the left panel expand the remote group (represented by a cloud).Luckily you can do this inside GitKraken.įirst you should navigate to your repo in GitKraken. You will first have to change the URL for your remote. If the repo was cloned with HTTPS then no changes to SSH settings will work. When I do a pull I'm always prompted to insert the username and pass (even though I started the ssh-agent process from the git-bash).ĭon't know how I can solve this so any help you guys can provide will be much appreciated.Īlso, can't find a single way in app or online to remove/delete a repository from the app (I hope it's not obvious and I'm making a fool of myself).gitkraken and changed the paths for the ssh keys to: "useLocalAgent": true, "privateKey": "C:\Users\mendo\.ssh\id_rsa", "publicKey": "C:\Users\mendo\.ssh\id_rsa.pub". Have messed around with the profile inside.Added the public one to my gitlab profile and can "ssh -T successfully. I'm running Windows 10 with git-bash and have followed the tutorial on Github to generate the keys and add them to the ssh-agent. I believe the repo from Gitlab was added with https, can't find a way to change this, don't know if it's important. Configuration options / tutorials for this issue are scarce/nonexistant. It is one-time-per-remote-login procedure anyway.I've been having a hard time getting the auth to work with ssh keys (don't want to be prompted for user and pass every time). I can speculate that this prevents adding your public key (which is paired with encrypted private key) without knowing encryption password for corresponding private key. Remote SSH login password would be enough in this case. # NOTE: No password for private key anymore.Ĭonfusing enough. # Why? Isn't the private key is already loaded by `ssh-add`? # (and only then prompt for remote login). # NOTE: See password prompt for private key # Enter passphrase for key '/home/uvsmtid/.ssh/id_rsa': # Identity added: /home/uvsmtid/.ssh/id_rsa (/home/uvsmtid/.ssh/id_rsa) # Enter passphrase for /home/uvsmtid/.ssh/id_rsa: To reproduce: # We are about to ssh to localhost, therefore, unauthorized everyone. You will still get password prompt to decrypt private key even if it is loaded into ssh-agent until the corresponding SSH public key is added into remote ~/.ssh/authorized_keys. If it asks for it, there is a reason for that and it's basically required. ![]() You can try to bypass asking for the passphrase (which will redirect it into true), but I don't think it'll help. Re-run git via: GIT_TRACE=1 git pull or with GIT_SSH_COMMAND="ssh -vv" (Git 2.3.0+) to debug your command again.Double check your SSH agent is running ( eval "$(ssh-agent -s)").Install -vm700 <(echo "echo $PS") $PWD/my_passĭISPLAY= SSH_ASKPASS=$PWD/my_pass ssh-add - & rm -v my_pass If you know passphrase and you want to automate it, try the following workaround: PS="my_passphrase" Run ssh-add -l to list all your identities (then compare with your local) and double check with Stash if you're using the right keys (they exists on Stash configuration).If you'd like to use different key, specify other file or edit your ~/.ssh/config and specify different identity file ( IdentityFile). If it's encrypted you can try to remove the encryption.ZAzLq/LbHSfOVkXtQz6M6U8yuAx2lIu9bH/k7ksgat92IDjZntRrT1XMpkYtjB+0 The main reason for passphrase asking is that your key is encrypted, compare these two:ĪIIAogIBAAKCAQEAtOJQ0Z3ZbyzuknnHqn5oMCmNf8zGmERhW+g5Eftf9daZ5qvZĭEK-Info: AES-128-CBC,A95215C9E9FE00B8D73C58BE005DAD82 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |