Mike Perry:
- Windows:
- Bug 11286: Fix fte transport launch error
While this is working now, it seems there are new fingerprints available for the remaining two bridges:
10.04.14 12:06:18 [0x0-0x23023].org.mozilla.torbrowser[272] Apr 10 12:06:18.000 [warn] Tried connecting to router at 79.125.3.12:8080, but identity key was not as expected: wanted 17AF9F9F4E57614A060B7221DCCEDB8BB546DD73 but got [snip] 10.04.14 12:06:18 [0x0-0x23023].org.mozilla.torbrowser[272] Apr 10 12:06:18.000 [warn] Tried connecting to router at 131.252.210.150:8080, but identity key was not as expected: wanted 271EC1874E40FE65C145C6397AA34FFF7008E50E but got [snip]
And I did not get flashproxy to run at all (but tried not hard).
10.04.14 12:04:21 [0x0-0x23023].org.mozilla.torbrowser[272] Apr 10 12:04:21.000 [warn] We were supposed to connect to bridge '0.0.1.0:1' using pluggable transport 'flashproxy', but we can't find a pluggable transport proxy supporting 'flashproxy'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 10.04.14 12:04:21 [0x0-0x23023].org.mozilla.torbrowser[272] Apr 10 12:04:21.000 [warn] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Can't connect to bridge; PT_MISSING; count 1; recommendation warn)
This might be no surprise given that I just started the Tor Browser with flashproxy enabled in the TorLauncher dialog. If users are supposed to do additional things we should tell them that somehow...
Georg