[tor-commits] [tor/release-0.3.5] Pick release date, copy changelog to releasenotes.

nickm at torproject.org nickm at torproject.org
Wed Mar 18 13:34:39 UTC 2020

commit 87fca699578e7190c37e68a290d72b4a77c2be40
Author: Nick Mathewson <nickm at torproject.org>
Date:   Wed Mar 18 09:06:06 2020 -0400

    Pick release date, copy changelog to releasenotes.
 ChangeLog    |  2 +-
 ReleaseNotes | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 94 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index e6c153be4..a2f214a97 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,4 +1,4 @@
-Changes in version - 2020-03-??
+Changes in version - 2020-03-18
   Tor backports many fixes from later Tor releases, including a
   fix for TROVE-2020-002, a major denial-of-service vulnerability that
   affected all released Tor instances since Using this
diff --git a/ReleaseNotes b/ReleaseNotes
index e7384d99f..ee4c456d2 100644
--- a/ReleaseNotes
+++ b/ReleaseNotes
@@ -2,6 +2,99 @@ This document summarizes new features and bugfixes in each stable
 release of Tor. If you want to see more detailed descriptions of the
 changes in each development snapshot, see the ChangeLog file.
+Changes in version - 2020-03-18
+  Tor backports many fixes from later Tor releases, including a
+  fix for TROVE-2020-002, a major denial-of-service vulnerability that
+  affected all released Tor instances since Using this
+  vulnerability, an attacker could cause Tor instances to consume a huge
+  amount of CPU, disrupting their operations for several seconds or
+  minutes. This attack could be launched by anybody against a relay, or
+  by a directory cache against any client that had connected to it. The
+  attacker could launch this attack as much as they wanted, thereby
+  disrupting service or creating patterns that could aid in traffic
+  analysis. This issue was found by OSS-Fuzz, and is also tracked
+  as CVE-2020-10592.
+  We do not have reason to believe that this attack is currently being
+  exploited in the wild, but nonetheless we advise everyone to upgrade
+  as soon as packages are available.
+  o Major bugfixes (security, denial-of-service, backport from
+    - Fix a denial-of-service bug that could be used by anyone to
+      consume a bunch of CPU on any Tor relay or authority, or by
+      directories to consume a bunch of CPU on clients or hidden
+      services. Because of the potential for CPU consumption to
+      introduce observable timing patterns, we are treating this as a
+      high-severity security issue. Fixes bug 33119; bugfix on
+ Found by OSS-Fuzz. We are also tracking this issue
+      as TROVE-2020-002 and CVE-2020-10592.
+  o Major bugfixes (linux seccomp sandbox, backport from
+    - Correct how we use libseccomp. Particularly, stop assuming that
+      rules are applied in a particular order or that more rules are
+      processed after the first match. Neither is the case! In
+      libseccomp <2.4.0 this lead to some rules having no effect.
+      libseccomp 2.4.0 changed how rules are generated, leading to a
+      different ordering, which in turn led to a fatal crash during
+      startup. Fixes bug 29819; bugfix on Patch by
+      Peter Gerber.
+  o Minor features (continuous integration, backport from
+    - Stop allowing failures on the Travis CI stem tests job. It looks
+      like all the stem hangs we were seeing before are now fixed.
+      Closes ticket 33075.
+  o Minor bugfixes (bridges, backport from
+    - Lowercase the configured value of BridgeDistribution before adding
+      it to the descriptor. Fixes bug 32753; bugfix on
+  o Minor bugfixes (crash, backport from
+    - When running Tor with an option like --verify-config or
+      --dump-config that does not start the event loop, avoid crashing
+      if we try to exit early because of an error. Fixes bug 32407;
+      bugfix on
+  o Minor bugfixes (logging, backport from
+    - If we encounter a bug when flushing a buffer to a TLS connection,
+      only log the bug once per invocation of the Tor process.
+      Previously we would log with every occurrence, which could cause
+      us to run out of disk space. Fixes bug 33093; bugfix
+      on
+  o Minor bugfixes (onion services v3, backport from
+    - Fix an assertion failure that could result from a corrupted
+      ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
+      bugfix on This issue is also tracked
+      as TROVE-2020-003.
+  o Minor bugfixes (rust, build, backport from
+    - Fix a syntax warning given by newer versions of Rust that was
+      creating problems for our continuous integration. Fixes bug 33212;
+      bugfix on
+  o Testing (backport from
+    - Re-enable the Travis CI macOS Chutney build, but don't let it
+      prevent the Travis job from finishing. (The Travis macOS jobs are
+      slow, so we don't want to have it delay the whole CI process.)
+      Closes ticket 32629.
+    - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
+      Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
+      fix the sandbox errors in 32722. Closes ticket 32240.
+  o Testing (continuous integration, backport from
+    - Use zstd in our Travis Linux builds. Closes ticket 32242.
+  o Testing (Travis CI, backport from
+    - Remove a redundant distcheck job. Closes ticket 33194.
+    - Sort the Travis jobs in order of speed: putting the slowest jobs
+      first takes full advantage of Travis job concurrency. Closes
+      ticket 33194.
+    - Stop allowing the Chutney IPv6 Travis job to fail. This job was
+      previously configured to fast_finish (which requires
+    - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
+      tool to produce detailed diagnostic output. Closes ticket 32792.
 Changes in version - 2019-12-09
   Tor backports serveral fixes from later releases, including
   several that affect bridge users, relay stability, onion services,

More information about the tor-commits mailing list