All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Weber <matthew.weber@collins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-07-12
Date: Tue, 21 Jul 2020 11:00:58 -0500	[thread overview]
Message-ID: <CANQCQpY2W52CK2VTEBsh88VQYYh41KgJVuROWhs5bu5bygNYEg@mail.gmail.com> (raw)
In-Reply-To: <20200721175356.6980b430@windsurf.home>

On Tue, Jul 21, 2020 at 10:55 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> On Tue, 21 Jul 2020 10:30:34 -0500
> Matthew Weber <matthew.weber@collins.com> wrote:
>
> > Ah, yeah that could work.  I was looking at making a subsection under
> > "21.6. Reporting issues/bugs or getting help" if we do add it in the
> > manual.  There are going to be cases where a Buildroot CVE report
> > misreports because of our scripts, plus the case of an actual
> > dictionary bug.
>
> I think section 21.6 is really more oriented towards end users of
> Buildroot, and explain how they should get back to us to report
> issues/bugs.
>
> The topic of how to notify NVD maintainers of invalid CVEs is really
> advanced, and mainly a Buildroot maintainer/developer topic.
>
> > Maybe we start on the wiki?
>
> Yes, I would say yes. Perhaps start a page related to security/CVE
> tracking in Buildroot.

On the main page I've added "Security Vulnerability Management" under
https://elinux.org/Buildroot#Important_links .  I took a quick first
cut at pkgstats and developer email info as well

Regards,
Matt

  reply	other threads:[~2020-07-21 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5f0c105a.1c69fb81.17d79.8de3SMTPIN_ADDED_MISSING@mx.google.com>
2020-07-17 13:01 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-07-12 Guillaume Bres
2020-07-17 15:37   ` Thomas Petazzoni
2020-07-17 15:45     ` Matthew Weber
2020-07-17 15:46       ` Matthew Weber
2020-07-21 15:13     ` Matthew Weber
2020-07-21 15:23       ` Thomas Petazzoni
2020-07-21 15:30         ` Matthew Weber
2020-07-21 15:53           ` Thomas Petazzoni
2020-07-21 16:00             ` Matthew Weber [this message]
2020-07-21 17:28               ` 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=CANQCQpY2W52CK2VTEBsh88VQYYh41KgJVuROWhs5bu5bygNYEg@mail.gmail.com \
    --to=matthew.weber@collins.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.