Blink: ssh-add can not load ec keys

[TypedLambda]

The ssh-add command fails to load ecdsa and ed25519 keys. RSA and DSA keys work fine.

ssh-add test2

Error loading key "test2": invalid format

[yury]

Update:
ed25519 keys are working if the generated with ssh-keygen or copied to ~/.ssh/
ed25519 is not working with libssh exported keys (blink config -> keys)

[martinpaljak]

Can't there be a simple "also store in .ssh" option for the visual UI config ?

[yury]

@martinpaljak we prefer not to store keys in file system but store it in Secure Enclave.

[martinpaljak]

Me too, but I understand that none of the "small" keys (read: ec, especially the ones which could be agent-capable) can be stored there?

[yury]

All ecdsa will work in next release. Only remaining issue with ed25519. I reported to libssh team. Hope they fix it soon.

[martinpaljak]

Cool! Are those keys then kept in the secure enclave? Will it be possible to run ssh-agent without fiddling with a second terminal?

[yury]

For ssh-agent forwarding you still need to run ssh-agent in the tab for now

[martinpaljak]

(elliptic) keys kept in the secure enclave (like sekey) + fingerprint and/or PIN activation of those keys + ssh-agent forwarding via a simple checkbox in config

These are the features I hope blink will get, which would make it a real powertool

[yury]

Ok, ed25519 fix landed in libssh.

Waiting for release

[yury]

v12.7 released. Should be ok there.

[mcg]

Still have "invalid format" trying to add a ed25519 key to ssh-agent. Should this be fixed?

[yury]

@mcg sorry, I messed up with libssh update. Turns out that fix didn't make to release. We have to wait.

Sorry for false alarm :(

[yury]

Ok, @mcg.

Sorry again :) but I was to fast to response. It actually should work in v12.7. One note though.
You have to reimport key in keys. Actuall bug was in internal export.

[mcg]

Re-imported and it worked great. Thanks!

[yury]

Cool, closing.

Thank you!