From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Google Summer of Code 2018 ?
Date: Thu, 18 Jan 2018 08:51:53 +0100 [thread overview]
Message-ID: <20180118085153.57f7ba35@windsurf.lan> (raw)
In-Reply-To: <CANQCQpa3v8pf2CvXd867Xv0e9UPCd-L+Q-9yFgZsRNdVvUnkSQ@mail.gmail.com>
Hello,
On Wed, 17 Jan 2018 16:50:13 -0600, Matthew Weber wrote:
> > - Follow upstream updates and CVEs of packages. I think this topic is
> > still relevant, and IMO is the most interesting topic.
>
> I'd second that this is an interesting one (even just a manual
> approach to start with). ie. Minimally having our legal-info (or a
> new cpe-info) generate CPE compliant tags for our packages would be a
> great addition. Then those lists can be fed into various tools.
Could you describe in more details what are those "CPE compliant tags" ?
Ideally, what I'd like to see is a script that generates a webpage
showing for each package the current version in Buildroot, the latest
upstream version available, and whether the current version in
Buildroot is affected by CVEs. Optionally, such a script could be used
combined with the DEVELOPERS file to generate some notifications to
Buildroot developers that the packages they are looking after should
probably be upgraded (with a weekly notification, or something like
that).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-18 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 20:52 [Buildroot] Google Summer of Code 2018 ? Thomas Petazzoni
2018-01-17 22:50 ` Matthew Weber
2018-01-18 7:51 ` Thomas Petazzoni [this message]
2018-01-18 15:52 ` Matthew Weber
2018-01-18 22:43 ` Matthew Weber
2018-01-22 22:04 ` Arnout Vandecappelle
2018-01-23 18:00 ` Matthew Weber
2018-01-24 8:00 ` 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=20180118085153.57f7ba35@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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