Move CVE information into advisories directory
commit60c57b8467f11e334e7c7fd07d588c248e93d952
authorSiddhesh Poyarekar <siddhesh@sourceware.org>
Thu, 12 Oct 2023 16:50:49 +0000 (12 12:50 -0400)
committerSiddhesh Poyarekar <siddhesh@sourceware.org>
Thu, 7 Dec 2023 17:31:23 +0000 (7 12:31 -0500)
tree88d50506f7225fe19a10e76399ee3607271a7450
parent3367d8e180848030d1646f088759f02b8dfe0d6f
Move CVE information into advisories directory

One of the requirements to becoming a CVE Numbering Authority (CNA) is
to publish advisories.  Do this by maintaining a file for each CVE fixed
in the advisories directory in the source tree.  Links to the advisories
can then be shared as:

https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-YYYY-NNNN

The file format at the moment is rudimentary and derives from the git
commit format, i.e. a subject line and a potentially multi-paragraph
description and then tags to describe some meta information.  This is a
loose format at the moment and could change as we evolve this.

Also add a script process-fixed-cves.sh that processes these advisories
and generates a list to add to NEWS at release time.

Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
NEWS
advisories/GLIBC-SA-2023-0001 [new file with mode: 0644]
advisories/GLIBC-SA-2023-0002 [new file with mode: 0644]
advisories/GLIBC-SA-2023-0003 [new file with mode: 0644]
advisories/GLIBC-SA-2023-0004 [new file with mode: 0644]
advisories/GLIBC-SA-2023-0005 [new file with mode: 0644]
scripts/process-fixed-cves.sh [new file with mode: 0755]