Bad Passphrase Try Again for Root Ssh

wrong passphrase putty

Posted past Spankalish

When trying to connect to my Ubuntu machine via ssh with putty from a Windows machine I am getting a wrong passphrase error.

Things I have tried:

Transferred and inverse the individual key with Puttygen after creating them in Ubuntu and loaded that into putty.

Created both keys with Puttygen and transferred the public primal to my Linux car.

Edited the public key to just have ssh-rsa Central... Host@Machine

All of the above has been unsuccessful.

I had it working before for another user on the same auto, but I take since removed that ssh, locked downwardly the users profile so the terminal does not work and created the ssh account in a different contour. I don't know if that has messed this upward?

Whatever assistance would exist much appreciated.

Spankalish

check Best Answer

pigdog

check Best Answer

When prompted for the passphrase, are you entering anything?

If you lot told ssh-keygen to use a passphrase, you demand to provide it now.

If you don't know the passphrase, you have to start over with ssh-keygen, AFAIK.

When prompted for a passphrase in ssh-keygen, printing RETURN.

View Best Answer in replies below

13 Replies

passphrase, password or SSH key? Yous seem to be asking about all three.

Are you logging on as root?
This is the fault I get when I attempt ssh my Ubuntu auto using putty on windows

I'yard logging in to a administrator profile, but non equally root
Brian137185 wrote:

[...]

Edited the public fundamental to just have ssh-rsa Central... Host@Machine

[...]

What do you mean by that? Also, when y'all say yous transferred the public key to the server, what did you practise?

The public key should go into the "authorized_keys" file on the server you're trying to connect to. That file is a long list of all public keys that are immune to connect, so don't just overwrite information technology. Add your public key to the terminate of that file.
I read that putty does not except the open up ssh format for public keys, so you have to edit it, I didn't have to do that before and it could be wrong. I tried it and it didn't alter anything. Going by the putty log file it says the public fundamental is accepted, so I don't think the public primal is the problem
So did you put the public primal into the "authorized_keys" file on the server you lot're connecting to? And what permissions are set for that file and the binder that the "authorized_keys" file is in?
yeah I have information technology in authorized_keys

The authorized_keys is 600 and the .ssh is 700
check Best Answer

When prompted for the passphrase, are you lot entering annihilation?

If yous told ssh-keygen to utilise a passphrase, you need to provide information technology now.

If you don't know the passphrase, you lot have to start over with ssh-keygen, AFAIK.

When prompted for a passphrase in ssh-keygen, press Render.
Brian137185 wrote:

yeah I take it in authorized_keys

The authorized_keys is 600 and the .ssh is 700

OK, that all looks in order.
pigdog wrote:
When prompted for the passphrase, are yous entering annihilation?
If you lot told ssh-keygen to use a passphrase, you need to provide information technology now.

If yous don't know the passphrase, you have to beginning over with ssh-keygen, AFAIK.

When prompted for a passphrase in ssh-keygen, press RETURN.

Expert thinking, that'south probably it.
That sounds like it could exist what information technology was, but at present information technology'due south just plain refusing the key. Saying in that location is no supported authentication method available, which is new. No idea why this is happening.
Likewise the public key file which is authorized_keys is locked
Sorted. I created the authorized_keys via sudo nano. (only so used to editing root files) So ssh couldn't use it. rookie mistake.

And information technology was just looking for the password like pigdog said.

thank you guys. I knew the spiceheads could solve it :)
Try

ssh -v -v host

to see some details.

Assuming yous've remade keys, revisit Oliver's suggestion to check file permission, but likewise expect at file/directory ownership.

Check the logs (I don't know where they are on Ubuntu) after your ssh effort fails.

Read these next...

The SOC Briefing for May 13th - We are dorsum!
Security
Good morning and welcome to today's briefing. I am starting this back, ordinarily will try to mail service by and large Fridays on this as much as I can. As unremarkably this post bring various posts regarding Patches & Updates plus Security News and a bonus Security Tip! Hope...
Snap! Cybersecurity & the boardroom, Cooper, Starlink sabbatum cyberspace, & Sgr A*
Spiceworks Originals
Your daily dose of tech news, in brief. Not only is information technology Friday, merely information technology is also Friday the 13th! A twenty-four hours that has inspired a late 19th-century secret society, an early on 20th-century novel, a horror film franchise, and triskaidekaphobia, a word I had to...
Dell Server Eating Ability Supplies
Hardware
I have a Dell PowerEdge 750 that's been quietly running our old accounting software to network users for at to the lowest degree xv years. The server began powering off intermittently, and so I picked upwardly a refurbished power supply as a replacement. It ran for 3 days and fai...
IE11 retires in 1 calendar month on June xv, 2022
Windows
Received this reminder email from MS this morn. I won't exist sad to finally see this go, even though I know I accept a few hold outs who insist on clicking on that Due east however (more often than not out of habit)Is everyone Ready for the big day?-----------------------------...
Spark! Pro Serial - May 13th, 2022
Spiceworks Originals
To my fellow left-handers, Happy Friday the 13th. While the right-handed bulk quakes in fearfulness and wallows in superstition, a malady known as friggatriskaidekaphobia, nosotros celebrate the mean solar day that promises health, wea...