[tor-bugs] #27435 [Obfuscation/Obfsproxy]: Poland, PLAY operator and OBFS4

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#27435: Poland, PLAY operator and OBFS4
---------------------------------------+------------------------------
     Reporter:  VeryVeryBadUser        |      Owner:  asn
         Type:  defect                 |     Status:  new
     Priority:  High                   |  Milestone:  Tor: unspecified
    Component:  Obfuscation/Obfsproxy  |    Version:  Tor: unspecified
     Severity:  Blocker                |   Keywords:
Actual Points:                         |  Parent ID:
       Points:                         |   Reviewer:
      Sponsor:                         |
---------------------------------------+------------------------------
 The OBFS4 looks to be blocked by PLAY in Poland.

 The router was restarted, the computer with Tor Browser was restarted. It
 doesn't help me.

 I can connect via Firefox to other web pages but not via Tor.

 [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] Ignoring directory request, since no bridge nodes are available
 yet.
 [NOTICE] Bootstrapped 5%: Connecting to directory server
 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
 [NOTICE] Bridge 'Lisbeth' has both an IPv4 and an IPv6 address.  Will
 prefer using its IPv6 address
 ([2001:470:b381:bfff:216:3eff:fe23:d6c3]:443) based on the configured
 Bridge address.
 [NOTICE] Bridge 'Lisbeth' has both an IPv4 and an IPv6 address.  Will
 prefer using its IPv4 address (192.95.36.142:443) based on the configured
 Bridge address.
 [NOTICE] Bridge 'NX01' has both an IPv4 and an IPv6 address.  Will prefer
 using its IPv4 address (85.17.30.79:443) based on the configured Bridge
 address.
 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
 [NOTICE] new bridge descriptor 'noisebridge01' (fresh): [removed] at
 216.252.162.21
 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS
 server failure")
 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS
 server failure")
 [WARN] Proxy Client: unable to connect to 154.35.22.13:16815 ("general
 SOCKS server failure")
 9[WARN] Proxy Client: unable to connect to 154.35.22.11:443 ("general
 SOCKS server failure")
 [WARN] Proxy Client: unable to connect to 154.35.22.12:4304 ("general
 SOCKS server failure")
 [WARN] Proxy Client: unable to connect to 154.35.22.10:443 ("general SOCKS
 server failure")
 [NOTICE] Ignoring directory request, since no bridge nodes are available
 yet.
 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
 [NOTICE] I learned some more directory information, but not enough to
 build a circuit: We're missing descriptors for 1/2 of our primary entry
 guards (total microdescriptors: 6360/6377).
 [NOTICE] Ignoring directory request, since no bridge nodes are available
 yet.
 [NOTICE] Ignoring directory request, since no bridge nodes are available
 yet.
 [NOTICE] Bootstrapped 50%: Loading relay descriptors

 After last notice there is no progress.
 Version: 7.5.6 (based on Mozilla Firefox 52.9.0) (32-bit)
 Maybe security / privacy problem.

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

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs