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 | |
Results tagged with known-vulnerabilities
Search options not deleted
user 66010
A vulnerability which is known to the designers, implementers, or operators of the system, but has not been corrected.
1
vote
Can BREACH be thwarted by simply adding a sort of "salt" into the page being compressed?
add a random amount of random characters into the request body before GZipping it
This will slow down the attack, but not prevent it.
The idea behind BREACH (and compression oracles in general) …
- 248