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

engine: implement disguiser like methodology #2086

Open
bassosimone opened this issue May 6, 2022 · 1 comment
Open

engine: implement disguiser like methodology #2086

bassosimone opened this issue May 6, 2022 · 1 comment
Labels
data quality enhancement New feature request or improvement to existing functionality methodology issues related to the testing methodology new nettest ooni/probe-engine priority/low Nice to have research prototype

Comments

@bassosimone
Copy link
Contributor

This issue is about implementing a methodology called disguiser inside ooniprobe. We are going to use this methodology along with webconnectivity/websteps to increase our confidence and accuracy with respect to specific middleboxes. We will close this issue once we have fully implemented this methodology. As such, this issue is an umbrella for several activities.

With @hellais we have recently read Understanding the Practices of Global Censorship through
Accurate, End-to-End Measurements
. It's definitely an interesting paper that proposes an IMHO good methodology for detecting censoring middleboxes. (Though, it is sad that the paper says that OONI is not able to detect TLS blocking and I'm wondering whether this depends on us not having published a paper on OONI as a whole since 2012, even though we have been working on DoT/DoH blocking and QUIC blocking recently, so maybe we should just have a section of our website that lists the most recent papers we've been working on?)

The TL;DR about this methodology (called "disguiser") is that it rests on a server returning static DNS, HTTP and HTTPS responses and flags all responses that do not match the expected static responses as blocking. On top of that, disguiser has also code to deal with non-malicious transparent proxies (e.g., performance enhancing proxies) to single them out.

We think that it would be cool to integrate disguiser along with the methodologies we are currently using. Because disguiser is quite good at showing some kinds of censoring middleboxes, we are going to produce better measurements by also including it as a signal to determine blocking.

We will extend this issue to have a list of activities (possibly as sub-issues) required to integrate disguiser.

@bassosimone bassosimone added enhancement New feature request or improvement to existing functionality priority/medium Normal priority issue new nettest research prototype methodology issues related to the testing methodology data quality ooni/probe-engine labels May 6, 2022
@bassosimone bassosimone self-assigned this May 6, 2022
@bassosimone
Copy link
Contributor Author

Today I reached out to the paper's authors to understand if they already have a distributed Disguiser-server deployment (and whether they are okay for us using it) or we could collaborate on making such a deployment happen.

@hellais hellais added this to Roadmap Jan 7, 2025
@hellais hellais moved this to Icebox in Roadmap Jan 27, 2025
@hellais hellais added priority/low Nice to have and removed priority/medium Normal priority issue labels Jan 27, 2025
@hellais hellais removed this from Roadmap Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data quality enhancement New feature request or improvement to existing functionality methodology issues related to the testing methodology new nettest ooni/probe-engine priority/low Nice to have research prototype
Projects
None yet
Development

No branches or pull requests

2 participants