[SOLVED] Re: gpg4win expired code signing cert; please renew.

have--- via Gnupg-users <[email protected]> Tue, 28 Oct 2025 22:22:18 +0000

Newsgroups	gmane.comp.encryption.gpg.user
Message-ID	<[email protected]>

On Date: Fri, 17 Oct 2025 12:32:51 +0200, Werner Koch <[email protected]>
wrote:

>Nope. Your system is not up to date or something else is wrong at your
>site.

You are entirely correct, of course. I apologize for wasting your time.
Perhaps I should feel bad enough about this to set aside some time for
constructive contribution to gpg development one of these days. :-/

#ifdef YOU_WANT_TO_KNOW_WHY_I_MADE_THIS_NOISE

As I said upthread, this was an indirect report—and I don’t have
Microsoft Windows to test it myself. After I walked through this with
the inexpert remote user in detail and they provided me a ton of
screenshots, there emerged a situation with multiple layers of unusual
misunderstanding that I didn’t expect.

When I saw the expired date on the cert on gpg4win.org’s verification
instructions page, I thought the expired cert problem the user expressed
to me must be correct—whoops! The user is not to blame; they are a
newbie earnestly trying to DTRT without knowing how. This is my fault.

I had to drop everything 2025-10-17 due to unusual events in the U.S.,
and couldn’t process list mail or catch up until now. I think I do need
to post this “my faulty report, not GnuPG’s problem” notice.

#endif /* YOU_WANT_TO_KNOW_WHY_I_MADE_THIS_NOISE */

Always,

[email protected]

--
A makeshift way to distribute my current PQ-PGP key:
https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250107/4732a382/attachment.key
01A6D81EEAD7EEEC393DEC1401F4894C154E1B8EE32E9059CA5566792A836823

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

signature.asc (application/pgp-signature, 297 B)