1 Changes in version 0.3.5.6-rc - 2018-12-18
2 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
3 It is the first release candidate in the 0.3.5.x series; if no further
4 huge bugs are found, our next release may be the stable 0.3.5.x.
6 o Minor features (continuous integration, Windows):
7 - Always show the configure and test logs, and upload them as build
8 artifacts, when building for Windows using Appveyor CI.
11 o Minor features (fallback directory list):
12 - Replace the 150 fallbacks originally introduced in Tor
13 0.3.3.1-alpha in January 2018 (of which ~115 were still
14 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
15 removed) generated in December 2018. Closes ticket 24803.
17 o Minor features (geoip):
18 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
19 Country database. Closes ticket 28744.
21 o Minor bugfixes (compilation):
22 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
23 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
25 o Minor bugfixes (continuous integration, Windows):
26 - Explicitly specify the path to the OpenSSL library and do not
27 download OpenSSL from Pacman, but instead use the library that is
28 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
30 o Minor bugfixes (onion service v3):
31 - When deleting an ephemeral onion service (DEL_ONION), do not close
32 any rendezvous circuits in order to let the existing client
33 connections finish by themselves or closed by the application. The
34 HS v2 is doing that already so now we have the same behavior for
35 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
37 o Minor bugfixes (restart-in-process, boostrap):
38 - Add missing resets of bootstrap tracking state when shutting down
39 (regression caused by ticket 27169). Fixes bug 28524; bugfix
42 o Minor bugfixes (testing):
43 - Use a separate DataDirectory for the test_rebind script.
44 Previously, this script would run using the default DataDirectory,
45 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
46 Patch from Taylor R Campbell.
47 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
48 bugfix on 0.3.0.1-alpha.
50 o Minor bugfixes (Windows):
51 - Correctly identify Windows 8.1, Windows 10, and Windows Server
52 2008 and later from their NT versions. Fixes bug 28096; bugfix on
53 0.2.2.34; reported by Keifer Bly.
54 - On recent Windows versions, the GetVersionEx() function may report
55 an earlier Windows version than the running OS. To avoid user
56 confusion, add "[or later]" to Tor's version string on affected
57 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
59 - Remove Windows versions that were never supported by the
60 GetVersionEx() function. Stop duplicating the latest Windows
61 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
62 reported by Keifer Bly.
65 - Increase logging and tag all log entries with timestamps in
66 test_rebind.py. Provides diagnostics for issue 28229.
68 o Code simplification and refactoring (shared random, dirauth):
69 - Change many tor_assert() to use BUG() instead. The idea is to not
70 crash a dirauth but rather scream loudly with a stacktrace and let
71 it continue run. The shared random subsystem is very resilient and
72 if anything wrong happens with it, at worst a non coherent value
73 will be put in the vote and discarded by the other authorities.
76 o Documentation (onion services):
77 - Document in the man page that changing ClientOnionAuthDir value or
78 adding a new file in the directory will not work at runtime upon
79 sending a HUP if Sandbox 1. Closes ticket 28128.
80 - Note in the man page that the only real way to fully revoke an
81 onion service v3 client authorization is by restarting the tor
82 process. Closes ticket 28275.
85 Changes in version 0.3.5.5-alpha - 2018-11-16
86 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
87 including several that we hope to backport to older release series in
90 o Major bugfixes (OpenSSL, portability):
91 - Fix our usage of named groups when running as a TLS 1.3 client in
92 OpenSSL 1.1.1. Previously, we only initialized EC groups when
93 running as a relay, which caused clients to fail to negotiate TLS
94 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
97 o Minor features (geoip):
98 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
99 Country database. Closes ticket 28395.
101 o Minor bugfixes (compilation):
102 - Initialize a variable unconditionally in aes_new_cipher(), since
103 some compilers cannot tell that we always initialize it before
104 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
106 o Minor bugfixes (connection, relay):
107 - Avoid a logging a BUG() stacktrace when closing connection held
108 open because the write side is rate limited but not the read side.
109 Now, the connection read side is simply shut down until Tor is
110 able to flush the connection and close it. Fixes bug 27750; bugfix
113 o Minor bugfixes (continuous integration, Windows):
114 - Manually configure the zstd compiler options, when building using
115 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
116 not come with a pkg-config file. Fixes bug 28454; bugfix
118 - Stop using an external OpenSSL install, and stop installing MSYS2
119 packages, when building using mingw on Appveyor Windows CI. Fixes
120 bug 28399; bugfix on 0.3.4.1-alpha.
122 o Minor bugfixes (documentation):
123 - Make Doxygen work again after the code movement in the 0.3.5
124 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
126 o Minor bugfixes (Linux seccomp2 sandbox):
127 - Permit the "shutdown()" system call, which is apparently used by
128 OpenSSL under some circumstances. Fixes bug 28183; bugfix
131 o Minor bugfixes (logging):
132 - Stop talking about the Named flag in log messages. Clients have
133 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
136 o Minor bugfixes (memory leaks):
137 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
138 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
140 o Minor bugfixes (onion services):
141 - On an intro point for a version 3 onion service, stop closing
142 introduction circuits on an NACK. This lets the client decide
143 whether to reuse the circuit or discard it. Previously, we closed
144 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
145 0.3.2.1-alpha. Patch by Neel Chaunan.
146 - When replacing a descriptor in the client cache, make sure to
147 close all client introduction circuits for the old descriptor, so
148 we don't end up with unusable leftover circuits. Fixes bug 27471;
149 bugfix on 0.3.2.1-alpha.
152 Changes in version 0.3.5.4-alpha - 2018-11-08
153 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
154 improves our continuous integration support. It continues our attempts
155 to stabilize this alpha branch and build it into a foundation for an
156 acceptable long-term-support release.
158 o Major bugfixes (compilation, rust):
159 - Rust tests can now build and run successfully with the
160 --enable-fragile-hardening option enabled. Doing this currently
161 requires the rust beta channel; it will be possible with stable
162 rust once Rust version 1.31 is released. Patch from Alex Crichton.
163 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
165 o Major bugfixes (embedding, main loop):
166 - When DisableNetwork becomes set, actually disable periodic events
167 that are already enabled. (Previously, we would refrain from
168 enabling new ones, but we would leave the old ones turned on.)
169 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
171 o Minor features (continuous integration):
172 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
174 - Add new CI job to Travis configuration to run stem-based
175 integration tests. Closes ticket 27913.
177 o Minor features (Windows, continuous integration):
178 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
179 Appveyor's CI. Closes ticket 28318.
181 o Minor bugfixes (C correctness, also in 0.3.4.9):
182 - Avoid undefined behavior in an end-of-string check when parsing
183 the BEGIN line in a directory object. Fixes bug 28202; bugfix
186 o Minor bugfixes (compilation):
187 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
188 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
190 o Minor bugfixes (compilation, OpenSolaris):
191 - Fix compilation on OpenSolaris and its descendants by adding a
192 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
195 o Minor bugfixes (configuration):
196 - Refuse to start with relative file paths and RunAsDaemon set
197 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
200 o Minor bugfixes (directory authority, also in 0.3.4.9):
201 - Log additional info when we get a relay that shares an ed25519 ID
202 with a different relay, instead of a BUG() warning with a
203 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
205 o Minor bugfixes (onion service v3):
206 - Build the service descriptor's signing key certificate before
207 uploading, so we always have a fresh one: leaving no chances for
208 it to expire service side. Fixes bug 27838; bugfix
211 o Minor bugfixes (onion service v3, client authorization):
212 - Fix an assert() when adding a client authorization for the first
213 time and then sending a HUP signal to the service. Before that,
214 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
216 o Minor bugfixes (onion services):
217 - Unless we have explicitly set HiddenServiceVersion, detect the
218 onion service version and then look for invalid options.
219 Previously, we did the reverse, but that broke existing configs
220 which were pointed to a v2 service and had options like
221 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
222 0.3.5.1-alpha. Patch by Neel Chauhan.
224 o Minor bugfixes (portability):
225 - Make the OPE code (which is used for v3 onion services) run
226 correctly on big-endian platforms. Fixes bug 28115; bugfix
229 o Minor bugfixes (protover, rust):
230 - Reject extra commas in version strings. Fixes bug 27197; bugfix
233 o Minor bugfixes (relay shutdown, systemd):
234 - Notify systemd of ShutdownWaitLength so it can be set to longer
235 than systemd's TimeoutStopSec. In Tor's systemd service file, set
236 TimeoutSec to 60 seconds to allow Tor some time to shut down.
237 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
239 o Minor bugfixes (rust, also in 0.3.4.9):
240 - Fix a potential null dereference in protover_all_supported(). Add
241 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
242 - Return a string that can be safely freed by C code, not one
243 created by the rust allocator, in protover_all_supported(). Fixes
244 bug 27740; bugfix on 0.3.3.1-alpha.
246 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
247 - Fix an API mismatch in the rust implementation of
248 protover_compute_vote(). This bug could have caused crashes on any
249 directory authorities running Tor with Rust (which we do not yet
250 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
252 o Minor bugfixes (testing):
253 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
254 27968; bugfix on 0.3.5.1-alpha.
256 o Minor bugfixes (testing, also in 0.3.4.9):
257 - Treat backtrace test failures as expected on BSD-derived systems
258 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
259 (FreeBSD failures have been treated as expected since 18204 in
260 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
262 o Documentation (onion service manpage):
263 - Improve HSv3 client authorization by making some options more
264 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
267 Changes in version 0.3.4.9 - 2018-11-02
268 Tor 0.3.4.9 is the second stable release in its series; it backports
269 numerous fixes, including a fix for a bandwidth management bug that
270 was causing memory exhaustion on relays. Anyone running an earlier
271 version of Tor 0.3.4.9 should upgrade.
273 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
274 - Fix compilation on ARM (and other less-used CPUs) when compiling
275 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
277 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
278 - Make sure Tor bootstraps and works properly if only the
279 ControlPort is set. Prior to this fix, Tor would only bootstrap
280 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
281 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
283 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
284 - When our write bandwidth limit is exhausted, stop writing on the
285 connection. Previously, we had a typo in the code that would make
286 us stop reading instead, leading to relay connections being stuck
287 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
290 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
291 - Fix a use-after-free error that could be caused by passing Tor an
292 impossible set of options that would fail during options_act().
293 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
295 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
296 - Don't do a distcheck with --disable-module-dirauth in Travis.
297 Implements ticket 27252.
298 - Only run one online rust build in Travis, to reduce network
299 errors. Skip offline rust builds on Travis for Linux gcc, because
300 they're redundant. Implements ticket 27252.
301 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
302 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
303 Linux with default settings, because all the non-default builds
304 use gcc on Linux. Implements ticket 27252.
306 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
307 - Use the Travis Homebrew addon to install packages on macOS during
308 Travis CI. The package list is the same, but the Homebrew addon
309 does not do a `brew update` by default. Implements ticket 27738.
311 o Minor features (geoip):
312 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
313 Country database. Closes ticket 27991.
315 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
316 - Fix an integer overflow bug in our optimized 32-bit millisecond-
317 difference algorithm for 32-bit Apple platforms. Previously, it
318 would overflow when calculating the difference between two times
319 more than 47 days apart. Fixes part of bug 27139; bugfix
321 - Improve the precision of our 32-bit millisecond difference
322 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
323 bugfix on 0.3.4.1-alpha.
324 - Relax the tolerance on the mainloop/update_time_jumps test when
325 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
328 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
329 - Avoid undefined behavior in an end-of-string check when parsing
330 the BEGIN line in a directory object. Fixes bug 28202; bugfix
333 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
334 - Only install the necessary mingw packages during our appveyor
335 builds. This change makes the build a little faster, and prevents
336 a conflict with a preinstalled mingw openssl that appveyor now
337 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
339 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
340 - Rewrite our assertion macros so that they no longer suppress the
341 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
343 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
344 - Stop reinstalling identical packages in our Windows CI. Fixes bug
345 27464; bugfix on 0.3.4.1-alpha.
347 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
348 - Log additional info when we get a relay that shares an ed25519 ID
349 with a different relay, instead making a BUG() warning. Fixes bug
350 27800; bugfix on 0.3.2.1-alpha.
352 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
353 - Avoid a double-close when shutting down a stalled directory
354 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
356 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
357 - Fix a bug warning when closing an HTTP tunnel connection due to an
358 HTTP request we couldn't handle. Fixes bug 26470; bugfix
361 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
362 - Ensure circuitmux queues are empty before scheduling or sending
363 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
365 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
366 - When the onion service directory can't be created or has the wrong
367 permissions, do not log a stack trace. Fixes bug 27335; bugfix
370 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
371 - Close all SOCKS request (for the same .onion) if the newly fetched
372 descriptor is unusable. Before that, we would close only the first
373 one leaving the other hanging and let to time out by themselves.
374 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
376 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
377 - When selecting a v3 rendezvous point, don't only look at the
378 protover, but also check whether the curve25519 onion key is
379 present. This way we avoid picking a relay that supports the v3
380 rendezvous but for which we don't have the microdescriptor. Fixes
381 bug 27797; bugfix on 0.3.2.1-alpha.
383 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
384 - Reject protocol names containing bytes other than alphanumeric
385 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
388 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
389 - Compute protover votes correctly in the rust version of the
390 protover code. Previously, the protover rewrite in 24031 allowed
391 repeated votes from the same voter for the same protocol version
392 to be counted multiple times in protover_compute_vote(). Fixes bug
393 27649; bugfix on 0.3.3.5-rc.
394 - Reject protover names that contain invalid characters. Fixes bug
395 27687; bugfix on 0.3.3.1-alpha.
397 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
398 - protover_all_supported() would attempt to allocate up to 16GB on
399 some inputs, leading to a potential memory DoS. Fixes bug 27206;
400 bugfix on 0.3.3.5-rc.
402 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
403 - Fix an API mismatch in the rust implementation of
404 protover_compute_vote(). This bug could have caused crashes on any
405 directory authorities running Tor with Rust (which we do not yet
406 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
408 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
409 - Fix a potential null dereference in protover_all_supported(). Add
410 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
411 - Return a string that can be safely freed by C code, not one
412 created by the rust allocator, in protover_all_supported(). Fixes
413 bug 27740; bugfix on 0.3.3.1-alpha.
415 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
416 - If a unit test running in a subprocess exits abnormally or with a
417 nonzero status code, treat the test as having failed, even if the
418 test reported success. Without this fix, memory leaks don't cause
419 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
420 bugfix on 0.2.2.4-alpha.
422 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
423 - Make the hs_service tests use the same time source when creating
424 the introduction point and when testing it. Now tests work better
425 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
428 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
429 - Treat backtrace test failures as expected on BSD-derived systems
430 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
431 (FreeBSD failures have been treated as expected since 18204 in
432 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
435 Changes in version 0.3.5.3-alpha - 2018-10-17
436 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
437 versions. One important fix for relays addresses a problem with rate-
438 limiting code from back in 0.3.4.x: If the fix works out, we'll be
439 backporting it soon. This release is still an alpha, but we hope it's
440 getting closer and closer to stability.
442 o Major features (onion services):
443 - Version 3 onion services can now use the per-service
444 HiddenServiceExportCircuitID option to differentiate client
445 circuits. It communicates with the service by using the HAProxy
446 protocol to assign virtual IP addresses to inbound client
447 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
449 o Major bugfixes (compilation):
450 - Fix compilation on ARM (and other less-used CPUs) when compiling
451 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
453 o Major bugfixes (initialization, crash):
454 - Fix an assertion crash that would stop Tor from starting up if it
455 tried to activate a periodic event too early. Fixes bug 27861;
456 bugfix on 0.3.5.1-alpha.
458 o Major bugfixes (mainloop, bootstrap):
459 - Make sure Tor bootstraps and works properly if only the
460 ControlPort is set. Prior to this fix, Tor would only bootstrap
461 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
462 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
464 o Major bugfixes (relay):
465 - When our write bandwidth limit is exhausted, stop writing on the
466 connection. Previously, we had a typo in the code that would make
467 us stop reading instead, leading to relay connections being stuck
468 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
471 o Minor features (continuous integration):
472 - Use the Travis Homebrew addon to install packages on macOS during
473 Travis CI. The package list is the same, but the Homebrew addon
474 does not do a `brew update` by default. Implements ticket 27738.
475 - Report what program produced the mysterious core file that we
476 occasionally see on Travis CI during make distcheck. Closes
479 o Minor features (geoip):
480 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
481 Country database. Closes ticket 27991.
483 o Minor bugfixes (code safety):
484 - Rewrite our assertion macros so that they no longer suppress the
485 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
488 o Minor bugfixes (compilation):
489 - Compile the ed25519-donna code with a correct declaration of
490 crypto_strongest_rand(). Previously, we built it with one type,
491 but linked it against another in the unit tests, which caused
492 compilation failures with LTO enabled. This could have caused
493 other undefined behavior in the tests. Fixes bug 27728; bugfix
496 o Minor bugfixes (compilation, netbsd):
497 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
500 o Minor bugfixes (continuous integration, appveyor):
501 - Install only the necessary mingw packages during our appveyor
502 builds. This change makes the build a little faster, and prevents
503 a conflict with a preinstalled mingw openssl that appveyor now
504 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
506 o Minor bugfixes (directory permissions):
507 - When a user requests a group-readable DataDirectory, give it to
508 them. Previously, when the DataDirectory and the CacheDirectory
509 were the same, the default setting (0) for
510 CacheDirectoryGroupReadable would override the setting for
511 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
514 o Minor bugfixes (memory leaks):
515 - Fix a small memory leak when calling Tor with --dump-config. Fixes
516 bug 27893; bugfix on 0.3.2.1-alpha.
518 o Minor bugfixes (networking):
519 - In retry_listeners_ports(), make sure that we're removing a member
520 of old_conns smartlist at most once. Fixes bug 27808; bugfix
522 - Refrain from attempting socket rebinding when old and new
523 listeners are in different address families. Fixes bug 27928;
524 bugfix on 0.3.5.1-alpha.
526 o Minor bugfixes (onion service v3):
527 - Stop dumping a stack trace when trying to connect to an intro
528 point without having a descriptor for it. Fixes bug 27774; bugfix
530 - Don't warn so loudly when Tor is unable to decode an onion
531 descriptor. This can now happen as a normal use case if a client
532 gets a descriptor with client authorization but the client is not
533 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
534 - When selecting a v3 rendezvous point, don't only look at the
535 protover, but also check whether the curve25519 onion key is
536 present. This way we avoid picking a relay that supports the v3
537 rendezvous but for which we don't have the microdescriptor. Fixes
538 bug 27797; bugfix on 0.3.2.1-alpha.
540 o Minor bugfixes (protover):
541 - Reject protocol names containing bytes other than alphanumeric
542 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
545 o Minor bugfixes (testing):
546 - Make the hs_service tests use the same time source when creating
547 the introduction point and when testing it. Now tests work better
548 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
550 - In test_rebind.py, check if the Python version is in the supported
551 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
553 o Code simplification and refactoring:
554 - Divide more large Tor source files -- especially ones that span
555 multiple areas of functionality -- into smaller parts, including
556 onion.c and main.c. Closes ticket 26747.
557 - Divide the "routerparse.c" module into separate modules for each
558 group of parsed objects. Closes ticket 27924.
559 - Move protover_rust.c to the same place protover.c was moved to.
561 - Split directory.c into separate pieces for client, server, and
562 common functionality. Closes ticket 26744.
563 - Split the non-statistics-related parts from the rephist.c and
564 geoip.c modules. Closes ticket 27892.
565 - Split the router.c file into relay-only and shared components, to
566 help with future modularization. Closes ticket 27864.
569 - In the tor-resolve(1) manpage, fix the reference to socks-
570 extensions.txt by adding a web URL. Resolves ticket 27853.
571 - Mention that we require Python to be 2.7 or newer for some
572 integration tests that we ship with Tor. Resolves ticket 27677.
575 Changes in version 0.3.5.2-alpha - 2018-09-21
576 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
577 that made Tor think it had run out of sockets. Anybody running a relay
578 or an onion service on 0.3.5.1-alpha should upgrade.
580 o Major bugfixes (relay bandwidth statistics):
581 - When we close relayed circuits, report the data in the circuit
582 queues as being written in our relay bandwidth stats. This
583 mitigates guard discovery and other attacks that close circuits
584 for the explicit purpose of noticing this discrepancy in
585 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
587 o Major bugfixes (socket accounting):
588 - In our socket accounting code, count a socket as closed even when
589 it is closed indirectly by the TLS layer. Previously, we would
590 count these sockets as still in use, and incorrectly believe that
591 we had run out of sockets. Fixes bug 27795; bugfix
594 o Minor bugfixes (32-bit OSX and iOS, timing):
595 - Fix an integer overflow bug in our optimized 32-bit millisecond-
596 difference algorithm for 32-bit Apple platforms. Previously, it
597 would overflow when calculating the difference between two times
598 more than 47 days apart. Fixes part of bug 27139; bugfix
600 - Improve the precision of our 32-bit millisecond difference
601 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
602 bugfix on 0.3.4.1-alpha.
603 - Relax the tolerance on the mainloop/update_time_jumps test when
604 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
607 o Minor bugfixes (onion service v3):
608 - Close all SOCKS request (for the same .onion) if the newly fetched
609 descriptor is unusable. Before that, we would close only the first
610 one leaving the other hanging and let to time out by themselves.
611 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
613 o Minor bugfixes (memory leak):
614 - Fix an unlikely memory leak when trying to read a private key from
615 a ridiculously large file. Fixes bug 27764; bugfix on
616 0.3.5.1-alpha. This is CID 1439488.
618 o Minor bugfixes (NSS):
619 - Correctly detect failure to open a dummy TCP socket when stealing
620 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
623 o Minor bugfixes (rust):
624 - protover_all_supported() would attempt to allocate up to 16GB on
625 some inputs, leading to a potential memory DoS. Fixes bug 27206;
626 bugfix on 0.3.3.5-rc.
628 o Minor bugfixes (testing):
629 - Revise the "conditionvar_timeout" test so that it succeeds even on
630 heavily loaded systems where the test threads are not scheduled
631 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
633 o Code simplification and refactoring:
634 - Divide the routerlist.c and dirserv.c modules into smaller parts.
638 Changes in version 0.3.5.1-alpha - 2018-09-18
639 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
640 client authorization for modern (v3) onion services, improves
641 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
642 support for NSS in place of OpenSSL, and much more.
644 o Major features (onion services, UI change):
645 - For a newly created onion service, the default version is now 3.
646 Tor still supports existing version 2 services, but the operator
647 now needs to set "HiddenServiceVersion 2" in order to create a new
648 version 2 service. For existing services, Tor now learns the
649 version by reading the key file. Closes ticket 27215.
651 o Major features (relay, UI change):
652 - Relays no longer run as exits by default. If the "ExitRelay"
653 option is auto (or unset), and no exit policy is specified with
654 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
655 Previously in this case, we allowed exit traffic and logged a
656 warning message. Closes ticket 21530. Patch by Neel Chauhan.
657 - Tor now validates that the ContactInfo config option is valid UTF-
658 8 when parsing torrc. Closes ticket 27428.
660 o Major features (bootstrap):
661 - Don't report directory progress until after a connection to a
662 relay or bridge has succeeded. Previously, we'd report 80%
663 progress based on cached directory information when we couldn't
664 even connect to the network. Closes ticket 27169.
666 o Major features (new code layout):
667 - Nearly all of Tor's source code has been moved around into more
668 logical places. The "common" directory is now divided into a set
669 of libraries in "lib", and files in the "or" directory have been
670 split into "core" (logic absolutely needed for onion routing),
671 "feature" (independent modules in Tor), and "app" (to configure
672 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
673 more information. Closes ticket 26481.
675 This refactoring is not complete: although the libraries have been
676 refactored to be acyclic, the main body of Tor is still too
677 interconnected. We will attempt to improve this in the future.
679 o Major features (onion services v3):
680 - Implement onion service client authorization at the descriptor
681 level: only authorized clients can decrypt a service's descriptor
682 to find out how to contact it. A new torrc option was added to
683 control this client side: ClientOnionAuthDir <path>. On the
684 service side, if the "authorized_clients/" directory exists in the
685 onion service directory path, client configurations are read from
686 the files within. See the manpage for more details. Closes ticket
687 27547. Patch done by Suphanat Chunhapanya (haxxpop).
688 - Improve revision counter generation in next-gen onion services.
689 Onion services can now scale by hosting multiple instances on
690 different hosts without synchronization between them, which was
691 previously impossible because descriptors would get rejected by
692 HSDirs. Addresses ticket 25552.
694 o Major features (portability, cryptography, experimental, TLS):
695 - Tor now has the option to compile with the NSS library instead of
696 OpenSSL. This feature is experimental, and we expect that bugs may
697 remain. It is mainly intended for environments where Tor's
698 performance is not CPU-bound, and where NSS is already known to be
699 installed. To try it out, configure Tor with the --enable-nss
700 flag. Closes tickets 26631, 26815, and 26816.
702 If you are experimenting with this option and using an old cached
703 consensus, Tor may fail to start. To solve this, delete your
704 "cached-consensus" and "cached-microdesc-consensus" files,
705 (if present), and restart Tor.
707 o Major bugfixes (directory authority):
708 - Actually check that the address we get from DirAuthority
709 configuration line is valid IPv4. Explicitly disallow DirAuthority
710 address to be a DNS hostname. Fixes bug 26488; bugfix
713 o Major bugfixes (restart-in-process):
714 - Fix a use-after-free error that could be caused by passing Tor an
715 impossible set of options that would fail during options_act().
716 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
718 o Minor features (admin tools):
719 - Add a new --key-expiration option to print the expiration date of
720 the signing cert in an ed25519_signing_cert file. Resolves
723 o Minor features (build):
724 - If you pass the "--enable-pic" option to configure, Tor will try
725 to tell the compiler to build position-independent code suitable
726 to link into a dynamic library. (The default remains -fPIE, for
727 code suitable for a relocatable executable.) Closes ticket 23846.
729 o Minor features (code correctness, testing):
730 - Tor's build process now includes a "check-includes" make target to
731 verify that no module of Tor relies on any headers from a higher-
732 level module. We hope to use this feature over time to help
733 refactor our codebase. Closes ticket 26447.
735 o Minor features (code layout):
736 - We have a new "lowest-level" error-handling API for use by code
737 invoked from within the logging module. With this interface, the
738 logging code is no longer at risk of calling into itself if a
739 failure occurs while it is trying to log something. Closes
742 o Minor features (compilation):
743 - Tor's configure script now supports a --with-malloc= option to
744 select your malloc implementation. Supported options are
745 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
746 default). Addresses part of ticket 20424. Based on a patch from
749 o Minor features (config):
750 - The "auto" keyword in torrc is now case-insensitive. Closes
753 o Minor features (continuous integration):
754 - Don't do a distcheck with --disable-module-dirauth in Travis.
755 Implements ticket 27252.
756 - Install libcap-dev and libseccomp2-dev so these optional
757 dependencies get tested on Travis CI. Closes ticket 26560.
758 - Only run one online rust build in Travis, to reduce network
759 errors. Skip offline rust builds on Travis for Linux gcc, because
760 they're redundant. Implements ticket 27252.
761 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
762 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
763 Linux with default settings, because all the non-default builds
764 use gcc on Linux. Implements ticket 27252.
766 o Minor features (controller):
767 - Emit CIRC_BW events as soon as we detect that we processed an
768 invalid or otherwise dropped cell on a circuit. This allows
769 vanguards and other controllers to react more quickly to dropped
770 cells. Closes ticket 27678.
771 - For purposes of CIRC_BW-based dropped cell detection, track half-
772 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
773 bias check cells to arrive without counting it as dropped until
774 either the END arrives, or the windows are empty. Closes
776 - Implement a 'GETINFO md/all' controller command to enable getting
777 all known microdescriptors. Closes ticket 8323.
778 - The GETINFO command now support an "uptime" argument, to return
779 Tor's uptime in seconds. Closes ticket 25132.
781 o Minor features (denial-of-service avoidance):
782 - Make our OOM handler aware of the DNS cache so that it doesn't
783 fill up the memory. This check is important for our DoS mitigation
784 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
786 o Minor features (development):
787 - Tor's makefile now supports running the "clippy" Rust style tool
788 on our Rust code. Closes ticket 22156.
790 o Minor features (directory authority):
791 - There is no longer an artificial upper limit on the length of
792 bandwidth lines. Closes ticket 26223.
793 - When a bandwidth file is used to obtain the bandwidth measurements,
794 include this bandwidth file headers in the votes. Closes
796 - Improved support for networks with only a single authority or a
797 single fallback directory. Patch from Gabriel Somlo. Closes
800 o Minor features (embedding API):
801 - The Tor controller API now supports a function to launch Tor with
802 a preconstructed owning controller FD, so that embedding
803 applications don't need to manage controller ports and
804 authentication. Closes ticket 24204.
805 - The Tor controller API now has a function that returns the name
806 and version of the backend implementing the API. Closes
809 o Minor features (geoip):
810 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
811 Country database. Closes ticket 27631.
813 o Minor features (memory management):
814 - Get Libevent to use the same memory allocator as Tor, by calling
815 event_set_mem_functions() during initialization. Resolves
818 o Minor features (memory usage):
819 - When not using them, store legacy TAP public onion keys in DER-
820 encoded format, rather than as expanded public keys. This should
821 save several megabytes on typical clients. Closes ticket 27246.
823 o Minor features (OpenSSL):
824 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
825 than our own. Resolves ticket 19979.
827 o Minor features (Rust, code quality):
828 - Improve rust code quality in the rust protover implementation by
829 making it more idiomatic. Includes changing an internal API to
830 take &str instead of &String. Closes ticket 26492.
832 o Minor features (testing):
833 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
834 chutney. Implements ticket 27211.
836 o Minor features (tor-resolve):
837 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
838 Side-effect of the refactoring for ticket 26526.
840 o Minor features (UI):
841 - Log each included configuration file or directory as we read it,
842 to provide more visibility about where Tor is reading from. Patch
843 from Unto Sten; closes ticket 27186.
844 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
847 o Minor bugfixes (bootstrap):
848 - Try harder to get descriptors in non-exit test networks, by using
849 the mid weight for the third hop when there are no exits. Fixes
850 bug 27237; bugfix on 0.2.6.2-alpha.
852 o Minor bugfixes (C correctness):
853 - Avoid casting smartlist index to int implicitly, as it may trigger
854 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
855 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
856 - Use time_t for all values in
857 predicted_ports_prediction_time_remaining(). Rework the code that
858 computes difference between durations/timestamps. Fixes bug 27165;
859 bugfix on 0.3.1.1-alpha.
861 o Minor bugfixes (client, memory usage):
862 - When not running as a directory cache, there is no need to store
863 the text of the current consensus networkstatus in RAM.
864 Previously, however, clients would store it anyway, at a cost of
865 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
868 o Minor bugfixes (client, reachableaddresses):
869 - Instead of adding a "reject *:*" line to ReachableAddresses when
870 loading the configuration, add one to the policy after parsing it
871 in parse_reachable_addresses(). This prevents extra "reject *.*"
872 lines from accumulating on reloads. Fixes bug 20874; bugfix on
873 0.1.1.5-alpha. Patch by Neel Chauhan.
875 o Minor bugfixes (code quality):
876 - Rename sandbox_getaddrinfo() and other functions to no longer
877 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
878 bugfix on 0.2.7.1-alpha.
880 o Minor bugfixes (configuration, Onion Services):
881 - In rend_service_parse_port_config(), disallow any input to remain
882 after address-port pair was parsed. This will catch address and
883 port being whitespace-separated by mistake of the user. Fixes bug
884 27044; bugfix on 0.2.9.10.
886 o Minor bugfixes (continuous integration):
887 - Stop reinstalling identical packages in our Windows CI. Fixes bug
888 27464; bugfix on 0.3.4.1-alpha.
890 o Minor bugfixes (controller):
891 - Consider all routerinfo errors other than "not a server" to be
892 transient for the purpose of "GETINFO exit-policy/*" controller
893 request. Print stacktrace in the unlikely case of failing to
894 recompute routerinfo digest. Fixes bug 27034; bugfix
897 o Minor bugfixes (directory connection shutdown):
898 - Avoid a double-close when shutting down a stalled directory
899 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
901 o Minor bugfixes (HTTP tunnel):
902 - Fix a bug warning when closing an HTTP tunnel connection due to an
903 HTTP request we couldn't handle. Fixes bug 26470; bugfix
906 o Minor bugfixes (ipv6):
907 - In addrs_in_same_network_family(), we choose the subnet size based
908 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
909 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
910 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
912 o Minor bugfixes (logging):
913 - As a precaution, do an early return from log_addr_has_changed() if
914 Tor is running as client. Also, log a stack trace for debugging as
915 this function should only be called when Tor runs as server. Fixes
916 bug 26892; bugfix on 0.1.1.9-alpha.
917 - Refrain from mentioning bug 21018 in the logs, as it is already
918 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
920 o Minor bugfixes (logging, documentation):
921 - When SafeLogging is enabled, scrub IP address in
922 channel_tls_process_netinfo_cell(). Also, add a note to manpage
923 that scrubbing is not guaranteed on loglevels below Notice. Fixes
924 bug 26882; bugfix on 0.2.4.10-alpha.
926 o Minor bugfixes (netflow padding):
927 - Ensure circuitmux queues are empty before scheduling or sending
928 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
930 o Minor bugfixes (onion service v2):
931 - Log at level "info", not "warning", in the case that we do not
932 have a consensus when a .onion request comes in. This can happen
933 normally while bootstrapping. Fixes bug 27040; bugfix
936 o Minor bugfixes (onion service v3):
937 - When the onion service directory can't be created or has the wrong
938 permissions, do not log a stack trace. Fixes bug 27335; bugfix
941 o Minor bugfixes (OS compatibility):
942 - Properly handle configuration changes that move a listener to/from
943 wildcard IP address. If the first attempt to bind a socket fails,
944 close the old listener and try binding the socket again. Fixes bug
945 17873; bugfix on 0.0.8pre-1.
947 o Minor bugfixes (performance)::
948 - Rework node_is_a_configured_bridge() to no longer call
949 node_get_all_orports(), which was performing too many memory
950 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
952 o Minor bugfixes (relay statistics):
953 - Update relay descriptor on bandwidth changes only when the uptime
954 is smaller than 24h, in order to reduce the efficiency of guard
955 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
957 o Minor bugfixes (relays):
958 - Consider the fact that we'll be making direct connections to our
959 entry and guard nodes when computing the fraction of nodes that
960 have their descriptors. Also, if we are using bridges and there is
961 at least one bridge with a full descriptor, treat the fraction of
962 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
963 Patch by Neel Chauhan.
964 - Update the message logged on relays when DirCache is disabled.
965 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
966 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
968 o Minor bugfixes (rust, protover):
969 - Compute protover votes correctly in the rust version of the
970 protover code. Previously, the protover rewrite in 24031 allowed
971 repeated votes from the same voter for the same protocol version
972 to be counted multiple times in protover_compute_vote(). Fixes bug
973 27649; bugfix on 0.3.3.5-rc.
974 - Reject protover names that contain invalid characters. Fixes bug
975 27687; bugfix on 0.3.3.1-alpha.
977 o Minor bugfixes (testing):
978 - Fix two unit tests to work when HOME environment variable is not
979 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
980 - If a unit test running in a subprocess exits abnormally or with a
981 nonzero status code, treat the test as having failed, even if the
982 test reported success. Without this fix, memory leaks don't cause
983 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
984 bugfix on 0.2.2.4-alpha.
985 - When logging a version mismatch in our openssl_version tests,
986 report the actual offending version strings. Fixes bug 26152;
987 bugfix on 0.2.9.1-alpha.
988 - Fix forking tests on Windows when there is a space somewhere in
989 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
991 o Code simplification and refactoring:
992 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
993 longer needed. Closes ticket 26502.
994 - Include paths to header files within Tor are now qualified by
995 directory within the top-level src directory.
996 - Many structures have been removed from the centralized "or.h"
997 header, and moved into their own headers. This will allow us to
998 reduce the number of places in the code that rely on each
999 structure's contents and layout. Closes ticket 26383.
1000 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
1001 - Remove GetAdaptersAddresses_fn_t. The code that used it was
1002 removed as part of the 26481 refactor. Closes ticket 27467.
1003 - Rework Tor SOCKS server code to use Trunnel and benefit from
1004 autogenerated functions for parsing and generating SOCKS wire
1005 format. New implementation is cleaner, more maintainable and
1006 should be less prone to heartbleed-style vulnerabilities.
1007 Implements a significant fraction of ticket 3569.
1008 - Split sampled_guards_update_from_consensus() and
1009 select_entry_guard_for_circuit() into subfunctions. In
1010 entry_guards_update_primary() unite three smartlist enumerations
1011 into one and move smartlist comparison code out of the function.
1012 Closes ticket 21349.
1013 - Tor now assumes that you have standards-conformant stdint.h and
1014 inttypes.h headers when compiling. Closes ticket 26626.
1015 - Unify our bloom filter logic. Previously we had two copies of this
1016 code: one for routerlist filtering, and one for address set
1017 calculations. Closes ticket 26510.
1018 - Use the simpler strcmpstart() helper in
1019 rend_parse_v2_service_descriptor instead of strncmp(). Closes
1021 - Utility functions that can perform a DNS lookup are now wholly
1022 separated from those that can't, in separate headers and C
1023 modules. Closes ticket 26526.
1026 - Copy paragraph and URL to Tor's code of conduct document from
1027 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
1028 - Remove old instructions from INSTALL document. Closes ticket 26588.
1029 - Warn users that they should not include MyFamily line(s) in their
1030 torrc when running Tor bridge. Closes ticket 26908.
1033 - Tor no longer supports building with the dmalloc library. For
1034 debugging memory issues, we suggest using gperftools or msan
1035 instead. Closes ticket 26426.
1036 - Tor no longer attempts to run on Windows environments without the
1037 GetAdaptersAddresses() function. This function has existed since
1038 Windows XP, which is itself already older than we support.
1039 - Remove Tor2web functionality for version 2 onion services. The
1040 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
1041 (This feature was never shipped in vanilla Tor and it was only
1042 possible to use this feature by building the support at compile
1043 time. Tor2webMode is not implemented for version 3 onion services.)
1044 Closes ticket 26367.
1047 Changes in version 0.2.9.17 - 2018-09-10
1048 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
1050 o Minor features (compatibility, backport from 0.3.4.8):
1051 - Tell OpenSSL to maintain backward compatibility with previous
1052 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1053 ciphers are disabled by default. Closes ticket 27344.
1055 o Minor features (continuous integration, backport from 0.3.4.7-rc):
1056 - Enable macOS builds in our Travis CI configuration. Closes
1058 - Install libcap-dev and libseccomp2-dev so these optional
1059 dependencies get tested on Travis CI. Closes ticket 26560.
1060 - Run asciidoc during Travis CI. Implements ticket 27087.
1061 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1063 o Minor features (geoip):
1064 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1065 Country database. Closes ticket 27089.
1067 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
1068 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1069 tell the compiler not to include the system malloc implementation.
1070 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1072 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
1073 - Silence a spurious compiler warning on the GetAdaptersAddresses
1074 function pointer cast. This issue is already fixed by 26481 in
1075 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
1076 bugfix on 0.2.3.11-alpha.
1077 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
1078 supported, and always fails. Some compilers warn about the
1079 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
1082 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
1083 - Don't link or search for pthreads when building for Windows, even
1084 if we are using build environment (like mingw) that provides a
1085 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
1087 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
1088 - Skip a pair of unreliable key generation tests on Windows, until
1089 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1090 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1092 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
1093 - Pass the module flags to distcheck configure, and log the flags
1094 before running configure. (Backported to 0.2.9 and later as a
1095 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
1097 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
1098 - When a Travis build fails, and showing a log fails, keep trying to
1099 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
1100 - When we use echo in Travis, don't pass a --flag as the first
1101 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
1103 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
1104 - When voting for recommended versions, make sure that all of the
1105 versions are well-formed and parsable. Fixes bug 26485; bugfix
1108 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
1109 - Fix a bug in out sandboxing rules for the openat() syscall.
1110 Previously, no openat() call would be permitted, which would break
1111 filesystem operations on recent glibc versions. Fixes bug 25440;
1112 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
1114 o Minor bugfixes (onion services, backport from 0.3.4.8):
1115 - Silence a spurious compiler warning in
1116 rend_client_send_introduction(). Fixes bug 27463; bugfix
1119 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
1120 - Log a protocol warning when single onion services or Tor2web clients
1121 fail to authenticate direct connections to relays.
1122 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
1124 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
1125 - Disable core dumps in test_bt.sh, to avoid failures in "make
1126 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
1128 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
1129 - Before running make test-network-all, delete old logs and test
1130 result files, to avoid spurious failures. Fixes bug 27295; bugfix
1133 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
1134 - Our "tortls/cert_matches_key" unit test no longer relies on
1135 OpenSSL internals. Previously, it relied on unsupported OpenSSL
1136 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
1137 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
1139 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
1140 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
1141 27185; bugfix on 0.2.2.2-alpha.
1144 Changes in version 0.3.2.12 - 2018-09-10
1145 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
1147 o Minor features (compatibility, backport from 0.3.4.8):
1148 - Tell OpenSSL to maintain backward compatibility with previous
1149 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1150 ciphers are disabled by default. Closes ticket 27344.
1152 o Minor features (continuous integration, backport from 0.3.4.7-rc):
1153 - Enable macOS builds in our Travis CI configuration. Closes
1155 - Install libcap-dev and libseccomp2-dev so these optional
1156 dependencies get tested on Travis CI. Closes ticket 26560.
1157 - Run asciidoc during Travis CI. Implements ticket 27087.
1158 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1160 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
1161 - Use cargo cache in our Travis CI configuration. Closes
1164 o Minor features (controller, backport from 0.3.4.6-rc):
1165 - The control port now exposes the list of HTTPTunnelPorts and
1166 ExtOrPorts via GETINFO net/listeners/httptunnel and
1167 net/listeners/extor respectively. Closes ticket 26647.
1169 o Minor features (directory authorities, backport from 0.3.4.7-rc):
1170 - Authorities no longer vote to make the subprotocol version
1171 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
1172 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
1174 o Minor features (geoip):
1175 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1176 Country database. Closes ticket 27089.
1178 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
1179 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1180 tell the compiler not to include the system malloc implementation.
1181 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1182 - Don't try to use a pragma to temporarily disable the
1183 -Wunused-const-variable warning if the compiler doesn't support
1184 it. Fixes bug 26785; bugfix on 0.3.2.11.
1186 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
1187 - Silence a spurious compiler warning on the GetAdaptersAddresses
1188 function pointer cast. This issue is already fixed by 26481 in
1189 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
1190 bugfix on 0.2.3.11-alpha.
1191 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
1192 supported, and always fails. Some compilers warn about the
1193 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
1196 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
1197 - Don't link or search for pthreads when building for Windows, even
1198 if we are using build environment (like mingw) that provides a
1199 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
1201 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
1202 - Skip a pair of unreliable key generation tests on Windows, until
1203 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1204 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1206 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
1207 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
1208 - Pass the module flags to distcheck configure, and log the flags
1209 before running configure. (Backported to 0.2.9 and later as a
1210 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
1212 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
1213 - When a Travis build fails, and showing a log fails, keep trying to
1214 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
1215 - When we use echo in Travis, don't pass a --flag as the first
1216 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
1218 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
1219 - When voting for recommended versions, make sure that all of the
1220 versions are well-formed and parsable. Fixes bug 26485; bugfix
1223 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
1224 - Fix a bug in out sandboxing rules for the openat() syscall.
1225 Previously, no openat() call would be permitted, which would break
1226 filesystem operations on recent glibc versions. Fixes bug 25440;
1227 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
1229 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
1230 - Improve the log message when connection initiators fail to
1231 authenticate direct connections to relays. Fixes bug 26927; bugfix
1234 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
1235 - Fix bug that causes services to not ever rotate their descriptors
1236 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
1239 o Minor bugfixes (onion services, backport from 0.3.4.8):
1240 - Silence a spurious compiler warning in
1241 rend_client_send_introduction(). Fixes bug 27463; bugfix
1244 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
1245 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
1247 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
1248 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
1249 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
1250 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
1252 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
1253 - Log a protocol warning when single onion services or Tor2web clients
1254 fail to authenticate direct connections to relays.
1255 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
1257 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
1258 - Disable core dumps in test_bt.sh, to avoid failures in "make
1259 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
1261 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
1262 - When running make test-network-all, use the mixed+hs-v2 network.
1263 (A previous fix to chutney removed v3 onion services from the
1264 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
1265 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
1266 - Before running make test-network-all, delete old logs and test
1267 result files, to avoid spurious failures. Fixes bug 27295; bugfix
1270 o Minor bugfixes (testing, openssl compatibility):
1271 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
1272 internals. Previously, it relied on unsupported OpenSSL behavior in
1273 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
1274 bugfix on 0.2.5.1-alpha.
1276 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
1277 - Our "tortls/cert_matches_key" unit test no longer relies on
1278 OpenSSL internals. Previously, it relied on unsupported OpenSSL
1279 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
1280 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
1282 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
1283 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
1284 27185; bugfix on 0.2.2.2-alpha.
1287 Changes in version 0.3.3.10 - 2018-09-10
1288 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
1290 o Minor features (bug workaround, backport from 0.3.4.7-rc):
1291 - Compile correctly on systems that provide the C11 stdatomic.h
1292 header, but where C11 atomic functions don't actually compile.
1293 Closes ticket 26779; workaround for Debian issue 903709.
1295 o Minor features (compatibility, backport from 0.3.4.8):
1296 - Tell OpenSSL to maintain backward compatibility with previous
1297 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1298 ciphers are disabled by default. Closes ticket 27344.
1300 o Minor features (continuous integration, backport from 0.3.4.7-rc):
1301 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
1302 - Enable macOS builds in our Travis CI configuration. Closes
1304 - Install libcap-dev and libseccomp2-dev so these optional
1305 dependencies get tested on Travis CI. Closes ticket 26560.
1306 - Run asciidoc during Travis CI. Implements ticket 27087.
1307 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1309 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
1310 - Use cargo cache in our Travis CI configuration. Closes
1313 o Minor features (controller, backport from 0.3.4.6-rc):
1314 - The control port now exposes the list of HTTPTunnelPorts and
1315 ExtOrPorts via GETINFO net/listeners/httptunnel and
1316 net/listeners/extor respectively. Closes ticket 26647.
1318 o Minor features (directory authorities, backport from 0.3.4.7-rc):
1319 - Authorities no longer vote to make the subprotocol version
1320 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
1321 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
1323 o Minor features (geoip):
1324 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1325 Country database. Closes ticket 27089.
1327 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
1328 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1329 tell the compiler not to include the system malloc implementation.
1330 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1331 - Don't try to use a pragma to temporarily disable the
1332 -Wunused-const-variable warning if the compiler doesn't support
1333 it. Fixes bug 26785; bugfix on 0.3.2.11.
1335 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
1336 - Silence a spurious compiler warning on the GetAdaptersAddresses
1337 function pointer cast. This issue is already fixed by 26481 in
1338 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
1339 bugfix on 0.2.3.11-alpha.
1340 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
1341 supported, and always fails. Some compilers warn about the
1342 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
1345 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
1346 - Don't link or search for pthreads when building for Windows, even
1347 if we are using build environment (like mingw) that provides a
1348 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
1350 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
1351 - Skip a pair of unreliable key generation tests on Windows, until
1352 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1353 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1355 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
1356 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
1357 - Pass the module flags to distcheck configure, and log the flags
1358 before running configure. (Backported to 0.2.9 and later as a
1359 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
1361 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
1362 - When a Travis build fails, and showing a log fails, keep trying to
1363 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
1364 - When we use echo in Travis, don't pass a --flag as the first
1365 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
1367 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
1368 - When voting for recommended versions, make sure that all of the
1369 versions are well-formed and parsable. Fixes bug 26485; bugfix
1372 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
1373 - Always call tor_free_all() when leaving tor_run_main(). When we
1374 did not, restarting tor in-process would cause an assertion
1375 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
1377 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
1378 - Fix a bug in our sandboxing rules for the openat() syscall.
1379 Previously, no openat() call would be permitted, which would break
1380 filesystem operations on recent glibc versions. Fixes bug 25440;
1381 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
1383 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
1384 - Improve the log message when connection initiators fail to
1385 authenticate direct connections to relays. Fixes bug 26927; bugfix
1388 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
1389 - Fix bug that causes services to not ever rotate their descriptors
1390 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
1393 o Minor bugfixes (onion services, backport from 0.3.4.8):
1394 - Silence a spurious compiler warning in
1395 rend_client_send_introduction(). Fixes bug 27463; bugfix
1398 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
1399 - Work around two different bugs in the OS X 10.10 and later SDKs
1400 that would prevent us from successfully targeting earlier versions
1401 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
1403 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
1404 - Fix compilation of the unit tests on GNU/Hurd, which does not
1405 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
1408 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
1409 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
1411 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
1412 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
1413 - Protover parsing was accepting the presence of whitespace in
1414 version strings, which the C implementation would choke on, e.g.
1415 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
1416 - Protover parsing was ignoring a 2nd hyphen and everything after
1417 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
1419 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
1420 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
1421 - cd to ${abs_top_builddir}/src/rust before running cargo in
1422 src/test/test_rust.sh. This makes the working directory consistent
1423 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
1425 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
1426 - Log a protocol warning when single onion services or Tor2web clients
1427 fail to authenticate direct connections to relays.
1428 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
1430 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
1431 - Disable core dumps in test_bt.sh, to avoid failures in "make
1432 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
1434 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
1435 - When running make test-network-all, use the mixed+hs-v2 network.
1436 (A previous fix to chutney removed v3 onion services from the
1437 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
1438 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
1439 - Before running make test-network-all, delete old logs and test
1440 result files, to avoid spurious failures. Fixes bug 27295; bugfix
1443 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
1444 - Our "tortls/cert_matches_key" unit test no longer relies on
1445 OpenSSL internals. Previously, it relied on unsupported OpenSSL
1446 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
1447 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
1449 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
1450 - Stop sending ed25519 link specifiers in v3 onion service introduce
1451 cells and descriptors, when the rendezvous or introduction point
1452 doesn't support ed25519 link authentication. Fixes bug 26627;
1453 bugfix on 0.3.2.4-alpha.
1455 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
1456 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
1457 27185; bugfix on 0.2.2.2-alpha.
1460 Changes in version 0.3.4.8 - 2018-09-10
1461 Tor 0.3.4.8 is the first stable release in its series; it includes
1462 compilation and portability fixes.
1464 The Tor 0.3.4 series includes improvements for running Tor in
1465 low-power and embedded environments, which should help performance in
1466 general. We've begun work on better modularity, and included preliminary
1467 changes on the directory authority side to accommodate a new bandwidth
1468 measurement system. We've also integrated more continuous-integration
1469 systems into our development process, and made corresponding changes to
1470 Tor's testing infrastructure. Finally, we've continued to refine
1471 our anti-denial-of-service code.
1473 Below are the changes since 0.3.4.7-rc. For a complete list of changes
1474 since 0.3.3.9, see the ReleaseNotes file.
1476 o Minor features (compatibility):
1477 - Tell OpenSSL to maintain backward compatibility with previous
1478 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1479 ciphers are disabled by default. Closes ticket 27344.
1481 o Minor features (continuous integration):
1482 - Log the compiler path and version during Appveyor builds.
1483 Implements ticket 27449.
1484 - Show config.log and test-suite.log after failed Appveyor builds.
1485 Also upload the zipped full logs as a build artifact. Implements
1488 o Minor bugfixes (compilation):
1489 - Silence a spurious compiler warning on the GetAdaptersAddresses
1490 function pointer cast. This issue is already fixed by 26481 in
1491 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
1492 bugfix on 0.2.3.11-alpha.
1493 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
1494 supported, and always fails. Some compilers warn about the
1495 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
1498 o Minor bugfixes (continuous integration):
1499 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
1500 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
1501 Executables compiled for 64-bit Windows with this version of gcc
1502 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
1503 27460; bugfix on 0.3.4.1-alpha.
1504 - When a Travis build fails, and showing a log fails, keep trying to
1505 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
1506 - When we use echo in Travis, don't pass a --flag as the first
1507 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
1509 o Minor bugfixes (onion services):
1510 - Silence a spurious compiler warning in
1511 rend_client_send_introduction(). Fixes bug 27463; bugfix
1514 o Minor bugfixes (testing, chutney):
1515 - When running make test-network-all, use the mixed+hs-v2 network.
1516 (A previous fix to chutney removed v3 onion services from the
1517 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
1518 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
1519 - Before running make test-network-all, delete old logs and test
1520 result files, to avoid spurious failures. Fixes bug 27295; bugfix
1523 Changes in version 0.3.4.7-rc - 2018-08-24
1524 Tor 0.3.4.7-rc fixes several small compilation, portability, and
1525 correctness issues in previous versions of Tor. This version is a
1526 release candidate: if no serious bugs are found, we expect that the
1527 stable 0.3.4 release will be (almost) the same as this release.
1529 o Minor features (bug workaround):
1530 - Compile correctly on systems that provide the C11 stdatomic.h
1531 header, but where C11 atomic functions don't actually compile.
1532 Closes ticket 26779; workaround for Debian issue 903709.
1534 o Minor features (continuous integration):
1535 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
1536 - Enable macOS builds in our Travis CI configuration. Closes
1538 - Install libcap-dev and libseccomp2-dev so these optional
1539 dependencies get tested on Travis CI. Closes ticket 26560.
1540 - Only post Appveyor IRC notifications when the build fails.
1541 Implements ticket 27275.
1542 - Run asciidoc during Travis CI. Implements ticket 27087.
1543 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1545 o Minor features (continuous integration, rust):
1546 - Use cargo cache in our Travis CI configuration. Closes
1549 o Minor features (directory authorities):
1550 - Authorities no longer vote to make the subprotocol version
1551 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
1552 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
1554 o Minor features (geoip):
1555 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1556 Country database. Closes ticket 27089.
1558 o Minor bugfixes (compilation, windows):
1559 - Don't link or search for pthreads when building for Windows, even
1560 if we are using build environment (like mingw) that provides a
1561 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
1563 o Minor bugfixes (continuous integration):
1564 - Improve Appveyor CI IRC logging. Generate correct branches and
1565 URLs for pull requests and tags. Use unambiguous short commits.
1566 Fixes bug 26979; bugfix on master.
1567 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
1568 - Pass the module flags to distcheck configure, and log the flags
1569 before running configure. (Backported to 0.2.9 and later as a
1570 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
1572 o Minor bugfixes (in-process restart):
1573 - Always call tor_free_all() when leaving tor_run_main(). When we
1574 did not, restarting tor in-process would cause an assertion
1575 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
1577 o Minor bugfixes (linux seccomp2 sandbox):
1578 - Fix a bug in out sandboxing rules for the openat() syscall.
1579 Previously, no openat() call would be permitted, which would break
1580 filesystem operations on recent glibc versions. Fixes bug 25440;
1581 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
1583 o Minor bugfixes (onion services):
1584 - Fix bug that causes services to not ever rotate their descriptors
1585 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
1588 o Minor bugfixes (portability):
1589 - Fix compilation of the unit tests on GNU/Hurd, which does not
1590 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
1593 o Minor bugfixes (rust):
1594 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
1596 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
1597 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
1598 - Protover parsing was accepting the presence of whitespace in
1599 version strings, which the C implementation would choke on, e.g.
1600 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
1601 - Protover parsing was ignoring a 2nd hyphen and everything after
1602 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
1604 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
1605 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
1606 - cd to ${abs_top_builddir}/src/rust before running cargo in
1607 src/test/test_rust.sh. This makes the working directory consistent
1608 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
1610 o Minor bugfixes (testing, bootstrap):
1611 - When calculating bootstrap progress, check exit policies and the
1612 exit flag. Previously, Tor would only check the exit flag, which
1613 caused race conditions in small and fast networks like chutney.
1614 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
1616 o Minor bugfixes (testing, openssl compatibility):
1617 - Our "tortls/cert_matches_key" unit test no longer relies on
1618 OpenSSL internals. Previously, it relied on unsupported OpenSSL
1619 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
1620 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
1622 o Minor bugfixes (Windows, compilation):
1623 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
1624 27185; bugfix on 0.2.2.2-alpha.
1627 Changes in version 0.3.4.6-rc - 2018-08-06
1628 Tor 0.3.4.6-rc fixes several small compilation, portability, and
1629 correctness issues in previous versions of Tor. This version is a
1630 release candidate: if no serious bugs are found, we expect that the
1631 stable 0.3.4 release will be (almost) the same as this release.
1633 o Major bugfixes (event scheduler):
1634 - When we enable a periodic event, schedule it in the event loop
1635 rather than running it immediately. Previously, we would re-run
1636 periodic events immediately in the middle of (for example)
1637 changing our options, with unpredictable effects. Fixes bug 27003;
1638 bugfix on 0.3.4.1-alpha.
1640 o Minor features (compilation):
1641 - When building Tor, prefer to use Python 3 over Python 2, and more
1642 recent (contemplated) versions over older ones. Closes
1644 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1645 tell the compiler not to include the system malloc implementation.
1646 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1647 - Don't try to use a pragma to temporarily disable the
1648 -Wunused-const-variable warning if the compiler doesn't support
1649 it. Fixes bug 26785; bugfix on 0.3.2.11.
1651 o Minor bugfixes (continuous integration):
1652 - Skip a pair of unreliable key generation tests on Windows, until
1653 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1654 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1656 o Minor features (controller):
1657 - The control port now exposes the list of HTTPTunnelPorts and
1658 ExtOrPorts via GETINFO net/listeners/httptunnel and
1659 net/listeners/extor respectively. Closes ticket 26647.
1661 o Minor bugfixes (directory authority):
1662 - When voting for recommended versions, make sure that all of the
1663 versions are well-formed and parsable. Fixes bug 26485; bugfix
1666 o Minor features (geoip):
1667 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1668 Country database. Closes ticket 26674.
1670 o Minor features (Rust, portability):
1671 - Rust cross-compilation is now supported. Closes ticket 25895.
1673 o Minor bugfixes (compilation):
1674 - Update build system so that tor builds again with --disable-unittests
1675 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
1676 - Fix a compilation warning on some versions of GCC when building
1677 code that calls routerinfo_get_my_routerinfo() twice, assuming
1678 that the second call will succeed if the first one did. Fixes bug
1679 26269; bugfix on 0.2.8.2-alpha.
1681 o Minor bugfixes (controller):
1682 - Report the port correctly when a port is configured to bind to
1683 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
1684 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
1685 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
1686 on 0.3.3.1-alpha. Patch by "akwizgran".
1688 o Minor bugfixes (correctness, flow control):
1689 - Upon receiving a stream-level SENDME cell, verify that our window
1690 has not grown too large. Fixes bug 26214; bugfix on svn
1693 o Minor bugfixes (memory, correctness):
1694 - Fix a number of small memory leaks identified by coverity. Fixes
1695 bug 26467; bugfix on numerous Tor versions.
1697 o Minor bugfixes (logging):
1698 - Improve the log message when connection initiators fail to
1699 authenticate direct connections to relays. Fixes bug 26927; bugfix
1702 o Minor bugfixes (portability):
1703 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
1704 26994; bugfix on 0.3.4.1-alpha.
1705 - Work around two different bugs in the OS X 10.10 and later SDKs
1706 that would prevent us from successfully targeting earlier versions
1707 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
1709 o Minor bugfixes (single onion services, Tor2web):
1710 - Log a protocol warning when single onion services or Tor2web
1711 clients fail to authenticate direct connections to relays. Fixes
1712 bug 26924; bugfix on 0.2.9.1-alpha.
1714 o Minor bugfixes (testing):
1715 - Disable core dumps in test_bt.sh, to avoid failures in "make
1716 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
1718 o Minor bugfixes (testing, compatibility):
1719 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
1720 only to pass strings (rather than "bytes" objects) to the Python
1721 subprocess module. Python 3 on Windows seems to require this.
1722 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
1723 0.3.1.1-alpha (for hs_ntor_ref.py).
1725 o Minor bugfixes (v3 onion services):
1726 - Stop sending ed25519 link specifiers in v3 onion service introduce
1727 cells and descriptors, when the rendezvous or introduction point
1728 doesn't support ed25519 link authentication. Fixes bug 26627;
1729 bugfix on 0.3.2.4-alpha.
1732 Changes in version 0.3.4.5-rc - 2018-07-13
1733 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
1734 bridge relays should upgrade.
1736 o Directory authority changes:
1737 - The "Bifroest" bridge authority has been retired; the new bridge
1738 authority is "Serge", and it is operated by George from the
1739 TorBSD project. Closes ticket 26771.
1742 Changes in version 0.3.3.9 - 2018-07-13
1743 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
1744 bridge relays should upgrade.
1746 o Directory authority changes:
1747 - The "Bifroest" bridge authority has been retired; the new bridge
1748 authority is "Serge", and it is operated by George from the
1749 TorBSD project. Closes ticket 26771.
1752 Changes in version 0.3.2.11 - 2018-07-13
1753 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
1754 bridge relays should upgrade. We also take this opportunity to backport
1757 o Directory authority changes:
1758 - The "Bifroest" bridge authority has been retired; the new bridge
1759 authority is "Serge", and it is operated by George from the
1760 TorBSD project. Closes ticket 26771.
1762 o Directory authority changes (backport from 0.3.3.7):
1763 - Add an IPv6 address for the "dannenberg" directory authority.
1764 Closes ticket 26343.
1766 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
1767 - When directory authorities read a zero-byte bandwidth file, they
1768 would previously log a warning with the contents of an
1769 uninitialised buffer. They now log a warning about the empty file
1770 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1772 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
1773 - Correctly detect when onion services get disabled after HUP. Fixes
1774 bug 25761; bugfix on 0.3.2.1.
1776 o Minor features (sandbox, backport from 0.3.3.4-alpha):
1777 - Explicitly permit the poll() system call when the Linux
1778 seccomp2-based sandbox is enabled: apparently, some versions of
1779 libc use poll() when calling getpwnam(). Closes ticket 25313.
1781 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
1782 - Update the Travis CI configuration to use the stable Rust channel,
1783 now that we have decided to require that. Closes ticket 25714.
1785 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
1786 - Our .travis.yml configuration now includes support for testing the
1787 results of "make distcheck". (It's not uncommon for "make check"
1788 to pass but "make distcheck" to fail.) Closes ticket 25814.
1789 - Our Travis CI configuration now integrates with the Coveralls
1790 coverage analysis tool. Closes ticket 25818.
1792 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
1793 - Add several checks to detect whether Tor relays are uploading
1794 their descriptors without specifying why they regenerated them.
1795 Diagnostic for ticket 25686.
1797 o Minor features (compilation, backport from 0.3.4.4-rc):
1798 - When building Tor, prefer to use Python 3 over Python 2, and more
1799 recent (contemplated) versions over older ones. Closes
1802 o Minor features (geoip):
1803 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1804 Country database. Closes ticket 26674.
1806 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
1807 - Upon receiving a malformed connected cell, stop processing the
1808 cell immediately. Previously we would mark the connection for
1809 close, but continue processing the cell as if the connection were
1810 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
1812 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
1813 - Allow the nanosleep() system call, which glibc uses to implement
1814 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
1816 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
1817 - When running the hs_ntor_ref.py test, make sure only to pass
1818 strings (rather than "bytes" objects) to the Python subprocess
1819 module. Python 3 on Windows seems to require this. Fixes bug
1820 26535; bugfix on 0.3.1.1-alpha.
1821 - When running the ntor_ref.py test, make sure only to pass strings
1822 (rather than "bytes" objects) to the Python subprocess module.
1823 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1826 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
1827 - Work around a change in OpenSSL 1.1.1 where return values that
1828 would previously indicate "no password" now indicate an empty
1829 password. Without this workaround, Tor instances running with
1830 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1831 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1833 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
1834 - Document that the PerConnBW{Rate,Burst} options will fall back to
1835 their corresponding consensus parameters only if those parameters
1836 are set. Previously we had claimed that these values would always
1837 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
1839 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
1840 - Fix a compilation warning on some versions of GCC when building
1841 code that calls routerinfo_get_my_routerinfo() twice, assuming
1842 that the second call will succeed if the first one did. Fixes bug
1843 26269; bugfix on 0.2.8.2-alpha.
1845 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
1846 - Don't consider Tor running as a client if the ControlPort is open,
1847 but no actual client ports are open. Fixes bug 26062; bugfix
1850 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
1851 - Prevent a possible out-of-bounds smartlist read in
1852 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1854 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
1855 - Fix a very unlikely (impossible, we believe) null pointer
1856 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
1857 Coverity; this is CID 1430932.
1859 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
1860 - Fix a memory leak when a v3 onion service is configured and gets a
1861 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
1862 - When parsing the descriptor signature, look for the token plus an
1863 extra white-space at the end. This is more correct but also will
1864 allow us to support new fields that might start with "signature".
1865 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
1867 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
1868 - Relays now correctly block attempts to re-extend to the previous
1869 relay by Ed25519 identity. Previously they would warn in this
1870 case, but not actually reject the attempt. Fixes bug 26158; bugfix
1873 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
1874 - Avoid a crash when running with DirPort set but ORPort turned off.
1875 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
1877 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
1878 - Silence unused-const-variable warnings in zstd.h with some GCC
1879 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
1881 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
1882 - Avoid intermittent test failures due to a test that had relied on
1883 onion service introduction point creation finishing within 5
1884 seconds of real clock time. Fixes bug 25450; bugfix
1887 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
1888 - Fix a C99 compliance issue in our configuration script that caused
1889 compilation issues when compiling Tor with certain versions of
1890 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
1892 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
1893 - Fix a number of small memory leaks identified by coverity. Fixes
1894 bug 26467; bugfix on numerous Tor versions.
1896 o Code simplification and refactoring (backport from 0.3.3.5-rc):
1897 - Move the list of default directory authorities to its own file.
1898 Closes ticket 24854. Patch by "beastr0".
1901 Changes in version 0.2.9.16 - 2018-07-13
1902 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
1903 bridge relays should upgrade. We also take this opportunity to backport
1906 o Directory authority changes:
1907 - The "Bifroest" bridge authority has been retired; the new bridge
1908 authority is "Serge", and it is operated by George from the
1909 TorBSD project. Closes ticket 26771.
1911 o Directory authority changes (backport from 0.3.3.7):
1912 - Add an IPv6 address for the "dannenberg" directory authority.
1913 Closes ticket 26343.
1915 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
1916 - When directory authorities read a zero-byte bandwidth file, they
1917 would previously log a warning with the contents of an
1918 uninitialised buffer. They now log a warning about the empty file
1919 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1921 o Minor features (sandbox, backport from 0.3.3.4-alpha):
1922 - Explicitly permit the poll() system call when the Linux
1923 seccomp2-based sandbox is enabled: apparently, some versions of
1924 libc use poll() when calling getpwnam(). Closes ticket 25313.
1926 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
1927 - Our .travis.yml configuration now includes support for testing the
1928 results of "make distcheck". (It's not uncommon for "make check"
1929 to pass but "make distcheck" to fail.) Closes ticket 25814.
1930 - Our Travis CI configuration now integrates with the Coveralls
1931 coverage analysis tool. Closes ticket 25818.
1933 o Minor features (compilation, backport from 0.3.4.4-rc):
1934 - When building Tor, prefer to use Python 3 over Python 2, and more
1935 recent (contemplated) versions over older ones. Closes
1938 o Minor features (geoip):
1939 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1940 Country database. Closes ticket 26674.
1942 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
1943 - Upon receiving a malformed connected cell, stop processing the
1944 cell immediately. Previously we would mark the connection for
1945 close, but continue processing the cell as if the connection were
1946 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
1948 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
1949 - Allow the nanosleep() system call, which glibc uses to implement
1950 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
1952 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
1953 - When running the ntor_ref.py test, make sure only to pass strings
1954 (rather than "bytes" objects) to the Python subprocess module.
1955 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1958 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
1959 - Work around a change in OpenSSL 1.1.1 where return values that
1960 would previously indicate "no password" now indicate an empty
1961 password. Without this workaround, Tor instances running with
1962 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1963 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1965 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
1966 - Fix a compilation warning on some versions of GCC when building
1967 code that calls routerinfo_get_my_routerinfo() twice, assuming
1968 that the second call will succeed if the first one did. Fixes bug
1969 26269; bugfix on 0.2.8.2-alpha.
1971 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
1972 - Don't consider Tor running as a client if the ControlPort is open,
1973 but no actual client ports are open. Fixes bug 26062; bugfix
1976 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
1977 - Prevent a possible out-of-bounds smartlist read in
1978 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1980 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
1981 - Fix a very unlikely (impossible, we believe) null pointer
1982 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
1983 Coverity; this is CID 1430932.
1985 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
1986 - Fix a number of small memory leaks identified by coverity. Fixes
1987 bug 26467; bugfix on numerous Tor versions.
1989 o Code simplification and refactoring (backport from 0.3.3.5-rc):
1990 - Move the list of default directory authorities to its own file.
1991 Closes ticket 24854. Patch by "beastr0".
1994 Changes in version 0.3.4.4-rc - 2018-07-09
1995 Tor 0.3.4.4-rc fixes several small compilation, portability, and
1996 correctness issues in previous versions of Tor. This version is a
1997 release candidate: if no serious bugs are found, we expect that the
1998 stable 0.3.4 release will be (almost) the same as this release.
2000 o Minor features (compilation):
2001 - When building Tor, prefer to use Python 3 over Python 2, and more
2002 recent (contemplated) versions over older ones. Closes
2005 o Minor features (geoip):
2006 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2007 Country database. Closes ticket 26674.
2009 o Minor features (Rust, portability):
2010 - Rust cross-compilation is now supported. Closes ticket 25895.
2012 o Minor bugfixes (compilation):
2013 - Fix a compilation warning on some versions of GCC when building
2014 code that calls routerinfo_get_my_routerinfo() twice, assuming
2015 that the second call will succeed if the first one did. Fixes bug
2016 26269; bugfix on 0.2.8.2-alpha.
2018 o Minor bugfixes (control port):
2019 - Report the port correctly when a port is configured to bind to
2020 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
2021 - Handle the HSADDRESS= argument to the HSPOST command properly.
2022 (Previously, this argument was misparsed and thus ignored.) Fixes
2023 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
2025 o Minor bugfixes (correctness, flow control):
2026 - Upon receiving a stream-level SENDME cell, verify that our window
2027 has not grown too large. Fixes bug 26214; bugfix on svn
2030 o Minor bugfixes (memory, correctness):
2031 - Fix a number of small memory leaks identified by coverity. Fixes
2032 bug 26467; bugfix on numerous Tor versions.
2034 o Minor bugfixes (testing, compatibility):
2035 - When running the hs_ntor_ref.py test, make sure only to pass
2036 strings (rather than "bytes" objects) to the Python subprocess
2037 module. Python 3 on Windows seems to require this. Fixes bug
2038 26535; bugfix on 0.3.1.1-alpha.
2039 - When running the ntor_ref.py test, make sure only to pass strings
2040 (rather than "bytes" objects) to the Python subprocess module.
2041 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2045 Changes in version 0.3.3.8 - 2018-07-09
2046 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
2047 fixes for a memory leak affecting directory authorities.
2049 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
2050 - Stop leaking memory on directory authorities when planning to
2051 vote. This bug was crashing authorities by exhausting their
2052 memory. Fixes bug 26435; bugfix on 0.3.3.6.
2054 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
2055 - Make sure that failing tests in Rust will actually cause the build
2056 to fail: previously, they were ignored. Fixes bug 26258; bugfix
2059 o Minor features (compilation, backport from 0.3.4.4-rc):
2060 - When building Tor, prefer to use Python 3 over Python 2, and more
2061 recent (contemplated) versions over older ones. Closes
2064 o Minor features (geoip):
2065 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2066 Country database. Closes ticket 26674.
2068 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
2069 - Add several checks to detect whether Tor relays are uploading
2070 their descriptors without specifying why they regenerated them.
2071 Diagnostic for ticket 25686.
2073 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
2074 - Don't count path selection failures as circuit build failures.
2075 This change should eliminate cases where Tor blames its guard or
2076 the network for situations like insufficient microdescriptors
2077 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
2080 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2081 - Fix a compilation warning on some versions of GCC when building
2082 code that calls routerinfo_get_my_routerinfo() twice, assuming
2083 that the second call will succeed if the first one did. Fixes bug
2084 26269; bugfix on 0.2.8.2-alpha.
2086 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
2087 - Handle the HSADDRESS= argument to the HSPOST command properly.
2088 (Previously, this argument was misparsed and thus ignored.) Fixes
2089 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
2091 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2092 - Fix a number of small memory leaks identified by coverity. Fixes
2093 bug 26467; bugfix on numerous Tor versions.
2095 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
2096 - Relays now correctly block attempts to re-extend to the previous
2097 relay by Ed25519 identity. Previously they would warn in this
2098 case, but not actually reject the attempt. Fixes bug 26158; bugfix
2101 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
2102 - When shutting down, Tor now clears all the flags in the control.c
2103 module. This should prevent a bug where authentication cookies are
2104 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
2106 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2107 - When running the hs_ntor_ref.py test, make sure only to pass
2108 strings (rather than "bytes" objects) to the Python subprocess
2109 module. Python 3 on Windows seems to require this. Fixes bug
2110 26535; bugfix on 0.3.1.1-alpha.
2111 - When running the ntor_ref.py test, make sure only to pass strings
2112 (rather than "bytes" objects) to the Python subprocess module.
2113 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2117 Changes in version 0.3.4.3-alpha - 2018-06-26
2118 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
2119 one that was causing stability issues on directory authorities.
2121 o Major bugfixes (directory authority):
2122 - Stop leaking memory on directory authorities when planning to
2123 vote. This bug was crashing authorities by exhausting their
2124 memory. Fixes bug 26435; bugfix on 0.3.3.6.
2126 o Major bugfixes (rust, testing):
2127 - Make sure that failing tests in Rust will actually cause the build
2128 to fail: previously, they were ignored. Fixes bug 26258; bugfix
2131 o Minor feature (directory authorities):
2132 - Stop warning about incomplete bw lines before the first complete
2133 bw line has been found, so that additional header lines can be
2134 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
2136 o Minor features (relay, diagnostic):
2137 - Add several checks to detect whether Tor relays are uploading
2138 their descriptors without specifying why they regenerated them.
2139 Diagnostic for ticket 25686.
2141 o Minor features (unit tests):
2142 - Test complete bandwidth measurements files, and test that
2143 incomplete bandwidth lines only give warnings when the end of the
2144 header has not been detected. Fixes bug 25947; bugfix
2147 o Minor bugfixes (compilation):
2148 - Refrain from compiling unit testing related object files when
2149 --disable-unittests is set to configure script. Fixes bug 24891;
2150 bugfix on 0.2.5.1-alpha.
2151 - When linking the libtor_testing.a library, only include the
2152 dirauth object files once. Previously, they were getting added
2153 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
2154 - The --enable-fatal-warnings flag now affects Rust code as well.
2155 Closes ticket 26245.
2157 o Minor bugfixes (onion services):
2158 - Recompute some consensus information after detecting a clock jump,
2159 or after transitioning from a non-live consensus to a live
2160 consensus. We do this to avoid having an outdated state, and
2161 miscalculating the index for next-generation onion services. Fixes
2162 bug 24977; bugfix on 0.3.2.1-alpha.
2164 o Minor bugfixes (relay):
2165 - Relays now correctly block attempts to re-extend to the previous
2166 relay by Ed25519 identity. Previously they would warn in this
2167 case, but not actually reject the attempt. Fixes bug 26158; bugfix
2170 o Minor bugfixes (testing):
2171 - Fix compilation of the doctests in the Rust crypto crate. Fixes
2172 bug 26415; bugfix on 0.3.4.1-alpha.
2173 - Instead of trying to read the geoip configuration files from
2174 within the unit tests, instead create our own ersatz files with
2175 just enough geoip data in the format we expect. Trying to read
2176 from the source directory created problems on Windows with mingw,
2177 where the build system's paths are not the same as the platform's
2178 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
2179 - Refrain from trying to get an item from an empty smartlist in
2180 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
2181 to catch improper smartlist usage. Furthermore, enable
2182 DEBUG_SMARTLIST globally when build is configured with fragile
2183 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
2186 Changes in version 0.3.3.7 - 2018-06-12
2187 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
2188 fixes for bugs affecting compatibility and stability.
2190 o Directory authority changes:
2191 - Add an IPv6 address for the "dannenberg" directory authority.
2192 Closes ticket 26343.
2194 o Minor features (geoip):
2195 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
2196 Country database. Closes ticket 26351.
2198 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
2199 - Work around a change in OpenSSL 1.1.1 where return values that
2200 would previously indicate "no password" now indicate an empty
2201 password. Without this workaround, Tor instances running with
2202 OpenSSL 1.1.1 would accept descriptors that other Tor instances
2203 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
2205 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
2206 - Silence unused-const-variable warnings in zstd.h with some GCC
2207 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
2209 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
2210 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
2211 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
2212 miscounting the total number of circuits for these field values.)
2213 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
2215 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
2216 - Prevent a possible out-of-bounds smartlist read in
2217 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
2219 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
2220 - Only select relays when they have the descriptors we prefer to use
2221 for them. This change fixes a bug where we could select a relay
2222 because it had _some_ descriptor, but reject it later with a
2223 nonfatal assertion error because it didn't have the exact one we
2224 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
2227 Changes in version 0.3.4.2-alpha - 2018-06-12
2228 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
2229 release, and forward-ports an authority-only security fix from 0.3.3.6.
2231 o Directory authority changes:
2232 - Add an IPv6 address for the "dannenberg" directory authority.
2233 Closes ticket 26343.
2235 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
2236 - Fix a bug that could have allowed an attacker to force a directory
2237 authority to use up all its RAM by passing it a maliciously
2238 crafted protocol versions string. Fixes bug 25517; bugfix on
2239 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
2241 o Minor features (continuous integration):
2242 - Add the necessary configuration files for continuous integration
2243 testing on Windows, via the Appveyor platform. Closes ticket
2244 25549. Patches from Marcin Cieślak and Isis Lovecruft.
2246 o Minor features (geoip):
2247 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
2248 Country database. Closes ticket 26351.
2250 o Minor bugfixes (compatibility, openssl):
2251 - Work around a change in OpenSSL 1.1.1 where return values that
2252 would previously indicate "no password" now indicate an empty
2253 password. Without this workaround, Tor instances running with
2254 OpenSSL 1.1.1 would accept descriptors that other Tor instances
2255 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
2257 o Minor bugfixes (compilation):
2258 - Silence unused-const-variable warnings in zstd.h with some GCC
2259 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
2260 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
2261 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
2262 - Avoid a compiler warning when casting the return value of
2263 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
2264 26283; bugfix on 0.2.4.10-alpha.
2266 o Minor bugfixes (control port):
2267 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
2268 CIRC_BW events. Previously, such cells were counted entirely in
2269 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
2272 o Minor bugfixes (controller):
2273 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
2274 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
2275 miscounting the total number of circuits for these field values.)
2276 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
2278 o Minor bugfixes (hardening):
2279 - Prevent a possible out-of-bounds smartlist read in
2280 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
2282 o Minor bugfixes (onion services):
2283 - Fix a bug that blocked the creation of ephemeral v3 onion
2284 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
2286 o Minor bugfixes (test coverage tools):
2287 - Update our "cov-diff" script to handle output from the latest
2288 version of gcov, and to remove extraneous timestamp information
2289 from its output. Fixes bugs 26101 and 26102; bugfix
2293 Changes in version 0.3.3.6 - 2018-05-22
2294 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
2295 backports several important fixes from the 0.3.4.1-alpha.
2297 The Tor 0.3.3 series includes controller support and other
2298 improvements for v3 onion services, official support for embedding Tor
2299 within other applications, and our first non-trivial module written in
2300 the Rust programming language. (Rust is still not enabled by default
2301 when building Tor.) And as usual, there are numerous other smaller
2302 bugfixes, features, and improvements.
2304 Below are the changes since 0.3.3.5-rc. For a list of all changes
2305 since 0.3.2.10, see the ReleaseNotes file.
2307 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
2308 - When directory authorities read a zero-byte bandwidth file, they
2309 would previously log a warning with the contents of an
2310 uninitialised buffer. They now log a warning about the empty file
2311 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
2313 o Major bugfixes (security, directory authority, denial-of-service):
2314 - Fix a bug that could have allowed an attacker to force a directory
2315 authority to use up all its RAM by passing it a maliciously
2316 crafted protocol versions string. Fixes bug 25517; bugfix on
2317 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
2319 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
2320 - Avoid a rare assertion failure in the circuit build timeout code
2321 if we fail to allow any circuits to actually complete. Fixes bug
2322 25733; bugfix on 0.2.2.2-alpha.
2324 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
2325 - Avoid a crash when testing router reachability on a router that
2326 could have an ed25519 ID, but which does not. Fixes bug 25415;
2327 bugfix on 0.3.3.2-alpha.
2329 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
2330 - Correctly detect when onion services get disabled after HUP. Fixes
2331 bug 25761; bugfix on 0.3.2.1.
2333 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
2334 - Impose a limit on circuit cell queue size. The limit can be
2335 controlled by a consensus parameter. Fixes bug 25226; bugfix
2338 o Minor features (compatibility, backport from 0.3.4.1-alpha):
2339 - Avoid some compilation warnings with recent versions of LibreSSL.
2340 Closes ticket 26006.
2342 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
2343 - Our .travis.yml configuration now includes support for testing the
2344 results of "make distcheck". (It's not uncommon for "make check"
2345 to pass but "make distcheck" to fail.) Closes ticket 25814.
2346 - Our Travis CI configuration now integrates with the Coveralls
2347 coverage analysis tool. Closes ticket 25818.
2349 o Minor features (geoip):
2350 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
2351 database. Closes ticket 26104.
2353 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
2354 - Don't consider Tor running as a client if the ControlPort is open,
2355 but no actual client ports are open. Fixes bug 26062; bugfix
2358 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
2359 - Upon receiving a malformed connected cell, stop processing the
2360 cell immediately. Previously we would mark the connection for
2361 close, but continue processing the cell as if the connection were
2362 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
2364 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
2365 - Stop saying in the manual that clients cache ipv4 dns answers from
2366 exit relays. We haven't used them since 0.2.6.3-alpha, and in
2367 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
2368 we forgot to say so in the man page. Fixes bug 26052; bugfix
2371 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
2372 - Allow the nanosleep() system call, which glibc uses to implement
2373 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2375 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
2376 - Fix a memory leak when a v3 onion service is configured and gets a
2377 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
2378 - When parsing the descriptor signature, look for the token plus an
2379 extra white-space at the end. This is more correct but also will
2380 allow us to support new fields that might start with "signature".
2381 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
2383 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
2384 - Avoid a crash when running with DirPort set but ORPort turned off.
2385 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
2387 o Documentation (backport from 0.3.4.1-alpha):
2388 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
2389 ticket 25857. Patch from "CTassisF".
2392 Changes in version 0.3.4.1-alpha - 2018-05-17
2393 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
2394 includes refactoring to begin reducing Tor's binary size and idle CPU
2395 usage on mobile, along with prep work for new bandwidth scanners,
2396 improvements to the experimental "vanguards" feature, and numerous
2397 other small features and bugfixes.
2399 o New system requirements:
2400 - Tor no longer tries to support old operating systems without
2401 mmap() or some local equivalent. Apparently, compilation on such
2402 systems has been broken for some time, without anybody noticing or
2403 complaining. Closes ticket 25398.
2405 o Major feature (directory authority, modularization):
2406 - The directory authority subsystem has been modularized. The code
2407 is now located in src/or/dirauth/, and is compiled in by default.
2408 To disable the module, the configure option
2409 --disable-module-dirauth has been added. This module may be
2410 disabled by default in some future release. Closes ticket 25610.
2412 o Major features (main loop, CPU usage):
2413 - When Tor is disabled (via DisableNetwork or via hibernation), it
2414 no longer needs to run any per-second events. This change should
2415 make it easier for mobile applications to disable Tor while the
2416 device is sleeping, or Tor is not running. Closes ticket 26063.
2417 - Tor no longer enables all of its periodic events by default.
2418 Previously, Tor would enable all possible main loop events,
2419 regardless of whether it needed them. Furthermore, many of these
2420 events are now disabled with Tor is hibernating or DisableNetwork
2421 is set. This is a big step towards reducing client CPU usage by
2422 reducing the amount of wake-ups the daemon does. Closes ticket
2424 - The bandwidth-limitation logic has been refactored so that
2425 bandwidth calculations are performed on-demand, rather than every
2426 TokenBucketRefillInterval milliseconds. This change should improve
2427 the granularity of our bandwidth calculations, and limit the
2428 number of times that the Tor process needs to wake up when it is
2429 idle. Closes ticket 25373.
2430 - Move responsibility for many operations from a once-per-second
2431 callback to a callback that is only scheduled as needed. Moving
2432 this functionality has allowed us to disable the callback when
2433 Tor's network is disabled. Once enough items are removed from our
2434 once-per-second callback, we can eliminate it entirely to conserve
2435 CPU when idle. The functionality removed includes: closing
2436 connections, circuits, and channels (ticket 25932); consensus
2437 voting (25937); flushing log callbacks (25951); honoring delayed
2438 SIGNEWNYM requests (25949); rescanning the consensus cache
2439 (25931); saving the state file to disk (25948); warning relay
2440 operators about unreachable ports (25952); and keeping track of
2441 Tor's uptime (26009).
2443 o Major bugfixes (directory authorities, security):
2444 - When directory authorities read a zero-byte bandwidth file, they
2445 would previously log a warning with the contents of an
2446 uninitialised buffer. They now log a warning about the empty file
2447 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
2449 o Major bugfixes (crash):
2450 - Avoid a rare assertion failure in the circuit build timeout code
2451 if we fail to allow any circuits to actually complete. Fixes bug
2452 25733; bugfix on 0.2.2.2-alpha.
2454 o Major bugfixes (directory authority):
2455 - Avoid a crash when testing router reachability on a router that
2456 could have an ed25519 ID, but which does not. Fixes bug 25415;
2457 bugfix on 0.3.3.2-alpha.
2459 o Major bugfixes (onion service):
2460 - Correctly detect when onion services get disabled after HUP. Fixes
2461 bug 25761; bugfix on 0.3.2.1.
2463 o Major bugfixes (protover, voting):
2464 - Revise Rust implementation of protover to use a more memory-
2465 efficient voting algorithm and corresponding data structures, thus
2466 avoiding a potential (but small impact) DoS attack where specially
2467 crafted protocol strings would expand to several potential
2468 megabytes in memory. In the process, several portions of code were
2469 revised to be methods on new, custom types, rather than functions
2470 taking interchangeable types, thus increasing type safety of the
2471 module. Custom error types and handling were added as well, in
2472 order to facilitate better error dismissal/handling in outside
2473 crates and avoid mistakenly passing an internal error string to C
2474 over the FFI boundary. Many tests were added, and some previous
2475 differences between the C and Rust implementations have been
2476 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
2478 o Major bugfixes (relay, denial of service):
2479 - Impose a limit on circuit cell queue size. The limit can be
2480 controlled by a consensus parameter. Fixes bug 25226; bugfix
2483 o Minor features (accounting):
2484 - When Tor becomes dormant, it now uses a scheduled event to wake up
2485 at the right time. Previously, we would use the per-second timer
2486 to check whether to wake up, but we no longer have any per-second
2487 timers enabled when the network is disabled. Closes ticket 26064.
2489 o Minor features (code quality):
2490 - Add optional spell-checking for the Tor codebase, using the
2491 "misspell" program. To use this feature, run "make check-typos".
2492 Closes ticket 25024.
2494 o Minor features (compatibility):
2495 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
2496 the no-deprecated option, and builds correctly with them. Closes
2497 tickets 19429, 19981, and 25353.
2498 - Avoid some compilation warnings with recent versions of LibreSSL.
2499 Closes ticket 26006.
2501 o Minor features (compression, zstd):
2502 - When running with zstd, Tor now considers using advanced functions
2503 that the zstd maintainers have labeled as potentially unstable. To
2504 prevent breakage, Tor will only use this functionality when the
2505 runtime version of the zstd library matches the version with which
2506 Tor was compiled. Closes ticket 25162.
2508 o Minor features (configuration):
2509 - The "DownloadSchedule" options have been renamed to end with
2510 "DownloadInitialDelay". The old names are still allowed, but will
2511 produce a warning. Comma-separated lists are still permitted for
2512 these options, but all values after the first are ignored (as they
2513 have been since 0.2.9). Closes ticket 23354.
2515 o Minor features (continuous integration):
2516 - Our .travis.yml configuration now includes support for testing the
2517 results of "make distcheck". (It's not uncommon for "make check"
2518 to pass but "make distcheck" to fail.) Closes ticket 25814.
2519 - Our Travis CI configuration now integrates with the Coveralls
2520 coverage analysis tool. Closes ticket 25818.
2522 o Minor features (control port):
2523 - Introduce GETINFO "current-time/{local,utc}" to return the local
2524 and UTC times respectively in ISO format. This helps a controller
2525 like Tor Browser detect a time-related error. Closes ticket 25511.
2526 Patch by Neel Chauhan.
2527 - Introduce new fields to the CIRC_BW event. There are two new
2528 fields in each of the read and written directions. The DELIVERED
2529 fields report the total valid data on the circuit, as measured by
2530 the payload sizes of verified and error-checked relay command
2531 cells. The OVERHEAD fields report the total unused bytes in each
2532 of these cells. Closes ticket 25903.
2534 o Minor features (directory authority):
2535 - Directory authorities now open their key-pinning files as O_SYNC,
2536 to limit their chances of accidentally writing partial lines.
2537 Closes ticket 23909.
2539 o Minor features (directory authority, forward compatibility):
2540 - Make the lines of the measured bandwidth file able to contain
2541 their entries in any order. Previously, the node_id entry needed
2542 to come first. Closes ticket 26004.
2544 o Minor features (entry guards):
2545 - Introduce a new torrc option NumPrimaryGuards for controlling the
2546 number of primary guards. Closes ticket 25843.
2548 o Minor features (geoip):
2549 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
2550 database. Closes ticket 26104.
2552 o Minor features (performance):
2553 - Avoid a needless call to malloc() when processing an incoming
2554 relay cell. Closes ticket 24914.
2555 - Make our timing-wheel code run a tiny bit faster on 32-bit
2556 platforms, by preferring 32-bit math to 64-bit. Closes
2558 - Avoid a needless malloc()/free() pair every time we handle an ntor
2559 handshake. Closes ticket 25150.
2561 o Minor features (testing):
2562 - Add a unit test for voting_schedule_get_start_of_next_interval().
2563 Closes ticket 26014, and helps make unit test coverage
2565 - A new unittests module specifically for testing the functions in
2566 the (new-ish) bridges.c module has been created with new
2567 unittests, raising the code coverage percentages. Closes 25425.
2568 - We now have improved testing for addressmap_get_virtual_address()
2569 function. This should improve our test coverage, and make our test
2570 coverage more deterministic. Closes ticket 25993.
2572 o Minor features (timekeeping, circuit scheduling):
2573 - When keeping track of how busy each circuit have been recently on
2574 a given connection, use coarse-grained monotonic timers rather
2575 than gettimeofday(). This change should marginally increase
2576 accuracy and performance. Implements part of ticket 25927.
2578 o Minor bugfixes (bandwidth management):
2579 - Consider ourselves "low on write bandwidth" if we have exhausted
2580 our write bandwidth some time in the last second. This was the
2581 documented behavior before, but the actual behavior was to change
2582 this value every TokenBucketRefillInterval. Fixes bug 25828;
2583 bugfix on 0.2.3.5-alpha.
2585 o Minor bugfixes (C correctness):
2586 - Add a missing lock acquisition in the shutdown code of the control
2587 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
2588 Coverity; this is CID 1433643.
2590 o Minor bugfixes (circuit path selection):
2591 - Don't count path selection failures as circuit build failures.
2592 This change should eliminate cases where Tor blames its guard or
2593 the network for situations like insufficient microdescriptors
2594 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
2597 o Minor bugfixes (client):
2598 - Don't consider Tor running as a client if the ControlPort is open,
2599 but no actual client ports are open. Fixes bug 26062; bugfix
2602 o Minor bugfixes (code style):
2603 - Fixed multiple includes of transports.h in src/or/connection.c
2604 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
2605 - Remove the unused variable n_possible from the function
2606 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
2608 o Minor bugfixes (control interface):
2609 - Respond with more human-readable error messages to GETINFO exit-
2610 policy/* requests. Also, let controller know if an error is
2611 transient (response code 551) or not (response code 552). Fixes
2612 bug 25852; bugfix on 0.2.8.1-alpha.
2614 o Minor bugfixes (controller):
2615 - Make CIRC_BW event reflect the total of all data sent on a
2616 circuit, including padding and dropped cells. Also fix a mis-
2617 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
2618 bugfix on 0.2.5.2-alpha.
2620 o Minor bugfixes (correctness, client):
2621 - Upon receiving a malformed connected cell, stop processing the cell
2622 immediately. Previously we would mark the connection for close, but
2623 continue processing the cell as if the connection were open. Fixes bug
2624 26072; bugfix on 0.2.4.7-alpha.
2626 o Minor bugfixes (directory client):
2627 - When unverified-consensus is verified, rename it to cached-
2628 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
2629 - Fixed launching a certificate fetch always during the scheduled
2630 periodic consensus fetch by fetching only in those cases when
2631 consensus are waiting for certs. Fixes bug 24740; bugfix
2634 o Minor bugfixes (documentation):
2635 - Stop saying in the manual that clients cache ipv4 dns answers from
2636 exit relays. We haven't used them since 0.2.6.3-alpha, and in
2637 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
2638 we forgot to say so in the man page. Fixes bug 26052; bugfix
2641 o Minor bugfixes (error reporting):
2642 - Improve tolerance for directory authorities with skewed clocks.
2643 Previously, an authority with a clock more than 60 seconds ahead
2644 could cause a client with a correct clock to warn that the
2645 client's clock was behind. Now the clocks of a majority of
2646 directory authorities have to be ahead of the client before this
2647 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
2649 o Minor bugfixes (Linux seccomp2 sandbox):
2650 - Allow the nanosleep() system call, which glibc uses to implement
2651 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2653 o Minor bugfixes (onion service):
2654 - Fix a memory leak when a v3 onion service is configured and gets a
2655 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
2656 - When parsing the descriptor signature, look for the token plus an
2657 extra white-space at the end. This is more correct but also will
2658 allow us to support new fields that might start with "signature".
2659 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
2661 o Minor bugfixes (path selection):
2662 - Only select relays when they have the descriptors we prefer to use
2663 for them. This change fixes a bug where we could select a relay
2664 because it had _some_ descriptor, but reject it later with a
2665 nonfatal assertion error because it didn't have the exact one we
2666 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
2668 o Minor bugfixes (portability):
2669 - Do not align mmap length, as it is not required by POSIX, and the
2670 getpagesize function is deprecated. Fixes bug 25399; bugfix
2673 o Minor bugfixes (portability, FreeBSD):
2674 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
2675 does not stringify on FreeBSD, so we switch to tor_asprintf().
2676 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
2678 o Minor bugfixes (relay statistics):
2679 - When a relay is collecting internal statistics about how many
2680 create cell requests it has seen of each type, accurately count
2681 the requests from relays that temporarily fall out of the
2682 consensus. (To be extra conservative, we were already ignoring
2683 requests from clients in our counts, and we continue ignoring them
2684 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
2686 o Minor bugfixes (relay, crash):
2687 - Avoid a crash when running with DirPort set but ORPort turned off.
2688 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
2690 o Minor bugfixes (restart-in-process):
2691 - When shutting down, Tor now clears all the flags in the control.c
2692 module. This should prevent a bug where authentication cookies are
2693 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
2695 o Minor bugfixes (testing):
2696 - When testing workqueue event-cancellation, make sure that we
2697 actually cancel an event, and that cancel each event with equal
2698 probability. (It was previously possible, though extremely
2699 unlikely, for our event-canceling test not to cancel any events.)
2700 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
2701 - Repeat part of the test in test_client_pick_intro() a number of
2702 times, to give it consistent coverage. Fixes bug 25996; bugfix
2704 - Remove randomness from the hs_common/responsible_hsdirs test, so
2705 that it always takes the same path through the function it tests.
2706 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
2707 - Change the behavior of the "channel/outbound" test so that it
2708 never causes a 10-second rollover for the EWMA circuitmux code.
2709 Previously, this behavior would happen randomly, and result in
2710 fluctuating test coverage. Fixes bug 25994; bugfix
2712 - Use X509_new() to allocate certificates that will be freed later
2713 with X509_free(). Previously, some parts of the unit tests had
2714 used tor_malloc_zero(), which is incorrect, and which caused test
2715 failures on Windows when they were built with extra hardening.
2716 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
2718 - While running the circuit_timeout test, fix the PRNG to a
2719 deterministic AES stream, so that the test coverage from this test
2720 will itself be deterministic. Fixes bug 25995; bugfix
2723 o Minor bugfixes (vanguards):
2724 - Allow the last hop in a vanguard circuit to be the same as our
2725 first, to prevent the adversary from influencing guard node choice
2726 by choice of last hop. Also prevent the creation of A - B - A
2727 paths, or A - A paths, which are forbidden by relays. Fixes bug
2728 25870; bugfix on 0.3.3.1-alpha.
2730 o Code simplification and refactoring:
2731 - Remove duplicate code in parse_{c,s}method_line and bootstrap
2732 their functionalities into a single function. Fixes bug 6236;
2733 bugfix on 0.2.3.6-alpha.
2734 - We remove the PortForwsrding and PortForwardingHelper options,
2735 related functions, and the port_forwarding tests. These options
2736 were used by the now-deprecated Vidalia to help ordinary users
2737 become Tor relays or bridges. Closes ticket 25409. Patch by
2739 - In order to make the OR and dir checking function in router.c less
2740 confusing we renamed some functions and
2741 consider_testing_reachability() has been split into
2742 router_should_check_reachability() and
2743 router_do_reachability_checks(). Also we improved the documentation
2744 in some functions. Closes ticket 18918.
2745 - Initial work to isolate Libevent usage to a handful of modules in
2746 our codebase, to simplify our call structure, and so that we can
2747 more easily change event loops in the future if needed. Closes
2749 - Introduce a function to call getsockname() and return tor_addr_t,
2750 to save a little complexity throughout the codebase. Closes
2752 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
2753 as hsdir_index is always present. Also, we move hsdir_index_t into
2754 or.h. Closes ticket 23094. Patch by Neel Chauhan.
2755 - Merge functions used for describing nodes and suppress the
2756 functions that do not allocate memory for the output buffer
2757 string. NODE_DESC_BUF_LEN constant and format_node_description()
2758 function cannot be used externally from router.c module anymore.
2759 Closes ticket 25432. Patch by valentecaio.
2760 - Our main loop has been simplified so that all important operations
2761 happen inside events. Previously, some operations had to happen
2762 outside the event loop, to prevent infinite sequences of event
2763 activations. Closes ticket 25374.
2764 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
2765 it in register_intro_circ() and service_intro_point_new(). This
2766 prevents the digest from being re-calculated each time. Closes
2767 ticket 23107. Patch by Neel Chauhan.
2768 - Refactor token-bucket implementations to use a common backend.
2769 Closes ticket 25766.
2770 - Remove extern declaration of stats_n_seconds_working variable from
2771 main, protecting its accesses with get_uptime() and reset_uptime()
2772 functions. Closes ticket 25081, patch by “valentecaio”.
2773 - Remove our previous logic for "cached gettimeofday()" -- our
2774 coarse monotonic timers are fast enough for this purpose, and far
2775 less error-prone. Implements part of ticket 25927.
2776 - Remove the return value for fascist_firewall_choose_address_base(),
2777 and sister functions such as fascist_firewall_choose_address_node()
2778 and fascist_firewall_choose_address_rs(). Also, while we're here,
2779 initialize the ap argument as leaving it uninitialized can pose a
2780 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
2781 - Rename two fields of connection_t struct. timestamp_lastwritten is
2782 renamed to timestamp_last_write_allowed and timestamp_lastread is
2783 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
2785 - Since Tor requires C99, remove our old workaround code for libc
2786 implementations where free(NULL) doesn't work. Closes ticket 24484.
2787 - Use our standard rate-limiting code to deal with excessive
2788 libevent failures, rather than the hand-rolled logic we had
2789 before. Closes ticket 26016.
2790 - We remove the return value of node_get_prim_orport() and
2791 node_get_prim_dirport(), and introduce node_get_prim_orport() in
2792 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
2793 check for a null address. Closes ticket 23873. Patch by
2795 - We switch to should_record_bridge_info() in
2796 geoip_note_client_seen() and options_need_geoip_info() instead of
2797 accessing the configuration values directly. Fixes bug 25290;
2798 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
2800 o Deprecated features:
2801 - As we are not recommending 0.2.5 anymore, we require relays that
2802 once had an ed25519 key associated with their RSA key to always
2803 have that key, instead of allowing them to drop back to a version
2804 that didn't support ed25519. This means they need to use a new RSA
2805 key if they want to downgrade to an older version of tor without
2806 ed25519. Closes ticket 20522.
2809 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
2810 ticket 25857. Patch from "CTassisF".
2813 - Directory authorities will no longer support voting according to
2814 any consensus method before consensus method 25. This keeps
2815 authorities compatible with all authorities running 0.2.9.8 and
2816 later, and does not break any clients or relays. Implements ticket
2817 24378 and proposal 290.
2818 - The PortForwarding and PortForwardingHelper features have been
2819 removed. The reasoning is, given that implementations of NAT
2820 traversal protocols within common consumer grade routers are
2821 frequently buggy, and that the target audience for a NAT punching
2822 feature is a perhaps less-technically-inclined relay operator,
2823 when the helper fails to setup traversal the problems are usually
2824 deep, ugly, and very router specific, making them horrendously
2825 impossible for technical support to reliable assist with, and thus
2826 resulting in frustration all around. Unfortunately, relay
2827 operators who would like to run relays behind NATs will need to
2828 become more familiar with the port forwarding configurations on
2829 their local router. Closes 25409.
2830 - The TestingEnableTbEmptyEvent option has been removed. It was used
2831 in testing simulations to measure how often connection buckets
2832 were emptied, in order to improve our scheduling, but it has not
2833 been actively used in years. Closes ticket 25760.
2834 - The old "round-robin" circuit multiplexer (circuitmux)
2835 implementation has been removed, along with a fairly large set of
2836 code that existed to support it. It has not been the default
2837 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
2838 but it still required an unreasonable amount of memory and CPU.
2839 Closes ticket 25268.
2842 Changes in version 0.3.3.5-rc - 2018-04-15
2843 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
2844 including some that could affect reliability or correctness.
2846 This is the first release candidate in the 0.3.3 series. If we find no
2847 new bugs or regression here, then the first stable 0.3.3 release will
2848 be nearly identical to this one.
2850 o Major bugfixes (security, protover, voting):
2851 - Revise Rust implementation of protover to use a more memory-
2852 efficient voting algorithm and corresponding data structures, thus
2853 avoiding a potential memory-based DoS attack where specially
2854 crafted protocol strings would expand to fill available memory.
2855 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
2857 o Major bugfixes (performance, load balancing):
2858 - Directory authorities no longer vote in favor of the Guard flag
2859 for relays without directory support. Starting in Tor
2860 0.3.0.1-alpha, clients have been avoiding using such relays in the
2861 Guard position, leading to increasingly broken load balancing for
2862 the 5%-or-so of Guards that don't advertise directory support.
2863 Fixes bug 22310; bugfix on 0.3.0.6.
2865 o Minor feature (continuous integration):
2866 - Update the Travis CI configuration to use the stable Rust channel,
2867 now that we have decided to require that. Closes ticket 25714.
2869 o Minor features (config options):
2870 - Change the way the default value for MaxMemInQueues is calculated.
2871 We now use 40% of the hardware RAM if the system has 8 GB RAM or
2872 more. Otherwise we use the former value of 75%. Closes
2875 o Minor features (geoip):
2876 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
2877 Country database. Closes ticket 25718.
2879 o Minor bugfixes (client):
2880 - When using a listed relay as a bridge, and also using
2881 microdescriptors, and considering that relay as a non-bridge in a
2882 circuit, treat its microdescriptor as a valid source of
2883 information about that relay. This change should prevent a non-
2884 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
2886 o Minor bugfixes (controller):
2887 - Restore the correct operation of the RESOLVE command, which had
2888 been broken since we added the ability to enable/disable DNS on
2889 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
2891 o Minor bugfixes (distribution, compilation, rust):
2892 - Build correctly when the rust dependencies submodule is loaded,
2893 but the TOR_RUST_DEPENDENCIES environment variable is not set.
2894 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
2895 - Actually include all of our Rust source in our source
2896 distributions. (Previously, a few of the files were accidentally
2897 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
2899 o Minor bugfixes (documentation):
2900 - Document that the PerConnBW{Rate,Burst} options will fall back to
2901 their corresponding consensus parameters only if those parameters
2902 are set. Previously we had claimed that these values would always
2903 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
2904 - Revert a misformatting issue in the ExitPolicy documentation.
2905 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
2907 o Minor bugfixes (exit relay DNS retries):
2908 - Re-attempt timed-out DNS queries 3 times before failure, since our
2909 timeout is 5 seconds for them, but clients wait 10-15. Also allow
2910 slightly more timeouts per resolver when an exit has multiple
2911 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
2913 o Minor bugfixes (onion services):
2914 - Re-instate counting the client HSDir fetch circuits against the
2915 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
2917 - Remove underscores from the _HSLayer{2,3}Nodes options. This
2918 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
2919 Fixes bug 25581; bugfix on 0.3.3.1-alpha
2921 o Code simplification and refactoring:
2922 - Move the list of default directory authorities to its own file.
2923 Closes ticket 24854. Patch by "beastr0".
2925 o Documentation (manpage, denial of service):
2926 - Provide more detail about the denial-of-service options, by
2927 listing each mitigation and explaining how they relate. Closes
2931 Changes in version 0.3.3.4-alpha - 2018-03-29
2932 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
2933 the alpha testing of earlier releases in its series. We are
2934 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
2936 o New system requirements:
2937 - When built with Rust, Tor now depends on version 0.2.39 of the
2938 libc crate. Closes tickets 25310 and 25664.
2940 o Major bugfixes (relay, connection):
2941 - If we have failed to connect to a relay and received a connection
2942 refused, timeout, or similar error (at the TCP level), do not try
2943 that same address/port again for 60 seconds after the failure has
2944 occurred. Fixes bug 24767; bugfix on 0.0.6.
2946 o Minor features (geoip):
2947 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
2948 Country database. Closes ticket 25469.
2950 o Minor features (log messages):
2951 - Improve log message in the out-of-memory handler to include
2952 information about memory usage from the different compression
2953 backends. Closes ticket 25372.
2955 o Minor features (sandbox):
2956 - Explicitly permit the poll() system call when the Linux
2957 seccomp2-based sandbox is enabled: apparently, some versions of
2958 libc use poll() when calling getpwnam(). Closes ticket 25313.
2960 o Minor bugfixes (C correctness):
2961 - Fix a very unlikely (impossible, we believe) null pointer
2962 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
2963 Coverity; this is CID 1430932.
2965 o Minor bugfixes (channel, client):
2966 - Better identify client connection when reporting to the geoip
2967 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
2969 o Minor bugfixes (compilation):
2970 - Fix a C99 compliance issue in our configuration script that caused
2971 compilation issues when compiling Tor with certain versions of
2972 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
2974 o Minor bugfixes (controller, reliability):
2975 - Avoid a (nonfatal) assertion failure when extending a one-hop
2976 circuit from the controller to become a multihop circuit. Fixes
2977 bug 24903; bugfix on 0.2.5.2-alpha.
2979 o Major bugfixes (networking):
2980 - Tor will no longer reject IPv6 address strings from Tor Browser
2981 when they are passed as hostnames in SOCKS5 requests. Fixes bug
2982 25036, bugfix on Tor 0.3.1.2.
2984 o Minor bugfixes (networking):
2985 - string_is_valid_hostname() will not consider IP strings to be
2986 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
2988 o Minor bugfixes (onion service v3):
2989 - Avoid an assertion failure when the next onion service
2990 descriptor rotation type is out of sync with the consensus's
2991 valid-after time. Instead, log a warning message with extra
2992 information, so we can better hunt down the cause of this
2993 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
2995 o Minor bugfixes (testing):
2996 - Avoid intermittent test failures due to a test that had relied on
2997 onion service introduction point creation finishing within 5
2998 seconds of real clock time. Fixes bug 25450; bugfix
3000 - Rust crates are now automatically detected and tested. Previously,
3001 some crates were not tested by `make test-rust` due to a static
3002 string in the `src/test/test_rust.sh` script specifying which
3003 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
3005 o Minor bugfixes (testing, benchmarks):
3006 - Fix a crash when running benchmark tests on win32 systems. The
3007 crash was due to a mutex that wasn't initialized before logging
3008 and options were initialized. Fixes bug 25479; bugfix
3011 o Minor bugfixes (warnings, ipv6):
3012 - Avoid a bug warning that could occur when trying to connect to a
3013 relay over IPv6. This warning would occur on a Tor instance that
3014 downloads router descriptors, but prefers to use microdescriptors.
3015 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
3017 o Code simplification and refactoring:
3018 - Remove the old (deterministic) directory retry logic entirely:
3019 We've used exponential backoff exclusively for some time. Closes
3023 - Improved the documentation of AccountingStart parameter. Closes
3025 - Update the documentation for "Log" to include the current list of
3026 logging domains. Closes ticket 25378.
3029 Changes in version 0.3.1.10 - 2018-03-03
3030 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
3033 It includes an important security fix for a remote crash attack
3034 against directory authorities, tracked as TROVE-2018-001.
3036 This release also backports our new system for improved resistance to
3037 denial-of-service attacks against relays.
3039 This release also fixes several minor bugs and annoyances from
3042 All directory authorities should upgrade to one of the versions
3043 released today. Relays running 0.3.1.x may wish to update to one of
3044 the versions released today, for the DoS mitigations.
3046 Please note: according to our release calendar, Tor 0.3.1 will no
3047 longer be supported after 1 July 2018. If you will be running Tor
3048 after that date, you should make sure to plan to upgrade to the latest
3049 stable version, or downgrade to 0.2.9 (which will receive long-term
3052 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
3053 - Fix a protocol-list handling bug that could be used to remotely crash
3054 directory authorities with a null-pointer exception. Fixes bug 25074;
3055 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
3058 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
3059 - Give relays some defenses against the recent network overload. We
3060 start with three defenses (default parameters in parentheses).
3061 First: if a single client address makes too many concurrent
3062 connections (>100), hang up on further connections. Second: if a
3063 single client address makes circuits too quickly (more than 3 per
3064 second, with an allowed burst of 90) while also having too many
3065 connections open (3), refuse new create cells for the next while
3066 (1-2 hours). Third: if a client asks to establish a rendezvous
3067 point to you directly, ignore the request. These defenses can be
3068 manually controlled by new torrc options, but relays will also
3069 take guidance from consensus parameters, so there's no need to
3070 configure anything manually. Implements ticket 24902.
3072 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
3073 - Update the sandbox rules so that they should now work correctly
3074 with Glibc 2.26. Closes ticket 24315.
3076 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
3077 - Fix an "off by 2" error in counting rendezvous failures on the
3078 onion service side. While we thought we would stop the rendezvous
3079 attempt after one failed circuit, we were actually making three
3080 circuit attempts before giving up. Now switch to a default of 2,
3081 and allow the consensus parameter "hs_service_max_rdv_failures" to
3082 override. Fixes bug 24895; bugfix on 0.0.6.
3084 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
3085 - Add Link protocol version 5 to the supported protocols list. Fixes
3086 bug 25070; bugfix on 0.3.1.1-alpha.
3088 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
3089 - Fix a set of false positives where relays would consider
3090 connections to other relays as being client-only connections (and
3091 thus e.g. deserving different link padding schemes) if those
3092 relays fell out of the consensus briefly. Now we look only at the
3093 initial handshake and whether the connection authenticated as a
3094 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
3096 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
3097 - Make our OOM handler aware of the geoip client history cache so it
3098 doesn't fill up the memory. This check is important for IPv6 and
3099 our DoS mitigation subsystem. Closes ticket 25122.
3101 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
3102 - Change relay bandwidth reporting stats interval from 4 hours to 24
3103 hours in order to reduce the efficiency of guard discovery
3104 attacks. Fixes ticket 23856.
3106 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
3107 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3108 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3109 since they neither disabled TLS 1.3 nor enabled any of the
3110 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3111 Closes ticket 24978.
3113 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
3114 - The fallback directory list has been re-generated based on the
3115 current status of the network. Tor uses fallback directories to
3116 bootstrap when it doesn't yet have up-to-date directory
3117 information. Closes ticket 24801.
3118 - Make the default DirAuthorityFallbackRate 0.1, so that clients
3119 prefer to bootstrap from fallback directory mirrors. This is a
3120 follow-up to 24679, which removed weights from the default
3121 fallbacks. Implements ticket 24681.
3123 o Minor features (geoip):
3124 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
3127 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
3128 - Use the actual observed address of an incoming relay connection,
3129 not the canonical address of the relay from its descriptor, when
3130 making decisions about how to handle the incoming connection.
3131 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
3133 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
3134 - Directory authorities, when refusing a descriptor from a rejected
3135 relay, now explicitly tell the relay (in its logs) to set a valid
3136 ContactInfo address and contact the bad-relays@ mailing list.
3137 Fixes bug 25170; bugfix on 0.2.9.1.
3139 o Minor bugfixes (address selection, backport from 0.3.2.9):
3140 - When the fascist_firewall_choose_address_ functions don't find a
3141 reachable address, set the returned address to the null address
3142 and port. This is a precautionary measure, because some callers do
3143 not check the return value. Fixes bug 24736; bugfix
3146 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
3147 - Fetch descriptors aggressively whenever we lack enough to build
3148 circuits, regardless of how many descriptors we are missing.
3149 Previously, we would delay launching the fetch when we had fewer
3150 than 15 missing descriptors, even if some of those descriptors
3151 were blocking circuits from building. Fixes bug 23985; bugfix on
3152 0.1.1.11-alpha. The effects of this bug became worse in
3153 0.3.0.3-alpha, when we began treating missing descriptors from our
3154 primary guards as a reason to delay circuits.
3155 - Don't try fetching microdescriptors from relays that have failed
3156 to deliver them in the past. Fixes bug 23817; bugfix
3159 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
3160 - Fix a signed/unsigned comparison warning introduced by our fix to
3161 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
3163 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
3164 - Avoid a crash when attempting to use the seccomp2 sandbox together
3165 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
3168 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
3169 - Fix a possible crash on malformed consensus. If a consensus had
3170 contained an unparseable protocol line, it could have made clients
3171 and relays crash with a null-pointer exception. To exploit this
3172 issue, however, an attacker would need to be able to subvert the
3173 directory authority system. Fixes bug 25251; bugfix on
3174 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
3176 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
3177 - Recover better from empty or corrupt files in the consensus cache
3178 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
3179 - When a consensus diff calculation is only partially successful,
3180 only record the successful parts as having succeeded. Partial
3181 success can happen if (for example) one compression method fails
3182 but the others succeed. Previously we misrecorded all the
3183 calculations as having succeeded, which would later cause a
3184 nonfatal assertion failure. Fixes bug 24086; bugfix
3187 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
3188 - Tor now updates its guard state when it reads a consensus
3189 regardless of whether it's missing descriptors. That makes tor use
3190 its primary guards to fetch descriptors in some edge cases where
3191 it would previously have used fallback directories. Fixes bug
3192 23862; bugfix on 0.3.0.1-alpha.
3194 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
3195 - Don't treat inability to store a cached consensus object as a bug:
3196 it can happen normally when we are out of disk space. Fixes bug
3197 24859; bugfix on 0.3.1.1-alpha.
3199 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
3200 - When queuing DESTROY cells on a channel, only queue the circuit-id
3201 and reason fields: not the entire 514-byte cell. This fix should
3202 help mitigate any bugs or attacks that fill up these queues, and
3203 free more RAM for other uses. Fixes bug 24666; bugfix
3206 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
3207 - When closing a connection via close_connection_immediately(), we
3208 mark it as "not blocked on bandwidth", to prevent later calls from
3209 trying to unblock it, and give it permission to read. This fixes a
3210 backtrace warning that can happen on relays under various
3211 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
3213 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
3214 - When selecting relays by bandwidth, avoid a rounding error that
3215 could sometimes cause load to be imbalanced incorrectly.
3216 Previously, we would always round upwards; now, we round towards
3217 the nearest integer. This had the biggest effect when a relay's
3218 weight adjustments should have given it weight 0, but it got
3219 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
3220 - When calculating the fraction of nodes that have descriptors, and
3221 all nodes in the network have zero bandwidths, count the number of
3222 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
3223 - Actually log the total bandwidth in compute_weighted_bandwidths().
3224 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
3226 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
3227 - Improve the performance of our consensus-diff application code
3228 when Tor is built with the --enable-fragile-hardening option set.
3229 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
3231 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
3232 - Don't exit the Tor process if setrlimit() fails to change the file
3233 limit (which can happen sometimes on some versions of OSX). Fixes
3234 bug 21074; bugfix on 0.0.9pre5.
3236 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
3237 - Fix a bug in the bit-counting parts of our timing-wheel code on
3238 MSVC. (Note that MSVC is still not a supported build platform, due
3239 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
3242 o Minor bugfixes (relay, partial backport):
3243 - Make the internal channel_is_client() function look at what sort
3244 of connection handshake the other side used, rather than whether
3245 the other side ever sent a create_fast cell to us. Backports part
3246 of the fixes from bugs 22805 and 24898.
3248 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
3249 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
3251 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
3252 bugfix on 0.2.9.4-alpha.
3254 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
3255 - Update the "rust dependencies" submodule to be a project-level
3256 repository, rather than a user repository. Closes ticket 25323.
3259 Changes in version 0.2.9.15 - 2018-03-03
3260 Tor 0.2.9.15 backports important security and stability bugfixes from
3263 It includes an important security fix for a remote crash attack
3264 against directory authorities, tracked as TROVE-2018-001.
3266 This release also backports our new system for improved resistance to
3267 denial-of-service attacks against relays.
3269 This release also fixes several minor bugs and annoyances from
3272 All directory authorities should upgrade to one of the versions
3273 released today. Relays running 0.2.9.x may wish to update to one of
3274 the versions released today, for the DoS mitigations.
3276 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
3277 - Fix a protocol-list handling bug that could be used to remotely crash
3278 directory authorities with a null-pointer exception. Fixes bug 25074;
3279 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
3282 o Major features (denial-of-service mitigation):
3283 - Give relays some defenses against the recent network overload. We
3284 start with three defenses (default parameters in parentheses).
3285 First: if a single client address makes too many concurrent
3286 connections (>100), hang up on further connections. Second: if a
3287 single client address makes circuits too quickly (more than 3 per
3288 second, with an allowed burst of 90) while also having too many
3289 connections open (3), refuse new create cells for the next while
3290 (1-2 hours). Third: if a client asks to establish a rendezvous
3291 point to you directly, ignore the request. These defenses can be
3292 manually controlled by new torrc options, but relays will also
3293 take guidance from consensus parameters, so there's no need to
3294 configure anything manually. Implements ticket 24902.
3296 o Major bugfixes (bootstrapping):
3297 - Fetch descriptors aggressively whenever we lack enough to build
3298 circuits, regardless of how many descriptors we are missing.
3299 Previously, we would delay launching the fetch when we had fewer
3300 than 15 missing descriptors, even if some of those descriptors
3301 were blocking circuits from building. Fixes bug 23985; bugfix on
3302 0.1.1.11-alpha. The effects of this bug became worse in
3303 0.3.0.3-alpha, when we began treating missing descriptors from our
3304 primary guards as a reason to delay circuits.
3306 o Major bugfixes (onion services, retry behavior):
3307 - Fix an "off by 2" error in counting rendezvous failures on the
3308 onion service side. While we thought we would stop the rendezvous
3309 attempt after one failed circuit, we were actually making three
3310 circuit attempts before giving up. Now switch to a default of 2,
3311 and allow the consensus parameter "hs_service_max_rdv_failures" to
3312 override. Fixes bug 24895; bugfix on 0.0.6.
3314 o Minor feature (relay statistics):
3315 - Change relay bandwidth reporting stats interval from 4 hours to 24
3316 hours in order to reduce the efficiency of guard discovery
3317 attacks. Fixes ticket 23856.
3319 o Minor features (compatibility, OpenSSL):
3320 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3321 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3322 since they neither disabled TLS 1.3 nor enabled any of the
3323 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3324 Closes ticket 24978.
3326 o Minor features (denial-of-service avoidance):
3327 - Make our OOM handler aware of the geoip client history cache so it
3328 doesn't fill up the memory. This check is important for IPv6 and
3329 our DoS mitigation subsystem. Closes ticket 25122.
3331 o Minor features (fallback directory mirrors):
3332 - The fallback directory list has been re-generated based on the
3333 current status of the network. Tor uses fallback directories to
3334 bootstrap when it doesn't yet have up-to-date directory
3335 information. Closes ticket 24801.
3336 - Make the default DirAuthorityFallbackRate 0.1, so that clients
3337 prefer to bootstrap from fallback directory mirrors. This is a
3338 follow-up to 24679, which removed weights from the default
3339 fallbacks. Implements ticket 24681.
3341 o Minor features (geoip):
3342 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
3345 o Minor features (linux seccomp2 sandbox):
3346 - Update the sandbox rules so that they should now work correctly
3347 with Glibc 2.26. Closes ticket 24315.
3349 o Minor bugfix (channel connection):
3350 - Use the actual observed address of an incoming relay connection,
3351 not the canonical address of the relay from its descriptor, when
3352 making decisions about how to handle the incoming connection.
3353 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
3355 o Minor bugfix (directory authority):
3356 - Directory authorities, when refusing a descriptor from a rejected
3357 relay, now explicitly tell the relay (in its logs) to set a valid
3358 ContactInfo address and contact the bad-relays@ mailing list.
3359 Fixes bug 25170; bugfix on 0.2.9.1.
3361 o Minor bugfixes (address selection):
3362 - When the fascist_firewall_choose_address_ functions don't find a
3363 reachable address, set the returned address to the null address
3364 and port. This is a precautionary measure, because some callers do
3365 not check the return value. Fixes bug 24736; bugfix
3368 o Minor bugfixes (compilation):
3369 - Fix a signed/unsigned comparison warning introduced by our fix to
3370 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
3372 o Minor bugfixes (control port, linux seccomp2 sandbox):
3373 - Avoid a crash when attempting to use the seccomp2 sandbox together
3374 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
3377 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
3378 - Fix a possible crash on malformed consensus. If a consensus had
3379 contained an unparseable protocol line, it could have made clients
3380 and relays crash with a null-pointer exception. To exploit this
3381 issue, however, an attacker would need to be able to subvert the
3382 directory authority system. Fixes bug 25251; bugfix on
3383 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
3385 o Minor bugfixes (memory usage):
3386 - When queuing DESTROY cells on a channel, only queue the circuit-id
3387 and reason fields: not the entire 514-byte cell. This fix should
3388 help mitigate any bugs or attacks that fill up these queues, and
3389 free more RAM for other uses. Fixes bug 24666; bugfix
3392 o Minor bugfixes (network layer):
3393 - When closing a connection via close_connection_immediately(), we
3394 mark it as "not blocked on bandwidth", to prevent later calls from
3395 trying to unblock it, and give it permission to read. This fixes a
3396 backtrace warning that can happen on relays under various
3397 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
3399 o Minor bugfixes (OSX):
3400 - Don't exit the Tor process if setrlimit() fails to change the file
3401 limit (which can happen sometimes on some versions of OSX). Fixes
3402 bug 21074; bugfix on 0.0.9pre5.
3404 o Minor bugfixes (path selection):
3405 - When selecting relays by bandwidth, avoid a rounding error that
3406 could sometimes cause load to be imbalanced incorrectly.
3407 Previously, we would always round upwards; now, we round towards
3408 the nearest integer. This had the biggest effect when a relay's
3409 weight adjustments should have given it weight 0, but it got
3410 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
3411 - When calculating the fraction of nodes that have descriptors, and
3412 all nodes in the network have zero bandwidths, count the number of
3413 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
3414 - Actually log the total bandwidth in compute_weighted_bandwidths().
3415 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
3417 o Minor bugfixes (portability, msvc):
3418 - Fix a bug in the bit-counting parts of our timing-wheel code on
3419 MSVC. (Note that MSVC is still not a supported build platform, due
3420 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
3423 o Minor bugfixes (relay):
3424 - Make the internal channel_is_client() function look at what sort
3425 of connection handshake the other side used, rather than whether
3426 the other side ever sent a create_fast cell to us. Backports part
3427 of the fixes from bugs 22805 and 24898.
3429 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
3430 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
3432 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
3433 bugfix on 0.2.9.4-alpha.
3436 Changes in version 0.3.2.10 - 2018-03-03
3437 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
3438 backports a number of bugfixes, including important fixes for security
3441 It includes an important security fix for a remote crash attack
3442 against directory authorities, tracked as TROVE-2018-001.
3444 Additionally, it backports a fix for a bug whose severity we have
3445 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
3446 triggered in order to crash relays with a use-after-free pattern. As
3447 such, we are now tracking that bug as TROVE-2018-002 and
3448 CVE-2018-0491, and backporting it to earlier releases. This bug
3449 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
3452 This release also backports our new system for improved resistance to
3453 denial-of-service attacks against relays.
3455 This release also fixes several minor bugs and annoyances from
3458 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
3459 today, for the fix to TROVE-2018-002. Directory authorities should
3460 also upgrade. (Relays on earlier versions might want to update too for
3461 the DoS mitigations.)
3463 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
3464 - Fix a protocol-list handling bug that could be used to remotely crash
3465 directory authorities with a null-pointer exception. Fixes bug 25074;
3466 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
3469 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
3470 - Avoid adding the same channel twice in the KIST scheduler pending
3471 list, which could lead to remote denial-of-service use-after-free
3472 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
3474 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
3475 - Give relays some defenses against the recent network overload. We
3476 start with three defenses (default parameters in parentheses).
3477 First: if a single client address makes too many concurrent
3478 connections (>100), hang up on further connections. Second: if a
3479 single client address makes circuits too quickly (more than 3 per
3480 second, with an allowed burst of 90) while also having too many
3481 connections open (3), refuse new create cells for the next while
3482 (1-2 hours). Third: if a client asks to establish a rendezvous
3483 point to you directly, ignore the request. These defenses can be
3484 manually controlled by new torrc options, but relays will also
3485 take guidance from consensus parameters, so there's no need to
3486 configure anything manually. Implements ticket 24902.
3488 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
3489 - Fix an "off by 2" error in counting rendezvous failures on the
3490 onion service side. While we thought we would stop the rendezvous
3491 attempt after one failed circuit, we were actually making three
3492 circuit attempts before giving up. Now switch to a default of 2,
3493 and allow the consensus parameter "hs_service_max_rdv_failures" to
3494 override. Fixes bug 24895; bugfix on 0.0.6.
3495 - New-style (v3) onion services now obey the "max rendezvous circuit
3496 attempts" logic. Previously they would make as many rendezvous
3497 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
3498 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
3500 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
3501 - Add Link protocol version 5 to the supported protocols list. Fixes
3502 bug 25070; bugfix on 0.3.1.1-alpha.
3504 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
3505 - Fix a set of false positives where relays would consider
3506 connections to other relays as being client-only connections (and
3507 thus e.g. deserving different link padding schemes) if those
3508 relays fell out of the consensus briefly. Now we look only at the
3509 initial handshake and whether the connection authenticated as a
3510 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
3512 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
3513 - The scheduler subsystem was failing to promptly notice changes in
3514 consensus parameters, making it harder to switch schedulers
3515 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
3517 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
3518 - Make our OOM handler aware of the geoip client history cache so it
3519 doesn't fill up the memory. This check is important for IPv6 and
3520 our DoS mitigation subsystem. Closes ticket 25122.
3522 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
3523 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3524 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3525 since they neither disabled TLS 1.3 nor enabled any of the
3526 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3527 Closes ticket 24978.
3529 o Minor features (geoip):
3530 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
3533 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
3534 - When logging a failure to create an onion service's descriptor,
3535 also log what the problem with the descriptor was. Diagnostic
3538 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
3539 - Use the actual observed address of an incoming relay connection,
3540 not the canonical address of the relay from its descriptor, when
3541 making decisions about how to handle the incoming connection.
3542 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
3544 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
3545 - Fix a possible crash on malformed consensus. If a consensus had
3546 contained an unparseable protocol line, it could have made clients
3547 and relays crash with a null-pointer exception. To exploit this
3548 issue, however, an attacker would need to be able to subvert the
3549 directory authority system. Fixes bug 25251; bugfix on
3550 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
3552 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
3553 - Directory authorities, when refusing a descriptor from a rejected
3554 relay, now explicitly tell the relay (in its logs) to set a valid
3555 ContactInfo address and contact the bad-relays@ mailing list.
3556 Fixes bug 25170; bugfix on 0.2.9.1.
3558 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
3559 - When building with Rust on OSX, link against libresolv, to work
3560 around the issue at https://github.com/rust-lang/rust/issues/46797.
3561 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
3563 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
3564 - Remove a BUG() statement when a client fetches an onion descriptor
3565 that has a lower revision counter than the one in its cache. This
3566 can happen in normal circumstances due to HSDir desync. Fixes bug
3567 24976; bugfix on 0.3.2.1-alpha.
3569 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
3570 - Don't treat inability to store a cached consensus object as a bug:
3571 it can happen normally when we are out of disk space. Fixes bug
3572 24859; bugfix on 0.3.1.1-alpha.
3574 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
3575 - Improve the performance of our consensus-diff application code
3576 when Tor is built with the --enable-fragile-hardening option set.
3577 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
3579 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
3580 - Don't exit the Tor process if setrlimit() fails to change the file
3581 limit (which can happen sometimes on some versions of OSX). Fixes
3582 bug 21074; bugfix on 0.0.9pre5.
3584 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
3585 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
3587 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
3588 bugfix on 0.2.9.4-alpha.
3590 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
3591 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
3592 25005; bugfix on 0.3.2.7-rc.
3594 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
3595 - Look at the "HSRend" protocol version, not the "HSDir" protocol
3596 version, when deciding whether a consensus entry can support the
3597 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
3598 bugfix on 0.3.2.1-alpha.
3600 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
3601 - Update the "rust dependencies" submodule to be a project-level
3602 repository, rather than a user repository. Closes ticket 25323.
3604 o Documentation (backport from 0.3.3.1-alpha)
3605 - Document that operators who run more than one relay or bridge are
3606 expected to set MyFamily and ContactInfo correctly. Closes
3610 Changes in version 0.3.3.3-alpha - 2018-03-03
3611 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
3612 It includes an important security fix for a remote crash attack
3613 against directory authorities tracked as TROVE-2018-001.
3615 Additionally, with this release, we are upgrading the severity of a
3616 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
3617 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
3618 a use-after-free pattern. As such, we are now tracking that bug as
3619 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
3620 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
3622 This release also fixes several minor bugs and annoyances from
3625 Relays running 0.3.2.x should upgrade to one of the versions released
3626 today, for the fix to TROVE-2018-002. Directory authorities should
3627 also upgrade. (Relays on earlier versions might want to update too for
3628 the DoS mitigations.)
3630 o Major bugfixes (denial-of-service, directory authority):
3631 - Fix a protocol-list handling bug that could be used to remotely crash
3632 directory authorities with a null-pointer exception. Fixes bug 25074;
3633 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
3636 o Minor features (compatibility, OpenSSL):
3637 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3638 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3639 since they neither disabled TLS 1.3 nor enabled any of the
3640 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3641 Closes ticket 24978.
3643 o Minor features (logging):
3644 - Clarify the log messages produced when getrandom() or a related
3645 entropy-generation mechanism gives an error. Closes ticket 25120.
3647 o Minor features (testing):
3648 - Add a "make test-rust" target to run the rust tests only. Closes
3651 o Minor bugfixes (denial-of-service):
3652 - Fix a possible crash on malformed consensus. If a consensus had
3653 contained an unparseable protocol line, it could have made clients
3654 and relays crash with a null-pointer exception. To exploit this
3655 issue, however, an attacker would need to be able to subvert the
3656 directory authority system. Fixes bug 25251; bugfix on
3657 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
3659 o Minor bugfixes (DoS mitigation):
3660 - Add extra safety checks when refilling the circuit creation bucket
3661 to ensure we never set a value above the allowed maximum burst.
3662 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
3663 - When a new consensus arrives, don't update our DoS-mitigation
3664 parameters if we aren't a public relay. Fixes bug 25223; bugfix
3667 o Minor bugfixes (man page, SocksPort):
3668 - Remove dead code from the old "SocksSocket" option, and rename
3669 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
3670 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
3672 o Minor bugfixes (performance):
3673 - Reduce the number of circuits that will be opened at once during
3674 the circuit build timeout phase. This is done by increasing the
3675 idle timeout to 3 minutes, and lowering the maximum number of
3676 concurrent learning circuits to 10. Fixes bug 24769; bugfix
3679 o Minor bugfixes (spec conformance):
3680 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
3682 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
3683 bugfix on 0.2.9.4-alpha.
3685 o Minor bugfixes (spec conformance, rust):
3686 - Resolve a denial-of-service issue caused by an infinite loop in
3687 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
3688 Also tracked as TROVE-2018-003.
3690 o Code simplification and refactoring:
3691 - Update the "rust dependencies" submodule to be a project-level
3692 repository, rather than a user repository. Closes ticket 25323.
3695 Changes in version 0.3.3.2-alpha - 2018-02-10
3696 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
3697 introduces a mechanism to handle the high loads that many relay
3698 operators have been reporting recently. It also fixes several bugs in
3699 older releases. If this new code proves reliable, we plan to backport
3700 it to older supported release series.
3702 o Major features (denial-of-service mitigation):
3703 - Give relays some defenses against the recent network overload. We
3704 start with three defenses (default parameters in parentheses).
3705 First: if a single client address makes too many concurrent
3706 connections (>100), hang up on further connections. Second: if a
3707 single client address makes circuits too quickly (more than 3 per
3708 second, with an allowed burst of 90) while also having too many
3709 connections open (3), refuse new create cells for the next while
3710 (1-2 hours). Third: if a client asks to establish a rendezvous
3711 point to you directly, ignore the request. These defenses can be
3712 manually controlled by new torrc options, but relays will also
3713 take guidance from consensus parameters, so there's no need to
3714 configure anything manually. Implements ticket 24902.
3716 o Major bugfixes (netflow padding):
3717 - Stop adding unneeded channel padding right after we finish
3718 flushing to a connection that has been trying to flush for many
3719 seconds. Instead, treat all partial or complete flushes as
3720 activity on the channel, which will defer the time until we need
3721 to add padding. This fix should resolve confusing and scary log
3722 messages like "Channel padding timeout scheduled 221453ms in the
3723 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
3725 o Major bugfixes (protocol versions):
3726 - Add Link protocol version 5 to the supported protocols list. Fixes
3727 bug 25070; bugfix on 0.3.1.1-alpha.
3729 o Major bugfixes (scheduler, consensus):
3730 - The scheduler subsystem was failing to promptly notice changes in
3731 consensus parameters, making it harder to switch schedulers
3732 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
3734 o Minor features (denial-of-service avoidance):
3735 - Make our OOM handler aware of the geoip client history cache so it
3736 doesn't fill up the memory. This check is important for IPv6 and
3737 our DoS mitigation subsystem. Closes ticket 25122.
3739 o Minor features (directory authority):
3740 - When directory authorities are unable to add signatures to a
3741 pending consensus, log the reason why. Closes ticket 24849.
3743 o Minor features (geoip):
3744 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
3747 o Minor features (logging, diagnostic):
3748 - When logging a failure to create an onion service's descriptor,
3749 also log what the problem with the descriptor was. Diagnostic for
3752 o Minor bugfix (channel connection):
3753 - Use the actual observed address of an incoming relay connection,
3754 not the canonical address of the relay from its descriptor, when
3755 making decisions about how to handle the incoming connection.
3756 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
3758 o Minor bugfix (directory authority):
3759 - Directory authorities, when refusing a descriptor from a rejected
3760 relay, now explicitly tell the relay (in its logs) to set a valid
3761 ContactInfo address and contact the bad-relays@ mailing list.
3762 Fixes bug 25170; bugfix on 0.2.9.1.
3764 o Minor bugfixes (all versions of Tor):
3765 - Use the "misspell" tool to detect and fix typos throughout the
3766 source code. Fixes bug 23650; bugfix on various versions of Tor.
3767 Patch from Deepesh Pathak.
3769 o Minor bugfixes (circuit, cannibalization):
3770 - Don't cannibalize preemptively-built circuits if we no longer
3771 recognize their first hop. This situation can happen if our Guard
3772 relay went off the consensus after the circuit was created. Fixes
3773 bug 24469; bugfix on 0.0.6.
3775 o Minor bugfixes (correctness):
3776 - Remove a nonworking, unnecessary check to see whether a circuit
3777 hop's identity digest was set when the circuit failed. Fixes bug
3778 24927; bugfix on 0.2.4.4-alpha.
3780 o Minor bugfixes (logging):
3781 - Don't treat inability to store a cached consensus object as a bug:
3782 it can happen normally when we are out of disk space. Fixes bug
3783 24859; bugfix on 0.3.1.1-alpha.
3784 - Fix a (mostly harmless) race condition when invoking
3785 LOG_PROTOCOL_WARN message from a subthread while the torrc options
3786 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
3788 o Minor bugfixes (onion services):
3789 - Remove a BUG() statement when a client fetches an onion descriptor
3790 that has a lower revision counter than the one in its cache. This
3791 can happen in normal circumstances due to HSDir desync. Fixes bug
3792 24976; bugfix on 0.3.2.1-alpha.
3793 - If we are configured to offer a single onion service, don't log
3794 long-term established one hop rendezvous points in the heartbeat.
3795 Fixes bug 25116; bugfix on 0.2.9.6-rc.
3797 o Minor bugfixes (performance):
3798 - Avoid calling protocol_list_supports_protocol() from inside tight
3799 loops when running with cached routerinfo_t objects. Instead,
3800 summarize the relevant protocols as flags in the routerinfo_t, as
3801 we do for routerstatus_t objects. This change simplifies our code
3802 a little, and saves a large amount of short-term memory allocation
3803 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
3805 o Minor bugfixes (Rust FFI):
3806 - Fix a minor memory leak which would happen whenever the C code
3807 would call the Rust implementation of
3808 protover_get_supported_protocols(). This was due to the C version
3809 returning a static string, whereas the Rust version newly allocated
3810 a CString to pass across the FFI boundary. Consequently, the C
3811 code was not expecting to need to free() what it was given. Fixes
3812 bug 25127; bugfix on 0.3.2.1-alpha.
3814 o Minor bugfixes (scheduler, KIST):
3815 - Avoid adding the same channel twice in the KIST scheduler pending
3816 list, which would waste CPU cycles. Fixes bug 24700; bugfix
3819 o Minor bugfixes (unit test, monotonic time):
3820 - Increase a constant (1msec to 10msec) in the monotonic time test
3821 that makes sure the nsec/usec/msec times read are synchronized.
3822 This change was needed to accommodate slow systems like armel or
3823 when the clock_gettime() is not a VDSO on the running kernel.
3824 Fixes bug 25113; bugfix on 0.2.9.1.
3826 o Minor bugfixes (v3 onion services):
3827 - Look at the "HSRend" protocol version, not the "HSDir" protocol
3828 version, when deciding whether a consensus entry can support the
3829 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
3830 bugfix on 0.3.2.1-alpha.
3832 o Code simplification and refactoring:
3833 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
3835 - Remove a series of counters used to track circuit extend attempts
3836 and connection status but that in reality we aren't using for
3837 anything other than stats logged by a SIGUSR1 signal. Closes
3840 o Documentation (man page):
3841 - The HiddenServiceVersion torrc option accepts only one number:
3842 either version 2 or 3. Closes ticket 25026; bugfix
3846 Changes in version 0.3.3.1-alpha - 2018-01-25
3847 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
3848 several new features to Tor, including several improvements to
3849 bootstrapping, and support for an experimental "vanguards" feature to
3850 resist guard discovery attacks. This series also includes better
3851 support for applications that need to embed Tor or manage v3
3854 o Major features (embedding):
3855 - There is now a documented stable API for programs that need to
3856 embed Tor. See tor_api.h for full documentation and known bugs.
3857 Closes ticket 23684.
3858 - Tor now has support for restarting in the same process.
3859 Controllers that run Tor using the "tor_api.h" interface can now
3860 restart Tor after Tor has exited. This support is incomplete,
3861 however: we fixed crash bugs that prevented it from working at
3862 all, but many bugs probably remain, including a possibility of
3863 security issues. Implements ticket 24581.
3865 o Major features (IPv6, directory documents):
3866 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
3867 consensus. This information makes it easier for IPv6 clients to
3868 bootstrap and choose reachable entry guards. Implements ticket 23826.
3869 - Add consensus method 28, which removes IPv6 ORPorts from
3870 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
3871 are redundant in microdescs. This change will be used by Tor clients
3872 on 0.2.8.x and later. (That is to say, with all Tor clients that
3873 have IPv6 bootstrap and guard support.) Implements ticket 23828.
3874 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
3875 set by different numbers of authorities. Fixes 23870
3878 o Major features (onion service v3, control port):
3879 - The control port now supports commands and events for v3 onion
3880 services. It is now possible to create ephemeral v3 services using
3881 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
3882 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
3883 DEL_ONION) have been extended to support v3 onion services. Closes
3884 ticket 20699; implements proposal 284.
3886 o Major features (onion services):
3887 - Provide torrc options to pin the second and third hops of onion
3888 service circuits to a list of nodes. The option HSLayer2Guards
3889 pins the second hop, and the option HSLayer3Guards pins the third
3890 hop. These options are for use in conjunction with experiments
3891 with "vanguards" for preventing guard enumeration attacks. Closes
3894 o Major features (rust, portability, experimental):
3895 - Tor now ships with an optional implementation of one of its
3896 smaller modules (protover.c) in the Rust programming language. To
3897 try it out, install a Rust build environment, and configure Tor
3898 with "--enable-rust --enable-cargo-online-mode". This should not
3899 cause any user-visible changes, but should help us gain more
3900 experience with Rust, and plan future Rust integration work.
3901 Implementation by Chelsea Komlo. Closes ticket 22840.
3903 o Minor features (storage, configuration):
3904 - Users can store cached directory documents somewhere other than
3905 the DataDirectory by using the CacheDirectory option. Similarly,
3906 the storage location for relay's keys can be overridden with the
3907 KeyDirectory option. Closes ticket 22703.
3909 o Major features (v3 onion services, ipv6):
3910 - When v3 onion service clients send introduce cells, they now
3911 include the IPv6 address of the rendezvous point, if it has one.
3912 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
3913 in future Tor versions, IPv6-only v3 single onion services will be
3914 able to use IPv6 addresses to connect directly to the rendezvous
3915 point. Closes ticket 23577. Patch by Neel Chauhan.
3917 o Major bugfixes (onion services, retry behavior):
3918 - Fix an "off by 2" error in counting rendezvous failures on the
3919 onion service side. While we thought we would stop the rendezvous
3920 attempt after one failed circuit, we were actually making three
3921 circuit attempts before giving up. Now switch to a default of 2,
3922 and allow the consensus parameter "hs_service_max_rdv_failures" to
3923 override. Fixes bug 24895; bugfix on 0.0.6.
3924 - New-style (v3) onion services now obey the "max rendezvous circuit
3925 attempts" logic. Previously they would make as many rendezvous
3926 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
3927 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
3929 o Major bugfixes (relays):
3930 - Fix a set of false positives where relays would consider
3931 connections to other relays as being client-only connections (and
3932 thus e.g. deserving different link padding schemes) if those
3933 relays fell out of the consensus briefly. Now we look only at the
3934 initial handshake and whether the connection authenticated as a
3935 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
3937 o Minor feature (IPv6):
3938 - Make IPv6-only clients wait for microdescs for relays, even if we
3939 were previously using descriptors (or were using them as a bridge)
3940 and have a cached descriptor for them. Implements ticket 23827.
3941 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
3942 them, rather than waiting to download microdescriptors.
3943 Implements ticket 23827.
3945 o Minor features (cleanup):
3946 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
3947 when it stops. Closes ticket 23271.
3949 o Minor features (defensive programming):
3950 - Most of the functions in Tor that free objects have been replaced
3951 with macros that free the objects and set the corresponding
3952 pointers to NULL. This change should help prevent a large class of
3953 dangling pointer bugs. Closes ticket 24337.
3954 - Where possible, the tor_free() macro now only evaluates its input
3955 once. Part of ticket 24337.
3956 - Check that microdesc ed25519 ids are non-zero in
3957 node_get_ed25519_id() before returning them. Implements ticket
3958 24001, patch by "aruna1234".
3960 o Minor features (embedding):
3961 - Tor can now start with a preauthenticated control connection
3962 created by the process that launched it. This feature is meant for
3963 use by programs that want to launch and manage a Tor process
3964 without allowing other programs to manage it as well. For more
3965 information, see the __OwningControllerFD option documented in
3966 control-spec.txt. Closes ticket 23900.
3967 - On most errors that would cause Tor to exit, it now tries to
3968 return from the tor_main() function, rather than calling the
3969 system exit() function. Most users won't notice a difference here,
3970 but it should be significant for programs that run Tor inside
3971 a separate thread: they should now be able to survive Tor's exit
3972 conditions rather than having Tor shut down the entire process.
3973 Closes ticket 23848.
3974 - Applications that want to embed Tor can now tell Tor not to
3975 register any of its own POSIX signal handlers, using the
3976 __DisableSignalHandlers option. Closes ticket 24588.
3978 o Minor features (fallback directory list):
3979 - Avoid selecting fallbacks that change their IP addresses too
3980 often. Select more fallbacks by ignoring the Guard flag, and
3981 allowing lower cutoffs for the Running and V2Dir flags. Also allow
3982 a lower bandwidth, and a higher number of fallbacks per operator
3983 (5% of the list). Implements ticket 24785.
3984 - Update the fallback whitelist and blacklist based on opt-ins and
3985 relay changes. Closes tickets 22321, 24678, 22527, 24135,
3988 o Minor features (fallback directory mirror configuration):
3989 - Add a nickname to each fallback in a C comment. This makes it
3990 easier for operators to find their relays, and allows stem to use
3991 nicknames to identify fallbacks. Implements ticket 24600.
3992 - Add a type and version header to the fallback directory mirror
3993 file. Also add a delimiter to the end of each fallback entry. This
3994 helps external parsers like stem and Relay Search. Implements
3996 - Add an extrainfo cache flag for each fallback in a C comment. This
3997 allows stem to use fallbacks to fetch extra-info documents, rather
3998 than using authorities. Implements ticket 22759.
3999 - Add the generateFallbackDirLine.py script for automatically
4000 generating fallback directory mirror lines from relay fingerprints.
4001 No more typos! Add the lookupFallbackDirContact.py script for
4002 automatically looking up operator contact info from relay
4003 fingerprints. Implements ticket 24706, patch by teor and atagar.
4004 - Reject any fallback directory mirror that serves an expired
4005 consensus. Implements ticket 20942, patch by "minik".
4006 - Remove commas and equals signs from external string inputs to the
4007 fallback list. This avoids format confusion attacks. Implements
4009 - Remove the "weight=10" line from fallback directory mirror
4010 entries. Ticket 24681 will maintain the current fallback weights
4011 by changing Tor's default fallback weight to 10. Implements
4013 - Stop logging excessive information about fallback netblocks.
4014 Implements ticket 24791.
4016 o Minor features (forward-compatibility):
4017 - If a relay supports some link authentication protocol that we do
4018 not recognize, then include that relay's ed25519 key when telling
4019 other relays to extend to it. Previously, we treated future
4020 versions as if they were too old to support ed25519 link
4021 authentication. Closes ticket 20895.
4023 o Minor features (heartbeat):
4024 - Add onion service information to our heartbeat logs, displaying
4025 stats about the activity of configured onion services. Closes
4028 o Minor features (instrumentation, development):
4029 - Add the MainloopStats option to allow developers to get
4030 instrumentation information from the main event loop via the
4031 heartbeat messages. We hope to use this to improve Tor's behavior
4032 when it's trying to sleep. Closes ticket 24605.
4034 o Minor features (log messages):
4035 - Improve a warning message that happens when we fail to re-parse an
4036 old router because of an expired certificate. Closes ticket 20020.
4037 - Make the log more quantitative when we hit MaxMemInQueues
4038 threshold exposing some values. Closes ticket 24501.
4040 o Minor features (logging, android):
4041 - Added support for the Android logging subsystem. Closes
4044 o Minor features (performance):
4045 - Support predictive circuit building for onion service circuits
4046 with multiple layers of guards. Closes ticket 23101.
4047 - Use stdatomic.h where available, rather than mutexes, to implement
4048 atomic_counter_t. Closes ticket 23953.
4050 o Minor features (performance, 32-bit):
4051 - Improve performance on 32-bit systems by avoiding 64-bit division
4052 when calculating the timestamp in milliseconds for channel padding
4053 computations. Implements ticket 24613.
4054 - Improve performance on 32-bit systems by avoiding 64-bit division
4055 when timestamping cells and buffer chunks for OOM calculations.
4056 Implements ticket 24374.
4058 o Minor features (performance, OSX, iOS):
4059 - Use the mach_approximate_time() function (when available) to
4060 implement coarse monotonic time. Having a coarse time function
4061 should avoid a large number of system calls, and improve
4062 performance slightly, especially under load. Closes ticket 24427.
4064 o Minor features (performance, windows):
4065 - Improve performance on Windows Vista and Windows 7 by adjusting
4066 TCP send window size according to the recommendation from
4067 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
4070 o Major features (relay):
4071 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
4072 operator to use a more reasonable ("reduced") exit policy, rather
4073 than the default one. If you want to run an exit node without
4074 thinking too hard about which ports to allow, this one is for you.
4075 Closes ticket 13605. Patch from Neel Chauhan.
4077 o Minor features (testing, debugging, embedding):
4078 - For development purposes, Tor now has a mode in which it runs for
4079 a few seconds, then stops, and starts again without exiting the
4080 process. This mode is meant to help us debug various issues with
4081 ticket 23847. To use this feature, compile with
4082 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
4083 environment variable. This is expected to crash a lot, and is
4084 really meant for developers only. It will likely be removed in a
4085 future release. Implements ticket 24583.
4087 o Minor bugfix (network IPv6 test):
4088 - Tor's test scripts now check if "ping -6 ::1" works when the user
4089 runs "make test-network-all". Fixes bug 24677; bugfix on
4090 0.2.9.3-alpha. Patch by "ffmancera".
4092 o Minor bugfixes (build, rust):
4093 - Fix output of autoconf checks to display success messages for Rust
4094 dependencies and a suitable rustc compiler version. Fixes bug
4095 24612; bugfix on 0.3.1.3-alpha.
4096 - When building with Rust on OSX, link against libresolv, to work
4097 around the issue at https://github.com/rust-lang/rust/issues/46797.
4098 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
4099 - Don't pass the --quiet option to cargo: it seems to suppress some
4100 errors, which is not what we want to do when building. Fixes bug
4101 24518; bugfix on 0.3.1.7.
4102 - Build correctly when building from outside Tor's source tree with
4103 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
4106 o Minor bugfixes (directory authorities, IPv6):
4107 - When creating a routerstatus (vote) from a routerinfo (descriptor),
4108 set the IPv6 address to the unspecified IPv6 address, and
4109 explicitly initialize the port to zero. Fixes bug 24488; bugfix
4112 o Minor bugfixes (fallback directory mirrors):
4113 - Make updateFallbackDirs.py search harder for python. (Some OSs
4114 don't put it in /usr/bin.) Fixes bug 24708; bugfix
4117 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
4118 - When hibernating, close connections normally and allow them to
4119 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
4121 - Do not attempt to launch self-reachability tests when entering
4122 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
4123 - Resolve several bugs related to descriptor fetching on bridge
4124 clients with bandwidth accounting enabled. (This combination is
4125 not recommended!) Fixes a case of bug 12062; bugfix
4127 - When hibernating, do not attempt to launch DNS checks. Fixes a
4128 case of bug 12062; bugfix on 0.1.2.2-alpha.
4129 - When hibernating, do not try to upload or download descriptors.
4130 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
4132 o Minor bugfixes (IPv6, bridges):
4133 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
4134 bugfix on 0.2.8.2-alpha.
4135 - Tor now sets IPv6 address in the routerstatus as well as in the
4136 router descriptors when updating addresses for a bridge. Closes
4137 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
4139 o Minor bugfixes (linux seccomp2 sandbox):
4140 - When running with the sandbox enabled, reload configuration files
4141 correctly even when %include was used. Previously we would crash.
4142 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
4144 o Minor bugfixes (memory leaks):
4145 - Avoid possible at-exit memory leaks related to use of Libevent's
4146 event_base_once() function. (This function tends to leak memory if
4147 the event_base is closed before the event fires.) Fixes bug 24584;
4148 bugfix on 0.2.8.1-alpha.
4149 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
4152 o Minor bugfixes (OSX):
4153 - Don't exit the Tor process if setrlimit() fails to change the file
4154 limit (which can happen sometimes on some versions of OSX). Fixes
4155 bug 21074; bugfix on 0.0.9pre5.
4157 o Minor bugfixes (performance, fragile-hardening):
4158 - Improve the performance of our consensus-diff application code
4159 when Tor is built with the --enable-fragile-hardening option set.
4160 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4162 o Minor bugfixes (performance, timeouts):
4163 - Consider circuits for timeout as soon as they complete a hop. This
4164 is more accurate than applying the timeout in
4165 circuit_expire_building() because that function is only called
4166 once per second, which is now too slow for typical timeouts on the
4167 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
4168 - Use onion service circuits (and other circuits longer than 3 hops)
4169 to calculate a circuit build timeout. Previously, Tor only
4170 calculated its build timeout based on circuits that planned to be
4171 exactly 3 hops long. With this change, we include measurements
4172 from all circuits at the point where they complete their third
4173 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
4175 o Minor bugfixes (testing):
4176 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
4177 bugfix on 0.2.3.1-alpha.
4178 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
4179 25005; bugfix on 0.3.2.7-rc.
4181 o Code simplification and refactoring:
4182 - Remove /usr/athena from search path in configure.ac. Closes
4184 - Remove duplicate code in node_has_curve25519_onion_key() and
4185 node_get_curve25519_onion_key(), and add a check for a zero
4186 microdesc curve25519 onion key. Closes ticket 23966, patch by
4187 "aruna1234" and teor.
4188 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
4189 memory allocations with large numbers of OR connections (e.g.
4190 relays). Closes ticket 24119.
4191 - Separate the function that deletes ephemeral files when Tor
4193 - Small changes to Tor's buf_t API to make it suitable for use as a
4194 general-purpose safe string constructor. Closes ticket 22342.
4195 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
4196 avoid source code identifier confusion. Closes ticket 24467.
4197 - The tor_git_revision[] constant no longer needs to be redeclared
4198 by everything that links against the rest of Tor. Done as part of
4199 ticket 23845, to simplify our external API.
4200 - We make extend_info_from_node() use node_get_curve25519_onion_key()
4201 introduced in ticket 23577 to access the curve25519 public keys
4202 rather than accessing it directly. Closes ticket 23760. Patch by
4204 - Add a function to log channels' scheduler state changes to aid
4205 debugging efforts. Closes ticket 24531.
4208 - Add documentation on how to build tor with Rust dependencies
4209 without having to be online. Closes ticket 22907; bugfix
4211 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
4212 traffic. Closes ticket 24318.
4213 - Document that OutboundBindAddress doesn't apply to DNS requests.
4214 Closes ticket 22145. Patch from Aruna Maurya.
4215 - Document that operators who run more than one relay or bridge are
4216 expected to set MyFamily and ContactInfo correctly. Closes
4219 o Code simplification and refactoring (channels):
4220 - Remove the incoming and outgoing channel queues. These were never
4221 used, but still took up a step in our fast path.
4222 - The majority of the channel unit tests have been rewritten and the
4223 code coverage has now been raised to 83.6% for channel.c. Closes
4225 - Remove other dead code from the channel subsystem: All together,
4226 this cleanup has removed more than 1500 lines of code overall and
4227 adding very little except for unit test.
4229 o Code simplification and refactoring (circuit rendezvous):
4230 - Split the client-side rendezvous circuit lookup into two
4231 functions: one that returns only established circuits and another
4232 that returns all kinds of circuits. Closes ticket 23459.
4234 o Code simplification and refactoring (controller):
4235 - Make most of the variables in networkstatus_getinfo_by_purpose()
4236 const. Implements ticket 24489.
4239 Changes in version 0.3.2.9 - 2018-01-09
4240 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
4242 The 0.3.2 series includes our long-anticipated new onion service
4243 design, with numerous security features. (For more information, see
4244 our blog post at https://blog.torproject.org/fall-harvest.) We also
4245 have a new circuit scheduler algorithm for improved performance on
4246 relays everywhere (see https://blog.torproject.org/kist-and-tell),
4247 along with many smaller features and bugfixes.
4249 Per our stable release policy, we plan to support each stable release
4250 series for at least the next nine months, or for three months after
4251 the first stable release of the next series: whichever is longer. If
4252 you need a release with long-term support, we recommend that you stay
4253 with the 0.2.9 series.
4255 Below is a list of the changes since 0.3.2.8-rc. For a list of all
4256 changes since 0.3.1, see the ReleaseNotes file.
4258 o Minor features (fallback directory mirrors):
4259 - The fallback directory list has been re-generated based on the
4260 current status of the network. Tor uses fallback directories to
4261 bootstrap when it doesn't yet have up-to-date directory
4262 information. Closes ticket 24801.
4263 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4264 prefer to bootstrap from fallback directory mirrors. This is a
4265 follow-up to 24679, which removed weights from the default
4266 fallbacks. Implements ticket 24681.
4268 o Minor features (geoip):
4269 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
4272 o Minor bugfixes (address selection):
4273 - When the fascist_firewall_choose_address_ functions don't find a
4274 reachable address, set the returned address to the null address
4275 and port. This is a precautionary measure, because some callers do
4276 not check the return value. Fixes bug 24736; bugfix
4279 o Minor bugfixes (compilation):
4280 - Resolve a few shadowed-variable warnings in the onion service
4281 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
4283 o Minor bugfixes (portability, msvc):
4284 - Fix a bug in the bit-counting parts of our timing-wheel code on
4285 MSVC. (Note that MSVC is still not a supported build platform, due
4286 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
4290 Changes in version 0.3.2.8-rc - 2017-12-21
4291 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
4292 schedulers that had led servers under heavy load to overload their
4293 outgoing connections. All relay operators running earlier 0.3.2.x
4294 versions should upgrade. This version also includes a mitigation for
4295 over-full DESTROY queues leading to out-of-memory conditions: if it
4296 works, we will soon backport it to earlier release series.
4298 This is the second release candidate in the 0.3.2 series. If we find
4299 no new bugs or regression here, then the first stable 0.3.2 release
4300 will be nearly identical to this.
4302 o Major bugfixes (KIST, scheduler):
4303 - The KIST scheduler did not correctly account for data already
4304 enqueued in each connection's send socket buffer, particularly in
4305 cases when the TCP/IP congestion window was reduced between
4306 scheduler calls. This situation lead to excessive per-connection
4307 buffering in the kernel, and a potential memory DoS. Fixes bug
4308 24665; bugfix on 0.3.2.1-alpha.
4310 o Minor features (geoip):
4311 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
4314 o Minor bugfixes (hidden service v3):
4315 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
4316 the probability of reaching a service for a client missing
4317 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
4319 o Minor bugfixes (memory usage):
4320 - When queuing DESTROY cells on a channel, only queue the circuit-id
4321 and reason fields: not the entire 514-byte cell. This fix should
4322 help mitigate any bugs or attacks that fill up these queues, and
4323 free more RAM for other uses. Fixes bug 24666; bugfix
4326 o Minor bugfixes (scheduler, KIST):
4327 - Use a sane write limit for KISTLite when writing onto a connection
4328 buffer instead of using INT_MAX and shoving as much as it can.
4329 Because the OOM handler cleans up circuit queues, we are better
4330 off at keeping them in that queue instead of the connection's
4331 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
4334 Changes in version 0.3.2.7-rc - 2017-12-14
4335 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
4336 including some that could affect reliability or correctness.
4338 This is the first release candidate in the 0.3.2 series. If we find no
4339 new bugs or regression here, then the first stable 0.3.2. release will
4340 be nearly identical to this.
4342 o Major bugfixes (circuit prediction):
4343 - Fix circuit prediction logic so that a client doesn't treat a port
4344 as being "handled" by a circuit if that circuit already has
4345 isolation settings on it. This change should make Tor clients more
4346 responsive by improving their chances of having a pre-created
4347 circuit ready for use when a request arrives. Fixes bug 18859;
4348 bugfix on 0.2.3.3-alpha.
4350 o Minor features (logging):
4351 - Provide better warnings when the getrandom() syscall fails. Closes
4354 o Minor features (portability):
4355 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
4356 (It doesn't yet work with the sandbox enabled.) Closes
4359 o Minor bugfixes (bridge clients, bootstrap):
4360 - Retry directory downloads when we get our first bridge descriptor
4361 during bootstrap or while reconnecting to the network. Keep
4362 retrying every time we get a bridge descriptor, until we have a
4363 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
4364 - Stop delaying bridge descriptor fetches when we have cached bridge
4365 descriptors. Instead, only delay bridge descriptor fetches when we
4366 have at least one reachable bridge. Fixes part of bug 24367;
4367 bugfix on 0.2.0.3-alpha.
4368 - Stop delaying directory fetches when we have cached bridge
4369 descriptors. Instead, only delay bridge descriptor fetches when
4370 all our bridges are definitely unreachable. Fixes part of bug
4371 24367; bugfix on 0.2.0.3-alpha.
4373 o Minor bugfixes (compilation):
4374 - Fix a signed/unsigned comparison warning introduced by our fix to
4375 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4377 o Minor bugfixes (correctness):
4378 - Fix several places in our codebase where a C compiler would be
4379 likely to eliminate a check, based on assuming that undefined
4380 behavior had not happened elsewhere in the code. These cases are
4381 usually a sign of redundant checking or dubious arithmetic. Found
4382 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
4383 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
4386 o Minor bugfixes (onion service v3):
4387 - Fix a race where an onion service would launch a new intro circuit
4388 after closing an old one, but fail to register it before freeing
4389 the previously closed circuit. This bug was making the service
4390 unable to find the established intro circuit and thus not upload
4391 its descriptor, thus making a service unavailable for up to 24
4392 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
4394 o Minor bugfixes (scheduler, KIST):
4395 - Properly set the scheduler state of an unopened channel in the
4396 KIST scheduler main loop. This prevents a harmless but annoying
4397 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
4398 - Avoid a possible integer overflow when computing the available
4399 space on the TCP buffer of a channel. This had no security
4400 implications; but could make KIST allow too many cells on a
4401 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
4402 - Downgrade to "info" a harmless warning about the monotonic time
4403 moving backwards: This can happen on platform not supporting
4404 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
4407 Changes in version 0.3.2.6-alpha - 2017-12-01
4408 This version of Tor is the latest in the 0.3.2 alpha series. It
4409 includes fixes for several important security issues. All Tor users
4410 should upgrade to this release, or to one of the other releases coming
4413 o Major bugfixes (security):
4414 - Fix a denial of service bug where an attacker could use a
4415 malformed directory object to cause a Tor instance to pause while
4416 OpenSSL would try to read a passphrase from the terminal. (Tor
4417 instances run without a terminal, which is the case for most Tor
4418 packages, are not impacted.) Fixes bug 24246; bugfix on every
4419 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4420 Found by OSS-Fuzz as testcase 6360145429790720.
4421 - Fix a denial of service issue where an attacker could crash a
4422 directory authority using a malformed router descriptor. Fixes bug
4423 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
4425 - When checking for replays in the INTRODUCE1 cell data for a
4426 (legacy) onion service, correctly detect replays in the RSA-
4427 encrypted part of the cell. We were previously checking for
4428 replays on the entire cell, but those can be circumvented due to
4429 the malleability of Tor's legacy hybrid encryption. This fix helps
4430 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4431 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4434 o Major bugfixes (security, onion service v2):
4435 - Fix a use-after-free error that could crash v2 Tor onion services
4436 when they failed to open circuits while expiring introduction
4437 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4438 also tracked as TROVE-2017-013 and CVE-2017-8823.
4440 o Major bugfixes (security, relay):
4441 - When running as a relay, make sure that we never build a path
4442 through ourselves, even in the case where we have somehow lost the
4443 version of our descriptor appearing in the consensus. Fixes part
4444 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4445 as TROVE-2017-012 and CVE-2017-8822.
4446 - When running as a relay, make sure that we never choose ourselves
4447 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
4448 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
4450 o Minor feature (relay statistics):
4451 - Change relay bandwidth reporting stats interval from 4 hours to 24
4452 hours in order to reduce the efficiency of guard discovery
4453 attacks. Fixes ticket 23856.
4455 o Minor features (directory authority):
4456 - Add an IPv6 address for the "bastet" directory authority. Closes
4459 o Minor bugfixes (client):
4460 - By default, do not enable storage of client-side DNS values. These
4461 values were unused by default previously, but they should not have
4462 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
4465 Changes in version 0.3.1.9 - 2017-12-01:
4466 Tor 0.3.1.9 backports important security and stability fixes from the
4467 0.3.2 development series. All Tor users should upgrade to this
4468 release, or to another of the releases coming out today.
4470 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4471 - Fix a denial of service bug where an attacker could use a
4472 malformed directory object to cause a Tor instance to pause while
4473 OpenSSL would try to read a passphrase from the terminal. (Tor
4474 instances run without a terminal, which is the case for most Tor
4475 packages, are not impacted.) Fixes bug 24246; bugfix on every
4476 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4477 Found by OSS-Fuzz as testcase 6360145429790720.
4478 - Fix a denial of service issue where an attacker could crash a
4479 directory authority using a malformed router descriptor. Fixes bug
4480 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
4482 - When checking for replays in the INTRODUCE1 cell data for a
4483 (legacy) onion service, correctly detect replays in the RSA-
4484 encrypted part of the cell. We were previously checking for
4485 replays on the entire cell, but those can be circumvented due to
4486 the malleability of Tor's legacy hybrid encryption. This fix helps
4487 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4488 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4491 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
4492 - Fix a use-after-free error that could crash v2 Tor onion services
4493 when they failed to open circuits while expiring introduction
4494 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4495 also tracked as TROVE-2017-013 and CVE-2017-8823.
4497 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4498 - When running as a relay, make sure that we never build a path
4499 through ourselves, even in the case where we have somehow lost the
4500 version of our descriptor appearing in the consensus. Fixes part
4501 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4502 as TROVE-2017-012 and CVE-2017-8822.
4503 - When running as a relay, make sure that we never choose ourselves
4504 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
4505 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
4507 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
4508 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4509 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4510 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4511 identifying and finding a workaround to this bug and to Moritz,
4512 Arthur Edelstein, and Roger for helping to track it down and
4515 o Minor features (bridge):
4516 - Bridges now include notice in their descriptors that they are
4517 bridges, and notice of their distribution status, based on their
4518 publication settings. Implements ticket 18329. For more fine-
4519 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4522 o Minor features (directory authority, backport from 0.3.2.6-alpha):
4523 - Add an IPv6 address for the "bastet" directory authority. Closes
4526 o Minor features (geoip):
4527 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4530 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
4531 - Avoid unnecessary calls to directory_fetches_from_authorities() on
4532 relays, to prevent spurious address resolutions and descriptor
4533 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
4534 bugfix on in 0.2.8.1-alpha.
4536 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
4537 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
4538 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
4540 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
4541 - When a circuit is marked for close, do not attempt to package any
4542 cells for channels on that circuit. Previously, we would detect
4543 this condition lower in the call stack, when we noticed that the
4544 circuit had no attached channel, and log an annoying message.
4545 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4547 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
4548 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
4549 so it matches dir-spec.txt. Fixes bug 24262; bugfix
4552 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
4553 - Avoid a crash when transitioning from client mode to bridge mode.
4554 Previously, we would launch the worker threads whenever our
4555 "public server" mode changed, but not when our "server" mode
4556 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4559 Changes in version 0.3.0.13 - 2017-12-01
4560 Tor 0.3.0.13 backports important security and stability bugfixes from
4561 later Tor releases. All Tor users should upgrade to this release, or
4562 to another of the releases coming out today.
4564 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
4565 2018. If you need a release with long-term support, please stick with
4566 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4568 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4569 - Fix a denial of service bug where an attacker could use a
4570 malformed directory object to cause a Tor instance to pause while
4571 OpenSSL would try to read a passphrase from the terminal. (Tor
4572 instances run without a terminal, which is the case for most Tor
4573 packages, are not impacted.) Fixes bug 24246; bugfix on every
4574 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4575 Found by OSS-Fuzz as testcase 6360145429790720.
4576 - Fix a denial of service issue where an attacker could crash a
4577 directory authority using a malformed router descriptor. Fixes bug
4578 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
4580 - When checking for replays in the INTRODUCE1 cell data for a
4581 (legacy) onion service, correctly detect replays in the RSA-
4582 encrypted part of the cell. We were previously checking for
4583 replays on the entire cell, but those can be circumvented due to
4584 the malleability of Tor's legacy hybrid encryption. This fix helps
4585 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4586 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4589 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
4590 - Fix a use-after-free error that could crash v2 Tor onion services
4591 when they failed to open circuits while expiring introduction
4592 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4593 also tracked as TROVE-2017-013 and CVE-2017-8823.
4595 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4596 - When running as a relay, make sure that we never build a path
4597 through ourselves, even in the case where we have somehow lost the
4598 version of our descriptor appearing in the consensus. Fixes part
4599 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4600 as TROVE-2017-012 and CVE-2017-8822.
4601 - When running as a relay, make sure that we never choose ourselves
4602 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
4603 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
4605 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
4606 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4607 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4608 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4609 identifying and finding a workaround to this bug and to Moritz,
4610 Arthur Edelstein, and Roger for helping to track it down and
4613 o Minor features (security, windows, backport from 0.3.1.1-alpha):
4614 - Enable a couple of pieces of Windows hardening: one
4615 (HeapEnableTerminationOnCorruption) that has been on-by-default
4616 since Windows 8, and unavailable before Windows 7; and one
4617 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
4618 affect us, but shouldn't do any harm. Closes ticket 21953.
4620 o Minor features (bridge, backport from 0.3.1.9):
4621 - Bridges now include notice in their descriptors that they are
4622 bridges, and notice of their distribution status, based on their
4623 publication settings. Implements ticket 18329. For more fine-
4624 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4627 o Minor features (directory authority, backport from 0.3.2.6-alpha):
4628 - Add an IPv6 address for the "bastet" directory authority. Closes
4631 o Minor features (geoip):
4632 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4635 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
4636 - Avoid unnecessary calls to directory_fetches_from_authorities() on
4637 relays, to prevent spurious address resolutions and descriptor
4638 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
4639 bugfix on in 0.2.8.1-alpha.
4641 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
4642 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
4643 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
4645 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
4646 - When a circuit is marked for close, do not attempt to package any
4647 cells for channels on that circuit. Previously, we would detect
4648 this condition lower in the call stack, when we noticed that the
4649 circuit had no attached channel, and log an annoying message.
4650 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4652 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
4653 - Avoid a crash when transitioning from client mode to bridge mode.
4654 Previously, we would launch the worker threads whenever our
4655 "public server" mode changed, but not when our "server" mode
4656 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4658 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
4659 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4660 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4663 Changes in version 0.2.9.14 - 2017-12-01
4664 Tor 0.3.0.13 backports important security and stability bugfixes from
4665 later Tor releases. All Tor users should upgrade to this release, or
4666 to another of the releases coming out today.
4668 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
4669 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4670 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4671 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4672 identifying and finding a workaround to this bug and to Moritz,
4673 Arthur Edelstein, and Roger for helping to track it down and
4676 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4677 - Fix a denial of service bug where an attacker could use a
4678 malformed directory object to cause a Tor instance to pause while
4679 OpenSSL would try to read a passphrase from the terminal. (Tor
4680 instances run without a terminal, which is the case for most Tor
4681 packages, are not impacted.) Fixes bug 24246; bugfix on every
4682 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4683 Found by OSS-Fuzz as testcase 6360145429790720.
4684 - Fix a denial of service issue where an attacker could crash a
4685 directory authority using a malformed router descriptor. Fixes bug
4686 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
4688 - When checking for replays in the INTRODUCE1 cell data for a
4689 (legacy) onion service, correctly detect replays in the RSA-
4690 encrypted part of the cell. We were previously checking for
4691 replays on the entire cell, but those can be circumvented due to
4692 the malleability of Tor's legacy hybrid encryption. This fix helps
4693 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4694 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4697 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
4698 - Fix a use-after-free error that could crash v2 Tor onion services
4699 when they failed to open circuits while expiring introduction
4700 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4701 also tracked as TROVE-2017-013 and CVE-2017-8823.
4703 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4704 - When running as a relay, make sure that we never build a path
4705 through ourselves, even in the case where we have somehow lost the
4706 version of our descriptor appearing in the consensus. Fixes part
4707 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4708 as TROVE-2017-012 and CVE-2017-8822.
4710 o Minor features (bridge, backport from 0.3.1.9):
4711 - Bridges now include notice in their descriptors that they are
4712 bridges, and notice of their distribution status, based on their
4713 publication settings. Implements ticket 18329. For more fine-
4714 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4717 o Minor features (directory authority, backport from 0.3.2.6-alpha):
4718 - Add an IPv6 address for the "bastet" directory authority. Closes
4721 o Minor features (geoip):
4722 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4725 o Minor features (security, windows, backport from 0.3.1.1-alpha):
4726 - Enable a couple of pieces of Windows hardening: one
4727 (HeapEnableTerminationOnCorruption) that has been on-by-default
4728 since Windows 8, and unavailable before Windows 7; and one
4729 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
4730 affect us, but shouldn't do any harm. Closes ticket 21953.
4732 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
4733 - Avoid unnecessary calls to directory_fetches_from_authorities() on
4734 relays, to prevent spurious address resolutions and descriptor
4735 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
4736 bugfix on in 0.2.8.1-alpha.
4738 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
4739 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
4740 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
4742 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
4743 - When a circuit is marked for close, do not attempt to package any
4744 cells for channels on that circuit. Previously, we would detect
4745 this condition lower in the call stack, when we noticed that the
4746 circuit had no attached channel, and log an annoying message.
4747 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4749 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
4750 - Avoid a crash when transitioning from client mode to bridge mode.
4751 Previously, we would launch the worker threads whenever our
4752 "public server" mode changed, but not when our "server" mode
4753 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4755 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
4756 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4757 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4760 Changes in version 0.2.8.17 - 2017-12-01
4761 Tor 0.2.8.17 backports important security and stability bugfixes from
4762 later Tor releases. All Tor users should upgrade to this release, or
4763 to another of the releases coming out today.
4765 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
4766 2018. If you need a release with long-term support, please upgrade with
4767 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4769 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4770 - Fix a denial of service bug where an attacker could use a
4771 malformed directory object to cause a Tor instance to pause while
4772 OpenSSL would try to read a passphrase from the terminal. (Tor
4773 instances run without a terminal, which is the case for most Tor
4774 packages, are not impacted.) Fixes bug 24246; bugfix on every
4775 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4776 Found by OSS-Fuzz as testcase 6360145429790720.
4777 - When checking for replays in the INTRODUCE1 cell data for a
4778 (legacy) onion service, correctly detect replays in the RSA-
4779 encrypted part of the cell. We were previously checking for
4780 replays on the entire cell, but those can be circumvented due to
4781 the malleability of Tor's legacy hybrid encryption. This fix helps
4782 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4783 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4786 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
4787 - Fix a use-after-free error that could crash v2 Tor onion services
4788 when they failed to open circuits while expiring introduction
4789 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4790 also tracked as TROVE-2017-013 and CVE-2017-8823.
4792 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4793 - When running as a relay, make sure that we never build a path through
4794 ourselves, even in the case where we have somehow lost the version of
4795 our descriptor appearing in the consensus. Fixes part of bug 21534;
4796 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
4799 o Minor features (bridge, backport from 0.3.1.9):
4800 - Bridges now include notice in their descriptors that they are
4801 bridges, and notice of their distribution status, based on their
4802 publication settings. Implements ticket 18329. For more fine-
4803 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4806 o Minor features (directory authority, backport from 0.3.2.6-alpha):
4807 - Add an IPv6 address for the "bastet" directory authority. Closes
4810 o Minor features (geoip):
4811 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4814 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
4815 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4816 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4819 Changes in version 0.2.5.16 - 2017-12-01
4820 Tor 0.2.5.13 backports important security and stability bugfixes from
4821 later Tor releases. All Tor users should upgrade to this release, or
4822 to another of the releases coming out today.
4824 Note: the Tor 0.2.5 series will no longer be supported after 1 May
4825 2018. If you need a release with long-term support, please upgrade to
4826 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4828 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4829 - Fix a denial of service bug where an attacker could use a
4830 malformed directory object to cause a Tor instance to pause while
4831 OpenSSL would try to read a passphrase from the terminal. (Tor
4832 instances run without a terminal, which is the case for most Tor
4833 packages, are not impacted.) Fixes bug 24246; bugfix on every
4834 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4835 Found by OSS-Fuzz as testcase 6360145429790720.
4836 - When checking for replays in the INTRODUCE1 cell data for a
4837 (legacy) onion service, correctly detect replays in the RSA-
4838 encrypted part of the cell. We were previously checking for
4839 replays on the entire cell, but those can be circumvented due to
4840 the malleability of Tor's legacy hybrid encryption. This fix helps
4841 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4842 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4845 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4846 - When running as a relay, make sure that we never build a path
4847 through ourselves, even in the case where we have somehow lost the
4848 version of our descriptor appearing in the consensus. Fixes part
4849 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4850 as TROVE-2017-012 and CVE-2017-8822.
4852 o Minor features (bridge, backport from 0.3.1.9):
4853 - Bridges now include notice in their descriptors that they are
4854 bridges, and notice of their distribution status, based on their
4855 publication settings. Implements ticket 18329. For more fine-
4856 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4859 o Minor features (geoip):
4860 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4864 Changes in version 0.3.2.5-alpha - 2017-11-22
4865 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
4866 fixes several stability and reliability bugs, including a fix for
4867 intermittent bootstrapping failures that some people have been seeing
4868 since the 0.3.0.x series.
4870 Please test this alpha out -- many of these fixes will soon be
4871 backported to stable Tor versions if no additional bugs are found
4874 o Major bugfixes (bootstrapping):
4875 - Fetch descriptors aggressively whenever we lack enough to build
4876 circuits, regardless of how many descriptors we are missing.
4877 Previously, we would delay launching the fetch when we had fewer
4878 than 15 missing descriptors, even if some of those descriptors
4879 were blocking circuits from building. Fixes bug 23985; bugfix on
4880 0.1.1.11-alpha. The effects of this bug became worse in
4881 0.3.0.3-alpha, when we began treating missing descriptors from our
4882 primary guards as a reason to delay circuits.
4883 - Don't try fetching microdescriptors from relays that have failed
4884 to deliver them in the past. Fixes bug 23817; bugfix
4887 o Minor features (directory authority):
4888 - Make the "Exit" flag assignment only depend on whether the exit
4889 policy allows connections to ports 80 and 443. Previously relays
4890 would get the Exit flag if they allowed connections to one of
4891 these ports and also port 6667. Resolves ticket 23637.
4893 o Minor features (geoip):
4894 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4897 o Minor features (linux seccomp2 sandbox):
4898 - Update the sandbox rules so that they should now work correctly
4899 with Glibc 2.26. Closes ticket 24315.
4901 o Minor features (logging):
4902 - Downgrade a pair of log messages that could occur when an exit's
4903 resolver gave us an unusual (but not forbidden) response. Closes
4905 - Improve the message we log when re-enabling circuit build timeouts
4906 after having received a consensus. Closes ticket 20963.
4908 o Minor bugfixes (compilation):
4909 - Fix a memory leak warning in one of the libevent-related
4910 configuration tests that could occur when manually specifying
4911 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
4912 Found and patched by Alex Xu.
4913 - When detecting OpenSSL on Windows from our configure script, make
4914 sure to try linking with the ws2_32 library. Fixes bug 23783;
4915 bugfix on 0.3.2.2-alpha.
4917 o Minor bugfixes (control port, linux seccomp2 sandbox):
4918 - Avoid a crash when attempting to use the seccomp2 sandbox together
4919 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4922 o Minor bugfixes (control port, onion services):
4923 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
4924 HS_DESC event when a service is not able to upload a descriptor.
4925 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
4927 o Minor bugfixes (directory cache):
4928 - Recover better from empty or corrupt files in the consensus cache
4929 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4930 - When a consensus diff calculation is only partially successful,
4931 only record the successful parts as having succeeded. Partial
4932 success can happen if (for example) one compression method fails
4933 but the others succeed. Previously we misrecorded all the
4934 calculations as having succeeded, which would later cause a
4935 nonfatal assertion failure. Fixes bug 24086; bugfix
4938 o Minor bugfixes (logging):
4939 - Only log once if we notice that KIST support is gone. Fixes bug
4940 24158; bugfix on 0.3.2.1-alpha.
4941 - Suppress a log notice when relay descriptors arrive. We already
4942 have a bootstrap progress for this so no need to log notice
4943 everytime tor receives relay descriptors. Microdescriptors behave
4944 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
4946 o Minor bugfixes (network layer):
4947 - When closing a connection via close_connection_immediately(), we
4948 mark it as "not blocked on bandwidth", to prevent later calls from
4949 trying to unblock it, and give it permission to read. This fixes a
4950 backtrace warning that can happen on relays under various
4951 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4953 o Minor bugfixes (onion services):
4954 - The introduction circuit was being timed out too quickly while
4955 waiting for the rendezvous circuit to complete. Keep the intro
4956 circuit around longer instead of timing out and reopening new ones
4957 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
4958 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
4959 so it matches dir-spec.txt. Fixes bug 24262; bugfix
4961 - Silence a warning about failed v3 onion descriptor uploads that
4962 can happen naturally under certain edge cases. Fixes part of bug
4963 23662; bugfix on 0.3.2.1-alpha.
4965 o Minor bugfixes (tests):
4966 - Fix a memory leak in one of the bridge-distribution test cases.
4967 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
4968 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
4969 to correctly handle cases where a caller gives it an RSA key of
4970 under 160 bits. (This is not actually a bug in Tor itself, but
4971 rather in our fuzzing code.) Fixes bug 24247; bugfix on
4972 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
4975 - Add notes in man page regarding OS support for the various
4976 scheduler types. Attempt to use less jargon in the scheduler
4977 section. Closes ticket 24254.
4980 Changes in version 0.3.2.4-alpha - 2017-11-08
4981 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
4982 It fixes several stability and reliability bugs, especially including
4983 a major reliability issue that has been plaguing fast exit relays in
4986 o Major bugfixes (exit relays, DNS):
4987 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4988 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4989 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4990 identifying and finding a workaround to this bug and to Moritz,
4991 Arthur Edelstein, and Roger for helping to track it down and
4994 o Major bugfixes (scheduler, channel):
4995 - Stop processing scheduled channels if they closed while flushing
4996 cells. This can happen if the write on the connection fails
4997 leading to the channel being closed while in the scheduler loop.
4998 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
5000 o Minor features (logging, scheduler):
5001 - Introduce a SCHED_BUG() function to log extra information about
5002 the scheduler state if we ever catch a bug in the scheduler.
5003 Closes ticket 23753.
5005 o Minor features (removed deprecations):
5006 - The ClientDNSRejectInternalAddresses flag can once again be set in
5007 non-testing Tor networks, so long as they do not use the default
5008 directory authorities. This change also removes the deprecation of
5009 this flag from 0.2.9.2-alpha. Closes ticket 21031.
5011 o Minor features (testing):
5012 - Our fuzzing tests now test the encrypted portions of v3 onion
5013 service descriptors. Implements more of 21509.
5015 o Minor bugfixes (directory client):
5016 - On failure to download directory information, delay retry attempts
5017 by a random amount based on the "decorrelated jitter" algorithm.
5018 Our previous delay algorithm tended to produce extra-long delays
5019 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
5021 o Minor bugfixes (IPv6, v3 single onion services):
5022 - Remove buggy code for IPv6-only v3 single onion services, and
5023 reject attempts to configure them. This release supports IPv4,
5024 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
5025 stack v3 single onion services. Fixes bug 23820; bugfix
5028 o Minor bugfixes (logging, relay):
5029 - Give only a protocol warning when the ed25519 key is not
5030 consistent between the descriptor and microdescriptor of a relay.
5031 This can happen, for instance, if the relay has been flagged
5032 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
5034 o Minor bugfixes (manpage, onion service):
5035 - Document that the HiddenServiceNumIntroductionPoints option is
5036 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
5037 bugfix on 0.3.2.1-alpha.
5039 o Minor bugfixes (memory leaks):
5040 - Fix a minor memory leak at exit in the KIST scheduler. This bug
5041 should have no user-visible impact. Fixes bug 23774; bugfix
5043 - Fix a memory leak when decrypting a badly formatted v3 onion
5044 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
5045 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
5047 o Minor bugfixes (onion services):
5048 - Cache some needed onion service client information instead of
5049 constantly computing it over and over again. Fixes bug 23623;
5050 bugfix on 0.3.2.1-alpha.
5051 - Properly retry HSv3 descriptor fetches when missing required
5052 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
5054 o Minor bugfixes (path selection):
5055 - When selecting relays by bandwidth, avoid a rounding error that
5056 could sometimes cause load to be imbalanced incorrectly.
5057 Previously, we would always round upwards; now, we round towards
5058 the nearest integer. This had the biggest effect when a relay's
5059 weight adjustments should have given it weight 0, but it got
5060 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5061 - When calculating the fraction of nodes that have descriptors, and
5062 all nodes in the network have zero bandwidths, count the number of
5063 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5064 - Actually log the total bandwidth in compute_weighted_bandwidths().
5065 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5067 o Minor bugfixes (relay, crash):
5068 - Avoid a crash when transitioning from client mode to bridge mode.
5069 Previously, we would launch the worker threads whenever our
5070 "public server" mode changed, but not when our "server" mode
5071 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5073 o Minor bugfixes (testing):
5074 - Fix a spurious fuzzing-only use of an uninitialized value. Found
5075 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
5076 - Test that IPv6-only clients can use microdescriptors when running
5077 "make test-network-all". Requires chutney master 61c28b9 or later.
5078 Closes ticket 24109.
5081 Changes in version 0.3.2.3-alpha - 2017-10-27
5082 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
5083 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
5084 directory authority, Bastet.
5086 o Directory authority changes:
5087 - Add "Bastet" as a ninth directory authority to the default list.
5088 Closes ticket 23910.
5089 - The directory authority "Longclaw" has changed its IP address.
5090 Closes ticket 23592.
5092 o Minor features (bridge):
5093 - Bridge relays can now set the BridgeDistribution config option to
5094 add a "bridge-distribution-request" line to their bridge
5095 descriptor, which tells BridgeDB how they'd like their bridge
5096 address to be given out. (Note that as of Oct 2017, BridgeDB does
5097 not yet implement this feature.) As a side benefit, this feature
5098 provides a way to distinguish bridge descriptors from non-bridge
5099 descriptors. Implements tickets 18329.
5101 o Minor features (client, entry guards):
5102 - Improve log messages when missing descriptors for primary guards.
5103 Resolves ticket 23670.
5105 o Minor features (geoip):
5106 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5109 o Minor bugfixes (bridge):
5110 - Overwrite the bridge address earlier in the process of retrieving
5111 its descriptor, to make sure we reach it on the configured
5112 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
5114 o Minor bugfixes (documentation):
5115 - Document better how to read gcov, and what our gcov postprocessing
5116 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
5118 o Minor bugfixes (entry guards):
5119 - Tor now updates its guard state when it reads a consensus
5120 regardless of whether it's missing descriptors. That makes tor use
5121 its primary guards to fetch descriptors in some edge cases where
5122 it would previously have used fallback directories. Fixes bug
5123 23862; bugfix on 0.3.0.1-alpha.
5125 o Minor bugfixes (hidden service client):
5126 - When handling multiple SOCKS request for the same .onion address,
5127 only fetch the service descriptor once.
5128 - When a descriptor fetch fails with a non-recoverable error, close
5129 all pending SOCKS requests for that .onion. Fixes bug 23653;
5130 bugfix on 0.3.2.1-alpha.
5132 o Minor bugfixes (hidden service):
5133 - Always regenerate missing hidden service public key files. Prior
5134 to this, if the public key was deleted from disk, it wouldn't get
5135 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
5137 - Make sure that we have a usable ed25519 key when the intro point
5138 relay supports ed25519 link authentication. Fixes bug 24002;
5139 bugfix on 0.3.2.1-alpha.
5141 o Minor bugfixes (hidden service, v2):
5142 - When reloading configured hidden services, copy all information
5143 from the old service object. Previously, some data was omitted,
5144 causing delays in descriptor upload, and other bugs. Fixes bug
5145 23790; bugfix on 0.2.1.9-alpha.
5147 o Minor bugfixes (memory safety, defensive programming):
5148 - Clear the target address when node_get_prim_orport() returns
5149 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
5151 o Minor bugfixes (relay):
5152 - Avoid a BUG warning when receiving a dubious CREATE cell while an
5153 option transition is in progress. Fixes bug 23952; bugfix
5156 o Minor bugfixes (testing):
5157 - Adjust the GitLab CI configuration to more closely match that of
5158 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
5159 - Prevent scripts/test/coverage from attempting to move gcov output
5160 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
5161 - When running unit tests as root, skip a test that would fail
5162 because it expects a permissions error. This affects some
5163 continuous integration setups. Fixes bug 23758; bugfix
5165 - Stop unconditionally mirroring the tor repository in GitLab CI.
5166 This prevented developers from enabling GitLab CI on master. Fixes
5167 bug 23755; bugfix on 0.3.2.2-alpha.
5168 - Fix the hidden service v3 descriptor decoding fuzzing to use the
5169 latest decoding API correctly. Fixes bug 21509; bugfix
5172 o Minor bugfixes (warnings):
5173 - When we get an HTTP request on a SOCKS port, tell the user about
5174 the new HTTPTunnelPort option. Previously, we would give a "Tor is
5175 not an HTTP Proxy" message, which stopped being true when
5176 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
5180 Changes in version 0.2.5.15 - 2017-10-25
5181 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
5182 series. It also adds a new directory authority, Bastet.
5184 Note: the Tor 0.2.5 series will no longer be supported after 1 May
5185 2018. If you need a release with long-term support, please upgrade to
5186 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5188 o Directory authority changes:
5189 - Add "Bastet" as a ninth directory authority to the default list.
5190 Closes ticket 23910.
5191 - The directory authority "Longclaw" has changed its IP address.
5192 Closes ticket 23592.
5194 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5195 - Avoid an assertion failure bug affecting our implementation of
5196 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5197 handling of "0xx" differs from what we had expected. Fixes bug
5198 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5200 o Minor features (geoip):
5201 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5204 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
5205 - Fix a memset() off the end of an array when packing cells. This
5206 bug should be harmless in practice, since the corrupted bytes are
5207 still in the same structure, and are always padding bytes,
5208 ignored, or immediately overwritten, depending on compiler
5209 behavior. Nevertheless, because the memset()'s purpose is to make
5210 sure that any other cell-handling bugs can't expose bytes to the
5211 network, we need to fix it. Fixes bug 22737; bugfix on
5212 0.2.4.11-alpha. Fixes CID 1401591.
5214 o Build features (backport from 0.3.1.5-alpha):
5215 - Tor's repository now includes a Travis Continuous Integration (CI)
5216 configuration file (.travis.yml). This is meant to help new
5217 developers and contributors who fork Tor to a Github repository be
5218 better able to test their changes, and understand what we expect
5219 to pass. To use this new build feature, you must fork Tor to your
5220 Github account, then go into the "Integrations" menu in the
5221 repository settings for your fork and enable Travis, then push
5222 your changes. Closes ticket 22636.
5225 Changes in version 0.2.8.16 - 2017-10-25
5226 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
5227 series, including a bugfix for a crash issue that had affected relays
5228 under memory pressure. It also adds a new directory authority, Bastet.
5230 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
5231 2018. If you need a release with long-term support, please stick with
5232 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5234 o Directory authority changes:
5235 - Add "Bastet" as a ninth directory authority to the default list.
5236 Closes ticket 23910.
5237 - The directory authority "Longclaw" has changed its IP address.
5238 Closes ticket 23592.
5240 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
5241 - Fix a timing-based assertion failure that could occur when the
5242 circuit out-of-memory handler freed a connection's output buffer.
5243 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5245 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
5246 - Remove longclaw's IPv6 address, as it will soon change. Authority
5247 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5248 3/8 directory authorities with IPv6 addresses, but there are also
5249 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5251 o Minor features (geoip):
5252 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5256 Changes in version 0.2.9.13 - 2017-10-25
5257 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
5258 series, including a bugfix for a crash issue that had affected relays
5259 under memory pressure. It also adds a new directory authority, Bastet.
5261 o Directory authority changes:
5262 - Add "Bastet" as a ninth directory authority to the default list.
5263 Closes ticket 23910.
5264 - The directory authority "Longclaw" has changed its IP address.
5265 Closes ticket 23592.
5267 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
5268 - Fix a timing-based assertion failure that could occur when the
5269 circuit out-of-memory handler freed a connection's output buffer.
5270 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5272 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
5273 - Remove longclaw's IPv6 address, as it will soon change. Authority
5274 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5275 3/8 directory authorities with IPv6 addresses, but there are also
5276 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5278 o Minor features (geoip):
5279 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5282 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
5283 - When a directory authority rejects a descriptor or extrainfo with
5284 a given digest, mark that digest as undownloadable, so that we do
5285 not attempt to download it again over and over. We previously
5286 tried to avoid downloading such descriptors by other means, but we
5287 didn't notice if we accidentally downloaded one anyway. This
5288 behavior became problematic in 0.2.7.2-alpha, when authorities
5289 began pinning Ed25519 keys. Fixes bug 22349; bugfix
5292 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
5293 - Clear the address when node_get_prim_orport() returns early.
5294 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
5296 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
5297 - When running as a Windows service, set the ID of the main thread
5298 correctly. Failure to do so made us fail to send log messages to
5299 the controller in 0.2.1.16-rc, slowed down controller event
5300 delivery in 0.2.7.3-rc and later, and crash with an assertion
5301 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
5302 Patch and diagnosis from "Vort".
5305 Changes in version 0.3.0.12 - 2017-10-25
5306 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
5307 series, including a bugfix for a crash issue that had affected relays
5308 under memory pressure. It also adds a new directory authority, Bastet.
5310 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
5311 2018. If you need a release with long-term support, please stick with
5312 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5314 o Directory authority changes:
5315 - Add "Bastet" as a ninth directory authority to the default list.
5316 Closes ticket 23910.
5317 - The directory authority "Longclaw" has changed its IP address.
5318 Closes ticket 23592.
5320 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
5321 - Fix a timing-based assertion failure that could occur when the
5322 circuit out-of-memory handler freed a connection's output buffer.
5323 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5325 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
5326 - Remove longclaw's IPv6 address, as it will soon change. Authority
5327 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5328 3/8 directory authorities with IPv6 addresses, but there are also
5329 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5331 o Minor features (geoip):
5332 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5335 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
5336 - When a directory authority rejects a descriptor or extrainfo with
5337 a given digest, mark that digest as undownloadable, so that we do
5338 not attempt to download it again over and over. We previously
5339 tried to avoid downloading such descriptors by other means, but we
5340 didn't notice if we accidentally downloaded one anyway. This
5341 behavior became problematic in 0.2.7.2-alpha, when authorities
5342 began pinning Ed25519 keys. Fixes bug 22349; bugfix
5345 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
5346 - Avoid a possible double close of a circuit by the intro point on
5347 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
5348 bugfix on 0.3.0.1-alpha.
5350 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
5351 - Clear the address when node_get_prim_orport() returns early.
5352 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
5354 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
5355 - When running as a Windows service, set the ID of the main thread
5356 correctly. Failure to do so made us fail to send log messages to
5357 the controller in 0.2.1.16-rc, slowed down controller event
5358 delivery in 0.2.7.3-rc and later, and crash with an assertion
5359 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
5360 Patch and diagnosis from "Vort".
5363 Changes in version 0.3.1.8 - 2017-10-25
5364 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
5365 It includes several bugfixes, including a bugfix for a crash issue
5366 that had affected relays under memory pressure. It also adds
5367 a new directory authority, Bastet.
5369 o Directory authority changes:
5370 - Add "Bastet" as a ninth directory authority to the default list.
5371 Closes ticket 23910.
5372 - The directory authority "Longclaw" has changed its IP address.
5373 Closes ticket 23592.
5375 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
5376 - Fix a timing-based assertion failure that could occur when the
5377 circuit out-of-memory handler freed a connection's output buffer.
5378 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5380 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
5381 - Remove longclaw's IPv6 address, as it will soon change. Authority
5382 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5383 3/8 directory authorities with IPv6 addresses, but there are also
5384 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5386 o Minor features (geoip):
5387 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5390 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
5391 - Fix a compilation warning when building with zstd support on
5392 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
5393 and fixed by Andreas Stieger.
5395 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
5396 - Handle a pathological case when decompressing Zstandard data when
5397 the output buffer size is zero. Fixes bug 23551; bugfix
5400 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
5401 - Remove the length limit on HTTP status lines that authorities can
5402 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
5404 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
5405 - Avoid a possible double close of a circuit by the intro point on
5406 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
5407 bugfix on 0.3.0.1-alpha.
5409 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
5410 - Clear the address when node_get_prim_orport() returns early.
5411 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
5413 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
5414 - Fix additional channelpadding unit test failures by using mocked
5415 time instead of actual time for all tests. Fixes bug 23608; bugfix
5419 Changes in version 0.3.2.2-alpha - 2017-09-29
5420 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
5421 release fixes several minor bugs in the new scheduler and next-
5422 generation onion services; both features were newly added in the 0.3.2
5423 series. Other fixes in this alpha include several fixes for non-fatal
5424 tracebacks which would appear in logs.
5426 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
5427 alpha does not contain any substantial new features. Minor features
5428 include better testing and logging.
5430 The following comprises the complete list of changes included
5433 o Major bugfixes (relay, crash, assertion failure):
5434 - Fix a timing-based assertion failure that could occur when the
5435 circuit out-of-memory handler freed a connection's output buffer.
5436 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5438 o Major bugfixes (scheduler):
5439 - If a channel is put into the scheduler's pending list, then it
5440 starts closing, and then if the scheduler runs before it finishes
5441 closing, the scheduler will get stuck trying to flush its cells
5442 while the lower layers refuse to cooperate. Fix that race
5443 condition by giving the scheduler an escape method. Fixes bug
5444 23676; bugfix on 0.3.2.1-alpha.
5446 o Minor features (build, compilation):
5447 - The "check-changes" feature is now part of the "make check" tests;
5448 we'll use it to try to prevent misformed changes files from
5449 accumulating. Closes ticket 23564.
5450 - Tor builds should now fail if there are any mismatches between the
5451 C type representing a configuration variable and the C type the
5452 data-driven parser uses to store a value there. Previously, we
5453 needed to check these by hand, which sometimes led to mistakes.
5454 Closes ticket 23643.
5456 o Minor features (directory authorities):
5457 - Remove longclaw's IPv6 address, as it will soon change. Authority
5458 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5459 3/8 directory authorities with IPv6 addresses, but there are also
5460 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5462 o Minor features (hidden service, circuit, logging):
5463 - Improve logging of many callsite in the circuit subsystem to print
5464 the circuit identifier(s).
5465 - Log when we cleanup an intro point from a service so we know when
5466 and for what reason it happened. Closes ticket 23604.
5468 o Minor features (logging):
5469 - Log more circuit information whenever we are about to try to
5470 package a relay cell on a circuit with a nonexistent n_chan.
5471 Attempt to diagnose ticket 8185.
5472 - Improve info-level log identification of particular circuits, to
5473 help with debugging. Closes ticket 23645.
5475 o Minor features (relay):
5476 - When choosing which circuits can be expired as unused, consider
5477 circuits from clients even if those clients used regular CREATE
5478 cells to make them; and do not consider circuits from relays even
5479 if they were made with CREATE_FAST. Part of ticket 22805.
5481 o Minor features (robustness):
5482 - Change several fatal assertions when flushing buffers into non-
5483 fatal assertions, to prevent any recurrence of 23690.
5485 o Minor features (spec conformance, bridge, diagnostic):
5486 - When handling the USERADDR command on an ExtOrPort, warn when the
5487 transports provides a USERADDR with no port. In a future version,
5488 USERADDR commands of this format may be rejected. Detects problems
5489 related to ticket 23080.
5491 o Minor features (testing):
5492 - Add a unit test to make sure that our own generated platform
5493 string will be accepted by directory authorities. Closes
5496 o Minor bugfixes (bootstrapping):
5497 - When warning about state file clock skew, report the correct
5498 direction for the detected skew. Fixes bug 23606; bugfix
5500 - Avoid an assertion failure when logging a state file clock skew
5501 very early in bootstrapping. Fixes bug 23607; bugfix
5504 o Minor bugfixes (build, compilation):
5505 - Fix a compilation warning when building with zstd support on
5506 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
5507 and fixed by Andreas Stieger.
5508 - When searching for OpenSSL, don't accept any OpenSSL library that
5509 lacks TLSv1_1_method(): Tor doesn't build with those versions.
5510 Additionally, look in /usr/local/opt/openssl, if it's present.
5511 These changes together repair the default build on OSX systems
5512 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
5514 o Minor bugfixes (compression):
5515 - Handle a pathological case when decompressing Zstandard data when
5516 the output buffer size is zero. Fixes bug 23551; bugfix
5519 o Minor bugfixes (documentation):
5520 - Fix manpage to not refer to the obsolete (and misspelled)
5521 UseEntryGuardsAsDirectoryGuards parameter in the description of
5522 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
5524 o Minor bugfixes (hidden service v3):
5525 - Don't log an assertion failure when we can't find the right
5526 information to extend to an introduction point. In rare cases,
5527 this could happen, causing a warning, even though tor would
5528 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
5529 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
5530 much bigger so the rendezvous point can't distinguish which hidden
5531 service protocol is being used. Fixes bug 23420; bugfix
5534 o Minor bugfixes (hidden service, relay):
5535 - Avoid a possible double close of a circuit by the intro point on
5536 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
5537 bugfix on 0.3.0.1-alpha.
5539 o Minor bugfixes (logging, relay shutdown, annoyance):
5540 - When a circuit is marked for close, do not attempt to package any
5541 cells for channels on that circuit. Previously, we would detect
5542 this condition lower in the call stack, when we noticed that the
5543 circuit had no attached channel, and log an annoying message.
5544 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5546 o Minor bugfixes (scheduler):
5547 - When switching schedulers due to a consensus change, we didn't
5548 give the new scheduler a chance to react to the consensus. Fix
5549 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
5550 - Make the KISTSchedRunInterval option a non negative value. With
5551 this, the way to disable KIST through the consensus is to set it
5552 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
5553 - Only notice log the selected scheduler when we switch scheduler
5554 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
5555 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
5556 by a different tv_usec data type. Fixes bug 23575; bugfix
5558 - Make a hard exit if tor is unable to pick a scheduler which can
5559 happen if the user specifies a scheduler type that is not
5560 supported and not other types in Schedulers. Fixes bug 23581;
5561 bugfix on 0.3.2.1-alpha.
5562 - Properly initialize the scheduler last run time counter so it is
5563 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
5565 o Minor bugfixes (testing):
5566 - Capture and detect several "Result does not fit" warnings in unit
5567 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
5569 - Fix additional channelpadding unit test failures by using mocked
5570 time instead of actual time for all tests. Fixes bug 23608; bugfix
5572 - The removal of some old scheduler options caused some tests to
5573 fail on BSD systems. Assume current behavior is correct and make
5574 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
5576 o Code simplification and refactoring:
5577 - Remove various ways of testing circuits and connections for
5578 "clientness"; instead, favor channel_is_client(). Part of
5581 o Deprecated features:
5582 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
5583 now deprecated; they do not apply to relays, and they have had no
5584 effect on clients since 0.2.8.x. Closes ticket 19704.
5587 - HiddenServiceVersion man page entry wasn't mentioning the now
5588 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
5589 - Clarify that the Address option is entirely about setting an
5590 advertised IPv4 address. Closes ticket 18891.
5591 - Clarify the manpage's use of the term "address" to clarify what
5592 kind of address is intended. Closes ticket 21405.
5593 - Document that onion service subdomains are allowed, and ignored.
5594 Closes ticket 18736.
5597 Changes in version 0.3.2.1-alpha - 2017-09-18
5598 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
5599 includes support for our next-generation ("v3") onion service
5600 protocol, and adds a new circuit scheduler for more responsive
5601 forwarding decisions from relays. There are also numerous other small
5602 features and bugfixes here.
5604 Below are the changes since Tor 0.3.1.7.
5606 o Major feature (scheduler, channel):
5607 - Tor now uses new schedulers to decide which circuits should
5608 deliver cells first, in order to improve congestion at relays. The
5609 first type is called "KIST" ("Kernel Informed Socket Transport"),
5610 and is only available on Linux-like systems: it uses feedback from
5611 the kernel to prevent the kernel's TCP buffers from growing too
5612 full. The second new scheduler type is called "KISTLite": it
5613 behaves the same as KIST, but runs on systems without kernel
5614 support for inspecting TCP implementation details. The old
5615 scheduler is still available, under the name "Vanilla". To change
5616 the default scheduler preference order, use the new "Schedulers"
5617 option. (The default preference order is "KIST,KISTLite,Vanilla".)
5619 Matt Traudt implemented KIST, based on research by Rob Jansen,
5620 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
5621 more information, see the design paper at
5622 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
5623 followup implementation paper at https://arxiv.org/abs/1709.01044.
5624 Closes ticket 12541.
5626 o Major features (next-generation onion services):
5627 - Tor now supports the next-generation onion services protocol for
5628 clients and services! As part of this release, the core of
5629 proposal 224 has been implemented and is available for
5630 experimentation and testing by our users. This newer version of
5631 onion services ("v3") features many improvements over the legacy
5634 a) Better crypto (replaced SHA1/DH/RSA1024
5635 with SHA3/ed25519/curve25519)
5637 b) Improved directory protocol, leaking much less information to
5640 c) Improved directory protocol, with smaller surface for
5643 d) Better onion address security against impersonation.
5645 e) More extensible introduction/rendezvous protocol.
5647 f) A cleaner and more modular codebase.
5649 You can identify a next-generation onion address by its length:
5650 they are 56 characters long, as in
5651 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
5653 In the future, we will release more options and features for v3
5654 onion services, but we first need a testing period, so that the
5655 current codebase matures and becomes more robust. Planned features
5656 include: offline keys, advanced client authorization, improved
5657 guard algorithms, and statistics. For full details, see
5660 Legacy ("v2") onion services will still work for the foreseeable
5661 future, and will remain the default until this new codebase gets
5662 tested and hardened. Service operators who want to experiment with
5663 the new system can use the 'HiddenServiceVersion 3' torrc
5664 directive along with the regular onion service configuration
5665 options. We will publish a blog post about this new feature
5668 o Major bugfixes (usability, control port):
5669 - Report trusted clock skew indications as bootstrap errors, so
5670 controllers can more easily alert users when their clocks are
5671 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
5673 o Minor features (bug detection):
5674 - Log a warning message with a stack trace for any attempt to call
5675 get_options() during option validation. This pattern has caused
5676 subtle bugs in the past. Closes ticket 22281.
5678 o Minor features (client):
5679 - You can now use Tor as a tunneled HTTP proxy: use the new
5680 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
5681 requests. Closes ticket 22407.
5682 - Add an extra check to make sure that we always use the newer guard
5683 selection code for picking our guards. Closes ticket 22779.
5684 - When downloading (micro)descriptors, don't split the list into
5685 multiple requests unless we want at least 32 descriptors.
5686 Previously, we split at 4, not 32, which led to significant
5687 overhead in HTTP request size and degradation in compression
5688 performance. Closes ticket 23220.
5690 o Minor features (command line):
5691 - Add a new commandline option, --key-expiration, which prints when
5692 the current signing key is going to expire. Implements ticket
5693 17639; patch by Isis Lovecruft.
5695 o Minor features (control port):
5696 - If an application tries to use the control port as an HTTP proxy,
5697 respond with a meaningful "This is the Tor control port" message,
5698 and log the event. Closes ticket 1667. Patch from Ravi
5700 - Provide better error message for GETINFO desc/(id|name) when not
5701 fetching router descriptors. Closes ticket 5847. Patch by
5703 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
5704 whether Tor will try to download router descriptors and
5705 microdescriptors respectively. Closes ticket 22684.
5706 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
5707 so controllers can tell whether the geoip databases are loaded.
5708 Closes ticket 23237.
5709 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
5710 events. Closes ticket 19254. Patch by "DonnchaC".
5712 o Minor features (development support):
5713 - Developers can now generate a call-graph for Tor using the
5714 "calltool" python program, which post-processes object dumps. It
5715 should work okay on many Linux and OSX platforms, and might work
5716 elsewhere too. To run it, install calltool from
5717 https://gitweb.torproject.org/user/nickm/calltool.git and run
5718 "make callgraph". Closes ticket 19307.
5720 o Minor features (ed25519):
5721 - Add validation function to checks for torsion components in
5722 ed25519 public keys, used by prop224 client-side code. Closes
5723 ticket 22006. Math help by Ian Goldberg.
5725 o Minor features (exit relay, DNS):
5726 - Improve the clarity and safety of the log message from evdns when
5727 receiving an apparently spoofed DNS reply. Closes ticket 3056.
5729 o Minor features (integration, hardening):
5730 - Add a new NoExec option to prevent Tor from running other
5731 programs. When this option is set to 1, Tor will never try to run
5732 another program, regardless of the settings of
5733 PortForwardingHelper, ClientTransportPlugin, or
5734 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
5735 without restarting Tor. Closes ticket 22976.
5737 o Minor features (logging):
5738 - Improve the warning message for specifying a relay by nickname.
5739 The previous message implied that nickname registration was still
5740 part of the Tor network design, which it isn't. Closes
5742 - If the sandbox filter fails to load, suggest to the user that
5743 their kernel might not support seccomp2. Closes ticket 23090.
5745 o Minor features (portability):
5746 - Check at configure time whether uint8_t is the same type as
5747 unsigned char. Lots of existing code already makes this
5748 assumption, and there could be strict aliasing issues if the
5749 assumption is violated. Closes ticket 22410.
5751 o Minor features (relay, configuration):
5752 - Reject attempts to use relative file paths when RunAsDaemon is
5753 set. Previously, Tor would accept these, but the directory-
5754 changing step of RunAsDaemon would give strange and/or confusing
5755 results. Closes ticket 22731.
5757 o Minor features (startup, safety):
5758 - When configured to write a PID file, Tor now exits if it is unable
5759 to do so. Previously, it would warn and continue. Closes
5762 o Minor features (static analysis):
5763 - The BUG() macro has been changed slightly so that Coverity no
5764 longer complains about dead code if the bug is impossible. Closes
5767 o Minor features (testing):
5768 - The default chutney network tests now include tests for the v3
5769 hidden service design. Make sure you have the latest version of
5770 chutney if you want to run these. Closes ticket 22437.
5771 - Add a unit test to verify that we can parse a hardcoded v2 hidden
5772 service descriptor. Closes ticket 15554.
5774 o Minor bugfixes (certificate handling):
5775 - Fix a time handling bug in Tor certificates set to expire after
5776 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
5777 Coverity as CID 1415728.
5779 o Minor bugfixes (client, usability):
5780 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
5781 SOCKS4a requests that contain IP address strings, even when
5782 SafeSocks in enabled, as this prevents user from connecting to
5783 known IP addresses without relying on DNS for resolving. SafeSocks
5784 still rejects SOCKS connections that connect to IP addresses when
5785 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
5786 bugfix on Tor 0.2.6.2-alpha.
5788 o Minor bugfixes (code correctness):
5789 - Call htons() in extend_cell_format() for encoding a 16-bit value.
5790 Previously we used ntohs(), which happens to behave the same on
5791 all the platforms we support, but which isn't really correct.
5792 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
5793 - For defense-in-depth, make the controller's write_escaped_data()
5794 function robust to extremely long inputs. Fixes bug 19281; bugfix
5795 on 0.1.1.1-alpha. Reported by Guido Vranken.
5797 o Minor bugfixes (compilation):
5798 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
5799 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5801 o Minor bugfixes (consensus expiry):
5802 - Check for adequate directory information correctly. Previously, Tor
5803 would reconsider whether it had sufficient directory information
5804 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
5806 o Minor bugfixes (directory protocol):
5807 - Directory servers now include a "Date:" http header for response
5808 codes other than 200. Clients starting with a skewed clock and a
5809 recent consensus were getting "304 Not modified" responses from
5810 directory authorities, so without the Date header, the client
5811 would never hear about a wrong clock. Fixes bug 23499; bugfix
5813 - Make clients wait for 6 seconds before trying to download a
5814 consensus from an authority. Fixes bug 17750; bugfix
5817 o Minor bugfixes (DoS-resistance):
5818 - If future code asks if there are any running bridges, without
5819 checking if bridges are enabled, log a BUG warning rather than
5820 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
5822 o Minor bugfixes (format strictness):
5823 - Restrict several data formats to decimal. Previously, the
5824 BuildTimeHistogram entries in the state file, the "bw=" entries in
5825 the bandwidth authority file, and the process IDs passed to the
5826 __OwningControllerProcess option could all be specified in hex or
5827 octal as well as in decimal. This was not an intentional feature.
5828 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
5831 o Minor bugfixes (heartbeat):
5832 - If we fail to write a heartbeat message, schedule a retry for the
5833 minimum heartbeat interval number of seconds in the future. Fixes
5834 bug 19476; bugfix on 0.2.3.1-alpha.
5836 o Minor bugfixes (linux seccomp2 sandbox, logging):
5837 - Fix some messages on unexpected errors from the seccomp2 library.
5838 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
5840 o Minor bugfixes (logging):
5841 - Remove duplicate log messages regarding opening non-local
5842 SocksPorts upon parsing config and opening listeners at startup.
5843 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
5844 - Use a more comprehensible log message when telling the user
5845 they've excluded every running exit node. Fixes bug 7890; bugfix
5847 - When logging the number of descriptors we intend to download per
5848 directory request, do not log a number higher than then the number
5849 of descriptors we're fetching in total. Fixes bug 19648; bugfix
5851 - When warning about a directory owned by the wrong user, log the
5852 actual name of the user owning the directory. Previously, we'd log
5853 the name of the process owner twice. Fixes bug 23487; bugfix
5855 - The tor specification says hop counts are 1-based, so fix two log
5856 messages that mistakenly logged 0-based hop counts. Fixes bug
5857 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
5858 Credit to Xiaofan Li for reporting this issue.
5860 o Minor bugfixes (portability):
5861 - Stop using the PATH_MAX variable, which is not defined on GNU
5862 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
5864 o Minor bugfixes (relay):
5865 - When uploading our descriptor for the first time after startup,
5866 report the reason for uploading as "Tor just started" rather than
5867 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
5868 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5869 relays, to prevent spurious address resolutions and descriptor
5870 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5871 bugfix on in 0.2.8.1-alpha.
5873 o Minor bugfixes (tests):
5874 - Fix a broken unit test for the OutboundAddress option: the parsing
5875 function was never returning an error on failure. Fixes bug 23366;
5876 bugfix on 0.3.0.3-alpha.
5877 - Fix a signed-integer overflow in the unit tests for
5878 dir/download_status_random_backoff, which was untriggered until we
5879 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
5881 o Minor bugfixes (usability, control port):
5882 - Stop making an unnecessary routerlist check in NETINFO clock skew
5883 detection; this was preventing clients from reporting NETINFO clock
5884 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
5886 o Code simplification and refactoring:
5887 - Extract the code for handling newly-open channels into a separate
5888 function from the general code to handle channel state
5889 transitions. This change simplifies our callgraph, reducing the
5890 size of the largest strongly connected component by roughly a
5891 factor of two. Closes ticket 22608.
5892 - Remove dead code for largely unused statistics on the number of
5893 times we've attempted various public key operations. Fixes bug
5894 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
5895 - Remove several now-obsolete functions for asking about old
5896 variants directory authority status. Closes ticket 22311; patch
5898 - Remove some of the code that once supported "Named" and "Unnamed"
5899 routers. Authorities no longer vote for these flags. Closes
5901 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
5902 and old hidden services, to indicate that they aren't suitable for
5903 new protocols or formats. Closes ticket 23026.
5904 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
5905 22521. Patch from Neel Chauhan.
5906 - Split the enormous circuit_send_next_onion_skin() function into
5907 multiple subfunctions. Closes ticket 22804.
5908 - Split the portions of the buffer.c module that handle particular
5909 protocols into separate modules. Part of ticket 23149.
5910 - Use our test macros more consistently, to produce more useful
5911 error messages when our unit tests fail. Add coccinelle patches to
5912 allow us to re-check for test macro uses. Closes ticket 22497.
5914 o Deprecated features:
5915 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
5916 only applies to direct unencrypted HTTP connections to your
5917 directory server, which your Tor probably isn't using. Closes
5921 - Clarify in the manual that "Sandbox 1" is only supported on Linux
5922 kernels. Closes ticket 22677.
5923 - Document all values of PublishServerDescriptor in the manpage.
5924 Closes ticket 15645.
5925 - Improve the documentation for the directory port part of the
5926 DirAuthority line. Closes ticket 20152.
5927 - Restore documentation for the authorities' "approved-routers"
5928 file. Closes ticket 21148.
5931 - The AllowDotExit option has been removed as unsafe. It has been
5932 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
5933 - The ClientDNSRejectInternalAddresses flag can no longer be set on
5934 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
5935 Closes ticket 21031.
5936 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
5937 nobody was using it any longer. Closes ticket 22377.
5940 Changes in version 0.2.8.15 - 2017-09-18
5941 Tor 0.2.8.15 backports a collection of bugfixes from later
5944 Most significantly, it includes a fix for TROVE-2017-008, a
5945 security bug that affects hidden services running with the
5946 SafeLogging option disabled. For more information, see
5947 https://trac.torproject.org/projects/tor/ticket/23490
5949 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
5950 2018. We suggest that you upgrade to the latest stable release if
5951 possible. If you can't, we recommend that you upgrade at least to
5952 0.2.9, which will be supported until 2020.
5954 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5955 - Avoid an assertion failure bug affecting our implementation of
5956 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5957 handling of "0xx" differs from what we had expected. Fixes bug
5958 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5961 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5964 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
5965 - Backport a fix for an "unused variable" warning that appeared
5966 in some versions of mingw. Fixes bug 22838; bugfix on
5969 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
5970 - Fix a memset() off the end of an array when packing cells. This
5971 bug should be harmless in practice, since the corrupted bytes are
5972 still in the same structure, and are always padding bytes,
5973 ignored, or immediately overwritten, depending on compiler
5974 behavior. Nevertheless, because the memset()'s purpose is to make
5975 sure that any other cell-handling bugs can't expose bytes to the
5976 network, we need to fix it. Fixes bug 22737; bugfix on
5977 0.2.4.11-alpha. Fixes CID 1401591.
5979 o Build features (backport from 0.3.1.5-alpha):
5980 - Tor's repository now includes a Travis Continuous Integration (CI)
5981 configuration file (.travis.yml). This is meant to help new
5982 developers and contributors who fork Tor to a Github repository be
5983 better able to test their changes, and understand what we expect
5984 to pass. To use this new build feature, you must fork Tor to your
5985 Github account, then go into the "Integrations" menu in the
5986 repository settings for your fork and enable Travis, then push
5987 your changes. Closes ticket 22636.
5990 Changes in version 0.2.9.12 - 2017-09-18
5991 Tor 0.2.9.12 backports a collection of bugfixes from later
5994 Most significantly, it includes a fix for TROVE-2017-008, a
5995 security bug that affects hidden services running with the
5996 SafeLogging option disabled. For more information, see
5997 https://trac.torproject.org/projects/tor/ticket/23490
5999 o Major features (security, backport from 0.3.0.2-alpha):
6000 - Change the algorithm used to decide DNS TTLs on client and server
6001 side, to better resist DNS-based correlation attacks like the
6002 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
6003 Feamster. Now relays only return one of two possible DNS TTL
6004 values, and clients are willing to believe DNS TTL values up to 3
6005 hours long. Closes ticket 19769.
6007 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
6008 - Fix a rare crash when sending a begin cell on a circuit whose
6009 linked directory connection had already been closed. Fixes bug
6010 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
6012 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
6013 - Fix a bug that prevented exit nodes from caching DNS records for
6014 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
6016 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
6017 - Fix a typo that had prevented TPROXY-based transparent proxying
6018 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
6019 Patch from "d4fq0fQAgoJ".
6021 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6022 - Avoid an assertion failure bug affecting our implementation of
6023 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6024 handling of "0xx" differs from what we had expected. Fixes bug
6025 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6027 o Minor features (code style, backport from 0.3.1.3-alpha):
6028 - Add "Falls through" comments to our codebase, in order to silence
6029 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6030 Stieger. Closes ticket 22446.
6032 o Minor features (geoip):
6033 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6036 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
6037 - Roll over monthly accounting at the configured hour and minute,
6038 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
6039 Found by Andrey Karpov with PVS-Studio.
6041 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
6042 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
6043 bugfix on 0.2.8.1-alpha.
6044 - Fix warnings when building with libscrypt and openssl scrypt support
6045 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
6046 - When building with certain versions the mingw C header files, avoid
6047 float-conversion warnings when calling the C functions isfinite(),
6048 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
6050 o Minor bugfixes (compilation, backport from 0.3.1.7):
6051 - Avoid compiler warnings in the unit tests for running tor_sscanf()
6052 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
6054 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
6055 - Backport a fix for an "unused variable" warning that appeared
6056 in some versions of mingw. Fixes bug 22838; bugfix on
6059 o Minor bugfixes (controller, backport from 0.3.1.7):
6060 - Do not crash when receiving a HSPOST command with an empty body.
6061 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
6062 - Do not crash when receiving a POSTDESCRIPTOR command with an
6063 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
6065 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
6066 - Avoid Coverity build warnings related to our BUG() macro. By
6067 default, Coverity treats BUG() as the Linux kernel does: an
6068 instant abort(). We need to override that so our BUG() macro
6069 doesn't prevent Coverity from analyzing functions that use it.
6070 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
6072 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6073 - Fix a memset() off the end of an array when packing cells. This
6074 bug should be harmless in practice, since the corrupted bytes are
6075 still in the same structure, and are always padding bytes,
6076 ignored, or immediately overwritten, depending on compiler
6077 behavior. Nevertheless, because the memset()'s purpose is to make
6078 sure that any other cell-handling bugs can't expose bytes to the
6079 network, we need to fix it. Fixes bug 22737; bugfix on
6080 0.2.4.11-alpha. Fixes CID 1401591.
6082 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
6083 - When setting the maximum number of connections allowed by the OS,
6084 always allow some extra file descriptors for other files. Fixes
6085 bug 22797; bugfix on 0.2.0.10-alpha.
6087 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
6088 - Avoid a sandbox failure when trying to re-bind to a socket and
6089 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
6091 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
6092 - Permit the fchmod system call, to avoid crashing on startup when
6093 starting with the seccomp2 sandbox and an unexpected set of
6094 permissions on the data directory or its contents. Fixes bug
6095 22516; bugfix on 0.2.5.4-alpha.
6097 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
6098 - Avoid a double-marked-circuit warning that could happen when we
6099 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
6102 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
6103 - Reject version numbers with non-numeric prefixes (such as +, -, or
6104 whitespace). Disallowing whitespace prevents differential version
6105 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6106 and part of 21508; bugfix on 0.0.8pre1.
6108 o Build features (backport from 0.3.1.5-alpha):
6109 - Tor's repository now includes a Travis Continuous Integration (CI)
6110 configuration file (.travis.yml). This is meant to help new
6111 developers and contributors who fork Tor to a Github repository be
6112 better able to test their changes, and understand what we expect
6113 to pass. To use this new build feature, you must fork Tor to your
6114 Github account, then go into the "Integrations" menu in the
6115 repository settings for your fork and enable Travis, then push
6116 your changes. Closes ticket 22636.
6119 Changes in version 0.3.0.11 - 2017-09-18
6120 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
6123 Most significantly, it includes a fix for TROVE-2017-008, a
6124 security bug that affects hidden services running with the
6125 SafeLogging option disabled. For more information, see
6126 https://trac.torproject.org/projects/tor/ticket/23490
6128 o Minor features (code style, backport from 0.3.1.7):
6129 - Add "Falls through" comments to our codebase, in order to silence
6130 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6131 Stieger. Closes ticket 22446.
6134 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6137 o Minor bugfixes (compilation, backport from 0.3.1.7):
6138 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
6139 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
6141 o Minor bugfixes (controller, backport from 0.3.1.7):
6142 - Do not crash when receiving a HSPOST command with an empty body.
6143 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
6144 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
6145 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
6147 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
6148 - When setting the maximum number of connections allowed by the OS,
6149 always allow some extra file descriptors for other files. Fixes
6150 bug 22797; bugfix on 0.2.0.10-alpha.
6152 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
6153 - Remove a forgotten debugging message when an introduction point
6154 successfully establishes a hidden service prop224 circuit with
6156 - Change three other log_warn() for an introduction point to
6157 protocol warnings, because they can be failure from the network
6158 and are not relevant to the operator. Fixes bug 23078; bugfix on
6159 0.3.0.1-alpha and 0.3.0.2-alpha.
6162 Changes in version 0.3.1.7 - 2017-09-18
6163 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
6165 With the 0.3.1 series, Tor now serves and downloads directory
6166 information in more compact formats, to save on bandwidth overhead. It
6167 also contains a new padding system to resist netflow-based traffic
6168 analysis, and experimental support for building parts of Tor in Rust
6169 (though no parts of Tor are in Rust yet). There are also numerous
6170 small features, bugfixes on earlier release series, and groundwork for
6171 the hidden services revamp of 0.3.2.
6173 This release also includes a fix for TROVE-2017-008, a security bug
6174 that affects hidden services running with the SafeLogging option
6175 disabled. For more information, see
6176 https://trac.torproject.org/projects/tor/ticket/23490
6178 Per our stable release policy, we plan to support each stable release
6179 series for at least the next nine months, or for three months after
6180 the first stable release of the next series: whichever is longer. If
6181 you need a release with long-term support, we recommend that you stay
6182 with the 0.2.9 series.
6184 Below is a list of the changes since 0.3.1.6-rc. For a list of all
6185 changes since 0.3.0, see the ReleaseNotes file.
6187 o Major bugfixes (security, hidden services, loggging):
6188 - Fix a bug where we could log uninitialized stack when a certain
6189 hidden service error occurred while SafeLogging was disabled.
6190 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
6191 TROVE-2017-008 and CVE-2017-0380.
6193 o Minor features (defensive programming):
6194 - Create a pair of consensus parameters, nf_pad_tor2web and
6195 nf_pad_single_onion, to disable netflow padding in the consensus
6196 for non-anonymous connections in case the overhead is high. Closes
6199 o Minor features (diagnostic):
6200 - Add a stack trace to the bug warnings that can be logged when
6201 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
6202 attempt for bug 23105.
6204 o Minor features (geoip):
6205 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6208 o Minor bugfixes (compilation):
6209 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
6210 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
6212 o Minor bugfixes (controller):
6213 - Do not crash when receiving a HSPOST command with an empty body.
6214 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
6215 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
6216 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
6218 o Minor bugfixes (relay):
6219 - Inform the geoip and rephist modules about all requests, even on
6220 relays that are only fetching microdescriptors. Fixes a bug
6221 related to 21585; bugfix on 0.3.0.1-alpha.
6223 o Minor bugfixes (unit tests):
6224 - Fix a channelpadding unit test failure on slow systems by using
6225 mocked time instead of actual time. Fixes bug 23077; bugfix
6229 Changes in version 0.3.1.6-rc - 2017-09-05
6230 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
6231 release series, including a bug that produced weird behavior on
6232 Windows directory caches.
6234 This is the first release candidate in the Tor 0.3.1 series. If we
6235 find no new bugs or regressions here, the first stable 0.3.1 release
6236 will be nearly identical to it.
6238 o Major bugfixes (windows, directory cache):
6239 - On Windows, do not try to delete cached consensus documents and
6240 diffs before they are unmapped from memory--Windows won't allow
6241 that. Instead, allow the consensus cache directory to grow larger,
6242 to hold files that might need to stay around longer. Fixes bug
6243 22752; bugfix on 0.3.1.1-alpha.
6245 o Minor features (directory authority):
6246 - Improve the message that authorities report to relays that present
6247 RSA/Ed25519 keypairs that conflict with previously pinned keys.
6248 Closes ticket 22348.
6250 o Minor features (geoip):
6251 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
6254 o Minor features (testing):
6255 - Add more tests for compression backend initialization. Closes
6258 o Minor bugfixes (directory cache):
6259 - Fix a memory leak when recovering space in the consensus cache.
6260 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
6262 o Minor bugfixes (hidden service):
6263 - Increase the number of circuits that a service is allowed to
6264 open over a specific period of time. The value was lower than it
6265 should be (8 vs 12) in the normal case of 3 introduction points.
6266 Fixes bug 22159; bugfix on 0.3.0.5-rc.
6267 - Fix a BUG warning during HSv3 descriptor decoding that could be
6268 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
6269 on 0.3.0.1-alpha. Bug found by "haxxpop".
6270 - Rate-limit the log messages if we exceed the maximum number of
6271 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
6273 o Minor bugfixes (logging, relay):
6274 - Remove a forgotten debugging message when an introduction point
6275 successfully establishes a hidden service prop224 circuit with
6277 - Change three other log_warn() for an introduction point to
6278 protocol warnings, because they can be failure from the network
6279 and are not relevant to the operator. Fixes bug 23078; bugfix on
6280 0.3.0.1-alpha and 0.3.0.2-alpha.
6282 o Minor bugfixes (relay):
6283 - When a relay is not running as a directory cache, it will no
6284 longer generate compressed consensuses and consensus diff
6285 information. Previously, this was a waste of disk and CPU. Fixes
6286 bug 23275; bugfix on 0.3.1.1-alpha.
6288 o Minor bugfixes (robustness, error handling):
6289 - Improve our handling of the cases where OpenSSL encounters a
6290 memory error while encoding keys and certificates. We haven't
6291 observed these errors in the wild, but if they do happen, we now
6292 detect and respond better. Fixes bug 19418; bugfix on all versions
6293 of Tor. Reported by Guido Vranken.
6295 o Minor bugfixes (stability):
6296 - Avoid crashing on a double-free when unable to load or process an
6297 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
6298 with the clang static analyzer.
6300 o Minor bugfixes (testing):
6301 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6302 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6303 - Port the hs_ntor handshake test to work correctly with recent
6304 versions of the pysha3 module. Fixes bug 23071; bugfix
6307 o Minor bugfixes (Windows service):
6308 - When running as a Windows service, set the ID of the main thread
6309 correctly. Failure to do so made us fail to send log messages to
6310 the controller in 0.2.1.16-rc, slowed down controller event
6311 delivery in 0.2.7.3-rc and later, and crash with an assertion
6312 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6313 Patch and diagnosis from "Vort".
6316 Changes in version 0.3.0.10 - 2017-08-02
6317 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
6318 from the current Tor alpha series. OpenBSD users and TPROXY users
6319 should upgrade; others are probably okay sticking with 0.3.0.9.
6321 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
6322 - Tor's repository now includes a Travis Continuous Integration (CI)
6323 configuration file (.travis.yml). This is meant to help new
6324 developers and contributors who fork Tor to a Github repository be
6325 better able to test their changes, and understand what we expect
6326 to pass. To use this new build feature, you must fork Tor to your
6327 Github account, then go into the "Integrations" menu in the
6328 repository settings for your fork and enable Travis, then push
6329 your changes. Closes ticket 22636.
6331 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
6332 - Fix a typo that had prevented TPROXY-based transparent proxying
6333 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
6334 Patch from "d4fq0fQAgoJ".
6336 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6337 - Avoid an assertion failure bug affecting our implementation of
6338 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6339 handling of "0xbar" differs from what we had expected. Fixes bug
6340 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6342 o Minor features (backport from 0.3.1.5-alpha):
6343 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
6346 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
6347 - Roll over monthly accounting at the configured hour and minute,
6348 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
6349 Found by Andrey Karpov with PVS-Studio.
6351 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
6352 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
6353 bugfix on 0.2.8.1-alpha.
6354 - Fix warnings when building with libscrypt and openssl scrypt
6355 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
6356 - When building with certain versions of the mingw C header files,
6357 avoid float-conversion warnings when calling the C functions
6358 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
6361 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
6362 - Backport a fix for an "unused variable" warning that appeared
6363 in some versions of mingw. Fixes bug 22838; bugfix on
6366 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
6367 - Avoid Coverity build warnings related to our BUG() macro. By
6368 default, Coverity treats BUG() as the Linux kernel does: an
6369 instant abort(). We need to override that so our BUG() macro
6370 doesn't prevent Coverity from analyzing functions that use it.
6371 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
6373 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
6374 - When rejecting a router descriptor for running an obsolete version
6375 of Tor without ntor support, warn about the obsolete tor version,
6376 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
6378 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
6379 - Avoid a sandbox failure when trying to re-bind to a socket and
6380 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
6382 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
6383 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
6384 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
6387 Changes in version 0.3.1.5-alpha - 2017-08-01
6388 Tor 0.3.1.5-alpha improves the performance of consensus diff
6389 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
6390 several other bugs. If no serious bugs are found in this version, the
6391 next version will be a release candidate.
6393 This release also marks the end of support for the Tor 0.2.4.x,
6394 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
6395 further bug or security fixes. Anyone still running or distributing
6396 one of those versions should upgrade.
6398 o Major features (build system, continuous integration):
6399 - Tor's repository now includes a Travis Continuous Integration (CI)
6400 configuration file (.travis.yml). This is meant to help new
6401 developers and contributors who fork Tor to a Github repository be
6402 better able to test their changes, and understand what we expect
6403 to pass. To use this new build feature, you must fork Tor to your
6404 Github account, then go into the "Integrations" menu in the
6405 repository settings for your fork and enable Travis, then push
6406 your changes. Closes ticket 22636.
6408 o Major bugfixes (openbsd, denial-of-service):
6409 - Avoid an assertion failure bug affecting our implementation of
6410 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6411 handling of "0xbar" differs from what we had expected. Fixes bug
6412 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6414 o Major bugfixes (relay, performance):
6415 - Perform circuit handshake operations at a higher priority than we
6416 use for consensus diff creation and compression. This should
6417 prevent circuits from starving when a relay or bridge receives a
6418 new consensus, especially on lower-powered machines. Fixes bug
6419 22883; bugfix on 0.3.1.1-alpha.
6421 o Minor features (bridge authority):
6422 - Add "fingerprint" lines to the networkstatus-bridges file produced
6423 by bridge authorities. Closes ticket 22207.
6425 o Minor features (directory cache, consensus diff):
6426 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
6427 operators with low-resource environments to adjust the number of
6428 consensuses they'll store and generate diffs from. Most cache
6429 operators should leave it unchanged. Helps to work around
6432 o Minor features (geoip):
6433 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
6436 o Minor features (relay, performance):
6437 - Always start relays with at least two worker threads, to prevent
6438 priority inversion on slow tasks. Part of the fix for bug 22883.
6439 - Allow background work to be queued with different priorities, so
6440 that a big pile of slow low-priority jobs will not starve out
6441 higher priority jobs. This lays the groundwork for a fix for
6444 o Minor bugfixes (build system, rust):
6445 - Fix a problem where Rust toolchains were not being found when
6446 building without --enable-cargo-online-mode, due to setting the
6447 $HOME environment variable instead of $CARGO_HOME. Fixes bug
6448 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
6450 o Minor bugfixes (compatibility, zstd):
6451 - Write zstd epilogues correctly when the epilogue requires
6452 reallocation of the output buffer, even with zstd 1.3.0.
6453 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
6454 22927; bugfix on 0.3.1.1-alpha.
6456 o Minor bugfixes (compilation warnings):
6457 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
6458 22915; bugfix on 0.2.8.1-alpha.
6459 - Fix warnings when building with libscrypt and openssl scrypt
6460 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
6461 - Compile correctly when both openssl 1.1.0 and libscrypt are
6462 detected. Previously this would cause an error. Fixes bug 22892;
6463 bugfix on 0.3.1.1-alpha.
6464 - When building with certain versions of the mingw C header files,
6465 avoid float-conversion warnings when calling the C functions
6466 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
6469 o Minor bugfixes (coverity build support):
6470 - Avoid Coverity build warnings related to our BUG() macro. By
6471 default, Coverity treats BUG() as the Linux kernel does: an
6472 instant abort(). We need to override that so our BUG() macro
6473 doesn't prevent Coverity from analyzing functions that use it.
6474 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
6476 o Minor bugfixes (directory authority):
6477 - When a directory authority rejects a descriptor or extrainfo with
6478 a given digest, mark that digest as undownloadable, so that we do
6479 not attempt to download it again over and over. We previously
6480 tried to avoid downloading such descriptors by other means, but we
6481 didn't notice if we accidentally downloaded one anyway. This
6482 behavior became problematic in 0.2.7.2-alpha, when authorities
6483 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6486 o Minor bugfixes (error reporting, windows):
6487 - When formatting Windows error messages, use the English format to
6488 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
6491 o Minor bugfixes (file limits, osx):
6492 - When setting the maximum number of connections allowed by the OS,
6493 always allow some extra file descriptors for other files. Fixes
6494 bug 22797; bugfix on 0.2.0.10-alpha.
6496 o Minor bugfixes (linux seccomp2 sandbox):
6497 - Avoid a sandbox failure when trying to re-bind to a socket and
6498 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
6500 o Minor bugfixes (memory leaks):
6501 - Fix a small memory leak when validating a configuration that uses
6502 two or more AF_UNIX sockets for the same port type. Fixes bug
6503 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
6505 o Minor bugfixes (unit tests):
6506 - test_consdiff_base64cmp would fail on OS X because while OS X
6507 follows the standard of (less than zero/zero/greater than zero),
6508 it doesn't follow the convention of (-1/0/+1). Make the test
6509 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
6510 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
6511 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
6514 Changes in version 0.3.1.4-alpha - 2017-06-29
6515 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
6516 to use a guard that was in the same network family as a chosen exit
6517 relay. This is a security regression; all clients running earlier
6518 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
6521 This release also fixes several other bugs introduced in 0.3.0.x
6522 and 0.3.1.x, including others that can affect bandwidth usage
6526 - To build with zstd and lzma support, Tor now requires the
6527 pkg-config tool at build time. (This requirement was new in
6528 0.3.1.1-alpha, but was not noted at the time. Noting it here to
6529 close ticket 22623.)
6531 o Major bugfixes (path selection, security):
6532 - When choosing which guard to use for a circuit, avoid the exit's
6533 family along with the exit itself. Previously, the new guard
6534 selection logic avoided the exit, but did not consider its family.
6535 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
6536 006 and CVE-2017-0377.
6538 o Major bugfixes (compression, zstd):
6539 - Correctly detect a full buffer when decompressing a large zstd-
6540 compressed input. Previously, we would sometimes treat a full
6541 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
6543 o Major bugfixes (directory protocol):
6544 - Ensure that we send "304 Not modified" as HTTP status code when a
6545 client is attempting to fetch a consensus or consensus diff, and
6546 the best one we can send them is one they already have. Fixes bug
6547 22702; bugfix on 0.3.1.1-alpha.
6549 o Major bugfixes (entry guards):
6550 - When starting with an old consensus, do not add new entry guards
6551 unless the consensus is "reasonably live" (under 1 day old). Fixes
6552 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
6554 o Minor features (bug mitigation, diagnostics, logging):
6555 - Avoid an assertion failure, and log a better error message, when
6556 unable to remove a file from the consensus cache on Windows.
6557 Attempts to mitigate and diagnose bug 22752.
6559 o Minor features (geoip):
6560 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
6563 o Minor bugfixes (compression):
6564 - When compressing or decompressing a buffer, check for a failure to
6565 create a compression object. Fixes bug 22626; bugfix
6567 - When decompressing a buffer, check for extra data after the end of
6568 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
6569 - When decompressing an object received over an anonymous directory
6570 connection, if we have already decompressed it using an acceptable
6571 compression method, do not reject it for looking like an
6572 unacceptable compression method. Fixes part of bug 22670; bugfix
6574 - When serving directory votes compressed with zlib, do not claim to
6575 have compressed them with zstd. Fixes bug 22669; bugfix
6577 - When spooling compressed data to an output buffer, don't try to
6578 spool more data when there is no more data to spool and we are not
6579 trying to flush the input. Previously, we would sometimes launch
6580 compression requests with nothing to do, which interferes with our
6581 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
6583 o Minor bugfixes (defensive programming):
6584 - Detect and break out of infinite loops in our compression code. We
6585 don't think that any such loops exist now, but it's best to be
6586 safe. Closes ticket 22672.
6587 - Fix a memset() off the end of an array when packing cells. This
6588 bug should be harmless in practice, since the corrupted bytes are
6589 still in the same structure, and are always padding bytes,
6590 ignored, or immediately overwritten, depending on compiler
6591 behavior. Nevertheless, because the memset()'s purpose is to make
6592 sure that any other cell-handling bugs can't expose bytes to the
6593 network, we need to fix it. Fixes bug 22737; bugfix on
6594 0.2.4.11-alpha. Fixes CID 1401591.
6596 o Minor bugfixes (linux seccomp2 sandbox):
6597 - Permit the fchmod system call, to avoid crashing on startup when
6598 starting with the seccomp2 sandbox and an unexpected set of
6599 permissions on the data directory or its contents. Fixes bug
6600 22516; bugfix on 0.2.5.4-alpha.
6601 - Fix a crash in the LZMA module, when the sandbox was enabled, and
6602 liblzma would allocate more than 16 MB of memory. We solve this by
6603 bumping the mprotect() limit in the sandbox module from 16 MB to
6604 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
6606 o Minor bugfixes (logging):
6607 - When decompressing, do not warn if we fail to decompress using a
6608 compression method that we merely guessed. Fixes part of bug
6609 22670; bugfix on 0.1.1.14-alpha.
6610 - When decompressing, treat mismatch between content-encoding and
6611 actual compression type as a protocol warning. Fixes part of bug
6612 22670; bugfix on 0.1.1.9-alpha.
6613 - Downgrade "assigned_to_cpuworker failed" message to info-level
6614 severity. In every case that can reach it, either a better warning
6615 has already been logged, or no warning is warranted. Fixes bug
6616 22356; bugfix on 0.2.6.3-alpha.
6617 - Demote a warn that was caused by libevent delays to info if
6618 netflow padding is less than 4.5 seconds late, or to notice
6619 if it is more (4.5 seconds is the amount of time that a netflow
6620 record might be emitted after, if we chose the maximum timeout).
6621 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
6623 o Minor bugfixes (process behavior):
6624 - When exiting because of an error, always exit with a nonzero exit
6625 status. Previously, we would fail to report an error in our exit
6626 status in cases related to __OwningControllerProcess failure,
6627 lockfile contention, and Ed25519 key initialization. Fixes bug
6628 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
6629 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
6633 - Add a manpage description for the key-pinning-journal file. Closes
6635 - Correctly note that bandwidth accounting values are stored in the
6636 state file, and the bw_accounting file is now obsolete. Closes
6638 - Document more of the files in the Tor data directory, including
6639 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
6640 approved-routers, sr-random, and diff-cache. Found while fixing
6644 Changes in version 0.3.0.9 - 2017-06-29
6645 Tor 0.3.0.9 fixes a path selection bug that would allow a client
6646 to use a guard that was in the same network family as a chosen exit
6647 relay. This is a security regression; all clients running earlier
6648 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
6651 This release also backports several other bugfixes from the 0.3.1.x
6654 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
6655 - When choosing which guard to use for a circuit, avoid the exit's
6656 family along with the exit itself. Previously, the new guard
6657 selection logic avoided the exit, but did not consider its family.
6658 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
6659 006 and CVE-2017-0377.
6661 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
6662 - Don't block bootstrapping when a primary bridge is offline and we
6663 can't get its descriptor. Fixes bug 22325; fixes one case of bug
6664 21969; bugfix on 0.3.0.3-alpha.
6666 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
6667 - When starting with an old consensus, do not add new entry guards
6668 unless the consensus is "reasonably live" (under 1 day old). Fixes
6669 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
6671 o Minor features (geoip):
6672 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
6675 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
6676 - Reject version numbers with non-numeric prefixes (such as +, -, or
6677 whitespace). Disallowing whitespace prevents differential version
6678 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6679 and part of 21508; bugfix on 0.0.8pre1.
6681 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
6682 - Permit the fchmod system call, to avoid crashing on startup when
6683 starting with the seccomp2 sandbox and an unexpected set of
6684 permissions on the data directory or its contents. Fixes bug
6685 22516; bugfix on 0.2.5.4-alpha.
6687 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
6688 - Fix a memset() off the end of an array when packing cells. This
6689 bug should be harmless in practice, since the corrupted bytes are
6690 still in the same structure, and are always padding bytes,
6691 ignored, or immediately overwritten, depending on compiler
6692 behavior. Nevertheless, because the memset()'s purpose is to make
6693 sure that any other cell-handling bugs can't expose bytes to the
6694 network, we need to fix it. Fixes bug 22737; bugfix on
6695 0.2.4.11-alpha. Fixes CID 1401591.
6698 Changes in version 0.3.1.3-alpha - 2017-06-08
6699 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
6700 remotely crash a hidden service with an assertion failure. Anyone
6701 running a hidden service should upgrade to this version, or to some
6702 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
6704 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
6705 that sometimes made relays unreliable, as well as several other
6706 bugfixes described below.
6708 o Major bugfixes (hidden service, relay, security):
6709 - Fix a remotely triggerable assertion failure when a hidden service
6710 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
6711 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
6712 - Fix a remotely triggerable assertion failure caused by receiving a
6713 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6714 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6717 o Major bugfixes (relay, link handshake):
6718 - When performing the v3 link handshake on a TLS connection, report
6719 that we have the x509 certificate that we actually used on that
6720 connection, even if we have changed certificates since that
6721 connection was first opened. Previously, we would claim to have
6722 used our most recent x509 link certificate, which would sometimes
6723 make the link handshake fail. Fixes one case of bug 22460; bugfix
6726 o Major bugfixes (relays, key management):
6727 - Regenerate link and authentication certificates whenever the key
6728 that signs them changes; also, regenerate link certificates
6729 whenever the signed key changes. Previously, these processes were
6730 only weakly coupled, and we relays could (for minutes to hours)
6731 wind up with an inconsistent set of keys and certificates, which
6732 other relays would not accept. Fixes two cases of bug 22460;
6733 bugfix on 0.3.0.1-alpha.
6734 - When sending an Ed25519 signing->link certificate in a CERTS cell,
6735 send the certificate that matches the x509 certificate that we
6736 used on the TLS connection. Previously, there was a race condition
6737 if the TLS context rotated after we began the TLS handshake but
6738 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
6741 o Major bugfixes (torrc, crash):
6742 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
6743 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
6745 o Minor features (code style):
6746 - Add "Falls through" comments to our codebase, in order to silence
6747 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6748 Stieger. Closes ticket 22446.
6750 o Minor features (diagnostic):
6751 - Add logging messages to try to diagnose a rare bug that seems to
6752 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
6753 think this is happening because of incorrect system clocks, but
6754 we'd like to know for certain. Diagnostic for bug 22466.
6756 o Minor bugfixes (correctness):
6757 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6758 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6760 o Minor bugfixes (directory protocol):
6761 - Check for libzstd >= 1.1, because older versions lack the
6762 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
6764 o Minor bugfixes (link handshake):
6765 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
6766 months, and regenerate it when it is within one month of expiring.
6767 Previously, we had generated this certificate at startup with a
6768 ten-year lifetime, but that could lead to weird behavior when Tor
6769 was started with a grossly inaccurate clock. Mitigates bug 22466;
6770 mitigation on 0.3.0.1-alpha.
6772 o Minor bugfixes (storage directories):
6773 - Always check for underflows in the cached storage directory usage.
6774 If the usage does underflow, re-calculate it. Also, avoid a
6775 separate underflow when the usage is not known. Fixes bug 22424;
6776 bugfix on 0.3.1.1-alpha.
6778 o Minor bugfixes (unit tests):
6779 - The unit tests now pass on systems where localhost is misconfigured
6780 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
6784 - Clarify the manpage for the (deprecated) torify script. Closes
6787 Changes in version 0.3.0.8 - 2017-06-08
6788 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
6789 remotely crash a hidden service with an assertion failure. Anyone
6790 running a hidden service should upgrade to this version, or to some
6791 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
6793 Tor 0.3.0.8 also includes fixes for several key management bugs
6794 that sometimes made relays unreliable, as well as several other
6795 bugfixes described below.
6797 o Major bugfixes (hidden service, relay, security, backport
6798 from 0.3.1.3-alpha):
6799 - Fix a remotely triggerable assertion failure when a hidden service
6800 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
6801 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
6802 - Fix a remotely triggerable assertion failure caused by receiving a
6803 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6804 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6807 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
6808 - When performing the v3 link handshake on a TLS connection, report
6809 that we have the x509 certificate that we actually used on that
6810 connection, even if we have changed certificates since that
6811 connection was first opened. Previously, we would claim to have
6812 used our most recent x509 link certificate, which would sometimes
6813 make the link handshake fail. Fixes one case of bug 22460; bugfix
6816 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
6817 - Regenerate link and authentication certificates whenever the key
6818 that signs them changes; also, regenerate link certificates
6819 whenever the signed key changes. Previously, these processes were
6820 only weakly coupled, and we relays could (for minutes to hours)
6821 wind up with an inconsistent set of keys and certificates, which
6822 other relays would not accept. Fixes two cases of bug 22460;
6823 bugfix on 0.3.0.1-alpha.
6824 - When sending an Ed25519 signing->link certificate in a CERTS cell,
6825 send the certificate that matches the x509 certificate that we
6826 used on the TLS connection. Previously, there was a race condition
6827 if the TLS context rotated after we began the TLS handshake but
6828 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
6831 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
6832 - Stop rejecting v3 hidden service descriptors because their size
6833 did not match an old padding rule. Fixes bug 22447; bugfix on
6836 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6837 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6838 December 2016 (of which ~126 were still functional) with a list of
6839 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6840 2017. Resolves ticket 21564.
6842 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
6843 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
6844 bug 22252; bugfix on 0.2.9.3-alpha.
6846 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
6847 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6848 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6850 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
6851 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
6852 months, and regenerate it when it is within one month of expiring.
6853 Previously, we had generated this certificate at startup with a
6854 ten-year lifetime, but that could lead to weird behavior when Tor
6855 was started with a grossly inaccurate clock. Mitigates bug 22466;
6856 mitigation on 0.3.0.1-alpha.
6858 o Minor bugfixes (memory leak, directory authority, backport from
6860 - When directory authorities reject a router descriptor due to
6861 keypinning, free the router descriptor rather than leaking the
6862 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6865 Changes in version 0.2.9.11 - 2017-06-08
6866 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
6867 remotely crash a hidden service with an assertion failure. Anyone
6868 running a hidden service should upgrade to this version, or to some
6869 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6870 are not affected by TROVE-2017-004.)
6872 Tor 0.2.9.11 also backports fixes for several key management bugs
6873 that sometimes made relays unreliable, as well as several other
6874 bugfixes described below.
6876 o Major bugfixes (hidden service, relay, security, backport
6877 from 0.3.1.3-alpha):
6878 - Fix a remotely triggerable assertion failure caused by receiving a
6879 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6880 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6883 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
6884 - When performing the v3 link handshake on a TLS connection, report
6885 that we have the x509 certificate that we actually used on that
6886 connection, even if we have changed certificates since that
6887 connection was first opened. Previously, we would claim to have
6888 used our most recent x509 link certificate, which would sometimes
6889 make the link handshake fail. Fixes one case of bug 22460; bugfix
6892 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6893 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6894 December 2016 (of which ~126 were still functional) with a list of
6895 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6896 2017. Resolves ticket 21564.
6898 o Minor features (future-proofing, backport from 0.3.0.7):
6899 - Tor no longer refuses to download microdescriptors or descriptors if
6900 they are listed as "published in the future". This change will
6901 eventually allow us to stop listing meaningful "published" dates
6902 in microdescriptor consensuses, and thereby allow us to reduce the
6903 resources required to download consensus diffs by over 50%.
6904 Implements part of ticket 21642; implements part of proposal 275.
6906 o Minor features (directory authorities, backport from 0.3.0.4-rc)
6907 - Directory authorities now reject relays running versions
6908 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
6909 suffer from bug 20499 and don't keep their consensus cache
6910 up-to-date. Resolves ticket 20509.
6912 o Minor features (geoip):
6913 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6916 o Minor bugfixes (control port, backport from 0.3.0.6):
6917 - The GETINFO extra-info/digest/<digest> command was broken because
6918 of a wrong base16 decode return value check, introduced when
6919 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
6921 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
6922 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6923 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6925 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
6926 - The getpid() system call is now permitted under the Linux seccomp2
6927 sandbox, to avoid crashing with versions of OpenSSL (and other
6928 libraries) that attempt to learn the process's PID by using the
6929 syscall rather than the VDSO code. Fixes bug 21943; bugfix
6932 o Minor bugfixes (memory leak, directory authority, backport
6933 from 0.3.1.2-alpha):
6934 - When directory authorities reject a router descriptor due to
6935 keypinning, free the router descriptor rather than leaking the
6936 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6938 Changes in version 0.2.8.14 - 2017-06-08
6939 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
6940 remotely crash a hidden service with an assertion failure. Anyone
6941 running a hidden service should upgrade to this version, or to some
6942 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6943 are not affected by TROVE-2017-004.)
6945 o Major bugfixes (hidden service, relay, security):
6946 - Fix a remotely triggerable assertion failure caused by receiving a
6947 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6948 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6951 o Minor features (geoip):
6952 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6955 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6956 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6957 December 2016 (of which ~126 were still functional) with a list of
6958 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6959 2017. Resolves ticket 21564.
6961 o Minor bugfixes (correctness):
6962 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6963 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6965 Changes in version 0.2.7.8 - 2017-06-08
6966 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
6967 remotely crash a hidden service with an assertion failure. Anyone
6968 running a hidden service should upgrade to this version, or to some
6969 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6970 are not affected by TROVE-2017-004.)
6972 o Major bugfixes (hidden service, relay, security):
6973 - Fix a remotely triggerable assertion failure caused by receiving a
6974 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6975 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6978 o Minor features (geoip):
6979 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6982 o Minor bugfixes (correctness):
6983 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6984 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6987 Changes in version 0.2.6.12 - 2017-06-08
6988 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
6989 remotely crash a hidden service with an assertion failure. Anyone
6990 running a hidden service should upgrade to this version, or to some
6991 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6992 are not affected by TROVE-2017-004.)
6994 o Major bugfixes (hidden service, relay, security):
6995 - Fix a remotely triggerable assertion failure caused by receiving a
6996 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6997 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7000 o Minor features (geoip):
7001 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7004 o Minor bugfixes (correctness):
7005 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7006 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7008 Changes in version 0.2.5.14 - 2017-06-08
7009 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
7010 remotely crash a hidden service with an assertion failure. Anyone
7011 running a hidden service should upgrade to this version, or to some
7012 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7013 are not affected by TROVE-2017-004.)
7015 o Major bugfixes (hidden service, relay, security):
7016 - Fix a remotely triggerable assertion failure caused by receiving a
7017 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7018 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7021 o Minor features (geoip):
7022 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7025 o Minor bugfixes (correctness):
7026 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7027 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7029 Changes in version 0.2.4.29 - 2017-06-08
7030 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
7031 remotely crash a hidden service with an assertion failure. Anyone
7032 running a hidden service should upgrade to this version, or to some
7033 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7034 are not affected by TROVE-2017-004.)
7036 o Major bugfixes (hidden service, relay, security):
7037 - Fix a remotely triggerable assertion failure caused by receiving a
7038 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7039 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7042 o Minor features (geoip):
7043 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7046 o Minor bugfixes (correctness):
7047 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7048 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7051 Changes in version 0.3.1.2-alpha - 2017-05-26
7052 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
7053 fixes a few bugs found while testing 0.3.1.1-alpha, including a
7054 memory corruption bug that affected relay stability.
7056 o Major bugfixes (crash, relay):
7057 - Fix a memory-corruption bug in relays that set MyFamily.
7058 Previously, they would double-free MyFamily elements when making
7059 the next descriptor or when changing their configuration. Fixes
7060 bug 22368; bugfix on 0.3.1.1-alpha.
7062 o Minor bugfixes (logging):
7063 - Log a better message when a directory authority replies to an
7064 upload with an unexpected status code. Fixes bug 11121; bugfix
7067 o Minor bugfixes (memory leak, directory authority):
7068 - When directory authorities reject a router descriptor due to
7069 keypinning, free the router descriptor rather than leaking the
7070 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7073 Changes in version 0.3.1.1-alpha - 2017-05-22
7074 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
7075 reduces the bandwidth usage for Tor's directory protocol, adds some
7076 basic padding to resist netflow-based traffic analysis and to serve as
7077 the basis of other padding in the future, and adds rust support to the
7080 It also contains numerous other small features and improvements to
7081 security, correctness, and performance.
7083 Below are the changes since 0.3.0.7.
7085 o Major features (directory protocol):
7086 - Tor relays and authorities can now serve clients an abbreviated
7087 version of the consensus document, containing only the changes
7088 since an older consensus document that the client holds. Clients
7089 now request these documents when available. When both client and
7090 server use this new protocol, they will use far less bandwidth (up
7091 to 94% less) to keep the client's consensus up-to-date. Implements
7092 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
7093 - Tor can now compress directory traffic with lzma or with zstd
7094 compression algorithms, which can deliver better bandwidth
7095 performance. Because lzma is computationally expensive, it's only
7096 used for documents that can be compressed once and served many
7097 times. Support for these algorithms requires that tor is built
7098 with the libzstd and/or liblzma libraries available. Implements
7099 proposal 278; closes ticket 21662.
7100 - Relays now perform the more expensive compression operations, and
7101 consensus diff generation, in worker threads. This separation
7102 avoids delaying the main thread when a new consensus arrives.
7104 o Major features (experimental):
7105 - Tor can now build modules written in Rust. To turn this on, pass
7106 the "--enable-rust" flag to the configure script. It's not time to
7107 get excited yet: currently, there is no actual Rust functionality
7108 beyond some simple glue code, and a notice at startup to tell you
7109 that Rust is running. Still, we hope that programmers and
7110 packagers will try building Tor with Rust support, so that we can
7111 find issues and solve portability problems. Closes ticket 22106.
7113 o Major features (traffic analysis resistance):
7114 - Connections between clients and relays now send a padding cell in
7115 each direction every 1.5 to 9.5 seconds (tunable via consensus
7116 parameters). This padding will not resist specialized
7117 eavesdroppers, but it should be enough to make many ISPs' routine
7118 network flow logging less useful in traffic analysis against
7121 Padding is negotiated using Tor's link protocol, so both relays
7122 and clients must upgrade for this to take effect. Clients may
7123 still send padding despite the relay's version by setting
7124 ConnectionPadding 1 in torrc, and may disable padding by setting
7125 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
7126 users with the torrc option ReducedConnectionPadding. Implements
7127 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
7128 - Relays will publish 24 hour totals of padding and non-padding cell
7129 counts to their extra-info descriptors, unless PaddingStatistics 0
7130 is set in torrc. These 24 hour totals are also rounded to
7133 o Major bugfixes (connection usage):
7134 - We use NETINFO cells to try to determine if both relays involved
7135 in a connection will agree on the canonical status of that
7136 connection. We prefer the connections where this is the case for
7137 extend cells, and try to close connections where relays disagree
7138 on their canonical status early. Also, we now prefer the oldest
7139 valid connection for extend cells. These two changes should reduce
7140 the number of long-term connections that are kept open between
7141 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
7142 - Relays now log hourly statistics (look for
7143 "channel_check_for_duplicates" lines) on the total number of
7144 connections to other relays. If the number of connections per
7145 relay is unexpectedly large, this log message is at notice level.
7146 Otherwise it is at info.
7148 o Major bugfixes (entry guards):
7149 - Don't block bootstrapping when a primary bridge is offline and we
7150 can't get its descriptor. Fixes bug 22325; fixes one case of bug
7151 21969; bugfix on 0.3.0.3-alpha.
7153 o Major bugfixes (linux TPROXY support):
7154 - Fix a typo that had prevented TPROXY-based transparent proxying
7155 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7156 Patch from "d4fq0fQAgoJ".
7158 o Minor features (security, windows):
7159 - Enable a couple of pieces of Windows hardening: one
7160 (HeapEnableTerminationOnCorruption) that has been on-by-default
7161 since Windows 8, and unavailable before Windows 7; and one
7162 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
7163 affect us, but shouldn't do any harm. Closes ticket 21953.
7165 o Minor features (config options):
7166 - Allow "%include" directives in torrc configuration files. These
7167 directives import the settings from other files, or from all the
7168 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
7169 - Make SAVECONF return an error when overwriting a torrc that has
7170 includes. Using SAVECONF with the FORCE option will allow it to
7171 overwrite torrc even if includes are used. Related to ticket 1922.
7172 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
7173 will work without the FORCE option. Related to ticket 1922.
7175 o Minor features (controller):
7176 - Warn the first time that a controller requests data in the long-
7177 deprecated 'GETINFO network-status' format. Closes ticket 21703.
7179 o Minor features (defaults):
7180 - The default value for UseCreateFast is now 0: clients which
7181 haven't yet received a consensus document will now use a proper
7182 ntor handshake to talk to their directory servers whenever they
7183 can. Closes ticket 21407.
7184 - Onion key rotation and expiry intervals are now defined as a
7185 network consensus parameter, per proposal 274. The default
7186 lifetime of an onion key is increased from 7 to 28 days. Old onion
7187 keys will expire after 7 days by default. This change will make
7188 consensus diffs much smaller, and save significant bandwidth.
7189 Closes ticket 21641.
7191 o Minor features (fallback directory list):
7192 - Update the fallback directory mirror whitelist and blacklist based
7193 on operator emails. Closes task 21121.
7194 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7195 December 2016 (of which ~126 were still functional) with a list of
7196 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7197 2017. Resolves ticket 21564.
7199 o Minor features (hidden services, logging):
7200 - Log a message when a hidden service descriptor has fewer
7201 introduction points than specified in
7202 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
7203 - Log a message when a hidden service reaches its introduction point
7204 circuit limit, and when that limit is reset. Follow up to ticket
7205 21594; closes ticket 21622.
7206 - Warn user if multiple entries in EntryNodes and at least one
7207 HiddenService are used together. Pinning EntryNodes along with a
7208 hidden service can be possibly harmful; for instance see ticket
7209 14917 or 21155. Closes ticket 21155.
7211 o Minor features (linux seccomp2 sandbox):
7212 - We now have a document storage backend compatible with the Linux
7213 seccomp2 sandbox. This backend is used for consensus documents and
7214 diffs between them; in the long term, we'd like to use it for
7215 unparseable directory material too. Closes ticket 21645
7216 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
7217 from 1MB to 16MB. This was necessary with the glibc allocator in
7218 order to allow worker threads to allocate more memory -- which in
7219 turn is necessary because of our new use of worker threads for
7220 compression. Closes ticket 22096.
7222 o Minor features (logging):
7223 - Log files are no longer created world-readable by default.
7224 (Previously, most distributors would store the logs in a non-
7225 world-readable location to prevent inappropriate access. This
7226 change is an extra precaution.) Closes ticket 21729; patch
7229 o Minor features (performance):
7230 - Our Keccak (SHA-3) implementation now accesses memory more
7231 efficiently, especially on little-endian systems. Closes
7233 - Add an O(1) implementation of channel_find_by_global_id(), to
7234 speed some controller functions.
7236 o Minor features (relay, configuration):
7237 - The MyFamily option may now be repeated as many times as desired,
7238 for relays that want to configure large families. Closes ticket
7239 4998; patch by Daniel Pinto.
7241 o Minor features (safety):
7242 - Add an explicit check to extrainfo_parse_entry_from_string() for
7243 NULL inputs. We don't believe this can actually happen, but it may
7244 help silence a warning from the Clang analyzer. Closes
7247 o Minor features (testing):
7248 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
7249 When Tor is compiled with this option, we disable a number of
7250 redundant memory-safety failsafes that are intended to stop bugs
7251 from becoming security issues. This makes it easier to hunt for
7252 bugs that would be security issues without the failsafes turned
7253 on. Closes ticket 21439.
7254 - Add a general event-tracing instrumentation support to Tor. This
7255 subsystem will enable developers and researchers to add fine-
7256 grained instrumentation to their Tor instances, for use when
7257 examining Tor network performance issues. There are no trace
7258 events yet, and event-tracing is off by default unless enabled at
7259 compile time. Implements ticket 13802.
7260 - Improve our version parsing tests: add tests for typical version
7261 components, add tests for invalid versions, including numeric
7262 range and non-numeric prefixes. Unit tests 21278, 21450, and
7263 21507. Partially implements 21470.
7265 o Minor bugfixes (bandwidth accounting):
7266 - Roll over monthly accounting at the configured hour and minute,
7267 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7268 Found by Andrey Karpov with PVS-Studio.
7270 o Minor bugfixes (code correctness):
7271 - Accurately identify client connections by their lack of peer
7272 authentication. This means that we bail out earlier if asked to
7273 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
7276 o Minor bugfixes (configuration):
7277 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
7278 bug 22252; bugfix on 0.2.9.3-alpha.
7280 o Minor bugfixes (connection lifespan):
7281 - Allow more control over how long TLS connections are kept open:
7282 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
7283 single option called CircuitsAvailableTimeout. Also, allow the
7284 consensus to control the default values for both this preference
7285 and the lifespan of relay-to-relay connections. Fixes bug 17592;
7286 bugfix on 0.2.5.5-alpha.
7287 - Increase the initial circuit build timeout testing frequency, to
7288 help ensure that ReducedConnectionPadding clients finish learning
7289 a timeout before their orconn would expire. The initial testing
7290 rate was set back in the days of TAP and before the Tor Browser
7291 updater, when we had to be much more careful about new clients
7292 making lots of circuits. With this change, a circuit build timeout
7293 is learned in about 15-20 minutes, instead of 100-120 minutes.
7295 o Minor bugfixes (controller):
7296 - GETINFO onions/current and onions/detached no longer respond with
7297 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
7298 - Trigger HS descriptor events on the control port when the client
7299 fails to pick a hidden service directory for a hidden service.
7300 This can happen if all the hidden service directories are in
7301 ExcludeNodes, or they have all been queried within the last 15
7302 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
7304 o Minor bugfixes (directory authority):
7305 - When rejecting a router descriptor for running an obsolete version
7306 of Tor without ntor support, warn about the obsolete tor version,
7307 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
7308 - Prevent the shared randomness subsystem from asserting when
7309 initialized by a bridge authority with an incomplete configuration
7310 file. Fixes bug 21586; bugfix on 0.2.9.8.
7312 o Minor bugfixes (exit-side DNS):
7313 - Fix an untriggerable assertion that checked the output of a
7314 libevent DNS error, so that the assertion actually behaves as
7315 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
7316 Karpov using PVS-Studio.
7318 o Minor bugfixes (fallback directories):
7319 - Make the usage example in updateFallbackDirs.py actually work, and
7320 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
7321 - Decrease the guard flag average required to be a fallback. This
7322 allows us to keep relays that have their guard flag removed when
7323 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
7324 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
7325 bugfix on 0.2.8.1-alpha.
7326 - Make sure fallback directory mirrors have the same address, port,
7327 and relay identity key for at least 30 days before they are
7328 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
7330 o Minor bugfixes (hidden services):
7331 - Stop printing a cryptic warning when a hidden service gets a
7332 request to connect to a virtual port that it hasn't configured.
7333 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
7334 - Simplify hidden service descriptor creation by using an existing
7335 flag to check if an introduction point is established. Fixes bug
7336 21599; bugfix on 0.2.7.2-alpha.
7338 o Minor bugfixes (memory leak):
7339 - Fix a small memory leak at exit from the backtrace handler code.
7340 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
7342 o Minor bugfixes (protocol, logging):
7343 - Downgrade a log statement about unexpected relay cells from "bug"
7344 to "protocol warning", because there is at least one use case
7345 where it can be triggered by a buggy tor implementation. Fixes bug
7346 21293; bugfix on 0.1.1.14-alpha.
7348 o Minor bugfixes (testing):
7349 - Use unbuffered I/O for utility functions around the
7350 process_handle_t type. This fixes unit test failures reported on
7351 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
7352 - Make display of captured unit test log messages consistent. Fixes
7353 bug 21510; bugfix on 0.2.9.3-alpha.
7354 - Make test-network.sh always call chutney's test-network.sh.
7355 Previously, this only worked on systems which had bash installed,
7356 due to some bash-specific code in the script. Fixes bug 19699;
7357 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
7359 o Minor bugfixes (voting consistency):
7360 - Reject version numbers with non-numeric prefixes (such as +, -, or
7361 whitespace). Disallowing whitespace prevents differential version
7362 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7363 and part of 21508; bugfix on 0.0.8pre1.
7365 o Minor bugfixes (windows, relay):
7366 - Resolve "Failure from drain_fd: No error" warnings on Windows
7367 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
7369 o Code simplification and refactoring:
7370 - Break up the 630-line function connection_dir_client_reached_eof()
7371 into a dozen smaller functions. This change should help
7372 maintainability and readability of the client directory code.
7373 - Isolate our use of the openssl headers so that they are only
7374 included from our crypto wrapper modules, and from tests that
7375 examine those modules' internals. Closes ticket 21841.
7376 - Simplify our API to launch directory requests, making it more
7377 extensible and less error-prone. Now it's easier to add extra
7378 headers to directory requests. Closes ticket 21646.
7379 - Our base64 decoding functions no longer overestimate the output
7380 space that they need when parsing unpadded inputs. Closes
7382 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
7383 Resolves ticket 22213.
7384 - The logic that directory caches use to spool request to clients,
7385 serving them one part at a time so as not to allocate too much
7386 memory, has been refactored for consistency. Previously there was
7387 a separate spooling implementation per type of spoolable data. Now
7388 there is one common spooling implementation, with extensible data
7389 types. Closes ticket 21651.
7390 - Tor's compression module now supports multiple backends. Part of
7391 the implementation for proposal 278; closes ticket 21663.
7394 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
7395 Closes ticket 21873.
7396 - Correct documentation about the default DataDirectory value.
7397 Closes ticket 21151.
7398 - Document the default behavior of NumEntryGuards and
7399 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
7401 - Document key=value pluggable transport arguments for Bridge lines
7402 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
7403 - Note that bandwidth-limiting options don't affect TCP headers or
7404 DNS. Closes ticket 17170.
7406 o Removed features (configuration options, all in ticket 22060):
7407 - These configuration options are now marked Obsolete, and no longer
7408 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
7409 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
7410 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
7411 in 0.2.9.2-alpha and have now been removed. The previous default
7412 behavior is now always chosen; the previous (less secure) non-
7413 default behavior is now unavailable.
7414 - CloseHSClientCircuitsImmediatelyOnTimeout and
7415 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
7416 0.2.9.2-alpha and now have been removed. HS circuits never close
7417 on circuit build timeout; they have a longer timeout period.
7418 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
7419 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
7420 (and others) to configure listen-only and advertise-only addresses.
7422 o Removed features (tools):
7423 - We've removed the tor-checkkey tool from src/tools. Long ago, we
7424 used it to help people detect RSA keys that were generated by
7425 versions of Debian affected by CVE-2008-0166. But those keys have
7426 been out of circulation for ages, and this tool is no longer
7427 required. Closes ticket 21842.
7430 Changes in version 0.3.0.7 - 2017-05-15
7431 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
7432 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
7433 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
7434 clients are not affected.
7436 o Major bugfixes (hidden service directory, security):
7437 - Fix an assertion failure in the hidden service directory code, which
7438 could be used by an attacker to remotely cause a Tor relay process to
7439 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
7440 should upgrade. This security issue is tracked as TROVE-2017-002.
7441 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
7444 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7447 o Minor features (future-proofing):
7448 - Tor no longer refuses to download microdescriptors or descriptors
7449 if they are listed as "published in the future". This change will
7450 eventually allow us to stop listing meaningful "published" dates
7451 in microdescriptor consensuses, and thereby allow us to reduce the
7452 resources required to download consensus diffs by over 50%.
7453 Implements part of ticket 21642; implements part of proposal 275.
7455 o Minor bugfixes (Linux seccomp2 sandbox):
7456 - The getpid() system call is now permitted under the Linux seccomp2
7457 sandbox, to avoid crashing with versions of OpenSSL (and other
7458 libraries) that attempt to learn the process's PID by using the
7459 syscall rather than the VDSO code. Fixes bug 21943; bugfix
7463 Changes in version 0.3.0.6 - 2017-04-26
7464 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
7466 With the 0.3.0 series, clients and relays now use Ed25519 keys to
7467 authenticate their link connections to relays, rather than the old
7468 RSA1024 keys that they used before. (Circuit crypto has been
7469 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
7470 the guard selection and replacement algorithm to behave more robustly
7471 in the presence of unreliable networks, and to resist guard-
7474 This series also includes numerous other small features and bugfixes,
7475 along with more groundwork for the upcoming hidden-services revamp.
7477 Per our stable release policy, we plan to support the Tor 0.3.0
7478 release series for at least the next nine months, or for three months
7479 after the first stable release of the 0.3.1 series: whichever is
7480 longer. If you need a release with long-term support, we recommend
7481 that you stay with the 0.2.9 series.
7483 Below are the changes since 0.3.0.5-rc. For a list of all changes
7484 since 0.2.9, see the ReleaseNotes file.
7486 o Minor features (geoip):
7487 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
7490 o Minor bugfixes (control port):
7491 - The GETINFO extra-info/digest/<digest> command was broken because
7492 of a wrong base16 decode return value check, introduced when
7493 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
7495 o Minor bugfixes (crash prevention):
7496 - Fix a (currently untriggerable, but potentially dangerous) crash
7497 bug when base32-encoding inputs whose sizes are not a multiple of
7498 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
7501 Changes in version 0.3.0.5-rc - 2017-04-05
7502 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
7503 0.3.0 release series.
7505 This is the second release candidate in the Tor 0.3.0 series, and has
7506 much fewer changes than the first. If we find no new bugs or
7507 regressions here, the first stable 0.3.0 release will be nearly
7510 o Major bugfixes (crash, directory connections):
7511 - Fix a rare crash when sending a begin cell on a circuit whose
7512 linked directory connection had already been closed. Fixes bug
7513 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
7515 o Major bugfixes (guard selection):
7516 - Fix a guard selection bug where Tor would refuse to bootstrap in
7517 some cases if the user swapped a bridge for another bridge in
7518 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
7519 Reported by "torvlnt33r".
7521 o Minor features (geoip):
7522 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
7525 o Minor bugfix (compilation):
7526 - Fix a warning when compiling hs_service.c. Previously, it had no
7527 exported symbols when compiled for libor.a, resulting in a
7528 compilation warning from clang. Fixes bug 21825; bugfix
7531 o Minor bugfixes (hidden services):
7532 - Make hidden services check for failed intro point connections,
7533 even when they have exceeded their intro point creation limit.
7534 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
7535 - Make hidden services with 8 to 10 introduction points check for
7536 failed circuits immediately after startup. Previously, they would
7537 wait for 5 minutes before performing their first checks. Fixes bug
7538 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
7540 o Minor bugfixes (memory leaks):
7541 - Fix a memory leak when using GETCONF on a port option. Fixes bug
7542 21682; bugfix on 0.3.0.3-alpha.
7544 o Minor bugfixes (relay):
7545 - Avoid a double-marked-circuit warning that could happen when we
7546 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
7549 o Minor bugfixes (tests):
7550 - Run the entry_guard_parse_from_state_full() test with the time set
7551 to a specific date. (The guard state that this test was parsing
7552 contained guards that had expired since the test was first
7553 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
7556 - Update the description of the directory server options in the
7557 manual page, to clarify that a relay no longer needs to set
7558 DirPort in order to be a directory cache. Closes ticket 21720.
7562 Changes in version 0.2.8.13 - 2017-03-03
7563 Tor 0.2.8.13 backports a security fix from later Tor
7564 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
7565 this release, if for some reason they cannot upgrade to a later
7566 release series, and if they build Tor with the --enable-expensive-hardening
7569 Note that support for Tor 0.2.8.x is ending next year: we will not issue
7570 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
7571 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7573 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7574 - Fix an integer underflow bug when comparing malformed Tor
7575 versions. This bug could crash Tor when built with
7576 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7577 0.2.9.8, which were built with -ftrapv by default. In other cases
7578 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7579 on 0.0.8pre1. Found by OSS-Fuzz.
7581 o Minor features (geoip):
7582 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7586 Changes in version 0.2.7.7 - 2017-03-03
7587 Tor 0.2.7.7 backports a number of security fixes from later Tor
7588 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
7589 this release, if for some reason they cannot upgrade to a later
7592 Note that support for Tor 0.2.7.x is ending this year: we will not issue
7593 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
7594 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7596 o Directory authority changes (backport from 0.2.8.5-rc):
7597 - Urras is no longer a directory authority. Closes ticket 19271.
7599 o Directory authority changes (backport from 0.2.9.2-alpha):
7600 - The "Tonga" bridge authority has been retired; the new bridge
7601 authority is "Bifroest". Closes tickets 19728 and 19690.
7603 o Directory authority key updates (backport from 0.2.8.1-alpha):
7604 - Update the V3 identity key for the dannenberg directory authority:
7605 it was changed on 18 November 2015. Closes task 17906. Patch
7608 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7609 - Fix a bug in parsing that could cause clients to read a single
7610 byte past the end of an allocated region. This bug could be used
7611 to cause hardened clients (built with --enable-expensive-hardening)
7612 to crash if they tried to visit a hostile hidden service. Non-
7613 hardened clients are only affected depending on the details of
7614 their platform's memory allocator. Fixes bug 21018; bugfix on
7615 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7616 2016-12-002 and as CVE-2016-1254.
7618 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7619 - Stop a crash that could occur when a client running with DNSPort
7620 received a query with multiple address types, and the first
7621 address type was not supported. Found and fixed by Scott Dial.
7622 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7623 - Prevent a class of security bugs caused by treating the contents
7624 of a buffer chunk as if they were a NUL-terminated string. At
7625 least one such bug seems to be present in all currently used
7626 versions of Tor, and would allow an attacker to remotely crash
7627 most Tor instances, especially those compiled with extra compiler
7628 hardening. With this defense in place, such bugs can't crash Tor,
7629 though we should still fix them as they occur. Closes ticket
7630 20384 (TROVE-2016-10-001).
7632 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7633 - Avoid a difficult-to-trigger heap corruption attack when extending
7634 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7635 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7636 Reported by Guido Vranken.
7638 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7639 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7640 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7642 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7643 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7644 pointer to the previous (uninitialized) key value. The impact here
7645 should be limited to a difficult-to-trigger crash, if OpenSSL is
7646 running an engine that makes key generation failures possible, or
7647 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7648 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7651 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7652 - Fix an integer underflow bug when comparing malformed Tor
7653 versions. This bug could crash Tor when built with
7654 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7655 0.2.9.8, which were built with -ftrapv by default. In other cases
7656 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7657 on 0.0.8pre1. Found by OSS-Fuzz.
7659 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7660 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7661 zero size. Check size argument to memwipe() for underflow. Fixes
7662 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7665 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7666 - Make Tor survive errors involving connections without a
7667 corresponding event object. Previously we'd fail with an
7668 assertion; now we produce a log message. Related to bug 16248.
7670 o Minor features (geoip):
7671 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7675 Changes in version 0.2.6.11 - 2017-03-03
7676 Tor 0.2.6.11 backports a number of security fixes from later Tor
7677 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
7678 this release, if for some reason they cannot upgrade to a later
7681 Note that support for Tor 0.2.6.x is ending this year: we will not issue
7682 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
7683 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7685 o Directory authority changes (backport from 0.2.8.5-rc):
7686 - Urras is no longer a directory authority. Closes ticket 19271.
7688 o Directory authority changes (backport from 0.2.9.2-alpha):
7689 - The "Tonga" bridge authority has been retired; the new bridge
7690 authority is "Bifroest". Closes tickets 19728 and 19690.
7692 o Directory authority key updates (backport from 0.2.8.1-alpha):
7693 - Update the V3 identity key for the dannenberg directory authority:
7694 it was changed on 18 November 2015. Closes task 17906. Patch
7697 o Major features (security fixes, backport from 0.2.9.4-alpha):
7698 - Prevent a class of security bugs caused by treating the contents
7699 of a buffer chunk as if they were a NUL-terminated string. At
7700 least one such bug seems to be present in all currently used
7701 versions of Tor, and would allow an attacker to remotely crash
7702 most Tor instances, especially those compiled with extra compiler
7703 hardening. With this defense in place, such bugs can't crash Tor,
7704 though we should still fix them as they occur. Closes ticket
7705 20384 (TROVE-2016-10-001).
7707 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7708 - Fix a bug in parsing that could cause clients to read a single
7709 byte past the end of an allocated region. This bug could be used
7710 to cause hardened clients (built with --enable-expensive-hardening)
7711 to crash if they tried to visit a hostile hidden service. Non-
7712 hardened clients are only affected depending on the details of
7713 their platform's memory allocator. Fixes bug 21018; bugfix on
7714 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7715 2016-12-002 and as CVE-2016-1254.
7717 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7718 - Stop a crash that could occur when a client running with DNSPort
7719 received a query with multiple address types, and the first
7720 address type was not supported. Found and fixed by Scott Dial.
7721 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7723 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7724 - Fix an error that could cause us to read 4 bytes before the
7725 beginning of an openssl string. This bug could be used to cause
7726 Tor to crash on systems with unusual malloc implementations, or
7727 systems with unusual hardening installed. Fixes bug 17404; bugfix
7730 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7731 - Avoid a difficult-to-trigger heap corruption attack when extending
7732 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7733 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7734 Reported by Guido Vranken.
7736 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7737 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7738 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7740 o Major bugfixes (guard selection, backport from 0.2.7.6):
7741 - Actually look at the Guard flag when selecting a new directory
7742 guard. When we implemented the directory guard design, we
7743 accidentally started treating all relays as if they have the Guard
7744 flag during guard selection, leading to weaker anonymity and worse
7745 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7748 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7749 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7750 pointer to the previous (uninitialized) key value. The impact here
7751 should be limited to a difficult-to-trigger crash, if OpenSSL is
7752 running an engine that makes key generation failures possible, or
7753 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7754 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7757 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7758 - Fix an integer underflow bug when comparing malformed Tor
7759 versions. This bug could crash Tor when built with
7760 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7761 0.2.9.8, which were built with -ftrapv by default. In other cases
7762 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7763 on 0.0.8pre1. Found by OSS-Fuzz.
7765 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7766 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7767 zero size. Check size argument to memwipe() for underflow. Fixes
7768 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7771 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7772 - Make Tor survive errors involving connections without a
7773 corresponding event object. Previously we'd fail with an
7774 assertion; now we produce a log message. Related to bug 16248.
7776 o Minor features (geoip):
7777 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7780 o Minor bugfixes (compilation, backport from 0.2.7.6):
7781 - Fix a compilation warning with Clang 3.6: Do not check the
7782 presence of an address which can never be NULL. Fixes bug 17781.
7785 Changes in version 0.2.5.13 - 2017-03-03
7786 Tor 0.2.5.13 backports a number of security fixes from later Tor
7787 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
7788 this release, if for some reason they cannot upgrade to a later
7791 Note that support for Tor 0.2.5.x is ending next year: we will not issue
7792 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
7793 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7795 o Directory authority changes (backport from 0.2.8.5-rc):
7796 - Urras is no longer a directory authority. Closes ticket 19271.
7798 o Directory authority changes (backport from 0.2.9.2-alpha):
7799 - The "Tonga" bridge authority has been retired; the new bridge
7800 authority is "Bifroest". Closes tickets 19728 and 19690.
7802 o Directory authority key updates (backport from 0.2.8.1-alpha):
7803 - Update the V3 identity key for the dannenberg directory authority:
7804 it was changed on 18 November 2015. Closes task 17906. Patch
7807 o Major features (security fixes, backport from 0.2.9.4-alpha):
7808 - Prevent a class of security bugs caused by treating the contents
7809 of a buffer chunk as if they were a NUL-terminated string. At
7810 least one such bug seems to be present in all currently used
7811 versions of Tor, and would allow an attacker to remotely crash
7812 most Tor instances, especially those compiled with extra compiler
7813 hardening. With this defense in place, such bugs can't crash Tor,
7814 though we should still fix them as they occur. Closes ticket
7815 20384 (TROVE-2016-10-001).
7817 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7818 - Fix a bug in parsing that could cause clients to read a single
7819 byte past the end of an allocated region. This bug could be used
7820 to cause hardened clients (built with --enable-expensive-hardening)
7821 to crash if they tried to visit a hostile hidden service. Non-
7822 hardened clients are only affected depending on the details of
7823 their platform's memory allocator. Fixes bug 21018; bugfix on
7824 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7825 2016-12-002 and as CVE-2016-1254.
7827 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7828 - Stop a crash that could occur when a client running with DNSPort
7829 received a query with multiple address types, and the first
7830 address type was not supported. Found and fixed by Scott Dial.
7831 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7833 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7834 - Fix an error that could cause us to read 4 bytes before the
7835 beginning of an openssl string. This bug could be used to cause
7836 Tor to crash on systems with unusual malloc implementations, or
7837 systems with unusual hardening installed. Fixes bug 17404; bugfix
7840 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7841 - Avoid a difficult-to-trigger heap corruption attack when extending
7842 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7843 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7844 Reported by Guido Vranken.
7846 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7847 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7848 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7850 o Major bugfixes (guard selection, backport from 0.2.7.6):
7851 - Actually look at the Guard flag when selecting a new directory
7852 guard. When we implemented the directory guard design, we
7853 accidentally started treating all relays as if they have the Guard
7854 flag during guard selection, leading to weaker anonymity and worse
7855 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7858 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7859 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7860 pointer to the previous (uninitialized) key value. The impact here
7861 should be limited to a difficult-to-trigger crash, if OpenSSL is
7862 running an engine that makes key generation failures possible, or
7863 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7864 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7867 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7868 - Fix an integer underflow bug when comparing malformed Tor
7869 versions. This bug could crash Tor when built with
7870 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7871 0.2.9.8, which were built with -ftrapv by default. In other cases
7872 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7873 on 0.0.8pre1. Found by OSS-Fuzz.
7875 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7876 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7877 zero size. Check size argument to memwipe() for underflow. Fixes
7878 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7881 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7882 - Make Tor survive errors involving connections without a
7883 corresponding event object. Previously we'd fail with an
7884 assertion; now we produce a log message. Related to bug 16248.
7886 o Minor features (geoip):
7887 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7890 o Minor bugfixes (compilation, backport from 0.2.7.6):
7891 - Fix a compilation warning with Clang 3.6: Do not check the
7892 presence of an address which can never be NULL. Fixes bug 17781.
7894 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
7895 - Check for failures from crypto_early_init, and refuse to continue.
7896 A previous typo meant that we could keep going with an
7897 uninitialized crypto library, and would have OpenSSL initialize
7898 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7899 when implementing ticket 4900. Patch by "teor".
7901 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7902 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7903 a client authorized hidden service. Fixes bug 15823; bugfix
7907 Changes in version 0.2.4.28 - 2017-03-03
7908 Tor 0.2.4.28 backports a number of security fixes from later Tor
7909 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
7910 this release, if for some reason they cannot upgrade to a later
7913 Note that support for Tor 0.2.4.x is ending soon: we will not issue
7914 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
7915 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
7917 o Directory authority changes (backport from 0.2.8.5-rc):
7918 - Urras is no longer a directory authority. Closes ticket 19271.
7920 o Directory authority changes (backport from 0.2.9.2-alpha):
7921 - The "Tonga" bridge authority has been retired; the new bridge
7922 authority is "Bifroest". Closes tickets 19728 and 19690.
7924 o Directory authority key updates (backport from 0.2.8.1-alpha):
7925 - Update the V3 identity key for the dannenberg directory authority:
7926 it was changed on 18 November 2015. Closes task 17906. Patch
7929 o Major features (security fixes, backport from 0.2.9.4-alpha):
7930 - Prevent a class of security bugs caused by treating the contents
7931 of a buffer chunk as if they were a NUL-terminated string. At
7932 least one such bug seems to be present in all currently used
7933 versions of Tor, and would allow an attacker to remotely crash
7934 most Tor instances, especially those compiled with extra compiler
7935 hardening. With this defense in place, such bugs can't crash Tor,
7936 though we should still fix them as they occur. Closes ticket
7937 20384 (TROVE-2016-10-001).
7939 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7940 - Fix a bug in parsing that could cause clients to read a single
7941 byte past the end of an allocated region. This bug could be used
7942 to cause hardened clients (built with --enable-expensive-hardening)
7943 to crash if they tried to visit a hostile hidden service. Non-
7944 hardened clients are only affected depending on the details of
7945 their platform's memory allocator. Fixes bug 21018; bugfix on
7946 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7947 2016-12-002 and as CVE-2016-1254.
7949 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7950 - Fix an error that could cause us to read 4 bytes before the
7951 beginning of an openssl string. This bug could be used to cause
7952 Tor to crash on systems with unusual malloc implementations, or
7953 systems with unusual hardening installed. Fixes bug 17404; bugfix
7956 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7957 - Avoid a difficult-to-trigger heap corruption attack when extending
7958 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7959 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7960 Reported by Guido Vranken.
7962 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7963 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7964 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7966 o Major bugfixes (guard selection, backport from 0.2.7.6):
7967 - Actually look at the Guard flag when selecting a new directory
7968 guard. When we implemented the directory guard design, we
7969 accidentally started treating all relays as if they have the Guard
7970 flag during guard selection, leading to weaker anonymity and worse
7971 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7974 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7975 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7976 pointer to the previous (uninitialized) key value. The impact here
7977 should be limited to a difficult-to-trigger crash, if OpenSSL is
7978 running an engine that makes key generation failures possible, or
7979 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7980 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7983 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7984 - Fix an integer underflow bug when comparing malformed Tor
7985 versions. This bug could crash Tor when built with
7986 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7987 0.2.9.8, which were built with -ftrapv by default. In other cases
7988 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7989 on 0.0.8pre1. Found by OSS-Fuzz.
7991 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7992 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7993 zero size. Check size argument to memwipe() for underflow. Fixes
7994 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7997 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7998 - Make Tor survive errors involving connections without a
7999 corresponding event object. Previously we'd fail with an
8000 assertion; now we produce a log message. Related to bug 16248.
8002 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
8003 - Make it harder for attackers to overload hidden services with
8004 introductions, by blocking multiple introduction requests on the
8005 same circuit. Resolves ticket 15515.
8007 o Minor features (geoip):
8008 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8011 o Minor bugfixes (compilation, backport from 0.2.7.6):
8012 - Fix a compilation warning with Clang 3.6: Do not check the
8013 presence of an address which can never be NULL. Fixes bug 17781.
8015 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8016 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8017 a client authorized hidden service. Fixes bug 15823; bugfix
8021 Changes in version 0.3.0.4-rc - 2017-03-01
8022 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
8023 0.3.0 release series, and introduces a few reliability features to
8024 keep them from coming back.
8026 This is the first release candidate in the Tor 0.3.0 series. If we
8027 find no new bugs or regressions here, the first stable 0.3.0 release
8028 will be nearly identical to it.
8030 o Major bugfixes (bridges):
8031 - When the same bridge is configured multiple times with the same
8032 identity, but at different address:port combinations, treat those
8033 bridge instances as separate guards. This fix restores the ability
8034 of clients to configure the same bridge with multiple pluggable
8035 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
8037 o Major bugfixes (hidden service directory v3):
8038 - Stop crashing on a failed v3 hidden service descriptor lookup
8039 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
8041 o Major bugfixes (parsing):
8042 - When parsing a malformed content-length field from an HTTP
8043 message, do not read off the end of the buffer. This bug was a
8044 potential remote denial-of-service attack against Tor clients and
8045 relays. A workaround was released in October 2016, to prevent this
8046 bug from crashing Tor. This is a fix for the underlying issue,
8047 which should no longer matter (if you applied the earlier patch).
8048 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
8049 using AFL (http://lcamtuf.coredump.cx/afl/).
8050 - Fix an integer underflow bug when comparing malformed Tor
8051 versions. This bug could crash Tor when built with
8052 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8053 0.2.9.8, which were built with -ftrapv by default. In other cases
8054 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8055 on 0.0.8pre1. Found by OSS-Fuzz.
8057 o Minor feature (protocol versioning):
8058 - Add new protocol version for proposal 224. HSIntro now advertises
8059 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
8061 o Minor features (directory authorities):
8062 - Directory authorities now reject descriptors that claim to be
8063 malformed versions of Tor. Helps prevent exploitation of
8065 - Reject version numbers with components that exceed INT32_MAX.
8066 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
8067 Fixes bug 21450; bugfix on 0.0.8pre1.
8068 - Directory authorities now reject relays running versions
8069 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
8070 suffer from bug 20499 and don't keep their consensus cache
8071 up-to-date. Resolves ticket 20509.
8073 o Minor features (geoip):
8074 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8077 o Minor features (reliability, crash):
8078 - Try better to detect problems in buffers where they might grow (or
8079 think they have grown) over 2 GB in size. Diagnostic for
8082 o Minor features (testing):
8083 - During 'make test-network-all', if tor logs any warnings, ask
8084 chutney to output them. Requires a recent version of chutney with
8085 the 21572 patch. Implements 21570.
8087 o Minor bugfixes (certificate expiration time):
8088 - Avoid using link certificates that don't become valid till some
8089 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
8091 o Minor bugfixes (code correctness):
8092 - Repair a couple of (unreachable or harmless) cases of the risky
8093 comparison-by-subtraction pattern that caused bug 21278.
8094 - Remove a redundant check for the UseEntryGuards option from the
8095 options_transition_affects_guards() function. Fixes bug 21492;
8096 bugfix on 0.3.0.1-alpha.
8098 o Minor bugfixes (directory mirrors):
8099 - Allow relays to use directory mirrors without a DirPort: these
8100 relays need to be contacted over their ORPorts using a begindir
8101 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
8102 - Clarify the message logged when a remote relay is unexpectedly
8103 missing an ORPort or DirPort: users were confusing this with a
8104 local port. Fixes another case of bug 20711; bugfix
8107 o Minor bugfixes (guards):
8108 - Don't warn about a missing guard state on timeout-measurement
8109 circuits: they aren't supposed to be using guards. Fixes an
8110 instance of bug 21007; bugfix on 0.3.0.1-alpha.
8111 - Silence a BUG() warning when attempting to use a guard whose
8112 descriptor we don't know, and make this scenario less likely to
8113 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
8115 o Minor bugfixes (hidden service):
8116 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
8117 cells. Previously, we were using sizeof() on a pointer, instead of
8118 the real destination buffer. Fortunately, that value was only used
8119 to double-check that there was enough room--which was already
8120 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
8122 o Minor bugfixes (testing):
8123 - Fix Raspbian build issues related to missing socket errno in
8124 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
8126 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
8127 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
8128 - Use bash in src/test/test-network.sh. This ensures we reliably
8129 call chutney's newer tools/test-network.sh when available. Fixes
8130 bug 21562; bugfix on 0.2.9.1-alpha.
8133 - Small fixes to the fuzzing documentation. Closes ticket 21472.
8136 Changes in version 0.2.9.10 - 2017-03-01
8137 Tor 0.2.9.10 backports a security fix from later Tor release. It also
8138 includes fixes for some major issues affecting directory authorities,
8139 LibreSSL compatibility, and IPv6 correctness.
8141 The Tor 0.2.9.x release series is now marked as a long-term-support
8142 series. We intend to backport security fixes to 0.2.9.x until at
8143 least January of 2020.
8145 o Major bugfixes (directory authority, 0.3.0.3-alpha):
8146 - During voting, when marking a relay as a probable sybil, do not
8147 clear its BadExit flag: sybils can still be bad in other ways
8148 too. (We still clear the other flags.) Fixes bug 21108; bugfix
8151 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
8152 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
8153 any IPv6 addresses. Instead, only reject a port over IPv6 if the
8154 exit policy rejects that port on more than an IPv6 /16 of
8155 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
8156 which rejected a relay's own IPv6 address by default. Fixes bug
8157 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
8159 o Major bugfixes (parsing, also in 0.3.0.4-rc):
8160 - Fix an integer underflow bug when comparing malformed Tor
8161 versions. This bug could crash Tor when built with
8162 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8163 0.2.9.8, which were built with -ftrapv by default. In other cases
8164 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8165 on 0.0.8pre1. Found by OSS-Fuzz.
8167 o Minor features (directory authorities, also in 0.3.0.4-rc):
8168 - Directory authorities now reject descriptors that claim to be
8169 malformed versions of Tor. Helps prevent exploitation of
8171 - Reject version numbers with components that exceed INT32_MAX.
8172 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
8173 Fixes bug 21450; bugfix on 0.0.8pre1.
8175 o Minor features (geoip):
8176 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8179 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
8180 - Autoconf now checks to determine if OpenSSL structures are opaque,
8181 instead of explicitly checking for OpenSSL version numbers. Part
8183 - Support building with recent LibreSSL code that uses opaque
8184 structures. Closes ticket 21359.
8186 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
8187 - Repair a couple of (unreachable or harmless) cases of the risky
8188 comparison-by-subtraction pattern that caused bug 21278.
8190 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
8191 - The tor-resolve command line tool now rejects hostnames over 255
8192 characters in length. Previously, it would silently truncate them,
8193 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
8194 Patch by "junglefowl".
8197 Changes in version 0.3.0.3-alpha - 2017-02-03
8198 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
8199 0.3.0.x development series, including some that could cause
8200 authorities to behave badly. There is also a fix for a longstanding
8201 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
8202 includes some smaller features and bugfixes.
8204 The Tor 0.3.0.x release series is now in patch-freeze: no additional
8205 features will be considered for inclusion in 0.3.0.x. We suspect that
8206 some bugs will probably remain, however, and we encourage people to
8209 o Major bugfixes (directory authority):
8210 - During voting, when marking a relay as a probable sybil, do not
8211 clear its BadExit flag: sybils can still be bad in other ways
8212 too. (We still clear the other flags.) Fixes bug 21108; bugfix
8214 - When deciding whether we have just found a router to be reachable,
8215 do not penalize it for not having performed an Ed25519 link
8216 handshake if it does not claim to support an Ed25519 handshake.
8217 Previously, we would treat such relays as non-running. Fixes bug
8218 21107; bugfix on 0.3.0.1-alpha.
8220 o Major bugfixes (entry guards):
8221 - Stop trying to build circuits through entry guards for which we
8222 have no descriptor. Also, stop crashing in the case that we *do*
8223 accidentally try to build a circuit in such a state. Fixes bug
8224 21242; bugfix on 0.3.0.1-alpha.
8226 o Major bugfixes (IPv6 Exits):
8227 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
8228 any IPv6 addresses. Instead, only reject a port over IPv6 if the
8229 exit policy rejects that port on more than an IPv6 /16 of
8230 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
8231 which rejected a relay's own IPv6 address by default. Fixes bug
8232 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
8234 o Minor feature (client):
8235 - Enable IPv6 traffic on the SocksPort by default. To disable this,
8236 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
8238 o Minor feature (fallback scripts):
8239 - Add a check_existing mode to updateFallbackDirs.py, which checks
8240 if fallbacks in the hard-coded list are working. Closes ticket
8241 20174. Patch by haxxpop.
8243 o Minor features (ciphersuite selection):
8244 - Clients now advertise a list of ciphersuites closer to the ones
8245 preferred by Firefox. Closes part of ticket 15426.
8246 - Allow relays to accept a wider range of ciphersuites, including
8247 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
8249 o Minor features (controller, configuration):
8250 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
8251 and so on, now comes with a __*Port variant that will not be saved
8252 to the torrc file by the controller's SAVECONF command. This
8253 change allows TorBrowser to set up a single-use domain socket for
8254 each time it launches Tor. Closes ticket 20956.
8255 - The GETCONF command can now query options that may only be
8256 meaningful in context-sensitive lists. This allows the controller
8257 to query the mixed SocksPort/__SocksPort style options introduced
8258 in feature 20956. Implements ticket 21300.
8260 o Minor features (portability, compilation):
8261 - Autoconf now checks to determine if OpenSSL structures are opaque,
8262 instead of explicitly checking for OpenSSL version numbers. Part
8264 - Support building with recent LibreSSL code that uses opaque
8265 structures. Closes ticket 21359.
8267 o Minor features (relay):
8268 - We now allow separation of exit and relay traffic to different
8269 source IP addresses, using the OutboundBindAddressExit and
8270 OutboundBindAddressOR options respectively. Closes ticket 17975.
8271 Written by Michael Sonntag.
8273 o Minor bugfix (logging):
8274 - Don't recommend the use of Tor2web in non-anonymous mode.
8275 Recommending Tor2web is a bad idea because the client loses all
8276 anonymity. Tor2web should only be used in specific cases by users
8277 who *know* and understand the issues. Fixes bug 21294; bugfix
8280 o Minor bugfixes (client):
8281 - Always recover from failures in extend_info_from_node(), in an
8282 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
8283 bugfix on 0.2.3.1-alpha.
8285 o Minor bugfixes (client, entry guards):
8286 - Fix a bug warning (with backtrace) when we fail a channel that
8287 circuits to fallback directories on it. Fixes bug 21128; bugfix
8289 - Fix a spurious bug warning (with backtrace) when removing an
8290 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
8291 - Fix a bug of the new guard algorithm where tor could stall for up
8292 to 10 minutes before retrying a guard after a long period of no
8293 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
8294 - Do not try to build circuits until we have descriptors for our
8295 primary entry guards. Related to fix for bug 21242.
8297 o Minor bugfixes (configure, autoconf):
8298 - Rename the configure option --enable-expensive-hardening to
8299 --enable-fragile-hardening. Expensive hardening makes the tor
8300 daemon abort when some kinds of issues are detected. Thus, it
8301 makes tor more at risk of remote crashes but safer against RCE or
8302 heartbleed bug category. We now try to explain this issue in a
8303 message from the configure script. Fixes bug 21290; bugfix
8306 o Minor bugfixes (controller):
8307 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
8308 20824; bugfix on 0.3.0.1-alpha.
8310 o Minor bugfixes (hidden service):
8311 - Clean up the code for expiring intro points with no associated
8312 circuits. It was causing, rarely, a service with some expiring
8313 introduction points to not open enough additional introduction
8314 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
8315 - Stop setting the torrc option HiddenServiceStatistics to "0" just
8316 because we're not a bridge or relay. Instead, we preserve whatever
8317 value the user set (or didn't set). Fixes bug 21150; bugfix
8319 - Resolve two possible underflows which could lead to creating and
8320 closing a lot of introduction point circuits in a non-stop loop.
8321 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
8323 o Minor bugfixes (portability):
8324 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
8325 It is supported by OpenBSD itself, and also by most OpenBSD
8326 variants (such as Bitrig). Fixes bug 20980; bugfix
8328 - When mapping a file of length greater than SIZE_MAX, do not
8329 silently truncate its contents. This issue could occur on 32 bit
8330 systems with large file support and files which are larger than 4
8331 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
8333 o Minor bugfixes (tor-resolve):
8334 - The tor-resolve command line tool now rejects hostnames over 255
8335 characters in length. Previously, it would silently truncate them,
8336 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
8337 Patch by "junglefowl".
8339 o Minor bugfixes (Windows services):
8340 - Be sure to initialize the monotonic time subsystem before using
8341 it, even when running as an NT service. Fixes bug 21356; bugfix
8345 Changes in version 0.3.0.2-alpha - 2017-01-23
8346 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
8347 cause relays and clients to crash, even if they were not built with
8348 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
8349 versions, and also affects 0.3.0.1-alpha: all relays running an affected
8350 version should upgrade.
8352 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
8353 time-to-live values, makes directory authorities enforce the 1-to-1
8354 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
8355 client-side onion service reachability bug, does better at selecting
8356 the set of fallback directories, and more.
8358 o Major bugfixes (security, also in 0.2.9.9):
8359 - Downgrade the "-ftrapv" option from "always on" to "only on when
8360 --enable-expensive-hardening is provided." This hardening option, like
8361 others, can turn survivable bugs into crashes--and having it on by
8362 default made a (relatively harmless) integer overflow bug into a
8363 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
8366 o Major features (security):
8367 - Change the algorithm used to decide DNS TTLs on client and server
8368 side, to better resist DNS-based correlation attacks like the
8369 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
8370 Feamster. Now relays only return one of two possible DNS TTL
8371 values, and clients are willing to believe DNS TTL values up to 3
8372 hours long. Closes ticket 19769.
8374 o Major features (directory authority, security):
8375 - The default for AuthDirPinKeys is now 1: directory authorities
8376 will reject relays where the RSA identity key matches a previously
8377 seen value, but the Ed25519 key has changed. Closes ticket 18319.
8379 o Major bugfixes (client, guard, crash):
8380 - In circuit_get_global_origin_list(), return the actual list of
8381 origin circuits. The previous version of this code returned the
8382 list of all the circuits, and could have caused strange bugs,
8383 including possible crashes. Fixes bug 21118; bugfix
8386 o Major bugfixes (client, onion service, also in 0.2.9.9):
8387 - Fix a client-side onion service reachability bug, where multiple
8388 socks requests to an onion service (or a single slow request)
8389 could cause us to mistakenly mark some of the service's
8390 introduction points as failed, and we cache that failure so
8391 eventually we run out and can't reach the service. Also resolves a
8392 mysterious "Remote server sent bogus reason code 65021" log
8393 warning. The bug was introduced in ticket 17218, where we tried to
8394 remember the circuit end reason as a uint16_t, which mangled
8395 negative values. Partially fixes bug 21056 and fixes bug 20307;
8396 bugfix on 0.2.8.1-alpha.
8398 o Major bugfixes (DNS):
8399 - Fix a bug that prevented exit nodes from caching DNS records for
8400 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
8402 o Minor features (controller):
8403 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
8404 shared-random values to the controller. Closes ticket 19925.
8406 o Minor features (entry guards):
8407 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
8408 break regression tests.
8409 - Require UseEntryGuards when UseBridges is set, in order to make
8410 sure bridges aren't bypassed. Resolves ticket 20502.
8412 o Minor features (fallback directories):
8413 - Select 200 fallback directories for each release. Closes
8415 - Allow 3 fallback relays per operator, which is safe now that we
8416 are choosing 200 fallback relays. Closes ticket 20912.
8417 - Exclude relays affected by bug 20499 from the fallback list.
8418 Exclude relays from the fallback list if they are running versions
8419 known to be affected by bug 20499, or if in our tests they deliver
8420 a stale consensus (i.e. one that expired more than 24 hours ago).
8421 Closes ticket 20539.
8422 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
8424 - Require fallback directories to have the same address and port for
8425 7 days (now that we have enough relays with this stability).
8426 Relays whose OnionOO stability timer is reset on restart by bug
8427 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
8428 this issue. Closes ticket 20880; maintains short-term fix
8430 - Require fallbacks to have flags for 90% of the time (weighted
8431 decaying average), rather than 95%. This allows at least 73% of
8432 clients to bootstrap in the first 5 seconds without contacting an
8433 authority. Part of ticket 18828.
8434 - Annotate updateFallbackDirs.py with the bandwidth and consensus
8435 weight for each candidate fallback. Closes ticket 20878.
8436 - Make it easier to change the output sort order of fallbacks.
8437 Closes ticket 20822.
8438 - Display the relay fingerprint when downloading consensuses from
8439 fallbacks. Closes ticket 20908.
8441 o Minor features (geoip, also in 0.2.9.9):
8442 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
8445 o Minor features (next-gen onion service directories):
8446 - Remove the "EnableOnionServicesV3" consensus parameter that we
8447 introduced in 0.3.0.1-alpha: relays are now always willing to act
8448 as v3 onion service directories. Resolves ticket 19899.
8450 o Minor features (linting):
8451 - Enhance the changes file linter to warn on Tor versions that are
8452 prefixed with "tor-". Closes ticket 21096.
8454 o Minor features (logging):
8455 - In several places, describe unset ed25519 keys as "<unset>",
8456 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
8458 o Minor bugfix (control protocol):
8459 - The reply to a "GETINFO config/names" request via the control
8460 protocol now spells the type "Dependent" correctly. This is a
8461 breaking change in the control protocol. (The field seems to be
8462 ignored by the most common known controllers.) Fixes bug 18146;
8463 bugfix on 0.1.1.4-alpha.
8465 o Minor bugfixes (bug resilience):
8466 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
8467 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
8468 Hans Jerry Illikainen.
8470 o Minor bugfixes (build):
8471 - Replace obsolete Autoconf macros with their modern equivalent and
8472 prevent similar issues in the future. Fixes bug 20990; bugfix
8475 o Minor bugfixes (client, guards):
8476 - Fix bug where Tor would think that there are circuits waiting for
8477 better guards even though those circuits have been freed. Fixes
8478 bug 21142; bugfix on 0.3.0.1-alpha.
8480 o Minor bugfixes (config):
8481 - Don't assert on startup when trying to get the options list and
8482 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
8483 options so of course they aren't ready yet. Fixes bug 21062;
8484 bugfix on 0.2.9.3-alpha.
8486 o Minor bugfixes (controller):
8487 - Make the GETINFO interface for inquiring about entry guards
8488 support the new guards backend. Fixes bug 20823; bugfix
8491 o Minor bugfixes (dead code):
8492 - Remove a redundant check for PidFile changes at runtime in
8493 options_transition_allowed(): this check is already performed
8494 regardless of whether the sandbox is active. Fixes bug 21123;
8495 bugfix on 0.2.5.4-alpha.
8497 o Minor bugfixes (documentation):
8498 - Update the tor manual page to document every option that can not
8499 be changed while tor is running. Fixes bug 21122.
8501 o Minor bugfixes (fallback directories):
8502 - Stop failing when a relay has no uptime data in
8503 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
8504 - Avoid checking fallback candidates' DirPorts if they are down in
8505 OnionOO. When a relay operator has multiple relays, this
8506 prioritizes relays that are up over relays that are down. Fixes
8507 bug 20926; bugfix on 0.2.8.3-alpha.
8508 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
8509 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
8511 o Minor bugfixes (guards, bootstrapping):
8512 - When connecting to a directory guard during bootstrap, do not mark
8513 the guard as successful until we receive a good-looking directory
8514 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
8516 o Minor bugfixes (onion services):
8517 - Fix the config reload pruning of old vs new services so it
8518 actually works when both ephemeral and non-ephemeral services are
8519 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
8520 - Allow the number of introduction points to be as low as 0, rather
8521 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
8523 o Minor bugfixes (IPv6):
8524 - Make IPv6-using clients try harder to find an IPv6 directory
8525 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
8526 - When IPv6 addresses have not been downloaded yet (microdesc
8527 consensus documents don't list relay IPv6 addresses), use hard-
8528 coded addresses for authorities, fallbacks, and configured
8529 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
8530 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
8532 o Minor bugfixes (memory leaks):
8533 - Fix a memory leak when configuring hidden services. Fixes bug
8534 20987; bugfix on 0.3.0.1-alpha.
8536 o Minor bugfixes (portability, also in 0.2.9.9):
8537 - Avoid crashing when Tor is built using headers that contain
8538 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
8539 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
8541 - Fix Libevent detection on platforms without Libevent 1 headers
8542 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
8544 o Minor bugfixes (relay):
8545 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
8546 initializing the keys would reset the DataDirectory to 0700
8547 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
8548 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
8550 o Minor bugfixes (testing):
8551 - Remove undefined behavior from the backtrace generator by removing
8552 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
8554 o Minor bugfixes (unit tests):
8555 - Allow the unit tests to pass even when DNS lookups of bogus
8556 addresses do not fail as expected. Fixes bug 20862 and 20863;
8557 bugfix on unit tests introduced in 0.2.8.1-alpha
8558 through 0.2.9.4-alpha.
8560 o Code simplification and refactoring:
8561 - Refactor code to manipulate global_origin_circuit_list into
8562 separate functions. Closes ticket 20921.
8564 o Documentation (formatting):
8565 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
8566 blocks were incorrectly appearing. Closes ticket 20885.
8568 o Documentation (man page):
8569 - Clarify many options in tor.1 and add some min/max values for
8570 HiddenService options. Closes ticket 21058.
8573 Changes in version 0.2.9.9 - 2017-01-23
8574 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
8575 cause relays and clients to crash, even if they were not built with
8576 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
8577 versions, and also affects 0.3.0.1-alpha: all relays running an affected
8578 version should upgrade.
8580 This release also resolves a client-side onion service reachability
8581 bug, and resolves a pair of small portability issues.
8583 o Major bugfixes (security):
8584 - Downgrade the "-ftrapv" option from "always on" to "only on when
8585 --enable-expensive-hardening is provided." This hardening option,
8586 like others, can turn survivable bugs into crashes -- and having
8587 it on by default made a (relatively harmless) integer overflow bug
8588 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
8589 bugfix on 0.2.9.1-alpha.
8591 o Major bugfixes (client, onion service):
8592 - Fix a client-side onion service reachability bug, where multiple
8593 socks requests to an onion service (or a single slow request)
8594 could cause us to mistakenly mark some of the service's
8595 introduction points as failed, and we cache that failure so
8596 eventually we run out and can't reach the service. Also resolves a
8597 mysterious "Remote server sent bogus reason code 65021" log
8598 warning. The bug was introduced in ticket 17218, where we tried to
8599 remember the circuit end reason as a uint16_t, which mangled
8600 negative values. Partially fixes bug 21056 and fixes bug 20307;
8601 bugfix on 0.2.8.1-alpha.
8603 o Minor features (geoip):
8604 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
8607 o Minor bugfixes (portability):
8608 - Avoid crashing when Tor is built using headers that contain
8609 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
8610 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
8612 - Fix Libevent detection on platforms without Libevent 1 headers
8613 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
8616 Changes in version 0.3.0.1-alpha - 2016-12-19
8617 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
8618 series. It strengthens Tor's link and circuit handshakes by
8619 identifying relays by their Ed25519 keys, improves the algorithm that
8620 clients use to choose and maintain their list of guards, and includes
8621 additional backend support for the next-generation hidden service
8622 design. It also contains numerous other small features and
8623 improvements to security, correctness, and performance.
8625 Below are the changes since 0.2.9.8.
8627 o Major features (guard selection algorithm):
8628 - Tor's guard selection algorithm has been redesigned from the
8629 ground up, to better support unreliable networks and restrictive
8630 sets of entry nodes, and to better resist guard-capture attacks by
8631 hostile local networks. Implements proposal 271; closes
8634 o Major features (next-generation hidden services):
8635 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
8636 prop224 aka "Next Generation Hidden Services". Service and clients
8637 don't use this functionality yet. Closes ticket 19043. Based on
8638 initial code by Alec Heifetz.
8639 - Relays now support the HSDir version 3 protocol, so that they can
8640 can store and serve v3 descriptors. This is part of the next-
8641 generation onion service work detailed in proposal 224. Closes
8644 o Major features (protocol, ed25519 identity keys):
8645 - Relays now use Ed25519 to prove their Ed25519 identities and to
8646 one another, and to clients. This algorithm is faster and more
8647 secure than the RSA-based handshake we've been doing until now.
8648 Implements the second big part of proposal 220; Closes
8650 - Clients now support including Ed25519 identity keys in the EXTEND2
8651 cells they generate. By default, this is controlled by a consensus
8652 parameter, currently disabled. You can turn this feature on for
8653 testing by setting ExtendByEd25519ID in your configuration. This
8654 might make your traffic appear different than the traffic
8655 generated by other users, however. Implements part of ticket
8656 15056; part of proposal 220.
8657 - Relays now understand requests to extend to other relays by their
8658 Ed25519 identity keys. When an Ed25519 identity key is included in
8659 an EXTEND2 cell, the relay will only extend the circuit if the
8660 other relay can prove ownership of that identity. Implements part
8661 of ticket 15056; part of proposal 220.
8663 o Major bugfixes (scheduler):
8664 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
8665 caused the channel scheduler to behave more or less randomly,
8666 rather than preferring channels with higher-priority circuits.
8667 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
8669 o Minor features (controller):
8670 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
8671 rather than "unrecognized." Closes ticket 20389; patch from
8674 o Minor features (diagnostic, directory client):
8675 - Warn when we find an unexpected inconsistency in directory
8676 download status objects. Prevents some negative consequences of
8679 o Minor features (directory authority):
8680 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
8681 default) to control whether authorities should try to probe relays
8682 by their Ed25519 link keys. This option will go away in a few
8683 releases--unless we encounter major trouble in our ed25519 link
8684 protocol rollout, in which case it will serve as a safety option.
8686 o Minor features (directory cache):
8687 - Relays and bridges will now refuse to serve the consensus they
8688 have if they know it is too old for a client to use. Closes
8691 o Minor features (ed25519 link handshake):
8692 - Advertise support for the ed25519 link handshake using the
8693 subprotocol-versions mechanism, so that clients can tell which
8694 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
8696 o Minor features (fingerprinting resistance, authentication):
8697 - Extend the length of RSA keys used for TLS link authentication to
8698 2048 bits. (These weren't used for forward secrecy; for forward
8699 secrecy, we used P256.) Closes ticket 13752.
8701 o Minor features (infrastructure):
8702 - Implement smartlist_add_strdup() function. Replaces the use of
8703 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
8705 o Minor bugfixes (client):
8706 - When clients that use bridges start up with a cached consensus on
8707 disk, they were ignoring it and downloading a new one. Now they
8708 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
8710 o Minor bugfixes (configuration):
8711 - Accept non-space whitespace characters after the severity level in
8712 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
8713 - Support "TByte" and "TBytes" units in options given in bytes.
8714 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
8715 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
8717 o Minor bugfixes (consensus weight):
8718 - Add new consensus method that initializes bw weights to 1 instead
8719 of 0. This prevents a zero weight from making it all the way to
8720 the end (happens in small testing networks) and causing an error.
8721 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
8723 o Minor bugfixes (descriptors):
8724 - Correctly recognise downloaded full descriptors as valid, even
8725 when using microdescriptors as circuits. This affects clients with
8726 FetchUselessDescriptors set, and may affect directory authorities.
8727 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
8729 o Minor bugfixes (directory system):
8730 - Download all consensus flavors, descriptors, and authority
8731 certificates when FetchUselessDescriptors is set, regardless of
8732 whether tor is a directory cache or not. Fixes bug 20667; bugfix
8733 on all recent tor versions.
8734 - Bridges and relays now use microdescriptors (like clients do)
8735 rather than old-style router descriptors. Now bridges will blend
8736 in with clients in terms of the circuits they build. Fixes bug
8737 6769; bugfix on 0.2.3.2-alpha.
8739 o Minor bugfixes (ed25519 certificates):
8740 - Correctly interpret ed25519 certificates that would expire some
8741 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
8743 o Minor bugfixes (hidden services):
8744 - Stop ignoring misconfigured hidden services. Instead, refuse to
8745 start tor until the misconfigurations have been corrected. Fixes
8746 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
8749 o Minor bugfixes (memory leak at exit):
8750 - Fix a small harmless memory leak at exit of the previously unused
8751 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
8754 o Minor bugfixes (util):
8755 - When finishing writing a file to disk, if we were about to replace
8756 the file with the temporary file created before and we fail to
8757 replace it, remove the temporary file so it doesn't stay on disk.
8758 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
8760 o Minor bugfixes (Windows):
8761 - Check for getpagesize before using it to mmap files. This fixes
8762 compilation in some MinGW environments. Fixes bug 20530; bugfix on
8763 0.1.2.1-alpha. Reported by "ice".
8765 o Code simplification and refactoring:
8766 - Abolish all global guard context in entrynodes.c; replace with new
8767 guard_selection_t structure as preparation for proposal 271.
8768 Closes ticket 19858.
8769 - Introduce rend_service_is_ephemeral() that tells if given onion
8770 service is ephemeral. Replace unclear NULL-checkings for service
8771 directory with this function. Closes ticket 20526.
8772 - Extract magic numbers in circuituse.c into defined variables.
8773 - Refactor circuit_is_available_for_use to remove unnecessary check.
8774 - Refactor circuit_predict_and_launch_new for readability and
8775 testability. Closes ticket 18873.
8776 - Refactor large if statement in purpose_needs_anonymity to use
8777 switch statement instead. Closes part of ticket 20077.
8778 - Refactor the hashing API to return negative values for errors, as
8779 is done as throughout the codebase. Closes ticket 20717.
8780 - Remove data structures that were used to index or_connection
8781 objects by their RSA identity digests. These structures are fully
8782 redundant with the similar structures used in the
8783 channel abstraction.
8784 - Remove duplicate code in the channel_write_*cell() functions.
8785 Closes ticket 13827; patch from Pingl.
8786 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
8787 use only purpose_needs_anonymity. Closes part of ticket 20077.
8788 - The code to generate and parse EXTEND and EXTEND2 cells has been
8789 replaced with code automatically generated by the
8793 - Include the "TBits" unit in Tor's man page. Fixes part of bug
8794 20622; bugfix on 0.2.5.1-alpha.
8795 - Change '1' to 'weight_scale' in consensus bw weights calculation
8796 comments, as that is reality. Closes ticket 20273. Patch
8798 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
8799 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
8801 - Stop the man page from incorrectly stating that HiddenServiceDir
8802 must already exist. Fixes 20486.
8803 - Clarify that when ClientRejectInternalAddresses is enabled (which
8804 is the default), multicast DNS hostnames for machines on the local
8805 network (of the form *.local) are also rejected. Closes
8809 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
8810 limit for relays running on a single IP applies to authority IP
8811 addresses as well as to non-authority IP addresses. Closes
8813 - The UseDirectoryGuards torrc option no longer exists: all users
8814 that use entry guards will also use directory guards. Related to
8815 proposal 271; implements part of ticket 20831.
8818 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
8819 from "overcaffeinated".
8820 - Perform the coding style checks when running the tests and fail
8821 when coding style violations are found. Closes ticket 5500.
8822 - Add tests for networkstatus_compute_bw_weights_v10.
8823 - Add unit tests circuit_predict_and_launch_new.
8824 - Extract dummy_origin_circuit_new so it can be used by other
8828 Changes in version 0.2.8.12 - 2016-12-19
8829 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
8830 below) where Tor clients could crash when attempting to visit a
8831 hostile hidden service. Clients are recommended to upgrade as packages
8832 become available for their systems.
8834 It also includes an updated list of fallback directories, backported
8837 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
8838 backported to 0.2.8 in the future.
8840 o Major bugfixes (parsing, security, backported from 0.2.9.8):
8841 - Fix a bug in parsing that could cause clients to read a single
8842 byte past the end of an allocated region. This bug could be used
8843 to cause hardened clients (built with --enable-expensive-hardening)
8844 to crash if they tried to visit a hostile hidden service. Non-
8845 hardened clients are only affected depending on the details of
8846 their platform's memory allocator. Fixes bug 21018; bugfix on
8847 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8848 2016-12-002 and as CVE-2016-1254.
8850 o Minor features (fallback directory list, backported from 0.2.9.8):
8851 - Replace the 81 remaining fallbacks of the 100 originally
8852 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
8853 fallbacks (123 new, 54 existing, 27 removed) generated in December
8854 2016. Resolves ticket 20170.
8856 o Minor features (geoip, backported from 0.2.9.7-rc):
8857 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
8861 Changes in version 0.2.9.8 - 2016-12-19
8862 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
8864 The Tor 0.2.9 series makes mandatory a number of security features
8865 that were formerly optional. It includes support for a new shared-
8866 randomness protocol that will form the basis for next generation
8867 hidden services, includes a single-hop hidden service mode for
8868 optimizing .onion services that don't actually want to be hidden,
8869 tries harder not to overload the directory authorities with excessive
8870 downloads, and supports a better protocol versioning scheme for
8871 improved compatibility with other implementations of the Tor protocol.
8873 And of course, there are numerous other bugfixes and improvements.
8875 This release also includes a fix for a medium-severity issue (bug
8876 21018 below) where Tor clients could crash when attempting to visit a
8877 hostile hidden service. Clients are recommended to upgrade as packages
8878 become available for their systems.
8880 Below are the changes since 0.2.9.7-rc. For a list of all changes
8881 since 0.2.8, see the ReleaseNotes file.
8883 o Major bugfixes (parsing, security):
8884 - Fix a bug in parsing that could cause clients to read a single
8885 byte past the end of an allocated region. This bug could be used
8886 to cause hardened clients (built with --enable-expensive-hardening)
8887 to crash if they tried to visit a hostile hidden service. Non-
8888 hardened clients are only affected depending on the details of
8889 their platform's memory allocator. Fixes bug 21018; bugfix on
8890 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8891 2016-12-002 and as CVE-2016-1254.
8893 o Minor features (fallback directory list):
8894 - Replace the 81 remaining fallbacks of the 100 originally
8895 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
8896 fallbacks (123 new, 54 existing, 27 removed) generated in December
8897 2016. Resolves ticket 20170.
8900 Changes in version 0.2.9.7-rc - 2016-12-12
8901 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
8902 including a few that had prevented tests from passing on
8905 o Minor features (geoip):
8906 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
8909 o Minor bugfix (build):
8910 - The current Git revision when building from a local repository is
8911 now detected correctly when using git worktrees. Fixes bug 20492;
8912 bugfix on 0.2.3.9-alpha.
8914 o Minor bugfixes (directory authority):
8915 - When computing old Tor protocol line version in protover, we were
8916 looking at 0.2.7.5 twice instead of a specific case for
8917 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
8919 o Minor bugfixes (download scheduling):
8920 - Resolve a "bug" warning when considering a download schedule whose
8921 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
8923 o Minor bugfixes (logging):
8924 - Downgrade a harmless log message about the
8925 pending_entry_connections list from "warn" to "info". Mitigates
8928 o Minor bugfixes (memory leak):
8929 - Fix a small memory leak when receiving AF_UNIX connections on a
8930 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
8931 - When moving a signed descriptor object from a source to an
8932 existing destination, free the allocated memory inside that
8933 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
8935 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
8936 - Fix a memory leak and use-after-free error when removing entries
8937 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
8938 0.2.5.5-alpha. Patch from "cypherpunks".
8940 o Minor bugfixes (portability):
8941 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
8942 Fixes bug 20935; bugfix on 0.2.9.6-rc.
8944 o Minor bugfixes (unit tests):
8945 - Stop expecting NetBSD unit tests to report success for ipfw. Part
8946 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
8947 - Fix tolerances in unit tests for monotonic time comparisons
8948 between nanoseconds and microseconds. Previously, we accepted a 10
8949 us difference only, which is not realistic on every platform's
8950 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
8951 - Remove a double-free in the single onion service unit test. Stop
8952 ignoring a return value. Make future changes less error-prone.
8953 Fixes bug 20864; bugfix on 0.2.9.6-rc.
8956 Changes in version 0.2.8.11 - 2016-12-08
8957 Tor 0.2.8.11 backports fixes for additional portability issues that
8958 could prevent Tor from building correctly on OSX Sierra, or with
8959 OpenSSL 1.1. Affected users should upgrade; others can safely stay
8962 o Minor bugfixes (portability):
8963 - Avoid compilation errors when building on OSX Sierra. Sierra began
8964 to support the getentropy() and clock_gettime() APIs, but created
8965 a few problems in doing so. Tor 0.2.9 has a more thorough set of
8966 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
8967 monotonic time interfaces. Fixes bug 20865. Bugfix
8970 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
8971 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
8972 architectures. Closes ticket 20588.
8975 Changes in version 0.2.8.10 - 2016-12-02
8976 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
8977 unusable after they left standby mode. It also backports fixes for
8978 a few portability issues and a small but problematic memory leak.
8980 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
8981 - When Tor leaves standby because of a new application request, open
8982 circuits as needed to serve that request. Previously, we would
8983 potentially wait a very long time. Fixes part of bug 19969; bugfix
8986 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
8987 - Clients now respond to new application stream requests immediately
8988 when they arrive, rather than waiting up to one second before
8989 starting to handle them. Fixes part of bug 19969; bugfix
8992 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
8993 - Work around a bug in the OSX 10.12 SDK that would prevent us from
8994 successfully targeting earlier versions of OSX. Resolves
8997 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
8998 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
8999 20551; bugfix on 0.2.1.1-alpha.
9001 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
9002 - Work around a memory leak in OpenSSL 1.1 when encoding public
9003 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
9005 o Minor features (geoip):
9006 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
9009 Changes in version 0.2.9.6-rc - 2016-12-02
9010 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
9011 version. We hope that it will be ready to become stable soon, and we
9012 encourage everyone to test this release. If no showstopper bugs are
9013 found here, the next 0.2.9 release will be stable.
9015 o Major bugfixes (relay, resolver, logging):
9016 - For relays that don't know their own address, avoid attempting a
9017 local hostname resolve for each descriptor we download. This
9018 will cut down on the number of "Success: chose address 'x.x.x.x'"
9019 log lines, and also avoid confusing clock jumps if the resolver
9020 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
9022 o Minor bugfixes (client, fascistfirewall):
9023 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
9024 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
9026 o Minor bugfixes (hidden services):
9027 - Stop ignoring the anonymity status of saved keys for hidden
9028 services and single onion services when first starting tor.
9029 Instead, refuse to start tor if any hidden service key has been
9030 used in a different hidden service anonymity mode. Fixes bug
9031 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
9033 o Minor bugfixes (portability):
9034 - Work around a bug in the OSX 10.12 SDK that would prevent us from
9035 successfully targeting earlier versions of OSX. Resolves
9037 - Run correctly when built on Windows build environments that
9038 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
9040 o Minor bugfixes (single onion services, Tor2web):
9041 - Stop complaining about long-term one-hop circuits deliberately
9042 created by single onion services and Tor2web. These log messages
9043 are intended to diagnose issue 8387, which relates to circuits
9044 hanging around forever for no reason. Fixes bug 20613; bugfix on
9045 0.2.9.1-alpha. Reported by "pastly".
9047 o Minor bugfixes (unit tests):
9048 - Stop spurious failures in the local interface address discovery
9049 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
9053 - Correct the minimum bandwidth value in torrc.sample, and queue a
9054 corresponding change for torrc.minimal. Closes ticket 20085.
9057 Changes in version 0.2.9.5-alpha - 2016-11-08
9058 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
9059 version. We believe one or two probably remain, and we encourage
9060 everyone to test this release.
9062 o Major bugfixes (client performance):
9063 - Clients now respond to new application stream requests immediately
9064 when they arrive, rather than waiting up to one second before
9065 starting to handle them. Fixes part of bug 19969; bugfix
9068 o Major bugfixes (client reliability):
9069 - When Tor leaves standby because of a new application request, open
9070 circuits as needed to serve that request. Previously, we would
9071 potentially wait a very long time. Fixes part of bug 19969; bugfix
9074 o Major bugfixes (download scheduling):
9075 - When using an exponential backoff schedule, do not give up on
9076 downloading just because we have failed a bunch of times. Since
9077 each delay is longer than the last, retrying indefinitely won't
9078 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
9079 - If a consensus expires while we are waiting for certificates to
9080 download, stop waiting for certificates.
9081 - If we stop waiting for certificates less than a minute after we
9082 started downloading them, do not consider the certificate download
9083 failure a separate failure. Fixes bug 20533; bugfix
9085 - Remove the maximum delay on exponential-backoff scheduling. Since
9086 we now allow an infinite number of failures (see ticket 20536), we
9087 must now allow the time to grow longer on each failure. Fixes part
9088 of bug 20534; bugfix on 0.2.9.1-alpha.
9089 - Make our initial download delays closer to those from 0.2.8. Fixes
9090 another part of bug 20534; bugfix on 0.2.9.1-alpha.
9091 - When determining when to download a directory object, handle times
9092 after 2038 if the operating system supports them. (Someday this
9093 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
9094 - When using exponential backoff in test networks, use a lower
9095 exponent, so the delays do not vary as much. This helps test
9096 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
9098 o Minor features (geoip):
9099 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
9102 o Minor bugfixes (client directory scheduling):
9103 - Treat "relay too busy to answer request" as a failed request and a
9104 reason to back off on our retry frequency. This is safe now that
9105 exponential backoffs retry indefinitely, and avoids a bug where we
9106 would reset our download schedule erroneously. Fixes bug 20593;
9107 bugfix on 0.2.9.1-alpha.
9109 o Minor bugfixes (client, logging):
9110 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
9111 assume all nodes support EXTEND2. Use ntor whenever a key is
9112 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
9113 - On DNSPort, stop logging a BUG warning on a failed hostname
9114 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
9116 o Minor bugfixes (hidden services):
9117 - When configuring hidden services, check every hidden service
9118 directory's permissions. Previously, we only checked the last
9119 hidden service. Fixes bug 20529; bugfix the work to fix 13942
9122 o Minor bugfixes (portability):
9123 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
9124 architectures. Closes ticket 20588.
9125 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
9126 removed the ECDH ciphers which caused the tests to fail on
9127 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
9128 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
9129 20551; bugfix on 0.2.1.1-alpha.
9131 o Minor bugfixes (relay bootstrap):
9132 - Ensure relays don't make multiple connections during bootstrap.
9133 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
9135 o Minor bugfixes (relay):
9136 - Work around a memory leak in OpenSSL 1.1 when encoding public
9137 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
9138 - Avoid a small memory leak when informing worker threads about
9139 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
9140 - Do not try to parallelize workers more than 16x without the user
9141 explicitly configuring us to do so, even if we do detect more than
9142 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
9144 o Minor bugfixes (single onion services):
9145 - Start correctly when creating a single onion service in a
9146 directory that did not previously exist. Fixes bug 20484; bugfix
9149 o Minor bugfixes (testing):
9150 - Avoid a unit test failure on systems with over 16 detectable CPU
9151 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
9154 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
9155 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
9156 - Module-level documentation for several more modules. Closes
9157 tickets 19287 and 19290.
9160 Changes in version 0.2.8.9 - 2016-10-17
9161 Tor 0.2.8.9 backports a fix for a security hole in previous versions
9162 of Tor that would allow a remote attacker to crash a Tor client,
9163 hidden service, relay, or authority. All Tor users should upgrade to
9164 this version, or to 0.2.9.4-alpha. Patches will be released for older
9167 o Major features (security fixes, also in 0.2.9.4-alpha):
9168 - Prevent a class of security bugs caused by treating the contents
9169 of a buffer chunk as if they were a NUL-terminated string. At
9170 least one such bug seems to be present in all currently used
9171 versions of Tor, and would allow an attacker to remotely crash
9172 most Tor instances, especially those compiled with extra compiler
9173 hardening. With this defense in place, such bugs can't crash Tor,
9174 though we should still fix them as they occur. Closes ticket
9175 20384 (TROVE-2016-10-001).
9177 o Minor features (geoip):
9178 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
9182 Changes in version 0.2.9.4-alpha - 2016-10-17
9183 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
9184 that would allow a remote attacker to crash a Tor client, hidden
9185 service, relay, or authority. All Tor users should upgrade to this
9186 version, or to 0.2.8.9. Patches will be released for older versions
9189 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
9190 previous versions of Tor, including the implementation of a feature to
9191 future- proof the Tor ecosystem against protocol changes, some bug
9192 fixes necessary for Tor Browser to use unix domain sockets correctly,
9193 and several portability improvements. We anticipate that this will be
9194 the last alpha in the Tor 0.2.9 series, and that the next release will
9195 be a release candidate.
9197 o Major features (security fixes):
9198 - Prevent a class of security bugs caused by treating the contents
9199 of a buffer chunk as if they were a NUL-terminated string. At
9200 least one such bug seems to be present in all currently used
9201 versions of Tor, and would allow an attacker to remotely crash
9202 most Tor instances, especially those compiled with extra compiler
9203 hardening. With this defense in place, such bugs can't crash Tor,
9204 though we should still fix them as they occur. Closes ticket
9205 20384 (TROVE-2016-10-001).
9207 o Major features (subprotocol versions):
9208 - Tor directory authorities now vote on a set of recommended
9209 subprotocol versions, and on a set of required subprotocol
9210 versions. Clients and relays that lack support for a _required_
9211 subprotocol version will not start; those that lack support for a
9212 _recommended_ subprotocol version will warn the user to upgrade.
9213 Closes ticket 19958; implements part of proposal 264.
9214 - Tor now uses "subprotocol versions" to indicate compatibility.
9215 Previously, versions of Tor looked at the declared Tor version of
9216 a relay to tell whether they could use a given feature. Now, they
9217 should be able to rely on its declared subprotocol versions. This
9218 change allows compatible implementations of the Tor protocol(s) to
9219 exist without pretending to be 100% bug-compatible with particular
9220 releases of Tor itself. Closes ticket 19958; implements part of
9223 o Minor feature (fallback directories):
9224 - Remove broken fallbacks from the hard-coded fallback directory
9225 list. Closes ticket 20190; patch by teor.
9227 o Minor features (client, directory):
9228 - Since authorities now omit all routers that lack the Running and
9229 Valid flags, we assume that any relay listed in the consensus must
9230 have those flags. Closes ticket 20001; implements part of
9233 o Minor features (compilation, portability):
9234 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
9237 o Minor features (development tools, etags):
9238 - Teach the "make tags" Makefile target how to correctly find
9239 "MOCK_IMPL" function definitions. Patch from nherring; closes
9242 o Minor features (geoip):
9243 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
9246 o Minor features (unix domain sockets):
9247 - When configuring a unix domain socket for a SocksPort,
9248 ControlPort, or Hidden service, you can now wrap the address in
9249 quotes, using C-style escapes inside the quotes. This allows unix
9250 domain socket paths to contain spaces.
9252 o Minor features (virtual addresses):
9253 - Increase the maximum number of bits for the IPv6 virtual network
9254 prefix from 16 to 104. In this way, the condition for address
9255 allocation is less restrictive. Closes ticket 20151; feature
9258 o Minor bugfixes (address discovery):
9259 - Stop reordering IP addresses returned by the OS. This makes it
9260 more likely that Tor will guess the same relay IP address every
9261 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
9262 Reported by René Mayrhofer, patch by "cypherpunks".
9264 o Minor bugfixes (client, unix domain sockets):
9265 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
9266 the client address is meaningless. Fixes bug 20261; bugfix
9269 o Minor bugfixes (compilation, OpenBSD):
9270 - Detect Libevent2 functions correctly on systems that provide
9271 libevent2, but where libevent1 is linked with -levent. Fixes bug
9272 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
9274 o Minor bugfixes (configuration):
9275 - When parsing quoted configuration values from the torrc file,
9276 handle windows line endings correctly. Fixes bug 19167; bugfix on
9277 0.2.0.16-alpha. Patch from "Pingl".
9279 o Minor bugfixes (getpass):
9280 - Defensively fix a non-triggerable heap corruption at do_getpass()
9281 to protect ourselves from mistakes in the future. Fixes bug
9282 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
9285 o Minor bugfixes (hidden service):
9286 - Allow hidden services to run on IPv6 addresses even when the
9287 IPv6Exit option is not set. Fixes bug 18357; bugfix
9291 - Add module-level internal documentation for 36 C files that
9292 previously didn't have a high-level overview. Closes ticket #20385.
9294 o Required libraries:
9295 - When building with OpenSSL, Tor now requires version 1.0.1 or
9296 later. OpenSSL 1.0.0 and earlier are no longer supported by the
9297 OpenSSL team, and should not be used. Closes ticket 20303.
9300 Changes in version 0.2.9.3-alpha - 2016-09-23
9301 Tor 0.2.9.3-alpha adds improved support for entities that want to make
9302 high-performance services available through the Tor .onion mechanism
9303 without themselves receiving anonymity as they host those services. It
9304 also tries harder to ensure that all steps on a circuit are using the
9305 strongest crypto possible, strengthens some TLS properties, and
9306 resolves several bugs -- including a pair of crash bugs from the 0.2.8
9307 series. Anybody running an earlier version of 0.2.9.x should upgrade.
9309 o Major bugfixes (crash, also in 0.2.8.8):
9310 - Fix a complicated crash bug that could affect Tor clients
9311 configured to use bridges when replacing a networkstatus consensus
9312 in which one of their bridges was mentioned. OpenBSD users saw
9313 more crashes here, but all platforms were potentially affected.
9314 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
9316 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
9317 - Fix a timing-dependent assertion failure that could occur when we
9318 tried to flush from a circuit after having freed its cells because
9319 of an out-of-memory condition. Fixes bug 20203; bugfix on
9320 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
9323 o Major features (circuit building, security):
9324 - Authorities, relays and clients now require ntor keys in all
9325 descriptors, for all hops (except for rare hidden service protocol
9326 cases), for all circuits, and for all other roles. Part of
9328 - Tor authorities, relays, and clients only use ntor, except for
9329 rare cases in the hidden service protocol. Part of ticket 19163.
9331 o Major features (single-hop "hidden" services):
9332 - Add experimental HiddenServiceSingleHopMode and
9333 HiddenServiceNonAnonymousMode options. When both are set to 1,
9334 every hidden service on a Tor instance becomes a non-anonymous
9335 Single Onion Service. Single Onions make one-hop (direct)
9336 connections to their introduction and renzedvous points. One-hop
9337 circuits make Single Onion servers easily locatable, but clients
9338 remain location-anonymous. This is compatible with the existing
9339 hidden service implementation, and works on the current tor
9340 network without any changes to older relays or clients. Implements
9341 proposal 260, completes ticket 17178. Patch by teor and asn.
9343 o Major features (resource management):
9344 - Tor can now notice it is about to run out of sockets, and
9345 preemptively close connections of lower priority. (This feature is
9346 off by default for now, since the current prioritizing method is
9347 yet not mature enough. You can enable it by setting
9348 "DisableOOSCheck 0", but watch out: it might close some sockets
9349 you would rather have it keep.) Closes ticket 18640.
9351 o Major bugfixes (circuit building):
9352 - Hidden service client-to-intro-point and service-to-rendezvous-
9353 point circuits use the TAP key supplied by the protocol, to avoid
9354 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
9356 o Major bugfixes (compilation, OpenBSD):
9357 - Fix a Libevent-detection bug in our autoconf script that would
9358 prevent Tor from linking successfully on OpenBSD. Patch from
9359 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
9361 o Major bugfixes (hidden services):
9362 - Clients now require hidden services to include the TAP keys for
9363 their intro points in the hidden service descriptor. This prevents
9364 an inadvertent upgrade to ntor, which a malicious hidden service
9365 could use to distinguish clients by consensus version. Fixes bug
9366 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
9368 o Minor features (security, TLS):
9369 - Servers no longer support clients that without AES ciphersuites.
9370 (3DES is no longer considered an acceptable cipher.) We believe
9371 that no such Tor clients currently exist, since Tor has required
9372 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
9374 o Minor feature (fallback directories):
9375 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
9376 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
9377 2016. Closes ticket 20190; patch by teor.
9379 o Minor features (geoip, also in 0.2.8.8):
9380 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
9383 o Minor feature (port flags):
9384 - Add new flags to the *Port options to finer control over which
9385 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
9386 and the synthetic flag OnionTrafficOnly, which is equivalent to
9387 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
9388 18693; patch by "teor".
9390 o Minor features (directory authority):
9391 - After voting, if the authorities decide that a relay is not
9392 "Valid", they no longer include it in the consensus at all. Closes
9393 ticket 20002; implements part of proposal 272.
9395 o Minor features (testing):
9396 - Disable memory protections on OpenBSD when performing our unit
9397 tests for memwipe(). The test deliberately invokes undefined
9398 behavior, and the OpenBSD protections interfere with this. Patch
9399 from "rubiate". Closes ticket 20066.
9401 o Minor features (testing, ipv6):
9402 - Add the single-onion and single-onion-ipv6 chutney targets to
9403 "make test-network-all". This requires a recent chutney version
9404 with the single onion network flavours (git c72a652 or later).
9405 Closes ticket 20072; patch by teor.
9406 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
9407 tests. Remove bridges+hs, as it's somewhat redundant. This
9408 requires a recent chutney version that supports IPv6 clients,
9409 relays, and authorities. Closes ticket 20069; patch by teor.
9411 o Minor features (Tor2web):
9412 - Make Tor2web clients respect ReachableAddresses. This feature was
9413 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
9414 0.2.8.7. Implements feature 20034. Patch by teor.
9416 o Minor features (unit tests):
9417 - We've done significant work to make the unit tests run faster.
9418 - Our link-handshake unit tests now check that when invalid
9419 handshakes fail, they fail with the error messages we expected.
9420 - Our unit testing code that captures log messages no longer
9421 prevents them from being written out if the user asked for them
9422 (by passing --debug or --info or or --notice --warn to the "test"
9423 binary). This change prevents us from missing unexpected log
9424 messages simply because we were looking for others. Related to
9426 - The unit tests now log all warning messages with the "BUG" flag.
9427 Previously, they only logged errors by default. This change will
9428 help us make our testing code more correct, and make sure that we
9429 only hit this code when we mean to. In the meantime, however,
9430 there will be more warnings in the unit test logs than before.
9431 This is preparatory work for ticket 19999.
9432 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
9433 assertion as a test failure.
9435 o Minor bug fixes (circuits):
9436 - Use the CircuitBuildTimeout option whenever
9437 LearnCircuitBuildTimeout is disabled. Previously, we would respect
9438 the option when a user disabled it, but not when it was disabled
9439 because some other option was set. Fixes bug 20073; bugfix on
9440 0.2.4.12-alpha. Patch by teor.
9442 o Minor bugfixes (allocation):
9443 - Change how we allocate memory for large chunks on buffers, to
9444 avoid a (currently impossible) integer overflow, and to waste less
9445 space when allocating unusually large chunks. Fixes bug 20081;
9446 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
9447 - Always include orconfig.h before including any other C headers.
9448 Sometimes, it includes macros that affect the behavior of the
9449 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
9450 first version to use AC_USE_SYSTEM_EXTENSIONS).
9451 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
9452 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
9453 Patch from Gisle Vanem.
9454 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
9455 They apparently require a set of annotations that we aren't
9456 currently using, and they create false positives in our pthreads
9457 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
9459 o Minor bugfixes (directory authority):
9460 - Die with a more useful error when the operator forgets to place
9461 the authority_signing_key file into the keys directory. This
9462 avoids an uninformative assert & traceback about having an invalid
9463 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
9464 - When allowing private addresses, mark Exits that only exit to
9465 private locations as such. Fixes bug 20064; bugfix
9468 o Minor bugfixes (documentation):
9469 - Document the default PathsNeededToBuildCircuits value that's used
9470 by clients when the directory authorities don't set
9471 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
9472 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
9473 - Fix manual for the User option: it takes a username, not a UID.
9474 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
9477 o Minor bugfixes (hidden services):
9478 - Stop logging intro point details to the client log on certain
9479 error conditions. Fixed as part of bug 20012; bugfix on
9480 0.2.4.8-alpha. Patch by teor.
9482 o Minor bugfixes (IPv6, testing):
9483 - Check for IPv6 correctly on Linux when running test networks.
9484 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
9486 o Minor bugfixes (Linux seccomp2 sandbox):
9487 - Add permission to run the sched_yield() and sigaltstack() system
9488 calls, in order to support versions of Tor compiled with asan or
9489 ubsan code that use these calls. Now "sandbox 1" and
9490 "--enable-expensive-hardening" should be compatible on more
9491 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
9493 o Minor bugfixes (logging):
9494 - When logging a message from the BUG() macro, be explicit about
9495 what we were asserting. Previously we were confusing what we were
9496 asserting with what the bug was. Fixes bug 20093; bugfix
9498 - When we are unable to remove the bw_accounting file, do not warn
9499 if the reason we couldn't remove it was that it didn't exist.
9500 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
9502 o Minor bugfixes (option parsing):
9503 - Count unix sockets when counting client listeners (SOCKS, Trans,
9504 NATD, and DNS). This has no user-visible behaviour changes: these
9505 options are set once, and never read. Required for correct
9506 behaviour in ticket 17178. Fixes bug 19677; bugfix on
9507 0.2.6.3-alpha. Patch by teor.
9509 o Minor bugfixes (options):
9510 - Check the consistency of UseEntryGuards and EntryNodes more
9511 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
9513 - Stop changing the configured value of UseEntryGuards on
9514 authorities and Tor2web clients. Fixes bug 20074; bugfix on
9515 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
9518 o Minor bugfixes (Tor2web):
9519 - Prevent Tor2web clients running hidden services, these services
9520 are not anonymous due to the one-hop client paths. Fixes bug
9521 19678. Patch by teor.
9523 o Minor bugfixes (unit tests):
9524 - Fix a shared-random unit test that was failing on big endian
9525 architectures due to internal representation of a integer copied
9526 to a buffer. The test is changed to take a full 32 bytes of data
9527 and use the output of a python script that make the COMMIT and
9528 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
9530 - The tor_tls_server_info_callback unit test no longer crashes when
9531 debug-level logging is turned on. Fixes bug 20041; bugfix
9535 Changes in version 0.2.8.8 - 2016-09-23
9536 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
9537 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
9538 who select public relays as their bridges.
9540 o Major bugfixes (crash):
9541 - Fix a complicated crash bug that could affect Tor clients
9542 configured to use bridges when replacing a networkstatus consensus
9543 in which one of their bridges was mentioned. OpenBSD users saw
9544 more crashes here, but all platforms were potentially affected.
9545 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
9547 o Major bugfixes (relay, OOM handler):
9548 - Fix a timing-dependent assertion failure that could occur when we
9549 tried to flush from a circuit after having freed its cells because
9550 of an out-of-memory condition. Fixes bug 20203; bugfix on
9551 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
9554 o Minor feature (fallback directories):
9555 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
9556 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
9557 2016. Closes ticket 20190; patch by teor.
9559 o Minor features (geoip):
9560 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
9564 Changes in version 0.2.9.2-alpha - 2016-08-24
9565 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
9566 several new features and bugfixes. It also includes an important
9567 authority update and an important bugfix from 0.2.8.7. Everyone who
9568 sets the ReachableAddresses option, and all bridges, are strongly
9569 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
9571 o Directory authority changes (also in 0.2.8.7):
9572 - The "Tonga" bridge authority has been retired; the new bridge
9573 authority is "Bifroest". Closes tickets 19728 and 19690.
9575 o Major bugfixes (client, security, also in 0.2.8.7):
9576 - Only use the ReachableAddresses option to restrict the first hop
9577 in a path. In earlier versions of 0.2.8.x, it would apply to
9578 every hop in the path, with a possible degradation in anonymity
9579 for anyone using an uncommon ReachableAddress setting. Fixes bug
9580 19973; bugfix on 0.2.8.2-alpha.
9582 o Major features (user interface):
9583 - Tor now supports the ability to declare options deprecated, so
9584 that we can recommend that people stop using them. Previously,
9585 this was done in an ad-hoc way. Closes ticket 19820.
9587 o Major bugfixes (directory downloads):
9588 - Avoid resetting download status for consensuses hourly, since we
9589 already have another, smarter retry mechanism. Fixes bug 8625;
9590 bugfix on 0.2.0.9-alpha.
9592 o Minor features (config):
9593 - Warn users when descriptor and port addresses are inconsistent.
9594 Mitigates bug 13953; patch by teor.
9596 o Minor features (geoip):
9597 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
9600 o Minor features (user interface):
9601 - There is a new --list-deprecated-options command-line option to
9602 list all of the deprecated options. Implemented as part of
9605 o Minor bugfixes (code style):
9606 - Fix an integer signedness conversion issue in the case conversion
9607 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
9609 o Minor bugfixes (compilation):
9610 - Build correctly on versions of libevent2 without support for
9611 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
9613 - Fix a compilation warning on GCC versions before 4.6. Our
9614 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
9615 when it is also required as an argument to the compiler pragma.
9616 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
9618 o Minor bugfixes (compilation, also in 0.2.8.7):
9619 - Remove an inappropriate "inline" in tortls.c that was causing
9620 warnings on older versions of GCC. Fixes bug 19903; bugfix
9623 o Minor bugfixes (fallback directories, also in 0.2.8.7):
9624 - Avoid logging a NULL string pointer when loading fallback
9625 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
9626 and 0.2.8.1-alpha. Report and patch by "rubiate".
9628 o Minor bugfixes (logging):
9629 - Log a more accurate message when we fail to dump a microdescriptor.
9630 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
9632 o Minor bugfixes (memory leak):
9633 - Fix a series of slow memory leaks related to parsing torrc files
9634 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
9636 o Deprecated features:
9637 - A number of DNS-cache-related sub-options for client ports are now
9638 deprecated for security reasons, and may be removed in a future
9639 version of Tor. (We believe that client-side DNS caching is a bad
9640 idea for anonymity, and you should not turn it on.) The options
9641 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
9642 UseIPv4Cache, and UseIPv6Cache.
9643 - A number of options are deprecated for security reasons, and may
9644 be removed in a future version of Tor. The options are:
9645 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
9646 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
9647 CloseHSClientCircuitsImmediatelyOnTimeout,
9648 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
9649 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
9650 UseNTorHandshake, and WarnUnsafeSocks.
9651 - The *ListenAddress options are now deprecated as unnecessary: the
9652 corresponding *Port options should be used instead. These options
9653 may someday be removed. The affected options are:
9654 ControlListenAddress, DNSListenAddress, DirListenAddress,
9655 NATDListenAddress, ORListenAddress, SocksListenAddress,
9656 and TransListenAddress.
9659 - Correct the IPv6 syntax in our documentation for the
9660 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
9663 - We no longer include the (dead, deprecated) bufferevent code in
9664 Tor. Closes ticket 19450. Based on a patch from U+039b.
9667 Changes in version 0.2.8.7 - 2016-08-24
9668 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
9669 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
9670 who sets the ReachableAddresses option, and all bridges, are strongly
9671 encouraged to upgrade.
9673 o Directory authority changes:
9674 - The "Tonga" bridge authority has been retired; the new bridge
9675 authority is "Bifroest". Closes tickets 19728 and 19690.
9677 o Major bugfixes (client, security):
9678 - Only use the ReachableAddresses option to restrict the first hop
9679 in a path. In earlier versions of 0.2.8.x, it would apply to
9680 every hop in the path, with a possible degradation in anonymity
9681 for anyone using an uncommon ReachableAddress setting. Fixes bug
9682 19973; bugfix on 0.2.8.2-alpha.
9684 o Minor features (geoip):
9685 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
9688 o Minor bugfixes (compilation):
9689 - Remove an inappropriate "inline" in tortls.c that was causing
9690 warnings on older versions of GCC. Fixes bug 19903; bugfix
9693 o Minor bugfixes (fallback directories):
9694 - Avoid logging a NULL string pointer when loading fallback
9695 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
9696 and 0.2.8.1-alpha. Report and patch by "rubiate".
9699 Changes in version 0.2.9.1-alpha - 2016-08-08
9700 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
9701 series. It improves our support for hardened builds and compiler
9702 warnings, deploys some critical infrastructure for improvements to
9703 hidden services, includes a new timing backend that we hope to use for
9704 better support for traffic padding, makes it easier for programmers to
9705 log unexpected events, and contains other small improvements to
9706 security, correctness, and performance.
9708 Below are the changes since 0.2.8.6.
9710 o New system requirements:
9711 - Tor now requires Libevent version 2.0.10-stable or later. Older
9712 versions of Libevent have less efficient backends for several
9713 platforms, and lack the DNS code that we use for our server-side
9714 DNS support. This implements ticket 19554.
9715 - Tor now requires zlib version 1.2 or later, for security,
9716 efficiency, and (eventually) gzip support. (Back when we started,
9717 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
9718 released in 2003. We recommend the latest version.)
9720 o Major features (build, hardening):
9721 - Tor now builds with -ftrapv by default on compilers that support
9722 it. This option detects signed integer overflow (which C forbids),
9723 and turns it into a hard-failure. We do not apply this option to
9724 code that needs to run in constant time to avoid side-channels;
9725 instead, we use -fwrapv in that code. Closes ticket 17983.
9726 - When --enable-expensive-hardening is selected, stop applying the
9727 clang/gcc sanitizers to code that needs to run in constant time.
9728 Although we are aware of no introduced side-channels, we are not
9729 able to prove that there are none. Related to ticket 17983.
9731 o Major features (compilation):
9732 - Our big list of extra GCC warnings is now enabled by default when
9733 building with GCC (or with anything like Clang that claims to be
9734 GCC-compatible). To make all warnings into fatal compilation
9735 errors, pass --enable-fatal-warnings to configure. Closes
9737 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
9738 turn on C and POSIX extensions. (Previously, we attempted to do
9739 this on an ad hoc basis.) Closes ticket 19139.
9741 o Major features (directory authorities, hidden services):
9742 - Directory authorities can now perform the shared randomness
9743 protocol specified by proposal 250. Using this protocol, directory
9744 authorities generate a global fresh random value every day. In the
9745 future, this value will be used by hidden services to select
9746 HSDirs. This release implements the directory authority feature;
9747 the hidden service side will be implemented in the future as part
9748 of proposal 224. Resolves ticket 16943; implements proposal 250.
9750 o Major features (downloading, random exponential backoff):
9751 - When we fail to download an object from a directory service, wait
9752 for an (exponentially increasing) randomized amount of time before
9753 retrying, rather than a fixed interval as we did before. This
9754 prevents a group of Tor instances from becoming too synchronized,
9755 or a single Tor instance from becoming too predictable, in its
9756 download schedule. Closes ticket 15942.
9758 o Major bugfixes (exit policies):
9759 - Avoid disclosing exit outbound bind addresses, configured port
9760 bind addresses, and local interface addresses in relay descriptors
9761 by default under ExitPolicyRejectPrivate. Instead, only reject
9762 these (otherwise unlisted) addresses if
9763 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
9764 0.2.7.2-alpha. Patch by teor.
9766 o Major bugfixes (hidden service client):
9767 - Allow Tor clients with appropriate controllers to work with
9768 FetchHidServDescriptors set to 0. Previously, this option also
9769 disabled descriptor cache lookup, thus breaking hidden services
9770 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
9772 o Minor features (build, hardening):
9773 - Detect and work around a libclang_rt problem that would prevent
9774 clang from finding __mulodi4() on some 32-bit platforms, and thus
9775 keep -ftrapv from linking on those systems. Closes ticket 19079.
9776 - When building on a system without runtime support for the runtime
9777 hardening options, try to log a useful warning at configuration
9778 time, rather than an incomprehensible warning at link time. If
9779 expensive hardening was requested, this warning becomes an error.
9780 Closes ticket 18895.
9782 o Minor features (code safety):
9783 - In our integer-parsing functions, ensure that maxiumum value we
9784 give is no smaller than the minimum value. Closes ticket 19063;
9787 o Minor features (controller):
9788 - Implement new GETINFO queries for all downloads that use
9789 download_status_t to schedule retries. This allows controllers to
9790 examine the schedule for pending downloads. Closes ticket 19323.
9791 - Allow controllers to configure basic client authorization on
9792 hidden services when they create them with the ADD_ONION control
9793 command. Implements ticket 15588. Patch by "special".
9794 - Fire a STATUS_SERVER controller event whenever the hibernation
9795 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
9797 o Minor features (directory authority):
9798 - Directory authorities now only give the Guard flag to a relay if
9799 they are also giving it the Stable flag. This change allows us to
9800 simplify path selection for clients. It should have minimal effect
9801 in practice, since >99% of Guards already have the Stable flag.
9802 Implements ticket 18624.
9803 - Directory authorities now write their v3-status-votes file out to
9804 disk earlier in the consensus process, so we have a record of the
9805 votes even if we abort the consensus process. Resolves
9808 o Minor features (hidden service):
9809 - Stop being so strict about the payload length of "rendezvous1"
9810 cells. We used to be locked in to the "TAP" handshake length, and
9811 now we can handle better handshakes like "ntor". Resolves
9814 o Minor features (infrastructure, time):
9815 - Tor now uses the operating system's monotonic timers (where
9816 available) for internal fine-grained timing. Previously we would
9817 look at the system clock, and then attempt to compensate for the
9818 clock running backwards. Closes ticket 18908.
9819 - Tor now includes an improved timer backend, so that we can
9820 efficiently support tens or hundreds of thousands of concurrent
9821 timers, as will be needed for some of our planned anti-traffic-
9822 analysis work. This code is based on William Ahern's "timeout.c"
9823 project, which implements a "tickless hierarchical timing wheel".
9824 Closes ticket 18365.
9826 o Minor features (logging):
9827 - Provide a more useful warning message when configured with an
9828 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
9829 - When dumping unparseable router descriptors, optionally store them
9830 in separate files, named by digest, up to a configurable size
9831 limit. You can change the size limit by setting the
9832 MaxUnparseableDescSizeToLog option, and disable this feature by
9833 setting that option to 0. Closes ticket 18322.
9834 - Add a set of macros to check nonfatal assertions, for internal
9835 use. Migrating more of our checks to these should help us avoid
9836 needless crash bugs. Closes ticket 18613.
9838 o Minor features (performance):
9839 - Changer the "optimistic data" extension from "off by default" to
9840 "on by default". The default was ordinarily overridden by a
9841 consensus option, but when clients were bootstrapping for the
9842 first time, they would not have a consensus to get the option
9843 from. Changing this default When fetching a consensus for the
9844 first time, use optimistic data. This saves a round-trip during
9845 startup. Closes ticket 18815.
9847 o Minor features (relay, usability):
9848 - When the directory authorities refuse a bad relay's descriptor,
9849 encourage the relay operator to contact us. Many relay operators
9850 won't notice this line in their logs, but it's a win if even a few
9851 learn why we don't like what their relay was doing. Resolves
9854 o Minor features (testing):
9855 - Let backtrace tests work correctly under AddressSanitizer. Fixes
9856 part of bug 18934; bugfix on 0.2.5.2-alpha.
9857 - Move the test-network.sh script to chutney, and modify tor's test-
9858 network.sh to call the (newer) chutney version when available.
9859 Resolves ticket 19116. Patch by teor.
9860 - Use the lcov convention for marking lines as unreachable, so that
9861 we don't count them when we're generating test coverage data.
9862 Update our coverage tools to understand this convention. Closes
9865 o Minor bugfixes (bootstrap):
9866 - Remember the directory we fetched the consensus or previous
9867 certificates from, and use it to fetch future authority
9868 certificates. This change improves bootstrapping performance.
9869 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
9871 o Minor bugfixes (build):
9872 - The test-stem and test-network makefile targets now depend only on
9873 the tor binary that they are testing. Previously, they depended on
9874 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
9875 patch from "cypherpunks".
9877 o Minor bugfixes (circuits):
9878 - Make sure extend_info_from_router() is only called on servers.
9879 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
9881 o Minor bugfixes (compilation):
9882 - When building with Clang, use a full set of GCC warnings.
9883 (Previously, we included only a subset, because of the way we
9884 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
9886 o Minor bugfixes (directory authority):
9887 - Authorities now sort the "package" lines in their votes, for ease
9888 of debugging. (They are already sorted in consensus documents.)
9889 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
9890 - When parsing a detached signature, make sure we use the length of
9891 the digest algorithm instead of an hardcoded DIGEST256_LEN in
9892 order to avoid comparing bytes out-of-bounds with a smaller digest
9893 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
9895 o Minor bugfixes (documentation):
9896 - Document the --passphrase-fd option in the tor manpage. Fixes bug
9897 19504; bugfix on 0.2.7.3-rc.
9898 - Fix the description of the --passphrase-fd option in the
9899 tor-gencert manpage. The option is used to pass the number of a
9900 file descriptor to read the passphrase from, not to read the file
9901 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
9903 o Minor bugfixes (ephemeral hidden service):
9904 - When deleting an ephemeral hidden service, close its intro points
9905 even if they are not completely open. Fixes bug 18604; bugfix
9908 o Minor bugfixes (guard selection):
9909 - Use a single entry guard even if the NumEntryGuards consensus
9910 parameter is not provided. Fixes bug 17688; bugfix
9912 - Don't mark guards as unreachable if connection_connect() fails.
9913 That function fails for local reasons, so it shouldn't reveal
9914 anything about the status of the guard. Fixes bug 14334; bugfix
9917 o Minor bugfixes (hidden service client):
9918 - Increase the minimum number of internal circuits we preemptively
9919 build from 2 to 3, so a circuit is available when a client
9920 connects to another onion service. Fixes bug 13239; bugfix
9923 o Minor bugfixes (logging):
9924 - When logging a directory ownership mismatch, log the owning
9925 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
9927 o Minor bugfixes (memory leaks):
9928 - Fix a small, uncommon memory leak that could occur when reading a
9929 truncated ed25519 key file. Fixes bug 18956; bugfix
9932 o Minor bugfixes (testing):
9933 - Allow clients to retry HSDirs much faster in test networks. Fixes
9934 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
9935 - Disable ASAN's detection of segmentation faults while running
9936 test_bt.sh, so that we can make sure that our own backtrace
9937 generation code works. Fixes another aspect of bug 18934; bugfix
9938 on 0.2.5.2-alpha. Patch from "cypherpunks".
9939 - Fix the test-network-all target on out-of-tree builds by using the
9940 correct path to the test driver script. Fixes bug 19421; bugfix
9943 o Minor bugfixes (time):
9944 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
9945 bugfix on all released tor versions.
9946 - When computing the difference between two times in milliseconds,
9947 we now round to the nearest millisecond correctly. Previously, we
9948 could sometimes round in the wrong direction. Fixes bug 19428;
9949 bugfix on 0.2.2.2-alpha.
9951 o Minor bugfixes (user interface):
9952 - Display a more accurate number of suppressed messages in the log
9953 rate-limiter. Previously, there was a potential integer overflow
9954 in the counter. Now, if the number of messages hits a maximum, the
9955 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
9957 - Fix a typo in the passphrase prompt for the ed25519 identity key.
9958 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
9960 o Code simplification and refactoring:
9961 - Remove redundant declarations of the MIN macro. Closes
9963 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
9964 Closes ticket 18462; patch from "icanhasaccount".
9965 - Split the 600-line directory_handle_command_get function into
9966 separate functions for different URL types. Closes ticket 16698.
9969 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
9970 ticket 19153. Patch from "U+039b".
9973 - Remove support for "GET /tor/bytes.txt" DirPort request, and
9974 "GETINFO dir-usage" controller request, which were only available
9975 via a compile-time option in Tor anyway. Feature was added in
9976 0.2.2.1-alpha. Resolves ticket 19035.
9977 - There is no longer a compile-time option to disable support for
9978 TransPort. (If you don't want TransPort; just don't use it.) Patch
9979 from "U+039b". Closes ticket 19449.
9982 - Run more workqueue tests as part of "make check". These had
9983 previously been implemented, but you needed to know special
9984 command-line options to enable them.
9985 - We now have unit tests for our code to reject zlib "compression
9986 bombs". (Fortunately, the code works fine.)
9989 Changes in version 0.2.8.6 - 2016-08-02
9991 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
9993 The Tor 0.2.8 series improves client bootstrapping performance,
9994 completes the authority-side implementation of improved identity
9995 keys for relays, and includes numerous bugfixes and performance
9996 improvements throughout the program. This release continues to
9997 improve the coverage of Tor's test suite. For a full list of
9998 changes since Tor 0.2.7, see the ReleaseNotes file.
10000 Changes since 0.2.8.5-rc:
10002 o Minor features (geoip):
10003 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
10006 o Minor bugfixes (compilation):
10007 - Fix a compilation warning in the unit tests on systems where char
10008 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
10010 o Minor bugfixes (fallback directories):
10011 - Remove 1 fallback that was on the hardcoded list, then opted-out,
10012 leaving 89 of the 100 fallbacks originally introduced in Tor
10013 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
10015 o Minor bugfixes (Linux seccomp2 sandbox):
10016 - Allow more syscalls when running with "Sandbox 1" enabled:
10017 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
10018 some systems, these are required for Tor to start. Fixes bug
10019 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
10020 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
10021 so that get_interface_address6_via_udp_socket_hack() can work.
10022 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
10025 Changes in version 0.2.8.5-rc - 2016-07-07
10026 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
10027 series. If we find no new bugs or regressions here, the first stable
10028 0.2.8 release will be identical to it. It has a few small bugfixes
10029 against previous versions.
10031 o Directory authority changes:
10032 - Urras is no longer a directory authority. Closes ticket 19271.
10034 o Major bugfixes (heartbeat):
10035 - Fix a regression that would crash Tor when the periodic
10036 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
10037 0.2.8.1-alpha. Reported by "kubaku".
10039 o Minor features (build):
10040 - Tor now again builds with the recent OpenSSL 1.1 development
10041 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
10042 - When building manual pages, set the timezone to "UTC", so that the
10043 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
10044 Patch from intrigeri.
10046 o Minor bugfixes (fallback directory selection):
10047 - Avoid errors during fallback selection if there are no eligible
10048 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
10051 o Minor bugfixes (IPv6, microdescriptors):
10052 - Don't check node addresses when we only have a routerstatus. This
10053 allows IPv6-only clients to bootstrap by fetching microdescriptors
10054 from fallback directory mirrors. (The microdescriptor consensus
10055 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
10058 o Minor bugfixes (logging):
10059 - Reduce pointlessly verbose log messages when directory servers
10060 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
10061 0.2.8.1-alpha. Patch by teor.
10062 - When a fallback directory changes its fingerprint from the hard-
10063 coded fingerprint, log a less severe, more explanatory log
10064 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
10066 o Minor bugfixes (Linux seccomp2 sandboxing):
10067 - Allow statistics to be written to disk when "Sandbox 1" is
10068 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
10069 0.2.6.1-alpha respectively.
10071 o Minor bugfixes (user interface):
10072 - Remove a warning message "Service [scrubbed] not found after
10073 descriptor upload". This message appears when one uses HSPOST
10074 control command to upload a service descriptor. Since there is
10075 only a descriptor and no service, showing this message is
10076 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
10078 o Fallback directory list:
10079 - Add a comment to the generated fallback directory list that
10080 explains how to comment out unsuitable fallbacks in a way that's
10081 compatible with the stem fallback parser.
10082 - Update fallback whitelist and blacklist based on relay operator
10083 emails. Blacklist unsuitable (non-working, over-volatile)
10084 fallbacks. Resolves ticket 19071. Patch by teor.
10085 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
10086 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
10087 ticket 19071; patch by teor.
10090 Changes in version 0.2.8.4-rc - 2016-06-15
10091 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
10092 If we find no new bugs or regressions here, the first stable 0.2.8
10093 release will be identical to it. It has a few small bugfixes against
10096 o Major bugfixes (user interface):
10097 - Correctly give a warning in the cases where a relay is specified
10098 by nickname, and one such relay is found, but it is not officially
10099 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
10101 o Minor features (build):
10102 - Tor now builds once again with the recent OpenSSL 1.1 development
10103 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
10105 o Minor features (geoip):
10106 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
10109 o Minor bugfixes (compilation):
10110 - Cause the unit tests to compile correctly on mingw64 versions that
10111 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
10113 o Minor bugfixes (downloading):
10114 - Predict more correctly whether we'll be downloading over HTTP when
10115 we determine the maximum length of a URL. This should avoid a
10116 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
10120 Changes in version 0.2.8.3-alpha - 2016-05-26
10121 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
10122 the course of the 0.2.8 development cycle. It improves the behavior of
10123 directory clients, fixes several crash bugs, fixes a gap in compiler
10124 hardening, and allows the full integration test suite to run on
10127 o Major bugfixes (security, client, DNS proxy):
10128 - Stop a crash that could occur when a client running with DNSPort
10129 received a query with multiple address types, and the first
10130 address type was not supported. Found and fixed by Scott Dial.
10131 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
10133 o Major bugfixes (security, compilation):
10134 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
10135 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
10136 cause a compiler warning, thereby making other checks fail, and
10137 needlessly disabling compiler-hardening support. Fixes one case of
10138 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
10140 o Major bugfixes (security, directory authorities):
10141 - Fix a crash and out-of-bounds write during authority voting, when
10142 the list of relays includes duplicate ed25519 identity keys. Fixes
10143 bug 19032; bugfix on 0.2.8.2-alpha.
10145 o Major bugfixes (client, bootstrapping):
10146 - Check if bootstrap consensus downloads are still needed when the
10147 linked connection attaches. This prevents tor making unnecessary
10148 begindir-style connections, which are the only directory
10149 connections tor clients make since the fix for 18483 was merged.
10150 - Fix some edge cases where consensus download connections may not
10151 have been closed, even though they were not needed. Related to fix
10153 - Make relays retry consensus downloads the correct number of times,
10154 rather than the more aggressive client retry count. Fixes part of
10156 - Stop downloading consensuses when we have a consensus, even if we
10157 don't have all the certificates for it yet. Fixes bug 18809;
10158 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
10160 o Major bugfixes (directory mirrors):
10161 - Decide whether to advertise begindir support in the the same way
10162 we decide whether to advertise our DirPort. Allowing these
10163 decisions to become out-of-sync led to surprising behavior like
10164 advertising begindir support when hibernation made us not
10165 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
10168 o Major bugfixes (IPv6 bridges, client):
10169 - Actually use IPv6 addresses when selecting directory addresses for
10170 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
10173 o Major bugfixes (key management):
10174 - If OpenSSL fails to generate an RSA key, do not retain a dangling
10175 pointer to the previous (uninitialized) key value. The impact here
10176 should be limited to a difficult-to-trigger crash, if OpenSSL is
10177 running an engine that makes key generation failures possible, or
10178 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
10179 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
10182 o Major bugfixes (testing):
10183 - Fix a bug that would block 'make test-network-all' on systems where
10184 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
10185 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
10186 bugfix on 0.2.8.1-alpha.
10188 o Minor features (clients):
10189 - Make clients, onion services, and bridge relays always use an
10190 encrypted begindir connection for directory requests. Resolves
10191 ticket 18483. Patch by "teor".
10193 o Minor features (fallback directory mirrors):
10194 - Give each fallback the same weight for client selection; restrict
10195 fallbacks to one per operator; report fallback directory detail
10196 changes when rebuilding list; add new fallback directory mirrors
10197 to the whitelist; and many other minor simplifications and fixes.
10198 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
10199 0.2.8.1-alpha; patch by "teor".
10200 - Replace the 21 fallbacks generated in January 2016 and included in
10201 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
10202 2016. Closes task 17158; patch by "teor".
10204 o Minor features (geoip):
10205 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
10208 o Minor bugfixes (assert, portability):
10209 - Fix an assertion failure in memarea.c on systems where "long" is
10210 shorter than the size of a pointer. Fixes bug 18716; bugfix
10213 o Minor bugfixes (bootstrap):
10214 - Consistently use the consensus download schedule for authority
10215 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
10217 o Minor bugfixes (build):
10218 - Remove a pair of redundant AM_CONDITIONAL declarations from
10219 configure.ac. Fixes one final case of bug 17744; bugfix
10221 - Resolve warnings when building on systems that are concerned with
10222 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
10224 - When libscrypt.h is found, but no libscrypt library can be linked,
10225 treat libscrypt as absent. Fixes bug 19161; bugfix
10228 o Minor bugfixes (client):
10229 - Turn all TestingClientBootstrap* into non-testing torrc options.
10230 This changes simply renames them by removing "Testing" in front of
10231 them and they do not require TestingTorNetwork to be enabled
10232 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
10233 - Make directory node selection more reliable, mainly for IPv6-only
10234 clients and clients with few reachable addresses. Fixes bug 18929;
10235 bugfix on 0.2.8.1-alpha. Patch by "teor".
10237 o Minor bugfixes (controller, microdescriptors):
10238 - Make GETINFO dir/status-vote/current/consensus conform to the
10239 control specification by returning "551 Could not open cached
10240 consensus..." when not caching consensuses. Fixes bug 18920;
10241 bugfix on 0.2.2.6-alpha.
10243 o Minor bugfixes (crypto, portability):
10244 - The SHA3 and SHAKE routines now produce the correct output on Big
10245 Endian systems. No code calls either algorithm yet, so this is
10246 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
10247 - Tor now builds again with the recent OpenSSL 1.1 development
10248 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
10251 o Minor bugfixes (directories):
10252 - When fetching extrainfo documents, compare their SHA256 digests
10253 and Ed25519 signing key certificates with the routerinfo that led
10254 us to fetch them, rather than with the most recent routerinfo.
10255 Otherwise we generate many spurious warnings about mismatches.
10256 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
10258 o Minor bugfixes (logging):
10259 - When we can't generate a signing key because OfflineMasterKey is
10260 set, do not imply that we should have been able to load it. Fixes
10261 bug 18133; bugfix on 0.2.7.2-alpha.
10262 - Stop periodic_event_dispatch() from blasting twelve lines per
10263 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
10264 - When rejecting a misformed INTRODUCE2 cell, only log at
10265 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
10267 o Minor bugfixes (pluggable transports):
10268 - Avoid reporting a spurious error when we decide that we don't need
10269 to terminate a pluggable transport because it has already exited.
10270 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
10272 o Minor bugfixes (pointer arithmetic):
10273 - Fix a bug in memarea_alloc() that could have resulted in remote
10274 heap write access, if Tor had ever passed an unchecked size to
10275 memarea_alloc(). Fortunately, all the sizes we pass to
10276 memarea_alloc() are pre-checked to be less than 128 kilobytes.
10277 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
10280 o Minor bugfixes (relays):
10281 - Consider more config options when relays decide whether to
10282 regenerate their descriptor. Fixes more of bug 12538; bugfix
10284 - Resolve some edge cases where we might launch an ORPort
10285 reachability check even when DisableNetwork is set. Noticed while
10286 fixing bug 18616; bugfix on 0.2.3.9-alpha.
10288 o Minor bugfixes (statistics):
10289 - We now include consensus downloads via IPv6 in our directory-
10290 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
10292 o Minor bugfixes (testing):
10293 - Allow directories in small networks to bootstrap by skipping
10294 DirPort checks when the consensus has no exits. Fixes bug 19003;
10295 bugfix on 0.2.8.1-alpha. Patch by teor.
10296 - Fix a small memory leak that would occur when the
10297 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
10298 bugfix on 0.2.5.2-alpha.
10300 o Minor bugfixes (time handling):
10301 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
10302 field. Otherwise, our unit tests crash on Windows. Fixes bug
10303 18977; bugfix on 0.2.2.25-alpha.
10306 - Document the contents of the 'datadir/keys' subdirectory in the
10307 manual page. Closes ticket 17621.
10308 - Stop recommending use of nicknames to identify relays in our
10309 MapAddress documentation. Closes ticket 18312.
10312 Changes in version 0.2.8.2-alpha - 2016-03-28
10313 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
10314 bugs in earlier versions of Tor, including some that prevented
10315 authorities using Tor 0.2.7.x from running correctly. IPv6 and
10316 directory support should also be much improved.
10318 o New system requirements:
10319 - Tor no longer supports versions of OpenSSL with a broken
10320 implementation of counter mode. (This bug was present in OpenSSL
10321 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
10322 longer runs with, these versions.
10323 - Tor no longer attempts to support platforms where the "time_t"
10324 type is unsigned. (To the best of our knowledge, only OpenVMS does
10325 this, and Tor has never actually built on OpenVMS.) Closes
10327 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
10328 later (released in 2008 and 2009 respectively). If you are
10329 building Tor from the git repository instead of from the source
10330 distribution, and your tools are older than this, you will need to
10331 upgrade. Closes ticket 17732.
10333 o Major bugfixes (security, pointers):
10334 - Avoid a difficult-to-trigger heap corruption attack when extending
10335 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
10336 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
10337 Reported by Guido Vranken.
10339 o Major bugfixes (bridges, pluggable transports):
10340 - Modify the check for OR connections to private addresses. Allow
10341 bridges on private addresses, including pluggable transports that
10342 ignore the (potentially private) address in the bridge line. Fixes
10343 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
10345 o Major bugfixes (compilation):
10346 - Repair hardened builds under the clang compiler. Previously, our
10347 use of _FORTIFY_SOURCE would conflict with clang's address
10348 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
10350 o Major bugfixes (crash on shutdown):
10351 - Correctly handle detaching circuits from muxes when shutting down.
10352 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
10353 - Fix an assert-on-exit bug related to counting memory usage in
10354 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
10356 o Major bugfixes (crash on startup):
10357 - Fix a segfault during startup: If a Unix domain socket was
10358 configured as listener (such as a ControlSocket or a SocksPort
10359 "unix:" socket), and tor was started as root but not configured to
10360 switch to another user, tor would segfault while trying to string
10361 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
10364 o Major bugfixes (dns proxy mode, crash):
10365 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
10366 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
10368 o Major bugfixes (relays, bridge clients):
10369 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
10370 bridge clients use the address configured in the bridge line.
10371 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
10374 o Major bugfixes (voting):
10375 - Actually enable support for authorities to match routers by their
10376 Ed25519 identities. Previously, the code had been written, but
10377 some debugging code that had accidentally been left in the
10378 codebase made it stay turned off. Fixes bug 17702; bugfix
10380 - When collating votes by Ed25519 identities, authorities now
10381 include a "NoEdConsensus" flag if the ed25519 value (or lack
10382 thereof) for a server does not reflect the majority consensus.
10383 Related to bug 17668; bugfix on 0.2.7.2-alpha.
10384 - When generating a vote with keypinning disabled, never include two
10385 entries for the same ed25519 identity. This bug was causing
10386 authorities to generate votes that they could not parse when a
10387 router violated key pinning by changing its RSA identity but
10388 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
10389 18318. Bugfix on 0.2.7.2-alpha.
10391 o Minor features (security, win32):
10392 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
10393 attack. Fixes bug 18123; bugfix on all tor versions. Patch
10396 o Minor features (bug-resistance):
10397 - Make Tor survive errors involving connections without a
10398 corresponding event object. Previously we'd fail with an
10399 assertion; now we produce a log message. Related to bug 16248.
10401 o Minor features (build):
10402 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
10403 as having possible IPFW support. Closes ticket 18448. Patch from
10404 Steven Chamberlain.
10406 o Minor features (code hardening):
10407 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
10408 level code, to harden against accidental failures to NUL-
10409 terminate. Part of ticket 17852. Patch from jsturgix. Found
10412 o Minor features (crypto):
10413 - Validate the hard-coded Diffie-Hellman parameters and ensure that
10414 p is a safe prime, and g is a suitable generator. Closes
10417 o Minor features (geoip):
10418 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
10421 o Minor features (hidden service directory):
10422 - Streamline relay-side hsdir handling: when relays consider whether
10423 to accept an uploaded hidden service descriptor, they no longer
10424 check whether they are one of the relays in the network that is
10425 "supposed" to handle that descriptor. Implements ticket 18332.
10427 o Minor features (IPv6):
10428 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
10429 to 1, tor prefers IPv6 directory addresses.
10430 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
10431 avoids using IPv4 for client OR and directory connections.
10432 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
10433 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
10434 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
10436 o Minor features (linux seccomp2 sandbox):
10437 - Reject attempts to change our Address with "Sandbox 1" enabled.
10438 Changing Address with Sandbox turned on would never actually work,
10439 but previously it would fail in strange and confusing ways. Found
10440 while fixing 18548.
10442 o Minor features (robustness):
10443 - Exit immediately with an error message if the code attempts to use
10444 Libevent without having initialized it. This should resolve some
10445 frequently-made mistakes in our unit tests. Closes ticket 18241.
10447 o Minor features (unix domain sockets):
10448 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
10449 Unix domain sockets without checking the permissions on the parent
10450 directory. (Tor checks permissions by default because some
10451 operating systems only check permissions on the parent directory.
10452 However, some operating systems do look at permissions on the
10453 socket, and tor's default check is unneeded.) Closes ticket 18458.
10456 o Minor bugfixes (exit policies, security):
10457 - Refresh an exit relay's exit policy when interface addresses
10458 change. Previously, tor only refreshed the exit policy when the
10459 configured external address changed. Fixes bug 18208; bugfix on
10460 0.2.7.3-rc. Patch by teor.
10462 o Minor bugfixes (security, hidden services):
10463 - Prevent hidden services connecting to client-supplied rendezvous
10464 addresses that are reserved as internal or multicast. Fixes bug
10465 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
10467 o Minor bugfixes (build):
10468 - Do not link the unit tests against both the testing and non-
10469 testing versions of the static libraries. Fixes bug 18490; bugfix
10471 - Avoid spurious failures from configure files related to calling
10472 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
10473 0.2.0.1-alpha. Patch from "cypherpunks".
10474 - Silence spurious clang-scan warnings in the ed25519_donna code by
10475 explicitly initializing some objects. Fixes bug 18384; bugfix on
10476 0.2.7.2-alpha. Patch by teor.
10478 o Minor bugfixes (client, bootstrap):
10479 - Count receipt of new microdescriptors as progress towards
10480 bootstrapping. Previously, with EntryNodes set, Tor might not
10481 successfully repopulate the guard set on bootstrapping. Fixes bug
10482 16825; bugfix on 0.2.3.1-alpha.
10484 o Minor bugfixes (code correctness):
10485 - Update to the latest version of Trunnel, which tries harder to
10486 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
10487 by clang address sanitizer. Fixes bug 18373; bugfix
10490 o Minor bugfixes (configuration):
10491 - Fix a tiny memory leak when parsing a port configuration ending in
10492 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
10494 o Minor bugfixes (containers):
10495 - If we somehow attempt to construct a heap with more than
10496 1073741822 elements, avoid an integer overflow when maintaining
10497 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
10499 o Minor bugfixes (correctness):
10500 - Fix a bad memory handling bug that would occur if we had queued a
10501 cell on a channel's incoming queue. Fortunately, we can't actually
10502 queue a cell like that as our code is constructed today, but it's
10503 best to avoid this kind of error, even if there isn't any code
10504 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
10506 o Minor bugfixes (directory):
10507 - When generating a URL for a directory server on an IPv6 address,
10508 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
10509 on 0.2.3.9-alpha. Patch from Malek.
10511 o Minor bugfixes (fallback directory mirrors):
10512 - When requesting extrainfo descriptors from a trusted directory
10513 server, check whether it is an authority or a fallback directory
10514 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
10515 0.2.4.7-alpha. Reported by atagar, patch by teor.
10517 o Minor bugfixes (hidden service, client):
10518 - Handle the case where the user makes several fast consecutive
10519 requests to the same .onion address. Previously, the first six
10520 requests would each trigger a descriptor fetch, each picking a
10521 directory (there are 6 overall) and the seventh one would fail
10522 because no directories were left, thereby triggering a close on
10523 all current directory connections asking for the hidden service.
10524 The solution here is to not close the connections if we have
10525 pending directory fetches. Fixes bug 15937; bugfix
10528 o Minor bugfixes (hidden service, control port):
10529 - Add the onion address to the HS_DESC event for the UPLOADED action
10530 both on success or failure. It was previously hardcoded with
10531 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
10533 o Minor bugfixes (hidden service, directory):
10534 - Bridges now refuse "rendezvous2" (hidden service descriptor)
10535 publish attempts. Suggested by ticket 18332.
10537 o Minor bugfixes (linux seccomp2 sandbox):
10538 - Allow the setrlimit syscall, and the prlimit and prlimit64
10539 syscalls, which some libc implementations use under the hood.
10540 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
10541 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
10542 enabled and no DNS resolvers configured. This should help TAILS
10543 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
10544 - Fix the sandbox's interoperability with unix domain sockets under
10545 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
10547 o Minor bugfixes (logging):
10548 - When logging information about an unparsable networkstatus vote or
10549 consensus, do not say "vote" when we mean consensus. Fixes bug
10550 18368; bugfix on 0.2.0.8-alpha.
10551 - Scrub service name in "unrecognized service ID" log messages.
10552 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
10553 - Downgrade logs and backtraces about IP versions to info-level.
10554 Only log backtraces once each time tor runs. Assists in diagnosing
10555 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
10556 Christian, patch by teor.
10558 o Minor bugfixes (memory safety):
10559 - Avoid freeing an uninitialized pointer when opening a socket fails
10560 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
10561 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
10563 - Correctly duplicate addresses in get_interface_address6_list().
10564 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
10565 patch by "cypherpunks".
10566 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
10568 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
10569 18672; bugfix on 0.2.5.1-alpha.
10571 o Minor bugfixes (private directory):
10572 - Prevent a race condition when creating private directories. Fixes
10573 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
10574 Patch from jsturgix. Found with Flawfinder.
10576 o Minor bugfixes (test networks, IPv6):
10577 - Allow internal IPv6 addresses in descriptors in test networks.
10578 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
10581 o Minor bugfixes (testing):
10582 - We no longer disable assertions in the unit tests when coverage is
10583 enabled. Instead, we require you to say --disable-asserts-in-tests
10584 to the configure script if you need assertions disabled in the
10585 unit tests (for example, if you want to perform branch coverage).
10586 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
10588 o Minor bugfixes (time parsing):
10589 - Avoid overflow in tor_timegm when parsing dates in and after 2038
10590 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
10591 0.0.2pre14. Patch by teor.
10593 o Minor bugfixes (tor-gencert):
10594 - Correctly handle the case where an authority operator enters a
10595 passphrase but sends an EOF before sending a newline. Fixes bug
10596 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
10598 o Code simplification and refactoring:
10599 - Quote all the string interpolations in configure.ac -- even those
10600 which we are pretty sure can't contain spaces. Closes ticket
10601 17744. Patch from zerosion.
10602 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
10603 inplace, so there's no need to have a separate implementation for
10604 the non-inplace code. Closes ticket 18258. Patch from Malek.
10605 - Simplify return types for some crypto functions that can't
10606 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
10609 - Change build messages to refer to "Fedora" instead of "Fedora
10610 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
10611 Patches from "icanhasaccount" and "cypherpunks".
10613 o Removed features:
10614 - We no longer maintain an internal freelist in memarea.c.
10615 Allocators should be good enough to make this code unnecessary,
10616 and it's doubtful that it ever had any performance benefit.
10619 - Fix several warnings from clang's address sanitizer produced in
10621 - Treat backtrace test failures as expected on FreeBSD until we
10622 solve bug 17808. Closes ticket 18204.
10625 Changes in version 0.2.8.1-alpha - 2016-02-04
10626 Tor 0.2.8.1-alpha is the first alpha release in its series. It
10627 includes numerous small features and bugfixes against previous Tor
10628 versions, and numerous small infrastructure improvements. The most
10629 notable features are a set of improvements to the directory subsystem.
10631 o Major features (security, Linux):
10632 - When Tor starts as root on Linux and is told to switch user ID, it
10633 can now retain the capability to bind to low ports. By default,
10634 Tor will do this only when it's switching user ID and some low
10635 ports have been configured. You can change this behavior with the
10636 new option KeepBindCapabilities. Closes ticket 8195.
10638 o Major features (directory system):
10639 - When bootstrapping multiple consensus downloads at a time, use the
10640 first one that starts downloading, and close the rest. This
10641 reduces failures when authorities or fallback directories are slow
10642 or down. Together with the code for feature 15775, this feature
10643 should reduces failures due to fallback churn. Implements ticket
10644 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
10645 "mikeperry" and "teor".
10646 - Include a trial list of 21 default fallback directories, generated
10647 in January 2016, based on an opt-in survey of suitable relays.
10648 Doing this should make clients bootstrap more quickly and reliably,
10649 and reduce the load on the directory authorities. Closes ticket
10650 15775. Patch by "teor".
10651 Candidates identified using an OnionOO script by "weasel", "teor",
10652 "gsathya", and "karsten".
10653 - Previously only relays that explicitly opened a directory port
10654 (DirPort) accepted directory requests from clients. Now all
10655 relays, with and without a DirPort, accept and serve tunneled
10656 directory requests that they receive through their ORPort. You can
10657 disable this behavior using the new DirCache option. Closes
10660 o Major key updates:
10661 - Update the V3 identity key for the dannenberg directory authority:
10662 it was changed on 18 November 2015. Closes task 17906. Patch
10665 o Minor features (security, clock):
10666 - Warn when the system clock appears to move back in time (when the
10667 state file was last written in the future). Tor doesn't know that
10668 consensuses have expired if the clock is in the past. Patch by
10669 "teor". Implements ticket 17188.
10671 o Minor features (security, exit policies):
10672 - ExitPolicyRejectPrivate now rejects more private addresses by
10673 default. Specifically, it now rejects the relay's outbound bind
10674 addresses (if configured), and the relay's configured port
10675 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
10676 0.2.0.11-alpha. Patch by "teor".
10678 o Minor features (security, memory erasure):
10679 - Set the unused entries in a smartlist to NULL. This helped catch
10680 a (harmless) bug, and shouldn't affect performance too much.
10681 Implements ticket 17026.
10682 - Use SecureMemoryWipe() function to securely clean memory on
10683 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
10684 Implements feature 17986.
10685 - Use explicit_bzero or memset_s when present. Previously, we'd use
10686 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
10687 from <logan@hackers.mu> and <selven@hackers.mu>.
10688 - Make memwipe() do nothing when passed a NULL pointer or buffer of
10689 zero size. Check size argument to memwipe() for underflow. Fixes
10690 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
10693 o Minor features (security, RNG):
10694 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
10695 positively are not allowed to fail. Previously we depended on
10696 internal details of OpenSSL's behavior. Closes ticket 17686.
10697 - Never use the system entropy output directly for anything besides
10698 seeding the PRNG. When we want to generate important keys, instead
10699 of using system entropy directly, we now hash it with the PRNG
10700 stream. This may help resist certain attacks based on broken OS
10701 entropy implementations. Closes part of ticket 17694.
10702 - Use modern system calls (like getentropy() or getrandom()) to
10703 generate strong entropy on platforms that have them. Closes
10706 o Minor features (accounting):
10707 - Added two modes to the AccountingRule option: One for limiting
10708 only the number of bytes sent ("AccountingRule out"), and one for
10709 limiting only the number of bytes received ("AccountingRule in").
10710 Closes ticket 15989; patch from "unixninja92".
10712 o Minor features (build):
10713 - Since our build process now uses "make distcheck", we no longer
10714 force "make dist" to depend on "make check". Closes ticket 17893;
10715 patch from "cypherpunks."
10716 - Tor now builds successfully with the recent OpenSSL 1.1
10717 development branch, and with the latest LibreSSL. Closes tickets
10718 17549, 17921, and 17984.
10720 o Minor features (controller):
10721 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
10722 tickets 16774 and 17817. Patch by George Tankersley.
10723 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
10724 service descriptor from a service's local hidden service
10725 descriptor cache. Closes ticket 14846.
10726 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
10727 controllers can examine the the reject rules added by
10728 ExitPolicyRejectPrivate. This makes it easier for stem to display
10731 o Minor features (crypto):
10732 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
10734 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
10735 - When allocating a digest state object, allocate no more space than
10736 we actually need. Previously, we would allocate as much space as
10737 the state for the largest algorithm would need. This change saves
10738 up to 672 bytes per circuit. Closes ticket 17796.
10739 - Improve performance when hashing non-multiple of 8 sized buffers,
10740 based on Andrew Moon's public domain SipHash-2-4 implementation.
10741 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
10743 o Minor features (directory downloads):
10744 - Wait for busy authorities and fallback directories to become non-
10745 busy when bootstrapping. (A similar change was made in 6c443e987d
10746 for directory caches chosen from the consensus.) Closes ticket
10747 17864; patch by "teor".
10748 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
10749 directory mirrors. The default is 1; set it to 0 to disable
10750 fallbacks. Implements ticket 17576. Patch by "teor".
10752 o Minor features (geoip):
10753 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
10756 o Minor features (IPv6):
10757 - Add an argument 'ipv6=address:orport' to the DirAuthority and
10758 FallbackDir torrc options, to specify an IPv6 address for an
10759 authority or fallback directory. Add hard-coded ipv6 addresses for
10760 directory authorities that have them. Closes ticket 17327; patch
10761 from Nick Mathewson and "teor".
10762 - Add address policy assume_action support for IPv6 addresses.
10763 - Limit IPv6 mask bits to 128.
10764 - Warn when comparing against an AF_UNSPEC address in a policy, it's
10765 almost always a bug. Closes ticket 17863; patch by "teor".
10766 - Allow users to configure directory authorities and fallback
10767 directory servers with IPv6 addresses and ORPorts. Resolves
10769 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
10770 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
10771 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
10772 17638; bugfix on 0.0.2pre8. Patch by "teor".
10774 o Minor features (logging):
10775 - When logging to syslog, allow a tag to be added to the syslog
10776 identity (the string prepended to every log message). The tag can
10777 be configured with SyslogIdentityTag and defaults to none. Setting
10778 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
10781 o Minor features (portability):
10782 - Use timingsafe_memcmp() where available. Closes ticket 17944;
10783 patch from <logan@hackers.mu>.
10785 o Minor features (relay, address discovery):
10786 - Add a family argument to get_interface_addresses_raw() and
10787 subfunctions to make network interface address interogation more
10788 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
10789 types of interfaces from the operating system. Resolves
10791 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
10792 fails to enumerate interface addresses using the platform-specific
10793 API, have it rely on the UDP socket fallback technique to try and
10794 find out what IP addresses (both IPv4 and IPv6) our machine has.
10795 Resolves ticket 17951.
10797 o Minor features (replay cache):
10798 - The replay cache now uses SHA256 instead of SHA1. Implements
10799 feature 8961. Patch by "teor", issue reported by "rransom".
10801 o Minor features (unix file permissions):
10802 - Defer creation of Unix sockets until after setuid. This avoids
10803 needing CAP_CHOWN and CAP_FOWNER when using systemd's
10804 CapabilityBoundingSet, or chown and fowner when using SELinux.
10805 Implements part of ticket 17562. Patch from Jamie Nguyen.
10806 - If any directory created by Tor is marked as group readable, the
10807 filesystem group is allowed to be either the default GID or the
10808 root user. Allowing root to read the DataDirectory prevents the
10809 need for CAP_READ_SEARCH when using systemd's
10810 CapabilityBoundingSet, or dac_read_search when using SELinux.
10811 Implements part of ticket 17562. Patch from Jamie Nguyen.
10812 - Introduce a new DataDirectoryGroupReadable option. If it is set to
10813 1, the DataDirectory will be made readable by the default GID.
10814 Implements part of ticket 17562. Patch from Jamie Nguyen.
10816 o Minor bugfixes (accounting):
10817 - The max bandwidth when using 'AccountRule sum' is now correctly
10818 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
10819 from "unixninja92".
10821 o Minor bugfixes (code correctness):
10822 - When closing an entry connection, generate a warning if we should
10823 have sent an end cell for it but we haven't. Fixes bug 17876;
10824 bugfix on 0.2.3.2-alpha.
10825 - Assert that allocated memory held by the reputation code is freed
10826 according to its internal counters. Fixes bug 17753; bugfix
10828 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
10831 o Minor bugfixes (compilation):
10832 - Mark all object files that include micro-revision.i as depending
10833 on it, so as to make parallel builds more reliable. Fixes bug
10834 17826; bugfix on 0.2.5.1-alpha.
10835 - Don't try to use the pthread_condattr_setclock() function unless
10836 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
10837 17819; bugfix on 0.2.6.3-alpha.
10838 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
10840 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
10841 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
10842 - Fix search for libevent libraries on OpenBSD (and other systems
10843 that install libevent 1 and libevent 2 in parallel). Fixes bug
10844 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
10845 - Isolate environment variables meant for tests from the rest of the
10846 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
10847 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
10849 - Remove config.log only from make distclean, not from make clean.
10850 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
10852 o Minor bugfixes (crypto):
10853 - Check the return value of HMAC() and assert on failure. Fixes bug
10854 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
10856 o Minor bugfixes (fallback directories):
10857 - Mark fallbacks as "too busy" when they return a 503 response,
10858 rather than just marking authorities. Fixes bug 17572; bugfix on
10859 0.2.4.7-alpha. Patch by "teor".
10861 o Minor bugfixes (IPv6):
10862 - Update the limits in max_dl_per_request for IPv6 address length.
10863 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
10865 o Minor bugfixes (linux seccomp2 sandbox):
10866 - Fix a crash when using offline master ed25519 keys with the Linux
10867 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
10869 o Minor bugfixes (logging):
10870 - In log messages that include a function name, use __FUNCTION__
10871 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
10872 with clang __PRETTY_FUNCTION__ has extra information we don't
10873 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
10875 - Remove needless quotes from a log message about unparseable
10876 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
10878 o Minor bugfixes (portability):
10879 - Remove an #endif from configure.ac so that we correctly detect the
10880 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
10883 o Minor bugfixes (relays):
10884 - Check that both the ORPort and DirPort (if present) are reachable
10885 before publishing a relay descriptor. Otherwise, relays publish a
10886 descriptor with DirPort 0 when the DirPort reachability test takes
10887 longer than the ORPort reachability test. Fixes bug 18050; bugfix
10888 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
10890 o Minor bugfixes (relays, hidden services):
10891 - Refuse connection requests to private OR addresses unless
10892 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
10893 then refuse to send any cells to a private address. Fixes bugs
10894 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
10896 o Minor bugfixes (safe logging):
10897 - When logging a malformed hostname received through socks4, scrub
10898 it if SafeLogging says we should. Fixes bug 17419; bugfix
10901 o Minor bugfixes (statistics code):
10902 - Consistently check for overflow in round_*_to_next_multiple_of
10903 functions, and add unit tests with additional and maximal values.
10904 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
10905 - Handle edge cases in the laplace functions: avoid division by
10906 zero, avoid taking the log of zero, and silence clang type
10907 conversion warnings using round and trunc. Add unit tests for edge
10908 cases with maximal values. Fixes part of bug 13192; bugfix
10911 o Minor bugfixes (testing):
10912 - The test for log_heartbeat was incorrectly failing in timezones
10913 with non-integer offsets. Instead of comparing the end of the time
10914 string against a constant, compare it to the output of
10915 format_local_iso_time when given the correct input. Fixes bug
10916 18039; bugfix on 0.2.5.4-alpha.
10917 - Make unit tests pass on IPv6-only systems, and systems without
10918 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
10919 bugfix on 0.2.7.3-rc. Patch by "teor".
10920 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
10922 - Check the full results of SHA256 and SHA512 digests in the unit
10923 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
10925 o Code simplification and refactoring:
10926 - Move logging of redundant policy entries in
10927 policies_parse_exit_policy_internal into its own function. Closes
10928 ticket 17608; patch from "juce".
10929 - Extract the more complicated parts of circuit_mark_for_close()
10930 into a new function that we run periodically before circuits are
10931 freed. This change removes more than half of the functions
10932 currently in the "blob". Closes ticket 17218.
10933 - Clean up a little duplicated code in
10934 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
10936 - Decouple the list of streams waiting to be attached to circuits
10937 from the overall connection list. This change makes it possible to
10938 attach streams quickly while simplifying Tor's callgraph and
10939 avoiding O(N) scans of the entire connection list. Closes
10941 - When a direct directory request fails immediately on launch,
10942 instead of relaunching that request from inside the code that
10943 launches it, instead mark the connection for teardown. This change
10944 simplifies Tor's callback and prevents the directory-request
10945 launching code from invoking itself recursively. Closes
10947 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
10948 use them. Closes ticket 17926.
10951 - Add a description of the correct use of the '--keygen' command-
10952 line option. Closes ticket 17583; based on text by 's7r'.
10953 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
10954 - Explain actual minima for BandwidthRate. Closes ticket 16382.
10955 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
10956 - Mention torspec URL in the manpage and point the reader to it
10957 whenever we mention a document that belongs in torspce. Fixes
10960 o Removed features:
10961 - Remove client-side support for connecting to Tor relays running
10962 versions of Tor before 0.2.3.6-alpha. These relays didn't support
10963 the v3 TLS handshake protocol, and are no longer allowed on the
10964 Tor network. Implements the client side of ticket 11150. Based on
10965 patches by Tom van der Woerdt.
10968 - Add unit tests to check for common RNG failure modes, such as
10969 returning all zeroes, identical values, or incrementing values
10970 (OpenSSL's rand_predictable feature). Patch by "teor".
10971 - Log more information when the backtrace tests fail. Closes ticket
10972 17892. Patch from "cypherpunks."
10973 - Always test both ed25519 backends, so that we can be sure that our
10974 batch-open replacement code works. Part of ticket 16794.
10975 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
10976 portion of ticket 16831.
10977 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
10978 util_format.c, directory.c, and options_validate.c. Closes tickets
10979 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
10981 - Unit tests for directory_handle_command_get. Closes ticket 17004.
10982 Patch from Reinaldo de Souza Jr.
10985 Changes in version 0.2.7.6 - 2015-12-10
10986 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
10987 well as a minor bug in hidden service reliability.
10989 o Major bugfixes (guard selection):
10990 - Actually look at the Guard flag when selecting a new directory
10991 guard. When we implemented the directory guard design, we
10992 accidentally started treating all relays as if they have the Guard
10993 flag during guard selection, leading to weaker anonymity and worse
10994 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
10997 o Minor features (geoip):
10998 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
11001 o Minor bugfixes (compilation):
11002 - When checking for net/pfvar.h, include netinet/in.h if possible.
11003 This fixes transparent proxy detection on OpenBSD. Fixes bug
11004 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
11005 - Fix a compilation warning with Clang 3.6: Do not check the
11006 presence of an address which can never be NULL. Fixes bug 17781.
11008 o Minor bugfixes (correctness):
11009 - When displaying an IPv6 exit policy, include the mask bits
11010 correctly even when the number is greater than 31. Fixes bug
11011 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
11012 - The wrong list was used when looking up expired intro points in a
11013 rend service object, causing what we think could be reachability
11014 issues for hidden services, and triggering a BUG log. Fixes bug
11015 16702; bugfix on 0.2.7.2-alpha.
11016 - Fix undefined behavior in the tor_cert_checksig function. Fixes
11017 bug 17722; bugfix on 0.2.7.2-alpha.
11020 Changes in version 0.2.7.5 - 2015-11-20
11021 The Tor 0.2.7 release series is dedicated to the memory of Tor user
11022 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
11023 tirelessly to advocate human rights regardless of national borders,
11024 and oppose the encroachments of mass surveillance. He opposed national
11025 exceptionalism, he brought clarity to legal and policy debates, he
11026 understood and predicted the impact of mass surveillance on the world,
11027 and he laid the groundwork for resisting it. While serving on the Tor
11028 Project's board of directors, he brought us his uncompromising focus
11029 on technical excellence in the service of humankind. Caspar was an
11030 inimitable force for good and a wonderful friend. He was kind,
11031 humorous, generous, gallant, and believed we should protect one
11032 another without exception. We honor him here for his ideals, his
11033 efforts, and his accomplishments. Please honor his memory with works
11034 that would make him proud.
11036 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
11038 The 0.2.7 series adds a more secure identity key type for relays,
11039 improves cryptography performance, resolves several longstanding
11040 hidden-service performance issues, improves controller support for
11041 hidden services, and includes small bugfixes and performance
11042 improvements throughout the program. This release series also includes
11043 more tests than before, and significant simplifications to which parts
11044 of Tor invoke which others.
11046 (This release contains no code changes since 0.2.7.4-rc.)
11049 Changes in version 0.2.7.4-rc - 2015-10-21
11050 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
11051 fixes some important memory leaks, and a scary-looking (but mostly
11052 harmless in practice) invalid-read bug. It also has a few small
11053 bugfixes, notably fixes for compilation and portability on different
11054 platforms. If no further significant bounds are found, the next
11055 release will the the official stable release.
11057 o Major bugfixes (security, correctness):
11058 - Fix an error that could cause us to read 4 bytes before the
11059 beginning of an openssl string. This bug could be used to cause
11060 Tor to crash on systems with unusual malloc implementations, or
11061 systems with unusual hardening installed. Fixes bug 17404; bugfix
11064 o Major bugfixes (correctness):
11065 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
11066 bug 17401; bugfix on 0.2.7.3-rc.
11068 o Major bugfixes (memory leaks):
11069 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
11070 17398; bugfix on 0.2.6.1-alpha.
11071 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
11072 17402; bugfix on 0.2.7.3-rc.
11073 - Fix a memory leak when reading an expired signing key from disk.
11074 Fixes bug 17403; bugfix on 0.2.7.2-rc.
11076 o Minor features (geoIP):
11077 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
11080 o Minor bugfixes (compilation):
11081 - Repair compilation with the most recent (unreleased, alpha)
11082 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
11083 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
11084 17251; bugfix on 0.2.7.2-alpha.
11085 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
11086 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
11088 o Minor bugfixes (portability):
11089 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
11090 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
11093 o Minor bugfixes (sandbox):
11094 - Add the "hidserv-stats" filename to our sandbox filter for the
11095 HiddenServiceStatistics option to work properly. Fixes bug 17354;
11096 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
11098 o Minor bugfixes (testing):
11099 - Add unit tests for get_interface_address* failure cases. Fixes bug
11100 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
11101 - Fix breakage when running 'make check' with BSD make. Fixes bug
11102 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
11103 - Make the get_ifaddrs_* unit tests more tolerant of different
11104 network configurations. (Don't assume every test box has an IPv4
11105 address, and don't assume every test box has a non-localhost
11106 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
11107 - Skip backtrace tests when backtrace support is not compiled in.
11108 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
11112 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
11113 - Note that HiddenServicePorts can take a unix domain socket. Closes
11117 Changes in version 0.2.7.3-rc - 2015-09-25
11118 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
11119 contains numerous usability fixes for Ed25519 keys, safeguards against
11120 several misconfiguration problems, significant simplifications to
11121 Tor's callgraph, and numerous bugfixes and small features.
11123 This is the most tested release of Tor to date. The unit tests cover
11124 39.40% of the code, and the integration tests (accessible with "make
11125 test-full-online", requiring stem and chutney and a network
11126 connection) raise the coverage to 64.49%.
11128 o Major features (security, hidden services):
11129 - Hidden services, if using the EntryNodes option, are required to
11130 use more than one EntryNode, in order to avoid a guard discovery
11131 attack. (This would only affect people who had configured hidden
11132 services and manually specified the EntryNodes option with a
11133 single entry-node. The impact was that it would be easy to
11134 remotely identify the guard node used by such a hidden service.
11135 See ticket for more information.) Fixes ticket 14917.
11137 o Major features (Ed25519 keys, keypinning):
11138 - The key-pinning option on directory authorities is now advisory-
11139 only by default. In a future version, or when the AuthDirPinKeys
11140 option is set, pins are enforced again. Disabling key-pinning
11141 seemed like a good idea so that we can survive the fallout of any
11142 usability problems associated with Ed25519 keys. Closes
11145 o Major features (Ed25519 performance):
11146 - Improve the speed of Ed25519 operations and Curve25519 keypair
11147 generation when built targeting 32 bit x86 platforms with SSE2
11148 available. Implements ticket 16535.
11149 - Improve the runtime speed of Ed25519 signature verification by
11150 using Ed25519-donna's batch verification support. Implements
11153 o Major features (performance testing):
11154 - The test-network.sh script now supports performance testing.
11155 Requires corresponding chutney performance testing changes. Patch
11156 by "teor". Closes ticket 14175.
11158 o Major features (relay, Ed25519):
11159 - Significant usability improvements for Ed25519 key management. Log
11160 messages are better, and the code can recover from far more
11161 failure conditions. Thanks to "s7r" for reporting and diagnosing
11163 - Add a new OfflineMasterKey option to tell Tor never to try loading
11164 or generating a secret Ed25519 identity key. You can use this in
11165 combination with tor --keygen to manage offline and/or encrypted
11166 Ed25519 keys. Implements ticket 16944.
11167 - Add a --newpass option to allow changing or removing the
11168 passphrase of an encrypted key with tor --keygen. Implements part
11170 - On receiving a HUP signal, check to see whether the Ed25519
11171 signing key has changed, and reload it if so. Closes ticket 16790.
11173 o Major bugfixes (relay, Ed25519):
11174 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
11175 0.2.7.2-alpha. Reported by "s7r".
11176 - Improve handling of expired signing keys with offline master keys.
11177 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
11179 o Minor features (client-side privacy):
11180 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
11181 lifespan when IsolateSOCKSAuth and streams with SOCKS
11182 authentication are attached to the circuit. This allows
11183 applications like TorBrowser to manage circuit lifetime on their
11184 own. Implements feature 15482.
11185 - When logging malformed hostnames from SOCKS5 requests, respect
11186 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
11188 o Minor features (compilation):
11189 - Give a warning as early as possible when trying to build with an
11190 unsupported OpenSSL version. Closes ticket 16901.
11191 - Fail during configure if we're trying to build against an OpenSSL
11192 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
11193 which started requiring ECC.
11195 o Minor features (geoip):
11196 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
11199 o Minor features (hidden services):
11200 - Relays need to have the Fast flag to get the HSDir flag. As this
11201 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
11202 drop. This change should make some attacks against the hidden
11203 service directory system harder. Fixes ticket 15963.
11204 - Turn on hidden service statistics collection by setting the torrc
11205 option HiddenServiceStatistics to "1" by default. (This keeps
11206 track only of the fraction of traffic used by hidden services, and
11207 the total number of hidden services in existence.) Closes
11209 - Client now uses an introduction point failure cache to know when
11210 to fetch or keep a descriptor in their cache. Previously, failures
11211 were recorded implicitly, but not explicitly remembered. Closes
11214 o Minor features (testing, authorities, documentation):
11215 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
11216 explicitly manage consensus flags in testing networks. Patch by
11217 "robgjansen", modified by "teor". Implements part of ticket 14882.
11219 o Minor bugfixes (security, exit policies):
11220 - ExitPolicyRejectPrivate now also rejects the relay's published
11221 IPv6 address (if any), and any publicly routable IPv4 or IPv6
11222 addresses on any local interfaces. ticket 17027. Patch by "teor".
11223 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
11225 o Minor bug fixes (torrc exit policies):
11226 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
11227 produce IPv6 wildcard addresses. Previously they would produce
11228 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
11229 of bug 16069; bugfix on 0.2.4.7-alpha.
11230 - When parsing torrc ExitPolicies, we now warn for a number of cases
11231 where the user's intent is likely to differ from Tor's actual
11232 behavior. These include: using an IPv4 address with an accept6 or
11233 reject6 line; using "private" on an accept6 or reject6 line; and
11234 including any ExitPolicy lines after accept *:* or reject *:*.
11235 Related to ticket 16069.
11236 - When parsing torrc ExitPolicies, we now issue an info-level
11237 message when expanding an "accept/reject *" line to include both
11238 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
11239 - In each instance above, usage advice is provided to avoid the
11240 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
11241 16069; bugfix on 0.2.4.7-alpha.
11243 o Minor bugfixes (authority):
11244 - Don't assign "HSDir" to a router if it isn't Valid and Running.
11245 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
11246 - Downgrade log messages about Ed25519 key issues if they are in old
11247 cached router descriptors. Fixes part of bug 16286; bugfix
11249 - When we find an Ed25519 key issue in a cached descriptor, stop
11250 saying the descriptor was just "uploaded". Fixes another part of
11251 bug 16286; bugfix on 0.2.7.2-alpha.
11253 o Minor bugfixes (control port):
11254 - Repair a warning and a spurious result when getting the maximum
11255 number of file descriptors from the controller. Fixes bug 16697;
11256 bugfix on 0.2.7.2-alpha.
11258 o Minor bugfixes (correctness):
11259 - When calling channel_free_list(), avoid calling smartlist_remove()
11260 while inside a FOREACH loop. This partially reverts commit
11261 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
11262 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
11264 o Minor bugfixes (documentation):
11265 - Advise users on how to configure separate IPv4 and IPv6 exit
11266 policies in the manpage and sample torrcs. Related to ticket 16069.
11267 - Fix the usage message of tor-resolve(1) so that it no longer lists
11268 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
11269 - Fix an error in the manual page and comments for
11270 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
11271 required "ORPort connectivity". While this is true, it is in no
11272 way unique to the HSDir flag. Of all the flags, only HSDirs need a
11273 DirPort configured in order for the authorities to assign that
11274 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
11277 o Minor bugfixes (Ed25519):
11278 - Fix a memory leak when reading router descriptors with expired
11279 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
11281 o Minor bugfixes (linux seccomp2 sandbox):
11282 - Allow bridge authorities to run correctly under the seccomp2
11283 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
11284 - Allow routers with ed25519 keys to run correctly under the
11285 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
11287 o Minor bugfixes (open file limit):
11288 - Fix set_max_file_descriptors() to set by default the max open file
11289 limit to the current limit when setrlimit() fails. Fixes bug
11290 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
11292 o Minor bugfixes (portability):
11293 - Try harder to normalize the exit status of the Tor process to the
11294 standard-provided range. Fixes bug 16975; bugfix on every version
11296 - Check correctly for Windows socket errors in the workqueue
11297 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
11298 - Fix the behavior of crypto_rand_time_range() when told to consider
11299 times before 1970. (These times were possible when running in a
11300 simulated network environment where time()'s output starts at
11301 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
11302 - Restore correct operation of TLS client-cipher detection on
11303 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
11305 o Minor bugfixes (relay):
11306 - Ensure that worker threads actually exit when a fatal error or
11307 shutdown is indicated. This fix doesn't currently affect the
11308 behavior of Tor, because Tor workers never indicates fatal error
11309 or shutdown except in the unit tests. Fixes bug 16868; bugfix
11311 - Unblock threads before releasing the work queue mutex to ensure
11312 predictable scheduling behavior. Fixes bug 16644; bugfix
11315 o Code simplification and refactoring:
11316 - Change the function that's called when we need to retry all
11317 downloads so that it only reschedules the downloads to happen
11318 immediately, rather than launching them all at once itself. This
11319 further simplifies Tor's callgraph.
11320 - Move some format-parsing functions out of crypto.c and
11321 crypto_curve25519.c into crypto_format.c and/or util_format.c.
11322 - Move the client-only parts of init_keys() into a separate
11323 function. Closes ticket 16763.
11324 - Simplify the microdesc_free() implementation so that it no longer
11325 appears (to code analysis tools) to potentially invoke a huge
11326 suite of other microdesc functions.
11327 - Simply the control graph further by deferring the inner body of
11328 directory_all_unreachable() into a callback. Closes ticket 16762.
11329 - Treat the loss of an owning controller as equivalent to a SIGTERM
11330 signal. This removes a tiny amount of duplicated code, and
11331 simplifies our callgraph. Closes ticket 16788.
11332 - When generating an event to send to the controller, we no longer
11333 put the event over the network immediately. Instead, we queue
11334 these events, and use a Libevent callback to deliver them. This
11335 change simplifies Tor's callgraph by reducing the number of
11336 functions from which all other Tor functions are reachable. Closes
11338 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
11339 that try to scan or compile every file on Unix won't decide that
11341 - Remove the unused "nulterminate" argument from buf_pullup().
11344 - Recommend a 40 GB example AccountingMax in torrc.sample rather
11345 than a 4 GB max. Closes ticket 16742.
11346 - Include the TUNING document in our source tarball. It is referred
11347 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
11351 - The internal pure-C tor-fw-helper tool is now removed from the Tor
11352 distribution, in favor of the pure-Go clone available from
11353 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
11354 used by the C tor-fw-helper are not, in our opinion, very
11355 confidence- inspiring in their secure-programming techniques.
11356 Closes ticket 13338.
11357 - Remove the code that would try to aggressively flush controller
11358 connections while writing to them. This code was introduced in
11359 0.1.2.7-alpha, in order to keep output buffers from exceeding
11360 their limits. But there is no longer a maximum output buffer size,
11361 and flushing data in this way caused some undesirable recursions
11362 in our call graph. Closes ticket 16480.
11365 - Make "bridges+hs" the default test network. This tests almost all
11366 tor functionality during make test-network, while allowing tests
11367 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
11368 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
11369 (chutney). Patches by "teor".
11370 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
11371 by-side in the same parent directory. Closes ticket 16903. Patch
11373 - Use environment variables rather than autoconf substitutions to
11374 send variables from the build system to the test scripts. This
11375 change should be easier to maintain, and cause 'make distcheck' to
11376 work better than before. Fixes bug 17148.
11377 - Add a new set of callgraph analysis scripts that use clang to
11378 produce a list of which Tor functions are reachable from which
11379 other Tor functions. We're planning to use these to help simplify
11380 our code structure by identifying illogical dependencies.
11381 - Add new 'test-full' and 'test-full-online' targets to run all
11382 tests, including integration tests with stem and chutney.
11383 - Make the test-workqueue test work on Windows by initializing the
11384 network before we begin.
11385 - New make target (make test-network-all) to run multiple applicable
11386 chutney test cases. Patch from Teor; closes 16953.
11387 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
11388 functions in dns.c. Implements a portion of ticket 16831.
11389 - When building Tor with testing coverage enabled, run Chutney tests
11390 (if any) using the 'tor-cov' coverage binary.
11391 - When running test-network or test-stem, check for the absence of
11392 stem/chutney before doing any build operations.
11395 Changes in version 0.2.7.2-alpha - 2015-07-27
11396 This, the second alpha in the Tor 0.2.7 series, has a number of new
11397 features, including a way to manually pick the number of introduction
11398 points for hidden services, and the much stronger Ed25519 signing key
11399 algorithm for regular Tor relays (including support for encrypted
11400 offline identity keys in the new algorithm).
11402 Support for Ed25519 on relays is currently limited to signing router
11403 descriptors; later alphas in this series will extend Ed25519 key
11404 support to more parts of the Tor protocol.
11406 o Major features (Ed25519 identity keys, Proposal 220):
11407 - All relays now maintain a stronger identity key, using the Ed25519
11408 elliptic curve signature format. This master key is designed so
11409 that it can be kept offline. Relays also generate an online
11410 signing key, and a set of other Ed25519 keys and certificates.
11411 These are all automatically regenerated and rotated as needed.
11412 Implements part of ticket 12498.
11413 - Directory authorities now vote on Ed25519 identity keys along with
11414 RSA1024 keys. Implements part of ticket 12498.
11415 - Directory authorities track which Ed25519 identity keys have been
11416 used with which RSA1024 identity keys, and do not allow them to
11417 vary freely. Implements part of ticket 12498.
11418 - Microdescriptors now include Ed25519 identity keys. Implements
11419 part of ticket 12498.
11420 - Add support for offline encrypted Ed25519 master keys. To use this
11421 feature on your tor relay, run "tor --keygen" to make a new master
11422 key (or to make a new signing key if you already have a master
11423 key). Closes ticket 13642.
11425 o Major features (Hidden services):
11426 - Add the torrc option HiddenServiceNumIntroductionPoints, to
11427 specify a fixed number of introduction points. Its maximum value
11428 is 10 and default is 3. Using this option can increase a hidden
11429 service's reliability under load, at the cost of making it more
11430 visible that the hidden service is facing extra load. Closes
11432 - Remove the adaptive algorithm for choosing the number of
11433 introduction points, which used to change the number of
11434 introduction points (poorly) depending on the number of
11435 connections the HS sees. Closes ticket 4862.
11437 o Major features (onion key cross-certification):
11438 - Relay descriptors now include signatures of their own identity
11439 keys, made using the TAP and ntor onion keys. These signatures
11440 allow relays to prove ownership of their own onion keys. Because
11441 of this change, microdescriptors will no longer need to include
11442 RSA identity keys. Implements proposal 228; closes ticket 12499.
11444 o Major features (performance):
11445 - Improve the runtime speed of Ed25519 operations by using the
11446 public-domain Ed25519-donna by Andrew M. ("floodyberry").
11447 Implements ticket 16467.
11448 - Improve the runtime speed of the ntor handshake by using an
11449 optimized curve25519 basepoint scalarmult implementation from the
11450 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
11451 ideas by Adam Langley. Implements ticket 9663.
11453 o Major bugfixes (client-side privacy, also in 0.2.6.9):
11454 - Properly separate out each SOCKSPort when applying stream
11455 isolation. The error occurred because each port's session group
11456 was being overwritten by a default value when the listener
11457 connection was initialized. Fixes bug 16247; bugfix on
11458 0.2.6.3-alpha. Patch by "jojelino".
11460 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
11461 - Stop refusing to store updated hidden service descriptors on a
11462 client. This reverts commit 9407040c59218 (which indeed fixed bug
11463 14219, but introduced a major hidden service reachability
11464 regression detailed in bug 16381). This is a temporary fix since
11465 we can live with the minor issue in bug 14219 (it just results in
11466 some load on the network) but the regression of 16381 is too much
11467 of a setback. First-round fix for bug 16381; bugfix
11470 o Major bugfixes (hidden services):
11471 - When cannibalizing a circuit for an introduction point, always
11472 extend to the chosen exit node (creating a 4 hop circuit).
11473 Previously Tor would use the current circuit exit node, which
11474 changed the original choice of introduction point, and could cause
11475 the hidden service to skip excluded introduction points or
11476 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
11479 o Major bugfixes (open file limit):
11480 - The open file limit wasn't checked before calling
11481 tor_accept_socket_nonblocking(), which would make Tor exceed the
11482 limit. Now, before opening a new socket, Tor validates the open
11483 file limit just before, and if the max has been reached, return an
11484 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
11486 o Major bugfixes (stability, also in 0.2.6.10):
11487 - Stop crashing with an assertion failure when parsing certain kinds
11488 of malformed or truncated microdescriptors. Fixes bug 16400;
11489 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
11490 by "cypherpunks_backup".
11491 - Stop random client-side assertion failures that could occur when
11492 connecting to a busy hidden service, or connecting to a hidden
11493 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
11496 o Minor features (directory authorities, security, also in 0.2.6.9):
11497 - The HSDir flag given by authorities now requires the Stable flag.
11498 For the current network, this results in going from 2887 to 2806
11499 HSDirs. Also, it makes it harder for an attacker to launch a sybil
11500 attack by raising the effort for a relay to become Stable to
11501 require at the very least 7 days, while maintaining the 96 hours
11502 uptime requirement for HSDir. Implements ticket 8243.
11504 o Minor features (client):
11505 - Relax the validation of hostnames in SOCKS5 requests, allowing the
11506 character '_' to appear, in order to cope with domains observed in
11507 the wild that are serving non-RFC compliant records. Resolves
11509 - Relax the validation done to hostnames in SOCKS5 requests, and
11510 allow a single trailing '.' to cope with clients that pass FQDNs
11511 using that syntax to explicitly indicate that the domain name is
11512 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
11513 - Add GroupWritable and WorldWritable options to unix-socket based
11514 SocksPort and ControlPort options. These options apply to a single
11515 socket, and override {Control,Socks}SocketsGroupWritable. Closes
11518 o Minor features (control protocol):
11519 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
11520 the control protocol. Resolves ticket 15358.
11522 o Minor features (directory authorities):
11523 - Directory authorities no longer vote against the "Fast", "Stable",
11524 and "HSDir" flags just because they were going to vote against
11525 "Running": if the consensus turns out to be that the router was
11526 running, then the authority's vote should count. Patch from Peter
11527 Retzlaff; closes issue 8712.
11529 o Minor features (geoip, also in 0.2.6.10):
11530 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
11531 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
11533 o Minor features (hidden services):
11534 - Add the new options "HiddenServiceMaxStreams" and
11535 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
11536 limit the maximum number of simultaneous streams per circuit, and
11537 optionally tear down the circuit when the limit is exceeded. Part
11540 o Minor features (portability):
11541 - Use C99 variadic macros when the compiler is not GCC. This avoids
11542 failing compilations on MSVC, and fixes a log-file-based race
11543 condition in our old workarounds. Original patch from Gisle Vanem.
11545 o Minor bugfixes (compilation, also in 0.2.6.9):
11546 - Build with --enable-systemd correctly when libsystemd is
11547 installed, but systemd is not. Fixes bug 16164; bugfix on
11548 0.2.6.3-alpha. Patch from Peter Palfrader.
11550 o Minor bugfixes (controller):
11551 - Add the descriptor ID in each HS_DESC control event. It was
11552 missing, but specified in control-spec.txt. Fixes bug 15881;
11553 bugfix on 0.2.5.2-alpha.
11555 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
11556 - Check for failures from crypto_early_init, and refuse to continue.
11557 A previous typo meant that we could keep going with an
11558 uninitialized crypto library, and would have OpenSSL initialize
11559 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
11560 when implementing ticket 4900. Patch by "teor".
11562 o Minor bugfixes (hidden services):
11563 - Fix a crash when reloading configuration while at least one
11564 configured and one ephemeral hidden service exists. Fixes bug
11565 16060; bugfix on 0.2.7.1-alpha.
11566 - Avoid crashing with a double-free bug when we create an ephemeral
11567 hidden service but adding it fails for some reason. Fixes bug
11568 16228; bugfix on 0.2.7.1-alpha.
11570 o Minor bugfixes (Linux seccomp2 sandbox):
11571 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
11572 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
11574 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
11575 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
11576 these when eventfd2() support is missing. Fixes bug 16363; bugfix
11577 on 0.2.6.3-alpha. Patch from "teor".
11579 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
11580 - Fix sandboxing to work when running as a relay, by allowing the
11581 renaming of secret_id_key, and allowing the eventfd2 and futex
11582 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
11584 - Allow systemd connections to work with the Linux seccomp2 sandbox
11585 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
11588 o Minor bugfixes (relay):
11589 - Fix a rarely-encountered memory leak when failing to initialize
11590 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
11591 from "cypherpunks".
11593 o Minor bugfixes (systemd):
11594 - Fix an accidental formatting error that broke the systemd
11595 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
11596 - Tor's systemd unit file no longer contains extraneous spaces.
11597 These spaces would sometimes confuse tools like deb-systemd-
11598 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
11600 o Minor bugfixes (tests):
11601 - Use the configured Python executable when running test-stem-full.
11602 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
11604 o Minor bugfixes (tests, also in 0.2.6.9):
11605 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
11606 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
11608 o Minor bugfixes (threads, comments):
11609 - Always initialize return value in compute_desc_id in rendcommon.c
11610 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
11611 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
11612 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
11613 - Remove undefined directive-in-macro in test_util_writepid clang
11614 3.7 complains that using a preprocessor directive inside a macro
11615 invocation in test_util_writepid in test_util.c is undefined.
11616 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
11618 o Code simplification and refactoring:
11619 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
11620 to ensure they remain consistent and visible everywhere.
11621 - Remove some vestigial workarounds for the MSVC6 compiler. We
11622 haven't supported that in ages.
11623 - The link authentication code has been refactored for better
11624 testability and reliability. It now uses code generated with the
11625 "trunnel" binary encoding generator, to reduce the risk of bugs
11626 due to programmer error. Done as part of ticket 12498.
11629 - Include a specific and (hopefully) accurate documentation of the
11630 torrc file's meta-format in doc/torrc_format.txt. This is mainly
11631 of interest to people writing programs to parse or generate torrc
11632 files. This document is not a commitment to long-term
11633 compatibility; some aspects of the current format are a bit
11634 ridiculous. Closes ticket 2325.
11636 o Removed features:
11637 - Tor no longer supports copies of OpenSSL that are missing support
11638 for Elliptic Curve Cryptography. (We began using ECC when
11639 available in 0.2.4.8-alpha, for more safe and efficient key
11640 negotiation.) In particular, support for at least one of P256 or
11641 P224 is now required, with manual configuration needed if only
11642 P224 is available. Resolves ticket 16140.
11643 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
11644 on an operating system that has not upgraded to OpenSSL 1.0 or
11645 later, and you compile Tor from source, you will need to install a
11646 more recent OpenSSL to link Tor against.) These versions of
11647 OpenSSL are still supported by the OpenSSL, but the numerous
11648 cryptographic improvements in later OpenSSL releases makes them a
11649 clear choice. Resolves ticket 16034.
11650 - Remove the HidServDirectoryV2 option. Now all relays offer to
11651 store hidden service descriptors. Related to 16543.
11652 - Remove the VoteOnHidServDirectoriesV2 option, since all
11653 authorities have long set it to 1. Closes ticket 16543.
11656 - Document use of coverity, clang static analyzer, and clang dynamic
11657 undefined behavior and address sanitizers in doc/HACKING. Include
11658 detailed usage instructions in the blacklist. Patch by "teor".
11659 Closes ticket 15817.
11660 - The link authentication protocol code now has extensive tests.
11661 - The relay descriptor signature testing code now has
11663 - The test_workqueue program now runs faster, and is enabled by
11664 default as a part of "make check".
11665 - Now that OpenSSL has its own scrypt implementation, add an unit
11666 test that checks for interoperability between libscrypt_scrypt()
11667 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
11668 and rely on EVP_PBE_scrypt() whenever possible. Resolves
11672 Changes in version 0.2.6.10 - 2015-07-12
11673 Tor version 0.2.6.10 fixes some significant stability and hidden
11674 service client bugs, bulletproofs the cryptography init process, and
11675 fixes a bug when using the sandbox code with some older versions of
11676 Linux. Everyone running an older version, especially an older version
11677 of 0.2.6, should upgrade.
11679 o Major bugfixes (hidden service clients, stability):
11680 - Stop refusing to store updated hidden service descriptors on a
11681 client. This reverts commit 9407040c59218 (which indeed fixed bug
11682 14219, but introduced a major hidden service reachability
11683 regression detailed in bug 16381). This is a temporary fix since
11684 we can live with the minor issue in bug 14219 (it just results in
11685 some load on the network) but the regression of 16381 is too much
11686 of a setback. First-round fix for bug 16381; bugfix
11689 o Major bugfixes (stability):
11690 - Stop crashing with an assertion failure when parsing certain kinds
11691 of malformed or truncated microdescriptors. Fixes bug 16400;
11692 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
11693 by "cypherpunks_backup".
11694 - Stop random client-side assertion failures that could occur when
11695 connecting to a busy hidden service, or connecting to a hidden
11696 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
11699 o Minor features (geoip):
11700 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
11701 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
11703 o Minor bugfixes (crypto error-handling):
11704 - Check for failures from crypto_early_init, and refuse to continue.
11705 A previous typo meant that we could keep going with an
11706 uninitialized crypto library, and would have OpenSSL initialize
11707 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
11708 when implementing ticket 4900. Patch by "teor".
11710 o Minor bugfixes (Linux seccomp2 sandbox):
11711 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
11712 these when eventfd2() support is missing. Fixes bug 16363; bugfix
11713 on 0.2.6.3-alpha. Patch from "teor".
11716 Changes in version 0.2.6.9 - 2015-06-11
11717 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
11718 requirements for receiving an HSDir flag, and addresses some other small
11719 bugs in the systemd and sandbox code. Clients using circuit isolation
11720 should upgrade; all directory authorities should upgrade.
11722 o Major bugfixes (client-side privacy):
11723 - Properly separate out each SOCKSPort when applying stream
11724 isolation. The error occurred because each port's session group was
11725 being overwritten by a default value when the listener connection
11726 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
11729 o Minor feature (directory authorities, security):
11730 - The HSDir flag given by authorities now requires the Stable flag.
11731 For the current network, this results in going from 2887 to 2806
11732 HSDirs. Also, it makes it harder for an attacker to launch a sybil
11733 attack by raising the effort for a relay to become Stable which
11734 takes at the very least 7 days to do so and by keeping the 96
11735 hours uptime requirement for HSDir. Implements ticket 8243.
11737 o Minor bugfixes (compilation):
11738 - Build with --enable-systemd correctly when libsystemd is
11739 installed, but systemd is not. Fixes bug 16164; bugfix on
11740 0.2.6.3-alpha. Patch from Peter Palfrader.
11742 o Minor bugfixes (Linux seccomp2 sandbox):
11743 - Fix sandboxing to work when running as a relaymby renaming of
11744 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
11745 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
11746 - Allow systemd connections to work with the Linux seccomp2 sandbox
11747 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
11750 o Minor bugfixes (tests):
11751 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
11752 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
11755 Changes in version 0.2.6.8 - 2015-05-21
11756 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
11757 fixes an authority-side bug in assigning the HSDir flag. All directory
11758 authorities should upgrade.
11760 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
11761 - Revert commit that made directory authorities assign the HSDir
11762 flag to relays without a DirPort; this was bad because such relays
11763 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
11766 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
11767 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11768 a client authorized hidden service. Fixes bug 15823; bugfix
11771 o Minor features (geoip):
11772 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
11773 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
11777 Changes in version 0.2.7.1-alpha - 2015-05-12
11778 Tor 0.2.7.1-alpha is the first alpha release in its series. It
11779 includes numerous small features and bugfixes against previous Tor
11780 versions, and numerous small infrastructure improvements. The most
11781 notable features are several new ways for controllers to interact with
11782 the hidden services subsystem.
11784 o New system requirements:
11785 - Tor no longer includes workarounds to support Libevent versions
11786 before 1.3e. Libevent 2.0 or later is recommended. Closes
11789 o Major features (controller):
11790 - Add the ADD_ONION and DEL_ONION commands that allow the creation
11791 and management of hidden services via the controller. Closes
11793 - New "GETINFO onions/current" and "GETINFO onions/detached"
11794 commands to get information about hidden services created via the
11795 controller. Part of ticket 6411.
11796 - New HSFETCH command to launch a request for a hidden service
11797 descriptor. Closes ticket 14847.
11798 - New HSPOST command to upload a hidden service descriptor. Closes
11799 ticket 3523. Patch by "DonnchaC".
11801 o Major bugfixes (hidden services):
11802 - Revert commit that made directory authorities assign the HSDir
11803 flag to relays without a DirPort; this was bad because such relays
11804 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
11807 o Minor features (clock-jump tolerance):
11808 - Recover better when our clock jumps back many hours, like might
11809 happen for Tails or Whonix users who start with a very wrong
11810 hardware clock, use Tor to discover a more accurate time, and then
11811 fix their clock. Resolves part of ticket 8766.
11813 o Minor features (command-line interface):
11814 - Make --hash-password imply --hush to prevent unnecessary noise.
11815 Closes ticket 15542. Patch from "cypherpunks".
11816 - Print a warning whenever we find a relative file path being used
11817 as torrc option. Resolves issue 14018.
11819 o Minor features (controller):
11820 - Add DirAuthority lines for default directory authorities to the
11821 output of the "GETINFO config/defaults" command if not already
11822 present. Implements ticket 14840.
11823 - Controllers can now use "GETINFO hs/client/desc/id/..." to
11824 retrieve items from the client's hidden service descriptor cache.
11825 Closes ticket 14845.
11826 - Implement a new controller command "GETINFO status/fresh-relay-
11827 descs" to fetch a descriptor/extrainfo pair that was generated on
11828 demand just for the controller's use. Implements ticket 14784.
11830 o Minor features (DoS-resistance):
11831 - Make it harder for attackers to overload hidden services with
11832 introductions, by blocking multiple introduction requests on the
11833 same circuit. Resolves ticket 15515.
11835 o Minor features (geoip):
11836 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
11837 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
11840 o Minor features (HS popularity countermeasure):
11841 - To avoid leaking HS popularity, don't cycle the introduction point
11842 when we've handled a fixed number of INTRODUCE2 cells but instead
11843 cycle it when a random number of introductions is reached, thus
11844 making it more difficult for an attacker to find out the amount of
11845 clients that have used the introduction point for a specific HS.
11846 Closes ticket 15745.
11848 o Minor features (logging):
11849 - Include the Tor version in all LD_BUG log messages, since people
11850 tend to cut and paste those into the bugtracker. Implements
11853 o Minor features (pluggable transports):
11854 - When launching managed pluggable transports on Linux systems,
11855 attempt to have the kernel deliver a SIGTERM on tor exit if the
11856 pluggable transport process is still running. Resolves
11858 - When launching managed pluggable transports, setup a valid open
11859 stdin in the child process that can be used to detect if tor has
11860 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
11861 can be used by implementations to detect this new behavior.
11862 Resolves ticket 15435.
11864 o Minor features (testing):
11865 - Add a test to verify that the compiler does not eliminate our
11866 memwipe() implementation. Closes ticket 15377.
11867 - Add make rule `check-changes` to verify the format of changes
11868 files. Closes ticket 15180.
11869 - Add unit tests for control_event_is_interesting(). Add a compile-
11870 time check that the number of events doesn't exceed the capacity
11871 of control_event_t.event_mask. Closes ticket 15431, checks for
11872 bugs similar to 13085. Patch by "teor".
11873 - Command-line argument tests moved to Stem. Resolves ticket 14806.
11874 - Integrate the ntor, backtrace, and zero-length keys tests into the
11875 automake test suite. Closes ticket 15344.
11876 - Remove assertions during builds to determine Tor's test coverage.
11877 We don't want to trigger these even in assertions, so including
11878 them artificially makes our branch coverage look worse than it is.
11879 This patch provides the new test-stem-full and coverage-html-full
11880 configure options. Implements ticket 15400.
11882 o Minor bugfixes (build):
11883 - Improve out-of-tree builds by making non-standard rules work and
11884 clean up additional files and directories. Fixes bug 15053; bugfix
11887 o Minor bugfixes (command-line interface):
11888 - When "--quiet" is provided along with "--validate-config", do not
11889 write anything to stdout on success. Fixes bug 14994; bugfix
11891 - When complaining about bad arguments to "--dump-config", use
11892 stderr, not stdout.
11894 o Minor bugfixes (configuration, unit tests):
11895 - Only add the default fallback directories when the DirAuthorities,
11896 AlternateDirAuthority, and FallbackDir directory config options
11897 are set to their defaults. The default fallback directory list is
11898 currently empty, this fix will only change tor's behavior when it
11899 has default fallback directories. Includes unit tests for
11900 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
11901 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
11903 o Minor bugfixes (correctness):
11904 - For correctness, avoid modifying a constant string in
11905 handle_control_postdescriptor. Fixes bug 15546; bugfix
11907 - Remove side-effects from tor_assert() calls. This was harmless,
11908 because we never disable assertions, but it is bad style and
11909 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
11912 o Minor bugfixes (hidden service):
11913 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11914 a client authorized hidden service. Fixes bug 15823; bugfix
11916 - Remove an extraneous newline character from the end of hidden
11917 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
11919 o Minor bugfixes (interface):
11920 - Print usage information for --dump-config when it is used without
11921 an argument. Also, fix the error message to use different wording
11922 and add newline at the end. Fixes bug 15541; bugfix
11925 o Minor bugfixes (logs):
11926 - When building Tor under Clang, do not include an extra set of
11927 parentheses in log messages that include function names. Fixes bug
11928 15269; bugfix on every released version of Tor when compiled with
11929 recent enough Clang.
11931 o Minor bugfixes (network):
11932 - When attempting to use fallback technique for network interface
11933 lookup, disregard loopback and multicast addresses since they are
11934 unsuitable for public communications.
11936 o Minor bugfixes (statistics):
11937 - Disregard the ConnDirectionStatistics torrc options when Tor is
11938 not a relay since in that mode of operation no sensible data is
11939 being collected and because Tor might run into measurement hiccups
11940 when running as a client for some time, then becoming a relay.
11941 Fixes bug 15604; bugfix on 0.2.2.35.
11943 o Minor bugfixes (test networks):
11944 - When self-testing reachability, use ExtendAllowPrivateAddresses to
11945 determine if local/private addresses imply reachability. The
11946 previous fix used TestingTorNetwork, which implies
11947 ExtendAllowPrivateAddresses, but this excluded rare configurations
11948 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
11949 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
11950 issue discovered by CJ Ess.
11952 o Minor bugfixes (testing):
11953 - Check for matching value in server response in ntor_ref.py. Fixes
11954 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
11956 - Set the severity correctly when testing
11957 get_interface_addresses_ifaddrs() and
11958 get_interface_addresses_win32(), so that the tests fail gracefully
11959 instead of triggering an assertion. Fixes bug 15759; bugfix on
11960 0.2.6.3-alpha. Reported by Nicolas Derive.
11962 o Code simplification and refactoring:
11963 - Move the hacky fallback code out of get_interface_address6() into
11964 separate function and get it covered with unit-tests. Resolves
11966 - Refactor hidden service client-side cache lookup to intelligently
11967 report its various failure cases, and disentangle failure cases
11968 involving a lack of introduction points. Closes ticket 14391.
11969 - Use our own Base64 encoder instead of OpenSSL's, to allow more
11970 control over the output. Part of ticket 15652.
11973 - Improve the descriptions of statistics-related torrc options in
11974 the manpage to describe rationale and possible uses cases. Fixes
11976 - Improve the layout and formatting of ./configure --help messages.
11977 Closes ticket 15024. Patch from "cypherpunks".
11978 - Standardize on the term "server descriptor" in the manual page.
11979 Previously, we had used "router descriptor", "server descriptor",
11980 and "relay descriptor" interchangeably. Part of ticket 14987.
11983 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
11984 and always use the internal Base64 decoder. The internal decoder
11985 has been part of tor since 0.2.0.10-alpha, and no one should
11986 be using the OpenSSL one. Part of ticket 15652.
11987 - Remove the 'tor_strclear()' function; use memwipe() instead.
11988 Closes ticket 14922.
11990 o Removed features:
11991 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
11992 fingerprinting we now recommend pluggable transports; for forward-
11993 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
11994 - Remove the undocumented "--digests" command-line option. It
11995 complicated our build process, caused subtle build issues on
11996 multiple platforms, and is now redundant since we started
11997 including git version identifiers. Closes ticket 14742.
11998 - Tor no longer contains checks for ancient directory cache versions
11999 that didn't know about microdescriptors.
12000 - Tor no longer contains workarounds for stat files generated by
12001 super-old versions of Tor that didn't choose guards sensibly.
12004 Changes in version 0.2.4.27 - 2015-04-06
12005 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
12006 could be used by an attacker to crash hidden services, or crash clients
12007 visiting hidden services. Hidden services should upgrade as soon as
12008 possible; clients should upgrade whenever packages become available.
12010 This release also backports a simple improvement to make hidden
12011 services a bit less vulnerable to denial-of-service attacks.
12013 o Major bugfixes (security, hidden service):
12014 - Fix an issue that would allow a malicious client to trigger an
12015 assertion failure and halt a hidden service. Fixes bug 15600;
12016 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
12017 - Fix a bug that could cause a client to crash with an assertion
12018 failure when parsing a malformed hidden service descriptor. Fixes
12019 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
12021 o Minor features (DoS-resistance, hidden service):
12022 - Introduction points no longer allow multiple INTRODUCE1 cells to
12023 arrive on the same circuit. This should make it more expensive for
12024 attackers to overwhelm hidden services with introductions.
12025 Resolves ticket 15515.
12028 Changes in version 0.2.5.12 - 2015-04-06
12029 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
12030 could be used by an attacker to crash hidden services, or crash clients
12031 visiting hidden services. Hidden services should upgrade as soon as
12032 possible; clients should upgrade whenever packages become available.
12034 This release also backports a simple improvement to make hidden
12035 services a bit less vulnerable to denial-of-service attacks.
12037 o Major bugfixes (security, hidden service):
12038 - Fix an issue that would allow a malicious client to trigger an
12039 assertion failure and halt a hidden service. Fixes bug 15600;
12040 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
12041 - Fix a bug that could cause a client to crash with an assertion
12042 failure when parsing a malformed hidden service descriptor. Fixes
12043 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
12045 o Minor features (DoS-resistance, hidden service):
12046 - Introduction points no longer allow multiple INTRODUCE1 cells to
12047 arrive on the same circuit. This should make it more expensive for
12048 attackers to overwhelm hidden services with introductions.
12049 Resolves ticket 15515.
12052 Changes in version 0.2.6.7 - 2015-04-06
12053 Tor 0.2.6.7 fixes two security issues that could be used by an
12054 attacker to crash hidden services, or crash clients visiting hidden
12055 services. Hidden services should upgrade as soon as possible; clients
12056 should upgrade whenever packages become available.
12058 This release also contains two simple improvements to make hidden
12059 services a bit less vulnerable to denial-of-service attacks.
12061 o Major bugfixes (security, hidden service):
12062 - Fix an issue that would allow a malicious client to trigger an
12063 assertion failure and halt a hidden service. Fixes bug 15600;
12064 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
12065 - Fix a bug that could cause a client to crash with an assertion
12066 failure when parsing a malformed hidden service descriptor. Fixes
12067 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
12069 o Minor features (DoS-resistance, hidden service):
12070 - Introduction points no longer allow multiple INTRODUCE1 cells to
12071 arrive on the same circuit. This should make it more expensive for
12072 attackers to overwhelm hidden services with introductions.
12073 Resolves ticket 15515.
12074 - Decrease the amount of reattempts that a hidden service performs
12075 when its rendezvous circuits fail. This reduces the computational
12076 cost for running a hidden service under heavy load. Resolves
12080 Changes in version 0.2.6.6 - 2015-03-24
12081 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
12083 It adds numerous safety, security, correctness, and performance
12084 improvements. Client programs can be configured to use more kinds of
12085 sockets, AutomapHosts works better, the multithreading backend is
12086 improved, cell transmission is refactored, test coverage is much
12087 higher, more denial-of-service attacks are handled, guard selection is
12088 improved to handle long-term guards better, pluggable transports
12089 should work a bit better, and some annoying hidden service performance
12090 bugs should be addressed.
12092 o Minor bugfixes (portability):
12093 - Use the correct datatype in the SipHash-2-4 function to prevent
12094 compilers from assuming any sort of alignment. Fixes bug 15436;
12095 bugfix on 0.2.5.3-alpha.
12097 Changes in version 0.2.6.5-rc - 2015-03-18
12098 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
12099 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
12101 o Major bugfixes (client):
12102 - Avoid crashing when making certain configuration option changes on
12103 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
12106 o Major bugfixes (pluggable transports):
12107 - Initialize the extended OR Port authentication cookie before
12108 launching pluggable transports. This prevents a race condition
12109 that occurred when server-side pluggable transports would cache the
12110 authentication cookie before it has been (re)generated. Fixes bug
12111 15240; bugfix on 0.2.5.1-alpha.
12113 o Major bugfixes (portability):
12114 - Do not crash on startup when running on Solaris. Fixes a bug
12115 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
12118 o Minor features (heartbeat):
12119 - On relays, report how many connections we negotiated using each
12120 version of the Tor link protocols. This information will let us
12121 know if removing support for very old versions of the Tor
12122 protocols is harming the network. Closes ticket 15212.
12124 o Code simplification and refactoring:
12125 - Refactor main loop to extract the 'loop' part. This makes it
12126 easier to run Tor under Shadow. Closes ticket 15176.
12129 Changes in version 0.2.5.11 - 2015-03-17
12130 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
12132 It backports several bugfixes from the 0.2.6 branch, including a
12133 couple of medium-level security fixes for relays and exit nodes.
12134 It also updates the list of directory authorities.
12136 o Directory authority changes:
12137 - Remove turtles as a directory authority.
12138 - Add longclaw as a new (v3) directory authority. This implements
12139 ticket 13296. This keeps the directory authority count at 9.
12140 - The directory authority Faravahar has a new IP address. This
12141 closes ticket 14487.
12143 o Major bugfixes (crash, OSX, security):
12144 - Fix a remote denial-of-service opportunity caused by a bug in
12145 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
12148 o Major bugfixes (relay, stability, possible security):
12149 - Fix a bug that could lead to a relay crashing with an assertion
12150 failure if a buffer of exactly the wrong layout was passed to
12151 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
12152 0.2.0.10-alpha. Patch from 'cypherpunks'.
12153 - Do not assert if the 'data' pointer on a buffer is advanced to the
12154 very end of the buffer; log a BUG message instead. Only assert if
12155 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
12157 o Major bugfixes (exit node stability):
12158 - Fix an assertion failure that could occur under high DNS load.
12159 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
12160 diagnosed and fixed by "cypherpunks".
12162 o Major bugfixes (Linux seccomp2 sandbox):
12163 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
12164 crash during attempts to call wait4. Fixes bug 15088; bugfix on
12165 0.2.5.1-alpha. Patch from "sanic".
12167 o Minor features (controller):
12168 - New "GETINFO bw-event-cache" to get information about recent
12169 bandwidth events. Closes ticket 14128. Useful for controllers to
12170 get recent bandwidth history after the fix for ticket 13988.
12172 o Minor features (geoip):
12173 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
12174 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
12177 o Minor bugfixes (client, automapping):
12178 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
12179 no value follows the option. Fixes bug 14142; bugfix on
12180 0.2.4.7-alpha. Patch by "teor".
12181 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
12182 14195; bugfix on 0.1.0.1-rc.
12184 o Minor bugfixes (compilation):
12185 - Build without warnings with the stock OpenSSL srtp.h header, which
12186 has a duplicate declaration of SSL_get_selected_srtp_profile().
12187 Fixes bug 14220; this is OpenSSL's bug, not ours.
12189 o Minor bugfixes (directory authority):
12190 - Allow directory authorities to fetch more data from one another if
12191 they find themselves missing lots of votes. Previously, they had
12192 been bumping against the 10 MB queued data limit. Fixes bug 14261;
12193 bugfix on 0.1.2.5-alpha.
12194 - Enlarge the buffer to read bwauth generated files to avoid an
12195 issue when parsing the file in dirserv_read_measured_bandwidths().
12196 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
12198 o Minor bugfixes (statistics):
12199 - Increase period over which bandwidth observations are aggregated
12200 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
12202 o Minor bugfixes (preventative security, C safety):
12203 - When reading a hexadecimal, base-32, or base-64 encoded value from
12204 a string, always overwrite the whole output buffer. This prevents
12205 some bugs where we would look at (but fortunately, not reveal)
12206 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
12210 Changes in version 0.2.4.26 - 2015-03-17
12211 Tor 0.2.4.26 includes an updated list of directory authorities. It
12212 also backports a couple of stability and security bugfixes from 0.2.5
12215 o Directory authority changes:
12216 - Remove turtles as a directory authority.
12217 - Add longclaw as a new (v3) directory authority. This implements
12218 ticket 13296. This keeps the directory authority count at 9.
12219 - The directory authority Faravahar has a new IP address. This
12220 closes ticket 14487.
12222 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
12223 - Fix an assertion failure that could occur under high DNS load.
12224 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
12225 diagnosed and fixed by "cypherpunks".
12227 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
12228 - Fix a bug that could lead to a relay crashing with an assertion
12229 failure if a buffer of exactly the wrong layout was passed to
12230 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
12231 0.2.0.10-alpha. Patch from 'cypherpunks'.
12232 - Do not assert if the 'data' pointer on a buffer is advanced to the
12233 very end of the buffer; log a BUG message instead. Only assert if
12234 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
12236 o Minor features (geoip):
12237 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
12238 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
12241 Changes in version 0.2.6.4-rc - 2015-03-09
12242 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
12243 attacker might be able to use in order to crash certain Tor
12244 directories. It also resolves some minor issues left over from, or
12245 introduced in, Tor 0.2.6.3-alpha or earlier.
12247 o Major bugfixes (crash, OSX, security):
12248 - Fix a remote denial-of-service opportunity caused by a bug in
12249 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
12252 o Major bugfixes (relay, stability, possible security):
12253 - Fix a bug that could lead to a relay crashing with an assertion
12254 failure if a buffer of exactly the wrong layout is passed to
12255 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
12256 0.2.0.10-alpha. Patch from "cypherpunks".
12257 - Do not assert if the 'data' pointer on a buffer is advanced to the
12258 very end of the buffer; log a BUG message instead. Only assert if
12259 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
12261 o Major bugfixes (FreeBSD IPFW transparent proxy):
12262 - Fix address detection with FreeBSD transparent proxies, when
12263 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
12266 o Major bugfixes (Linux seccomp2 sandbox):
12267 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
12268 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
12270 - Allow AF_UNIX hidden services to be used with the seccomp2
12271 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
12272 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
12273 crash during attempts to call wait4. Fixes bug 15088; bugfix on
12274 0.2.5.1-alpha. Patch from "sanic".
12276 o Minor features (controller):
12277 - Messages about problems in the bootstrap process now include
12278 information about the server we were trying to connect to when we
12279 noticed the problem. Closes ticket 15006.
12281 o Minor features (geoip):
12282 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
12283 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
12286 o Minor features (logs):
12287 - Quiet some log messages in the heartbeat and at startup. Closes
12290 o Minor bugfixes (certificate handling):
12291 - If an authority operator accidentally makes a signing certificate
12292 with a future publication time, do not discard its real signing
12293 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
12294 - Remove any old authority certificates that have been superseded
12295 for at least two days. Previously, we would keep superseded
12296 certificates until they expired, if they were published close in
12297 time to the certificate that superseded them. Fixes bug 11454;
12298 bugfix on 0.2.1.8-alpha.
12300 o Minor bugfixes (compilation):
12301 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
12303 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
12306 o Minor bugfixes (testing):
12307 - Fix endianness issues in unit test for resolve_my_address() to
12308 have it pass on big endian systems. Fixes bug 14980; bugfix on
12310 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
12311 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
12312 - When running the new 'make test-stem' target, use the configured
12313 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
12314 from "cypherpunks".
12315 - When running the zero-length-keys tests, do not use the default
12316 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
12319 o Directory authority IP change:
12320 - The directory authority Faravahar has a new IP address. This
12321 closes ticket 14487.
12324 - Remove some lingering dead code that once supported mempools.
12325 Mempools were disabled by default in 0.2.5, and removed entirely
12326 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
12330 Changes in version 0.2.6.3-alpha - 2015-02-19
12331 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
12332 the 0.2.6.x series. It introduces support for more kinds of sockets,
12333 makes it harder to accidentally run an exit, improves our
12334 multithreading backend, incorporates several fixes for the
12335 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
12337 If no major regressions or security holes are found in this version,
12338 the next version will be a release candidate.
12340 o Deprecated versions:
12341 - Tor relays older than 0.2.4.18-rc are no longer allowed to
12342 advertise themselves on the network. Closes ticket 13555.
12344 o Major features (security, unix domain sockets):
12345 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
12346 applications can reach Tor without having to create AF_INET or
12347 AF_INET6 sockets, meaning they can completely disable their
12348 ability to make non-Tor network connections. To create a socket of
12349 this type, use "SocksPort unix:/path/to/socket". Implements
12351 - Support mapping hidden service virtual ports to AF_UNIX sockets.
12352 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
12353 Implements ticket 11485.
12355 o Major features (changed defaults):
12356 - Prevent relay operators from unintentionally running exits: When a
12357 relay is configured as an exit node, we now warn the user unless
12358 the "ExitRelay" option is set to 1. We warn even more loudly if
12359 the relay is configured with the default exit policy, since this
12360 can indicate accidental misconfiguration. Setting "ExitRelay 0"
12361 stops Tor from running as an exit relay. Closes ticket 10067.
12363 o Major features (directory system):
12364 - When downloading server- or microdescriptors from a directory
12365 server, we no longer launch multiple simultaneous requests to the
12366 same server. This reduces load on the directory servers,
12367 especially when directory guards are in use. Closes ticket 9969.
12368 - When downloading server- or microdescriptors over a tunneled
12369 connection, do not limit the length of our requests to what the
12370 Squid proxy is willing to handle. Part of ticket 9969.
12371 - Authorities can now vote on the correct digests and latest
12372 versions for different software packages. This allows packages
12373 that include Tor to use the Tor authority system as a way to get
12374 notified of updates and their correct digests. Implements proposal
12375 227. Closes ticket 10395.
12377 o Major features (guards):
12378 - Introduce the Guardfraction feature to improves load balancing on
12379 guard nodes. Specifically, it aims to reduce the traffic gap that
12380 guard nodes experience when they first get the Guard flag. This is
12381 a required step if we want to increase the guard lifetime to 9
12382 months or greater. Closes ticket 9321.
12384 o Major features (performance):
12385 - Make the CPU worker implementation more efficient by avoiding the
12386 kernel and lengthening pipelines. The original implementation used
12387 sockets to transfer data from the main thread to the workers, and
12388 didn't allow any thread to be assigned more than a single piece of
12389 work at once. The new implementation avoids communications
12390 overhead by making requests in shared memory, avoiding kernel IO
12391 where possible, and keeping more requests in flight at once.
12392 Implements ticket 9682.
12394 o Major features (relay):
12395 - Raise the minimum acceptable configured bandwidth rate for bridges
12396 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
12397 20 KiB/sec.) Closes ticket 13822.
12399 o Major bugfixes (exit node stability):
12400 - Fix an assertion failure that could occur under high DNS load.
12401 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
12402 diagnosed and fixed by "cypherpunks".
12404 o Major bugfixes (mixed relay-client operation):
12405 - When running as a relay and client at the same time (not
12406 recommended), if we decide not to use a new guard because we want
12407 to retry older guards, only close the locally-originating circuits
12408 passing through that guard. Previously we would close all the
12409 circuits through that guard. Fixes bug 9819; bugfix on
12410 0.2.1.1-alpha. Reported by "skruffy".
12412 o Minor features (build):
12413 - New --disable-system-torrc compile-time option to prevent Tor from
12414 looking for the system-wide torrc or torrc-defaults files.
12415 Resolves ticket 13037.
12417 o Minor features (controller):
12418 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
12419 events so controllers can observe circuit isolation inputs. Closes
12421 - ControlPort now supports the unix:/path/to/socket syntax as an
12422 alternative to the ControlSocket option, for consistency with
12423 SocksPort and HiddenServicePort. Closes ticket 14451.
12424 - New "GETINFO bw-event-cache" to get information about recent
12425 bandwidth events. Closes ticket 14128. Useful for controllers to
12426 get recent bandwidth history after the fix for ticket 13988.
12428 o Minor features (Denial of service resistance):
12429 - Count the total number of bytes used storing hidden service
12430 descriptors against the value of MaxMemInQueues. If we're low on
12431 memory, and more than 20% of our memory is used holding hidden
12432 service descriptors, free them until no more than 10% of our
12433 memory holds hidden service descriptors. Free the least recently
12434 fetched descriptors first. Resolves ticket 13806.
12435 - When we have recently been under memory pressure (over 3/4 of
12436 MaxMemInQueues is allocated), then allocate smaller zlib objects
12437 for small requests. Closes ticket 11791.
12439 o Minor features (geoip):
12440 - Update geoip and geoip6 files to the January 7 2015 Maxmind
12441 GeoLite2 Country database.
12443 o Minor features (guard nodes):
12444 - Reduce the time delay before saving guard status to disk from 10
12445 minutes to 30 seconds (or from one hour to 10 minutes if
12446 AvoidDiskWrites is set). Closes ticket 12485.
12448 o Minor features (hidden service):
12449 - Make Sybil attacks against hidden services harder by changing the
12450 minimum time required to get the HSDir flag from 25 hours up to 96
12451 hours. Addresses ticket 14149.
12452 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
12453 services to disable the anti-scanning feature introduced in
12454 0.2.6.2-alpha. With this option not set, a connection to an
12455 unlisted port closes the circuit. With this option set, only a
12456 RELAY_DONE cell is sent. Closes ticket 14084.
12458 o Minor features (interface):
12459 - Implement "-f -" command-line option to read torrc configuration
12460 from standard input, if you don't want to store the torrc file in
12461 the file system. Implements feature 13865.
12463 o Minor features (logging):
12464 - Add a count of unique clients to the bridge heartbeat message.
12465 Resolves ticket 6852.
12466 - Suppress "router info incompatible with extra info" message when
12467 reading extrainfo documents from cache. (This message got loud
12468 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
12470 - Elevate hidden service authorized-client message from DEBUG to
12471 INFO. Closes ticket 14015.
12473 o Minor features (stability):
12474 - Add assertions in our hash-table iteration code to check for
12475 corrupted values that could cause infinite loops. Closes
12478 o Minor features (systemd):
12479 - Various improvements and modernizations in systemd hardening
12480 support. Closes ticket 13805. Patch from Craig Andrews.
12482 o Minor features (testing networks):
12483 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
12484 and the default on a testing network to 2 minutes. Drop the
12485 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
12486 keep the default on a testing network at 30 seconds. This reduces
12487 HS bootstrap time to around 25 seconds. Also, change the default
12488 time in test-network.sh to match. Closes ticket 13401. Patch
12490 - Create TestingDirAuthVoteHSDir to correspond to
12491 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
12492 HSDir flag for the listed relays regardless of uptime or ORPort
12493 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
12494 Partial implementation for ticket 14067. Patch by "teor".
12496 o Minor features (tor2web mode):
12497 - Introduce the config option Tor2webRendezvousPoints, which allows
12498 clients in Tor2webMode to select a specific Rendezvous Point to be
12499 used in HS circuits. This might allow better performance for
12500 Tor2Web nodes. Implements ticket 12844.
12502 o Minor bugfixes (client DNS):
12503 - Report the correct cached DNS expiration times on SOCKS port or in
12504 DNS replies. Previously, we would report everything as "never
12505 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
12506 - Avoid a small memory leak when we find a cached answer for a
12507 reverse DNS lookup in a client-side DNS cache. (Remember, client-
12508 side DNS caching is off by default, and is not recommended.) Fixes
12509 bug 14259; bugfix on 0.2.0.1-alpha.
12511 o Minor bugfixes (client, automapping):
12512 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
12513 no value follows the option. Fixes bug 14142; bugfix on
12514 0.2.4.7-alpha. Patch by "teor".
12515 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
12516 14195; bugfix on 0.1.0.1-rc.
12517 - Prevent changes to other options from removing the wildcard value
12518 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
12520 - Allow MapAddress and AutomapHostsOnResolve to work together when
12521 an address is mapped into another address type (like .onion) that
12522 must be automapped at resolve time. Fixes bug 7555; bugfix
12525 o Minor bugfixes (client, bridges):
12526 - When we are using bridges and we had a network connectivity
12527 problem, only retry connecting to our currently configured
12528 bridges, not all bridges we know about and remember using. Fixes
12529 bug 14216; bugfix on 0.2.2.17-alpha.
12531 o Minor bugfixes (client, IPv6):
12532 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
12533 flag is not set; and not because the NoIPv4Traffic flag was set.
12534 Previously we'd looked at the NoIPv4Traffic flag for both types of
12535 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
12537 o Minor bugfixes (compilation):
12538 - The address of an array in the middle of a structure will always
12539 be non-NULL. clang recognises this and complains. Disable the
12540 tautologous and redundant check to silence this warning. Fixes bug
12541 14001; bugfix on 0.2.1.2-alpha.
12542 - Avoid warnings when building with systemd 209 or later. Fixes bug
12543 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
12544 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
12545 Addresses ticket 14188.
12546 - Build without warnings with the stock OpenSSL srtp.h header, which
12547 has a duplicate declaration of SSL_get_selected_srtp_profile().
12548 Fixes bug 14220; this is OpenSSL's bug, not ours.
12549 - Do not compile any code related to Tor2Web mode when Tor2Web mode
12550 is not enabled at compile time. Previously, this code was included
12551 in a disabled state. See discussion on ticket 12844.
12552 - Remove the --disable-threads configure option again. It was
12553 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
12554 14819; bugfix on 0.2.6.2-alpha.
12556 o Minor bugfixes (controller):
12557 - Report "down" in response to the "GETINFO entry-guards" command
12558 when relays are down with an unreachable_since value. Previously,
12559 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
12560 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
12561 14116; bugfix on 0.2.2.9-alpha.
12562 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
12563 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
12565 o Minor bugfixes (directory authority):
12566 - Allow directory authorities to fetch more data from one another if
12567 they find themselves missing lots of votes. Previously, they had
12568 been bumping against the 10 MB queued data limit. Fixes bug 14261;
12569 bugfix on 0.1.2.5-alpha.
12570 - Do not attempt to download extrainfo documents which we will be
12571 unable to validate with a matching server descriptor. Fixes bug
12572 13762; bugfix on 0.2.0.1-alpha.
12573 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
12574 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
12575 - Enlarge the buffer to read bwauth generated files to avoid an
12576 issue when parsing the file in dirserv_read_measured_bandwidths().
12577 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
12579 o Minor bugfixes (file handling):
12580 - Stop failing when key files are zero-length. Instead, generate new
12581 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
12582 on all versions of Tor. Patch by "teor".
12583 - Stop generating a fresh .old RSA onion key file when the .old file
12584 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
12585 - Avoid overwriting .old key files with empty key files.
12586 - Skip loading zero-length extrainfo store, router store, stats,
12587 state, and key files.
12588 - Avoid crashing when trying to reload a torrc specified as a
12589 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
12592 o Minor bugfixes (hidden services):
12593 - Close the introduction circuit when we have no more usable intro
12594 points, instead of waiting for it to time out. This also ensures
12595 that no follow-up HS descriptor fetch is triggered when the
12596 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
12597 - When fetching a hidden service descriptor for a down service that
12598 was recently up, do not keep refetching until we try the same
12599 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
12600 - Successfully launch Tor with a nonexistent hidden service
12601 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
12602 14106; bugfix on 0.2.6.2-alpha.
12604 o Minor bugfixes (logging):
12605 - Avoid crashing when there are more log domains than entries in
12606 domain_list. Bugfix on 0.2.3.1-alpha.
12607 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
12609 - Don't log messages to stdout twice when starting up. Fixes bug
12610 13993; bugfix on 0.2.6.1-alpha.
12612 o Minor bugfixes (parsing):
12613 - Stop accepting milliseconds (or other junk) at the end of
12614 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
12615 - Support two-number and three-number version numbers correctly, in
12616 case we change the Tor versioning system in the future. Fixes bug
12617 13661; bugfix on 0.0.8pre1.
12619 o Minor bugfixes (path counting):
12620 - When deciding whether the consensus lists any exit nodes, count
12621 the number listed in the consensus, not the number we have
12622 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
12623 - When deciding whether we have any exit nodes, only examine
12624 ExitNodes when the ExitNodes option is actually set. Fixes part of
12625 bug 14918; bugfix on 0.2.6.2-alpha.
12626 - Get rid of redundant and possibly scary warnings that we are
12627 missing directory information while we bootstrap. Fixes part of
12628 bug 14918; bugfix on 0.2.6.2-alpha.
12630 o Minor bugfixes (portability):
12631 - Fix the ioctl()-based network interface lookup code so that it
12632 will work on systems that have variable-length struct ifreq, for
12634 - Fix scheduler compilation on targets where char is unsigned. Fixes
12635 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
12637 o Minor bugfixes (sandbox):
12638 - Allow glibc fatal errors to be sent to stderr before Tor exits.
12639 Previously, glibc would try to write them to /dev/tty, and the
12640 sandbox would trap the call and make Tor exit prematurely. Fixes
12641 bug 14759; bugfix on 0.2.5.1-alpha.
12643 o Minor bugfixes (shutdown):
12644 - When shutting down, always call event_del() on lingering read or
12645 write events before freeing them. Otherwise, we risk double-frees
12646 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
12649 o Minor bugfixes (small memory leaks):
12650 - Avoid leaking memory when using IPv6 virtual address mappings.
12651 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
12654 o Minor bugfixes (statistics):
12655 - Increase period over which bandwidth observations are aggregated
12656 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
12658 o Minor bugfixes (systemd support):
12659 - Fix detection and operation of systemd watchdog. Fixes part of bug
12660 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
12661 - Run correctly under systemd with the RunAsDaemon option set. Fixes
12662 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
12663 - Inform the systemd supervisor about more changes in the Tor
12664 process status. Implements part of ticket 14141. Patch from
12666 - Cause the "--disable-systemd" option to actually disable systemd
12667 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
12670 o Minor bugfixes (TLS):
12671 - Check more thoroughly throughout the TLS code for possible
12672 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
12674 o Minor bugfixes (transparent proxy):
12675 - Use getsockname, not getsockopt, to retrieve the address for a
12676 TPROXY-redirected connection. Fixes bug 13796; bugfix
12679 o Code simplification and refactoring:
12680 - Move fields related to isolating and configuring client ports into
12681 a shared structure. Previously, they were duplicated across
12682 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
12683 to copy them correctly had been the cause of at least one bug in
12684 the past. Closes ticket 8546.
12685 - Refactor the get_interface_addresses_raw() doom-function into
12686 multiple smaller and simpler subfunctions. Cover the resulting
12687 subfunctions with unit-tests. Fixes a significant portion of
12689 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
12690 only for version <= 0.2.2.24 which is now deprecated. Closes
12692 - Remove a test for a long-defunct broken version-one
12696 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
12697 for writing the OpenBSD-specific tips. Resolves ticket 13702.
12698 - Make the tor-resolve documentation match its help string and its
12699 options. Resolves part of ticket 14325.
12700 - Log a more useful error message from tor-resolve when failing to
12701 look up a hidden service address. Resolves part of ticket 14325.
12703 o Downgraded warnings:
12704 - Don't warn when we've attempted to contact a relay using the wrong
12705 ntor onion key. Closes ticket 9635.
12707 o Removed features:
12708 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
12709 longer silently accepted as an alias for "ExitNodes".
12710 - The --enable-mempool and --enable-buf-freelists options, which
12711 were originally created to work around bad malloc implementations,
12712 no longer exist. They were off-by-default in 0.2.5. Closes
12716 - Make the checkdir/perms test complete successfully even if the
12717 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
12718 - Test that tor does not fail when key files are zero-length. Check
12719 that tor generates new keys, and overwrites the empty key files.
12720 - Test that tor generates new keys when keys are missing
12721 (existing behavior).
12722 - Test that tor does not overwrite key files that already contain
12723 data (existing behavior). Tests bug 13111. Patch by "teor".
12724 - New "make test-stem" target to run stem integration tests.
12725 Requires that the "STEM_SOURCE_DIR" environment variable be set.
12726 Closes ticket 14107.
12727 - Make the test_cmdline_args.py script work correctly on Windows.
12728 Patch from Gisle Vanem.
12729 - Move the slower unit tests into a new "./src/test/test-slow"
12730 binary that can be run independently of the other tests. Closes
12732 - Avoid undefined behavior when sampling huge values from the
12733 Laplace distribution. This made unittests fail on Raspberry Pi.
12734 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
12737 Changes in version 0.2.6.2-alpha - 2014-12-31
12738 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
12739 It introduces a major new backend for deciding when to send cells on
12740 channels, which should lead down the road to big performance
12741 increases. It contains security and statistics features for better
12742 work on hidden services, and numerous bugfixes.
12744 This release contains many new unit tests, along with major
12745 performance improvements for running testing networks using Chutney.
12746 Thanks to a series of patches contributed by "teor", testing networks
12747 should now bootstrap in seconds, rather than minutes.
12749 o Major features (relay, infrastructure):
12750 - Complete revision of the code that relays use to decide which cell
12751 to send next. Formerly, we selected the best circuit to write on
12752 each channel, but we didn't select among channels in any
12753 sophisticated way. Now, we choose the best circuits globally from
12754 among those whose channels are ready to deliver traffic.
12756 This patch implements a new inter-cmux comparison API, a global
12757 high/low watermark mechanism and a global scheduler loop for
12758 transmission prioritization across all channels as well as among
12759 circuits on one channel. This schedule is currently tuned to
12760 (tolerantly) avoid making changes in network performance, but it
12761 should form the basis for major circuit performance increases in
12762 the future. Code by Andrea; tuning by Rob Jansen; implements
12765 o Major features (hidden services):
12766 - Make HS port scanning more difficult by immediately closing the
12767 circuit when a user attempts to connect to a nonexistent port.
12768 Closes ticket 13667.
12769 - Add a HiddenServiceStatistics option that allows Tor relays to
12770 gather and publish statistics about the overall size and volume of
12771 hidden service usage. Specifically, when this option is turned on,
12772 an HSDir will publish an approximate number of hidden services
12773 that have published descriptors to it the past 24 hours. Also, if
12774 a relay has acted as a hidden service rendezvous point, it will
12775 publish the approximate amount of rendezvous cells it has relayed
12776 the past 24 hours. The statistics themselves are obfuscated so
12777 that the exact values cannot be derived. For more details see
12778 proposal 238, "Better hidden service stats from Tor relays". This
12779 feature is currently disabled by default. Implements feature 13192.
12781 o Major bugfixes (client, automap):
12782 - Repair automapping with IPv6 addresses. This automapping should
12783 have worked previously, but one piece of debugging code that we
12784 inserted to detect a regression actually caused the regression to
12785 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
12786 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
12789 o Major bugfixes (hidden services):
12790 - When closing an introduction circuit that was opened in parallel
12791 with others, don't mark the introduction point as unreachable.
12792 Previously, the first successful connection to an introduction
12793 point would make the other introduction points get marked as
12794 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
12796 o Directory authority changes:
12797 - Remove turtles as a directory authority.
12798 - Add longclaw as a new (v3) directory authority. This implements
12799 ticket 13296. This keeps the directory authority count at 9.
12801 o Major removed features:
12802 - Tor clients no longer support connecting to hidden services
12803 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
12804 option has been removed. (There shouldn't be any hidden services
12805 running these versions on the network.) Closes ticket 7803.
12807 o Minor features (client):
12808 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
12809 is enabled, reject requests with IP addresses as hostnames.
12810 Resolves ticket 13315.
12812 o Minor features (controller):
12813 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
12814 write an unscheduled heartbeat message to the log. Implements
12817 o Minor features (geoip):
12818 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
12821 o Minor features (hidden services):
12822 - When re-enabling the network, don't try to build introduction
12823 circuits until we have successfully built a circuit. This makes
12824 hidden services come up faster when the network is re-enabled.
12825 Patch from "akwizgran". Closes ticket 13447.
12826 - When we fail to retrieve a hidden service descriptor, send the
12827 controller an "HS_DESC FAILED" controller event. Implements
12829 - New HiddenServiceDirGroupReadable option to cause hidden service
12830 directories and hostname files to be created group-readable. Patch
12831 from "anon", David Stainton, and "meejah". Closes ticket 11291.
12833 o Minor features (systemd):
12834 - Where supported, when running with systemd, report successful
12835 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
12836 - When running with systemd, support systemd watchdog messages. Part
12837 of ticket 11016. Patch by Michael Scherer.
12839 o Minor features (transparent proxy):
12840 - Update the transparent proxy option checks to allow for both ipfw
12841 and pf on OS X. Closes ticket 14002.
12842 - Use the correct option when using IPv6 with transparent proxy
12843 support on Linux. Resolves 13808. Patch by Francisco Blas
12846 o Minor bugfixes (preventative security, C safety):
12847 - When reading a hexadecimal, base-32, or base-64 encoded value from
12848 a string, always overwrite the whole output buffer. This prevents
12849 some bugs where we would look at (but fortunately, not reveal)
12850 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
12852 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
12853 just the part that's used. This makes it harder for data leak bugs
12854 to occur in the event of other programming failures. Resolves
12857 o Minor bugfixes (client, microdescriptors):
12858 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
12859 computing which microdescriptors to download. This keeps us from
12860 erroneous download behavior if two microdescriptor digests ever
12861 have the same first 160 bits. Fixes part of bug 13399; bugfix
12863 - Reset a router's status if its microdescriptor digest changes,
12864 even if the first 160 bits remain the same. Fixes part of bug
12865 13399; bugfix on 0.2.3.1-alpha.
12867 o Minor bugfixes (compilation):
12868 - Silence clang warnings under --enable-expensive-hardening,
12869 including implicit truncation of 64 bit values to 32 bit, const
12870 char assignment to self, tautological compare, and additional
12871 parentheses around equality tests. Fixes bug 13577; bugfix
12873 - Fix a clang warning about checking whether an address in the
12874 middle of a structure is NULL. Fixes bug 14001; bugfix
12877 o Minor bugfixes (hidden services):
12878 - Correctly send a controller event when we find that a rendezvous
12879 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
12880 - Pre-check directory permissions for new hidden-services to avoid
12881 at least one case of "Bug: Acting on config options left us in a
12882 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
12883 - When adding a new hidden service (for example, via SETCONF), Tor
12884 no longer congratulates the user for running a relay. Fixes bug
12885 13941; bugfix on 0.2.6.1-alpha.
12886 - When fetching hidden service descriptors, we now check not only
12887 for whether we got the hidden service we had in mind, but also
12888 whether we got the particular descriptors we wanted. This prevents
12889 a class of inefficient but annoying DoS attacks by hidden service
12890 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
12893 o Minor bugfixes (Linux seccomp2 sandbox):
12894 - Make transparent proxy support work along with the seccomp2
12895 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
12896 by Francisco Blas Izquierdo Riera.
12897 - Fix a memory leak in tor-resolve when running with the sandbox
12898 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
12900 o Minor bugfixes (logging):
12901 - Downgrade warnings about RSA signature failures to info log level.
12902 Emit a warning when an extra info document is found incompatible
12903 with a corresponding router descriptor. Fixes bug 9812; bugfix
12905 - Make connection_ap_handshake_attach_circuit() log the circuit ID
12906 correctly. Fixes bug 13701; bugfix on 0.0.6.
12908 o Minor bugfixes (misc):
12909 - Stop allowing invalid address patterns like "*/24" that contain
12910 both a wildcard address and a bit prefix length. This affects all
12911 our address-range parsing code. Fixes bug 7484; bugfix
12914 o Minor bugfixes (testing networks, fast startup):
12915 - Allow Tor to build circuits using a consensus with no exits. If
12916 the consensus has no exits (typical of a bootstrapping test
12917 network), allow Tor to build circuits once enough descriptors have
12918 been downloaded. This assists in bootstrapping a testing Tor
12919 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
12921 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
12922 header to directory servers. This allows us to obtain consensuses
12923 promptly when the consensus interval is very short. This assists
12924 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
12925 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
12926 - Stop assuming that private addresses are local when checking
12927 reachability in a TestingTorNetwork. Instead, when testing, assume
12928 all OR connections are remote. (This is necessary due to many test
12929 scenarios running all relays on localhost.) This assists in
12930 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
12931 0.1.0.1-rc. Patch by "teor".
12932 - Avoid building exit circuits from a consensus with no exits. Now
12933 thanks to our fix for 13718, we accept a no-exit network as not
12934 wholly lost, but we need to remember not to try to build exit
12935 circuits on it. Closes ticket 13814; patch by "teor".
12936 - Stop requiring exits to have non-zero bandwithcapacity in a
12937 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
12938 ignore exit bandwidthcapacity. This assists in bootstrapping a
12939 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
12940 on 0.2.0.3-alpha. Patch by "teor".
12941 - Add "internal" to some bootstrap statuses when no exits are
12942 available. If the consensus does not contain Exits, Tor will only
12943 build internal circuits. In this case, relevant statuses will
12944 contain the word "internal" as indicated in the Tor control-
12945 spec.txt. When bootstrap completes, Tor will be ready to build
12946 internal circuits. If a future consensus contains Exits, exit
12947 circuits may become available. Fixes part of bug 13718; bugfix on
12948 0.2.4.10-alpha. Patch by "teor".
12949 - Decrease minimum consensus interval to 10 seconds when
12950 TestingTorNetwork is set, or 5 seconds for the first consensus.
12951 Fix assumptions throughout the code that assume larger intervals.
12952 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
12954 - Avoid excluding guards from path building in minimal test
12955 networks, when we're in a test network and excluding guards would
12956 exclude all relays. This typically occurs in incredibly small tor
12957 networks, and those using "TestingAuthVoteGuard *". Fixes part of
12958 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
12960 o Code simplification and refactoring:
12961 - Stop using can_complete_circuits as a global variable; access it
12962 with a function instead.
12963 - Avoid using operators directly as macro arguments: this lets us
12964 apply coccinelle transformations to our codebase more directly.
12965 Closes ticket 13172.
12966 - Combine the functions used to parse ClientTransportPlugin and
12967 ServerTransportPlugin into a single function. Closes ticket 6456.
12968 - Add inline functions and convenience macros for inspecting channel
12969 state. Refactor the code to use convenience macros instead of
12970 checking channel state directly. Fixes issue 7356.
12971 - Document all members of was_router_added_t and rename
12972 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
12973 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
12974 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
12975 constant instead of hardcoded value. Fixes issue 13840.
12976 - Refactor our generic strmap and digestmap types into a single
12977 implementation, so that we can add a new digest256map
12981 - Document the bridge-authority-only 'networkstatus-bridges' file.
12982 Closes ticket 13713; patch from "tom".
12983 - Fix typo in PredictedPortsRelevanceTime option description in
12984 manpage. Resolves issue 13707.
12985 - Stop suggesting that users specify relays by nickname: it isn't a
12986 good idea. Also, properly cross-reference how to specify relays in
12987 all parts of manual documenting options that take a list of
12988 relays. Closes ticket 13381.
12989 - Clarify the HiddenServiceDir option description in manpage to make
12990 it clear that relative paths are taken with respect to the current
12991 working directory. Also clarify that this behavior is not
12992 guaranteed to remain indefinitely. Fixes issue 13913.
12995 - New tests for many parts of channel, relay, and circuitmux
12996 functionality. Code by Andrea; part of 9262.
12997 - New tests for parse_transport_line(). Part of ticket 6456.
12998 - In the unit tests, use chgrp() to change the group of the unit
12999 test temporary directory to the current user, so that the sticky
13000 bit doesn't interfere with tests that check directory groups.
13002 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
13006 Changes in version 0.2.6.1-alpha - 2014-10-30
13007 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
13008 includes numerous code cleanups and new tests, and fixes a large
13009 number of annoying bugs. Out-of-memory conditions are handled better
13010 than in 0.2.5, pluggable transports have improved proxy support, and
13011 clients now use optimistic data for contacting hidden services. Also,
13012 we are now more robust to changes in what we consider a parseable
13013 directory object, so that tightening restrictions does not have a risk
13014 of introducing infinite download loops.
13016 This is the first alpha release in a new series, so expect there to be
13017 bugs. Users who would rather test out a more stable branch should stay
13018 with 0.2.5.x for now.
13020 o New compiler and system requirements:
13021 - Tor 0.2.6.x requires that your compiler support more of the C99
13022 language standard than before. The 'configure' script now detects
13023 whether your compiler supports C99 mid-block declarations and
13024 designated initializers. If it does not, Tor will not compile.
13026 We may revisit this requirement if it turns out that a significant
13027 number of people need to build Tor with compilers that don't
13028 bother implementing a 15-year-old standard. Closes ticket 13233.
13029 - Tor no longer supports systems without threading support. When we
13030 began working on Tor, there were several systems that didn't have
13031 threads, or where the thread support wasn't able to run the
13032 threads of a single process on multiple CPUs. That no longer
13033 holds: every system where Tor needs to run well now has threading
13034 support. Resolves ticket 12439.
13036 o Removed platform support:
13037 - We no longer include special code to build on Windows CE; as far
13038 as we know, nobody has used Tor on Windows CE in a very long time.
13039 Closes ticket 11446.
13041 o Major features (bridges):
13042 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
13043 transports if they are configured via the "TOR_PT_PROXY"
13044 environment variable. Implements proposal 232. Resolves
13047 o Major features (client performance, hidden services):
13048 - Allow clients to use optimistic data when connecting to a hidden
13049 service, which should remove a round-trip from hidden service
13050 initialization. See proposal 181 for details. Implements
13053 o Major features (directory system):
13054 - Upon receiving an unparseable directory object, if its digest
13055 matches what we expected, then don't try to download it again.
13056 Previously, when we got a descriptor we didn't like, we would keep
13057 trying to download it over and over. Closes ticket 11243.
13059 o Major features (sample torrc):
13060 - Add a new, infrequently-changed "torrc.minimal". This file is
13061 similar to torrc.sample, but it will change as infrequently as
13062 possible, for the benefit of users whose systems prompt them for
13063 intervention whenever a default configuration file is changed.
13064 Making this change allows us to update torrc.sample to be a more
13065 generally useful "sample torrc".
13067 o Major bugfixes (directory authorities):
13068 - Do not assign the HSDir flag to relays if they are not Valid, or
13069 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
13071 o Major bugfixes (directory bandwidth performance):
13072 - Don't flush the zlib buffer aggressively when compressing
13073 directory information for clients. This should save about 7% of
13074 the bandwidth currently used for compressed descriptors and
13075 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
13077 o Minor features (security, memory wiping):
13078 - Ensure we securely wipe keys from memory after
13079 crypto_digest_get_digest and init_curve25519_keypair_from_file
13080 have finished using them. Resolves ticket 13477.
13082 o Minor features (security, out-of-memory handling):
13083 - When handling an out-of-memory condition, allocate less memory for
13084 temporary data structures. Fixes issue 10115.
13085 - When handling an out-of-memory condition, consider more types of
13086 buffers, including those on directory connections, and zlib
13087 buffers. Resolves ticket 11792.
13090 - When identity keypair is generated for first time, log a
13091 congratulatory message that links to the new relay lifecycle
13092 document. Implements feature 10427.
13094 o Minor features (client):
13095 - Clients are now willing to send optimistic data (before they
13096 receive a 'connected' cell) to relays of any version. (Relays
13097 without support for optimistic data are no longer supported on the
13098 Tor network.) Resolves ticket 13153.
13100 o Minor features (directory authorities):
13101 - Don't list relays with a bandwidth estimate of 0 in the consensus.
13102 Implements a feature proposed during discussion of bug 13000.
13103 - In tor-gencert, report an error if the user provides the same
13104 argument more than once.
13105 - If a directory authority can't find a best consensus method in the
13106 votes that it holds, it now falls back to its favorite consensus
13107 method. Previously, it fell back to method 1. Neither of these is
13108 likely to get enough signatures, but "fall back to favorite"
13109 doesn't require us to maintain support an obsolete consensus
13110 method. Implements part of proposal 215.
13112 o Minor features (logging):
13113 - On Unix-like systems, you can now use named pipes as the target of
13114 the Log option, and other options that try to append to files.
13115 Closes ticket 12061. Patch from "carlo von lynX".
13116 - When opening a log file at startup, send it every log message that
13117 we generated between startup and opening it. Previously, log
13118 messages that were generated before opening the log file were only
13119 logged to stdout. Closes ticket 6938.
13120 - Add a TruncateLogFile option to overwrite logs instead of
13121 appending to them. Closes ticket 5583.
13123 o Minor features (portability, Solaris):
13124 - Threads are no longer disabled by default on Solaris; we believe
13125 that the versions of Solaris with broken threading support are all
13126 obsolete by now. Resolves ticket 9495.
13128 o Minor features (relay):
13129 - Re-check our address after we detect a changed IP address from
13130 getsockname(). This ensures that the controller command "GETINFO
13131 address" will report the correct value. Resolves ticket 11582.
13133 - A new AccountingRule option lets Relays set whether they'd like
13134 AccountingMax to be applied separately to inbound and outbound
13135 traffic, or applied to the sum of inbound and outbound traffic.
13136 Resolves ticket 961. Patch by "chobe".
13138 o Minor features (testing networks):
13139 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
13140 the "Exit" flag regardless of their uptime, bandwidth, or exit
13141 policy. TestingTorNetwork must be set for this option to have any
13142 effect. Previously, authorities would take up to 35 minutes to
13143 give nodes the Exit flag in a test network. Partially implements
13146 o Minor features (validation):
13147 - Check all date/time values passed to tor_timegm and
13148 parse_rfc1123_time for validity, taking leap years into account.
13149 Improves HTTP header validation. Implemented with bug 13476.
13150 - In correct_tm(), limit the range of values returned by system
13151 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
13152 This means we don't have to deal with negative or too large dates,
13153 even if a clock is wrong. Otherwise we might fail to read a file
13154 written by us which includes such a date. Fixes bug 13476.
13156 o Minor bugfixes (bridge clients):
13157 - When configured to use a bridge without an identity digest (not
13158 recommended), avoid launching an extra channel to it when
13159 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
13161 o Minor bugfixes (bridges):
13162 - When DisableNetwork is set, do not launch pluggable transport
13163 plugins, and if any are running, terminate them. Fixes bug 13213;
13164 bugfix on 0.2.3.6-alpha.
13166 o Minor bugfixes (C correctness):
13167 - Fix several instances of possible integer overflow/underflow/NaN.
13168 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
13170 - In circuit_build_times_calculate_timeout() in circuitstats.c,
13171 avoid dividing by zero in the pareto calculations. This traps
13172 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
13174 - Fix an integer overflow in format_time_interval(). Fixes bug
13175 13393; bugfix on 0.2.0.10-alpha.
13176 - Set the correct day of year value when the system's localtime(_r)
13177 or gmtime(_r) functions fail to set struct tm. Not externally
13178 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
13179 - Avoid unlikely signed integer overflow in tor_timegm on systems
13180 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
13182 o Minor bugfixes (client):
13183 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
13184 BadExit flag are not considered worthy candidates. Fixes bug
13185 13066; bugfix on 0.1.2.3-alpha.
13186 - Use the consensus schedule for downloading consensuses, and not
13187 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
13188 - Handle unsupported or malformed SOCKS5 requests properly by
13189 responding with the appropriate error message before closing the
13190 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
13192 o Minor bugfixes (client, torrc):
13193 - Stop modifying the value of our DirReqStatistics torrc option just
13194 because we're not a bridge or relay. This bug was causing Tor
13195 Browser users to write "DirReqStatistics 0" in their torrc files
13196 as if they had chosen to change the config. Fixes bug 4244; bugfix
13198 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
13199 that our options have changed every time we SIGHUP. Fixes bug
13200 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
13202 o Minor bugfixes (controller):
13203 - Return an error when the second or later arguments of the
13204 "setevents" controller command are invalid events. Previously we
13205 would return success while silently skipping invalid events. Fixes
13206 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
13208 o Minor bugfixes (directory system):
13209 - Always believe that v3 directory authorities serve extra-info
13210 documents, whether they advertise "caches-extra-info" or not.
13211 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
13212 - When running as a v3 directory authority, advertise that you serve
13213 extra-info documents so that clients who want them can find them
13214 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
13215 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
13216 Previously, directories offering BRIDGE_DIRINFO and some other
13217 flag (i.e. microdescriptors or extrainfo) would be ignored when
13218 looking for bridges. Partially fixes bug 13163; bugfix
13221 o Minor bugfixes (networking):
13222 - Check for orconns and use connection_or_close_for_error() rather
13223 than connection_mark_for_close() directly in the getsockopt()
13224 failure case of connection_handle_write_impl(). Fixes bug 11302;
13225 bugfix on 0.2.4.4-alpha.
13227 o Minor bugfixes (relay):
13228 - When generating our family list, remove spaces from around the
13229 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
13230 - If our previous bandwidth estimate was 0 bytes, allow publishing a
13231 new relay descriptor immediately. Fixes bug 13000; bugfix
13234 o Minor bugfixes (testing networks):
13235 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
13236 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
13237 - Stop using the default authorities in networks which provide both
13238 AlternateDirAuthority and AlternateBridgeAuthority. Partially
13239 fixes bug 13163; bugfix on 0.2.0.13-alpha.
13241 o Minor bugfixes (testing):
13242 - Stop spawn test failures due to a race condition between the
13243 SIGCHLD handler updating the process status, and the test reading
13244 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
13246 o Minor bugfixes (testing, Windows):
13247 - Avoid passing an extra backslash when creating a temporary
13248 directory for running the unit tests on Windows. Fixes bug 12392;
13249 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
13251 o Minor bugfixes (windows):
13252 - Remove code to special-case handling of NTE_BAD_KEYSET when
13253 acquiring windows CryptoAPI context. This error can't actually
13254 occur for the parameters we're providing. Fixes bug 10816; bugfix
13257 o Minor bugfixes (zlib):
13258 - Avoid truncating a zlib stream when trying to finalize it with an
13259 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
13262 - Allow our configure script to build correctly with autoconf 2.62
13263 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
13264 - Improve the error message from ./configure to make it clear that
13265 when asciidoc has not been found, the user will have to either add
13266 --disable-asciidoc argument or install asciidoc. Resolves
13269 o Code simplification and refactoring:
13270 - Change the entry_is_live() function to take named bitfield
13271 elements instead of an unnamed list of booleans. Closes
13273 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
13274 Resolves ticket 12205.
13275 - Use calloc and reallocarray functions instead of multiply-
13276 then-malloc. This makes it less likely for us to fall victim to an
13277 integer overflow attack when allocating. Resolves ticket 12855.
13278 - Use the standard macro name SIZE_MAX, instead of our
13280 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
13281 functions which take them as arguments. Replace 0 with NO_DIRINFO
13282 in a function call for clarity. Seeks to prevent future issues
13284 - Avoid 4 null pointer errors under clang static analysis by using
13285 tor_assert() to prove that the pointers aren't null. Fixes
13287 - Rework the API of policies_parse_exit_policy() to use a bitmask to
13288 represent parsing options, instead of a confusing mess of
13289 booleans. Resolves ticket 8197.
13290 - Introduce a helper function to parse ExitPolicy in
13291 or_options_t structure.
13294 - Add a doc/TUNING document with tips for handling large numbers of
13295 TCP connections when running busy Tor relay. Update the warning
13296 message to point to this file when running out of sockets
13297 operating system is allowing to use simultaneously. Resolves
13300 o Removed features:
13301 - We no longer remind the user about configuration options that have
13302 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
13303 - Remove our old, non-weighted bandwidth-based node selection code.
13304 Previously, we used it as a fallback when we couldn't perform
13305 weighted bandwidth-based node selection. But that would only
13306 happen in the cases where we had no consensus, or when we had a
13307 consensus generated by buggy or ancient directory authorities. In
13308 either case, it's better to use the more modern, better maintained
13309 algorithm, with reasonable defaults for the weights. Closes
13311 - Remove the --disable-curve25519 configure option. Relays and
13312 clients now are required to support curve25519 and the
13314 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
13315 used to be deprecated synonyms for "StrictNodes", are now marked
13316 obsolete. Resolves ticket 12226.
13317 - Clients don't understand the BadDirectory flag in the consensus
13318 anymore, and ignore it.
13321 - Refactor the function that chooses guard nodes so that it can more
13322 easily be tested; write some tests for it.
13323 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
13324 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
13325 - Create unit tests for format_time_interval(). With bug 13393.
13326 - Add unit tests for tor_timegm signed overflow, tor_timegm and
13327 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
13328 tests (visible) fixes in bug 13476.
13329 - Add a "coverage-html" make target to generate HTML-visualized
13330 coverage results when building with --enable-coverage. (Requires
13331 lcov.) Patch from Kevin Murray.
13332 - Enable the backtrace handler (where supported) when running the
13334 - Revise all unit tests that used the legacy test_* macros to
13335 instead use the recommended tt_* macros. This patch was generated
13336 with coccinelle, to avoid manual errors. Closes ticket 13119.
13338 o Distribution (systemd):
13339 - systemd unit file: only allow tor to write to /var/lib/tor and
13340 /var/log/tor. The rest of the filesystem is accessible for reading
13341 only. Patch by intrigeri; resolves ticket 12751.
13342 - systemd unit file: ensure that the process and all its children
13343 can never gain new privileges. Patch by intrigeri; resolves
13345 - systemd unit file: set up /var/run/tor as writable for the Tor
13346 service. Patch by intrigeri; resolves ticket 13196.
13348 o Removed features (directory authorities):
13349 - Remove code that prevented authorities from listing Tor relays
13350 affected by CVE-2011-2769 as guards. These relays are already
13351 rejected altogether due to the minimum version requirement of
13352 0.2.3.16-alpha. Closes ticket 13152.
13353 - The "AuthDirRejectUnlisted" option no longer has any effect, as
13354 the fingerprints file (approved-routers) has been deprecated.
13355 - Directory authorities do not support being Naming dirauths anymore.
13356 The "NamingAuthoritativeDir" config option is now obsolete.
13357 - Directory authorities do not support giving out the BadDirectory
13359 - Directory authorities no longer advertise or support consensus
13360 methods 1 through 12 inclusive. These consensus methods were
13361 obsolete and/or insecure: maintaining the ability to support them
13362 served no good purpose. Implements part of proposal 215; closes
13365 o Testing (test-network.sh):
13366 - Stop using "echo -n", as some shells' built-in echo doesn't
13367 support "-n". Instead, use "/bin/echo -n". Partially fixes
13369 - Stop an apparent test-network hang when used with make -j2. Fixes
13371 - Add a --delay option to test-network.sh, which configures the
13372 delay before the chutney network tests for data transmission.
13373 Partially implements ticket 13161.
13376 Changes in version 0.2.5.10 - 2014-10-24
13377 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
13379 It adds several new security features, including improved
13380 denial-of-service resistance for relays, new compiler hardening
13381 options, and a system-call sandbox for hardened installations on Linux
13382 (requires seccomp2). The controller protocol has several new features,
13383 resolving IPv6 addresses should work better than before, and relays
13384 should be a little more CPU-efficient. We've added support for more
13385 OpenBSD and FreeBSD transparent proxy types. We've improved the build
13386 system and testing infrastructure to allow unit testing of more parts
13387 of the Tor codebase. Finally, we've addressed several nagging pluggable
13388 transport usability issues, and included numerous other small bugfixes
13389 and features mentioned below.
13391 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
13392 have accumulated many known flaws; everyone should upgrade.
13394 o Deprecated versions:
13395 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
13396 attention for some while.
13399 Changes in version 0.2.5.9-rc - 2014-10-20
13400 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
13401 series. It disables SSL3 in response to the recent "POODLE" attack
13402 (even though POODLE does not affect Tor). It also works around a crash
13403 bug caused by some operating systems' response to the "POODLE" attack
13404 (which does affect Tor). It also contains a few miscellaneous fixes.
13406 o Major security fixes:
13407 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
13408 today support TLS 1.0 or later, so we can safely turn off support
13409 for this old (and insecure) protocol. Fixes bug 13426.
13411 o Major bugfixes (openssl bug workaround):
13412 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
13413 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
13414 13471. This is a workaround for an OpenSSL bug.
13417 - Disable the sandbox name resolver cache when running tor-resolve:
13418 tor-resolve doesn't use the sandbox code, and turning it on was
13419 breaking attempts to do tor-resolve on a non-default server on
13420 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
13422 o Compilation fixes:
13423 - Build and run correctly on systems like OpenBSD-current that have
13424 patched OpenSSL to remove get_cipher_by_char and/or its
13425 implementations. Fixes issue 13325.
13427 o Downgraded warnings:
13428 - Downgrade the severity of the 'unexpected sendme cell from client'
13429 from 'warn' to 'protocol warning'. Closes ticket 8093.
13432 Changes in version 0.2.4.25 - 2014-10-20
13433 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
13434 (even though POODLE does not affect Tor). It also works around a crash
13435 bug caused by some operating systems' response to the "POODLE" attack
13436 (which does affect Tor).
13438 o Major security fixes (also in 0.2.5.9-rc):
13439 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
13440 today support TLS 1.0 or later, so we can safely turn off support
13441 for this old (and insecure) protocol. Fixes bug 13426.
13443 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
13444 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
13445 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
13446 13471. This is a workaround for an OpenSSL bug.
13449 Changes in version 0.2.5.8-rc - 2014-09-22
13450 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
13451 series. It fixes a bug that affects consistency and speed when
13452 connecting to hidden services, and it updates the location of one of
13453 the directory authorities.
13456 - Clients now send the correct address for their chosen rendezvous
13457 point when trying to access a hidden service. They used to send
13458 the wrong address, which would still work some of the time because
13459 they also sent the identity digest of the rendezvous point, and if
13460 the hidden service happened to try connecting to the rendezvous
13461 point from a relay that already had a connection open to it,
13462 the relay would reuse that connection. Now connections to hidden
13463 services should be more robust and faster. Also, this bug meant
13464 that clients were leaking to the hidden service whether they were
13465 on a little-endian (common) or big-endian (rare) system, which for
13466 some users might have reduced their anonymity. Fixes bug 13151;
13467 bugfix on 0.2.1.5-alpha.
13469 o Directory authority changes:
13470 - Change IP address for gabelmoo (v3 directory authority).
13473 Changes in version 0.2.4.24 - 2014-09-22
13474 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
13475 connecting to hidden services, and it updates the location of one of
13476 the directory authorities.
13479 - Clients now send the correct address for their chosen rendezvous
13480 point when trying to access a hidden service. They used to send
13481 the wrong address, which would still work some of the time because
13482 they also sent the identity digest of the rendezvous point, and if
13483 the hidden service happened to try connecting to the rendezvous
13484 point from a relay that already had a connection open to it,
13485 the relay would reuse that connection. Now connections to hidden
13486 services should be more robust and faster. Also, this bug meant
13487 that clients were leaking to the hidden service whether they were
13488 on a little-endian (common) or big-endian (rare) system, which for
13489 some users might have reduced their anonymity. Fixes bug 13151;
13490 bugfix on 0.2.1.5-alpha.
13492 o Directory authority changes:
13493 - Change IP address for gabelmoo (v3 directory authority).
13495 o Minor features (geoip):
13496 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
13500 Changes in version 0.2.5.7-rc - 2014-09-11
13501 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
13502 release series, and some long-standing bugs related to ORPort reachability
13503 testing and failure to send CREATE cells. It is the first release
13504 candidate for the Tor 0.2.5.x series.
13506 o Major bugfixes (client, startup):
13507 - Start making circuits as soon as DisabledNetwork is turned off.
13508 When Tor started with DisabledNetwork set, it would correctly
13509 conclude that it shouldn't build circuits, but it would mistakenly
13510 cache this conclusion, and continue believing it even when
13511 DisableNetwork is set to 0. Fixes the bug introduced by the fix
13512 for bug 11200; bugfix on 0.2.5.4-alpha.
13513 - Resume expanding abbreviations for command-line options. The fix
13514 for bug 4647 accidentally removed our hack from bug 586 that
13515 rewrote HashedControlPassword to __HashedControlSessionPassword
13516 when it appears on the commandline (which allowed the user to set
13517 her own HashedControlPassword in the torrc file while the
13518 controller generates a fresh session password for each run). Fixes
13519 bug 12948; bugfix on 0.2.5.1-alpha.
13520 - Warn about attempts to run hidden services and relays in the same
13521 process: that's probably not a good idea. Closes ticket 12908.
13523 o Major bugfixes (relay):
13524 - Avoid queuing or sending destroy cells for circuit ID zero when we
13525 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
13526 Found and fixed by "cypherpunks".
13527 - Fix ORPort reachability detection on relays running behind a
13528 proxy, by correctly updating the "local" mark on the controlling
13529 channel when changing the address of an or_connection_t after the
13530 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
13532 o Minor features (bridge):
13533 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
13534 cookie file for the ExtORPort g+r by default.
13536 o Minor features (geoip):
13537 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
13540 o Minor bugfixes (logging):
13541 - Reduce the log severity of the "Pluggable transport proxy does not
13542 provide any needed transports and will not be launched." message,
13543 since Tor Browser includes several ClientTransportPlugin lines in
13544 its torrc-defaults file, leading every Tor Browser user who looks
13545 at her logs to see these notices and wonder if they're dangerous.
13546 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
13547 - Downgrade "Unexpected onionskin length after decryption" warning
13548 to a protocol-warn, since there's nothing relay operators can do
13549 about a client that sends them a malformed create cell. Resolves
13550 bug 12996; bugfix on 0.0.6rc1.
13551 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
13552 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
13553 - When logging information about an EXTEND2 or EXTENDED2 cell, log
13554 their names correctly. Fixes part of bug 12700; bugfix
13556 - When logging information about a relay cell whose command we don't
13557 recognize, log its command as an integer. Fixes part of bug 12700;
13558 bugfix on 0.2.1.10-alpha.
13559 - Escape all strings from the directory connection before logging
13560 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
13562 o Minor bugfixes (controller):
13563 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
13564 bug 12864; bugfix on 0.2.5.1-alpha.
13565 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
13566 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
13569 o Minor bugfixes (compilation):
13570 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
13571 bugfix on 0.2.5.5-alpha.
13572 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
13573 0.2.5.1-alpha. Patch from "NewEraCracker".
13574 - In routerlist_assert_ok(), don't take the address of a
13575 routerinfo's cache_info member unless that routerinfo is non-NULL.
13576 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
13577 - Fix a large number of false positive warnings from the clang
13578 analyzer static analysis tool. This should make real warnings
13579 easier for clang analyzer to find. Patch from "teor". Closes
13582 o Distribution (systemd):
13583 - Verify configuration file via ExecStartPre in the systemd unit
13584 file. Patch from intrigeri; resolves ticket 12730.
13585 - Explicitly disable RunAsDaemon in the systemd unit file. Our
13586 current systemd unit uses "Type = simple", so systemd does not
13587 expect tor to fork. If the user has "RunAsDaemon 1" in their
13588 torrc, then things won't work as expected. This is e.g. the case
13589 on Debian (and derivatives), since there we pass "--defaults-torrc
13590 /usr/share/tor/tor-service-defaults-torrc" (that contains
13591 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
13595 - Adjust the URLs in the README to refer to the new locations of
13596 several documents on the website. Fixes bug 12830. Patch from
13598 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
13602 Changes in version 0.2.5.6-alpha - 2014-07-28
13603 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
13604 risk from guard rotation, and fixes a variety of other issues to get
13605 us closer to a release candidate.
13607 o Major features (also in 0.2.4.23):
13608 - Make the number of entry guards configurable via a new
13609 NumEntryGuards consensus parameter, and the number of directory
13610 guards configurable via a new NumDirectoryGuards consensus
13611 parameter. Implements ticket 12688.
13613 o Major bugfixes (also in 0.2.4.23):
13614 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
13615 implementation that caused incorrect results on 32-bit
13616 implementations when certain malformed inputs were used along with
13617 a small class of private ntor keys. This bug does not currently
13618 appear to allow an attacker to learn private keys or impersonate a
13619 Tor server, but it could provide a means to distinguish 32-bit Tor
13620 implementations from 64-bit Tor implementations. Fixes bug 12694;
13621 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
13625 - Perform circuit cleanup operations even when circuit
13626 construction operations are disabled (because the network is
13627 disabled, or because there isn't enough directory information).
13628 Previously, when we were not building predictive circuits, we
13629 were not closing expired circuits either. Fixes bug 8387; bugfix on
13630 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
13631 became more strict about when we have "enough directory information
13632 to build circuits".
13635 - Authorities now assign the Guard flag to the fastest 25% of the
13636 network (it used to be the fastest 50%). Also raise the consensus
13637 weight that guarantees the Guard flag from 250 to 2000. For the
13638 current network, this results in about 1100 guards, down from 2500.
13639 This step paves the way for moving the number of entry guards
13640 down to 1 (proposal 236) while still providing reasonable expected
13641 performance for most users. Implements ticket 12690.
13642 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
13644 - Slightly enhance the diagnostic message for bug 12184.
13646 o Minor bugfixes (also in 0.2.4.23):
13647 - Warn and drop the circuit if we receive an inbound 'relay early'
13648 cell. Those used to be normal to receive on hidden service circuits
13649 due to bug 1038, but the buggy Tor versions are long gone from
13650 the network so we can afford to resume watching for them. Resolves
13651 the rest of bug 1038; bugfix on 0.2.1.19.
13652 - Correct a confusing error message when trying to extend a circuit
13653 via the control protocol but we don't know a descriptor or
13654 microdescriptor for one of the specified relays. Fixes bug 12718;
13655 bugfix on 0.2.3.1-alpha.
13658 - Fix compilation when building with bufferevents enabled. (This
13659 configuration is still not expected to work, however.)
13660 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
13661 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
13663 - Compile correctly with builds and forks of OpenSSL (such as
13664 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
13665 0.2.1.1-alpha. Patch from "dhill".
13668 Changes in version 0.2.4.23 - 2014-07-28
13669 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
13670 guard rotation, and also backports several important fixes from the
13671 Tor 0.2.5 alpha release series.
13674 - Clients now look at the "usecreatefast" consensus parameter to
13675 decide whether to use CREATE_FAST or CREATE cells for the first hop
13676 of their circuit. This approach can improve security on connections
13677 where Tor's circuit handshake is stronger than the available TLS
13678 connection security levels, but the tradeoff is more computational
13679 load on guard relays. Implements proposal 221. Resolves ticket 9386.
13680 - Make the number of entry guards configurable via a new
13681 NumEntryGuards consensus parameter, and the number of directory
13682 guards configurable via a new NumDirectoryGuards consensus
13683 parameter. Implements ticket 12688.
13686 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
13687 implementation that caused incorrect results on 32-bit
13688 implementations when certain malformed inputs were used along with
13689 a small class of private ntor keys. This bug does not currently
13690 appear to allow an attacker to learn private keys or impersonate a
13691 Tor server, but it could provide a means to distinguish 32-bit Tor
13692 implementations from 64-bit Tor implementations. Fixes bug 12694;
13693 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
13697 - Warn and drop the circuit if we receive an inbound 'relay early'
13698 cell. Those used to be normal to receive on hidden service circuits
13699 due to bug 1038, but the buggy Tor versions are long gone from
13700 the network so we can afford to resume watching for them. Resolves
13701 the rest of bug 1038; bugfix on 0.2.1.19.
13702 - Correct a confusing error message when trying to extend a circuit
13703 via the control protocol but we don't know a descriptor or
13704 microdescriptor for one of the specified relays. Fixes bug 12718;
13705 bugfix on 0.2.3.1-alpha.
13706 - Avoid an illegal read from stack when initializing the TLS
13707 module using a version of OpenSSL without all of the ciphers
13708 used by the v2 link handshake. Fixes bug 12227; bugfix on
13709 0.2.4.8-alpha. Found by "starlight".
13712 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
13716 Changes in version 0.2.5.5-alpha - 2014-06-18
13717 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
13718 0.2.5.x release series, including a couple of DoS issues, some
13719 performance regressions, a large number of bugs affecting the Linux
13720 seccomp2 sandbox code, and various other bugfixes. It also adds
13721 diagnostic bugfixes for a few tricky issues that we're trying to
13724 o Major features (security, traffic analysis resistance):
13725 - Several major improvements to the algorithm used to decide when to
13726 close TLS connections. Previous versions of Tor closed connections
13727 at a fixed interval after the last time a non-padding cell was
13728 sent over the connection, regardless of the target of the
13729 connection. Now, we randomize the intervals by adding up to 50% of
13730 their base value, we measure the length of time since connection
13731 last had at least one circuit, and we allow connections to known
13732 ORs to remain open a little longer (15 minutes instead of 3
13733 minutes minimum). These changes should improve Tor's resistance
13734 against some kinds of traffic analysis, and lower some overhead
13735 from needlessly closed connections. Fixes ticket 6799.
13736 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
13738 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
13739 - Fix a memory leak that could occur if a microdescriptor parse
13740 fails during the tokenizing step. This bug could enable a memory
13741 exhaustion attack by directory servers. Fixes bug 11649; bugfix
13744 o Major bugfixes (security, directory authorities):
13745 - Directory authorities now include a digest of each relay's
13746 identity key as a part of its microdescriptor.
13748 This is a workaround for bug 11743 (reported by "cypherpunks"),
13749 where Tor clients do not support receiving multiple
13750 microdescriptors with the same SHA256 digest in the same
13751 consensus. When clients receive a consensus like this, they only
13752 use one of the relays. Without this fix, a hostile relay could
13753 selectively disable some client use of target relays by
13754 constructing a router descriptor with a different identity and the
13755 same microdescriptor parameters and getting the authorities to
13756 list it in a microdescriptor consensus. This fix prevents an
13757 attacker from causing a microdescriptor collision, because the
13758 router's identity is not forgeable.
13760 o Major bugfixes (relay):
13761 - Use a direct dirport connection when uploading non-anonymous
13762 descriptors to the directory authorities. Previously, relays would
13763 incorrectly use tunnel connections under a fairly wide variety of
13764 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
13765 - When a circuit accidentally has the same circuit ID for its
13766 forward and reverse direction, correctly detect the direction of
13767 cells using that circuit. Previously, this bug made roughly one
13768 circuit in a million non-functional. Fixes bug 12195; this is a
13769 bugfix on every version of Tor.
13771 o Major bugfixes (client, pluggable transports):
13772 - When managing pluggable transports, use OS notification facilities
13773 to learn if they have crashed, and don't attempt to kill any
13774 process that has already exited. Fixes bug 8746; bugfix
13777 o Minor features (diagnostic):
13778 - When logging a warning because of bug 7164, additionally check the
13779 hash table for consistency (as proposed on ticket 11737). This may
13780 help diagnose bug 7164.
13781 - When we log a heartbeat, log how many one-hop circuits we have
13782 that are at least 30 minutes old, and log status information about
13783 a few of them. This is an attempt to track down bug 8387.
13784 - When encountering an unexpected CR while writing text to a file on
13785 Windows, log the name of the file. Should help diagnosing
13787 - Give more specific warnings when a client notices that an onion
13788 handshake has failed. Fixes ticket 9635.
13789 - Add significant new logging code to attempt to diagnose bug 12184,
13790 where relays seem to run out of available circuit IDs.
13791 - Improve the diagnostic log message for bug 8387 even further to
13792 try to improve our odds of figuring out why one-hop directory
13793 circuits sometimes do not get closed.
13795 o Minor features (security, memory management):
13796 - Memory allocation tricks (mempools and buffer freelists) are now
13797 disabled by default. You can turn them back on with
13798 --enable-mempools and --enable-buf-freelists respectively. We're
13799 disabling these features because malloc performance is good enough
13800 on most platforms, and a similar feature in OpenSSL exacerbated
13801 exploitation of the Heartbleed attack. Resolves ticket 11476.
13803 o Minor features (security):
13804 - Apply the secure SipHash-2-4 function to the hash table mapping
13805 circuit IDs and channels to circuits. We missed this one when we
13806 were converting all the other hash functions to use SipHash back
13807 in 0.2.5.3-alpha. Resolves ticket 11750.
13809 o Minor features (build):
13810 - The configure script has a --disable-seccomp option to turn off
13811 support for libseccomp on systems that have it, in case it (or
13812 Tor's use of it) is broken. Resolves ticket 11628.
13814 o Minor features (other):
13815 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
13818 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
13819 - When running a hidden service, do not allow TunneledDirConns 0;
13820 this will keep the hidden service from running, and also
13821 make it publish its descriptors directly over HTTP. Fixes bug 10849;
13822 bugfix on 0.2.1.1-alpha.
13824 o Minor bugfixes (performance):
13825 - Avoid a bug where every successful connection made us recompute
13826 the flag telling us whether we have sufficient information to
13827 build circuits. Previously, we would forget our cached value
13828 whenever we successfully opened a channel (or marked a router as
13829 running or not running for any other reason), regardless of
13830 whether we had previously believed the router to be running. This
13831 forced us to run an expensive update operation far too often.
13832 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
13833 - Avoid using tor_memeq() for checking relay cell integrity. This
13834 removes a possible performance bottleneck. Fixes part of bug
13835 12169; bugfix on 0.2.1.31.
13837 o Minor bugfixes (compilation):
13838 - Fix compilation of test_status.c when building with MVSC. Bugfix
13839 on 0.2.5.4-alpha. Patch from Gisle Vanem.
13840 - Resolve GCC complaints on OpenBSD about discarding constness in
13841 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
13842 on 0.1.1.23. Patch from Dana Koch.
13843 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
13844 treatment of long and time_t as comparable types. Fixes part of
13845 bug 11633. Patch from Dana Koch.
13846 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
13847 11623; bugfix on 0.2.5.3-alpha.
13848 - When deciding whether to build the 64-bit curve25519
13849 implementation, detect platforms where we can compile 128-bit
13850 arithmetic but cannot link it. Fixes bug 11729; bugfix on
13851 0.2.4.8-alpha. Patch from "conradev".
13852 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
13853 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
13854 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
13857 o Minor bugfixes (Directory server):
13858 - When sending a compressed set of descriptors or microdescriptors,
13859 make sure to finalize the zlib stream. Previously, we would write
13860 all the compressed data, but if the last descriptor we wanted to
13861 send was missing or too old, we would not mark the stream as
13862 finished. This caused problems for decompression tools. Fixes bug
13863 11648; bugfix on 0.1.1.23.
13865 o Minor bugfixes (Linux seccomp sandbox):
13866 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
13867 11622; bugfix on 0.2.5.1-alpha.
13868 - Avoid crashing when re-opening listener ports with the seccomp
13869 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
13870 - Avoid crashing with the seccomp sandbox enabled along with
13871 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
13872 - When we receive a SIGHUP with the sandbox enabled, correctly
13873 support rotating our log files. Fixes bug 12032; bugfix
13875 - Avoid crash when running with sandboxing enabled and
13876 DirReqStatistics not disabled. Fixes bug 12035; bugfix
13878 - Fix a "BUG" warning when trying to write bridge-stats files with
13879 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
13881 - Prevent the sandbox from crashing on startup when run with the
13882 --enable-expensive-hardening configuration option. Fixes bug
13883 11477; bugfix on 0.2.5.4-alpha.
13884 - When running with DirPortFrontPage and sandboxing both enabled,
13885 reload the DirPortFrontPage correctly when restarting. Fixes bug
13886 12028; bugfix on 0.2.5.1-alpha.
13887 - Don't try to enable the sandbox when using the Tor binary to check
13888 its configuration, hash a passphrase, or so on. Doing so was
13889 crashing on startup for some users. Fixes bug 11609; bugfix
13891 - Avoid warnings when running with sandboxing and node statistics
13892 enabled at the same time. Fixes part of 12064; bugfix on
13893 0.2.5.1-alpha. Patch from Michael Wolf.
13894 - Avoid warnings when running with sandboxing enabled at the same
13895 time as cookie authentication, hidden services, or directory
13896 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
13897 - Do not allow options that require calls to exec to be enabled
13898 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
13899 bug 12043; bugfix on 0.2.5.1-alpha.
13900 - Handle failures in getpwnam()/getpwuid() when running with the
13901 User option set and the Linux syscall sandbox enabled. Fixes bug
13902 11946; bugfix on 0.2.5.1-alpha.
13903 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
13904 to avoid calling getaddrinfo() after installing the sandbox
13905 filters. Previously, it preloaded a cache with the IPv4 address
13906 for our hostname, and nothing else. Now, it loads the cache with
13907 every address that it used to initialize the Tor process. Fixes
13908 bug 11970; bugfix on 0.2.5.1-alpha.
13910 o Minor bugfixes (pluggable transports):
13911 - Enable the ExtORPortCookieAuthFile option, to allow changing the
13912 default location of the authentication token for the extended OR
13913 Port as used by sever-side pluggable transports. We had
13914 implemented this option before, but the code to make it settable
13915 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
13916 - Avoid another 60-second delay when starting Tor in a pluggable-
13917 transport-using configuration when we already have cached
13918 descriptors for our bridges. Fixes bug 11965; bugfix
13921 o Minor bugfixes (client):
13922 - Avoid "Tried to open a socket with DisableNetwork set" warnings
13923 when starting a client with bridges configured and DisableNetwork
13924 set. (Tor launcher starts Tor with DisableNetwork set the first
13925 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
13927 o Minor bugfixes (testing):
13928 - The Python parts of the test scripts now work on Python 3 as well
13929 as Python 2, so systems where '/usr/bin/python' is Python 3 will
13930 no longer have the tests break. Fixes bug 11608; bugfix
13932 - When looking for versions of python that we could run the tests
13933 with, check for "python2.7" and "python3.3"; previously we were
13934 only looking for "python", "python2", and "python3". Patch from
13935 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
13936 - Fix all valgrind warnings produced by the unit tests. There were
13937 over a thousand memory leak warnings previously, mostly produced
13938 by forgetting to free things in the unit test code. Fixes bug
13939 11618, bugfixes on many versions of Tor.
13941 o Minor bugfixes (tor-fw-helper):
13942 - Give a correct log message when tor-fw-helper fails to launch.
13943 (Previously, we would say something like "tor-fw-helper sent us a
13944 string we could not parse".) Fixes bug 9781; bugfix
13947 o Minor bugfixes (relay, threading):
13948 - Check return code on spawn_func() in cpuworker code, so that we
13949 don't think we've spawned a nonworking cpuworker and write junk to
13950 it forever. Fix related to bug 4345; bugfix on all released Tor
13951 versions. Found by "skruffy".
13952 - Use a pthread_attr to make sure that spawn_func() cannot return an
13953 error while at the same time launching a thread. Fix related to
13954 bug 4345; bugfix on all released Tor versions. Reported
13957 o Minor bugfixes (relay, oom prevention):
13958 - Correctly detect the total available system memory. We tried to do
13959 this in 0.2.5.4-alpha, but the code was set up to always return an
13960 error value, even on success. Fixes bug 11805; bugfix
13963 o Minor bugfixes (relay, other):
13964 - We now drop CREATE cells for already-existent circuit IDs and for
13965 zero-valued circuit IDs, regardless of other factors that might
13966 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
13968 - Avoid an illegal read from stack when initializing the TLS module
13969 using a version of OpenSSL without all of the ciphers used by the
13970 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
13972 - When rejecting DATA cells for stream_id zero, still count them
13973 against the circuit's deliver window so that we don't fail to send
13974 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
13976 o Minor bugfixes (logging):
13977 - Fix a misformatted log message about delayed directory fetches.
13978 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
13979 - Squelch a spurious LD_BUG message "No origin circuit for
13980 successful SOCKS stream" in certain hidden service failure cases;
13984 - Include a tor.service file in contrib/dist for use with systemd.
13985 Some distributions will be able to use this file unmodified;
13986 others will need to tweak it, or write their own. Patch from Jamie
13987 Nguyen; resolves ticket 8368.
13990 - Clean up several option names in the manpage to match their real
13991 names, add the missing documentation for a couple of testing and
13992 directory authority options, remove the documentation for a
13993 V2-directory fetching option that no longer exists. Resolves
13995 - Correct the documentation so that it lists the correct directory
13996 for the stats files. (They are in a subdirectory called "stats",
13998 - In the manpage, move more authority-only options into the
13999 directory authority section so that operators of regular directory
14000 caches don't get confused.
14003 - The contrib directory has been sorted and tidied. Before, it was
14004 an unsorted dumping ground for useful and not-so-useful things.
14005 Now, it is divided based on functionality, and the items which
14006 seemed to be nonfunctional or useless have been removed. Resolves
14007 ticket 8966; based on patches from "rl1987".
14010 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
14011 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
14012 - The TunnelDirConns and PreferTunnelledDirConns options no longer
14013 exist; tunneled directory connections have been available since
14014 0.1.2.5-alpha, and turning them off is not a good idea. This is a
14015 brute-force fix for 10849, where "TunnelDirConns 0" would break
14019 Changes in version 0.2.4.22 - 2014-05-16
14020 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
14021 alpha release series. These include blocking all authority signing
14022 keys that may have been affected by the OpenSSL "heartbleed" bug,
14023 choosing a far more secure set of TLS ciphersuites by default, closing
14024 a couple of memory leaks that could be used to run a target relay out
14025 of RAM, and several others.
14027 o Major features (security, backport from 0.2.5.4-alpha):
14028 - Block authority signing keys that were used on authorities
14029 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
14030 don't have any evidence that these keys _were_ compromised; we're
14031 doing this to be prudent.) Resolves ticket 11464.
14033 o Major bugfixes (security, OOM):
14034 - Fix a memory leak that could occur if a microdescriptor parse
14035 fails during the tokenizing step. This bug could enable a memory
14036 exhaustion attack by directory servers. Fixes bug 11649; bugfix
14039 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
14040 - The relay ciphersuite list is now generated automatically based on
14041 uniform criteria, and includes all OpenSSL ciphersuites with
14042 acceptable strength and forward secrecy. Previously, we had left
14043 some perfectly fine ciphersuites unsupported due to omission or
14044 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
14045 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
14046 - Relays now trust themselves to have a better view than clients of
14047 which TLS ciphersuites are better than others. (Thanks to bug
14048 11513, the relay list is now well-considered, whereas the client
14049 list has been chosen mainly for anti-fingerprinting purposes.)
14050 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
14051 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
14052 AES128. Resolves ticket 11528.
14053 - Clients now try to advertise the same list of ciphersuites as
14054 Firefox 28. This change enables selection of (fast) GCM
14055 ciphersuites, disables some strange old ciphers, and stops
14056 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
14057 Resolves ticket 11438.
14059 o Minor bugfixes (configuration, security):
14060 - When running a hidden service, do not allow TunneledDirConns 0:
14061 trying to set that option together with a hidden service would
14062 otherwise prevent the hidden service from running, and also make
14063 it publish its descriptors directly over HTTP. Fixes bug 10849;
14064 bugfix on 0.2.1.1-alpha.
14066 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
14067 - Avoid sending a garbage value to the controller when a circuit is
14068 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
14070 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
14071 - Stop leaking memory when we successfully resolve a PTR record.
14072 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
14074 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
14075 - Avoid 60-second delays in the bootstrapping process when Tor is
14076 launching for a second time while using bridges. Fixes bug 9229;
14077 bugfix on 0.2.0.3-alpha.
14079 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
14080 - Give the correct URL in the warning message when trying to run a
14081 relay on an ancient version of Windows. Fixes bug 9393.
14083 o Minor bugfixes (compilation):
14084 - Fix a compilation error when compiling with --disable-curve25519.
14085 Fixes bug 9700; bugfix on 0.2.4.17-rc.
14088 - Downgrade the warning severity for the the "md was still
14089 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
14090 for trying to diagnose this bug, and the current warning in
14091 earlier versions of tor achieves nothing useful. Addresses warning
14094 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
14095 - When we run out of usable circuit IDs on a channel, log only one
14096 warning for the whole channel, and describe how many circuits
14097 there were on the channel. Fixes part of ticket 11553.
14099 o Minor features (security, backport from 0.2.5.4-alpha):
14100 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
14101 leave the default at 8GBytes), to better support Raspberry Pi
14102 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
14104 o Documentation (backport from 0.2.5.4-alpha):
14105 - Correctly document that we search for a system torrc file before
14106 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
14110 Changes in version 0.2.5.4-alpha - 2014-04-25
14111 Tor 0.2.5.4-alpha includes several security and performance
14112 improvements for clients and relays, including blacklisting authority
14113 signing keys that were used while susceptible to the OpenSSL
14114 "heartbleed" bug, fixing two expensive functions on busy relays,
14115 improved TLS ciphersuite preference lists, support for run-time
14116 hardening on compilers that support AddressSanitizer, and more work on
14117 the Linux sandbox code.
14119 There are also several usability fixes for clients (especially clients
14120 that use bridges), two new TransPort protocols supported (one on
14121 OpenBSD, one on FreeBSD), and various other bugfixes.
14123 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
14124 have accumulated many known flaws; everyone should upgrade.
14126 o Major features (security):
14127 - If you don't specify MaxMemInQueues yourself, Tor now tries to
14128 pick a good value based on your total system memory. Previously,
14129 the default was always 8 GB. You can still override the default by
14130 setting MaxMemInQueues yourself. Resolves ticket 11396.
14131 - Block authority signing keys that were used on authorities
14132 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
14133 don't have any evidence that these keys _were_ compromised; we're
14134 doing this to be prudent.) Resolves ticket 11464.
14136 o Major features (relay performance):
14137 - Speed up server-side lookups of rendezvous and introduction point
14138 circuits by using hashtables instead of linear searches. These
14139 functions previously accounted between 3 and 7% of CPU usage on
14140 some busy relays. Resolves ticket 9841.
14141 - Avoid wasting CPU when extending a circuit over a channel that is
14142 nearly out of circuit IDs. Previously, we would do a linear scan
14143 over possible circuit IDs before finding one or deciding that we
14144 had exhausted our possibilities. Now, we try at most 64 random
14145 circuit IDs before deciding that we probably won't succeed. Fixes
14146 a possible root cause of ticket 11553.
14148 o Major features (seccomp2 sandbox, Linux only):
14149 - The seccomp2 sandbox can now run a test network for multiple hours
14150 without crashing. The sandbox is still experimental, and more bugs
14151 will probably turn up. To try it, enable "Sandbox 1" on a Linux
14152 host. Resolves ticket 11351.
14153 - Strengthen sandbox code: the sandbox can now test the arguments
14154 for rename(), and blocks _sysctl() entirely. Resolves another part
14156 - When the sandbox blocks a system call, it now tries to log a stack
14157 trace before exiting. Resolves ticket 11465.
14159 o Major bugfixes (TLS cipher selection):
14160 - The relay ciphersuite list is now generated automatically based on
14161 uniform criteria, and includes all OpenSSL ciphersuites with
14162 acceptable strength and forward secrecy. Previously, we had left
14163 some perfectly fine ciphersuites unsupported due to omission or
14164 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
14165 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
14166 - Relays now trust themselves to have a better view than clients of
14167 which TLS ciphersuites are better than others. (Thanks to bug
14168 11513, the relay list is now well-considered, whereas the client
14169 list has been chosen mainly for anti-fingerprinting purposes.)
14170 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
14171 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
14172 AES128. Resolves ticket 11528.
14173 - Clients now try to advertise the same list of ciphersuites as
14174 Firefox 28. This change enables selection of (fast) GCM
14175 ciphersuites, disables some strange old ciphers, and stops
14176 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
14177 Resolves ticket 11438.
14179 o Major bugfixes (bridge client):
14180 - Avoid 60-second delays in the bootstrapping process when Tor is
14181 launching for a second time while using bridges. Fixes bug 9229;
14182 bugfix on 0.2.0.3-alpha.
14184 o Minor features (transparent proxy, *BSD):
14185 - Support FreeBSD's ipfw firewall interface for TransPort ports on
14186 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
14187 10267; patch from "yurivict".
14188 - Support OpenBSD's divert-to rules with the pf firewall for
14189 transparent proxy ports. To enable it, set "TransProxyType
14190 pf-divert". This allows Tor to run a TransPort transparent proxy
14191 port on OpenBSD 4.4 or later without root privileges. See the
14192 pf.conf(5) manual page for information on configuring pf to use
14193 divert-to rules. Closes ticket 10896; patch from Dana Koch.
14195 o Minor features (security):
14196 - New --enable-expensive-hardening option to enable security
14197 hardening options that consume nontrivial amounts of CPU and
14198 memory. Right now, this includes AddressSanitizer and UbSan, which
14199 are supported in newer versions of GCC and Clang. Closes ticket
14202 o Minor features (log verbosity):
14203 - Demote the message that we give when a flushing connection times
14204 out for too long from NOTICE to INFO. It was usually meaningless.
14205 Resolves ticket 5286.
14206 - Don't log so many notice-level bootstrapping messages at startup
14207 about downloading descriptors. Previously, we'd log a notice
14208 whenever we learned about more routers. Now, we only log a notice
14209 at every 5% of progress. Fixes bug 9963.
14210 - Warn less verbosely when receiving a malformed
14211 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
14212 - When we run out of usable circuit IDs on a channel, log only one
14213 warning for the whole channel, and describe how many circuits
14214 there were on the channel. Fixes part of ticket 11553.
14216 o Minor features (relay):
14217 - If a circuit timed out for at least 3 minutes, check if we have a
14218 new external IP address, and publish a new descriptor with the new
14219 IP address if it changed. Resolves ticket 2454.
14221 o Minor features (controller):
14222 - Make the entire exit policy available from the control port via
14223 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
14225 - Because of the fix for ticket 11396, the real limit for memory
14226 usage may no longer match the configured MaxMemInQueues value. The
14227 real limit is now exposed via GETINFO limits/max-mem-in-queues.
14229 o Minor features (bridge client):
14230 - Report a more useful failure message when we can't connect to a
14231 bridge because we don't have the right pluggable transport
14232 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
14234 o Minor features (diagnostic):
14235 - Add more log messages to diagnose bug 7164, which causes
14236 intermittent "microdesc_free() called but md was still referenced"
14237 warnings. We now include more information, to figure out why we
14238 might be cleaning a microdescriptor for being too old if it's
14239 still referenced by a live node_t object.
14241 o Minor bugfixes (client, DNSPort):
14242 - When using DNSPort, try to respond to AAAA requests with AAAA
14243 answers. Previously, we hadn't looked at the request type when
14244 deciding which answer type to prefer. Fixes bug 10468; bugfix on
14246 - When receiving a DNS query for an unsupported record type, reply
14247 with no answer rather than with a NOTIMPL error. This behavior
14248 isn't correct either, but it will break fewer client programs, we
14249 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
14252 o Minor bugfixes (exit relay):
14253 - Stop leaking memory when we successfully resolve a PTR record.
14254 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
14256 o Minor bugfixes (bridge client):
14257 - Stop accepting bridge lines containing hostnames. Doing so would
14258 cause clients to perform DNS requests on the hostnames, which was
14259 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
14260 - Avoid a 60-second delay in the bootstrapping process when a Tor
14261 client with pluggable transports re-reads its configuration at
14262 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
14264 o Minor bugfixes (client, logging during bootstrap):
14265 - Warn only once if we start logging in an unsafe way. Previously,
14266 we complain as many times as we had problems. Fixes bug 9870;
14267 bugfix on 0.2.5.1-alpha.
14268 - Only report the first fatal bootstrap error on a given OR
14269 connection. This stops us from telling the controller bogus error
14270 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
14271 - Be more helpful when trying to run sandboxed on Linux without
14272 libseccomp. Instead of saying "Sandbox is not implemented on this
14273 platform", we now explain that we need to be built with
14274 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
14275 - Avoid generating spurious warnings when starting with
14276 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
14279 o Minor bugfixes (closing OR connections):
14280 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
14281 check if it's an or_connection_t and correctly call
14282 connection_or_close_for_error() rather than
14283 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
14285 - When closing all connections on setting DisableNetwork to 1, use
14286 connection_or_close_normally() rather than closing OR connections
14287 out from under the channel layer. Fixes bug 11306; bugfix on
14290 o Minor bugfixes (controller):
14291 - Avoid sending a garbage value to the controller when a circuit is
14292 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
14294 o Minor bugfixes (tor-fw-helper):
14295 - Allow tor-fw-helper to build again by adding src/ext to its
14296 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
14298 o Minor bugfixes (bridges):
14299 - Avoid potential crashes or bad behavior when launching a
14300 server-side managed proxy with ORPort or ExtORPort temporarily
14301 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
14303 o Minor bugfixes (platform-specific):
14304 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
14305 bug 11426; bugfix on 0.2.5.3-alpha.
14306 - When dumping a malformed directory object to disk, save it in
14307 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
14309 - Don't report failures from make_socket_reuseable() on incoming
14310 sockets on OSX: this can happen when incoming connections close
14311 early. Fixes bug 10081.
14313 o Minor bugfixes (trivial memory leaks):
14314 - Fix a small memory leak when signing a directory object. Fixes bug
14315 11275; bugfix on 0.2.4.13-alpha.
14316 - Free placeholder entries in our circuit table at exit; fixes a
14317 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
14318 - Don't re-initialize a second set of OpenSSL mutexes when starting
14319 up. Previously, we'd make one set of mutexes, and then immediately
14320 replace them with another. Fixes bug 11726; bugfix on
14322 - Resolve some memory leaks found by coverity in the unit tests, on
14323 exit in tor-gencert, and on a failure to compute digests for our
14324 own keys when generating a v3 networkstatus vote. These leaks
14325 should never have affected anyone in practice.
14327 o Minor bugfixes (hidden service):
14328 - Only retry attempts to connect to a chosen rendezvous point 8
14329 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
14331 o Minor bugfixes (misc code correctness):
14332 - Fix various instances of undefined behavior in channeltls.c,
14333 tor_memmem(), and eventdns.c that would cause us to construct
14334 pointers to memory outside an allocated object. (These invalid
14335 pointers were not accessed, but C does not even allow them to
14336 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
14337 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
14338 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
14339 fix some miscellaneous errors in our tests and codebase. Fixes bug
14340 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
14341 - Always check return values for unlink, munmap, UnmapViewOfFile;
14342 check strftime return values more often. In some cases all we can
14343 do is report a warning, but this may help prevent deeper bugs from
14344 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
14346 - Fix numerous warnings from the clang "scan-build" static analyzer.
14347 Some of these are programming style issues; some of them are false
14348 positives that indicated awkward code; some are undefined behavior
14349 cases related to constructing (but not using) invalid pointers;
14350 some are assumptions about API behavior; some are (harmlessly)
14351 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
14352 correct; and one or two are genuine bugs that weren't reachable
14353 from the rest of the program. Fixes bug 8793; bugfixes on many,
14357 - Build the torify.1 manpage again. Previously, we were only trying
14358 to build it when also building tor-fw-helper. That's why we didn't
14359 notice that we'd broken the ability to build it. Fixes bug 11321;
14360 bugfix on 0.2.5.1-alpha.
14361 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
14362 11061; bugfix on 0.2.4.7-alpha.
14363 - Correctly document that we search for a system torrc file before
14364 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
14366 - Resolve warnings from Doxygen.
14368 o Code simplifications and refactoring:
14369 - Remove is_internal_IP() function. Resolves ticket 4645.
14370 - Remove unused function circuit_dump_by_chan from circuitlist.c.
14371 Closes issue 9107; patch from "marek".
14372 - Change our use of the ENUM_BF macro to avoid declarations that
14375 o Deprecated versions:
14376 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
14377 attention for some while. Directory authorities no longer accept
14378 descriptors from relays running any version of Tor prior to Tor
14379 0.2.3.16-alpha. Resolves ticket 11149.
14382 - New macros in test.h to simplify writing mock-functions for unit
14383 tests. Part of ticket 11507. Patch from Dana Koch.
14384 - Complete tests for the status.c module. Resolves ticket 11507.
14385 Patch from Dana Koch.
14388 - Remove all code for the long unused v1 directory protocol.
14389 Resolves ticket 11070.
14392 Changes in version 0.2.5.3-alpha - 2014-03-22
14393 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
14394 two new anti-DoS features for Tor relays, resolves a bug that kept
14395 SOCKS5 support for IPv6 from working, fixes several annoying usability
14396 issues for bridge users, and removes more old code for unused
14399 The Tor 0.2.5.x release series is now in patch-freeze: no feature
14400 patches not already written will be considered for inclusion in 0.2.5.x.
14402 o Major features (relay security, DoS-resistance):
14403 - When deciding whether we have run out of memory and we need to
14404 close circuits, also consider memory allocated in buffers for
14405 streams attached to each circuit.
14407 This change, which extends an anti-DoS feature introduced in
14408 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
14409 better resist more memory-based DoS attacks than before. Since the
14410 MaxMemInCellQueues option now applies to all queues, it is renamed
14411 to MaxMemInQueues. This feature fixes bug 10169.
14412 - Avoid hash-flooding denial-of-service attacks by using the secure
14413 SipHash-2-4 hash function for our hashtables. Without this
14414 feature, an attacker could degrade performance of a targeted
14415 client or server by flooding their data structures with a large
14416 number of entries to be stored at the same hash table position,
14417 thereby slowing down the Tor instance. With this feature, hash
14418 table positions are derived from a randomized cryptographic key,
14419 and an attacker cannot predict which entries will collide. Closes
14421 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
14422 the default at 8GBytes), to better support Raspberry Pi users. Fixes
14423 bug 9686; bugfix on 0.2.4.14-alpha.
14425 o Minor features (bridges, pluggable transports):
14426 - Bridges now write the SHA1 digest of their identity key
14427 fingerprint (that is, a hash of a hash of their public key) to
14428 notice-level logs, and to a new hashed-fingerprint file. This
14429 information will help bridge operators look up their bridge in
14430 Globe and similar tools. Resolves ticket 10884.
14431 - Improve the message that Tor displays when running as a bridge
14432 using pluggable transports without an Extended ORPort listener.
14433 Also, log the message in the log file too. Resolves ticket 11043.
14435 o Minor features (other):
14436 - Add a new option, PredictedPortsRelevanceTime, to control how long
14437 after having received a request to connect to a given port Tor
14438 will try to keep circuits ready in anticipation of future requests
14439 for that port. Patch from "unixninja92"; implements ticket 9176.
14440 - Generate a warning if any ports are listed in the SocksPolicy,
14441 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
14442 AuthDirBadExit options. (These options only support address
14443 ranges.) Fixes part of ticket 11108.
14444 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
14447 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
14448 - Build without warnings under clang 3.4. (We have some macros that
14449 define static functions only some of which will get used later in
14450 the module. Starting with clang 3.4, these give a warning unless the
14451 unused attribute is set on them.) Resolves ticket 10904.
14452 - Fix build warnings about missing "a2x" comment when building the
14453 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
14454 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
14456 o Minor bugfixes (client):
14457 - Improve the log message when we can't connect to a hidden service
14458 because all of the hidden service directory nodes hosting its
14459 descriptor are excluded. Improves on our fix for bug 10722, which
14460 was a bugfix on 0.2.0.10-alpha.
14461 - Raise a control port warning when we fail to connect to all of
14462 our bridges. Previously, we didn't inform the controller, and
14463 the bootstrap process would stall. Fixes bug 11069; bugfix on
14465 - Exit immediately when a process-owning controller exits.
14466 Previously, tor relays would wait for a little while after their
14467 controller exited, as if they had gotten an INT signal -- but this
14468 was problematic, since there was no feedback for the user. To do a
14469 clean shutdown, controllers should send an INT signal and give Tor
14470 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
14471 - Stop attempting to connect to bridges before our pluggable
14472 transports are configured (harmless but resulted in some erroneous
14473 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
14474 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
14475 generating incorrect SOCKS5 responses, and confusing client
14476 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
14478 o Minor bugfixes (relays and bridges):
14479 - Avoid crashing on a malformed resolv.conf file when running a
14480 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
14481 - Non-exit relays no longer launch mock DNS requests to check for
14482 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
14483 non-exit relays stopped servicing DNS requests. Fixes bug 965;
14484 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
14485 - Bridges now report complete directory request statistics. Related
14486 to bug 5824; bugfix on 0.2.2.1-alpha.
14487 - Bridges now never collect statistics that were designed for
14488 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
14489 - Stop giving annoying warning messages when we decide not to launch
14490 a pluggable transport proxy that we don't need (because there are
14491 no bridges configured to use it). Resolves ticket 5018; bugfix
14493 - Give the correct URL in the warning message when trying to run a
14494 relay on an ancient version of Windows. Fixes bug 9393.
14496 o Minor bugfixes (backtrace support):
14497 - Support automatic backtraces on more platforms by using the
14498 "-fasynchronous-unwind-tables" compiler option. This option is
14499 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
14500 is on by default and table generation is not. This doesn't yet
14501 add Windows support; only Linux, OSX, and some BSDs are affected.
14502 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
14503 - Avoid strange behavior if two threads hit failed assertions at the
14504 same time and both try to log backtraces at once. (Previously, if
14505 this had happened, both threads would have stored their intermediate
14506 results in the same buffer, and generated junk outputs.) Reported by
14507 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
14508 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
14509 0.2.5.2-alpha; patch from Nick Hopper.
14511 o Minor bugfixes (unit tests):
14512 - Fix a small bug in the unit tests that might have made the tests
14513 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
14514 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
14517 - Remove all remaining code related to version-0 hidden service
14518 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
14519 the rest of bug 10841.
14522 - Document in the manpage that "KBytes" may also be written as
14523 "kilobytes" or "KB", that "Kbits" may also be written as
14524 "kilobits", and so forth. Closes ticket 9222.
14525 - Document that the ClientOnly config option overrides ORPort.
14526 Our old explanation made ClientOnly sound as though it did
14527 nothing at all. Resolves bug 9059.
14528 - Explain that SocksPolicy, DirPolicy, and similar options don't
14529 take port arguments. Fixes the other part of ticket 11108.
14530 - Fix a comment about the rend_server_descriptor_t.protocols field
14531 to more accurately describe its range. Also, make that field
14532 unsigned, to more accurately reflect its usage. Fixes bug 9099;
14533 bugfix on 0.2.1.5-alpha.
14534 - Fix the manpage's description of HiddenServiceAuthorizeClient:
14535 the maximum client name length is 16, not 19. Fixes bug 11118;
14536 bugfix on 0.2.1.6-alpha.
14538 o Code simplifications and refactoring:
14539 - Get rid of router->address, since in all cases it was just the
14540 string representation of router->addr. Resolves ticket 5528.
14542 o Test infrastructure:
14543 - Update to the latest version of tinytest.
14544 - Improve the tinytest implementation of string operation tests so
14545 that comparisons with NULL strings no longer crash the tests; they
14546 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
14549 Changes in version 0.2.4.21 - 2014-02-28
14550 Tor 0.2.4.21 further improves security against potential adversaries who
14551 find breaking 1024-bit crypto doable, and backports several stability
14552 and robustness patches from the 0.2.5 branch.
14554 o Major features (client security):
14555 - When we choose a path for a 3-hop circuit, make sure it contains
14556 at least one relay that supports the NTor circuit extension
14557 handshake. Otherwise, there is a chance that we're building
14558 a circuit that's worth attacking by an adversary who finds
14559 breaking 1024-bit crypto doable, and that chance changes the game
14560 theory. Implements ticket 9777.
14563 - Do not treat streams that fail with reason
14564 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
14565 since it could also indicate an ENETUNREACH connection error. Fixes
14566 part of bug 10777; bugfix on 0.2.4.8-alpha.
14568 o Code simplification and refactoring:
14569 - Remove data structures which were introduced to implement the
14570 CellStatistics option: they are now redundant with the new timestamp
14571 field in the regular packed_cell_t data structure, which we did
14572 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
14575 - Always clear OpenSSL bignums before freeing them -- even bignums
14576 that don't contain secrets. Resolves ticket 10793. Patch by
14578 - Build without warnings under clang 3.4. (We have some macros that
14579 define static functions only some of which will get used later in
14580 the module. Starting with clang 3.4, these give a warning unless the
14581 unused attribute is set on them.) Resolves ticket 10904.
14582 - Update geoip and geoip6 files to the February 7 2014 Maxmind
14583 GeoLite2 Country database.
14586 - Set the listen() backlog limit to the largest actually supported
14587 on the system, not to the value in a header file. Fixes bug 9716;
14588 bugfix on every released Tor.
14589 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
14590 exit node as a NOROUTE error, not an INTERNAL error, since they
14591 can apparently happen when trying to connect to the wrong sort
14592 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
14593 - Fix build warnings about missing "a2x" comment when building the
14594 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
14595 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
14596 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
14597 not entirely remove it from the connection lists. Fixes bug 9602;
14598 bugfix on 0.2.4.4-alpha.
14599 - Fix a segmentation fault in our benchmark code when running with
14600 Fedora's OpenSSL package, or any other OpenSSL that provides
14601 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
14602 - Turn "circuit handshake stats since last time" log messages into a
14603 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
14605 o Documentation fixes:
14606 - Document that all but one DirPort entry must have the NoAdvertise
14607 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
14610 Changes in version 0.2.5.2-alpha - 2014-02-13
14611 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
14612 like the "poor random number generation" fix and the "building too many
14613 circuits" fix. It also further improves security against potential
14614 adversaries who find breaking 1024-bit crypto doable, and launches
14615 pluggable transports on demand (which gets us closer to integrating
14616 pluggable transport support by default -- not to be confused with Tor
14617 bundles enabling pluggable transports and bridges by default).
14619 o Major features (client security):
14620 - When we choose a path for a 3-hop circuit, make sure it contains
14621 at least one relay that supports the NTor circuit extension
14622 handshake. Otherwise, there is a chance that we're building
14623 a circuit that's worth attacking by an adversary who finds
14624 breaking 1024-bit crypto doable, and that chance changes the game
14625 theory. Implements ticket 9777.
14626 - Clients now look at the "usecreatefast" consensus parameter to
14627 decide whether to use CREATE_FAST or CREATE cells for the first hop
14628 of their circuit. This approach can improve security on connections
14629 where Tor's circuit handshake is stronger than the available TLS
14630 connection security levels, but the tradeoff is more computational
14631 load on guard relays. Implements proposal 221. Resolves ticket 9386.
14633 o Major features (bridges):
14634 - Don't launch pluggable transport proxies if we don't have any
14635 bridges configured that would use them. Now we can list many
14636 pluggable transports, and Tor will dynamically start one when it
14637 hears a bridge address that needs it. Resolves ticket 5018.
14638 - The bridge directory authority now assigns status flags (Stable,
14639 Guard, etc) to bridges based on thresholds calculated over all
14640 Running bridges. Now bridgedb can finally make use of its features
14641 to e.g. include at least one Stable bridge in its answers. Fixes
14644 o Major features (other):
14645 - Extend ORCONN controller event to include an "ID" parameter,
14646 and add four new controller event types CONN_BW, CIRC_BW,
14647 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
14648 The new events are emitted in private Tor networks only, with the
14649 goal of being able to better track performance and load during
14650 full-network simulations. Implements proposal 218 and ticket 7359.
14651 - On some platforms (currently: recent OSX versions, glibc-based
14652 platforms that support the ELF format, and a few other
14653 Unix-like operating systems), Tor can now dump stack traces
14654 when a crash occurs or an assertion fails. By default, traces
14655 are dumped to stderr (if possible) and to any logs that are
14656 reporting errors. Implements ticket 9299.
14659 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
14660 not entirely remove it from the connection lists. Fixes bug 9602;
14661 bugfix on 0.2.4.4-alpha.
14662 - Do not treat streams that fail with reason
14663 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
14664 since it could also indicate an ENETUNREACH connection error. Fixes
14665 part of bug 10777; bugfix on 0.2.4.8-alpha.
14667 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
14668 - Do not allow OpenSSL engines to replace the PRNG, even when
14669 HardwareAccel is set. The only default builtin PRNG engine uses
14670 the Intel RDRAND instruction to replace the entire PRNG, and
14671 ignores all attempts to seed it with more entropy. That's
14672 cryptographically stupid: the right response to a new alleged
14673 entropy source is never to discard all previously used entropy
14674 sources. Fixes bug 10402; works around behavior introduced in
14675 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
14677 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
14678 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
14679 - Avoid launching spurious extra circuits when a stream is pending.
14680 This fixes a bug where any circuit that _wasn't_ unusable for new
14681 streams would be treated as if it were, causing extra circuits to
14682 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
14684 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14685 - No longer stop reading or writing on cpuworker connections when
14686 our rate limiting buckets go empty. Now we should handle circuit
14687 handshake requests more promptly. Resolves bug 9731.
14688 - Stop trying to bootstrap all our directory information from
14689 only our first guard. Discovered while fixing bug 9946; bugfix
14692 o Minor features (bridges, pluggable transports):
14693 - Add threshold cutoffs to the networkstatus document created by
14694 the Bridge Authority. Fixes bug 1117.
14695 - On Windows, spawn background processes using the CREATE_NO_WINDOW
14696 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
14697 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
14698 Vidalia set this option for us.) Implements ticket 10297.
14700 o Minor features (security):
14701 - Always clear OpenSSL bignums before freeing them -- even bignums
14702 that don't contain secrets. Resolves ticket 10793. Patch by
14705 o Minor features (config options and command line):
14706 - Add an --allow-missing-torrc commandline option that tells Tor to
14707 run even if the configuration file specified by -f is not available.
14708 Implements ticket 10060.
14709 - Add support for the TPROXY transparent proxying facility on Linux.
14710 See documentation for the new TransProxyType option for more
14711 details. Implementation by "thomo". Closes ticket 10582.
14713 o Minor features (controller):
14714 - Add a new "HS_DESC" controller event that reports activities
14715 related to hidden service descriptors. Resolves ticket 8510.
14716 - New "DROPGUARDS" controller command to forget all current entry
14717 guards. Not recommended for ordinary use, since replacing guards
14718 too frequently makes several attacks easier. Resolves ticket 9934;
14721 o Minor features (build):
14722 - Assume that a user using ./configure --host wants to cross-compile,
14723 and give an error if we cannot find a properly named
14724 tool-chain. Add a --disable-tool-name-check option to proceed
14725 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
14726 - If we run ./configure and the compiler recognizes -fstack-protector
14727 but the linker rejects it, warn the user about a potentially missing
14728 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
14730 o Minor features (testing):
14731 - If Python is installed, "make check" now runs extra tests beyond
14732 the unit test scripts.
14733 - When bootstrapping a test network, sometimes very few relays get
14734 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
14735 specify a set of relays which should be voted Guard regardless of
14736 their uptime or bandwidth. Addresses ticket 9206.
14738 o Minor features (log messages):
14739 - When ServerTransportPlugin is set on a bridge, Tor can write more
14740 useful statistics about bridge use in its extrainfo descriptors,
14741 but only if the Extended ORPort ("ExtORPort") is set too. Add a
14742 log message to inform the user in this case. Resolves ticket 9651.
14743 - When receiving a new controller connection, log the origin address.
14744 Resolves ticket 9698; patch from "sigpipe".
14745 - When logging OpenSSL engine status at startup, log the status of
14746 more engines. Fixes ticket 10043; patch from Joshua Datko.
14747 - Turn "circuit handshake stats since last time" log messages into a
14748 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
14750 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14751 - Improve the circuit queue out-of-memory handler. Previously, when
14752 we ran low on memory, we'd close whichever circuits had the most
14753 queued cells. Now, we close those that have the *oldest* queued
14754 cells, on the theory that those are most responsible for us
14755 running low on memory. Based on analysis from a forthcoming paper
14756 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
14757 - Generate bootstrapping status update events correctly when fetching
14758 microdescriptors. Fixes bug 9927.
14759 - Update to the October 2 2013 Maxmind GeoLite Country database.
14761 o Minor bugfixes (clients):
14762 - When closing a channel that has already been open, do not close
14763 pending circuits that were waiting to connect to the same relay.
14764 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
14767 o Minor bugfixes (relays):
14768 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
14769 exit node as a NOROUTE error, not an INTERNAL error, since they
14770 can apparently happen when trying to connect to the wrong sort
14771 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
14773 o Minor bugfixes (bridges):
14774 - Fix a bug where the first connection works to a bridge that uses a
14775 pluggable transport with client-side parameters, but we don't send
14776 the client-side parameters on subsequent connections. (We don't
14777 use any pluggable transports with client-side parameters yet,
14778 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
14779 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
14781 o Minor bugfixes (node selection):
14782 - If ExcludeNodes is set, consider non-excluded hidden service
14783 directory servers before excluded ones. Do not consider excluded
14784 hidden service directory servers at all if StrictNodes is
14785 set. (Previously, we would sometimes decide to connect to those
14786 servers, and then realize before we initiated a connection that
14787 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
14788 Reported by "mr-4".
14789 - If we set the ExitNodes option but it doesn't include any nodes
14790 that have the Exit flag, we would choose not to bootstrap. Now we
14791 bootstrap so long as ExitNodes includes nodes which can exit to
14792 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
14794 o Minor bugfixes (controller and command-line):
14795 - If changing a config option via "setconf" fails in a recoverable
14796 way, we used to nonetheless write our new control ports to the
14797 file described by the "ControlPortWriteToFile" option. Now we only
14798 write out that file if we successfully switch to the new config
14799 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
14800 - When a command-line option such as --version or --help that
14801 ordinarily implies --hush appears on the command line along with
14802 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
14803 only if it appeared later on the command line. Fixes bug 9578;
14804 bugfix on 0.2.5.1-alpha.
14806 o Minor bugfixes (code correctness):
14807 - Previously we used two temporary files when writing descriptors to
14808 disk; now we only use one. Fixes bug 1376.
14809 - Remove an erroneous (but impossible and thus harmless) pointer
14810 comparison that would have allowed compilers to skip a bounds
14811 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
14812 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
14813 - Fix an always-true assertion in pluggable transports code so it
14814 actually checks what it was trying to check. Fixes bug 10046;
14815 bugfix on 0.2.3.9-alpha. Found by "dcb".
14817 o Minor bugfixes (protocol correctness):
14818 - When receiving a VERSIONS cell with an odd number of bytes, close
14819 the connection immediately since the cell is malformed. Fixes bug
14820 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
14823 o Minor bugfixes (build):
14824 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
14825 turned off (that is, without support for v2 link handshakes). Fixes
14826 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
14827 - Fix compilation warnings and startup issues when running with
14828 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
14830 - Fix compilation on Solaris 9, which didn't like us having an
14831 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
14833 o Minor bugfixes (testing):
14834 - Fix a segmentation fault in our benchmark code when running with
14835 Fedora's OpenSSL package, or any other OpenSSL that provides
14836 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
14838 o Minor bugfixes (log messages):
14839 - Fix a bug where clients using bridges would report themselves
14840 as 50% bootstrapped even without a live consensus document.
14841 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
14842 - Suppress a warning where, if there's only one directory authority
14843 in the network, we would complain that votes and signatures cannot
14844 be uploaded to other directory authorities. Fixes bug 10842;
14845 bugfix on 0.2.2.26-beta.
14846 - Report bootstrapping progress correctly when we're downloading
14847 microdescriptors. We had updated our "do we have enough microdescs
14848 to begin building circuits?" logic most recently in 0.2.4.10-alpha
14849 (see bug 5956), but we left the bootstrap status event logic at
14850 "how far through getting 1/4 of them are we?" Fixes bug 9958;
14851 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
14853 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
14854 - Avoid a crash bug when starting with a corrupted microdescriptor
14855 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
14856 - If we fail to dump a previously cached microdescriptor to disk, avoid
14857 freeing duplicate data later on. Fixes bug 10423; bugfix on
14858 0.2.4.13-alpha. Spotted by "bobnomnom".
14860 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14861 - Correctly log long IPv6 exit policies, instead of truncating them
14862 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
14863 - Our default TLS ecdhe groups were backwards: we meant to be using
14864 P224 for relays (for performance win) and P256 for bridges (since
14865 it is more common in the wild). Instead we had it backwards. After
14866 reconsideration, we decided that the default should be P256 on all
14867 hosts, since its security is probably better, and since P224 is
14868 reportedly used quite little in the wild. Found by "skruffy" on
14869 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
14870 - Free directory authority certificate download statuses on exit
14871 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
14873 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14874 - If the guard we choose first doesn't answer, we would try the
14875 second guard, but once we connected to the second guard we would
14876 abandon it and retry the first one, slowing down bootstrapping.
14877 The fix is to treat all our initially chosen guards as acceptable
14878 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
14879 - Fix an assertion failure that would occur when disabling the
14880 ORPort setting on a running Tor process while accounting was
14881 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
14882 - When examining the list of network interfaces to find our address,
14883 do not consider non-running or disabled network interfaces. Fixes
14884 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
14885 - Avoid an off-by-one error when checking buffer boundaries when
14886 formatting the exit status of a pluggable transport helper.
14887 This is probably not an exploitable bug, but better safe than
14888 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
14891 o Removed code and features:
14892 - Clients now reject any directory authority certificates lacking
14893 a dir-key-crosscert element. These have been included since
14894 0.2.1.9-alpha, so there's no real reason for them to be optional
14895 any longer. Completes proposal 157. Resolves ticket 10162.
14896 - Remove all code that existed to support the v2 directory system,
14897 since there are no longer any v2 directory authorities. Resolves
14899 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
14900 options, which were used for designating authorities as "Hidden
14901 service authorities". There has been no use of hidden service
14902 authorities since 0.2.2.1-alpha, when we stopped uploading or
14903 downloading v0 hidden service descriptors. Fixes bug 10881; also
14904 part of a fix for bug 10841.
14906 o Code simplification and refactoring:
14907 - Remove some old fallback code designed to keep Tor clients working
14908 in a network with only two working relays. Elsewhere in the code we
14909 have long since stopped supporting such networks, so there wasn't
14910 much point in keeping it around. Addresses ticket 9926.
14911 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
14912 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
14913 - Remove data structures which were introduced to implement the
14914 CellStatistics option: they are now redundant with the addition
14915 of a timestamp to the regular packed_cell_t data structure, which
14916 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
14919 o Documentation (man page) fixes:
14920 - Update manpage to describe some of the files you can expect to
14921 find in Tor's DataDirectory. Addresses ticket 9839.
14922 - Document that all but one DirPort entry must have the NoAdvertise
14923 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
14925 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14926 - Clarify the usage and risks of setting the ContactInfo torrc line
14927 for your relay or bridge. Resolves ticket 9854.
14928 - Add anchors to the manpage so we can link to the html version of
14929 the documentation for specific options. Resolves ticket 9866.
14930 - Replace remaining references to DirServer in man page and
14931 log entries. Resolves ticket 10124.
14934 - Make the "tor-gencert" tool used by directory authority operators
14935 create 2048-bit signing keys by default (rather than 1024-bit, since
14936 1024-bit is uncomfortably small these days). Addresses ticket 10324.
14939 Changes in version 0.2.4.20 - 2013-12-22
14940 Tor 0.2.4.20 fixes potentially poor random number generation for users
14941 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
14942 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
14943 and 4) have no state file in their DataDirectory (as would happen on
14944 first start). Users who generated relay or hidden service identity
14945 keys in such a situation should discard them and generate new ones.
14947 This release also fixes a logic error that caused Tor clients to build
14948 many more preemptive circuits than they actually need.
14951 - Do not allow OpenSSL engines to replace the PRNG, even when
14952 HardwareAccel is set. The only default builtin PRNG engine uses
14953 the Intel RDRAND instruction to replace the entire PRNG, and
14954 ignores all attempts to seed it with more entropy. That's
14955 cryptographically stupid: the right response to a new alleged
14956 entropy source is never to discard all previously used entropy
14957 sources. Fixes bug 10402; works around behavior introduced in
14958 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
14960 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
14961 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
14962 - Avoid launching spurious extra circuits when a stream is pending.
14963 This fixes a bug where any circuit that _wasn't_ unusable for new
14964 streams would be treated as if it were, causing extra circuits to
14965 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
14968 - Avoid a crash bug when starting with a corrupted microdescriptor
14969 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
14970 - If we fail to dump a previously cached microdescriptor to disk, avoid
14971 freeing duplicate data later on. Fixes bug 10423; bugfix on
14972 0.2.4.13-alpha. Spotted by "bobnomnom".
14975 Changes in version 0.2.4.19 - 2013-12-11
14976 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
14977 (1986-2013). Aaron worked on diverse projects including helping to guide
14978 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
14979 transparency to the U.S government's PACER documents, and contributing
14980 design and development for Tor and Tor2Web. Aaron was one of the latest
14981 martyrs in our collective fight for civil liberties and human rights,
14982 and his death is all the more painful because he was one of us.
14984 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
14985 a new circuit handshake and link encryption that use ECC to provide
14986 better security and efficiency; makes relays better manage circuit
14987 creation requests; uses "directory guards" to reduce client enumeration
14988 risks; makes bridges collect and report statistics about the pluggable
14989 transports they support; cleans up and improves our geoip database;
14990 gets much closer to IPv6 support for clients, bridges, and relays; makes
14991 directory authorities use measured bandwidths rather than advertised
14992 ones when computing flags and thresholds; disables client-side DNS
14993 caching to reduce tracking risks; and fixes a big bug in bridge
14994 reachability testing. This release introduces two new design
14995 abstractions in the code: a new "channel" abstraction between circuits
14996 and or_connections to allow for implementing alternate relay-to-relay
14997 transports, and a new "circuitmux" abstraction storing the queue of
14998 circuits for a channel. The release also includes many stability,
14999 security, and privacy fixes.
15002 Changes in version 0.2.4.18-rc - 2013-11-16
15003 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
15004 series. It takes a variety of fixes from the 0.2.5.x branch to improve
15005 stability, performance, and better handling of edge cases.
15008 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
15009 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
15010 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
15011 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
15012 them to solve bug 6033.)
15015 - No longer stop reading or writing on cpuworker connections when
15016 our rate limiting buckets go empty. Now we should handle circuit
15017 handshake requests more promptly. Resolves bug 9731.
15018 - If we are unable to save a microdescriptor to the journal, do not
15019 drop it from memory and then reattempt downloading it. Fixes bug
15020 9645; bugfix on 0.2.2.6-alpha.
15021 - Stop trying to bootstrap all our directory information from
15022 only our first guard. Discovered while fixing bug 9946; bugfix
15024 - The new channel code sometimes lost track of in-progress circuits,
15025 causing long-running clients to stop building new circuits. The
15026 fix is to always call circuit_n_chan_done(chan, 0) from
15027 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
15029 o Minor bugfixes (on 0.2.4.x):
15030 - Correctly log long IPv6 exit policies, instead of truncating them
15031 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
15032 - Our default TLS ecdhe groups were backwards: we meant to be using
15033 P224 for relays (for performance win) and P256 for bridges (since
15034 it is more common in the wild). Instead we had it backwards. After
15035 reconsideration, we decided that the default should be P256 on all
15036 hosts, since its security is probably better, and since P224 is
15037 reportedly used quite little in the wild. Found by "skruffy" on
15038 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
15039 - Free directory authority certificate download statuses on exit
15040 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
15042 o Minor bugfixes (on 0.2.3.x and earlier):
15043 - If the guard we choose first doesn't answer, we would try the
15044 second guard, but once we connected to the second guard we would
15045 abandon it and retry the first one, slowing down bootstrapping.
15046 The fix is to treat all our initially chosen guards as acceptable
15047 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
15048 - Fix an assertion failure that would occur when disabling the
15049 ORPort setting on a running Tor process while accounting was
15050 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
15051 - When examining the list of network interfaces to find our address,
15052 do not consider non-running or disabled network interfaces. Fixes
15053 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
15054 - Avoid an off-by-one error when checking buffer boundaries when
15055 formatting the exit status of a pluggable transport helper.
15056 This is probably not an exploitable bug, but better safe than
15057 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
15060 o Minor features (protecting client timestamps):
15061 - Clients no longer send timestamps in their NETINFO cells. These were
15062 not used for anything, and they provided one small way for clients
15063 to be distinguished from each other as they moved from network to
15064 network or behind NAT. Implements part of proposal 222.
15065 - Clients now round timestamps in INTRODUCE cells down to the nearest
15066 10 minutes. If a new Support022HiddenServices option is set to 0, or
15067 if it's set to "auto" and the feature is disabled in the consensus,
15068 the timestamp is sent as 0 instead. Implements part of proposal 222.
15069 - Stop sending timestamps in AUTHENTICATE cells. This is not such
15070 a big deal from a security point of view, but it achieves no actual
15071 good purpose, and isn't needed. Implements part of proposal 222.
15072 - Reduce down accuracy of timestamps in hidden service descriptors.
15073 Implements part of proposal 222.
15075 o Minor features (other):
15076 - Improve the circuit queue out-of-memory handler. Previously, when
15077 we ran low on memory, we'd close whichever circuits had the most
15078 queued cells. Now, we close those that have the *oldest* queued
15079 cells, on the theory that those are most responsible for us
15080 running low on memory. Based on analysis from a forthcoming paper
15081 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
15082 - Generate bootstrapping status update events correctly when fetching
15083 microdescriptors. Fixes bug 9927.
15084 - Update to the October 2 2013 Maxmind GeoLite Country database.
15086 o Documentation fixes:
15087 - Clarify the usage and risks of setting the ContactInfo torrc line
15088 for your relay or bridge. Resolves ticket 9854.
15089 - Add anchors to the manpage so we can link to the html version of
15090 the documentation for specific options. Resolves ticket 9866.
15091 - Replace remaining references to DirServer in man page and
15092 log entries. Resolves ticket 10124.
15095 Changes in version 0.2.5.1-alpha - 2013-10-02
15096 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
15097 on Linux, allows bridges that offer pluggable transports to report usage
15098 statistics, fixes many issues to make testing easier, and provides
15099 a pile of minor features and bugfixes that have been waiting for a
15100 release of the new branch.
15102 This is the first alpha release in a new series, so expect there to
15103 be bugs. Users who would rather test out a more stable branch should
15104 stay with 0.2.4.x for now.
15106 o Major features (security):
15107 - Use the seccomp2 syscall filtering facility on Linux to limit
15108 which system calls Tor can invoke. This is an experimental,
15109 Linux-only feature to provide defense-in-depth against unknown
15110 attacks. To try turning it on, set "Sandbox 1" in your torrc
15111 file. Please be ready to report bugs. We hope to add support
15112 for better sandboxing in the future, including more fine-grained
15113 filters, better division of responsibility, and support for more
15114 platforms. This work has been done by Cristian-Matei Toader for
15115 Google Summer of Code.
15116 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
15117 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
15118 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
15119 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
15120 them to solve bug 6033.)
15122 o Major features (other):
15123 - Add support for passing arguments to managed pluggable transport
15124 proxies. Implements ticket 3594.
15125 - Bridges now track GeoIP information and the number of their users
15126 even when pluggable transports are in use, and report usage
15127 statistics in their extra-info descriptors. Resolves tickets 4773
15129 - Make testing Tor networks bootstrap better: lower directory fetch
15130 retry schedules and maximum interval without directory requests,
15131 and raise maximum download tries. Implements ticket 6752.
15132 - Add make target 'test-network' to run tests on a Chutney network.
15133 Implements ticket 8530.
15134 - The ntor handshake is now on-by-default, no matter what the
15135 directory authorities recommend. Implements ticket 8561.
15138 - Instead of writing destroy cells directly to outgoing connection
15139 buffers, queue them and intersperse them with other outgoing cells.
15140 This can prevent a set of resource starvation conditions where too
15141 many pending destroy cells prevent data cells from actually getting
15142 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
15143 bugfix on 0.2.0.1-alpha.
15144 - If we are unable to save a microdescriptor to the journal, do not
15145 drop it from memory and then reattempt downloading it. Fixes bug
15146 9645; bugfix on 0.2.2.6-alpha.
15147 - The new channel code sometimes lost track of in-progress circuits,
15148 causing long-running clients to stop building new circuits. The
15149 fix is to always call circuit_n_chan_done(chan, 0) from
15150 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
15153 - Tor now builds each source file in two modes: a mode that avoids
15154 exposing identifiers needlessly, and another mode that exposes
15155 more identifiers for testing. This lets the compiler do better at
15156 optimizing the production code, while enabling us to take more
15157 radical measures to let the unit tests test things.
15158 - The production builds no longer include functions used only in
15159 the unit tests; all functions exposed from a module only for
15160 unit-testing are now static in production builds.
15161 - Add an --enable-coverage configuration option to make the unit
15162 tests (and a new src/or/tor-cov target) to build with gcov test
15166 - We now have rudimentary function mocking support that our unit
15167 tests can use to test functions in isolation. Function mocking
15168 lets the tests temporarily replace a function's dependencies with
15169 stub functions, so that the tests can check the function without
15170 invoking the other functions it calls.
15171 - Add more unit tests for the <circid,channel>->circuit map, and
15172 the destroy-cell-tracking code to fix bug 7912.
15173 - Unit tests for failing cases of the TAP onion handshake.
15174 - More unit tests for address-manipulation functions.
15176 o Minor features (protecting client timestamps):
15177 - Clients no longer send timestamps in their NETINFO cells. These were
15178 not used for anything, and they provided one small way for clients
15179 to be distinguished from each other as they moved from network to
15180 network or behind NAT. Implements part of proposal 222.
15181 - Clients now round timestamps in INTRODUCE cells down to the nearest
15182 10 minutes. If a new Support022HiddenServices option is set to 0, or
15183 if it's set to "auto" and the feature is disabled in the consensus,
15184 the timestamp is sent as 0 instead. Implements part of proposal 222.
15185 - Stop sending timestamps in AUTHENTICATE cells. This is not such
15186 a big deal from a security point of view, but it achieves no actual
15187 good purpose, and isn't needed. Implements part of proposal 222.
15188 - Reduce down accuracy of timestamps in hidden service descriptors.
15189 Implements part of proposal 222.
15191 o Minor features (config options):
15192 - Config (torrc) lines now handle fingerprints which are missing
15193 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
15194 - Support a --dump-config option to print some or all of the
15195 configured options. Mainly useful for debugging the command-line
15196 option parsing code. Helps resolve ticket 4647.
15197 - Raise awareness of safer logging: notify user of potentially
15198 unsafe config options, like logging more verbosely than severity
15199 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
15200 - Add a new configuration option TestingV3AuthVotingStartOffset
15201 that bootstraps a network faster by changing the timing for
15202 consensus votes. Addresses ticket 8532.
15203 - Add a new torrc option "ServerTransportOptions" that allows
15204 bridge operators to pass configuration parameters to their
15205 pluggable transports. Resolves ticket 8929.
15206 - The config (torrc) file now accepts bandwidth and space limits in
15207 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
15208 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
15211 o Minor features (build):
15212 - Add support for `--library-versions` flag. Implements ticket 6384.
15213 - Return the "unexpected sendme" warnings to a warn severity, but make
15214 them rate limited, to help diagnose ticket 8093.
15215 - Detect a missing asciidoc, and warn the user about it, during
15216 configure rather than at build time. Fixes issue 6506. Patch from
15219 o Minor features (other):
15220 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
15221 sockets in a single system call. Implements ticket 5129.
15222 - Log current accounting state (bytes sent and received + remaining
15223 time for the current accounting period) in the relay's heartbeat
15224 message. Implements ticket 5526; patch from Peter Retzlaff.
15225 - Implement the TRANSPORT_LAUNCHED control port event that
15226 notifies controllers about new launched pluggable
15227 transports. Resolves ticket 5609.
15228 - If we're using the pure-C 32-bit curve25519_donna implementation
15229 of curve25519, build it with the -fomit-frame-pointer option to
15230 make it go faster on register-starved hosts. This improves our
15231 handshake performance by about 6% on i386 hosts without nacl.
15232 Closes ticket 8109.
15233 - Update to the September 4 2013 Maxmind GeoLite Country database.
15236 - Set the listen() backlog limit to the largest actually supported
15237 on the system, not to the value in a header file. Fixes bug 9716;
15238 bugfix on every released Tor.
15239 - No longer accept malformed http headers when parsing urls from
15240 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
15241 bugfix on 0.0.6pre1.
15242 - In munge_extrainfo_into_routerinfo(), check the return value of
15243 memchr(). This would have been a serious issue if we ever passed
15244 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
15246 - On the chance that somebody manages to build Tor on a
15247 platform where time_t is unsigned, correct the way that
15248 microdesc_add_to_cache() handles negative time arguments.
15249 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
15250 - Reject relative control socket paths and emit a warning. Previously,
15251 single-component control socket paths would be rejected, but Tor
15252 would not log why it could not validate the config. Fixes bug 9258;
15253 bugfix on 0.2.3.16-alpha.
15255 o Minor bugfixes (command line):
15256 - Use a single command-line parser for parsing torrc options on the
15257 command line and for finding special command-line options to avoid
15258 inconsistent behavior for torrc option arguments that have the same
15259 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
15261 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
15262 9573; bugfix on 0.0.9pre5.
15264 o Minor fixes (build, auxiliary programs):
15265 - Stop preprocessing the "torify" script with autoconf, since
15266 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
15268 - The tor-fw-helper program now follows the standard convention and
15269 exits with status code "0" on success. Fixes bug 9030; bugfix on
15270 0.2.3.1-alpha. Patch by Arlo Breault.
15271 - Corrected ./configure advice for what openssl dev package you should
15272 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
15274 o Minor code improvements:
15275 - Remove constants and tests for PKCS1 padding; it's insecure and
15276 shouldn't be used for anything new. Fixes bug 8792; patch
15278 - Remove instances of strcpy() from the unit tests. They weren't
15279 hurting anything, since they were only in the unit tests, but it's
15280 embarrassing to have strcpy() in the code at all, and some analysis
15281 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
15282 0.2.3.8-alpha. Patch from Arlo Breault.
15284 o Removed features:
15285 - Remove migration code from when we renamed the "cached-routers"
15286 file to "cached-descriptors" back in 0.2.0.8-alpha. This
15287 incidentally resolves ticket 6502 by cleaning up the related code
15288 a bit. Patch from Akshay Hebbar.
15290 o Code simplification and refactoring:
15291 - Extract the common duplicated code for creating a subdirectory
15292 of the data directory and writing to a file in it. Fixes ticket
15293 4282; patch from Peter Retzlaff.
15294 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
15295 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
15296 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
15297 - Add a set of accessor functions for the circuit timeout data
15298 structure. Fixes ticket 6153; patch from "piet".
15299 - Clean up exit paths from connection_listener_new(). Closes ticket
15300 8789. Patch from Arlo Breault.
15301 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
15302 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
15303 - Use a doubly-linked list to implement the global circuit list.
15304 Resolves ticket 9108. Patch from Marek Majkowski.
15305 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
15308 Changes in version 0.2.4.17-rc - 2013-09-05
15309 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
15310 series. It adds an emergency step to help us tolerate the massive
15311 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
15312 circuit-level handshakes now effectively jump the queue compared to
15313 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
15314 big bug hindering bridge reachability tests.
15317 - Relays now process the new "NTor" circuit-level handshake requests
15318 with higher priority than the old "TAP" circuit-level handshake
15319 requests. We still process some TAP requests to not totally starve
15320 0.2.3 clients when NTor becomes popular. A new consensus parameter
15321 "NumNTorsPerTAP" lets us tune the balance later if we need to.
15322 Implements ticket 9574.
15325 - If the circuit build timeout logic is disabled (via the consensus,
15326 or because we are an authority), then don't build testing circuits.
15327 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
15328 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
15329 previously they did not, which prevented them from receiving
15330 successful connections from relays for self-test or bandwidth
15331 testing. Also, when a relay is extending a circuit to a bridge,
15332 it needs to send a NETINFO cell, even when the bridge hasn't sent
15333 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
15334 - If the time to download the next old-style networkstatus is in
15335 the future, do not decline to consider whether to download the
15336 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
15340 - Avoid double-closing the listener socket in our socketpair()
15341 replacement (used on Windows) in the case where the addresses on
15342 our opened sockets don't match what we expected. Fixes bug 9400;
15343 bugfix on 0.0.2pre7. Found by Coverity.
15345 o Minor fixes (config options):
15346 - Avoid overflows when the user sets MaxCircuitDirtiness to a
15347 ridiculously high value, by imposing a (ridiculously high) 30-day
15348 maximum on MaxCircuitDirtiness.
15349 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
15350 message is logged at notice, not at info.
15351 - Warn and fail if a server is configured not to advertise any
15352 ORPorts at all. (We need *something* to put in our descriptor,
15353 or we just won't work.)
15356 - Track how many "TAP" and "NTor" circuit handshake requests we get,
15357 and how many we complete, and log it every hour to help relay
15358 operators follow trends in network load. Addresses ticket 9658.
15359 - Update to the August 7 2013 Maxmind GeoLite Country database.
15362 Changes in version 0.2.4.16-rc - 2013-08-10
15363 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
15364 series. It fixes several crash bugs in the 0.2.4 branch.
15367 - Fix a bug in the voting algorithm that could yield incorrect results
15368 when a non-naming authority declared too many flags. Fixes bug 9200;
15369 bugfix on 0.2.0.3-alpha.
15370 - Fix an uninitialized read that could in some cases lead to a remote
15371 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
15372 Anybody running a hidden service on the experimental 0.2.4.x
15373 branch should upgrade. (This is, so far as we know, unrelated to
15375 - Avoid an assertion failure when processing DNS replies without the
15376 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
15377 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
15378 0.2.4.15-rc. Found by stem integration tests.
15381 - Fix an invalid memory read that occurred when a pluggable
15382 transport proxy failed its configuration protocol.
15383 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
15384 - When evaluating whether to use a connection that we haven't
15385 decided is canonical using a recent link protocol version,
15386 decide that it's canonical only if it used address _does_
15387 match the desired address. Fixes bug 9309; bugfix on
15388 0.2.4.4-alpha. Reported by skruffy.
15389 - Make the default behavior of NumDirectoryGuards be to track
15390 NumEntryGuards. Now a user who changes only NumEntryGuards will get
15391 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
15392 - Fix a spurious compilation warning with some older versions of
15393 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
15396 - Update to the July 3 2013 Maxmind GeoLite Country database.
15399 Changes in version 0.2.4.15-rc - 2013-07-01
15400 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
15401 series. It fixes a few smaller bugs, but generally appears stable.
15402 Please test it and let us know whether it is!
15405 - When receiving a new configuration file via the control port's
15406 LOADCONF command, do not treat the defaults file as absent.
15407 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
15410 - Issue a warning when running with the bufferevents backend enabled.
15411 It's still not stable, and people should know that they're likely
15412 to hit unexpected problems. Closes ticket 9147.
15415 Changes in version 0.2.4.14-alpha - 2013-06-18
15416 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
15417 present in 0.2.4.13-alpha.
15420 - When we have too much memory queued in circuits (according to a new
15421 MaxMemInCellQueues option), close the circuits consuming the most
15422 memory. This prevents us from running out of memory as a relay if
15423 circuits fill up faster than they can be drained. Fixes bug 9063;
15424 bugfix on the 54th commit of Tor. This bug is a further fix beyond
15425 bug 6252, whose fix was merged into 0.2.3.21-rc.
15427 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
15428 where we tried to solve this issue simply by imposing an upper limit
15429 on the number of queued cells for a single circuit. That approach
15430 proved to be problematic, since there are ways to provoke clients to
15431 send a number of cells in excess of any such reasonable limit. Fixes
15432 bug 9072; bugfix on 0.2.4.13-alpha.
15434 - Limit hidden service descriptors to at most ten introduction
15435 points, to slow one kind of guard enumeration. Fixes bug 9002;
15436 bugfix on 0.1.1.11-alpha.
15439 Changes in version 0.2.4.13-alpha - 2013-06-14
15440 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
15441 vulnerabilities, makes socks5 username/password circuit isolation
15442 actually actually work (this time for sure!), and cleans up a bunch
15443 of other issues in preparation for a release candidate.
15445 o Major bugfixes (robustness):
15446 - Close any circuit that has too many cells queued on it. Fixes
15447 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
15448 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
15449 - Prevent the get_freelists() function from running off the end of
15450 the list of freelists if it somehow gets an unrecognized
15451 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
15453 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
15454 when an exit connection with optimistic data succeeds immediately
15455 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
15457 - Fix a directory authority crash bug when building a consensus
15458 using an older consensus as its basis. Fixes bug 8833. Bugfix
15462 - Avoid a memory leak where we would leak a consensus body when we
15463 find that a consensus which we couldn't previously verify due to
15464 missing certificates is now verifiable. Fixes bug 8719; bugfix
15466 - We used to always request authority certificates by identity digest,
15467 meaning we'd get the newest one even when we wanted one with a
15468 different signing key. Then we would complain about being given
15469 a certificate we already had, and never get the one we really
15470 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
15471 resource to request the one we want. Fixes bug 5595; bugfix on
15473 - Follow the socks5 protocol when offering username/password
15474 authentication. The fix for bug 8117 exposed this bug, and it
15475 turns out real-world applications like Pidgin do care. Bugfix on
15476 0.2.3.2-alpha; fixes bug 8879.
15477 - Prevent failures on Windows Vista and later when rebuilding the
15478 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
15479 bugfix on 0.2.4.12-alpha.
15482 - Fix an impossible buffer overrun in the AES unit tests. Fixes
15483 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
15484 - If for some reason we fail to write a microdescriptor while
15485 rebuilding the cache, do not let the annotations from that
15486 microdescriptor linger in the cache file, and do not let the
15487 microdescriptor stay recorded as present in its old location.
15488 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
15489 - Fix a memory leak that would occur whenever a configuration
15490 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
15491 - Paste the description for PathBias parameters from the man
15492 page into or.h, so the code documents them too. Fixes bug 7982;
15493 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
15494 - Relays now treat a changed IPv6 ORPort as sufficient reason to
15495 publish an updated descriptor. Fixes bug 6026; bugfix on
15497 - When launching a resolve request on behalf of an AF_UNIX control
15498 socket, omit the address field of the new entry connection, used in
15499 subsequent controller events, rather than letting tor_dup_addr()
15500 set it to "<unknown address type>". Fixes bug 8639; bugfix on
15503 o Minor bugfixes (log messages):
15504 - Fix a scaling issue in the path bias accounting code that
15505 resulted in "Bug:" log messages from either
15506 pathbias_scale_close_rates() or pathbias_count_build_success().
15507 This represents a bugfix on a previous bugfix: the original fix
15508 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
15510 - Give a less useless error message when the user asks for an IPv4
15511 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
15515 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
15516 to tolerate bug 8093 for now.
15517 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
15518 in directory authority votes to describe whether they have enough
15519 measured bandwidths to ignore advertised (relay descriptor)
15520 bandwidth claims. Resolves ticket 8711.
15521 - Update to the June 5 2013 Maxmind GeoLite Country database.
15523 o Removed documentation:
15524 - Remove some of the older contents of doc/ as obsolete; move others
15525 to torspec.git. Fixes bug 8965.
15527 o Code simplification and refactoring:
15528 - Avoid using character buffers when constructing most directory
15529 objects: this approach was unwieldy and error-prone. Instead,
15530 build smartlists of strings, and concatenate them when done.
15533 Changes in version 0.2.4.12-alpha - 2013-04-18
15534 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
15535 process for lengthening the guard rotation period, makes directory
15536 authority opinions in the consensus a bit less gameable, makes socks5
15537 username/password circuit isolation actually work, and fixes a wide
15538 variety of other issues.
15541 - Raise the default time that a client keeps an entry guard from
15542 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
15543 2012 paper. (We would make it even longer, but we need better client
15544 load balancing first.) Also, make the guard lifetime controllable
15545 via a new GuardLifetime torrc option and a GuardLifetime consensus
15546 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
15547 - Directory authorities now prefer using measured bandwidths to
15548 advertised ones when computing flags and thresholds. Resolves
15550 - Directory authorities that have more than a threshold number
15551 of relays with measured bandwidths now treat relays with unmeasured
15552 bandwidths as having bandwidth 0. Resolves ticket 8435.
15554 o Major bugfixes (assert / resource use):
15555 - Avoid a bug where our response to TLS renegotiation under certain
15556 network conditions could lead to a busy-loop, with 100% CPU
15557 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
15558 - Avoid an assertion when we discover that we'd like to write a cell
15559 onto a closing connection: just discard the cell. Fixes another
15560 case of bug 7350; bugfix on 0.2.4.4-alpha.
15562 o Major bugfixes (client-side privacy):
15563 - When we mark a circuit as unusable for new circuits, have it
15564 continue to be unusable for new circuits even if MaxCircuitDirtiness
15565 is increased too much at the wrong time, or the system clock jumps
15566 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
15567 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
15568 which have resolved to internal addresses") is set, apply that
15569 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
15570 - When an exit relay rejects a stream with reason "exit policy", but
15571 we only know an exit policy summary (e.g. from the microdesc
15572 consensus) for it, do not mark the relay as useless for all exiting.
15573 Instead, mark just the circuit as unsuitable for that particular
15574 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
15575 - Allow applications to get proper stream isolation with
15576 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
15577 username/password authentication also offer "no authentication". Tor
15578 had previously preferred "no authentication", so the applications
15579 never actually sent Tor their auth details. Now Tor selects
15580 username/password authentication if it's offered. You can disable
15581 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
15582 bug 8117; bugfix on 0.2.3.3-alpha.
15584 o Major bugfixes (other):
15585 - When unable to find any working directory nodes to use as a
15586 directory guard, give up rather than adding the same non-working
15587 nodes to the directory guard list over and over. Fixes bug 8231;
15588 bugfix on 0.2.4.8-alpha.
15591 - Reject as invalid most directory objects containing a NUL.
15592 Belt-and-suspender fix for bug 8037.
15593 - In our testsuite, create temporary directories with a bit more
15594 entropy in their name to make name collisions less likely. Fixes
15596 - Add CACHED keyword to ADDRMAP events in the control protocol
15597 to indicate whether a DNS result will be cached or not. Resolves
15599 - Update to the April 3 2013 Maxmind GeoLite Country database.
15601 o Minor features (build):
15602 - Detect and reject attempts to build Tor with threading support
15603 when OpenSSL has been compiled without threading support.
15605 - Clarify that when autoconf is checking for nacl, it is checking
15606 specifically for nacl with a fast curve25519 implementation.
15608 - Warn if building on a platform with an unsigned time_t: there
15609 are too many places where Tor currently assumes that time_t can
15610 hold negative values. We'd like to fix them all, but probably
15613 o Minor bugfixes (build):
15614 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
15615 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
15616 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
15617 - Add the old src/or/micro-revision.i filename to CLEANFILES.
15618 On the off chance that somebody has one, it will go away as soon
15619 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
15620 - Build Tor correctly on 32-bit platforms where the compiler can build
15621 but not run code using the "uint128_t" construction. Fixes bug 8587;
15622 bugfix on 0.2.4.8-alpha.
15623 - Fix compilation warning with some versions of clang that would
15624 prefer the -Wswitch-enum compiler flag to warn about switch
15625 statements with missing enum values, even if those switch
15626 statements have a "default:" statement. Fixes bug 8598; bugfix
15629 o Minor bugfixes (protocol):
15630 - Fix the handling of a TRUNCATE cell when it arrives while the
15631 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
15632 - Fix a misframing issue when reading the version numbers in a
15633 VERSIONS cell. Previously we would recognize [00 01 00 02] as
15634 'version 1, version 2, and version 0x100', when it should have
15635 only included versions 1 and 2. Fixes bug 8059; bugfix on
15636 0.2.0.10-alpha. Reported pseudonymously.
15637 - Make the format and order of STREAM events for DNS lookups
15638 consistent among the various ways to launch DNS lookups. Fixes
15639 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
15640 - Correct our check for which versions of Tor support the EXTEND2
15641 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
15642 later, when support was really added in version 0.2.4.8-alpha.
15643 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
15645 o Minor bugfixes (other):
15646 - Correctly store microdescriptors and extrainfo descriptors with
15647 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
15648 Bug reported by "cypherpunks".
15649 - Increase the width of the field used to remember a connection's
15650 link protocol version to two bytes. Harmless for now, since the
15651 only currently recognized versions are one byte long. Reported
15652 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
15653 - If the state file's path bias counts are invalid (presumably from a
15654 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
15655 additional checks and log messages to the scaling of Path Bias
15656 counts, in case there still are remaining issues with scaling.
15657 Should help resolve bug 8235.
15658 - Eliminate several instances where we use "Nickname=ID" to refer to
15659 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
15660 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
15661 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
15663 o Minor bugfixes (syscalls):
15664 - Always check the return values of functions fcntl() and
15665 setsockopt(). We don't believe these are ever actually failing in
15666 practice, but better safe than sorry. Also, checking these return
15667 values should please analysis tools like Coverity. Patch from
15668 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
15669 - Use direct writes rather than stdio when building microdescriptor
15670 caches, in an attempt to mitigate bug 8031, or at least make it
15673 o Minor bugfixes (config):
15674 - When rejecting a configuration because we were unable to parse a
15675 quoted string, log an actual error message. Fixes bug 7950; bugfix
15677 - Behave correctly when the user disables LearnCircuitBuildTimeout
15678 but doesn't tell us what they would like the timeout to be. Fixes
15679 bug 6304; bugfix on 0.2.2.14-alpha.
15680 - When autodetecting the number of CPUs, use the number of available
15681 CPUs in preference to the number of configured CPUs. Inform the
15682 user if this reduces the number of available CPUs. Fixes bug 8002;
15683 bugfix on 0.2.3.1-alpha.
15684 - Make it an error when you set EntryNodes but disable UseGuardNodes,
15685 since it will (surprisingly to some users) ignore EntryNodes. Fixes
15686 bug 8180; bugfix on 0.2.3.11-alpha.
15687 - Allow TestingTorNetworks to override the 4096-byte minimum for
15688 the Fast threshold. Otherwise they can't bootstrap until they've
15689 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
15690 - Fix some logic errors when the user manually overrides the
15691 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
15694 o Minor bugfixes (log messages to help diagnose bugs):
15695 - If we fail to free a microdescriptor because of bug 7164, log
15696 the filename and line number from which we tried to free it.
15697 - Add another diagnostic to the heartbeat message: track and log
15698 overhead that TLS is adding to the data we write. If this is
15699 high, we are sending too little data to SSL_write at a time.
15700 Diagnostic for bug 7707.
15701 - Add more detail to a log message about relaxed timeouts, to help
15703 - Warn more aggressively when flushing microdescriptors to a
15704 microdescriptor cache fails, in an attempt to mitigate bug 8031,
15705 or at least make it more diagnosable.
15706 - Improve debugging output to help track down bug 8185 ("Bug:
15707 outgoing relay cell has n_chan==NULL. Dropping.")
15708 - Log the purpose of a path-bias testing circuit correctly.
15709 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
15711 o Minor bugfixes (0.2.4.x log messages that were too noisy):
15712 - Don't attempt to relax the timeout of already opened 1-hop circuits.
15713 They might never timeout. This should eliminate some/all cases of
15714 the relaxed timeout log message.
15715 - Use circuit creation time for network liveness evaluation. This
15716 should eliminate warning log messages about liveness caused
15717 by changes in timeout evaluation. Fixes bug 6572; bugfix on
15719 - Reduce a path bias length check from notice to info. The message
15720 is triggered when creating controller circuits. Fixes bug 8196;
15721 bugfix on 0.2.4.8-alpha.
15722 - Fix a path state issue that triggered a notice during relay startup.
15723 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
15724 - Reduce occurrences of warns about circuit purpose in
15725 connection_ap_expire_building(). Fixes bug 8477; bugfix on
15728 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
15729 - If we encounter a write failure on a SOCKS connection before we
15730 finish our SOCKS handshake, don't warn that we closed the
15731 connection before we could send a SOCKS reply. Fixes bug 8427;
15732 bugfix on 0.1.0.1-rc.
15733 - Correctly recognize that [::1] is a loopback address. Fixes
15734 bug 8377; bugfix on 0.2.1.3-alpha.
15735 - Fix a directory authority warn caused when we have a large amount
15736 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
15737 - Don't log inappropriate heartbeat messages when hibernating: a
15738 hibernating node is _expected_ to drop out of the consensus,
15739 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
15740 bugfix on 0.2.3.1-alpha.
15741 - Don't complain about bootstrapping problems while hibernating.
15742 These complaints reflect a general code problem, but not one
15743 with any problematic effects (no connections are actually
15744 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
15746 o Documentation fixes:
15747 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
15748 names match. Fixes bug 7768.
15749 - Make the torify manpage no longer refer to tsocks; torify hasn't
15750 supported tsocks since 0.2.3.14-alpha.
15751 - Make the tor manpage no longer reference tsocks.
15752 - Fix the GeoIPExcludeUnknown documentation to refer to
15753 ExcludeExitNodes rather than the currently nonexistent
15754 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
15757 - The tor-tsocks.conf is no longer distributed or installed. We
15758 recommend that tsocks users use torsocks instead. Resolves
15762 Changes in version 0.2.4.11-alpha - 2013-03-11
15763 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
15764 more robust, makes hidden service authentication work again, and
15765 resolves a DPI fingerprint for Tor's SSL transport.
15767 o Major features (directory authorities):
15768 - Directory authorities now support a new consensus method (17)
15769 where they cap the published bandwidth of servers for which
15770 insufficient bandwidth measurements exist. Fixes part of bug 2286.
15771 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
15772 serve any v2 directory information. Now we can test disabling the
15773 old deprecated v2 directory format, and see whether doing so has
15774 any effect on network load. Begins to fix bug 6783.
15775 - Directory authorities now include inside each vote a statement of
15776 the performance thresholds they used when assigning flags.
15777 Implements ticket 8151.
15779 o Major bugfixes (directory authorities):
15780 - Stop marking every relay as having been down for one hour every
15781 time we restart a directory authority. These artificial downtimes
15782 were messing with our Stable and Guard flag calculations. Fixes
15783 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
15785 o Major bugfixes (hidden services):
15786 - Allow hidden service authentication to succeed again. When we
15787 refactored the hidden service introduction code back
15788 in 0.2.4.1-alpha, we didn't update the code that checks
15789 whether authentication information is present, causing all
15790 authentication checks to return "false". Fix for bug 8207; bugfix
15791 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
15793 o Minor features (relays, bridges):
15794 - Make bridge relays check once a minute for whether their IP
15795 address has changed, rather than only every 15 minutes. Resolves
15796 bugs 1913 and 1992.
15797 - Refactor resolve_my_address() so it returns the method by which we
15798 decided our public IP address (explicitly configured, resolved from
15799 explicit hostname, guessed from interfaces, learned by gethostname).
15800 Now we can provide more helpful log messages when a relay guesses
15801 its IP address incorrectly (e.g. due to unexpected lines in
15802 /etc/hosts). Resolves ticket 2267.
15803 - Teach bridge-using clients to avoid 0.2.2 bridges when making
15804 microdescriptor-related dir requests, and only fall back to normal
15805 descriptors if none of their bridges can handle microdescriptors
15806 (as opposed to the fix in ticket 4013, which caused them to fall
15807 back to normal descriptors if *any* of their bridges preferred
15808 them). Resolves ticket 4994.
15809 - Randomize the lifetime of our SSL link certificate, so censors can't
15810 use the static value for filtering Tor flows. Resolves ticket 8443;
15811 related to ticket 4014 which was included in 0.2.2.33.
15812 - Support a new version of the link protocol that allows 4-byte circuit
15813 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
15814 a possible resource exhaustion issue. Closes ticket 7351; implements
15817 o Minor features (portability):
15818 - Tweak the curve25519-donna*.c implementations to tolerate systems
15819 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
15820 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
15821 the signs of types during autoconf. This is better than our old
15822 approach, which didn't work when cross-compiling.
15823 - Detect the sign of enum values, rather than assuming that MSC is the
15824 only compiler where enum types are all signed. Fixes bug 7727;
15825 bugfix on 0.2.4.10-alpha.
15827 o Minor features (other):
15828 - Say "KBytes" rather than "KB" in the man page (for various values
15829 of K), to further reduce confusion about whether Tor counts in
15830 units of memory or fractions of units of memory. Resolves ticket 7054.
15831 - Clear the high bit on curve25519 public keys before passing them to
15832 our backend, in case we ever wind up using a backend that doesn't do
15833 so itself. If we used such a backend, and *didn't* clear the high bit,
15834 we could wind up in a situation where users with such backends would
15835 be distinguishable from users without. Fixes bug 8121; bugfix on
15837 - Update to the March 6 2013 Maxmind GeoLite Country database.
15839 o Minor bugfixes (clients):
15840 - When we receive a RELAY_END cell with the reason DONE, or with no
15841 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
15842 status as "connection refused". Previously we reported these cases
15843 as success but then immediately closed the connection. Fixes bug
15844 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
15845 - Downgrade an assertion in connection_ap_expire_beginning to an
15846 LD_BUG message. The fix for bug 8024 should prevent this message
15847 from displaying, but just in case, a warn that we can diagnose
15848 is better than more assert crashes. Fixes bug 8065; bugfix on
15850 - Lower path use bias thresholds to .80 for notice and .60 for warn.
15851 Also make the rate limiting flags for the path use bias log messages
15852 independent from the original path bias flags. Fixes bug 8161;
15853 bugfix on 0.2.4.10-alpha.
15855 o Minor bugfixes (relays):
15856 - Stop trying to resolve our hostname so often (e.g. every time we
15857 think about doing a directory fetch). Now we reuse the cached
15858 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
15859 and 2410 (bugfix on 0.1.2.2-alpha).
15860 - Stop sending a stray "(null)" in some cases for the server status
15861 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
15863 - When choosing which stream on a formerly stalled circuit to wake
15864 first, make better use of the platform's weak RNG. Previously,
15865 we had been using the % ("modulo") operator to try to generate a
15866 1/N chance of picking each stream, but this behaves badly with
15867 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
15869 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
15870 Irix's random() only return 15 bits; Solaris's random() returns more
15871 bits but its RAND_MAX says it only returns 15, and so on. Motivated
15872 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
15874 o Minor bugfixes (directory authorities):
15875 - Directory authorities now use less space when formatting identical
15876 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
15879 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
15880 - Avoid leaking memory if we fail to compute a consensus signature
15881 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
15882 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
15884 - Fix a memory leak during safe-cookie controller authentication.
15885 Bugfix on 0.2.3.13-alpha.
15886 - Avoid memory leak of IPv6 policy content if we fail to format it into
15887 a router descriptor. Bugfix on 0.2.4.7-alpha.
15889 o Minor bugfixes (other code correctness issues):
15890 - Avoid a crash if we fail to generate an extrainfo descriptor.
15891 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
15892 this is CID 718634.
15893 - When detecting the largest possible file descriptor (in order to
15894 close all file descriptors when launching a new program), actually
15895 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
15896 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
15898 - Fix a copy-and-paste error when adding a missing A1 to a routerset
15899 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
15900 Bugfix on 0.2.4.10-alpha.
15901 - Fix an impossible-to-trigger integer overflow when estimating how
15902 long our onionskin queue would take. (This overflow would require us
15903 to accept 4 million onionskins before processing 100 of them.) Fixes
15904 bug 8210; bugfix on 0.2.4.10-alpha.
15906 o Code simplification and refactoring:
15907 - Add a wrapper function for the common "log a message with a
15911 Changes in version 0.2.4.10-alpha - 2013-02-04
15912 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
15913 certain attacks that flood the network with relays; changes the queue
15914 for circuit create requests from a sized-based limit to a time-based
15915 limit; resumes building with MSVC on Windows; and fixes a wide variety
15918 o Major bugfixes (directory authority):
15919 - When computing directory thresholds, ignore any rejected-as-sybil
15920 nodes during the computation so that they can't influence Fast,
15921 Guard, etc. (We should have done this for proposal 109.) Fixes
15923 - When marking a node as a likely sybil, reset its uptime metrics
15924 to zero, so that it cannot time towards getting marked as Guard,
15925 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
15929 - When a TLS write is partially successful but incomplete, remember
15930 that the flushed part has been flushed, and notice that bytes were
15931 actually written. Reported and fixed pseudonymously. Fixes bug
15932 7708; bugfix on Tor 0.1.0.5-rc.
15933 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
15934 ID: these could be used to create unexpected streams and circuits
15935 which would count as "present" to some parts of Tor but "absent"
15936 to others, leading to zombie circuits and streams or to a bandwidth
15937 denial-of-service. Fixes bug 7889; bugfix on every released version
15938 of Tor. Reported by "oftc_must_be_destroyed".
15939 - Rename all macros in our local copy of queue.h to begin with "TOR_".
15940 This change seems the only good way to permanently prevent conflicts
15941 with queue.h on various operating systems. Fixes bug 8107; bugfix
15944 o Major features (relay):
15945 - Instead of limiting the number of queued onionskins (aka circuit
15946 create requests) to a fixed, hard-to-configure number, we limit
15947 the size of the queue based on how many we expect to be able to
15948 process in a given amount of time. We estimate the time it will
15949 take to process an onionskin based on average processing time
15950 of previous onionskins. Closes ticket 7291. You'll never have to
15951 configure MaxOnionsPending again.
15953 o Major features (portability):
15954 - Resume building correctly with MSVC and Makefile.nmake. This patch
15955 resolves numerous bugs and fixes reported by ultramage, including
15956 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
15957 - Make the ntor and curve25519 code build correctly with MSVC.
15958 Fix on 0.2.4.8-alpha.
15961 - When directory authorities are computing thresholds for flags,
15962 never let the threshold for the Fast flag fall below 4096
15963 bytes. Also, do not consider nodes with extremely low bandwidths
15964 when deciding thresholds for various directory flags. This change
15965 should raise our threshold for Fast relays, possibly in turn
15966 improving overall network performance; see ticket 1854. Resolves
15968 - The Tor client now ignores sub-domain components of a .onion
15969 address. This change makes HTTP "virtual" hosting
15970 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
15971 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
15972 hosted on the same hidden service. Implements proposal 204.
15973 - We compute the overhead from passing onionskins back and forth to
15974 cpuworkers, and report it when dumping statistics in response to
15975 SIGUSR1. Supports ticket 7291.
15977 o Minor features (path selection):
15978 - When deciding whether we have enough descriptors to build circuits,
15979 instead of looking at raw relay counts, look at which fraction
15980 of (bandwidth-weighted) paths we're able to build. This approach
15981 keeps clients from building circuits if their paths are likely to
15982 stand out statistically. The default fraction of paths needed is
15983 taken from the consensus directory; you can override it with the
15984 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
15985 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
15986 and we have GeoIP information, also exclude all nodes with unknown
15987 countries "??" and "A1". This behavior is controlled by the
15988 new GeoIPExcludeUnknown option: you can make such nodes always
15989 excluded with "GeoIPExcludeUnknown 1", and disable the feature
15990 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
15991 gets you the default behavior. Implements feature 7706.
15992 - Path Use Bias: Perform separate accounting for successful circuit
15993 use. Keep separate statistics on stream attempt rates versus stream
15994 success rates for each guard. Provide configurable thresholds to
15995 determine when to emit log messages or disable use of guards that
15996 fail too many stream attempts. Resolves ticket 7802.
15998 o Minor features (log messages):
15999 - When learning a fingerprint for a bridge, log its corresponding
16000 transport type. Implements ticket 7896.
16001 - Improve the log message when "Bug/attack: unexpected sendme cell
16002 from client" occurs, to help us track bug 8093.
16005 - Remove a couple of extraneous semicolons that were upsetting the
16006 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
16007 bugfix on 0.2.2.1-alpha.
16008 - Remove a source of rounding error during path bias count scaling;
16009 don't count cannibalized circuits as used for path bias until we
16010 actually try to use them; and fix a circuit_package_relay_cell()
16011 warning message about n_chan==NULL. Fixes bug 7802.
16012 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
16013 actually link against nacl when we're configured to use it. Fixes
16014 bug 7972; bugfix on 0.2.4.8-alpha.
16015 - Compile correctly with the --disable-curve25519 option. Fixes
16016 bug 8153; bugfix on 0.2.4.8-alpha.
16018 o Build improvements:
16019 - Do not report status verbosely from autogen.sh unless the -v flag
16020 is specified. Fixes issue 4664. Patch from Onizuka.
16021 - Replace all calls to snprintf() outside of src/ext with
16022 tor_snprintf(). Also remove the #define to replace snprintf with
16023 _snprintf on Windows; they have different semantics, and all of
16024 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
16025 - Try to detect if we are ever building on a platform where
16026 memset(...,0,...) does not set the value of a double to 0.0. Such
16027 platforms are permitted by the C standard, though in practice
16028 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
16029 currently support them, but it's better to detect them and fail
16030 than to perform erroneously.
16032 o Removed features:
16033 - Stop exporting estimates of v2 and v3 directory traffic shares
16034 in extrainfo documents. They were unneeded and sometimes inaccurate.
16035 Also stop exporting any v2 directory request statistics. Resolves
16037 - Drop support for detecting and warning about versions of Libevent
16038 before 1.3e. Nothing reasonable ships with them any longer;
16039 warning the user about them shouldn't be needed. Resolves ticket
16042 o Code simplifications and refactoring:
16043 - Rename "isin" functions to "contains", for grammar. Resolves
16045 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
16046 with the natural logarithm function from the system libm. Resolves
16050 Changes in version 0.2.4.9-alpha - 2013-01-15
16051 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
16052 work more robustly.
16055 - Fix backward compatibility logic when receiving an embedded ntor
16056 handshake tunneled in a CREATE cell. This clears up the "Bug:
16057 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
16061 Changes in version 0.2.4.8-alpha - 2013-01-14
16062 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
16063 risks, adds a new stronger and faster circuit handshake, and offers
16064 stronger and faster link encryption when both sides support it.
16067 - Preliminary support for directory guards (proposal 207): when
16068 possible, clients now use their entry guards for non-anonymous
16069 directory requests. This can help prevent client enumeration. Note
16070 that this behavior only works when we have a usable consensus
16071 directory, and when options about what to download are more or less
16072 standard. In the future we should re-bootstrap from our guards,
16073 rather than re-bootstrapping from the preconfigured list of
16074 directory sources that ships with Tor. Resolves ticket 6526.
16075 - Tor relays and clients now support a better CREATE/EXTEND cell
16076 format, allowing the sender to specify multiple address, identity,
16077 and handshake types. Implements Robert Ransom's proposal 200;
16078 closes ticket 7199.
16080 o Major features (new circuit handshake):
16081 - Tor now supports a new circuit extension handshake designed by Ian
16082 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
16083 circuit extension handshake, later called "TAP", was a bit slow
16084 (especially on the relay side), had a fragile security proof, and
16085 used weaker keys than we'd now prefer. The new circuit handshake
16086 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
16087 function, making it significantly more secure than the older
16088 handshake, and significantly faster. Tor can use one of two built-in
16089 pure-C curve25519-donna implementations by Adam Langley, or it
16090 can link against the "nacl" library for a tuned version if present.
16092 The built-in version is very fast for 64-bit systems when building
16093 with GCC. The built-in 32-bit version is still faster than the
16094 old TAP protocol, but using libnacl is better on most such hosts.
16096 Clients don't currently use this protocol by default, since
16097 comparatively few clients support it so far. To try it, set
16098 UseNTorHandshake to 1.
16100 Implements proposal 216; closes ticket 7202.
16102 o Major features (better link encryption):
16103 - Relays can now enable the ECDHE TLS ciphersuites when available
16104 and appropriate. These ciphersuites let us negotiate forward-secure
16105 TLS secret keys more safely and more efficiently than with our
16106 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
16107 public relays prefer the (faster) P224 group, and bridges prefer
16108 the (more common) P256 group; you can override this with the
16111 Enabling these ciphers was a little tricky, since for a long time,
16112 clients had been claiming to support them without actually doing
16113 so, in order to foil fingerprinting. But with the client-side
16114 implementation of proposal 198 in 0.2.3.17-beta, clients can now
16115 match the ciphers from recent Firefox versions *and* list the
16116 ciphers they actually mean, so relays can believe such clients
16117 when they advertise ECDHE support in their TLS ClientHello messages.
16119 This feature requires clients running 0.2.3.17-beta or later,
16120 and requires both sides to be running OpenSSL 1.0.0 or later
16121 with ECC support. OpenSSL 1.0.1, with the compile-time option
16122 "enable-ec_nistp_64_gcc_128", is highly recommended.
16124 Implements the relay side of proposal 198; closes ticket 7200.
16127 - Avoid crashing when, as a relay without IPv6-exit support, a
16128 client insists on getting an IPv6 address or nothing. Fixes bug
16129 7814; bugfix on 0.2.4.7-alpha.
16132 - Improve circuit build timeout handling for hidden services.
16133 In particular: adjust build timeouts more accurately depending
16134 upon the number of hop-RTTs that a particular circuit type
16135 undergoes. Additionally, launch intro circuits in parallel
16136 if they timeout, and take the first one to reply as valid.
16137 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
16138 separate error codes; or at least, don't break for that reason.
16139 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
16140 - Update to the January 2 2013 Maxmind GeoLite Country database.
16142 o Minor features (testing):
16143 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
16144 (P-256) Diffie-Hellman handshakes to src/or/bench.
16145 - Add benchmark functions to test onion handshake performance.
16147 o Minor features (path bias detection):
16148 - Alter the Path Bias log messages to be more descriptive in terms
16149 of reporting timeouts and other statistics.
16150 - Create three levels of Path Bias log messages, as opposed to just
16151 two. These are configurable via consensus as well as via the torrc
16152 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
16153 The default values are 0.70, 0.50, and 0.30 respectively.
16154 - Separate the log message levels from the decision to drop guards,
16155 which also is available via torrc option PathBiasDropGuards.
16156 PathBiasDropGuards still defaults to 0 (off).
16157 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
16158 in combination with PathBiasExtremeRate.
16159 - Increase the default values for PathBiasScaleThreshold and
16160 PathBiasCircThreshold from (200, 20) to (300, 150).
16161 - Add in circuit usage accounting to path bias. If we try to use a
16162 built circuit but fail for any reason, it counts as path bias.
16163 Certain classes of circuits where the adversary gets to pick your
16164 destination node are exempt from this accounting. Usage accounting
16165 can be specifically disabled via consensus parameter or torrc.
16166 - Convert all internal path bias state to double-precision floating
16167 point, to avoid roundoff error and other issues.
16168 - Only record path bias information for circuits that have completed
16169 *two* hops. Assuming end-to-end tagging is the attack vector, this
16170 makes us more resilient to ambient circuit failure without any
16171 detection capability loss.
16173 o Minor bugfixes (log messages):
16174 - Rate-limit the "No circuits are opened. Relaxed timeout for a
16175 circuit with channel state open..." message to once per hour to
16176 keep it from filling the notice logs. Mitigates bug 7799 but does
16177 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
16178 - Avoid spurious warnings when configuring multiple client ports of
16179 which only some are nonlocal. Previously, we had claimed that some
16180 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
16183 o Code simplifications and refactoring:
16184 - Get rid of a couple of harmless clang warnings, where we compared
16185 enums to ints. These warnings are newly introduced in clang 3.2.
16186 - Split the onion.c file into separate modules for the onion queue
16187 and the different handshakes it supports.
16188 - Remove the marshalling/unmarshalling code for sending requests to
16189 cpuworkers over a socket, and instead just send structs. The
16190 recipient will always be the same Tor binary as the sender, so
16191 any encoding is overkill.
16194 Changes in version 0.2.4.7-alpha - 2012-12-24
16195 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
16196 directory mirrors for more robust bootstrapping; fixes more issues where
16197 clients with changing network conditions refuse to make any circuits;
16198 adds initial support for exiting to IPv6 addresses; resumes being able
16199 to update our GeoIP database, and includes the geoip6 file this time;
16200 turns off the client-side DNS cache by default due to privacy risks;
16201 and fixes a variety of other issues.
16203 o Major features (client resilience):
16204 - Add a new "FallbackDir" torrc option to use when we can't use
16205 a directory mirror from the consensus (either because we lack a
16206 consensus, or because they're all down). Currently, all authorities
16207 are fallbacks by default, and there are no other default fallbacks,
16208 but that will change. This option will allow us to give clients a
16209 longer list of servers to try to get a consensus from when first
16210 connecting to the Tor network, and thereby reduce load on the
16211 directory authorities. Implements proposal 206, "Preconfigured
16212 directory sources for bootstrapping". We also removed the old
16213 "FallbackNetworkstatus" option, since we never got it working well
16214 enough to use it. Closes bug 572.
16215 - If we have no circuits open, use a relaxed timeout (the
16216 95-percentile cutoff) until a circuit succeeds. This heuristic
16217 should allow Tor to succeed at building circuits even when the
16218 network connection drastically changes. Should help with bug 3443.
16220 o Major features (IPv6):
16221 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
16222 connectivity, then set the IPv6Exit flag to 1. Also make sure your
16223 exit policy reads as you would like: the address * applies to all
16224 address families, whereas *4 is IPv4 address only, and *6 is IPv6
16225 addresses only. On the client side, you'll need to wait until the
16226 authorities have upgraded, wait for enough exits to support IPv6,
16227 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
16228 ticket 5547, implements proposal 117 as revised in proposal 208.
16230 We DO NOT recommend that clients with actual anonymity needs start
16231 using IPv6 over Tor yet, since not enough exits support it yet.
16233 o Major features (geoip database):
16234 - Maxmind began labelling Tor relays as being in country "A1",
16235 which breaks by-country node selection inside Tor. Now we use a
16236 script to replace "A1" ("Anonymous Proxy") entries in our geoip
16237 file with real country codes. This script fixes about 90% of "A1"
16238 entries automatically and uses manual country code assignments to
16239 fix the remaining 10%. See src/config/README.geoip for details.
16240 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
16241 Country database, as modified above.
16243 o Major bugfixes (client-side DNS):
16244 - Turn off the client-side DNS cache by default. Updating and using
16245 the DNS cache is now configurable on a per-client-port
16246 level. SOCKSPort, DNSPort, etc lines may now contain
16247 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
16248 cache these types of DNS answers when we receive them from an
16249 exit node in response to an application request on this port, and
16250 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
16251 cached DNS answers of these types, we shouldn't use them. It's
16252 potentially risky to use cached DNS answers at the client, since
16253 doing so can indicate to one exit what answers we've gotten
16254 for DNS lookups in the past. With IPv6, this becomes especially
16255 problematic. Using cached DNS answers for requests on the same
16256 circuit would present less linkability risk, since all traffic
16257 on a circuit is already linkable, but it would also provide
16258 little performance benefit: the exit node caches DNS replies
16259 too. Implements a simplified version of Proposal 205. Implements
16262 o Major bugfixes (other):
16263 - Alter circuit build timeout measurement to start at the point
16264 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
16265 initialization). This should make our timeout measurements more
16266 uniform. Previously, we were sometimes including ORconn setup time
16267 in our circuit build time measurements. Should resolve bug 3443.
16268 - Fix an assertion that could trigger in hibernate_go_dormant() when
16269 closing an or_connection_t: call channel_mark_for_close() rather
16270 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
16272 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
16273 7655; bugfix on 0.2.4.6-alpha.
16276 - Add a new torrc option "ServerTransportListenAddr" to let bridge
16277 operators select the address where their pluggable transports will
16278 listen for connections. Resolves ticket 7013.
16279 - Allow an optional $ before the node identity digest in the
16280 controller command GETINFO ns/id/<identity>, for consistency with
16281 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
16282 - Log packaged cell fullness as part of the heartbeat message.
16283 Diagnosis to try to determine the extent of bug 7743.
16285 o Minor features (IPv6):
16286 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
16287 prefer to hand out virtual IPv6 addresses, since there are more of
16288 them and we can't run out. To override this behavior and make IPv4
16289 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
16290 or DNSPort you're using for resolving. Implements ticket 7571.
16291 - AutomapHostsOnResolve responses are now randomized, to avoid
16292 annoying situations where Tor is restarted and applications
16293 connect to the wrong addresses.
16294 - Never try more than 1000 times to pick a new virtual address when
16295 AutomapHostsOnResolve is set. That's good enough so long as we
16296 aren't close to handing out our entire virtual address space;
16297 if you're getting there, it's best to switch to IPv6 virtual
16301 - The ADDRMAP command can no longer generate an ill-formed error
16302 code on a failed MAPADDRESS. It now says "internal" rather than
16303 an English sentence fragment with spaces in the middle. Bugfix on
16304 Tor 0.2.0.19-alpha.
16305 - Fix log messages and comments to avoid saying "GMT" when we mean
16306 "UTC". Fixes bug 6113.
16307 - Compile on win64 using mingw64. Fixes bug 7260; patches from
16309 - Fix a crash when debugging unit tests on Windows: deallocate a
16310 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
16311 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
16314 - The DirServer option is now DirAuthority, for consistency with
16315 current naming patterns. You can still use the old DirServer form.
16317 o Code simplification and refactoring:
16318 - Move the client-side address-map/virtual-address/DNS-cache code
16319 out of connection_edge.c into a new addressmap.c module.
16320 - Remove unused code for parsing v1 directories and "running routers"
16321 documents. Fixes bug 6887.
16324 Changes in version 0.2.3.25 - 2012-11-19
16325 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
16326 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
16327 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
16328 programmer, and friend. Unstinting in his dedication to the cause of
16329 freedom, he inspired and helped many of us as we began our work on
16330 anonymity, and inspires us still. Please honor his memory by writing
16331 software to protect people's freedoms, and by helping others to do so.
16333 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
16334 significantly reduced directory overhead (via microdescriptors),
16335 enormous crypto performance improvements for fast relays on new
16336 enough hardware, a new v3 TLS handshake protocol that can better
16337 resist fingerprinting, support for protocol obfuscation plugins (aka
16338 pluggable transports), better scalability for hidden services, IPv6
16339 support for bridges, performance improvements like allowing clients
16340 to skip the first round-trip on the circuit ("optimistic data") and
16341 refilling token buckets more often, a new "stream isolation" design
16342 to isolate different applications on different circuits, and many
16343 stability, security, and privacy fixes.
16346 - Tor tries to wipe potentially sensitive data after using it, so
16347 that if some subsequent security failure exposes Tor's memory,
16348 the damage will be limited. But we had a bug where the compiler
16349 was eliminating these wipe operations when it decided that the
16350 memory was no longer visible to a (correctly running) program,
16351 hence defeating our attempt at defense in depth. We fix that
16352 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
16353 is unlikely to optimize away. Future versions of Tor may use
16354 a less ridiculously heavy approach for this. Fixes bug 7352.
16355 Reported in an article by Andrey Karpov.
16358 - Fix a harmless bug when opting against publishing a relay descriptor
16359 because DisableNetwork is set. Fixes bug 7464; bugfix on
16363 Changes in version 0.2.4.6-alpha - 2012-11-13
16364 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
16365 makes our defense-in-depth memory wiping more reliable, and begins to
16366 count IPv6 addresses in bridge statistics,
16369 - Fix an assertion failure that could occur when closing a connection
16370 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
16372 - Tor tries to wipe potentially sensitive data after using it, so
16373 that if some subsequent security failure exposes Tor's memory,
16374 the damage will be limited. But we had a bug where the compiler
16375 was eliminating these wipe operations when it decided that the
16376 memory was no longer visible to a (correctly running) program,
16377 hence defeating our attempt at defense in depth. We fix that
16378 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
16379 is unlikely to optimize away. Future versions of Tor may use
16380 a less ridiculously heavy approach for this. Fixes bug 7352.
16381 Reported in an article by Andrey Karpov.
16384 - Add GeoIP database for IPv6 addresses. The new config option
16386 - Bridge statistics now count bridge clients connecting over IPv6:
16387 bridge statistics files now list "bridge-ip-versions" and
16388 extra-info documents list "geoip6-db-digest". The control protocol
16389 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
16390 implementation by "shkoo", addressing ticket 5055.
16393 - Warn when we are binding low ports when hibernation is enabled;
16394 previously we had warned when we were _advertising_ low ports with
16395 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
16396 - Fix a harmless bug when opting against publishing a relay descriptor
16397 because DisableNetwork is set. Fixes bug 7464; bugfix on
16399 - Add warning message when a managed proxy dies during configuration.
16400 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
16401 - Fix a linking error when building tor-fw-helper without miniupnp.
16402 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
16403 - Check for closing an or_connection_t without going through correct
16404 channel functions; emit a warning and then call
16405 connection_or_close_for_error() so we don't assert as in bugs 7212
16407 - Compile correctly on compilers without C99 designated initializer
16408 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
16409 - Avoid a possible assert that can occur when channel_send_destroy() is
16410 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
16411 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
16412 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
16413 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
16414 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
16416 o Code simplification and refactoring:
16417 - Start using OpenBSD's implementation of queue.h, so that we don't
16418 need to hand-roll our own pointer and list structures whenever we
16419 need them. (We can't rely on a sys/queue.h, since some operating
16420 systems don't have them, and the ones that do have them don't all
16421 present the same extensions.)
16424 Changes in version 0.2.4.5-alpha - 2012-10-25
16425 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
16426 two important security vulnerabilities that could lead to remotely
16427 triggerable relay crashes, fix a major bug that was preventing clients
16428 from choosing suitable exit nodes, and refactor some of our code.
16430 o Major bugfixes (security, also in 0.2.3.24-rc):
16431 - Fix a group of remotely triggerable assertion failures related to
16432 incorrect link protocol negotiation. Found, diagnosed, and fixed
16433 by "some guy from France". Fix for CVE-2012-2250; bugfix on
16435 - Fix a denial of service attack by which any directory authority
16436 could crash all the others, or by which a single v2 directory
16437 authority could crash everybody downloading v2 directory
16438 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
16440 o Major bugfixes (also in 0.2.3.24-rc):
16441 - When parsing exit policy summaries from microdescriptors, we had
16442 previously been ignoring the last character in each one, so that
16443 "accept 80,443,8080" would be treated by clients as indicating
16444 a node that allows access to ports 80, 443, and 808. That would
16445 lead to clients attempting connections that could never work,
16446 and ignoring exit nodes that would support their connections. Now
16447 clients parse these exit policy summaries correctly. Fixes bug 7192;
16448 bugfix on 0.2.3.1-alpha.
16450 o Minor bugfixes (also in 0.2.3.24-rc):
16451 - Clients now consider the ClientRejectInternalAddresses config option
16452 when using a microdescriptor consensus stanza to decide whether
16453 an exit relay would allow exiting to an internal address. Fixes
16454 bug 7190; bugfix on 0.2.3.1-alpha.
16457 - Only disable TLS session ticket support when running as a TLS
16458 server. Now clients will blend better with regular Firefox
16459 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
16461 o Code simplification and refactoring:
16462 - Start using OpenBSD's implementation of queue.h (originally by
16464 - Move the entry node code from circuitbuild.c to its own file.
16465 - Move the circuit build timeout tracking code from circuitbuild.c
16469 Changes in version 0.2.3.24-rc - 2012-10-25
16470 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
16471 could lead to remotely triggerable relay crashes, and fixes
16472 a major bug that was preventing clients from choosing suitable exit
16475 o Major bugfixes (security):
16476 - Fix a group of remotely triggerable assertion failures related to
16477 incorrect link protocol negotiation. Found, diagnosed, and fixed
16478 by "some guy from France". Fix for CVE-2012-2250; bugfix on
16480 - Fix a denial of service attack by which any directory authority
16481 could crash all the others, or by which a single v2 directory
16482 authority could crash everybody downloading v2 directory
16483 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
16486 - When parsing exit policy summaries from microdescriptors, we had
16487 previously been ignoring the last character in each one, so that
16488 "accept 80,443,8080" would be treated by clients as indicating
16489 a node that allows access to ports 80, 443, and 808. That would
16490 lead to clients attempting connections that could never work,
16491 and ignoring exit nodes that would support their connections. Now
16492 clients parse these exit policy summaries correctly. Fixes bug 7192;
16493 bugfix on 0.2.3.1-alpha.
16496 - Clients now consider the ClientRejectInternalAddresses config option
16497 when using a microdescriptor consensus stanza to decide whether
16498 an exit relay would allow exiting to an internal address. Fixes
16499 bug 7190; bugfix on 0.2.3.1-alpha.
16502 Changes in version 0.2.4.4-alpha - 2012-10-20
16503 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
16504 vulnerability introduced by a change in OpenSSL, fixes a remotely
16505 triggerable assert, and adds new channel_t and circuitmux_t abstractions
16506 that will make it easier to test new connection transport and cell
16507 scheduling algorithms.
16509 o New directory authorities (also in 0.2.3.23-rc):
16510 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
16511 authority. Closes ticket 5749.
16513 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
16514 - Disable TLS session tickets. OpenSSL's implementation was giving
16515 our TLS session keys the lifetime of our TLS context objects, when
16516 perfect forward secrecy would want us to discard anything that
16517 could decrypt a link connection as soon as the link connection
16518 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
16519 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
16520 - Discard extraneous renegotiation attempts once the V3 link
16521 protocol has been initiated. Failure to do so left us open to
16522 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
16523 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
16525 o Internal abstraction features:
16526 - Introduce new channel_t abstraction between circuits and
16527 or_connection_t to allow for implementing alternate OR-to-OR
16528 transports. A channel_t is an abstract object which can either be a
16529 cell-bearing channel, which is responsible for authenticating and
16530 handshaking with the remote OR and transmitting cells to and from
16531 it, or a listening channel, which spawns new cell-bearing channels
16532 at the request of remote ORs. Implements part of ticket 6465.
16533 - Also new is the channel_tls_t subclass of channel_t, adapting it
16534 to the existing or_connection_t code. The V2/V3 protocol handshaking
16535 code which formerly resided in command.c has been moved below the
16536 channel_t abstraction layer and may be found in channeltls.c now.
16537 Implements the rest of ticket 6465.
16538 - Introduce new circuitmux_t storing the queue of circuits for
16539 a channel; this encapsulates and abstracts the queue logic and
16540 circuit selection policy, and allows the latter to be overridden
16541 easily by switching out a policy object. The existing EWMA behavior
16542 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
16544 o Required libraries:
16545 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
16546 strongly recommended.
16549 - Warn users who run hidden services on a Tor client with
16550 UseEntryGuards disabled that their hidden services will be
16551 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
16552 attack which motivated Tor to support entry guards in the first
16553 place). Resolves ticket 6889.
16554 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
16555 dhill. Resolves ticket 6982.
16556 - Option OutboundBindAddress can be specified multiple times and
16557 accepts IPv6 addresses. Resolves ticket 6876.
16559 o Minor bugfixes (also in 0.2.3.23-rc):
16560 - Don't serve or accept v2 hidden service descriptors over a
16561 relay's DirPort. It's never correct to do so, and disabling it
16562 might make it more annoying to exploit any bugs that turn up in the
16563 descriptor-parsing code. Fixes bug 7149.
16564 - Fix two cases in src/or/transports.c where we were calling
16565 fmt_addr() twice in a parameter list. Bug found by David
16566 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
16567 - Fix memory leaks whenever we logged any message about the "path
16568 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
16569 - When relays refuse a "create" cell because their queue of pending
16570 create cells is too big (typically because their cpu can't keep up
16571 with the arrival rate), send back reason "resource limit" rather
16572 than reason "internal", so network measurement scripts can get a
16573 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
16576 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
16577 - Free some more still-in-use memory at exit, to make hunting for
16578 memory leaks easier. Resolves bug 7029.
16579 - When a Tor client gets a "truncated" relay cell, the first byte of
16580 its payload specifies why the circuit was truncated. We were
16581 ignoring this 'reason' byte when tearing down the circuit, resulting
16582 in the controller not being told why the circuit closed. Now we
16583 pass the reason from the truncated cell to the controller. Bugfix
16584 on 0.1.2.3-alpha; fixes bug 7039.
16585 - Downgrade "Failed to hand off onionskin" messages to "debug"
16586 severity, since they're typically redundant with the "Your computer
16587 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
16588 - Make clients running with IPv6 bridges connect over IPv6 again,
16589 even without setting new config options ClientUseIPv6 and
16590 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
16591 - Use square brackets around IPv6 addresses in numerous places
16592 that needed them, including log messages, HTTPS CONNECT proxy
16593 requests, TransportProxy statefile entries, and pluggable transport
16594 extra-info lines. Fixes bug 7011; patch by David Fifield.
16596 o Code refactoring and cleanup:
16597 - Source files taken from other packages now reside in src/ext;
16598 previously they were scattered around the rest of Tor.
16599 - Avoid use of reserved identifiers in our C code. The C standard
16600 doesn't like us declaring anything that starts with an
16601 underscore, so let's knock it off before we get in trouble. Fix
16602 for bug 1031; bugfix on the first Tor commit.
16605 Changes in version 0.2.3.23-rc - 2012-10-20
16606 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
16607 vulnerability introduced by a change in OpenSSL, and fixes a variety
16608 of smaller bugs in preparation for the release.
16610 o New directory authorities:
16611 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
16612 authority. Closes ticket 5749.
16614 o Major bugfixes (security/privacy):
16615 - Disable TLS session tickets. OpenSSL's implementation was giving
16616 our TLS session keys the lifetime of our TLS context objects, when
16617 perfect forward secrecy would want us to discard anything that
16618 could decrypt a link connection as soon as the link connection
16619 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
16620 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
16621 - Discard extraneous renegotiation attempts once the V3 link
16622 protocol has been initiated. Failure to do so left us open to
16623 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
16624 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
16627 - Fix a possible crash bug when checking for deactivated circuits
16628 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
16629 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
16631 o Minor bugfixes (on 0.2.3.x):
16632 - Fix two cases in src/or/transports.c where we were calling
16633 fmt_addr() twice in a parameter list. Bug found by David
16634 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
16635 - Convert an assert in the pathbias code to a log message. The assert
16636 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
16637 bugfix on 0.2.3.17-beta.
16638 - Fix memory leaks whenever we logged any message about the "path
16639 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
16641 o Minor bugfixes (on 0.2.2.x and earlier):
16642 - Don't serve or accept v2 hidden service descriptors over a relay's
16643 DirPort. It's never correct to do so, and disabling it might
16644 make it more annoying to exploit any bugs that turn up in the
16645 descriptor-parsing code. Fixes bug 7149.
16646 - When relays refuse a "create" cell because their queue of pending
16647 create cells is too big (typically because their cpu can't keep up
16648 with the arrival rate), send back reason "resource limit" rather
16649 than reason "internal", so network measurement scripts can get a
16650 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
16651 - Correct file sizes when reading binary files on Cygwin, to avoid
16652 a bug where Tor would fail to read its state file. Fixes bug 6844;
16653 bugfix on 0.1.2.7-alpha.
16654 - Avoid undefined behavior when parsing the list of supported
16655 rendezvous/introduction protocols in a hidden service descriptor.
16656 Previously, Tor would have confused (as-yet-unused) protocol version
16657 numbers greater than 32 with lower ones on many platforms. Fixes
16658 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
16660 o Documentation fixes:
16661 - Clarify that hidden services are TCP only. Fixes bug 6024.
16664 Changes in version 0.2.4.3-alpha - 2012-09-22
16665 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
16666 assertion, resumes letting relays test reachability of their DirPort,
16667 and cleans up a bunch of smaller bugs.
16670 - Fix an assertion failure in tor_timegm() that could be triggered
16671 by a badly formatted directory object. Bug found by fuzzing with
16672 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
16675 - Fix a possible crash bug when checking for deactivated circuits
16676 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
16677 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
16678 - Allow routers to detect that their own DirPorts are running. When
16679 we removed support for versions_supports_begindir, we also
16680 accidentally removed the mechanism we used to self-test our
16681 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
16682 bugfix on 0.2.4.2-alpha.
16684 o Security features:
16685 - Switch to a completely time-invariant approach for picking nodes
16686 weighted by bandwidth. Our old approach would run through the
16687 part of the loop after it had made its choice slightly slower
16688 than it ran through the part of the loop before it had made its
16689 choice. Addresses ticket 6538.
16690 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
16691 by tor2web clients allows hidden services to identify tor2web
16692 clients through their repeated selection of the same rendezvous
16693 and introduction point circuit endpoints (their guards). Resolves
16697 - Enable Tor to read configuration, state, and key information from
16698 a FIFO. Previously Tor would only read from files with a positive
16699 stat.st_size. Code from meejah; fixes bug 6044.
16702 - Correct file sizes when reading binary files on Cygwin, to avoid
16703 a bug where Tor would fail to read its state file. Fixes bug 6844;
16704 bugfix on 0.1.2.7-alpha.
16705 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
16706 bugfix on 0.2.0.3-alpha.
16707 - When complaining about a client port on a public address, log
16708 which address we're complaining about. Fixes bug 4020; bugfix on
16709 0.2.3.3-alpha. Patch by Tom Fitzhenry.
16710 - Convert an assert in the pathbias code to a log message. The assert
16711 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
16712 bugfix on 0.2.3.17-beta.
16713 - Our new buildsystem was overzealous about rebuilding manpages: it
16714 would rebuild them all whenever any one of them changed. Now our
16715 dependency checking should be correct. Fixes bug 6843; bugfix on
16717 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
16718 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
16719 - Correct log printout about which address family is preferred
16720 when connecting to a bridge with both an IPv4 and IPv6 OR port.
16721 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
16723 o Minor bugfixes (code cleanliness):
16724 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
16725 with large values. This situation was untriggered, but nevertheless
16726 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
16727 - Reject consensus votes with more than 64 known-flags. We aren't even
16728 close to that limit yet, and our code doesn't handle it correctly.
16729 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
16730 - Avoid undefined behavior when parsing the list of supported
16731 rendezvous/introduction protocols in a hidden service descriptor.
16732 Previously, Tor would have confused (as-yet-unused) protocol version
16733 numbers greater than 32 with lower ones on many platforms. Fixes
16734 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
16735 - Fix handling of rendezvous client authorization types over 8.
16736 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
16737 - Fix building with older versions of GCC (2.95, for one) that don't
16738 like preprocessor directives inside macro arguments. Found by
16739 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
16740 - Switch weighted node selection rule from using a list of doubles
16741 to using a list of int64_t. This change should make the process
16742 slightly easier to debug and maintain. Needed to finish ticket 6538.
16744 o Code simplification and refactoring:
16745 - Move the generic "config" code into a new file, and have "config.c"
16746 hold only torrc- and state-related code. Resolves ticket 6823.
16747 - Move the core of our "choose a weighted element at random" logic
16748 into its own function, and give it unit tests. Now the logic is
16749 testable, and a little less fragile too.
16750 - Removed the testing_since field of node_t, which hasn't been used
16751 for anything since 0.2.0.9-alpha.
16753 o Documentation fixes:
16754 - Clarify that hidden services are TCP only. Fixes bug 6024.
16755 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
16759 Changes in version 0.2.3.22-rc - 2012-09-11
16760 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
16764 - Fix an assertion failure in tor_timegm() that could be triggered
16765 by a badly formatted directory object. Bug found by fuzzing with
16766 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
16769 - Avoid segfault when starting up having run with an extremely old
16770 version of Tor and parsing its state file. Fixes bug 6801; bugfix
16774 Changes in version 0.2.2.39 - 2012-09-11
16775 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
16779 - Fix an assertion failure in tor_timegm() that could be triggered
16780 by a badly formatted directory object. Bug found by fuzzing with
16781 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
16782 - Do not crash when comparing an address with port value 0 to an
16783 address policy. This bug could have been used to cause a remote
16784 assertion failure by or against directory authorities, or to
16785 allow some applications to crash clients. Fixes bug 6690; bugfix
16789 Changes in version 0.2.4.2-alpha - 2012-09-10
16790 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
16791 raises the default rate limiting even more, and makes the bootstrapping
16792 log messages less noisy.
16795 - Automatically forward the TCP ports of pluggable transport
16796 proxies using tor-fw-helper if PortForwarding is enabled. Implements
16800 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
16801 to 1GB/1GB. The previous defaults were intended to be "basically
16802 infinite", but it turns out they're now limiting our 100mbit+
16803 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
16804 last time we raised it).
16807 - Detect when we're running with a version of OpenSSL other than the
16808 one we compiled with. This has occasionally given people hard-to-
16810 - Log fewer lines at level "notice" about our OpenSSL and Libevent
16811 versions and capabilities when everything is going right. Resolves
16812 part of ticket 6736.
16813 - Directory authorities no long accept descriptors for any version of
16814 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
16815 These versions are insecure, unsupported, or both. Implements
16819 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
16820 to start with a triple-underscore so the controller won't touch it.
16821 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
16822 - Avoid segfault when starting up having run with an extremely old
16823 version of Tor and parsing its state file. Fixes bug 6801; bugfix
16825 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
16826 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
16827 - Don't follow the NULL pointer if microdescriptor generation fails.
16828 (This does not appear to be triggerable, but it's best to be safe.)
16829 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
16830 - Fix mis-declared dependencies on src/common/crypto.c and
16831 src/or/tor_main.c that could break out-of-tree builds under some
16832 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
16833 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
16834 6778; bugfix on 0.2.4.1-alpha.
16835 - Fix a harmless (in this case) build warning for implicitly
16836 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
16838 o Removed features:
16839 - Now that all versions before 0.2.2.x are disallowed, we no longer
16840 need to work around their missing features. Thus we can remove a
16841 bunch of compatibility code.
16843 o Code refactoring:
16844 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
16845 TCP ports to forward. In the past it only accepted two ports:
16846 the ORPort and the DirPort.
16849 Changes in version 0.2.4.1-alpha - 2012-09-05
16850 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
16851 bridgedb; lets relays use IPv6 addresses and directory authorities
16852 advertise them; and switches to a cleaner build interface.
16854 This is the first alpha release in a new series, so expect there to
16855 be bugs. Users who would rather test out a more stable branch should
16856 stay with 0.2.3.x for now.
16858 o Major features (bridges):
16859 - Bridges now report the pluggable transports they support to the
16860 bridge authority, so it can pass the supported transports on to
16861 bridgedb and/or eventually do reachability testing. Implements
16864 o Major features (IPv6):
16865 - Bridge authorities now accept IPv6 bridge addresses and include
16866 them in network status documents. Implements ticket 5534.
16867 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
16868 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
16869 to happen. Implements ticket 5535.
16870 - All kind of relays, not just bridges, can now advertise an IPv6
16871 OR port. Implements ticket 6362.
16872 - Directory authorities vote on IPv6 OR ports using the new consensus
16873 method 14. Implements ticket 6363.
16875 o Major features (build):
16876 - Switch to a nonrecursive Makefile structure. Now instead of each
16877 Makefile.am invoking other Makefile.am's, there is a master
16878 Makefile.am that includes the others. This change makes our build
16879 process slightly more maintainable, and improves parallelism for
16880 building with make -j. Original patch by Stewart Smith; various
16881 fixes by Jim Meyering.
16882 - Where available, we now use automake's "silent" make rules by
16883 default, so that warnings are easier to spot. You can get the old
16884 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
16886 o Minor features (code security and spec conformance):
16887 - Clear keys and key-derived material left on the stack in
16888 rendservice.c and rendclient.c. Check return value of
16889 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
16890 These fixes should make us more forward-secure against cold-boot
16891 attacks and the like. Fixes bug 2385.
16892 - Reject EXTEND cells sent to nonexistent streams. According to the
16893 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
16894 we were only checking for stream IDs that were currently in use.
16895 Found while hunting for more instances of bug 6271. Bugfix on
16896 0.0.2pre8, which introduced incremental circuit construction.
16898 o Minor features (streamlining);
16899 - No longer include the "opt" prefix when generating routerinfos
16900 or v2 directories: it has been needless since Tor 0.1.2. Closes
16902 - Remove some now-needless code that tried to aggressively flush
16903 OR connections as data was added to them. Since 0.2.0.1-alpha, our
16904 cell queue logic has saved us from the failure mode that this code
16905 was supposed to prevent. Removing this code will limit the number
16906 of baroque control flow paths through Tor's network logic. Reported
16907 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
16909 o Minor features (controller):
16910 - Add a "GETINFO signal/names" control port command. Implements
16912 - Provide default values for all options via "GETINFO config/defaults".
16913 Implements ticket 4971.
16915 o Minor features (IPv6):
16916 - New config option "AuthDirHasIPv6Connectivity 1" that directory
16917 authorities should set if they have IPv6 connectivity and want to
16918 do reachability tests for IPv6 relays. Implements feature 5974.
16919 - A relay with an IPv6 OR port now sends that address in NETINFO
16920 cells (in addition to its other address). Implements ticket 6364.
16922 o Minor features (log messages):
16923 - Omit the first heartbeat log message, because it never has anything
16924 useful to say, and it clutters up the bootstrapping messages.
16925 Resolves ticket 6758.
16926 - Don't log about reloading the microdescriptor cache at startup. Our
16927 bootstrap warnings are supposed to tell the user when there's a
16928 problem, and our bootstrap notices say when there isn't. Resolves
16929 ticket 6759; bugfix on 0.2.2.6-alpha.
16930 - Don't log "I learned some more directory information" when we're
16931 reading cached directory information. Reserve it for when new
16932 directory information arrives in response to a fetch. Resolves
16934 - Prevent rounding error in path bias counts when scaling
16935 them down, and use the correct scale factor default. Also demote
16936 some path bias related log messages down a level and make others
16937 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
16938 - We no longer warn so much when generating manpages from their
16941 o Code simplifications and refactoring:
16942 - Enhance our internal sscanf replacement so that we can eliminate
16943 the last remaining uses of the system sscanf. (Though those uses
16944 of sscanf were safe, sscanf itself is generally error prone, so
16945 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
16947 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
16948 - Move last_reachable and testing_since from routerinfo_t to node_t.
16949 Implements ticket 5529.
16950 - Add replaycache_t structure, functions and unit tests, then refactor
16951 rend_service_introduce() to be more clear to read, improve, debug,
16952 and test. Resolves bug 6177.
16953 - Finally remove support for malloc_good_size and malloc_usable_size.
16954 We had hoped that these functions would let us eke a little more
16955 memory out of our malloc implementation. Unfortunately, the only
16956 implementations that provided these functions are also ones that
16957 are already efficient about not overallocation: they never got us
16958 more than 7 or so bytes per allocation. Removing them saves us a
16959 little code complexity and a nontrivial amount of build complexity.
16961 o New requirements:
16962 - Tor maintainers now require Automake version 1.9 or later to build
16963 Tor from the Git repository. (Automake is not required when building
16964 from a source distribution.)
16967 Changes in version 0.2.3.21-rc - 2012-09-05
16968 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
16969 series. It fixes a trio of potential security bugs, fixes a bug where
16970 we were leaving some of the fast relays out of the microdescriptor
16971 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
16972 and cleans up other smaller issues.
16974 o Major bugfixes (security):
16975 - Tear down the circuit if we get an unexpected SENDME cell. Clients
16976 could use this trick to make their circuits receive cells faster
16977 than our flow control would have allowed, or to gum up the network,
16978 or possibly to do targeted memory denial-of-service attacks on
16979 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
16980 from July 2002, before the release of Tor 0.0.0. We had committed
16981 this patch previously, but we had to revert it because of bug 6271.
16982 Now that 6271 is fixed, this patch appears to work.
16983 - Reject any attempt to extend to an internal address. Without
16984 this fix, a router could be used to probe addresses on an internal
16985 network to see whether they were accepting connections. Fixes bug
16986 6710; bugfix on 0.0.8pre1.
16987 - Do not crash when comparing an address with port value 0 to an
16988 address policy. This bug could have been used to cause a remote
16989 assertion failure by or against directory authorities, or to
16990 allow some applications to crash clients. Fixes bug 6690; bugfix
16994 - Remove the upper bound on microdescriptor length. We were hitting
16995 the limit for routers with complex exit policies or family
16996 declarations, causing clients to not use them. Fixes the first
16997 piece of bug 6404; fix on 0.2.2.6-alpha.
16998 - Detect "ORPort 0" as meaning, uniformly, that we're not running
16999 as a relay. Previously, some of our code would treat the presence
17000 of any ORPort line as meaning that we should act like a relay,
17001 even though our new listener code would correctly not open any
17002 ORPorts for ORPort 0. Similar bugs in other Port options are also
17003 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
17006 - Avoid a pair of double-free and use-after-mark bugs that can
17007 occur with certain timings in canceled and re-received DNS
17008 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
17009 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
17010 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
17011 - Allow one-hop directory fetching circuits the full "circuit build
17012 timeout" period, rather than just half of it, before failing them
17013 and marking the relay down. This fix should help reduce cases where
17014 clients declare relays (or worse, bridges) unreachable because
17015 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
17016 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
17018 - Authorities no longer include any router in their microdescriptor
17019 consensuses for which they couldn't generate or agree on a
17020 microdescriptor. Fixes the second piece of bug 6404; fix on
17022 - Detect and reject attempts to specify both "FooPort" and
17023 "FooPort 0" in the same configuration domain. (It's still okay
17024 to have a FooPort in your configuration file, and use "FooPort 0"
17025 on the command line to disable it.) Fixes the second half of bug
17026 6507; bugfix on 0.2.3.3-alpha.
17027 - Make wildcarded addresses (that is, ones beginning with "*.") work
17028 when provided via the controller's MapAddress command. Previously,
17029 they were accepted, but we never actually noticed that they were
17030 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
17031 - Avoid crashing on a malformed state file where EntryGuardPathBias
17032 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
17033 - Add a (probably redundant) memory clear between iterations of
17034 the router status voting loop, to prevent future coding errors
17035 where data might leak between iterations of the loop. Resolves
17038 o Minor bugfixes (log messages):
17039 - Downgrade "set buildtimeout to low value" messages to "info"
17040 severity; they were never an actual problem, there was never
17041 anything reasonable to do about them, and they tended to spam logs
17042 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
17043 - Downgrade path-bias warning messages to "info". We'll try to get
17044 them working better in 0.2.4. Add internal circuit construction
17045 state to protect against the noisy warn message "Unexpectedly high
17046 circuit_successes". Also add some additional rate-limited notice
17047 messages to help determine the root cause of the warn. Fixes bug
17048 6475. Bugfix against 0.2.3.17-beta.
17049 - Move log message when unable to find a microdesc in a routerstatus
17050 entry to parse time. Previously we'd spam this warning every time
17051 we tried to figure out which microdescriptors to download. Fixes
17052 the third piece of bug 6404; fix on 0.2.3.18-rc.
17055 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
17056 change when the authority is deciding whether to accept a newly
17057 uploaded descriptor. Implements ticket 6423.
17058 - Add missing documentation for consensus and microdesc files.
17059 Resolves ticket 6732.
17062 Changes in version 0.2.2.38 - 2012-08-12
17063 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
17064 attack that could in theory leak path information.
17067 - Avoid an uninitialized memory read when reading a vote or consensus
17068 document that has an unrecognized flavor name. This read could
17069 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
17070 - Try to leak less information about what relays a client is
17071 choosing to a side-channel attacker. Previously, a Tor client would
17072 stop iterating through the list of available relays as soon as it
17073 had chosen one, thus finishing a little earlier when it picked
17074 a router earlier in the list. If an attacker can recover this
17075 timing information (nontrivial but not proven to be impossible),
17076 they could learn some coarse-grained information about which relays
17077 a client was picking (middle nodes in particular are likelier to
17078 be affected than exits). The timing attack might be mitigated by
17079 other factors (see bug 6537 for some discussion), but it's best
17080 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
17083 Changes in version 0.2.3.20-rc - 2012-08-05
17084 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
17085 series. It fixes a pair of code security bugs and a potential anonymity
17086 issue, updates our RPM spec files, and cleans up other smaller issues.
17089 - Avoid read-from-freed-memory and double-free bugs that could occur
17090 when a DNS request fails while launching it. Fixes bug 6480;
17091 bugfix on 0.2.0.1-alpha.
17092 - Avoid an uninitialized memory read when reading a vote or consensus
17093 document that has an unrecognized flavor name. This read could
17094 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
17095 - Try to leak less information about what relays a client is
17096 choosing to a side-channel attacker. Previously, a Tor client would
17097 stop iterating through the list of available relays as soon as it
17098 had chosen one, thus finishing a little earlier when it picked
17099 a router earlier in the list. If an attacker can recover this
17100 timing information (nontrivial but not proven to be impossible),
17101 they could learn some coarse-grained information about which relays
17102 a client was picking (middle nodes in particular are likelier to
17103 be affected than exits). The timing attack might be mitigated by
17104 other factors (see bug 6537 for some discussion), but it's best
17105 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
17108 - Try to make the warning when giving an obsolete SOCKSListenAddress
17109 a little more useful.
17110 - Terminate active server managed proxies if Tor stops being a
17111 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
17112 - Provide a better error message about possible OSX Asciidoc failure
17113 reasons. Fixes bug 6436.
17114 - Warn when Tor is configured to use accounting in a way that can
17115 link a hidden service to some other hidden service or public
17116 address. Resolves ticket 6490.
17119 - Check return value of fputs() when writing authority certificate
17120 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
17121 - Ignore ServerTransportPlugin lines when Tor is not configured as
17122 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
17123 - When disabling guards for having too high a proportion of failed
17124 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
17128 - Update our default RPM spec files to work with mock and rpmbuild
17129 on RHEL/Fedora. They have an updated set of dependencies and
17130 conflicts, a fix for an ancient typo when creating the "_tor"
17131 user, and better instructions. Thanks to Ondrej Mikle for the
17132 patch series. Fixes bug 6043.
17135 - Make it possible to set the TestingTorNetwork configuration
17136 option using AlternateDirAuthority and AlternateBridgeAuthority
17137 as an alternative to setting DirServer. Addresses ticket 6377.
17140 - Clarify the documentation for the Alternate*Authority options.
17142 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
17144 o Code simplification and refactoring:
17145 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
17146 10 lines. Also, don't nest them. Doing so in the past has
17147 led to hard-to-debug code. The new style is to use the
17148 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
17151 Changes in version 0.2.3.19-rc - 2012-07-06
17152 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
17153 series. It fixes the compile on Windows, reverts to a GeoIP database
17154 that isn't as broken, and fixes a flow control bug that has been around
17155 since the beginning of Tor.
17158 - Fix a bug handling SENDME cells on nonexistent streams that could
17159 result in bizarre window values. Report and patch contributed
17160 pseudonymously. Fixes part of bug 6271. This bug was introduced
17161 before the first Tor release, in svn commit r152.
17162 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
17163 June 2012 database, Maxmind marked many Tor relays as country "A1",
17164 which will cause risky behavior for clients that set EntryNodes
17165 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
17166 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
17167 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
17170 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
17171 bugfix on 0.2.1.10-alpha.
17174 Changes in version 0.2.3.18-rc - 2012-06-28
17175 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
17176 series. It fixes a few smaller bugs, but generally appears stable.
17177 Please test it and let us know whether it is!
17180 - Allow wildcarded mapaddress targets to be specified on the
17181 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
17182 - Make our linker option detection code more robust against linkers
17183 such as on FreeBSD 8, where a bad combination of options completes
17184 successfully but makes an unrunnable binary. Fixes bug 6173;
17185 bugfix on 0.2.3.17-beta.
17187 o Minor bugfixes (on 0.2.2.x and earlier):
17188 - Avoid a false positive in the util/threads unit test by increasing
17189 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
17190 - Replace "Sending publish request" log messages with "Launching
17191 upload", so that they no longer confusingly imply that we're
17192 sending something to a directory we might not even be connected
17193 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
17194 - Make sure to set *socket_error in all error cases in
17195 connection_connect(), so it can't produce a warning about
17196 errno being zero from errno_to_orconn_end_reason(). Bugfix on
17197 0.2.1.1-alpha; resolves ticket 6028.
17198 - Downgrade "Got a certificate, but we already have it" log messages
17199 from warning to info, except when we're a dirauth. Fixes bug 5238;
17200 bugfix on 0.2.1.7-alpha.
17201 - When checking for requested signatures on the latest consensus
17202 before serving it to a client, make sure to check the right
17203 consensus flavor. Bugfix on 0.2.2.6-alpha.
17204 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
17205 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
17207 o Minor bugfixes (on 0.2.3.x):
17208 - Make format_helper_exit_status() avoid unnecessary space padding
17209 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
17211 - Downgrade a message about cleaning the microdescriptor cache to
17212 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
17213 - Log a BUG message at severity INFO if we have a networkstatus with
17214 a missing entry for some microdescriptor. Continues on a patch
17216 - Improve the log message when a managed proxy fails to launch. Fixes
17217 bug 5099; bugfix on 0.2.3.6-alpha.
17218 - Don't do DNS lookups when parsing corrupted managed proxy protocol
17219 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
17220 - When formatting wildcarded address mappings for the controller,
17221 be sure to include "*." as appropriate. Partially fixes bug 6244;
17222 bugfix on 0.2.3.9-alpha.
17223 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
17224 Bugfix on 0.2.3.13-alpha.
17225 - Stop logging messages about running with circuit timeout learning
17226 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
17227 - Disable a spurious warning about reading on a marked and flushing
17228 connection. We shouldn't be doing that, but apparently we
17229 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
17230 - Fix a bug that stopped AllowDotExit from working on addresses
17231 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
17234 o Code simplification, refactoring, unit tests:
17235 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
17236 Libevent's notion of cached time when possible.
17237 - Remove duplicate code for invoking getrlimit() from control.c.
17238 - Add a unit test for the environment_variable_names_equal function.
17241 - Document the --defaults-torrc option, and the new (in 0.2.3)
17242 semantics for overriding, extending, and clearing lists of
17243 options. Closes bug 4748.
17246 Changes in version 0.2.3.17-beta - 2012-06-15
17247 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
17248 gets our TLS handshake back on track for being able to blend in with
17249 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
17250 with Vidalia, and otherwise continues to get us closer to a release
17254 - Enable gcc and ld hardening by default. Resolves ticket 5210.
17255 - Update TLS cipher list to match Firefox 8 and later. Resolves
17257 - Implement the client side of proposal 198: remove support for
17258 clients falsely claiming to support standard ciphersuites that
17259 they can actually provide. As of modern OpenSSL versions, it's not
17260 necessary to fake any standard ciphersuite, and doing so prevents
17261 us from using better ciphersuites in the future, since servers
17262 can't know whether an advertised ciphersuite is really supported or
17263 not. Some hosts -- notably, ones with very old versions of OpenSSL
17264 or where OpenSSL has been built with ECC disabled -- will stand
17265 out because of this change; TBB users should not be affected.
17268 - Change the default value for DynamicDHGroups (introduced in
17269 0.2.3.9-alpha) to 0. This feature can make Tor relays less
17270 identifiable by their use of the mod_ssl DH group, but at
17271 the cost of some usability (#4721) and bridge tracing (#6087)
17272 regressions. Resolves ticket 5598.
17273 - Send a CRLF at the end of each STATUS_* control protocol event. This
17274 bug tickled a bug in Vidalia which would make it freeze. Fixes
17275 bug 6094; bugfix on 0.2.3.16-alpha.
17278 - Disable writing on marked-for-close connections when they are
17279 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
17280 bug 5263; bugfix on 0.0.2pre13, where we first added a special
17281 case for flushing marked connections.
17282 - Detect SSL handshake even when the initial attempt to write the
17283 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
17284 - Change the AllowDotExit rules so they should actually work.
17285 We now enforce AllowDotExit only immediately after receiving an
17286 address via SOCKS or DNSPort: other sources are free to provide
17287 .exit addresses after the resolution occurs. Fixes bug 3940;
17288 bugfix on 0.2.2.1-alpha.
17289 - Fix a (harmless) integer overflow in cell statistics reported by
17290 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
17291 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
17292 right places and never depends on the consensus parameters or
17293 computes adaptive timeouts when it is disabled. Fixes bug 5049;
17294 bugfix on 0.2.2.14-alpha.
17295 - When building Tor on Windows with -DUNICODE (not default), ensure
17296 that error messages, filenames, and DNS server names are always
17297 NUL-terminated when we convert them to a single-byte encoding.
17298 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
17299 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
17300 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
17301 - Fix an edge case where TestingTorNetwork is set but the authorities
17302 and relays all have an uptime of zero, where the private Tor network
17303 could briefly lack support for hidden services. Fixes bug 3886;
17304 bugfix on 0.2.2.18-alpha.
17305 - Correct the manpage's descriptions for the default values of
17306 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
17308 - Fix the documentation for the --hush and --quiet command line
17309 options, which changed their behavior back in 0.2.3.3-alpha.
17310 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
17314 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
17315 more information to it, so that we can track it down in case it
17316 returns again. Mitigates bug 5235.
17317 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
17318 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
17319 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
17320 - Warn the user when HTTPProxy, but no other proxy type, is
17321 configured. This can cause surprising behavior: it doesn't send
17322 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
17323 directory traffic only. Resolves ticket 4663.
17324 - Issue a notice if a guard completes less than 40% of your circuits.
17325 Threshold is configurable by torrc option PathBiasNoticeRate and
17326 consensus parameter pb_noticepct. There is additional, off-by-
17327 default code to disable guards which fail too many circuits.
17328 Addresses ticket 5458.
17329 - Update to the June 6 2012 Maxmind GeoLite Country database.
17331 o Code simplifications and refactoring:
17332 - Remove validate_pluggable_transports_config(): its warning
17333 message is now handled by connection_or_connect().
17336 Changes in version 0.2.2.37 - 2012-06-06
17337 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
17338 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
17342 - Work around a bug in OpenSSL that broke renegotiation with TLS
17343 1.1 and TLS 1.2. Without this workaround, all attempts to speak
17344 the v2 Tor connection protocol when both sides were using OpenSSL
17345 1.0.1 would fail. Resolves ticket 6033.
17346 - When waiting for a client to renegotiate, don't allow it to add
17347 any bytes to the input buffer. This fixes a potential DoS issue.
17348 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
17349 - Fix an edge case where if we fetch or publish a hidden service
17350 descriptor, we might build a 4-hop circuit and then use that circuit
17351 for exiting afterwards -- even if the new last hop doesn't obey our
17352 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
17355 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
17356 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
17359 - Tell GCC and Clang to check for any errors in format strings passed
17360 to the tor_v*(print|scan)f functions.
17363 Changes in version 0.2.3.16-alpha - 2012-06-05
17364 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
17365 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
17366 currently). It also fixes a variety of smaller bugs and other cleanups
17367 that get us closer to a release candidate.
17369 o Major bugfixes (general):
17370 - Work around a bug in OpenSSL that broke renegotiation with TLS
17371 1.1 and TLS 1.2. Without this workaround, all attempts to speak
17372 the v2 Tor connection protocol when both sides were using OpenSSL
17373 1.0.1 would fail. Resolves ticket 6033.
17374 - When waiting for a client to renegotiate, don't allow it to add
17375 any bytes to the input buffer. This fixes a potential DoS issue.
17376 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
17377 - Pass correct OR address to managed proxies (like obfsproxy),
17378 even when ORListenAddress is used. Fixes bug 4865; bugfix on
17380 - The advertised platform of a router now includes only its operating
17381 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
17382 service pack level (for Windows) or its CPU architecture (for Unix).
17383 We also no longer include the "git-XYZ" tag in the version. Resolves
17386 o Major bugfixes (clients):
17387 - If we are unable to find any exit that supports our predicted ports,
17388 stop calling them predicted, so that we don't loop and build
17389 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
17390 which introduced predicted ports.
17391 - Fix an edge case where if we fetch or publish a hidden service
17392 descriptor, we might build a 4-hop circuit and then use that circuit
17393 for exiting afterwards -- even if the new last hop doesn't obey our
17394 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
17395 - Check at each new consensus whether our entry guards were picked
17396 long enough ago that we should rotate them. Previously, we only
17397 did this check at startup, which could lead to us holding a guard
17398 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
17399 - When fetching a bridge descriptor from a bridge authority,
17400 always do so anonymously, whether we have been able to open
17401 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
17402 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
17403 but we'll need to wait for bug 6010 before it's actually usable.
17405 o Major bugfixes (directory authorities):
17406 - When computing weight parameters, behave more robustly in the
17407 presence of a bad bwweightscale value. Previously, the authorities
17408 would crash if they agreed on a sufficiently broken weight_scale
17409 value: now, they use a reasonable default and carry on. Partial
17410 fix for 5786; bugfix on 0.2.2.17-alpha.
17411 - Check more thoroughly to prevent a rogue authority from
17412 double-voting on any consensus directory parameter. Previously,
17413 authorities would crash in this case if the total number of
17414 votes for any parameter exceeded the number of active voters,
17415 but would let it pass otherwise. Partial fix for bug 5786; bugfix
17419 - Rate-limit log messages when asked to connect anonymously to
17420 a private address. When these hit, they tended to hit fast and
17421 often. Also, don't bother trying to connect to addresses that we
17422 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
17423 reply makes us think we have been lied to, even when the address the
17424 client tried to connect to was "localhost." Resolves ticket 2822.
17425 - Allow packagers to insert an extra string in server descriptor
17426 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
17427 Resolves the rest of ticket 2988.
17428 - Raise the threshold of server descriptors needed (75%) and exit
17429 server descriptors needed (50%) before we will declare ourselves
17430 bootstrapped. This will make clients start building circuits a
17431 little later, but makes the initially constructed circuits less
17432 skewed and less in conflict with further directory fetches. Fixes
17434 - Close any connection that sends unrecognized junk before the
17435 handshake. Solves an issue noted in bug 4369.
17436 - Improve log messages about managed transports. Resolves ticket 5070.
17437 - Tag a bridge's descriptor as "never to be sent unencrypted".
17438 This shouldn't matter, since bridges don't open non-anonymous
17439 connections to the bridge authority and don't allow unencrypted
17440 directory connections from clients, but we might as well make
17441 sure. Closes bug 5139.
17442 - Expose our view of whether we have gone dormant to the controller,
17443 via a new "GETINFO dormant" value. Torbutton and other controllers
17444 can use this to avoid doing periodic requests through Tor while
17445 it's dormant (bug 4718). Fixes bug 5954.
17446 - Tell GCC and Clang to check for any errors in format strings passed
17447 to the tor_v*(print|scan)f functions.
17448 - Update to the May 1 2012 Maxmind GeoLite Country database.
17450 o Minor bugfixes (already included in 0.2.2.36):
17451 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
17452 Fixes bug 5346; bugfix on 0.0.8pre3.
17453 - Correct parsing of certain date types in parse_http_time().
17454 Without this patch, If-Modified-Since would behave
17455 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
17456 Esteban Manchado Velázques.
17457 - Make our number-parsing functions always treat too-large values
17458 as an error, even when those values exceed the width of the
17459 underlying type. Previously, if the caller provided these
17460 functions with minima or maxima set to the extreme values of the
17461 underlying integer type, these functions would return those
17462 values on overflow rather than treating overflow as an error.
17463 Fixes part of bug 5786; bugfix on 0.0.9.
17464 - If we hit the error case where routerlist_insert() replaces an
17465 existing (old) server descriptor, make sure to remove that
17466 server descriptor from the old_routers list. Fix related to bug
17467 1776. Bugfix on 0.2.2.18-alpha.
17468 - Clarify the behavior of MaxCircuitDirtiness with hidden service
17469 circuits. Fixes issue 5259.
17471 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
17472 - Prevent a null-pointer dereference when receiving a data cell
17473 for a nonexistent stream when the circuit in question has an
17474 empty deliver window. We don't believe this is triggerable,
17475 since we don't currently allow deliver windows to become empty,
17476 but the logic is tricky enough that it's better to make the code
17477 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
17478 - Fix a memory leak when trying to launch a DNS request when the
17479 network is disabled or the nameservers are unconfigurable. Fixes
17480 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
17481 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
17482 - Don't hold a Windows file handle open for every file mapping;
17483 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
17485 - Avoid O(n^2) performance characteristics when parsing a large
17486 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
17487 - Format more doubles with %f, not %lf. Patch from grarpamp to make
17488 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
17490 - Make our replacement implementation of strtok_r() compatible with
17491 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
17492 bugfix on 0.2.2.1-alpha.
17493 - Fix a NULL-pointer dereference on a badly formed
17494 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
17495 bugfix on 0.2.2.9-alpha.
17496 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
17497 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
17498 - Defensively refactor rend_mid_rendezvous() so that protocol
17499 violations and length checks happen in the beginning. Fixes
17501 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
17502 that IPv6 stuff will compile on MSVC, and compilation issues
17503 will be easier to track down. Fixes bug 5861.
17505 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
17506 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
17507 resource exhaustion, so that clients can adjust their load to
17508 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
17509 started using END_STREAM_REASON_RESOURCELIMIT.
17510 - Don't check for whether the address we're using for outbound
17511 connections has changed until after the outbound connection has
17512 completed. On Windows, getsockname() doesn't succeed until the
17513 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
17514 - If the configuration tries to set MyFamily on a bridge, refuse to
17515 do so, and warn about the security implications. Fixes bug 4657;
17516 bugfix on 0.2.0.3-alpha.
17517 - If the client fails to set a reasonable set of ciphersuites
17518 during its v2 handshake renegotiation, allow the renegotiation to
17519 continue nevertheless (i.e. send all the required certificates).
17520 Fixes bug 4591; bugfix on 0.2.0.20-rc.
17521 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
17522 option is set to 0 (which Vidalia version 0.2.16 now does when
17523 a SAVECONF attempt fails), perform other actions that SIGHUP
17524 usually causes (like reopening the logs). Fixes bug 5095; bugfix
17526 - If we fail to write a microdescriptor to the disk cache, do not
17527 continue replacing the old microdescriptor file. Fixes bug 2954;
17528 bugfix on 0.2.2.6-alpha.
17529 - Exit nodes don't need to fetch certificates for authorities that
17530 they don't recognize; only directory authorities, bridges,
17531 and caches need to do that. Fixes part of bug 2297; bugfix on
17533 - Correctly handle checking the permissions on the parent
17534 directory of a control socket in the root directory. Bug found
17535 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
17537 - When told to add a bridge with the same digest as a preexisting
17538 bridge but a different addr:port, change the addr:port as
17539 requested. Previously we would not notice the change. Fixes half
17540 of bug 5603; fix on 0.2.2.26-beta.
17541 - End AUTHCHALLENGE error messages (in the control protocol) with
17542 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
17544 o Minor bugfixes (on 0.2.3.x):
17545 - Turn an assertion (that the number of handshakes received as a
17546 server is not < 1) into a warning. Fixes bug 4873; bugfix on
17548 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
17549 we had reversed them when the answer was cached.) Fixes bug
17550 5723; bugfix on 0.2.3.1-alpha.
17551 - Work correctly on Linux systems with accept4 support advertised in
17552 their headers, but without accept4 support in the kernel. Fix
17553 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
17554 - When told to add a bridge with the same addr:port as a preexisting
17555 bridge but a different transport, change the transport as
17556 requested. Previously we would not notice the change. Fixes half
17557 of bug 5603; fix on 0.2.3.2-alpha.
17558 - Avoid a "double-reply" warning when replying to a SOCKS request
17559 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
17560 bugfix on 0.2.3.4-alpha.
17561 - Fix a bug where a bridge authority crashes if it has seen no
17562 directory requests when it's time to write statistics to disk.
17563 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
17565 - Don't try to open non-control listeners when DisableNetwork is set.
17566 Previously, we'd open all listeners, then immediately close them.
17567 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
17568 - Don't abort the managed proxy protocol if the managed proxy
17569 sends us an unrecognized line; ignore it instead. Fixes bug
17570 5910; bugfix on 0.2.3.9-alpha.
17571 - Fix a compile warning in crypto.c when compiling with clang 3.1.
17572 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
17573 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
17574 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
17575 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
17576 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
17577 - Resolve numerous small warnings and build issues with MSVC. Resolves
17580 o Documentation fixes:
17581 - Improve the manual's documentation for the NT Service command-line
17582 options. Addresses ticket 3964.
17583 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
17584 - Document the changes to the ORPort and DirPort options, and the
17585 fact that {OR/Dir}ListenAddress is now unnecessary (and
17586 therefore deprecated). Resolves ticket 5597.
17589 - Remove the torrc.bridge file: we don't use it for anything, and
17590 it had become badly desynchronized from torrc.sample. Resolves
17594 Changes in version 0.2.2.36 - 2012-05-24
17595 Tor 0.2.2.36 updates the addresses for two of the eight directory
17596 authorities, fixes some potential anonymity and security issues,
17597 and fixes several crash bugs.
17599 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
17600 known flaws, and nobody should be using them. You should upgrade. If
17601 you're using a Linux or BSD and its packages are obsolete, stop using
17602 those packages and upgrade anyway.
17604 o Directory authority changes:
17605 - Change IP address for maatuska (v3 directory authority).
17606 - Change IP address for ides (v3 directory authority), and rename
17610 - When building or running with any version of OpenSSL earlier
17611 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
17612 versions have a bug (CVE-2011-4576) in which their block cipher
17613 padding includes uninitialized data, potentially leaking sensitive
17614 information to any peer with whom they make a SSLv3 connection. Tor
17615 does not use SSL v3 by default, but a hostile client or server
17616 could force an SSLv3 connection in order to gain information that
17617 they shouldn't have been able to get. The best solution here is to
17618 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
17619 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
17620 to make sure that the bug can't happen.
17621 - Never use a bridge or a controller-supplied node as an exit, even
17622 if its exit policy allows it. Found by wanoskarnet. Fixes bug
17623 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
17624 and 0.2.0.3-alpha (for bridge-purpose descriptors).
17625 - Only build circuits if we have a sufficient threshold of the total
17626 descriptors that are marked in the consensus with the "Exit"
17627 flag. This mitigates an attack proposed by wanoskarnet, in which
17628 all of a client's bridges collude to restrict the exit nodes that
17629 the client knows about. Fixes bug 5343.
17630 - Provide controllers with a safer way to implement the cookie
17631 authentication mechanism. With the old method, if another locally
17632 running program could convince a controller that it was the Tor
17633 process, then that program could trick the controller into telling
17634 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
17635 authentication method uses a challenge-response approach to prevent
17636 this attack. Fixes bug 5185; implements proposal 193.
17639 - Avoid logging uninitialized data when unable to decode a hidden
17640 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
17641 - Avoid a client-side assertion failure when receiving an INTRODUCE2
17642 cell on a general purpose circuit. Fixes bug 5644; bugfix on
17644 - Fix builds when the path to sed, openssl, or sha1sum contains
17645 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
17647 - Correct our replacements for the timeradd() and timersub() functions
17648 on platforms that lack them (for example, Windows). The timersub()
17649 function is used when expiring circuits, while timeradd() is
17650 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
17651 bugfix on 0.2.2.24-alpha.
17652 - Fix the SOCKET_OK test that we use to tell when socket
17653 creation fails so that it works on Win64. Fixes part of bug 4533;
17654 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
17657 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
17658 Fixes bug 5346; bugfix on 0.0.8pre3.
17659 - Make our number-parsing functions always treat too-large values
17660 as an error, even when those values exceed the width of the
17661 underlying type. Previously, if the caller provided these
17662 functions with minima or maxima set to the extreme values of the
17663 underlying integer type, these functions would return those
17664 values on overflow rather than treating overflow as an error.
17665 Fixes part of bug 5786; bugfix on 0.0.9.
17666 - Older Linux kernels erroneously respond to strange nmap behavior
17667 by having accept() return successfully with a zero-length
17668 socket. When this happens, just close the connection. Previously,
17669 we would try harder to learn the remote address: but there was
17670 no such remote address to learn, and our method for trying to
17671 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
17672 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
17673 - Correct parsing of certain date types in parse_http_time().
17674 Without this patch, If-Modified-Since would behave
17675 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
17676 Esteban Manchado Velázques.
17677 - Change the BridgePassword feature (part of the "bridge community"
17678 design, which is not yet implemented) to use a time-independent
17679 comparison. The old behavior might have allowed an adversary
17680 to use timing to guess the BridgePassword value. Fixes bug 5543;
17681 bugfix on 0.2.0.14-alpha.
17682 - Detect and reject certain misformed escape sequences in
17683 configuration values. Previously, these values would cause us
17684 to crash if received in a torrc file or over an authenticated
17685 control port. Bug found by Esteban Manchado Velázquez, and
17686 independently by Robert Connolly from Matta Consulting who further
17687 noted that it allows a post-authentication heap overflow. Patch
17688 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
17689 bugfix on 0.2.0.16-alpha.
17690 - Fix a compile warning when using the --enable-openbsd-malloc
17691 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
17692 - During configure, detect when we're building with clang version
17693 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
17694 CFLAGS. clang doesn't support them yet.
17695 - When sending an HTTP/1.1 proxy request, include a Host header.
17696 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
17697 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
17698 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
17699 - If we hit the error case where routerlist_insert() replaces an
17700 existing (old) server descriptor, make sure to remove that
17701 server descriptor from the old_routers list. Fix related to bug
17702 1776. Bugfix on 0.2.2.18-alpha.
17704 o Minor bugfixes (documentation and log messages):
17705 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
17706 Fixes bug 4856; bugfix on Tor 0.0.6.
17707 - Update "ClientOnly" man page entry to explain that there isn't
17708 really any point to messing with it. Resolves ticket 5005.
17709 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
17710 directory authority option (introduced in Tor 0.2.2.34).
17711 - Downgrade the "We're missing a certificate" message from notice
17712 to info: people kept mistaking it for a real problem, whereas it
17713 is seldom the problem even when we are failing to bootstrap. Fixes
17714 bug 5067; bugfix on 0.2.0.10-alpha.
17715 - Correctly spell "connect" in a log message on failure to create a
17716 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
17717 - Clarify the behavior of MaxCircuitDirtiness with hidden service
17718 circuits. Fixes issue 5259.
17721 - Directory authorities now reject versions of Tor older than
17722 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
17723 inclusive. These versions accounted for only a small fraction of
17724 the Tor network, and have numerous known security issues. Resolves
17726 - Update to the May 1 2012 Maxmind GeoLite Country database.
17729 - When sending or relaying a RELAY_EARLY cell, we used to convert
17730 it to a RELAY cell if the connection was using the v1 link
17731 protocol. This was a workaround for older versions of Tor, which
17732 didn't handle RELAY_EARLY cells properly. Now that all supported
17733 versions can handle RELAY_EARLY cells, and now that we're enforcing
17734 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
17735 remove this workaround. Addresses bug 4786.
17738 Changes in version 0.2.3.15-alpha - 2012-04-30
17739 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
17740 the development branch build on Windows again.
17742 o Minor bugfixes (on 0.2.2.x and earlier):
17743 - Make sure that there are no unhandled pending TLS errors before
17744 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
17745 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
17746 Bugfix on 0.1.0.5-rc; fixes bug 4528.
17747 - Fix an assert that directory authorities could trigger on sighup
17748 during some configuration state transitions. We now don't treat
17749 it as a fatal error when the new descriptor we just generated in
17750 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
17751 - After we pick a directory mirror, we would refuse to use it if
17752 it's in our ExcludeExitNodes list, resulting in mysterious failures
17753 to bootstrap for people who just wanted to avoid exiting from
17754 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
17755 - When building with --enable-static-tor on OpenBSD, do not
17756 erroneously attempt to link -lrt. Fixes bug 5103.
17758 o Minor bugfixes (on 0.2.3.x):
17759 - When Tor is built with kernel headers from a recent (last few
17760 years) Linux kernel, do not fail to run on older (pre-2.6.28
17761 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
17762 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
17763 and 0.2.3.12-alpha.
17764 - Fix compilation with miniupnpc version 1.6; patch from
17765 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
17766 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
17767 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
17768 - Fix compilation on platforms without unistd.h, or where environ
17769 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
17772 - Directory authorities are now a little more lenient at accepting
17773 older router descriptors, or newer router descriptors that don't
17774 make big changes. This should help ameliorate past and future
17775 issues where routers think they have uploaded valid descriptors,
17776 but the authorities don't think so. Fix for ticket 2479.
17777 - Make the code that clients use to detect an address change be
17778 IPv6-aware, so that it won't fill clients' logs with error
17779 messages when trying to get the IPv4 address of an IPv6
17780 connection. Implements ticket 5537.
17782 o Removed features:
17783 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
17784 authorities needed to use it for a while to keep the network working
17785 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
17786 that was six months ago. As of now, it should no longer be needed
17790 Changes in version 0.2.3.14-alpha - 2012-04-23
17791 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
17792 candidate. It also dramatically speeds up AES: fast relays should
17793 consider switching to the newer OpenSSL library.
17795 o Directory authority changes:
17796 - Change IP address for ides (v3 directory authority), and rename
17800 - Avoid logging uninitialized data when unable to decode a hidden
17801 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
17802 - Avoid a client-side assertion failure when receiving an INTRODUCE2
17803 cell on a general purpose circuit. Fixes bug 5644; bugfix on
17805 - If authorities are unable to get a v2 consensus document from other
17806 directory authorities, they no longer fall back to fetching
17807 them from regular directory caches. Fixes bug 5635; bugfix on
17808 0.2.2.26-beta, where routers stopped downloading v2 consensus
17809 documents entirely.
17810 - When we start a Tor client with a normal consensus already cached,
17811 be willing to download a microdescriptor consensus. Fixes bug 4011;
17812 fix on 0.2.3.1-alpha.
17814 o Major features (performance):
17815 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
17816 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
17817 vectorized AES implementations as appropriate. These can be much,
17818 much faster than other AES implementations.
17820 o Minor bugfixes (0.2.2.x and earlier):
17821 - Don't launch more than 10 service-side introduction-point circuits
17822 for a hidden service in five minutes. Previously, we would consider
17823 launching more introduction-point circuits if at least one second
17824 had passed without any introduction-point circuits failing. Fixes
17825 bug 4607; bugfix on 0.0.7pre1.
17826 - Change the BridgePassword feature (part of the "bridge community"
17827 design, which is not yet implemented) to use a time-independent
17828 comparison. The old behavior might have allowed an adversary
17829 to use timing to guess the BridgePassword value. Fixes bug 5543;
17830 bugfix on 0.2.0.14-alpha.
17831 - Enforce correct return behavior of tor_vsscanf() when the '%%'
17832 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
17833 - When sending an HTTP/1.1 proxy request, include a Host header.
17834 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
17835 - Don't log that we have "decided to publish new relay descriptor"
17836 unless we are actually publishing a descriptor. Fixes bug 3942;
17837 bugfix on 0.2.2.28-beta.
17839 o Minor bugfixes (0.2.3.x):
17840 - Fix a bug where a bridge authority crashes (on a failed assert)
17841 if it has seen no directory requests when it's time to write
17842 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
17843 - Fix bug stomping on ORPort option NoListen and ignoring option
17844 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
17845 - In the testsuite, provide a large enough buffer in the tor_sscanf
17846 unit test. Otherwise we'd overrun that buffer and crash during
17847 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
17849 - Make sure we create the keys directory if it doesn't exist and we're
17850 about to store the dynamic Diffie-Hellman parameters. Fixes bug
17851 5572; bugfix on 0.2.3.13-alpha.
17852 - Fix a small memory leak when trying to decode incorrect base16
17853 authenticator during SAFECOOKIE authentication. Found by
17854 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
17857 - Add more information to a log statement that might help track down
17858 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
17859 non-IP address" messages (or any Bug messages, for that matter!),
17860 please let us know about it.
17861 - Relays now understand an IPv6 address when they get one from a
17862 directory server. Resolves ticket 4875.
17863 - Resolve IPv6 addresses in bridge and entry statistics to country
17864 code "??" which means we at least count them. Resolves ticket 5053;
17865 improves on 0.2.3.9-alpha.
17866 - Update to the April 3 2012 Maxmind GeoLite Country database.
17867 - Begin a doc/state-contents.txt file to explain the contents of
17868 the Tor state file. Fixes bug 2987.
17870 o Default torrc changes:
17871 - Stop listing "socksport 9050" in torrc.sample. We open a socks
17872 port on 9050 by default anyway, so this should not change anything
17874 - Stop mentioning the deprecated *ListenAddress options in
17875 torrc.sample. Fixes bug 5438.
17876 - Document unit of bandwidth related options in sample torrc.
17879 o Removed features:
17880 - The "torify" script no longer supports the "tsocks" socksifier
17881 tool, since tsocks doesn't support DNS and UDP right for Tor.
17882 Everyone should be using torsocks instead. Fixes bugs 3530 and
17883 5180. Based on a patch by "ugh".
17885 o Code refactoring:
17886 - Change the symmetric cipher interface so that creating and
17887 initializing a stream cipher are no longer separate functions.
17888 - Remove all internal support for unpadded RSA. We never used it, and
17889 it would be a bad idea to start.
17892 Changes in version 0.2.3.13-alpha - 2012-03-26
17893 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
17894 in managed pluggable transports, as well as providing other cleanups
17895 that get us closer to a release candidate.
17897 o Directory authority changes:
17898 - Change IP address for maatuska (v3 directory authority).
17901 - Provide controllers with a safer way to implement the cookie
17902 authentication mechanism. With the old method, if another locally
17903 running program could convince a controller that it was the Tor
17904 process, then that program could trick the controller into telling
17905 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
17906 authentication method uses a challenge-response approach to prevent
17907 this attack. Fixes bug 5185, implements proposal 193.
17908 - Never use a bridge or a controller-supplied node as an exit, even
17909 if its exit policy allows it. Found by wanoskarnet. Fixes bug
17910 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
17911 and 0.2.0.3-alpha (for bridge-purpose descriptors).
17912 - Only build circuits if we have a sufficient threshold of the total
17913 descriptors that are marked in the consensus with the "Exit"
17914 flag. This mitigates an attack proposed by wanoskarnet, in which
17915 all of a client's bridges collude to restrict the exit nodes that
17916 the client knows about. Fixes bug 5343.
17918 o Major bugfixes (on Tor 0.2.3.x):
17919 - Avoid an assert when managed proxies like obfsproxy are configured,
17920 and we receive HUP signals or setconf attempts too rapidly. This
17921 situation happens most commonly when Vidalia tries to attach to
17922 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
17923 bugfix on 0.2.3.6-alpha.
17924 - Fix a relay-side pluggable transports bug where managed proxies were
17925 unreachable from the Internet, because Tor asked them to bind on
17926 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
17927 - Stop discarding command-line arguments when TestingTorNetwork
17928 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
17929 0.2.3.9-alpha, where task 4552 added support for two layers of
17931 - Resume allowing the unit tests to run in gdb. This was accidentally
17932 made impossible when the DisableDebuggerAttachment option was
17933 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
17934 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
17935 0.2.3.11-alpha. Reported by Anthony G. Basile.
17937 o Minor bugfixes (on 0.2.2.x and earlier):
17938 - Ensure we don't cannibalize circuits that are longer than three hops
17939 already, so we don't end up making circuits with 5 or more
17940 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
17941 0.1.0.1-rc which introduced cannibalization.
17942 - Detect and reject certain misformed escape sequences in
17943 configuration values. Previously, these values would cause us
17944 to crash if received in a torrc file or over an authenticated
17945 control port. Bug found by Esteban Manchado Velázquez, and
17946 independently by Robert Connolly from Matta Consulting who further
17947 noted that it allows a post-authentication heap overflow. Patch
17948 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
17949 bugfix on 0.2.0.16-alpha.
17950 - Fix a compile warning when using the --enable-openbsd-malloc
17951 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
17952 - Directory caches no longer refuse to clean out descriptors because
17953 of missing v2 networkstatus documents, unless they're configured
17954 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
17955 0.2.2.26-beta. Patch by Daniel Bryg.
17956 - Update to the latest version of the tinytest unit testing framework.
17957 This includes a couple of bugfixes that can be relevant for
17958 running forked unit tests on Windows, and removes all reserved
17961 o Minor bugfixes (on 0.2.3.x):
17962 - On a failed pipe() call, don't leak file descriptors. Fixes bug
17963 4296; bugfix on 0.2.3.1-alpha.
17964 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
17965 until after we have received a CERTS cell. Fixes bug 4361; bugfix
17966 on 0.2.3.6-alpha. Patch by "frosty".
17967 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
17968 option, so that the IP stack doesn't decide to use it for IPv4
17969 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
17970 - Ensure that variables set in Tor's environment cannot override
17971 environment variables that Tor passes to a managed
17972 pluggable-transport proxy. Previously, Tor would pass every
17973 variable in its environment to managed proxies along with the new
17974 ones, in such a way that on many operating systems, the inherited
17975 environment variables would override those which Tor tried to
17976 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
17977 bugfix on 0.2.3.9-alpha for Windows.
17980 - A wide variety of new unit tests by Esteban Manchado Velázquez.
17981 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
17982 - Update to the March 6 2012 Maxmind GeoLite Country database.
17985 Changes in version 0.2.3.12-alpha - 2012-02-13
17986 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
17987 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
17988 when Tor is configured to use a pluggable transport like obfsproxy.
17991 - Fix builds when the path to sed, openssl, or sha1sum contains
17992 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
17994 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
17995 connections. This change should allow busy exit relays to stop
17996 running out of available sockets as quickly. Fixes bug 4950;
17997 bugfix on 0.2.2.26-beta.
17998 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
17999 would ask the bridge for microdescriptors, which are only supported
18000 in 0.2.3.x, and then fail to bootstrap when it didn't get the
18001 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
18002 - Properly set up obfsproxy's environment when in managed mode. The
18003 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
18004 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
18005 5076 and 5082; bugfix on 0.2.3.6-alpha.
18008 - Use the dead_strip option when building Tor on OS X. This reduces
18009 binary size by almost 19% when linking openssl and libevent
18010 statically, which we do for Tor Browser Bundle.
18011 - Fix broken URLs in the sample torrc file, and tell readers about
18012 the OutboundBindAddress, ExitPolicyRejectPrivate, and
18013 PublishServerDescriptor options. Addresses bug 4652.
18014 - Update to the February 7 2012 Maxmind GeoLite Country database.
18017 - Downgrade the "We're missing a certificate" message from notice
18018 to info: people kept mistaking it for a real problem, whereas it
18019 is seldom the problem even when we are failing to bootstrap. Fixes
18020 bug 5067; bugfix on 0.2.0.10-alpha.
18021 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
18022 managed pluggable transport server proxy's environment.
18023 Previously, we would put it there, even though Tor doesn't
18024 implement an 'extended server port' yet, and even though Tor
18025 almost certainly isn't listening at that address. For now, we set
18026 it to an empty string to avoid crashing older obfsproxies. Bugfix
18028 - Log the heartbeat message every HeartbeatPeriod seconds, not every
18029 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
18030 0.2.3.1-alpha. Bug reported by Scott Bennett.
18031 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
18032 bugfix on 0.2.3.11-alpha.
18033 - Update "ClientOnly" man page entry to explain that there isn't
18034 really any point to messing with it. Resolves ticket 5005.
18035 - Use the correct CVE number for CVE-2011-4576 in our comments and
18036 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
18039 o Code simplifications and refactoring:
18040 - Use the _WIN32 macro throughout our code to detect Windows.
18041 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
18045 Changes in version 0.2.3.11-alpha - 2012-01-22
18046 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
18047 the last step of the plan to limit maximum circuit length, includes
18048 a wide variety of hidden service performance and correctness fixes,
18049 works around an OpenSSL security flaw if your distro is too stubborn
18050 to upgrade, and fixes a bunch of smaller issues.
18053 - Now that Tor 0.2.0.x is completely deprecated, enable the final
18054 part of "Proposal 110: Avoiding infinite length circuits" by
18055 refusing all circuit-extend requests that do not use a relay_early
18056 cell. This change helps Tor resist a class of denial-of-service
18057 attacks by limiting the maximum circuit length.
18058 - Adjust the number of introduction points that a hidden service
18059 will try to maintain based on how long its introduction points
18060 remain in use and how many introductions they handle. Fixes
18062 - Try to use system facilities for enumerating local interface
18063 addresses, before falling back to our old approach (which was
18064 binding a UDP socket, and calling getsockname() on it). That
18065 approach was scaring OS X users whose draconian firewall
18066 software warned about binding to UDP sockets, regardless of
18067 whether packets were sent. Now we try to use getifaddrs(),
18068 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
18069 system supports. Resolves ticket 1827.
18071 o Major security workaround:
18072 - When building or running with any version of OpenSSL earlier
18073 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
18074 versions have a bug (CVE-2011-4576) in which their block cipher
18075 padding includes uninitialized data, potentially leaking sensitive
18076 information to any peer with whom they make a SSLv3 connection. Tor
18077 does not use SSL v3 by default, but a hostile client or server
18078 could force an SSLv3 connection in order to gain information that
18079 they shouldn't have been able to get. The best solution here is to
18080 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
18081 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
18082 to make sure that the bug can't happen.
18085 - Fix the SOCKET_OK test that we use to tell when socket
18086 creation fails so that it works on Win64. Fixes part of bug 4533;
18087 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
18088 - Correct our replacements for the timeradd() and timersub() functions
18089 on platforms that lack them (for example, Windows). The timersub()
18090 function is used when expiring circuits, while timeradd() is
18091 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
18092 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
18093 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
18094 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
18095 bug at runtime, not compile time, because some distributions hack
18096 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
18097 on 0.2.3.9-alpha. Found by Pascal.
18099 o Minor features (controller):
18100 - Use absolute path names when reporting the torrc filename in the
18101 control protocol, so a controller can more easily find the torrc
18102 file. Resolves bug 1101.
18103 - Extend the control protocol to report flags that control a circuit's
18104 path selection in CIRC events and in replies to 'GETINFO
18105 circuit-status'. Implements part of ticket 2411.
18106 - Extend the control protocol to report the hidden service address
18107 and current state of a hidden-service-related circuit in CIRC
18108 events and in replies to 'GETINFO circuit-status'. Implements part
18110 - When reporting the path to the cookie file to the controller,
18111 give an absolute path. Resolves ticket 4881.
18112 - Allow controllers to request an event notification whenever a
18113 circuit is cannibalized or its purpose is changed. Implements
18114 part of ticket 3457.
18115 - Include the creation time of a circuit in CIRC and CIRC2
18116 control-port events and the list produced by the 'GETINFO
18117 circuit-status' control-port command.
18119 o Minor features (directory authorities):
18120 - Directory authorities now reject versions of Tor older than
18121 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
18122 inclusive. These versions accounted for only a small fraction of
18123 the Tor network, and have numerous known security issues. Resolves
18125 - Authority operators can now vote for all relays in a given
18126 set of countries to be BadDir/BadExit/Invalid/Rejected.
18127 - Provide two consensus parameters (FastFlagMinThreshold and
18128 FastFlagMaxThreshold) to control the range of allowable bandwidths
18129 for the Fast directory flag. These allow authorities to run
18130 experiments on appropriate requirements for being a "Fast" node.
18131 The AuthDirFastGuarantee config value still applies. Implements
18133 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
18134 directory authority option (introduced in Tor 0.2.2.34).
18136 o Minor features (other):
18137 - Don't disable the DirPort when we cannot exceed our AccountingMax
18138 limit during this interval because the effective bandwidthrate is
18139 low enough. This is useful in a situation where AccountMax is only
18140 used as an additional safeguard or to provide statistics.
18141 - Prepend an informative header to generated dynamic_dh_params files.
18142 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
18143 EntryNodes will have no effect. Resolves issue 2571.
18144 - Log more useful messages when we fail to disable debugger
18146 - Log which authority we're missing votes from when we go to fetch
18147 them from the other auths.
18148 - Log (at debug level) whenever a circuit's purpose is changed.
18149 - Add missing documentation for the MaxClientCircuitsPending,
18150 UseMicrodescriptors, UserspaceIOCPBuffers, and
18151 _UseFilteringSSLBufferevents options, all introduced during
18152 the 0.2.3.x series.
18153 - Update to the January 3 2012 Maxmind GeoLite Country database.
18155 o Minor bugfixes (hidden services):
18156 - Don't close hidden service client circuits which have almost
18157 finished connecting to their destination when they reach
18158 the normal circuit-build timeout. Previously, we would close
18159 introduction circuits which are waiting for an acknowledgement
18160 from the introduction point, and rendezvous circuits which have
18161 been specified in an INTRODUCE1 cell sent to a hidden service,
18162 after the normal CBT. Now, we mark them as 'timed out', and launch
18163 another rendezvous attempt in parallel. This behavior change can
18164 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
18165 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
18166 - Don't close hidden-service-side rendezvous circuits when they
18167 reach the normal circuit-build timeout. This behavior change can
18168 be disabled using the new
18169 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
18170 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
18171 - Make sure we never mark the wrong rendezvous circuit as having
18172 had its introduction cell acknowledged by the introduction-point
18173 relay. Previously, when we received an INTRODUCE_ACK cell on a
18174 client-side hidden-service introduction circuit, we might have
18175 marked a rendezvous circuit other than the one we specified in
18176 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
18177 a warning message and interfered with the hidden service
18178 connection-establishment process. Fixes bug 4759; bugfix on
18179 0.2.3.3-alpha, when we added the stream-isolation feature which
18180 might cause Tor to open multiple rendezvous circuits for the same
18182 - Don't trigger an assertion failure when we mark a new client-side
18183 hidden-service introduction circuit for close during the process
18184 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
18187 o Minor bugfixes (log messages):
18188 - Correctly spell "connect" in a log message on failure to create a
18189 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
18191 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
18192 Fixes bug 4856; bugfix on Tor 0.0.6.
18193 - Fix the log message describing how we work around discovering
18194 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
18195 4837; bugfix on 0.2.2.9-alpha.
18196 - When logging about a disallowed .exit name, do not also call it
18197 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
18199 o Minor bugfixes (build fixes):
18200 - During configure, detect when we're building with clang version
18201 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
18202 CFLAGS. clang doesn't support them yet.
18203 - During configure, search for library containing cos function as
18204 libm lives in libcore on some platforms (BeOS/Haiku). Linking
18205 against libm was hard-coded before. Fixes the first part of bug
18206 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
18208 - Detect attempts to build Tor on (as yet hypothetical) versions
18209 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
18210 fix for bug 4533. Bugfix on 0.2.2.28-beta.
18211 - Preprocessor directives should not be put inside the arguments
18212 of a macro. This would break compilation with GCC releases prior
18213 to version 3.3. We would never recommend such an old GCC version,
18214 but it is apparently required for binary compatibility on some
18215 platforms (namely, certain builds of Haiku). Fixes the other part
18216 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
18219 o Minor bugfixes (other):
18220 - Older Linux kernels erroneously respond to strange nmap behavior
18221 by having accept() return successfully with a zero-length
18222 socket. When this happens, just close the connection. Previously,
18223 we would try harder to learn the remote address: but there was
18224 no such remote address to learn, and our method for trying to
18225 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
18226 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
18227 - Fix null-pointer access that could occur if TLS allocation failed.
18228 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
18229 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
18230 accidentally been reverted.
18231 - Fix our implementation of crypto_random_hostname() so it can't
18232 overflow on ridiculously large inputs. (No Tor version has ever
18233 provided this kind of bad inputs, but let's be correct in depth.)
18234 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
18235 - Find more places in the code that should have been testing for
18236 invalid sockets using the SOCKET_OK macro. Required for a fix
18237 for bug 4533. Bugfix on 0.2.2.28-beta.
18238 - Fix an assertion failure when, while running with bufferevents, a
18239 connection finishes connecting after it is marked for close, but
18240 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
18241 - test_util_spawn_background_ok() hardcoded the expected value
18242 for ENOENT to 2. This isn't portable as error numbers are
18243 platform specific, and particularly the hurd has ENOENT at
18244 0x40000002. Construct expected string at runtime, using the correct
18245 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
18246 - Reject attempts to disable DisableDebuggerAttachment while Tor is
18247 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
18248 - Use an appropriate-width type for sockets in tor-fw-helper on
18249 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
18252 - When sending or relaying a RELAY_EARLY cell, we used to convert
18253 it to a RELAY cell if the connection was using the v1 link
18254 protocol. This was a workaround for older versions of Tor, which
18255 didn't handle RELAY_EARLY cells properly. Now that all supported
18256 versions can handle RELAY_EARLY cells, and now that we're enforcing
18257 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
18258 remove this workaround. Addresses bug 4786.
18260 o Code simplifications and refactoring:
18261 - Use OpenSSL's built-in SSL_state_string_long() instead of our
18262 own homebrewed ssl_state_to_string() replacement. Patch from
18263 Emile Snyder. Fixes bug 4653.
18264 - Use macros to indicate OpenSSL versions, so we don't need to worry
18265 about accidental hexadecimal bit shifts.
18266 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
18268 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
18269 - Use the smartlist_add_asprintf() alias more consistently.
18270 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
18271 invalid value, rather than just -1.
18272 - Rename a handful of old identifiers, mostly related to crypto
18273 structures and crypto functions. By convention, our "create an
18274 object" functions are called "type_new()", our "free an object"
18275 functions are called "type_free()", and our types indicate that
18276 they are types only with a final "_t". But a handful of older
18277 types and functions broke these rules, with function names like
18278 "type_create" or "subsystem_op_type", or with type names like
18282 Changes in version 0.2.3.10-alpha - 2011-12-16
18283 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
18284 Tor's buffers code. Absolutely everybody should upgrade.
18286 The bug relied on an incorrect calculation when making data continuous
18287 in one of our IO buffers, if the first chunk of the buffer was
18288 misaligned by just the wrong amount. The miscalculation would allow an
18289 attacker to overflow a piece of heap-allocated memory. To mount this
18290 attack, the attacker would need to either open a SOCKS connection to
18291 Tor's SocksPort (usually restricted to localhost), or target a Tor
18292 instance configured to make its connections through a SOCKS proxy
18293 (which Tor does not do by default).
18295 Good security practice requires that all heap-overflow bugs should be
18296 presumed to be exploitable until proven otherwise, so we are treating
18297 this as a potential code execution attack. Please upgrade immediately!
18298 This bug does not affect bufferevents-based builds of Tor. Special
18299 thanks to "Vektor" for reporting this issue to us!
18301 This release also contains a few minor bugfixes for issues discovered
18305 - Fix a heap overflow bug that could occur when trying to pull
18306 data into the first chunk of a buffer, when that chunk had
18307 already had some data drained from it. Fixes CVE-2011-2778;
18308 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
18311 - If we can't attach streams to a rendezvous circuit when we
18312 finish connecting to a hidden service, clear the rendezvous
18313 circuit's stream-isolation state and try to attach streams
18314 again. Previously, we cleared rendezvous circuits' isolation
18315 state either too early (if they were freshly built) or not at all
18316 (if they had been built earlier and were cannibalized). Bugfix on
18317 0.2.3.3-alpha; fixes bug 4655.
18318 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
18319 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
18320 - Fix an assertion failure when a relay with accounting enabled
18321 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
18324 - Update to the December 6 2011 Maxmind GeoLite Country database.
18327 Changes in version 0.2.2.35 - 2011-12-16
18328 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
18329 buffers code. Absolutely everybody should upgrade.
18331 The bug relied on an incorrect calculation when making data continuous
18332 in one of our IO buffers, if the first chunk of the buffer was
18333 misaligned by just the wrong amount. The miscalculation would allow an
18334 attacker to overflow a piece of heap-allocated memory. To mount this
18335 attack, the attacker would need to either open a SOCKS connection to
18336 Tor's SocksPort (usually restricted to localhost), or target a Tor
18337 instance configured to make its connections through a SOCKS proxy
18338 (which Tor does not do by default).
18340 Good security practice requires that all heap-overflow bugs should be
18341 presumed to be exploitable until proven otherwise, so we are treating
18342 this as a potential code execution attack. Please upgrade immediately!
18343 This bug does not affect bufferevents-based builds of Tor. Special
18344 thanks to "Vektor" for reporting this issue to us!
18346 Tor 0.2.2.35 also fixes several bugs in previous versions, including
18347 crash bugs for unusual configurations, and a long-term bug that
18348 would prevent Tor from starting on Windows machines with draconian
18351 With this release, we remind everyone that 0.2.0.x has reached its
18352 formal end-of-life. Those Tor versions have many known flaws, and
18353 nobody should be using them. You should upgrade -- ideally to the
18354 0.2.2.x series. If you're using a Linux or BSD and its packages are
18355 obsolete, stop using those packages and upgrade anyway.
18357 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
18358 longer receive support after some time in early 2012.
18361 - Fix a heap overflow bug that could occur when trying to pull
18362 data into the first chunk of a buffer, when that chunk had
18363 already had some data drained from it. Fixes CVE-2011-2778;
18364 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
18365 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
18366 that it doesn't attempt to allocate a socketpair. This could cause
18367 some problems on Windows systems with overzealous firewalls. Fix for
18368 bug 4457; workaround for Libevent versions 2.0.1-alpha through
18370 - If we mark an OR connection for close based on a cell we process,
18371 don't process any further cells on it. We already avoid further
18372 reads on marked-for-close connections, but now we also discard the
18373 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
18374 which was the first version where we might mark a connection for
18375 close based on processing a cell on it.
18376 - Correctly sanity-check that we don't underflow on a memory
18377 allocation (and then assert) for hidden service introduction
18378 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
18379 bugfix on 0.2.1.5-alpha.
18380 - Fix a memory leak when we check whether a hidden service
18381 descriptor has any usable introduction points left. Fixes bug
18382 4424. Bugfix on 0.2.2.25-alpha.
18383 - Don't crash when we're running as a relay and don't have a GeoIP
18384 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
18385 we've had in the 0.2.3.x branch already.
18386 - When running as a client, do not print a misleading (and plain
18387 wrong) log message that we're collecting "directory request"
18388 statistics: clients don't collect statistics. Also don't create a
18389 useless (because empty) stats file in the stats/ directory. Fixes
18390 bug 4353; bugfix on 0.2.2.34.
18393 - Detect failure to initialize Libevent. This fix provides better
18394 detection for future instances of bug 4457.
18395 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
18396 function. This was eating up hideously large amounts of time on some
18397 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
18398 - Resolve an integer overflow bug in smartlist_ensure_capacity().
18399 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
18401 - Don't warn about unused log_mutex in log.c when building with
18402 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
18403 0.1.0.6-rc which introduced --disable-threads.
18404 - When configuring, starting, or stopping an NT service, stop
18405 immediately after the service configuration attempt has succeeded
18406 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
18407 - When sending a NETINFO cell, include the original address
18408 received for the other side, not its canonical address. Found
18409 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
18410 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
18411 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
18412 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
18413 occurred when a client tried to fetch a descriptor for a bridge
18414 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
18415 - Backport fixes for a pair of compilation warnings on Windows.
18416 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
18417 - If we had ever tried to call tor_addr_to_str on an address of
18418 unknown type, we would have done a strdup on an uninitialized
18419 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
18420 Reported by "troll_un".
18421 - Correctly detect and handle transient lookup failures from
18422 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
18423 Reported by "troll_un".
18424 - Fix null-pointer access that could occur if TLS allocation failed.
18425 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
18426 - Use tor_socket_t type for listener argument to accept(). Fixes bug
18427 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
18430 - Add two new config options for directory authorities:
18431 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
18432 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
18433 that is always sufficient to satisfy the bandwidth requirement for
18434 the Guard flag. Now it will be easier for researchers to simulate
18435 Tor networks with different values. Resolves ticket 4484.
18436 - When Tor ignores a hidden service specified in its configuration,
18437 include the hidden service's directory in the warning message.
18438 Previously, we would only tell the user that some hidden service
18439 was ignored. Bugfix on 0.0.6; fixes bug 4426.
18440 - Update to the December 6 2011 Maxmind GeoLite Country database.
18442 o Packaging changes:
18443 - Make it easier to automate expert package builds on Windows,
18444 by removing an absolute path from makensis.exe command.
18447 Changes in version 0.2.1.32 - 2011-12-16
18448 Tor 0.2.1.32 backports important security and privacy fixes for
18449 oldstable. This release is intended only for package maintainers and
18450 others who cannot use the 0.2.2 stable series. All others should be
18451 using Tor 0.2.2.x or newer.
18453 The Tor 0.2.1.x series will reach formal end-of-life some time in
18454 early 2012; we will stop releasing patches for it then.
18456 o Major bugfixes (also included in 0.2.2.x):
18457 - Correctly sanity-check that we don't underflow on a memory
18458 allocation (and then assert) for hidden service introduction
18459 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
18460 bugfix on 0.2.1.5-alpha.
18461 - Fix a heap overflow bug that could occur when trying to pull
18462 data into the first chunk of a buffer, when that chunk had
18463 already had some data drained from it. Fixes CVE-2011-2778;
18464 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
18467 - Update to the December 6 2011 Maxmind GeoLite Country database.
18470 Changes in version 0.2.3.9-alpha - 2011-12-08
18471 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
18472 a "DisableNetwork" security feature that bundles can use to avoid
18473 touching the network until bridges are configured, moves forward on
18474 the pluggable transport design, fixes a flaw in the hidden service
18475 design that unnecessarily prevented clients with wrong clocks from
18476 reaching hidden services, and fixes a wide variety of other issues.
18479 - Clients can now connect to private bridges over IPv6. Bridges
18480 still need at least one IPv4 address in order to connect to
18481 other relays. Note that we don't yet handle the case where the
18482 user has two bridge lines for the same bridge (one IPv4, one
18483 IPv6). Implements parts of proposal 186.
18484 - New "DisableNetwork" config option to prevent Tor from launching any
18485 connections or accepting any connections except on a control port.
18486 Bundles and controllers can set this option before letting Tor talk
18487 to the rest of the network, for example to prevent any connections
18488 to a non-bridge address. Packages like Orbot can also use this
18489 option to instruct Tor to save power when the network is off.
18490 - Clients and bridges can now be configured to use a separate
18491 "transport" proxy. This approach makes the censorship arms race
18492 easier by allowing bridges to use protocol obfuscation plugins. It
18493 implements the "managed proxy" part of proposal 180 (ticket 3472).
18494 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
18495 implementation. It makes AES_CTR about 7% faster than our old one
18496 (which was about 10% faster than the one OpenSSL used to provide).
18497 Resolves ticket 4526.
18498 - Add a "tor2web mode" for clients that want to connect to hidden
18499 services non-anonymously (and possibly more quickly). As a safety
18500 measure to try to keep users from turning this on without knowing
18501 what they are doing, tor2web mode must be explicitly enabled at
18502 compile time, and a copy of Tor compiled to run in tor2web mode
18503 cannot be used as a normal Tor client. Implements feature 2553.
18504 - Add experimental support for running on Windows with IOCP and no
18505 kernel-space socket buffers. This feature is controlled by a new
18506 "UserspaceIOCPBuffers" config option (off by default), which has
18507 no effect unless Tor has been built with support for bufferevents,
18508 is running on Windows, and has enabled IOCP. This may, in the long
18509 run, help solve or mitigate bug 98.
18510 - Use a more secure consensus parameter voting algorithm. Now at
18511 least three directory authorities or a majority of them must
18512 vote on a given parameter before it will be included in the
18513 consensus. Implements proposal 178.
18516 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
18517 They used to check that the timestamp was within 30 minutes
18518 of their system clock, so they could cap the size of their
18519 replay-detection cache, but that approach unnecessarily refused
18520 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
18521 the v3 intro-point protocol (the first one which sent a timestamp
18522 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
18523 - Only use the EVP interface when AES acceleration is enabled,
18524 to avoid a 5-7% performance regression. Resolves issue 4525;
18525 bugfix on 0.2.3.8-alpha.
18527 o Privacy/anonymity features (bridge detection):
18528 - Make bridge SSL certificates a bit more stealthy by using random
18529 serial numbers, in the same fashion as OpenSSL when generating
18530 self-signed certificates. Implements ticket 4584.
18531 - Introduce a new config option "DynamicDHGroups", enabled by
18532 default, which provides each bridge with a unique prime DH modulus
18533 to be used during SSL handshakes. This option attempts to help
18534 against censors who might use the Apache DH modulus as a static
18535 identifier for bridges. Addresses ticket 4548.
18537 o Minor features (new/different config options):
18538 - New configuration option "DisableDebuggerAttachment" (on by default)
18539 to prevent basic debugging attachment attempts by other processes.
18540 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
18541 - Allow MapAddress directives to specify matches against super-domains,
18542 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
18543 Implements issue 933.
18544 - Slightly change behavior of "list" options (that is, config
18545 options that can appear more than once) when they appear both in
18546 torrc and on the command line. Previously, the command-line options
18547 would be appended to the ones from torrc. Now, the command-line
18548 options override the torrc options entirely. This new behavior
18549 allows the user to override list options (like exit policies and
18550 ports to listen on) from the command line, rather than simply
18551 appending to the list.
18552 - You can get the old (appending) command-line behavior for "list"
18553 options by prefixing the option name with a "+".
18554 - You can remove all the values for a "list" option from the command
18555 line without adding any new ones by prefixing the option name
18557 - Add experimental support for a "defaults" torrc file to be parsed
18558 before the regular torrc. Torrc options override the defaults file's
18559 options in the same way that the command line overrides the torrc.
18560 The SAVECONF controller command saves only those options which
18561 differ between the current configuration and the defaults file. HUP
18562 reloads both files. (Note: This is an experimental feature; its
18563 behavior will probably be refined in future 0.2.3.x-alpha versions
18564 to better meet packagers' needs.) Implements task 4552.
18567 - Try to make the introductory warning message that Tor prints on
18568 startup more useful for actually finding help and information.
18569 Resolves ticket 2474.
18570 - Running "make version" now displays the version of Tor that
18571 we're about to build. Idea from katmagic; resolves issue 4400.
18572 - Expire old or over-used hidden service introduction points.
18573 Required by fix for bug 3460.
18574 - Move the replay-detection cache for the RSA-encrypted parts of
18575 INTRODUCE2 cells to the introduction point data structures.
18576 Previously, we would use one replay-detection cache per hidden
18577 service. Required by fix for bug 3460.
18578 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
18579 public key replay-detection cache from 60 minutes to 5 minutes. This
18580 replay-detection cache is now used only to detect multiple
18581 INTRODUCE2 cells specifying the same rendezvous point, so we can
18582 avoid launching multiple simultaneous attempts to connect to it.
18584 o Minor bugfixes (on Tor 0.2.2.x and earlier):
18585 - Resolve an integer overflow bug in smartlist_ensure_capacity().
18586 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
18588 - Fix a minor formatting issue in one of tor-gencert's error messages.
18590 - Prevent a false positive from the check-spaces script, by disabling
18591 the "whitespace between function name and (" check for functions
18593 - Fix a log message suggesting that people contact a non-existent
18594 email address. Fixes bug 3448.
18595 - Fix null-pointer access that could occur if TLS allocation failed.
18596 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
18597 - Report a real bootstrap problem to the controller on router
18598 identity mismatch. Previously we just said "foo", which probably
18599 made a lot of sense at the time. Fixes bug 4169; bugfix on
18601 - If we had ever tried to call tor_addr_to_str() on an address of
18602 unknown type, we would have done a strdup() on an uninitialized
18603 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
18604 Reported by "troll_un".
18605 - Correctly detect and handle transient lookup failures from
18606 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
18607 Reported by "troll_un".
18608 - Use tor_socket_t type for listener argument to accept(). Fixes bug
18609 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
18610 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
18611 bug 4532; found by "troll_un".
18613 o Minor bugfixes (on Tor 0.2.3.x):
18614 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
18616 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
18617 circuit for use as a hidden service client's rendezvous point.
18618 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
18619 with help from wanoskarnet.
18620 - Restore behavior of overriding SocksPort, ORPort, and similar
18621 options from the command line. Bugfix on 0.2.3.3-alpha.
18624 - Properly handle the case where the build-tree is not the same
18625 as the source tree when generating src/common/common_sha1.i,
18626 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
18627 bugfix on 0.2.0.1-alpha.
18629 o Code simplifications, cleanups, and refactorings:
18630 - Remove the pure attribute from all functions that used it
18631 previously. In many cases we assigned it incorrectly, because the
18632 functions might assert or call impure functions, and we don't have
18633 evidence that keeping the pure attribute is worthwhile. Implements
18634 changes suggested in ticket 4421.
18635 - Remove some dead code spotted by coverity. Fixes cid 432.
18636 Bugfix on 0.2.3.1-alpha, closes bug 4637.
18639 Changes in version 0.2.3.8-alpha - 2011-11-22
18640 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
18641 socketpair-related bug that has been bothering Windows users. It adds
18642 support to serve microdescriptors to controllers, so Vidalia's network
18643 map can resume listing relays (once Vidalia implements its side),
18644 and adds better support for hardware AES acceleration. Finally, it
18645 starts the process of adjusting the bandwidth cutoff for getting the
18646 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
18647 that tiny relays harm performance more than they help network capacity.
18650 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
18651 that it doesn't attempt to allocate a socketpair. This could cause
18652 some problems on Windows systems with overzealous firewalls. Fix for
18653 bug 4457; workaround for Libevent versions 2.0.1-alpha through
18655 - Correctly sanity-check that we don't underflow on a memory
18656 allocation (and then assert) for hidden service introduction
18657 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
18658 bugfix on 0.2.1.5-alpha.
18659 - Remove the artificially low cutoff of 20KB to guarantee the Fast
18660 flag. In the past few years the average relay speed has picked
18661 up, and while the "top 7/8 of the network get the Fast flag" and
18662 "all relays with 20KB or more of capacity get the Fast flag" rules
18663 used to have the same result, now the top 7/8 of the network has
18664 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
18665 - Fix a rare assertion failure when checking whether a v0 hidden
18666 service descriptor has any usable introduction points left, and
18667 we don't have enough information to build a circuit to the first
18668 intro point named in the descriptor. The HS client code in
18669 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
18670 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
18671 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
18672 - Make bridge authorities not crash when they are asked for their own
18673 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
18674 - When running as a client, do not print a misleading (and plain
18675 wrong) log message that we're collecting "directory request"
18676 statistics: clients don't collect statistics. Also don't create a
18677 useless (because empty) stats file in the stats/ directory. Fixes
18678 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
18681 - Allow Tor controllers like Vidalia to obtain the microdescriptor
18682 for a relay by identity digest or nickname. Previously,
18683 microdescriptors were only available by their own digests, so a
18684 controller would have to ask for and parse the whole microdescriptor
18685 consensus in order to look up a single relay's microdesc. Fixes
18686 bug 3832; bugfix on 0.2.3.1-alpha.
18687 - Use OpenSSL's EVP interface for AES encryption, so that all AES
18688 operations can use hardware acceleration (if present). Resolves
18691 o Minor bugfixes (on 0.2.2.x and earlier):
18692 - Detect failure to initialize Libevent. This fix provides better
18693 detection for future instances of bug 4457.
18694 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
18695 function. This was eating up hideously large amounts of time on some
18696 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
18697 - Don't warn about unused log_mutex in log.c when building with
18698 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
18699 0.1.0.6-rc which introduced --disable-threads.
18700 - Allow manual 'authenticate' commands to the controller interface
18701 from netcat (nc) as well as telnet. We were rejecting them because
18702 they didn't come with the expected whitespace at the end of the
18703 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
18704 - Fix some (not actually triggerable) buffer size checks in usage of
18705 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
18707 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
18708 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
18709 - When configuring, starting, or stopping an NT service, stop
18710 immediately after the service configuration attempt has succeeded
18711 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
18712 - When sending a NETINFO cell, include the original address
18713 received for the other side, not its canonical address. Found
18714 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
18715 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
18716 can pick them up when the tests aren't disabled. Bugfix on
18717 0.2.2.4-alpha which introduced tinytest.
18718 - Fix a memory leak when we check whether a hidden service
18719 descriptor has any usable introduction points left. Fixes bug
18720 4424. Bugfix on 0.2.2.25-alpha.
18721 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
18722 occurred when a client tried to fetch a descriptor for a bridge
18723 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
18725 o Minor bugfixes (on 0.2.3.x):
18726 - Make util unit tests build correctly with MSVC. Bugfix on
18727 0.2.3.3-alpha. Patch by Gisle Vanem.
18728 - Successfully detect AUTH_CHALLENGE cells with no recognized
18729 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
18730 Found by frosty_un.
18731 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
18732 it should still send a NETINFO cell to allow the connection to
18733 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
18735 - Log less loudly when we get an invalid authentication certificate
18736 from a source other than a directory authority: it's not unusual
18737 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
18739 - Tolerate servers with more clock skew in their authentication
18740 certificates than previously. Fixes bug 4371; bugfix on
18742 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
18743 on 0.2.3.4-alpha and 0.2.3.6-alpha.
18746 - Add two new config options for directory authorities:
18747 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
18748 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
18749 that is always sufficient to satisfy the bandwidth requirement for
18750 the Guard flag. Now it will be easier for researchers to simulate
18751 Tor networks with different values. Resolves ticket 4484.
18752 - When Tor ignores a hidden service specified in its configuration,
18753 include the hidden service's directory in the warning message.
18754 Previously, we would only tell the user that some hidden service
18755 was ignored. Bugfix on 0.0.6; fixes bug 4426.
18756 - When we fail to initialize Libevent, retry with IOCP disabled so we
18757 don't need to turn on multi-threading support in Libevent, which in
18758 turn requires a working socketpair(). This is a workaround for bug
18759 4457, which affects Libevent versions from 2.0.1-alpha through
18761 - Detect when we try to build on a platform that doesn't define
18762 AF_UNSPEC to 0. We don't work there, so refuse to compile.
18763 - Update to the November 1 2011 Maxmind GeoLite Country database.
18765 o Packaging changes:
18766 - Make it easier to automate expert package builds on Windows,
18767 by removing an absolute path from makensis.exe command.
18769 o Code simplifications and refactoring:
18770 - Remove some redundant #include directives throughout the code.
18771 Patch from Andrea Gelmini.
18772 - Unconditionally use OpenSSL's AES implementation instead of our
18773 old built-in one. OpenSSL's AES has been better for a while, and
18774 relatively few servers should still be on any version of OpenSSL
18775 that doesn't have good optimized assembly AES.
18776 - Use the name "CERTS" consistently to refer to the new cell type;
18777 we were calling it CERT in some places and CERTS in others.
18780 - Numerous new unit tests for functions in util.c and address.c by
18782 - The long-disabled benchmark tests are now split into their own
18783 ./src/test/bench binary.
18784 - The benchmark tests can now use more accurate timers than
18785 gettimeofday() when such timers are available.
18788 Changes in version 0.2.3.7-alpha - 2011-10-30
18789 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
18790 the new v3 handshake. It also resolves yet another bridge address
18794 - If we mark an OR connection for close based on a cell we process,
18795 don't process any further cells on it. We already avoid further
18796 reads on marked-for-close connections, but now we also discard the
18797 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
18798 which was the first version where we might mark a connection for
18799 close based on processing a cell on it.
18800 - Fix a double-free bug that would occur when we received an invalid
18801 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
18802 bugfix on 0.2.3.6-alpha.
18803 - Bridges no longer include their address in NETINFO cells on outgoing
18804 OR connections, to allow them to blend in better with clients.
18805 Removes another avenue for enumerating bridges. Reported by
18806 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
18807 cells were introduced.
18810 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
18811 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
18814 Changes in version 0.2.3.6-alpha - 2011-10-26
18815 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
18816 anonymity vulnerability where an attacker can deanonymize Tor
18817 users. Everybody should upgrade.
18819 This release also features support for a new v3 connection handshake
18820 protocol, and fixes to make hidden service connections more robust.
18823 - Implement a new handshake protocol (v3) for authenticating Tors to
18824 each other over TLS. It should be more resistant to fingerprinting
18825 than previous protocols, and should require less TLS hacking for
18826 future Tor implementations. Implements proposal 176.
18827 - Allow variable-length padding cells to disguise the length of
18828 Tor's TLS records. Implements part of proposal 184.
18830 o Privacy/anonymity fixes (clients):
18831 - Clients and bridges no longer send TLS certificate chains on
18832 outgoing OR connections. Previously, each client or bridge would
18833 use the same cert chain for all outgoing OR connections until
18834 its IP address changes, which allowed any relay that the client
18835 or bridge contacted to determine which entry guards it is using.
18836 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
18837 - If a relay receives a CREATE_FAST cell on a TLS connection, it
18838 no longer considers that connection as suitable for satisfying a
18839 circuit EXTEND request. Now relays can protect clients from the
18840 CVE-2011-2768 issue even if the clients haven't upgraded yet.
18841 - Directory authorities no longer assign the Guard flag to relays
18842 that haven't upgraded to the above "refuse EXTEND requests
18843 to client connections" fix. Now directory authorities can
18844 protect clients from the CVE-2011-2768 issue even if neither
18845 the clients nor the relays have upgraded yet. There's a new
18846 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
18847 to let us transition smoothly, else tomorrow there would be no
18850 o Major bugfixes (hidden services):
18851 - Improve hidden service robustness: when an attempt to connect to
18852 a hidden service ends, be willing to refetch its hidden service
18853 descriptors from each of the HSDir relays responsible for them
18854 immediately. Previously, we would not consider refetching the
18855 service's descriptors from each HSDir for 15 minutes after the last
18856 fetch, which was inconvenient if the hidden service was not running
18857 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
18858 - When one of a hidden service's introduction points appears to be
18859 unreachable, stop trying it. Previously, we would keep trying
18860 to build circuits to the introduction point until we lost the
18861 descriptor, usually because the user gave up and restarted Tor.
18862 Partly fixes bug 3825.
18863 - Don't launch a useless circuit after failing to use one of a
18864 hidden service's introduction points. Previously, we would
18865 launch a new introduction circuit, but not set the hidden service
18866 which that circuit was intended to connect to, so it would never
18867 actually be used. A different piece of code would then create a
18868 new introduction circuit correctly. Bug reported by katmagic and
18869 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
18871 o Major bugfixes (other):
18872 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
18873 that they initiated. Relays could distinguish incoming bridge
18874 connections from client connections, creating another avenue for
18875 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
18876 Found by "frosty_un".
18877 - Don't update the AccountingSoftLimitHitAt state file entry whenever
18878 tor gets started. This prevents a wrong average bandwidth
18879 estimate, which would cause relays to always start a new accounting
18880 interval at the earliest possible moment. Fixes bug 2003; bugfix
18881 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
18882 immensely in tracking this bug down.
18883 - Fix a crash bug when changing node restrictions while a DNS lookup
18884 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
18887 o Minor bugfixes (on 0.2.2.x and earlier):
18888 - When a hidden service turns an extra service-side introduction
18889 circuit into a general-purpose circuit, free the rend_data and
18890 intro_key fields first, so we won't leak memory if the circuit
18891 is cannibalized for use as another service-side introduction
18892 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
18893 - Rephrase the log message emitted if the TestSocks check is
18894 successful. Patch from Fabian Keil; fixes bug 4094.
18895 - Bridges now skip DNS self-tests, to act a little more stealthily.
18896 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
18897 bridges. Patch by "warms0x".
18898 - Remove a confusing dollar sign from the example fingerprint in the
18899 man page, and also make the example fingerprint a valid one. Fixes
18900 bug 4309; bugfix on 0.2.1.3-alpha.
18901 - Fix internal bug-checking logic that was supposed to catch
18902 failures in digest generation so that it will fail more robustly
18903 if we ask for a nonexistent algorithm. Found by Coverity Scan.
18904 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
18905 - Report any failure in init_keys() calls launched because our
18906 IP address has changed. Spotted by Coverity Scan. Bugfix on
18907 0.1.1.4-alpha; fixes CID 484.
18909 o Minor bugfixes (on 0.2.3.x):
18910 - Fix a bug in configure.in that kept it from building a configure
18911 script with autoconf versions earlier than 2.61. Fixes bug 2430;
18912 bugfix on 0.2.3.1-alpha.
18913 - Don't warn users that they are exposing a client port to the
18914 Internet if they have specified an RFC1918 address. Previously,
18915 we would warn if the user had specified any non-loopback
18916 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
18917 - Fix memory leaks in the failing cases of the new SocksPort and
18918 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
18919 fixes coverity CIDs 485, 486, and 487.
18922 - When a hidden service's introduction point times out, consider
18923 trying it again during the next attempt to connect to the
18924 HS. Previously, we would not try it again unless a newly fetched
18925 descriptor contained it. Required by fixes for bugs 1297 and 3825.
18926 - The next version of Windows will be called Windows 8, and it has
18927 a major version of 6, minor version of 2. Correctly identify that
18928 version instead of calling it "Very recent version". Resolves
18929 ticket 4153; reported by funkstar.
18930 - The Bridge Authority now writes statistics on how many bridge
18931 descriptors it gave out in total, and how many unique descriptors
18932 it gave out. It also lists how often the most and least commonly
18933 fetched descriptors were given out, as well as the median and
18934 25th/75th percentile. Implements tickets 4200 and 4294.
18935 - Update to the October 4 2011 Maxmind GeoLite Country database.
18937 o Code simplifications and refactoring:
18938 - Remove some old code to remember statistics about which descriptors
18939 we've served as a directory mirror. The feature wasn't used and
18940 is outdated now that microdescriptors are around.
18941 - Rename Tor functions that turn strings into addresses, so that
18942 "parse" indicates that no hostname resolution occurs, and
18943 "lookup" indicates that hostname resolution may occur. This
18944 should help prevent mistakes in the future. Fixes bug 3512.
18947 Changes in version 0.2.2.34 - 2011-10-26
18948 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
18949 can deanonymize Tor users. Everybody should upgrade.
18951 The attack relies on four components: 1) Clients reuse their TLS cert
18952 when talking to different relays, so relays can recognize a user by
18953 the identity key in her cert. 2) An attacker who knows the client's
18954 identity key can probe each guard relay to see if that identity key
18955 is connected to that guard relay right now. 3) A variety of active
18956 attacks in the literature (starting from "Low-Cost Traffic Analysis
18957 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
18958 discover the guard relays that a Tor user visiting the website is using.
18959 4) Clients typically pick three guards at random, so the set of guards
18960 for a given user could well be a unique fingerprint for her. This
18961 release fixes components #1 and #2, which is enough to block the attack;
18962 the other two remain as open research problems. Special thanks to
18963 "frosty_un" for reporting the issue to us!
18965 Clients should upgrade so they are no longer recognizable by the TLS
18966 certs they present. Relays should upgrade so they no longer allow a
18967 remote attacker to probe them to test whether unpatched clients are
18968 currently connected to them.
18970 This release also fixes several vulnerabilities that allow an attacker
18971 to enumerate bridge relays. Some bridge enumeration attacks still
18972 remain; see for example proposal 188.
18974 o Privacy/anonymity fixes (clients):
18975 - Clients and bridges no longer send TLS certificate chains on
18976 outgoing OR connections. Previously, each client or bridge would
18977 use the same cert chain for all outgoing OR connections until
18978 its IP address changes, which allowed any relay that the client
18979 or bridge contacted to determine which entry guards it is using.
18980 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
18981 - If a relay receives a CREATE_FAST cell on a TLS connection, it
18982 no longer considers that connection as suitable for satisfying a
18983 circuit EXTEND request. Now relays can protect clients from the
18984 CVE-2011-2768 issue even if the clients haven't upgraded yet.
18985 - Directory authorities no longer assign the Guard flag to relays
18986 that haven't upgraded to the above "refuse EXTEND requests
18987 to client connections" fix. Now directory authorities can
18988 protect clients from the CVE-2011-2768 issue even if neither
18989 the clients nor the relays have upgraded yet. There's a new
18990 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
18991 to let us transition smoothly, else tomorrow there would be no
18994 o Privacy/anonymity fixes (bridge enumeration):
18995 - Bridge relays now do their directory fetches inside Tor TLS
18996 connections, like all the other clients do, rather than connecting
18997 directly to the DirPort like public relays do. Removes another
18998 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
18999 - Bridges relays now build circuits for themselves in a more similar
19000 way to how clients build them. Removes another avenue for
19001 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
19002 when bridges were introduced.
19003 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19004 that they initiated. Relays could distinguish incoming bridge
19005 connections from client connections, creating another avenue for
19006 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19007 Found by "frosty_un".
19010 - Fix a crash bug when changing node restrictions while a DNS lookup
19011 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
19013 - Don't launch a useless circuit after failing to use one of a
19014 hidden service's introduction points. Previously, we would
19015 launch a new introduction circuit, but not set the hidden service
19016 which that circuit was intended to connect to, so it would never
19017 actually be used. A different piece of code would then create a
19018 new introduction circuit correctly. Bug reported by katmagic and
19019 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
19022 - Change an integer overflow check in the OpenBSD_Malloc code so
19023 that GCC is less likely to eliminate it as impossible. Patch
19024 from Mansour Moufid. Fixes bug 4059.
19025 - When a hidden service turns an extra service-side introduction
19026 circuit into a general-purpose circuit, free the rend_data and
19027 intro_key fields first, so we won't leak memory if the circuit
19028 is cannibalized for use as another service-side introduction
19029 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
19030 - Bridges now skip DNS self-tests, to act a little more stealthily.
19031 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
19032 bridges. Patch by "warms0x".
19033 - Fix internal bug-checking logic that was supposed to catch
19034 failures in digest generation so that it will fail more robustly
19035 if we ask for a nonexistent algorithm. Found by Coverity Scan.
19036 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
19037 - Report any failure in init_keys() calls launched because our
19038 IP address has changed. Spotted by Coverity Scan. Bugfix on
19039 0.1.1.4-alpha; fixes CID 484.
19041 o Minor bugfixes (log messages and documentation):
19042 - Remove a confusing dollar sign from the example fingerprint in the
19043 man page, and also make the example fingerprint a valid one. Fixes
19044 bug 4309; bugfix on 0.2.1.3-alpha.
19045 - The next version of Windows will be called Windows 8, and it has
19046 a major version of 6, minor version of 2. Correctly identify that
19047 version instead of calling it "Very recent version". Resolves
19048 ticket 4153; reported by funkstar.
19049 - Downgrade log messages about circuit timeout calibration from
19050 "notice" to "info": they don't require or suggest any human
19051 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
19052 bugfix on 0.2.2.14-alpha.
19055 - Turn on directory request statistics by default and include them in
19056 extra-info descriptors. Don't break if we have no GeoIP database.
19057 Backported from 0.2.3.1-alpha; implements ticket 3951.
19058 - Update to the October 4 2011 Maxmind GeoLite Country database.
19061 Changes in version 0.2.1.31 - 2011-10-26
19062 Tor 0.2.1.31 backports important security and privacy fixes for
19063 oldstable. This release is intended only for package maintainers and
19064 others who cannot use the 0.2.2 stable series. All others should be
19065 using Tor 0.2.2.x or newer.
19067 o Security fixes (also included in 0.2.2.x):
19068 - Replace all potentially sensitive memory comparison operations
19069 with versions whose runtime does not depend on the data being
19070 compared. This will help resist a class of attacks where an
19071 adversary can use variations in timing information to learn
19072 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19073 implementation by Robert Ransom based partially on code by DJB.)
19074 - Fix an assert in parsing router descriptors containing IPv6
19075 addresses. This one took down the directory authorities when
19076 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
19078 o Privacy/anonymity fixes (also included in 0.2.2.x):
19079 - Clients and bridges no longer send TLS certificate chains on
19080 outgoing OR connections. Previously, each client or bridge would
19081 use the same cert chain for all outgoing OR connections until
19082 its IP address changes, which allowed any relay that the client
19083 or bridge contacted to determine which entry guards it is using.
19084 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19085 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19086 no longer considers that connection as suitable for satisfying a
19087 circuit EXTEND request. Now relays can protect clients from the
19088 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19089 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19090 that they initiated. Relays could distinguish incoming bridge
19091 connections from client connections, creating another avenue for
19092 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19093 Found by "frosty_un".
19094 - When receiving a hidden service descriptor, check that it is for
19095 the hidden service we wanted. Previously, Tor would store any
19096 hidden service descriptors that a directory gave it, whether it
19097 wanted them or not. This wouldn't have let an attacker impersonate
19098 a hidden service, but it did let directories pre-seed a client
19099 with descriptors that it didn't want. Bugfix on 0.0.6.
19100 - Avoid linkability based on cached hidden service descriptors: forget
19101 all hidden service descriptors cached as a client when processing a
19102 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
19103 - Make the bridge directory authority refuse to answer directory
19104 requests for "all" descriptors. It used to include bridge
19105 descriptors in its answer, which was a major information leak.
19106 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
19107 - Don't attach new streams to old rendezvous circuits after SIGNAL
19108 NEWNYM. Previously, we would keep using an existing rendezvous
19109 circuit if it remained open (i.e. if it were kept open by a
19110 long-lived stream, or if a new stream were attached to it before
19111 Tor could notice that it was old and no longer in use). Bugfix on
19112 0.1.1.15-rc; fixes bug 3375.
19114 o Minor bugfixes (also included in 0.2.2.x):
19115 - When we restart our relay, we might get a successful connection
19116 from the outside before we've started our reachability tests,
19117 triggering a warning: "ORPort found reachable, but I have no
19118 routerinfo yet. Failing to inform controller of success." This
19119 bug was harmless unless Tor is running under a controller
19120 like Vidalia, in which case the controller would never get a
19121 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
19123 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
19124 enabled. Fixes bug 1526.
19125 - Remove undocumented option "-F" from tor-resolve: it hasn't done
19126 anything since 0.2.1.16-rc.
19127 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
19128 None of the cases where we did this before were wrong, but by making
19129 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
19130 - Fix a rare crash bug that could occur when a client was configured
19131 with a large number of bridges. Fixes bug 2629; bugfix on
19132 0.2.1.2-alpha. Bugfix by trac user "shitlei".
19133 - Correct the warning displayed when a rendezvous descriptor exceeds
19134 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
19136 - Fix an uncommon assertion failure when running with DNSPort under
19137 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
19138 - When warning about missing zlib development packages during compile,
19139 give the correct package names. Bugfix on 0.2.0.1-alpha.
19140 - Require that introduction point keys and onion keys have public
19141 exponent 65537. Bugfix on 0.2.0.10-alpha.
19142 - Do not crash when our configuration file becomes unreadable, for
19143 example due to a permissions change, between when we start up
19144 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
19146 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
19148 - Always NUL-terminate the sun_path field of a sockaddr_un before
19149 passing it to the kernel. (Not a security issue: kernels are
19150 smart enough to reject bad sockaddr_uns.) Found by Coverity;
19151 CID #428. Bugfix on Tor 0.2.0.3-alpha.
19152 - Don't stack-allocate the list of supplementary GIDs when we're
19153 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
19154 could take up to 256K, which is way too much stack. Found by
19155 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
19157 o Minor bugfixes (only in 0.2.1.x):
19158 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
19159 rely on them. Bugfix on 0.2.1.30.
19160 - Use git revisions instead of svn revisions when generating our
19161 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
19163 o Minor features (also included in 0.2.2.x):
19164 - Adjust the expiration time on our SSL session certificates to
19165 better match SSL certs seen in the wild. Resolves ticket 4014.
19166 - Allow nameservers with IPv6 address. Resolves bug 2574.
19167 - Update to the October 4 2011 Maxmind GeoLite Country database.
19170 Changes in version 0.2.3.5-alpha - 2011-09-28
19171 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
19172 bridge relays; fixes an assertion error that many users started hitting
19173 today; and adds the ability to refill token buckets more often than
19174 once per second, allowing significant performance improvements.
19177 - Bridge relays now do their directory fetches inside Tor TLS
19178 connections, like all the other clients do, rather than connecting
19179 directly to the DirPort like public relays do. Removes another
19180 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
19181 - Bridges relays now build circuits for themselves in a more similar
19182 way to how clients build them. Removes another avenue for
19183 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
19184 when bridges were introduced.
19187 - Fix an "Assertion md->held_by_node == 1 failed" error that could
19188 occur when the same microdescriptor was referenced by two node_t
19189 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
19191 o Major features (networking):
19192 - Add a new TokenBucketRefillInterval option to refill token buckets
19193 more frequently than once per second. This should improve network
19194 performance, alleviate queueing problems, and make traffic less
19195 bursty. Implements proposal 183; closes ticket 3630. Design by
19196 Florian Tschorsch and Björn Scheuermann; implementation by
19200 - Change an integer overflow check in the OpenBSD_Malloc code so
19201 that GCC is less likely to eliminate it as impossible. Patch
19202 from Mansour Moufid. Fixes bug 4059.
19204 o Minor bugfixes (usability):
19205 - Downgrade log messages about circuit timeout calibration from
19206 "notice" to "info": they don't require or suggest any human
19207 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
19208 bugfix on 0.2.2.14-alpha.
19210 o Minor features (diagnostics):
19211 - When the system call to create a listener socket fails, log the
19212 error message explaining why. This may help diagnose bug 4027.
19215 Changes in version 0.2.3.4-alpha - 2011-09-13
19216 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
19217 tweak to Tor's TLS handshake that makes relays and bridges that run
19218 this new version reachable from Iran again. It also fixes a few new
19219 bugs in 0.2.3.x, and teaches relays to recognize when they're not
19220 listed in the network consensus and republish.
19222 o Major bugfixes (also part of 0.2.2.33):
19223 - Avoid an assertion failure when reloading a configuration with
19224 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
19225 3923; bugfix on 0.2.2.25-alpha.
19227 o Minor features (security, also part of 0.2.2.33):
19228 - Check for replays of the public-key encrypted portion of an
19229 INTRODUCE1 cell, in addition to the current check for replays of
19230 the g^x value. This prevents a possible class of active attacks
19231 by an attacker who controls both an introduction point and a
19232 rendezvous point, and who uses the malleability of AES-CTR to
19233 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
19234 that these attacks are infeasible (requiring the attacker to send
19235 on the order of zettabytes of altered cells in a short interval),
19236 but we'd rather block them off in case there are any classes of
19237 this attack that we missed. Reported by Willem Pinckaers.
19239 o Minor features (also part of 0.2.2.33):
19240 - Adjust the expiration time on our SSL session certificates to
19241 better match SSL certs seen in the wild. Resolves ticket 4014.
19242 - Change the default required uptime for a relay to be accepted as
19243 a HSDir (hidden service directory) from 24 hours to 25 hours.
19244 Improves on 0.2.0.10-alpha; resolves ticket 2649.
19245 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
19246 authorities to abstain from voting on assignment of the HSDir
19247 consensus flag. Related to bug 2649.
19248 - Update to the September 6 2011 Maxmind GeoLite Country database.
19250 o Minor bugfixes (also part of 0.2.2.33):
19251 - Demote the 'replay detected' log message emitted when a hidden
19252 service receives the same Diffie-Hellman public key in two different
19253 INTRODUCE2 cells to info level. A normal Tor client can cause that
19254 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
19255 fixes part of bug 2442.
19256 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
19257 level. There is nothing that a hidden service's operator can do
19258 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
19260 - Clarify a log message specifying the characters permitted in
19261 HiddenServiceAuthorizeClient client names. Previously, the log
19262 message said that "[A-Za-z0-9+-_]" were permitted; that could have
19263 given the impression that every ASCII character between "+" and "_"
19264 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
19266 o Build fixes (also part of 0.2.2.33):
19267 - Clean up some code issues that prevented Tor from building on older
19268 BSDs. Fixes bug 3894; reported by "grarpamp".
19269 - Search for a platform-specific version of "ar" when cross-compiling.
19270 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
19273 - Fix a bug where the SocksPort option (for example) would get
19274 ignored and replaced by the default if a SocksListenAddress
19275 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
19279 - Relays now try regenerating and uploading their descriptor more
19280 frequently if they are not listed in the consensus, or if the
19281 version of their descriptor listed in the consensus is too
19282 old. This fix should prevent situations where a server declines
19283 to re-publish itself because it has done so too recently, even
19284 though the authorities decided not to list its recent-enough
19285 descriptor. Fix for bug 3327.
19288 - Relays now include a reason for regenerating their descriptors
19289 in an HTTP header when uploading to the authorities. This will
19290 make it easier to debug descriptor-upload issues in the future.
19291 - When starting as root and then changing our UID via the User
19292 control option, and we have a ControlSocket configured, make sure
19293 that the ControlSocket is owned by the same account that Tor will
19294 run under. Implements ticket 3421; fix by Jérémy Bobbio.
19297 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
19298 utility function used in the control-port code). This shouldn't
19299 ever happen unless Tor is completely out of memory, but if it did
19300 happen and Tor somehow recovered from it, Tor could have sent a log
19301 message to a control port in the middle of a reply to a controller
19302 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
19303 - Make 'FetchUselessDescriptors' cause all descriptor types and
19304 all consensus types (including microdescriptors) to get fetched.
19305 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
19307 o Code refactoring:
19308 - Make a new "entry connection" struct as an internal subtype of "edge
19309 connection", to simplify the code and make exit connections smaller.
19312 Changes in version 0.2.2.33 - 2011-09-13
19313 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
19314 TLS handshake that makes relays and bridges that run this new version
19315 reachable from Iran again.
19318 - Avoid an assertion failure when reloading a configuration with
19319 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
19320 3923; bugfix on 0.2.2.25-alpha.
19322 o Minor features (security):
19323 - Check for replays of the public-key encrypted portion of an
19324 INTRODUCE1 cell, in addition to the current check for replays of
19325 the g^x value. This prevents a possible class of active attacks
19326 by an attacker who controls both an introduction point and a
19327 rendezvous point, and who uses the malleability of AES-CTR to
19328 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
19329 that these attacks are infeasible (requiring the attacker to send
19330 on the order of zettabytes of altered cells in a short interval),
19331 but we'd rather block them off in case there are any classes of
19332 this attack that we missed. Reported by Willem Pinckaers.
19335 - Adjust the expiration time on our SSL session certificates to
19336 better match SSL certs seen in the wild. Resolves ticket 4014.
19337 - Change the default required uptime for a relay to be accepted as
19338 a HSDir (hidden service directory) from 24 hours to 25 hours.
19339 Improves on 0.2.0.10-alpha; resolves ticket 2649.
19340 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
19341 authorities to abstain from voting on assignment of the HSDir
19342 consensus flag. Related to bug 2649.
19343 - Update to the September 6 2011 Maxmind GeoLite Country database.
19345 o Minor bugfixes (documentation and log messages):
19346 - Correct the man page to explain that HashedControlPassword and
19347 CookieAuthentication can both be set, in which case either method
19348 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
19349 when we decided to allow these config options to both be set. Issue
19350 raised by bug 3898.
19351 - Demote the 'replay detected' log message emitted when a hidden
19352 service receives the same Diffie-Hellman public key in two different
19353 INTRODUCE2 cells to info level. A normal Tor client can cause that
19354 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
19355 fixes part of bug 2442.
19356 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
19357 level. There is nothing that a hidden service's operator can do
19358 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
19360 - Clarify a log message specifying the characters permitted in
19361 HiddenServiceAuthorizeClient client names. Previously, the log
19362 message said that "[A-Za-z0-9+-_]" were permitted; that could have
19363 given the impression that every ASCII character between "+" and "_"
19364 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
19367 - Provide a substitute implementation of lround() for MSVC, which
19368 apparently lacks it. Patch from Gisle Vanem.
19369 - Clean up some code issues that prevented Tor from building on older
19370 BSDs. Fixes bug 3894; reported by "grarpamp".
19371 - Search for a platform-specific version of "ar" when cross-compiling.
19372 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
19375 Changes in version 0.2.3.3-alpha - 2011-09-01
19376 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
19377 security, and provides client-side support for the microdescriptor
19378 and optimistic data features introduced earlier in the 0.2.3.x
19379 series. It also includes numerous critical bugfixes in the (optional)
19380 bufferevent-based networking backend.
19382 o Major features (stream isolation):
19383 - You can now configure Tor so that streams from different
19384 applications are isolated on different circuits, to prevent an
19385 attacker who sees your streams as they leave an exit node from
19386 linking your sessions to one another. To do this, choose some way
19387 to distinguish the applications: have them connect to different
19388 SocksPorts, or have one of them use SOCKS4 while the other uses
19389 SOCKS5, or have them pass different authentication strings to the
19390 SOCKS proxy. Then, use the new SocksPort syntax to configure the
19391 degree of isolation you need. This implements Proposal 171.
19392 - There's a new syntax for specifying multiple client ports (such as
19393 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
19394 multiple *Port entries with full addr:port syntax on each.
19395 The old *ListenAddress format is still supported, but you can't
19396 mix it with the new *Port syntax.
19398 o Major features (other):
19399 - Enable microdescriptor fetching by default for clients. This allows
19400 clients to download a much smaller amount of directory information.
19401 To disable it (and go back to the old-style consensus and
19402 descriptors), set "UseMicrodescriptors 0" in your torrc file.
19403 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
19404 "PortForwarding" config option), now supports Windows.
19405 - When using an exit relay running 0.2.3.x, clients can now
19406 "optimistically" send data before the exit relay reports that
19407 the stream has opened. This saves a round trip when starting
19408 connections where the client speaks first (such as web browsing).
19409 This behavior is controlled by a consensus parameter (currently
19410 disabled). To turn it on or off manually, use the "OptimisticData"
19411 torrc option. Implements proposal 181; code by Ian Goldberg.
19413 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
19414 - When using IOCP on Windows, we need to enable Libevent windows
19416 - The IOCP backend now works even when the user has not specified
19417 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
19418 Fixes part of bug 3752.
19419 - Correctly record the bytes we've read and written when using
19420 bufferevents, so that we can include them in our bandwidth history
19421 and advertised bandwidth. Fixes bug 3803.
19422 - Apply rate-limiting only at the bottom of a chain of filtering
19423 bufferevents. This prevents us from filling up internal read
19424 buffers and violating rate-limits when filtering bufferevents
19425 are enabled. Fixes part of bug 3804.
19426 - Add high-watermarks to the output buffers for filtered
19427 bufferevents. This prevents us from filling up internal write
19428 buffers and wasting CPU cycles when filtering bufferevents are
19429 enabled. Fixes part of bug 3804.
19430 - Correctly notice when data has been written from a bufferevent
19431 without flushing it completely. Fixes bug 3805.
19432 - Fix a bug where server-side tunneled bufferevent-based directory
19433 streams would get closed prematurely. Fixes bug 3814.
19434 - Fix a use-after-free error with per-connection rate-limiting
19435 buckets. Fixes bug 3888.
19437 o Major bugfixes (also part of 0.2.2.31-rc):
19438 - If we're configured to write our ControlPorts to disk, only write
19439 them after switching UID and creating the data directory. This way,
19440 we don't fail when starting up with a nonexistent DataDirectory
19441 and a ControlPortWriteToFile setting based on that directory. Fixes
19442 bug 3747; bugfix on Tor 0.2.2.26-beta.
19445 - Added a new CONF_CHANGED event so that controllers can be notified
19446 of any configuration changes made by other controllers, or by the
19447 user. Implements ticket 1692.
19448 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
19449 leak when using bufferevents, and lets Libevent worry about how to
19450 best copy data out of a buffer.
19451 - Replace files in stats/ rather than appending to them. Now that we
19452 include statistics in extra-info descriptors, it makes no sense to
19453 keep old statistics forever. Implements ticket 2930.
19455 o Minor features (build compatibility):
19456 - Limited, experimental support for building with nmake and MSVC.
19457 - Provide a substitute implementation of lround() for MSVC, which
19458 apparently lacks it. Patch from Gisle Vanem.
19460 o Minor features (also part of 0.2.2.31-rc):
19461 - Update to the August 2 2011 Maxmind GeoLite Country database.
19463 o Minor bugfixes (on 0.2.3.x-alpha):
19464 - Fix a spurious warning when parsing SOCKS requests with
19465 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
19466 - Get rid of a harmless warning that could happen on relays running
19467 with bufferevents. The warning was caused by someone doing an http
19468 request to a relay's orport. Also don't warn for a few related
19469 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
19471 o Minor bugfixes (on 2.2.x and earlier):
19472 - Correct the man page to explain that HashedControlPassword and
19473 CookieAuthentication can both be set, in which case either method
19474 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
19475 when we decided to allow these config options to both be set. Issue
19476 raised by bug 3898.
19477 - The "--quiet" and "--hush" options now apply not only to Tor's
19478 behavior before logs are configured, but also to Tor's behavior in
19479 the absence of configured logs. Fixes bug 3550; bugfix on
19482 o Minor bugfixes (also part of 0.2.2.31-rc):
19483 - Write several files in text mode, on OSes that distinguish text
19484 mode from binary mode (namely, Windows). These files are:
19485 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
19486 that collect those statistics; 'client_keys' and 'hostname' for
19487 hidden services that use authentication; and (in the tor-gencert
19488 utility) newly generated identity and signing keys. Previously,
19489 we wouldn't specify text mode or binary mode, leading to an
19490 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
19491 the DirRecordUsageByCountry option which would have triggered
19492 the assertion failure was added), although this assertion failure
19493 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
19494 - Selectively disable deprecation warnings on OS X because Lion
19495 started deprecating the shipped copy of openssl. Fixes bug 3643.
19496 - Remove an extra pair of quotation marks around the error
19497 message in control-port STATUS_GENERAL BUG events. Bugfix on
19498 0.1.2.6-alpha; fixes bug 3732.
19499 - When unable to format an address as a string, report its value
19500 as "???" rather than reusing the last formatted address. Bugfix
19503 o Code simplifications and refactoring:
19504 - Rewrite the listener-selection logic so that parsing which ports
19505 we want to listen on is now separate from binding to the ports
19509 - Building Tor with bufferevent support now requires Libevent
19510 2.0.13-stable or later. Previous versions of Libevent had bugs in
19511 SSL-related bufferevents and related issues that would make Tor
19512 work badly with bufferevents. Requiring 2.0.13-stable also allows
19513 Tor with bufferevents to take advantage of Libevent APIs
19514 introduced after 2.0.8-rc.
19517 Changes in version 0.2.2.32 - 2011-08-27
19518 The Tor 0.2.2 release series is dedicated to the memory of Andreas
19519 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
19520 a founder of the PETS community, a leader in our field, a mentor,
19521 and a friend. He left us with these words: "I had the possibility
19522 to contribute to this world that is not as it should be. I hope I
19523 could help in some areas to make the world a better place, and that
19524 I could also encourage other people to be engaged in improving the
19525 world. Please, stay engaged. This world needs you, your love, your
19526 initiative -- now I cannot be part of that anymore."
19528 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
19529 ready. More than two years in the making, this release features improved
19530 client performance and hidden service reliability, better compatibility
19531 for Android, correct behavior for bridges that listen on more than
19532 one address, more extensible and flexible directory object handling,
19533 better reporting of network statistics, improved code security, and
19534 many many other features and bugfixes.
19537 Changes in version 0.2.2.31-rc - 2011-08-17
19538 Tor 0.2.2.31-rc is the second and hopefully final release candidate
19539 for the Tor 0.2.2.x series.
19542 - Remove an extra pair of quotation marks around the error
19543 message in control-port STATUS_GENERAL BUG events. Bugfix on
19544 0.1.2.6-alpha; fixes bug 3732.
19545 - If we're configured to write our ControlPorts to disk, only write
19546 them after switching UID and creating the data directory. This way,
19547 we don't fail when starting up with a nonexistent DataDirectory
19548 and a ControlPortWriteToFile setting based on that directory. Fixes
19549 bug 3747; bugfix on Tor 0.2.2.26-beta.
19552 - Update to the August 2 2011 Maxmind GeoLite Country database.
19555 - Allow GETINFO fingerprint to return a fingerprint even when
19556 we have not yet built a router descriptor. Fixes bug 3577;
19557 bugfix on 0.2.0.1-alpha.
19558 - Write several files in text mode, on OSes that distinguish text
19559 mode from binary mode (namely, Windows). These files are:
19560 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
19561 that collect those statistics; 'client_keys' and 'hostname' for
19562 hidden services that use authentication; and (in the tor-gencert
19563 utility) newly generated identity and signing keys. Previously,
19564 we wouldn't specify text mode or binary mode, leading to an
19565 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
19566 the DirRecordUsageByCountry option which would have triggered
19567 the assertion failure was added), although this assertion failure
19568 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
19569 - Selectively disable deprecation warnings on OS X because Lion
19570 started deprecating the shipped copy of openssl. Fixes bug 3643.
19571 - When unable to format an address as a string, report its value
19572 as "???" rather than reusing the last formatted address. Bugfix
19576 Changes in version 0.2.3.2-alpha - 2011-07-18
19577 Tor 0.2.3.2-alpha introduces two new experimental features:
19578 microdescriptors and pluggable transports. It also continues cleaning
19579 up a variety of recently introduced features.
19582 - Clients can now use microdescriptors instead of regular descriptors
19583 to build circuits. Microdescriptors are authority-generated
19584 summaries of regular descriptors' contents, designed to change
19585 very rarely (see proposal 158 for details). This feature is
19586 designed to save bandwidth, especially for clients on slow internet
19587 connections. It's off by default for now, since nearly no caches
19588 support it, but it will be on-by-default for clients in a future
19589 version. You can use the UseMicrodescriptors option to turn it on.
19590 - Tor clients using bridges can now be configured to use a separate
19591 'transport' proxy for each bridge. This approach helps to resist
19592 censorship by allowing bridges to use protocol obfuscation
19593 plugins. It implements part of proposal 180. Implements ticket 2841.
19594 - While we're trying to bootstrap, record how many TLS connections
19595 fail in each state, and report which states saw the most failures
19596 in response to any bootstrap failures. This feature may speed up
19597 diagnosis of censorship events. Implements ticket 3116.
19599 o Major bugfixes (on 0.2.3.1-alpha):
19600 - When configuring a large set of nodes in EntryNodes (as with
19601 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
19602 random subset to be guards, and choose them in random
19603 order. Fixes bug 2798.
19604 - Tor could crash when remembering a consensus in a non-used consensus
19605 flavor without having a current consensus set. Fixes bug 3361.
19606 - Comparing an unknown address to a microdescriptor's shortened exit
19607 policy would always give a "rejected" result. Fixes bug 3599.
19608 - Using microdescriptors as a client no longer prevents Tor from
19609 uploading and downloading hidden service descriptors. Fixes
19613 - Allow nameservers with IPv6 address. Resolves bug 2574.
19614 - Accept attempts to include a password authenticator in the
19615 handshake, as supported by SOCKS5. This handles SOCKS clients that
19616 don't know how to omit a password when authenticating. Resolves
19618 - When configuring a large set of nodes in EntryNodes, and there are
19619 enough of them listed as Guard so that we don't need to consider
19620 the non-guard entries, prefer the ones listed with the Guard flag.
19621 - Check for and recover from inconsistency in the microdescriptor
19622 cache. This will make it harder for us to accidentally free a
19623 microdescriptor without removing it from the appropriate data
19624 structures. Fixes issue 3135; issue noted by "wanoskarnet".
19625 - Log SSL state transitions at log level DEBUG, log domain
19626 HANDSHAKE. This can be useful for debugging censorship events.
19627 Implements ticket 3264.
19628 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
19629 implements ticket 3439.
19631 o Minor bugfixes (on 0.2.3.1-alpha):
19632 - Do not free all general-purpose regular descriptors just
19633 because microdescriptor use is enabled. Fixes bug 3113.
19634 - Correctly link libevent_openssl when --enable-static-libevent
19635 is passed to configure. Fixes bug 3118.
19636 - Bridges should not complain during their heartbeat log messages that
19637 they are unlisted in the consensus: that's more or less the point
19638 of being a bridge. Fixes bug 3183.
19639 - Report a SIGNAL event to controllers when acting on a delayed
19640 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
19641 event to the controller if we acted on a SIGNAL NEWNYM command
19642 immediately, and otherwise not report a SIGNAL event for the
19643 command at all. Fixes bug 3349.
19644 - Fix a crash when handling the SIGNAL controller command or
19645 reporting ERR-level status events with bufferevents enabled. Found
19646 by Robert Ransom. Fixes bug 3367.
19647 - Always ship the tor-fw-helper manpage in our release tarballs.
19648 Fixes bug 3389. Reported by Stephen Walker.
19649 - Fix a class of double-mark-for-close bugs when bufferevents
19650 are enabled. Fixes bug 3403.
19651 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
19652 - Add SIGNAL to the list returned by the 'GETINFO events/names'
19653 control-port command. Fixes part of bug 3465.
19654 - Prevent using negative indices during unit test runs when read_all()
19655 fails. Spotted by coverity.
19656 - Fix a rare memory leak when checking the nodelist without it being
19657 present. Found by coverity.
19658 - Only try to download a microdescriptor-flavored consensus from
19659 a directory cache that provides them.
19661 o Minor bugfixes (on 0.2.2.x and earlier):
19662 - Assert that hidden-service-related operations are not performed
19663 using single-hop circuits. Previously, Tor would assert that
19664 client-side streams are not attached to single-hop circuits,
19665 but not that other sensitive operations on the client and service
19666 side are not performed using single-hop circuits. Fixes bug 3332;
19668 - Don't publish a new relay descriptor when we reload our onion key,
19669 unless the onion key has actually changed. Fixes bug 3263 and
19670 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
19671 - Allow GETINFO fingerprint to return a fingerprint even when
19672 we have not yet built a router descriptor. Fixes bug 3577;
19673 bugfix on 0.2.0.1-alpha.
19674 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
19675 on 0.2.2.4-alpha; fixes bug 3427.
19677 o Code simplification and refactoring:
19678 - Use tor_sscanf() in place of scanf() in more places through the
19679 code. This makes us a little more locale-independent, and
19680 should help shut up code-analysis tools that can't tell
19681 a safe sscanf string from a dangerous one.
19682 - Use tt_assert(), not tor_assert(), for checking for test failures.
19683 This makes the unit tests more able to go on in the event that
19685 - Split connection_about_to_close() into separate functions for each
19689 - On Windows, we now define the _WIN32_WINNT macros only if they
19690 are not already defined. This lets the person building Tor decide,
19691 if they want, to require a later version of Windows.
19694 Changes in version 0.2.2.30-rc - 2011-07-07
19695 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
19696 series. It fixes a few smaller bugs, but generally appears stable.
19697 Please test it and let us know whether it is!
19700 - Send a SUCCEEDED stream event to the controller when a reverse
19701 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
19702 discovered by katmagic.
19703 - Always NUL-terminate the sun_path field of a sockaddr_un before
19704 passing it to the kernel. (Not a security issue: kernels are
19705 smart enough to reject bad sockaddr_uns.) Found by Coverity;
19706 CID #428. Bugfix on Tor 0.2.0.3-alpha.
19707 - Don't stack-allocate the list of supplementary GIDs when we're
19708 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
19709 could take up to 256K, which is way too much stack. Found by
19710 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
19711 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
19712 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
19713 fixes part of bug 3465.
19714 - Fix a memory leak when receiving a descriptor for a hidden
19715 service we didn't ask for. Found by Coverity; CID #30. Bugfix
19719 - Update to the July 1 2011 Maxmind GeoLite Country database.
19722 Changes in version 0.2.2.29-beta - 2011-06-20
19723 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
19724 have bridge lines in their torrc but don't want to use them; gets
19725 us closer to having the control socket feature working on Debian;
19726 and fixes a variety of smaller bugs.
19729 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
19730 When we changed the default behavior to "use bridges if any
19731 are listed in the torrc", we surprised users who had bridges
19732 in their torrc files but who didn't actually want to use them.
19733 Partial resolution for bug 3354.
19736 - Don't attach new streams to old rendezvous circuits after SIGNAL
19737 NEWNYM. Previously, we would keep using an existing rendezvous
19738 circuit if it remained open (i.e. if it were kept open by a
19739 long-lived stream, or if a new stream were attached to it before
19740 Tor could notice that it was old and no longer in use). Bugfix on
19741 0.1.1.15-rc; fixes bug 3375.
19744 - Fix a bug when using ControlSocketsGroupWritable with User. The
19745 directory's group would be checked against the current group, not
19746 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
19747 bugfix on 0.2.2.26-beta.
19748 - Make connection_printf_to_buf()'s behavior sane. Its callers
19749 expect it to emit a CRLF iff the format string ends with CRLF;
19750 it actually emitted a CRLF iff (a) the format string ended with
19751 CRLF or (b) the resulting string was over 1023 characters long or
19752 (c) the format string did not end with CRLF *and* the resulting
19753 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
19754 fixes part of bug 3407.
19755 - Make send_control_event_impl()'s behavior sane. Its callers
19756 expect it to always emit a CRLF at the end of the string; it
19757 might have emitted extra control characters as well. Bugfix on
19758 0.1.1.9-alpha; fixes another part of bug 3407.
19759 - Make crypto_rand_int() check the value of its input correctly.
19760 Previously, it accepted values up to UINT_MAX, but could return a
19761 negative number if given a value above INT_MAX+1. Found by George
19762 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
19763 - Avoid a segfault when reading a malformed circuit build state
19764 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
19766 - When asked about a DNS record type we don't support via a
19767 client DNSPort, reply with NOTIMPL rather than an empty
19768 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
19769 - Fix a rare memory leak during stats writing. Found by coverity.
19772 - Update to the June 1 2011 Maxmind GeoLite Country database.
19774 o Code simplifications and refactoring:
19775 - Remove some dead code as indicated by coverity.
19776 - Remove a few dead assignments during router parsing. Found by
19778 - Add some forgotten return value checks during unit tests. Found
19780 - Don't use 1-bit wide signed bit fields. Found by coverity.
19783 Changes in version 0.2.2.28-beta - 2011-06-04
19784 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
19785 fixed a big bug in whether relays stay in the consensus consistently,
19786 we moved closer to handling bridges and hidden services correctly,
19787 and we started the process of better handling the dreaded "my Vidalia
19788 died, and now my Tor demands a password when I try to reconnect to it"
19792 - Don't decide to make a new descriptor when receiving a HUP signal.
19793 This bug has caused a lot of 0.2.2.x relays to disappear from the
19794 consensus periodically. Fixes the most common case of triggering
19795 bug 1810; bugfix on 0.2.2.7-alpha.
19796 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
19797 - Don't try to build descriptors if "ORPort auto" is set and we
19798 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
19800 - Resolve a crash that occurred when setting BridgeRelay to 1 with
19801 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
19802 - Apply circuit timeouts to opened hidden-service-related circuits
19803 based on the correct start time. Previously, we would apply the
19804 circuit build timeout based on time since the circuit's creation;
19805 it was supposed to be applied based on time since the circuit
19806 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
19807 - Use the same circuit timeout for client-side introduction
19808 circuits as for other four-hop circuits, rather than the timeout
19809 for single-hop directory-fetch circuits; the shorter timeout may
19810 have been appropriate with the static circuit build timeout in
19811 0.2.1.x and earlier, but caused many hidden service access attempts
19812 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
19813 on 0.2.2.2-alpha; fixes another part of bug 1297.
19814 - In ticket 2511 we fixed a case where you could use an unconfigured
19815 bridge if you had configured it as a bridge the last time you ran
19816 Tor. Now fix another edge case: if you had configured it as a bridge
19817 but then switched to a different bridge via the controller, you
19818 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
19822 - Add an __OwningControllerProcess configuration option and a
19823 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
19824 that when it exits, Tor will shut down. Implements feature 3049.
19825 - If "UseBridges 1" is set and no bridges are configured, Tor will
19826 now refuse to build any circuits until some bridges are set.
19827 If "UseBridges auto" is set, Tor will use bridges if they are
19828 configured and we are not running as a server, but otherwise will
19829 make circuits as usual. The new default is "auto". Patch by anonym,
19830 so the Tails LiveCD can stop automatically revealing you as a Tor
19834 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
19835 - Remove a trailing asterisk from "exit-policy/default" in the
19836 output of the control port command "GETINFO info/names". Bugfix
19838 - Use a wide type to hold sockets when built for 64-bit Windows builds.
19840 - Warn when the user configures two HiddenServiceDir lines that point
19841 to the same directory. Bugfix on 0.0.6 (the version introducing
19842 HiddenServiceDir); fixes bug 3289.
19843 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
19844 part of bug 2748; bugfix on 0.2.0.10-alpha.
19845 - Log malformed requests for rendezvous descriptors as protocol
19846 warnings, not warnings. Also, use a more informative log message
19847 in case someone sees it at log level warning without prior
19848 info-level messages. Fixes the other part of bug 2748; bugfix
19850 - Clear the table recording the time of the last request for each
19851 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
19852 Previously, we would clear our HS descriptor cache on SIGNAL
19853 NEWNYM, but if we had previously retrieved a descriptor (or tried
19854 to) from every directory responsible for it, we would refuse to
19855 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
19857 - Fix a log message that said "bits" while displaying a value in
19858 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
19860 - When checking for 1024-bit keys, check for 1024 bits, not 128
19861 bytes. This allows Tor to correctly discard keys of length 1017
19862 through 1023. Bugfix on 0.0.9pre5.
19865 - Relays now log the reason for publishing a new relay descriptor,
19866 so we have a better chance of hunting down instances of bug 1810.
19867 Resolves ticket 3252.
19868 - Revise most log messages that refer to nodes by nickname to
19869 instead use the "$key=nickname at address" format. This should be
19870 more useful, especially since nicknames are less and less likely
19871 to be unique. Resolves ticket 3045.
19872 - Log (at info level) when purging pieces of hidden-service-client
19873 state because of SIGNAL NEWNYM.
19876 - Remove undocumented option "-F" from tor-resolve: it hasn't done
19877 anything since 0.2.1.16-rc.
19880 Changes in version 0.2.2.27-beta - 2011-05-18
19881 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
19882 release, and also adds a few more general bugfixes.
19885 - Fix a crash bug when changing bridges in a running Tor process.
19886 Fixes bug 3213; bugfix on 0.2.2.26-beta.
19887 - When the controller configures a new bridge, don't wait 10 to 60
19888 seconds before trying to fetch its descriptor. Bugfix on
19889 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
19892 - Require that onion keys have exponent 65537 in microdescriptors too.
19893 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
19894 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
19895 Changed the limit to 512 characters by removing base64 newlines.
19896 Fixes bug 2752. Fix by Michael Yakubovich.
19897 - When a client starts or stops using bridges, never use a circuit
19898 that was built before the configuration change. This behavior could
19899 put at risk a user who uses bridges to ensure that her traffic
19900 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
19904 Changes in version 0.2.2.26-beta - 2011-05-17
19905 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
19906 also introduces a new "socksport auto" approach that should make it
19907 easier to run multiple Tors on the same system, and does a lot of
19908 cleanup to get us closer to a release candidate.
19910 o Security/privacy fixes:
19911 - Replace all potentially sensitive memory comparison operations
19912 with versions whose runtime does not depend on the data being
19913 compared. This will help resist a class of attacks where an
19914 adversary can use variations in timing information to learn
19915 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19916 implementation by Robert Ransom based partially on code by DJB.)
19917 - When receiving a hidden service descriptor, check that it is for
19918 the hidden service we wanted. Previously, Tor would store any
19919 hidden service descriptors that a directory gave it, whether it
19920 wanted them or not. This wouldn't have let an attacker impersonate
19921 a hidden service, but it did let directories pre-seed a client
19922 with descriptors that it didn't want. Bugfix on 0.0.6.
19923 - On SIGHUP, do not clear out all TrackHostExits mappings, client
19924 DNS cache entries, and virtual address mappings: that's what
19925 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
19928 - The options SocksPort, ControlPort, and so on now all accept a
19929 value "auto" that opens a socket on an OS-selected port. A
19930 new ControlPortWriteToFile option tells Tor to write its
19931 actual control port or ports to a chosen file. If the option
19932 ControlPortFileGroupReadable is set, the file is created as
19933 group-readable. Now users can run two Tor clients on the same
19934 system without needing to manually mess with parameters. Resolves
19935 part of ticket 3076.
19936 - Set SO_REUSEADDR on all sockets, not just listeners. This should
19937 help busy exit nodes avoid running out of useable ports just
19938 because all the ports have been used in the near past. Resolves
19942 - New "GETINFO net/listeners/(type)" controller command to return
19943 a list of addresses and ports that are bound for listeners for a
19944 given connection type. This is useful when the user has configured
19945 "SocksPort auto" and the controller needs to know which port got
19946 chosen. Resolves another part of ticket 3076.
19947 - Add a new ControlSocketsGroupWritable configuration option: when
19948 it is turned on, ControlSockets are group-writeable by the default
19949 group of the current user. Patch by Jérémy Bobbio; implements
19951 - Tor now refuses to create a ControlSocket in a directory that is
19952 world-readable (or group-readable if ControlSocketsGroupWritable
19953 is 0). This is necessary because some operating systems do not
19954 enforce permissions on an AF_UNIX sockets. Permissions on the
19955 directory holding the socket, however, seems to work everywhere.
19956 - Rate-limit a warning about failures to download v2 networkstatus
19957 documents. Resolves part of bug 1352.
19958 - Backport code from 0.2.3.x that allows directory authorities to
19959 clean their microdescriptor caches. Needed to resolve bug 2230.
19960 - When an HTTPS proxy reports "403 Forbidden", we now explain
19961 what it means rather than calling it an unexpected status code.
19962 Closes bug 2503. Patch from Michael Yakubovich.
19963 - Update to the May 1 2011 Maxmind GeoLite Country database.
19966 - Authorities now clean their microdesc cache periodically and when
19967 reading from disk initially, not only when adding new descriptors.
19968 This prevents a bug where we could lose microdescriptors. Bugfix
19969 on 0.2.2.6-alpha. Fixes bug 2230.
19970 - Do not crash when our configuration file becomes unreadable, for
19971 example due to a permissions change, between when we start up
19972 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
19974 - Avoid a bug that would keep us from replacing a microdescriptor
19975 cache on Windows. (We would try to replace the file while still
19976 holding it open. That's fine on Unix, but Windows doesn't let us
19977 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
19978 - Add missing explanations for the authority-related torrc options
19979 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
19980 man page. Resolves issue 2379.
19981 - As an authority, do not upload our own vote or signature set to
19982 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
19983 it would get flagged as a duplicate. Resolves bug 3026.
19984 - Accept hidden service descriptors if we think we might be a hidden
19985 service directory, regardless of what our consensus says. This
19986 helps robustness, since clients and hidden services can sometimes
19987 have a more up-to-date view of the network consensus than we do,
19988 and if they think that the directory authorities list us a HSDir,
19989 we might actually be one. Related to bug 2732; bugfix on
19991 - When a controller changes TrackHostExits, remove mappings for
19992 hosts that should no longer have their exits tracked. Bugfix on
19994 - When a controller changes VirtualAddrNetwork, remove any mappings
19995 for hosts that were automapped to the old network. Bugfix on
19997 - When a controller changes one of the AutomapHosts* options, remove
19998 any mappings for hosts that should no longer be automapped. Bugfix
20000 - Do not reset the bridge descriptor download status every time we
20001 re-parse our configuration or get a configuration change. Fixes
20002 bug 3019; bugfix on 0.2.0.3-alpha.
20004 o Minor bugfixes (code cleanup):
20005 - When loading the microdesc journal, remember its current size.
20006 In 0.2.2, this helps prevent the microdesc journal from growing
20007 without limit on authorities (who are the only ones to use it in
20008 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
20009 Fix posted by "cypherpunks."
20010 - The microdesc journal is supposed to get rebuilt only if it is
20011 at least _half_ the length of the store, not _twice_ the length
20012 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
20013 - Fix a potential null-pointer dereference while computing a
20014 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
20016 - Avoid a possible null-pointer dereference when rebuilding the mdesc
20017 cache without actually having any descriptors to cache. Bugfix on
20018 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
20019 - If we fail to compute the identity digest of a v3 legacy keypair,
20020 warn, and don't use a buffer-full of junk instead. Bugfix on
20021 0.2.1.1-alpha; fixes bug 3106.
20022 - Resolve an untriggerable issue in smartlist_string_num_isin(),
20023 where if the function had ever in the future been used to check
20024 for the presence of a too-large number, it would have given an
20025 incorrect result. (Fortunately, we only used it for 16-bit
20026 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
20027 - Require that introduction point keys and onion handshake keys
20028 have a public exponent of 65537. Starts to fix bug 3207; bugfix
20031 o Removed features:
20032 - Caches no longer download and serve v2 networkstatus documents
20033 unless FetchV2Networkstatus flag is set: these documents haven't
20034 haven't been used by clients or relays since 0.2.0.x. Resolves
20038 Changes in version 0.2.3.1-alpha - 2011-05-05
20039 Tor 0.2.3.1-alpha adds some new experimental features, including support
20040 for an improved network IO backend, IOCP networking on Windows,
20041 microdescriptor caching, "fast-start" support for streams, and automatic
20042 home router configuration. There are also numerous internal improvements
20043 to try to make the code easier for developers to work with.
20045 This is the first alpha release in a new series, so expect there to be
20046 bugs. Users who would rather test out a more stable branch should
20047 stay with 0.2.2.x for now.
20050 - Tor can now optionally build with the "bufferevents" buffered IO
20051 backend provided by Libevent 2. To use this feature, make sure you
20052 have the latest possible version of Libevent, and pass the
20053 --enable-bufferevents flag to configure when building Tor from
20054 source. This feature will make our networking code more flexible,
20055 let us stack layers on each other, and let us use more efficient
20056 zero-copy transports where available.
20057 - As an experimental feature, Tor can use IOCP for networking on Windows.
20058 Once this code is tuned and optimized, it promises much better
20059 performance than the select-based backend we've used in the past. To
20060 try this feature, you must build Tor with Libevent 2, configure Tor
20061 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
20062 your torrc. There are known bugs here: only try this if you can help
20063 debug it as it breaks.
20064 - The EntryNodes option can now include country codes like {de} or IP
20065 addresses or network masks. Previously we had disallowed these options
20066 because we didn't have an efficient way to keep the list up to
20067 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
20068 - Exit nodes now accept and queue data on not-yet-connected streams.
20069 Previously, the client wasn't allowed to send data until the stream was
20070 connected, which slowed down all connections. This change will enable
20071 clients to perform a "fast-start" on streams and send data without
20072 having to wait for a confirmation that the stream has opened. (Patch
20073 from Ian Goldberg; implements the server side of Proposal 174.)
20074 - Tor now has initial support for automatic port mapping on the many
20075 home routers that support NAT-PMP or UPnP. (Not yet supported on
20076 Windows). To build the support code, you'll need to have libnatpnp
20077 library and/or the libminiupnpc library, and you'll need to enable the
20078 feature specifically by passing "--enable-upnp" and/or
20079 "--enable-natpnp" to configure. To turn it on, use the new
20080 PortForwarding option.
20081 - Caches now download, cache, and serve multiple "flavors" of the
20082 consensus, including a flavor that describes microdescriptors.
20083 - Caches now download, cache, and serve microdescriptors -- small
20084 summaries of router descriptors that are authenticated by all of the
20085 directory authorities. Once enough caches are running this code,
20086 clients will be able to save significant amounts of directory bandwidth
20087 by downloading microdescriptors instead of router descriptors.
20090 - Make logging resolution configurable with a new LogTimeGranularity
20091 option, and change the default from 1 millisecond to 1 second.
20092 Implements enhancement 1668.
20093 - We log which torrc file we're using on startup. Implements ticket
20095 - Ordinarily, Tor does not count traffic from private addresses (like
20096 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
20097 There is now a new option, CountPrivateBandwidth, to disable this
20098 behavior. Patch from Daniel Cagara.
20099 - New --enable-static-tor configure option for building Tor as
20100 statically as possible. Idea, general hackery and thoughts from
20101 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
20103 - If you set the NumCPUs option to 0, Tor will now try to detect how
20104 many CPUs you have. This is the new default behavior.
20105 - Turn on directory request statistics by default and include them in
20106 extra-info descriptors. Don't break if we have no GeoIP database.
20107 - Relays that set "ConnDirectionStatistics 1" write statistics on the
20108 bidirectional use of connections to disk every 24 hours.
20109 - Add a GeoIP file digest to the extra-info descriptor. Implements
20111 - The NodeFamily option -- which let you declare that you want to
20112 consider nodes to be part of a family whether they list themselves
20113 that way or not -- now allows IP address ranges and country codes.
20114 - Add a new 'Heartbeat' log message type to periodically log a message
20115 describing Tor's status at level Notice. This feature is meant for
20116 operators who log at notice, and want to make sure that their Tor
20117 server is still working. Implementation by George Kadianakis.
20119 o Minor bugfixes (on 0.2.2.25-alpha):
20120 - When loading the microdesc journal, remember its current size.
20121 In 0.2.2, this helps prevent the microdesc journal from growing
20122 without limit on authorities (who are the only ones to use it in
20123 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
20124 Fix posted by "cypherpunks."
20125 - The microdesc journal is supposed to get rebuilt only if it is
20126 at least _half_ the length of the store, not _twice_ the length
20127 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
20128 - If as an authority we fail to compute the identity digest of a v3
20129 legacy keypair, warn, and don't use a buffer-full of junk instead.
20130 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
20131 - Authorities now clean their microdesc cache periodically and when
20132 reading from disk initially, not only when adding new descriptors.
20133 This prevents a bug where we could lose microdescriptors. Bugfix
20136 o Minor features (controller):
20137 - Add a new SIGNAL event to the controller interface so that
20138 controllers can be notified when Tor handles a signal. Resolves
20139 issue 1955. Patch by John Brooks.
20140 - Add a new GETINFO option to get total bytes read and written. Patch
20141 from pipe, revised by atagar. Resolves ticket 2345.
20142 - Implement some GETINFO controller fields to provide information about
20143 the Tor process's pid, euid, username, and resource limits.
20146 - Our build system requires automake 1.6 or later to create the
20147 Makefile.in files. Previously, you could have used 1.4.
20148 This only affects developers and people building Tor from git;
20149 people who build Tor from the source distribution without changing
20150 the Makefile.am files should be fine.
20151 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
20152 so on. This is more robust against some of the failure modes
20153 associated with running the autotools pieces on their own.
20155 o Minor packaging issues:
20156 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
20157 already created. Patch from Andreas Stieger. Fixes bug 2573.
20159 o Code simplifications and refactoring:
20160 - A major revision to our internal node-selecting and listing logic.
20161 Tor already had at least two major ways to look at the question of
20162 "which Tor servers do we know about": a list of router descriptors,
20163 and a list of entries in the current consensus. With
20164 microdescriptors, we're adding a third. Having so many systems
20165 without an abstraction layer over them was hurting the codebase.
20166 Now, we have a new "node_t" abstraction that presents a consistent
20167 interface to a client's view of a Tor node, and holds (nearly) all
20168 of the mutable state formerly in routerinfo_t and routerstatus_t.
20169 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
20170 no longer link against Libevent: they never used it, but
20171 our library structure used to force them to link it.
20173 o Removed features:
20174 - Remove some old code to work around even older versions of Tor that
20175 used forked processes to handle DNS requests. Such versions of Tor
20176 are no longer in use as servers.
20178 o Documentation fixes:
20179 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
20180 - Add missing documentation for the authority-related torrc options
20181 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
20185 Changes in version 0.2.2.25-alpha - 2011-04-29
20186 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
20187 robust, routers no longer overreport their bandwidth, Win7 should crash
20188 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
20189 now prevents hidden service-related activity from being linkable. It
20190 provides more information to Vidalia so you can see if your bridge is
20191 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
20192 StrictNodes configuration options to make them more reliable, more
20193 understandable, and more regularly applied. If you use those options,
20194 please see the revised documentation for them in the manual page.
20197 - Relays were publishing grossly inflated bandwidth values because
20198 they were writing their state files wrong--now they write the
20199 correct value. Also, resume reading bandwidth history from the
20200 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
20201 - Improve hidden service robustness: When we find that we have
20202 extended a hidden service's introduction circuit to a relay not
20203 listed as an introduction point in the HS descriptor we currently
20204 have, retry with an introduction point from the current
20205 descriptor. Previously we would just give up. Fixes bugs 1024 and
20206 1930; bugfix on 0.2.0.10-alpha.
20207 - Clients now stop trying to use an exit node associated with a given
20208 destination by TrackHostExits if they fail to reach that exit node.
20209 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
20210 - Fix crash bug on platforms where gmtime and localtime can return
20211 NULL. Windows 7 users were running into this one. Fixes part of bug
20212 2077. Bugfix on all versions of Tor. Found by boboper.
20214 o Security and stability fixes:
20215 - Don't double-free a parsable, but invalid, microdescriptor, even if
20216 it is followed in the blob we're parsing by an unparsable
20217 microdescriptor. Fixes an issue reported in a comment on bug 2954.
20218 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
20219 - If the Nickname configuration option isn't given, Tor would pick a
20220 nickname based on the local hostname as the nickname for a relay.
20221 Because nicknames are not very important in today's Tor and the
20222 "Unnamed" nickname has been implemented, this is now problematic
20223 behavior: It leaks information about the hostname without being
20224 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
20225 introduced the Unnamed nickname. Reported by tagnaq.
20226 - Fix an uncommon assertion failure when running with DNSPort under
20227 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
20228 - Avoid linkability based on cached hidden service descriptors: forget
20229 all hidden service descriptors cached as a client when processing a
20230 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
20233 - Export GeoIP information on bridge usage to controllers even if we
20234 have not yet been running for 24 hours. Now Vidalia bridge operators
20235 can get more accurate and immediate feedback about their
20236 contributions to the network.
20238 o Major features and bugfixes (node selection):
20239 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
20240 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
20241 options. Previously, we had been ambiguous in describing what
20242 counted as an "exit" node, and what operations exactly "StrictNodes
20243 0" would permit. This created confusion when people saw nodes built
20244 through unexpected circuits, and made it hard to tell real bugs from
20245 surprises. Now the intended behavior is:
20246 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
20247 a node that delivers user traffic outside the Tor network.
20248 . "Entry", in the context of EntryNodes, means a node used as the
20249 first hop of a multihop circuit. It doesn't include direct
20250 connections to directory servers.
20251 . "ExcludeNodes" applies to all nodes.
20252 . "StrictNodes" changes the behavior of ExcludeNodes only. When
20253 StrictNodes is set, Tor should avoid all nodes listed in
20254 ExcludeNodes, even when it will make user requests fail. When
20255 StrictNodes is *not* set, then Tor should follow ExcludeNodes
20256 whenever it can, except when it must use an excluded node to
20257 perform self-tests, connect to a hidden service, provide a
20258 hidden service, fulfill a .exit request, upload directory
20259 information, or fetch directory information.
20260 Collectively, the changes to implement the behavior fix bug 1090.
20261 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
20262 a node is listed in both, it's treated as excluded.
20263 - ExcludeNodes now applies to directory nodes -- as a preference if
20264 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
20265 Don't exclude all the directory authorities and set StrictNodes to 1
20266 unless you really want your Tor to break.
20267 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
20268 - ExcludeExitNodes now overrides .exit requests.
20269 - We don't use bridges listed in ExcludeNodes.
20270 - When StrictNodes is 1:
20271 . We now apply ExcludeNodes to hidden service introduction points
20272 and to rendezvous points selected by hidden service users. This
20273 can make your hidden service less reliable: use it with caution!
20274 . If we have used ExcludeNodes on ourself, do not try relay
20275 reachability self-tests.
20276 . If we have excluded all the directory authorities, we will not
20277 even try to upload our descriptor if we're a relay.
20278 . Do not honor .exit requests to an excluded node.
20279 - Remove a misfeature that caused us to ignore the Fast/Stable flags
20280 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
20281 - When the set of permitted nodes changes, we now remove any mappings
20282 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
20284 - We never cannibalize a circuit that had excluded nodes on it, even
20285 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
20286 - Revert a change where we would be laxer about attaching streams to
20287 circuits than when building the circuits. This was meant to prevent
20288 a set of bugs where streams were never attachable, but our improved
20289 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
20290 - Keep track of how many times we launch a new circuit to handle a
20291 given stream. Too many launches could indicate an inconsistency
20292 between our "launch a circuit to handle this stream" logic and our
20293 "attach this stream to one of the available circuits" logic.
20294 - Improve log messages related to excluded nodes.
20297 - Fix a spurious warning when moving from a short month to a long
20298 month on relays with month-based BandwidthAccounting. Bugfix on
20299 0.2.2.17-alpha; fixes bug 3020.
20300 - When a client finds that an origin circuit has run out of 16-bit
20301 stream IDs, we now mark it as unusable for new streams. Previously,
20302 we would try to close the entire circuit. Bugfix on 0.0.6.
20303 - Add a forgotten cast that caused a compile warning on OS X 10.6.
20304 Bugfix on 0.2.2.24-alpha.
20305 - Be more careful about reporting the correct error from a failed
20306 connect() system call. Under some circumstances, it was possible to
20307 look at an incorrect value for errno when sending the end reason.
20308 Bugfix on 0.1.0.1-rc.
20309 - Correctly handle an "impossible" overflow cases in connection byte
20310 counting, where we write or read more than 4GB on an edge connection
20311 in a single second. Bugfix on 0.1.2.8-beta.
20312 - Correct the warning displayed when a rendezvous descriptor exceeds
20313 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20315 - Clients and hidden services now use HSDir-flagged relays for hidden
20316 service descriptor downloads and uploads even if the relays have no
20317 DirPort set and the client has disabled TunnelDirConns. This will
20318 eventually allow us to give the HSDir flag to relays with no
20319 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
20320 - Downgrade "no current certificates known for authority" message from
20321 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
20322 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
20323 2917. Bugfix on 0.1.1.1-alpha.
20324 - Only limit the lengths of single HS descriptors, even when multiple
20325 HS descriptors are published to an HSDir relay in a single POST
20326 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
20327 - Write the current time into the LastWritten line in our state file,
20328 rather than the time from the previous write attempt. Also, stop
20329 trying to use a time of -1 in our log statements. Fixes bug 3039;
20330 bugfix on 0.2.2.14-alpha.
20331 - Be more consistent in our treatment of file system paths. "~" should
20332 get expanded to the user's home directory in the Log config option.
20333 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
20334 feature for the -f and --DataDirectory options.
20337 - Make sure every relay writes a state file at least every 12 hours.
20338 Previously, a relay could go for weeks without writing its state
20339 file, and on a crash could lose its bandwidth history, capacity
20340 estimates, client country statistics, and so on. Addresses bug 3012.
20341 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
20342 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
20343 clients are already deprecated because of security bugs.
20344 - Don't allow v0 hidden service authorities to act as clients.
20345 Required by fix for bug 3000.
20346 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
20347 by fix for bug 3000.
20348 - Ensure that no empty [dirreq-](read|write)-history lines are added
20349 to an extrainfo document. Implements ticket 2497.
20351 o Code simplification and refactoring:
20352 - Remove workaround code to handle directory responses from servers
20353 that had bug 539 (they would send HTTP status 503 responses _and_
20354 send a body too). Since only server versions before
20355 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
20356 keep the workaround in place.
20357 - Remove the old 'fuzzy time' logic. It was supposed to be used for
20358 handling calculations where we have a known amount of clock skew and
20359 an allowed amount of unknown skew. But we only used it in three
20360 places, and we never adjusted the known/unknown skew values. This is
20361 still something we might want to do someday, but if we do, we'll
20362 want to do it differently.
20363 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20364 None of the cases where we did this before were wrong, but by making
20365 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20366 - Use GetTempDir to find the proper temporary directory location on
20367 Windows when generating temporary files for the unit tests. Patch by
20371 Changes in version 0.2.2.24-alpha - 2011-04-08
20372 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
20373 prevented Tor clients from effectively using "multihomed" bridges,
20374 that is, bridges that listen on multiple ports or IP addresses so users
20375 can continue to use some of their addresses even if others get blocked.
20378 - Fix a bug where bridge users who configure the non-canonical
20379 address of a bridge automatically switch to its canonical
20380 address. If a bridge listens at more than one address, it should be
20381 able to advertise those addresses independently and any non-blocked
20382 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
20384 - If you configured Tor to use bridge A, and then quit and
20385 configured Tor to use bridge B instead, it would happily continue
20386 to use bridge A if it's still reachable. While this behavior is
20387 a feature if your goal is connectivity, in some scenarios it's a
20388 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
20389 - Directory authorities now use data collected from their own
20390 uptime observations when choosing whether to assign the HSDir flag
20391 to relays, instead of trusting the uptime value the relay reports in
20392 its descriptor. This change helps prevent an attack where a small
20393 set of nodes with frequently-changing identity keys can blackhole
20394 a hidden service. (Only authorities need upgrade; others will be
20395 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
20398 - When we restart our relay, we might get a successful connection
20399 from the outside before we've started our reachability tests,
20400 triggering a warning: "ORPort found reachable, but I have no
20401 routerinfo yet. Failing to inform controller of success." This
20402 bug was harmless unless Tor is running under a controller
20403 like Vidalia, in which case the controller would never get a
20404 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
20406 - Make directory authorities more accurate at recording when
20407 relays that have failed several reachability tests became
20408 unreachable, so we can provide more accuracy at assigning Stable,
20409 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
20410 - Fix an issue that prevented static linking of libevent on
20411 some platforms (notably Linux). Fixes bug 2698; bugfix on
20412 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
20413 the --with-static-libevent configure option).
20414 - We now ask the other side of a stream (the client or the exit)
20415 for more data on that stream when the amount of queued data on
20416 that stream dips low enough. Previously, we wouldn't ask the
20417 other side for more data until either it sent us more data (which
20418 it wasn't supposed to do if it had exhausted its window!) or we
20419 had completely flushed all our queued data. This flow control fix
20420 should improve throughput. Fixes bug 2756; bugfix on the earliest
20421 released versions of Tor (svn commit r152).
20422 - Avoid a double-mark-for-free warning when failing to attach a
20423 transparent proxy connection. (We thought we had fixed this in
20424 0.2.2.23-alpha, but it turns out our fix was checking the wrong
20425 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
20426 bug) and 0.2.2.23-alpha (the incorrect fix).
20427 - When warning about missing zlib development packages during compile,
20428 give the correct package names. Bugfix on 0.2.0.1-alpha.
20431 - Directory authorities now log the source of a rejected POSTed v3
20432 networkstatus vote.
20433 - Make compilation with clang possible when using
20434 --enable-gcc-warnings by removing two warning options that clang
20435 hasn't implemented yet and by fixing a few warnings. Implements
20437 - When expiring circuits, use microsecond timers rather than
20438 one-second timers. This can avoid an unpleasant situation where a
20439 circuit is launched near the end of one second and expired right
20440 near the beginning of the next, and prevent fluctuations in circuit
20442 - Use computed circuit-build timeouts to decide when to launch
20443 parallel introduction circuits for hidden services. (Previously,
20444 we would retry after 15 seconds.)
20445 - Update to the April 1 2011 Maxmind GeoLite Country database.
20448 - Create the /var/run/tor directory on startup on OpenSUSE if it is
20449 not already created. Patch from Andreas Stieger. Fixes bug 2573.
20451 o Documentation changes:
20452 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
20453 - Resolve all doxygen warnings except those for missing documentation.
20455 - Add doxygen documentation for more functions, fields, and types.
20458 Changes in version 0.2.2.23-alpha - 2011-03-08
20459 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
20460 they restart they don't lose their bandwidth capacity estimate. This
20461 release also fixes a diverse set of user-facing bugs, ranging from
20462 relays overrunning their rate limiting to clients falsely warning about
20463 clock skew to bridge descriptor leaks by our bridge directory authority.
20466 - Stop sending a CLOCK_SKEW controller status event whenever
20467 we fetch directory information from a relay that has a wrong clock.
20468 Instead, only inform the controller when it's a trusted authority
20469 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
20470 the rest of bug 1074.
20471 - Fix an assert in parsing router descriptors containing IPv6
20472 addresses. This one took down the directory authorities when
20473 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
20474 - Make the bridge directory authority refuse to answer directory
20475 requests for "all" descriptors. It used to include bridge
20476 descriptors in its answer, which was a major information leak.
20477 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
20478 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
20479 Tor would ignore their RelayBandwidthBurst setting,
20480 potentially using more bandwidth than expected. Bugfix on
20481 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
20482 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
20483 hidserv" in her torrc. The 'hidserv' argument never controlled
20484 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
20487 - Relays now save observed peak bandwidth throughput rates to their
20488 state file (along with total usage, which was already saved)
20489 so that they can determine their correct estimated bandwidth on
20490 restart. Resolves bug 1863, where Tor relays would reset their
20491 estimated bandwidth to 0 after restarting.
20492 - Directory authorities now take changes in router IP address and
20493 ORPort into account when determining router stability. Previously,
20494 if a router changed its IP or ORPort, the authorities would not
20495 treat it as having any downtime for the purposes of stability
20496 calculation, whereas clients would experience downtime since the
20497 change could take a while to propagate to them. Resolves issue 1035.
20498 - Enable Address Space Layout Randomization (ASLR) and Data Execution
20499 Prevention (DEP) by default on Windows to make it harder for
20500 attackers to exploit vulnerabilities. Patch from John Brooks.
20502 o Minor bugfixes (on 0.2.1.x and earlier):
20503 - Fix a rare crash bug that could occur when a client was configured
20504 with a large number of bridges. Fixes bug 2629; bugfix on
20505 0.2.1.2-alpha. Bugfix by trac user "shitlei".
20506 - Avoid a double mark-for-free warning when failing to attach a
20507 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
20509 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
20510 found by "cypherpunks". This bug was introduced before the first
20511 Tor release, in svn commit r110.
20512 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
20513 don't mention them in the manpage. Fixes bug 2450; issue
20514 spotted by keb and G-Lo.
20515 - Fix a bug in bandwidth history state parsing that could have been
20516 triggered if a future version of Tor ever changed the timing
20517 granularity at which bandwidth history is measured. Bugfix on
20518 Tor 0.1.1.11-alpha.
20519 - When a relay decides that its DNS is too broken for it to serve
20520 as an exit server, it advertised itself as a non-exit, but
20521 continued to act as an exit. This could create accidental
20522 partitioning opportunities for users. Instead, if a relay is
20523 going to advertise reject *:* as its exit policy, it should
20524 really act with exit policy "reject *:*". Fixes bug 2366.
20525 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
20526 - In the special case where you configure a public exit relay as your
20527 bridge, Tor would be willing to use that exit relay as the last
20528 hop in your circuit as well. Now we fail that circuit instead.
20529 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
20530 - Fix a bug with our locking implementation on Windows that couldn't
20531 correctly detect when a file was already locked. Fixes bug 2504,
20532 bugfix on 0.2.1.6-alpha.
20533 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
20534 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
20536 - Set target port in get_interface_address6() correctly. Bugfix
20537 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
20538 - Directory authorities are now more robust to hops back in time
20539 when calculating router stability. Previously, if a run of uptime
20540 or downtime appeared to be negative, the calculation could give
20541 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
20543 - Fix an assert that got triggered when using the TestingTorNetwork
20544 configuration option and then issuing a GETINFO config-text control
20545 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
20547 o Minor bugfixes (on 0.2.2.x):
20548 - Clients should not weight BadExit nodes as Exits in their node
20549 selection. Similarly, directory authorities should not count BadExit
20550 bandwidth as Exit bandwidth when computing bandwidth-weights.
20551 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
20552 - Correctly clear our dir_read/dir_write history when there is an
20553 error parsing any bw history value from the state file. Bugfix on
20554 Tor 0.2.2.15-alpha.
20555 - Resolve a bug in verifying signatures of directory objects
20556 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
20557 Fixes bug 2409. Found by "piebeer".
20558 - Bridge authorities no longer crash on SIGHUP when they try to
20559 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
20563 - Log less aggressively about circuit timeout changes, and improve
20564 some other circuit timeout messages. Resolves bug 2004.
20565 - Log a little more clearly about the times at which we're no longer
20566 accepting new connections. Resolves bug 2181.
20567 - Reject attempts at the client side to open connections to private
20568 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
20569 a randomly chosen exit node. Attempts to do so are always
20570 ill-defined, generally prevented by exit policies, and usually
20571 in error. This will also help to detect loops in transparent
20572 proxy configurations. You can disable this feature by setting
20573 "ClientRejectInternalAddresses 0" in your torrc.
20574 - Always treat failure to allocate an RSA key as an unrecoverable
20576 - Update to the March 1 2011 Maxmind GeoLite Country database.
20578 o Minor features (log subsystem):
20579 - Add documentation for configuring logging at different severities in
20580 different log domains. We've had this feature since 0.2.1.1-alpha,
20581 but for some reason it never made it into the manpage. Fixes
20583 - Make it simpler to specify "All log domains except for A and B".
20584 Previously you needed to say "[*,~A,~B]". Now you can just say
20586 - Add a "LogMessageDomains 1" option to include the domains of log
20587 messages along with the messages. Without this, there's no way
20588 to use log domains without reading the source or doing a lot
20591 o Packaging changes:
20592 - Stop shipping the Tor specs files and development proposal documents
20593 in the tarball. They are now in a separate git repository at
20594 git://git.torproject.org/torspec.git
20597 Changes in version 0.2.1.30 - 2011-02-23
20598 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
20599 change is a slight tweak to Tor's TLS handshake that makes relays
20600 and bridges that run this new version reachable from Iran again.
20601 We don't expect this tweak will win the arms race long-term, but it
20602 buys us time until we roll out a better solution.
20605 - Stop sending a CLOCK_SKEW controller status event whenever
20606 we fetch directory information from a relay that has a wrong clock.
20607 Instead, only inform the controller when it's a trusted authority
20608 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
20609 the rest of bug 1074.
20610 - Fix a bounds-checking error that could allow an attacker to
20611 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
20612 Found by "piebeer".
20613 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
20614 Tor would ignore their RelayBandwidthBurst setting,
20615 potentially using more bandwidth than expected. Bugfix on
20616 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
20617 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
20618 hidserv" in her torrc. The 'hidserv' argument never controlled
20619 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
20622 - Adjust our TLS Diffie-Hellman parameters to match those used by
20624 - Update to the February 1 2011 Maxmind GeoLite Country database.
20627 - Check for and reject overly long directory certificates and
20628 directory tokens before they have a chance to hit any assertions.
20629 Bugfix on 0.2.1.28. Found by "doorss".
20630 - Bring the logic that gathers routerinfos and assesses the
20631 acceptability of circuits into line. This prevents a Tor OP from
20632 getting locked in a cycle of choosing its local OR as an exit for a
20633 path (due to a .exit request) and then rejecting the circuit because
20634 its OR is not listed yet. It also prevents Tor clients from using an
20635 OR running in the same instance as an exit (due to a .exit request)
20636 if the OR does not meet the same requirements expected of an OR
20637 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
20639 o Packaging changes:
20640 - Stop shipping the Tor specs files and development proposal documents
20641 in the tarball. They are now in a separate git repository at
20642 git://git.torproject.org/torspec.git
20643 - Do not include Git version tags as though they are SVN tags when
20644 generating a tarball from inside a repository that has switched
20645 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20648 Changes in version 0.2.2.22-alpha - 2011-01-25
20649 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
20650 main other change is a slight tweak to Tor's TLS handshake that makes
20651 relays and bridges that run this new version reachable from Iran again.
20652 We don't expect this tweak will win the arms race long-term, but it
20653 will buy us a bit more time until we roll out a better solution.
20656 - Fix a bounds-checking error that could allow an attacker to
20657 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
20658 Found by "piebeer".
20659 - Don't assert when changing from bridge to relay or vice versa
20660 via the controller. The assert happened because we didn't properly
20661 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
20662 bug 2433. Reported by bastik.
20665 - Adjust our TLS Diffie-Hellman parameters to match those used by
20667 - Provide a log message stating which geoip file we're parsing
20668 instead of just stating that we're parsing the geoip file.
20669 Implements ticket 2432.
20672 - Check for and reject overly long directory certificates and
20673 directory tokens before they have a chance to hit any assertions.
20674 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
20677 Changes in version 0.2.2.21-alpha - 2011-01-15
20678 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
20679 continues our recent code security audit work. The main fix resolves
20680 a remote heap overflow vulnerability that can allow remote code
20681 execution (CVE-2011-0427). Other fixes address a variety of assert
20682 and crash bugs, most of which we think are hard to exploit remotely.
20684 o Major bugfixes (security), also included in 0.2.1.29:
20685 - Fix a heap overflow bug where an adversary could cause heap
20686 corruption. This bug probably allows remote code execution
20687 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
20689 - Prevent a denial-of-service attack by disallowing any
20690 zlib-compressed data whose compression factor is implausibly
20691 high. Fixes part of bug 2324; reported by "doorss".
20692 - Zero out a few more keys in memory before freeing them. Fixes
20693 bug 2384 and part of bug 2385. These key instances found by
20694 "cypherpunks", based on Andrew Case's report about being able
20695 to find sensitive data in Tor's memory space if you have enough
20696 permissions. Bugfix on 0.0.2pre9.
20698 o Major bugfixes (crashes), also included in 0.2.1.29:
20699 - Prevent calls to Libevent from inside Libevent log handlers.
20700 This had potential to cause a nasty set of crashes, especially
20701 if running Libevent with debug logging enabled, and running
20702 Tor with a controller watching for low-severity log messages.
20703 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
20704 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
20705 underflow errors there too. Fixes the other part of bug 2324.
20706 - Fix a bug where we would assert if we ever had a
20707 cached-descriptors.new file (or another file read directly into
20708 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
20709 on 0.2.1.25. Found by doorss.
20710 - Fix some potential asserts and parsing issues with grossly
20711 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
20714 o Minor bugfixes (other), also included in 0.2.1.29:
20715 - Fix a bug with handling misformed replies to reverse DNS lookup
20716 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
20717 bug reported by doorss.
20718 - Fix compilation on mingw when a pthreads compatibility library
20719 has been installed. (We don't want to use it, so we shouldn't
20720 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
20721 - Fix a bug where we would declare that we had run out of virtual
20722 addresses when the address space was only half-exhausted. Bugfix
20724 - Correctly handle the case where AutomapHostsOnResolve is set but
20725 no virtual addresses are available. Fixes bug 2328; bugfix on
20726 0.1.2.1-alpha. Bug found by doorss.
20727 - Correctly handle wrapping around when we run out of virtual
20728 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
20730 o Minor features, also included in 0.2.1.29:
20731 - Update to the January 1 2011 Maxmind GeoLite Country database.
20732 - Introduce output size checks on all of our decryption functions.
20734 o Build changes, also included in 0.2.1.29:
20735 - Tor does not build packages correctly with Automake 1.6 and earlier;
20736 added a check to Makefile.am to make sure that we're building with
20737 Automake 1.7 or later.
20738 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
20739 because we built it with a too-old version of automake. Thus that
20740 release broke ./configure --enable-openbsd-malloc, which is popular
20741 among really fast exit relays on Linux.
20743 o Major bugfixes, new in 0.2.2.21-alpha:
20744 - Prevent crash/heap corruption when the cbtnummodes consensus
20745 parameter is set to 0 or large values. Fixes bug 2317; bugfix
20748 o Major features, new in 0.2.2.21-alpha:
20749 - Introduce minimum/maximum values that clients will believe
20750 from the consensus. Now we'll have a better chance to avoid crashes
20751 or worse when a consensus param has a weird value.
20753 o Minor features, new in 0.2.2.21-alpha:
20754 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
20755 used on bridges, and it makes bridge scanning somewhat easier.
20756 - If writing the state file to disk fails, wait up to an hour before
20757 retrying again, rather than trying again each second. Fixes bug
20758 2346; bugfix on Tor 0.1.1.3-alpha.
20759 - Make Libevent log messages get delivered to controllers later,
20760 and not from inside the Libevent log handler. This prevents unsafe
20761 reentrant Libevent calls while still letting the log messages
20763 - Detect platforms that brokenly use a signed size_t, and refuse to
20764 build there. Found and analyzed by doorss and rransom.
20765 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
20768 o Minor bugfixes, new in 0.2.2.21-alpha:
20769 - Handle SOCKS messages longer than 128 bytes long correctly, rather
20770 than waiting forever for them to finish. Fixes bug 2330; bugfix
20771 on 0.2.0.16-alpha. Found by doorss.
20772 - Add assertions to check for overflow in arguments to
20773 base32_encode() and base32_decode(); fix a signed-unsigned
20774 comparison there too. These bugs are not actually reachable in Tor,
20775 but it's good to prevent future errors too. Found by doorss.
20776 - Correctly detect failures to create DNS requests when using Libevent
20777 versions before v2. (Before Libevent 2, we used our own evdns
20778 implementation. Its return values for Libevent's evdns_resolve_*()
20779 functions are not consistent with those from Libevent.) Fixes bug
20780 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
20782 o Documentation, new in 0.2.2.21-alpha:
20783 - Document the default socks host and port (127.0.0.1:9050) for
20787 Changes in version 0.2.1.29 - 2011-01-15
20788 Tor 0.2.1.29 continues our recent code security audit work. The main
20789 fix resolves a remote heap overflow vulnerability that can allow remote
20790 code execution. Other fixes address a variety of assert and crash bugs,
20791 most of which we think are hard to exploit remotely.
20793 o Major bugfixes (security):
20794 - Fix a heap overflow bug where an adversary could cause heap
20795 corruption. This bug probably allows remote code execution
20796 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
20798 - Prevent a denial-of-service attack by disallowing any
20799 zlib-compressed data whose compression factor is implausibly
20800 high. Fixes part of bug 2324; reported by "doorss".
20801 - Zero out a few more keys in memory before freeing them. Fixes
20802 bug 2384 and part of bug 2385. These key instances found by
20803 "cypherpunks", based on Andrew Case's report about being able
20804 to find sensitive data in Tor's memory space if you have enough
20805 permissions. Bugfix on 0.0.2pre9.
20807 o Major bugfixes (crashes):
20808 - Prevent calls to Libevent from inside Libevent log handlers.
20809 This had potential to cause a nasty set of crashes, especially
20810 if running Libevent with debug logging enabled, and running
20811 Tor with a controller watching for low-severity log messages.
20812 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
20813 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
20814 underflow errors there too. Fixes the other part of bug 2324.
20815 - Fix a bug where we would assert if we ever had a
20816 cached-descriptors.new file (or another file read directly into
20817 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
20818 on 0.2.1.25. Found by doorss.
20819 - Fix some potential asserts and parsing issues with grossly
20820 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
20823 o Minor bugfixes (other):
20824 - Fix a bug with handling misformed replies to reverse DNS lookup
20825 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
20826 bug reported by doorss.
20827 - Fix compilation on mingw when a pthreads compatibility library
20828 has been installed. (We don't want to use it, so we shouldn't
20829 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
20830 - Fix a bug where we would declare that we had run out of virtual
20831 addresses when the address space was only half-exhausted. Bugfix
20833 - Correctly handle the case where AutomapHostsOnResolve is set but
20834 no virtual addresses are available. Fixes bug 2328; bugfix on
20835 0.1.2.1-alpha. Bug found by doorss.
20836 - Correctly handle wrapping around to when we run out of virtual
20837 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
20838 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
20839 because we built it with a too-old version of automake. Thus that
20840 release broke ./configure --enable-openbsd-malloc, which is popular
20841 among really fast exit relays on Linux.
20844 - Update to the January 1 2011 Maxmind GeoLite Country database.
20845 - Introduce output size checks on all of our decryption functions.
20848 - Tor does not build packages correctly with Automake 1.6 and earlier;
20849 added a check to Makefile.am to make sure that we're building with
20850 Automake 1.7 or later.
20853 Changes in version 0.2.2.20-alpha - 2010-12-17
20854 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
20855 exploitable bugs. We also fix a variety of other significant bugs,
20856 change the IP address for one of our directory authorities, and update
20857 the minimum version that Tor relays must run to join the network.
20860 - Fix a remotely exploitable bug that could be used to crash instances
20861 of Tor remotely by overflowing on the heap. Remote-code execution
20862 hasn't been confirmed, but can't be ruled out. Everyone should
20863 upgrade. Bugfix on the 0.1.1 series and later.
20864 - Fix a bug that could break accounting on 64-bit systems with large
20865 time_t values, making them hibernate for impossibly long intervals.
20866 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
20867 - Fix a logic error in directory_fetches_from_authorities() that
20868 would cause all _non_-exits refusing single-hop-like circuits
20869 to fetch from authorities, when we wanted to have _exits_ fetch
20870 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
20872 - Fix a stream fairness bug that would cause newer streams on a given
20873 circuit to get preference when reading bytes from the origin or
20874 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
20875 introduced before the first Tor release, in svn revision r152.
20877 o Directory authority changes:
20878 - Change IP address and ports for gabelmoo (v3 directory authority).
20881 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
20882 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
20883 - Fix an off-by-one error in calculating some controller command
20884 argument lengths. Fortunately, this mistake is harmless since
20885 the controller code does redundant NUL termination too. Found by
20886 boboper. Bugfix on 0.1.1.1-alpha.
20887 - Do not dereference NULL if a bridge fails to build its
20888 extra-info descriptor. Found by an anonymous commenter on
20889 Trac. Bugfix on 0.2.2.19-alpha.
20892 - Update to the December 1 2010 Maxmind GeoLite Country database.
20893 - Directory authorities now reject relays running any versions of
20894 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
20895 known bugs that keep RELAY_EARLY cells from working on rendezvous
20896 circuits. Followup to fix for bug 2081.
20897 - Directory authorities now reject relays running any version of Tor
20898 older than 0.2.0.26-rc. That version is the earliest that fetches
20899 current directory information correctly. Fixes bug 2156.
20900 - Report only the top 10 ports in exit-port stats in order not to
20901 exceed the maximum extra-info descriptor length of 50 KB. Implements
20905 Changes in version 0.2.1.28 - 2010-12-17
20906 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
20907 exploitable bugs. We also took this opportunity to change the IP address
20908 for one of our directory authorities, and to update the geoip database
20912 - Fix a remotely exploitable bug that could be used to crash instances
20913 of Tor remotely by overflowing on the heap. Remote-code execution
20914 hasn't been confirmed, but can't be ruled out. Everyone should
20915 upgrade. Bugfix on the 0.1.1 series and later.
20917 o Directory authority changes:
20918 - Change IP address and ports for gabelmoo (v3 directory authority).
20921 - Update to the December 1 2010 Maxmind GeoLite Country database.
20924 Changes in version 0.2.1.27 - 2010-11-23
20925 Yet another OpenSSL security patch broke its compatibility with Tor:
20926 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
20927 also took this opportunity to fix several crash bugs, integrate a new
20928 directory authority, and update the bundled GeoIP database.
20931 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
20932 No longer set the tlsext_host_name extension on server SSL objects;
20933 but continue to set it on client SSL objects. Our goal in setting
20934 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
20935 bugfix on 0.2.1.1-alpha.
20936 - Do not log messages to the controller while shrinking buffer
20937 freelists. Doing so would sometimes make the controller connection
20938 try to allocate a buffer chunk, which would mess up the internals
20939 of the freelist and cause an assertion failure. Fixes bug 1125;
20940 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
20941 - Learn our external IP address when we're a relay or bridge, even if
20942 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
20943 where we introduced bridge relays that don't need to publish to
20944 be useful. Fixes bug 2050.
20945 - Do even more to reject (and not just ignore) annotations on
20946 router descriptors received anywhere but from the cache. Previously
20947 we would ignore such annotations at first, but cache them to disk
20948 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
20949 - When you're using bridges and your network goes away and your
20950 bridges get marked as down, recover when you attempt a new socks
20951 connection (if the network is back), rather than waiting up to an
20952 hour to try fetching new descriptors for your bridges. Bugfix on
20953 0.2.0.3-alpha; fixes bug 1981.
20956 - Move to the November 2010 Maxmind GeoLite country db (rather
20957 than the June 2009 ip-to-country GeoIP db) for our statistics that
20958 count how many users relays are seeing from each country. Now we'll
20959 have more accurate data, especially for many African countries.
20961 o New directory authorities:
20962 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
20966 - Fix an assertion failure that could occur in directory caches or
20967 bridge users when using a very short voting interval on a testing
20968 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
20970 - Enforce multiplicity rules when parsing annotations. Bugfix on
20971 0.2.0.8-alpha. Found by piebeer.
20972 - Allow handshaking OR connections to take a full KeepalivePeriod
20973 seconds to handshake. Previously, we would close them after
20974 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
20975 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
20977 - When building with --enable-gcc-warnings on OpenBSD, disable
20978 warnings in system headers. This makes --enable-gcc-warnings
20979 pass on OpenBSD 4.8.
20982 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
20983 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
20984 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
20985 Servers can start sending this code when enough clients recognize
20986 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
20987 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
20988 Patch from mingw-san.
20991 - Remove the old debian/ directory from the main Tor distribution.
20992 The official Tor-for-debian git repository lives at the URL
20993 https://git.torproject.org/debian/tor.git
20994 - Stop shipping the old doc/website/ directory in the tarball. We
20995 changed the website format in late 2010, and what we shipped in
20996 0.2.1.26 really wasn't that useful anyway.
20999 Changes in version 0.2.2.19-alpha - 2010-11-22
21000 Yet another OpenSSL security patch broke its compatibility with Tor:
21001 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
21004 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
21005 No longer set the tlsext_host_name extension on server SSL objects;
21006 but continue to set it on client SSL objects. Our goal in setting
21007 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
21008 bugfix on 0.2.1.1-alpha.
21011 - Try harder not to exceed the maximum length of 50 KB when writing
21012 statistics to extra-info descriptors. This bug was triggered by very
21013 fast relays reporting exit-port, entry, and dirreq statistics.
21014 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
21015 - Publish a router descriptor even if generating an extra-info
21016 descriptor fails. Previously we would not publish a router
21017 descriptor without an extra-info descriptor; this can cause fast
21018 exit relays collecting exit-port statistics to drop from the
21019 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
21022 Changes in version 0.2.2.18-alpha - 2010-11-16
21023 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
21024 us lately, makes unpublished bridge relays able to detect their IP
21025 address, and fixes a wide variety of other bugs to get us much closer
21026 to a stable release.
21029 - Do even more to reject (and not just ignore) annotations on
21030 router descriptors received anywhere but from the cache. Previously
21031 we would ignore such annotations at first, but cache them to disk
21032 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
21033 - Do not log messages to the controller while shrinking buffer
21034 freelists. Doing so would sometimes make the controller connection
21035 try to allocate a buffer chunk, which would mess up the internals
21036 of the freelist and cause an assertion failure. Fixes bug 1125;
21037 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
21038 - Learn our external IP address when we're a relay or bridge, even if
21039 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
21040 where we introduced bridge relays that don't need to publish to
21041 be useful. Fixes bug 2050.
21042 - Maintain separate TLS contexts and certificates for incoming and
21043 outgoing connections in bridge relays. Previously we would use the
21044 same TLS contexts and certs for incoming and outgoing connections.
21045 Bugfix on 0.2.0.3-alpha; addresses bug 988.
21046 - Maintain separate identity keys for incoming and outgoing TLS
21047 contexts in bridge relays. Previously we would use the same
21048 identity keys for incoming and outgoing TLS contexts. Bugfix on
21049 0.2.0.3-alpha; addresses the other half of bug 988.
21050 - Avoid an assertion failure when we as an authority receive a
21051 duplicate upload of a router descriptor that we already have,
21052 but which we previously considered an obsolete descriptor.
21053 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
21054 - Avoid a crash bug triggered by looking at a dangling pointer while
21055 setting the network status consensus. Found by Robert Ransom.
21056 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
21057 - Fix a logic error where servers that _didn't_ act as exits would
21058 try to keep their server lists more aggressively up to date than
21059 exits, when it was supposed to be the other way around. Bugfix
21062 o Minor bugfixes (on Tor 0.2.1.x and earlier):
21063 - When we're trying to guess whether we know our IP address as
21064 a relay, we would log various ways that we failed to guess
21065 our address, but never log that we ended up guessing it
21066 successfully. Now add a log line to help confused and anxious
21067 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
21068 - Bring the logic that gathers routerinfos and assesses the
21069 acceptability of circuits into line. This prevents a Tor OP from
21070 getting locked in a cycle of choosing its local OR as an exit for a
21071 path (due to a .exit request) and then rejecting the circuit because
21072 its OR is not listed yet. It also prevents Tor clients from using an
21073 OR running in the same instance as an exit (due to a .exit request)
21074 if the OR does not meet the same requirements expected of an OR
21075 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
21076 - Correctly describe errors that occur when generating a TLS object.
21077 Previously we would attribute them to a failure while generating a
21078 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
21080 - Enforce multiplicity rules when parsing annotations. Bugfix on
21081 0.2.0.8-alpha. Found by piebeer.
21082 - Fix warnings that newer versions of autoconf produced during
21083 ./autogen.sh. These warnings appear to be harmless in our case,
21084 but they were extremely verbose. Fixes bug 2020.
21086 o Minor bugfixes (on Tor 0.2.2.x):
21087 - Enable protection of small arrays whenever we build with gcc
21088 hardening features, not only when also building with warnings
21089 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
21092 - Make hidden services work better in private Tor networks by not
21093 requiring any uptime to join the hidden service descriptor
21094 DHT. Implements ticket 2088.
21095 - Rate-limit the "your application is giving Tor only an IP address"
21096 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
21097 - When AllowSingleHopExits is set, print a warning to explain to the
21098 relay operator why most clients are avoiding her relay.
21099 - Update to the November 1 2010 Maxmind GeoLite Country database.
21101 o Code simplifications and refactoring:
21102 - When we fixed bug 1038 we had to put in a restriction not to send
21103 RELAY_EARLY cells on rend circuits. This was necessary as long
21104 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
21105 active. Now remove this obsolete check. Resolves bug 2081.
21106 - Some options used different conventions for uppercasing of acronyms
21107 when comparing manpage and source. Fix those in favor of the
21108 manpage, as it makes sense to capitalize acronyms.
21109 - Remove the torrc.complete file. It hasn't been kept up to date
21110 and users will have better luck checking out the manpage.
21111 - Remove the obsolete "NoPublish" option; it has been flagged
21112 as obsolete and has produced a warning since 0.1.1.18-rc.
21113 - Remove everything related to building the expert bundle for OS X.
21114 It has confused many users, doesn't work right on OS X 10.6,
21115 and is hard to get rid of once installed. Resolves bug 1274.
21118 Changes in version 0.2.2.17-alpha - 2010-09-30
21119 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
21120 to use one-hop circuits (which can put the exit relays at higher risk,
21121 plus unbalance the network); fixes a big bug in bandwidth accounting
21122 for relays that want to limit their monthly bandwidth use; fixes a
21123 big pile of bugs in how clients tolerate temporary network failure;
21124 and makes our adaptive circuit build timeout feature (which improves
21125 client performance if your network is fast while not breaking things
21126 if your network is slow) better handle bad networks.
21129 - Exit relays now try harder to block exit attempts from unknown
21130 relays, to make it harder for people to use them as one-hop proxies
21131 a la tortunnel. Controlled by the refuseunknownexits consensus
21132 parameter (currently enabled), or you can override it on your
21133 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
21135 o Major bugfixes (0.2.1.x and earlier):
21136 - Fix a bug in bandwidth accounting that could make us use twice
21137 the intended bandwidth when our interval start changes due to
21138 daylight saving time. Now we tolerate skew in stored vs computed
21139 interval starts: if the start of the period changes by no more than
21140 50% of the period's duration, we remember bytes that we transferred
21141 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
21142 - Always search the Windows system directory for system DLLs, and
21143 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
21144 - When you're using bridges and your network goes away and your
21145 bridges get marked as down, recover when you attempt a new socks
21146 connection (if the network is back), rather than waiting up to an
21147 hour to try fetching new descriptors for your bridges. Bugfix on
21148 0.2.0.3-alpha; fixes bug 1981.
21150 o Major bugfixes (on 0.2.2.x):
21151 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
21153 - Fix a segfault that could happen when operating a bridge relay with
21154 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
21155 - The consensus bandwidth-weights (used by clients to choose fast
21156 relays) entered an unexpected edge case in September where
21157 Exits were much scarcer than Guards, resulting in bad weight
21158 recommendations. Now we compute them using new constraints that
21159 should succeed in all cases. Also alter directory authorities to
21160 not include the bandwidth-weights line if they fail to produce
21161 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
21162 - When weighting bridges during path selection, we used to trust
21163 the bandwidths they provided in their descriptor, only capping them
21164 at 10MB/s. This turned out to be problematic for two reasons:
21165 Bridges could claim to handle a lot more traffic then they
21166 actually would, thus making more clients pick them and have a
21167 pretty effective DoS attack. The other issue is that new bridges
21168 that might not have a good estimate for their bw capacity yet
21169 would not get used at all unless no other bridges are available
21170 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
21172 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
21173 - Ignore cannibalized circuits when recording circuit build times.
21174 This should provide for a minor performance improvement for hidden
21175 service users using 0.2.2.14-alpha, and should remove two spurious
21176 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
21177 - Simplify the logic that causes us to decide if the network is
21178 unavailable for purposes of recording circuit build times. If we
21179 receive no cells whatsoever for the entire duration of a circuit's
21180 full measured lifetime, the network is probably down. Also ignore
21181 one-hop directory fetching circuit timeouts when calculating our
21182 circuit build times. These changes should hopefully reduce the
21183 cases where we see ridiculous circuit build timeouts for people
21184 with spotty wireless connections. Fixes part of bug 1772; bugfix
21186 - Prevent the circuit build timeout from becoming larger than
21187 the maximum build time we have ever seen. Also, prevent the time
21188 period for measurement circuits from becoming larger than twice that
21189 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
21192 - When we run out of directory information such that we can't build
21193 circuits, but then get enough that we can build circuits, log when
21194 we actually construct a circuit, so the user has a better chance of
21195 knowing what's going on. Fixes bug 1362.
21196 - Be more generous with how much bandwidth we'd use up (with
21197 accounting enabled) before entering "soft hibernation". Previously,
21198 we'd refuse new connections and circuits once we'd used up 95% of
21199 our allotment. Now, we use up 95% of our allotment, AND make sure
21200 that we have no more than 500MB (or 3 hours of expected traffic,
21201 whichever is lower) remaining before we enter soft hibernation.
21202 - If we've configured EntryNodes and our network goes away and/or all
21203 our entrynodes get marked down, optimistically retry them all when
21204 a new socks application request appears. Fixes bug 1882.
21205 - Add some more defensive programming for architectures that can't
21206 handle unaligned integer accesses. We don't know of any actual bugs
21207 right now, but that's the best time to fix them. Fixes bug 1943.
21208 - Support line continuations in the torrc config file. If a line
21209 ends with a single backslash character, the newline is ignored, and
21210 the configuration value is treated as continuing on the next line.
21213 o Minor bugfixes (on 0.2.1.x and earlier):
21214 - For bandwidth accounting, calculate our expected bandwidth rate
21215 based on the time during which we were active and not in
21216 soft-hibernation during the last interval. Previously, we were
21217 also considering the time spent in soft-hibernation. If this
21218 was a long time, we would wind up underestimating our bandwidth
21219 by a lot, and skewing our wakeup time towards the start of the
21220 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
21222 o Minor bugfixes (on 0.2.2.x):
21223 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
21224 which were disabled by the circuit build timeout changes in
21225 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
21226 - Make sure we don't warn about missing bandwidth weights when
21227 choosing bridges or other relays not in the consensus. Bugfix on
21228 0.2.2.10-alpha; fixes bug 1805.
21229 - In our logs, do not double-report signatures from unrecognized
21230 authorities both as "from unknown authority" and "not
21231 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
21234 Changes in version 0.2.2.16-alpha - 2010-09-17
21235 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
21236 evident at exit relays), and also continues to resolve all the little
21237 bugs that have been filling up trac lately.
21239 o Major bugfixes (stream-level fairness):
21240 - When receiving a circuit-level SENDME for a blocked circuit, try
21241 to package cells fairly from all the streams that had previously
21242 been blocked on that circuit. Previously, we had started with the
21243 oldest stream, and allowed each stream to potentially exhaust
21244 the circuit's package window. This gave older streams on any
21245 given circuit priority over newer ones. Fixes bug 1937. Detected
21246 originally by Camilo Viecco. This bug was introduced before the
21247 first Tor release, in svn commit r152: it is the new winner of
21248 the longest-lived bug prize.
21249 - When the exit relay got a circuit-level sendme cell, it started
21250 reading on the exit streams, even if had 500 cells queued in the
21251 circuit queue already, so the circuit queue just grew and grew in
21252 some cases. We fix this by not re-enabling reading on receipt of a
21253 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
21254 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
21256 - Newly created streams were allowed to read cells onto circuits,
21257 even if the circuit's cell queue was blocked and waiting to drain.
21258 This created potential unfairness, as older streams would be
21259 blocked, but newer streams would gladly fill the queue completely.
21260 We add code to detect this situation and prevent any stream from
21261 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
21265 - Update to the September 1 2010 Maxmind GeoLite Country database.
21266 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
21267 not. This would lead to a cookie that is still not group readable.
21268 Closes bug 1843. Suggested by katmagic.
21269 - When logging a rate-limited warning, we now mention how many messages
21270 got suppressed since the last warning.
21271 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
21272 do individual connection-level rate limiting of clients. The torrc
21273 config options with the same names trump the consensus params, if
21274 both are present. Replaces the old "bwconnrate" and "bwconnburst"
21275 consensus params which were broken from 0.2.2.7-alpha through
21276 0.2.2.14-alpha. Closes bug 1947.
21277 - When a router changes IP address or port, authorities now launch
21278 a new reachability test for it. Implements ticket 1899.
21279 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
21280 2 no signature, 4 required" messages about consensus signatures
21281 easier to read, and make sure they get logged at the same severity
21282 as the messages explaining which keys are which. Fixes bug 1290.
21283 - Don't warn when we have a consensus that we can't verify because
21284 of missing certificates, unless those certificates are ones
21285 that we have been trying and failing to download. Fixes bug 1145.
21286 - If you configure your bridge with a known identity fingerprint,
21287 and the bridge authority is unreachable (as it is in at least
21288 one country now), fall back to directly requesting the descriptor
21289 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
21291 - When building with --enable-gcc-warnings on OpenBSD, disable
21292 warnings in system headers. This makes --enable-gcc-warnings
21293 pass on OpenBSD 4.8.
21295 o Minor bugfixes (on 0.2.1.x and earlier):
21296 - Authorities will now attempt to download consensuses if their
21297 own efforts to make a live consensus have failed. This change
21298 means authorities that restart will fetch a valid consensus, and
21299 it means authorities that didn't agree with the current consensus
21300 will still fetch and serve it if it has enough signatures. Bugfix
21301 on 0.2.0.9-alpha; fixes bug 1300.
21302 - Ensure DNS requests launched by "RESOLVE" commands from the
21303 controller respect the __LeaveStreamsUnattached setconf options. The
21304 same goes for requests launched via DNSPort or transparent
21305 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
21306 - Allow handshaking OR connections to take a full KeepalivePeriod
21307 seconds to handshake. Previously, we would close them after
21308 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
21309 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
21311 - Rate-limit "Failed to hand off onionskin" warnings.
21312 - Never relay a cell for a circuit we have already destroyed.
21313 Between marking a circuit as closeable and finally closing it,
21314 it may have been possible for a few queued cells to get relayed,
21315 even though they would have been immediately dropped by the next
21316 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
21317 - Never queue a cell for a circuit that's already been marked
21319 - Never vote for a server as "Running" if we have a descriptor for
21320 it claiming to be hibernating, and that descriptor was published
21321 more recently than our last contact with the server. Bugfix on
21322 0.2.0.3-alpha; fixes bug 911.
21323 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
21326 o Minor bugfixes (on 0.2.2.x):
21327 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
21328 down if a directory fetch fails and you've configured either
21329 bridges or EntryNodes. The intent was to mark the relay as down
21330 _unless_ you're using bridges or EntryNodes, since if you are
21331 then you could quickly run out of entry points.
21332 - Fix the Windows directory-listing code. A bug introduced in
21333 0.2.2.14-alpha could make Windows directory servers forget to load
21334 some of their cached v2 networkstatus files.
21335 - Really allow clients to use relays as bridges. Fixes bug 1776;
21336 bugfix on 0.2.2.15-alpha.
21337 - Demote a warn to info that happens when the CellStatistics option
21338 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
21339 Reported by Moritz Bartl.
21340 - On Windows, build correctly either with or without Unicode support.
21341 This is necessary so that Tor can support fringe platforms like
21342 Windows 98 (which has no Unicode), or Windows CE (which has no
21343 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
21346 - Add a unit test for cross-platform directory-listing code.
21349 Changes in version 0.2.2.15-alpha - 2010-08-18
21350 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
21351 fixes a variety of other bugs that were preventing performance
21352 experiments from moving forward, fixes several bothersome memory leaks,
21353 and generally closes a lot of smaller bugs that have been filling up
21357 - Stop assigning the HSDir flag to relays that disable their
21358 DirPort (and thus will refuse to answer directory requests). This
21359 fix should dramatically improve the reachability of hidden services:
21360 hidden services and hidden service clients pick six HSDir relays
21361 to store and retrieve the hidden service descriptor, and currently
21362 about half of the HSDir relays will refuse to work. Bugfix on
21363 0.2.0.10-alpha; fixes part of bug 1693.
21364 - The PerConnBWRate and Burst config options, along with the
21365 bwconnrate and bwconnburst consensus params, initialized each conn's
21366 token bucket values only when the connection is established. Now we
21367 update them if the config options change, and update them every time
21368 we get a new consensus. Otherwise we can encounter an ugly edge
21369 case where we initialize an OR conn to client-level bandwidth,
21370 but then later the relay joins the consensus and we leave it
21371 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
21372 - Fix a regression that caused Tor to rebind its ports if it receives
21373 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
21376 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
21377 should give us approximately 40-50% more Guard-flagged nodes,
21378 improving the anonymity the Tor network can provide and also
21379 decreasing the dropoff in throughput that relays experience when
21380 they first get the Guard flag.
21381 - Allow enabling or disabling the *Statistics config options while
21385 - Update to the August 1 2010 Maxmind GeoLite Country database.
21386 - Have the controller interface give a more useful message than
21387 "Internal Error" in response to failed GETINFO requests.
21388 - Warn when the same option is provided more than once in a torrc
21389 file, on the command line, or in a single SETCONF statement, and
21390 the option is one that only accepts a single line. Closes bug 1384.
21391 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
21392 Patch from mingw-san.
21393 - Add support for the country code "{??}" in torrc options like
21394 ExcludeNodes, to indicate all routers of unknown country. Closes
21396 - Relays report the number of bytes spent on answering directory
21397 requests in extra-info descriptors similar to {read,write}-history.
21398 Implements enhancement 1790.
21400 o Minor bugfixes (on 0.2.1.x and earlier):
21401 - Complain if PublishServerDescriptor is given multiple arguments that
21402 include 0 or 1. This configuration will be rejected in the future.
21403 Bugfix on 0.2.0.1-alpha; closes bug 1107.
21404 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
21405 Bugfix on 0.2.0.13-alpha; closes bug 928.
21406 - Change "Application request when we're believed to be offline."
21407 notice to "Application request when we haven't used client
21408 functionality lately.", to clarify that it's not an error. Bugfix
21409 on 0.0.9.3; fixes bug 1222.
21410 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
21411 would return "551 Internal error" rather than "552 Unrecognized key
21412 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
21413 - Users can't configure a regular relay to be their bridge. It didn't
21414 work because when Tor fetched the bridge descriptor, it found
21415 that it already had it, and didn't realize that the purpose of the
21416 descriptor had changed. Now we replace routers with a purpose other
21417 than bridge with bridge descriptors when fetching them. Bugfix on
21418 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
21419 refetch the descriptor with router purpose 'general', disabling
21421 - Fix a rare bug in rend_fn unit tests: we would fail a test when
21422 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
21423 on 0.2.0.10-alpha; fixes bug 1808.
21424 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
21425 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
21426 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
21427 Servers can start sending this code when enough clients recognize
21428 it. Also update the spec to reflect this new reason. Bugfix on
21429 0.1.0.1-rc; fixes part of bug 1793.
21430 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
21431 when we switch from being a public relay to a bridge. Otherwise
21432 there will still be clients that see the relay in their consensus,
21433 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
21435 - Instead of giving an assertion failure on an internal mismatch
21436 on estimated freelist size, just log a BUG warning and try later.
21437 Mitigates but does not fix bug 1125.
21438 - Fix an assertion failure that could occur in caches or bridge users
21439 when using a very short voting interval on a testing network.
21440 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
21442 o Minor bugfixes (on 0.2.2.x):
21443 - Alter directory authorities to always consider Exit-flagged nodes
21444 as potential Guard nodes in their votes. The actual decision to
21445 use Exits as Guards is done in the consensus bandwidth weights.
21446 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
21447 - When the controller is reporting the purpose of circuits that
21448 didn't finish building before the circuit build timeout, it was
21449 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
21450 - Our libevent version parsing code couldn't handle versions like
21451 1.4.14b-stable and incorrectly warned the user about using an
21452 old and broken version of libevent. Treat 1.4.14b-stable like
21453 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
21455 - Don't use substitution references like $(VAR:MOD) when
21456 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
21457 '$(:x)' to 'x' rather than the empty string. This bites us in
21458 doc/ when configured with --disable-asciidoc. Bugfix on
21459 0.2.2.9-alpha; fixes bug 1773.
21460 - Remove a spurious hidden service server-side log notice about
21461 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
21463 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
21465 - Correctly report written bytes on linked connections. Found while
21466 implementing 1790. Bugfix on 0.2.2.4-alpha.
21467 - Fix three memory leaks: one in circuit_build_times_parse_state(),
21468 one in dirvote_add_signatures_to_pending_consensus(), and one every
21469 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
21470 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
21472 o Code simplifications and refactoring:
21473 - Take a first step towards making or.h smaller by splitting out
21474 function definitions for all source files in src/or/. Leave
21475 structures and defines in or.h for now.
21476 - Remove a bunch of unused function declarations as well as a block of
21477 #if 0'd code from the unit tests. Closes bug 1824.
21478 - New unit tests for exit-port history statistics; refactored exit
21479 statistics code to be more easily tested.
21480 - Remove the old debian/ directory from the main Tor distribution.
21481 The official Tor-for-debian git repository lives at the URL
21482 https://git.torproject.org/debian/tor.git
21485 Changes in version 0.2.2.14-alpha - 2010-07-12
21486 Tor 0.2.2.14-alpha greatly improves client-side handling of
21487 circuit build timeouts, which are used to estimate speed and improve
21488 performance. We also move to a much better GeoIP database, port Tor to
21489 Windows CE, introduce new compile flags that improve code security,
21490 add an eighth v3 directory authority, and address a lot of more
21494 - Tor directory authorities no longer crash when started with a
21495 cached-microdesc-consensus file in their data directory. Bugfix
21496 on 0.2.2.6-alpha; fixes bug 1532.
21497 - Treat an unset $HOME like an empty $HOME rather than triggering an
21498 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
21499 - Ignore negative and large circuit build timeout values that can
21500 happen during a suspend or hibernate. These values caused various
21501 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
21502 - Alter calculation of Pareto distribution parameter 'Xm' for
21503 Circuit Build Timeout learning to use the weighted average of the
21504 top N=3 modes (because we have three entry guards). Considering
21505 multiple modes should improve the timeout calculation in some cases,
21506 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
21508 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
21509 right censored distribution model. This approach improves over the
21510 synthetic timeout generation approach that was producing insanely
21511 high timeout values. Now we calculate build timeouts using truncated
21512 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
21513 - Do not close circuits that are under construction when they reach
21514 the circuit build timeout. Instead, leave them building (but do not
21515 use them) for up until the time corresponding to the 95th percentile
21516 on the Pareto CDF or 60 seconds, whichever is greater. This is done
21517 to provide better data for the new Pareto model. This percentile
21518 can be controlled by the consensus.
21521 - Move to the June 2010 Maxmind GeoLite country db (rather than the
21522 June 2009 ip-to-country GeoIP db) for our statistics that count
21523 how many users relays are seeing from each country. Now we have
21524 more accurate data for many African countries.
21525 - Port Tor to build and run correctly on Windows CE systems, using
21526 the wcecompat library. Contributed by Valerio Lupi.
21527 - New "--enable-gcc-hardening" ./configure flag (off by default)
21528 to turn on gcc compile time hardening options. It ensures
21529 that signed ints have defined behavior (-fwrapv), enables
21530 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
21531 with canaries (-fstack-protector-all), turns on ASLR protection if
21532 supported by the kernel (-fPIE, -pie), and adds additional security
21533 related warnings. Verified to work on Mac OS X and Debian Lenny.
21534 - New "--enable-linker-hardening" ./configure flag (off by default)
21535 to turn on ELF specific hardening features (relro, now). This does
21536 not work with Mac OS X or any other non-ELF binary format.
21538 o New directory authorities:
21539 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
21543 - New config option "WarnUnsafeSocks 0" disables the warning that
21544 occurs whenever Tor receives a socks handshake using a version of
21545 the socks protocol that can only provide an IP address (rather
21546 than a hostname). Setups that do DNS locally over Tor are fine,
21547 and we shouldn't spam the logs in that case.
21548 - Convert the HACKING file to asciidoc, and add a few new sections
21549 to it, explaining how we use Git, how we make changelogs, and
21550 what should go in a patch.
21551 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
21552 event, to give information on the current rate of circuit timeouts
21553 over our stored history.
21554 - Add ability to disable circuit build time learning via consensus
21555 parameter and via a LearnCircuitBuildTimeout config option. Also
21556 automatically disable circuit build time calculation if we are
21557 either a AuthoritativeDirectory, or if we fail to write our state
21558 file. Fixes bug 1296.
21559 - More gracefully handle corrupt state files, removing asserts
21560 in favor of saving a backup and resetting state.
21561 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
21565 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
21567 - When a2x fails, mention that the user could disable manpages instead
21568 of trying to fix their asciidoc installation.
21569 - Where available, use Libevent 2.0's periodic timers so that our
21570 once-per-second cleanup code gets called even more closely to
21571 once per second than it would otherwise. Fixes bug 943.
21572 - If you run a bridge that listens on multiple IP addresses, and
21573 some user configures a bridge address that uses a different IP
21574 address than your bridge writes in its router descriptor, and the
21575 user doesn't specify an identity key, their Tor would discard the
21576 descriptor because "it isn't one of our configured bridges", and
21577 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
21578 Bugfix on 0.2.0.3-alpha.
21579 - If OpenSSL fails to make a duplicate of a private or public key, log
21580 an error message and try to exit cleanly. May help with debugging
21581 if bug 1209 ever remanifests.
21582 - Save a couple bytes in memory allocation every time we escape
21583 certain characters in a string. Patch from Florian Zumbiehl.
21584 - Make it explicit that we don't cannibalize one-hop circuits. This
21585 happens in the wild, but doesn't turn out to be a problem because
21586 we fortunately don't use those circuits. Many thanks to outofwords
21587 for the initial analysis and to swissknife who confirmed that
21588 two-hop circuits are actually created.
21589 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
21590 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
21591 - Eliminate a case where a circuit build time warning was displayed
21592 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
21595 Changes in version 0.2.1.26 - 2010-05-02
21596 Tor 0.2.1.26 addresses the recent connection and memory overload
21597 problems we've been seeing on relays, especially relays with their
21598 DirPort open. If your relay has been crashing, or you turned it off
21599 because it used too many resources, give this release a try.
21601 This release also fixes yet another instance of broken OpenSSL libraries
21602 that was causing some relays to drop out of the consensus.
21605 - Teach relays to defend themselves from connection overload. Relays
21606 now close idle circuits early if it looks like they were intended
21607 for directory fetches. Relays are also more aggressive about closing
21608 TLS connections that have no circuits on them. Such circuits are
21609 unlikely to be re-used, and tens of thousands of them were piling
21610 up at the fast relays, causing the relays to run out of sockets
21611 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
21612 their directory fetches over TLS).
21613 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
21614 that claim to be earlier than 0.9.8m, but which have in reality
21615 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
21616 behavior. Possible fix for some cases of bug 1346.
21617 - Directory mirrors were fetching relay descriptors only from v2
21618 directory authorities, rather than v3 authorities like they should.
21619 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
21620 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
21623 - Finally get rid of the deprecated and now harmful notion of "clique
21624 mode", where directory authorities maintain TLS connections to
21628 - In the util/threads test, no longer free the test_mutex before all
21629 worker threads have finished. Bugfix on 0.2.1.6-alpha.
21630 - The master thread could starve the worker threads quite badly on
21631 certain systems, causing them to run only partially in the allowed
21632 window. This resulted in test failures. Now the master thread sleeps
21633 occasionally for a few microseconds while the two worker-threads
21634 compete for the mutex. Bugfix on 0.2.0.1-alpha.
21637 Changes in version 0.2.2.13-alpha - 2010-04-24
21638 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
21639 problems we've been seeing on relays, especially relays with their
21640 DirPort open. If your relay has been crashing, or you turned it off
21641 because it used too many resources, give this release a try.
21644 - Teach relays to defend themselves from connection overload. Relays
21645 now close idle circuits early if it looks like they were intended
21646 for directory fetches. Relays are also more aggressive about closing
21647 TLS connections that have no circuits on them. Such circuits are
21648 unlikely to be re-used, and tens of thousands of them were piling
21649 up at the fast relays, causing the relays to run out of sockets
21650 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
21651 their directory fetches over TLS).
21654 - Finally get rid of the deprecated and now harmful notion of "clique
21655 mode", where directory authorities maintain TLS connections to
21657 - Directory authorities now do an immediate reachability check as soon
21658 as they hear about a new relay. This change should slightly reduce
21659 the time between setting up a relay and getting listed as running
21660 in the consensus. It should also improve the time between setting
21661 up a bridge and seeing use by bridge users.
21662 - Directory authorities no longer launch a TLS connection to every
21663 relay as they startup. Now that we have 2k+ descriptors cached,
21664 the resulting network hiccup is becoming a burden. Besides,
21665 authorities already avoid voting about Running for the first half
21666 hour of their uptime.
21669 Changes in version 0.2.2.12-alpha - 2010-04-20
21670 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
21671 handle and vote on descriptors. It was causing relays to drop out of
21675 - Many relays have been falling out of the consensus lately because
21676 not enough authorities know about their descriptor for them to get
21677 a majority of votes. When we deprecated the v2 directory protocol,
21678 we got rid of the only way that v3 authorities can hear from each
21679 other about other descriptors. Now authorities examine every v3
21680 vote for new descriptors, and fetch them from that authority. Bugfix
21682 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
21683 and a warning in or.h related to bandwidth_weight_rule_t that
21684 prevented clean compile on OS X. Fixes bug 1363; bugfix on
21686 - Fix a segfault on relays when DirReqStatistics is enabled
21687 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
21691 - Demote a confusing TLS warning that relay operators might get when
21692 someone tries to talk to their OrPort. It is neither the operator's
21693 fault nor can they do anything about it. Fixes bug 1364; bugfix
21697 Changes in version 0.2.2.11-alpha - 2010-04-15
21698 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
21699 libraries that was causing some relays to drop out of the consensus.
21702 - Directory mirrors were fetching relay descriptors only from v2
21703 directory authorities, rather than v3 authorities like they should.
21704 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
21705 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
21706 - Fix a parsing error that made every possible value of
21707 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
21708 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
21709 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
21710 about the option without breaking older ones.
21711 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
21712 that claim to be earlier than 0.9.8m, but which have in reality
21713 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
21714 behavior. Possible fix for some cases of bug 1346.
21717 - Experiment with a more aggressive approach to preventing clients
21718 from making one-hop exit streams. Exit relays who want to try it
21719 out can set "RefuseUnknownExits 1" in their torrc, and then look
21720 for "Attempt by %s to open a stream" log messages. Let us know
21722 - Add support for statically linking zlib by specifying
21723 --enable-static-zlib, to go with our support for statically linking
21724 openssl and libevent. Resolves bug 1358.
21727 - Fix a segfault that happens whenever a Tor client that is using
21728 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
21730 - When we cleaned up the contrib/tor-exit-notice.html file, we left
21731 out the first line. Fixes bug 1295.
21732 - When building the manpage from a tarball, we required asciidoc, but
21733 the asciidoc -> roff/html conversion was already done for the
21734 tarball. Make 'make' complain only when we need asciidoc (either
21735 because we're compiling directly from git, or because we altered
21736 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
21737 - When none of the directory authorities vote on any params, Tor
21738 segfaulted when trying to make the consensus from the votes. We
21739 didn't trigger the bug in practice, because authorities do include
21740 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
21743 - In the util/threads test, no longer free the test_mutex before all
21744 worker threads have finished. Bugfix on 0.2.1.6-alpha.
21745 - The master thread could starve the worker threads quite badly on
21746 certain systems, causing them to run only partially in the allowed
21747 window. This resulted in test failures. Now the master thread sleeps
21748 occasionally for a few microseconds while the two worker-threads
21749 compete for the mutex. Bugfix on 0.2.0.1-alpha.
21752 Changes in version 0.2.2.10-alpha - 2010-03-07
21753 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
21754 could prevent relays from guessing their IP address correctly. It also
21755 starts the groundwork for another client-side performance boost, since
21756 currently we're not making efficient use of relays that have both the
21757 Guard flag and the Exit flag.
21760 - Fix a regression from our patch for bug 1244 that caused relays
21761 to guess their IP address incorrectly if they didn't set Address
21762 in their torrc and/or their address fails to resolve. Bugfix on
21763 0.2.2.9-alpha; fixes bug 1269.
21765 o Major features (performance):
21766 - Directory authorities now compute consensus weightings that instruct
21767 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
21768 and no flag. Clients that use these weightings will distribute
21769 network load more evenly across these different relay types. The
21770 weightings are in the consensus so we can change them globally in
21771 the future. Extra thanks to "outofwords" for finding some nasty
21772 security bugs in the first implementation of this feature.
21774 o Minor features (performance):
21775 - Always perform router selections using weighted relay bandwidth,
21776 even if we don't need a high capacity circuit at the time. Non-fast
21777 circuits now only differ from fast ones in that they can use relays
21778 not marked with the Fast flag. This "feature" could turn out to
21779 be a horrible bug; we should investigate more before it goes into
21783 - Allow disabling building of the manpages. Skipping the manpage
21784 speeds up the build considerably.
21786 o Minor bugfixes (on 0.2.2.x):
21787 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
21788 Bugfix on 0.2.2.9-alpha.
21789 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
21790 config option. Bugfix on 0.2.2.7-alpha.
21791 - Ship the asciidoc-helper file in the tarball, so that people can
21792 build from source if they want to, and touching the .1.txt files
21793 doesn't break the build. Bugfix on 0.2.2.9-alpha.
21795 o Minor bugfixes (on 0.2.1.x or earlier):
21796 - Fix a dereference-then-NULL-check sequence when publishing
21797 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
21799 - Fix another dereference-then-NULL-check sequence. Bugfix on
21800 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
21801 - Make sure we treat potentially not NUL-terminated strings correctly.
21802 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
21804 o Code simplifications and refactoring:
21805 - Fix some urls in the exit notice file and make it XHTML1.1 strict
21806 compliant. Based on a patch from Christian Kujau.
21807 - Don't use sed in asciidoc-helper anymore.
21808 - Make the build process fail if asciidoc cannot be found and
21809 building with asciidoc isn't disabled.
21812 Changes in version 0.2.2.9-alpha - 2010-02-22
21813 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
21814 location of a directory authority, and cleans up a bunch of small bugs.
21816 o Directory authority changes:
21817 - Change IP address for dannenberg (v3 directory authority), and
21818 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
21819 service directory authority) from the list.
21822 - Make Tor work again on the latest OS X: when deciding whether to
21823 use strange flags to turn TLS renegotiation on, detect the OpenSSL
21824 version at run-time, not compile time. We need to do this because
21825 Apple doesn't update its dev-tools headers when it updates its
21826 libraries in a security patch.
21827 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
21828 that could happen on 32-bit platforms with 64-bit time_t. Also fix
21829 a memory leak when requesting a hidden service descriptor we've
21830 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
21832 - Authorities could be tricked into giving out the Exit flag to relays
21833 that didn't allow exiting to any ports. This bug could screw
21834 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
21835 1238. Bug discovered by Martin Kowalczyk.
21836 - When freeing a session key, zero it out completely. We only zeroed
21837 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
21838 patched by ekir. Fixes bug 1254.
21841 - Fix static compilation by listing the openssl libraries in the right
21842 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
21843 - Resume handling .exit hostnames in a special way: originally we
21844 stripped the .exit part and used the requested exit relay. In
21845 0.2.2.1-alpha we stopped treating them in any special way, meaning
21846 if you use a .exit address then Tor will pass it on to the exit
21847 relay. Now we reject the .exit stream outright, since that behavior
21848 might be more expected by the user. Found and diagnosed by Scott
21849 Bennett and Downie on or-talk.
21850 - Don't spam the controller with events when we have no file
21851 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
21852 for log messages was already solved from bug 748.)
21853 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
21855 - Make the DNSPort option work with libevent 2.x. Don't alter the
21856 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
21857 - Emit a GUARD DROPPED controller event for a case we missed.
21858 - Make more fields in the controller protocol case-insensitive, since
21859 control-spec.txt said they were.
21860 - Refactor resolve_my_address() to not use gethostbyname() anymore.
21861 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
21862 - Fix a spec conformance issue: the network-status-version token
21863 must be the first token in a v3 consensus or vote. Discovered by
21864 parakeep. Bugfix on 0.2.0.3-alpha.
21866 o Code simplifications and refactoring:
21867 - Generate our manpage and HTML documentation using Asciidoc. This
21868 change should make it easier to maintain the documentation, and
21869 produce nicer HTML.
21870 - Remove the --enable-iphone option. According to reports from Marco
21871 Bonetti, Tor builds fine without any special tweaking on recent
21872 iPhone SDK versions.
21873 - Removed some unnecessary files from the source distribution. The
21874 AUTHORS file has now been merged into the people page on the
21875 website. The roadmaps and design doc can now be found in the
21876 projects directory in svn.
21877 - Enabled various circuit build timeout constants to be controlled
21878 by consensus parameters. Also set better defaults for these
21879 parameters based on experimentation on broadband and simulated
21880 high latency links.
21883 - The 'EXTENDCIRCUIT' control port command can now be used with
21884 a circ id of 0 and no path. This feature will cause Tor to build
21885 a new 'fast' general purpose circuit using its own path selection
21887 - Added a BUILDTIMEOUT_SET controller event to describe changes
21888 to the circuit build timeout.
21889 - Future-proof the controller protocol a bit by ignoring keyword
21890 arguments we do not recognize.
21891 - Expand homedirs passed to tor-checkkey. This should silence a
21892 coverity complaint about passing a user-supplied string into
21893 open() without checking it.
21896 Changes in version 0.2.1.25 - 2010-03-16
21897 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
21898 prevent relays from guessing their IP address correctly. It also fixes
21899 several minor potential security bugs.
21902 - Fix a regression from our patch for bug 1244 that caused relays
21903 to guess their IP address incorrectly if they didn't set Address
21904 in their torrc and/or their address fails to resolve. Bugfix on
21905 0.2.1.23; fixes bug 1269.
21906 - When freeing a session key, zero it out completely. We only zeroed
21907 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
21908 patched by ekir. Fixes bug 1254.
21911 - Fix a dereference-then-NULL-check sequence when publishing
21912 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
21914 - Fix another dereference-then-NULL-check sequence. Bugfix on
21915 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
21916 - Make sure we treat potentially not NUL-terminated strings correctly.
21917 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
21921 Changes in version 0.2.1.24 - 2010-02-21
21922 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
21926 - Work correctly out-of-the-box with even more vendor-patched versions
21927 of OpenSSL. In particular, make it so Debian and OS X don't need
21928 customized patches to run/build.
21931 Changes in version 0.2.1.23 - 2010-02-13
21932 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
21933 again on the latest OS X, and updates the location of a directory
21936 o Major bugfixes (performance):
21937 - We were selecting our guards uniformly at random, and then weighting
21938 which of our guards we'd use uniformly at random. This imbalance
21939 meant that Tor clients were severely limited on throughput (and
21940 probably latency too) by the first hop in their circuit. Now we
21941 select guards weighted by currently advertised bandwidth. We also
21942 automatically discard guards picked using the old algorithm. Fixes
21943 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
21946 - Make Tor work again on the latest OS X: when deciding whether to
21947 use strange flags to turn TLS renegotiation on, detect the OpenSSL
21948 version at run-time, not compile time. We need to do this because
21949 Apple doesn't update its dev-tools headers when it updates its
21950 libraries in a security patch.
21951 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
21952 that could happen on 32-bit platforms with 64-bit time_t. Also fix
21953 a memory leak when requesting a hidden service descriptor we've
21954 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
21957 o Directory authority changes:
21958 - Change IP address for dannenberg (v3 directory authority), and
21959 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
21960 service directory authority) from the list.
21963 - Refactor resolve_my_address() to not use gethostbyname() anymore.
21964 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
21967 - Avoid a mad rush at the beginning of each month when each client
21968 rotates half of its guards. Instead we spread the rotation out
21969 throughout the month, but we still avoid leaving a precise timestamp
21970 in the state file about when we first picked the guard. Improves
21971 over the behavior introduced in 0.1.2.17.
21974 Changes in version 0.2.2.8-alpha - 2010-01-26
21975 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
21976 causing bridge relays to disappear. If you're running a bridge,
21980 - Fix a memory corruption bug on bridges that occurred during the
21981 inclusion of stats data in extra-info descriptors. Also fix the
21982 interface for geoip_get_bridge_stats* to prevent similar bugs in
21983 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
21984 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
21987 - Ignore OutboundBindAddress when connecting to localhost.
21988 Connections to localhost need to come _from_ localhost, or else
21989 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
21993 Changes in version 0.2.2.7-alpha - 2010-01-19
21994 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
21995 as laying the groundwork for further relay-side performance fixes. It
21996 also starts cleaning up client behavior with respect to the EntryNodes,
21997 ExitNodes, and StrictNodes config options.
21999 This release also rotates two directory authority keys, due to a
22000 security breach of some of the Torproject servers.
22002 o Directory authority changes:
22003 - Rotate keys (both v3 identity and relay identity) for moria1
22006 o Major features (performance):
22007 - We were selecting our guards uniformly at random, and then weighting
22008 which of our guards we'd use uniformly at random. This imbalance
22009 meant that Tor clients were severely limited on throughput (and
22010 probably latency too) by the first hop in their circuit. Now we
22011 select guards weighted by currently advertised bandwidth. We also
22012 automatically discard guards picked using the old algorithm. Fixes
22013 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
22014 - When choosing which cells to relay first, relays can now favor
22015 circuits that have been quiet recently, to provide lower latency
22016 for low-volume circuits. By default, relays enable or disable this
22017 feature based on a setting in the consensus. You can override
22018 this default by using the new "CircuitPriorityHalflife" config
22019 option. Design and code by Ian Goldberg, Can Tang, and Chris
22021 - Add separate per-conn write limiting to go with the per-conn read
22022 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
22023 but never per-conn write limits.
22024 - New consensus params "bwconnrate" and "bwconnburst" to let us
22025 rate-limit client connections as they enter the network. It's
22026 controlled in the consensus so we can turn it on and off for
22027 experiments. It's starting out off. Based on proposal 163.
22029 o Major features (relay selection options):
22030 - Switch to a StrictNodes config option, rather than the previous
22031 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
22032 "StrictExcludeNodes" option.
22033 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
22034 change during a config reload, mark and discard all our origin
22035 circuits. This fix should address edge cases where we change the
22036 config options and but then choose a circuit that we created before
22038 - If EntryNodes or ExitNodes are set, be more willing to use an
22039 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
22041 - Make EntryNodes config option much more aggressive even when
22042 StrictNodes is not set. Before it would prepend your requested
22043 entrynodes to your list of guard nodes, but feel free to use others
22044 after that. Now it chooses only from your EntryNodes if any of
22045 those are available, and only falls back to others if a) they're
22046 all down and b) StrictNodes is not set.
22047 - Now we refresh your entry guards from EntryNodes at each consensus
22048 fetch -- rather than just at startup and then they slowly rot as
22049 the network changes.
22052 - Stop bridge directory authorities from answering dbg-stability.txt
22053 directory queries, which would let people fetch a list of all
22054 bridge identities they track. Bugfix on 0.2.1.6-alpha.
22057 - Log a notice when we get a new control connection. Now it's easier
22058 for security-conscious users to recognize when a local application
22059 is knocking on their controller door. Suggested by bug 1196.
22060 - New config option "CircuitStreamTimeout" to override our internal
22061 timeout schedule for how many seconds until we detach a stream from
22062 a circuit and try a new circuit. If your network is particularly
22063 slow, you might want to set this to a number like 60.
22064 - New controller command "getinfo config-text". It returns the
22065 contents that Tor would write if you send it a SAVECONF command,
22066 so the controller can write the file to disk itself.
22067 - New options for SafeLogging to allow scrubbing only log messages
22068 generated while acting as a relay.
22069 - Ship the bridges spec file in the tarball too.
22070 - Avoid a mad rush at the beginning of each month when each client
22071 rotates half of its guards. Instead we spread the rotation out
22072 throughout the month, but we still avoid leaving a precise timestamp
22073 in the state file about when we first picked the guard. Improves
22074 over the behavior introduced in 0.1.2.17.
22076 o Minor bugfixes (compiling):
22077 - Fix compilation on OS X 10.3, which has a stub mlockall() but
22078 hides it. Bugfix on 0.2.2.6-alpha.
22079 - Fix compilation on Solaris by removing support for the
22080 DisableAllSwap config option. Solaris doesn't have an rlimit for
22081 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
22084 o Minor bugfixes (crashes):
22085 - Do not segfault when writing buffer stats when we haven't observed
22086 a single circuit to report about. Found by Fabian Lanze. Bugfix on
22088 - If we're in the pathological case where there's no exit bandwidth
22089 but there is non-exit bandwidth, or no guard bandwidth but there
22090 is non-guard bandwidth, don't crash during path selection. Bugfix
22092 - Fix an impossible-to-actually-trigger buffer overflow in relay
22093 descriptor generation. Bugfix on 0.1.0.15.
22095 o Minor bugfixes (privacy):
22096 - Fix an instance where a Tor directory mirror might accidentally
22097 log the IP address of a misbehaving Tor client. Bugfix on
22099 - Don't list Windows capabilities in relay descriptors. We never made
22100 use of them, and maybe it's a bad idea to publish them. Bugfix
22103 o Minor bugfixes (other):
22104 - Resolve an edge case in path weighting that could make us misweight
22105 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
22106 - Fix statistics on client numbers by country as seen by bridges that
22107 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
22108 intervals instead of variable 12-to-48-hour intervals.
22109 - After we free an internal connection structure, overwrite it
22110 with a different memory value than we use for overwriting a freed
22111 internal circuit structure. Should help with debugging. Suggested
22113 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
22116 o Removed features:
22117 - Remove the HSAuthorityRecordStats option that version 0 hidden
22118 service authorities could have used to track statistics of overall
22119 hidden service usage.
22122 Changes in version 0.2.1.22 - 2010-01-19
22123 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
22124 authorities -- it would tell you its whole history of bridge descriptors
22125 if you make the right directory request. This stable update also
22126 rotates two of the seven v3 directory authority keys and locations.
22128 o Directory authority changes:
22129 - Rotate keys (both v3 identity and relay identity) for moria1
22133 - Stop bridge directory authorities from answering dbg-stability.txt
22134 directory queries, which would let people fetch a list of all
22135 bridge identities they track. Bugfix on 0.2.1.6-alpha.
22138 Changes in version 0.2.1.21 - 2009-12-21
22139 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
22140 library. If you use Tor on Linux / Unix and you're getting SSL
22141 renegotiation errors, upgrading should help. We also recommend an
22142 upgrade if you're an exit relay.
22145 - Work around a security feature in OpenSSL 0.9.8l that prevents our
22146 handshake from working unless we explicitly tell OpenSSL that we
22147 are using SSL renegotiation safely. We are, of course, but OpenSSL
22148 0.9.8l won't work unless we say we are.
22149 - Avoid crashing if the client is trying to upload many bytes and the
22150 circuit gets torn down at the same time, or if the flip side
22151 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
22154 - Do not refuse to learn about authority certs and v2 networkstatus
22155 documents that are older than the latest consensus. This bug might
22156 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
22157 Spotted and fixed by xmux.
22158 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
22159 trigger platform-specific option misparsing case found by Coverity
22161 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
22162 trigger assert. Fixes bug 1173.
22165 Changes in version 0.2.2.6-alpha - 2009-11-19
22166 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
22167 support for the new lower-footprint "microdescriptor" directory design,
22168 future-proofing our consensus format against new hash functions or
22169 other changes, and an Android port. It also makes Tor compatible with
22170 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
22173 - Directory authorities can now create, vote on, and serve multiple
22174 parallel formats of directory data as part of their voting process.
22175 Partially implements Proposal 162: "Publish the consensus in
22177 - Directory authorities can now agree on and publish small summaries
22178 of router information that clients can use in place of regular
22179 server descriptors. This transition will eventually allow clients
22180 to use far less bandwidth for downloading information about the
22181 network. Begins the implementation of Proposal 158: "Clients
22182 download consensus + microdescriptors".
22183 - The directory voting system is now extensible to use multiple hash
22184 algorithms for signatures and resource selection. Newer formats
22185 are signed with SHA256, with a possibility for moving to a better
22186 hash algorithm in the future.
22187 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
22188 current and future memory pages via mlockall(). On supported
22189 platforms (modern Linux and probably BSD but not Windows or OS X),
22190 this should effectively disable any and all attempts to page out
22191 memory. This option requires that you start your Tor as root --
22192 if you use DisableAllSwap, please consider using the User option
22193 to properly reduce the privileges of your Tor.
22194 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
22195 to help Tor build correctly for Android phones.
22198 - Work around a security feature in OpenSSL 0.9.8l that prevents our
22199 handshake from working unless we explicitly tell OpenSSL that we
22200 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
22201 won't work unless we say we are.
22204 - Fix a crash bug when trying to initialize the evdns module in
22205 Libevent 2. Bugfix on 0.2.1.16-rc.
22206 - Stop logging at severity 'warn' when some other Tor client tries
22207 to establish a circuit with us using weak DH keys. It's a protocol
22208 violation, but that doesn't mean ordinary users need to hear about
22209 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
22210 - Do not refuse to learn about authority certs and v2 networkstatus
22211 documents that are older than the latest consensus. This bug might
22212 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
22213 Spotted and fixed by xmux.
22214 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
22215 - If all authorities restart at once right before a consensus vote,
22216 nobody will vote about "Running", and clients will get a consensus
22217 with no usable relays. Instead, authorities refuse to build a
22218 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
22219 - If your relay can't keep up with the number of incoming create
22220 cells, it would log one warning per failure into your logs. Limit
22221 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
22222 - Bridges now use "reject *:*" as their default exit policy. Bugfix
22223 on 0.2.0.3-alpha; fixes bug 1113.
22224 - Fix a memory leak on directory authorities during voting that was
22225 introduced in 0.2.2.1-alpha. Found via valgrind.
22228 Changes in version 0.2.1.20 - 2009-10-15
22229 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
22230 services at once, prepares for more performance improvements, and
22231 fixes a bunch of smaller bugs.
22233 The Windows and OS X bundles also include a more recent Vidalia,
22234 and switch from Privoxy to Polipo.
22236 The OS X installers are now drag and drop. It's best to un-install
22237 Tor/Vidalia and then install this new bundle, rather than upgrade. If
22238 you want to upgrade, you'll need to update the paths for Tor and Polipo
22239 in the Vidalia Settings window.
22242 - Send circuit or stream sendme cells when our window has decreased
22243 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
22244 by Karsten when testing the "reduce circuit window" performance
22245 patch. Bugfix on the 54th commit on Tor -- from July 2002,
22246 before the release of Tor 0.0.0. This is the new winner of the
22248 - Fix a remotely triggerable memory leak when a consensus document
22249 contains more than one signature from the same voter. Bugfix on
22251 - Avoid segfault in rare cases when finishing an introduction circuit
22252 as a client and finding out that we don't have an introduction key
22253 for it. Fixes bug 1073. Reported by Aaron Swartz.
22256 - Tor now reads the "circwindow" parameter out of the consensus,
22257 and uses that value for its circuit package window rather than the
22258 default of 1000 cells. Begins the implementation of proposal 168.
22260 o New directory authorities:
22261 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
22263 - Move moria1 and tonga to alternate IP addresses.
22266 - Fix a signed/unsigned compile warning in 0.2.1.19.
22267 - Fix possible segmentation fault on directory authorities. Bugfix on
22269 - Fix an extremely rare infinite recursion bug that could occur if
22270 we tried to log a message after shutting down the log subsystem.
22271 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
22272 - Fix an obscure bug where hidden services on 64-bit big-endian
22273 systems might mis-read the timestamp in v3 introduce cells, and
22274 refuse to connect back to the client. Discovered by "rotor".
22275 Bugfix on 0.2.1.6-alpha.
22276 - We were triggering a CLOCK_SKEW controller status event whenever
22277 we connect via the v2 connection protocol to any relay that has
22278 a wrong clock. Instead, we should only inform the controller when
22279 it's a trusted authority that claims our clock is wrong. Bugfix
22280 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
22281 - We were telling the controller about CHECKING_REACHABILITY and
22282 REACHABILITY_FAILED status events whenever we launch a testing
22283 circuit or notice that one has failed. Instead, only tell the
22284 controller when we want to inform the user of overall success or
22285 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
22287 - Don't warn when we're using a circuit that ends with a node
22288 excluded in ExcludeExitNodes, but the circuit is not used to access
22289 the outside world. This should help fix bug 1090. Bugfix on
22291 - Work around a small memory leak in some versions of OpenSSL that
22292 stopped the memory used by the hostname TLS extension from being
22296 - Add a "getinfo status/accepted-server-descriptor" controller
22297 command, which is the recommended way for controllers to learn
22298 whether our server descriptor has been successfully received by at
22299 least on directory authority. Un-recommend good-server-descriptor
22300 getinfo and status events until we have a better design for them.
22303 Changes in version 0.2.2.5-alpha - 2009-10-11
22304 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
22307 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
22309 o Directory authorities:
22310 - Temporarily (just for this release) move dizum to an alternate
22314 Changes in version 0.2.2.4-alpha - 2009-10-10
22315 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
22316 introduces a new unit test framework, shifts directry authority
22317 addresses around to reduce the impact from recent blocking events,
22318 and fixes a few smaller bugs.
22321 - Fix several more asserts in the circuit_build_times code, for
22322 example one that causes Tor to fail to start once we have
22323 accumulated 5000 build times in the state file. Bugfixes on
22324 0.2.2.2-alpha; fixes bug 1108.
22326 o New directory authorities:
22327 - Move moria1 and Tonga to alternate IP addresses.
22330 - Log SSL state transitions at debug level during handshake, and
22331 include SSL states in error messages. This may help debug future
22332 SSL handshake issues.
22333 - Add a new "Handshake" log domain for activities that happen
22334 during the TLS handshake.
22335 - Revert to the "June 3 2009" ip-to-country file. The September one
22336 seems to have removed most US IP addresses.
22337 - Directory authorities now reject Tor relays with versions less than
22338 0.1.2.14. This step cuts out four relays from the current network,
22339 none of which are very big.
22342 - Fix a couple of smaller issues with gathering statistics. Bugfixes
22344 - Fix two memory leaks in the error case of
22345 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
22346 - Don't count one-hop circuits when we're estimating how long it
22347 takes circuits to build on average. Otherwise we'll set our circuit
22348 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
22349 - Directory authorities no longer change their opinion of, or vote on,
22350 whether a router is Running, unless they have themselves been
22351 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
22354 o Code simplifications and refactoring:
22355 - Revise our unit tests to use the "tinytest" framework, so we
22356 can run tests in their own processes, have smarter setup/teardown
22357 code, and so on. The unit test code has moved to its own
22358 subdirectory, and has been split into multiple modules.
22361 Changes in version 0.2.2.3-alpha - 2009-09-23
22362 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
22365 - Fix an overzealous assert in our new circuit build timeout code.
22366 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
22369 - If the networkstatus consensus tells us that we should use a
22370 negative circuit package window, ignore it. Otherwise we'll
22371 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
22374 Changes in version 0.2.2.2-alpha - 2009-09-21
22375 Tor 0.2.2.2-alpha introduces our latest performance improvement for
22376 clients: Tor tracks the average time it takes to build a circuit, and
22377 avoids using circuits that take too long to build. For fast connections,
22378 this feature can cut your expected latency in half. For slow or flaky
22379 connections, it could ruin your Tor experience. Let us know if it does!
22382 - Tor now tracks how long it takes to build client-side circuits
22383 over time, and adapts its timeout to local network performance.
22384 Since a circuit that takes a long time to build will also provide
22385 bad performance, we get significant latency improvements by
22386 discarding the slowest 20% of circuits. Specifically, Tor creates
22387 circuits more aggressively than usual until it has enough data
22388 points for a good timeout estimate. Implements proposal 151.
22389 We are especially looking for reports (good and bad) from users with
22390 both EDGE and broadband connections that can move from broadband
22391 to EDGE and find out if the build-time data in the .tor/state gets
22392 reset without loss of Tor usability. You should also see a notice
22393 log message telling you that Tor has reset its timeout.
22394 - Directory authorities can now vote on arbitrary integer values as
22395 part of the consensus process. This is designed to help set
22396 network-wide parameters. Implements proposal 167.
22397 - Tor now reads the "circwindow" parameter out of the consensus,
22398 and uses that value for its circuit package window rather than the
22399 default of 1000 cells. Begins the implementation of proposal 168.
22402 - Fix a remotely triggerable memory leak when a consensus document
22403 contains more than one signature from the same voter. Bugfix on
22407 - Fix an extremely rare infinite recursion bug that could occur if
22408 we tried to log a message after shutting down the log subsystem.
22409 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
22410 - Fix parsing for memory or time units given without a space between
22411 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
22412 - A networkstatus vote must contain exactly one signature. Spec
22413 conformance issue. Bugfix on 0.2.0.3-alpha.
22414 - Fix an obscure bug where hidden services on 64-bit big-endian
22415 systems might mis-read the timestamp in v3 introduce cells, and
22416 refuse to connect back to the client. Discovered by "rotor".
22417 Bugfix on 0.2.1.6-alpha.
22418 - We were triggering a CLOCK_SKEW controller status event whenever
22419 we connect via the v2 connection protocol to any relay that has
22420 a wrong clock. Instead, we should only inform the controller when
22421 it's a trusted authority that claims our clock is wrong. Bugfix
22422 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
22423 - We were telling the controller about CHECKING_REACHABILITY and
22424 REACHABILITY_FAILED status events whenever we launch a testing
22425 circuit or notice that one has failed. Instead, only tell the
22426 controller when we want to inform the user of overall success or
22427 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
22429 - Don't warn when we're using a circuit that ends with a node
22430 excluded in ExcludeExitNodes, but the circuit is not used to access
22431 the outside world. This should help fix bug 1090, but more problems
22432 remain. Bugfix on 0.2.1.6-alpha.
22433 - Work around a small memory leak in some versions of OpenSSL that
22434 stopped the memory used by the hostname TLS extension from being
22436 - Make our 'torify' script more portable; if we have only one of
22437 'torsocks' or 'tsocks' installed, don't complain to the user;
22438 and explain our warning about tsocks better.
22441 - Add a "getinfo status/accepted-server-descriptor" controller
22442 command, which is the recommended way for controllers to learn
22443 whether our server descriptor has been successfully received by at
22444 least on directory authority. Un-recommend good-server-descriptor
22445 getinfo and status events until we have a better design for them.
22446 - Update to the "September 4 2009" ip-to-country file.
22449 Changes in version 0.2.2.1-alpha - 2009-08-26
22450 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
22451 Tor clients to bootstrap on networks where only port 80 is reachable,
22452 makes it more straightforward to support hardware crypto accelerators,
22453 and starts the groundwork for gathering stats safely at relays.
22456 - Start the process of disabling ".exit" address notation, since it
22457 can be used for a variety of esoteric application-level attacks
22458 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
22461 o New directory authorities:
22462 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
22466 - New AccelName and AccelDir options add support for dynamic OpenSSL
22467 hardware crypto acceleration engines.
22468 - Tor now supports tunneling all of its outgoing connections over
22469 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
22470 configuration options. Code by Christopher Davis.
22473 - Send circuit or stream sendme cells when our window has decreased
22474 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
22475 by Karsten when testing the "reduce circuit window" performance
22476 patch. Bugfix on the 54th commit on Tor -- from July 2002,
22477 before the release of Tor 0.0.0. This is the new winner of the
22480 o New options for gathering stats safely:
22481 - Directory mirrors that set "DirReqStatistics 1" write statistics
22482 about directory requests to disk every 24 hours. As compared to the
22483 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
22484 1) stats are written to disk exactly every 24 hours; 2) estimated
22485 shares of v2 and v3 requests are determined as mean values, not at
22486 the end of a measurement period; 3) unresolved requests are listed
22487 with country code '??'; 4) directories also measure download times.
22488 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
22489 number of exit streams and transferred bytes per port to disk every
22491 - Relays that set "CellStatistics 1" write statistics on how long
22492 cells spend in their circuit queues to disk every 24 hours.
22493 - Entry nodes that set "EntryStatistics 1" write statistics on the
22494 rough number and origins of connecting clients to disk every 24
22496 - Relays that write any of the above statistics to disk and set
22497 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
22498 their extra-info documents.
22501 - New --digests command-line switch to output the digests of the
22502 source files Tor was built with.
22503 - The "torify" script now uses torsocks where available.
22504 - The memarea code now uses a sentinel value at the end of each area
22505 to make sure nothing writes beyond the end of an area. This might
22506 help debug some conceivable causes of bug 930.
22507 - Time and memory units in the configuration file can now be set to
22508 fractional units. For example, "2.5 GB" is now a valid value for
22510 - Certain Tor clients (such as those behind check.torproject.org) may
22511 want to fetch the consensus in an extra early manner. To enable this
22512 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
22513 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
22514 as only certain clients who must have this information sooner should
22516 - Instead of adding the svn revision to the Tor version string, report
22517 the git commit (when we're building from a git checkout).
22520 - If any of the v3 certs we download are unparseable, we should
22521 actually notice the failure so we don't retry indefinitely. Bugfix
22522 on 0.2.0.x; reported by "rotator".
22523 - If the cached cert file is unparseable, warn but don't exit.
22524 - Fix possible segmentation fault on directory authorities. Bugfix on
22526 - When Tor fails to parse a descriptor of any kind, dump it to disk.
22527 Might help diagnosing bug 1051.
22529 o Deprecated and removed features:
22530 - The controller no longer accepts the old obsolete "addr-mappings/"
22531 or "unregistered-servers-" GETINFO values.
22532 - Hidden services no longer publish version 0 descriptors, and clients
22533 do not request or use version 0 descriptors. However, the old hidden
22534 service authorities still accept and serve version 0 descriptors
22535 when contacted by older hidden services/clients.
22536 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
22537 always on; using them is necessary for correct forward-compatible
22539 - Remove support for .noconnect style addresses. Nobody was using
22540 them, and they provided another avenue for detecting Tor users
22541 via application-level web tricks.
22543 o Packaging changes:
22544 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
22545 installer bundles. See
22546 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
22547 for details of what's new in Vidalia 0.2.3.
22548 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
22549 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
22550 configuration file, rather than the old Privoxy.
22551 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
22552 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
22553 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
22554 better compatibility with OS X 10.6, aka Snow Leopard.
22555 - OS X Vidalia Bundle: The multi-package installer is now replaced
22556 by a simple drag and drop to the /Applications folder. This change
22557 occurred with the upgrade to Vidalia 0.2.3.
22560 Changes in version 0.2.1.19 - 2009-07-28
22561 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
22562 services on Tor 0.2.1.3-alpha through 0.2.1.18.
22565 - Make accessing hidden services on 0.2.1.x work right again.
22566 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
22567 part of patch provided by "optimist".
22570 - When a relay/bridge is writing out its identity key fingerprint to
22571 the "fingerprint" file and to its logs, write it without spaces. Now
22572 it will look like the fingerprints in our bridges documentation,
22573 and confuse fewer users.
22576 - Relays no longer publish a new server descriptor if they change
22577 their MaxAdvertisedBandwidth config option but it doesn't end up
22578 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
22579 fixes bug 1026. Patch from Sebastian.
22580 - Avoid leaking memory every time we get a create cell but we have
22581 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
22582 fixes bug 1034. Reported by BarkerJr.
22585 Changes in version 0.2.1.18 - 2009-07-24
22586 Tor 0.2.1.18 lays the foundations for performance improvements,
22587 adds status events to help users diagnose bootstrap problems, adds
22588 optional authentication/authorization for hidden services, fixes a
22589 variety of potential anonymity problems, and includes a huge pile of
22590 other features and bug fixes.
22593 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
22596 Changes in version 0.2.1.17-rc - 2009-07-07
22597 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
22598 candidate for the 0.2.1.x series. It lays the groundwork for further
22599 client performance improvements, and also fixes a big bug with directory
22600 authorities that were causing them to assign Guard and Stable flags
22603 The Windows bundles also finally include the geoip database that we
22604 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
22605 should actually install Torbutton rather than giving you a cryptic
22606 failure message (oops).
22609 - Clients now use the bandwidth values in the consensus, rather than
22610 the bandwidth values in each relay descriptor. This approach opens
22611 the door to more accurate bandwidth estimates once the directory
22612 authorities start doing active measurements. Implements more of
22616 - When Tor clients restart after 1-5 days, they discard all their
22617 cached descriptors as too old, but they still use the cached
22618 consensus document. This approach is good for robustness, but
22619 bad for performance: since they don't know any bandwidths, they
22620 end up choosing at random rather than weighting their choice by
22621 speed. Fixed by the above feature of putting bandwidths in the
22622 consensus. Bugfix on 0.2.0.x.
22623 - Directory authorities were neglecting to mark relays down in their
22624 internal histories if the relays fall off the routerlist without
22625 ever being found unreachable. So there were relays in the histories
22626 that haven't been seen for eight months, and are listed as being
22627 up for eight months. This wreaked havoc on the "median wfu"
22628 and "median mtbf" calculations, in turn making Guard and Stable
22629 flags very wrong, hurting network performance. Fixes bugs 696 and
22630 969. Bugfix on 0.2.0.6-alpha.
22633 - Serve the DirPortFrontPage page even when we have been approaching
22634 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
22635 - The control port would close the connection before flushing long
22636 replies, such as the network consensus, if a QUIT command was issued
22637 before the reply had completed. Now, the control port flushes all
22638 pending replies before closing the connection. Also fixed a spurious
22639 warning when a QUIT command is issued after a malformed or rejected
22640 AUTHENTICATE command, but before the connection was closed. Patch
22641 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
22642 - When we can't find an intro key for a v2 hidden service descriptor,
22643 fall back to the v0 hidden service descriptor and log a bug message.
22644 Workaround for bug 1024.
22645 - Fix a log message that did not respect the SafeLogging option.
22649 - If we're a relay and we change our IP address, be more verbose
22650 about the reason that made us change. Should help track down
22651 further bugs for relays on dynamic IP addresses.
22654 Changes in version 0.2.0.35 - 2009-06-24
22656 - Avoid crashing in the presence of certain malformed descriptors.
22657 Found by lark, and by automated fuzzing.
22658 - Fix an edge case where a malicious exit relay could convince a
22659 controller that the client's DNS question resolves to an internal IP
22660 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
22663 - Finally fix the bug where dynamic-IP relays disappear when their
22664 IP address changes: directory mirrors were mistakenly telling
22665 them their old address if they asked via begin_dir, so they
22666 never got an accurate answer about their new address, so they
22667 just vanished after a day. For belt-and-suspenders, relays that
22668 don't set Address in their config now avoid using begin_dir for
22669 all direct connections. Should fix bugs 827, 883, and 900.
22670 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
22671 that would occur on some exit nodes when DNS failures and timeouts
22672 occurred in certain patterns. Fix for bug 957.
22675 - When starting with a cache over a few days old, do not leak
22676 memory for the obsolete router descriptors in it. Bugfix on
22677 0.2.0.33; fixes bug 672.
22678 - Hidden service clients didn't use a cached service descriptor that
22679 was older than 15 minutes, but wouldn't fetch a new one either,
22680 because there was already one in the cache. Now, fetch a v2
22681 descriptor unless the same descriptor was added to the cache within
22682 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
22685 Changes in version 0.2.1.16-rc - 2009-06-20
22686 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
22687 a bunch of minor bugs.
22690 - Fix an edge case where a malicious exit relay could convince a
22691 controller that the client's DNS question resolves to an internal IP
22692 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
22694 o Major performance improvements (on 0.2.0.x):
22695 - Disable and refactor some debugging checks that forced a linear scan
22696 over the whole server-side DNS cache. These accounted for over 50%
22697 of CPU time on a relatively busy exit node's gprof profile. Found
22699 - Disable some debugging checks that appeared in exit node profile
22703 - Update to the "June 3 2009" ip-to-country file.
22704 - Do not have tor-resolve automatically refuse all .onion addresses;
22705 if AutomapHostsOnResolve is set in your torrc, this will work fine.
22707 o Minor bugfixes (on 0.2.0.x):
22708 - Log correct error messages for DNS-related network errors on
22710 - Fix a race condition that could cause crashes or memory corruption
22711 when running as a server with a controller listening for log
22713 - Avoid crashing when we have a policy specified in a DirPolicy or
22714 SocksPolicy or ReachableAddresses option with ports set on it,
22715 and we re-load the policy. May fix bug 996.
22716 - Hidden service clients didn't use a cached service descriptor that
22717 was older than 15 minutes, but wouldn't fetch a new one either,
22718 because there was already one in the cache. Now, fetch a v2
22719 descriptor unless the same descriptor was added to the cache within
22720 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
22722 o Minor bugfixes (on 0.2.1.x):
22723 - Don't warn users about low port and hibernation mix when they
22724 provide a *ListenAddress directive to fix that. Bugfix on
22726 - When switching back and forth between bridge mode, do not start
22727 gathering GeoIP data until two hours have passed.
22728 - Do not complain that the user has requested an excluded node as
22729 an exit when the node is not really an exit. This could happen
22730 because the circuit was for testing, or an introduction point.
22734 Changes in version 0.2.1.15-rc - 2009-05-25
22735 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
22736 series. It fixes a major bug on fast exit relays, as well as a variety
22737 of more minor bugs.
22739 o Major bugfixes (on 0.2.0.x):
22740 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
22741 that would occur on some exit nodes when DNS failures and timeouts
22742 occurred in certain patterns. Fix for bug 957.
22744 o Minor bugfixes (on 0.2.0.x):
22745 - Actually return -1 in the error case for read_bandwidth_usage().
22746 Harmless bug, since we currently don't care about the return value
22747 anywhere. Bugfix on 0.2.0.9-alpha.
22748 - Provide a more useful log message if bug 977 (related to buffer
22749 freelists) ever reappears, and do not crash right away.
22750 - Fix an assertion failure on 64-bit platforms when we allocated
22751 memory right up to the end of a memarea, then realigned the memory
22752 one step beyond the end. Fixes a possible cause of bug 930.
22753 - Protect the count of open sockets with a mutex, so we can't
22754 corrupt it when two threads are closing or opening sockets at once.
22755 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
22756 - Don't allow a bridge to publish its router descriptor to a
22757 non-bridge directory authority. Fixes part of bug 932.
22758 - When we change to or from being a bridge, reset our counts of
22759 client usage by country. Fixes bug 932.
22760 - Fix a bug that made stream bandwidth get misreported to the
22762 - Stop using malloc_usable_size() to use more area than we had
22763 actually allocated: it was safe, but made valgrind really unhappy.
22764 - Fix a memory leak when v3 directory authorities load their keys
22765 and cert from disk. Bugfix on 0.2.0.1-alpha.
22767 o Minor bugfixes (on 0.2.1.x):
22768 - Fix use of freed memory when deciding to mark a non-addable
22769 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
22772 Changes in version 0.2.1.14-rc - 2009-04-12
22773 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
22774 series. It begins fixing some major performance problems, and also
22775 finally addresses the bug that was causing relays on dynamic IP
22776 addresses to fall out of the directory.
22779 - Clients replace entry guards that were chosen more than a few months
22780 ago. This change should significantly improve client performance,
22781 especially once more people upgrade, since relays that have been
22782 a guard for a long time are currently overloaded.
22784 o Major bugfixes (on 0.2.0):
22785 - Finally fix the bug where dynamic-IP relays disappear when their
22786 IP address changes: directory mirrors were mistakenly telling
22787 them their old address if they asked via begin_dir, so they
22788 never got an accurate answer about their new address, so they
22789 just vanished after a day. For belt-and-suspenders, relays that
22790 don't set Address in their config now avoid using begin_dir for
22791 all direct connections. Should fix bugs 827, 883, and 900.
22792 - Relays were falling out of the networkstatus consensus for
22793 part of a day if they changed their local config but the
22794 authorities discarded their new descriptor as "not sufficiently
22795 different". Now directory authorities accept a descriptor as changed
22796 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
22797 patch by Sebastian.
22798 - Avoid crashing in the presence of certain malformed descriptors.
22799 Found by lark, and by automated fuzzing.
22802 - When generating circuit events with verbose nicknames for
22803 controllers, try harder to look up nicknames for routers on a
22804 circuit. (Previously, we would look in the router descriptors we had
22805 for nicknames, but not in the consensus.) Partial fix for bug 941.
22806 - If the bridge config line doesn't specify a port, assume 443.
22807 This makes bridge lines a bit smaller and easier for users to
22809 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
22810 bytes (aka 20KB/s), to match our documentation. Also update
22811 directory authorities so they always assign the Fast flag to relays
22812 with 20KB/s of capacity. Now people running relays won't suddenly
22813 find themselves not seeing any use, if the network gets faster
22815 - Update to the "April 3 2009" ip-to-country file.
22818 - Avoid trying to print raw memory to the logs when we decide to
22819 give up on downloading a given relay descriptor. Bugfix on
22821 - In tor-resolve, when the Tor client to use is specified by
22822 <hostname>:<port>, actually use the specified port rather than
22823 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
22824 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
22825 - When starting with a cache over a few days old, do not leak
22826 memory for the obsolete router descriptors in it. Bugfix on
22828 - Avoid double-free on list of successfully uploaded hidden
22829 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
22830 - Change memarea_strndup() implementation to work even when
22831 duplicating a string at the end of a page. This bug was
22832 harmless for now, but could have meant crashes later. Fix by
22833 lark. Bugfix on 0.2.1.1-alpha.
22834 - Limit uploaded directory documents to be 16M rather than 500K.
22835 The directory authorities were refusing v3 consensus votes from
22836 other authorities, since the votes are now 504K. Fixes bug 959;
22837 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
22838 - Directory authorities should never send a 503 "busy" response to
22839 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
22843 Changes in version 0.2.1.13-alpha - 2009-03-09
22844 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
22845 cleanups. We're finally getting close to a release candidate.
22848 - Correctly update the list of which countries we exclude as
22849 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
22850 lark. Bugfix on 0.2.1.6-alpha.
22852 o Minor bugfixes (on 0.2.0.x and earlier):
22853 - Automatically detect MacOSX versions earlier than 10.4.0, and
22854 disable kqueue from inside Tor when running with these versions.
22855 We previously did this from the startup script, but that was no
22856 help to people who didn't use the startup script. Resolves bug 863.
22857 - When we had picked an exit node for a connection, but marked it as
22858 "optional", and it turned out we had no onion key for the exit,
22859 stop wanting that exit and try again. This situation may not
22860 be possible now, but will probably become feasible with proposal
22861 158. Spotted by rovv. Fixes another case of bug 752.
22862 - Clients no longer cache certificates for authorities they do not
22863 recognize. Bugfix on 0.2.0.9-alpha.
22864 - When we can't transmit a DNS request due to a network error, retry
22865 it after a while, and eventually transmit a failing response to
22866 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
22867 - If the controller claimed responsibility for a stream, but that
22868 stream never finished making its connection, it would live
22869 forever in circuit_wait state. Now we close it after SocksTimeout
22870 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
22871 - Drop begin cells to a hidden service if they come from the middle
22872 of a circuit. Patch from lark.
22873 - When we erroneously receive two EXTEND cells for the same circuit
22874 ID on the same connection, drop the second. Patch from lark.
22875 - Fix a crash that occurs on exit nodes when a nameserver request
22876 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
22877 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
22879 - Do not assume that a stack-allocated character array will be
22880 64-bit aligned on platforms that demand that uint64_t access is
22881 aligned. Possible fix for bug 604.
22882 - Parse dates and IPv4 addresses in a locale- and libc-independent
22883 manner, to avoid platform-dependent behavior on malformed input.
22884 - Build correctly when configured to build outside the main source
22885 path. Patch from Michael Gold.
22886 - We were already rejecting relay begin cells with destination port
22887 of 0. Now also reject extend cells with destination port or address
22888 of 0. Suggested by lark.
22890 o Minor bugfixes (on 0.2.1.x):
22891 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
22892 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
22893 - If we're an exit node, scrub the IP address to which we are exiting
22894 in the logs. Bugfix on 0.2.1.8-alpha.
22897 - On Linux, use the prctl call to re-enable core dumps when the user
22899 - New controller event NEWCONSENSUS that lists the networkstatus
22900 lines for every recommended relay. Now controllers like Torflow
22901 can keep up-to-date on which relays they should be using.
22902 - Update to the "February 26 2009" ip-to-country file.
22905 Changes in version 0.2.0.34 - 2009-02-08
22906 Tor 0.2.0.34 features several more security-related fixes. You should
22907 upgrade, especially if you run an exit relay (remote crash) or a
22908 directory authority (remote infinite loop), or you're on an older
22909 (pre-XP) or not-recently-patched Windows (remote exploit).
22911 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
22912 have many known flaws, and nobody should be using them. You should
22913 upgrade. If you're using a Linux or BSD and its packages are obsolete,
22914 stop using those packages and upgrade anyway.
22917 - Fix an infinite-loop bug on handling corrupt votes under certain
22918 circumstances. Bugfix on 0.2.0.8-alpha.
22919 - Fix a temporary DoS vulnerability that could be performed by
22920 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
22921 - Avoid a potential crash on exit nodes when processing malformed
22922 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
22923 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
22924 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
22927 - Fix compilation on systems where time_t is a 64-bit integer.
22928 Patch from Matthias Drochner.
22929 - Don't consider expiring already-closed client connections. Fixes
22930 bug 893. Bugfix on 0.0.2pre20.
22933 Changes in version 0.2.1.12-alpha - 2009-02-08
22934 Tor 0.2.1.12-alpha features several more security-related fixes. You
22935 should upgrade, especially if you run an exit relay (remote crash) or
22936 a directory authority (remote infinite loop), or you're on an older
22937 (pre-XP) or not-recently-patched Windows (remote exploit). It also
22938 includes a big pile of minor bugfixes and cleanups.
22941 - Fix an infinite-loop bug on handling corrupt votes under certain
22942 circumstances. Bugfix on 0.2.0.8-alpha.
22943 - Fix a temporary DoS vulnerability that could be performed by
22944 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
22945 - Avoid a potential crash on exit nodes when processing malformed
22946 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
22949 - Let controllers actually ask for the "clients_seen" event for
22950 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
22951 reported by Matt Edman.
22952 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
22954 - Fix a bug in address parsing that was preventing bridges or hidden
22955 service targets from being at IPv6 addresses.
22956 - Solve a bug that kept hardware crypto acceleration from getting
22957 enabled when accounting was turned on. Fixes bug 907. Bugfix on
22959 - Remove a bash-ism from configure.in to build properly on non-Linux
22960 platforms. Bugfix on 0.2.1.1-alpha.
22961 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
22962 headers. Bugfix on 0.2.0.10-alpha.
22963 - Don't consider expiring already-closed client connections. Fixes
22964 bug 893. Bugfix on 0.0.2pre20.
22965 - Fix another interesting corner-case of bug 891 spotted by rovv:
22966 Previously, if two hosts had different amounts of clock drift, and
22967 one of them created a new connection with just the wrong timing,
22968 the other might decide to deprecate the new connection erroneously.
22969 Bugfix on 0.1.1.13-alpha.
22970 - Resolve a very rare crash bug that could occur when the user forced
22971 a nameserver reconfiguration during the middle of a nameserver
22972 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
22973 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
22974 Bugfix on 0.2.1.7-alpha.
22975 - If we're using bridges and our network goes away, be more willing
22976 to forgive our bridges and try again when we get an application
22977 request. Bugfix on 0.2.0.x.
22980 - Support platforms where time_t is 64 bits long. (Congratulations,
22981 NetBSD!) Patch from Matthias Drochner.
22982 - Add a 'getinfo status/clients-seen' controller command, in case
22983 controllers want to hear clients_seen events but connect late.
22986 - Disable GCC's strict alias optimization by default, to avoid the
22987 likelihood of its introducing subtle bugs whenever our code violates
22988 the letter of C99's alias rules.
22991 Changes in version 0.2.0.33 - 2009-01-21
22992 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
22993 useful to users. It also finally fixes a bug where a relay or client
22994 that's been off for many days would take a long time to bootstrap.
22996 This update also fixes an important security-related bug reported by
22997 Ilja van Sprundel. You should upgrade. (We'll send out more details
22998 about the bug once people have had some time to upgrade.)
23001 - Fix a heap-corruption bug that may be remotely triggerable on
23002 some platforms. Reported by Ilja van Sprundel.
23005 - When a stream at an exit relay is in state "resolving" or
23006 "connecting" and it receives an "end" relay cell, the exit relay
23007 would silently ignore the end cell and not close the stream. If
23008 the client never closes the circuit, then the exit relay never
23009 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
23010 reported by "wood".
23011 - When sending CREATED cells back for a given circuit, use a 64-bit
23012 connection ID to find the right connection, rather than an addr:port
23013 combination. Now that we can have multiple OR connections between
23014 the same ORs, it is no longer possible to use addr:port to uniquely
23015 identify a connection.
23016 - Bridge relays that had DirPort set to 0 would stop fetching
23017 descriptors shortly after startup, and then briefly resume
23018 after a new bandwidth test and/or after publishing a new bridge
23019 descriptor. Bridge users that try to bootstrap from them would
23020 get a recent networkstatus but would get descriptors from up to
23021 18 hours earlier, meaning most of the descriptors were obsolete
23022 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
23023 - Prevent bridge relays from serving their 'extrainfo' document
23024 to anybody who asks, now that extrainfo docs include potentially
23025 sensitive aggregated client geoip summaries. Bugfix on
23027 - If the cached networkstatus consensus is more than five days old,
23028 discard it rather than trying to use it. In theory it could be
23029 useful because it lists alternate directory mirrors, but in practice
23030 it just means we spend many minutes trying directory mirrors that
23031 are long gone from the network. Also discard router descriptors as
23032 we load them if they are more than five days old, since the onion
23033 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
23036 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
23037 could make gcc generate non-functional binary search code. Bugfix
23039 - Build correctly on platforms without socklen_t.
23040 - Compile without warnings on solaris.
23041 - Avoid potential crash on internal error during signature collection.
23042 Fixes bug 864. Patch from rovv.
23043 - Correct handling of possible malformed authority signing key
23044 certificates with internal signature types. Fixes bug 880.
23045 Bugfix on 0.2.0.3-alpha.
23046 - Fix a hard-to-trigger resource leak when logging credential status.
23048 - When we can't initialize DNS because the network is down, do not
23049 automatically stop Tor from starting. Instead, we retry failed
23050 dns_init() every 10 minutes, and change the exit policy to reject
23051 *:* until one succeeds. Fixes bug 691.
23052 - Use 64 bits instead of 32 bits for connection identifiers used with
23053 the controller protocol, to greatly reduce risk of identifier reuse.
23054 - When we're choosing an exit node for a circuit, and we have
23055 no pending streams, choose a good general exit rather than one that
23056 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
23057 - Fix another case of assuming, when a specific exit is requested,
23058 that we know more than the user about what hosts it allows.
23059 Fixes one case of bug 752. Patch from rovv.
23060 - Clip the MaxCircuitDirtiness config option to a minimum of 10
23061 seconds. Warn the user if lower values are given in the
23062 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
23063 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
23064 user if lower values are given in the configuration. Bugfix on
23065 0.1.1.17-rc. Patch by Sebastian.
23066 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
23067 the cache because we already had a v0 descriptor with the same ID.
23068 Bugfix on 0.2.0.18-alpha.
23069 - Fix a race condition when freeing keys shared between main thread
23070 and CPU workers that could result in a memory leak. Bugfix on
23071 0.1.0.1-rc. Fixes bug 889.
23072 - Send a valid END cell back when a client tries to connect to a
23073 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
23074 840. Patch from rovv.
23075 - Check which hops rendezvous stream cells are associated with to
23076 prevent possible guess-the-streamid injection attacks from
23077 intermediate hops. Fixes another case of bug 446. Based on patch
23079 - If a broken client asks a non-exit router to connect somewhere,
23080 do not even do the DNS lookup before rejecting the connection.
23081 Fixes another case of bug 619. Patch from rovv.
23082 - When a relay gets a create cell it can't decrypt (e.g. because it's
23083 using the wrong onion key), we were dropping it and letting the
23084 client time out. Now actually answer with a destroy cell. Fixes
23085 bug 904. Bugfix on 0.0.2pre8.
23087 o Minor bugfixes (hidden services):
23088 - Do not throw away existing introduction points on SIGHUP. Bugfix on
23089 0.0.6pre1. Patch by Karsten. Fixes bug 874.
23092 - Report the case where all signatures in a detached set are rejected
23093 differently than the case where there is an error handling the
23095 - When we realize that another process has modified our cached
23096 descriptors, print out a more useful error message rather than
23097 triggering an assertion. Fixes bug 885. Patch from Karsten.
23098 - Implement the 0x20 hack to better resist DNS poisoning: set the
23099 case on outgoing DNS requests randomly, and reject responses that do
23100 not match the case correctly. This logic can be disabled with the
23101 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
23102 of servers that do not reliably preserve case in replies. See
23103 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
23105 - Check DNS replies for more matching fields to better resist DNS
23107 - Never use OpenSSL compression: it wastes RAM and CPU trying to
23108 compress cells, which are basically all encrypted, compressed, or
23112 Changes in version 0.2.1.11-alpha - 2009-01-20
23113 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
23114 week it will take a long time to bootstrap again" bug. It also fixes
23115 an important security-related bug reported by Ilja van Sprundel. You
23116 should upgrade. (We'll send out more details about the bug once people
23117 have had some time to upgrade.)
23120 - Fix a heap-corruption bug that may be remotely triggerable on
23121 some platforms. Reported by Ilja van Sprundel.
23124 - Discard router descriptors as we load them if they are more than
23125 five days old. Otherwise if Tor is off for a long time and then
23126 starts with cached descriptors, it will try to use the onion
23127 keys in those obsolete descriptors when building circuits. Bugfix
23128 on 0.2.0.x. Fixes bug 887.
23131 - Try to make sure that the version of Libevent we're running with
23132 is binary-compatible with the one we built with. May address bug
23134 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
23135 for bug 905. Bugfix on 0.2.1.7-alpha.
23136 - Add a new --enable-local-appdata configuration switch to change
23137 the default location of the datadir on win32 from APPDATA to
23138 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
23139 entirely. Patch from coderman.
23142 - Make outbound DNS packets respect the OutboundBindAddress setting.
23143 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
23144 - When our circuit fails at the first hop (e.g. we get a destroy
23145 cell back), avoid using that OR connection anymore, and also
23146 tell all the one-hop directory requests waiting for it that they
23147 should fail. Bugfix on 0.2.1.3-alpha.
23148 - In the torify(1) manpage, mention that tsocks will leak your
23152 Changes in version 0.2.1.10-alpha - 2009-01-06
23153 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
23154 would make the bridge relay not so useful if it had DirPort set to 0,
23155 and one that could let an attacker learn a little bit of information
23156 about the bridge's users), and a bug that would cause your Tor relay
23157 to ignore a circuit create request it can't decrypt (rather than reply
23158 with an error). It also fixes a wide variety of other bugs.
23161 - If the cached networkstatus consensus is more than five days old,
23162 discard it rather than trying to use it. In theory it could
23163 be useful because it lists alternate directory mirrors, but in
23164 practice it just means we spend many minutes trying directory
23165 mirrors that are long gone from the network. Helps bug 887 a bit;
23167 - Bridge relays that had DirPort set to 0 would stop fetching
23168 descriptors shortly after startup, and then briefly resume
23169 after a new bandwidth test and/or after publishing a new bridge
23170 descriptor. Bridge users that try to bootstrap from them would
23171 get a recent networkstatus but would get descriptors from up to
23172 18 hours earlier, meaning most of the descriptors were obsolete
23173 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
23174 - Prevent bridge relays from serving their 'extrainfo' document
23175 to anybody who asks, now that extrainfo docs include potentially
23176 sensitive aggregated client geoip summaries. Bugfix on
23180 - New controller event "clients_seen" to report a geoip-based summary
23181 of which countries we've seen clients from recently. Now controllers
23182 like Vidalia can show bridge operators that they're actually making
23184 - Build correctly against versions of OpenSSL 0.9.8 or later built
23185 without support for deprecated functions.
23186 - Update to the "December 19 2008" ip-to-country file.
23188 o Minor bugfixes (on 0.2.0.x):
23189 - Authorities now vote for the Stable flag for any router whose
23190 weighted MTBF is at least 5 days, regardless of the mean MTBF.
23191 - Do not remove routers as too old if we do not have any consensus
23192 document. Bugfix on 0.2.0.7-alpha.
23193 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
23194 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
23195 - When an exit relay resolves a stream address to a local IP address,
23196 do not just keep retrying that same exit relay over and
23197 over. Instead, just close the stream. Addresses bug 872. Bugfix
23198 on 0.2.0.32. Patch from rovv.
23199 - If a hidden service sends us an END cell, do not consider
23200 retrying the connection; just close it. Patch from rovv.
23201 - When we made bridge authorities stop serving bridge descriptors over
23202 unencrypted links, we also broke DirPort reachability testing for
23203 bridges. So bridges with a non-zero DirPort were printing spurious
23204 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
23205 - When a relay gets a create cell it can't decrypt (e.g. because it's
23206 using the wrong onion key), we were dropping it and letting the
23207 client time out. Now actually answer with a destroy cell. Fixes
23208 bug 904. Bugfix on 0.0.2pre8.
23209 - Squeeze 2-5% out of client performance (according to oprofile) by
23210 improving the implementation of some policy-manipulation functions.
23212 o Minor bugfixes (on 0.2.1.x):
23213 - Make get_interface_address() function work properly again; stop
23214 guessing the wrong parts of our address as our address.
23215 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
23216 send on that circuit. Otherwise we might violate the proposal-110
23217 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
23219 - When we're sending non-EXTEND cells to the first hop in a circuit,
23220 for example to use an encrypted directory connection, we don't need
23221 to use RELAY_EARLY cells: the first hop knows what kind of cell
23222 it is, and nobody else can even see the cell type. Conserving
23223 RELAY_EARLY cells makes it easier to cannibalize circuits like
23225 - Stop logging nameserver addresses in reverse order.
23226 - If we are retrying a directory download slowly over and over, do
23227 not automatically give up after the 254th failure. Bugfix on
23229 - Resume reporting accurate "stream end" reasons to the local control
23230 port. They were lost in the changes for Proposal 148. Bugfix on
23233 o Deprecated and removed features:
23234 - The old "tor --version --version" command, which would print out
23235 the subversion "Id" of most of the source files, is now removed. It
23236 turned out to be less useful than we'd expected, and harder to
23239 o Code simplifications and refactoring:
23240 - Change our header file guard macros to be less likely to conflict
23241 with system headers. Adam Langley noticed that we were conflicting
23242 with log.h on Android.
23243 - Tool-assisted documentation cleanup. Nearly every function or
23244 static variable in Tor should have its own documentation now.
23247 Changes in version 0.2.1.9-alpha - 2008-12-25
23248 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
23250 o New directory authorities:
23251 - gabelmoo (the authority run by Karsten Loesing) now has a new
23255 - Never use a connection with a mismatched address to extend a
23256 circuit, unless that connection is canonical. A canonical
23257 connection is one whose address is authenticated by the router's
23258 identity key, either in a NETINFO cell or in a router descriptor.
23259 - Avoid a possible memory corruption bug when receiving hidden service
23260 descriptors. Bugfix on 0.2.1.6-alpha.
23263 - Fix a logic error that would automatically reject all but the first
23264 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
23265 part of bug 813/868. Bug spotted by coderman.
23266 - When a stream at an exit relay is in state "resolving" or
23267 "connecting" and it receives an "end" relay cell, the exit relay
23268 would silently ignore the end cell and not close the stream. If
23269 the client never closes the circuit, then the exit relay never
23270 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
23271 reported by "wood".
23272 - When we can't initialize DNS because the network is down, do not
23273 automatically stop Tor from starting. Instead, retry failed
23274 dns_init() every 10 minutes, and change the exit policy to reject
23275 *:* until one succeeds. Fixes bug 691.
23278 - Give a better error message when an overzealous init script says
23279 "sudo -u username tor --user username". Makes Bug 882 easier for
23281 - When a directory authority gives us a new guess for our IP address,
23282 log which authority we used. Hopefully this will help us debug
23283 the recent complaints about bad IP address guesses.
23284 - Detect svn revision properly when we're using git-svn.
23285 - Try not to open more than one descriptor-downloading connection
23286 to an authority at once. This should reduce load on directory
23287 authorities. Fixes bug 366.
23288 - Add cross-certification to newly generated certificates, so that
23289 a signing key is enough information to look up a certificate.
23290 Partial implementation of proposal 157.
23291 - Start serving certificates by <identity digest, signing key digest>
23292 pairs. Partial implementation of proposal 157.
23293 - Clients now never report any stream end reason except 'MISC'.
23294 Implements proposal 148.
23295 - On platforms with a maximum syslog string length, truncate syslog
23296 messages to that length ourselves, rather than relying on the
23297 system to do it for us.
23298 - Optimize out calls to time(NULL) that occur for every IO operation,
23299 or for every cell. On systems where time() is a slow syscall,
23300 this fix will be slightly helpful.
23301 - Exit servers can now answer resolve requests for ip6.arpa addresses.
23302 - When we download a descriptor that we then immediately (as
23303 a directory authority) reject, do not retry downloading it right
23304 away. Should save some bandwidth on authorities. Fix for bug
23305 888. Patch by Sebastian Hahn.
23306 - When a download gets us zero good descriptors, do not notify
23307 Tor that new directory information has arrived.
23308 - Avoid some nasty corner cases in the logic for marking connections
23309 as too old or obsolete or noncanonical for circuits. Partial
23312 o Minor features (controller):
23313 - New CONSENSUS_ARRIVED event to note when a new consensus has
23314 been fetched and validated.
23315 - When we realize that another process has modified our cached
23316 descriptors file, print out a more useful error message rather
23317 than triggering an assertion. Fixes bug 885. Patch from Karsten.
23318 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
23319 controllers to prevent SIGHUP from reloading the
23320 configuration. Fixes bug 856.
23323 - Resume using the correct "REASON=" stream when telling the
23324 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
23325 - When a canonical connection appears later in our internal list
23326 than a noncanonical one for a given OR ID, always use the
23327 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
23329 - Clip the MaxCircuitDirtiness config option to a minimum of 10
23330 seconds. Warn the user if lower values are given in the
23331 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
23332 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
23333 user if lower values are given in the configuration. Bugfix on
23334 0.1.1.17-rc. Patch by Sebastian.
23335 - Fix a race condition when freeing keys shared between main thread
23336 and CPU workers that could result in a memory leak. Bugfix on
23337 0.1.0.1-rc. Fixes bug 889.
23339 o Minor bugfixes (hidden services):
23340 - Do not throw away existing introduction points on SIGHUP (bugfix on
23341 0.0.6pre1); also, do not stall hidden services because we're
23342 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
23343 by John Brooks. Patch by Karsten. Fixes bug 874.
23344 - Fix a memory leak when we decline to add a v2 rendezvous
23345 descriptor to the cache because we already had a v0 descriptor
23346 with the same ID. Bugfix on 0.2.0.18-alpha.
23348 o Deprecated and removed features:
23349 - RedirectExits has been removed. It was deprecated since
23351 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
23352 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
23353 - Cell pools are now always enabled; --disable-cell-pools is ignored.
23355 o Code simplifications and refactoring:
23356 - Rename the confusing or_is_obsolete field to the more appropriate
23357 is_bad_for_new_circs, and move it to or_connection_t where it
23359 - Move edge-only flags from connection_t to edge_connection_t: not
23360 only is this better coding, but on machines of plausible alignment,
23361 it should save 4-8 bytes per connection_t. "Every little bit helps."
23362 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
23363 for consistency; keep old option working for backward compatibility.
23364 - Simplify the code for finding connections to use for a circuit.
23367 Changes in version 0.2.1.8-alpha - 2008-12-08
23368 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
23369 builds better on unusual platforms like Solaris and old OS X, and
23370 fixes a variety of other issues.
23373 - New DirPortFrontPage option that takes an html file and publishes
23374 it as "/" on the DirPort. Now relay operators can provide a
23375 disclaimer without needing to set up a separate webserver. There's
23376 a sample disclaimer in contrib/tor-exit-notice.html.
23379 - When the client is choosing entry guards, now it selects at most
23380 one guard from a given relay family. Otherwise we could end up with
23381 all of our entry points into the network run by the same operator.
23382 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
23385 - Fix a DOS opportunity during the voting signature collection process
23386 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
23387 - Fix a possible segfault when establishing an exit connection. Bugfix
23391 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
23393 - Made Tor a little less aggressive about deleting expired
23394 certificates. Partial fix for bug 854.
23395 - Stop doing unaligned memory access that generated bus errors on
23396 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
23397 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
23398 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
23399 - Make USR2 log-level switch take effect immediately. Bugfix on
23401 - If one win32 nameserver fails to get added, continue adding the
23402 rest, and don't automatically fail.
23403 - Use fcntl() for locking when flock() is not available. Should fix
23404 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
23405 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
23406 could make gcc generate non-functional binary search code. Bugfix
23408 - Build correctly on platforms without socklen_t.
23409 - Avoid potential crash on internal error during signature collection.
23410 Fixes bug 864. Patch from rovv.
23411 - Do not use C's stdio library for writing to log files. This will
23412 improve logging performance by a minute amount, and will stop
23413 leaking fds when our disk is full. Fixes bug 861.
23414 - Stop erroneous use of O_APPEND in cases where we did not in fact
23415 want to re-seek to the end of a file before every last write().
23416 - Correct handling of possible malformed authority signing key
23417 certificates with internal signature types. Fixes bug 880. Bugfix
23419 - Fix a hard-to-trigger resource leak when logging credential status.
23423 - Directory mirrors no longer fetch the v1 directory or
23424 running-routers files. They are obsolete, and nobody asks for them
23425 anymore. This is the first step to making v1 authorities obsolete.
23427 o Minor features (controller):
23428 - Return circuit purposes in response to GETINFO circuit-status. Fixes
23432 Changes in version 0.2.0.32 - 2008-11-20
23433 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
23434 packages (and maybe other packages) noticed by Theo de Raadt, fixes
23435 a smaller security flaw that might allow an attacker to access local
23436 services, further improves hidden service performance, and fixes a
23437 variety of other issues.
23440 - The "User" and "Group" config options did not clear the
23441 supplementary group entries for the Tor process. The "User" option
23442 is now more robust, and we now set the groups to the specified
23443 user's primary group. The "Group" option is now ignored. For more
23444 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
23445 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
23446 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
23447 - The "ClientDNSRejectInternalAddresses" config option wasn't being
23448 consistently obeyed: if an exit relay refuses a stream because its
23449 exit policy doesn't allow it, we would remember what IP address
23450 the relay said the destination address resolves to, even if it's
23451 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
23454 - Fix a DOS opportunity during the voting signature collection process
23455 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
23457 o Major bugfixes (hidden services):
23458 - When fetching v0 and v2 rendezvous service descriptors in parallel,
23459 we were failing the whole hidden service request when the v0
23460 descriptor fetch fails, even if the v2 fetch is still pending and
23461 might succeed. Similarly, if the last v2 fetch fails, we were
23462 failing the whole hidden service request even if a v0 fetch is
23463 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
23464 - When extending a circuit to a hidden service directory to upload a
23465 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
23466 requests failed, because the router descriptor has not been
23467 downloaded yet. In these cases, do not attempt to upload the
23468 rendezvous descriptor, but wait until the router descriptor is
23469 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
23470 descriptor from a hidden service directory for which the router
23471 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
23475 - Fix several infrequent memory leaks spotted by Coverity.
23476 - When testing for libevent functions, set the LDFLAGS variable
23477 correctly. Found by Riastradh.
23478 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
23479 bootstrapping with tunneled directory connections. Bugfix on
23480 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
23481 - When asked to connect to A.B.exit:80, if we don't know the IP for A
23482 and we know that server B rejects most-but-not all connections to
23483 port 80, we would previously reject the connection. Now, we assume
23484 the user knows what they were asking for. Fixes bug 752. Bugfix
23485 on 0.0.9rc5. Diagnosed by BarkerJr.
23486 - If we overrun our per-second write limits a little, count this as
23487 having used up our write allocation for the second, and choke
23488 outgoing directory writes. Previously, we had only counted this when
23489 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
23490 Bugfix on 0.2.0.x (??).
23491 - Remove the old v2 directory authority 'lefkada' from the default
23492 list. It has been gone for many months.
23493 - Stop doing unaligned memory access that generated bus errors on
23494 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
23495 - Make USR2 log-level switch take effect immediately. Bugfix on
23498 o Minor bugfixes (controller):
23499 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
23500 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
23503 Changes in version 0.2.1.7-alpha - 2008-11-08
23504 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
23505 packages (and maybe other packages) noticed by Theo de Raadt, fixes
23506 a smaller security flaw that might allow an attacker to access local
23507 services, adds better defense against DNS poisoning attacks on exit
23508 relays, further improves hidden service performance, and fixes a
23509 variety of other issues.
23512 - The "ClientDNSRejectInternalAddresses" config option wasn't being
23513 consistently obeyed: if an exit relay refuses a stream because its
23514 exit policy doesn't allow it, we would remember what IP address
23515 the relay said the destination address resolves to, even if it's
23516 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
23517 - The "User" and "Group" config options did not clear the
23518 supplementary group entries for the Tor process. The "User" option
23519 is now more robust, and we now set the groups to the specified
23520 user's primary group. The "Group" option is now ignored. For more
23521 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
23522 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
23523 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
23524 - Do not use or believe expired v3 authority certificates. Patch
23525 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
23528 - Now NodeFamily and MyFamily config options allow spaces in
23529 identity fingerprints, so it's easier to paste them in.
23530 Suggested by Lucky Green.
23531 - Implement the 0x20 hack to better resist DNS poisoning: set the
23532 case on outgoing DNS requests randomly, and reject responses that do
23533 not match the case correctly. This logic can be disabled with the
23534 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
23535 of servers that do not reliably preserve case in replies. See
23536 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
23538 - Preserve case in replies to DNSPort requests in order to support
23539 the 0x20 hack for resisting DNS poisoning attacks.
23541 o Hidden service performance improvements:
23542 - When the client launches an introduction circuit, retry with a
23543 new circuit after 30 seconds rather than 60 seconds.
23544 - Launch a second client-side introduction circuit in parallel
23545 after a delay of 15 seconds (based on work by Christian Wilms).
23546 - Hidden services start out building five intro circuits rather
23547 than three, and when the first three finish they publish a service
23548 descriptor using those. Now we publish our service descriptor much
23549 faster after restart.
23552 - Minor fix in the warning messages when you're having problems
23553 bootstrapping; also, be more forgiving of bootstrap problems when
23554 we're still making incremental progress on a given bootstrap phase.
23555 - When we're choosing an exit node for a circuit, and we have
23556 no pending streams, choose a good general exit rather than one that
23557 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
23558 - Send a valid END cell back when a client tries to connect to a
23559 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
23560 840. Patch from rovv.
23561 - If a broken client asks a non-exit router to connect somewhere,
23562 do not even do the DNS lookup before rejecting the connection.
23563 Fixes another case of bug 619. Patch from rovv.
23564 - Fix another case of assuming, when a specific exit is requested,
23565 that we know more than the user about what hosts it allows.
23566 Fixes another case of bug 752. Patch from rovv.
23567 - Check which hops rendezvous stream cells are associated with to
23568 prevent possible guess-the-streamid injection attacks from
23569 intermediate hops. Fixes another case of bug 446. Based on patch
23571 - Avoid using a negative right-shift when comparing 32-bit
23572 addresses. Possible fix for bug 845 and bug 811.
23573 - Make the assert_circuit_ok() function work correctly on circuits that
23574 have already been marked for close.
23575 - Fix read-off-the-end-of-string error in unit tests when decoding
23576 introduction points.
23577 - Fix uninitialized size field for memory area allocation: may improve
23578 memory performance during directory parsing.
23579 - Treat duplicate certificate fetches as failures, so that we do
23580 not try to re-fetch an expired certificate over and over and over.
23581 - Do not say we're fetching a certificate when we'll in fact skip it
23582 because of a pending download.
23585 Changes in version 0.2.1.6-alpha - 2008-09-30
23586 Tor 0.2.1.6-alpha further improves performance and robustness of
23587 hidden services, starts work on supporting per-country relay selection,
23588 and fixes a variety of smaller issues.
23591 - Implement proposal 121: make it possible to build hidden services
23592 that only certain clients are allowed to connect to. This is
23593 enforced at several points, so that unauthorized clients are unable
23594 to send INTRODUCE cells to the service, or even (depending on the
23595 type of authentication) to learn introduction points. This feature
23596 raises the bar for certain kinds of active attacks against hidden
23597 services. Code by Karsten Loesing.
23598 - Relays now store and serve v2 hidden service descriptors by default,
23599 i.e., the new default value for HidServDirectoryV2 is 1. This is
23600 the last step in proposal 114, which aims to make hidden service
23601 lookups more reliable.
23602 - Start work to allow node restrictions to include country codes. The
23603 syntax to exclude nodes in a country with country code XX is
23604 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
23605 refinement to decide what config options should take priority if
23606 you ask to both use a particular node and exclude it.
23607 - Allow ExitNodes list to include IP ranges and country codes, just
23608 like the Exclude*Nodes lists. Patch from Robert Hogan.
23611 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
23612 Tor to fail to start if you had it configured to use a bridge
23613 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
23614 - When extending a circuit to a hidden service directory to upload a
23615 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
23616 requests failed, because the router descriptor had not been
23617 downloaded yet. In these cases, we now wait until the router
23618 descriptor is downloaded, and then retry. Likewise, clients
23619 now skip over a hidden service directory if they don't yet have
23620 its router descriptor, rather than futilely requesting it and
23621 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
23623 - When fetching v0 and v2 rendezvous service descriptors in parallel,
23624 we were failing the whole hidden service request when the v0
23625 descriptor fetch fails, even if the v2 fetch is still pending and
23626 might succeed. Similarly, if the last v2 fetch fails, we were
23627 failing the whole hidden service request even if a v0 fetch is
23628 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
23629 - DNS replies need to have names matching their requests, but
23630 these names should be in the questions section, not necessarily
23631 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
23634 - Update to the "September 1 2008" ip-to-country file.
23635 - Allow ports 465 and 587 in the default exit policy again. We had
23636 rejected them in 0.1.0.15, because back in 2005 they were commonly
23637 misconfigured and ended up as spam targets. We hear they are better
23638 locked down these days.
23639 - Use a lockfile to make sure that two Tor processes are not
23640 simultaneously running with the same datadir.
23641 - Serve the latest v3 networkstatus consensus via the control
23642 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
23643 - Better logging about stability/reliability calculations on directory
23645 - Drop the requirement to have an open dir port for storing and
23646 serving v2 hidden service descriptors.
23647 - Directory authorities now serve a /tor/dbg-stability.txt URL to
23648 help debug WFU and MTBF calculations.
23649 - Implement most of Proposal 152: allow specialized servers to permit
23650 single-hop circuits, and clients to use those servers to build
23651 single-hop circuits when using a specialized controller. Patch
23652 from Josh Albrecht. Resolves feature request 768.
23653 - Add a -p option to tor-resolve for specifying the SOCKS port: some
23654 people find host:port too confusing.
23655 - Make TrackHostExit mappings expire a while after their last use, not
23656 after their creation. Patch from Robert Hogan.
23657 - Provide circuit purposes along with circuit events to the controller.
23660 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
23662 - Fixed some memory leaks -- some quite frequent, some almost
23663 impossible to trigger -- based on results from Coverity.
23664 - When testing for libevent functions, set the LDFLAGS variable
23665 correctly. Found by Riastradh.
23666 - Fix an assertion bug in parsing policy-related options; possible fix
23668 - Catch and report a few more bootstrapping failure cases when Tor
23669 fails to establish a TCP connection. Cleanup on 0.2.1.x.
23670 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
23671 bootstrapping with tunneled directory connections. Bugfix on
23672 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
23673 - When asked to connect to A.B.exit:80, if we don't know the IP for A
23674 and we know that server B rejects most-but-not all connections to
23675 port 80, we would previously reject the connection. Now, we assume
23676 the user knows what they were asking for. Fixes bug 752. Bugfix
23677 on 0.0.9rc5. Diagnosed by BarkerJr.
23678 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
23679 service directories if they have no advertised dir port. Bugfix
23681 - If we overrun our per-second write limits a little, count this as
23682 having used up our write allocation for the second, and choke
23683 outgoing directory writes. Previously, we had only counted this when
23684 we had met our limits precisely. Fixes bug 824. Patch by rovv.
23685 Bugfix on 0.2.0.x (??).
23686 - Avoid a "0 divided by 0" calculation when calculating router uptime
23687 at directory authorities. Bugfix on 0.2.0.8-alpha.
23688 - Make DNS resolved controller events into "CLOSED", not
23689 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
23691 - Fix a bug where an unreachable relay would establish enough
23692 reachability testing circuits to do a bandwidth test -- if
23693 we already have a connection to the middle hop of the testing
23694 circuit, then it could establish the last hop by using the existing
23695 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
23696 circuits no longer use entry guards in 0.2.1.3-alpha.
23697 - If we have correct permissions on $datadir, we complain to stdout
23698 and fail to start. But dangerous permissions on
23699 $datadir/cached-status/ would cause us to open a log and complain
23700 there. Now complain to stdout and fail to start in both cases. Fixes
23701 bug 820, reported by seeess.
23702 - Remove the old v2 directory authority 'lefkada' from the default
23703 list. It has been gone for many months.
23705 o Code simplifications and refactoring:
23706 - Revise the connection_new functions so that a more typesafe variant
23707 exists. This will work better with Coverity, and let us find any
23708 actual mistakes we're making here.
23709 - Refactor unit testing logic so that dmalloc can be used sensibly
23710 with unit tests to check for memory leaks.
23711 - Move all hidden-service related fields from connection and circuit
23712 structure to substructures: this way they won't eat so much memory.
23715 Changes in version 0.2.0.31 - 2008-09-03
23716 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
23717 a big bug we're seeing where in rare cases traffic from one Tor stream
23718 gets mixed into another stream, and fixes a variety of smaller issues.
23721 - Make sure that two circuits can never exist on the same connection
23722 with the same circuit ID, even if one is marked for close. This
23723 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
23724 - Relays now reject risky extend cells: if the extend cell includes
23725 a digest of all zeroes, or asks to extend back to the relay that
23726 sent the extend cell, tear down the circuit. Ideas suggested
23728 - If not enough of our entry guards are available so we add a new
23729 one, we might use the new one even if it overlapped with the
23730 current circuit's exit relay (or its family). Anonymity bugfix
23731 pointed out by rovv.
23734 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
23735 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
23736 - Correctly detect the presence of the linux/netfilter_ipv4.h header
23737 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
23738 - Pick size of default geoip filename string correctly on windows.
23739 Fixes bug 806. Bugfix on 0.2.0.30.
23740 - Make the autoconf script accept the obsolete --with-ssl-dir
23741 option as an alias for the actually-working --with-openssl-dir
23742 option. Fix the help documentation to recommend --with-openssl-dir.
23743 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
23744 - When using the TransPort option on OpenBSD, and using the User
23745 option to change UID and drop privileges, make sure to open
23746 /dev/pf before dropping privileges. Fixes bug 782. Patch from
23747 Christopher Davis. Bugfix on 0.1.2.1-alpha.
23748 - Try to attach connections immediately upon receiving a RENDEZVOUS2
23749 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
23750 on the client side when connecting to a hidden service. Bugfix
23751 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
23752 - When closing an application-side connection because its circuit is
23753 getting torn down, generate the stream event correctly. Bugfix on
23754 0.1.2.x. Anonymous patch.
23757 Changes in version 0.2.1.5-alpha - 2008-08-31
23758 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
23759 in a lot of the infrastructure for adding authorization to hidden
23760 services, lays the groundwork for having clients read their load
23761 balancing information out of the networkstatus consensus rather than
23762 the individual router descriptors, addresses two potential anonymity
23763 issues, and fixes a variety of smaller issues.
23766 - Convert many internal address representations to optionally hold
23768 - Generate and accept IPv6 addresses in many protocol elements.
23769 - Make resolver code handle nameservers located at ipv6 addresses.
23770 - Begin implementation of proposal 121 ("Client authorization for
23771 hidden services"): configure hidden services with client
23772 authorization, publish descriptors for them, and configure
23773 authorization data for hidden services at clients. The next
23774 step is to actually access hidden services that perform client
23776 - More progress toward proposal 141: Network status consensus
23777 documents and votes now contain bandwidth information for each
23778 router and a summary of that router's exit policy. Eventually this
23779 will be used by clients so that they do not have to download every
23780 known descriptor before building circuits.
23782 o Major bugfixes (on 0.2.0.x and before):
23783 - When sending CREATED cells back for a given circuit, use a 64-bit
23784 connection ID to find the right connection, rather than an addr:port
23785 combination. Now that we can have multiple OR connections between
23786 the same ORs, it is no longer possible to use addr:port to uniquely
23787 identify a connection.
23788 - Relays now reject risky extend cells: if the extend cell includes
23789 a digest of all zeroes, or asks to extend back to the relay that
23790 sent the extend cell, tear down the circuit. Ideas suggested
23792 - If not enough of our entry guards are available so we add a new
23793 one, we might use the new one even if it overlapped with the
23794 current circuit's exit relay (or its family). Anonymity bugfix
23795 pointed out by rovv.
23798 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
23799 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
23800 - When using the TransPort option on OpenBSD, and using the User
23801 option to change UID and drop privileges, make sure to open /dev/pf
23802 before dropping privileges. Fixes bug 782. Patch from Christopher
23803 Davis. Bugfix on 0.1.2.1-alpha.
23804 - Correctly detect the presence of the linux/netfilter_ipv4.h header
23805 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
23806 - Add a missing safe_str() call for a debug log message.
23807 - Use 64 bits instead of 32 bits for connection identifiers used with
23808 the controller protocol, to greatly reduce risk of identifier reuse.
23809 - Make the autoconf script accept the obsolete --with-ssl-dir
23810 option as an alias for the actually-working --with-openssl-dir
23811 option. Fix the help documentation to recommend --with-openssl-dir.
23812 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
23815 - Rate-limit too-many-sockets messages: when they happen, they happen
23816 a lot. Resolves bug 748.
23817 - Resist DNS poisoning a little better by making sure that names in
23818 answer sections match.
23819 - Print the SOCKS5 error message string as well as the error code
23820 when a tor-resolve request fails. Patch from Jacob.
23823 Changes in version 0.2.1.4-alpha - 2008-08-04
23824 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
23827 - The address part of exit policies was not correctly written
23828 to router descriptors. This generated router descriptors that failed
23829 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
23831 - Tor triggered a false assert when extending a circuit to a relay
23832 but we already have a connection open to that relay. Noticed by
23833 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
23836 - Fix a hidden service logging bug: in some edge cases, the router
23837 descriptor of a previously picked introduction point becomes
23838 obsolete and we need to give up on it rather than continually
23839 complaining that it has become obsolete. Observed by xiando. Bugfix
23842 o Removed features:
23843 - Take out the TestVia config option, since it was a workaround for
23844 a bug that was fixed in Tor 0.1.1.21.
23847 Changes in version 0.2.1.3-alpha - 2008-08-03
23848 Tor 0.2.1.3-alpha implements most of the pieces to prevent
23849 infinite-length circuit attacks (see proposal 110); fixes a bug that
23850 might cause exit relays to corrupt streams they send back; allows
23851 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
23852 ExcludeExitNodes config options; and fixes a big pile of bugs.
23854 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
23855 - Send a bootstrap problem "warn" event on the first problem if the
23856 reason is NO_ROUTE (that is, our network is down).
23859 - Implement most of proposal 110: The first K cells to be sent
23860 along a circuit are marked as special "early" cells; only K "early"
23861 cells will be allowed. Once this code is universal, we can block
23862 certain kinds of DOS attack by requiring that EXTEND commands must
23863 be sent using an "early" cell.
23866 - Try to attach connections immediately upon receiving a RENDEZVOUS2
23867 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
23868 on the client side when connecting to a hidden service. Bugfix
23869 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
23870 - Ensure that two circuits can never exist on the same connection
23871 with the same circuit ID, even if one is marked for close. This
23872 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
23875 - When relays do their initial bandwidth measurement, don't limit
23876 to just our entry guards for the test circuits. Otherwise we tend
23877 to have multiple test circuits going through a single entry guard,
23878 which makes our bandwidth test less accurate. Fixes part of bug 654;
23879 patch contributed by Josh Albrecht.
23880 - Add an ExcludeExitNodes option so users can list a set of nodes
23881 that should be be excluded from the exit node position, but
23882 allowed elsewhere. Implements proposal 151.
23883 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
23884 ExcludeNodes and ExcludeExitNodes lists.
23885 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
23886 be more efficient. Formerly it was quadratic in the number of
23887 servers; now it should be linear. Fixes bug 509.
23888 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
23889 and n_conn_id_digest fields into a separate structure that's
23890 only needed when the circuit has not yet attached to an n_conn.
23893 - Change the contrib/tor.logrotate script so it makes the new
23894 logs as "_tor:_tor" rather than the default, which is generally
23895 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
23896 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
23897 warnings (occasionally), but it can also cause the compiler to
23898 eliminate error-checking code. Suggested by Peter Gutmann.
23899 - When a hidden service is giving up on an introduction point candidate
23900 that was not included in the last published rendezvous descriptor,
23901 don't reschedule publication of the next descriptor. Fixes bug 763.
23903 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
23904 HiddenServiceExcludeNodes as obsolete: they never worked properly,
23905 and nobody claims to be using them. Fixes bug 754. Bugfix on
23906 0.1.0.1-rc. Patch from Christian Wilms.
23907 - Fix a small alignment and memory-wasting bug on buffer chunks.
23910 o Minor bugfixes (controller):
23911 - When closing an application-side connection because its circuit
23912 is getting torn down, generate the stream event correctly.
23913 Bugfix on 0.1.2.x. Anonymous patch.
23915 o Removed features:
23916 - Remove all backward-compatibility code to support relays running
23917 versions of Tor so old that they no longer work at all on the
23921 Changes in version 0.2.0.30 - 2008-07-15
23923 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
23924 warnings (occasionally), but it can also cause the compiler to
23925 eliminate error-checking code. Suggested by Peter Gutmann.
23928 Changes in version 0.2.0.29-rc - 2008-07-08
23929 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
23930 hidden-service performance bugs, and fixes a bunch of smaller bugs.
23933 - If you have more than one bridge but don't know their keys,
23934 you would only launch a request for the descriptor of the first one
23935 on your list. (Tor considered launching requests for the others, but
23936 found that it already had a connection on the way for $0000...0000
23937 so it didn't open another.) Bugfix on 0.2.0.x.
23938 - If you have more than one bridge but don't know their keys, and the
23939 connection to one of the bridges failed, you would cancel all
23940 pending bridge connections. (After all, they all have the same
23941 digest.) Bugfix on 0.2.0.x.
23942 - When a hidden service was trying to establish an introduction point,
23943 and Tor had built circuits preemptively for such purposes, we
23944 were ignoring all the preemptive circuits and launching a new one
23945 instead. Bugfix on 0.2.0.14-alpha.
23946 - When a hidden service was trying to establish an introduction point,
23947 and Tor *did* manage to reuse one of the preemptively built
23948 circuits, it didn't correctly remember which one it used,
23949 so it asked for another one soon after, until there were no
23950 more preemptive circuits, at which point it launched one from
23951 scratch. Bugfix on 0.0.9.x.
23952 - Make directory servers include the X-Your-Address-Is: http header in
23953 their responses even for begin_dir conns. Now clients who only
23954 ever use begin_dir connections still have a way to learn their IP
23955 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
23958 - Fix a macro/CPP interaction that was confusing some compilers:
23959 some GCCs don't like #if/#endif pairs inside macro arguments.
23961 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
23962 Fixes bug 704; fix from Steven Murdoch.
23963 - When opening /dev/null in finish_daemonize(), do not pass the
23964 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
23965 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
23966 - Correctly detect transparent proxy support on Linux hosts that
23967 require in.h to be included before netfilter_ipv4.h. Patch
23969 - Disallow session resumption attempts during the renegotiation
23970 stage of the v2 handshake protocol. Clients should never be trying
23971 session resumption at this point, but apparently some did, in
23972 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
23973 found by Geoff Goodell.
23976 Changes in version 0.2.1.2-alpha - 2008-06-20
23977 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
23978 make it easier to set up your own private Tor network; fixes several
23979 big bugs with using more than one bridge relay; fixes a big bug with
23980 offering hidden services quickly after Tor starts; and uses a better
23981 API for reporting potential bootstrapping problems to the controller.
23984 - New TestingTorNetwork config option to allow adjustment of
23985 previously constant values that, while reasonable, could slow
23986 bootstrapping. Implements proposal 135. Patch from Karsten.
23989 - If you have more than one bridge but don't know their digests,
23990 you would only learn a request for the descriptor of the first one
23991 on your list. (Tor considered launching requests for the others, but
23992 found that it already had a connection on the way for $0000...0000
23993 so it didn't open another.) Bugfix on 0.2.0.x.
23994 - If you have more than one bridge but don't know their digests,
23995 and the connection to one of the bridges failed, you would cancel
23996 all pending bridge connections. (After all, they all have the
23997 same digest.) Bugfix on 0.2.0.x.
23998 - When establishing a hidden service, introduction points that
23999 originate from cannibalized circuits are completely ignored and not
24000 included in rendezvous service descriptors. This might be another
24001 reason for delay in making a hidden service available. Bugfix
24002 from long ago (0.0.9.x?)
24005 - Allow OpenSSL to use dynamic locks if it wants.
24006 - When building a consensus, do not include routers that are down.
24007 This will cut down 30% to 40% on consensus size. Implements
24009 - In directory authorities' approved-routers files, allow
24010 fingerprints with or without space.
24011 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
24012 controller can query our current bootstrap state in case it attaches
24013 partway through and wants to catch up.
24014 - Send an initial "Starting" bootstrap status event, so we have a
24015 state to start out in.
24018 - Asking for a conditional consensus at .../consensus/<fingerprints>
24019 would crash a dirserver if it did not already have a
24020 consensus. Bugfix on 0.2.1.1-alpha.
24021 - Clean up some macro/CPP interactions: some GCC versions don't like
24022 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
24025 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
24026 - Directory authorities shouldn't complain about bootstrapping
24027 problems just because they do a lot of reachability testing and
24028 some of the connection attempts fail.
24029 - Start sending "count" and "recommendation" key/value pairs in
24030 bootstrap problem status events, so the controller can hear about
24031 problems even before Tor decides they're worth reporting for sure.
24032 - If you're using bridges, generate "bootstrap problem" warnings
24033 as soon as you run out of working bridges, rather than waiting
24034 for ten failures -- which will never happen if you have less than
24036 - If we close our OR connection because there's been a circuit
24037 pending on it for too long, we were telling our bootstrap status
24038 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
24041 Changes in version 0.2.1.1-alpha - 2008-06-13
24042 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
24043 were making the Tor process bloat especially on Linux; makes our TLS
24044 handshake blend in better; sends "bootstrap phase" status events to
24045 the controller, so it can keep the user informed of progress (and
24046 problems) fetching directory information and establishing circuits;
24047 and adds a variety of smaller features.
24050 - More work on making our TLS handshake blend in: modify the list
24051 of ciphers advertised by OpenSSL in client mode to even more
24052 closely resemble a common web browser. We cheat a little so that
24053 we can advertise ciphers that the locally installed OpenSSL doesn't
24055 - Start sending "bootstrap phase" status events to the controller,
24056 so it can keep the user informed of progress fetching directory
24057 information and establishing circuits. Also inform the controller
24058 if we think we're stuck at a particular bootstrap phase. Implements
24060 - Resume using OpenSSL's RAND_poll() for better (and more portable)
24061 cross-platform entropy collection again. We used to use it, then
24062 stopped using it because of a bug that could crash systems that
24063 called RAND_poll when they had a lot of fds open. It looks like the
24064 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
24065 at startup, and to call RAND_poll() when we reseed later only if
24066 we have a non-buggy OpenSSL version.
24069 - When we choose to abandon a new entry guard because we think our
24070 older ones might be better, close any circuits pending on that
24071 new entry guard connection. This fix should make us recover much
24072 faster when our network is down and then comes back. Bugfix on
24073 0.1.2.8-beta; found by lodger.
24075 o Memory fixes and improvements:
24076 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
24077 to avoid unused RAM in buffer chunks and memory pools.
24078 - Speed up parsing and cut down on memory fragmentation by using
24079 stack-style allocations for parsing directory objects. Previously,
24080 this accounted for over 40% of allocations from within Tor's code
24081 on a typical directory cache.
24082 - Use a Bloom filter rather than a digest-based set to track which
24083 descriptors we need to keep around when we're cleaning out old
24084 router descriptors. This speeds up the computation significantly,
24085 and may reduce fragmentation.
24086 - Reduce the default smartlist size from 32 to 16; it turns out that
24087 most smartlists hold around 8-12 elements tops.
24088 - Make dumpstats() log the fullness and size of openssl-internal
24090 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
24091 patch to their OpenSSL, turn it on to save memory on servers. This
24092 patch will (with any luck) get included in a mainline distribution
24094 - Never use OpenSSL compression: it wastes RAM and CPU trying to
24095 compress cells, which are basically all encrypted, compressed,
24099 - Stop reloading the router list from disk for no reason when we
24100 run out of reachable directory mirrors. Once upon a time reloading
24101 it would set the 'is_running' flag back to 1 for them. It hasn't
24102 done that for a long time.
24103 - In very rare situations new hidden service descriptors were
24104 published earlier than 30 seconds after the last change to the
24105 service. (We currently think that a hidden service descriptor
24106 that's been stable for 30 seconds is worth publishing.)
24109 - Allow separate log levels to be configured for different logging
24110 domains. For example, this allows one to log all notices, warnings,
24111 or errors, plus all memory management messages of level debug or
24112 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
24113 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
24114 and stop using a warning that had become unfixably verbose under
24116 - New --hush command-line option similar to --quiet. While --quiet
24117 disables all logging to the console on startup, --hush limits the
24118 output to messages of warning and error severity.
24119 - Servers support a new URL scheme for consensus downloads that
24120 allows the client to specify which authorities are trusted.
24121 The server then only sends the consensus if the client will trust
24122 it. Otherwise a 404 error is sent back. Clients use this
24123 new scheme when the server supports it (meaning it's running
24124 0.2.1.1-alpha or later). Implements proposal 134.
24125 - New configure/torrc options (--enable-geoip-stats,
24126 DirRecordUsageByCountry) to record how many IPs we've served
24127 directory info to in each country code, how many status documents
24128 total we've sent to each country code, and what share of the total
24129 directory requests we should expect to see.
24130 - Use the TLS1 hostname extension to more closely resemble browser
24132 - Lots of new unit tests.
24133 - Add a macro to implement the common pattern of iterating through
24134 two parallel lists in lockstep.
24137 Changes in version 0.2.0.28-rc - 2008-06-13
24138 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
24139 performance bug, and fixes a bunch of smaller bugs.
24142 - Fix a bug where, when we were choosing the 'end stream reason' to
24143 put in our relay end cell that we send to the exit relay, Tor
24144 clients on Windows were sometimes sending the wrong 'reason'. The
24145 anonymity problem is that exit relays may be able to guess whether
24146 the client is running Windows, thus helping partition the anonymity
24147 set. Down the road we should stop sending reasons to exit relays,
24148 or otherwise prevent future versions of this bug.
24151 - While setting up a hidden service, some valid introduction circuits
24152 were overlooked and abandoned. This might be the reason for
24153 the long delay in making a hidden service available. Bugfix on
24157 - Update to the "June 9 2008" ip-to-country file.
24158 - Run 'make test' as part of 'make dist', so we stop releasing so
24159 many development snapshots that fail their unit tests.
24162 - When we're checking if we have enough dir info for each relay
24163 to begin establishing circuits, make sure that we actually have
24164 the descriptor listed in the consensus, not just any descriptor.
24166 - Bridge relays no longer print "xx=0" in their extrainfo document
24167 for every single country code in the geoip db. Bugfix on
24169 - Only warn when we fail to load the geoip file if we were planning to
24170 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
24171 - If we change our MaxAdvertisedBandwidth and then reload torrc,
24172 Tor won't realize it should publish a new relay descriptor. Fixes
24173 bug 688, reported by mfr. Bugfix on 0.1.2.x.
24174 - When we haven't had any application requests lately, don't bother
24175 logging that we have expired a bunch of descriptors. Bugfix
24177 - Make relay cells written on a connection count as non-padding when
24178 tracking how long a connection has been in use. Bugfix on
24179 0.2.0.1-alpha. Spotted by lodger.
24180 - Fix unit tests in 0.2.0.27-rc.
24181 - Fix compile on Windows.
24184 Changes in version 0.2.0.27-rc - 2008-06-03
24185 Tor 0.2.0.27-rc adds a few features we left out of the earlier
24186 release candidates. In particular, we now include an IP-to-country
24187 GeoIP database, so controllers can easily look up what country a
24188 given relay is in, and so bridge relays can give us some sanitized
24189 summaries about which countries are making use of bridges. (See proposal
24190 126-geoip-fetching.txt for details.)
24193 - Include an IP-to-country GeoIP file in the tarball, so bridge
24194 relays can report sanitized summaries of the usage they're seeing.
24197 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
24198 Robert Hogan. Fixes the first part of bug 681.
24199 - Make bridge authorities never serve extrainfo docs.
24200 - Add support to detect Libevent versions in the 1.4.x series
24202 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
24203 - Include a new contrib/tor-exit-notice.html file that exit relay
24204 operators can put on their website to help reduce abuse queries.
24207 - When tunneling an encrypted directory connection, and its first
24208 circuit fails, do not leave it unattached and ask the controller
24209 to deal. Fixes the second part of bug 681.
24210 - Make bridge authorities correctly expire old extrainfo documents
24214 Changes in version 0.2.0.26-rc - 2008-05-13
24215 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
24216 in Debian's OpenSSL packages. All users running any 0.2.0.x version
24217 should upgrade, whether they're running Debian or not.
24219 o Major security fixes:
24220 - Use new V3 directory authority keys on the tor26, gabelmoo, and
24221 moria1 V3 directory authorities. The old keys were generated with
24222 a vulnerable version of Debian's OpenSSL package, and must be
24223 considered compromised. Other authorities' keys were not generated
24224 with an affected version of OpenSSL.
24227 - List authority signatures as "unrecognized" based on DirServer
24228 lines, not on cert cache. Bugfix on 0.2.0.x.
24231 - Add a new V3AuthUseLegacyKey option to make it easier for
24232 authorities to change their identity keys if they have to.
24235 Changes in version 0.2.0.25-rc - 2008-04-23
24236 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
24239 - Remember to initialize threading before initializing logging.
24240 Otherwise, many BSD-family implementations will crash hard on
24241 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
24244 - Authorities correctly free policies on bad servers on
24245 exit. Fixes bug 672. Bugfix on 0.2.0.x.
24248 Changes in version 0.2.0.24-rc - 2008-04-22
24249 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
24250 v3 directory authority, makes relays with dynamic IP addresses and no
24251 DirPort notice more quickly when their IP address changes, fixes a few
24252 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
24254 o New directory authorities:
24255 - Take lefkada out of the list of v3 directory authorities, since
24256 it has been down for months.
24257 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
24261 - Detect address changes more quickly on non-directory mirror
24262 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
24264 o Minor features (security):
24265 - Reject requests for reverse-dns lookup of names that are in
24266 a private address space. Patch from lodger.
24267 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
24270 o Minor bugfixes (crashes):
24271 - Avoid a rare assert that can trigger when Tor doesn't have much
24272 directory information yet and it tries to fetch a v2 hidden
24273 service descriptor. Fixes bug 651, reported by nwf.
24274 - Initialize log mutex before initializing dmalloc. Otherwise,
24275 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
24276 - Use recursive pthread mutexes in order to avoid deadlock when
24277 logging debug-level messages to a controller. Bug spotted by nwf,
24278 bugfix on 0.2.0.16-alpha.
24280 o Minor bugfixes (resource management):
24281 - Keep address policies from leaking memory: start their refcount
24282 at 1, not 2. Bugfix on 0.2.0.16-alpha.
24283 - Free authority certificates on exit, so they don't look like memory
24284 leaks. Bugfix on 0.2.0.19-alpha.
24285 - Free static hashtables for policy maps and for TLS connections on
24286 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
24287 - Avoid allocating extra space when computing consensuses on 64-bit
24288 platforms. Bug spotted by aakova.
24290 o Minor bugfixes (misc):
24291 - Do not read the configuration file when we've only been told to
24292 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
24293 based on patch from Sebastian Hahn.
24294 - Exit relays that are used as a client can now reach themselves
24295 using the .exit notation, rather than just launching an infinite
24296 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
24297 - When attempting to open a logfile fails, tell us why.
24298 - Fix a dumb bug that was preventing us from knowing that we should
24299 preemptively build circuits to handle expected directory requests.
24300 Fixes bug 660. Bugfix on 0.1.2.x.
24301 - Warn less verbosely about clock skew from netinfo cells from
24302 untrusted sources. Fixes bug 663.
24303 - Make controller stream events for DNS requests more consistent,
24304 by adding "new stream" events for DNS requests, and removing
24305 spurious "stream closed" events" for cached reverse resolves.
24306 Patch from mwenge. Fixes bug 646.
24307 - Correctly notify one-hop connections when a circuit build has
24308 failed. Possible fix for bug 669. Found by lodger.
24311 Changes in version 0.2.0.23-rc - 2008-03-24
24312 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
24313 makes bootstrapping faster if the first directory mirror you contact
24314 is down. The bundles also include the new Vidalia 0.1.2 release.
24317 - When a tunneled directory request is made to a directory server
24318 that's down, notice after 30 seconds rather than 120 seconds. Also,
24319 fail any begindir streams that are pending on it, so they can
24320 retry elsewhere. This was causing multi-minute delays on bootstrap.
24323 Changes in version 0.2.0.22-rc - 2008-03-18
24324 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
24325 enables encrypted directory connections by default for non-relays, fixes
24326 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
24327 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
24330 - Enable encrypted directory connections by default for non-relays,
24331 so censor tools that block Tor directory connections based on their
24332 plaintext patterns will no longer work. This means Tor works in
24333 certain censored countries by default again.
24336 - Make sure servers always request certificates from clients during
24337 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
24338 - Do not enter a CPU-eating loop when a connection is closed in
24339 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
24340 diagnosed by lodger; bugfix on 0.2.0.20-rc.
24341 - Fix assertion failure that could occur when a blocked circuit
24342 became unblocked, and it had pending client DNS requests. Bugfix
24343 on 0.2.0.1-alpha. Fixes bug 632.
24345 o Minor bugfixes (on 0.1.2.x):
24346 - Generate "STATUS_SERVER" events rather than misspelled
24347 "STATUS_SEVER" events. Caught by mwenge.
24348 - When counting the number of bytes written on a TLS connection,
24349 look at the BIO actually used for writing to the network, not
24350 at the BIO used (sometimes) to buffer data for the network.
24351 Looking at different BIOs could result in write counts on the
24352 order of ULONG_MAX. Fixes bug 614.
24353 - On Windows, correctly detect errors when listing the contents of
24354 a directory. Fix from lodger.
24356 o Minor bugfixes (on 0.2.0.x):
24357 - Downgrade "sslv3 alert handshake failure" message to INFO.
24358 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
24359 left BandwidthRate and BandwidthBurst at the default, we would be
24360 silently limited by those defaults. Now raise them to match the
24361 RelayBandwidth* values.
24362 - Fix the SVK version detection logic to work correctly on a branch.
24363 - Make --enable-openbsd-malloc work correctly on Linux with alpha
24364 CPUs. Fixes bug 625.
24365 - Logging functions now check that the passed severity is sane.
24366 - Use proper log levels in the testsuite call of
24367 get_interface_address6().
24368 - When using a nonstandard malloc, do not use the platform values for
24369 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
24370 - Make the openbsd malloc code use 8k pages on alpha CPUs and
24372 - Detect mismatched page sizes when using --enable-openbsd-malloc.
24373 - Avoid double-marked-for-close warning when certain kinds of invalid
24374 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
24375 for bug 617. Bugfix on 0.2.0.1-alpha.
24376 - Make sure that the "NULL-means-reject *:*" convention is followed by
24377 all the policy manipulation functions, avoiding some possible crash
24378 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
24379 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
24380 actually works, and doesn't warn about every single reverse lookup.
24381 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
24384 - Only log guard node status when guard node status has changed.
24385 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
24386 make "INFO" 75% less verbose.
24389 Changes in version 0.2.0.21-rc - 2008-03-02
24390 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
24391 makes Tor work well with Vidalia again, fixes a rare assert bug,
24392 and fixes a pair of more minor bugs. The bundles also include Vidalia
24393 0.1.0 and Torbutton 1.1.16.
24396 - The control port should declare that it requires password auth
24397 when HashedControlSessionPassword is set too. Patch from Matt Edman;
24398 bugfix on 0.2.0.20-rc. Fixes bug 615.
24399 - Downgrade assert in connection_buckets_decrement() to a log message.
24400 This may help us solve bug 614, and in any case will make its
24401 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
24402 - We were sometimes miscounting the number of bytes read from the
24403 network, causing our rate limiting to not be followed exactly.
24404 Bugfix on 0.2.0.16-alpha. Reported by lodger.
24407 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
24408 OpenSSL versions should have been working fine. Diagnosis and patch
24409 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
24410 Bugfix on 0.2.0.20-rc.
24413 Changes in version 0.2.0.20-rc - 2008-02-24
24414 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
24415 makes more progress towards normalizing Tor's TLS handshake, makes
24416 hidden services work better again, helps relays bootstrap if they don't
24417 know their IP address, adds optional support for linking in openbsd's
24418 allocator or tcmalloc, allows really fast relays to scale past 15000
24419 sockets, and fixes a bunch of minor bugs reported by Veracode.
24422 - Enable the revised TLS handshake based on the one designed by
24423 Steven Murdoch in proposal 124, as revised in proposal 130. It
24424 includes version negotiation for OR connections as described in
24425 proposal 105. The new handshake is meant to be harder for censors
24426 to fingerprint, and it adds the ability to detect certain kinds of
24427 man-in-the-middle traffic analysis attacks. The version negotiation
24428 feature will allow us to improve Tor's link protocol more safely
24430 - Choose which bridge to use proportional to its advertised bandwidth,
24431 rather than uniformly at random. This should speed up Tor for
24432 bridge users. Also do this for people who set StrictEntryNodes.
24433 - When a TrackHostExits-chosen exit fails too many times in a row,
24434 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
24437 - Resolved problems with (re-)fetching hidden service descriptors.
24438 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
24439 and 0.2.0.19-alpha.
24440 - If we only ever used Tor for hidden service lookups or posts, we
24441 would stop building circuits and start refusing connections after
24442 24 hours, since we falsely believed that Tor was dormant. Reported
24443 by nwf; bugfix on 0.1.2.x.
24444 - Servers that don't know their own IP address should go to the
24445 authorities for their first directory fetch, even if their DirPort
24446 is off or if they don't know they're reachable yet. This will help
24447 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
24448 - When counting the number of open sockets, count not only the number
24449 of sockets we have received from the socket() call, but also
24450 the number we've gotten from accept() and socketpair(). This bug
24451 made us fail to count all sockets that we were using for incoming
24452 connections. Bugfix on 0.2.0.x.
24453 - Fix code used to find strings within buffers, when those strings
24454 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
24455 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
24456 - Add a new __HashedControlSessionPassword option for controllers
24457 to use for one-off session password hashes that shouldn't get
24458 saved to disk by SAVECONF --- Vidalia users were accumulating a
24459 pile of HashedControlPassword lines in their torrc files, one for
24460 each time they had restarted Tor and then clicked Save. Make Tor
24461 automatically convert "HashedControlPassword" to this new option but
24462 only when it's given on the command line. Partial fix for bug 586.
24464 o Minor features (performance):
24465 - Tune parameters for cell pool allocation to minimize amount of
24467 - Add OpenBSD malloc code from phk as an optional malloc
24468 replacement on Linux: some glibc libraries do very poorly
24469 with Tor's memory allocation patterns. Pass
24470 --enable-openbsd-malloc to get the replacement malloc code.
24471 - Add a --with-tcmalloc option to the configure script to link
24472 against tcmalloc (if present). Does not yet search for
24473 non-system include paths.
24474 - Stop imposing an arbitrary maximum on the number of file descriptors
24475 used for busy servers. Bug reported by Olaf Selke; patch from
24478 o Minor features (other):
24479 - When SafeLogging is disabled, log addresses along with all TLS
24481 - When building with --enable-gcc-warnings, check for whether Apple's
24482 warning "-Wshorten-64-to-32" is available.
24483 - Add a --passphrase-fd argument to the tor-gencert command for
24486 o Minor bugfixes (memory leaks and code problems):
24487 - We were leaking a file descriptor if Tor started with a zero-length
24488 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
24489 - Detect size overflow in zlib code. Reported by Justin Ferguson and
24491 - We were comparing the raw BridgePassword entry with a base64'ed
24492 version of it, when handling a "/tor/networkstatus-bridges"
24493 directory request. Now compare correctly. Noticed by Veracode.
24494 - Recover from bad tracked-since value in MTBF-history file.
24495 Should fix bug 537.
24496 - Alter the code that tries to recover from unhandled write
24497 errors, to not try to flush onto a socket that's given us
24498 unhandled errors. Bugfix on 0.1.2.x.
24499 - Make Unix controlsockets work correctly on OpenBSD. Patch from
24500 tup. Bugfix on 0.2.0.3-alpha.
24502 o Minor bugfixes (other):
24503 - If we have an extra-info document for our server, always make
24504 it available on the control port, even if we haven't gotten
24505 a copy of it from an authority yet. Patch from mwenge.
24506 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
24507 - Directory mirrors no longer include a guess at the client's IP
24508 address if the connection appears to be coming from the same /24
24509 network; it was producing too many wrong guesses.
24510 - Make the new hidden service code respect the SafeLogging setting.
24511 Bugfix on 0.2.0.x. Patch from Karsten.
24512 - When starting as an authority, do not overwrite all certificates
24513 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
24514 - If we're trying to flush the last bytes on a connection (for
24515 example, when answering a directory request), reset the
24516 time-to-give-up timeout every time we manage to write something
24517 on the socket. Bugfix on 0.1.2.x.
24518 - Change the behavior of "getinfo status/good-server-descriptor"
24519 so it doesn't return failure when any authority disappears.
24520 - Even though the man page said that "TrackHostExits ." should
24521 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
24522 - Report TLS "zero return" case as a "clean close" and "IO error"
24523 as a "close". Stop calling closes "unexpected closes": existing
24524 Tors don't use SSL_close(), so having a connection close without
24525 the TLS shutdown handshake is hardly unexpected.
24526 - Send NAMESERVER_STATUS messages for a single failed nameserver
24529 o Code simplifications and refactoring:
24530 - Remove the tor_strpartition function: its logic was confused,
24531 and it was only used for one thing that could be implemented far
24535 Changes in version 0.2.0.19-alpha - 2008-02-09
24536 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
24537 handshake, makes path selection for relays more secure and IP address
24538 guessing more robust, and generally fixes a lot of bugs in preparation
24539 for calling the 0.2.0 branch stable.
24542 - Do not include recognizeable strings in the commonname part of
24543 Tor's x509 certificates.
24546 - If we're a relay, avoid picking ourselves as an introduction point,
24547 a rendezvous point, or as the final hop for internal circuits. Bug
24548 reported by taranis and lodger. Bugfix on 0.1.2.x.
24549 - Patch from "Andrew S. Lists" to catch when we contact a directory
24550 mirror at IP address X and he says we look like we're coming from
24551 IP address X. Bugfix on 0.1.2.x.
24553 o Minor features (security):
24554 - Be more paranoid about overwriting sensitive memory on free(),
24555 as a defensive programming tactic to ensure forward secrecy.
24557 o Minor features (directory authority):
24558 - Actually validate the options passed to AuthDirReject,
24559 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
24560 - Reject router descriptors with out-of-range bandwidthcapacity or
24561 bandwidthburst values.
24563 o Minor features (controller):
24564 - Reject controller commands over 1MB in length. This keeps rogue
24565 processes from running us out of memory.
24567 o Minor features (misc):
24568 - Give more descriptive well-formedness errors for out-of-range
24569 hidden service descriptor/protocol versions.
24570 - Make memory debugging information describe more about history
24571 of cell allocation, so we can help reduce our memory use.
24573 o Deprecated features (controller):
24574 - The status/version/num-versioning and status/version/num-concurring
24575 GETINFO options are no longer useful in the v3 directory protocol:
24576 treat them as deprecated, and warn when they're used.
24579 - When our consensus networkstatus has been expired for a while, stop
24580 being willing to build circuits using it. Fixes bug 401. Bugfix
24582 - Directory caches now fetch certificates from all authorities
24583 listed in a networkstatus consensus, even when they do not
24584 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
24585 - When connecting to a bridge without specifying its key, insert
24586 the connection into the identity-to-connection map as soon as
24587 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
24588 - Detect versions of OS X where malloc_good_size() is present in the
24589 library but never actually declared. Resolves bug 587. Bugfix
24591 - Stop incorrectly truncating zlib responses to directory authority
24592 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
24593 - Stop recommending that every server operator send mail to tor-ops.
24594 Resolves bug 597. Bugfix on 0.1.2.x.
24595 - Don't trigger an assert if we start a directory authority with a
24596 private IP address (like 127.0.0.1).
24597 - Avoid possible failures when generating a directory with routers
24598 with over-long versions strings, or too many flags set. Bugfix
24600 - If an attempt to launch a DNS resolve request over the control
24601 port fails because we have overrun the limit on the number of
24602 connections, tell the controller that the request has failed.
24603 - Avoid using too little bandwidth when our clock skips a few
24604 seconds. Bugfix on 0.1.2.x.
24605 - Fix shell error when warning about missing packages in configure
24606 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
24607 - Do not become confused when receiving a spurious VERSIONS-like
24608 cell from a confused v1 client. Bugfix on 0.2.0.x.
24609 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
24610 introduction points for a hidden service have failed. Patch from
24611 Karsten Loesing. Bugfix on 0.2.0.x.
24613 o Code simplifications and refactoring:
24614 - Remove some needless generality from cpuworker code, for improved
24616 - Stop overloading the circuit_t.onionskin field for both "onionskin
24617 from a CREATE cell that we are waiting for a cpuworker to be
24618 assigned" and "onionskin from an EXTEND cell that we are going to
24619 send to an OR as soon as we are connected". Might help with bug 600.
24620 - Add an in-place version of aes_crypt() so that we can avoid doing a
24621 needless memcpy() call on each cell payload.
24624 Changes in version 0.2.0.18-alpha - 2008-01-25
24625 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
24626 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
24627 that can warn or reject connections to ports generally associated with
24628 vulnerable-plaintext protocols.
24630 o New directory authorities:
24631 - Set up dannenberg (run by CCC) as the sixth v3 directory
24635 - Fix a major memory leak when attempting to use the v2 TLS
24636 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
24637 - We accidentally enabled the under-development v2 TLS handshake
24638 code, which was causing log entries like "TLS error while
24639 renegotiating handshake". Disable it again. Resolves bug 590.
24640 - We were computing the wrong Content-Length: header for directory
24641 responses that need to be compressed on the fly, causing clients
24642 asking for those items to always fail. Bugfix on 0.2.0.x; partially
24646 - Avoid going directly to the directory authorities even if you're a
24647 relay, if you haven't found yourself reachable yet or if you've
24648 decided not to advertise your dirport yet. Addresses bug 556.
24649 - If we've gone 12 hours since our last bandwidth check, and we
24650 estimate we have less than 50KB bandwidth capacity but we could
24651 handle more, do another bandwidth test.
24652 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
24653 Tor can warn and/or refuse connections to ports commonly used with
24654 vulnerable-plaintext protocols. Currently we warn on ports 23,
24655 109, 110, and 143, but we don't reject any.
24658 - When we setconf ClientOnly to 1, close any current OR and Dir
24659 listeners. Reported by mwenge.
24660 - When we get a consensus that's been signed by more people than
24661 we expect, don't log about it; it's not a big deal. Reported
24665 - Don't answer "/tor/networkstatus-bridges" directory requests if
24666 the request isn't encrypted.
24667 - Make "ClientOnly 1" config option disable directory ports too.
24668 - Patches from Karsten Loesing to make v2 hidden services more
24669 robust: work even when there aren't enough HSDir relays available;
24670 retry when a v2 rend desc fetch fails; but don't retry if we
24671 already have a usable v0 rend desc.
24674 Changes in version 0.2.0.17-alpha - 2008-01-17
24675 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
24678 - Make the tor-gencert man page get included correctly in the tarball.
24681 Changes in version 0.2.0.16-alpha - 2008-01-17
24682 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
24683 Loesing, and generally cleans up a lot of features and minor bugs.
24685 o New directory authorities:
24686 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
24689 o Major performance improvements:
24690 - Switch our old ring buffer implementation for one more like that
24691 used by free Unix kernels. The wasted space in a buffer with 1mb
24692 of data will now be more like 8k than 1mb. The new implementation
24693 also avoids realloc();realloc(); patterns that can contribute to
24694 memory fragmentation.
24697 - Configuration files now accept C-style strings as values. This
24698 helps encode characters not allowed in the current configuration
24699 file format, such as newline or #. Addresses bug 557.
24700 - Although we fixed bug 539 (where servers would send HTTP status 503
24701 responses _and_ send a body too), there are still servers out
24702 there that haven't upgraded. Therefore, make clients parse such
24703 bodies when they receive them.
24704 - When we're not serving v2 directory information, there is no reason
24705 to actually keep any around. Remove the obsolete files and directory
24706 on startup if they are very old and we aren't going to serve them.
24708 o Minor performance improvements:
24709 - Reference-count and share copies of address policy entries; only 5%
24710 of them were actually distinct.
24711 - Never walk through the list of logs if we know that no log is
24712 interested in a given message.
24715 - When an authority has not signed a consensus, do not try to
24716 download a nonexistent "certificate with key 00000000". Bugfix
24717 on 0.2.0.x. Fixes bug 569.
24718 - Fix a rare assert error when we're closing one of our threads:
24719 use a mutex to protect the list of logs, so we never write to the
24720 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
24721 bug 575, which is kind of the revenge of bug 222.
24722 - Patch from Karsten Loesing to complain less at both the client
24723 and the relay when a relay used to have the HSDir flag but doesn't
24724 anymore, and we try to upload a hidden service descriptor.
24725 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
24727 - Do not try to download missing certificates until we have tried
24728 to check our fallback consensus. Fixes bug 583.
24729 - Make bridges round reported GeoIP stats info up to the nearest
24730 estimate, not down. Now we can distinguish between "0 people from
24731 this country" and "1 person from this country".
24732 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
24733 - Avoid possible segfault if key generation fails in
24734 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
24735 - Avoid segfault in the case where a badly behaved v2 versioning
24736 directory sends a signed networkstatus with missing client-versions.
24738 - Avoid segfaults on certain complex invocations of
24739 router_get_by_hexdigest(). Bugfix on 0.1.2.
24740 - Correct bad index on array access in parse_http_time(). Bugfix
24742 - Fix possible bug in vote generation when server versions are present
24743 but client versions are not.
24744 - Fix rare bug on REDIRECTSTREAM control command when called with no
24745 port set: it could erroneously report an error when none had
24747 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
24748 compressing large objects and find ourselves with more than 4k
24749 left over. Bugfix on 0.2.0.
24750 - Fix a small memory leak when setting up a hidden service.
24751 - Fix a few memory leaks that could in theory happen under bizarre
24753 - Fix an assert if we post a general-purpose descriptor via the
24754 control port but that descriptor isn't mentioned in our current
24755 network consensus. Bug reported by Jon McLachlan; bugfix on
24758 o Minor features (controller):
24759 - Get NS events working again. Patch from tup.
24760 - The GETCONF command now escapes and quotes configuration values
24761 that don't otherwise fit into the torrc file.
24762 - The SETCONF command now handles quoted values correctly.
24764 o Minor features (directory authorities):
24765 - New configuration options to override default maximum number of
24766 servers allowed on a single IP address. This is important for
24767 running a test network on a single host.
24768 - Actually implement the -s option to tor-gencert.
24769 - Add a manual page for tor-gencert.
24771 o Minor features (bridges):
24772 - Bridge authorities no longer serve bridge descriptors over
24773 unencrypted connections.
24775 o Minor features (other):
24776 - Add hidden services and DNSPorts to the list of things that make
24777 Tor accept that it has running ports. Change starting Tor with no
24778 ports from a fatal error to a warning; we might change it back if
24779 this turns out to confuse anybody. Fixes bug 579.
24782 Changes in version 0.1.2.19 - 2008-01-17
24783 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
24784 exit policy a little bit more conservative so it's safer to run an
24785 exit relay on a home system, and fixes a variety of smaller issues.
24788 - Exit policies now reject connections that are addressed to a
24789 relay's public (external) IP address too, unless
24790 ExitPolicyRejectPrivate is turned off. We do this because too
24791 many relays are running nearby to services that trust them based
24792 on network address.
24795 - When the clock jumps forward a lot, do not allow the bandwidth
24796 buckets to become negative. Fixes bug 544.
24797 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
24798 on every successful resolve. Reported by Mike Perry.
24799 - Purge old entries from the "rephist" database and the hidden
24800 service descriptor database even when DirPort is zero.
24801 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
24802 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
24803 crashing or mis-answering these requests.
24804 - When we decide to send a 503 response to a request for servers, do
24805 not then also send the server descriptors: this defeats the whole
24806 purpose. Fixes bug 539.
24809 - Changing the ExitPolicyRejectPrivate setting should cause us to
24810 rebuild our server descriptor.
24811 - Fix handling of hex nicknames when answering controller requests for
24812 networkstatus by name, or when deciding whether to warn about
24813 unknown routers in a config option. (Patch from mwenge.)
24814 - Fix a couple of hard-to-trigger autoconf problems that could result
24815 in really weird results on platforms whose sys/types.h files define
24816 nonstandard integer types.
24817 - Don't try to create the datadir when running --verify-config or
24818 --hash-password. Resolves bug 540.
24819 - If we were having problems getting a particular descriptor from the
24820 directory caches, and then we learned about a new descriptor for
24821 that router, we weren't resetting our failure count. Reported
24823 - Although we fixed bug 539 (where servers would send HTTP status 503
24824 responses _and_ send a body too), there are still servers out there
24825 that haven't upgraded. Therefore, make clients parse such bodies
24826 when they receive them.
24827 - Run correctly on systems where rlim_t is larger than unsigned long.
24828 This includes some 64-bit systems.
24829 - Run correctly on platforms (like some versions of OS X 10.5) where
24830 the real limit for number of open files is OPEN_FILES, not rlim_max
24831 from getrlimit(RLIMIT_NOFILES).
24832 - Avoid a spurious free on base64 failure.
24833 - Avoid segfaults on certain complex invocations of
24834 router_get_by_hexdigest().
24835 - Fix rare bug on REDIRECTSTREAM control command when called with no
24836 port set: it could erroneously report an error when none had
24840 Changes in version 0.2.0.15-alpha - 2007-12-25
24841 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
24842 features added in 0.2.0.13-alpha.
24845 - Fix several remotely triggerable asserts based on DirPort requests
24846 for a v2 or v3 networkstatus object before we were prepared. This
24847 was particularly bad for 0.2.0.13 and later bridge relays, who
24848 would never have a v2 networkstatus and would thus always crash
24849 when used. Bugfixes on 0.2.0.x.
24850 - Estimate the v3 networkstatus size more accurately, rather than
24851 estimating it at zero bytes and giving it artificially high priority
24852 compared to other directory requests. Bugfix on 0.2.0.x.
24855 - Fix configure.in logic for cross-compilation.
24856 - When we load a bridge descriptor from the cache, and it was
24857 previously unreachable, mark it as retriable so we won't just
24858 ignore it. Also, try fetching a new copy immediately. Bugfixes
24860 - The bridge GeoIP stats were counting other relays, for example
24861 self-reachability and authority-reachability tests.
24864 - Support compilation to target iPhone; patch from cjacker huang.
24865 To build for iPhone, pass the --enable-iphone option to configure.
24868 Changes in version 0.2.0.14-alpha - 2007-12-23
24870 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
24871 without a datadirectory from a previous Tor install. Reported
24873 - Fix a crash when we fetch a descriptor that turns out to be
24874 unexpected (it used to be in our networkstatus when we started
24875 fetching it, but it isn't in our current networkstatus), and we
24876 aren't using bridges. Bugfix on 0.2.0.x.
24877 - Fix a crash when accessing hidden services: it would work the first
24878 time you use a given introduction point for your service, but
24879 on subsequent requests we'd be using garbage memory. Fixed by
24880 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
24881 - Fix a crash when we load a bridge descriptor from disk but we don't
24882 currently have a Bridge line for it in our torrc. Bugfix on
24886 - If bridge authorities set BridgePassword, they will serve a
24887 snapshot of known bridge routerstatuses from their DirPort to
24888 anybody who knows that password. Unset by default.
24891 - Make the unit tests build again.
24892 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
24893 - Make PublishServerDescriptor default to 1, so the default doesn't
24894 have to change as we invent new directory protocol versions.
24895 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
24896 be included unless sys/time.h is already included. Fixes
24897 bug 553. Bugfix on 0.2.0.x.
24898 - If we receive a general-purpose descriptor and then receive an
24899 identical bridge-purpose descriptor soon after, don't discard
24900 the next one as a duplicate.
24903 - If BridgeRelay is set to 1, then the default for
24904 PublishServerDescriptor is now "bridge" rather than "v2,v3".
24905 - If the user sets RelayBandwidthRate but doesn't set
24906 RelayBandwidthBurst, then make them equal rather than erroring out.
24909 Changes in version 0.2.0.13-alpha - 2007-12-21
24910 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
24911 Goodell, fixes many more bugs, and adds a lot of infrastructure for
24914 o New directory authorities:
24915 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
24919 - Only update guard status (usable / not usable) once we have
24920 enough directory information. This was causing us to always pick
24921 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
24922 causing us to discard all our guards on startup if we hadn't been
24923 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
24924 - Purge old entries from the "rephist" database and the hidden
24925 service descriptor databases even when DirPort is zero. Bugfix
24927 - We were ignoring our RelayBandwidthRate for the first 30 seconds
24928 after opening a circuit -- even a relayed circuit. Bugfix on
24930 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
24931 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
24932 crashing or mis-answering these types of requests.
24933 - Relays were publishing their server descriptor to v1 and v2
24934 directory authorities, but they didn't try publishing to v3-only
24935 authorities. Fix this; and also stop publishing to v1 authorities.
24937 - When we were reading router descriptors from cache, we were ignoring
24938 the annotations -- so for example we were reading in bridge-purpose
24939 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
24940 - When we decided to send a 503 response to a request for servers, we
24941 were then also sending the server descriptors: this defeats the
24942 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
24945 - Bridge relays now behave like clients with respect to time
24946 intervals for downloading new consensus documents -- otherwise they
24947 stand out. Bridge users now wait until the end of the interval,
24948 so their bridge relay will be sure to have a new consensus document.
24949 - Three new config options (AlternateDirAuthority,
24950 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
24951 user selectively replace the default directory authorities by type,
24952 rather than the all-or-nothing replacement that DirServer offers.
24953 - Tor can now be configured to read a GeoIP file from disk in one
24954 of two formats. This can be used by controllers to map IP addresses
24955 to countries. Eventually, it may support exit-by-country.
24956 - When possible, bridge relays remember which countries users
24957 are coming from, and report aggregate information in their
24958 extra-info documents, so that the bridge authorities can learn
24959 where Tor is blocked.
24960 - Bridge directory authorities now do reachability testing on the
24961 bridges they know. They provide router status summaries to the
24962 controller via "getinfo ns/purpose/bridge", and also dump summaries
24963 to a file periodically.
24964 - Stop fetching directory info so aggressively if your DirPort is
24965 on but your ORPort is off; stop fetching v2 dir info entirely.
24966 You can override these choices with the new FetchDirInfoEarly
24970 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
24971 consensus documents when there are too many relays at a single
24972 IP address. Now clear it in v2 network status documents too, and
24973 also clear it in routerinfo_t when the relay is no longer listed
24974 in the relevant networkstatus document.
24975 - Don't crash if we get an unexpected value for the
24976 PublishServerDescriptor config option. Reported by Matt Edman;
24977 bugfix on 0.2.0.9-alpha.
24978 - Our new v2 hidden service descriptor format allows descriptors
24979 that have no introduction points. But Tor crashed when we tried
24980 to build a descriptor with no intro points (and it would have
24981 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
24982 by Karsten Loesing.
24983 - Fix building with dmalloc 5.5.2 with glibc.
24984 - Reject uploaded descriptors and extrainfo documents if they're
24985 huge. Otherwise we'll cache them all over the network and it'll
24986 clog everything up. Reported by Aljosha Judmayer.
24987 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
24988 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
24989 - When the DANGEROUS_VERSION controller status event told us we're
24990 running an obsolete version, it used the string "OLD" to describe
24991 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
24992 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
24993 - If we can't expand our list of entry guards (e.g. because we're
24994 using bridges or we have StrictEntryNodes set), don't mark relays
24995 down when they fail a directory request. Otherwise we're too quick
24996 to mark all our entry points down. Bugfix on 0.1.2.x.
24997 - Fix handling of hex nicknames when answering controller requests for
24998 networkstatus by name, or when deciding whether to warn about unknown
24999 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
25000 - Fix a couple of hard-to-trigger autoconf problems that could result
25001 in really weird results on platforms whose sys/types.h files define
25002 nonstandard integer types. Bugfix on 0.1.2.x.
25003 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
25004 - Don't crash on name lookup when we have no current consensus. Fixes
25005 bug 538; bugfix on 0.2.0.x.
25006 - Only Tors that want to mirror the v2 directory info should
25007 create the "cached-status" directory in their datadir. (All Tors
25008 used to create it.) Bugfix on 0.2.0.9-alpha.
25009 - Directory authorities should only automatically download Extra Info
25010 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
25013 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
25014 consumers. (We already do this on HUP.)
25015 - Authorities and caches fetch the v2 networkstatus documents
25016 less often, now that v3 is encouraged.
25017 - Add a new config option BridgeRelay that specifies you want to
25018 be a bridge relay. Right now the only difference is that it makes
25019 you answer begin_dir requests, and it makes you cache dir info,
25020 even if your DirPort isn't on.
25021 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
25022 ask about source, timestamp of arrival, purpose, etc. We need
25023 something like this to help Vidalia not do GeoIP lookups on bridge
25025 - Allow multiple HashedControlPassword config lines, to support
25026 multiple controller passwords.
25027 - Authorities now decide whether they're authoritative for a given
25028 router based on the router's purpose.
25029 - New config options AuthDirBadDir and AuthDirListBadDirs for
25030 authorities to mark certain relays as "bad directories" in the
25031 networkstatus documents. Also supports the "!baddir" directive in
25032 the approved-routers file.
25035 Changes in version 0.2.0.12-alpha - 2007-11-16
25036 This twelfth development snapshot fixes some more build problems as
25037 well as a few minor bugs.
25040 - Make it build on OpenBSD again. Patch from tup.
25041 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
25042 package-building for Red Hat, OS X, etc.
25044 o Minor bugfixes (on 0.1.2.x):
25045 - Changing the ExitPolicyRejectPrivate setting should cause us to
25046 rebuild our server descriptor.
25048 o Minor bugfixes (on 0.2.0.x):
25049 - When we're lacking a consensus, don't try to perform rendezvous
25050 operations. Reported by Karsten Loesing.
25051 - Fix a small memory leak whenever we decide against using a
25052 newly picked entry guard. Reported by Mike Perry.
25053 - When authorities detected more than two relays running on the same
25054 IP address, they were clearing all the status flags but forgetting
25055 to clear the "hsdir" flag. So clients were being told that a
25056 given relay was the right choice for a v2 hsdir lookup, yet they
25057 never had its descriptor because it was marked as 'not running'
25059 - If we're trying to fetch a bridge descriptor and there's no way
25060 the bridge authority could help us (for example, we don't know
25061 a digest, or there is no bridge authority), don't be so eager to
25062 fall back to asking the bridge authority.
25063 - If we're using bridges or have strictentrynodes set, and our
25064 chosen exit is in the same family as all our bridges/entry guards,
25065 then be flexible about families.
25068 - When we negotiate a v2 link-layer connection (not yet implemented),
25069 accept RELAY_EARLY cells and turn them into RELAY cells if we've
25070 negotiated a v1 connection for their next step. Initial code for
25074 Changes in version 0.2.0.11-alpha - 2007-11-12
25075 This eleventh development snapshot fixes some build problems with
25076 the previous snapshot. It also includes a more secure-by-default exit
25077 policy for relays, fixes an enormous memory leak for exit relays, and
25078 fixes another bug where servers were falling out of the directory list.
25081 - Exit policies now reject connections that are addressed to a
25082 relay's public (external) IP address too, unless
25083 ExitPolicyRejectPrivate is turned off. We do this because too
25084 many relays are running nearby to services that trust them based
25085 on network address. Bugfix on 0.1.2.x.
25088 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
25089 on every successful resolve. Reported by Mike Perry; bugfix
25091 - On authorities, never downgrade to old router descriptors simply
25092 because they're listed in the consensus. This created a catch-22
25093 where we wouldn't list a new descriptor because there was an
25094 old one in the consensus, and we couldn't get the new one in the
25095 consensus because we wouldn't list it. Possible fix for bug 548.
25096 Also, this might cause bug 543 to appear on authorities; if so,
25097 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
25099 o Packaging fixes on 0.2.0.10-alpha:
25100 - We were including instructions about what to do with the
25101 src/config/fallback-consensus file, but we weren't actually
25102 including it in the tarball. Disable all of that for now.
25105 - Allow people to say PreferTunnelledDirConns rather than
25106 PreferTunneledDirConns, for those alternate-spellers out there.
25109 - Don't reevaluate all the information from our consensus document
25110 just because we've downloaded a v2 networkstatus that we intend
25111 to cache. Fixes bug 545; bugfix on 0.2.0.x.
25114 Changes in version 0.2.0.10-alpha - 2007-11-10
25115 This tenth development snapshot adds a third v3 directory authority
25116 run by Mike Perry, adds most of Karsten Loesing's new hidden service
25117 descriptor format, fixes a bad crash bug and new bridge bugs introduced
25118 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
25119 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
25120 addresses many more minor issues.
25122 o New directory authorities:
25123 - Set up ides (run by Mike Perry) as the third v3 directory authority.
25126 - Allow tunnelled directory connections to ask for an encrypted
25127 "begin_dir" connection or an anonymized "uses a full Tor circuit"
25128 connection independently. Now we can make anonymized begin_dir
25129 connections for (e.g.) more secure hidden service posting and
25131 - More progress on proposal 114: code from Karsten Loesing to
25132 implement new hidden service descriptor format.
25133 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
25134 accommodate the growing number of servers that use the default
25135 and are reaching it.
25136 - Directory authorities use a new formula for selecting which nodes
25137 to advertise as Guards: they must be in the top 7/8 in terms of
25138 how long we have known about them, and above the median of those
25139 nodes in terms of weighted fractional uptime.
25140 - Make "not enough dir info yet" warnings describe *why* Tor feels
25141 it doesn't have enough directory info yet.
25144 - Stop servers from crashing if they set a Family option (or
25145 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
25147 - Make bridge users work again -- the move to v3 directories in
25148 0.2.0.9-alpha had introduced a number of bugs that made bridges
25149 no longer work for clients.
25150 - When the clock jumps forward a lot, do not allow the bandwidth
25151 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
25153 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
25154 - When the consensus lists a router descriptor that we previously were
25155 mirroring, but that we considered non-canonical, reload the
25156 descriptor as canonical. This fixes bug 543 where Tor servers
25157 would start complaining after a few days that they don't have
25158 enough directory information to build a circuit.
25159 - Consider replacing the current consensus when certificates arrive
25160 that make the pending consensus valid. Previously, we were only
25161 considering replacement when the new certs _didn't_ help.
25162 - Fix an assert error on startup if we didn't already have the
25163 consensus and certs cached in our datadirectory: we were caching
25164 the consensus in consensus_waiting_for_certs but then free'ing it
25166 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
25167 Request) if we need more v3 certs but we've already got pending
25168 requests for all of them.
25169 - Correctly back off from failing certificate downloads. Fixes
25171 - Authorities don't vote on the Running flag if they have been running
25172 for less than 30 minutes themselves. Fixes bug 547, where a newly
25173 started authority would vote that everyone was down.
25175 o New requirements:
25176 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
25177 it, it had no AES, and it hasn't seen any security patches since
25181 - Clients now hold circuitless TLS connections open for 1.5 times
25182 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
25183 rebuild a new circuit over them within that timeframe. Previously,
25184 they held them open only for KeepalivePeriod (5 minutes).
25185 - Use "If-Modified-Since" to avoid retrieving consensus
25186 networkstatuses that we already have.
25187 - When we have no consensus, check FallbackNetworkstatusFile (defaults
25188 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
25189 we start knowing some directory caches.
25190 - When we receive a consensus from the future, warn about skew.
25191 - Improve skew reporting: try to give the user a better log message
25192 about how skewed they are, and how much this matters.
25193 - When we have a certificate for an authority, believe that
25194 certificate's claims about the authority's IP address.
25195 - New --quiet command-line option to suppress the default console log.
25196 Good in combination with --hash-password.
25197 - Authorities send back an X-Descriptor-Not-New header in response to
25198 an accepted-but-discarded descriptor upload. Partially implements
25200 - Make the log message for "tls error. breaking." more useful.
25201 - Better log messages about certificate downloads, to attempt to
25202 track down the second incarnation of bug 546.
25204 o Minor features (bridges):
25205 - If bridge users set UpdateBridgesFromAuthority, but the digest
25206 they ask for is a 404 from the bridge authority, they now fall
25207 back to trying the bridge directly.
25208 - Bridges now use begin_dir to publish their server descriptor to
25209 the bridge authority, even when they haven't set TunnelDirConns.
25211 o Minor features (controller):
25212 - When reporting clock skew, and we know that the clock is _at least
25213 as skewed_ as some value, but we don't know the actual value,
25214 report the value as a "minimum skew."
25217 - Update linux-tor-prio.sh script to allow QoS based on the uid of
25218 the Tor process. Patch from Marco Bonetti with tweaks from Mike
25222 - Refuse to start if both ORPort and UseBridges are set. Bugfix
25223 on 0.2.0.x, suggested by Matt Edman.
25224 - Don't stop fetching descriptors when FetchUselessDescriptors is
25225 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
25226 reported by tup and ioerror.
25227 - Better log message on vote from unknown authority.
25228 - Don't log "Launching 0 request for 0 router" message.
25230 o Minor bugfixes (memory leaks):
25231 - Stop leaking memory every time we parse a v3 certificate. Bugfix
25233 - Stop leaking memory every time we load a v3 certificate. Bugfix
25234 on 0.2.0.1-alpha. Fixes bug 536.
25235 - Stop leaking a cached networkstatus on exit. Bugfix on
25237 - Stop leaking voter information every time we free a consensus.
25238 Bugfix on 0.2.0.3-alpha.
25239 - Stop leaking signed data every time we check a voter signature.
25240 Bugfix on 0.2.0.3-alpha.
25241 - Stop leaking a signature every time we fail to parse a consensus or
25242 a vote. Bugfix on 0.2.0.3-alpha.
25243 - Stop leaking v2_download_status_map on shutdown. Bugfix on
25245 - Stop leaking conn->nickname every time we make a connection to a
25246 Tor relay without knowing its expected identity digest (e.g. when
25247 using bridges). Bugfix on 0.2.0.3-alpha.
25249 - Minor bugfixes (portability):
25250 - Run correctly on platforms where rlim_t is larger than unsigned
25251 long, and/or where the real limit for number of open files is
25252 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
25253 particular, these may be needed for OS X 10.5.
25256 Changes in version 0.1.2.18 - 2007-10-28
25257 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
25258 hidden service introduction that were causing huge delays, and a big
25259 bug that was causing some servers to disappear from the network status
25260 lists for a few hours each day.
25262 o Major bugfixes (crashes):
25263 - If a connection is shut down abruptly because of something that
25264 happened inside connection_flushed_some(), do not call
25265 connection_finished_flushing(). Should fix bug 451:
25266 "connection_stop_writing: Assertion conn->write_event failed"
25267 Bugfix on 0.1.2.7-alpha.
25268 - Fix possible segfaults in functions called from
25269 rend_process_relay_cell().
25271 o Major bugfixes (hidden services):
25272 - Hidden services were choosing introduction points uniquely by
25273 hexdigest, but when constructing the hidden service descriptor
25274 they merely wrote the (potentially ambiguous) nickname.
25275 - Clients now use the v2 intro format for hidden service
25276 connections: they specify their chosen rendezvous point by identity
25277 digest rather than by (potentially ambiguous) nickname. These
25278 changes could speed up hidden service connections dramatically.
25280 o Major bugfixes (other):
25281 - Stop publishing a new server descriptor just because we get a
25282 HUP signal. This led (in a roundabout way) to some servers getting
25283 dropped from the networkstatus lists for a few hours each day.
25284 - When looking for a circuit to cannibalize, consider family as well
25285 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
25286 circuit cannibalization).
25287 - When a router wasn't listed in a new networkstatus, we were leaving
25288 the flags for that router alone -- meaning it remained Named,
25289 Running, etc -- even though absence from the networkstatus means
25290 that it shouldn't be considered to exist at all anymore. Now we
25291 clear all the flags for routers that fall out of the networkstatus
25292 consensus. Fixes bug 529.
25295 - Don't try to access (or alter) the state file when running
25296 --list-fingerprint or --verify-config or --hash-password. Resolves
25298 - When generating information telling us how to extend to a given
25299 router, do not try to include the nickname if it is
25300 absent. Resolves bug 467.
25301 - Fix a user-triggerable segfault in expand_filename(). (There isn't
25302 a way to trigger this remotely.)
25303 - When sending a status event to the controller telling it that an
25304 OR address is reachable, set the port correctly. (Previously we
25305 were reporting the dir port.)
25306 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
25307 command. Bugfix on 0.1.2.17.
25308 - When loading bandwidth history, do not believe any information in
25309 the future. Fixes bug 434.
25310 - When loading entry guard information, do not believe any information
25312 - When we have our clock set far in the future and generate an
25313 onion key, then re-set our clock to be correct, we should not stop
25314 the onion key from getting rotated.
25315 - On some platforms, accept() can return a broken address. Detect
25316 this more quietly, and deal accordingly. Fixes bug 483.
25317 - It's not actually an error to find a non-pending entry in the DNS
25318 cache when canceling a pending resolve. Don't log unless stuff
25319 is fishy. Resolves bug 463.
25320 - Don't reset trusted dir server list when we set a configuration
25321 option. Patch from Robert Hogan.
25322 - Don't try to create the datadir when running --verify-config or
25323 --hash-password. Resolves bug 540.
25326 Changes in version 0.2.0.9-alpha - 2007-10-24
25327 This ninth development snapshot switches clients to the new v3 directory
25328 system; allows servers to be listed in the network status even when they
25329 have the same nickname as a registered server; and fixes many other
25330 bugs including a big one that was causing some servers to disappear
25331 from the network status lists for a few hours each day.
25333 o Major features (directory system):
25334 - Clients now download v3 consensus networkstatus documents instead
25335 of v2 networkstatus documents. Clients and caches now base their
25336 opinions about routers on these consensus documents. Clients only
25337 download router descriptors listed in the consensus.
25338 - Authorities now list servers who have the same nickname as
25339 a different named server, but list them with a new flag,
25340 "Unnamed". Now we can list servers that happen to pick the same
25341 nickname as a server that registered two years ago and then
25342 disappeared. Partially implements proposal 122.
25343 - If the consensus lists a router as "Unnamed", the name is assigned
25344 to a different router: do not identify the router by that name.
25345 Partially implements proposal 122.
25346 - Authorities can now come to a consensus on which method to use to
25347 compute the consensus. This gives us forward compatibility.
25350 - Stop publishing a new server descriptor just because we HUP or
25351 when we find our DirPort to be reachable but won't actually publish
25352 it. New descriptors without any real changes are dropped by the
25353 authorities, and can screw up our "publish every 18 hours" schedule.
25355 - When a router wasn't listed in a new networkstatus, we were leaving
25356 the flags for that router alone -- meaning it remained Named,
25357 Running, etc -- even though absence from the networkstatus means
25358 that it shouldn't be considered to exist at all anymore. Now we
25359 clear all the flags for routers that fall out of the networkstatus
25360 consensus. Fixes bug 529; bugfix on 0.1.2.x.
25361 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
25362 extrainfo documents and then discard them immediately for not
25363 matching the latest router. Bugfix on 0.2.0.1-alpha.
25365 o Minor features (v3 directory protocol):
25366 - Allow tor-gencert to generate a new certificate without replacing
25368 - Allow certificates to include an address.
25369 - When we change our directory-cache settings, reschedule all voting
25370 and download operations.
25371 - Reattempt certificate downloads immediately on failure, as long as
25372 we haven't failed a threshold number of times yet.
25373 - Delay retrying consensus downloads while we're downloading
25374 certificates to verify the one we just got. Also, count getting a
25375 consensus that we already have (or one that isn't valid) as a failure,
25376 and count failing to get the certificates after 20 minutes as a
25378 - Build circuits and download descriptors even if our consensus is a
25379 little expired. (This feature will go away once authorities are
25382 o Minor features (router descriptor cache):
25383 - If we find a cached-routers file that's been sitting around for more
25384 than 28 days unmodified, then most likely it's a leftover from
25385 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
25387 - When we (as a cache) download a descriptor because it was listed
25388 in a consensus, remember when the consensus was supposed to expire,
25389 and don't expire the descriptor until then.
25391 o Minor features (performance):
25392 - Call routerlist_remove_old_routers() much less often. This should
25393 speed startup, especially on directory caches.
25394 - Don't try to launch new descriptor downloads quite so often when we
25395 already have enough directory information to build circuits.
25396 - Base64 decoding was actually showing up on our profile when parsing
25397 the initial descriptor file; switch to an in-process all-at-once
25398 implementation that's about 3.5x times faster than calling out to
25401 o Minor features (compilation):
25402 - Detect non-ASCII platforms (if any still exist) and refuse to
25403 build there: some of our code assumes that 'A' is 65 and so on.
25405 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
25406 - Make the "next period" votes into "current period" votes immediately
25407 after publishing the consensus; avoid a heisenbug that made them
25408 stick around indefinitely.
25409 - When we discard a vote as a duplicate, do not report this as
25411 - Treat missing v3 keys or certificates as an error when running as a
25412 v3 directory authority.
25413 - When we're configured to be a v3 authority, but we're only listed
25414 as a non-v3 authority in our DirServer line for ourself, correct
25416 - If an authority doesn't have a qualified hostname, just put
25417 its address in the vote. This fixes the problem where we referred to
25418 "moria on moria:9031."
25419 - Distinguish between detached signatures for the wrong period, and
25420 detached signatures for a divergent vote.
25421 - Fix a small memory leak when computing a consensus.
25422 - When there's no consensus, we were forming a vote every 30
25423 minutes, but writing the "valid-after" line in our vote based
25424 on our configured V3AuthVotingInterval: so unless the intervals
25425 matched up, we immediately rejected our own vote because it didn't
25426 start at the voting interval that caused us to construct a vote.
25428 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
25429 - Delete unverified-consensus when the real consensus is set.
25430 - Consider retrying a consensus networkstatus fetch immediately
25431 after one fails: don't wait 60 seconds to notice.
25432 - When fetching a consensus as a cache, wait until a newer consensus
25433 should exist before trying to replace the current one.
25434 - Use a more forgiving schedule for retrying failed consensus
25435 downloads than for other types.
25437 o Minor bugfixes (other directory issues):
25438 - Correct the implementation of "download votes by digest." Bugfix on
25440 - Authorities no longer send back "400 you're unreachable please fix
25441 it" errors to Tor servers that aren't online all the time. We're
25442 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
25444 o Minor bugfixes (controller):
25445 - Don't reset trusted dir server list when we set a configuration
25446 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
25447 - Respond to INT and TERM SIGNAL commands before we execute the
25448 signal, in case the signal shuts us down. We had a patch in
25449 0.1.2.1-alpha that tried to do this by queueing the response on
25450 the connection's buffer before shutting down, but that really
25451 isn't the same thing at all. Bug located by Matt Edman.
25453 o Minor bugfixes (misc):
25454 - Correctly check for bad options to the "PublishServerDescriptor"
25455 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
25456 - Stop leaking memory on failing case of base32_decode, and make
25457 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
25458 - Don't try to download extrainfo documents when we're trying to
25459 fetch enough directory info to build a circuit: having enough
25460 info should get priority. Bugfix on 0.2.0.x.
25461 - Don't complain that "your server has not managed to confirm that its
25462 ports are reachable" if we haven't been able to build any circuits
25463 yet. Bug found by spending four hours without a v3 consensus. Bugfix
25465 - Detect the reason for failing to mmap a descriptor file we just
25466 wrote, and give a more useful log message. Fixes bug 533. Bugfix
25469 o Code simplifications and refactoring:
25470 - Remove support for the old bw_accounting file: we've been storing
25471 bandwidth accounting information in the state file since
25472 0.1.2.5-alpha. This may result in bandwidth accounting errors
25473 if you try to upgrade from 0.1.1.x or earlier, or if you try to
25474 downgrade to 0.1.1.x or earlier.
25475 - New convenience code to locate a file within the DataDirectory.
25476 - Move non-authority functionality out of dirvote.c.
25477 - Refactor the arguments for router_pick_{directory_|trusteddir}server
25478 so that they all take the same named flags.
25481 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
25482 Unix users an easy way to script their Tor process (e.g. by
25483 adjusting bandwidth based on the time of the day).
25486 Changes in version 0.2.0.8-alpha - 2007-10-12
25487 This eighth development snapshot fixes a crash bug that's been bothering
25488 us since February 2007, lets bridge authorities store a list of bridge
25489 descriptors they've seen, gets v3 directory voting closer to working,
25490 starts caching v3 directory consensus documents on directory mirrors,
25491 and fixes a variety of smaller issues including some minor memory leaks.
25493 o Major features (router descriptor cache):
25494 - Store routers in a file called cached-descriptors instead of in
25495 cached-routers. Initialize cached-descriptors from cached-routers
25496 if the old format is around. The new format allows us to store
25497 annotations along with descriptors.
25498 - Use annotations to record the time we received each descriptor, its
25499 source, and its purpose.
25500 - Disable the SETROUTERPURPOSE controller command: it is now
25502 - Controllers should now specify cache=no or cache=yes when using
25503 the +POSTDESCRIPTOR command.
25504 - Bridge authorities now write bridge descriptors to disk, meaning
25505 we can export them to other programs and begin distributing them
25508 o Major features (directory authorities):
25509 - When a v3 authority is missing votes or signatures, it now tries
25511 - Directory authorities track weighted fractional uptime as well as
25512 weighted mean-time-between failures. WFU is suitable for deciding
25513 whether a node is "usually up", while MTBF is suitable for deciding
25514 whether a node is "likely to stay up." We need both, because
25515 "usually up" is a good requirement for guards, while "likely to
25516 stay up" is a good requirement for long-lived connections.
25518 o Major features (v3 directory system):
25519 - Caches now download v3 network status documents as needed,
25520 and download the descriptors listed in them.
25521 - All hosts now attempt to download and keep fresh v3 authority
25522 certificates, and re-attempt after failures.
25523 - More internal-consistency checks for vote parsing.
25525 o Major bugfixes (crashes):
25526 - If a connection is shut down abruptly because of something that
25527 happened inside connection_flushed_some(), do not call
25528 connection_finished_flushing(). Should fix bug 451. Bugfix on
25531 o Major bugfixes (performance):
25532 - Fix really bad O(n^2) performance when parsing a long list of
25533 routers: Instead of searching the entire list for an "extra-info "
25534 string which usually wasn't there, once for every routerinfo
25535 we read, just scan lines forward until we find one we like.
25537 - When we add data to a write buffer in response to the data on that
25538 write buffer getting low because of a flush, do not consider the
25539 newly added data as a candidate for immediate flushing, but rather
25540 make it wait until the next round of writing. Otherwise, we flush
25541 and refill recursively, and a single greedy TLS connection can
25542 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
25544 o Minor features (v3 authority system):
25545 - Add more ways for tools to download the votes that lead to the
25547 - Send a 503 when low on bandwidth and a vote, consensus, or
25548 certificate is requested.
25549 - If-modified-since is now implemented properly for all kinds of
25550 certificate requests.
25552 o Minor bugfixes (network statuses):
25553 - Tweak the implementation of proposal 109 slightly: allow at most
25554 two Tor servers on the same IP address, except if it's the location
25555 of a directory authority, in which case allow five. Bugfix on
25558 o Minor bugfixes (controller):
25559 - When sending a status event to the controller telling it that an
25560 OR address is reachable, set the port correctly. (Previously we
25561 were reporting the dir port.) Bugfix on 0.1.2.x.
25563 o Minor bugfixes (v3 directory system):
25564 - Fix logic to look up a cert by its signing key digest. Bugfix on
25566 - Only change the reply to a vote to "OK" if it's not already
25567 set. This gets rid of annoying "400 OK" log messages, which may
25568 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
25569 - When we get a valid consensus, recompute the voting schedule.
25570 - Base the valid-after time of a vote on the consensus voting
25571 schedule, not on our preferred schedule.
25572 - Make the return values and messages from signature uploads and
25573 downloads more sensible.
25574 - Fix a memory leak when serving votes and consensus documents, and
25575 another when serving certificates.
25577 o Minor bugfixes (performance):
25578 - Use a slightly simpler string hashing algorithm (copying Python's
25579 instead of Java's) and optimize our digest hashing algorithm to take
25580 advantage of 64-bit platforms and to remove some possibly-costly
25582 - Fix a minor memory leak whenever we parse guards from our state
25583 file. Bugfix on 0.2.0.7-alpha.
25584 - Fix a minor memory leak whenever we write out a file. Bugfix on
25586 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
25587 command. Bugfix on 0.2.0.5-alpha.
25589 o Minor bugfixes (portability):
25590 - On some platforms, accept() can return a broken address. Detect
25591 this more quietly, and deal accordingly. Fixes bug 483.
25592 - Stop calling tor_strlower() on uninitialized memory in some cases.
25593 Bugfix in 0.2.0.7-alpha.
25595 o Minor bugfixes (usability):
25596 - Treat some 403 responses from directory servers as INFO rather than
25597 WARN-severity events.
25598 - It's not actually an error to find a non-pending entry in the DNS
25599 cache when canceling a pending resolve. Don't log unless stuff is
25600 fishy. Resolves bug 463.
25602 o Minor bugfixes (anonymity):
25603 - Never report that we've used more bandwidth than we're willing to
25604 relay: it leaks how much non-relay traffic we're using. Resolves
25606 - When looking for a circuit to cannibalize, consider family as well
25607 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
25608 circuit cannibalization).
25610 o Code simplifications and refactoring:
25611 - Make a bunch of functions static. Remove some dead code.
25612 - Pull out about a third of the really big routerlist.c; put it in a
25613 new module, networkstatus.c.
25614 - Merge the extra fields in local_routerstatus_t back into
25615 routerstatus_t: we used to need one routerstatus_t for each
25616 authority's opinion, plus a local_routerstatus_t for the locally
25617 computed consensus opinion. To save space, we put the locally
25618 modified fields into local_routerstatus_t, and only the common
25619 stuff into routerstatus_t. But once v3 directories are in use,
25620 clients and caches will no longer need to hold authority opinions;
25621 thus, the rationale for keeping the types separate is now gone.
25622 - Make the code used to reschedule and reattempt downloads more
25624 - Turn all 'Are we a directory server/mirror?' logic into a call to
25626 - Remove the code to generate the oldest (v1) directory format.
25627 The code has been disabled since 0.2.0.5-alpha.
25630 Changes in version 0.2.0.7-alpha - 2007-09-21
25631 This seventh development snapshot makes bridges work again, makes bridge
25632 authorities work for the first time, fixes two huge performance flaws
25633 in hidden services, and fixes a variety of minor issues.
25635 o New directory authorities:
25636 - Set up moria1 and tor26 as the first v3 directory authorities. See
25637 doc/spec/dir-spec.txt for details on the new directory design.
25639 o Major bugfixes (crashes):
25640 - Fix possible segfaults in functions called from
25641 rend_process_relay_cell(). Bugfix on 0.1.2.x.
25643 o Major bugfixes (bridges):
25644 - Fix a bug that made servers send a "404 Not found" in response to
25645 attempts to fetch their server descriptor. This caused Tor servers
25646 to take many minutes to establish reachability for their DirPort,
25647 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
25648 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
25649 users configure that and specify a bridge with an identity
25650 fingerprint, now they will lookup the bridge descriptor at the
25651 default bridge authority via a one-hop tunnel, but once circuits
25652 are established they will switch to a three-hop tunnel for later
25653 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
25655 o Major bugfixes (hidden services):
25656 - Hidden services were choosing introduction points uniquely by
25657 hexdigest, but when constructing the hidden service descriptor
25658 they merely wrote the (potentially ambiguous) nickname.
25659 - Clients now use the v2 intro format for hidden service
25660 connections: they specify their chosen rendezvous point by identity
25661 digest rather than by (potentially ambiguous) nickname. Both
25662 are bugfixes on 0.1.2.x, and they could speed up hidden service
25663 connections dramatically. Thanks to Karsten Loesing.
25665 o Minor features (security):
25666 - As a client, do not believe any server that tells us that an
25667 address maps to an internal address space.
25668 - Make it possible to enable HashedControlPassword and
25669 CookieAuthentication at the same time.
25671 o Minor features (guard nodes):
25672 - Tag every guard node in our state file with the version that
25673 we believe added it, or with our own version if we add it. This way,
25674 if a user temporarily runs an old version of Tor and then switches
25675 back to a new one, she doesn't automatically lose her guards.
25677 o Minor features (speed):
25678 - When implementing AES counter mode, update only the portions of the
25679 counter buffer that need to change, and don't keep separate
25680 network-order and host-order counters when they are the same (i.e.,
25681 on big-endian hosts.)
25683 o Minor features (controller):
25684 - Accept LF instead of CRLF on controller, since some software has a
25685 hard time generating real Internet newlines.
25686 - Add GETINFO values for the server status events
25687 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
25690 o Removed features:
25691 - Routers no longer include bandwidth-history lines in their
25692 descriptors; this information is already available in extra-info
25693 documents, and including it in router descriptors took up 60%
25694 (!) of compressed router descriptor downloads. Completes
25695 implementation of proposal 104.
25696 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
25697 and TorControl.py, as they use the old v0 controller protocol,
25698 and are obsoleted by TorFlow anyway.
25699 - Drop support for v1 rendezvous descriptors, since we never used
25700 them anyway, and the code has probably rotted by now. Based on
25701 patch from Karsten Loesing.
25702 - On OSX, stop warning the user that kqueue support in libevent is
25703 "experimental", since it seems to have worked fine for ages.
25706 - When generating information telling us how to extend to a given
25707 router, do not try to include the nickname if it is absent. Fixes
25708 bug 467. Bugfix on 0.2.0.3-alpha.
25709 - Fix a user-triggerable (but not remotely-triggerable) segfault
25710 in expand_filename(). Bugfix on 0.1.2.x.
25711 - Fix a memory leak when freeing incomplete requests from DNSPort.
25712 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
25713 - Don't try to access (or alter) the state file when running
25714 --list-fingerprint or --verify-config or --hash-password. (Resolves
25715 bug 499.) Bugfix on 0.1.2.x.
25716 - Servers used to decline to publish their DirPort if their
25717 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
25718 were below a threshold. Now they only look at BandwidthRate and
25719 RelayBandwidthRate. Bugfix on 0.1.2.x.
25720 - Remove an optimization in the AES counter-mode code that assumed
25721 that the counter never exceeded 2^68. When the counter can be set
25722 arbitrarily as an IV (as it is by Karsten's new hidden services
25723 code), this assumption no longer holds. Bugfix on 0.1.2.x.
25724 - Resume listing "AUTHORITY" flag for authorities in network status.
25725 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
25727 o Code simplifications and refactoring:
25728 - Revamp file-writing logic so we don't need to have the entire
25729 contents of a file in memory at once before we write to disk. Tor,
25731 - Turn "descriptor store" into a full-fledged type.
25732 - Move all NT services code into a separate source file.
25733 - Unify all code that computes medians, percentile elements, etc.
25734 - Get rid of a needless malloc when parsing address policies.
25737 Changes in version 0.1.2.17 - 2007-08-30
25738 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
25739 X bundles. Vidalia 0.0.14 makes authentication required for the
25740 ControlPort in the default configuration, which addresses important
25741 security risks. Everybody who uses Vidalia (or another controller)
25744 In addition, this Tor update fixes major load balancing problems with
25745 path selection, which should speed things up a lot once many people
25748 o Major bugfixes (security):
25749 - We removed support for the old (v0) control protocol. It has been
25750 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
25751 become more of a headache than it's worth.
25753 o Major bugfixes (load balancing):
25754 - When choosing nodes for non-guard positions, weight guards
25755 proportionally less, since they already have enough load. Patch
25757 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
25758 will allow fast Tor servers to get more attention.
25759 - When we're upgrading from an old Tor version, forget our current
25760 guards and pick new ones according to the new weightings. These
25761 three load balancing patches could raise effective network capacity
25762 by a factor of four. Thanks to Mike Perry for measurements.
25764 o Major bugfixes (stream expiration):
25765 - Expire not-yet-successful application streams in all cases if
25766 they've been around longer than SocksTimeout. Right now there are
25767 some cases where the stream will live forever, demanding a new
25768 circuit every 15 seconds. Fixes bug 454; reported by lodger.
25770 o Minor features (controller):
25771 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
25772 is valid before any authentication has been received. It tells
25773 a controller what kind of authentication is expected, and what
25774 protocol is spoken. Implements proposal 119.
25776 o Minor bugfixes (performance):
25777 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
25778 greatly speeding up loading cached-routers from disk on startup.
25779 - Disable sentinel-based debugging for buffer code: we squashed all
25780 the bugs that this was supposed to detect a long time ago, and now
25781 its only effect is to change our buffer sizes from nice powers of
25782 two (which platform mallocs tend to like) to values slightly over
25783 powers of two (which make some platform mallocs sad).
25785 o Minor bugfixes (misc):
25786 - If exit bandwidth ever exceeds one third of total bandwidth, then
25787 use the correct formula to weight exit nodes when choosing paths.
25788 Based on patch from Mike Perry.
25789 - Choose perfectly fairly among routers when choosing by bandwidth and
25790 weighting by fraction of bandwidth provided by exits. Previously, we
25791 would choose with only approximate fairness, and correct ourselves
25792 if we ran off the end of the list.
25793 - If we require CookieAuthentication but we fail to write the
25794 cookie file, we would warn but not exit, and end up in a state
25795 where no controller could authenticate. Now we exit.
25796 - If we require CookieAuthentication, stop generating a new cookie
25797 every time we change any piece of our config.
25798 - Refuse to start with certain directory authority keys, and
25799 encourage people using them to stop.
25800 - Terminate multi-line control events properly. Original patch
25802 - Fix a minor memory leak when we fail to find enough suitable
25803 servers to choose a circuit.
25804 - Stop leaking part of the descriptor when we run into a particularly
25805 unparseable piece of it.
25808 Changes in version 0.2.0.6-alpha - 2007-08-26
25809 This sixth development snapshot features a new Vidalia version in the
25810 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
25811 the ControlPort in the default configuration, which addresses important
25814 In addition, this snapshot fixes major load balancing problems
25815 with path selection, which should speed things up a lot once many
25816 people have upgraded. The directory authorities also use a new
25817 mean-time-between-failure approach to tracking which servers are stable,
25818 rather than just looking at the most recent uptime.
25820 o New directory authorities:
25821 - Set up Tonga as the default bridge directory authority.
25824 - Directory authorities now track servers by weighted
25825 mean-times-between-failures. When we have 4 or more days of data,
25826 use measured MTBF rather than declared uptime to decide whether
25827 to call a router Stable. Implements proposal 108.
25829 o Major bugfixes (load balancing):
25830 - When choosing nodes for non-guard positions, weight guards
25831 proportionally less, since they already have enough load. Patch
25833 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
25834 will allow fast Tor servers to get more attention.
25835 - When we're upgrading from an old Tor version, forget our current
25836 guards and pick new ones according to the new weightings. These
25837 three load balancing patches could raise effective network capacity
25838 by a factor of four. Thanks to Mike Perry for measurements.
25840 o Major bugfixes (descriptor parsing):
25841 - Handle unexpected whitespace better in malformed descriptors. Bug
25842 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
25845 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
25846 GETINFO for Torstat to use until it can switch to using extrainfos.
25847 - Optionally (if built with -DEXPORTMALLINFO) export the output
25848 of mallinfo via http, as tor/mallinfo.txt. Only accessible
25852 - Do not intermix bridge routers with controller-added
25853 routers. (Bugfix on 0.2.0.x)
25854 - Do not fail with an assert when accept() returns an unexpected
25855 address family. Addresses but does not wholly fix bug 483. (Bugfix
25857 - Let directory authorities startup even when they can't generate
25858 a descriptor immediately, e.g. because they don't know their
25860 - Stop putting the authentication cookie in a file called "0"
25861 in your working directory if you don't specify anything for the
25862 new CookieAuthFile option. Reported by Matt Edman.
25863 - Make it possible to read the PROTOCOLINFO response in a way that
25864 conforms to our control-spec. Reported by Matt Edman.
25865 - Fix a minor memory leak when we fail to find enough suitable
25866 servers to choose a circuit. Bugfix on 0.1.2.x.
25867 - Stop leaking part of the descriptor when we run into a particularly
25868 unparseable piece of it. Bugfix on 0.1.2.x.
25869 - Unmap the extrainfo cache file on exit.
25872 Changes in version 0.2.0.5-alpha - 2007-08-19
25873 This fifth development snapshot fixes compilation on Windows again;
25874 fixes an obnoxious client-side bug that slowed things down and put
25875 extra load on the network; gets us closer to using the v3 directory
25876 voting scheme; makes it easier for Tor controllers to use cookie-based
25877 authentication; and fixes a variety of other bugs.
25879 o Removed features:
25880 - Version 1 directories are no longer generated in full. Instead,
25881 authorities generate and serve "stub" v1 directories that list
25882 no servers. This will stop Tor versions 0.1.0.x and earlier from
25883 working, but (for security reasons) nobody should be running those
25886 o Major bugfixes (compilation, 0.2.0.x):
25887 - Try to fix Win32 compilation again: improve checking for IPv6 types.
25888 - Try to fix MSVC compilation: build correctly on platforms that do
25889 not define s6_addr16 or s6_addr32.
25890 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
25893 o Major bugfixes (stream expiration):
25894 - Expire not-yet-successful application streams in all cases if
25895 they've been around longer than SocksTimeout. Right now there are
25896 some cases where the stream will live forever, demanding a new
25897 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
25898 reported by lodger.
25900 o Minor features (directory servers):
25901 - When somebody requests a list of statuses or servers, and we have
25902 none of those, return a 404 rather than an empty 200.
25904 o Minor features (directory voting):
25905 - Store v3 consensus status consensuses on disk, and reload them
25908 o Minor features (security):
25909 - Warn about unsafe ControlPort configurations.
25910 - Refuse to start with certain directory authority keys, and
25911 encourage people using them to stop.
25913 o Minor features (controller):
25914 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
25915 is valid before any authentication has been received. It tells
25916 a controller what kind of authentication is expected, and what
25917 protocol is spoken. Implements proposal 119.
25918 - New config option CookieAuthFile to choose a new location for the
25919 cookie authentication file, and config option
25920 CookieAuthFileGroupReadable to make it group-readable.
25922 o Minor features (unit testing):
25923 - Add command-line arguments to unit-test executable so that we can
25924 invoke any chosen test from the command line rather than having
25925 to run the whole test suite at once; and so that we can turn on
25926 logging for the unit tests.
25928 o Minor bugfixes (on 0.1.2.x):
25929 - If we require CookieAuthentication but we fail to write the
25930 cookie file, we would warn but not exit, and end up in a state
25931 where no controller could authenticate. Now we exit.
25932 - If we require CookieAuthentication, stop generating a new cookie
25933 every time we change any piece of our config.
25934 - When loading bandwidth history, do not believe any information in
25935 the future. Fixes bug 434.
25936 - When loading entry guard information, do not believe any information
25938 - When we have our clock set far in the future and generate an
25939 onion key, then re-set our clock to be correct, we should not stop
25940 the onion key from getting rotated.
25941 - Clean up torrc sample config file.
25942 - Do not automatically run configure from autogen.sh. This
25943 non-standard behavior tended to annoy people who have built other
25946 o Minor bugfixes (on 0.2.0.x):
25947 - Fix a bug with AutomapHostsOnResolve that would always cause
25948 the second request to fail. Bug reported by Kate. Bugfix on
25950 - Fix a bug in ADDRMAP controller replies that would sometimes
25951 try to print a NULL. Patch from tup.
25952 - Read v3 directory authority keys from the right location.
25953 - Numerous bugfixes to directory voting code.
25956 Changes in version 0.1.2.16 - 2007-08-01
25957 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
25958 remote attacker in certain situations to rewrite the user's torrc
25959 configuration file. This can completely compromise anonymity of users
25960 in most configurations, including those running the Vidalia bundles,
25961 TorK, etc. Or worse.
25963 o Major security fixes:
25964 - Close immediately after missing authentication on control port;
25965 do not allow multiple authentication attempts.
25968 Changes in version 0.2.0.4-alpha - 2007-08-01
25969 This fourth development snapshot fixes a critical security vulnerability
25970 for most users, specifically those running Vidalia, TorK, etc. Everybody
25971 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
25973 o Major security fixes:
25974 - Close immediately after missing authentication on control port;
25975 do not allow multiple authentication attempts.
25977 o Major bugfixes (compilation):
25978 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
25981 o Minor features (performance):
25982 - Be even more aggressive about releasing RAM from small
25983 empty buffers. Thanks to our free-list code, this shouldn't be too
25984 performance-intensive.
25985 - Disable sentinel-based debugging for buffer code: we squashed all
25986 the bugs that this was supposed to detect a long time ago, and
25987 now its only effect is to change our buffer sizes from nice
25988 powers of two (which platform mallocs tend to like) to values
25989 slightly over powers of two (which make some platform mallocs sad).
25990 - Log malloc statistics from mallinfo() on platforms where it
25994 Changes in version 0.2.0.3-alpha - 2007-07-29
25995 This third development snapshot introduces new experimental
25996 blocking-resistance features and a preliminary version of the v3
25997 directory voting design, and includes many other smaller features
26001 - The first pieces of our "bridge" design for blocking-resistance
26002 are implemented. People can run bridge directory authorities;
26003 people can run bridges; and people can configure their Tor clients
26004 with a set of bridges to use as the first hop into the Tor network.
26005 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
26007 - Create listener connections before we setuid to the configured
26008 User and Group. Now non-Windows users can choose port values
26009 under 1024, start Tor as root, and have Tor bind those ports
26010 before it changes to another UID. (Windows users could already
26012 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
26013 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
26014 on "vserver" accounts. (Patch from coderman.)
26015 - Be even more aggressive about separating local traffic from relayed
26016 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
26018 o Major features (experimental):
26019 - First cut of code for "v3 dir voting": directory authorities will
26020 vote on a common network status document rather than each publishing
26021 their own opinion. This code needs more testing and more corner-case
26022 handling before it's ready for use.
26025 - Directory authorities now call routers Fast if their bandwidth is
26026 at least 100KB/s, and consider their bandwidth adequate to be a
26027 Guard if it is at least 250KB/s, no matter the medians. This fix
26028 complements proposal 107. [Bugfix on 0.1.2.x]
26029 - Directory authorities now never mark more than 3 servers per IP as
26030 Valid and Running. (Implements proposal 109, by Kevin Bauer and
26032 - Minor change to organizationName and commonName generation
26033 procedures in TLS certificates during Tor handshakes, to invalidate
26034 some earlier censorware approaches. This is not a long-term
26035 solution, but applying it will give us a bit of time to look into
26036 the epidemiology of countermeasures as they spread.
26038 o Major bugfixes (directory):
26039 - Rewrite directory tokenization code to never run off the end of
26040 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
26042 o Minor features (controller):
26043 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
26044 match requests to applications. (Patch from Robert Hogan.)
26045 - Report address and port correctly on connections to DNSPort. (Patch
26046 from Robert Hogan.)
26047 - Add a RESOLVE command to launch hostname lookups. (Original patch
26048 from Robert Hogan.)
26049 - Add GETINFO status/enough-dir-info to let controllers tell whether
26050 Tor has downloaded sufficient directory information. (Patch
26052 - You can now use the ControlSocket option to tell Tor to listen for
26053 controller connections on Unix domain sockets on systems that
26054 support them. (Patch from Peter Palfrader.)
26055 - STREAM NEW events are generated for DNSPort requests and for
26056 tunneled directory connections. (Patch from Robert Hogan.)
26057 - New "GETINFO address-mappings/*" command to get address mappings
26058 with expiry information. "addr-mappings/*" is now deprecated.
26061 o Minor features (misc):
26062 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
26064 - The tor-gencert tool for v3 directory authorities now creates all
26065 files as readable to the file creator only, and write-protects
26066 the authority identity key.
26067 - When dumping memory usage, list bytes used in buffer memory
26069 - When running with dmalloc, dump more stats on hup and on exit.
26070 - Directory authorities now fail quickly and (relatively) harmlessly
26071 if they generate a network status document that is somehow
26074 o Traffic load balancing improvements:
26075 - If exit bandwidth ever exceeds one third of total bandwidth, then
26076 use the correct formula to weight exit nodes when choosing paths.
26077 (Based on patch from Mike Perry.)
26078 - Choose perfectly fairly among routers when choosing by bandwidth and
26079 weighting by fraction of bandwidth provided by exits. Previously, we
26080 would choose with only approximate fairness, and correct ourselves
26081 if we ran off the end of the list. [Bugfix on 0.1.2.x]
26083 o Performance improvements:
26084 - Be more aggressive with freeing buffer RAM or putting it on the
26086 - Use Critical Sections rather than Mutexes for synchronizing threads
26087 on win32; Mutexes are heavier-weight, and designed for synchronizing
26090 o Deprecated and removed features:
26091 - RedirectExits is now deprecated.
26092 - Stop allowing address masks that do not correspond to bit prefixes.
26093 We have warned about these for a really long time; now it's time
26094 to reject them. (Patch from croup.)
26096 o Minor bugfixes (directory):
26097 - Fix another crash bug related to extra-info caching. (Bug found by
26098 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
26099 - Directories no longer return a "304 not modified" when they don't
26100 have the networkstatus the client asked for. Also fix a memory
26101 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
26102 - We had accidentally labelled 0.1.2.x directory servers as not
26103 suitable for begin_dir requests, and had labelled no directory
26104 servers as suitable for uploading extra-info documents. [Bugfix
26107 o Minor bugfixes (dns):
26108 - Fix a crash when DNSPort is set more than once. (Patch from Robert
26109 Hogan.) [Bugfix on 0.2.0.2-alpha]
26110 - Add DNSPort connections to the global connection list, so that we
26111 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
26113 - Fix a dangling reference that could lead to a crash when DNSPort is
26114 changed or closed (Patch from Robert Hogan.) [Bugfix on
26117 o Minor bugfixes (controller):
26118 - Provide DNS expiry times in GMT, not in local time. For backward
26119 compatibility, ADDRMAP events only provide GMT expiry in an extended
26120 field. "GETINFO address-mappings" always does the right thing.
26121 - Use CRLF line endings properly in NS events.
26122 - Terminate multi-line control events properly. (Original patch
26123 from tup.) [Bugfix on 0.1.2.x-alpha]
26124 - Do not include spaces in SOURCE_ADDR fields in STREAM
26125 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
26128 Changes in version 0.1.2.15 - 2007-07-17
26129 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
26130 problems, fixes compilation on BSD, and fixes a variety of other
26131 bugs. Everybody should upgrade.
26133 o Major bugfixes (compilation):
26134 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
26136 o Major bugfixes (crashes):
26137 - Try even harder not to dereference the first character after
26138 an mmap(). Reported by lodger.
26139 - Fix a crash bug in directory authorities when we re-number the
26140 routerlist while inserting a new router.
26141 - When the cached-routers file is an even multiple of the page size,
26142 don't run off the end and crash. (Fixes bug 455; based on idea
26144 - Fix eventdns.c behavior on Solaris: It is critical to include
26145 orconfig.h _before_ sys/types.h, so that we can get the expected
26146 definition of _FILE_OFFSET_BITS.
26148 o Major bugfixes (security):
26149 - Fix a possible buffer overrun when using BSD natd support. Bug
26151 - When sending destroy cells from a circuit's origin, don't include
26152 the reason for tearing down the circuit. The spec says we didn't,
26153 and now we actually don't. Reported by lodger.
26154 - Keep streamids from different exits on a circuit separate. This
26155 bug may have allowed other routers on a given circuit to inject
26156 cells into streams. Reported by lodger; fixes bug 446.
26157 - If there's a never-before-connected-to guard node in our list,
26158 never choose any guards past it. This way we don't expand our
26159 guard list unless we need to.
26161 o Minor bugfixes (guard nodes):
26162 - Weight guard selection by bandwidth, so that low-bandwidth nodes
26163 don't get overused as guards.
26165 o Minor bugfixes (directory):
26166 - Correctly count the number of authorities that recommend each
26167 version. Previously, we were under-counting by 1.
26168 - Fix a potential crash bug when we load many server descriptors at
26169 once and some of them make others of them obsolete. Fixes bug 458.
26171 o Minor bugfixes (hidden services):
26172 - Stop tearing down the whole circuit when the user asks for a
26173 connection to a port that the hidden service didn't configure.
26176 o Minor bugfixes (misc):
26177 - On Windows, we were preventing other processes from reading
26178 cached-routers while Tor was running. Reported by janbar.
26179 - Fix a possible (but very unlikely) bug in picking routers by
26180 bandwidth. Add a log message to confirm that it is in fact
26181 unlikely. Patch from lodger.
26182 - Backport a couple of memory leak fixes.
26183 - Backport miscellaneous cosmetic bugfixes.
26186 Changes in version 0.2.0.2-alpha - 2007-06-02
26187 o Major bugfixes on 0.2.0.1-alpha:
26188 - Fix an assertion failure related to servers without extra-info digests.
26189 Resolves bugs 441 and 442.
26191 o Minor features (directory):
26192 - Support "If-Modified-Since" when answering HTTP requests for
26193 directories, running-routers documents, and network-status documents.
26194 (There's no need to support it for router descriptors, since those
26195 are downloaded by descriptor digest.)
26197 o Minor build issues:
26198 - Clear up some MIPSPro compiler warnings.
26199 - When building from a tarball on a machine that happens to have SVK
26200 installed, report the micro-revision as whatever version existed
26201 in the tarball, not as "x".
26204 Changes in version 0.2.0.1-alpha - 2007-06-01
26205 This early development snapshot provides new features for people running
26206 Tor as both a client and a server (check out the new RelayBandwidth
26207 config options); lets Tor run as a DNS proxy; and generally moves us
26208 forward on a lot of fronts.
26210 o Major features, server usability:
26211 - New config options RelayBandwidthRate and RelayBandwidthBurst:
26212 a separate set of token buckets for relayed traffic. Right now
26213 relayed traffic is defined as answers to directory requests, and
26214 OR connections that don't have any local circuits on them.
26216 o Major features, client usability:
26217 - A client-side DNS proxy feature to replace the need for
26218 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
26219 for DNS requests on port 9999, use the Tor network to resolve them
26220 anonymously, and send the reply back like a regular DNS server.
26221 The code still only implements a subset of DNS.
26222 - Make PreferTunneledDirConns and TunnelDirConns work even when
26223 we have no cached directory info. This means Tor clients can now
26224 do all of their connections protected by TLS.
26226 o Major features, performance and efficiency:
26227 - Directory authorities accept and serve "extra info" documents for
26228 routers. These documents contain fields from router descriptors
26229 that aren't usually needed, and that use a lot of excess
26230 bandwidth. Once these fields are removed from router descriptors,
26231 the bandwidth savings should be about 60%. [Partially implements
26233 - Servers upload extra-info documents to any authority that accepts
26234 them. Authorities (and caches that have been configured to download
26235 extra-info documents) download them as needed. [Partially implements
26237 - Change the way that Tor buffers data that it is waiting to write.
26238 Instead of queueing data cells in an enormous ring buffer for each
26239 client->OR or OR->OR connection, we now queue cells on a separate
26240 queue for each circuit. This lets us use less slack memory, and
26241 will eventually let us be smarter about prioritizing different kinds
26243 - Use memory pools to allocate cells with better speed and memory
26244 efficiency, especially on platforms where malloc() is inefficient.
26245 - Stop reading on edge connections when their corresponding circuit
26246 buffers are full; start again as the circuits empty out.
26248 o Major features, other:
26249 - Add an HSAuthorityRecordStats option that hidden service authorities
26250 can use to track statistics of overall hidden service usage without
26251 logging information that would be very useful to an attacker.
26252 - Start work implementing multi-level keys for directory authorities:
26253 Add a standalone tool to generate key certificates. (Proposal 103.)
26256 - Directory authorities now call routers Stable if they have an
26257 uptime of at least 30 days, even if that's not the median uptime
26258 in the network. Implements proposal 107, suggested by Kevin Bauer
26261 o Minor fixes (resource management):
26262 - Count the number of open sockets separately from the number
26263 of active connection_t objects. This will let us avoid underusing
26264 our allocated connection limit.
26265 - We no longer use socket pairs to link an edge connection to an
26266 anonymous directory connection or a DirPort test connection.
26267 Instead, we track the link internally and transfer the data
26268 in-process. This saves two sockets per "linked" connection (at the
26269 client and at the server), and avoids the nasty Windows socketpair()
26271 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
26272 for every single inactive connection_t. Free items from the
26273 4k/16k-buffer free lists when they haven't been used for a while.
26275 o Minor features (build):
26276 - Make autoconf search for libevent, openssl, and zlib consistently.
26277 - Update deprecated macros in configure.in.
26278 - When warning about missing headers, tell the user to let us
26279 know if the compile succeeds anyway, so we can downgrade the
26281 - Include the current subversion revision as part of the version
26282 string: either fetch it directly if we're in an SVN checkout, do
26283 some magic to guess it if we're in an SVK checkout, or use
26284 the last-detected version if we're building from a .tar.gz.
26285 Use this version consistently in log messages.
26287 o Minor features (logging):
26288 - Always prepend "Bug: " to any log message about a bug.
26289 - Put a platform string (e.g. "Linux i686") in the startup log
26290 message, so when people paste just their logs, we know if it's
26291 OpenBSD or Windows or what.
26292 - When logging memory usage, break down memory used in buffers by
26295 o Minor features (directory system):
26296 - New config option V2AuthoritativeDirectory that all directory
26297 authorities should set. This will let future authorities choose
26298 not to serve V2 directory information.
26299 - Directory authorities allow multiple router descriptors and/or extra
26300 info documents to be uploaded in a single go. This will make
26301 implementing proposal 104 simpler.
26303 o Minor features (controller):
26304 - Add a new config option __DisablePredictedCircuits designed for
26305 use by the controller, when we don't want Tor to build any circuits
26307 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
26308 so we can exit from the middle of the circuit.
26309 - Implement "getinfo status/circuit-established".
26310 - Implement "getinfo status/version/..." so a controller can tell
26311 whether the current version is recommended, and whether any versions
26312 are good, and how many authorities agree. (Patch from shibz.)
26314 o Minor features (hidden services):
26315 - Allow multiple HiddenServicePort directives with the same virtual
26316 port; when they occur, the user is sent round-robin to one
26317 of the target ports chosen at random. Partially fixes bug 393 by
26318 adding limited ad-hoc round-robining.
26320 o Minor features (other):
26322 - Add a new AutomapHostsOnResolve option: when it is enabled, any
26323 resolve request for hosts matching a given pattern causes Tor to
26324 generate an internal virtual address mapping for that host. This
26325 allows DNSPort to work sensibly with hidden service users. By
26326 default, .exit and .onion addresses are remapped; the list of
26327 patterns can be reconfigured with AutomapHostsSuffixes.
26328 - Add an "-F" option to tor-resolve to force a resolve for a .onion
26329 address. Thanks to the AutomapHostsOnResolve option, this is no
26330 longer a completely silly thing to do.
26331 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
26332 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
26333 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
26334 minus 1 byte: the actual maximum declared bandwidth.
26336 o Removed features:
26337 - Removed support for the old binary "version 0" controller protocol.
26338 This has been deprecated since 0.1.1, and warnings have been issued
26339 since 0.1.2. When we encounter a v0 control message, we now send
26340 back an error and close the connection.
26341 - Remove the old "dns worker" server DNS code: it hasn't been default
26342 since 0.1.2.2-alpha, and all the servers seem to be using the new
26345 o Minor bugfixes (portability):
26346 - Even though Windows is equally happy with / and \ as path separators,
26347 try to use \ consistently on Windows and / consistently on Unix: it
26348 makes the log messages nicer.
26349 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
26350 - Read resolv.conf files correctly on platforms where read() returns
26351 partial results on small file reads.
26353 o Minor bugfixes (directory):
26354 - Correctly enforce that elements of directory objects do not appear
26355 more often than they are allowed to appear.
26356 - When we are reporting the DirServer line we just parsed, we were
26357 logging the second stanza of the key fingerprint, not the first.
26359 o Minor bugfixes (logging):
26360 - When we hit an EOF on a log (probably because we're shutting down),
26361 don't try to remove the log from the list: just mark it as
26362 unusable. (Bulletproofs against bug 222.)
26364 o Minor bugfixes (other):
26365 - In the exitlist script, only consider the most recently published
26366 server descriptor for each server. Also, when the user requests
26367 a list of servers that _reject_ connections to a given address,
26368 explicitly exclude the IPs that also have servers that accept
26369 connections to that address. (Resolves bug 405.)
26370 - Stop allowing hibernating servers to be "stable" or "fast".
26371 - On Windows, we were preventing other processes from reading
26372 cached-routers while Tor was running. (Reported by janbar)
26373 - Make the NodeFamilies config option work. (Reported by
26374 lodger -- it has never actually worked, even though we added it
26376 - Check return values from pthread_mutex functions.
26377 - Don't save non-general-purpose router descriptors to the disk cache,
26378 because we have no way of remembering what their purpose was when
26380 - Add even more asserts to hunt down bug 417.
26381 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
26382 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
26383 Add a log message to confirm that it is in fact unlikely.
26385 o Minor bugfixes (controller):
26386 - Make 'getinfo fingerprint' return a 551 error if we're not a
26387 server, so we match what the control spec claims we do. Reported
26389 - Fix a typo in an error message when extendcircuit fails that
26390 caused us to not follow the \r\n-based delimiter protocol. Reported
26393 o Code simplifications and refactoring:
26394 - Stop passing around circuit_t and crypt_path_t pointers that are
26395 implicit in other procedure arguments.
26396 - Drop the old code to choke directory connections when the
26397 corresponding OR connections got full: thanks to the cell queue
26398 feature, OR conns don't get full any more.
26399 - Make dns_resolve() handle attaching connections to circuits
26400 properly, so the caller doesn't have to.
26401 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
26402 - Keep the connection array as a dynamic smartlist_t, rather than as
26403 a fixed-sized array. This is important, as the number of connections
26404 is becoming increasingly decoupled from the number of sockets.
26407 Changes in version 0.1.2.14 - 2007-05-25
26408 Tor 0.1.2.14 changes the addresses of two directory authorities (this
26409 change especially affects those who serve or use hidden services),
26410 and fixes several other crash- and security-related bugs.
26412 o Directory authority changes:
26413 - Two directory authorities (moria1 and moria2) just moved to new
26414 IP addresses. This change will particularly affect those who serve
26415 or use hidden services.
26417 o Major bugfixes (crashes):
26418 - If a directory server runs out of space in the connection table
26419 as it's processing a begin_dir request, it will free the exit stream
26420 but leave it attached to the circuit, leading to unpredictable
26421 behavior. (Reported by seeess, fixes bug 425.)
26422 - Fix a bug in dirserv_remove_invalid() that would cause authorities
26423 to corrupt memory under some really unlikely scenarios.
26424 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
26425 - Avoid segfaults when reading from mmaped descriptor file. (Reported
26428 o Major bugfixes (security):
26429 - When choosing an entry guard for a circuit, avoid using guards
26430 that are in the same family as the chosen exit -- not just guards
26431 that are exactly the chosen exit. (Reported by lodger.)
26433 o Major bugfixes (resource management):
26434 - If a directory authority is down, skip it when deciding where to get
26435 networkstatus objects or descriptors. Otherwise we keep asking
26436 every 10 seconds forever. Fixes bug 384.
26437 - Count it as a failure if we fetch a valid network-status but we
26438 don't want to keep it. Otherwise we'll keep fetching it and keep
26439 not wanting to keep it. Fixes part of bug 422.
26440 - If all of our dirservers have given us bad or no networkstatuses
26441 lately, then stop hammering them once per minute even when we
26442 think they're failed. Fixes another part of bug 422.
26445 - Actually set the purpose correctly for descriptors inserted with
26446 purpose=controller.
26447 - When we have k non-v2 authorities in our DirServer config,
26448 we ignored the last k authorities in the list when updating our
26450 - Correctly back-off from requesting router descriptors that we are
26451 having a hard time downloading.
26452 - Read resolv.conf files correctly on platforms where read() returns
26453 partial results on small file reads.
26454 - Don't rebuild the entire router store every time we get 32K of
26455 routers: rebuild it when the journal gets very large, or when
26456 the gaps in the store get very large.
26459 - When routers publish SVN revisions in their router descriptors,
26460 authorities now include those versions correctly in networkstatus
26462 - Warn when using a version of libevent before 1.3b to run a server on
26463 OSX or BSD: these versions interact badly with userspace threads.
26466 Changes in version 0.1.2.13 - 2007-04-24
26467 This release features some major anonymity fixes, such as safer path
26468 selection; better client performance; faster bootstrapping, better
26469 address detection, and better DNS support for servers; write limiting as
26470 well as read limiting to make servers easier to run; and a huge pile of
26471 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
26473 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
26474 of the Freenode IRC network, remembering his patience and vision for
26475 free speech on the Internet.
26478 - Fix a memory leak when we ask for "all" networkstatuses and we
26479 get one we don't recognize.
26480 - Add more asserts to hunt down bug 417.
26481 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
26484 Changes in version 0.1.2.12-rc - 2007-03-16
26486 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
26487 directory information requested inside Tor connections (i.e. via
26488 begin_dir cells). It only triggered when the same connection was
26489 serving other data at the same time. Reported by seeess.
26492 - When creating a circuit via the controller, send a 'launched'
26493 event when we're done, so we follow the spec better.
26496 Changes in version 0.1.2.11-rc - 2007-03-15
26497 o Minor bugfixes (controller), reported by daejees:
26498 - Correct the control spec to match how the code actually responds
26499 to 'getinfo addr-mappings/*'.
26500 - The control spec described a GUARDS event, but the code
26501 implemented a GUARD event. Standardize on GUARD, but let people
26502 ask for GUARDS too.
26505 Changes in version 0.1.2.10-rc - 2007-03-07
26506 o Major bugfixes (Windows):
26507 - Do not load the NT services library functions (which may not exist)
26508 just to detect if we're a service trying to shut down. Now we run
26509 on Win98 and friends again.
26511 o Minor bugfixes (other):
26512 - Clarify a couple of log messages.
26513 - Fix a misleading socks5 error number.
26516 Changes in version 0.1.2.9-rc - 2007-03-02
26517 o Major bugfixes (Windows):
26518 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
26519 of the usual GCC "%llu". This prevents a bug when saving 64-bit
26520 int configuration values: the high-order 32 bits would get
26521 truncated. In particular, we were being bitten by the default
26522 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
26523 and maybe also bug 397.)
26525 o Minor bugfixes (performance):
26526 - Use OpenSSL's AES implementation on platforms where it's faster.
26527 This could save us as much as 10% CPU usage.
26529 o Minor bugfixes (server):
26530 - Do not rotate onion key immediately after setting it for the first
26533 o Minor bugfixes (directory authorities):
26534 - Stop calling servers that have been hibernating for a long time
26535 "stable". Also, stop letting hibernating or obsolete servers affect
26536 uptime and bandwidth cutoffs.
26537 - Stop listing hibernating servers in the v1 directory.
26539 o Minor bugfixes (hidden services):
26540 - Upload hidden service descriptors slightly less often, to reduce
26541 load on authorities.
26543 o Minor bugfixes (other):
26544 - Fix an assert that could trigger if a controller quickly set then
26545 cleared EntryNodes. Bug found by Udo van den Heuvel.
26546 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
26548 - Fix a potential race condition in the rpm installer. Found by
26550 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
26551 of 2 as indicating that the server is completely bad; it sometimes
26552 means that the server is just bad for the request in question. (may fix
26553 the last of bug 326.)
26554 - Disable encrypted directory connections when we don't have a server
26555 descriptor for the destination. We'll get this working again in
26559 Changes in version 0.1.2.8-beta - 2007-02-26
26560 o Major bugfixes (crashes):
26561 - Stop crashing when the controller asks us to resetconf more than
26562 one config option at once. (Vidalia 0.0.11 does this.)
26563 - Fix a crash that happened on Win98 when we're given command-line
26564 arguments: don't try to load NT service functions from advapi32.dll
26565 except when we need them. (Bug introduced in 0.1.2.7-alpha;
26567 - Fix a longstanding obscure crash bug that could occur when
26568 we run out of DNS worker processes. (Resolves bug 390.)
26570 o Major bugfixes (hidden services):
26571 - Correctly detect whether hidden service descriptor downloads are
26572 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
26574 o Major bugfixes (accounting):
26575 - When we start during an accounting interval before it's time to wake
26576 up, remember to wake up at the correct time. (May fix bug 342.)
26578 o Minor bugfixes (controller):
26579 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
26580 clear the corresponding on_circuit variable, and remember later
26581 that we don't need to send a redundant CLOSED event. Resolves part
26583 - Report events where a resolve succeeded or where we got a socks
26584 protocol error correctly, rather than calling both of them
26586 - Change reported stream target addresses to IP consistently when
26587 we finally get the IP from an exit node.
26588 - Send log messages to the controller even if they happen to be very
26591 o Minor bugfixes (other):
26592 - Display correct results when reporting which versions are
26593 recommended, and how recommended they are. (Resolves bug 383.)
26594 - Improve our estimates for directory bandwidth to be less random:
26595 guess that an unrecognized directory will have the average bandwidth
26596 from all known directories, not that it will have the average
26597 bandwidth from those directories earlier than it on the list.
26598 - If we start a server with ClientOnly 1, then set ClientOnly to 0
26599 and hup, stop triggering an assert based on an empty onion_key.
26600 - On platforms with no working mmap() equivalent, don't warn the
26601 user when cached-routers doesn't exist.
26602 - Warn the user when mmap() [or its equivalent] fails for some reason
26603 other than file-not-found.
26604 - Don't warn the user when cached-routers.new doesn't exist: that's
26605 perfectly fine when starting up for the first time.
26606 - When EntryNodes are configured, rebuild the guard list to contain,
26607 in order: the EntryNodes that were guards before; the rest of the
26608 EntryNodes; the nodes that were guards before.
26609 - Mask out all signals in sub-threads; only the libevent signal
26610 handler should be processing them. This should prevent some crashes
26611 on some machines using pthreads. (Patch from coderman.)
26612 - Fix switched arguments on memset in the implementation of
26613 tor_munmap() for systems with no mmap() call.
26614 - When Tor receives a router descriptor that it asked for, but
26615 no longer wants (because it has received fresh networkstatuses
26616 in the meantime), do not warn the user. Cache the descriptor if
26617 we're a cache; drop it if we aren't.
26618 - Make earlier entry guards _really_ get retried when the network
26620 - On a malformed DNS reply, always give an error to the corresponding
26622 - Build with recent libevents on platforms that do not define the
26623 nonstandard types "u_int8_t" and friends.
26625 o Minor features (controller):
26626 - Warn the user when an application uses the obsolete binary v0
26627 control protocol. We're planning to remove support for it during
26628 the next development series, so it's good to give people some
26630 - Add STREAM_BW events to report per-entry-stream bandwidth
26631 use. (Patch from Robert Hogan.)
26632 - Rate-limit SIGNEWNYM signals in response to controllers that
26633 impolitely generate them for every single stream. (Patch from
26634 mwenge; closes bug 394.)
26635 - Make REMAP stream events have a SOURCE (cache or exit), and
26636 make them generated in every case where we get a successful
26637 connected or resolved cell.
26639 o Minor bugfixes (performance):
26640 - Call router_have_min_dir_info half as often. (This is showing up in
26641 some profiles, but not others.)
26642 - When using GCC, make log_debug never get called at all, and its
26643 arguments never get evaluated, when no debug logs are configured.
26644 (This is showing up in some profiles, but not others.)
26647 - Remove some never-implemented options. Mark PathlenCoinWeight as
26649 - Implement proposal 106: Stop requiring clients to have well-formed
26650 certificates; stop checking nicknames in certificates. (Clients
26651 have certificates so that they can look like Tor servers, but in
26652 the future we might want to allow them to look like regular TLS
26653 clients instead. Nicknames in certificates serve no purpose other
26654 than making our protocol easier to recognize on the wire.)
26655 - Revise messages on handshake failure again to be even more clear about
26656 which are incoming connections and which are outgoing.
26657 - Discard any v1 directory info that's over 1 month old (for
26658 directories) or over 1 week old (for running-routers lists).
26659 - Do not warn when individual nodes in the configuration's EntryNodes,
26660 ExitNodes, etc are down: warn only when all possible nodes
26661 are down. (Fixes bug 348.)
26662 - Always remove expired routers and networkstatus docs before checking
26663 whether we have enough information to build circuits. (Fixes
26665 - Put a lower-bound on MaxAdvertisedBandwidth.
26668 Changes in version 0.1.2.7-alpha - 2007-02-06
26669 o Major bugfixes (rate limiting):
26670 - Servers decline directory requests much more aggressively when
26671 they're low on bandwidth. Otherwise they end up queueing more and
26672 more directory responses, which can't be good for latency.
26673 - But never refuse directory requests from local addresses.
26674 - Fix a memory leak when sending a 503 response for a networkstatus
26676 - Be willing to read or write on local connections (e.g. controller
26677 connections) even when the global rate limiting buckets are empty.
26678 - If our system clock jumps back in time, don't publish a negative
26679 uptime in the descriptor. Also, don't let the global rate limiting
26680 buckets go absurdly negative.
26681 - Flush local controller connection buffers periodically as we're
26682 writing to them, so we avoid queueing 4+ megabytes of data before
26685 o Major bugfixes (NT services):
26686 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
26687 command-line flag so that admins can override the default by saying
26688 "tor --service install --user "SomeUser"". This will not affect
26689 existing installed services. Also, warn the user that the service
26690 will look for its configuration file in the service user's
26691 %appdata% directory. (We can't do the 'hardwire the user's appdata
26692 directory' trick any more, since we may not have read access to that
26695 o Major bugfixes (other):
26696 - Previously, we would cache up to 16 old networkstatus documents
26697 indefinitely, if they came from nontrusted authorities. Now we
26698 discard them if they are more than 10 days old.
26699 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
26701 - Detect and reject malformed DNS responses containing circular
26703 - If exits are rare enough that we're not marking exits as guards,
26704 ignore exit bandwidth when we're deciding the required bandwidth
26706 - When we're handling a directory connection tunneled over Tor,
26707 don't fill up internal memory buffers with all the data we want
26708 to tunnel; instead, only add it if the OR connection that will
26709 eventually receive it has some room for it. (This can lead to
26710 slowdowns in tunneled dir connections; a better solution will have
26711 to wait for 0.2.0.)
26713 o Minor bugfixes (dns):
26714 - Add some defensive programming to eventdns.c in an attempt to catch
26715 possible memory-stomping bugs.
26716 - Detect and reject DNS replies containing IPv4 or IPv6 records with
26717 an incorrect number of bytes. (Previously, we would ignore the
26719 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
26720 in the correct order, and doesn't crash.
26721 - Free memory held in recently-completed DNS lookup attempts on exit.
26722 This was not a memory leak, but may have been hiding memory leaks.
26723 - Handle TTL values correctly on reverse DNS lookups.
26724 - Treat failure to parse resolv.conf as an error.
26726 o Minor bugfixes (other):
26727 - Fix crash with "tor --list-fingerprint" (reported by seeess).
26728 - When computing clock skew from directory HTTP headers, consider what
26729 time it was when we finished asking for the directory, not what
26731 - Expire socks connections if they spend too long waiting for the
26732 handshake to finish. Previously we would let them sit around for
26733 days, if the connecting application didn't close them either.
26734 - And if the socks handshake hasn't started, don't send a
26735 "DNS resolve socks failed" handshake reply; just close it.
26736 - Stop using C functions that OpenBSD's linker doesn't like.
26737 - Don't launch requests for descriptors unless we have networkstatuses
26738 from at least half of the authorities. This delays the first
26739 download slightly under pathological circumstances, but can prevent
26740 us from downloading a bunch of descriptors we don't need.
26741 - Do not log IPs with TLS failures for incoming TLS
26742 connections. (Fixes bug 382.)
26743 - If the user asks to use invalid exit nodes, be willing to use
26745 - Stop using the reserved ac_cv namespace in our configure script.
26746 - Call stat() slightly less often; use fstat() when possible.
26747 - Refactor the way we handle pending circuits when an OR connection
26748 completes or fails, in an attempt to fix a rare crash bug.
26749 - Only rewrite a conn's address based on X-Forwarded-For: headers
26750 if it's a parseable public IP address; and stop adding extra quotes
26751 to the resulting address.
26754 - Weight directory requests by advertised bandwidth. Now we can
26755 let servers enable write limiting but still allow most clients to
26756 succeed at their directory requests. (We still ignore weights when
26757 choosing a directory authority; I hope this is a feature.)
26760 - Create a new file ReleaseNotes which was the old ChangeLog. The
26761 new ChangeLog file now includes the summaries for all development
26763 - Check for addresses with invalid characters at the exit as well
26764 as at the client, and warn less verbosely when they fail. You can
26765 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
26766 - Adapt a patch from goodell to let the contrib/exitlist script
26767 take arguments rather than require direct editing.
26768 - Inform the server operator when we decide not to advertise a
26769 DirPort due to AccountingMax enabled or a low BandwidthRate. It
26770 was confusing Zax, so now we're hopefully more helpful.
26771 - Bring us one step closer to being able to establish an encrypted
26772 directory tunnel without knowing a descriptor first. Still not
26773 ready yet. As part of the change, now assume we can use a
26774 create_fast cell if we don't know anything about a router.
26775 - Allow exit nodes to use nameservers running on ports other than 53.
26776 - Servers now cache reverse DNS replies.
26777 - Add an --ignore-missing-torrc command-line option so that we can
26778 get the "use sensible defaults if the configuration file doesn't
26779 exist" behavior even when specifying a torrc location on the command
26782 o Minor features (controller):
26783 - Track reasons for OR connection failure; make these reasons
26784 available via the controller interface. (Patch from Mike Perry.)
26785 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
26786 can learn when clients are sending malformed hostnames to Tor.
26787 - Clean up documentation for controller status events.
26788 - Add a REMAP status to stream events to note that a stream's
26789 address has changed because of a cached address or a MapAddress
26793 Changes in version 0.1.2.6-alpha - 2007-01-09
26795 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
26796 connection handles more than 4 gigs in either direction, we crash.
26797 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
26798 advertised exit node, somebody might try to exit from us when
26799 we're bootstrapping and before we've built our descriptor yet.
26800 Refuse the connection rather than crashing.
26803 - Warn if we (as a server) find that we've resolved an address that we
26804 weren't planning to resolve.
26805 - Warn that using select() on any libevent version before 1.1 will be
26806 unnecessarily slow (even for select()).
26807 - Flush ERR-level controller status events just like we currently
26808 flush ERR-level log events, so that a Tor shutdown doesn't prevent
26809 the controller from learning about current events.
26811 o Minor features (more controller status events):
26812 - Implement EXTERNAL_ADDRESS server status event so controllers can
26813 learn when our address changes.
26814 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
26815 can learn when directories reject our descriptor.
26816 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
26817 can learn when a client application is speaking a non-socks protocol
26819 - Implement DANGEROUS_SOCKS client status event so controllers
26820 can learn when a client application is leaking DNS addresses.
26821 - Implement BUG general status event so controllers can learn when
26822 Tor is unhappy about its internal invariants.
26823 - Implement CLOCK_SKEW general status event so controllers can learn
26824 when Tor thinks the system clock is set incorrectly.
26825 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
26826 server status events so controllers can learn when their descriptors
26827 are accepted by a directory.
26828 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
26829 server status events so controllers can learn about Tor's progress in
26830 deciding whether it's reachable from the outside.
26831 - Implement BAD_LIBEVENT general status event so controllers can learn
26832 when we have a version/method combination in libevent that needs to
26834 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
26835 and DNS_USELESS server status events so controllers can learn
26836 about changes to DNS server status.
26838 o Minor features (directory):
26839 - Authorities no longer recommend exits as guards if this would shift
26840 too much load to the exit nodes.
26843 Changes in version 0.1.2.5-alpha - 2007-01-06
26845 - Enable write limiting as well as read limiting. Now we sacrifice
26846 capacity if we're pushing out lots of directory traffic, rather
26847 than overrunning the user's intended bandwidth limits.
26848 - Include TLS overhead when counting bandwidth usage; previously, we
26849 would count only the bytes sent over TLS, but not the bytes used
26851 - Support running the Tor service with a torrc not in the same
26852 directory as tor.exe and default to using the torrc located in
26853 the %appdata%\Tor\ of the user who installed the service. Patch
26855 - Servers now check for the case when common DNS requests are going to
26856 wildcarded addresses (i.e. all getting the same answer), and change
26857 their exit policy to reject *:* if it's happening.
26858 - Implement BEGIN_DIR cells, so we can connect to the directory
26859 server via TLS to do encrypted directory requests rather than
26860 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
26861 config options if you like.
26863 o Minor features (config and docs):
26864 - Start using the state file to store bandwidth accounting data:
26865 the bw_accounting file is now obsolete. We'll keep generating it
26866 for a while for people who are still using 0.1.2.4-alpha.
26867 - Try to batch changes to the state file so that we do as few
26868 disk writes as possible while still storing important things in
26870 - The state file and the bw_accounting file get saved less often when
26871 the AvoidDiskWrites config option is set.
26872 - Make PIDFile work on Windows (untested).
26873 - Add internal descriptions for a bunch of configuration options:
26874 accessible via controller interface and in comments in saved
26876 - Reject *:563 (NNTPS) in the default exit policy. We already reject
26877 NNTP by default, so this seems like a sensible addition.
26878 - Clients now reject hostnames with invalid characters. This should
26879 avoid some inadvertent info leaks. Add an option
26880 AllowNonRFC953Hostnames to disable this behavior, in case somebody
26881 is running a private network with hosts called @, !, and #.
26882 - Add a maintainer script to tell us which options are missing
26883 documentation: "make check-docs".
26884 - Add a new address-spec.txt document to describe our special-case
26885 addresses: .exit, .onion, and .noconnnect.
26887 o Minor features (DNS):
26888 - Ongoing work on eventdns infrastructure: now it has dns server
26889 and ipv6 support. One day Tor will make use of it.
26890 - Add client-side caching for reverse DNS lookups.
26891 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
26892 - When we change nameservers or IP addresses, reset and re-launch
26893 our tests for DNS hijacking.
26895 o Minor features (directory):
26896 - Authorities now specify server versions in networkstatus. This adds
26897 about 2% to the size of compressed networkstatus docs, and allows
26898 clients to tell which servers support BEGIN_DIR and which don't.
26899 The implementation is forward-compatible with a proposed future
26900 protocol version scheme not tied to Tor versions.
26901 - DirServer configuration lines now have an orport= option so
26902 clients can open encrypted tunnels to the authorities without
26903 having downloaded their descriptors yet. Enabled for moria1,
26904 moria2, tor26, and lefkada now in the default configuration.
26905 - Directory servers are more willing to send a 503 "busy" if they
26906 are near their write limit, especially for v1 directory requests.
26907 Now they can use their limited bandwidth for actual Tor traffic.
26908 - Clients track responses with status 503 from dirservers. After a
26909 dirserver has given us a 503, we try not to use it until an hour has
26910 gone by, or until we have no dirservers that haven't given us a 503.
26911 - When we get a 503 from a directory, and we're not a server, we don't
26912 count the failure against the total number of failures allowed
26913 for the thing we're trying to download.
26914 - Report X-Your-Address-Is correctly from tunneled directory
26915 connections; don't report X-Your-Address-Is when it's an internal
26916 address; and never believe reported remote addresses when they're
26918 - Protect against an unlikely DoS attack on directory servers.
26919 - Add a BadDirectory flag to network status docs so that authorities
26920 can (eventually) tell clients about caches they believe to be
26923 o Minor features (controller):
26924 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
26925 - Reimplement GETINFO so that info/names stays in sync with the
26927 - Implement "GETINFO fingerprint".
26928 - Implement "SETEVENTS GUARD" so controllers can get updates on
26929 entry guard status as it changes.
26931 o Minor features (clean up obsolete pieces):
26932 - Remove some options that have been deprecated since at least
26933 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
26934 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
26935 to set log options.
26936 - We no longer look for identity and onion keys in "identity.key" and
26937 "onion.key" -- these were replaced by secret_id_key and
26938 secret_onion_key in 0.0.8pre1.
26939 - We no longer require unrecognized directory entries to be
26942 o Major bugfixes (security):
26943 - Stop sending the HttpProxyAuthenticator string to directory
26944 servers when directory connections are tunnelled through Tor.
26945 - Clients no longer store bandwidth history in the state file.
26946 - Do not log introduction points for hidden services if SafeLogging
26948 - When generating bandwidth history, round down to the nearest
26949 1k. When storing accounting data, round up to the nearest 1k.
26950 - When we're running as a server, remember when we last rotated onion
26951 keys, so that we will rotate keys once they're a week old even if
26952 we never stay up for a week ourselves.
26954 o Major bugfixes (other):
26955 - Fix a longstanding bug in eventdns that prevented the count of
26956 timed-out resolves from ever being reset. This bug caused us to
26957 give up on a nameserver the third time it timed out, and try it
26958 10 seconds later... and to give up on it every time it timed out
26960 - Take out the '5 second' timeout from the connection retry
26961 schedule. Now the first connect attempt will wait a full 10
26962 seconds before switching to a new circuit. Perhaps this will help
26963 a lot. Based on observations from Mike Perry.
26964 - Fix a bug on the Windows implementation of tor_mmap_file() that
26965 would prevent the cached-routers file from ever loading. Reported
26969 - Fix an assert failure when a directory authority sets
26970 AuthDirRejectUnlisted and then receives a descriptor from an
26971 unlisted router. Reported by seeess.
26972 - Avoid a double-free when parsing malformed DirServer lines.
26973 - Fix a bug when a BSD-style PF socket is first used. Patch from
26975 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
26976 to resolve an address at a given exit node even when they ask for
26978 - Servers no longer ever list themselves in their "family" line,
26979 even if configured to do so. This makes it easier to configure
26980 family lists conveniently.
26981 - When running as a server, don't fall back to 127.0.0.1 when no
26982 nameservers are configured in /etc/resolv.conf; instead, make the
26983 user fix resolv.conf or specify nameservers explicitly. (Resolves
26985 - Stop accepting certain malformed ports in configured exit policies.
26986 - Don't re-write the fingerprint file every restart, unless it has
26988 - Stop warning when a single nameserver fails: only warn when _all_ of
26989 our nameservers have failed. Also, when we only have one nameserver,
26990 raise the threshold for deciding that the nameserver is dead.
26991 - Directory authorities now only decide that routers are reachable
26992 if their identity keys are as expected.
26993 - When the user uses bad syntax in the Log config line, stop
26994 suggesting other bad syntax as a replacement.
26995 - Correctly detect ipv6 DNS capability on OpenBSD.
26997 o Minor bugfixes (controller):
26998 - Report the circuit number correctly in STREAM CLOSED events. Bug
26999 reported by Mike Perry.
27000 - Do not report bizarre values for results of accounting GETINFOs
27001 when the last second's write or read exceeds the allotted bandwidth.
27002 - Report "unrecognized key" rather than an empty string when the
27003 controller tries to fetch a networkstatus that doesn't exist.
27006 Changes in version 0.1.1.26 - 2006-12-14
27007 o Security bugfixes:
27008 - Stop sending the HttpProxyAuthenticator string to directory
27009 servers when directory connections are tunnelled through Tor.
27010 - Clients no longer store bandwidth history in the state file.
27011 - Do not log introduction points for hidden services if SafeLogging
27015 - Fix an assert failure when a directory authority sets
27016 AuthDirRejectUnlisted and then receives a descriptor from an
27017 unlisted router (reported by seeess).
27020 Changes in version 0.1.2.4-alpha - 2006-12-03
27022 - Add support for using natd; this allows FreeBSDs earlier than
27023 5.1.2 to have ipfw send connections through Tor without using
27024 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
27027 - Make all connections to addresses of the form ".noconnect"
27028 immediately get closed. This lets application/controller combos
27029 successfully test whether they're talking to the same Tor by
27030 watching for STREAM events.
27031 - Make cross.sh cross-compilation script work even when autogen.sh
27032 hasn't been run. (Patch from Michael Mohr.)
27033 - Statistics dumped by -USR2 now include a breakdown of public key
27034 operations, for profiling.
27037 - Fix a major leak when directory authorities parse their
27038 approved-routers list, a minor memory leak when we fail to pick
27039 an exit node, and a few rare leaks on errors.
27040 - Handle TransPort connections even when the server sends data before
27041 the client sends data. Previously, the connection would just hang
27042 until the client sent data. (Patch from tup based on patch from
27044 - Avoid assert failure when our cached-routers file is empty on
27048 - Don't log spurious warnings when we see a circuit close reason we
27049 don't recognize; it's probably just from a newer version of Tor.
27050 - Have directory authorities allow larger amounts of drift in uptime
27051 without replacing the server descriptor: previously, a server that
27052 restarted every 30 minutes could have 48 "interesting" descriptors
27054 - Start linking to the Tor specification and Tor reference manual
27055 correctly in the Windows installer.
27056 - Add Vidalia to the OS X uninstaller script, so when we uninstall
27057 Tor/Privoxy we also uninstall Vidalia.
27058 - Resume building on Irix64, and fix a lot of warnings from its
27059 MIPSpro C compiler.
27060 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
27061 when we're running as a client.
27064 Changes in version 0.1.1.25 - 2006-11-04
27066 - When a client asks us to resolve (rather than connect to)
27067 an address, and we have a cached answer, give them the cached
27068 answer. Previously, we would give them no answer at all.
27069 - We were building exactly the wrong circuits when we predict
27070 hidden service requirements, meaning Tor would have to build all
27071 its circuits on demand.
27072 - If none of our live entry guards have a high uptime, but we
27073 require a guard with a high uptime, try adding a new guard before
27074 we give up on the requirement. This patch should make long-lived
27075 connections more stable on average.
27076 - When testing reachability of our DirPort, don't launch new
27077 tests when there's already one in progress -- unreachable
27078 servers were stacking up dozens of testing streams.
27080 o Security bugfixes:
27081 - When the user sends a NEWNYM signal, clear the client-side DNS
27082 cache too. Otherwise we continue to act on previous information.
27085 - Avoid a memory corruption bug when creating a hash table for
27087 - Avoid possibility of controller-triggered crash when misusing
27088 certain commands from a v0 controller on platforms that do not
27089 handle printf("%s",NULL) gracefully.
27090 - Avoid infinite loop on unexpected controller input.
27091 - Don't log spurious warnings when we see a circuit close reason we
27092 don't recognize; it's probably just from a newer version of Tor.
27093 - Add Vidalia to the OS X uninstaller script, so when we uninstall
27094 Tor/Privoxy we also uninstall Vidalia.
27097 Changes in version 0.1.2.3-alpha - 2006-10-29
27099 - Prepare for servers to publish descriptors less often: never
27100 discard a descriptor simply for being too old until either it is
27101 recommended by no authorities, or until we get a better one for
27102 the same router. Make caches consider retaining old recommended
27103 routers for even longer.
27104 - If most authorities set a BadExit flag for a server, clients
27105 don't think of it as a general-purpose exit. Clients only consider
27106 authorities that advertise themselves as listing bad exits.
27107 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
27108 headers for content, so that we can work better in the presence of
27109 caching HTTP proxies.
27110 - Allow authorities to list nodes as bad exits by fingerprint or by
27113 o Minor features, controller:
27114 - Add a REASON field to CIRC events; for backward compatibility, this
27115 field is sent only to controllers that have enabled the extended
27116 event format. Also, add additional reason codes to explain why
27117 a given circuit has been destroyed or truncated. (Patches from
27119 - Add a REMOTE_REASON field to extended CIRC events to tell the
27120 controller about why a remote OR told us to close a circuit.
27121 - Stream events also now have REASON and REMOTE_REASON fields,
27122 working much like those for circuit events.
27123 - There's now a GETINFO ns/... field so that controllers can ask Tor
27124 about the current status of a router.
27125 - A new event type "NS" to inform a controller when our opinion of
27126 a router's status has changed.
27127 - Add a GETINFO events/names and GETINFO features/names so controllers
27128 can tell which events and features are supported.
27129 - A new CLEARDNSCACHE signal to allow controllers to clear the
27130 client-side DNS cache without expiring circuits.
27132 o Security bugfixes:
27133 - When the user sends a NEWNYM signal, clear the client-side DNS
27134 cache too. Otherwise we continue to act on previous information.
27137 - Avoid sending junk to controllers or segfaulting when a controller
27138 uses EVENT_NEW_DESC with verbose nicknames.
27139 - Stop triggering asserts if the controller tries to extend hidden
27140 service circuits (reported by mwenge).
27141 - Avoid infinite loop on unexpected controller input.
27142 - When the controller does a "GETINFO network-status", tell it
27143 about even those routers whose descriptors are very old, and use
27144 long nicknames where appropriate.
27145 - Change NT service functions to be loaded on demand. This lets us
27146 build with MinGW without breaking Tor for Windows 98 users.
27147 - Do DirPort reachability tests less often, since a single test
27148 chews through many circuits before giving up.
27149 - In the hidden service example in torrc.sample, stop recommending
27150 esoteric and discouraged hidden service options.
27151 - When stopping an NT service, wait up to 10 sec for it to actually
27152 stop. Patch from Matt Edman; resolves bug 295.
27153 - Fix handling of verbose nicknames with ORCONN controller events:
27154 make them show up exactly when requested, rather than exactly when
27156 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
27157 printing a duplicate "$" in the keys we send (reported by mwenge).
27158 - Correctly set maximum connection limit on Cygwin. (This time
27160 - Try to detect Windows correctly when cross-compiling.
27161 - Detect the size of the routers file correctly even if it is
27162 corrupted (on systems without mmap) or not page-aligned (on systems
27163 with mmap). This bug was harmless.
27164 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
27165 to open a stream fails; now we do in more cases. This should
27166 make clients able to find a good exit faster in some cases, since
27167 unhandleable requests will now get an error rather than timing out.
27168 - Resolve two memory leaks when rebuilding the on-disk router cache
27169 (reported by fookoowa).
27170 - Clean up minor code warnings suggested by the MIPSpro C compiler,
27171 and reported by some Centos users.
27172 - Controller signals now work on non-Unix platforms that don't define
27173 SIGUSR1 and SIGUSR2 the way we expect.
27174 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
27175 values before failing, and always enables eventdns.
27176 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
27177 Try to fix this in configure.in by checking for most functions
27178 before we check for libevent.
27181 Changes in version 0.1.2.2-alpha - 2006-10-07
27183 - Make our async eventdns library on-by-default for Tor servers,
27184 and plan to deprecate the separate dnsworker threads.
27185 - Add server-side support for "reverse" DNS lookups (using PTR
27186 records so clients can determine the canonical hostname for a given
27187 IPv4 address). Only supported by servers using eventdns; servers
27188 now announce in their descriptors whether they support eventdns.
27189 - Specify and implement client-side SOCKS5 interface for reverse DNS
27190 lookups (see doc/socks-extensions.txt).
27191 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
27192 connect to directory servers through Tor. Previously, clients needed
27193 to find Tor exits to make private connections to directory servers.
27194 - Avoid choosing Exit nodes for entry or middle hops when the
27195 total bandwidth available from non-Exit nodes is much higher than
27196 the total bandwidth available from Exit nodes.
27197 - Workaround for name servers (like Earthlink's) that hijack failing
27198 DNS requests and replace the no-such-server answer with a "helpful"
27199 redirect to an advertising-driven search portal. Also work around
27200 DNS hijackers who "helpfully" decline to hijack known-invalid
27201 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
27202 lets you turn it off.
27203 - Send out a burst of long-range padding cells once we've established
27204 that we're reachable. Spread them over 4 circuits, so hopefully
27205 a few will be fast. This exercises our bandwidth and bootstraps
27206 us into the directory more quickly.
27208 o New/improved config options:
27209 - Add new config option "ResolvConf" to let the server operator
27210 choose an alternate resolve.conf file when using eventdns.
27211 - Add an "EnforceDistinctSubnets" option to control our "exclude
27212 servers on the same /16" behavior. It's still on by default; this
27213 is mostly for people who want to operate private test networks with
27214 all the machines on the same subnet.
27215 - If one of our entry guards is on the ExcludeNodes list, or the
27216 directory authorities don't think it's a good guard, treat it as
27217 if it were unlisted: stop using it as a guard, and throw it off
27218 the guards list if it stays that way for a long time.
27219 - Allow directory authorities to be marked separately as authorities
27220 for the v1 directory protocol, the v2 directory protocol, and
27221 as hidden service directories, to make it easier to retire old
27222 authorities. V1 authorities should set "HSAuthoritativeDir 1"
27223 to continue being hidden service authorities too.
27224 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
27226 o Minor features, controller:
27227 - Fix CIRC controller events so that controllers can learn the
27228 identity digests of non-Named servers used in circuit paths.
27229 - Let controllers ask for more useful identifiers for servers. Instead
27230 of learning identity digests for un-Named servers and nicknames
27231 for Named servers, the new identifiers include digest, nickname,
27232 and indication of Named status. Off by default; see control-spec.txt
27233 for more information.
27234 - Add a "getinfo address" controller command so it can display Tor's
27235 best guess to the user.
27236 - New controller event to alert the controller when our server
27237 descriptor has changed.
27238 - Give more meaningful errors on controller authentication failure.
27240 o Minor features, other:
27241 - When asked to resolve a hostname, don't use non-exit servers unless
27242 requested to do so. This allows servers with broken DNS to be
27243 useful to the network.
27244 - Divide eventdns log messages into warn and info messages.
27245 - Reserve the nickname "Unnamed" for routers that can't pick
27246 a hostname: any router can call itself Unnamed; directory
27247 authorities will never allocate Unnamed to any particular router;
27248 clients won't believe that any router is the canonical Unnamed.
27249 - Only include function names in log messages for info/debug messages.
27250 For notice/warn/err, the content of the message should be clear on
27251 its own, and printing the function name only confuses users.
27252 - Avoid some false positives during reachability testing: don't try
27253 to test via a server that's on the same /24 as us.
27254 - If we fail to build a circuit to an intended enclave, and it's
27255 not mandatory that we use that enclave, stop wanting it.
27256 - When eventdns is enabled, allow multithreaded builds on NetBSD and
27257 OpenBSD. (We had previously disabled threads on these platforms
27258 because they didn't have working thread-safe resolver functions.)
27260 o Major bugfixes, anonymity/security:
27261 - If a client asked for a server by name, and there's a named server
27262 in our network-status but we don't have its descriptor yet, we
27263 could return an unnamed server instead.
27264 - Fix NetBSD bug that could allow someone to force uninitialized RAM
27265 to be sent to a server's DNS resolver. This only affects NetBSD
27266 and other platforms that do not bounds-check tolower().
27267 - Reject (most) attempts to use Tor circuits with length one. (If
27268 many people start using Tor as a one-hop proxy, exit nodes become
27269 a more attractive target for compromise.)
27270 - Just because your DirPort is open doesn't mean people should be
27271 able to remotely teach you about hidden service descriptors. Now
27272 only accept rendezvous posts if you've got HSAuthoritativeDir set.
27274 o Major bugfixes, other:
27275 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
27276 - When a client asks the server to resolve (not connect to)
27277 an address, and it has a cached answer, give them the cached answer.
27278 Previously, the server would give them no answer at all.
27279 - Allow really slow clients to not hang up five minutes into their
27280 directory downloads (suggested by Adam J. Richter).
27281 - We were building exactly the wrong circuits when we anticipated
27282 hidden service requirements, meaning Tor would have to build all
27283 its circuits on demand.
27284 - Avoid crashing when we mmap a router cache file of size 0.
27285 - When testing reachability of our DirPort, don't launch new
27286 tests when there's already one in progress -- unreachable
27287 servers were stacking up dozens of testing streams.
27289 o Minor bugfixes, correctness:
27290 - If we're a directory mirror and we ask for "all" network status
27291 documents, we would discard status documents from authorities
27292 we don't recognize.
27293 - Avoid a memory corruption bug when creating a hash table for
27295 - Avoid controller-triggered crash when misusing certain commands
27296 from a v0 controller on platforms that do not handle
27297 printf("%s",NULL) gracefully.
27298 - Don't crash when a controller sends a third argument to an
27299 "extendcircuit" request.
27300 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
27301 response; fix error code when "getinfo dir/status/" fails.
27302 - Avoid crash when telling controller stream-status and a stream
27304 - Patch from Adam Langley to fix assert() in eventdns.c.
27305 - Fix a debug log message in eventdns to say "X resolved to Y"
27306 instead of "X resolved to X".
27307 - Make eventdns give strings for DNS errors, not just error numbers.
27308 - Track unreachable entry guards correctly: don't conflate
27309 'unreachable by us right now' with 'listed as down by the directory
27310 authorities'. With the old code, if a guard was unreachable by
27311 us but listed as running, it would clog our guard list forever.
27312 - Behave correctly in case we ever have a network with more than
27313 2GB/s total advertised capacity.
27314 - Make TrackExitHosts case-insensitive, and fix the behavior of
27315 ".suffix" TrackExitHosts items to avoid matching in the middle of
27317 - Finally fix the openssl warnings from newer gccs that believe that
27318 ignoring a return value is okay, but casting a return value and
27319 then ignoring it is a sign of madness.
27320 - Prevent the contrib/exitlist script from printing the same
27321 result more than once.
27322 - Patch from Steve Hildrey: Generate network status correctly on
27323 non-versioning dirservers.
27324 - Don't listen to the X-Your-Address-Is hint if you did the lookup
27325 via Tor; otherwise you'll think you're the exit node's IP address.
27327 o Minor bugfixes, performance:
27328 - Two small performance improvements on parsing descriptors.
27329 - Major performance improvement on inserting descriptors: change
27330 algorithm from O(n^2) to O(n).
27331 - Make the common memory allocation path faster on machines where
27332 malloc(0) returns a pointer.
27333 - Start remembering X-Your-Address-Is directory hints even if you're
27334 a client, so you can become a server more smoothly.
27335 - Avoid duplicate entries on MyFamily line in server descriptor.
27337 o Packaging, features:
27338 - Remove architecture from OS X builds. The official builds are
27339 now universal binaries.
27340 - The Debian package now uses --verify-config when (re)starting,
27341 to distinguish configuration errors from other errors.
27342 - Update RPMs to require libevent 1.1b.
27344 o Packaging, bugfixes:
27345 - Patches so Tor builds with MinGW on Windows.
27346 - Patches so Tor might run on Cygwin again.
27347 - Resume building on non-gcc compilers and ancient gcc. Resume
27348 building with the -O0 compile flag. Resume building cleanly on
27350 - Run correctly on OS X platforms with case-sensitive filesystems.
27351 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
27352 - Add autoconf checks so Tor can build on Solaris x86 again.
27355 - Documented (and renamed) ServerDNSSearchDomains and
27356 ServerDNSResolvConfFile options.
27357 - Be clearer that the *ListenAddress directives can be repeated
27361 Changes in version 0.1.1.24 - 2006-09-29
27363 - Allow really slow clients to not hang up five minutes into their
27364 directory downloads (suggested by Adam J. Richter).
27365 - Fix major performance regression from 0.1.0.x: instead of checking
27366 whether we have enough directory information every time we want to
27367 do something, only check when the directory information has changed.
27368 This should improve client CPU usage by 25-50%.
27369 - Don't crash if, after a server has been running for a while,
27370 it can't resolve its hostname.
27373 - Allow Tor to start when RunAsDaemon is set but no logs are set.
27374 - Don't crash when the controller receives a third argument to an
27375 "extendcircuit" request.
27376 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
27377 response; fix error code when "getinfo dir/status/" fails.
27378 - Fix configure.in to not produce broken configure files with
27379 more recent versions of autoconf. Thanks to Clint for his auto*
27381 - Fix security bug on NetBSD that could allow someone to force
27382 uninitialized RAM to be sent to a server's DNS resolver. This
27383 only affects NetBSD and other platforms that do not bounds-check
27385 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
27386 methods: these are known to be buggy.
27387 - If we're a directory mirror and we ask for "all" network status
27388 documents, we would discard status documents from authorities
27389 we don't recognize.
27392 Changes in version 0.1.2.1-alpha - 2006-08-27
27394 - Add "eventdns" async dns library from Adam Langley, tweaked to
27395 build on OSX and Windows. Only enabled if you pass the
27396 --enable-eventdns argument to configure.
27397 - Allow servers with no hostname or IP address to learn their
27398 IP address by asking the directory authorities. This code only
27399 kicks in when you would normally have exited with a "no address"
27400 error. Nothing's authenticated, so use with care.
27401 - Rather than waiting a fixed amount of time between retrying
27402 application connections, we wait only 5 seconds for the first,
27403 10 seconds for the second, and 15 seconds for each retry after
27404 that. Hopefully this will improve the expected user experience.
27405 - Patch from Tup to add support for transparent AP connections:
27406 this basically bundles the functionality of trans-proxy-tor
27407 into the Tor mainline. Now hosts with compliant pf/netfilter
27408 implementations can redirect TCP connections straight to Tor
27409 without diverting through SOCKS. Needs docs.
27410 - Busy directory servers save lots of memory by spooling server
27411 descriptors, v1 directories, and v2 networkstatus docs to buffers
27412 as needed rather than en masse. Also mmap the cached-routers
27413 files, so we don't need to keep the whole thing in memory too.
27414 - Automatically avoid picking more than one node from the same
27415 /16 network when constructing a circuit.
27416 - Revise and clean up the torrc.sample that we ship with; add
27417 a section for BandwidthRate and BandwidthBurst.
27420 - Split circuit_t into origin_circuit_t and or_circuit_t, and
27421 split connection_t into edge, or, dir, control, and base structs.
27422 These will save quite a bit of memory on busy servers, and they'll
27423 also help us track down bugs in the code and bugs in the spec.
27424 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
27425 or later. Log when we are doing this, so we can diagnose it when
27426 it fails. (Also, recommend libevent 1.1b for kqueue and
27427 win32 methods; deprecate libevent 1.0b harder; make libevent
27428 recommendation system saner.)
27429 - Start being able to build universal binaries on OS X (thanks
27431 - Export the default exit policy via the control port, so controllers
27432 don't need to guess what it is / will be later.
27433 - Add a man page entry for ProtocolWarnings.
27434 - Add TestVia config option to the man page.
27435 - Remove even more protocol-related warnings from Tor server logs,
27436 such as bad TLS handshakes and malformed begin cells.
27437 - Stop fetching descriptors if you're not a dir mirror and you
27438 haven't tried to establish any circuits lately. [This currently
27439 causes some dangerous behavior, because when you start up again
27440 you'll use your ancient server descriptors.]
27441 - New DirPort behavior: if you have your dirport set, you download
27442 descriptors aggressively like a directory mirror, whether or not
27443 your ORPort is set.
27444 - Get rid of the router_retry_connections notion. Now routers
27445 no longer try to rebuild long-term connections to directory
27446 authorities, and directory authorities no longer try to rebuild
27447 long-term connections to all servers. We still don't hang up
27448 connections in these two cases though -- we need to look at it
27449 more carefully to avoid flapping, and we likely need to wait til
27450 0.1.1.x is obsolete.
27451 - Drop compatibility with obsolete Tors that permit create cells
27452 to have the wrong circ_id_type.
27453 - Re-enable per-connection rate limiting. Get rid of the "OP
27454 bandwidth" concept. Lay groundwork for "bandwidth classes" --
27455 separate global buckets that apply depending on what sort of conn
27457 - Start publishing one minute or so after we find our ORPort
27458 to be reachable. This will help reduce the number of descriptors
27459 we have for ourselves floating around, since it's quite likely
27460 other things (e.g. DirPort) will change during that minute too.
27461 - Fork the v1 directory protocol into its own spec document,
27462 and mark dir-spec.txt as the currently correct (v2) spec.
27465 - When we find our DirPort to be reachable, publish a new descriptor
27466 so we'll tell the world (reported by pnx).
27467 - Publish a new descriptor after we hup/reload. This is important
27468 if our config has changed such that we'll want to start advertising
27469 our DirPort now, etc.
27470 - Allow Tor to start when RunAsDaemon is set but no logs are set.
27471 - When we have a state file we cannot parse, tell the user and
27472 move it aside. Now we avoid situations where the user starts
27473 Tor in 1904, Tor writes a state file with that timestamp in it,
27474 the user fixes her clock, and Tor refuses to start.
27475 - Fix configure.in to not produce broken configure files with
27476 more recent versions of autoconf. Thanks to Clint for his auto*
27478 - "tor --verify-config" now exits with -1(255) or 0 depending on
27479 whether the config options are bad or good.
27480 - Resolve bug 321 when using dnsworkers: append a period to every
27481 address we resolve at the exit node, so that we do not accidentally
27482 pick up local addresses, and so that failing searches are retried
27483 in the resolver search domains. (This is already solved for
27484 eventdns.) (This breaks Blossom servers for now.)
27485 - If we are using an exit enclave and we can't connect, e.g. because
27486 its webserver is misconfigured to not listen on localhost, then
27487 back off and try connecting from somewhere else before we fail.
27490 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
27491 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
27492 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
27493 when the IP address is mapped through MapAddress to a hostname.
27494 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
27495 useless IPv6 DNS resolves.
27496 - Patch suggested by Karsten Loesing: respond to SIGNAL command
27497 before we execute the signal, in case the signal shuts us down.
27498 - Clean up AllowInvalidNodes man page entry.
27499 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
27500 - Add more asserts to track down an assert error on a windows Tor
27501 server with connection_add being called with socket == -1.
27502 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
27503 - Fix misleading log messages: an entry guard that is "unlisted",
27504 as well as not known to be "down" (because we've never heard
27505 of it), is not therefore "up".
27506 - Remove code to special-case "-cvs" ending, since it has not
27507 actually mattered since 0.0.9.
27508 - Make our socks5 handling more robust to broken socks clients:
27509 throw out everything waiting on the buffer in between socks
27510 handshake phases, since they can't possibly (so the theory
27511 goes) have predicted what we plan to respond to them.
27514 Changes in version 0.1.1.23 - 2006-07-30
27516 - Fast Tor servers, especially exit nodes, were triggering asserts
27517 due to a bug in handling the list of pending DNS resolves. Some
27518 bugs still remain here; we're hunting them.
27519 - Entry guards could crash clients by sending unexpected input.
27520 - More fixes on reachability testing: if you find yourself reachable,
27521 then don't ever make any client requests (so you stop predicting
27522 circuits), then hup or have your clock jump, then later your IP
27523 changes, you won't think circuits are working, so you won't try to
27524 test reachability, so you won't publish.
27527 - Avoid a crash if the controller does a resetconf firewallports
27528 and then a setconf fascistfirewall=1.
27529 - Avoid an integer underflow when the dir authority decides whether
27530 a router is stable: we might wrongly label it stable, and compute
27531 a slightly wrong median stability, when a descriptor is published
27533 - Fix a place where we might trigger an assert if we can't build our
27534 own server descriptor yet.
27537 Changes in version 0.1.1.22 - 2006-07-05
27539 - Fix a big bug that was causing servers to not find themselves
27540 reachable if they changed IP addresses. Since only 0.1.1.22+
27541 servers can do reachability testing correctly, now we automatically
27542 make sure to test via one of these.
27543 - Fix to allow clients and mirrors to learn directory info from
27544 descriptor downloads that get cut off partway through.
27545 - Directory authorities had a bug in deciding if a newly published
27546 descriptor was novel enough to make everybody want a copy -- a few
27547 servers seem to be publishing new descriptors many times a minute.
27549 - Fix a rare bug that was causing some servers to complain about
27550 "closing wedged cpuworkers" and skip some circuit create requests.
27551 - Make the Exit flag in directory status documents actually work.
27554 Changes in version 0.1.1.21 - 2006-06-10
27555 o Crash and assert fixes from 0.1.1.20:
27556 - Fix a rare crash on Tor servers that have enabled hibernation.
27557 - Fix a seg fault on startup for Tor networks that use only one
27558 directory authority.
27559 - Fix an assert from a race condition that occurs on Tor servers
27560 while exiting, where various threads are trying to log that they're
27561 exiting, and delete the logs, at the same time.
27562 - Make our unit tests pass again on certain obscure platforms.
27565 - Add support for building SUSE RPM packages.
27566 - Speed up initial bootstrapping for clients: if we are making our
27567 first ever connection to any entry guard, then don't mark it down
27569 - When only one Tor server in the network is labelled as a guard,
27570 and we've already picked him, we would cycle endlessly picking him
27571 again, being unhappy about it, etc. Now we specifically exclude
27572 current guards when picking a new guard.
27573 - Servers send create cells more reliably after the TLS connection
27574 is established: we were sometimes forgetting to send half of them
27575 when we had more than one pending.
27576 - If we get a create cell that asks us to extend somewhere, but the
27577 Tor server there doesn't match the expected digest, we now send
27578 a destroy cell back, rather than silently doing nothing.
27579 - Make options->RedirectExit work again.
27580 - Make cookie authentication for the controller work again.
27581 - Stop being picky about unusual characters in the arguments to
27582 mapaddress. It's none of our business.
27583 - Add a new config option "TestVia" that lets you specify preferred
27584 middle hops to use for test circuits. Perhaps this will let me
27585 debug the reachability problems better.
27587 o Log / documentation fixes:
27588 - If we're a server and some peer has a broken TLS certificate, don't
27589 log about it unless ProtocolWarnings is set, i.e., we want to hear
27590 about protocol violations by others.
27591 - Fix spelling of VirtualAddrNetwork in man page.
27592 - Add a better explanation at the top of the autogenerated torrc file
27593 about what happened to our old torrc.
27596 Changes in version 0.1.1.20 - 2006-05-23
27598 - Downgrade a log severity where servers complain that they're
27600 - Avoid a compile warning on FreeBSD.
27601 - Remove string size limit on NEWDESC messages; solve bug 291.
27602 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
27603 more thoroughly when we're running on windows.
27606 Changes in version 0.1.1.19-rc - 2006-05-03
27608 - Regenerate our local descriptor if it's dirty and we try to use
27609 it locally (e.g. if it changes during reachability detection).
27610 - If we setconf our ORPort to 0, we continued to listen on the
27611 old ORPort and receive connections.
27612 - Avoid a second warning about machine/limits.h on Debian
27614 - Be willing to add our own routerinfo into the routerlist.
27615 Now authorities will include themselves in their directories
27616 and network-statuses.
27617 - Stop trying to upload rendezvous descriptors to every
27618 directory authority: only try the v1 authorities.
27619 - Servers no longer complain when they think they're not
27620 registered with the directory authorities. There were too many
27622 - Backport dist-rpm changes so rpms can be built without errors.
27625 - Implement an option, VirtualAddrMask, to set which addresses
27626 get handed out in response to mapaddress requests. This works
27627 around a bug in tsocks where 127.0.0.0/8 is never socksified.
27630 Changes in version 0.1.1.18-rc - 2006-04-10
27632 - Work harder to download live network-statuses from all the
27633 directory authorities we know about. Improve the threshold
27634 decision logic so we're more robust to edge cases.
27635 - When fetching rendezvous descriptors, we were willing to ask
27636 v2 authorities too, which would always return 404.
27639 - Stop listing down or invalid nodes in the v1 directory. This will
27640 reduce its bulk by about 1/3, and reduce load on directory
27642 - When deciding whether a router is Fast or Guard-worthy, consider
27643 his advertised BandwidthRate and not just the BandwidthCapacity.
27644 - No longer ship INSTALL and README files -- they are useless now.
27645 - Force rpmbuild to behave and honor target_cpu.
27646 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
27647 - Start to include translated versions of the tor-doc-*.html
27648 files, along with the screenshots. Still needs more work.
27649 - Start sending back 512 and 451 errors if mapaddress fails,
27650 rather than not sending anything back at all.
27651 - When we fail to bind or listen on an incoming or outgoing
27652 socket, we should close it before failing. otherwise we just
27653 leak it. (thanks to weasel for finding.)
27654 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
27655 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
27656 - Make NoPublish (even though deprecated) work again.
27657 - Fix a minor security flaw where a versioning auth dirserver
27658 could list a recommended version many times in a row to make
27659 clients more convinced that it's recommended.
27660 - Fix crash bug if there are two unregistered servers running
27661 with the same nickname, one of them is down, and you ask for
27662 them by nickname in your EntryNodes or ExitNodes. Also, try
27663 to pick the one that's running rather than an arbitrary one.
27664 - Fix an infinite loop we could hit if we go offline for too long.
27665 - Complain when we hit WSAENOBUFS on recv() or write() too.
27666 Perhaps this will help us hunt the bug.
27667 - If you're not a versioning dirserver, don't put the string
27668 "client-versions \nserver-versions \n" in your network-status.
27669 - Lower the minimum required number of file descriptors to 1000,
27670 so we can have some overhead for Valgrind on Linux, where the
27671 default ulimit -n is 1024.
27674 - Add tor.dizum.com as the fifth authoritative directory server.
27675 - Add a new config option FetchUselessDescriptors, off by default,
27676 for when you plan to run "exitlist" on your client and you want
27677 to know about even the non-running descriptors.
27680 Changes in version 0.1.1.17-rc - 2006-03-28
27682 - Clients and servers since 0.1.1.10-alpha have been expiring
27683 connections whenever they are idle for 5 minutes and they *do*
27684 have circuits on them. Oops. With this new version, clients will
27685 discard their previous entry guard choices and avoid choosing
27686 entry guards running these flawed versions.
27687 - Fix memory leak when uncompressing concatenated zlib streams. This
27688 was causing substantial leaks over time on Tor servers.
27689 - The v1 directory was including servers as much as 48 hours old,
27690 because that's how the new routerlist->routers works. Now only
27691 include them if they're 20 hours old or less.
27694 - Resume building on irix64, netbsd 2.0, etc.
27695 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
27697 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
27698 and it is confusing some users.
27699 - Mirrors stop caching the v1 directory so often.
27700 - Make the max number of old descriptors that a cache will hold
27701 rise with the number of directory authorities, so we can scale.
27702 - Change our win32 uname() hack to be more forgiving about what
27703 win32 versions it thinks it's found.
27706 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
27708 - When the controller's *setconf commands fail, collect an error
27709 message in a string and hand it back to the controller.
27710 - Make the v2 dir's "Fast" flag based on relative capacity, just
27711 like "Stable" is based on median uptime. Name everything in the
27712 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
27713 - Log server fingerprint on startup, so new server operators don't
27714 have to go hunting around their filesystem for it.
27715 - Return a robots.txt on our dirport to discourage google indexing.
27716 - Let the controller ask for GETINFO dir/status/foo so it can ask
27717 directly rather than connecting to the dir port. Only works when
27718 dirport is set for now.
27720 o New config options rather than constants in the code:
27721 - SocksTimeout: How long do we let a socks connection wait
27722 unattached before we fail it?
27723 - CircuitBuildTimeout: Cull non-open circuits that were born
27724 at least this many seconds ago.
27725 - CircuitIdleTimeout: Cull open clean circuits that were born
27726 at least this many seconds ago.
27729 Changes in version 0.1.1.16-rc - 2006-03-18
27730 o Bugfixes on 0.1.1.15-rc:
27731 - Fix assert when the controller asks to attachstream a connect-wait
27732 or resolve-wait stream.
27733 - Now do address rewriting when the controller asks us to attach
27734 to a particular circuit too. This will let Blossom specify
27735 "moria2.exit" without having to learn what moria2's IP address is.
27736 - Make the "tor --verify-config" command-line work again, so people
27737 can automatically check if their torrc will parse.
27738 - Authoritative dirservers no longer require an open connection from
27739 a server to consider him "reachable". We need this change because
27740 when we add new auth dirservers, old servers won't know not to
27742 - Let Tor build on Sun CC again.
27743 - Fix an off-by-one buffer size in dirserv.c that magically never
27744 hit our three authorities but broke sjmurdoch's own tor network.
27745 - If we as a directory mirror don't know of any v1 directory
27746 authorities, then don't try to cache any v1 directories.
27747 - Stop warning about unknown servers in our family when they are
27748 given as hex digests.
27749 - Stop complaining as quickly to the server operator that he
27750 hasn't registered his nickname/key binding.
27751 - Various cleanups so we can add new V2 Auth Dirservers.
27752 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
27753 reflect the updated flags in our v2 dir protocol.
27754 - Resume allowing non-printable characters for exit streams (both
27755 for connecting and for resolving). Now we tolerate applications
27756 that don't follow the RFCs. But continue to block malformed names
27759 o Bugfixes on 0.1.0.x:
27760 - Fix assert bug in close_logs(): when we close and delete logs,
27761 remove them all from the global "logfiles" list.
27762 - Fix minor integer overflow in calculating when we expect to use up
27763 our bandwidth allocation before hibernating.
27764 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
27765 there are multiple SSLs installed with different versions.
27766 - When we try to be a server and Address is not explicitly set and
27767 our hostname resolves to a private IP address, try to use an
27768 interface address if it has a public address. Now Windows machines
27769 that think of themselves as localhost can work by default.
27772 - Let the controller ask for GETINFO dir/server/foo so it can ask
27773 directly rather than connecting to the dir port.
27774 - Let the controller tell us about certain router descriptors
27775 that it doesn't want Tor to use in circuits. Implement
27776 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
27777 - New config option SafeSocks to reject all application connections
27778 using unsafe socks protocols. Defaults to off.
27781 Changes in version 0.1.1.15-rc - 2006-03-11
27782 o Bugfixes and cleanups:
27783 - When we're printing strings from the network, don't try to print
27784 non-printable characters. This protects us against shell escape
27785 sequence exploits, and also against attacks to fool humans into
27786 misreading their logs.
27787 - Fix a bug where Tor would fail to establish any connections if you
27788 left it off for 24 hours and then started it: we were happy with
27789 the obsolete network statuses, but they all referred to router
27790 descriptors that were too old to fetch, so we ended up with no
27791 valid router descriptors.
27792 - Fix a seg fault in the controller's "getinfo orconn-status"
27793 command while listing status on incoming handshaking connections.
27794 Introduce a status name "NEW" for these connections.
27795 - If we get a linelist or linelist_s config option from the torrc
27796 (e.g. ExitPolicy) and it has no value, warn and skip rather than
27797 silently resetting it to its default.
27798 - Don't abandon entry guards until they've been down or gone for
27800 - Cleaner and quieter log messages.
27803 - New controller signal NEWNYM that makes new application requests
27804 use clean circuits.
27805 - Add a new circuit purpose 'controller' to let the controller ask
27806 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
27807 controller command to let you specify the purpose if you're
27808 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
27809 command to let you change a circuit's purpose after it's been
27811 - Accept "private:*" in routerdesc exit policies; not generated yet
27812 because older Tors do not understand it.
27813 - Add BSD-style contributed startup script "rc.subr" from Peter
27817 Changes in version 0.1.1.14-alpha - 2006-02-20
27818 o Bugfixes on 0.1.1.x:
27819 - Don't die if we ask for a stdout or stderr log (even implicitly)
27820 and we're set to RunAsDaemon -- just warn.
27821 - We still had a few bugs in the OR connection rotation code that
27822 caused directory servers to slowly aggregate connections to other
27823 fast Tor servers. This time for sure!
27824 - Make log entries on Win32 include the name of the function again.
27825 - We were treating a pair of exit policies if they were equal even
27826 if one said accept and the other said reject -- causing us to
27827 not always publish a new descriptor since we thought nothing
27829 - Retry pending server downloads as well as pending networkstatus
27830 downloads when we unexpectedly get a socks request.
27831 - We were ignoring the IS_FAST flag in the directory status,
27832 meaning we were willing to pick trivial-bandwidth nodes for "fast"
27834 - If the controller's SAVECONF command fails (e.g. due to file
27835 permissions), let the controller know that it failed.
27838 - If we're trying to be a Tor server and running Windows 95/98/ME
27839 as a server, explain that we'll likely crash.
27840 - When we're a server, a client asks for an old-style directory,
27841 and our write bucket is empty, don't give it to him. This way
27842 small servers can continue to serve the directory *sometimes*,
27843 without getting overloaded.
27844 - Compress exit policies even more -- look for duplicate lines
27846 - Clients now honor the "guard" flag in the router status when
27847 picking entry guards, rather than looking at is_fast or is_stable.
27848 - Retain unrecognized lines in $DATADIR/state file, so that we can
27849 be forward-compatible.
27850 - Generate 18.0.0.0/8 address policy format in descs when we can;
27851 warn when the mask is not reducible to a bit-prefix.
27852 - Let the user set ControlListenAddress in the torrc. This can be
27853 dangerous, but there are some cases (like a secured LAN) where it
27855 - Split ReachableAddresses into ReachableDirAddresses and
27856 ReachableORAddresses, so we can restrict Dir conns to port 80
27857 and OR conns to port 443.
27858 - Now we can target arch and OS in rpm builds (contributed by
27859 Phobos). Also make the resulting dist-rpm filename match the
27861 - New config options to help controllers: FetchServerDescriptors
27862 and FetchHidServDescriptors for whether to fetch server
27863 info and hidserv info or let the controller do it, and
27864 PublishServerDescriptor and PublishHidServDescriptors.
27865 - Also let the controller set the __AllDirActionsPrivate config
27866 option if you want all directory fetches/publishes to happen via
27867 Tor (it assumes your controller bootstraps your circuits).
27870 Changes in version 0.1.0.17 - 2006-02-17
27871 o Crash bugfixes on 0.1.0.x:
27872 - When servers with a non-zero DirPort came out of hibernation,
27873 sometimes they would trigger an assert.
27875 o Other important bugfixes:
27876 - On platforms that don't have getrlimit (like Windows), we were
27877 artificially constraining ourselves to a max of 1024
27878 connections. Now just assume that we can handle as many as 15000
27879 connections. Hopefully this won't cause other problems.
27881 o Backported features:
27882 - When we're a server, a client asks for an old-style directory,
27883 and our write bucket is empty, don't give it to him. This way
27884 small servers can continue to serve the directory *sometimes*,
27885 without getting overloaded.
27886 - Whenever you get a 503 in response to a directory fetch, try
27887 once more. This will become important once servers start sending
27888 503's whenever they feel busy.
27889 - Fetch a new directory every 120 minutes, not every 40 minutes.
27890 Now that we have hundreds of thousands of users running the old
27891 directory algorithm, it's starting to hurt a lot.
27892 - Bump up the period for forcing a hidden service descriptor upload
27893 from 20 minutes to 1 hour.
27896 Changes in version 0.1.1.13-alpha - 2006-02-09
27897 o Crashes in 0.1.1.x:
27898 - When you tried to setconf ORPort via the controller, Tor would
27899 crash. So people using TorCP to become a server were sad.
27900 - Solve (I hope) the stack-smashing bug that we were seeing on fast
27901 servers. The problem appears to be something do with OpenSSL's
27902 random number generation, or how we call it, or something. Let me
27903 know if the crashes continue.
27904 - Turn crypto hardware acceleration off by default, until we find
27905 somebody smart who can test it for us. (It appears to produce
27906 seg faults in at least some cases.)
27907 - Fix a rare assert error when we've tried all intro points for
27908 a hidden service and we try fetching the service descriptor again:
27909 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
27912 - Fix a major load balance bug: we were round-robining in 16 KB
27913 chunks, and servers with bandwidthrate of 20 KB, while downloading
27914 a 600 KB directory, would starve their other connections. Now we
27915 try to be a bit more fair.
27916 - Dir authorities and mirrors were never expiring the newest
27917 descriptor for each server, causing memory and directory bloat.
27918 - Fix memory-bloating and connection-bloating bug on servers: We
27919 were never closing any connection that had ever had a circuit on
27920 it, because we were checking conn->n_circuits == 0, yet we had a
27921 bug that let it go negative.
27922 - Make Tor work using squid as your http proxy again -- squid
27923 returns an error if you ask for a URL that's too long, and it uses
27924 a really generic error message. Plus, many people are behind a
27925 transparent squid so they don't even realize it.
27926 - On platforms that don't have getrlimit (like Windows), we were
27927 artificially constraining ourselves to a max of 1024
27928 connections. Now just assume that we can handle as many as 15000
27929 connections. Hopefully this won't cause other problems.
27930 - Add a new config option ExitPolicyRejectPrivate which defaults to
27931 1. This means all exit policies will begin with rejecting private
27932 addresses, unless the server operator explicitly turns it off.
27935 - Clients no longer download descriptors for non-running
27937 - Before we add new directory authorities, we should make it
27938 clear that only v1 authorities should receive/publish hidden
27939 service descriptors.
27942 - As soon as we've fetched some more directory info, immediately
27943 try to download more server descriptors. This way we don't have
27944 a 10 second pause during initial bootstrapping.
27945 - Remove even more loud log messages that the server operator can't
27947 - When we're running an obsolete or un-recommended version, make
27948 the log message more clear about what the problem is and what
27949 versions *are* still recommended.
27950 - Provide a more useful warn message when our onion queue gets full:
27951 the CPU is too slow or the exit policy is too liberal.
27952 - Don't warn when we receive a 503 from a dirserver/cache -- this
27953 will pave the way for them being able to refuse if they're busy.
27954 - When we fail to bind a listener, try to provide a more useful
27955 log message: e.g., "Is Tor already running?"
27956 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
27957 Goldberg can prove things about our handshake protocol more
27959 - MaxConn has been obsolete for a while now. Document the ConnLimit
27960 config option, which is a *minimum* number of file descriptors
27961 that must be available else Tor refuses to start.
27962 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
27963 if you log to syslog and want something other than LOG_DAEMON.
27964 - Make dirservers generate a separate "guard" flag to mean,
27965 "would make a good entry guard". Make clients parse it and vote
27966 on it. Not used by clients yet.
27967 - Implement --with-libevent-dir option to ./configure. Also, improve
27968 search techniques to find libevent, and use those for openssl too.
27969 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
27970 - Only start testing reachability once we've established a
27971 circuit. This will make startup on dirservers less noisy.
27972 - Don't try to upload hidden service descriptors until we have
27973 established a circuit.
27974 - Fix the controller's "attachstream 0" command to treat conn like
27975 it just connected, doing address remapping, handling .exit and
27976 .onion idioms, and so on. Now we're more uniform in making sure
27977 that the controller hears about new and closing connections.
27980 Changes in version 0.1.1.12-alpha - 2006-01-11
27981 o Bugfixes on 0.1.1.x:
27982 - The fix to close duplicate server connections was closing all
27983 Tor client connections if they didn't establish a circuit
27984 quickly enough. Oops.
27985 - Fix minor memory issue (double-free) that happened on exit.
27987 o Bugfixes on 0.1.0.x:
27988 - Tor didn't warn when it failed to open a log file.
27991 Changes in version 0.1.1.11-alpha - 2006-01-10
27992 o Crashes in 0.1.1.x:
27993 - Include all the assert/crash fixes from 0.1.0.16.
27994 - If you start Tor and then quit very quickly, there were some
27995 races that tried to free things that weren't allocated yet.
27996 - Fix a rare memory stomp if you're running hidden services.
27997 - Fix segfault when specifying DirServer in config without nickname.
27998 - Fix a seg fault when you finish connecting to a server but at
27999 that moment you dump his server descriptor.
28000 - Extendcircuit and Attachstream controller commands would
28001 assert/crash if you don't give them enough arguments.
28002 - Fix an assert error when we're out of space in the connection_list
28003 and we try to post a hidden service descriptor (reported by weasel).
28004 - If you specify a relative torrc path and you set RunAsDaemon in
28005 your torrc, then it chdir()'s to the new directory. If you HUP,
28006 it tries to load the new torrc location, fails, and exits.
28007 The fix: no longer allow a relative path to torrc using -f.
28010 - Implement "entry guards": automatically choose a handful of entry
28011 nodes and stick with them for all circuits. Only pick new guards
28012 when the ones you have are unsuitable, and if the old guards
28013 become suitable again, switch back. This will increase security
28014 dramatically against certain end-point attacks. The EntryNodes
28015 config option now provides some hints about which entry guards you
28016 want to use most; and StrictEntryNodes means to only use those.
28017 - New directory logic: download by descriptor digest, not by
28018 fingerprint. Caches try to download all listed digests from
28019 authorities; clients try to download "best" digests from caches.
28020 This avoids partitioning and isolating attacks better.
28021 - Make the "stable" router flag in network-status be the median of
28022 the uptimes of running valid servers, and make clients pay
28023 attention to the network-status flags. Thus the cutoff adapts
28024 to the stability of the network as a whole, making IRC, IM, etc
28025 connections more reliable.
28028 - Tor servers with dynamic IP addresses were needing to wait 18
28029 hours before they could start doing reachability testing using
28030 the new IP address and ports. This is because they were using
28031 the internal descriptor to learn what to test, yet they were only
28032 rebuilding the descriptor once they decided they were reachable.
28033 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
28034 to download certain server descriptors, throw them away, and then
28035 fetch them again after 30 minutes. Now mirrors throw away these
28036 server descriptors so clients can't get them.
28037 - We were leaving duplicate connections to other ORs open for a week,
28038 rather than closing them once we detect a duplicate. This only
28039 really affected authdirservers, but it affected them a lot.
28040 - Spread the authdirservers' reachability testing over the entire
28041 testing interval, so we don't try to do 500 TLS's at once every
28045 - If the network is down, and we try to connect to a conn because
28046 we have a circuit in mind, and we timeout (30 seconds) because the
28047 network never answers, we were expiring the circuit, but we weren't
28048 obsoleting the connection or telling the entry_guards functions.
28049 - Some Tor servers process billions of cells per day. These statistics
28050 need to be uint64_t's.
28051 - Check for integer overflows in more places, when adding elements
28052 to smartlists. This could possibly prevent a buffer overflow
28053 on malicious huge inputs. I don't see any, but I haven't looked
28055 - ReachableAddresses kept growing new "reject *:*" lines on every
28057 - When you "setconf log" via the controller, it should remove all
28058 logs. We were automatically adding back in a "log notice stdout".
28059 - Newly bootstrapped Tor networks couldn't establish hidden service
28060 circuits until they had nodes with high uptime. Be more tolerant.
28061 - We were marking servers down when they could not answer every piece
28062 of the directory request we sent them. This was far too harsh.
28063 - Fix the torify (tsocks) config file to not use Tor for localhost
28065 - Directory authorities now go to the proper authority when asking for
28066 a networkstatus, even when they want a compressed one.
28067 - Fix a harmless bug that was causing Tor servers to log
28068 "Got an end because of misc error, but we're not an AP. Closing."
28069 - Authorities were treating their own descriptor changes as cosmetic,
28070 meaning the descriptor available in the network-status and the
28071 descriptor that clients downloaded were different.
28072 - The OS X installer was adding a symlink for tor_resolve but
28073 the binary was called tor-resolve (reported by Thomas Hardly).
28074 - Workaround a problem with some http proxies where they refuse GET
28075 requests that specify "Content-Length: 0" (reported by Adrian).
28076 - Fix wrong log message when you add a "HiddenServiceNodes" config
28077 line without any HiddenServiceDir line (reported by Chris Thomas).
28080 - Write the TorVersion into the state file so we have a prayer of
28081 keeping forward and backward compatibility.
28082 - Revive the FascistFirewall config option rather than eliminating it:
28083 now it's a synonym for ReachableAddresses *:80,*:443.
28084 - Clients choose directory servers from the network status lists,
28085 not from their internal list of router descriptors. Now they can
28086 go to caches directly rather than needing to go to authorities
28088 - Directory authorities ignore router descriptors that have only
28089 cosmetic differences: do this for 0.1.0.x servers now too.
28090 - Add a new flag to network-status indicating whether the server
28091 can answer v2 directory requests too.
28092 - Authdirs now stop whining so loudly about bad descriptors that
28093 they fetch from other dirservers. So when there's a log complaint,
28094 it's for sure from a freshly uploaded descriptor.
28095 - Reduce memory requirements in our structs by changing the order
28097 - There used to be two ways to specify your listening ports in a
28098 server descriptor: on the "router" line and with a separate "ports"
28099 line. Remove support for the "ports" line.
28100 - New config option "AuthDirRejectUnlisted" for auth dirservers as
28101 a panic button: if we get flooded with unusable servers we can
28102 revert to only listing servers in the approved-routers file.
28103 - Auth dir servers can now mark a fingerprint as "!reject" or
28104 "!invalid" in the approved-routers file (as its nickname), to
28105 refuse descriptors outright or include them but marked as invalid.
28106 - Servers store bandwidth history across restarts/crashes.
28107 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
28108 get a better idea of why their circuits failed. Not used yet.
28109 - Directory mirrors now cache up to 16 unrecognized network-status
28110 docs. Now we can add new authdirservers and they'll be cached too.
28111 - When picking a random directory, prefer non-authorities if any
28113 - New controller option "getinfo desc/all-recent" to fetch the
28114 latest server descriptor for every router that Tor knows about.
28117 Changes in version 0.1.0.16 - 2006-01-02
28118 o Crash bugfixes on 0.1.0.x:
28119 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
28120 corrupting the heap, losing FDs, or crashing when we need to resize
28121 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
28122 - It turns out sparc64 platforms crash on unaligned memory access
28123 too -- so detect and avoid this.
28124 - Handle truncated compressed data correctly (by detecting it and
28126 - Fix possible-but-unlikely free(NULL) in control.c.
28127 - When we were closing connections, there was a rare case that
28128 stomped on memory, triggering seg faults and asserts.
28129 - Avoid potential infinite recursion when building a descriptor. (We
28130 don't know that it ever happened, but better to fix it anyway.)
28131 - We were neglecting to unlink marked circuits from soon-to-close OR
28132 connections, which caused some rare scribbling on freed memory.
28133 - Fix a memory stomping race bug when closing the joining point of two
28134 rendezvous circuits.
28135 - Fix an assert in time parsing found by Steven Murdoch.
28137 o Other bugfixes on 0.1.0.x:
28138 - When we're doing reachability testing, provide more useful log
28139 messages so the operator knows what to expect.
28140 - Do not check whether DirPort is reachable when we are suppressing
28141 advertising it because of hibernation.
28142 - When building with -static or on Solaris, we sometimes needed -ldl.
28143 - When we're deciding whether a stream has enough circuits around
28144 that can handle it, count the freshly dirty ones and not the ones
28145 that are so dirty they won't be able to handle it.
28146 - When we're expiring old circuits, we had a logic error that caused
28147 us to close new rendezvous circuits rather than old ones.
28148 - Give a more helpful log message when you try to change ORPort via
28149 the controller: you should upgrade Tor if you want that to work.
28150 - We were failing to parse Tor versions that start with "Tor ".
28151 - Tolerate faulty streams better: when a stream fails for reason
28152 exitpolicy, stop assuming that the router is lying about his exit
28153 policy. When a stream fails for reason misc, allow it to retry just
28154 as if it was resolvefailed. When a stream has failed three times,
28155 reset its failure count so we can try again and get all three tries.
28158 Changes in version 0.1.1.10-alpha - 2005-12-11
28159 o Correctness bugfixes on 0.1.0.x:
28160 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
28161 corrupting the heap, losing FDs, or crashing when we need to resize
28162 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
28163 - Stop doing the complex voodoo overkill checking for insecure
28164 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
28165 - When we were closing connections, there was a rare case that
28166 stomped on memory, triggering seg faults and asserts.
28167 - We were neglecting to unlink marked circuits from soon-to-close OR
28168 connections, which caused some rare scribbling on freed memory.
28169 - When we're deciding whether a stream has enough circuits around
28170 that can handle it, count the freshly dirty ones and not the ones
28171 that are so dirty they won't be able to handle it.
28172 - Recover better from TCP connections to Tor servers that are
28173 broken but don't tell you (it happens!); and rotate TLS
28174 connections once a week.
28175 - When we're expiring old circuits, we had a logic error that caused
28176 us to close new rendezvous circuits rather than old ones.
28177 - Fix a scary-looking but apparently harmless bug where circuits
28178 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
28179 servers, and never switch to state CIRCUIT_STATE_OPEN.
28180 - When building with -static or on Solaris, we sometimes needed to
28182 - Give a useful message when people run Tor as the wrong user,
28183 rather than telling them to start chowning random directories.
28184 - We were failing to inform the controller about new .onion streams.
28186 o Security bugfixes on 0.1.0.x:
28187 - Refuse server descriptors if the fingerprint line doesn't match
28188 the included identity key. Tor doesn't care, but other apps (and
28189 humans) might actually be trusting the fingerprint line.
28190 - We used to kill the circuit when we receive a relay command we
28191 don't recognize. Now we just drop it.
28192 - Start obeying our firewall options more rigorously:
28193 . If we can't get to a dirserver directly, try going via Tor.
28194 . Don't ever try to connect (as a client) to a place our
28195 firewall options forbid.
28196 . If we specify a proxy and also firewall options, obey the
28197 firewall options even when we're using the proxy: some proxies
28198 can only proxy to certain destinations.
28199 - Fix a bug found by Lasse Overlier: when we were making internal
28200 circuits (intended to be cannibalized later for rendezvous and
28201 introduction circuits), we were picking them so that they had
28202 useful exit nodes. There was no need for this, and it actually
28203 aids some statistical attacks.
28204 - Start treating internal circuits and exit circuits separately.
28205 It's important to keep them separate because internal circuits
28206 have their last hops picked like middle hops, rather than like
28207 exit hops. So exiting on them will break the user's expectations.
28209 o Bugfixes on 0.1.1.x:
28210 - Take out the mis-feature where we tried to detect IP address
28211 flapping for people with DynDNS, and chose not to upload a new
28212 server descriptor sometimes.
28213 - Try to be compatible with OpenSSL 0.9.6 again.
28214 - Log fix: when the controller is logging about .onion addresses,
28215 sometimes it didn't include the ".onion" part of the address.
28216 - Don't try to modify options->DirServers internally -- if the
28217 user didn't specify any, just add the default ones directly to
28218 the trusted dirserver list. This fixes a bug where people running
28219 controllers would use SETCONF on some totally unrelated config
28220 option, and Tor would start yelling at them about changing their
28222 - Let the controller's redirectstream command specify a port, in
28223 case the controller wants to change that too.
28224 - When we requested a pile of server descriptors, we sometimes
28225 accidentally launched a duplicate request for the first one.
28226 - Bugfix for trackhostexits: write down the fingerprint of the
28227 chosen exit, not its nickname, because the chosen exit might not
28229 - When parsing foo.exit, if foo is unknown, and we are leaving
28230 circuits unattached, set the chosen_exit field and leave the
28231 address empty. This matters because controllers got confused
28233 - Directory authorities no longer try to download server
28234 descriptors that they know they will reject.
28236 o Features and updates:
28237 - Replace balanced trees with hash tables: this should make stuff
28238 significantly faster.
28239 - Resume using the AES counter-mode implementation that we ship,
28240 rather than OpenSSL's. Ours is significantly faster.
28241 - Many other CPU and memory improvements.
28242 - Add a new config option FastFirstHopPK (on by default) so clients
28243 do a trivial crypto handshake for their first hop, since TLS has
28244 already taken care of confidentiality and authentication.
28245 - Add a new config option TestSocks so people can see if their
28246 applications are using socks4, socks4a, socks5-with-ip, or
28247 socks5-with-hostname. This way they don't have to keep mucking
28248 with tcpdump and wondering if something got cached somewhere.
28249 - Warn when listening on a public address for socks. I suspect a
28250 lot of people are setting themselves up as open socks proxies,
28251 and they have no idea that jerks on the Internet are using them,
28252 since they simply proxy the traffic into the Tor network.
28253 - Add "private:*" as an alias in configuration for policies. Now
28254 you can simplify your exit policy rather than needing to list
28255 every single internal or nonroutable network space.
28256 - Add a new controller event type that allows controllers to get
28257 all server descriptors that were uploaded to a router in its role
28258 as authoritative dirserver.
28259 - Start shipping socks-extensions.txt, tor-doc-unix.html,
28260 tor-doc-server.html, and stylesheet.css in the tarball.
28261 - Stop shipping tor-doc.html in the tarball.
28264 Changes in version 0.1.1.9-alpha - 2005-11-15
28265 o Usability improvements:
28266 - Start calling it FooListenAddress rather than FooBindAddress,
28267 since few of our users know what it means to bind an address
28269 - Reduce clutter in server logs. We're going to try to make
28270 them actually usable now. New config option ProtocolWarnings that
28271 lets you hear about how _other Tors_ are breaking the protocol. Off
28273 - Divide log messages into logging domains. Once we put some sort
28274 of interface on this, it will let people looking at more verbose
28275 log levels specify the topics they want to hear more about.
28276 - Make directory servers return better http 404 error messages
28277 instead of a generic "Servers unavailable".
28278 - Check for even more Windows version flags when writing the platform
28279 string in server descriptors, and note any we don't recognize.
28280 - Clean up more of the OpenSSL memory when exiting, so we can detect
28281 memory leaks better.
28282 - Make directory authorities be non-versioning, non-naming by
28283 default. Now we can add new directory servers without requiring
28284 their operators to pay close attention.
28285 - When logging via syslog, include the pid whenever we provide
28286 a log entry. Suggested by Todd Fries.
28288 o Performance improvements:
28289 - Directory servers now silently throw away new descriptors that
28290 haven't changed much if the timestamps are similar. We do this to
28291 tolerate older Tor servers that upload a new descriptor every 15
28292 minutes. (It seemed like a good idea at the time.)
28293 - Inline bottleneck smartlist functions; use fast versions by default.
28294 - Add a "Map from digest to void*" abstraction digestmap_t so we
28295 can do less hex encoding/decoding. Use it in router_get_by_digest()
28296 to resolve a performance bottleneck.
28297 - Allow tor_gzip_uncompress to extract as much as possible from
28298 truncated compressed data. Try to extract as many
28299 descriptors as possible from truncated http responses (when
28300 DIR_PURPOSE_FETCH_ROUTERDESC).
28301 - Make circ->onionskin a pointer, not a static array. moria2 was using
28302 125000 circuit_t's after it had been up for a few weeks, which
28303 translates to 20+ megs of wasted space.
28304 - The private half of our EDH handshake keys are now chosen out
28305 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
28307 o Security improvements:
28308 - Start making directory caches retain old routerinfos, so soon
28309 clients can start asking by digest of descriptor rather than by
28310 fingerprint of server.
28311 - Add half our entropy from RAND_poll in OpenSSL. This knows how
28312 to use egd (if present), openbsd weirdness (if present), vms/os2
28313 weirdness (if we ever port there), and more in the future.
28315 o Bugfixes on 0.1.0.x:
28316 - Do round-robin writes of at most 16 kB per write. This might be
28317 more fair on loaded Tor servers, and it might resolve our Windows
28318 crash bug. It might also slow things down.
28319 - Our TLS handshakes were generating a single public/private
28320 keypair for the TLS context, rather than making a new one for
28321 each new connections. Oops. (But we were still rotating them
28322 periodically, so it's not so bad.)
28323 - When we were cannibalizing a circuit with a particular exit
28324 node in mind, we weren't checking to see if that exit node was
28325 already present earlier in the circuit. Oops.
28326 - When a Tor server's IP changes (e.g. from a dyndns address),
28327 upload a new descriptor so clients will learn too.
28328 - Really busy servers were keeping enough circuits open on stable
28329 connections that they were wrapping around the circuit_id
28330 space. (It's only two bytes.) This exposed a bug where we would
28331 feel free to reuse a circuit_id even if it still exists but has
28332 been marked for close. Try to fix this bug. Some bug remains.
28333 - If we would close a stream early (e.g. it asks for a .exit that
28334 we know would refuse it) but the LeaveStreamsUnattached config
28335 option is set by the controller, then don't close it.
28337 o Bugfixes on 0.1.1.8-alpha:
28338 - Fix a big pile of memory leaks, some of them serious.
28339 - Do not try to download a routerdesc if we would immediately reject
28341 - Resume inserting a newline between all router descriptors when
28342 generating (old style) signed directories, since our spec says
28344 - When providing content-type application/octet-stream for
28345 server descriptors using .z, we were leaving out the
28346 content-encoding header. Oops. (Everything tolerated this just
28347 fine, but that doesn't mean we need to be part of the problem.)
28348 - Fix a potential seg fault in getconf and getinfo using version 1
28349 of the controller protocol.
28350 - Avoid crash: do not check whether DirPort is reachable when we
28351 are suppressing it because of hibernation.
28352 - Make --hash-password not crash on exit.
28355 Changes in version 0.1.1.8-alpha - 2005-10-07
28356 o New features (major):
28357 - Clients don't download or use the directory anymore. Now they
28358 download and use network-statuses from the trusted dirservers,
28359 and fetch individual server descriptors as needed from mirrors.
28360 See dir-spec.txt for all the gory details.
28361 - Be more conservative about whether to advertise our DirPort.
28362 The main change is to not advertise if we're running at capacity
28363 and either a) we could hibernate or b) our capacity is low and
28364 we're using a default DirPort.
28365 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
28367 o New features (minor):
28368 - Try to be smart about when to retry network-status and
28369 server-descriptor fetches. Still needs some tuning.
28370 - Stop parsing, storing, or using running-routers output (but
28371 mirrors still cache and serve it).
28372 - Consider a threshold of versioning dirservers (dirservers who have
28373 an opinion about which Tor versions are still recommended) before
28374 deciding whether to warn the user that he's obsolete.
28375 - Dirservers can now reject/invalidate by key and IP, with the
28376 config options "AuthDirInvalid" and "AuthDirReject". This is
28377 useful since currently we automatically list servers as running
28378 and usable even if we know they're jerks.
28379 - Provide dire warnings to any users who set DirServer; move it out
28380 of torrc.sample and into torrc.complete.
28381 - Add MyFamily to torrc.sample in the server section.
28382 - Add nicknames to the DirServer line, so we can refer to them
28383 without requiring all our users to memorize their IP addresses.
28384 - When we get an EOF or a timeout on a directory connection, note
28385 how many bytes of serverdesc we are dropping. This will help
28386 us determine whether it is smart to parse incomplete serverdesc
28388 - Add a new function to "change pseudonyms" -- that is, to stop
28389 using any currently-dirty circuits for new streams, so we don't
28390 link new actions to old actions. Currently it's only called on
28391 HUP (or SIGNAL RELOAD).
28392 - On sighup, if UseHelperNodes changed to 1, use new circuits.
28393 - Start using RAND_bytes rather than RAND_pseudo_bytes from
28394 OpenSSL. Also, reseed our entropy every hour, not just at
28395 startup. And entropy in 512-bit chunks, not 160-bit chunks.
28397 o Fixes on 0.1.1.7-alpha:
28398 - Nobody ever implemented EVENT_ADDRMAP for control protocol
28399 version 0, so don't let version 0 controllers ask for it.
28400 - If you requested something with too many newlines via the
28401 v1 controller protocol, you could crash tor.
28402 - Fix a number of memory leaks, including some pretty serious ones.
28403 - Re-enable DirPort testing again, so Tor servers will be willing
28404 to advertise their DirPort if it's reachable.
28405 - On TLS handshake, only check the other router's nickname against
28406 its expected nickname if is_named is set.
28408 o Fixes forward-ported from 0.1.0.15:
28409 - Don't crash when we don't have any spare file descriptors and we
28410 try to spawn a dns or cpu worker.
28411 - Make the numbers in read-history and write-history into uint64s,
28412 so they don't overflow and publish negatives in the descriptor.
28414 o Fixes on 0.1.0.x:
28415 - For the OS X package's modified privoxy config file, comment
28416 out the "logfile" line so we don't log everything passed
28418 - We were whining about using socks4 or socks5-with-local-lookup
28419 even when it's an IP in the "virtual" range we designed exactly
28421 - We were leaking some memory every time the client changes IPs.
28422 - Never call free() on tor_malloc()d memory. This will help us
28423 use dmalloc to detect memory leaks.
28424 - Check for named servers when looking them up by nickname;
28425 warn when we'recalling a non-named server by its nickname;
28426 don't warn twice about the same name.
28427 - Try to list MyFamily elements by key, not by nickname, and warn
28428 if we've not heard of the server.
28429 - Make windows platform detection (uname equivalent) smarter.
28430 - It turns out sparc64 doesn't like unaligned access either.
28433 Changes in version 0.1.0.15 - 2005-09-23
28434 o Bugfixes on 0.1.0.x:
28435 - Reject ports 465 and 587 (spam targets) in default exit policy.
28436 - Don't crash when we don't have any spare file descriptors and we
28437 try to spawn a dns or cpu worker.
28438 - Get rid of IgnoreVersion undocumented config option, and make us
28439 only warn, never exit, when we're running an obsolete version.
28440 - Don't try to print a null string when your server finds itself to
28441 be unreachable and the Address config option is empty.
28442 - Make the numbers in read-history and write-history into uint64s,
28443 so they don't overflow and publish negatives in the descriptor.
28444 - Fix a minor memory leak in smartlist_string_remove().
28445 - We were only allowing ourselves to upload a server descriptor at
28446 most every 20 minutes, even if it changed earlier than that.
28447 - Clean up log entries that pointed to old URLs.
28450 Changes in version 0.1.1.7-alpha - 2005-09-14
28451 o Fixes on 0.1.1.6-alpha:
28452 - Exit servers were crashing when people asked them to make a
28453 connection to an address not in their exit policy.
28454 - Looking up a non-existent stream for a v1 control connection would
28456 - Fix a seg fault if we ask a dirserver for a descriptor by
28457 fingerprint but he doesn't know about him.
28458 - SETCONF was appending items to linelists, not clearing them.
28459 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
28460 out and refuse the setconf if it would fail.
28461 - Downgrade the dirserver log messages when whining about
28465 - Add Peter Palfrader's check-tor script to tor/contrib/
28466 It lets you easily check whether a given server (referenced by
28467 nickname) is reachable by you.
28468 - Numerous changes to move towards client-side v2 directories. Not
28471 o Fixes on 0.1.0.x:
28472 - If the user gave tor an odd number of command-line arguments,
28473 we were silently ignoring the last one. Now we complain and fail.
28474 [This wins the oldest-bug prize -- this bug has been present since
28475 November 2002, as released in Tor 0.0.0.]
28476 - Do not use unaligned memory access on alpha, mips, or mipsel.
28477 It *works*, but is very slow, so we treat them as if it doesn't.
28478 - Retry directory requests if we fail to get an answer we like
28479 from a given dirserver (we were retrying before, but only if
28480 we fail to connect).
28481 - When writing the RecommendedVersions line, sort them first.
28482 - When the client asked for a rendezvous port that the hidden
28483 service didn't want to provide, we were sending an IP address
28484 back along with the end cell. Fortunately, it was zero. But stop
28486 - Correct "your server is reachable" log entries to indicate that
28487 it was self-testing that told us so.
28490 Changes in version 0.1.1.6-alpha - 2005-09-09
28491 o Fixes on 0.1.1.5-alpha:
28492 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
28493 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
28494 - Fix bug with tor_memmem finding a match at the end of the string.
28495 - Make unit tests run without segfaulting.
28496 - Resolve some solaris x86 compile warnings.
28497 - Handle duplicate lines in approved-routers files without warning.
28498 - Fix bug where as soon as a server refused any requests due to his
28499 exit policy (e.g. when we ask for localhost and he tells us that's
28500 127.0.0.1 and he won't do it), we decided he wasn't obeying his
28501 exit policy using him for any exits.
28502 - Only do openssl hardware accelerator stuff if openssl version is
28505 o New controller features/fixes:
28506 - Add a "RESETCONF" command so you can set config options like
28507 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
28508 a config option in the torrc with no value, then it clears it
28509 entirely (rather than setting it to its default).
28510 - Add a "GETINFO config-file" to tell us where torrc is.
28511 - Avoid sending blank lines when GETINFO replies should be empty.
28512 - Add a QUIT command for the controller (for using it manually).
28513 - Fix a bug in SAVECONF that was adding default dirservers and
28514 other redundant entries to the torrc file.
28516 o Start on the new directory design:
28517 - Generate, publish, cache, serve new network-status format.
28518 - Publish individual descriptors (by fingerprint, by "all", and by
28520 - Publish client and server recommended versions separately.
28521 - Allow tor_gzip_uncompress() to handle multiple concatenated
28522 compressed strings. Serve compressed groups of router
28523 descriptors. The compression logic here could be more
28525 - Distinguish v1 authorities (all currently trusted directories)
28526 from v2 authorities (all trusted directories).
28527 - Change DirServers config line to note which dirs are v1 authorities.
28528 - Add configuration option "V1AuthoritativeDirectory 1" which
28529 moria1, moria2, and tor26 should set.
28530 - Remove option when getting directory cache to see whether they
28531 support running-routers; they all do now. Replace it with one
28532 to see whether caches support v2 stuff.
28535 - Dirservers now do their own external reachability testing of each
28536 Tor server, and only list them as running if they've been found to
28537 be reachable. We also send back warnings to the server's logs if
28538 it uploads a descriptor that we already believe is unreachable.
28539 - Implement exit enclaves: if we know an IP address for the
28540 destination, and there's a running Tor server at that address
28541 which allows exit to the destination, then extend the circuit to
28542 that exit first. This provides end-to-end encryption and end-to-end
28543 authentication. Also, if the user wants a .exit address or enclave,
28544 use 4 hops rather than 3, and cannibalize a general circ for it
28546 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
28547 controller. Also, rotate dns and cpu workers if the controller
28548 changes options that will affect them; and initialize the dns
28549 worker cache tree whether or not we start out as a server.
28550 - Only upload a new server descriptor when options change, 18
28551 hours have passed, uptime is reset, or bandwidth changes a lot.
28552 - Check [X-]Forwarded-For headers in HTTP requests when generating
28553 log messages. This lets people run dirservers (and caches) behind
28554 Apache but still know which IP addresses are causing warnings.
28556 o Config option changes:
28557 - Replace (Fascist)Firewall* config options with a new
28558 ReachableAddresses option that understands address policies.
28559 For example, "ReachableAddresses *:80,*:443"
28560 - Get rid of IgnoreVersion undocumented config option, and make us
28561 only warn, never exit, when we're running an obsolete version.
28562 - Make MonthlyAccountingStart config option truly obsolete now.
28564 o Fixes on 0.1.0.x:
28565 - Reject ports 465 and 587 in the default exit policy, since
28566 people have started using them for spam too.
28567 - It turns out we couldn't bootstrap a network since we added
28568 reachability detection in 0.1.0.1-rc. Good thing the Tor network
28569 has never gone down. Add an AssumeReachable config option to let
28570 servers and dirservers bootstrap. When we're trying to build a
28571 high-uptime or high-bandwidth circuit but there aren't enough
28572 suitable servers, try being less picky rather than simply failing.
28573 - Our logic to decide if the OR we connected to was the right guy
28574 was brittle and maybe open to a mitm for unverified routers.
28575 - We weren't cannibalizing circuits correctly for
28576 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
28577 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
28578 build those from scratch. This should make hidden services faster.
28579 - Predict required circuits better, with an eye toward making hidden
28580 services faster on the service end.
28581 - Retry streams if the exit node sends back a 'misc' failure. This
28582 should result in fewer random failures. Also, after failing
28583 from resolve failed or misc, reset the num failures, so we give
28584 it a fair shake next time we try.
28585 - Clean up the rendezvous warn log msgs, and downgrade some to info.
28586 - Reduce severity on logs about dns worker spawning and culling.
28587 - When we're shutting down and we do something like try to post a
28588 server descriptor or rendezvous descriptor, don't complain that
28589 we seem to be unreachable. Of course we are, we're shutting down.
28590 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
28591 We don't use them yet, but maybe one day our DNS resolver will be
28592 able to discover them.
28593 - Make ContactInfo mandatory for authoritative directory servers.
28594 - Require server descriptors to list IPv4 addresses -- hostnames
28595 are no longer allowed. This also fixes some potential security
28596 problems with people providing hostnames as their address and then
28597 preferentially resolving them to partition users.
28598 - Change log line for unreachability to explicitly suggest /etc/hosts
28599 as the culprit. Also make it clearer what IP address and ports we're
28600 testing for reachability.
28601 - Put quotes around user-supplied strings when logging so users are
28602 more likely to realize if they add bad characters (like quotes)
28604 - Let auth dir servers start without specifying an Address config
28606 - Make unit tests (and other invocations that aren't the real Tor)
28607 run without launching listeners, creating subdirectories, and so on.
28610 Changes in version 0.1.1.5-alpha - 2005-08-08
28611 o Bugfixes included in 0.1.0.14.
28613 o Bugfixes on 0.1.0.x:
28614 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
28615 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
28616 it would silently using ignore the 6668.
28619 Changes in version 0.1.0.14 - 2005-08-08
28620 o Bugfixes on 0.1.0.x:
28621 - Fix the other half of the bug with crypto handshakes
28623 - Fix an assert trigger if you send a 'signal term' via the
28624 controller when it's listening for 'event info' messages.
28627 Changes in version 0.1.1.4-alpha - 2005-08-04
28628 o Bugfixes included in 0.1.0.13.
28631 - Improve tor_gettimeofday() granularity on windows.
28632 - Make clients regenerate their keys when their IP address changes.
28633 - Implement some more GETINFO goodness: expose helper nodes, config
28634 options, getinfo keys.
28637 Changes in version 0.1.0.13 - 2005-08-04
28638 o Bugfixes on 0.1.0.x:
28639 - Fix a critical bug in the security of our crypto handshakes.
28640 - Fix a size_t underflow in smartlist_join_strings2() that made
28641 it do bad things when you hand it an empty smartlist.
28642 - Fix Windows installer to ship Tor license (thanks to Aphex for
28643 pointing out this oversight) and put a link to the doc directory
28645 - Explicitly set no-unaligned-access for sparc: it turns out the
28646 new gcc's let you compile broken code, but that doesn't make it
28650 Changes in version 0.1.1.3-alpha - 2005-07-23
28651 o Bugfixes on 0.1.1.2-alpha:
28652 - Fix a bug in handling the controller's "post descriptor"
28654 - Fix several bugs in handling the controller's "extend circuit"
28656 - Fix a bug in handling the controller's "stream status" event.
28657 - Fix an assert failure if we have a controller listening for
28658 circuit events and we go offline.
28659 - Re-allow hidden service descriptors to publish 0 intro points.
28660 - Fix a crash when generating your hidden service descriptor if
28661 you don't have enough intro points already.
28663 o New features on 0.1.1.2-alpha:
28664 - New controller function "getinfo accounting", to ask how
28665 many bytes we've used in this time period.
28666 - Experimental support for helper nodes: a lot of the risk from
28667 a small static adversary comes because users pick new random
28668 nodes every time they rebuild a circuit. Now users will try to
28669 stick to the same small set of entry nodes if they can. Not
28670 enabled by default yet.
28672 o Bugfixes on 0.1.0.12:
28673 - If you're an auth dir server, always publish your dirport,
28674 even if you haven't yet found yourself to be reachable.
28675 - Fix a size_t underflow in smartlist_join_strings2() that made
28676 it do bad things when you hand it an empty smartlist.
28679 Changes in version 0.1.0.12 - 2005-07-18
28680 o New directory servers:
28681 - tor26 has changed IP address.
28683 o Bugfixes on 0.1.0.x:
28684 - Fix a possible double-free in tor_gzip_uncompress().
28685 - When --disable-threads is set, do not search for or link against
28686 pthreads libraries.
28687 - Don't trigger an assert if an authoritative directory server
28688 claims its dirport is 0.
28689 - Fix bug with removing Tor as an NT service: some people were
28690 getting "The service did not return an error." Thanks to Matt
28694 Changes in version 0.1.1.2-alpha - 2005-07-15
28695 o New directory servers:
28696 - tor26 has changed IP address.
28698 o Bugfixes on 0.1.0.x, crashes/leaks:
28699 - Port the servers-not-obeying-their-exit-policies fix from
28701 - Fix an fd leak in start_daemon().
28702 - On Windows, you can't always reopen a port right after you've
28703 closed it. So change retry_listeners() to only close and re-open
28704 ports that have changed.
28705 - Fix a possible double-free in tor_gzip_uncompress().
28707 o Bugfixes on 0.1.0.x, usability:
28708 - When tor_socketpair() fails in Windows, give a reasonable
28709 Windows-style errno back.
28710 - Let people type "tor --install" as well as "tor -install" when
28712 want to make it an NT service.
28713 - NT service patch from Matt Edman to improve error messages.
28714 - When the controller asks for a config option with an abbreviated
28715 name, give the full name in our response.
28716 - Correct the man page entry on TrackHostExitsExpire.
28717 - Looks like we were never delivering deflated (i.e. compressed)
28718 running-routers lists, even when asked. Oops.
28719 - When --disable-threads is set, do not search for or link against
28720 pthreads libraries.
28722 o Bugfixes on 0.1.1.x:
28723 - Fix a seg fault with autodetecting which controller version is
28727 - New hidden service descriptor format: put a version in it, and
28728 let people specify introduction/rendezvous points that aren't
28729 in "the directory" (which is subjective anyway).
28730 - Allow the DEBUG controller event to work again. Mark certain log
28731 entries as "don't tell this to controllers", so we avoid cycles.
28734 Changes in version 0.1.0.11 - 2005-06-30
28735 o Bugfixes on 0.1.0.x:
28736 - Fix major security bug: servers were disregarding their
28737 exit policies if clients behaved unexpectedly.
28738 - Make OS X init script check for missing argument, so we don't
28739 confuse users who invoke it incorrectly.
28740 - Fix a seg fault in "tor --hash-password foo".
28741 - The MAPADDRESS control command was broken.
28744 Changes in version 0.1.1.1-alpha - 2005-06-29
28746 - Make OS X init script check for missing argument, so we don't
28747 confuse users who invoke it incorrectly.
28748 - Fix a seg fault in "tor --hash-password foo".
28749 - Fix a possible way to DoS dirservers.
28750 - When we complain that your exit policy implicitly allows local or
28751 private address spaces, name them explicitly so operators can
28753 - Make the log message less scary when all the dirservers are
28754 temporarily unreachable.
28755 - We were printing the number of idle dns workers incorrectly when
28759 - Revised controller protocol (version 1) that uses ascii rather
28760 than binary. Add supporting libraries in python and java so you
28761 can use the controller from your applications without caring how
28762 our protocol works.
28763 - Spiffy new support for crypto hardware accelerators. Can somebody
28767 Changes in version 0.0.9.10 - 2005-06-16
28768 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
28769 - Refuse relay cells that claim to have a length larger than the
28770 maximum allowed. This prevents a potential attack that could read
28771 arbitrary memory (e.g. keys) from an exit server's process
28775 Changes in version 0.1.0.10 - 2005-06-14
28776 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
28777 libevent before 1.1a.
28780 Changes in version 0.1.0.9-rc - 2005-06-09
28782 - Reset buf->highwater every time buf_shrink() is called, not just on
28783 a successful shrink. This was causing significant memory bloat.
28784 - Fix buffer overflow when checking hashed passwords.
28785 - Security fix: if seeding the RNG on Win32 fails, quit.
28786 - Allow seeding the RNG on Win32 even when you're not running as
28788 - Disable threading on Solaris too. Something is wonky with it,
28789 cpuworkers, and reentrant libs.
28790 - Reenable the part of the code that tries to flush as soon as an
28791 OR outbuf has a full TLS record available. Perhaps this will make
28792 OR outbufs not grow as huge except in rare cases, thus saving lots
28793 of CPU time plus memory.
28794 - Reject malformed .onion addresses rather then passing them on as
28795 normal web requests.
28796 - Adapt patch from Adam Langley: fix possible memory leak in
28797 tor_lookup_hostname().
28798 - Initialize libevent later in the startup process, so the logs are
28799 already established by the time we start logging libevent warns.
28800 - Use correct errno on win32 if libevent fails.
28801 - Check and warn about known-bad/slow libevent versions.
28802 - Pay more attention to the ClientOnly config option.
28803 - Have torctl.in/tor.sh.in check for location of su binary (needed
28805 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
28806 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
28807 HttpProxyAuthenticator
28808 - Stop warning about sigpipes in the logs. We're going to
28809 pretend that getting these occasionally is normal and fine.
28810 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
28812 installer screens; and don't put stuff into StartupItems unless
28813 the user asks you to.
28814 - Require servers that use the default dirservers to have public IP
28815 addresses. We have too many servers that are configured with private
28816 IPs and their admins never notice the log entries complaining that
28817 their descriptors are being rejected.
28818 - Add OSX uninstall instructions. An actual uninstall script will
28822 Changes in version 0.1.0.8-rc - 2005-05-23
28824 - It turns out that kqueue on OS X 10.3.9 was causing kernel
28825 panics. Disable kqueue on all OS X Tors.
28826 - Fix RPM: remove duplicate line accidentally added to the rpm
28828 - Disable threads on openbsd too, since its gethostaddr is not
28830 - Tolerate libevent 0.8 since it still works, even though it's
28832 - Enable building on Red Hat 9.0 again.
28833 - Allow the middle hop of the testing circuit to be running any
28834 version, now that most of them have the bugfix to let them connect
28835 to unknown servers. This will allow reachability testing to work
28836 even when 0.0.9.7-0.0.9.9 become obsolete.
28837 - Handle relay cells with rh.length too large. This prevents
28838 a potential attack that could read arbitrary memory (maybe even
28839 keys) from the exit server's process.
28840 - We screwed up the dirport reachability testing when we don't yet
28841 have a cached version of the directory. Hopefully now fixed.
28842 - Clean up router_load_single_router() (used by the controller),
28843 so it doesn't seg fault on error.
28844 - Fix a minor memory leak when somebody establishes an introduction
28845 point at your Tor server.
28846 - If a socks connection ends because read fails, don't warn that
28847 you're not sending a socks reply back.
28850 - Add HttpProxyAuthenticator config option too, that works like
28851 the HttpsProxyAuthenticator config option.
28852 - Encode hashed controller passwords in hex instead of base64,
28853 to make it easier to write controllers.
28856 Changes in version 0.1.0.7-rc - 2005-05-17
28858 - Fix a bug in the OS X package installer that prevented it from
28859 installing on Tiger.
28860 - Fix a script bug in the OS X package installer that made it
28861 complain during installation.
28862 - Find libevent even if it's hiding in /usr/local/ and your
28863 CFLAGS and LDFLAGS don't tell you to look there.
28864 - Be able to link with libevent as a shared library (the default
28865 after 1.0d), even if it's hiding in /usr/local/lib and even
28866 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
28867 assuming you're running gcc. Otherwise fail and give a useful
28869 - Fix a bug in the RPM packager: set home directory for _tor to
28870 something more reasonable when first installing.
28871 - Free a minor amount of memory that is still reachable on exit.
28874 Changes in version 0.1.0.6-rc - 2005-05-14
28876 - Implement --disable-threads configure option. Disable threads on
28877 netbsd by default, because it appears to have no reentrant resolver
28879 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
28880 release (1.1) detects and disables kqueue if it's broken.
28881 - Append default exit policy before checking for implicit internal
28882 addresses. Now we don't log a bunch of complaints on startup
28883 when using the default exit policy.
28884 - Some people were putting "Address " in their torrc, and they had
28885 a buggy resolver that resolved " " to 0.0.0.0. Oops.
28886 - If DataDir is ~/.tor, and that expands to /.tor, then default to
28887 LOCALSTATEDIR/tor instead.
28888 - Fix fragmented-message bug in TorControl.py.
28889 - Resolve a minor bug which would prevent unreachable dirports
28890 from getting suppressed in the published descriptor.
28891 - When the controller gave us a new descriptor, we weren't resolving
28892 it immediately, so Tor would think its address was 0.0.0.0 until
28893 we fetched a new directory.
28894 - Fix an uppercase/lowercase case error in suppressing a bogus
28895 libevent warning on some Linuxes.
28898 - Begin scrubbing sensitive strings from logs by default. Turn off
28899 the config option SafeLogging if you need to do debugging.
28900 - Switch to a new buffer management algorithm, which tries to avoid
28901 reallocing and copying quite as much. In first tests it looks like
28902 it uses *more* memory on average, but less cpu.
28903 - First cut at support for "create-fast" cells. Clients can use
28904 these when extending to their first hop, since the TLS already
28905 provides forward secrecy and authentication. Not enabled on
28907 - When dirservers refuse a router descriptor, we now log its
28908 contactinfo, platform, and the poster's IP address.
28909 - Call tor_free_all instead of connections_free_all after forking, to
28910 save memory on systems that need to fork.
28911 - Whine at you if you're a server and you don't set your contactinfo.
28912 - Implement --verify-config command-line option to check if your torrc
28913 is valid without actually launching Tor.
28914 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
28915 rather than just rejecting it.
28918 Changes in version 0.1.0.5-rc - 2005-04-27
28920 - Stop trying to print a null pointer if an OR conn fails because
28921 we didn't like its cert.
28923 - Switch our internal buffers implementation to use a ring buffer,
28924 to hopefully improve performance for fast servers a lot.
28925 - Add HttpsProxyAuthenticator support (basic auth only), based
28926 on patch from Adam Langley.
28927 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
28928 the fast servers that have been joining lately.
28929 - Give hidden service accesses extra time on the first attempt,
28930 since 60 seconds is often only barely enough. This might improve
28932 - Improve performance for dirservers: stop re-parsing the whole
28933 directory every time you regenerate it.
28934 - Add more debugging info to help us find the weird dns freebsd
28935 pthreads bug; cleaner debug messages to help track future issues.
28938 Changes in version 0.0.9.9 - 2005-04-23
28939 o Bugfixes on 0.0.9.x:
28940 - If unofficial Tor clients connect and send weird TLS certs, our
28941 Tor server triggers an assert. This release contains a minimal
28942 backport from the broader fix that we put into 0.1.0.4-rc.
28945 Changes in version 0.1.0.4-rc - 2005-04-23
28947 - If unofficial Tor clients connect and send weird TLS certs, our
28948 Tor server triggers an assert. Stop asserting, and start handling
28949 TLS errors better in other situations too.
28950 - When the controller asks us to tell it about all the debug-level
28951 logs, it turns out we were generating debug-level logs while
28952 telling it about them, which turns into a bad loop. Now keep
28953 track of whether you're sending a debug log to the controller,
28954 and don't log when you are.
28955 - Fix the "postdescriptor" feature of the controller interface: on
28956 non-complete success, only say "done" once.
28958 - Clients are now willing to load balance over up to 2mB, not 1mB,
28959 of advertised bandwidth capacity.
28960 - Add a NoPublish config option, so you can be a server (e.g. for
28961 testing running Tor servers in other Tor networks) without
28962 publishing your descriptor to the primary dirservers.
28965 Changes in version 0.1.0.3-rc - 2005-04-08
28966 o Improvements on 0.1.0.2-rc:
28967 - Client now retries when streams end early for 'hibernating' or
28968 'resource limit' reasons, rather than failing them.
28969 - More automated handling for dirserver operators:
28970 - Automatically approve nodes running 0.1.0.2-rc or later,
28971 now that the the reachability detection stuff is working.
28972 - Now we allow two unverified servers with the same nickname
28973 but different keys. But if a nickname is verified, only that
28974 nickname+key are allowed.
28975 - If you're an authdirserver connecting to an address:port,
28976 and it's not the OR you were expecting, forget about that
28977 descriptor. If he *was* the one you were expecting, then forget
28978 about all other descriptors for that address:port.
28979 - Allow servers to publish descriptors from 12 hours in the future.
28980 Corollary: only whine about clock skew from the dirserver if
28981 he's a trusted dirserver (since now even verified servers could
28982 have quite wrong clocks).
28983 - Adjust maximum skew and age for rendezvous descriptors: let skew
28984 be 48 hours rather than 90 minutes.
28985 - Efficiency improvements:
28986 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
28987 it much faster to look up a circuit for each relay cell.
28988 - Remove most calls to assert_all_pending_dns_resolves_ok(),
28989 since they're eating our cpu on exit nodes.
28990 - Stop wasting time doing a case insensitive comparison for every
28991 dns name every time we do any lookup. Canonicalize the names to
28992 lowercase and be done with it.
28993 - Start sending 'truncated' cells back rather than destroy cells,
28994 if the circuit closes in front of you. This means we won't have
28995 to abandon partially built circuits.
28996 - Only warn once per nickname from add_nickname_list_to_smartlist
28997 per failure, so an entrynode or exitnode choice that's down won't
28999 - Put a note in the torrc about abuse potential with the default
29001 - Revise control spec and implementation to allow all log messages to
29002 be sent to controller with their severities intact (suggested by
29003 Matt Edman). Update TorControl to handle new log event types.
29004 - Provide better explanation messages when controller's POSTDESCRIPTOR
29006 - Stop putting nodename in the Platform string in server descriptors.
29007 It doesn't actually help, and it is confusing/upsetting some people.
29009 o Bugfixes on 0.1.0.2-rc:
29010 - We were printing the host mask wrong in exit policies in server
29011 descriptors. This isn't a critical bug though, since we were still
29012 obeying the exit policy internally.
29013 - Fix Tor when compiled with libevent but without pthreads: move
29014 connection_unregister() from _connection_free() to
29016 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
29017 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
29018 when we look through the connection array, we'll find any of the
29019 cpu/dnsworkers. This is no good.
29021 o Bugfixes on 0.0.9.8:
29022 - Fix possible bug on threading platforms (e.g. win32) which was
29023 leaking a file descriptor whenever a cpuworker or dnsworker died.
29024 - When using preferred entry or exit nodes, ignore whether the
29025 circuit wants uptime or capacity. They asked for the nodes, they
29027 - chdir() to your datadirectory at the *end* of the daemonize process,
29028 not the beginning. This was a problem because the first time you
29029 run tor, if your datadir isn't there, and you have runasdaemon set
29030 to 1, it will try to chdir to it before it tries to create it. Oops.
29031 - Handle changed router status correctly when dirserver reloads
29032 fingerprint file. We used to be dropping all unverified descriptors
29033 right then. The bug was hidden because we would immediately
29034 fetch a directory from another dirserver, which would include the
29035 descriptors we just dropped.
29036 - When we're connecting to an OR and he's got a different nickname/key
29037 than we were expecting, only complain loudly if we're an OP or a
29038 dirserver. Complaining loudly to the OR admins just confuses them.
29039 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
29040 artificially capped at 500kB.
29043 Changes in version 0.0.9.8 - 2005-04-07
29044 o Bugfixes on 0.0.9.x:
29045 - We have a bug that I haven't found yet. Sometimes, very rarely,
29046 cpuworkers get stuck in the 'busy' state, even though the cpuworker
29047 thinks of itself as idle. This meant that no new circuits ever got
29048 established. Here's a workaround to kill any cpuworker that's been
29049 busy for more than 100 seconds.
29052 Changes in version 0.1.0.2-rc - 2005-04-01
29053 o Bugfixes on 0.1.0.1-rc:
29054 - Fixes on reachability detection:
29055 - Don't check for reachability while hibernating.
29056 - If ORPort is reachable but DirPort isn't, still publish the
29057 descriptor, but zero out DirPort until it's found reachable.
29058 - When building testing circs for ORPort testing, use only
29059 high-bandwidth nodes, so fewer circuits fail.
29060 - Complain about unreachable ORPort separately from unreachable
29061 DirPort, so the user knows what's going on.
29062 - Make sure we only conclude ORPort reachability if we didn't
29063 initiate the conn. Otherwise we could falsely conclude that
29064 we're reachable just because we connected to the guy earlier
29065 and he used that same pipe to extend to us.
29066 - Authdirservers shouldn't do ORPort reachability detection,
29067 since they're in clique mode, so it will be rare to find a
29068 server not already connected to them.
29069 - When building testing circuits, always pick middle hops running
29070 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
29071 bug. (This is a kludge; it will go away when 0.0.9.x becomes
29073 - When we decide we're reachable, actually publish our descriptor
29075 - Fix bug in redirectstream in the controller.
29076 - Fix the state descriptor strings so logs don't claim edge streams
29077 are in a different state than they actually are.
29078 - Use recent libevent features when possible (this only really affects
29079 win32 and osx right now, because the new libevent with these
29080 features hasn't been released yet). Add code to suppress spurious
29082 - Prevent possible segfault in connection_close_unattached_ap().
29083 - Fix newlines on torrc in win32.
29084 - Improve error msgs when tor-resolve fails.
29086 o Improvements on 0.0.9.x:
29087 - New experimental script tor/contrib/ExerciseServer.py (needs more
29088 work) that uses the controller interface to build circuits and
29089 fetch pages over them. This will help us bootstrap servers that
29090 have lots of capacity but haven't noticed it yet.
29091 - New experimental script tor/contrib/PathDemo.py (needs more work)
29092 that uses the controller interface to let you choose whole paths
29094 "<hostname>.<path,separated by dots>.<length of path>.path"
29095 - When we've connected to an OR and handshaked but didn't like
29096 the result, we were closing the conn without sending destroy
29097 cells back for pending circuits. Now send those destroys.
29100 Changes in version 0.0.9.7 - 2005-04-01
29101 o Bugfixes on 0.0.9.x:
29102 - Fix another race crash bug (thanks to Glenn Fink for reporting).
29103 - Compare identity to identity, not to nickname, when extending to
29104 a router not already in the directory. This was preventing us from
29105 extending to unknown routers. Oops.
29106 - Make sure to create OS X Tor user in <500 range, so we aren't
29107 creating actual system users.
29108 - Note where connection-that-hasn't-sent-end was marked, and fix
29109 a few really loud instances of this harmless bug (it's fixed more
29113 Changes in version 0.1.0.1-rc - 2005-03-28
29115 - Add reachability testing. Your Tor server will automatically try
29116 to see if its ORPort and DirPort are reachable from the outside,
29117 and it won't upload its descriptor until it decides they are.
29118 - Handle unavailable hidden services better. Handle slow or busy
29119 hidden services better.
29120 - Add support for CONNECTing through https proxies, with "HttpsProxy"
29122 - New exit policy: accept most low-numbered ports, rather than
29123 rejecting most low-numbered ports.
29124 - More Tor controller support (still experimental). See
29125 http://tor.eff.org/doc/control-spec.txt for all the new features,
29126 including signals to emulate unix signals from any platform;
29127 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
29128 closestream; closecircuit; etc.
29129 - Make nt services work and start on startup on win32 (based on
29130 patch by Matt Edman).
29131 - Add a new AddressMap config directive to rewrite incoming socks
29132 addresses. This lets you, for example, declare an implicit
29133 required exit node for certain sites.
29134 - Add a new TrackHostExits config directive to trigger addressmaps
29135 for certain incoming socks addresses -- for sites that break when
29136 your exit keeps changing (based on patch by Mike Perry).
29137 - Redo the client-side dns cache so it's just an addressmap too.
29138 - Notice when our IP changes, and reset stats/uptime/reachability.
29139 - When an application is using socks5, give him the whole variety of
29140 potential socks5 responses (connect refused, host unreachable, etc),
29141 rather than just "success" or "failure".
29142 - A more sane version numbering system. See
29143 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
29144 - New contributed script "exitlist": a simple python script to
29145 parse directories and find Tor nodes that exit to listed
29147 - New contributed script "privoxy-tor-toggle" to toggle whether
29148 Privoxy uses Tor. Seems to be configured for Debian by default.
29149 - Report HTTP reasons to client when getting a response from directory
29150 servers -- so you can actually know what went wrong.
29151 - New config option MaxAdvertisedBandwidth which lets you advertise
29152 a low bandwidthrate (to not attract as many circuits) while still
29153 allowing a higher bandwidthrate in reality.
29155 o Robustness/stability fixes:
29156 - Make Tor use Niels Provos's libevent instead of its current
29157 poll-but-sometimes-select mess. This will let us use faster async
29158 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
29160 - pthread support now too. This was forced because when we forked,
29161 we ended up wasting a lot of duplicate ram over time. Also switch
29162 to foo_r versions of some library calls to allow reentry and
29164 - Better handling for heterogeneous / unreliable nodes:
29165 - Annotate circuits w/ whether they aim to contain high uptime nodes
29166 and/or high capacity nodes. When building circuits, choose
29168 - This means that every single node in an intro rend circuit,
29169 not just the last one, will have a minimum uptime.
29170 - New config option LongLivedPorts to indicate application streams
29171 that will want high uptime circuits.
29172 - Servers reset uptime when a dir fetch entirely fails. This
29173 hopefully reflects stability of the server's network connectivity.
29174 - If somebody starts his tor server in Jan 2004 and then fixes his
29175 clock, don't make his published uptime be a year.
29176 - Reset published uptime when you wake up from hibernation.
29177 - Introduce a notion of 'internal' circs, which are chosen without
29178 regard to the exit policy of the last hop. Intro and rendezvous
29179 circs must be internal circs, to avoid leaking information. Resolve
29180 and connect streams can use internal circs if they want.
29181 - New circuit pooling algorithm: make sure to have enough circs around
29182 to satisfy any predicted ports, and also make sure to have 2 internal
29183 circs around if we've required internal circs lately (and with high
29184 uptime if we've seen that lately too).
29185 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
29186 which describes how often we retry making new circuits if current
29187 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
29188 how long we're willing to make use of an already-dirty circuit.
29189 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
29190 circ as necessary, if there are any completed ones lying around
29191 when we try to launch one.
29192 - Make hidden services try to establish a rendezvous for 30 seconds,
29193 rather than for n (where n=3) attempts to build a circuit.
29194 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
29195 "ShutdownWaitLength".
29196 - Try to be more zealous about calling connection_edge_end when
29197 things go bad with edge conns in connection.c.
29198 - Revise tor-spec to add more/better stream end reasons.
29199 - Revise all calls to connection_edge_end to avoid sending "misc",
29200 and to take errno into account where possible.
29203 - Fix a race condition that can trigger an assert, when we have a
29204 pending create cell and an OR connection fails right then.
29205 - Fix several double-mark-for-close bugs, e.g. where we were finding
29206 a conn for a cell even if that conn is already marked for close.
29207 - Make sequence of log messages when starting on win32 with no config
29208 file more reasonable.
29209 - When choosing an exit node for a new non-internal circ, don't take
29210 into account whether it'll be useful for any pending x.onion
29211 addresses -- it won't.
29212 - Turn addr_policy_compare from a tristate to a quadstate; this should
29213 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
29214 for google.com" problem.
29215 - Make "platform" string in descriptor more accurate for Win32 servers,
29216 so it's not just "unknown platform".
29217 - Fix an edge case in parsing config options (thanks weasel).
29218 If they say "--" on the commandline, it's not an option.
29219 - Reject odd-looking addresses at the client (e.g. addresses that
29220 contain a colon), rather than having the server drop them because
29222 - tor-resolve requests were ignoring .exit if there was a working circuit
29223 they could use instead.
29224 - REUSEADDR on normal platforms means you can rebind to the port
29225 right after somebody else has let it go. But REUSEADDR on win32
29226 means to let you bind to the port _even when somebody else
29227 already has it bound_! So, don't do that on Win32.
29228 - Change version parsing logic: a version is "obsolete" if it is not
29229 recommended and (1) there is a newer recommended version in the
29230 same series, or (2) there are no recommended versions in the same
29231 series, but there are some recommended versions in a newer series.
29232 A version is "new" if it is newer than any recommended version in
29234 - Stop most cases of hanging up on a socks connection without sending
29238 - Require BandwidthRate to be at least 20kB/s for servers.
29239 - When a dirserver causes you to give a warn, mention which dirserver
29241 - New config option DirAllowPrivateAddresses for authdirservers.
29242 Now by default they refuse router descriptors that have non-IP or
29243 private-IP addresses.
29244 - Stop publishing socksport in the directory, since it's not
29245 actually meant to be public. For compatibility, publish a 0 there
29247 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
29248 smart" value, that is low for servers and high for clients.
29249 - If our clock jumps forward by 100 seconds or more, assume something
29250 has gone wrong with our network and abandon all not-yet-used circs.
29251 - Warn when exit policy implicitly allows local addresses.
29252 - If we get an incredibly skewed timestamp from a dirserver mirror
29253 that isn't a verified OR, don't warn -- it's probably him that's
29255 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
29256 cookies to disk and doesn't log each web request to disk. (Thanks
29257 to Brett Carrington for pointing this out.)
29258 - When a client asks us for a dir mirror and we don't have one,
29259 launch an attempt to get a fresh one.
29260 - If we're hibernating and we get a SIGINT, exit immediately.
29261 - Add --with-dmalloc ./configure option, to track memory leaks.
29262 - And try to free all memory on closing, so we can detect what
29264 - Cache local dns resolves correctly even when they're .exit
29266 - Give a better warning when some other server advertises an
29267 ORPort that is actually an apache running ssl.
29268 - Add "opt hibernating 1" to server descriptor to make it clearer
29269 whether the server is hibernating.
29272 Changes in version 0.0.9.6 - 2005-03-24
29273 o Bugfixes on 0.0.9.x (crashes and asserts):
29274 - Add new end stream reasons to maintenance branch. Fix bug where
29275 reason (8) could trigger an assert. Prevent bug from recurring.
29276 - Apparently win32 stat wants paths to not end with a slash.
29277 - Fix assert triggers in assert_cpath_layer_ok(), where we were
29278 blowing away the circuit that conn->cpath_layer points to, then
29279 checking to see if the circ is well-formed. Backport check to make
29280 sure we dont use the cpath on a closed connection.
29281 - Prevent circuit_resume_edge_reading_helper() from trying to package
29282 inbufs for marked-for-close streams.
29283 - Don't crash on hup if your options->address has become unresolvable.
29284 - Some systems (like OS X) sometimes accept() a connection and tell
29285 you the remote host is 0.0.0.0:0. If this happens, due to some
29286 other mis-features, we get confused; so refuse the conn for now.
29288 o Bugfixes on 0.0.9.x (other):
29289 - Fix harmless but scary "Unrecognized content encoding" warn message.
29290 - Add new stream error reason: TORPROTOCOL reason means "you are not
29291 speaking a version of Tor I understand; say bye-bye to your stream."
29292 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
29293 into the future, now that we are more tolerant of skew. This
29294 resolves a bug where a Tor server would refuse to cache a directory
29295 because all the directories it gets are too far in the future;
29296 yet the Tor server never logs any complaints about clock skew.
29297 - Mac packaging magic: make man pages useable, and do not overwrite
29298 existing torrc files.
29299 - Make OS X log happily to /var/log/tor/tor.log
29302 Changes in version 0.0.9.5 - 2005-02-22
29303 o Bugfixes on 0.0.9.x:
29304 - Fix an assert race at exit nodes when resolve requests fail.
29305 - Stop picking unverified dir mirrors--it only leads to misery.
29306 - Patch from Matt Edman to make NT services work better. Service
29307 support is still not compiled into the executable by default.
29308 - Patch from Dmitri Bely so the Tor service runs better under
29309 the win32 SYSTEM account.
29310 - Make tor-resolve actually work (?) on Win32.
29311 - Fix a sign bug when getrlimit claims to have 4+ billion
29312 file descriptors available.
29313 - Stop refusing to start when bandwidthburst == bandwidthrate.
29314 - When create cells have been on the onion queue more than five
29315 seconds, just send back a destroy and take them off the list.
29318 Changes in version 0.0.9.4 - 2005-02-03
29319 o Bugfixes on 0.0.9:
29320 - Fix an assert bug that took down most of our servers: when
29321 a server claims to have 1 GB of bandwidthburst, don't
29323 - Don't crash as badly if we have spawned the max allowed number
29324 of dnsworkers, or we're out of file descriptors.
29325 - Block more file-sharing ports in the default exit policy.
29326 - MaxConn is now automatically set to the hard limit of max
29327 file descriptors we're allowed (ulimit -n), minus a few for
29329 - Give a clearer message when servers need to raise their
29330 ulimit -n when they start running out of file descriptors.
29331 - SGI Compatibility patches from Jan Schaumann.
29332 - Tolerate a corrupt cached directory better.
29333 - When a dirserver hasn't approved your server, list which one.
29334 - Go into soft hibernation after 95% of the bandwidth is used,
29335 not 99%. This is especially important for daily hibernators who
29336 have a small accounting max. Hopefully it will result in fewer
29337 cut connections when the hard hibernation starts.
29338 - Load-balance better when using servers that claim more than
29339 800kB/s of capacity.
29340 - Make NT services work (experimental, only used if compiled in).
29343 Changes in version 0.0.9.3 - 2005-01-21
29344 o Bugfixes on 0.0.9:
29345 - Backport the cpu use fixes from main branch, so busy servers won't
29346 need as much processor time.
29347 - Work better when we go offline and then come back, or when we
29348 run Tor at boot before the network is up. We do this by
29349 optimistically trying to fetch a new directory whenever an
29350 application request comes in and we think we're offline -- the
29351 human is hopefully a good measure of when the network is back.
29352 - Backport some minimal hidserv bugfixes: keep rend circuits open as
29353 long as you keep using them; actually publish hidserv descriptors
29354 shortly after they change, rather than waiting 20-40 minutes.
29355 - Enable Mac startup script by default.
29356 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
29357 - When you update AllowUnverifiedNodes or FirewallPorts via the
29358 controller's setconf feature, we were always appending, never
29360 - When you update HiddenServiceDir via setconf, it was screwing up
29361 the order of reading the lines, making it fail.
29362 - Do not rewrite a cached directory back to the cache; otherwise we
29363 will think it is recent and not fetch a newer one on startup.
29364 - Workaround for webservers that lie about Content-Encoding: Tor
29365 now tries to autodetect compressed directories and compression
29366 itself. This lets us Proxypass dir fetches through apache.
29369 Changes in version 0.0.9.2 - 2005-01-04
29370 o Bugfixes on 0.0.9 (crashes and asserts):
29371 - Fix an assert on startup when the disk is full and you're logging
29373 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
29374 style address, then we'd crash.
29375 - Fix an assert trigger when the running-routers string we get from
29376 a dirserver is broken.
29377 - Make worker threads start and run on win32. Now win32 servers
29379 - Bandaid (not actually fix, but now it doesn't crash) an assert
29380 where the dns worker dies mysteriously and the main Tor process
29381 doesn't remember anything about the address it was resolving.
29383 o Bugfixes on 0.0.9 (Win32):
29384 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
29385 name out of the warning/assert messages.
29386 - Fix a superficial "unhandled error on read" bug on win32.
29387 - The win32 installer no longer requires a click-through for our
29388 license, since our Free Software license grants rights but does not
29390 - Win32: When connecting to a dirserver fails, try another one
29391 immediately. (This was already working for non-win32 Tors.)
29392 - Stop trying to parse $HOME on win32 when hunting for default
29394 - Make tor-resolve.c work on win32 by calling network_init().
29396 o Bugfixes on 0.0.9 (other):
29397 - Make 0.0.9.x build on Solaris again.
29398 - Due to a fencepost error, we were blowing away the \n when reporting
29399 confvalue items in the controller. So asking for multiple config
29400 values at once couldn't work.
29401 - When listing circuits that are pending on an opening OR connection,
29402 if we're an OR we were listing circuits that *end* at us as
29403 being pending on every listener, dns/cpu worker, etc. Stop that.
29404 - Dirservers were failing to create 'running-routers' or 'directory'
29405 strings if we had more than some threshold of routers. Fix them so
29406 they can handle any number of routers.
29407 - Fix a superficial "Duplicate mark for close" bug.
29408 - Stop checking for clock skew for OR connections, even for servers.
29409 - Fix a fencepost error that was chopping off the last letter of any
29410 nickname that is the maximum allowed nickname length.
29411 - Update URLs in log messages so they point to the new website.
29412 - Fix a potential problem in mangling server private keys while
29413 writing to disk (not triggered yet, as far as we know).
29414 - Include the licenses for other free software we include in Tor,
29415 now that we're shipping binary distributions more regularly.
29418 Changes in version 0.0.9.1 - 2004-12-15
29419 o Bugfixes on 0.0.9:
29420 - Make hibernation actually work.
29421 - Make HashedControlPassword config option work.
29422 - When we're reporting event circuit status to a controller,
29423 don't use the stream status code.
29426 Changes in version 0.0.9 - 2004-12-12
29428 - Clean up manpage and torrc.sample file.
29429 - Clean up severities and text of log warnings.
29431 - Make servers trigger an assert when they enter hibernation.
29434 Changes in version 0.0.9rc7 - 2004-12-08
29435 o Bugfixes on 0.0.9rc:
29436 - Fix a stack-trashing crash when an exit node begins hibernating.
29437 - Avoid looking at unallocated memory while considering which
29438 ports we need to build circuits to cover.
29439 - Stop a sigpipe: when an 'end' cell races with eof from the app,
29440 we shouldn't hold-open-until-flush if the eof arrived first.
29441 - Fix a bug with init_cookie_authentication() in the controller.
29442 - When recommending new-format log lines, if the upper bound is
29443 LOG_ERR, leave it implicit.
29445 o Bugfixes on 0.0.8.1:
29446 - Fix a whole slew of memory leaks.
29447 - Fix isspace() and friends so they still make Solaris happy
29448 but also so they don't trigger asserts on win32.
29449 - Fix parse_iso_time on platforms without strptime (eg win32).
29450 - win32: tolerate extra "readable" events better.
29451 - win32: when being multithreaded, leave parent fdarray open.
29452 - Make unit tests work on win32.
29455 Changes in version 0.0.9rc6 - 2004-12-06
29456 o Bugfixes on 0.0.9pre:
29457 - Clean up some more integer underflow opportunities (not exploitable
29459 - While hibernating, hup should not regrow our listeners.
29460 - Send an end to the streams we close when we hibernate, rather
29461 than just chopping them off.
29462 - React to eof immediately on non-open edge connections.
29464 o Bugfixes on 0.0.8.1:
29465 - Calculate timeout for waiting for a connected cell from the time
29466 we sent the begin cell, not from the time the stream started. If
29467 it took a long time to establish the circuit, we would time out
29468 right after sending the begin cell.
29469 - Fix router_compare_addr_to_addr_policy: it was not treating a port
29470 of * as always matching, so we were picking reject *:* nodes as
29471 exit nodes too. Oops.
29474 - New circuit building strategy: keep a list of ports that we've
29475 used in the past 6 hours, and always try to have 2 circuits open
29476 or on the way that will handle each such port. Seed us with port
29477 80 so web users won't complain that Tor is "slow to start up".
29478 - Make kill -USR1 dump more useful stats about circuits.
29479 - When warning about retrying or giving up, print the address, so
29480 the user knows which one it's talking about.
29481 - If you haven't used a clean circuit in an hour, throw it away,
29482 just to be on the safe side. (This means after 6 hours a totally
29483 unused Tor client will have no circuits open.)
29486 Changes in version 0.0.9rc5 - 2004-12-01
29487 o Bugfixes on 0.0.8.1:
29488 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
29489 - Let resolve conns retry/expire also, rather than sticking around
29491 - If we are using select, make sure we stay within FD_SETSIZE.
29493 o Bugfixes on 0.0.9pre:
29494 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
29495 but doesn't seem to be currently; thanks to Ilja van Sprundel for
29497 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
29498 instead. Impose minima and maxima for all *Period options; impose
29499 even tighter maxima for fetching if we are a caching dirserver.
29500 Clip rather than rejecting.
29501 - Fetch cached running-routers from servers that serve it (that is,
29502 authdirservers and servers running 0.0.9rc5-cvs or later.)
29505 - Accept *:706 (silc) in default exit policy.
29506 - Implement new versioning format for post 0.1.
29507 - Support "foo.nickname.exit" addresses, to let Alice request the
29508 address "foo" as viewed by exit node "nickname". Based on a patch
29510 - Make tor --version --version dump the cvs Id of every file.
29513 Changes in version 0.0.9rc4 - 2004-11-28
29514 o Bugfixes on 0.0.8.1:
29515 - Make windows sockets actually non-blocking (oops), and handle
29516 win32 socket errors better.
29518 o Bugfixes on 0.0.9rc1:
29519 - Actually catch the -USR2 signal.
29522 Changes in version 0.0.9rc3 - 2004-11-25
29523 o Bugfixes on 0.0.8.1:
29524 - Flush the log file descriptor after we print "Tor opening log file",
29525 so we don't see those messages days later.
29527 o Bugfixes on 0.0.9rc1:
29528 - Make tor-resolve work again.
29529 - Avoid infinite loop in tor-resolve if tor hangs up on it.
29530 - Fix an assert trigger for clients/servers handling resolves.
29533 Changes in version 0.0.9rc2 - 2004-11-24
29534 o Bugfixes on 0.0.9rc1:
29535 - I broke socks5 support while fixing the eof bug.
29536 - Allow unitless bandwidths and intervals; they default to bytes
29538 - New servers don't start out hibernating; they are active until
29539 they run out of bytes, so they have a better estimate of how
29540 long it takes, and so their operators can know they're working.
29543 Changes in version 0.0.9rc1 - 2004-11-23
29544 o Bugfixes on 0.0.8.1:
29545 - Finally fix a bug that's been plaguing us for a year:
29546 With high load, circuit package window was reaching 0. Whenever
29547 we got a circuit-level sendme, we were reading a lot on each
29548 socket, but only writing out a bit. So we would eventually reach
29549 eof. This would be noticed and acted on even when there were still
29550 bytes sitting in the inbuf.
29551 - When poll() is interrupted, we shouldn't believe the revents values.
29553 o Bugfixes on 0.0.9pre6:
29554 - Fix hibernate bug that caused pre6 to be broken.
29555 - Don't keep rephist info for routers that haven't had activity for
29556 24 hours. (This matters now that clients have keys, since we track
29558 - Never call close_temp_logs while validating log options.
29559 - Fix backslash-escaping on tor.sh.in and torctl.in.
29562 - Implement weekly/monthly/daily accounting: now you specify your
29563 hibernation properties by
29564 AccountingMax N bytes|KB|MB|GB|TB
29565 AccountingStart day|week|month [day] HH:MM
29566 Defaults to "month 1 0:00".
29567 - Let bandwidth and interval config options be specified as 5 bytes,
29568 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
29569 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
29570 get back to normal.)
29571 - If your requested entry or exit node has advertised bandwidth 0,
29573 - Be more greedy about filling up relay cells -- we try reading again
29574 once we've processed the stuff we read, in case enough has arrived
29575 to fill the last cell completely.
29576 - Apply NT service patch from Osamu Fujino. Still needs more work.
29579 Changes in version 0.0.9pre6 - 2004-11-15
29580 o Bugfixes on 0.0.8.1:
29581 - Fix assert failure on malformed socks4a requests.
29582 - Use identity comparison, not nickname comparison, to choose which
29583 half of circuit-ID-space each side gets to use. This is needed
29584 because sometimes we think of a router as a nickname, and sometimes
29585 as a hex ID, and we can't predict what the other side will do.
29586 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
29587 write() call will fail and we handle it there.
29588 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
29589 and smartlist_len, which are two major profiling offenders.
29591 o Bugfixes on 0.0.9pre5:
29592 - Fix a bug in read_all that was corrupting config files on windows.
29593 - When we're raising the max number of open file descriptors to
29594 'unlimited', don't log that we just raised it to '-1'.
29595 - Include event code with events, as required by control-spec.txt.
29596 - Don't give a fingerprint when clients do --list-fingerprint:
29597 it's misleading, because it will never be the same again.
29598 - Stop using strlcpy in tor_strndup, since it was slowing us
29600 - Remove warn on startup about missing cached-directory file.
29601 - Make kill -USR1 work again.
29602 - Hibernate if we start tor during the "wait for wakeup-time" phase
29603 of an accounting interval. Log our hibernation plans better.
29604 - Authoritative dirservers now also cache their directory, so they
29605 have it on start-up.
29608 - Fetch running-routers; cache running-routers; compress
29609 running-routers; serve compressed running-routers.z
29610 - Add NSI installer script contributed by J Doe.
29611 - Commit VC6 and VC7 workspace/project files.
29612 - Commit a tor.spec for making RPM files, with help from jbash.
29613 - Add contrib/torctl.in contributed by Glenn Fink.
29614 - Implement the control-spec's SAVECONF command, to write your
29615 configuration to torrc.
29616 - Get cookie authentication for the controller closer to working.
29617 - Include control-spec.txt in the tarball.
29618 - When set_conf changes our server descriptor, upload a new copy.
29619 But don't upload it too often if there are frequent changes.
29620 - Document authentication config in man page, and document signals
29622 - Clean up confusing parts of man page and torrc.sample.
29623 - Make expand_filename handle ~ and ~username.
29624 - Use autoconf to enable largefile support where necessary. Use
29625 ftello where available, since ftell can fail at 2GB.
29626 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
29627 log more informatively.
29628 - Give a slightly more useful output for "tor -h".
29629 - Refuse application socks connections to port 0.
29630 - Check clock skew for verified servers, but allow unverified
29631 servers and clients to have any clock skew.
29632 - Break DirFetchPostPeriod into:
29633 - DirFetchPeriod for fetching full directory,
29634 - StatusFetchPeriod for fetching running-routers,
29635 - DirPostPeriod for posting server descriptor,
29636 - RendPostPeriod for posting hidden service descriptors.
29637 - Make sure the hidden service descriptors are at a random offset
29638 from each other, to hinder linkability.
29641 Changes in version 0.0.9pre5 - 2004-11-09
29642 o Bugfixes on 0.0.9pre4:
29643 - Fix a seg fault in unit tests (doesn't affect main program).
29644 - Fix an assert bug where a hidden service provider would fail if
29645 the first hop of his rendezvous circuit was down.
29646 - Hidden service operators now correctly handle version 1 style
29647 INTRODUCE1 cells (nobody generates them still, so not a critical
29649 - If do_hup fails, actually notice.
29650 - Handle more errnos from accept() without closing the listener.
29651 Some OpenBSD machines were closing their listeners because
29652 they ran out of file descriptors.
29653 - Send resolve cells to exit routers that are running a new
29654 enough version of the resolve code to work right.
29655 - Better handling of winsock includes on non-MSV win32 compilers.
29656 - Some people had wrapped their tor client/server in a script
29657 that would restart it whenever it died. This did not play well
29658 with our "shut down if your version is obsolete" code. Now people
29659 don't fetch a new directory if their local cached version is
29661 - Make our autogen.sh work on ksh as well as bash.
29664 - Hibernation: New config option "AccountingMaxKB" lets you
29665 set how many KBytes per month you want to allow your server to
29666 consume. Rather than spreading those bytes out evenly over the
29667 month, we instead hibernate for some of the month and pop up
29668 at a deterministic time, work until the bytes are consumed, then
29669 hibernate again. Config option "MonthlyAccountingStart" lets you
29670 specify which day of the month your billing cycle starts on.
29671 - Control interface: a separate program can now talk to your
29672 client/server over a socket, and get/set config options, receive
29673 notifications of circuits and streams starting/finishing/dying,
29674 bandwidth used, etc. The next step is to get some GUIs working.
29675 Let us know if you want to help out. See doc/control-spec.txt .
29676 - Ship a contrib/tor-control.py as an example script to interact
29677 with the control port.
29678 - "tor --hash-password zzyxz" will output a salted password for
29679 use in authenticating to the control interface.
29680 - New log format in config:
29681 "Log minsev[-maxsev] stdout|stderr|syslog" or
29682 "Log minsev[-maxsev] file /var/foo"
29685 - DirPolicy config option, to let people reject incoming addresses
29686 from their dirserver.
29687 - "tor --list-fingerprint" will list your identity key fingerprint
29689 - Add "pass" target for RedirectExit, to make it easier to break
29690 out of a sequence of RedirectExit rules.
29691 - Clients now generate a TLS cert too, in preparation for having
29692 them act more like real nodes.
29693 - Ship src/win32/ in the tarball, so people can use it to build.
29694 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
29696 - New "router-status" line in directory, to better bind each verified
29697 nickname to its identity key.
29698 - Deprecate unofficial config option abbreviations, and abbreviations
29699 not on the command line.
29700 - Add a pure-C tor-resolve implementation.
29701 - Use getrlimit and friends to ensure we can reach MaxConn (currently
29702 1024) file descriptors.
29704 o Code security improvements, inspired by Ilja:
29705 - Replace sprintf with snprintf. (I think they were all safe, but
29707 - Replace strcpy/strncpy with strlcpy in more places.
29708 - Avoid strcat; use snprintf or strlcat instead.
29709 - snprintf wrapper with consistent (though not C99) overflow behavior.
29712 Changes in version 0.0.9pre4 - 2004-10-17
29713 o Bugfixes on 0.0.9pre3:
29714 - If the server doesn't specify an exit policy, use the real default
29715 exit policy, not reject *:*.
29716 - Ignore fascistfirewall when uploading/downloading hidden service
29717 descriptors, since we go through Tor for those; and when using
29718 an HttpProxy, since we assume it can reach them all.
29719 - When looking for an authoritative dirserver, use only the ones
29720 configured at boot. Don't bother looking in the directory.
29721 - The rest of the fix for get_default_conf_file() on older win32.
29722 - Make 'Routerfile' config option obsolete.
29725 - New 'MyFamily nick1,...' config option for a server to
29726 specify other servers that shouldn't be used in the same circuit
29727 with it. Only believed if nick1 also specifies us.
29728 - New 'NodeFamily nick1,nick2,...' config option for a client to
29729 specify nodes that it doesn't want to use in the same circuit.
29730 - New 'Redirectexit pattern address:port' config option for a
29731 server to redirect exit connections, e.g. to a local squid.
29734 Changes in version 0.0.9pre3 - 2004-10-13
29735 o Bugfixes on 0.0.8.1:
29736 - Better torrc example lines for dirbindaddress and orbindaddress.
29737 - Improved bounds checking on parsed ints (e.g. config options and
29738 the ones we find in directories.)
29739 - Better handling of size_t vs int, so we're more robust on 64
29741 - Fix the rest of the bug where a newly started OR would appear
29742 as unverified even after we've added his fingerprint and hupped
29744 - Fix a bug from 0.0.7: when read() failed on a stream, we would
29745 close it without sending back an end. So 'connection refused'
29746 would simply be ignored and the user would get no response.
29748 o Bugfixes on 0.0.9pre2:
29749 - Serving the cached-on-disk directory to people is bad. We now
29750 provide no directory until we've fetched a fresh one.
29751 - Workaround for bug on windows where cached-directories get crlf
29753 - Make get_default_conf_file() work on older windows too.
29754 - If we write a *:* exit policy line in the descriptor, don't write
29755 any more exit policy lines.
29758 - Use only 0.0.9pre1 and later servers for resolve cells.
29759 - Make the dirservers file obsolete.
29760 - Include a dir-signing-key token in directories to tell the
29761 parsing entity which key is being used to sign.
29762 - Remove the built-in bulky default dirservers string.
29763 - New config option "Dirserver %s:%d [fingerprint]", which can be
29764 repeated as many times as needed. If no dirservers specified,
29765 default to moria1,moria2,tor26.
29766 - Make moria2 advertise a dirport of 80, so people behind firewalls
29767 will be able to get a directory.
29768 - Http proxy support
29769 - Dirservers translate requests for http://%s:%d/x to /x
29770 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
29771 be routed through this host.
29772 - Clients ask for /tor/x rather than /x for new enough dirservers.
29773 This way we can one day coexist peacefully with apache.
29774 - Clients specify a "Host: %s%d" http header, to be compatible
29775 with more proxies, and so running squid on an exit node can work.
29778 Changes in version 0.0.8.1 - 2004-10-13
29780 - Fix a seg fault that can be triggered remotely for Tor
29781 clients/servers with an open dirport.
29782 - Fix a rare assert trigger, where routerinfos for entries in
29783 our cpath would expire while we're building the path.
29784 - Fix a bug in OutboundBindAddress so it (hopefully) works.
29785 - Fix a rare seg fault for people running hidden services on
29786 intermittent connections.
29787 - Fix a bug in parsing opt keywords with objects.
29788 - Fix a stale pointer assert bug when a stream detaches and
29790 - Fix a string format vulnerability (probably not exploitable)
29791 in reporting stats locally.
29792 - Fix an assert trigger: sometimes launching circuits can fail
29793 immediately, e.g. because too many circuits have failed recently.
29794 - Fix a compile warning on 64 bit platforms.
29797 Changes in version 0.0.9pre2 - 2004-10-03
29799 - Make fetching a cached directory work for 64-bit platforms too.
29800 - Make zlib.h a required header, not an optional header.
29803 Changes in version 0.0.9pre1 - 2004-10-01
29805 - Stop using separate defaults for no-config-file and
29806 empty-config-file. Now you have to explicitly turn off SocksPort,
29807 if you don't want it open.
29808 - Fix a bug in OutboundBindAddress so it (hopefully) works.
29809 - Improve man page to mention more of the 0.0.8 features.
29810 - Fix a rare seg fault for people running hidden services on
29811 intermittent connections.
29812 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
29814 - Fix more dns related bugs: send back resolve_failed and end cells
29815 more reliably when the resolve fails, rather than closing the
29816 circuit and then trying to send the cell. Also attach dummy resolve
29817 connections to a circuit *before* calling dns_resolve(), to fix
29818 a bug where cached answers would never be sent in RESOLVED cells.
29819 - When we run out of disk space, or other log writing error, don't
29820 crash. Just stop logging to that log and continue.
29821 - We were starting to daemonize before we opened our logs, so if
29822 there were any problems opening logs, we would complain to stderr,
29823 which wouldn't work, and then mysteriously exit.
29824 - Fix a rare bug where sometimes a verified OR would connect to us
29825 before he'd uploaded his descriptor, which would cause us to
29826 assign conn->nickname as though he's unverified. Now we look through
29827 the fingerprint list to see if he's there.
29828 - Fix a rare assert trigger, where routerinfos for entries in
29829 our cpath would expire while we're building the path.
29832 - Clients can ask dirservers for /dir.z to get a compressed version
29833 of the directory. Only works for servers running 0.0.9, of course.
29834 - Make clients cache directories and use them to seed their router
29835 lists at startup. This means clients have a datadir again.
29836 - Configuration infrastructure support for warning on obsolete
29838 - Respond to content-encoding headers by trying to uncompress as
29840 - Reply with a deflated directory when a client asks for "dir.z".
29841 We could use allow-encodings instead, but allow-encodings isn't
29842 specified in HTTP 1.0.
29843 - Raise the max dns workers from 50 to 100.
29844 - Discourage people from setting their dirfetchpostperiod more often
29845 than once per minute.
29846 - Protect dirservers from overzealous descriptor uploading -- wait
29847 10 seconds after directory gets dirty, before regenerating.
29850 Changes in version 0.0.8 - 2004-08-25
29851 o Port it to SunOS 5.9 / Athena
29854 Changes in version 0.0.8rc2 - 2004-08-20
29855 o Make it compile on cygwin again.
29856 o When picking unverified routers, skip those with low uptime and/or
29857 low bandwidth, depending on what properties you care about.
29860 Changes in version 0.0.8rc1 - 2004-08-18
29861 o Changes from 0.0.7.3:
29863 - Fix assert triggers: if the other side returns an address 0.0.0.0,
29864 don't put it into the client dns cache.
29865 - If a begin failed due to exit policy, but we believe the IP address
29866 should have been allowed, switch that router to exitpolicy reject *:*
29867 until we get our next directory.
29869 - Clients choose nodes proportional to advertised bandwidth.
29870 - Avoid using nodes with low uptime as introduction points.
29871 - Handle servers with dynamic IP addresses: don't replace
29872 options->Address with the resolved one at startup, and
29873 detect our address right before we make a routerinfo each time.
29874 - 'FascistFirewall' option to pick dirservers and ORs on specific
29875 ports; plus 'FirewallPorts' config option to tell FascistFirewall
29876 which ports are open. (Defaults to 80,443)
29877 - Be more aggressive about trying to make circuits when the network
29878 has changed (e.g. when you unsuspend your laptop).
29879 - Check for time skew on http headers; report date in response to
29881 - If the entrynode config line has only one node, don't pick it as
29883 - Add strict{entry|exit}nodes config options. If set to 1, then
29884 we refuse to build circuits that don't include the specified entry
29886 - OutboundBindAddress config option, to bind to a specific
29887 IP address for outgoing connect()s.
29888 - End truncated log entries (e.g. directories) with "[truncated]".
29890 o Patches to 0.0.8preX:
29892 - Patches to compile and run on win32 again (maybe)?
29893 - Fix crash when looking for ~/.torrc with no $HOME set.
29894 - Fix a race bug in the unit tests.
29895 - Handle verified/unverified name collisions better when new
29896 routerinfo's arrive in a directory.
29897 - Sometimes routers were getting entered into the stats before
29898 we'd assigned their identity_digest. Oops.
29899 - Only pick and establish intro points after we've gotten a
29902 - AllowUnverifiedNodes config option to let circuits choose no-name
29903 routers in entry,middle,exit,introduction,rendezvous positions.
29904 Allow middle and rendezvous positions by default.
29905 - Add a man page for tor-resolve.
29908 Changes in version 0.0.7.3 - 2004-08-12
29909 o Stop dnsworkers from triggering an assert failure when you
29910 ask them to resolve the host "".
29913 Changes in version 0.0.8pre3 - 2004-08-09
29914 o Changes from 0.0.7.2:
29915 - Allow multiple ORs with same nickname in routerlist -- now when
29916 people give us one identity key for a nickname, then later
29917 another, we don't constantly complain until the first expires.
29918 - Remember used bandwidth (both in and out), and publish 15-minute
29919 snapshots for the past day into our descriptor.
29920 - You can now fetch $DIRURL/running-routers to get just the
29921 running-routers line, not the whole descriptor list. (But
29922 clients don't use this yet.)
29923 - When people mistakenly use Tor as an http proxy, point them
29924 at the tor-doc.html rather than the INSTALL.
29925 - Remove our mostly unused -- and broken -- hex_encode()
29926 function. Use base16_encode() instead. (Thanks to Timo Lindfors
29927 for pointing out this bug.)
29928 - Rotate onion keys every 12 hours, not every 2 hours, so we have
29929 fewer problems with people using the wrong key.
29930 - Change the default exit policy to reject the default edonkey,
29931 kazaa, gnutella ports.
29932 - Add replace_file() to util.[ch] to handle win32's rename().
29934 o Changes from 0.0.8preX:
29935 - Fix two bugs in saving onion keys to disk when rotating, so
29936 hopefully we'll get fewer people using old onion keys.
29937 - Fix an assert error that was making SocksPolicy not work.
29938 - Be willing to expire routers that have an open dirport -- it's
29939 just the authoritative dirservers we want to not forget.
29940 - Reject tor-resolve requests for .onion addresses early, so we
29941 don't build a whole rendezvous circuit and then fail.
29942 - When you're warning a server that he's unverified, don't cry
29943 wolf unpredictably.
29944 - Fix a race condition: don't try to extend onto a connection
29945 that's still handshaking.
29946 - For servers in clique mode, require the conn to be open before
29947 you'll choose it for your path.
29948 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
29949 end relay cell, etc.
29950 - Measure bandwidth capacity over the last 24 hours, not just 12
29951 - Bugfix: authoritative dirservers were making and signing a new
29952 directory for each client, rather than reusing the cached one.
29955 Changes in version 0.0.8pre2 - 2004-08-04
29956 o Changes from 0.0.7.2:
29958 - Check directory signature _before_ you decide whether you're
29959 you're running an obsolete version and should exit.
29960 - Check directory signature _before_ you parse the running-routers
29961 list to decide who's running or verified.
29962 - Bugfixes and features:
29963 - Check return value of fclose while writing to disk, so we don't
29964 end up with broken files when servers run out of disk space.
29965 - Log a warning if the user uses an unsafe socks variant, so people
29966 are more likely to learn about privoxy or socat.
29967 - Dirservers now include RFC1123-style dates in the HTTP headers,
29968 which one day we will use to better detect clock skew.
29970 o Changes from 0.0.8pre1:
29971 - Make it compile without warnings again on win32.
29972 - Log a warning if you're running an unverified server, to let you
29973 know you might want to get it verified.
29974 - Only pick a default nickname if you plan to be a server.
29977 Changes in version 0.0.8pre1 - 2004-07-23
29979 - Made our unit tests compile again on OpenBSD 3.5, and tor
29980 itself compile again on OpenBSD on a sparc64.
29981 - We were neglecting milliseconds when logging on win32, so
29982 everything appeared to happen at the beginning of each second.
29984 o Protocol changes:
29985 - 'Extend' relay cell payloads now include the digest of the
29986 intended next hop's identity key. Now we can verify that we're
29987 extending to the right router, and also extend to routers we
29988 hadn't heard of before.
29991 - Tor nodes can now act as relays (with an advertised ORPort)
29992 without being manually verified by the dirserver operators.
29993 - Uploaded descriptors of unverified routers are now accepted
29994 by the dirservers, and included in the directory.
29995 - Verified routers are listed by nickname in the running-routers
29996 list; unverified routers are listed as "$<fingerprint>".
29997 - We now use hash-of-identity-key in most places rather than
29998 nickname or addr:port, for improved security/flexibility.
29999 - To avoid Sybil attacks, paths still use only verified servers.
30000 But now we have a chance to play around with hybrid approaches.
30001 - Nodes track bandwidth usage to estimate capacity (not used yet).
30002 - ClientOnly option for nodes that never want to become servers.
30003 - Directory caching.
30004 - "AuthoritativeDir 1" option for the official dirservers.
30005 - Now other nodes (clients and servers) will cache the latest
30006 directory they've pulled down.
30007 - They can enable their DirPort to serve it to others.
30008 - Clients will pull down a directory from any node with an open
30009 DirPort, and check the signature/timestamp correctly.
30010 - Authoritative dirservers now fetch directories from other
30011 authdirservers, to stay better synced.
30012 - Running-routers list tells who's down also, along with noting
30013 if they're verified (listed by nickname) or unverified (listed
30015 - Allow dirservers to serve running-router list separately.
30016 This isn't used yet.
30017 - ORs connect-on-demand to other ORs
30018 - If you get an extend cell to an OR you're not connected to,
30019 connect, handshake, and forward the create cell.
30020 - The authoritative dirservers stay connected to everybody,
30021 and everybody stays connected to 0.0.7 servers, but otherwise
30022 clients/servers expire unused connections after 5 minutes.
30023 - When servers get a sigint, they delay 30 seconds (refusing new
30024 connections) then exit. A second sigint causes immediate exit.
30025 - File and name management:
30026 - Look for .torrc if no CONFDIR "torrc" is found.
30027 - If no datadir is defined, then choose, make, and secure ~/.tor
30029 - If torrc not found, exitpolicy reject *:*.
30030 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
30031 - If no nickname is defined, derive default from hostname.
30032 - Rename secret key files, e.g. identity.key -> secret_id_key,
30033 to discourage people from mailing their identity key to tor-ops.
30034 - Refuse to build a circuit before the directory has arrived --
30035 it won't work anyway, since you won't know the right onion keys
30037 - Try other dirservers immediately if the one you try is down. This
30038 should tolerate down dirservers better now.
30039 - Parse tor version numbers so we can do an is-newer-than check
30040 rather than an is-in-the-list check.
30041 - New socks command 'resolve', to let us shim gethostbyname()
30043 - A 'tor_resolve' script to access the socks resolve functionality.
30044 - A new socks-extensions.txt doc file to describe our
30045 interpretation and extensions to the socks protocols.
30046 - Add a ContactInfo option, which gets published in descriptor.
30047 - Publish OR uptime in descriptor (and thus in directory) too.
30048 - Write tor version at the top of each log file
30049 - New docs in the tarball:
30051 - Document that you should proxy your SSL traffic too.
30054 Changes in version 0.0.7.2 - 2004-07-07
30055 o A better fix for the 0.0.0.0 problem, that will hopefully
30056 eliminate the remaining related assertion failures.
30059 Changes in version 0.0.7.1 - 2004-07-04
30060 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
30061 since internally we use 0.0.0.0 to signify "not yet resolved".
30064 Changes in version 0.0.7 - 2004-06-07
30065 o Updated the man page to reflect the new features.
30068 Changes in version 0.0.7rc2 - 2004-06-06
30069 o Changes from 0.0.7rc1:
30070 - Make it build on Win32 again.
30071 o Changes from 0.0.6.2:
30072 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
30076 Changes in version 0.0.7rc1 - 2004-06-02
30078 - On sighup, we were adding another log without removing the first
30079 one. So log messages would get duplicated n times for n sighups.
30080 - Several cases of using a connection after we'd freed it. The
30081 problem was that connections that are pending resolve are in both
30082 the pending_resolve tree, and also the circuit's resolving_streams
30083 list. When you want to remove one, you must remove it from both.
30084 - Fix a double-mark-for-close where an end cell arrived for a
30085 resolving stream, and then the resolve failed.
30086 - Check directory signatures based on name of signer, not on whom
30087 we got the directory from. This will let us cache directories more
30090 - Crank up some of our constants to handle more users.
30093 Changes in version 0.0.7pre1 - 2004-06-02
30094 o Fixes for crashes and other obnoxious bugs:
30095 - Fix an epipe bug: sometimes when directory connections failed
30096 to connect, we would give them a chance to flush before closing
30098 - When we detached from a circuit because of resolvefailed, we
30099 would immediately try the same circuit twice more, and then
30100 give up on the resolve thinking we'd tried three different
30102 - Limit the number of intro circuits we'll attempt to build for a
30103 hidden service per 15-minute period.
30104 - Check recommended-software string *early*, before actually parsing
30105 the directory. Thus we can detect an obsolete version and exit,
30106 even if the new directory format doesn't parse.
30107 o Fixes for security bugs:
30108 - Remember which nodes are dirservers when you startup, and if a
30109 random OR enables his dirport, don't automatically assume he's
30110 a trusted dirserver.
30112 - Directory connections were asking the wrong poll socket to
30113 start writing, and not asking themselves to start writing.
30114 - When we detached from a circuit because we sent a begin but
30115 didn't get a connected, we would use it again the first time;
30116 but after that we would correctly switch to a different one.
30117 - Stop warning when the first onion decrypt attempt fails; they
30118 will sometimes legitimately fail now that we rotate keys.
30119 - Override unaligned-access-ok check when $host_cpu is ia64 or
30120 arm. Apparently they allow it but the kernel whines.
30121 - Dirservers try to reconnect periodically too, in case connections
30123 - Fix some memory leaks in directory servers.
30124 - Allow backslash in Win32 filenames.
30125 - Made Tor build complain-free on FreeBSD, hopefully without
30126 breaking other BSD builds. We'll see.
30128 - Doxygen markup on all functions and global variables.
30129 - Make directory functions update routerlist, not replace it. So
30130 now directory disagreements are not so critical a problem.
30131 - Remove the upper limit on number of descriptors in a dirserver's
30132 directory (not that we were anywhere close).
30133 - Allow multiple logfiles at different severity ranges.
30134 - Allow *BindAddress to specify ":port" rather than setting *Port
30135 separately. Allow multiple instances of each BindAddress config
30136 option, so you can bind to multiple interfaces if you want.
30137 - Allow multiple exit policy lines, which are processed in order.
30138 Now we don't need that huge line with all the commas in it.
30139 - Enable accept/reject policies on SOCKS connections, so you can bind
30140 to 0.0.0.0 but still control who can use your OP.
30143 Changes in version 0.0.6.2 - 2004-05-16
30144 o Our integrity-checking digest was checking only the most recent cell,
30145 not the previous cells like we'd thought.
30146 Thanks to Stefan Mark for finding the flaw!
30149 Changes in version 0.0.6.1 - 2004-05-06
30150 o Fix two bugs in our AES counter-mode implementation (this affected
30151 onion-level stream encryption, but not TLS-level). It turns
30152 out we were doing something much more akin to a 16-character
30153 polyalphabetic cipher. Oops.
30154 Thanks to Stefan Mark for finding the flaw!
30155 o Retire moria3 as a directory server, and add tor26 as a directory
30159 Changes in version 0.0.6 - 2004-05-02
30160 [version bump only]
30163 Changes in version 0.0.6rc4 - 2004-05-01
30164 o Update the built-in dirservers list to use the new directory format
30165 o Fix a rare seg fault: if a node offering a hidden service attempts
30166 to build a circuit to Alice's rendezvous point and fails before it
30167 reaches the last hop, it retries with a different circuit, but
30169 o Handle windows socket errors correctly.
30172 Changes in version 0.0.6rc3 - 2004-04-28
30173 o Don't expire non-general excess circuits (if we had enough
30174 circuits open, we were expiring rendezvous circuits -- even
30175 when they had a stream attached. oops.)
30176 o Fetch randomness from /dev/urandom better (not via fopen/fread)
30177 o Better debugging for tls errors
30178 o Some versions of openssl have an SSL_pending function that erroneously
30179 returns bytes when there is a non-application record pending.
30180 o Set Content-Type on the directory and hidserv descriptor.
30181 o Remove IVs from cipher code, since AES-ctr has none.
30182 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
30183 o We were using an array of length zero in a few places.
30184 o win32's gethostbyname can't resolve an IP to an IP.
30185 o win32's close can't close a socket.
30188 Changes in version 0.0.6rc2 - 2004-04-26
30189 o Fix a bug where we were closing tls connections intermittently.
30190 It turns out openssl keeps its errors around -- so if an error
30191 happens, and you don't ask about it, and then another openssl
30192 operation happens and succeeds, and you ask if there was an error,
30193 it tells you about the first error. Fun fun.
30194 o Fix a bug that's been lurking since 27 may 03 (!)
30195 When passing back a destroy cell, we would use the wrong circ id.
30196 'Mostly harmless', but still worth fixing.
30197 o Since we don't support truncateds much, don't bother sending them;
30198 just close the circ.
30199 o check for <machine/limits.h> so we build on NetBSD again (I hope).
30200 o don't crash if a conn that sent a begin has suddenly lost its circuit
30201 (this was quite rare).
30204 Changes in version 0.0.6rc1 - 2004-04-25
30205 o We now rotate link (tls context) keys and onion keys.
30206 o CREATE cells now include oaep padding, so you can tell
30207 if you decrypted them correctly.
30208 o Add bandwidthburst to server descriptor.
30209 o Directories now say which dirserver signed them.
30210 o Use a tor_assert macro that logs failed assertions too.
30213 Changes in version 0.0.6pre5 - 2004-04-18
30214 o changes from 0.0.6pre4:
30215 - make tor build on broken freebsd 5.2 installs
30216 - fix a failed assert when you try an intro point, get a nack, and try
30217 a second one and it works.
30218 - when alice uses a port that the hidden service doesn't accept,
30219 it now sends back an end cell (denied by exit policy). otherwise
30220 alice would just have to wait to time out.
30221 - fix another rare bug: when we had tried all the intro
30222 points for a hidden service, we fetched the descriptor
30223 again, but we left our introcirc thinking it had already
30224 sent an intro, so it kept waiting for a response...
30225 - bugfix: when you sleep your hidden-service laptop, as soon
30226 as it wakes up it tries to upload a service descriptor, but
30227 socketpair fails for some reason (localhost not up yet?).
30228 now we simply give up on that upload, and we'll try again later.
30229 i'd still like to find the bug though.
30230 - if an intro circ waiting for an ack dies before getting one, then
30232 - we were reusing stale service descriptors and refetching usable
30236 Changes in version 0.0.6pre4 - 2004-04-14
30237 o changes from 0.0.6pre3:
30238 - when bob fails to connect to the rendezvous point, and his
30239 circ didn't fail because of the rendezvous point itself, then
30240 he retries a couple of times
30241 - we expire introduction and rendezvous circs more thoroughly
30242 (sometimes they were hanging around forever)
30243 - we expire unattached rendezvous streams that have been around
30244 too long (they were sticking around forever).
30245 - fix a measly fencepost error that was crashing everybody with
30249 Changes in version 0.0.6pre3 - 2004-04-14
30250 o changes from 0.0.6pre2:
30251 - make hup work again
30252 - fix some memory leaks for dirservers
30253 - allow more skew in rendezvous descriptor timestamps, to help
30254 handle people like blanu who don't know what time it is
30255 - normal circs are 3 hops, but some rend/intro circs are 4, if
30256 the initiator doesn't get to choose the last hop
30257 - send acks for introductions, so alice can know whether to try
30259 - bob publishes intro points more correctly
30260 o changes from 0.0.5:
30261 - fix an assert trigger that's been plaguing us since the days
30262 of 0.0.2prexx (thanks weasel!)
30263 - retry stream correctly when we fail to connect because of
30264 exit-policy-reject (should try another) or can't-resolve-address
30265 (also should try another, because dns on random internet servers
30267 - when we hup a dirserver and we've *removed* a server from the
30268 approved-routers list, now we remove that server from the
30269 in-memory directories too
30272 Changes in version 0.0.6pre2 - 2004-04-08
30273 o We fixed our base32 implementation. Now it works on all architectures.
30276 Changes in version 0.0.6pre1 - 2004-04-08
30278 - Hidden services and rendezvous points are implemented. Go to
30279 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
30280 hidden services. (This only works via a socks4a proxy such as
30281 Privoxy, and currently it's quite slow.)
30284 Changes in version 0.0.5 - 2004-03-30
30285 [version bump only]
30288 Changes in version 0.0.5rc3 - 2004-03-29
30289 o Install torrc as torrc.sample -- we no longer clobber your
30291 o Re-enable recommendedversion checking (we broke it in rc2, oops)
30292 o Add in a 'notice' log level for things the operator should hear
30293 but that aren't warnings
30296 Changes in version 0.0.5rc2 - 2004-03-29
30297 o Hold socks connection open until reply is flushed (if possible)
30298 o Make exit nodes resolve IPs to IPs immediately, rather than asking
30299 the dns farm to do it.
30300 o Fix c99 aliasing warnings in rephist.c
30301 o Don't include server descriptors that are older than 24 hours in the
30303 o Give socks 'reject' replies their whole 15s to attempt to flush,
30304 rather than seeing the 60s timeout and assuming the flush had failed.
30305 o Clean automake droppings from the cvs repository
30308 Changes in version 0.0.5rc1 - 2004-03-28
30309 o Fix mangled-state bug in directory fetching (was causing sigpipes).
30310 o Only build circuits after we've fetched the directory: clients were
30311 using only the directory servers before they'd fetched a directory.
30312 This also means longer startup time; so it goes.
30313 o Fix an assert trigger where an OP would fail to handshake, and we'd
30314 expect it to have a nickname.
30315 o Work around a tsocks bug: do a socks reject when AP connection dies
30316 early, else tsocks goes into an infinite loop.
30319 Changes in version 0.0.4 - 2004-03-26
30320 o When connecting to a dirserver or OR and the network is down,
30324 Changes in version 0.0.3 - 2004-03-26
30325 o Warn and fail if server chose a nickname with illegal characters
30326 o Port to Solaris and Sparc:
30327 - include missing header fcntl.h
30328 - have autoconf find -lsocket -lnsl automatically
30329 - deal with hardware word alignment
30330 - make uname() work (solaris has a different return convention)
30331 - switch from using signal() to sigaction()
30332 o Preliminary work on reputation system:
30333 - Keep statistics on success/fail of connect attempts; they're published
30334 by kill -USR1 currently.
30335 - Add a RunTesting option to try to learn link state by creating test
30336 circuits, even when SocksPort is off.
30337 - Remove unused open circuits when there are too many.
30340 Changes in version 0.0.2 - 2004-03-19
30341 - Include strlcpy and strlcat for safer string ops
30342 - define INADDR_NONE so we compile (but still not run) on solaris
30345 Changes in version 0.0.2pre27 - 2004-03-14
30347 - Allow internal tor networks (we were rejecting internal IPs,
30348 now we allow them if they're set explicitly).
30349 - And fix a few endian issues.
30352 Changes in version 0.0.2pre26 - 2004-03-14
30354 - If a stream times out after 15s without a connected cell, don't
30355 try that circuit again: try a new one.
30356 - Retry streams at most 4 times. Then give up.
30357 - When a dirserver gets a descriptor from an unknown router, it
30358 logs its fingerprint (so the dirserver operator can choose to
30359 accept it even without mail from the server operator).
30360 - Inform unapproved servers when we reject their descriptors.
30361 - Make tor build on Windows again. It works as a client, who knows
30363 - Clearer instructions in the torrc for how to set up a server.
30364 - Be more efficient about reading fd's when our global token bucket
30365 (used for rate limiting) becomes empty.
30367 - Stop asserting that computers always go forward in time. It's
30369 - When we sent a cell (e.g. destroy) and then marked an OR connection
30370 expired, we might close it before finishing a flush if the other
30371 side isn't reading right then.
30372 - Don't allow dirservers to start if they haven't defined
30373 RecommendedVersions
30374 - We were caching transient dns failures. Oops.
30375 - Prevent servers from publishing an internal IP as their address.
30376 - Address a strcat vulnerability in circuit.c
30379 Changes in version 0.0.2pre25 - 2004-03-04
30381 - Put the OR's IP in its router descriptor, not its fqdn. That way
30382 we'll stop being stalled by gethostbyname for nodes with flaky dns,
30385 - If the user typed in an address that didn't resolve, the server
30389 Changes in version 0.0.2pre24 - 2004-03-03
30391 - Fix an assertion failure in dns.c, where we were trying to dequeue
30392 a pending dns resolve even if it wasn't pending
30393 - Fix a spurious socks5 warning about still trying to write after the
30394 connection is finished.
30395 - Hold certain marked_for_close connections open until they're finished
30396 flushing, rather than losing bytes by closing them too early.
30397 - Correctly report the reason for ending a stream
30398 - Remove some duplicate calls to connection_mark_for_close
30399 - Put switch_id and start_daemon earlier in the boot sequence, so it
30400 will actually try to chdir() to options.DataDirectory
30401 - Make 'make test' exit(1) if a test fails; fix some unit tests
30402 - Make tor fail when you use a config option it doesn't know about,
30403 rather than warn and continue.
30404 - Make --version work
30405 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
30408 Changes in version 0.0.2pre23 - 2004-02-29
30410 - Print a statement when the first circ is finished, so the user
30411 knows it's working.
30412 - If a relay cell is unrecognized at the end of the circuit,
30413 send back a destroy. (So attacks to mutate cells are more
30415 - New config option 'excludenodes' to avoid certain nodes for circuits.
30416 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
30417 so you can collect coredumps there.
30419 - Fix a bug in tls flushing where sometimes data got wedged and
30420 didn't flush until more data got sent. Hopefully this bug was
30421 a big factor in the random delays we were seeing.
30422 - Make 'connected' cells include the resolved IP, so the client
30423 dns cache actually gets populated.
30424 - Disallow changing from ORPort=0 to ORPort>0 on hup.
30425 - When we time-out on a stream and detach from the circuit, send an
30426 end cell down it first.
30427 - Only warn about an unknown router (in exitnodes, entrynodes,
30428 excludenodes) after we've fetched a directory.
30431 Changes in version 0.0.2pre22 - 2004-02-26
30433 - Servers publish less revealing uname information in descriptors.
30434 - More memory tracking and assertions, to crash more usefully when
30436 - If the default torrc isn't there, just use some default defaults.
30437 Plus provide an internal dirservers file if they don't have one.
30438 - When the user tries to use Tor as an http proxy, give them an http
30439 501 failure explaining that we're a socks proxy.
30440 - Dump a new router.desc on hup, to help confused people who change
30441 their exit policies and then wonder why router.desc doesn't reflect
30443 - Clean up the generic tor.sh init script that we ship with.
30445 - If the exit stream is pending on the resolve, and a destroy arrives,
30446 then the stream wasn't getting removed from the pending list. I
30447 think this was the one causing recent server crashes.
30448 - Use a more robust poll on OSX 10.3, since their poll is flaky.
30449 - When it couldn't resolve any dirservers, it was useless from then on.
30450 Now it reloads the RouterFile (or default dirservers) if it has no
30452 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
30453 many users don't even *have* a /usr/local/sbin/.
30456 Changes in version 0.0.2pre21 - 2004-02-18
30458 - There's a ChangeLog file that actually reflects the changelog.
30459 - There's a 'torify' wrapper script, with an accompanying
30460 tor-tsocks.conf, that simplifies the process of using tsocks for
30461 tor. It even has a man page.
30462 - The tor binary gets installed to sbin rather than bin now.
30463 - Retry streams where the connected cell hasn't arrived in 15 seconds
30464 - Clean up exit policy handling -- get the default out of the torrc,
30465 so we can update it without forcing each server operator to fix
30467 - Allow imaps and pop3s in default exit policy
30469 - Prevent picking middleman nodes as the last node in the circuit
30472 Changes in version 0.0.2pre20 - 2004-01-30
30474 - We now have a deb package, and it's in debian unstable. Go to
30475 it, apt-getters. :)
30476 - I've split the TotalBandwidth option into BandwidthRate (how many
30477 bytes per second you want to allow, long-term) and
30478 BandwidthBurst (how many bytes you will allow at once before the cap
30479 kicks in). This better token bucket approach lets you, say, set
30480 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
30481 performance while not exceeding your monthly bandwidth quota.
30482 - Push out a tls record's worth of data once you've got it, rather
30483 than waiting until you've read everything waiting to be read. This
30484 may improve performance by pipelining better. We'll see.
30485 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
30486 from failed circuits (if they haven't been connected yet) and attach
30488 - Expire old streams that haven't managed to connect. Some day we'll
30489 have them reattach to new circuits instead.
30492 - Fix several memory leaks that were causing servers to become bloated
30494 - Fix a few very rare assert triggers. A few more remain.
30495 - Setuid to User _before_ complaining about running as root.
30498 Changes in version 0.0.2pre19 - 2004-01-07
30500 - Fix deadlock condition in dns farm. We were telling a child to die by
30501 closing the parent's file descriptor to him. But newer children were
30502 inheriting the open file descriptor from the parent, and since they
30503 weren't closing it, the socket never closed, so the child never read
30504 eof, so he never knew to exit. Similarly, dns workers were holding
30505 open other sockets, leading to all sorts of chaos.
30506 - New cleaner daemon() code for forking and backgrounding.
30507 - If you log to a file, it now prints an entry at the top of the
30508 logfile so you know it's working.
30509 - The onionskin challenge length was 30 bytes longer than necessary.
30510 - Started to patch up the spec so it's not quite so out of date.
30513 Changes in version 0.0.2pre18 - 2004-01-02
30515 - Fix endian issues with the 'integrity' field in the relay header.
30516 - Fix a potential bug where connections in state
30517 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
30520 Changes in version 0.0.2pre17 - 2003-12-30
30522 - Made --debuglogfile (or any second log file, actually) work.
30523 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
30524 adversary could force us into an infinite loop.
30527 - Each onionskin handshake now includes a hash of the computed key,
30528 to prove the server's identity and help perfect forward secrecy.
30529 - Changed cell size from 256 to 512 bytes (working toward compatibility
30531 - Changed cell length to 2 bytes, and moved it to the relay header.
30532 - Implemented end-to-end integrity checking for the payloads of
30534 - Separated streamid from 'recognized' (otherwise circuits will get
30535 messed up when we try to have streams exit from the middle). We
30536 use the integrity-checking to confirm that a cell is addressed to
30538 - Randomize the initial circid and streamid values, so an adversary who
30539 breaks into a node can't learn how many circuits or streams have
30543 Changes in version 0.0.2pre16 - 2003-12-14
30545 - Fixed a bug that made HUP trigger an assert
30546 - Fixed a bug where a circuit that immediately failed wasn't being
30547 counted as a failed circuit in counting retries.
30550 - Now we close the circuit when we get a truncated cell: otherwise we're
30551 open to an anonymity attack where a bad node in the path truncates
30552 the circuit and then we open streams at him.
30553 - Add port ranges to exit policies
30554 - Add a conservative default exit policy
30555 - Warn if you're running tor as root
30556 - on HUP, retry OR connections and close/rebind listeners
30557 - options.EntryNodes: try these nodes first when picking the first node
30558 - options.ExitNodes: if your best choices happen to include any of
30559 your preferred exit nodes, you choose among just those preferred
30561 - options.ExcludedNodes: nodes that are never picked in path building
30564 Changes in version 0.0.2pre15 - 2003-12-03
30565 o Robustness and bugfixes:
30566 - Sometimes clients would cache incorrect DNS resolves, which would
30567 really screw things up.
30568 - An OP that goes offline would slowly leak all its sockets and stop
30570 - A wide variety of bugfixes in exit node selection, exit policy
30571 handling, and processing pending streams when a new circuit is
30573 - Pick nodes for a path only from those the directory says are up
30574 - Choose randomly from all running dirservers, not always the first one
30575 - Increase allowed http header size for directory fetch.
30576 - Stop writing to stderr (if we're daemonized it will be closed).
30577 - Enable -g always, so cores will be more useful to me.
30578 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
30581 - Wrote a man page. It lists commonly used options.
30584 - Change default loglevel to warn.
30585 - Make PidFile default to null rather than littering in your CWD.
30586 - OnionRouter config option is now obsolete. Instead it just checks
30588 - Moved to a single unified torrc file for both clients and servers.
30591 Changes in version 0.0.2pre14 - 2003-11-29
30592 o Robustness and bugfixes:
30593 - Force the admin to make the DataDirectory himself
30594 - to get ownership/permissions right
30595 - so clients no longer make a DataDirectory and then never use it
30596 - fix bug where a client who was offline for 45 minutes would never
30597 pull down a directory again
30598 - fix (or at least hide really well) the dns assert bug that was
30599 causing server crashes
30600 - warnings and improved robustness wrt clockskew for certs
30601 - use the native daemon(3) to daemonize, when available
30602 - exit if bind() fails
30603 - exit if neither socksport nor orport is defined
30604 - include our own tor_timegm (Win32 doesn't have its own)
30605 - bugfix for win32 with lots of connections
30606 - fix minor bias in PRNG
30607 - make dirserver more robust to corrupt cached directory
30610 - Wrote the design document (woo)
30612 o Circuit building and exit policies:
30613 - Circuits no longer try to use nodes that the directory has told them
30615 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
30616 bitcounts (18.0.0.0/8).
30617 - Make AP connections standby for a circuit if no suitable circuit
30618 exists, rather than failing
30619 - Circuits choose exit node based on addr/port, exit policies, and
30620 which AP connections are standing by
30621 - Bump min pathlen from 2 to 3
30622 - Relay end cells have a payload to describe why the stream ended.
30623 - If the stream failed because of exit policy, try again with a new
30625 - Clients have a dns cache to remember resolved addresses.
30626 - Notice more quickly when we have no working circuits
30629 - APPort is now called SocksPort
30630 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
30632 - RecommendedVersions is now a config variable rather than
30633 hardcoded (for dirservers)
30634 - Reloads config on HUP
30635 - Usage info on -h or --help
30636 - If you set User and Group config vars, it'll setu/gid to them.
30639 Changes in version 0.0.2pre13 - 2003-10-19
30640 o General stability:
30641 - SSL_write no longer fails when it returns WANTWRITE and the number
30642 of bytes in the buf has changed by the next SSL_write call.
30643 - Fix segfault fetching directory when network is down
30644 - Fix a variety of minor memory leaks
30645 - Dirservers reload the fingerprints file on HUP, so I don't have
30646 to take down the network when I approve a new router
30647 - Default server config file has explicit Address line to specify fqdn
30650 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
30651 - Make listener connections not ever alloc bufs
30653 o Autoconf improvements:
30654 - don't clobber an external CFLAGS in ./configure
30655 - Make install now works
30656 - create var/lib/tor on make install
30657 - autocreate a tor.sh initscript to help distribs
30658 - autocreate the torrc and sample-server-torrc with correct paths
30660 o Log files and Daemonizing now work:
30661 - If --DebugLogFile is specified, log to it at -l debug
30662 - If --LogFile is specified, use it instead of commandline
30663 - If --RunAsDaemon is set, tor forks and backgrounds on startup