on unix it seems the "git@" notation part of the git clone command isn't needed, but I'm hearing from other people on windows7 that they need to add this username part when doing clones via putty...
when using git (1.9.4.msysgit.2) on windows, and using plink (0.63) for ssh transport, then it's plink who needs a username, as opposed to openssh.
One way around this is to change the putty “Default Settings”:
• Connection > Data : “Use system username”
• Connection > SSH > Auth : “Private Key file for authentication” (if you don't want to use pageant)
Be sure to save this in Putty, and plink will use those defaults.
That make the git clone via plink work for me again without having to specify “git@” in the URL.
The validation is done through the access key. This has been answered by one of our developers on the question below:
See the example below:
$ git push ssh://userDoesntMatter@localhost:7999/test/repotest3.git ... To ssh://userDoesntMatter@localhost:7999/test/repotest3.git 4d15880..da015bb master -> master
In order to enable SSH, please follow all the steps outlined in the document below:
I hope that it clarifies your question.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot