Support ED25519 OpenSSH standard formats
See original GitHub issueSo I tried to use this app to connect to my linux servers with SSH. I have been using ED25519 key for years without issues.
To my surprise this app doesn’t support the standard formats.
It would be nice if you could support .ppk
ED25519 keys from putty. They look like this:
---- BEGIN SSH2 PUBLIC KEY ----
Comment: "ed25519-key-20191223"
AAAAC3NzaC1lZDI1NTE5AAAAIEtoKz1DY+4+wfOKRkcdk6yFiCcCOiGholHqxzBM
DhfE
---- END SSH2 PUBLIC KEY ----
The app won’t even import this…so let’s try exporting the key as OpenSSH right?
-----BEGIN OPENSSH PRIVATE KEY-----
b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAAAMwAAAAtz
c2gtZWQyNTUxOQAAACBLaCs9Q2PuPsHzikZHHZOshYgnAjohoaJR6scwTA4XxAAA
AKCDeUcig3lHIgAAAAtzc2gtZWQyNTUxOQAAACBLaCs9Q2PuPsHzikZHHZOshYgn
AjohoaJR6scwTA4XxAAAAEAi+rcNDSHqnYCNEytLOGV7aEjjiOikHiZCkXnsVzxm
EktoKz1DY+4+wfOKRkcdk6yFiCcCOiGholHqxzBMDhfEAAAAFGVkMjU1MTkta2V5
LTIwMTkxMjIzAQIDBAUGBwgJ
-----END OPENSSH PRIVATE KEY-----
Also doesn’t work…so let’s try using the public key as we use in your linux servers right?
Also doesn’t work! So I had to create a key using the app to see what the format it was using…and turns out you need to remove ed25519-key-XXXX
from the end of the file for it to load.
Can we please adhere to the standards? For people like me who keeps the keys on the cloud, and want to use the same file everywhere it won’t work
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
I’m glad your problem is solved.
I gave up on connectbot and moved to Termius.
It was just too much complicated. With Termius I was able to download the app, import my putty .ppk key from google drive and connect to my server in 5 minutes…