pass-git-helper VS wsl2-ssh-pageant

And if you'd like to store the token encrypted in password store, there's a helper for that: pass git helper

In my setup use pass-git-helper and it works with both magit and CLI git without any problems

Hey there! So, I've been using WSL2 with a yubikey for gpg, which is pretty sweet. Basically, this setup uses a Unix socket to Windows gpg-agent and pageant (if you're curious, you can find all the details in this GitHub repo: https://github.com/BlackReloaded/wsl2-ssh-pageant). It's been working great for about a month or so, until I recently installed the Windows Store version for WSLg support on Windows 10. But now, my WSL2 isn't talking to the Win gpg-agent anymore. I've searched GitHub for answers, but no luck yet. Figured I'd post here and see if there are others in the same boat or who might have some tips on this pesky socket issue. Thanks!

You should use the latest wsl2-ssh-peagent, which has a new --gpgConfigBasepath option to allow you to specify the .gnupg directory in Windows.

sshCommand = C:/utils/OpenSSH-Win64/ssh.exe

For GPG, the only things I've done is to use gpg-agent and set up a passthrough for gpg-agent to WSL2 for both OpenSSH and GPG via https://github.com/BlackReloaded/wsl2-ssh-pageant/ since I do development both natively on Windows and via WSL2.

Yeah, I've been using a Yubikey for a bit over a year and I'm already a huge fan of the way it works with SSH/Git. It's a bit more of a pain to set up with WSL2 since you need something like https://github.com/BlackReloaded/wsl2-ssh-pageant but it's absolutely worth the setup time.

I use PuTTY's pageant and https://github.com/BlackReloaded/wsl2-ssh-pageant to share keys between environments but you still need to enter your passphrase at power-on. Window's ssh-agent looks like a better solution. No need to re-enter the passphrase and no need to keep the private key around.