#30314: Enable SESSION_COOKIE_SECURE by Default
-----------------------------------------+------------------------
Reporter: nstr10 | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 2.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-----------------------------------------+------------------------
Per the documentation, "Leaving this setting off isn’t a good idea because
an attacker could capture an unencrypted session cookie with a packet
sniffer and use the cookie to hijack the user’s session."
If it's not a good idea for this setting to be off, why is it off by
default? Seems backwards to me.
--
Ticket URL: <https://code.djangoproject.com/ticket/30314>
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/049.7d2a68c57614185e03203ef3d9d5791f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
