Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't import private key in the new OpenSSH format #79

Open
mrj opened this issue May 1, 2015 · 2 comments
Open

Can't import private key in the new OpenSSH format #79

mrj opened this issue May 1, 2015 · 2 comments
Assignees
Labels

Comments

@mrj
Copy link

@mrj mrj commented May 1, 2015

ConnectBot 1.8.4 cannot parse keys created by ssh-keygen with the "-o" option (OpenSSH >= 6.5), which are in the new (more secure) OpenSSH format rather than the PEM format, and have the header

-----BEGIN OPENSSH PRIVATE KEY-----

rather than one like

-----BEGIN RSA PRIVATE KEY-----
@kruton kruton added the feature label May 1, 2015
@kruton kruton self-assigned this May 1, 2015
@Nottt

This comment has been minimized.

Copy link

@Nottt Nottt commented Dec 23, 2019

4 years and this is still a issue. Guess the project is dead

@val-kulkov

This comment has been minimized.

Copy link

@val-kulkov val-kulkov commented Jan 7, 2020

Indeed, ConnectBot stumbles on "-----BEGIN OPENSSH PRIVATE KEY-----". According to "man ssh-keygen", Ed25519 keys always use the new private key format:

     -o      Causes ssh-keygen to save private keys using the new OpenSSH format rather than the more compatible PEM format.
             The new format has increased resistance to brute-force password cracking but is not supported by versions of
             OpenSSH prior to 6.5.  Ed25519 keys always use the new private key format.

Therefore, it is not presently possible to use Ed25519 keys generated by OpenSSH.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.