We can see that we configured the browser to connect through the proxy running on IP 127.0.0.1 and port 8118, which is exactly our Privoxy proxy. An example of Firefox configuration is presented on the next picture: The only missing step is to actually configure our browser to use the privoxy. Ok, the ports are in a listening state, which means all is well, because they can accept connections. This should open two ports, the 9050 one for tor and 8118 for privoxy. We won’t go into too much detail what the options mean right now, but we’ll describe the interesting configuration variables later. " > /etc/privoxy/configĪlso edit the /etc/tor/torrc and add the following lines: – privoxy: is used to connect our browser to Tor over HTTP proxy.Īdd the following line to the /etc/privoxy/config: – tor: is used to connect us to anonymous network over TCP. ![]() # echo "deb-src lucid main" > /etc/apt/sources.listĪt this point we should note what both of them are: # echo "deb lucid main" > /etc/apt/sources.list In case you’re using Ubuntu 10.04 – the same versions as Backtrack 5 R2 uses – then issue the commands presented below: First check on how to add the right repository to the sources list. ![]() When connecting via a SOCKS5 proxy, add to the configuration file:įor Proxy_IP, enter the IP address of the SOCKS5 proxy server, and replace the 8888 port with the desired one.We’ll assume that we use Ubuntu Linux distribution, but the steps are relevant for other distributions as well. Replace USER with your username and replace PASS with your password. If you need to enter a username and password on the proxy, then do it like this: If you are connecting via an HTTP proxy, then use the HTTPSProxy directive:Įnter the IP address of the proxy server as Proxy_IP, and replace port 8888 with the desired one. The following types of proxies are supported: Note that obfs4proxy.exe is not unloaded after stopping Tor and even after closing the console:Ĭ:\Tor\tor.exe -service install -options -f "C:\Tor\torrc" Notice the lines that talk about using the bridge:Īnd the line “ Bootstrapped 100%: Done” indicates that the connection was successful. Looks like client functionality is working. Jul 22 13:24:22.000 Tor has successfully opened a circuit. Jul 22 13:24:20.000 Bootstrapped 90%: Establishing a Tor circuit Jul 22 13:24:19.000 Bootstrapped 85%: Finishing handshake with first hop Jul 22 13:24:19.000 Bootstrapped 80%: Connecting to the Tor network Jul 22 13:24:12.000 Delaying directory fetches: Pluggable transport proxies still configuring Jul 22 13:24:12.000 Starting with guard context "bridges" Jul 22 13:24:09.844 Scheduler type KISTLite has been enabled. Jul 22 13:24:09.842 Path for GeoIPv6File () is relative and will resolve to C:\WINDOWS\system32\. Jul 22 13:24:09.842 Path for GeoIPFile () is relative and will resolve to C:\WINDOWS\system32\. Jul 22 13:24:09.812 Tor can't help you if you use it wrong! Learn how to be safe at Select obfs4 and click the Get Bridges Button: You need to get a list of current IP addresses. The required files are located in the \Browser\TorBrowser\Tor\PluggableTransports\ folder of your Tor Browser. ![]() I'll take the binaries from the Tor Browser. ![]() The obfs4 source code can be obtained here: Since not all bridge IP addresses are known, there is a chance to bypass Tor's blocking.įor this to work, you need obfs4 and a list of actual bridge IP addresses. The bridge is one of the types of repeaters. Repeaters can be used to bypass this blockage. They can use various approaches, for example, block connections to all IPs of the Tor network, or by analyzing traffic and, if it is identified as belonging to the Tor network, block it. It can be downloaded from this page of the official website.įrom the downloaded archive (in my case, the file is called tor-win32-0.4.5.8.zip), unpack the Tor folder to the root of the C drive.Ĭonfiguring Tor to Work Through a Bridge Relay If you want to install Tor as a service on Windows, then you need the Expert Bundle.
0 Comments
Leave a Reply. |