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

[Maxim Nazarenko]

Good afternoon,

Please see my suggestions at
https://gist.github.com/NovemberZulu/fbefa33fb90eba3fbcb8 -- no pull
requests for gists :( It also includes Seth's suggestion on the file
structure. I'll be happy to comment on suggested changes.

Best regards,
Maxim Nazarenko


On 21 May 2014 02:00, Red <redwire at riseup.net> wrote:

> Hello,
> I have been working on documenting a specification of the update.json
> file that will be used to provide information about the ruleset library
> released by eff.org.  Yan and I discussed some of the details regarding
> what kind of information this file will supply, how it will be
> retrieved, and how HTTPS Everywhere can check whether there is an update
> to the library of rulesets released available as well as verify the
> signature and hash of the database file containing the ruleset library.
>
> I've written my draft of the (hopefully not overly) simple specification
> for the contents of the update file and briefly explained how it will be
> used.  I posted the draft as a Gist on Github for anyone to read and
> comment on publicly: https://gist.github.com/redwire/2e1d8377ea58e43edb40
> Let me know if there is anything any of you feel should be better
> explained or modified.
>
> Cheers,
> Zack
>
>
> _______________________________________________
> HTTPS-Everywhere mailing list
> HTTPS-Everywhere at lists.eff.org
> https://lists.eff.org/mailman/listinfo/https-everywhere
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20140521/b68d35d6/attachment-0001.html>