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

2014-05-21 Thread 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, Re

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

2014-05-21 Thread Daniel Kahn Gillmor
On 05/20/2014 08:01 PM, Seth David Schoen wrote: > having a mechanism to let users know if they got the same update (whether > extension update or ruleset upset) that everyone else in the world got, > or at least whether everyone was _offered_ the same set of updates. > There are many ideas about t

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

2014-05-21 Thread Seth David Schoen
Daniel Kahn Gillmor writes: > This sounds very much like the idea of certificate transparency (CT), > but applied to source code or binaries. Have you considered raising > this with the CT folks? I'm also interested in seeing something like > this in other contexts (e.g. debian and other OS dist

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

2014-05-21 Thread Yan Zhu
On 05/21/2014 12:43 PM, Seth David Schoen wrote: > Daniel Kahn Gillmor writes: > >> This sounds very much like the idea of certificate transparency (CT), >> but applied to source code or binaries. Have you considered raising >> this with the CT folks? I'm also interested in seeing something like