Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
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!
Related posts
- Unix sockets + WSL2 win store
- If you want to use Yubikey from WSL2 (socat passthrough), install gpg4win 3.1.16, NOT the latest (4.0) one
- SSH Agent Restriction (new in OpenSSH 8.9)
- How to use Windows ssh-agent on a WSL2 distribution to avoid entering SSH key passphrases?
- Ask HN: Hosting a CLI Tool via SSH?