[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #29454 [HTTPS Everywhere/EFF-HTTPS Everywhere]: Updates of HTTPS-Everywhere we ship do not seem to update the rulesets
#29454: Updates of HTTPS-Everywhere we ship do not seem to update the rulesets
-------------------------------------------------+-------------------------
Reporter: gk | Owner: legind
Type: defect | Status:
| needs_information
Priority: Medium | Milestone:
Component: HTTPS Everywhere/EFF-HTTPS | Version:
Everywhere |
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by legind):
> Yes, but lying in the sense that the date is wrong as in the bug report.
The user opened an old Tor Browser, updated and was confused that the *old
date* was still shown in the display suggesting that the rules from that
date were used while the update brought a new HTTPS-Everywhere version
with the new rules. I think the expected behavior would be: show the date
of applied rulesets either those that got downloaded (as is the case now)
OR those that we got by a new HTTPS Everywhere version (which is not
happening right now). The request on start-up might not get through for
whatever reason...
To avoid the problem of old rulesets still applying even when a new
extension version is released, the simplest thing to do is probably to
just clear the out-of-band rulesets from storage upon first load of any
new version. This will ensure that the extension-bundled rulesets are
used upon each extension upgrade. How does this sound?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29454#comment:8>
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