Re: Unable to issue subkey revocation

--===============2595804158736245474==
Content-Type: multipart/signed; boundary="nextPart21198841.FMV2BEsqCQ";
 micalg="pgp-sha512"; protocol="application/pgp-signature"

--nextPart21198841.FMV2BEsqCQ
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"; protected-headers="v1"
From: Meik Michalke <[email protected]>
To: [email protected]
Subject: Re: Unable to issue subkey revocation
Date: Mon, 01 Jun 2026 11:30:00 +0200
Message-ID: <10794454.F3ui3E0B66@kasidy>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

Am Montag, 1. Juni 2026, 08:46:46 CEST schrieb Chris DeYoung:
> It doesn't need to. The subkey is automatically invalid because the
> primary key associated with it is invalid (revoked).

yes, first revoking a primary key and then asking to use it once more to 
revoke one of its subkeys sound a bit like burning down the house and then 
wanting to lock your flat door.

--nextPart21198841.FMV2BEsqCQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQRs7BjQbc011HqitSUz/RvPXledgwUCah1RGBsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIACgkQM/0bz15XnYOeEAEA7qUkSBGKvOGZduUh3SXJ
VvaQMYkZq/JMO+EBc27PNYgA/jZqosfynZCk/DD32QpUqHWYsVKLxzRe6KPzogwt
qYkM
=b+w2
-----END PGP SIGNATURE-----

--nextPart21198841.FMV2BEsqCQ--






--===============2595804158736245474==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-users mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-users

--===============2595804158736245474==--