Re: [tor-bugs] #23347 [Core Tor/Tor]: Switching from direct connection to a pluggable transport is not working anymore with tor on master

[Tor Bug Tracker & Wiki]

#23347: Switching from direct connection to a pluggable transport is not working
anymore with tor on master
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-bootstrap, tor-bridge-client  |  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * keywords:   => tor-bootstrap, tor-bridge-client
 * points:   => 0.5


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23347 [Core Tor/Tor]: Switching from direct connection to a pluggable transport is not working anymore with tor on master

[Tor Bug Tracker & Wiki]

#23347: Switching from direct connection to a pluggable transport is not working
anymore with tor on master
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 To reproduce this, you can use:
 {{{
 src/or/tor DataDirectory `mktemp -d` UseBridges 1 Bridge ...
 }}}
 where ... is any bridge on any transport.
 (I used a bridge from bridges.torproject.org, but any bridge or relay
 should work.)

 I have confirmed that this works on 0.3.0.10, but fails on master with:
 {{{
 Bootstrapped 0%: Starting
 Delaying directory fetches: No running bridges
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23347 [Core Tor/Tor]: Switching from direct connection to a pluggable transport is not working anymore with tor on master

[Tor Bug Tracker & Wiki]

#23347: Switching from direct connection to a pluggable transport is not working
anymore with tor on master
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 #17750 made download schedules use the specified initial delay, rather
 than 0.
 The two schedules with a non-zero delay are the fallback authority
 schedule and the bridge schedule.

 So my guess is that the bridge schedule's initial delay of 1 hour is
 wrong, and tor needs to download a bridge descriptor to bootstrap. It is
 possible that this bug was introduced in Tor 0.3.0 with the guard
 algorithm changes.

 I'll work out how to reproduce this on the command-line, and submit a
 schedule patch.
 This will probably involve re-thinking the entire schedule. (Because if we
 really need the bridge descriptor, we shouldn't wait 2 hours if we fail
 the first time.)

 I have closed #17750, because we really shouldn't backport it.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23347 [Core Tor/Tor]: Switching from direct connection to a pluggable transport is not working anymore with tor on master

[Tor Bug Tracker & Wiki]

#23347: Switching from direct connection to a pluggable transport is not working
anymore with tor on master
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by gk):

 (I am a bit confused about the Milestone usage: #17750 has "Tor:
 0.3.1.x-final" even though the code is not on `maint-0.3.1`, and reading
 the comments of this ticket, this might not even happen. I chose "Tor:
 0.3.2.x-final" as the problematic code is only on `master` right now. If
 that's wrong please readjust.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #23347 [Core Tor/Tor]: Switching from direct connection to a pluggable transport is not working anymore with tor on master

[Tor Bug Tracker & Wiki]

#23347: Switching from direct connection to a pluggable transport is not working
anymore with tor on master
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Trying to switch from a direct connection to using a bridge is not working
 anymore with tor on `master` (found while using commit
 f2f1cab2b3c6a56f93862c424663f083b79c7bc3) on my Linux box.

 Steps to reproduce:

 1) Take a recent Tor Browser (e.g. an alpha version)
 2) Make sure you replace `tor` shipped in your Tor Browser instance with
 one compiled from a recent master commit
 3) Start Tor Browser and choose direct connection
 4) Shut Tor Browser down after you got greeted with the `about:tor` page
 5) Restart Tor Browser and press the "Open Settings" button before the
 bootstrapping is finished
 6) Select e.g. the recommended `obfs4` default bridge option
 7) The start-up stalls (I quit Tor Browser after 5 minutes waiting)

 The first bad commit is c21cfd28f43a969229ede02e20c6b554c1b88aae which
 fixed #17750. Without that one Tor Browser resumes bootstrapping after a
 couple of seconds and is using an `obfs4` bridge.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs