Closed Sebazzz closed 1 year ago
I was able to "resolve" this by doing it a completely different way:
wsl-ssh-pageant-amd64-gui.exe -systray -winssh ssh-pageant
SSH_AUTH_SOCK
environment variable to \\.\pipe\ssh-pageant
I also tried this guide, which directly links OpenSSH to the Yubico library as well, but that didn't work either:
debug1: provider libykcs11.dll: manufacturerID <Yubico (www.yubico.com)> cryptokiVersion 2.40 libraryDescription <PKCS#11 PIV Library (SP-800-73)> libraryVersion 2.11
debug1: provider libykcs11.dll slot 0: label <YubiKey PIV #10146553> manufacturerID <Yubico (www.yubico.com)> model <YubiKey YK5> serial <10146553> flags 0x40d
debug1: have 1 keys
[...]
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: libykcs11.dll RSA SHA256:Xk7dUop5/qjwucmsUduwTtG9hgBmOE/jD3UJh+wqlVY token
debug1: Will attempt key: C:\\Users\\sebas/.ssh/id_rsa RSA SHA256:Cupj8urw603kxU7xN92kmKKbfpOIyBqAT7w0dNY0WYE
debug1: Will attempt key: C:\\Users\\sebas/.ssh/id_dsa
debug1: Will attempt key: C:\\Users\\sebas/.ssh/id_ecdsa
[...]
debug1: Authentications that can continue: publickey
debug1: Offering public key: C:\\Users\\sebas/.ssh/id_rsa RSA SHA256:Cupj8urw603kxU7xN92kmKKbfpOIyBqAT7w0dNY0WYE
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: C:\\Users\\sebas/.ssh/id_rsa RSA SHA256:Cupj8urw603kxU7xN92kmKKbfpOIyBqAT7w0dNY0WYE
debug3: sign_and_send_pubkey: RSA SHA256:Cupj8urw603kxU7xN92kmKKbfpOIyBqAT7w0dNY0WYE
debug3: sign_and_send_pubkey: signing using rsa-sha2-512
debug3: no such identity: C:\\Users\\sebas/.ssh/id_rsa: No such file or directory
debug1: pkcs11_k11_free: parent 000001D789DF91B0 ptr 0000000000000000 idx 0
debug1: Trying private key: C:\\Users\\sebas/.ssh/id_dsa
debug3: no such identity: C:\\Users\\sebas/.ssh/id_dsa: No such file or directory
Still, I'm happy to know any insights why the method described in this Github repository does not work anymore.
@Sebazzz I'm not a Windows user; can you take another look at the guide and recommend any improvements to the Windows or troubleshooting sections, or even better, send a PR with the same?
@Sebazzz wondering if you could take another look at your convenience and help us out.
Resolving to inactivity. Sorry Windows users.
Previously I had SSH public key authentication operational but at some point it stopped working and I have not been able to get it working anymore. Please note that git commit signing works properly.
GPG shows the keys properly:
Windows service ssh-agent is running. GPG connect agent is running. My
%USERPROFILE%/.ssh/id_rsa.pub
contains my key:scdaemon.conf contains my Yubikey device name as shown in device manager:
gpg-agent.conf contains:
My
.ssh/config
file is empty.When connecting to SSH (for instance my local Home Assistant instance - but it happens with any SSH host):
Full output: ssh-connect-output.log
The only thing I see is when I run ssh-add - but perhaps this is a red herring:
I can't figure it out. Everything seems like it should be - but I can't get it to work.
Anyone have any idea?