Unable to issue subkey revocation

Andrew Gallagher andrewg at andrewg.com
Mon May 25 13:45:59 CEST 2026


On 25/05/2026 12:10, marqueandreprisal--- via Gnupg-users wrote:
> A, oh it seems you want me to attach the pubkey for you to examine. The 
> key is still on keys.openpgp.org[https://keys.openpgp.org] just search 
> the key id shown in the screenshot.
OK, got it. It appears that the primary key is indeed revoked. The 
openkeychain screenshot implies that the primary key is a "subkey", 
which is incorrect, but this does not appear to have affected the 
validity calculation.

If I look at the key in gpg, it also shows that the primary has been 
revoked:

```
pub   rsa3072/0xA3ED3C7160B7E73F 2026-04-27 [SCEA] [revoked: 2026-05-24]
       C18FAB74166C6BBB2196B5B5A3ED3C7160B7E73F
       reason for revocation: Key has been compromised
          revocation comment: private key was copied during backup operation
```

Do you see something different in yours?

How did you revoke the subkey? The usual procedure on the command line 
would be:

```
gpg --edit-key <key-id>
key 1
revkey
save
```

The critical part being "key 1" that selects the first subkey (it should 
show a "*" beside the subkey after you do it). If you don't select the 
subkey then you will revoke the primary. Beware also that if you say 
"key 1" twice, the second will undo the first (because it is a toggle) 
and you will still revoke the primary.

A



More information about the Gnupg-users mailing list