From: Mark Wielaard <mark@klomp.org>
To: bzip2-devel@sourceware.org
Cc: lwn@lwn.net, Julian Seward <jseward@acm.org>
Subject: bzip2 1.0.7 released
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <b8aab785a67113e4f50c54a6cb59129c11f805b6.camel@klomp.org> (raw)
We are happy to announce the release of bzip2 1.0.7.
This is an emergency release because the old bzip2 home
is gone and there were outstanding security issues.
The original bzip2 home, downloads and documentation
can now be found at: https://sourceware.org/bzip2/
bzip2 1.0.7 contains only the following bug/security fixes:
* Fix undefined behavior in the macros SET_BH, CLEAR_BH, & ISSET_BH
* bzip2: Fix return value when combining --test,-t and -q.
* bzip2recover: Fix buffer overflow for large argv[0]
* bzip2recover: Fix use after free issue with outFile (CVE-2016-3189)
* Make sure nSelectors is not out of range (CVE-2019-12900)
A future 1.1.x release is being prepared by Federico Mena Quintero
which will include more fixes, an updated build system and possibly
an updated SONAME default.
Please read his blog for more background on this:
https://people.gnome.org/~federico/blog/tag/bzip2.html
next reply other threads:[~2019-06-27 18:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Mark Wielaard [this message]
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 ` 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
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 ` bzip2 test suite (Was: bzip2 1.0.7 released) Mark Wielaard
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=b8aab785a67113e4f50c54a6cb59129c11f805b6.camel@klomp.org \
--to=mark@klomp.org \
--cc=bzip2-devel@sourceware.org \
--cc=jseward@acm.org \
--cc=lwn@lwn.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).