id_ed25519 support in addition to id_rsa ?

[vjek]

This is an enhancement request.

Could you add support for id_ed25519 private keys in addition to id_rsa private keys? id_rsa private keys work just fine, no issue with that. Happy to keep using that.
However, there are some advantages to ed25519 keys, and it would be great to be able to use them with ssh.k connections.

[BCVerdouw]

From my experience ed25519 is supported, the keyfile just has to be named id_rsa.

[vjek]

Just tried that on Saturday, Jan 16th, and it doesn't work for me. I took an id_ed25519 private key file, renamed it id_rsa, and the connection will not work. Restore the original id_rsa file, and it works again. This id_ed25519 private key file works fine with a normal/typical ssh client, regardless of operating system.

The format of an id_ed25519 private key is different, the headers start with: -----BEGIN OPENSSH PRIVATE KEY----- rather than: -----BEGIN RSA PRIVATE KEY-----

But even manually editing the file to show those RSA headers and footers results in the same failed behavior, for me.

How did you get it to work for you, BCVerdouw?

[BCVerdouw]

I'm trying it through sshfs-win svc, as i had network name not found errors while trying with net use, that might be the difference

[kaplan2539]

@vjek @BCVerdouw I thought my comment to issue 155 might be interesting for you: https://github.com/billziss-gh/sshfs-win/issues/155#issuecomment-777466963

[JBlond]

@vjek For me it works using https://github.com/evsar3/sshfs-win-manager