[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2268 [EFF-HTTPS Everywhere]: https-everywhere no clobber option!
#2268: https-everywhere no clobber option!
-----------------------------------+----------------------------------------
Reporter: rosc2112 | Owner: pde
Type: defect | Status: closed
Priority: normal | Milestone:
Component: EFF-HTTPS Everywhere | Version:
Resolution: invalid | Keywords:
Parent: |
-----------------------------------+----------------------------------------
Changes (by rransom):
* status: new => closed
* resolution: => invalid
Comment:
Firefox replaces the contents of an extension's directory whenever it
updates the extension. There is nothing that the authors of HTTPS
Everywhere can do to prevent this.
If you are only adding new rules to HTTPS Everywhere, put your ruleset
files in the `HTTPSEverywhereUserRules` directory, which is not clobbered
when HTTPS Everywhere is updated or reinstalled.
If you are making other changes to HTTPS Everywhere, there are at least
three options:
* store your changes in a Git repository, use the provided Makefile to
build a new XPI, and install your XPIs manually;
* store your changes in another directory, install your modified
extension by copying the contents of your HTTPS Everywhere directory into
the Firefox HTTPS Everywhere extension directory, and ''never'' allow
Firefox to update HTTPS Everywhere; or
* store your changes in another directory, put a text file containing the
path to your HTTPS Everywhere directory in the Firefox extensions
directory, and ''never'' allow Firefox to update HTTPS Everywhere.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2268#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs