One thing I've been meaning to follow up on: The spec currently says " The ruleset database will be served as a ZIP file." I mentioned that Content-Encoding: gzip at the HTTP level would be simpler and offer similar compression. Yan's objection was that this could enable the BREACH attack. However, the BREACH attack only applies when there is both user-controllable content and secret content returned from a given URL. The ruleset database has neither.
_______________________________________________
HTTPS-Everywhere mailing list
[email protected]
https://lists.eff.org/mailman/listinfo/https-everywhere

Reply via email to