|
2 | 2 | This file is a temporary way to post CVE notifications before
|
3 | 3 | a release.
|
4 | 4 |
|
5 |
| - Document the CVE fix info in upgrading.txt. Publishing |
6 |
| - upgrading.txt would push info on the next release not the current |
7 |
| - release. |
| 5 | + Document the CVE fix info in upgrading.txt. We extract the sections |
| 6 | + from upgrading.txt that deal with the CVE into a separate CVE.html. |
| 7 | + An updated docs/security.html and docs/CVE.html provide the details |
| 8 | + on a between release CVE announcment. |
8 | 9 |
|
9 |
| - So we comment out a reference anchor in upgrading.txt and use that |
10 |
| - comment to extract the section from upgrading.txt into CVE.txt. |
11 |
| - The extracted section gets the same anchor that is in upgrading.txt, |
12 |
| - but is is not commented out. |
| 10 | + Publishing upgrading.txt would include info on the to be released |
| 11 | + roundup software and wouldn't match the rest of the release docs. |
13 | 12 |
|
14 |
| - Then we add a summary to the list of CVE's in security.txt using a |
15 |
| - :ref: to the anchor. If CVE.txt is part of the build and |
16 |
| - upgrading.txt has a commented out anchor, security.txt entries link |
17 |
| - to CVE.html in the generated documentation. |
| 13 | + To extract the info from upgrading.txt to use in CVE.html, add a |
| 14 | + commented out a reference anchor in upgrading.txt. Then in CVE.txt |
| 15 | + we use an include directive with start-after and end-before options |
| 16 | + to exract the sections from upgrading.txt into CVE.html. |
18 | 17 |
|
19 |
| - In upgrading.txt add a |
| 18 | + The extracted section in CVE.txt gets the same anchor that is in |
| 19 | + upgrading.txt, but is is not commented out. This allows us to swap |
| 20 | + out CVE.txt and uncomment the reference in upgrading.txt. Then |
| 21 | + rerunning sphinx-build will make security.html point to the sections |
| 22 | + in upgrading.html. |
| 23 | + |
| 24 | + For example, in upgrading.txt add a |
20 | 25 |
|
21 | 26 | .. comment: _CVE-2024-39124:
|
22 | 27 |
|
|
44 | 49 | :end-before: .. comment: end of CVE
|
45 | 50 |
|
46 | 51 | After building the docs, install docs/security.html and
|
47 |
| - docs/CVE.html on the web site. Use the security.html URL |
48 |
| - on the web site to update the CVE report. |
| 52 | + docs/CVE.html on the web site. Reference: |
| 53 | + |
| 54 | + https://www.roundup-tracker.org/docs/security.html |
| 55 | + |
| 56 | + in the CVE announcement from Mitre. |
49 | 57 |
|
50 | 58 | When the release is ready, replace 'comment: _CVE' with '_CVE' in
|
51 | 59 | upgrading.txt. This makes the anchors in upgrading.txt live.
|
52 | 60 |
|
53 |
| - Then disable CVE.txt by removing CVE.txt from contents.txt in the |
54 |
| - toctree hidden section. Also add CVE.txt to exclude_patterns in |
| 61 | + Then disable CVE.txt by removing CVE.txt from contents.txt in the |
| 62 | + toctree hidden section. Also add docs/CVE.txt to exclude_patterns in |
55 | 63 | conf.py.
|
56 | 64 |
|
57 | 65 | No change needs to happen to security.txt as it's using a :ref: and
|
|
0 commit comments