[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #1959 [Tor Client]: entry nodes marked bad if we don't have their descriptor when we parse the consensus
#1959: entry nodes marked bad if we don't have their descriptor when we parse the
consensus
------------------------+---------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: Tor: 0.2.2.x-final
Component: Tor Client | Version:
Keywords: | Parent:
------------------------+---------------------------------------------------
Comment(by arma):
There is more to come, alas.
I think we're going to need to do an "optimistically retrying" deal with
entrynodes too, where if all your entrynodes are down but you get a socks
request you put them all up again just in case.
I had a case where I configured one entrynode, and a single circuit
attempt to it timed out (I don't know why it didn't answer my
create_fast), and then my Tor refused to make circuits for 3 hours until
it got the next consensus.
Oh, and the "optimistically retrying" thing doesn't work for bridges
either, which I think is related to some of these other vague bugs we have
open.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1959#comment:6>
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