Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
the act of compression reduces the size of the file(s) being compressed by encoding information and eliminating statistical redundancy.
1
vote
Can BREACH be thwarted by simply adding a sort of "salt" into the page being compressed?
The idea behind BREACH (and compression oracles in general) is that the plaintext (and therefore the ciphertext) will be slightly shorter if the attacker guesses the next byte of the secret token correctly …