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

[tor-bugs] #28848 [Obfuscation/Snowflake]: Document Snowflake broker implementation



#28848: Document Snowflake broker implementation
---------------------------------------+------------------------------
     Reporter:  ahf                    |      Owner:  (none)
         Type:  project                |     Status:  new
     Priority:  Medium                 |  Milestone:  Tor: unspecified
    Component:  Obfuscation/Snowflake  |    Version:  Tor: unspecified
     Severity:  Normal                 |   Keywords:
Actual Points:                         |  Parent ID:
       Points:                         |   Reviewer:
      Sponsor:  Sponsor19              |
---------------------------------------+------------------------------
 We should document how the current Snowflake implementation distributes
 Snowflake proxies to clients that is in need of them.

 Once we have specified how the current implementation works, we should
 figure out if there are things we would like to change before we can start
 shipping Snowflake in an alpha state to users.

 1) Look at broker code in the Snowflake repository.
 2) Document current behavior with long-polling clients waiting to get
 handed a proxy.
 3) Let's discuss if this design have any weaknesses we would like to
 address.

 One weakness here could be that currently the broker nor client DOES NOT
 pass information about which bridge/relay to connect to, but this
 bridge/relay host is hardcoded in both the Go and JS proxy code.

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