From: Jeff King <peff@peff.net>
To: Erika Voss <erikav@zillowgroup.com>
Cc: "Randall S. Becker" <rsbecker@nexbridge.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git Vulnerability Announced?
Date: Thu, 31 May 2018 12:39:52 -0400 [thread overview]
Message-ID: <20180531163952.GA9423@sigill.intra.peff.net> (raw)
In-Reply-To: <E1D8F36A-9317-41ED-B761-2AE15B54B927@zillowgroup.com>
On Thu, May 31, 2018 at 04:00:38PM +0000, Erika Voss wrote:
> Yes here is what was sent to me -
>
> https://www.theregister.co.uk/2018/05/30/git_vulnerability_could_lead_to_an_attack_of_the_repo_clones/
> https://www.debian.org/security/2018/dsa-4212
Yeah, the release announcement from the project is at:
https://public-inbox.org/git/xmqqy3g2flb6.fsf@gitster-ct.c.googlers.com/
> The one that I could find from online was:
> https://git-scm.com/download/mac
>
> But, the latest version available on this site was 2.17.0, which does
> not include the security patch.
The binary installs for MacOS are done by a third party, and sometimes
lag the source releases. You can build it from source yourself, either
from a tarball:
https://git.kernel.org/pub/software/scm/git/git-2.17.1.tar.gz
or by cloning with git:
https://kernel.org/pub/scm/git/git.git
There are some instructions in the INSTALL file, which you can also read
online:
https://github.com/git/git/blob/master/INSTALL
You can also use Homebrew to install, which usually updates to new
versions pretty promptly:
https://brew.sh/
-Peff
prev parent reply other threads:[~2018-05-31 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 15:57 Git Vulnerability Announced? Erika Voss
2018-05-31 15:59 ` Randall S. Becker
2018-05-31 16:00 ` Erika Voss
2018-05-31 16:39 ` Jeff King [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=20180531163952.GA9423@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=erikav@zillowgroup.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).