ed25519 private keys are not supported.

[mmaguigan]

Please consider adding support for ed25519 private keys.

[jestemkojak]

I would also recommend ecdsa-sha2-nistp256 which is a default for ubuntu servers.
Here's a list of what type of keys openssh client supports. It would be nice to have them all:

• ssh-rsa
• ssh-dss
• ssh-ed25519
• ecdsa-sha2-nistp256
• ecdsa-sha2-nistp384
• ecdsa-sha2-nistp521
• ssh-rsa-cert-v01@openssh.com
• ssh-dss-cert-v01@openssh.com
• ecdsa-sha2-nistp256-cert-v01@openssh.com
• ecdsa-sha2-nistp384-cert-v01@openssh.com
• ecdsa-sha2-nistp521-cert-v01@openssh.com
• ssh-rsa-cert-v00@openssh.com
• ssh-dss-cert-v00@openssh.com
• ssh-ed25519-cert-v01@openssh.com

[wskinner]

This issue is over a year old. Are there any plans to support modern ciphers and macs in SSH.NET?

[VinsonY]

Does anyone know of a way to simply add ecdsa-sha2-nistp256 to the key exchange algorithm manually? I'm trying to connect to an SFTP site and it is telling me:

No suitable authentication method found to complete authentication (publickey,keyboard-interactive).

[sveeke]

I get the same errors. ed25519 keys can't be used. This is actually a dealbreaker since more and more defaults and policies are moving away from RSA in favour of ecdsa and ed25519.

[darinkes]

I would also recommend ecdsa-sha2-nistp256 which is a default for ubuntu servers.
Here's a list of what type of keys openssh client supports. It would be nice to have them all:

* ssh-rsa

* ssh-dss

* ssh-ed25519

* ecdsa-sha2-nistp256

* ecdsa-sha2-nistp384

* ecdsa-sha2-nistp521

* [ssh-rsa-cert-v01@openssh.com](mailto:ssh-rsa-cert-v01@openssh.com)

* [ssh-dss-cert-v01@openssh.com](mailto:ssh-dss-cert-v01@openssh.com)

* [ecdsa-sha2-nistp256-cert-v01@openssh.com](mailto:ecdsa-sha2-nistp256-cert-v01@openssh.com)

* [ecdsa-sha2-nistp384-cert-v01@openssh.com](mailto:ecdsa-sha2-nistp384-cert-v01@openssh.com)

* [ecdsa-sha2-nistp521-cert-v01@openssh.com](mailto:ecdsa-sha2-nistp521-cert-v01@openssh.com)

* [ssh-rsa-cert-v00@openssh.com](mailto:ssh-rsa-cert-v00@openssh.com)

* [ssh-dss-cert-v00@openssh.com](mailto:ssh-dss-cert-v00@openssh.com)

* [ssh-ed25519-cert-v01@openssh.com](mailto:ssh-ed25519-cert-v01@openssh.com)

FYI, I'm working now on this PR #489 to be able to use ECDSA (no ed25519).
Real World Tests would be highly appreciated.

These Keys already work with this diff:

• ecdsa-sha2-nistp256
• ecdsa-sha2-nistp384
• ecdsa-sha2-nistp521

But I also want to take a look if these can be added accordingly:

• ecdsa-sha2-nistp256-cert-v01@openssh.com
• ecdsa-sha2-nistp384-cert-v01@openssh.com
• ecdsa-sha2-nistp521-cert-v01@openssh.com

[darinkes]

Just a short update, cause of interest and need I spend now some time to update SSH.NET in this area:

There are now working (at least on my machine ;)) Diffs for:

• ECDSA (ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521) Host- and Private-Keys
  WIP: Add Support for ECDSA Host- and Private-Keys #489

• Support for Ed25519 Host- and Private-Keys
  (which is currently just missing crypted OPENSSH-Keyformat support)
  WIP: Support for Ed25519 Host- and Private-Keys #492

• WIP Support for EC KEX (curve25519-sha256, curve25519-sha256@libssh.org, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521)
  https://github.com/darinkes/SSH.NET-1/tree/ec_kex

If anybody wants to help and/or test those Diffs, it would be highly appreciated.

@darinkes repos are now deleted - does anyone have the code?

[darinkes]

@voltagex it just moved => #496

[drieseng]

@darinkes' changes have landed in the develop branch, and will be part of the next release.