progress report | Tor Blog

Tor's New Anti-Censorship Team: Defending The Open Internet

We formed an anti-censorship team to understand network censorship, build technology to circumvent it, and to make the Tor network accessible to everyone.

24 comments

Announcing Tor Reports

For the past four years, I've been summarizing progress of Tor on the blog.

14 comments

April 2012 Progress Report

Our progress report for April 2012 is now available.

March 2012 Progress Report

Our progress report for March 2012 is now available.

6 comments

February 2012 Progress Report

Our progress report for February 2012 is now available. It hightlights recent work with deep packet inspection and censorship circumvention in Iran and Kazakhstan.

18 comments

January 2012 Progress Report

Our progress report for January 2012 is available now.

5 comments

December 2011 Progress Report

Our progress report for December 2011 is available as a pdf with pretty graphs an

5 comments

November 2011 Progress Report

The progress report for November 2011 is released as pdf and

4 comments

October 2011 Progress Report

The October 2011 Progress report is available in PDF and

4 comments

September 2011 Progress Report

In September 2011 we made progress in a number of areas, such as handling issues in Iran's use of DPI to block tor, new versions of Tor, Tails 0.8 release, and more.

2 comments

Upcoming Events

October 08, 2020

Roger keynotes at CyberSec&AI

See All Upcoming Events

Recent Updates

Tor’s Bug Smash Fund, Year 2: $106,709 Raised!

Let’s start this post with a rousing THANK YOU to the Tor community!

New Release: Tor Browser 10.0a7

Tor Browser 10.0a7 is now available from the Tor Browser Alpha download page and also from our

Updates on Tor Project’s Board

We would like to share some updates regarding the Tor Project’s Board. Last year Megan Price stepped down as she took a second maternity leave.

After months of work, we have a new stable release series!
If you build Tor from source, you can download the source
code for 0.4.4.5 on the
download page.
Packages should be available within the next several weeks, with a new Tor Browser by some time next week.

Tor 0.4.4.5 is the first stable release in the 0.4.4.x series. This series improves our guard selection algorithms, adds v3 onion balance support, improves the amount of code that can be disabled when running without relay support, and includes numerous small bugfixes and enhancements. It also lays the ground for some IPv6 features that we'll be developing more in the next (0.4.5) series.

Per our support policy, we support each stable release series for nine months after its first stable release, or three months after the first stable release of the next series: whichever is longer. This means that 0.4.4.x will be supported until around June 2021--or later, if 0.4.5.x is later than anticipated.

Note also that support for 0.4.2.x has just ended; support for 0.4.3 will continue until Feb 15, 2021. We still plan to continue supporting 0.3.5.x, our long-term stable series, until Feb 2022.

Below are the changes since 0.4.3.6-rc. For a complete list of changes since 0.4.4.4-rc, see the ChangeLog file.

Changes in version 0.4.4.5 - 2020-09-15

Major features (Proposal 310, performance + security):
- Implements Proposal 310, "Bandaid on guard selection". Proposal 310 solves load-balancing issues with older versions of the guard selection algorithm, and improves its security. Under this new algorithm, a newly selected guard never becomes Primary unless all previously sampled guards are unreachable. Implements recommendation from 32088. (Proposal 310 is linked to the CLAPS project researching optimal client location-aware path selections. This project is a collaboration between the UCLouvain Crypto Group, the U.S. Naval Research Laboratory, and Princeton University.)
Major features (fallback directory list):
- Replace the 148 fallback directories originally included in Tor 0.4.1.4-rc (of which around 105 are still functional) with a list of 144 fallbacks generated in July 2020. Closes ticket 40061.