From: Mark Wielaard <mark@klomp.org>
To: bzip2-devel@sourceware.org
Cc: Julian Seward <jseward@acm.org>
Subject: CVE-2019-12900
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <f35fe6d206c2de539a50245281f98bd1b745ea41.camel@klomp.org> (raw)
Hi,
I wrote a bit about our handling of CVE-2019-12900
and the bzip2 1.0.7 and 1.0.8 releases.
https://gnu.wildebeest.org/blog/mjw/2019/08/02/bzip2-and-the-cve-that-wasnt/
Please do leave a comment if I got something wrong.
Thanks,
Mark
reply other threads:[~2019-08-03 20:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f35fe6d206c2de539a50245281f98bd1b745ea41.camel@klomp.org \
--to=mark@klomp.org \
--cc=bzip2-devel@sourceware.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).