On Tue, Feb 3, 2015 at 1:39 PM, Aymeric Augustin <[email protected]> wrote: > Le 3 févr. 2015 à 16:54, Jon Dufresne <[email protected]> a écrit : >> Assuming this MITM already has the correct CSRF value, what is >> stopping this MITM from adding a REFERER to the HTTPS request? > > While MITM of HTTP is trivial, MITM of HTTPS isn't possible (under Django's > security model, which doesn't account for government-level attacks, etc.) > > Back then, Facebook fixed Firesheep simply by enforcing HTTPS.
This was my thought on the issue too. If someone is successfully doing a MITM attack on your SSL sessions then CSRF is the least of your worries. Maybe the thought is that many Django sites mix HTTP and HTTPS session, and that the CSRF token would leak from the HTTP session. But ISTM that you could just use different tokens for HTTP and HTTPS. -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CAD4ANxVZP%3DyEHhXgGyFPPYqKGs79c9V4HfdvVvoVBwgnVzaDQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
