Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How did GFW block circumvention tools during the 19th people's congress? #1

Open
net4people opened this issue Nov 17, 2017 · 1 comment
Labels

Comments

@net4people
Copy link
Collaborator

@net4people net4people commented Nov 17, 2017

From around Oct 9th 2017 and especially during the 19th people's congress, GFW blocked almost all circumvention tools including Shadowsocks, Lantern and Psiphon. Currently, there has been no concrete findings on how exactly GFW blocks such tools.

A few hypothesis are follows.
GFW fingerprints popular circumvention protocols such as Shadowsocks, Obfs4 and HTTPS.
GFW did traffic analysis using metadata such as amount of data transferred between IP and flag them for manual review or randomly block them.

Please feel free to add new hypothesis and add data to prove/disprove any hypothesis.

@Zsnitm40
Copy link

@Zsnitm40 Zsnitm40 commented Jan 27, 2020

It's nothing new, I believe it is the Quality of Service referred to on the active filtering at https://en.wikipedia.org/wiki/Great_Firewall#Active_Filtering It states that it scores each IP based on how suspicious the connection is. The only difference is that the GFW turned up the sensitivity nob.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants