#31412: Database timing attack against sessions.
----------------------------------+--------------------------------------
Reporter: Brian May | Owner: (none)
Type: Bug | Status: closed
Component: contrib.sessions | Version: 3.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by shamrin):
Carlton, could you please share Django Security Team reasoning about the
impractically of session timing attack?
This page shows up if you search for general session storage
implementation advice (not specific to Django). It would be nice to learn
the details, if you can share them.
--
Ticket URL: <https://code.djangoproject.com/ticket/31412#comment:9>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/063.76005ffeb763ca321ffa45e733653894%40djangoproject.com.
