[tor-bugs] #4927 [Tor bundles/installation]: Prepare a Pluggable Transports Bundle
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Fri Feb 10 04:46:28 UTC 2012
#4927: Prepare a Pluggable Transports Bundle
--------------------------------------+-------------------------------------
Reporter: asn | Owner: erinn
Type: task | Status: new
Priority: normal | Milestone:
Component: Tor bundles/installation | Version:
Keywords: | Parent:
Points: | Actualpoints:
--------------------------------------+-------------------------------------
Comment(by rransom):
Replying to [comment:6 rransom]:
> Replying to [comment:5 asn]:
> > This is how I made a PTTB:
> >
> > I took the current TBB off
> > https://www.torproject.org/download/download-easy.html.en:
> >
> > I replaced ./App/tor with a tor-0.2.3.11.
> >
> > I copied an obfsproxy binary to ./App/.
> >
> > I added these lines in ./Data/Tor/torrc:
> > {{{
> > UseBridges 1
> > Bridge obfs2 192.0.2.1:42666
> > ClientTransportPlugin obfs2 exec ./App/obfsproxy --managed
> > }}}
> >
> > Of course, `192.0.2.1:42666` was an actual obfs2'ed bridge address.
>
> This was on Linux; for Windows, we have an obfsproxy binary (thanks to
Sebastian), we have Tor 0.2.3.10-alpha binaries in packages in
www.tpo/dist/ , and we need someone to test this process.
IT WORKS!!! Microsoft's screwy incompatible APIs for spawning and
controlling subprocesses couldn't stop us!
(I used Tor 0.2.3.10-alpha binaries from the ‘expert bundle’ `tor-0.2.3.10
-alpha-win32-1.exe` , and I copied only Sebastian's obfsproxy.exe into the
App/ directory because there was already a libeay32.dll there. The only
change I made to asn's torrc lines was to use a real obfsproxy address; I
didn't need to Windows-ize “`./App/obfsproxy`”.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4927#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list