#21121 closed New feature (fixed)
Docs should contain a list of all security issues
| Reported by: | Russell Keith-Magee | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.5 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Suggestion via Graham Dumpleton on Twitter:
Django has policies for handling security releases. However we don't have a single canonical archive of every security problem that has been found. You either need to work through the blog archive, or work through the point release documentation.
We should add a summary page to our docs listing every security problem, severity, and affected versions.
Change History (5)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Vulnerability database link for Django Software Foundation:
http://osvdb.org/vendor/32442-django-software-foundation/1