[tor-bugs] #15073 [Tor]: issue with establishing tor connection in linux

Tor Bug Tracker & Wiki blackhole at torproject.org
Sat Feb 28 08:07:53 UTC 2015


#15073: issue with establishing tor connection in linux
------------------------+----------------------------
     Reporter:  hsafe   |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:
    Component:  Tor     |    Version:  Tor: 0.2.5.10
   Resolution:          |   Keywords:  tor iran linux
Actual Points:          |  Parent ID:
       Points:          |
------------------------+----------------------------

Comment (by mrphs):

 Replying to [ticket:15073 hsafe]:

 > I am a user in Iran, running tor on a linux. Recently- more than a week-
 tor failed to establish connection to the tor network, messages as such:
 > Feb 28 09:41:51.000 [notice] Bootstrapped 25%: Loading networkstatus
 consensus
 > Feb 28 09:47:20.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no usable consensus.

 Have you tried (obfs) bridges?

 > I know that your first advise must be using the tor-browser but for the
 technical reason and ease of use and also torrifying everything outo f my
 linux I much prepfer to use tor as a daemon built in app in linux.

 Do you know about Tails? That's exactly what you're looking for, plus some
 more hardening and configs that you might not have even thought about.

 > I tried to troubleshoot all the possible ways including a new kvm and
 setting tor in it to observe the connection establishment and if that is
 suppressed by the Iran regime. I should say that there I received pretty
 funny messages as:
 >
 {{{
 Feb 28 09:57:48.000 [warn]  10 connections died in state connect()ing with
 SSL state (No SSL object)
 Feb 28 09:59:05.000 [warn] Problem bootstrapping. Stuck at 50%: Loading
 relay descriptors. (Connection timed out; TIMEOUT; count 12;
 recommendation warn)
 Feb 28 09:59:05.000 [warn] 11 connections have failed:
 Feb 28 09:59:05.000 [warn]  11 connections died in state connect()ing with
 SSL state (No SSL object)
 }}}
 >
 > or
 {{{
 Feb 28 10:06:14.000 [notice] Bootstrapped 100%: Done
 Feb 28 10:06:32.000 [warn] Received http status code 404 ("Not found")
 from server '85.14.240.188:443' while fetching
 "/tor/keys/fp/27B6B5996C426270A5C95488AA5BCEB6BCC86956".
 Feb 28 10:08:45.000 [warn] parse error: Malformed object: missing object
 end line
 Feb 28 10:08:45.000 [warn] Unparseable microdescripto
 }}}

 I wonder what changes did you make to manage to get the errors mentioned
 above.

 > pretty much seems to my eyes a tampered ssl. My tor config is straight
 forward and includes a default 9050 port socks 5 on the 127.0.0.1.
 > Here is the signature and version info:
 > -Linux localhost 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51
 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
 > -tor-0.2.5.10-1.el6.x86_64
 > -torsocks-2.0.0-2.el6.x86_64

 How did you download your Tor? Did you verify the signature?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15073#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list