[tor-bugs] #3496 [Pluggable transport]: Make obfsproxy an actual part of tor ?

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#3496: Make obfsproxy an actual part of tor ?
---------------------------------+------------------------------------------
 Reporter:  asn                  |          Owner:  asn
     Type:  defect               |         Status:  new
 Priority:  normal               |      Milestone:     
Component:  Pluggable transport  |        Version:     
 Keywords:                       |         Parent:     
   Points:                       |   Actualpoints:     
---------------------------------+------------------------------------------
 obfsproxy is currently orthogonal to tor, as far as the code is concerned.
 (probably not that orthogonal, as far its use is concerned though)

 The thing is that I'll have to use tor functions in obfsproxy soon.
 I'll *need* the constant time memcmp(), I'll need free() and malloc()
 wrappers and I'll surely find some use for smartlists and other high-level
 stuff that tor provides (like file IO functions etc.).

 Instead of copying the whole src/common/ directory or heavily butchering
 src/common/ files so that they compile in obfsproxy, I could compile it as
 part of tor and have it reside in src/tools/ next to that tor-fw-helper.

 What's your opinion on this?

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