Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

AFAIK the fact of TOR usage is rather easy to detect. AFAIK (from some news here on HN) you can get SWATed and arrested for a mere suspicion (e.g a false positive by an automated traffic analysis system) of using an end-to-end encrypting messenger or even Twitter in Turkey. I doubt it is legal and safe to use TOR in such countries. We need something that is harder to detect on the client ISP side.


> AFAIK the fact of TOR usage is rater easy to detect.

That's why I said: "Then use meek-amazon as a pluggable transport which should work." meek-amazon makes your traffic look like you're talking to:

> url=https://d2cly7j4zqgua7.cloudfront.net/ front=a0.awsstatic.com

With the snowflake pluggable transport (only available with Linux and Mac alphas for now) the traffic looks like WebRTC.

You can read more about them here:

https://trac.torproject.org/projects/tor/wiki/doc/meek

https://trac.torproject.org/projects/tor/wiki/doc/Snowflake


> "We need something that is harder to detect on the client ISP side."

That's what Telex[1][2] is designed to do. Too bad the project seems to have stalled.

[1] https://telex.cc

[2] https://en.wikipedia.org/wiki/Telex_(anti-censorship_system)


it is by no means foolproof and won't get around a deep packet inspection/flow analysis system, but this is why obfsproxy exists:

https://www.google.com/search?q=obfsproxy+tor&ie=utf-8&oe=ut...


But be sure not to use the default bundled obfs4 bridges, they're known.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: