Public SSH Key Error

[kikoking1]

When a public SSH key is added to my mac computer, atom commander tries to use it whether I want it to or not through sftp connecting. It says that the encoding is too long, no matter which settings I use in the sftp. I had to remove my public SSH key from my mac to get it to work again. Is there a way to get it not to use the Public SSH key if one is on the computer, or make it so it doesn't error out with the encoding being too long?

[morassman]

Hi @kikoking1

It isn't supposed to try and use the public key if it isn't configured to do so. I took a look at the code, but it isn't obvious how this can be happening. I'll experiment some more to see if I can reproduce this behaviour.

Just to make sure. So even if you choose 'Login with password' instead of 'Login with private key' you still get the error?

[kikoking1]

Yes, I get the same error even if I try to login with the private key and use the passphrase.

[morassman]

That makes sense, but do you get the error if you don't choose 'Login with private key', but choose 'Login with password'?

[kikoking1]

Oh sorry, yes the error happens even if I choose Login with password.

[morassman]

I couldn't reproduce the issue myself, but I think I found it. I just released v0.8.8. Let me know if it fixed the problem.

[kikoking1]

Hey, so it looks like everything is working great now! I did get a weird error when I try to edit, or add a new, sftp account without putting an ssh key (When having one installed on my computer).

but I clicked ok anyway and it stilled logged me in no problem.

It logs me in and test button returns connected successfully when I use the ssh key and passphrase.

[morassman]

Ok great. I'll look into the issue with testing the connection.