Hi Werner,
This was happening to me on the latest 2.3.4 with gpg4win 4.

Any idea why? I suspect it has to do with old intermediates being
crosssigned as well.

Best,
Anze

On Thu, 6 Jan 2022 at 09:41 Werner Koch via Gnupg-users <
gnupg-users@gnupg.org> wrote:

> Hi!
>
> instead of working around the problem, I strongly suggest to update
> gpg4win to 4.0 or at least install gnupg 2.2.33 on top of an older
> gpg4win.  This fixes the problem without a need to tweak the root cert
> store.
>
>
> Salam-Shalom,
>
>    Werner
>
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users@gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Reply via email to