CODEWITHSUNDEEP
sshkey
Jeff Faraci
Jeff Faraci

Reputation: 413

Access denied for `none'...ssh error on Windows

Hi I am trying to connect to a server using x2go client. I filled everything out under session preferences.

I am trying to use a RSA/DSA key for ssh connection.

I first made a key in terminal and then tried to use that in x2go but I get the error message

"access denied for `none'. Authentication that can continue : publickey"

I then tried to convert the private key into a public key using PuttyGen. However this public key still gives me same error message when I use it in x2go.

Lastly, I tried to generate a new public and private key using PuttyGen. I'm able to generate the new keys but when I use it in x2go, I still get the same error message

"access denied for `none'. Authentication that can continue : publickey"

Thus, using private keys or public keys, I am still getting this same error message it seems.

What am I doing wrong and how can I fix this error? Thanks

Upvotes: 0

Views: 4607

Answers (3)

Ed Greenberg
Ed Greenberg

Reputation: 269

I just went through this today and noticed something interesting. The environment was:

  • Server
    • Centos 7
    • Open SSH
    • Mariadb 10.3
  • Client
    • Windows 10
    • OpenSSH as provided by git-bash
    • Private/Public key pair created with ssh-keygen (Works elsewhere)

When I got the "none" error, I would always click "cancel". Finally, I realized that it was telling me that public key was one of the authentications that could continue. Instead of hitting cancel, I hit the other button (I don't have the window open now). It then asked me for the private key passphrase and continued to successfully log in. Since the public key passphrase was saved in the vault, I'm not able to reproduce it.

So please try this response: Don't click cancel, just click through and see what happens.

Best, Ed Greenberg

Upvotes: 0

Tim Strawbridge
Tim Strawbridge

Reputation: 655

One issue that I have experienced with this is my key had a passphrase on it. I solved the problem by removing the passphrase.

Inside a terminal window:

ssh-keygen -p
  1. Type in the name of the key you want to change
  2. Enter the old passphrase
  3. Enter the new passphrase
  4. Enter the new passphrase again

Upvotes: 3

VonC
VonC

Reputation: 1324228

Try using openssh instead (install the OpenSSH client for Windows 10)

Then type:

ssh-keygen -m PEM -P "" -t rsa

That should create a %USERPROFILE%\.ssh\id_rsa(.pub) key file pair (private/public)

Copy the id_rsa.pub public key to your remote server, adding it to ~remoteUSer/.ssh/authorized_keys

Then an SSH would work.

ssh remoteUSer@remoteServer

Upvotes: 3

Related Questions