[tor-bugs] #30166 [Applications/Tor Browser]: If custom bridges are specified, only use those bridges for connecting
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun Apr 28 00:00:55 UTC 2019
#30166: If custom bridges are specified, only use those bridges for connecting
-------------------------------------------------+-------------------------
Reporter: gk | Owner: tbb-
| team
Type: defect | Status:
| needs_revision
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-mobile, tbb-8.5-must, | Actual Points:
TorBrowserTeam201904 |
Parent ID: #27609 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by sisbell):
Replying to [comment:6 gk]:
> Okay, I double-checked that I did not make a mistake here. The `tor-
android-service` repo I used is indeed on commit
de13672fe1ef6eb180edd4ec80f3f416f5d5c6b1 and should thus have your fix.
However, testing the resulting nightly as follows still shows the behavior
in comment:5
>
> 1) Install the resulting nightly
> 2) Before you start bootstrapping click on the gear icon and enter a
random custom bridge. I just used 1.2.3.4:12345
> 3) Go back to the bootstrap screen
> 4) Start bootstrapping
> 5) Expected: error about not working bridge or something
> 6) Actual: Happy bootstrapping making a direct connection
Yes, there is a bug in the code. The app is only processing bridges if the
custom entry has obfs4 or meek at a first field. So the custom fields are
being ignored and then the app proceeds to just make a direct connection.
I'll put in a fix.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30166#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list