#22653: upgrading Tor-0.2.9.10 to Tor-0.3.0.8 or Tor-0.3.1.3_alpha fails to 
build
circuits
--------------------------+------------------------------------
 Reporter:  t0r           |          Owner:
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.0.8
 Severity:  Normal        |     Resolution:
 Keywords:  tor-guard     |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by t0r):

 Replying to [comment:11 teor]:
 > This looks similar to #22576.
 > If it is, it's not a bug in Tor, it's likely a bug in the pluggable
 transport: either the config, or the compilation. Please check that ticket
 for details.
 After reading through #22576, I think they are not related. I don't use
 squid HTTP proxy.
 I added more tests above, and pretty sure it's not obfs4proxy problem.
 > We also need to check and see if it's a guard issue in tor.
 It's probably the new '''guard''' feature drawn into Tor-0.3. There exists
 two clues:

 1. Based on all comments so far, I narrowed down the issue to Tor-0.3
 binary. I also tried to replace Tor binary in 7.0.1 with 6.5.2. But it
 reports error:

 {{{
 Launching './Browser/start-tor-browser --detach --debug --log'...
 Logging Tor Browser debug information to tor-browser.log
 Jun 19 12:54:49.584 [notice] Tor 0.2.9.10 (git-1f6c8eda0073f464) running
 on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2k and Zlib 1.2.11.
 Jun 19 12:54:49.584 [notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/download#warning
 Jun 19 12:54:49.584 [notice] Read configuration file "/home/bobme/opt/tor-
 browser_en-US/Browser/TorBrowser/Data/Tor/torrc-defaults".
 Jun 19 12:54:49.584 [notice] Read configuration file "/home/bobme/opt/tor-
 browser_en-US/Browser/TorBrowser/Data/Tor/torrc".
 Jun 19 12:54:49.594 [warn] Failed to parse/validate config: Unknown option
 '__ControlPort'.  Failing.
 Jun 19 12:54:49.594 [err] Reading config failed--see warnings above.
 }}}

 2. If we compare the log difference between Tor-0.2 and Tor-0.3 above, the
 later exclusively contains a special line:

 {{{
 Starting with guard context "bridges"
 }}}

 3. Although no circuits built with bridge and obfs4proxy, Tor-0.3 onward
 works greatly with Socks5Proxy option support since that proxy bypasses
 censorship successively.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22653#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Reply via email to