Seems like QUBES_GPG_DOMAIN setting is being ignored on QubesOS R4.0. Each time I run gpg2 --list-secret-keys I get a Qubes dialog box asking:
Do you want to allow the following operation?
Select the target domain and confirm with OK.
Source:
Operation: qubes.Gpg2
Target:
Not a huge problem (other than that all works as expected), but kind of annoying.
My .split-gpg2-rc from the client cube:
$ cat .split-gpg2-rc
# put this file in ~user/.split-gpg2-rc and modify according your needs
#### Settings affecting the client (running gpg2) ####
export QUBES_GPG_DOMAIN=vault
...and from the server cube:
$ cat .split-gpg2-rc
# put this file in ~user/.split-gpg2-rc and modify according your needs
#### Settings affecting the client (running gpg2) ####
export QUBES_GPG_DOMAIN=vault
##### Settings affecting the server (running gpg-agent) ####
export QUBES_SPLIT_GPG2_PKSIGN_AUTOACCEPT_TIME=no
export QUBES_SPLIT_GPG2_PKDECRYPT_AUTOACCEPT_TIME=300
# to enable verbose notifications comment the folloing line out:
export QUBES_SPLIT_GPG2_VERBOSE_NOTIFICATIONS=yes
Seems like
QUBES_GPG_DOMAINsetting is being ignored on QubesOS R4.0. Each time I rungpg2 --list-secret-keysI get a Qubes dialog box asking:Not a huge problem (other than that all works as expected), but kind of annoying.
My
.split-gpg2-rcfrom the client cube:...and from the server cube: