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

Prevent fingerprinting to improve anonymity & UX #351

Open
taoeffect opened this issue Feb 20, 2016 · 4 comments
Open

Prevent fingerprinting to improve anonymity & UX #351

taoeffect opened this issue Feb 20, 2016 · 4 comments
Labels

Comments

@taoeffect
Copy link

Apparently it's possible to distinguish Ricochet traffic from other Tor traffic, and that can lead to both anonymity and usability issues for the following reason:

  • If I want to attack Ricochet users I need to first be able to find them. If I can find them then I can start messing with their connections, harming UX (as in Still some weird flaky connections. #350). Addressing Still some weird flaky connections. #350 could involve re-creating circuits, but done too quickly that could result in an adversary pushing a user onto a circuit they fully control, threatening both their anonymity and potentially even revealing their communications.

By making Ricochet traffic appear like whatever the "average Tor traffic" is, it would be possible to both improve UX issues and prevent such an attack.

@JeremyRand
Copy link

How would one identify Ricochet traffic? Are you talking about traffic analysis in the general case? If so, that's a quite hard problem to solve, and may be impossible depending on the resources of the attacker.

@taoeffect
Copy link
Author

This is in reference to a private conversation I had with @special.

@special
Copy link
Member

special commented Jan 16, 2017

The distinguishers I would've been referring to are:

  1. Hidden services are relatively rare, and build a very unique pattern of circuits
  2. Ricochet clients connect to hidden services in unusual patterns that stand out from, say, a browser
  3. Ricochet circuits are long lived, very low traffic, etc, unlike the majority of tor circuits

As @JeremyRand says, traffic analysis is a really hard problem to solve, and Tor itself has taken almost no steps towards solving it in a general way. I don't think there's anything meaningful Ricochet could do without some sophisticated research demonstrating where the problems are and what defenses might actually work.

My preferred solutions would be for more general research to indicate a direction for tor itself to go towards solving traffic analysis problems, and for more people to use Ricochet for more reasons.

@Mikaela
Copy link

Mikaela commented Mar 11, 2019

Is Ricochet becoming more fingerprintable considering on how Tor 0.3.5 defaults to using version 3 for Hidden Services which Ricochet doesn't support (#575)?

There are a couple of changes in the 0.3.5 that may affect compatibility. First, the default version for newly created onion services is now v3. Use the HiddenServiceVersion option if you want to override this. Second, some log messages related to bootstrapping have changed; if you use stem, you may need to update to the latest version so it will recognize them.

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

No branches or pull requests

4 participants