From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnupg: security bump to version 1.4.23
Date: Sun, 17 Jun 2018 17:52:59 +0200 [thread overview]
Message-ID: <87y3fdo1es.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <8c0af0af39244f35c59dc5d9fb92f9369b831088.1528733323.git.baruch@tkos.co.il> (Baruch Siach's message of "Mon, 11 Jun 2018 19:08:43 +0300")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Fixes CVE-2018-12020: Unsanitized file names might cause injection of
> terminal control characters into the status output of gnupg.
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed to 2018.02.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-06-17 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 16:08 [Buildroot] [PATCH] gnupg: security bump to version 1.4.23 Baruch Siach
2018-06-11 19:37 ` Peter Korsgaard
2018-06-17 15:52 ` Peter Korsgaard [this message]
2018-07-17 7:26 ` 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=87y3fdo1es.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox