[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream
From: |
Leo Famulari |
Subject: |
bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream |
Date: |
Tue, 4 Apr 2023 12:33:36 -0400 |
On Mon, Mar 20, 2023 at 09:01:33AM -0400, Ethan Blanton via Bug reports for GNU
Guix wrote:
> However, the bug referenced here is fixed in upstream commit
> 4cc724639c012215f59648cbb4b7631b9d352e36, which shipped in gnupg
> 2.2.34. Meanwhile, all gnupg releases older than 2.2.35 suffer from
> an S/MIME key-parsing bug (referenced in
> https://www.mail-archive.com/gnupg-users@gnupg.org/msg40758.html).
Does this bug have a CVE ID, or any information from upstream about
where it was fixed? It's hard to find release notes on the GnuPG
website.
- bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream,
Leo Famulari <=