[tor-qa] Tor Browser 4.0 is ready for testing

Sherief Alaa sheriefalaa.w at gmail.com
Mon Oct 13 22:25:16 UTC 2014


On Oct 14, 2014, at 12:10 AM, David Fifield <david at bamsoftware.com> wrote:

> On Mon, Oct 13, 2014 at 11:54:30PM +0200, Sherief Alaa wrote:
>> 
>> On Oct 13, 2014, at 7:22 PM, David Fifield <david at bamsoftware.com> wrote:
>> 
>>> On Mon, Oct 13, 2014 at 04:55:29PM +0200, Sherief Alaa wrote:
>>>> + While testing on OS X, I noticed that in the "Apps using significant
>>>> energy" battery menu that "TorBrowser.app.meek-http-helper" is running
>>>> but I never chose to run meek to begin with (only obfs3).
>>> 
>>> Hmm, this shouldn't happen. Can you send me the tor log?
>> 
>> 
>> 10/13/14, 21:05:25.930 [NOTICE] Bootstrapped 5%: Connecting to directory server 
>> 10/13/14, 21:05:25.931 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 
>> 10/13/14, 21:05:27.205 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection 
>> 10/13/14, 21:05:27.481 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus 
>> 10/13/14, 21:05:27.646 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus 
>> 10/13/14, 21:05:28.387 [NOTICE] new bridge descriptor 'gamma' (fresh): $xxxxx~gamma at 37.13x.xx.xxx 
>> 10/13/14, 21:05:28.387 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus. 
>> 10/13/14, 21:05:34.445 [NOTICE] We now have enough directory information to build circuits. 
>> 10/13/14, 21:05:34.445 [NOTICE] Bootstrapped 80%: Connecting to the Tor network 
>> 10/13/14, 21:05:34.949 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit 
>> 10/13/14, 21:05:39.955 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working. 
>> 10/13/14, 21:05:39.955 [NOTICE] Bootstrapped 100%: Done 
>> 10/13/14, 21:05:40.792 [NOTICE] New control connection opened from 127.0.0.1. 
> 
> Maybe bump up the log level (add "Log info stdout" to
> Browser/TorBrowser/Data/Tor/torrc). The lines I'm looking for are:
> 
> [info] parse_client_transport_line(): Pluggable transport proxy (fte exec ./TorBrowser/Tor/PluggableTransports/fteproxy.bin --managed) does not provide any needed transports and will not be launched.
> [info] parse_client_transport_line(): Pluggable transport proxy (flashproxy exec ./TorBrowser/Tor/PluggableTransports/flashproxy-client --register :0 :9000) does not provide any needed transports and will not be launched.
> [info] parse_client_transport_line(): Pluggable transport proxy (meek exec ./TorBrowser/Tor/PluggableTransports/meek-client-torbrowser -- ./TorBrowser/Tor/PluggableTransports/meek-client) does not provide any needed transports and will not be launched.

Did that and no new messages appeared in the log.

BTW, I think Tom is right about OS X getting the wrong Application name but I don’t know why would it confuse TB with meek-http-helper when it’s not even running to being with.


More information about the tor-qa mailing list