On 25/05/2026 12:03, marqueandreprisal--- via Gnupg-users wrote:
I didn't notice a signing subkey in the screenshot it appeared to me the primary key is revoked while the E subkey was not.
Well, the first key is listed under "subkeys" so if it's actually the primary key then there's a bug in openkeychain, because the primary key is not a subkey.
Again however in gpg2 it reportes the E revoked maybe based only in the assumption that if the primary is revoked so are the subkeys, it seems to be a bug in gpg2.
Or it could be a bug in openkeychain. Given that it already seems to think that the primary key is a subkey, it may be that something internally has recorded that "the first subkey is revoked" and there's a mismatch internally so it gets displayed wrong.
As far as the export revocation command it is not clear why you want me to send it to you here.
Because I can tell by looking at it which (sub)key is really revoked - and it seems more likely to me that it is gpg that is correct.
In the hours wasted with AI trying to figure this out as I stated in the opening I did try to implicitly revoke the subkey by using the subkey ID to issue revocation and when doing so gpg2 would report "no change".
If you had already revoked it, and tried to revoke it again, then this would be expected.
A
_______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users
