[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

To: undisclosed-recipients:;
Subject: Re: [tor-bugs] #1959 [Tor Client]: entry nodes marked bad if we don't have their descriptor when we parse the consensus
From: "Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>
Date: Wed, 29 Sep 2010 04:21:48 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Wed, 29 Sep 2010 00:21:57 -0400
In-reply-to: <044.0d312bcb7d198721aae3301983af6ae8@xxxxxxxxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-bugs>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: Tor bugs reporting list for trac <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
References: <044.0d312bcb7d198721aae3301983af6ae8@xxxxxxxxxxxxxx>
Reply-to: tor-assistants@xxxxxxxxxxxxxx
Sender: tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx

#1959: entry nodes marked bad if we don't have their descriptor when we parse the
consensus
------------------------+---------------------------------------------------
 Reporter:  arma        |       Owner:  arma              
     Type:  defect      |      Status:  assigned          
 Priority:  major       |   Milestone:  Tor: 0.2.2.x-final
Component:  Tor Client  |     Version:                    
 Keywords:              |      Parent:                    
------------------------+---------------------------------------------------

Comment(by arma):

 Replying to [comment:6 arma]:
 > 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.

 Should be fixed by #1882.

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

 Should be fixed by #1981.

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

References:
- [tor-bugs] #1959 [Tor Client]: entry nodes marked bad if we don't have their descriptor when we parse the consensus
  - From: Tor Bug Tracker & Wiki

Prev by Author: Re: [tor-bugs] #1882 [Tor Client]: "Failed to find node for hop 0 of our path. Discarding this circuit." log spam after guard went down
Next by Author: Re: [tor-bugs] #1366 [Tor Relay]: reload of valid but changed config causes abort
Previous by thread: Re: [tor-bugs] #1959 [Tor Client]: entry nodes marked bad if we don't have their descriptor when we parse the consensus
Next by thread: Re: [tor-bugs] #1959 [Tor Client]: entry nodes marked bad if we don't have their descriptor when we parse the consensus
Index(es):
- Author
- Thread