Getting bridges only for port 80,443

I am running TBB behind a corporate proxy that only allows traffic to port 80 and 443. When I get new bridges from https://bridges.torproject.org they are mostly running on ports that are blocked for me. It would be good to have a checkbox "80,443" on the page that would allow to only get bridges with port 80, 443.

Thanks,

Torland

Trac:
Username: torland

added bridgedb-ui component::circumvention/bridgedb ex-sponsor-19 parent::31280 points::2 priority::high reporter::torland severity::normal sponsor::30-must status::new type::enhancement labels

I think this sounds like a good idea to add onto #9127 (moved). However, if you want these ports, you will need to make sure you don't select a pluggable transport due to #7875 (moved).

But, also to add to this, we do try to return at least one bridge that listens on port 80 or 443 within each response. Sometimes this doesn't happen, in practice, though.

Thanks. I am not using pluggable transport at the moment, but generally it is an issue. I noticed that I mostly get back one bridge with 80/443. It made it much easier, because of #10809 (moved).

Trac:
Username: torland

Trac:
Keywords: N/A deleted, bridgedb-ui added

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.

Trac:
Owner: N/A to isis
Status: new to assigned

Trac:
Status: assigned to needs_information

Trac:
Cc: N/A to sysrqb

Trac:
Username: maxxer
Cc: sysrqb to sysrqb, io@maxxer.it

I'm behind a very restrictive fw which does DPI (so I need to use obfs3 or any other pluggable transport) and blocks non standard ports. In the past I had the luck to obtain a bridge on port 80, now this is apparently not responding anymore and the other two I have are on high ports, thus unreachable to me.

Being able to obtain at least one bridge on 80/443 would really help.

Trac:
Username: maxxer

Replying to maxxer:

I'm behind a very restrictive fw which does DPI (so I need to use obfs3 or any other pluggable transport) and blocks non standard ports. In the past I had the luck to obtain a bridge on port 80, now this is apparently not responding anymore and the other two I have are on high ports, thus unreachable to me.

Being able to obtain at least one bridge on 80/443 would really help.

That is already implemented, as described above. This ticket is about getting bridges only on ports 80 and 443.

Set all open tickets without a severity to "Normal"

Trac:
Severity: N/A to Normal

Trac:
Sponsor: N/A to Sponsor19
Reviewer: N/A to N/A
Owner: isis to N/A
Points: N/A to 2
Priority: Medium to High
Status: needs_information to assigned

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

Trac:
Keywords: N/A deleted, ex-sponsor-19 added

Moving from Sponsor 19 to Sponsor 30.

Trac:
Sponsor: Sponsor19 to Sponsor30-must

Trac:
Parent: N/A to #31280 (moved)

Trac:
Parent: #31280 (moved) to #31349

Trac:
Parent: #31349 to #31280 (moved)

Change tickets that are assigned to nobody to "new".

Trac:
Status: assigned to new

cohosh cc'ing myself on sponsor 30 work

Trac:
Cc: sysrqb, io@maxxer.it to sysrqb, io@maxxer.it, cohosh

changed time estimate to 16h

mentioned in issue #31280 (moved)

moved to tpo/anti-censorship/bridgedb#10802