Re: [tor-bugs] #9349 [Flashproxy]: flashproxy facilitator: Allow clients to specify transports

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#9349: flashproxy facilitator: Allow clients to specify transports
----------------------------+--------------------------
     Reporter:  asn         |      Owner:  dcf
         Type:  task        |     Status:  needs_review
     Priority:  normal      |  Milestone:
    Component:  Flashproxy  |    Version:
   Resolution:              |   Keywords:
Actual Points:              |  Parent ID:  #7167
       Points:              |
----------------------------+--------------------------

Comment (by dcf):

 Replying to [comment:34 infinity0]:
 > As I understand, there are 3 input sources to the facilitator:
 >
 > - GET / for proxy polls, going through facilitator.cgi
 > - POST / for cleartext client registrations, going through
 facilitator.cgi
 > - various rendezvous channels for encrypted client registrations, going
 through facilitator-reg-daemon
 >
 > The patch for the newline-based client registration syntax only changes
 facilitator-reg-daemon - so am I correct in thinking that facilitator.cgi
 also needs to be updated?

 Yes, you're right. All registrations go through facilitator-reg-daemon
 except for one special case: POST requests directly to facilitator.cgi.

 Moving the shared code to `fac.py` is fine with me.

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