Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#18876 closed defect (fixed)

obfs4 custom bridges don't work on Windows XP

Reported by: geeyourhairsmellsterrific Owned by:
Priority: Medium Milestone:
Component: - Select a component Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hello,

On my test Windows XP, obfs4 "custom" bridges don't work even though obfs4 "provided" (preloaded) bridges work normally.

By custom bridges, I mean those added manually via this method: Click the Torbutton, click Tor Network Settings, and select "Enter custom bridges."

In contrast to the non-working obfs4 custom bridges, obfs3 custom and provided bridges both work normally.

I've added 12 custom obfs4 bridges and cannot connect to the Tor network even after restarting the Tor browser.

As long as I use obfs4 "provided" bridges, everything works fine.

Thanks for your attention!

Child Tickets

Change History (7)

comment:1 Changed 4 years ago by geeyourhairsmellsterrific

Summary: obsf4 custom bridges don't work on Windows XPobfs4 custom bridges don't work on Windows XP

comment:2 Changed 4 years ago by arma

Did you try the bridges on a different tor browser install? That is, is it possible that your 12 bridges are all dead?

comment:3 Changed 4 years ago by dcf

Click the "Copy Tor Log to Clipboard" button and see if there are any error messages there.

Make sure your bridge lines are formatted correctly. They need to include an IP address and port, a cert, and an iat-mode. They should look like this (it's one of the provided bridges):

obfs4 154.35.22.9:60873 C73ADBAC8ADFDBF0FC0F3F4E8091C0107D093716 cert=gEGKc5WN/bSjFa6UkG9hOcft1tuK+cV8hbZ0H6cqXiMPLqSbCh2Q3PHe5OOr6oMVORhoJA iat-mode=0

comment:4 Changed 4 years ago by geeyourhairsmellsterrific

Thanks, Arma and Dcf! You were absolutely right, the bridges were dead. In fact, my first 9 batches of bridges (27) were dead. Finally the tenth batch had two good bridges.

Below I'll paste the 30 bridges, with the two good ones at the top.

I'm sorry for wasting your time. I've been using bridges for years and never encountered so many duds. I should have tested more before filing a bug report.

I'm banning myself from this forum until I've done penance for my transgression :-)

Thanks so much for your help!

Also, thanks for your tips, such as using the whole bridge descriptor, which I'd been shortening for years (after either the port number or the fingerprint) without any _apparent_ harm. From now on, I'll use the whole thing.

Here's the list of bridges (2 good followed by 28 duds, as of this moment):

[Removed --yawning]

Last edited 4 years ago by yawning (previous) (diff)

comment:5 Changed 4 years ago by geeyourhairsmellsterrific

Resolution: fixed
Status: newclosed

comment:6 Changed 4 years ago by geeyourhairsmellsterrific

Please delete the bridges if they shouldn't be posted publicly. I'm sorry if I made a mistake doing that.

comment:7 Changed 4 years ago by yawning

Hm, editing the comment leaves still leaves them in the revision history, but it doesn't really matter now since trac comments etc are sent to a publicly archived mailing list anyway. Oh well.

Note: See TracTickets for help on using tickets.