[tor-bugs] #21836 [- Select a component]: meek-azure seems broken

[Tor Bug Tracker & Wiki]

#21836: meek-azure seems broken
--------------------------------------+-----------------
     Reporter:  cypherpunks           |      Owner:
         Type:  defect                |     Status:  new
     Priority:  High                  |  Milestone:
    Component:  - Select a component  |    Version:
     Severity:  Normal                |   Keywords:
Actual Points:                        |  Parent ID:
       Points:                        |   Reviewer:
      Sponsor:                        |
--------------------------------------+-----------------
 I am in a country where meek is the only thing that works. Amazon is much
 less stable than Azure for me normally, so thank you very much for keeping
 Azure alive - it is the only way to stay vaguely safe anymore.

 I was using Azure with no issues on TorBrowser v6.5.1 an hour or so before
 this event. Then, some time after Mar 29 2017 2230UTC I tried to reconnect
 and the connection failed on the SSL handshake. I examined the traffic
 pattern using a traffic visualizer during the connection and all that
 occurred was a single pulse and then the connection died.

 Nothing had been changed on my system - no updates, or firewall changes or
 anything else significant. To be sure, I tested on another machine which
 had not been used that day, but that had worked last time I used it a day
 earlier. Like the other machine, it also had a similar rapid connection
 failure. I am almost certain this is not an issue linked to my local
 machines and either is linked to the underlying bridge, something
 Microsoft has changed or something local authorities have done to break
 the Azure server. However, if it is caused by local authorities, I am a
 little unsure why only Azure would be broken.

 Amazon, as I said, sort of works here, but can be very unstable and almost
 unusably slow as it is for me right now. If someone could just check to
 see if anything has happened to the Azure server, it would be greatly
 appreciated!





 LOG SAMPLE:

 Opening Socks listener on 127.0.0.1:9150
 [NOTICE] Bootstrapped 5%: Connecting to directory server
 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with
 directory server. (DONE; DONE; count 1; recommendation warn; host
 97700DFE9F483596DDA6264C4D7DF7641E1E39CE at 0.0.2.0:3)
 [WARN] 1 connections have failed:
 [WARN]  1 connections died in state handshaking (TLS) with SSL state
 SSLv2/v3 read server hello A in HANDSHAKE
 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control
 network connections. Shutting down all existing connections.
 Closing old Socks listener on 127.0.0.1:9150
 [NOTICE] Delaying directory fetches: DisableNetwork is set.
 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control
 network connections. Shutting down all existing connections.
 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control
 network connections. Shutting down all existing connections.
 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control
 network connections. Shutting down all existing connections.
 [NOTICE] Opening Socks listener on 127.0.0.1:9150
 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
 [NOTICE] new bridge descriptor 'TorLandMeek' (fresh):
 $B9E7141C594AF25699E0079C1F0146F409495296~TorLandMeek at 0.0.2.0

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