2015-02-03 13:10 GMT+01:00 Tim Chase <django.us...@tim.thechases.com>:
> On 2015-02-03 10:31, Aymeric Augustin wrote: > > Your request boils down to "make Django's CSRF protection of HTTPS > > pages vulnerable to MITM attacks" which isn't acceptable. > > If you've got a MITM that can intercept HTTPS, is there any reason to > assume they aren't in a position to spoof DNS as well, rendering the > REFERER information immaterial? > We're talking about a MITM of an HTTP connection that is then used for posting a form over an HTTPS connection. Check the comment in the first message of this thread for details. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mWF5Mh_CE%3DjP8RdHUedxPSa59o4zkM%2B352Xc3iTgTRXFg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
