wsl2-ssh-pageant VS Win32-OpenSSH

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.

A request for an official answer on CALs for Microsofts' SSH port is about to turn 6 years old:

https://github.com/PowerShell/Win32-OpenSSH/issues/926

I have automated some things "normally" on Windows successfully after installing OpenSSH-win32; https://github.com/PowerShell/Win32-OpenSSH/releases

Are there any other ssh clients that support FIDO2 on windows besides Win32-OpenSSH?

If you're on windows, you need openssh 8.9 to use fido for ssh. https://github.com/PowerShell/Win32-OpenSSH/releases/tag/v8.9.1.0p1-Beta

Unlike Linux, Windows does not come with any tools for setting up an SFTP server. Even FileZilla Server, one of the most popular programs for setting up a FTP server, doesn't support SFTP out of the box. So, are there any other ways to set up an SFTP on Windows? Yes, of course. OpenSSH is a suite of programs for establishing secure connections to the server. sftp-server is one of the utility programs provided by OpenSSH, so this article will walk you through how to set up an SFTP server on Windows using OpenSSH. Originally, OpenSSH was only available on Linux, but Microsoft has ported it to Windows, so you can now use OpenSSH by downloading the zip file from here.

It is mentioned in Win32-OpenSSH's scope that it does not support "VPN Forwarding". Is it the same thing as local/remote port forwarding (ssh -L, and ssh -R)? Can I forward port to and from Windows with Win32-OpenSSH installed on both client and server?

So, personally, I haven't been able to get FIDO2 keys to work at all on Windows, but I didn't try very hard because I'm set-up just fine with GPG for SSH. Apparently there have been a few bugs reported (ref, and linked issue.