10 ms·
Tor Browser 11.0
- superkuh 5y agoThe 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-version-of-tor-they-run 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 https://i.ibb.co/9NzVcsz/plot.png)
- bberenberg 5y agoIs this a strong enough push to change community behavior?
- superkuh 5y agoDoubtful. 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.
- the_other 5y agoI’ve not been following Tor protocol news. Is this good for users?
- superkuh 5y agoYes, 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.
- fsflover 5y agoYou may be interested in I2P then.
- sowithit 5y agoI am curious: why can't you redirect your community to a new v3 address? Deprecating v2 onion services has been publicly planned for several years now, and it is being done for security reasons (e.g. name collisions and weak crypto). Honestly, it would seem irresponsible of the Tor community not to stop supporting insecure versions of Tor.
- I_Byte 5y agoThe depreciation of v2 addresses is the best course of action in this case. v2 addresses consist of the first 80 bits of the SHA-1 hash of the hidden services 1024 bit public RSA key. This sentence alone is enough to make any cryptographer cringe, it is really bad! (SHA-1 has been shown to be broken and it is suspected that 1024 bit RSA can be cracked by any determined well funded state actor) Also, Tor Project has had v2 address depreciation on it's roadmap for 2 years now, they have given hidden service operators plenty of time to prime their community for the v2 --> v3 switch. This gradual change is way better than scrambling to depreciate v2 addresses in response to some state actor publicly breaking the RSA keys of v2 hidden services. > I thought I owned my tor domain You may now, but if v2 is kept around soon you won't be the only one with the domains private key.
- brokenmachine 5y ago> v2 addresses consist of the first 80 bits of the SHA-1 hash of the hidden services 1024 bit public RSA key. What is the danger of exposing the hash of the services public key? Public keys are public anyway.
- laverya 5y agoIt's not the fact that the hash of the public key is exposed, it's the fact that 1. so little of the hash is exposed (only 80 bits of 160 for sha1), making it easier to find a collision 2. the hash is so weak (sha1 is widely considered broken), making it easier to find a collision 3. the underlying public key is so small, making it easier to derive the private key from the public key IIRC if you find a collision you can use that to take over / contest an onion address, and obviously reversing the public key into a private key gives you as much control over an onion address as the original creator.
- helios_invictus 5y agoYes, but like IPV4 to IPV6 transition it's work.
- 0des 5y agoIt's most like going from https to https2 (whatever that may be) in that it changes the fundamental systems beneath it resulting in having stronger keys, longer keys, composed with different tech.
- 0des 5y agoIt's most like going from http to https in that it changes the fundamental systems beneath it resulting in having stronger keys, longer keys, composed with different tech. You notice the new onion addresses are much longer, and created differently, this is that change.
- georgyo 5y agoUnlike IPv4 IPv6, there isn't an authority name service to advertise both connectable addresses. This makes discovery for the end user an explicit action. If they cannot connect on V2, the method to discover v3 is almost definitely out of band and potentially in the prone to hijacking.
- Aachen 5y agoSo it would be best if those services simply advertise their new address on the v2 domain right? Rather than sit still and lose their traffic when everyone's forced to, or when attacks really become feasible. It's not even a hard upgrade, afaik it's literally just a change of what address users have to copy/bookmark and nothing else. I just don't get what the reason to not upgrade is.
- saurik 5y ago> afaik it's literally just a change of what address users have to copy/bookmark and nothing else ...and all of the links that everyone has embedded in content all over the ecosystem.
- brokenmachine 5y agoWhat's a HSDir?
- Koshkin 5y agoAccording to Google, it's either a high school directory or a hidden service directory.
- edgyquant 5y agoSince we’re discussing TOR it’s probably the latter
- HackerNCoder 5y agoI should probably add something about that to the post. Sorta like the Tor version of DNS. It's where your Tor goes to get information about an onion, e.g. how to connect to it. Tor versions that don't support v2 will refuse to host this information, and so if all 6 HSDirs of an v2 onion doesn't support it, the onion will be unreachable. Maybe understanding a bit about how onion services work will help: https://community.torproject.org/onion-services/overview/ https://community.torproject.org/onion-services/overview/
- triter 5y agoGreat to see the project still going strong, we need this type of tools more than ever.
- agumonkey 5y agoI don't know about the low level / security details. But the Tor team constantly pushed good upgrades for a long time. Seriously impressive. Works great and is slick on pc and mobile.
- spurgu 5y agoSame. The world would feel quite dystopian without Tor, Signal and other similar software aiming to preserve your privacy. I rarely use Tor but I'm soooo happy it exists. Just started wondering: If Tor disappeared off the face of the earth right now, what would be the replacement? 1. Would it be an existing alternative that would become dominant in the space? 2. Would an identical software/network be built? 3. Would something new (and better) be built to replace it (and how would that look like)?
- yjftsjthsd-h 5y agoIf TOR went away tomorrow, I assume i2p would pick up the slack; it's already there and AFAIK a good alternative, just with a smaller network and less emphasis on exit nodes.
- therein 5y agoNetwork isn't even necessarily smaller. Since it has a lesser emphasis on exit nodes, each node is a relay and there are more of them than Tor relay nodes.
- wolverine876 5y agoI'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?
- zamadatix 5y ago1. 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/position-papers/HTTP3/HTTP3.pdf https://gitweb.torproject.org/tor-browser-spec.git/plain/pos...
- wolverine876 5y agoThank you! 2. So there is some non-TCP traffic. What happens when you load that page in Tor Browser, for example? Does it leak back to your clear Internet connection? Is it simply dropped? This seems like a critical issue. 3. Thanks. Do you know when that was written? To save others clicking the link and finding the applicable section, I'll paste it below. Designing and building your own protocol for Internet transport, compatible with the entire net and performing competitively enough to be usable, sounds like quite a project for a small organization. Note that Google didn't do that; they used UDP for QUIC. 7 Tor Network Compatibility Concerns Our final area of concern is continued compatibility of the Tor network with future versions of the HTTP proto- col. It is our understanding that there is a desire for future versions of HTTP to move to a UDP transport layer so that reliability, congestion control, and client mobility will be more directly under control of the client user agent. At present, the Tor Network is only capable of carrying TCP traffic. While it will be possible to support the transit of UDP datagrams using our existing TCP overlay network without significant anonymity risks within a year’s time or sooner, it is unlikely that this level of support will be sufficient to warrant the use of a finely-tuned UDP version of HTTP rather than a TCP variant. Long term, our goal is to transition the entire Tor network to our own datagram protocol with custom con- gestion and flow control to better support both native datagram transport and end-to-end flow control. However, additional research is still needed to examine the anonymity implications associated with this transition[12]. Our present estimate is that a full network transition to UDP is at least five years away. We are also concerned that even after a full network transition to a datagram transport, it is likely that the congestion, flow, and reliability control of a UDP version of HTTP may still end up performing poorly over higher-latency overlay networks such as ours. For these reasons, we are especially interested in ensuring that overlay networks are taken into account in the design of any UDP-based future versions of HTTP, and also prefer to retain the ability to use future HTTP versions over TCP, should the UDP implementations prove sub-optimal for our use case.
- Shadonototra 5y agoTor lost all credibility for sticking to firefox, not to mention all the other security issues discovered over the past few years
- yjftsjthsd-h 5y agoTOR is a privacy tool first; rebasing to a browser that aggressively undermines privacy at every turn would be a questionable use of resources.
- mike_hock 5y agoFirefox as opposed to what?
- Shadonototra 5y agoChromium
- edgyquant 5y agoWhat advantages would that bring?
- 0xdeadb00f 5y agoSecurity. I'm a die hard Firefox user. But chromium has insanely good site isolation and some other great security features. It was built with privilege separation in mind almost since day one, something Firefox does not do. My source here is OpenBSD devs, who said that Chromium was easy to sandbox with pledge+unveil, because for the most part the code was already written in such a way (to separate privileges). Firefox was a pain to sandbox, because its code is not written in the same way. Firefox is only now catching up in regard to site isolation.
- southerntofu 5y ago> Firefox is only now catching up in regard to site isolation. Yes, but firefox has other benefits. if only that, a cooperative team that's happy to take patches as part of the "tor uplift" project, whereas Chrome wants to fingerprint every single user and makes projects like TBB harder to implement. Also, i personally think it's a good thing that TBB is a noscript-first browser. Everything involving JS, even with a 10 feet pole, is a glaring security issue. So yes you can enable JS and the site isolation isn't the best, but truth is just use "Safest" mode and you'll be fine.
- giga_chad 5y agoTOR has been an invaluable tool for me for its ability to circumvent state censorship in an undetectable way. At some point in my career I was involved in some journalistic reporting in Saudi Arabia; had I used a regular VPN, it could have been easily detected, and in best case defeated, worst case put me in serious legal trouble, which in Saudi Arabia can easily end in corporal punishment and/or death. TOR allowed me to circumvent all that and keep reporting on government official and police force corruption in a safe way, in a country that frankly could use a lot more of this type of journalism. Thank you, TOR project!
- pfundstein 5y agoTor has long been billed as a tool for journalists to fly under the radar and avoid persecution, but it's great to hear these case studies from the horse's mouth. Thanks to you and other journalists who risk life and limb to report on and within these abusive regimes.
- hellbannedguy 5y agoThat is impressive. People throw around impressive too much, but I couldn't imagine pissing off any official in that country.
- wolverine876 5y agoI don't know the parent or their situation, but if you need similar security I would be very cautious about taking the parent literally. Sorry if I sound like a jerk; it sounds like the parent has taken great risks for the public good, but I don't want people to be hurt: I'm almost certain that Tor use is easily detected; that is what I've always (100%) read from security experts and it makes sense to me: Traffic patterns, packet fingerprints (encryption implementations, size, etc.), and of course all the traffic is going to and from a Tor node, a list of which is available to every Tor user. The attacker may not be able to read the contents or metadata, but they will know you are using Tor. Tor users are a very small population; it's a red flag. The same is true for websites, etc. that you visit: They can easily see that your traffic is coming from a Tor exit node. Also, exit nodes are of course as vulnerable to attack as any other server, and they provide access to the ip addresses you connect with and, when https isn't used or properly implemented, to the contents of the communication. Tor is not a panacea. Also, don't conflate Tor with Tor Browser, which I've read is possibly the worst security choice among browsers - a huge target without the resources to secure itself.
- chrismorgan 5y agoPet peeve: the word “deprecate” is misused in this article. (It’s used mostly correctly in the “v2 deprecation timeline” post.) > Final deprecation of v2 onion services Final removal, not deprecation. > v2 onion services would be deprecated in late 2021 No, removed in late 2021, after being deprecated for over a year (from July or September, depending on how you count it).
- 0xdeadb00f 5y ago> Known Issues Some of these issues seem like pretty big issues: > Bug 40671: Fonts don't render > Bug 40695: JS enabled on Safest in Windows (new)
- alexeiz 5y agoI've updated, and now the font rendering in the Tor's interface is FU'ed. Good thing I don't rely on the Tor browser. Otherwise I'd be so pissed.
- johnisgood 5y agoPrecisely this. Tor browser after this update looks pretty FU'ed. I hope they are going to fix this one ASAP. This update is actually so messed up, that I had to delete my whole profile and start from scratch, because everything was missing, including icons and text. It starts and is usable with the fresh profile, but this should seriously be fixed.
- neilv 5y agoMy other daily browser is Firefox ESR, so Tor Browser 11 is the first I've seen these strange new tabs. It's like they kept making the active tab harder to distinguish, until eventually someone had a thought, "the active tab is really hard to distinguish, so let's make this puppy dominate the entire UI". This is my least-favorite UI change since the intermediate submenu "Close Multiple Tabs" was introduced, to make a somewhat tedious mousing task even more work.