Stage up a slew of new CVEs, and also fix up the CVE tables a little #216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It annoyed me that the CVE IDs were getting wrapped in our published table, so I stopped that.
Also, chunked up the CVE table into years, now that we've been at this for a little while.
It all looks lovely in my local Hugo test env.
Finally, added entries for a bunch of new chipset vulns from @headlesszeke (see private repo issues https://github.com/AustinHackers/disclosures/issues/13 and https://github.com/AustinHackers/disclosures/issues/14).
Keeping the details out until right about 5pm today, but a couple hours of RBPs in a pull request shouldn't bother anyone none. Don't land that until the content commit shows up.
Thanks @headlesszeke!