I am having a similar issue on my Windows 11 system (upgraded from Windows
10).
I've tried with no luck
- adding the 2 root CAs and the intermediate CA from the referenced
article
- deleted the expired DST Root CA X3
- rebooted my system
Regards,
*Ken*
*Kenneth H. Lee,
I forgot to mention that I installed gpg4win 4.0.0 which has gpg 2.3.4
Regards,
*Ken*
*Kenneth H. Lee, CISSP*Google Voice: +1 646 883 9195
KHL at KENHLEE dot COM
On Sun, Dec 26, 2021 at 2:36 PM Kenneth H. Lee wrote:
> I am having a similar issue on my Windows 11 system (upgraded from
> On 25 Dec 2021, at 11:24, Alex Nadtoka wrote:
>
>
> Hi Andrew, yes I have changed the real name of my mailbox and the server)
> Thanks for the reply.
> My Client Machine is Windows . If you can tell me how to do that I would
> appreciate it. Thanks again for the update)
> Finally got
Hi Andrew, yes I have changed the real name of my mailbox and the server)
Thanks for the reply.
My Client Machine is Windows . If you can tell me how to do that I
would appreciate it. Thanks again for the update)
Finally got some help.
Sorry for all these troubles and Merry Christmas
Regards,
> 2021-12-23 11:27:30 gpg[12864] DBG: connection to the dirmngr established
> 2021-12-23 11:27:30 gpg[12864] DBG: chan_0x025c -> GETINFO version
> 2021-12-23 11:27:30 gpg[12864] DBG: chan_0x025c <- D 2.3.4
> 2021-12-23 11:27:30 gpg[12864] DBG: chan_0x025c <- OK
> 2021-12-23 11:27:30
On Thu, 2021-12-23 at 12:37 +0200, Alex Nadtoka via Gnupg-users wrote:
> 2021-12-23 11:27:30 gpg[12864] DBG: chan_0x025c -> KEYSERVER --
> clear hkps://gpg.example.com/
This doesn't look like a real keyserver. Did you redact this, or is
this really what is currently configured in
>
> I cannot connect to any keyserver. The error is certificate expired. Here
> is Debug log. I am on latest (I think) Windows 10
2021-12-23 11:27:15 gpg[17680] using character set 'utf-8'
2021-12-23 11:27:15 gpg[17680] Note: RFC4880bis features are enabled.
2021-12-23 11:27:15 gpg[17680]
