From: Joseph Reynolds <jrey@linux.ibm.com>
To: openbmc <openbmc@lists.ozlabs.org>, krtaylor <kurt.r.taylor@gmail.com>
Subject: [SecurityworkGroup] Security response team - bug database needed
Date: Wed, 9 Jun 2021 19:15:25 -0500 [thread overview]
Message-ID: <5961cc98-ef84-f38b-e606-35f94c94c511@linux.ibm.com> (raw)
This is a followup to a discussion in the security working group meeting
held 2021-06-09 agenda item 11.
The security response team has difficulty tracking reported security
vulnerabilities to closure and writing CVEs in a timely manner. Having
a confidential bug tracker would help.
Per Dick, the UEFI team uses bugzilla and has a restructured corner for
the security response team: anyone can write a bug, but only security
response team members can see it.
What are the best practices? How do we get a bug tracker which only
OpenBMC security response team members can read?
Joseph
next reply other threads:[~2021-06-10 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 0:15 Joseph Reynolds [this message]
2021-06-16 13:08 ` [SecurityworkGroup] Security response team - bug database needed krtaylor
2021-06-21 19:02 ` Joseph Reynolds
2021-06-30 22:11 ` Patrick Williams
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=5961cc98-ef84-f38b-e606-35f94c94c511@linux.ibm.com \
--to=jrey@linux.ibm.com \
--cc=kurt.r.taylor@gmail.com \
--cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).