-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 16.04.2013 22:37, Moritz Bartl wrote:
On 16.04.2013 22:27, Roman Mamedov wrote:
Also, obfsproxy was rewritten in Python and it now supports a new pluggable transport called 'obfs3' which works even in China [2].
I wish this sort of functionality was integrated directly into tor. I am not up for installing and configuring an extra piece of Python software on my bridges, and it doesn't help that it isn't even present in Debian (only version 0.1.4 is there, which I guess is not obfs "3" that you now promote).
If you have deb.torproject.org as apt repository source, which is also the recommended way to get and keep Tor up to date, you can simply apt-get it.
Don't confuse the version number of Obfsproxy with supported transport protocols. Obfsproxy is a software that currently supports the "obfs2" and "obfs3" protocols, and is at version 0.2.1-2. It is likely that in the future support for more protocols will be added.
Does it make sense to launch an Obfsproxy on a IP already running a relay node? If yes, can I run it in the same tor session? What options do I need to activate?
I added the SoftwareTransportPlugins to my configuration and upon rehashing it showed it listened to two more ports: 22:43:39 [NOTICE] Registered server transport 'obfs2' at '0.0.0.0:47533' 22:43:39 [NOTICE] Registered server transport 'obfs3' at '0.0.0.0:42580'
I however did not yet add "BridgeRelay 1" because I don't know how that affects relay functionality.
Where do I go from here?
Martin Weinelt