#19324: invalid session keys cause unnecessary empty records in django_session
table
----------------------------------+------------------------------------
Reporter: liangrubo@… | Owner: nobody
Type: Bug | Status: closed
Component: contrib.sessions | Version: 1.4
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"df049ed77a4db67e45db5679bfc76a85d2a26680" df049ed]:
{{{
#!CommitTicketReference repository=""
revision="df049ed77a4db67e45db5679bfc76a85d2a26680"
Fixed #19324 -- Avoided creating a session record when loading the
session.
The session record is now only created if/when the session is modified.
This
prevents a potential DoS via creation of many empty session records.
This is a security fix; disclosure to follow shortly.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19324#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/077.423ed256adf33a428b7c727952055e2c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
