From: luca.boccassi@gmail.com
To: dev@dpdk.org
Cc: thomas@monjalon.net, maxime.coquelin@redhat.com,
david.marchand@redhat.com, ktraynor@redhat.com,
Luca Boccassi <bluca@debian.org>
Subject: [PATCH] doc: relax requirement on commit messages of security fixes
Date: Thu, 10 Mar 2022 17:59:47 +0000 [thread overview]
Message-ID: <20220310175947.273850-1-luca.boccassi@gmail.com> (raw)
From: Luca Boccassi <bluca@debian.org>
Allow more flexibility with embargo lifting by not requiring
mentions of CVEs in commit messages if the lift date allows
it.
Signed-off-by: Luca Boccassi <bluca@debian.org>
---
doc/guides/contributing/vulnerability.rst | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/doc/guides/contributing/vulnerability.rst b/doc/guides/contributing/vulnerability.rst
index b6300252ad..fc60e02e37 100644
--- a/doc/guides/contributing/vulnerability.rst
+++ b/doc/guides/contributing/vulnerability.rst
@@ -170,7 +170,10 @@ The patches fixing the vulnerability are developed and reviewed
by the security team and
by elected area experts that agree to maintain confidentiality.
-The CVE id and the bug id must be referenced in the patch.
+The CVE id and the bug id must be referenced in the patch if there is no
+embargo, or if there is an embargo, but it will be lifted when the release
+including the patch is published. If the embargo is going to be lifted after the
+release, then the CVE and bug ids must be omitted from the commit message.
Backports to the identified affected versions are done once the fix is ready.
--
2.34.1
next reply other threads:[~2022-03-10 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 17:59 luca.boccassi [this message]
2023-03-31 10:34 ` Thomas Monjalon
2023-03-31 10:37 ` Maxime Coquelin
2023-07-05 23:07 ` Stephen Hemminger
2023-11-24 13:53 ` David Marchand
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=20220310175947.273850-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).