And then, using onion services, there are two three-relay circuits that meet at a rendezvous point. One picked by the onion, and the other by the user. So even deanonymizing one of those circuits would be insufficient.
But that's all theoretical. In practice, there are likely undisclosed vulnerabilities. Perhaps lots of them.
I do agree that the Tor browser standalone is rather a joke. Especially if it's in Windows. You at least want to be using Whonix. And if you really care, Whonix in Qubes.
No reason to think that they would not do that.
> And then, using onion services, there are two three-relay circuits that meet at a rendezvous point. One picked by the onion, and the other by the user. So even deanonymizing one of those circuits would be insufficient.
It would be sufficient to de-anonymise one of the parties.
> In practice, there are likely undisclosed vulnerabilities. Perhaps lots of them.
My point is that you do not need an undisclosed vulnerability to break tor if you have enough resources.
But will doing that be worth it to find someone like me? I doubt it. I'm just a hobbyist and writer.
Heck, until recently the tor team used 80-bit truncated sha-1, 1024-bit rsa, and 128-bit AES for their traffic, not to mention that the tor browser ships with javascript enabled by default.