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

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

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

Comment (by dcf):

 Replying to [comment:8 asn]:
 > Thanks for the clarifications.
 >
 > BTW, `design.txt` -- which I changed -- onyly specifies the HTTP
 registration format, it doesn't specify the format of the email
 registration etc. Should I assume that the body of the POST, is the same
 as the body of the email (this seems to be the case in the code)?
 >
 > Also, what about the OSS registration? Should we also change this to be
 transport-aware? Is its format specified somewhere?

 Basically everything uses the format understood by `facilitator-reg-
 daemon`. This program listens on a socket and reads a base64-encoded
 ciphertext (See `Handler.handle` in `facilitator-reg-daemon`). Decrypted,
 the plaintext format appears to be newline-separated name-value pairs
 (check `find_client_addr`). I'm not sure why it's using this homebrew
 format and not www-url-encoded, which would be easier to handle with
 respect to escaping.

 `facilitator-reg-daemon` exists as a separate process for privilege
 separation reasons. It's the only program that has to be able to read the
 facilitator's private key. When the email or appspot helpers get their
 base64 blob, they just pass it straight to `facilitator-reg-daemon`. Check
 `url_reg` in `facilitator.cgi` for how appspot is handled and
 `handle_message` in `facilitator-email-poller` for how email is handled.

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