Re: [tor-talk] Tor bridges not working

[Sherief Alaa <sheriefalaa.w@xxxxxxxxx>]

On Sat, Dec 7, 2013 at 6:18 PM, Shashwat Kumar <shashwatkmr.001@xxxxxxxxx>wrote:

> My institute has proxy server to connect to the internet. They have
> restricted few sites here as well as torrents. I used tor to download the
> torrents.
>

Downloading .torrent files isn't an issue but if you forward all your
torrent client traffic through the Tor network then you are hurting the
network and your anonymity.


> For a few days, the institute has blocked tor network.
> After 10 % of bootstrapping, it reaches "establishing an encrypted
> directory connection" and stuck there. Messages log is as follows
>
> *Dec 07 21:45:55.110 [Notice] Tor v0.2.2.37 (git-fce6eb1c44e87bc2). This is
> experimental software. Do not rely on it for strong anonymity. (Running on
> Linux i686)*
> *Dec 07 21:45:55.118 [Notice] Initialized libevent version 2.0.19-stable
> using method epoll. Good.*
> *Dec 07 21:45:55.118 [Notice] Opening Socks listener on 127.0.0.1:0
> <http://127.0.0.1:0>*
> *Dec 07 21:45:55.118 [Notice] Socks listener listening on port 47954.*
> *Dec 07 21:45:55.118 [Notice] Opening Control listener on 127.0.0.1:0
> <http://127.0.0.1:0>*
> *Dec 07 21:45:55.118 [Notice] Control listener listening on port 35270.*
> *Dec 07 21:45:55.118 [Notice] Parsing GEOIP file ./Data/Tor/geoip.*
> *Dec 07 21:45:57.556 [Notice] Bootstrapped 5%: Connecting to directory
> server.*
> *Dec 07 21:45:57.557 [Notice] Bootstrapped 10%: Finishing handshake with
> directory server.*
> *Dec 07 21:45:57.572 [Warning] Tried connecting to router at
> 128.31.0.39:9101 <http://128.31.0.39:9101>, but identity key was not as
> expected: wanted 9695DFC35FFEB861329B9F1AB04C46397020CE31 but got
> B0E8B26991725D15AD3F3F8F48FE8462E00A9805.*
> *Dec 07 21:45:57.587 [Warning] Tried connecting to router at
> 128.31.0.39:9101 <http://128.31.0.39:9101>, but identity key was not as
> expected: wanted 9695DFC35FFEB861329B9F1AB04C46397020CE31 but got
> B0E8B26991725D15AD3F3F8F48FE8462E00A9805.*
>


First, your version is highly outdated, try to update from one of the
following mirrors:

https://www.torservers.net/mirrors/torproject.org/download/download.html.en
https://www.torproject.us/download/download.html.en
https://tor.myrl.net/download/download-easy.html.en
https://www.oignon.net/download/download-easy.html.en

It also seems that your institute's firewall is hijacking connections like
Cyberoam and Kaspersky.

See: https://trac.torproject.org/projects/tor/ticket/9601#comment:13



> I even used bridges and obfuscated bridges but nothing worked.
>
> The following message log is shown after I used bridges.
>
> *Dec 07 21:47:33.000 [Notice] Tor v0.2.2.37 (git-fce6eb1c44e87bc2). This is
> experimental software. Do not rely on it for strong anonymity. (Running on
> Linux i686)*
> *Dec 07 21:47:33.001 [Notice] Initialized libevent version 2.0.19-stable
> using method epoll. Good.*
> *Dec 07 21:47:33.001 [Notice] Opening Socks listener on 127.0.0.1:0
> <http://127.0.0.1:0>*
> *Dec 07 21:47:33.001 [Notice] Socks listener listening on port 49847.*
> *Dec 07 21:47:33.001 [Notice] Opening Control listener on 127.0.0.1:0
> <http://127.0.0.1:0>*
> *Dec 07 21:47:33.001 [Notice] Control listener listening on port 59295.*
> *Dec 07 21:47:35.431 [Notice] Bootstrapped 5%: Connecting to directory
> server.*
> *Dec 07 21:47:35.435 [Notice] Bootstrapped 10%: Finishing handshake with
> directory server.*
> *Dec 07 21:47:35.453 [Notice] Learned fingerprint
> B0E8B26991725D15AD3F3F8F48FE8462E00A9805 for bridge 67.224.39.177:9001
> <http://67.224.39.177:9001>*
> *Dec 07 21:47:35.453 [Notice] Bootstrapped 15%: Establishing an encrypted
> directory connection.*
> *Dec 07 21:48:05.797 [Warning] The https proxy sent back an unexpected
> status code 504 ("Gateway Timeout"). Closing.*
> *Dec 07 21:48:05.798 [Warning] Proxy Client: unable to connect to
> 188.34.47.59:443 <http://188.34.47.59:443>*
>
> I don't know why bridges are not working. Is this because I am behind a
> proxy server? Is there any way to make tor working? Thanks for any help.
>

Even if you download the pluggable transports bundle to use obfs3 bridges
you won't be able to input your proxy settings because the bundle doesn't
support it yet.

Your best bet is to use TBB 2.3.25-15 with a bridge on port 80.  (
37.139.9.131:80 I've set this bridge up for such situations.)


-- 
Sherief Alaa
pgp 0x8623B882
-- 
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk