From: Andy Moreton <andrewjmoreton@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Security update needed for mercurial
Date: Tue, 19 Apr 2016 18:22:00 -0000 [thread overview]
Message-ID: <vz137qhlfxy.fsf@gmail.com> (raw)
In-Reply-To: <86h9fjdhkf.fsf@gmail.com>
On Sat 02 Apr 2016, Andy Moreton wrote:
> Hi,
>
> The current package is for mercurial 3.5.1, but upstream have released
> 3.7.3 as a security release, with fixes for:
>
> CVE-2016-3630 Mercurial: remote code execution in binary delta decoding
> CVE-2016-3068 Mercurial: arbitrary code execution with Git subrepos
> CVE-2016-3069 Mercurial: arbitrary code execution when converting Git repos
>
> Release announcement is here:
> http://permalink.gmane.org/gmane.comp.version-control.mercurial.general/37523
>
> Can the cygwin mercurial maintainer please issue an updated package.
>
Is the mercurial maintainer still reading the list ?
AndyM
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-04-19 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 17:52 Updated package needed for mercurial 3.7.3 security update Andy Moreton
2016-04-19 18:22 ` Andy Moreton [this message]
2016-04-20 9:00 ` Security update needed for mercurial Corinna Vinschen
2016-04-20 17:08 ` Security update needed for mercurial (upload error: doesn't follow naming convention) Jari Aalto
2016-04-20 17:14 ` Corinna Vinschen
2016-04-20 17:22 ` Jon Turney
2016-04-20 18:16 ` Warren Young
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=vz137qhlfxy.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).