From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] package/libsndfile: annotate _IGNORE_CVES for the included security patches
Date: Wed, 19 Feb 2020 22:37:04 +0100 [thread overview]
Message-ID: <87imk2cl8f.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200219200853.58120567@windsurf> (Thomas Petazzoni's message of "Wed, 19 Feb 2020 20:08:53 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> On Wed, 19 Feb 2020 17:01:59 +0100
> Peter Korsgaard <peter@korsgaard.com> wrote:
>> Also mark CVE-2018-13419 as disputed.
>>
>> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> What does "disputed" means in this context ?
That someone related to the project claims that it isn't a security
issue or cannot reproduce the issue.
Specifically for this CVE, see the discussion here:
https://github.com/erikd/libsndfile/issues/398
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-02-19 21:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 16:01 [Buildroot] [PATCH 1/5] package/audiofile: annotate _IGNORE_CVES for the included security patches Peter Korsgaard
2020-02-19 16:01 ` [Buildroot] [PATCH 2/5] package/libsndfile: " Peter Korsgaard
2020-02-19 19:08 ` Thomas Petazzoni
2020-02-19 21:37 ` Peter Korsgaard [this message]
2020-02-19 21:44 ` Thomas Petazzoni
2020-02-19 22:06 ` Peter Korsgaard
2020-02-19 22:58 ` Thomas Petazzoni
2020-02-20 7:01 ` Peter Korsgaard
2020-02-20 12:16 ` Peter Korsgaard
2020-02-19 16:02 ` [Buildroot] [PATCH 3/5] package/libtomcrypt: " Peter Korsgaard
2020-02-20 12:16 ` Peter Korsgaard
2020-02-19 16:02 ` [Buildroot] [PATCH 4/5] package/vorbis-tools: " Peter Korsgaard
2020-02-20 12:16 ` Peter Korsgaard
2020-02-19 16:02 ` [Buildroot] [PATCH 5/5] package/ipsec-tools: " Peter Korsgaard
2020-02-20 12:16 ` Peter Korsgaard
2020-02-20 12:14 ` [Buildroot] [PATCH 1/5] package/audiofile: " Peter Korsgaard
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=87imk2cl8f.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.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