From: Mark Wielaard <mark@klomp.org>
To: jseward@acm.org, Federico Mena Quintero <federico@gnome.org>,
bzip2-devel@sourceware.org
Subject: Re: Alternative nSelectors patch (Was: bzip2 1.0.7 released)
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <7fc165ba50cad2fc5cd21a5ee610acc6cac148fa.camel@klomp.org> (raw)
In-Reply-To: <f9230fc65a3529b59b31f13494c72a1c01a6148e.camel@klomp.org>
Hi,
> Attached is the patch with a commit message that hopefully explains why
> the change is correct (and why the CVE, although a source code bug,
> wasn't really exploitable in the first place). Hope it makes sense.
So the https://sourceware.org/git/bzip2-tests.git was integrated into
the buildbot and it turned RED. As expected, since without this fix it
fails with:
- ./lbzip2/32767.bz2 bad decompress result
So I have now pushed the patch and hopefully that turns the buildbot
green: https://builder.wildebeest.org/buildbot/#/builders?tags=bzip2
Cheers,
Mark
next prev parent reply other threads:[~2019-07-09 21:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 bzip2 1.0.7 released Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Julian Seward
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` bzip2 test suite (Was: bzip2 1.0.7 released) Mark Wielaard
2019-01-01 0:00 ` bzip2 1.0.7 released Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Alternative nSelectors patch (Was: bzip2 1.0.7 released) Mark Wielaard
2019-01-01 0:00 ` Julian Seward
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard [this message]
2019-01-01 0:00 ` bzip2 1.0.7 released Jeffrey Walton
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=7fc165ba50cad2fc5cd21a5ee610acc6cac148fa.camel@klomp.org \
--to=mark@klomp.org \
--cc=bzip2-devel@sourceware.org \
--cc=federico@gnome.org \
--cc=jseward@acm.org \
/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).