[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #23764 [Core Tor/Tor]: hs-v3: No live consensus on client with a bridge



#23764: hs-v3: No live consensus on client with a bridge
-----------------------------+------------------------------------
 Reporter:  dgoulet          |          Owner:  dgoulet
     Type:  defect           |         Status:  needs_information
 Priority:  High             |      Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor     |        Version:
 Severity:  Normal           |     Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:
Parent ID:                   |         Points:
 Reviewer:                   |        Sponsor:
-----------------------------+------------------------------------

Comment (by asn):

 Hmm, I took another look here and drew the various diagrams and I did not
 find any cases where your suggestion causes problems. However, it's been a
 while since I last carefully thought about these reachability diagrams and
 I'm afraid whether I'm forgetting something. I'm also afraid because I
 remember a conscious decision for requiring a live consensus, but perhaps
 that was invalidated when we switched to 24hours overlap periods...

 I think your suggested change makes sense, but if we are to do it I think
 we need to implement the new cases in `test_reachability()` and
 `test_client_service_hsdir_set_sync()` since we are basically creating a
 few extra scenarios here that we should make sure we are handling
 gracefully. Also, I'd like to test the branch a few days on my tor browser
 using a bridge to make sure that nothing goes weird before merging
 upstream.

 Cheers!

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