Yawning Angel: On Mon, 16 Feb 2015 10:30:57 +0000 eliaz eliaz@riseup.net wrote:
s I read it, the tor browser bundle 3.x FAQ [1] implies that bridges on windows can use only obfs3 of the provided pluggable transports. Can someone let me know if this is correct?
Huh? What does a old browser bundle FAQ have to do with running bridges on windows?
My apologies if my original query led you astray. It was only about the documentation being less helpful to windows users than it could be:
The FAQ I referenced includes information about Tor Browser 3.x, but only mentions obfs3:
If you've installed Obfsproxy, you'll need to add one more line:
ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
I went to that FAQ after not being able to incorporate any other transport lines into torrc for a windows implementation of the browser by using information in torrc-defaults. Tor documentation often leaves windows users (well, me at least) to figure out for ourselves by way of tedious experiments whether it applies generally, or only to Unix implementations. This was the case in torrc-defaults, which is what led me to wonder whether I had made a mistake when attempting to write the lines into torrc or if indeed the lines, except for obfs3, were inapplicable in windows.
The obfs3 line (as described in torrc-defaults) works fine, but torrc won't even accept obfs2, let alone fteproxy or flashproxy.
No one should use obfs2 for anything, it's deprecated.
Yeah, I know that. I was just illustrating another case where torrc unexpectedly refused to accept a line.
Would torrc in windows accept obfs4 ?
If you have an obfs4proxy binary compiled for windows, you can run an obfs4 bridge on windows (as well as any of the other transports supported by obfs4proxy, which is currently obfs2/obfs3).
Above my pay grade, sorry. I'll get around to it one of these days.
I'm not really understanding the question...
HTH - eliaz