![]() With these all set up, one can start a Julia session and add the package. SSH_PUB_KEY_PATH = C:\\Users/zpan\\.ssh\\id_rsa.pub SSH_PUB_KEY_PATH = C:/Users/zpan/.ssh/id_rsa.pubĪlternatively, these also work: SSH_KEY_PATH = C:\\Users\\zpan\\.ssh\\id_rsa (2) Create two system environmental variables: SSH_KEY_PATH = C:/Users/zpan/.ssh/id_rsa Ssh-keygen -t rsa -m PEM -C the public key submitted to the private git server with the new key. (1) Regenerate the SSH key using the “-m PEM” option. I cannot use https or any other protocol.Īnybody had similar problem? Did I miss something, or is it a Thank you for pointing me to the thread! After trying various combinations suggested by the replies and having a little “aha” moment of my own, I found the following workaround for Windows 10 with Julia 1.3.1: Unfortunately SSH authentication is the only authentication method our Bitbucket server is set up to support. If not, my other git operations would have failed.Īnd it’s not because the location cannot be found - the error message would be different if it had been the case. I double-checked that the private key location is correct, and the associated public key had been submitted to the Bitbucket server. Private key location for :ĮRROR: failed to clone from error: GitError(Code:ERROR, Class:SSH, Failed to authenticate SSH session: Unable to send userauth-publickey request) (v1.3) pkg> add git-repo key location for : ![]() However, when I tried to add the package in my Julia pacakge manager, this error happened: julia> ![]() Since I had already created SSH keys at my Git for Windows client (Git Bash), and I had provided the public key to the Bitbucket server, I was able to clone / push / pull using my Git Bash or any GUI (Atom, Sublime Merge) without any problem. We have a Julia package hosted on our company’s private Bitbucket server. I am not sure if this is a bug or I’m doing something wrong…
0 Comments
Leave a Reply. |