Platform: Windows 10
I am working my way through the article Set Up An SSH Key. I got to the point where the user is advised to enter
ssh -T email@example.com
I get Permission Denied. The article then advises:
If you get an error message with
Permission denied (publickey), check the Set up an SSH key page for help.
In other words, the article refers you to itself! To put it mildly, this is NOT HELPFUL. Can anyone advise on what to do at this point, other than enter an infinite loop.
Yes, that is pretty rubbish, as the article doesn't tell you how to fix it.
The error usually means the server doesn't like your key, although it can sometimes mean the file the key is in is not secured properly and ssh doesn't like that either.
It's hard to tell what might be wrong with this, so we'd like more info. Could you try
ssh -v -T firstname.lastname@example.org
That should be more wordy, most of which you don't need, but when it fails it should tell you why near the point of failure.
I actually fixed the problem by re-generating the keys and accepting all the defaults. This generates keys named id_rsa and id_rsa.pub. I also named my Bitbucket key id_rsa. Of course, this is computing by trail-and-error in that it is unclear why providing a non-default name caused a failure and why accepting the default name worked. If only the default name works then the user should not be provided the opportunity to supply a non-default name.
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