From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: libc-alpha@sourceware.org
Cc: carlos@redhat.com, adhemerval.zanella@linaro.org
Subject: [PATCH htdocs] glibc is now a CNA
Date: Wed, 7 Feb 2024 07:43:38 -0500 [thread overview]
Message-ID: <20240207124338.1400513-1-siddhesh@gotplt.org> (raw)
Drop the line about glibc not being a CNA and link to the CVE page about
us.
https://www.cve.org/Media/News/item/news/2024/02/06/GNU-C-Library-Added-as-CNA
Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>
---
security.html | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/security.html b/security.html
index 2b73211..7b044c2 100644
--- a/security.html
+++ b/security.html
@@ -126,13 +126,13 @@ directory on the master branch of the glibc git repository.
<h2>CVE management</h2>
<p>
-glibc does not yet have a CVE Numbering Authority (CNA), but this may
-change in the future. For glibc CVEs you may contact the security team
-for help with any updates you'd like to make. This would
-include updates to the contents of a CVE advisory or requests to update,
-dispute or reject a CVE. For CNA related requests please use the mailing
-list to contact the security team members, and not their private email
-addresses.
+For CVEs assigned by the
+<a href="https://www.cve.org/PartnerInformation/ListofPartners/partner/glibc">glibc CVE Numbering Authority (CNA)</a>,
+you may contact the security team for help with any updates you'd like
+to make. This would include updates to the contents of a CVE advisory or
+requests to update, dispute or reject a CVE. For CNA related requests
+please use the mailing list to contact the security team members, and
+not their private email addresses.
</p>
<a id="keys"><h2>GPG Keys</h2></a>
--
2.43.0
reply other threads:[~2024-02-07 12: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=20240207124338.1400513-1-siddhesh@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).