Closed
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
When trying to add an ecdsa-sk key to the Windows ssh-agent:
Using the Windows ssh-add (works properly):
PS > & "C:\Program Files\OpenSSH\ssh-add" id_ecdsa_sk
Identity added: id_ecdsa_sk (somu)
From Fedora 35 WSL2 (OpenSSH 8.7p1, via npiperelay, fails):
$ ssh-add -d
Identity removed: /home/abob/.ssh/id_ecdsa_sk ECDSA-SK ((null))
$ ssh-add -l
The agent has no identities.
$ ssh-add id_ecdsa_sk
Could not add identity "id_ecdsa_sk": communication with agent failed
Fedora and KeePassXC are able to add non-U2F/Fido2 keys
If I change the Fedora ssh-add client to not send a skprovider, it works:
$ ./ssh-add -l
The agent has no identities.
$ ./ssh-add ~/.ssh/id_ecdsa_sk
Identity added: /home/abob/.ssh/id_ecdsa_sk (somu)
$ ./ssh-add -l
256 SHA256:8gAXpKjrC+SzxcCkKk6xb6Rk4I+U/FyewnQy2H+zvtA somu (ECDSA-SK)
Expected behavior
SSH key loaded into agent
Actual behavior
Error messages from other ssh agent clients
Error details
No response
Environment data
PS > & "C:\Program Files\OpenSSH\ssh" -V
OpenSSH_for_Windows_8.9p1, LibreSSL 3.4.3
Version
8.9.1.0
Visuals
No response