This blog post aims to give some more context about an attack that happened earlier this year on the Tor network and what we have done to address this type of attack. We also want to share some information about the Tor Project’s capacity right now and some of our plans for the future.
The biggest change introduced thanks to this project is a generic publish-subscribe mechanism for delivering messages internally. It is meant to help us improve the modularity of our code by avoiding direct coupling between modules that don't actually need to invoke one another.
I'd like to tell you about some of our work your contributions can help over the coming year. I'll be focusing on things that my team works on in the "tor" program itself.
The Tor network is comprised of thousands of volunteer-run relays around the world, and millions of people rely on it for privacy and freedom online everyday. To monitor the Tor network's performance, detect attacks on it, and better distribute load across the network, we employ what we call Tor bandwidth scanners.
OnionShare is an open source tool for securely and anonymously sending and receiving files using Tor onion services. OnionShare 2 adds anonymous dropboxes, supports new Tor addresses, and is translated into a dozen new languages.
The latest Tor alpha release included a new feature to address traffic congestion in the Tor network. The new algorithm —Kernel Informed Socket Transport (KIST)— prevents connections between Tor relays from becoming overwhelmed by changing how traffic is distributed throughout the Tor network.
We, the Debian project and the Tor Project are enabling Tor
Around midnight on August 4th we were notified by a few people that a large number of hidden service addresses have disappeared from the Tor Network.
