- Issue created by @damienmckenna
- 🇺🇸United States greggles Denver, Colorado, USA
This seems like a great idea to me. Thanks for getting it started.
Do you have proposed template text for the SA description areas?
- 🇺🇸United States damienmckenna NH, USA
Outstanding questions:
* Should the existing "unsupported" SA be updated to look like a normal SA?
* If there were multiple vulnerabilities should additional SAs be created as needed to match the number of vulnerabilities? - 🇺🇸United States damienmckenna NH, USA
Maybe something like:
Updated 2022-02-02: New maintainers have volunteered for the project and created new releases which include fixes for the security issues that caused it to be unsupported.
(refined from one of the existing SAs)
.. but there are some unanswered questions around the process.
- 🇺🇸United States damienmckenna NH, USA
- 🇺🇸United States damienmckenna NH, USA
- 🇺🇸United States greggles Denver, Colorado, USA
I followed this process for False Account Detector.
The old advisory was a mega-combined item from 2010: https://www.drupal.org/forum/newsletters/security-advisories-for-contrib... →
I added
<del>tags around the old text and added this text:
<strong>Edited March 27, 2024:</strong> Previous versions of False Account Detector for Drupal core versions 5.x and 6.x contained these security vulnerabilities. The code has been rewritten completely for Drupal 10+ and is now available again.