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

Re: [tor-bugs] #1035 [Tor Relay]: Relay on dynamic IP marked as stable and guard

#1035: Relay on dynamic IP marked as stable and guard
------------------------------+---------------------------------------------
        Reporter:  rudis      |        Owner:  Sebastian         
            Type:  defect     |       Status:  needs_review      
        Priority:  minor      |    Milestone:  Tor: 0.2.2.x-final
       Component:  Tor Relay  |      Version:  0.2.0.35          
      Resolution:  None       |     Keywords:                    
          Parent:             |       Points:                    
Actualpointsdone:             |   Pointsdone:                    
    Actualpoints:             |  
------------------------------+---------------------------------------------

Comment(by arma):

 Replying to [comment:25 Sebastian]:
 > Replying to [comment:24 arma]:
 > > As for Sebastian's idea of omitting the log line entirely for the
 bridge authority, check out #1117 -- we'll want log lines like this when
 trying to sort out that bug.
 >
 > I copied this approach from dirserv_orconn_tls_done() where we also
 don't log some things when we are a bridge authority. Maybe that will need
 fixing too when this is resolved.

 Ah. Go back and read that function again -- it does the opposite of what
 you think.
 {{{
       if (!bridge_auth || ri->purpose == ROUTER_PURPOSE_BRIDGE) {
 }}}
 means "if you're a bridge authority, only do this for descriptors with
 purpose bridge." Basically that means this function, if you're a bridge
 authority, logs and remembers reachability info only about bridges.

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