Prior to using Qubes, I was using PGP with a hardware key as the ultimate trust. I used the key certification this way: once I have gained enough confidence about some public key I downloaded online, I will certify (sign) it with my PGP key on the hardware key.
Now that I moved to Qubes, I found that split-gpg 1 and 2 specifically forbids this usage. Why? The documentation didn’t discuss at length, only stating that
Therefore, it cannot differentiate between e.g. signatures of a piece of data or signatures of another key.
But why is that a problem? I can understand that, if the OS in which gpg is invoked is compromised, then gpg can be altered to always support signed key regardless of whether it’s genuine. But we have the public key with the signature as data, and we have an hypothetically uncompromised private key protected air-gapped. Thus, we can always move the data to another machine and verify there, which is very easy in Qubes: just open a new qube and check the key certification there; and the compromised VM can’t fake that, under the hypothesis that the private key is protected.
Therefore, I don’t understand the incentive behind the prohibition of key certification, and hope to discuss it.
Thanks in advance.