From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] git: security bump to version 2.12.3
Date: Wed, 17 May 2017 22:40:17 +0200 [thread overview]
Message-ID: <87lgpv43pq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170515144447.8596-1-peter@korsgaard.com> (Peter Korsgaard's message of "Mon, 15 May 2017 16:44:47 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes CVE-2017-8386 - Git Shell Bypass By Abusing Less
> For more details, see:
> https://insinuator.net/2017/05/git-shell-bypass-by-abusing-less-cve-2017-8386/
> http://www.mail-archive.com/git at vger.kernel.org/msg120982.html
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2017.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-05-17 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 14:44 [Buildroot] [PATCH] git: security bump to version 2.12.3 Peter Korsgaard
2017-05-16 7:25 ` Thomas Petazzoni
2017-05-17 20:40 ` Peter Korsgaard [this message]
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=87lgpv43pq.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