But perhaps I’ve misunderstood but that seems to suggest rebuilding qubes to include it. Whereas a bunch of threads seem to suggest it can just be installed.
I’ve tried various combinations of sudo dnf install split-gpg, split-gpg2, qubes-split-gpg etc and always getting a not found error.
In a new file /etc/qubes/policy.d/30-user-gpg2.policy, add line qubes.Gpg2 + SPLIT_GPG2_CLIENT_QUBE @default allow target=SPLIT_GPG2_VAULT_QUBE but using your app qube names instead of the all-caps names
Run: qvm-service --enable SPLIT_GPG2_CLIENT_QUBE split-gpg2-client (but using your client app qube name)
In your split-gpg2 vault app qube (not template):
Setup / import your secret key (as in the doc you linked)
In your split-gpg2 client app qube (not template):
Import your public key (as in the doc you linked)
I think that covers it all. It’s not trivial to set it all up. You can have multiple client app qubes, in which case you repeat some of the steps above for each.
sudo dnf install split-gpg2-dom0
Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00
No match for argument: split-gpg2-dom0
Error: Unable to find a match: split-gpg2-dom0
Out of curiosity I tried to configure Thunderbird with Split GPG-2 and it works. No need to follow Split GPG-1 docs: any how-to about Thunderbird using an external GnuPG will work. Split GPG-2 doesn’t need any extra step!
Side note: maybe the whole Thunderbird section could be replaced in the Split GPG-1 page by something like that:
The built-in functionality is more limited currently, including that public keys must live in yourwork-emailqube with Thunderbird rather than your offlinework-gpgqube.
Follow any tutorial about smartcards or external GnuPG. The only extra step is to make sure to set mail.openpgp.alternative_gpg_path value to /usr/bin/qubes-gpg-client-wrapper.