1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
+++
title = "WSL2, Yubikey, and You"
description = "A WSL2 YubiKey setup guide."
date = 2022-08-04
updated = 2022-08-24
authors = ["Toby Vincent"]
[extra]
toc = true
+++
## UPDATE 2022-8-24
This is no longer necessary due to
[usbipd-win](https://github.com/dorssel/usbipd-win)
I am now using [usbipd-win](https://github.com/dorssel/usbipd-win) to mount the
yubikey directly into WSL2, and using
[distod](https://github.com/nullpo-head/wsl-distrod) (adds bottled systemd to
wsl) to start services as I normally would in linux
Regardless, I am posting this here for posterity.
## Intro
The following two sections are the result of a painstaking amount of google
searches and GitHub issues followed by troubleshooting, tears, and tea breaks.
Well, more accurately, the 20% came from the aforementioned alliteration. The
80% came from the following two guides.
- [drduh/YubiKey-Guide](https://github.com/drduh/YubiKey-Guide)
- [The ultimate guide to YubiKey on WSL2](https://dev.to/dzerycz/series/11353)
- [Forwarding gpg-agent to a remote system over SSH](https://wiki.gnupg.org/AgentForwarding)
The former is an incredibly detailed guide to setting up GPG keys using YubiKey
as a smart card. The amount of information drduh has organized in that
repository in immense, so I urge you to go star it if you find anything in this
section helpful, as he deserves at least that much.
The second guide was used more as a reference/verification source for the first
guide but none-the-less I found it to be helpful, so I figured I would include
it here.
While I went down this rock filled rabbit hole for the purpose of getting my
YubiKey working (seamlessly) in WSL2, the majority of this should be helpful
even if you don't use a security key, as its specificity deals with getting the
respective agents/sockets communicating between WSL2 and Windows.
<!-- TODO ssh/git config to use gpnupg -->
<!-- TODO setting up remote gpg/ssh forwarding -->
## Windows
### SSH Agent
Install [gpg-bridge](https://github.com/BusyJay/gpg-bridge) using cargo
```powershell
# Powershell
cargo install -f --git https://github.com/busyjay/gpg-bridge
```
Set gpg-bridge to run on startup
```powershell
# Powershell
$cmd_path = "$HOME\.cargo\bin\gpg-bridge.exe"
$pipe = "\\.\pipe\gpg-bridge-ssh"
$cmdl = "$cmd_path gpg-bridge-ssh --extra 127.0.0.1:4321 --ssh $pipe --detach"
$key = New-Item -Path 'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run' -Force
New-ItemProperty -Path $key.PSPath -Name "gpg-bridge" -Value "$cmdl"
```
Set SSH_AUTH_SOCK to have ssh use the translated pipe
```powershell
# Powershell
[System.Environment]::SetEnvironmentVariable('SSH_AUTH_SOCK',"\\.\pipe\gpg-bridge-ssh")
```
One-off to run gpg-bridge.exe without restarting
```powershell
# Powershell
Invoke-Expression "& $cmdl"
```
### GPG Agent
On the windows side the YubiKey is fully accessible, the GPG agent should just
work.
## In WSL2
### SSH Agent
```sh
# Bash
# Install depends
sudo apt install socat iproute2
# Install wsl2-ssh-pageant
destination="$HOME/.ssh/wsl2-ssh-pageant.exe"
url="https://github.com/BlackReloaded/wsl2-ssh-pageant/releases/latest/download/wsl2-ssh-pageant.exe"
curl -sL "$url" -o "$destination"
# wget -O "$destination" "https://github.com/BlackReloaded/wsl2-ssh-pageant/releases/latest/download/wsl2-ssh-pageant.exe"
# Set the executable bit.
chmod +x "$destination"
```
### GPG Agent
The only setup needed for getting the YubiKey working in WSL2 is to
source/copy-paste [gpg.sh](wsl/gpg.sh) in your shell profile.
Along with the initialization code, I wrote a small function the resets all the
related agents/sockets. If you do not attempt to access the YubiKey while it is
not inserted, in my experience, GPG works great has no issues once reinserting
the YubiKey. It is only (inconsistently) when you try to access a YubiKey that
you have removed that puts it in a failed state.
|
