VS Code Version: 1.25.0
Commit: 0f080e5267e829de46638128001aeb7ca2d6d50e
Date: 2018-07-05T13:11:58.697Z
Electron: 1.7.12
Chrome: 58.0.3029.110
Node.js: 7.9.0
V8: 5.8.283.38
Architecture: x64
Git Version 2.18.0.windows.1 @ C:\Program Files\Git\cmd\git.exe
I keep getting this error when trying to push to GitHub from VS Code's menu. Git: [email protected]: Permission denied (publickey). I have installed Git-Credential-Manager, but am unsure of how to set it up. I also have OpenSSH (OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4) that comes with Windows 10 (Extra Features). It has ssh-add and ssh-agent. I was wondering if that can be used to authenticate my private key (password protected) to set up VS Code.
Guidance would be really appreciated!
Thanks!
@blackbird-98 Git Credential Manager is for authenticating to HTTPS remotes only. I'd recommend looking at the GitHub guides for setting up SSH: https://help.github.com/articles/connecting-to-github-with-ssh/ and in particular Working with SSH key passphrases.
Yes, I have that working, but was wondering how to use this extension with OpenSSL as they are integrated into windows. I believe it would be much easier using this (as OpenSSL services run by default in the background and seem well integrated) as opposed to making code get the env-vars of Git-bash by running code from it. This would make it much easier to manage remotes and repos with native windows tools.
Thank you!
was wondering how to use this extension with OpenSSL as they are integrated into windows.
OpenSSL != OpenSSH. Very different beasts.
@blackbird-98
I believe it would be much easier using this (as OpenSSL services run by default in the background and seem well integrated) as opposed to making code get the env-vars of Git-bash by running code from it.
I'll point you to #25 which was an earlier request for this and in particular this comment https://github.com/Microsoft/Git-Credential-Manager-for-Windows/issues/25#issuecomment-208755973 about why it's currently out of scope for GCM to be handling passphrases for SSH keys.
@dscho Whoops! Apologies!
@shiftkey okay! understood. Makes sense...
Thank you all for your time!