[tor-bugs] #20250 [Obfuscation/meek]: macOS 10.12 TorBrowser meek pluggable transport issues

[Tor Bug Tracker & Wiki]

#20250: macOS 10.12 TorBrowser meek pluggable transport issues
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  dcf
  tordevSZ0              |
         Type:  defect   |     Status:  new
     Priority:  High     |  Milestone:
    Component:           |    Version:  Tor: unspecified
  Obfuscation/meek       |   Keywords:  meek, macOS, TorBrowser, 10.12,
     Severity:  Major    |  sierra, macOS
Actual Points:           |  Parent ID:
       Points:           |   Reviewer:
      Sponsor:           |
-------------------------+-------------------------------------------------
 Having issues using the meek pluggable transports on macOS 10.12
 installation with a fresh install of TorBrowser.

 On the same machine running 10.11.6 before upgrade, TorBrowser with both
 of the meek transports worked fine.

 With 10.12, (tested with admin and standard accounts), the initial tor
 connection UI completes, the browser opens and the initial meek connection
 is established. However, briefly after the browser window has opened with
 the successful about:tor page it is clear something is wrong. Monitoring
 internet traffic with a network monitor it is clear that the traffic to
 the meek server stops almost immediately after the browser has opened.

 Having read some of the control port issues for other 10.12 users, I
 tested this issue with the extensions.torlauncher.control_port_use_socket
 pref set to false in prefs.js and without it, but it had no effect either
 way.


 Attached are the tor, meek-client and meek-client-torbrowser logs. Really
 hope someone can help with this since meek is the only way to use tor in
 my country without having the police banging down the door.

 Tor Log:

 AUTHENTICATE <HASH>
 250 OK
 SETEVENTS STATUS_CLIENT NOTICE WARN ERR
 250 OK
 650 NOTICE Opening Socks listener on 127.0.0.1:9150
 650 NOTICE Bootstrapped 5%: Connecting to directory server
 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=5 TAG=conn_dir
 SUMMARY="Connecting to directory server"
 650 NOTICE Bootstrapped 10%: Finishing handshake with directory server
 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=10 TAG=handshake_dir
 SUMMARY="Finishing handshake with directory server"
 650 NOTICE Bootstrapped 15%: Establishing an encrypted directory
 connection
 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=15 TAG=onehop_create
 SUMMARY="Establishing an encrypted directory connection"
 650 NOTICE Bootstrapped 20%: Asking for networkstatus consensus
 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=20 TAG=requesting_status
 SUMMARY="Asking for networkstatus consensus"
 650 NOTICE Bootstrapped 25%: Loading networkstatus consensus
 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=25 TAG=loading_status
 SUMMARY="Loading networkstatus consensus"
 650 STATUS_CLIENT NOTICE CONSENSUS_ARRIVED
 650 STATUS_CLIENT NOTICE ENOUGH_DIR_INFO
 650 NOTICE Bootstrapped 80%: Connecting to the Tor network
 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=80 TAG=conn_or
 SUMMARY="Connecting to the Tor network"
 650 NOTICE Bootstrapped 90%: Establishing a Tor circuit
 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=90 TAG=circuit_create
 SUMMARY="Establishing a Tor circuit"
 650 NOTICE Tor has successfully opened a circuit. Looks like client
 functionality is working.
 650 NOTICE Bootstrapped 100%: Done
 650 STATUS_CLIENT NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
 650 STATUS_CLIENT NOTICE CIRCUIT_ESTABLISHED
 650 NOTICE New control connection opened from 127.0.0.1.
 650 NOTICE New control connection opened from 127.0.0.1.

 #NOTICE THE LINE BELOW:

 650 WARN The connection to the SOCKS4 proxy server at 127.0.0.1:57343 just
 failed. Make sure that the proxy server is up and running.


 650 NOTICE Delaying directory fetches: No running bridges
 650 NOTICE Tried for 120 seconds to get a connection to [scrubbed]:443.
 Giving up. (waiting for circuit)



 meek-client log:

 0:05 using helper on 127.0.0.1:49193
 0:05 listening on 127.0.0.1:49196
 0:33 using helper on 127.0.0.1:49199
 0:33 listening on 127.0.0.1:49202


 meek-client-torbrowser log:

 0:00 running firefox command
 ["/Applications/TorBrowser.app/Contents/MacOS/firefox" "--invisible" "-no-
 remote" "-profile" "/Applications/TorBrowser-
 Data/Tor/PluggableTransports/profile.meek-http-helper"]
 0:00 firefox started with pid 3644
 0:01 running meek-client command ["PluggableTransports/meek-client" "--
 log" "meek-client.txt" "--helper" "127.0.0.1:49193"]
 0:01 meek-client started with pid 3646
 0:27 sig terminated
 0:27 sending signal terminated to PID 3646
 0:27 killing PID 3646
 0:27 killing PID 3644
 0:32 running firefox command
 ["/Applications/TorBrowser.app/Contents/MacOS/firefox" "--invisible" "-no-
 remote" "-profile" "/Applications/TorBrowser-
 Data/Tor/PluggableTransports/profile.meek-http-helper"]
 0:32 firefox started with pid 3660
 0:33 running meek-client command ["PluggableTransports/meek-client" "--
 log" "meek-client.txt" "--helper" "127.0.0.1:49199"]
 0:33 meek-client started with pid 3661
 1:00 sig terminated
 1:00 sending signal terminated to PID 3661
 1:00 killing PID 3661
 1:00 killing PID 3660

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20250>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online