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

ed25519 support #325

Closed
flokli opened this Issue May 11, 2014 · 12 comments

Comments

Projects
None yet
10 participants
@flokli

flokli commented May 11, 2014

It seems like logging in with an ed25519 keypair is not supported in paramiko.

paramiko/client does not look for id_ed25519, and there's also no
ed25519key.py file implementing the algorithm. Probaby this or this could be a good start...

@alekibango

This comment has been minimized.

alekibango commented Jan 30, 2015

ed25519 would be really good key type to support!
It is more efficient and maybe also more secure than rsa.

@bitprophet

This comment has been minimized.

Member

bitprophet commented Feb 4, 2015

This is probably related to other stuff marked 'Keys', adding it there on the slim chance other existing tickets don't mention this specific one.

@bitprophet bitprophet added the Keys label Feb 4, 2015

@xchs

This comment has been minimized.

xchs commented May 8, 2015

+1

@alex

This comment has been minimized.

Contributor

alex commented Nov 1, 2015

FWIW, the pynacl package has all the crypto you'd need for this. Happy to review.

@bitprophet

This comment has been minimized.

Member

bitprophet commented Nov 2, 2015

#67 (comment) (a recently left comment on a not really related much older ticket) is probably symptomatic of this lack of feature support.

@mchlt

This comment has been minimized.

mchlt commented Nov 7, 2015

Per man ssh-keygen:

-o Causes ssh-keygen to save SSH protocol 2 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.

So to support the Ed25519 keys, paramiko first needs to support the new OpenSSH private key format. See #602.

@eworm-de

This comment has been minimized.

eworm-de commented Nov 9, 2015

I've converted all my keys to SSH protocol 2 private key format and it works with mysql-workbench / paramiko. Possibly this is because of gpg-agent caching the keys, but it works.

@n0ts

This comment has been minimized.

n0ts commented Sep 28, 2016

Do you have a plan support ssh key type ed25519?

@thedotedge

This comment has been minimized.

thedotedge commented Oct 7, 2016

👍

@bitprophet

This comment has been minimized.

Member

bitprophet commented Oct 10, 2016

@n0ts Still waiting on someone to submit a PR for it, but we do want to support it.

Relatedly, #602 is about some groundwork for this, which in turn kinda wanted bcrypt support in Cryptography - which is now out, so that's one less blocker.

@alex

This comment has been minimized.

Contributor

alex commented Oct 10, 2016

To be clear, we don't have bcrypt in cryptography, we have
bcrypt_pbkdf in bcrypt :-)

On Mon, Oct 10, 2016 at 12:37 PM, Jeff Forcier notifications@github.com
wrote:

@n0ts https://github.com/n0ts Still waiting on someone to submit a PR
for it, but we do want to support it.

Relatedly, #602 #602 is
about some groundwork for this, which in turn kinda wanted bcrypt support
in Cryptography - which is now out, so that's one less blocker.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#325 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAADBNhD0gixq8y3DMOv1Te3shKmiBv6ks5qymmugaJpZM4B55WL
.

"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6

@daniel-ziegler

This comment has been minimized.

daniel-ziegler commented Feb 10, 2017

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment