[tor-qa] 3.6-beta-2 builds are up
Mark Smith
mcs at pearlcrescent.com
Thu Apr 10 17:30:05 UTC 2014
On 4/10/14, 9:30 AM, Sherief Alaa wrote:
> On Thu, Apr 10, 2014 at 7:51 AM, Mike Perry <mikeperry at torproject.org
> <mailto:mikeperry at torproject.org>> wrote:
>
> Ok, we've finally got a beta build with the OpenSSL fix in it. It also
> has some other PT-related fixes, as well:
> https://people.torproject.org/~mikeperry/builds/3.6-beta-2/
> ...
>
> Pluggable transports tests:
>
> a) FTE Test:
> ...
> 4/10/2014 12:50:01 PM.321 [NOTICE] DisableNetwork is set. Tor will not
> make or accept non-control network connections. Shutting down all
> existing connections.
> ...
> 4/10/2014 12:50:05 PM.817 [WARN] Tried connecting to router at
> 79.125.3.12:8080 <http://79.125.3.12:8080>, but identity key was not as
> expected: wanted 17AF9F9F4E57614A060B7221DCCEDB8BB546DD73 but got
> 272465348803EE2546A9BB8EE37D462915531F09.
> ...
> Notes:
>
> * While connecting "Open Settings" shows a yellow warning icon
> indicating something is wrong but tbb continues and connects anyway.
The warning icon is triggered by WARN or ERR tor log messages like the
one I left in the quoted text above. The icon is designed to tell
people "Please check your tor log; something bad may have happened." I
guess the fingerprints need to be updated for some of the PT bridges.
> * DisableNetwork is set...
DisableNetwork is initially set to 1 by Tor Launcher and then later it
is reset to 0. When it is set to 1, tor generates Notice-level log
messages like those you saw. I am not sure what if anything we should
do about those messages. They are possibly confusing but probably
important to see if you run tor outside of TBB with DisableNetwork=1.
--
Mark Smith
Pearl Crescent
http://pearlcrescent.com/
More information about the tor-qa
mailing list