HTTPS Everywhere EFF issueshttps://gitlab.torproject.org/tpo/applications/https-everywhere-eff/-/issues2022-08-15T21:59:32Zhttps://gitlab.torproject.org/tpo/applications/https-everywhere-eff/-/issues/5257Translate the Chrome port of HTTPS-E2022-08-15T21:59:32ZPeter EckersleyTranslate the Chrome port of HTTPS-EThe FF and Chrome builds should use the same translation sources. This probably means we need a script to parse the FF translation .dtds during the chrome build process, and write them out into whatever format Chrome uses for its transl...The FF and Chrome builds should use the same translation sources. This probably means we need a script to parse the FF translation .dtds during the chrome build process, and write them out into whatever format Chrome uses for its translations.https://gitlab.torproject.org/tpo/applications/https-everywhere-eff/-/issues/5224Allow rulesets to be different in Firefox and Chrome releases2020-06-27T14:15:15ZPeter EckersleyAllow rulesets to be different in Firefox and Chrome releasesWorking around#5196 is going to require a temporary divergence in the GoogleAPIs ruleset in order to work around a Chrome bug.
Right now I can think of two ways to do this. One is to add a new attribute to <rule> elements which specifi...Working around#5196 is going to require a temporary divergence in the GoogleAPIs ruleset in order to work around a Chrome bug.
Right now I can think of two ways to do this. One is to add a new attribute to <rule> elements which specifies that the only work on some platforms. Another is to build the Chrome releases from a different git branch.
The new rule element is probably slightly more elegant, and also slightly more work.Peter EckersleyPeter Eckersleyhttps://gitlab.torproject.org/tpo/applications/https-everywhere-eff/-/issues/4176Check that there are no holes left by the removal of nsIContentPolicy2020-06-27T14:15:20ZPeter EckersleyCheck that there are no holes left by the removal of nsIContentPolicySince this commit:
https://gitweb.torproject.org/https-everywhere.git/blobdiff/eb212b2e785b1760f976d2b7358a187f2adc82b1..445aa51a61fa2ec50998ac802c3d0c4261787929:/src/components/https-everywhere.js
To close legacy/trac#3882 , we should ...Since this commit:
https://gitweb.torproject.org/https-everywhere.git/blobdiff/eb212b2e785b1760f976d2b7358a187f2adc82b1..445aa51a61fa2ec50998ac802c3d0c4261787929:/src/components/https-everywhere.js
To close legacy/trac#3882 , we should run more tests to ensure that no HTTP requests are escaping redirection.
We have done a bit of this without plugins, but we should also perform more and with plugins. Methodology:
Run a wireshark capture with the BPF set to "port 80" (or a protocol-level equivalent?).
Do a lot of browsing.
Filter out the HTTP Request packets.
See if any of them should have been rewritten.Peter EckersleyPeter Eckersleyhttps://gitlab.torproject.org/tpo/applications/https-everywhere-eff/-/issues/3413Review HTTPS Everywhere Observatory Alpha2020-06-27T14:15:26ZMike PerryReview HTTPS Everywhere Observatory Alphapde has a branch he wants me to test and review.pde has a branch he wants me to test and review.Mike PerryMike Perryhttps://gitlab.torproject.org/tpo/applications/https-everywhere-eff/-/issues/1578Split off a development branch2020-06-27T14:15:35ZPeter EckersleySplit off a development branchNew features and rules will need to be tested by an appropriately sized population before they're pushed out to all of the users of this plugin.
We could achieve this by using an alternative update.rdf for people who are willing to be b...New features and rules will need to be tested by an appropriately sized population before they're pushed out to all of the users of this plugin.
We could achieve this by using an alternative update.rdf for people who are willing to be bleeding and edgy.Peter EckersleyPeter Eckersley