-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
change ssh private key default to ed25519 before checking for rsa #384
Comments
My proposal would be to try a couple of defaults and what ever is there will be used. With this given order:
Anything else that folks are using that is not mentioned in the list above? |
This also got me thinking about something else. What happens when keys are password protected (or more recently require a security key to unlock). Wouldn't it just be better to delegate all of this to |
those are very valid points. I'll toy around with them in order to understand the behaviour in cases there no But I guess we can extend the scope of this issue to support also arbitrary protected private keys, not only elliptic curve keys. |
Currently, only RSA keys are supported:
cargo-generate/src/git.rs
Line 119 in 528bf38
However, more and more people are defaulting to
ed25519
(myself included). Having to setup arsa
key just forcargo-generate
is not ideal.cargo-generate
should at least supported25519
keys as well.Edit: I realize I could manually override this via
-i | --identity
, but my request is to make it automatically useid_ed25519
if it exists.The text was updated successfully, but these errors were encountered: