Tor Browser 11.0
blog.torproject.org
Tor Browser 11.0
1–10 of 100 posts
Re: Tor Browser 11.0
#2The first major release that lacks all support for most tor onion service domains. Tor v2 code was removed for security reasons. But the community still mostly uses v2.
Follow along with the death of most tor onion services in the plots at: https://www.encryptionin.space/tracking-hsdirs-and-the-versi... (here's a snapshot mirror if the site is slow under load, https://i.ibb.co/9NzVcsz/plot.png)
Re: Tor Browser 11.0
#3Great to see the project still going strong, we need this type of tools more than ever.
Re: Tor Browser 11.0
#4The first major release that lacks all support for most tor onion service domains. Tor v2 code was removed for security reasons. But the community still mostly uses v2. Follow along with the death of most tor onion services in the plots at: https://www.encryptionin.space/tracking-hsdirs-and-the-versi... (here's a snapshot mirror if the site is slow under load, https://i.ibb.co/9NzVcsz/plot.png )
Is this a strong enough push to change community behavior?
Re: Tor Browser 11.0
#5The first major release that lacks all support for most tor onion service domains. Tor v2 code was removed for security reasons. But the community still mostly uses v2. Follow along with the death of most tor onion services in the plots at: https://www.encryptionin.space/tracking-hsdirs-and-the-versi... (here's a snapshot mirror if the site is slow under load, https://i.ibb.co/9NzVcsz/plot.png )
Is this a strong enough push to change community behavior?
Doubtful. At some point it is likely the tor project will use their control of things to push a version consensus flag that will block v2 supporting relays from participating in the network.
Re: Tor Browser 11.0
#6Earlier quoted context omitted.
Is this a strong enough push to change community behavior?
Doubtful. At some point it is likely the tor project will use their control of things to push a version consensus flag that will block v2 supporting relays from participating in the network.
I’ve not been following Tor protocol news. Is this good for users?
Re: Tor Browser 11.0
#7Earlier quoted context omitted.
Doubtful. At some point it is likely the tor project will use their control of things to push a version consensus flag that will block v2 supporting relays from participating in the network.
I’ve not been following Tor protocol news. Is this good for users?
Yes, it probably is. Most people use tor because they just want a pseudoanonymous proxy to the clear web. For them the switch to v3 internally is important and probably required. For users of the .onion and onion services in general it's more split but I think most would say v2 going away is good. Soon it will be possible to spoof v2 domain prefixes at a feasible cost.
I personally don't like that v2 is being shut off instead of let run alongside v3. I thought I owned my tor domain I've been using the last decade but it's clear the tor project has the same amount of control as any registrar. I thought I could work on building a community like I have on the clear web but the tor project doesn't consider that a priority and will throw 15 years of history away to make sure non-technical users don't accidentally use v2 services. Tor is not really a place for community building. My mistake. I just won't use it anymore.
Re: Tor Browser 11.0
#8Earlier quoted context omitted.
Doubtful. At some point it is likely the tor project will use their control of things to push a version consensus flag that will block v2 supporting relays from participating in the network.
I’ve not been following Tor protocol news. Is this good for users?
Yes, but like IPV4 to IPV6 transition it's work.
Re: Tor Browser 11.0
#9I've wondered about the fact that (AFAIK) Tor routes only TCP:
1. Is that (still) correct?
2. Can't web pages include non-TCP traffic, and if so, is it routed via Tor? For example, doesn't some some streaming media use UDP?
3. QUIC doesn't use TCP (deliberately, I think). Won't that affect Tor's long-term viability if everyone eventually moves to QUIC?
Re: Tor Browser 11.0
#10I've wondered about the fact that (AFAIK) Tor routes only TCP: 1. Is that (still) correct? 2. Can't web pages include non-TCP traffic, and if so, is it routed via Tor? For example, doesn't some some streaming media use UDP? 3. QUIC doesn't use TCP (deliberately, I think). Won't that affect Tor's long-term viability if everyone eventually moves to QUIC?
1. For now
2. That kind of traffic mostly died out with plugins like Flash, streaming media today is usually encapsulated in small frequent chunks over the same https channels as the rest of the page are delivered as that's what's available in JS/native. WebRTC reintroduced some UDP stuff and can be used for streaming but is still mostly used for peer to peer calls.
3. https://gitweb.torproject.org/tor-browser-spec.git/plain/pos...