Avoid to be easily the target of the HTTPS BREACH vulnerability.
Some of these mitigations may protect entire applications, while others may only protect individual web pages. 1. Disable HTTP compression. (1) 2. Separate the secrets from the user input. (2) 3. Randomize the secrets in each client request. -> Done! 4. Mask secrets (effectively randomizing by XORing with a random secret per request). -> Done! 5. Protect web pages from CSRF attacks. 6. Obfuscate the length of web responses by adding random amounts of arbitrary bytes. -> Done!
(1) I do not recommand this because of lack of performance, at least, but you can do it yourself in you PHP.ini or .htaccess, google "how to disable http gzip compression" (2) Can't do this in WordPress.
Install this plugin and be protected as much as we can do in WordPress.
Requires: 3.9 or higher
Compatible up to: 4.3.6
Last Updated: 1 year ago
Active Installs: 500+
0 of 1 support threads in the last two months have been marked resolved.
Got something to say? Need help?