#36436: Sensitive signer.key exposed via Django messages framework in templates
-------------------------------------+-------------------------------------
Reporter: Sarah Boyce | Owner: Sachi
Type: | Jain
Cleanup/optimization | Status: closed
Component: contrib.messages | Version: 5.1
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
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"5890d443e6e1ea454f1e76cc7c9239c0b5ccb5be" 5890d443]:
{{{#!CommitTicketReference repository=""
revision="5890d443e6e1ea454f1e76cc7c9239c0b5ccb5be"
Fixed #36436 -- Made CookieStorage.signer attribute private.
Co-authored-by: Sohail Ahmad <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36436#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019e84893797-88aa5cf9-f5dd-4c03-bd4e-eca420c27aab-000000%40eu-central-1.amazonses.com.
