From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CVE tracking for the kernel
Date: Wed, 26 Apr 2017 15:53:39 +0100 [thread overview]
Message-ID: <1493218419.10415.120.camel@codethink.co.uk> (raw)
This week I have done more work on scripts to track CVEs across mainline
and stable branches. I now have scripts to incrementally import data
from Debian and Ubuntu's trackers (descriptions, comments, commit
hashes) and to combine this with git commit logs to work out which
issues affect each branch. I've had to make some manual fixes to the
data, but mostly this Just Works - out of 164 issues imported, I
corrected errors in 3 and added missing information to 32.
I thought about using a database and web forms for this, but that would
complicate hosting. For now, the issues are stored in the git
repository in YAML format, one issue per file. There's validation code
that checks the format quite strictly, so it should be possible to
convert to a database schema at some later date.
The scripts and issue data are now at:
https://gitlab.com/cip-project/cip-kernel-sec
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
reply other threads:[~2017-04-26 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1493218419.10415.120.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/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