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

Re: [tor-bugs] #3785 [Tor Relay]: Revise/refine proposal 118 and implement it

#3785: Revise/refine proposal 118 and implement it
-----------------------+----------------------------------------------------
 Reporter:  ln5        |          Owner:  nickm             
     Type:  task       |         Status:  accepted          
 Priority:  normal     |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Relay  |        Version:                    
 Keywords:             |         Parent:  #3563             
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------

Comment(by nickm):

 See branch prop186_hacking in my public repository for a partial
 implementation of the minimum needed to implement this, proposal #3787,
 and #3788 .

 I'm not putting this into "needs_review" yet, because there are lots more
 known problems to solve here.  But you can review it if you want!

 Let me copy-and-paste my caveats and notes from IRC:
 {{{
 22:59 < nickm> It implements the new options insofar as letting you bind
 on
                multiple orports.
 22:59 < nickm> It also migrates dirport and controlport to the new port
                configuration system because why not
 23:00 < nickm> It lets routerinfo_t support exactly one IPv6 address, as a
                stopgap measure.
 23:01 < nickm> It handles parsing and formatting such routerinfo_t
 instances
 }}}

 Additionally, since then, I added a commit so that bridges with an IPv6
 address will advertise it in their router descriptor (#3788)  .

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