[HTTPS-Everywhere] Ruleset Changes Without Restart

[Yan Zhu]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Oh, also, if you want to change rulesets on the fly without
restarting, I think this would work:

1. Open up the HTTPS Everywhere directory in your Firefox profile (on
my Linux machine, it's at
~/.mozilla/firefox/PROFILE_NAME/extensions/https-everywhere at eff.org/.

2. cd into this directory and edit
./chrome/content/rules/default.rulesets. (Since this file is minified
xml and difficult to read, a better way is to git-clone HTTPS
Everywhere, change the xml rule file in the ./chrome/content/rules
directory, run ./makexpi.sh, and copy-and-paste the new
./chrome/content/rules/default.rulesets file from the git directory
into your Firefox profile directory.)

3. In Firefox, toggle one of the previously-mentioned prefs in
about:config to force ruleset re-initialization.

- -Yan

On 01/28/2014 04:55 PM, Yan Zhu wrote:
> Not sure if I understand the question in this thread, but the
> rulesets get reloaded when with a call to HTTPSRules.init(). We
> call this in a couple places:
> 
> 1. at startup 2. when the
> extensions.https_everywhere.enable_mixed_rulesets pref is toggled 
> 3. when security.mixed_content.block_active_content is toggled
> 
> So if you want to force-reload the rulesets in Firefox without 
> restarting, go to about:config and toggle one of those preferences
> twice.
> 
> -Yan
> 
> On 01/28/2014 02:29 PM, Claudio Moretti wrote:
>> On Tue, Jan 28, 2014 at 10:37 AM, Drake, Brian 
>> <brian at drakefamily.tk <mailto:brian at drakefamily.tk>> wrote:
> 
>> I?m only using stable versions for now (but when I?m working on 
>> rules, I do check the Atlas and/or Git for the latest rules).
> 
>> I?m not sure whether I we?re talking about the same thing here. I
>>  can enable or disable rulesets on the fly just fine, but
>> changing the rulesets themselves (that is, changing the XML files
>> in the HTTPSEverywhereUserRules folder, or deleting or adding
>> such files) requires a restart.
> 
> 
>> Oh, sorry: I misunderstood. I believe the problem may lie in the 
>> fact that rules are loaded when the extension starts (?) so it's 
>> necessary to restart Firefox before the new/edited rules are 
>> recognized.
> 
>> There is no obvious way around that; it may be possible to
>> relaunch the extension loading procedure, but I have no idea if
>> and how it can be done.
> 
>> I believe there is a reason why it's not possible to load rules
>> on the fly (which is what's causing your issue) but I'm not
>> sure; maybe Peter or Yan?
> 
>> P.S. I took a look at components/HTTPSEverywhere.js, it seems
>> just a matter of having a trigger or (maybe better) a button that
>> calls HTTPSRules.init()
> 
> 
>> _______________________________________________ HTTPS-Everywhere 
>> mailing list HTTPS-Everywhere at lists.eff.org 
>> https://lists.eff.org/mailman/listinfo/https-everywhere
> 
> 
> _______________________________________________ HTTPS-Everywhere
> mailing list HTTPS-Everywhere at lists.eff.org 
> https://lists.eff.org/mailman/listinfo/https-everywhere
> 

- -- 
Yan Zhu                           yan at eff.org
Technologist                      Tel  +1 415 436 9333 x134
Electronic Frontier Foundation    Fax  +1 415 436 9993
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJS6FMyAAoJENC7YDZD/dnsT2cH/0peJLmTXyVRncOnWvkAuboQ
OEf6aVvwT31wsXIizN9a+777YnYyAjxmbOYCtR0jJrUEWQ90gwr+/8rax09FYx8H
dJEHN4jRu8U7uqCeyUDVD/c+b+GMwR9QR7aj9yARa/8LmKMxxKXia3NzoiOhqeX2
+lEspMjPfbjRCKtOJTOean0TLAb0qn+ARM64P7+z3qyKWFXOEp/7ipVmo0JZjLC9
88Akphn1F+ASWlWPbWBft8c2oPxaDTnkohxdnXJacH3hzzG0dZxksWiBmibwR7jO
ovR1bxlo7J0qKq2kdaOojDvLm3x/n267zLTgbwwnjNHjg6z236hj2orkF25bGN4=
=R7Vu
-----END PGP SIGNATURE-----