[tor-bugs] #10802 [BridgeDB]: Getting bridges only for port 80, 443
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Feb 12 01:09:49 UTC 2015
#10802: Getting bridges only for port 80,443
-----------------------------+-------------------------
Reporter: torland | Owner: isis
Type: enhancement | Status: assigned
Priority: normal | Milestone:
Component: BridgeDB | Version:
Resolution: | Keywords: bridgedb-ui
Actual Points: | Parent ID:
Points: |
-----------------------------+-------------------------
Changes (by isis):
* status: new => assigned
* owner: => isis
Comment:
So… the issue that sysrqb pointed out, if I understood correctly, was that
if we add a little checkbox that says ''"I have a restrictive firewall
which only allows ports 80 and/or 443!"'' and they also select a Pluggable
Transport that might not have very many or any bridges running on those
ports, e.g. obfs3, then the little checkbox won't work: the client will
just get obfs3 bridges which are on random ports, not on port 443 or 80.
Also, as sysrqb pointed out, the way that BridgeDB is currently configured
(for all distributors, for all clients, for everything) is to try
''really'' hard to make sure that at least one of the bridges given to
every client is on port 443. We could add a system-wide configuration that
forces one of the other bridges to be on port 80, but this would mean that
all the other bridges on random ports wouldn't get used as much.
We now also have TBB default bridges (many of which should work for users
behind fascist corporate firewalls).
Because of all this, I'm not currently convinced that this ticket warrants
the extra development and maintenance… but I might still be convinced.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10802#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list