Terminus: SSH Key Not Working

[smithomaster]

I am on version 1.0.75 on Ubuntu, and whenever I try to connect to my server with my SSH private key, I get the following error:
Connecting to 45.77.239.27
Loading private key from /home/emil/.ssh/id_rsa
SHA256 fingerprint: 246c4c289b674e79ca40586c44faba861e2c3dd9524308b6d1aad0edd25b1187
All configured authentication methods failed

My SSH key is configured in the remote server, why is this coming up? The SSH key is not encrypted.

[smithomaster]

Additionally, I can connect without using an SSH key by using the ssh command in the terminal.

[bes-internal]

It seems Terminus doesnt support new format of openssh keys. Generate keys with ssh-keygen -m PEM (id_rsa should begin with "BEGIN RSA PRIVATE KEY")

[kankaristo]

According to the ssh-keygen man page, that's a _legacy_ format, not a new format (emphasis mine):

−m key_format
Specify a key format for the −i (import) or −e (export) conversion options. The supported key formats are: ’’RFC4716’’ (RFC 4716/SSH2 public or private key), ’’PKCS8’’ (PEM PKCS8 public key) or ’’PEM’’ (PEM public key). The default conversion format is ’’RFC4716’’. Setting a format of ’’PEM’’ when generating or updating a supported private key type will cause the key to be stored in the legacy PEM private key format.

Legacy formats should probably be avoided. I generate my keys with ssh-keygen -t rsa -b 4096

---

EDIT: Sorry, I misread your comment, you weren't actually saying that PEM is a new format. Terminus should support the "new" format (the default for ssh-keygen), it's not that new?

[bes-internal]

I did not carefully read your initial comment. Just double check you can auth with your key:
ssh -v -i /home/emil/.ssh/id_rsa
It looks like you just forgot to add id_rsa.pub to authorized_keys at server

[Clem-]

Sorry but same problem here. Private key generated from PuTTyGen. I tried every export format (ssh.com, new OpenSSH, legacy OpenSSH) but none of these keys are working. Note that everything's working well with PuTTy.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks unless you comment.
Thank you for your contributions.

[bes-internal]

what nonsense? remove this bot. Developer, you didn’t even unsubscribe in this bug. And your bot has already closed it.

[50l3r]

Any news?

[Mee1ad]

same problem

[Hassenky]

Got same issue. Putty private key cannot be used in Terminus. This issue should be solved because in most of the case, windows users just have putty private key generated from keygen. Linux users would never touch Terminus for sure.

[50l3r]

Got same issue. Putty private key cannot be used in Terminus. This issue should be solved because in most of the case, windows users just have putty private key generated from keygen. Linux users would never touch Terminus for sure.

Yeah

even im not able to set a pem key:

Litteraly frustrating

[Hassenky]

Got same issue. Putty private key cannot be used in Terminus. This issue should be solved because in most of the case, windows users just have putty private key generated from keygen. Linux users would never touch Terminus for sure.

Yeah

even im not able to set a pem key:

Litteraly frustrating

I tested this function and saw that Terminus just accepts private keys generated by a Linux system. If you have a linux computer, just generate a key pair (public and private), and then copy the private key to your windows. Copy the public key to the authorized_keys file in the .ssh folder of your remote server. Use the private key with Terminus.

[50l3r]

Got same issue. Putty private key cannot be used in Terminus. This issue should be solved because in most of the case, windows users just have putty private key generated from keygen. Linux users would never touch Terminus for sure.

Yeah
even im not able to set a pem key:

Litteraly frustrating

I tested this function and saw that Terminus just accepts private keys generated by a Linux system. If you have a linux computer, just generate a key pair (public and private), and then copy the private key to your windows. Copy the public key to the authorized_keys file in the .ssh folder of your remote server. Use the private key with Terminus.

I tried with pem file created in linux. This error its appear using a pem file

[Drarox]

Got same issue. Putty private key cannot be used in Terminus. This issue should be solved because in most of the case, windows users just have putty private key generated from keygen. Linux users would never touch Terminus for sure.

Yeah
even im not able to set a pem key:

Litteraly frustrating

I tested this function and saw that Terminus just accepts private keys generated by a Linux system. If you have a linux computer, just generate a key pair (public and private), and then copy the private key to your windows. Copy the public key to the authorized_keys file in the .ssh folder of your remote server. Use the private key with Terminus.

Same issue here, I tried to generate the keys with linux and copy them but same error again, very frustrating...

[lamitron]

I can confirm that this buy still exists, and still frustrates me. I'm using Google Cloud for a VM instance and I love Terminus because of how it looks. However, if the program doesn't function (which it doesn't, developer!) It's functionally useless to me.
Can it be really that hard for someone who has already created an application which seems as polished as this, already with some types of private keys supported, to simply add another?

[Hassenky]

It works for me if I generate keys on a linux machine, then copy them to the windows one.

[fahadysf]

Got same issue. Putty private key cannot be used in Terminus. This issue should be solved because in most of the case, windows users just have putty private key generated from keygen. Linux users would never touch Terminus for sure.

Yeah
even im not able to set a pem key:

Litteraly frustrating

I tested this function and saw that Terminus just accepts private keys generated by a Linux system. If you have a linux computer, just generate a key pair (public and private), and then copy the private key to your windows. Copy the public key to the authorized_keys file in the .ssh folder of your remote server. Use the private key with Terminus.

Same issue here, I tried to generate the keys with linux and copy them but same error again, very frustrating...

I just checked and this is a permissions issue in the temp file which is being generated.

I believe if the proper permissions for windows are set by whatever process is creating that temp file, this should be resolved.

[Eugeny]

@fahadysf are you using v1.0.114 (released yesterday)? It contains additional fixes to key file permissions.

[bepstein111]

Downloaded today, running into same issue. Key works on linux machines ssh'ing to each other. I am using ecdsa not rsa, could that be causing issues?