#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: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+----------------------------------------
Comment (by deprince@…):
B is a good point, but easy to protect against. The PRNG can be keyed
from the content's hash. This will make the compression deterministic on
a per string basis, so averaging thousands of calls for a specific
parameter won't betray the actual size it would have encoded to without a
random sprinkling of flush calls. I'm modifying breach buster to
consider this right now.
As for A, I guess if you want to use another project's content encoder
you're on your own. Yes, some people use the broken GzipEncoder in nginx
:-) Lets solve Django's problem and tell people "use our gzip
knucklehead!"
--
Ticket URL: <https://code.djangoproject.com/ticket/20869#comment:20>
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.85d84a607d909ae9d1ca441e63e9f5b0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
