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

[Tor Bug Tracker & Wiki]

#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 rransom):

 Replying to [comment:2 arma]:
 > Messy issue number 2: should we still do this address rewriting if we
 got the descriptor from the bridge authority? After all, one of the
 features we talk about is being able to 'follow' a bridge on a dynamic IP
 address from day to day, so long as you can still reach the bridge
 authority. Does that mean we should only do the rewriting when we got the
 descriptor from a direct request, and leave the address:port alone when we
 learned it from the directory authority?

 Add a router descriptor line `static-bridge` to dir-spec, and a torrc
 option to put `static-bridge` in a bridge's descriptor.  Non-bridge
 directory authorities should reject descriptors containing `static-
 bridge`; clients should ignore the IP address and port listed in a
 `@purpose bridge` descriptor containing a `static-bridge` line, and never
 ask a bridge authority for an update of a descriptor containing a `static-
 bridge` line.

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