-
Notifications
You must be signed in to change notification settings - Fork 82
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
35c3 videos #4
Comments
Censored Planet: a Global Censorship Observatory (56 min) Description of many off-path interference detection techniques: SpookyScan, Augur, Satellite/Iris, Quack. Rather technical.
|
Cat & Mouse: Evading the Censors in 2018 (55 min) Keith is an analyst at Psiphon. The first half of the talk is an introductory-level overview of Internet censorship and circumvention techniques. Starting at 27:00, he shows graphs of Psiphon usage during protests in Sudan, Iraq, and Iran; and during the 19th Party Congress in China. At 36:00 he identifies trends in censorship, which include large-scale DPI (1 TBit/s) and increasing resilience against collateral damage.
Fahrplan |
Russia vs. Telegram: technical notes on the battle (41 min) Starts by giving some context and history about Internet controls in Russia going back to 2007. ISPs run their own filtering system independently, but since 2016 have to install a government blackbox called "Revisor" that monitors the effectiveness of of the ISPs' filters. Attempts to block Telegram began in April 2018 after Telegram disobeyed a court order to hand over encryption keys. On the first day, 2M IP addresses were blocked; on the next, 16M; up to a peak of 19M. There was notable collateral damage which was however denied by the government. ISPs had varying levels of compliance with the blocking order (tested using RIPE Atlas). The blocking started to subside on April 28 and finally fell to about 4M IP addresses on June 8. Telegram remained more or less working throughout. Tests on one ISP found selective protocol throttling:
Filtering is at least partly based on packet lengths. An MTProto simulator that sends stereotyped packet lengths with random delays provokes blocking. Active probing was documented on the free wi-fi of the Moscow metro. After making a SOCKS5 connection, the SOCKS5 server was port-scanned and had a SOCKS request sent to it. If it was verified to be a SOCKS proxy, it was then added to a blocklist. Some ISPs apparently got advance notice of changes to the blocklist.
|
No description provided.
The text was updated successfully, but these errors were encountered: