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

Re: [tor-bugs] #5550 [Obfsproxy]: Discuss feasibility of a Python obfsproxy

#5550: Discuss feasibility of a Python obfsproxy
-----------------------+----------------------------------------------------
 Reporter:  karsten    |          Owner:          
     Type:  task       |         Status:  assigned
 Priority:  normal     |      Milestone:          
Component:  Obfsproxy  |        Version:          
 Keywords:             |         Parent:  #5549   
   Points:             |   Actualpoints:          
-----------------------+----------------------------------------------------

Comment(by karsten):

 Replying to [comment:2 asn]:
 > After discussing this issue in the dev meeting, we decided that the
 performance questions can be answered by creating a dummy pluggable
 transport proxy and doing stress tests on it.

 Oh great, sounds like a good portion of the suggested discussion has
 already taken place.

 So, regarding performance evaluation, what do we expect to be the
 performance bottleneck?  Is it handling hundreds of connections, doing
 crypto, or something else?  Is the plan to implement obfs2 in Python and
 comparing performance to the C obfsproxy, or something different?

 Is there already a ticket for this performance evaluation, or should I
 create one?  What's a reasonable deadline for this task (April 30?) and
 who would do the work?

 > This means that the current unanswered problem, is deployment in
 Windows. My understanding is that Nick is afraid that solutions like
 py2exe result in 30MB .exe files.
 >
 > I think we should find out what is our threshold for the size of a
 python binary (is 5MB okay?), and how big would a "pyobfsproxy" windows
 binary actually be in practice.

 Is there already a ticket for evaluating installer size?  If not, who
 would I assign a newly created ticket to and what would be a reasonable
 deadline (April 30?)?

 > This is a related thread in tor-dev by Arturo:
 > https://lists.torproject.org/pipermail/tor-dev/2012-March/003328.html

 Without reading that thread in detail, are there any other aspects that
 need discussion and/or evaluation with respect to "pyfsprxy?"

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