3

Today, I use obfs4 ,fte and scramblesuit to connect network unsuccessfully.Are they disabled by the GFW?What happend?

cao riza
  • 41
  • 1
  • 3

3 Answers3

2

Probably has something to do with the GFW admins deploying something like this fairly recently described classifier. All the current obfuscators seem to fall to entropy distribution, header length, and decision tree-based machine learning attacks with very low false-positive rates.

https://dl.acm.org/citation.cfm?doid=2810103.2813715

Also, this written by the people who design the GFW:

http://crad.ict.ac.cn/CN/abstract/abstract3031.shtml

PacoBell
  • 71
  • 1
  • 4
0

I believe at least integrated meek-azure bridge still works, although it seems lots of bridges have been blocked recently. How many bridges you've added? Do you check your Tor log? Any warning messages like 'connection failure?'

user66466
  • 131
  • 3
0

Obf3, Obf4, Meek-azure and Scramblesuit all works fine for me here in China. (fte looks not working)

I don't use the bundle but the vanilla Tor and I put in the config file all bridges I have together (Obf3-4, Meek-azure and scramblesuit) works pretty well :)

Now for Debian linux the packages for meek transport plugin are available so once installed you can configure tor adding this line:

ClientTransportPlugin obfs4,obfs3,scramblesuit exec /usr/bin/obfs4proxy
ClientTransportPlugin meek exec /usr/bin/meek-client
WonderLand
  • 379
  • 2
  • 16