Support new OpenSSH key format

[cyberduck]

398c125 created the issue

More recent OpenSSH version are using a new OpenSSH key format (see http://www.tedunangst.com/flak/post/new-openssh-key-format-and-bcrypt-pbkdf) - Cyberduck currently does not understand that version and comes back with

Exhausted available authentication methods. Unrecognised object: OPENSSH PRIVATE KEY.

[cyberduck]

5586502 commented

Hi DrWhoZee,

I didn't see your ticket before I opened #8553. Your link talks about ecdsa and ed25519 keys. According to https://stribika.github.io/2015/01/04/secure-secure-shell.html, only the latter is really secure. In case you want support for ed25519 keys, my ticket is a duplicate of yours. If you want ecdsa, you might want to change your mind about that ;-)

[cyberduck]

398c125 commented

No, this is not about ecdsa, this ticket is about the new OpenSSH private key format - the link just serves as the reference to the new format.

[cyberduck]

aeeef44 commented

Support for ed25519 keys (#8553) must require this issue because newly generated ed25519 keys are only in new OpenSSH format.

I receive

Login failed. Exhausted available authentication methods. Unrecognised object: OPENSSH PRIVATE KEY. Please contact your web hosting service provider for assistance.

error in nighly duck cli or OS X Version 4.8.4 (19355)

[cyberduck]

@dkocher commented

#9440 closed as duplicate.

[cyberduck]

@dkocher commented

Milestone renamed

[cyberduck]

@dkocher commented

Ticket retargeted after milestone closed

[cyberduck]

@dkocher commented

In 6e347be.