Make obfsproxy an actual part of tor ?
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?