#20869: Prevent repetitive output to counter BREACH-type attacks
-------------------------------+--------------------------------------
Reporter: patrys | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.csrf | Version: 1.5
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by tagrain@…):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
"Instead of delivering the credential as a 32-byte string, it should be
delivered as a 64-byte string. The first 32 bytes are a one-time pad, and
the second 32 bytes are encoded using the XOR algorithm between the pad
and the "real" token."
[https://github.com/rails/rails/pull/11729] via
[http://arstechnica.com/security/2013/08/how-do-you-stop-https-defeating-
breach-attacks-let-us-count-the-ways/ Ars Technica]
--
Ticket URL: <https://code.djangoproject.com/ticket/20869#comment:1>
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/064.df1e01c3f486d54be5075037a3910216%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.