Hello all,
I just tagged the obfsclient v0.0.1 (Release)
Download at: https://github.com/Yawning/obfsclient/releases/tag/v0.0.1
Major changes since 0.0.1-rc2:
* Invalid padding lengths in obfs3/ScrambleSuit handshakes are now correctly handled. * Handshake timeout is now set to a random interval between 60 and 120 seconds. * The ScrambleSuit probability distributions are now closer to what obfsproxy generates. * "--version" will now cause obfsclient to print the version and exit. * Various code cleanups.
Some notes about ScrambleSuit:
* I reverted the "workaround" I had for bug #11100, so Session Ticket handshakes to bridges running obfsproxy 0.2.6 will fail if they have been running long enough to trigger the bug condition. * Actual protocol behavior is closer to obfsproxy than my previous releases, but still not identical to 0.2.7. the next obfsproxy release will close the difference further.
Hopefully it is of some use to people.
Special thanks to Fabian Keil for help testing and fixing the various release candidates.
Questions, comments, feedback appreciated as always,
Yawning Angel yawning@schwanenlied.me wrote:
I just tagged the obfsclient v0.0.1 (Release)
Download at: https://github.com/Yawning/obfsclient/releases/tag/v0.0.1
[...]
Special thanks to Fabian Keil for help testing and fixing the various release candidates.
My pleasure. Unfortunately I apparently missed one issue on FreeBSD 8.4: https://redports.org/~fk/20140317110212-48719-187908/obfsclient-0.0.1.log
When I tested rc2 with Redports the 8.4 build systems had network problems and thus this might not be a new problem: https://redports.org/buildarchive/20140302115957-67062/
The first rc worked on 8.4, though: https://redports.org/buildarchive/20140227100527-33378/
Fabian
On Mon, 17 Mar 2014 13:26:25 +0100 Fabian Keil freebsd-listen@fabiankeil.de wrote:
My pleasure. Unfortunately I apparently missed one issue on FreeBSD 8.4: https://redports.org/~fk/20140317110212-48719-187908/obfsclient-0.0.1.log
Ah, that's a easy fix. FreeBSD 8.x's sys/cdefs.h doesn't define __STDC_LIMIT_MACROS when the compiler is using C++11, so the limit macros aren't getting defined when I pull in cstdint.
Fixed in: 5ab2988bdd390cdf557b4fd971dcd64380dd8ab5
When I tested rc2 with Redports the 8.4 build systems had network problems and thus this might not be a new problem: https://redports.org/buildarchive/20140302115957-67062/
It's code I changed for rc2. No biggie.
I don't think that the build fixes for Darwin/FreeBSD warrant tagging 0.0.2 on their own, but it should be easy to work around in the port package (it's a minor tweak to CXXFLAGS if the host is < FreeBSD 9.1).
Thanks!
Yawning Angel yawning@schwanenlied.me wrote:
On Mon, 17 Mar 2014 13:26:25 +0100 Fabian Keil freebsd-listen@fabiankeil.de wrote:
My pleasure. Unfortunately I apparently missed one issue on FreeBSD 8.4: https://redports.org/~fk/20140317110212-48719-187908/obfsclient-0.0.1.log
Ah, that's a easy fix. FreeBSD 8.x's sys/cdefs.h doesn't define __STDC_LIMIT_MACROS when the compiler is using C++11, so the limit macros aren't getting defined when I pull in cstdint.
Fixed in: 5ab2988bdd390cdf557b4fd971dcd64380dd8ab5
Thanks.
I just submitted the FreeBSD ports for liballium and obfclient: http://www.freebsd.org/cgi/query-pr.cgi?pr=187926 http://www.freebsd.org/cgi/query-pr.cgi?pr=187926
Fabian
Fabian Keil freebsd-listen@fabiankeil.de wrote:
I just submitted the FreeBSD ports for liballium and obfclient:
FYI, the ports have been committed on Saturday: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=4055628+0+/usr/local/www/db/te...
Fabian
-
Fabian Keil -
Yawning Angel