The Tor Project's official guide is available here. It has instructions on how to set up an obfs4 bridge for several platforms, including Debian and Ubuntu. Don't forget to make sure that your OR port and your obfs4 port must be publicly reachable. Tor automatically tests its OR port but it currently (as of August 2019) does not test its obfs4 port. You can ...
First you need to install obfsproxy package. Then configure torrc file like @user263485 said:
# This works for Ubuntu Linux, adjust the path according to your platform
ClientTransportPlugin obfs3, scramblesuit exec /usr/bin/obfsproxy managed
Bridge obfs3 <ip:port> <key>
To obtain obfs3 bridges visit BridgeDB (step 2) and ...
How to configure Tor and Obfsproxy:
According with this bug report:
... the obfsproxy permission error is triggered by the tor init script ( at least on debian/ubuntu ) because of tor apparmor wrong script (/etc/apparmor.d/...
The new meek pluggable transport — currently in beta stage — is likely to work as it employs the same tricks than GoAgent, a popular circumvention method in China.
Ready to use bundles are available to test it.
Open torrc file.
After first two comment lines which start with # add:
Bridge obfs3 IP-address:port Fingerprint of bridge
and save the file. For more information take a look at freebsd-ports
Update: Do not post the bridges you use in public. It make it easier to track you. This is how your torrc should look like:
# This file was generated by Tor; if ...
Great explanation, it helped me a lot. Like to add the following; These days I do not see a lot of obfs4 traffic yet. If you want to publish as an obfs3 AND obfs4 bridge relay you can change the line
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxy
You only need to install obfs4 as ...
I have solved this problem. Under Windows 7, the absolute path must be used for the obfs4proxy configuration in torrc-default; the relative path for obfs4proxy plugin doesn't work!
## obfs4proxy configuration
ClientTransportPlugin obfs2,obfs3,obfs4,scramblesuit exec E:\Tor Browser\Browser\TorBrowser\Tor\PluggableTransports\obfs4proxy
TOR cell size is 512 bytes but most TOR packets have size of 586
bytes. My question is that why there is such difference in size (74 bytes difference)?
The 586-byte packet being referenced in the papers is Tor's 512-byte cell wrapped in the headers of three different protocols: TLS, TCP, IP.
In my set up, using Wireshark, I'm seeing lots of outgoing ...
I confirm 100% obfs3 works as I'm using it right now. ( Instead meek does not work, maybe because it relay on Google )
You would need fresh obfs3 bridges, the one in the bundle are not working for me ...
... you can get them on the Tor page, the best option is to ask a friend to do it for you or use the mail service.
- Bridges -> https://bridges.torproject....
According to How to read our China usage graphs and Tor calls for help as its supply of bridges falters, the obfs3 plugin for obfsproxy is still effective in China. What's missing are enough bridges that are running obfs3 and associated software for reporting reliable measures for usage and effectiveness.
I have also read that the GFW may block or throttle ...
I have finally found a solution to this problem. For me, the offender was the /firstname.lastname@example.org file. I was directed by Tor ops to modify this file to include only the following after the "Hardening" comment:
Comment out or delete everything else and you will no longer get ...
obfsproxy should be setup inside of torrc if you wish to use it with tor, it shouldn't be executed seperately. The managed flag indicates that the opening process will be "managing" it, in this case the opening process is your shell and it's not providing the required configuration parameters.
The process for adding obfs3 bridges is outlined in this answer: ...
A program that wants to connect to obfsproxy must first
speak the Socks4 protocol with obfsproxy. obfsproxy also has to be started with the right Tor pluggable transport enviroment variables.
There is this project:
that handles Socks4 startup protocol and starting obfsproxy with the right ...
There doesn't appear to be available/packaged for FC/RH, however...
You could use the obfs4proxy binary packaged with Tor Browser by running.
gpg --recv-keys 0x4E2C6E8793298290
gpg --list-keys --fingerprint 0x4E2C6E8793298290
# Manually verify fingerprint ...
Bridges aren't published, they won't be used as exits but the reject policy won't cause any harm.
The config looks good and it should work.
I might be worth a few small changes though, they may not be relevant to your use case but...
Consider using obfs4 rather than obfs3 for the pluggable transport provider. It's what is currently recommended and it's ...
You should be able to build it natively, as per the README here or you can try to cross-compile from another architecture to armv5 using the method here.
go get -u github.com
go get git.torproject.org/pluggable-transports/obfs4.git/obfs4proxy
You should try pluggable transports, especially Meek and Obfs4. Of it won't help you, please post a torrc and error log here, I'll be able to help you further
UPDATE 13.1.2016 on your edit:
Try to use tor from Git - the latest version, Im using it. Also please paste a log from the very beginnig, i.e. with a shell cmd to execute a binary. Try to use my ...
obfs4 and obfs3, among others, are "pluggable transports", and the protocol they speak to Tor is well specified. You could write a program / script to implement that protocol in order to use any pluggable transport for your own purposes.
Shameless plug: I have written a Python 3 program that takes a pluggable transport binary and creates a standalone TCP ...
I used to have a similar problem as you. Now it is fixed for me, using the method described here:
obfs4proxy crash no apparent reason
Problem solved by change the relative path in the torrc-defaults to absolute path where the installation path insdead
Give me an example of what it should include:
This is an example torrc file:
DataDirectory C:\Documents and Settings\ron\Desktop\Tor\Data
# UseBridges 1
# bridge 126.96.36.199:9001
# bridge 188.8.131.52:444
# bridge 184.108.40.206:443
# ExitNodes 220.127.116.11/16
GeoIPFile C:\Documents and Settings\ron\Desktop\Tor\Data\Tor\...
The log says that Tor tries to connect to a bridge with obfs2. This variant of obfs is deprecated and probably the bridge doesn't offer it anymore. You can try if this bridge uses obfs3 with two ways:
If you're using the Tor Browser Bundle, just click on the green onion and select the last entry (network settings). On the next menu click on the last button (...
"Bridge at '18.104.22.168:47779' isn't reachable by our firewall policy." means that you have set your "ReachableAddresses" torrc option to tell Tor that it shouldn't even try to reach that address. Thus Tor is opting not to try to reach that bridge.
Perhaps you set ReachableAddresses using Tor Browser, by answering "yes" to the "Are you only able to ...
Links between Tor nodes are encrypted using TLS (on top of the telescoping onion routing circuit encryption) so the number of cells corresponding to each circuit is obscured from an external adversary. TLS also authenticates the link between nodes, to resist active attacks. It's not clear yet how to protect links better; padding might help but so far all the ...