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

Re: [tor-bugs] #7559 [Flashproxy]: Registration via indirect URL request

#7559: Registration via indirect URL request
------------------------+---------------------------------------------------
 Reporter:  dcf         |          Owner:  aallai        
     Type:  project     |         Status:  needs_revision
 Priority:  normal      |      Milestone:                
Component:  Flashproxy  |        Version:                
 Keywords:              |         Parent:                
   Points:              |   Actualpoints:                
------------------------+---------------------------------------------------
Changes (by dcf):

  * status:  needs_review => needs_revision


Comment:

 I decided that I want to architect the local facilitator programs
 differently, so this ticket is pending until I do that. This is how I
 expect it to break down:

  * `flashproxy-reg-daemon`: This is a daemon that reads base64-encoded
 encrypted registrations and passes them to the facilitator. Basically the
 common parts of `facilitator-email-poller` and `facilitator-reg-url` in a
 standalone daemon. This is the only process with access to private key
 material.
  * `flashproxy-reg`: Unprivileged process that reads a base64-encoded
 encrypted client registration and passes it to `flashproxy-reg-daemon`.
  * `flashproxy-email-poller`: Calls `flashproxy-reg` rather than doing its
 own decryption.
  * `flashproxy.cgi`: Calls `flashproxy-reg` rather than making a
 connection directly to `flashproxy-reg-daemon` (or `flashproxy-reg-url` as
 it is implemented so far in the ticket).

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