3 ms·
Interesting attack that uses the fact that when duplicate data is present in the returned packets, it will be compressed so will make the packet size smaller. T
by casca 13y ago
Interesting attack that uses the fact that when duplicate data is present in the returned packets, it will be compressed so will make the packet size smaller. This means that it's possible to quickly converge on secret session tokens.
The mitigation suggestions are all at the application level which will make fixes less likely as SSL/TLS is usually considered a security silver bullet.
- laumars 13y agoDisabling compression is at the server level rather than code level (and it's a real easy config change too). However I can see that being an unfavourable solution for some of the busier sites.
- cryptic 13y agoAdding a few random bytes to a response seems to be an easy fix and doesn't require compression being disabled.
- jmillikin 13y agoAdding a random amount of random bytes will not defeat the attack, it would only slightly increase the amount of time required by making the side channel noisier. Adding a fixed amount of random bytes will have no benefit at all.
- deleted 13y ago[deleted]
- beagle3 13y agoCan you quantify "slightly"?
- quizotic 13y agoNot following your assertion. Suppose the reported size was always a random epsilon larger than the actual size. Choose epsilon so that its small enough to benefit from compression and large enough to obscure the BREACH. Why doesn't that work?