News for hackers. Stuff that matters.
Re:Tor Browser 12.0 by schoen on Thursday December 08, 2022 @02:30AM (#33905241)
> people who otherwise seem to have tinfoil hats claiming that it’s not needed because Tor provides enough protection

I've been on the side of advocating for it, but the other side isn't making an obviously ridiculous argument. The onion protocol itself negotiates an end-to-end cryptographic session, authenticated by the onion site's public key, between the onion site and the end user. There's not cleartext traffic sent between a Tor exit node and the onion site or anything!

My argument in favor of TLS to onion sites was that, at least as of onion protocol v2, the cryptographic session was not itself TLS, and its security and threat model hadn't been as extensively reviewed as those of TLS. So it might turn out that there was something suboptimal there that the rendezvous server could then use to perform a sophisticated cryptographic attack.

I don't know if this is still true of onion protocol v3 or if the client-to-onion-site session is now also based on TLS.

Re:Tor Browser 12.0 by HackerNCoder on Thursday December 08, 2022 @03:59AM (#33905829)
No, v3 isn't TLS either. TLS is only used as a connector between hops (so the client connect to a node using TLS, and the nodes connect to each other using TLS), but that is it. (I think, if I'm wrong do tell me. I didn't go check the spec)
Re:Tor Browser 12.0 by schoen on Thursday December 08, 2022 @12:36PM (#33910674)
OK, I checked and it's indeed still not TLS.

https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/r...

I think the main question would be: are there cryptographic attacks that a rendezvous server could do that wouldn't work against TLS?