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

Re: [tor-bugs] #19728 [Core Tor/Tor]: Pick, and deploy, a new bridge authority



#19728: Pick, and deploy, a new bridge authority
--------------------------+------------------------------------
 Reporter:  arma          |          Owner:
     Type:  task          |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by teor):

 For the record, the bridge authority details that we hard-code in the Tor
 source code are:

 {{{
 "Tonga orport=443 bridge "
 "82.94.251.203:80 4A0C CD2D DC79 9508 3D73 F5D6 6710 0C8A 5831 F16D",
 }}}

 The bridge authority needs a stable IPv4, ports, and key.
 (The key isn't mentioned in the ticket description - it's implicit, but it
 does mean that we should pick one operator with key access, and stick with
 them.)

 There is no reason for us to hard-code an IPv6 address, as nothing needs
 to contact the bridge authority on IPv6.

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