New release candidate: 0.4.4.4-rc

There's a new alpha release available for download. If you build Tor from source, you can download the source code for 0.4.4.4-rc from the download page. Packages should be available over the coming weeks, with a new alpha Tor Browser release likely in the coming weeks.

Remember, this is a release candidate, not a a stable release: you should only run this if you'd like to find and report more bugs than usual.

Tor 0.4.4.4-rc is the first release candidate in its series. It fixes several bugs in previous versions, including some that caused annoying behavior for relay and bridge operators.

Changes in version 0.4.4.4-rc - 2020-08-13

  • Minor features (security):
    • Channels using obsolete versions of the Tor link protocol are no longer allowed to circumvent address-canonicity checks. (This is only a minor issue, since such channels have no way to set ed25519 keys, and therefore should always be rejected for circuits that specify ed25519 identities.) Closes ticket 40081.
  • Minor features (defense in depth):
    • Wipe more data from connection address fields before returning them to the memory heap. Closes ticket 6198.

 

  • Minor bugfixes (correctness, buffers):
    • Fix a correctness bug that could cause an assertion failure if we ever tried using the buf_move_all() function with an empty input buffer. As far as we know, no released versions of Tor do this. Fixes bug 40076; bugfix on 0.3.3.1-alpha.
  • Minor bugfixes (linux seccomp2 sandbox):
    • Fix startup crash with seccomp sandbox enabled when tor tries to open the data directory. Patch from Daniel Pinto. Fixes bug 40072; bugfix on 0.4.4.3-alpha-dev.
  • Minor bugfixes (onion service v3):
    • Remove a BUG() warning that could trigger in certain unlikely edge-cases. Fixes bug 34086; bugfix on 0.3.2.1-alpha.
  • Minor bugfixes (rate limiting, bridges, pluggable transports):
    • On a bridge, treat all connections from an ExtORPort as remote by default for the purposes of rate-limiting. Previously, bridges would treat the connection as local unless they explicitly received a "USERADDR" command. ExtORPort connections still count as local if there is a USERADDR command with an explicit local address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
  • Minor bugfixes (relay, self-testing):
    • When starting up as a relay, if we haven't been able to verify that we're reachable, only launch reachability tests at most once a minute. Previously, we had been launching tests up to once a second, which was needlessly noisy. Fixes bug 40083; bugfix on 0.2.8.1-alpha.
  • Minor bugfixes (testing):
    • When running the subsystem order check, use the Python binary configured with the PYTHON environment variable. Fixes bug 40095; bugfix on 0.4.4.1-alpha.
  • Minor bugfixes (windows):
    • Fix a bug that prevented Tor from starting if its log file grew above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
Anonymous

September 13, 2020

Permalink

Tor NOTICE: Tor has been idle for 33223 seconds; assuming established circuits no longer work.
Tor NOTICE: Heartbeat: Tor's uptime is 2 days 14:29 hours, with 5 circuits open. I've sent 36.41 MB and received 227.67 MB.
Tor NOTICE: While not bootstrapping, fetched this many bytes:
Tor NOTICE: 2548239 (consensus network-status fetch)
Tor NOTICE: 396326 (microdescriptor fetch)
Tor NOTICE: Average packaged cell fullness: 45.884%. TLS write overhead: 5%
Tor WARN: Failed to find node for hop #1 of our path. Discarding this circuit.
Tor NOTICE: Our circuit 0 (id: 3425) died due to an invalid selected path, purpose General-purpose client. This may be a torrc configuration issue, or a bug. [9 similar message(s) suppressed in last 3600 seconds]
Tor WARN: Guard catmeme5 ($9A48EC8AAFB2E8C9E20408596383DB74F1196747) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 6/166. Use counts are 1/1. 164 circuits completed, 0 were unusable, 158 collapsed, and 163 timed out. For reference, your timeout cutoff is 60 seconds.
Tor NOTICE: No circuits are opened. Relaxed timeout for circuit 3442 (a Measuring circuit timeout 3-hop circuit in state waiting to see how other guards perform with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.