From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/gnupg2: security bump to version 2.3.7
Date: Wed, 03 Aug 2022 22:43:59 +0200 [thread overview]
Message-ID: <878ro5t5v4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220716143311.711343-2-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 16 Jul 2022 16:33:11 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix CVE-2022-34903: GnuPG through 2.3.6, in unusual situations where an
> attacker possesses any secret-key information from a victim's keyring
> and other constraints (e.g., use of GPGME) are met, allows signature
> forgery via injection into the status line.
> https://lists.gnupg.org/pipermail/gnupg-announce/2022q3/000474.html
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.05.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-03 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 14:33 [Buildroot] [PATCH 1/2] package/gnupg2: drop unrecognized option Fabrice Fontaine
2022-07-16 14:33 ` [Buildroot] [PATCH 2/2] package/gnupg2: security bump to version 2.3.7 Fabrice Fontaine
2022-08-03 20:43 ` Peter Korsgaard [this message]
2022-07-16 15:32 ` [Buildroot] [PATCH 1/2] package/gnupg2: drop unrecognized option Yann E. MORIN
2022-08-03 20:43 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ro5t5v4.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.