From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [committed] advisories: Add Reported-By
Date: Thu, 18 Apr 2024 08:53:23 -0400 [thread overview]
Message-ID: <20240418125323.313508-1-siddhesh@sourceware.org> (raw)
Add a new tag to give credit to vulnerability discoverers.
Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
---
advisories/README | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/advisories/README b/advisories/README
index 94e68b1350..b8f8a829ca 100644
--- a/advisories/README
+++ b/advisories/README
@@ -37,6 +37,10 @@ entries for each release branch in the glibc repository, indicating that
all of those commits contributed to fixing that issue in each of those
branches.
+Reported-By:
+The entity that reported this issue. There could be multiple entries, one for
+each reporter.
+
Adding an Advisory
------------------
--
2.44.0
reply other threads:[~2024-04-18 12: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=20240418125323.313508-1-siddhesh@sourceware.org \
--to=siddhesh@sourceware.org \
--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).