New Release: Tor

New Release: Tor

May 15, 2020

After months of work, we have a new stable release series! If you build Tor from source, you can download the source code for on the website. Packages, including a new Tor Browser, should be available within the next several weeks.

Tor is the first stable release in the 0.4.3.x series. This series adds support for building without relay code enabled, and implements functionality needed for OnionBalance with v3 onion services. It includes significant refactoring of our configuration and controller functionality, and fixes numerous smaller bugs and performance issues.

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.3.x will be supported until around February 2021–later, if 0.4.4.x is later than anticipated.

Note also that support for 0.4.1.x is about to end on May 20 of this year; 0.4.2.x will be supported until September 15. We still plan to continue supporting 0.3.5.x, our long-term stable series, until Feb 2022.

Below are the changes since For a complete list of changes since, see the ReleaseNotes file.

Changes in version – 2020-05-15

  • Minor bugfixes (compiler compatibility):
    • Avoid compiler warnings from Clang 10 related to the use of GCC- style “/* falls through */” comments. Both Clang and GCC allow __attribute__((fallthrough)) instead, so that’s what we’re using now. Fixes bug 34078; bugfix on
    • Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix on
  • Minor bugfixes (logging):
    • Stop truncating IPv6 addresses and ports in channel and connection logs. Fixes bug 33918; bugfix on
    • Fix a logic error in a log message about whether an address was invalid. Previously, the code would never report that onion addresses were onion addresses. Fixes bug 34131; bugfix on

Link to original source

Categories: Tor Project

Leave a Reply

Your email address will not be published. Required fields are marked *