obfsproxy (0.2.6-2) unstable; urgency=low obfsproxy now supports a new obfsucation protocol named ScrambleSuit. The previous protocols did not require any form of authentication and were vulnerable to active probes. ScrambleSuit requires a shared secret instead. Tor bridges configuration should be updated to support the new protocol. Edit `/etc/tor/torrc`, and replace: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed with: ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed The “obfs2” protocol is known to be fingerprintable and is being phased out. -- Jérémy Bobbio Mon, 10 Feb 2014 18:19:55 +0100 obfsproxy (0.2.1-1) experimental; urgency=low obfsproxy now supports a new obfuscation protocol named “obfs3”. The command-line syntax also changed and `managed` should now be used instead of `--managed`. * Upgrading a bridge: Edit `/etc/tor/torrc` and replace: ServerTransportPlugin obfs2 exec /usr/bin/obfsproxy --managed with: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed * Upgrading a client: Edit `/etc/tor/torrc` and replace: ClientTransportPlugin obfs2 exec /usr/bin/obfsproxy --managed with: ClientTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed -- Jérémy Bobbio Thu, 28 Mar 2013 10:30:43 +0000