[HTTPS-Everywhere] Draft specification for file used to check for ruleset updates

Seth David Schoen schoen at eff.org
Mon Jun 9 14:43:32 PDT 2014

Yan Zhu writes:

> We decided in IRC last week that this would be the desired default behavior.
> In general, it would be difficult to guarantee that a new ruleset
> version is compatible with *all* previous extension versions. Ex: we
> introduce a new XML property, "hasKeyPins", or change the XML ruleset
> structure in a way that is not backwards-compatible past the previous
> extension release.

That's a convincing argument!

Seth Schoen  <schoen at eff.org>
Senior Staff Technologist                       https://www.eff.org/
Electronic Frontier Foundation                  https://www.eff.org/join
815 Eddy Street, San Francisco, CA  94109       +1 415 436 9333 x107

More information about the HTTPS-Everywhere mailing list