Re: [tor-bugs] #28614 [Core Tor/Tor]: Can't parse networkstatus consensus time

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

#28614: Can't parse networkstatus consensus time
-------------------------------------------------+-------------------------
 Reporter:  Vort                                 |          Owner:  nickm
     Type:  defect                               |         Status:
                                                 |  merge_ready
 Priority:  High                                 |      Milestone:  Tor:
                                                 |  0.4.0.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  040-rc-must, regression,             |  Actual Points:
  postfreeze-ok, tbb-needs                       |
Parent ID:                                       |         Points:
 Reviewer:  ahf                                  |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by watt):

 Replying to [comment:24 nickm]:
 > Replying to [comment:22 watt]:
 > > Replying to [comment:21 nickm]:
 > > > > Could we avoid that and just ask users to clear the old file if
 it's wrong?
 > > >
 > > > We could, but that would be inconvenience to the users, and it's
 best not to inconvenience users for a problem that we can fix.
 > > >
 > > > Not everybody is comfortable navigating inside folders and deleting
 stuff.
 > > No user intervention then. But adding more code to core tor just for
 transition to a new file format is not the best option. Will you remove it
 when tor is upgraded?
 >
 > Probably; would you like to open a ticket for that?  This code will be
 relevant until all earlier versions of Tor are obsolete, since people have
 any time between now and then to update.  Since 0.3.5.x is supported till
 2022, we shouldn't remove it before then.
 Usually such tickets are buried in the `Tor: unspecified` milestone. And
 it's almost impossible that somebody will remind us about it in 2022 :(
 The main drawback is that tor should do additional parsing again and again
 at runtime instead of one time deletion during update.

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