You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Would it be possible to have the rulesets on a server where clients could just periodically download them as they update? It seems like it would eliminate the problem of having to wait for an entirely new version of the extension before a site with a problem could be fixed. Have it more along the lines of an Adblock Plus subscription in that aspect.
We've definitely considered this strongly, and a GSoC participant last year produced an implementation for Firefox: #437. In the end I decided that, since releasing rulesets requires the same degree of care in signing that releasing the extension does, it's simpler to keep the current system where the extension is bundled with its rules. For instance, unbundling the rules would not actually allow daily updates to the rulesets, because we would have to manually sign those updates. I may wind up reconsidering in the future, depending on how onerous the new AMO release process becomes.
Why would the rules have to be signed by AMO? Extensions like AdBlock, uBlock and so on, can download their lists. Aren't the rules simple xml files? And xml is just plain text, just like the filter lists that uBlock or AdBlock use.
@rugk has it right. HTTPS Everywhere can rewrite any URL to any other URL, which would be a dangerous capability if someone was able to inject a bad ruleset into it. AdBlock and uBlock don't have to worry as much because they only block, not rewrite.
But the rules come from a https site (-> eff.org) with a valid certificate and they are checked beforehand (pull request here on Github). It's not like they come from some obscure unencrypted external site like http://wwrsdfsfgr5.verycooldownloadsite154.com
Activity
rugk commentedon Aug 19, 2015
Nice idea. 👍
jsha commentedon Aug 19, 2015
We've definitely considered this strongly, and a GSoC participant last year produced an implementation for Firefox: #437. In the end I decided that, since releasing rulesets requires the same degree of care in signing that releasing the extension does, it's simpler to keep the current system where the extension is bundled with its rules. For instance, unbundling the rules would not actually allow daily updates to the rulesets, because we would have to manually sign those updates. I may wind up reconsidering in the future, depending on how onerous the new AMO release process becomes.
Closing as a duplicate of #437.
foobar13373 commentedon Aug 22, 2015
Why would the rules have to be signed by AMO? Extensions like AdBlock, uBlock and so on, can download their lists. Aren't the rules simple xml files? And xml is just plain text, just like the filter lists that uBlock or AdBlock use.
rugk commentedon Aug 22, 2015
I don't think they have to be signed by AMO, but they would need a signature so that HTTPSE can verify they are genuine.
jsha commentedon Aug 22, 2015
@rugk has it right. HTTPS Everywhere can rewrite any URL to any other URL, which would be a dangerous capability if someone was able to inject a bad ruleset into it. AdBlock and uBlock don't have to worry as much because they only block, not rewrite.
foobar13373 commentedon Aug 22, 2015
But the rules come from a https site (-> eff.org) with a valid certificate and they are checked beforehand (pull request here on Github). It's not like they come from some obscure unencrypted external site like http://wwrsdfsfgr5.verycooldownloadsite154.com
semenko commentedon Dec 17, 2015
Closed per above as duplicate of #437