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

Maxim Nazarenko nz.phone at mail.ru
Tue Jun 10 02:46:26 PDT 2014

On 9 June 2014 20:57, Yan Zhu <yan at eff.org> wrote:
> On 06/09/2014 09:50 AM, Seth David Schoen wrote:
> > Does that mean that you can't update to a new ruleset release without
> > first updating to the corresponding extension release version?
> >
> We decided in IRC last week that this would be the desired default
> 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.
Second that. In fact, the ruleset needn't be forward compatible, i.e the
current extension doesn't need to understand old ruleset formats.

I strongly suggest having db_version field (which is bumped every time the
ruleset _format_ is changed) for this purpose.

Best regards,
Maxim Nazarenko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20140610/4f05897d/attachment.html>

More information about the HTTPS-Everywhere mailing list