[tor-qa] Please test bundles with slightly rearchitected meek-http-helper

[David Fifield]

On Thu, Mar 12, 2015 at 12:51:17PM +0000, Wilton Gorske wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> TorBrowser-4.5a4-osx64_en-US.dmg
> TorBrowser-4.5a4-osx64_en-US.dmg.asc
> 
> gpg: Signature made Wed Mar 11 18:09:16 2015 EDT using RSA key ID 5CD388E5
> gpg: Good signature from "David Fifield <david at bamsoftware.com>" [unknown]
> Primary key fingerprint: AD1A B35C 674D F572 FBCE  8B0A 6BC7 58CB C11F
> 6276
>      Subkey fingerprint: 797A 326A EC4A 478A F050  CC3A E2B9 3D81 5CD3
> 88E5
> 
> Platform: OS X 10.10.1 (14B25)
> Processor: 2.3GHz Intel Core i7
> Memory: 16 GB 1600 MHz DDR3
> Graphics: NVIDIA GeForce GT 750M 2048 MB
> Display: 15-inch (2880 x 1800 Retina)
> 
> ———————————————————————————————————————————
> 
> “Does your Internet Service Provider (ISP) or block or otherwise
> censor connections to the Tor Network?
> 
> > Yes
> 
> You may use the provided set of bridges or you may obtain and enter a
> custom set of bridges.
> 
> > Connect with provided bridges
> >> Transport type: meek-google
> 
> Does this computer need to use a local proxy to access the Internet?
> 
> > No
> 
> 4 windows pop up, all saying: “Profile Missing. Your Firefox profile
> cannot be loaded. It may be missing or inaccessible.”
> 
> Tor Launcher: Tor failed to establish a Tor network connection.
> Connection to a relay directory failed (missing pluggable transport).
> 
> It does this with every configuration, even if trying to connect
> directly with the Tor network.

Okay, hmm. Thanks for testing. I will take a look.

I'm surprised that it failed even when not using a pluggable transport.
Could you double-check that, by extracting the package again and
clicking "Connect" on the first screen? It's possible I branched off of
a bad commit or something.

David Fifield