[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 dcf):

 Thank you for making this test. Your approach looks like a good one. I
 think it will be more effective if you use an existing library like Stem
 or TorCtl to interact with the control port.

 https://trac.torproject.org/projects/tor/wiki/doc/stem
 https://stem.readthedocs.org/en/latest/index.html

 http://fscked.org/projects/torctl

 I haven't used either of these, but perhaps there is a way to look up a
 relay by IP address, and then check its exit policy. If so, that is easy
 enough that it can happen in a blocking way within the facilitator, and
 there is no need for a separate daemon. If it is only possible to get a
 big list of relays all at once, then having a separate daemon might still
 make sense.

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