Hello all,
I just tagged obfsclient v0.0.2 (Release)
Download at: https://github.com/Yawning/obfsclient/archive/v0.0.2.tar.gz
This is mostly a bug fix release that addresses issues found in testing/actual use. The code is quite stable now, and I have been using it for all of my tor for approximately 2 weeks.
Changes since 0.0.1:
* Change the command line arguments to match the obfsproxy counterparts. This fixes issue #31. * Apply pushback between each side of the proxied connection to limit the amount of data that can be buffered. This fixes issue #3. * Use bufferevent_write_buffer to save allocating/copying in obfs2/obfs3. This fixes issue #24. * Fix assertions primarily seen on abrupt connection close by disabling all reads on transition into the various SOCKS5 FLUSHING states. * Cleaned up the logging, and log SOCKS5 assertions to the log file. * Send a TTL EXPIRED SOCKS5 error on connection timeouts. * Fixed an assertion that occurred if the outgoing connection immediately failed (Eg: Network interface being down). * Darwin build fixes, pointed out by Jeroen Massar. * FreeBSD 8.x/9.0 build fix, pointed out by Fabian Keil.
NB: Darwin builds require using liballium from git and not 0.0.1, due to a minor code change to a embedded dependency. It is also entirely possible that I broke this again via changes made since then, but I don't use Darwin at all.
Assuming there are no major bugs, I am hoping that 0.0.3 will be a feature release so the pace should be less hectic.
Questions, comments, feedback appreciated as always,
Yawning Angel yawning@schwanenlied.me wrote:
I just tagged obfsclient v0.0.2 (Release)
No known problems on FreeBSD so far. The ports PR has been updated: http://www.freebsd.org/cgi/query-pr.cgi?pr=187927
Fabian