From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-04-11
Date: Mon, 14 Jun 2021 10:45:45 +0200 [thread overview]
Message-ID: <20210614104545.39c42d14@windsurf> (raw)
In-Reply-To: <CAFOYHZB_RK=hJaTBOoTi3=pxwo_fsx=kTRfEWm0uo8XJ5EbUGg@mail.gmail.com>
Hello Chris,
On Mon, 14 Jun 2021 19:58:12 +1200
Chris Packham <judge.packham@gmail.com> wrote:
> After some effort the description was updated to say "This flaw
> affects syslog-ng versions prior to and including 2.0.9.". But the cpe
> entry hasn't been updated (if I understand correctly the reporter
> controls the description but nist controls the configurations). The
> CVE entry does now say that it has been modified since it was last
> analyzed so I'm not sure how/when that will happen.
How did you contact the NVD maintainers? Because I contacted them a few
weeks ago about some CVE details, and they fixed up like a few days
later.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-06-14 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6073d64f.1c69fb81.9d11e.7f35SMTPIN_ADDED_MISSING@mx.google.com>
2021-04-12 8:37 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-04-11 Chris Packham
2021-04-25 7:10 ` Peter Korsgaard
2021-06-10 15:37 ` Thomas Petazzoni
2021-06-14 7:58 ` Chris Packham
2021-06-14 8:45 ` Thomas Petazzoni [this message]
2021-06-14 10:00 ` Chris Packham
2021-06-14 12:01 ` Thomas Petazzoni
2021-06-23 7:58 ` Chris Packham
2021-06-23 12:33 ` Thomas Petazzoni
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=20210614104545.39c42d14@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.