![]() ![]() So I made absolutely sure that I use the admin user in the remote URL - same problem. YES I CAN git clone, push, pull with users from command line, and I can also ssh to the server, although only with admin users (seems to be Synology's new standard). Event this post was no help - what am I doing wrong here? So I tried by generating a new key via GitKraken and installing it as described here, but nothing changed. I could clone and push elements via command prompt, no problem with git clone can clone/commit/pull via command prompt but when I do it via GitKraken, I get a "Configured SSH key is invalid" error. It is one-time-per-remote-login procedure anyway.I'm trying use GitKraken with my existing git repository hosted on a Synology NAS (web-managed, if this can make a difference). 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 |