From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Common Vulnerabilities and Exposures
Date: Fri, 18 Nov 2016 12:43:29 +0100 [thread overview]
Message-ID: <582EE961.3090602@codethink.co.uk> (raw)
Hi,
one of the key parts of the maintenance work is to follow the Common
Vulnerabilities and Exposures (CVE)[1] and the fixes that comes out of
them, in this case, to the kernel.
We can check against CVE and commit lists from Debian[2]. Currently
there is no good distribution-neutral tracker for this and MITRE is not
that fast in publishing details of CVEs.
One step that Members can take is to identify the person within their
organizations that deal with low level security issues and put them in
contact with Ben so:
* They can provide input to Ben.
* Ben H. can explain them how a kernel in maintenance work in this regard.
A long term point for CIP Members is to get a CNA ID[3] and act as a CNA
or participate through a liaison if you do not want to dedicate people
to this.
[1] https://cve.mitre.org/about/faqs.html
[2] svn://scm.alioth.debian.org/svn/kernel-sec/
[3] https://cve.mitre.org/cve/cna.html
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
reply other threads:[~2016-11-18 11:43 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=582EE961.3090602@codethink.co.uk \
--to=agustin.benito@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