Re: [tor-bugs] #29454 [HTTPS Everywhere/EFF-HTTPS Everywhere]: Updates of HTTPS-Everywhere we ship do not seem to update the rulesets

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#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 gk):

 Replying to [comment:6 legind]:
 > > Okay, so the item is meant to display the last date when those
 rulesets got *fetched*? Or is it meant to show the version of the
 currently *active* rulesets? My intuition (and that of the user who
 reported that bug) is the latter, because that's what I as a user care
 about. It seems to me then that the item should not "lie" to the user
 regardless whether the check on start-up is succeeding or not (it might in
 fact even fail outside of Tor Browser/unrelated to it for various
 reasons).
 >
 > Yes, it's the latter.  I don't quite understand your point about the
 extension lieing to the user.  If the rulesets have been downloaded and
 applied, it displays it.  If not, it will not display the ruleset line.

 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...

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29454#comment:7>
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