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

Re: [tor-bugs] #7549 [Flashproxy]: Facilitator should not give client registrations to Tor exits

#7549: Facilitator should not give client registrations to Tor exits
-------------------------+--------------------------------------------------
 Reporter:  dcf          |          Owner:  jct           
     Type:  enhancement  |         Status:  needs_revision
 Priority:  normal       |      Milestone:                
Component:  Flashproxy   |        Version:                
 Keywords:               |         Parent:                
   Points:               |   Actualpoints:                
-------------------------+--------------------------------------------------

Comment(by jct):

 The attached '''test.py''' has a proof of concept of a process connecting
 with a Tor instance through the Tor Control Protocol. Here the process is
 connecting to the Tor instance in order to ask for the router status info
 for all the routers that this Tor instance have an opinion about. Once the
 process is getting the list, it is filtering the list in order to only get
 the Tor Exit nodes (the good and the bad ones).

 The Tor instance configuration must be similar to the follow:
   * ControlPort 64000
   * HashedControlPassword
 16:17867273713930AB60BF206385EA5CFB1E71844AA6AE0F4DEFA3006579
   * SocksListenAddress 127.0.0.1
   * SocksPort 0

 The '''ControlPort''' is where the process must connect in order to ask
 for the routers status info through the Tor Control Protocol.

 The '''HashedControlPassword''' must have the salt hash for the password
 used by the process in order to authenticate with the Tor instance. This
 hash is generated running the following command (where the string '''aa'''
 is the password used by the process):
 {{{
  tor --hash-password aa
 }}}
 The '''SocksPort''' must be '0' in order to have a Tor instance with not
 listening ports (with the exception of the Control Port).

 If you are agree with the previous solution, then I'm implementing the
 exit daemon as a threaded TCP server that is communicating with a local
 Tor instance in that way.

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