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

Re: [tor-bugs] #2510 [Tor Client]: bridge users who configure the non-canonical address of a bridge switch to its canonical address

To: undisclosed-recipients:;
Subject: Re: [tor-bugs] #2510 [Tor Client]: bridge users who configure the non-canonical address of a bridge switch to its canonical address
From: "Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>
Date: Tue, 08 Feb 2011 10:28:28 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Tue, 08 Feb 2011 05:28:38 -0500
In-reply-to: <044.098fef9bda32bb3f398986ea98683669@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.098fef9bda32bb3f398986ea98683669@xxxxxxxxxxxxxx>
Reply-to: tor-assistants@xxxxxxxxxxxxxx
Sender: tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx

#2510: bridge users who configure the non-canonical address of a bridge switch to
its canonical address
------------------------+---------------------------------------------------
 Reporter:  arma        |       Owner:                    
     Type:  defect      |      Status:  needs_review      
 Priority:  major       |   Milestone:  Tor: 0.2.2.x-final
Component:  Tor Client  |     Version:                    
 Keywords:              |      Points:                    
   Parent:              |  
------------------------+---------------------------------------------------

Comment(by arma):

 Replying to [comment:2 arma]:
 > The specific problem that issue number 1 causes is that when we start
 our Tor again, it reads in the descriptor for the bridge at 128.31.0.34,
 reads from its state file that a node with that fingerprint is a guard
 node, and tries to connect to it (I think this is a separate bug).

 Opened bug #2511 to handle that issue.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2510#comment:3>
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] #2510 [Tor Client]: bridge users who configure the non-canonical address of a bridge switch to its canonical address
  - From: Tor Bug Tracker & Wiki

Prev by Author: [tor-bugs] #2511 [Tor Client]: Tor will use an unconfigured bridge if it was a configured bridge last time you ran Tor
Next by Author: Re: [tor-bugs] #2408 [Tor Relay]: "PublishServerDescriptor hidserv" publishes a public relay descriptor
Previous by thread: Re: [tor-bugs] #2510 [Tor Client]: bridge users who configure the non-canonical address of a bridge switch to its canonical address
Next by thread: Re: [tor-bugs] #2510 [Tor Client]: bridge users who configure the non-canonical address of a bridge switch to its canonical address
Index(es):
- Author
- Thread