#20869: Prevent repetitive output to counter BREACH-type attacks
-------------------------------+----------------------------------------
Reporter: patrys | Owner: adambrenecki
Type: Uncategorized | Status: assigned
Component: contrib.csrf | Version: 1.5
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+----------------------------------------
Comment (by lpomfrey@…):
Replying to [comment:17 chris@…]:
> This approach seems similar to that implemented in
https://github.com/csghormley/django-debreach. In django-debreach, the
token is AES-encrypted with a random key provided alongside it in the
response body. Note the version available through pip did not work for me
- see my fork until the issue gets resolved.
The issues mentioned have since been resolved, as have several others not
fixed in Chris' fork.
django-debreach also includes a middleware (and decorator in the latest
master at https://github.com/csghormley/django-debreach) to append a
random comment string to text/html responses, which should provide
additional protection against breach style attacks.
The use of AES vs. XOR is largely stylistic, both would provide the same
level of protection.
--
Ticket URL: <https://code.djangoproject.com/ticket/20869#comment:26>
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.e29d63eb46718f05641c00319ac8c568%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
