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

[Tor Bug Tracker & Wiki]

#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:     
---------------------------------+------------------------------------------

Comment(by nickm):

 I'd rather get to a situation where Tor exports some of its library as a
 .a or a .so, and lets things link against it.  Sticking X inside Y simply
 because X depends on part of Y is not really good software engineering.

 For now, I'd just copy stuff verbatim if you really need it.

 ...

 Also, this is to some extent a messaging/communication issue.  One of the
 goals of obfsproxy is to show other people, "Hey, we wrote this pluggable
 transport thing, and we want you to write transports too!"  Sticking one
 transport inside Tor would IMO send the message that it's the "official"
 transport, and that other transports should either try to get into the Tor
 source as well  (ick), or that other transports are not as welcome.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3496#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online