Please test bundles with slightly rearchitected meek-http-helper
Dear tor-qa, please test the meek transport in these test bundles: https://people.torproject.org/~dcf/pt-bundle/4.5a4-12716-1/ You only need to test that meek bootstraps and that there are no processes left running when you close the browser. Here is the test procedure: 1. Click "Configure". 2. Choose "Yes" on the bridge/pluggable transport question. 3. Choose meek-amazon, meek-azure, or meek-google (doesn't matter which) from the list. 4. Choose "No" on the proxy question. 5. Make sure it bootstraps 100%. 6. Close the browser and check the process list; make sure there are no processes with "meek" in the name. I tested on linux64 but not any of the other platforms. The purpose of these bundles is https://trac.torproject.org/projects/tor/ticket/12716, which changes the way the browser helper is spawned so that it can be used outside of Tor Browser. David Fifield
-----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@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. Copy of Tor Log (from first scenario with meek-google): —————————————————————————————————————————— 3/12/15, 08:40:58.121 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 3/12/15, 08:40:58.121 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 3/12/15, 08:40:58.121 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 3/12/15, 08:40:58.121 [NOTICE] Opening Socks listener on 127.0.0.1:9150 3/12/15, 08:40:58.121 [NOTICE] Renaming old configuration file to "/Users/**********/Desktop/TorBrowser.app/TorBrowser/Data/Tor/torrc.orig.1" 3/12/15, 08:41:16.507 [WARN] The communication stream of managed proxy 'PluggableTransports/meek-client-wrapper' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors. 3/12/15, 08:41:16.507 [NOTICE] Failed to terminate process with PID '4866' ('No child processes'). 3/12/15, 08:41:17.508 [NOTICE] Bootstrapped 5%: Connecting to directory server 3/12/15, 08:41:17.509 [WARN] We were supposed to connect to bridge '0.0.2.0:1' using pluggable transport 'meek', but we can't find a pluggable transport proxy supporting 'meek'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 3/12/15, 08:41:17.509 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Can't connect to bridge; PT_MISSING; count 1; recommendation warn) David Fifield:
Dear tor-qa, please test the meek transport in these test bundles: https://people.torproject.org/~dcf/pt-bundle/4.5a4-12716-1/ You only need to test that meek bootstraps and that there are no processes left running when you close the browser. Here is the test procedure: 1. Click "Configure". 2. Choose "Yes" on the bridge/pluggable transport question. 3. Choose meek-amazon, meek-azure, or meek-google (doesn't matter which) from the list. 4. Choose "No" on the proxy question. 5. Make sure it bootstraps 100%. 6. Close the browser and check the process list; make sure there are no processes with "meek" in the name.
I tested on linux64 but not any of the other platforms.
The purpose of these bundles is https://trac.torproject.org/projects/tor/ticket/12716, which changes the way the browser helper is spawned so that it can be used outside of Tor Browser.
David Fifield _______________________________________________ tor-qa mailing list tor-qa@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa
-----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVAYvFAAoJEBcGNROt9juxRm4P/13aGVpDQue5Hs6Eq3omUVnM UhauMoPPRjhvyMsiHfZPCCTxbLSXIioSD5OHwjCEx6VIgS2O5uRi1SqoCS8k7969 kN5AeKIcJAabQAm6RBV9HtzFhPNoEpkAdnQ4rmgXFGKUL/seKNJoZufZok1J3JKS uRvQ0f6tlikdo5ZdcVcoRS2Z4s0VCM0Dk2dmIrlfbV0Cw6BwkSYrO7ngWAuc7nDT ZIlAjT8kSBVuophWV8VTAYQbUgQBCHMMRvJ5Tx3yNv6uOSTfxjDUk33h41KjRxuA a7VD7XeejqnTiAvo5giICzqcrqbHBeeLwppxxm6lX6iK1jqSzdDRLs6BjraJ8Phv 2IBcFWAtlRB4Hf4e8nYV8u/jVBXxD9TZolF2X2cPiLZDpGGpKTtqwQT1nHG1mSEr KlsA5vDDe/Vxz36FD3xW58+vN76wZNhkjgdBRd5AkM3/kxKJBHPpSCjMCfE8f09+ aYDb+UgahGrf3XUOmoYsqj9J5oJqLxltl/tnjWMjsi1229ggeZL9lZS0rcnkvZHB 5oMBxb0bDk1wdiBPuzILexEBv/Mb8MwzF7mlzBcrK24yIAsOOHm3IgA0CtG4xXKd 9hUWas0EWx0BbMsBZV7wO6mrNVNU5GvFKqonOZU8hFIqd8309f5Cruhp56U5b5c7 khUVhUOdI95W1cIZrP8i =dmTt -----END PGP SIGNATURE-----
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@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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It works on linux32. Bootstrapped with meek, visited a few sites, verified the running meek processes, closed the browser and no meek process was left. On 03/12/2015 12:03 AM, David Fifield wrote:
Dear tor-qa, please test the meek transport in these test bundles: https://people.torproject.org/~dcf/pt-bundle/4.5a4-12716-1/ You only need to test that meek bootstraps and that there are no processes left running when you close the browser. Here is the test procedure: 1. Click "Configure". 2. Choose "Yes" on the bridge/pluggable transport question. 3. Choose meek-amazon, meek-azure, or meek-google (doesn't matter which) from the list. 4. Choose "No" on the proxy question. 5. Make sure it bootstraps 100%. 6. Close the browser and check the process list; make sure there are no processes with "meek" in the name.
I tested on linux64 but not any of the other platforms.
The purpose of these bundles is https://trac.torproject.org/projects/tor/ticket/12716, which changes the way the browser helper is spawned so that it can be used outside of Tor Browser.
David Fifield _______________________________________________ tor-qa mailing list tor-qa@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVAgyjAAoJEPb7JcMmVt4gES0IAKLBXiCrnqhnkAy4PjguekTv IMuFnIhlSsfPm75Mj0VPK3Qc2PE37iZroZAA9z4pZcwY6G/f+TP+DdSCtW4femWw G+LiZ7imnExihRIg1ilX7nJ2p8nP2j1TV7Y8eiHzPC/BUoh6fd13YOmXuHRq7Gdm NCNGX6VXxKNiyOTfmRAszleGq6U7GG+A93xEPSr+zbCzm/kUJ081faGLKkUbNRlj BqMYGhfeG0vaTY5gr1SbsED/aXDNSHD8TxnJrJar5Mv0Ixbv6WGbENtsUsK7cs8e cBJESS05eML9nVErc6fZ9Moccg8UUv/LY6ermYF0zkitR6eNP7NBiL+izRrZKHk= =6/ld -----END PGP SIGNATURE-----
On 3/11/15 7:03 PM, David Fifield wrote:
Dear tor-qa, please test the meek transport in these test bundles: https://people.torproject.org/~dcf/pt-bundle/4.5a4-12716-1/ ...
A very quick test on Mac OS 10.9.5 resulted in this error after choosing meek-amazon: Profile Missing Your Firefox profile cannot be loaded. It may be missing or inaccessible. Poking around, I discovered that meek-browser-helper-mac.sh uses realpath, which (as far as I can tell) is not present on the Mac OS system that I used for testing. -- Mark Smith Pearl Crescent http://pearlcrescent.com/
On 13/03/15 15:06, Mark Smith wrote:
On 3/11/15 7:03 PM, David Fifield wrote:
Dear tor-qa, please test the meek transport in these test bundles: https://people.torproject.org/~dcf/pt-bundle/4.5a4-12716-1/ ...
A very quick test on Mac OS 10.9.5 resulted in this error after choosing meek-amazon:
Profile Missing Your Firefox profile cannot be loaded. It may be missing or inaccessible.
Poking around, I discovered that meek-browser-helper-mac.sh uses realpath, which (as far as I can tell) is not present on the Mac OS system that I used for testing.
Ah, I thought realpath was a standard thing. Does "readlink -f" work instead? X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
On 3/13/15 8:48 PM, Ximin Luo wrote:
Ah, I thought realpath was a standard thing. Does "readlink -f" work instead?
No, the Mac OS / BSD readlink seems to be quite different than the Linux one. See: https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPa... Also, some possibly useful ideas can be found here: http://stackoverflow.com/questions/1055671/how-can-i-get-the-behavior-of-gnu... -- Mark Smith Pearl Crescent, LLC http://pearlcrescent.com/
On 14/03/15 03:02, Mark Smith wrote:
On 3/13/15 8:48 PM, Ximin Luo wrote:
Ah, I thought realpath was a standard thing. Does "readlink -f" work instead?
No, the Mac OS / BSD readlink seems to be quite different than the Linux one. See:
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPa...
Also, some possibly useful ideas can be found here:
http://stackoverflow.com/questions/1055671/how-can-i-get-the-behavior-of-gnu...
Ah ok, instead of "$(realpath "../Data/Browser/profile.meek-http-helper")" could you please try "$(dirname "$(pwd -P)")/Data/Browser/profile.meek-http-helper" X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
On Sat, Mar 14, 2015 at 10:04:58AM +0100, Ximin Luo wrote:
On 14/03/15 03:02, Mark Smith wrote:
On 3/13/15 8:48 PM, Ximin Luo wrote:
Ah, I thought realpath was a standard thing. Does "readlink -f" work instead?
No, the Mac OS / BSD readlink seems to be quite different than the Linux one. See:
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPa...
Also, some possibly useful ideas can be found here:
http://stackoverflow.com/questions/1055671/how-can-i-get-the-behavior-of-gnu...
Ah ok, instead of "$(realpath "../Data/Browser/profile.meek-http-helper")"
could you please try "$(dirname "$(pwd -P)")/Data/Browser/profile.meek-http-helper"
I tested this on Mac and it works: "$PWD/../Data/Browser/profile.meek-http-helper" This also works: "$(pwd)/../Data/Browser/profile.meek-http-helper" This also works: "$(dirname "$(pwd -P)")/Data/Browser/profile.meek-http-helper" I think I'll go with the first one, because it's the shortest. David
On 12/03/15 00:03, David Fifield wrote:
Dear tor-qa, please test the meek transport in these test bundles: https://people.torproject.org/~dcf/pt-bundle/4.5a4-12716-1/ You only need to test that meek bootstraps and that there are no processes left running when you close the browser. Here is the test procedure: 1. Click "Configure". 2. Choose "Yes" on the bridge/pluggable transport question. 3. Choose meek-amazon, meek-azure, or meek-google (doesn't matter which) from the list. 4. Choose "No" on the proxy question. 5. Make sure it bootstraps 100%. 6. Close the browser and check the process list; make sure there are no processes with "meek" in the name.
I tested on linux64 but not any of the other platforms.
I tested on windows7, and firefox.exe (meek-http-helper) sticks around after you shut down Tor Browser cleanly, preventing it from starting up a second time unless you go into Process Explorer and kill it. (Windows' own Task Manager appears not to show the command line, so it's hard to distinguish this from a normal user firefox process.) However, this should be fixed by the following files: https://people.torproject.org/~infinity0/bin/meek-browser-helper-windows.bat https://people.torproject.org/~infinity0/bin/meek-browser-helper-windows.js https://people.torproject.org/~infinity0/bin/meek-client-wrapper.exe Drop these in Browser\TorBrowser\Tor\PluggableTransports after you install the above bundle, and follow 1-6. If there are other windows users, please confirm that this also works for you. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
On Sun, Mar 15, 2015 at 11:20:29PM +0100, Ximin Luo wrote:
I tested on windows7, and firefox.exe (meek-http-helper) sticks around after you shut down Tor Browser cleanly, preventing it from starting up a second time unless you go into Process Explorer and kill it. (Windows' own Task Manager appears not to show the command line, so it's hard to distinguish this from a normal user firefox process.)
I get the same on Windows 7. firefox.exe (seems like two of them) keeps running, and you can't start the browser a second time. David
participants (6)
-
David Fifield -
gunes acar -
Mark Smith -
Wilton Gorske -
Ximin Luo -
Ximin Luo