#35612: Emphasise user responsibility within "Reporting security issues" to
detail
invalid reports
-------------------------------------+-------------------------------------
Reporter: Sarah Boyce | Owner: Sarah
Type: | Boyce
Cleanup/optimization | Status: closed
Component: Documentation | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia <124304+nessita@…>):
In [changeset:"d6a44efa496f407efaf67f61499b2c2ca4317aec" d6a44ef]:
{{{#!CommitTicketReference repository=""
revision="d6a44efa496f407efaf67f61499b2c2ca4317aec"
[5.2.x] Refs #35612 -- Extended docs on how the security team evaluates
reports.
Co-authored-by: Shai Berger <s...@platonix.com>
Backport of f609a2da868b2320ecdc0551df3cca360d5b5bc3 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35612#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070194d0d0c093-6d8a2db8-7fd4-4529-9e4c-c7f49a73cfa9-000000%40eu-central-1.amazonses.com.
