Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.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 23:58:05 +0100	[thread overview]
Message-ID: <20200219235805.4bd1e291@windsurf> (raw)
In-Reply-To: <87eeuqcjuk.fsf@dell.be.48ers.dk>

On Wed, 19 Feb 2020 23:06:59 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:

>  > That's the kind of thing I assumed, but perhaps we need to add at least
>  > this link next to the IGNORE_CVES line ?  
> 
> Do you think so? We don't really do it for the other things, E.G. we
> simply claim that a specific patch fixes one or more CVEs, without
> necessarily providing a lot of details besides the CVE identifier
> 
> From the CVE identifier you can then go and look up a bunch of these
> things, E.G. on the Debian securitytracker or on the NVD website.
> 
> In a way, this is quite similar to how we claim specific licenses for a
> package.

Well, it's not a strong opinion, but I believe:

# disputed, https://github.com/erikd/libsndfile/issues/398

doesn't cost much more than

# disputed

And it directly tells people reading this .mk file what we mean by
"disputed", together with the background information about it.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-02-19 22:58 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
2020-02-19 21:44       ` Thomas Petazzoni
2020-02-19 22:06         ` Peter Korsgaard
2020-02-19 22:58           ` Thomas Petazzoni [this message]
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=20200219235805.4bd1e291@windsurf \
    --to=thomas.petazzoni@bootlin.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