[tor-bugs] #4187 [Core Tor/Tor]: A verified unverified-consensus should be renamed to cached-consensus

Tor Bug Tracker & Wiki blackhole at torproject.org
Sat Dec 23 17:19:44 UTC 2017


#4187: A verified unverified-consensus should be renamed to cached-consensus
-------------------------------------------------+-------------------------
 Reporter:  anonym                               |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  High                                 |      Milestone:  Tor:
                                                 |  unspecified
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.2.2.33
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-client, directory, rename, fs,   |  Actual Points:
  easy, 032-unreached                            |
Parent ID:                                       |         Points:  1
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by aruna1234):

 The code in networkstatus.c regarding
 networkstatus_set_current_consensus(), has an assignment, where it assigns
 a char buff whether it is 'cached consensus' or 'unverified consensus'.
 When Tor is suddenly started and it can verify the unverified consensus,
 maybe we can have a check placed checking whether 'buff' is unverified, if
 it is then we could change it to 'verified consensus'. Is the approach
 feasible?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4187#comment:13>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list