1 Changes in version 0.4.2.5 - 2019-12-09
2 This is the first stable release in the 0.4.2.x series. This series
3 improves reliability and stability, and includes several stability and
4 correctness improvements for onion services. It also fixes many smaller
5 bugs present in previous series.
7 Per our support policy, we will support the 0.4.2.x series for nine
8 months, or until three months after the release of a stable 0.4.3.x:
9 whichever is longer. If you need longer-term support, please stick
10 with 0.3.5.x, which will we plan to support until Feb 2022.
12 Per our support policy, we will support the 0.4.2.x series for nine
13 months, or until three months after the release of a stable 0.4.3.x:
14 whichever is longer. If you need longer-term support, please stick
15 with 0.3.5.x, which will we plan to support until Feb 2022.
17 Below are the changes since 0.4.1.4-rc. For a complete list of changes
18 since 0.4.1.5, see the ReleaseNotes file.
20 o Minor features (geoip):
21 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
22 Country database. Closes ticket 32685.
25 - Require C99 standards-conforming code in Travis CI, but allow GNU
26 gcc extensions. Also activates clang's -Wtypedef-redefinition
27 warnings. Build some jobs with -std=gnu99, and some jobs without.
31 Changes in version 0.4.1.7 - 2019-12-09
32 This release backports several bugfixes to improve stability and
33 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
34 including all relays relying on AccountingMax, should upgrade.
36 o Major features (directory authorities, backport from 0.4.2.2-alpha):
37 - Directory authorities now reject relays running all currently
38 deprecated release series. The currently supported release series
39 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
41 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
42 - Avoid a possible crash when restarting Tor in embedded mode and
43 enabling a different set of publish/subscribe messages. Fixes bug
44 31898; bugfix on 0.4.1.1-alpha.
46 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
47 - Relays now respect their AccountingMax bandwidth again. When
48 relays entered "soft" hibernation (which typically starts when
49 we've hit 90% of our AccountingMax), we had stopped checking
50 whether we should enter hard hibernation. Soft hibernation refuses
51 new connections and new circuits, but the existing circuits can
52 continue, meaning that relays could have exceeded their configured
53 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
55 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
56 - Stop ignoring torrc options after an %include directive, when the
57 included directory ends with a file that does not contain any
58 config options (but does contain comments or whitespace). Fixes
59 bug 31408; bugfix on 0.3.1.1-alpha.
61 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
62 - Onion services now always use the exact number of intro points
63 configured with the HiddenServiceNumIntroductionPoints option (or
64 fewer if nodes are excluded). Before, a service could sometimes
65 pick more intro points than configured. Fixes bug 31548; bugfix
68 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
69 - When building on Appveyor and Travis, pass the "-k" flag to make,
70 so that we are informed of all compilation failures, not just the
71 first one or two. Closes ticket 31372.
73 o Minor features (geoip, backport from 0.4.2.5):
74 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
75 Country database. Closes ticket 32685.
77 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
78 - Avoid spurious errors when Appveyor CI fails before the install step.
79 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
81 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
82 - Fix a BUG() assertion that occurs within a very small race window
83 between when a client intro circuit opens and when its descriptor
84 gets cleaned up from the cache. The circuit is now closed early,
85 which will trigger a re-fetch of the descriptor and continue the
86 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
88 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
89 - Avoid trying to read data from closed connections, which can cause
90 needless loops in Libevent and infinite loops in Shadow. Fixes bug
91 30344; bugfix on 0.1.1.1-alpha.
93 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
94 - On abort, try harder to flush the output buffers of log messages.
95 On some platforms (macOS), log messages could be discarded when
96 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
97 - Report the tor version whenever an assertion fails. Previously, we
98 only reported the Tor version on some crashes, and some non-fatal
99 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
100 - When tor aborts due to an error, close log file descriptors before
101 aborting. Closing the logs makes some OSes flush log file buffers,
102 rather than deleting buffered log lines. Fixes bug 31594; bugfix
105 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
106 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
107 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
108 - Disable backtrace signal handlers when shutting down tor. Fixes
109 bug 31614; bugfix on 0.2.5.2-alpha.
110 - Rate-limit our the logging message about the obsolete .exit
111 notation. Previously, there was no limit on this warning, which
112 could potentially be triggered many times by a hostile website.
113 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
115 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
116 - Do not log a nonfatal assertion failure when receiving a VERSIONS
117 cell on a connection using the obsolete v1 link protocol. Log a
118 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
120 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
121 - Reset the periodic events' "enabled" flag when Tor is shut down
122 cleanly. Previously, this flag was left on, which caused periodic
123 events not to be re-enabled when Tor was relaunched in-process
124 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
127 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
128 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
129 31736; bugfix on 0.0.7.
131 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
132 - Remove overly strict assertions that triggered when a pluggable
133 transport failed to launch. Fixes bug 31091; bugfix
135 - Remove an assertion in the Unix process backend. This assertion
136 would trigger when we failed to find the executable for a child
137 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
139 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
140 - Avoid crashing when starting with a corrupt keys directory where
141 the old ntor key and the new ntor key are identical. Fixes bug
142 30916; bugfix on 0.2.4.8-alpha.
144 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
145 - When testing port rebinding, don't busy-wait for tor to log.
146 Instead, actually sleep for a short time before polling again.
147 Also improve the formatting of control commands and log messages.
148 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
150 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
151 - Avoid a map_anon_nofork test failure due to a signed/unsigned
152 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
154 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
155 - Log bugs about the TLS read buffer's length only once, rather than
156 filling the logs with similar warnings. Fixes bug 31939; bugfix
159 o Documentation (backport from 0.4.2.2-alpha):
160 - Explain why we can't destroy the backtrace buffer mutex. Explain
161 why we don't need to destroy the log mutex. Closes ticket 31736.
163 o Testing (continuous integration, backport from 0.4.2.3-alpha):
164 - Disable all but one Travis CI macOS build, to mitigate slow
165 scheduling of Travis macOS jobs. Closes ticket 32177.
166 - Run the chutney IPv6 networks as part of Travis CI. Closes
168 - Simplify the Travis CI build matrix, and optimise for build time.
170 - Use Windows Server 2019 instead of Windows Server 2016 in our
171 Appveyor builds. Closes ticket 32086.
173 o Testing (continuous integration, backport from 0.4.2.4-rc):
174 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
175 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
176 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
177 until we can fix some Bionic permissions issues (see ticket
178 32240). Related to ticket 31919.
179 - Install the mingw OpenSSL package in Appveyor. This makes sure
180 that the OpenSSL headers and libraries match in Tor's Appveyor
181 builds. (This bug was triggered by an Appveyor image update.)
182 Fixes bug 32449; bugfix on 0.3.5.6-rc.
184 o Testing (continuous integration, backport from 0.4.2.5):
185 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
186 extensions. Also activates clang's -Wtypedef-redefinition warnings.
187 Build some jobs with -std=gnu99, and some jobs without.
191 Changes in version 0.4.0.6 - 2019-12-09
192 This is the second stable release in the 0.4.0.x series. This release
193 backports several bugfixes to improve stability and correctness. Anyone
194 experiencing build problems or crashes with 0.4.0.5, including all relays
195 relying on AccountingMax, should upgrade.
197 Note that, per our support policy, support for the 0.4.0.x series will end
198 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
199 latest stable release, or downgrade to 0.3.5.x, which will get long-term
200 support until 1 Feb 2022.
202 o Directory authority changes (backport from 0.4.1.5):
203 - The directory authority "dizum" has a new IP address. Closes
206 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
207 - Consider our directory information to have changed when our list
208 of bridges changes. Previously, Tor would not re-compute the
209 status of its directory information when bridges changed, and
210 therefore would not realize that it was no longer able to build
211 circuits. Fixes part of bug 29875.
212 - Do not count previously configured working bridges towards our
213 total of working bridges. Previously, when Tor's list of bridges
214 changed, it would think that the old bridges were still usable,
215 and delay fetching router descriptors for the new ones. Fixes part
216 of bug 29875; bugfix on 0.3.0.1-alpha.
218 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
219 - When considering upgrading circuits from "waiting for guard" to
220 "open", always ignore circuits that are marked for close. Otherwise,
221 we can end up in the situation where a subsystem is notified that
222 a closing circuit has just opened, leading to undesirable
223 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
225 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
226 - Properly clean up the introduction point map when circuits change
227 purpose from onion service circuits to pathbias, measurement, or
228 other circuit types. This should fix some service-side instances
229 of introduction point failure. Fixes bug 29034; bugfix
232 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
233 - Fix an unreachable bug in which an introduction point could try to
234 send an INTRODUCE_ACK with a status code that Trunnel would refuse
235 to encode, leading the relay to assert(). We've consolidated the
236 ABI values into Trunnel now. Fixes bug 30454; bugfix
238 - Clients can now handle unknown status codes from INTRODUCE_ACK
239 cells. (The NACK behavior will stay the same.) This will allow us
240 to extend status codes in the future without breaking the normal
241 client behavior. Fixes another part of bug 30454; bugfix
244 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
245 - Relays now respect their AccountingMax bandwidth again. When
246 relays entered "soft" hibernation (which typically starts when
247 we've hit 90% of our AccountingMax), we had stopped checking
248 whether we should enter hard hibernation. Soft hibernation refuses
249 new connections and new circuits, but the existing circuits can
250 continue, meaning that relays could have exceeded their configured
251 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
253 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
254 - Stop ignoring torrc options after an %include directive, when the
255 included directory ends with a file that does not contain any
256 config options (but does contain comments or whitespace). Fixes
257 bug 31408; bugfix on 0.3.1.1-alpha.
259 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
260 - Onion services now always use the exact number of intro points
261 configured with the HiddenServiceNumIntroductionPoints option (or
262 fewer if nodes are excluded). Before, a service could sometimes
263 pick more intro points than configured. Fixes bug 31548; bugfix
266 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
267 - Add a "--list-modules" command to print a list of which compile-
268 time modules are enabled. Closes ticket 30452.
270 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
271 - Remove sudo configuration lines from .travis.yml as they are no
272 longer needed with current Travis build environment. Resolves
275 o Minor features (continuous integration, backport from 0.4.1.4-rc):
276 - Our Travis configuration now uses Chutney to run some network
277 integration tests automatically. Closes ticket 29280.
279 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
280 - When building on Appveyor and Travis, pass the "-k" flag to make,
281 so that we are informed of all compilation failures, not just the
282 first one or two. Closes ticket 31372.
284 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
285 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
286 in December 2018 (of which ~122 were still functional), with a
287 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
288 in June 2019. Closes ticket 28795.
290 o Minor features (geoip, backport from 0.4.2.5):
291 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
292 Country database. Closes ticket 32685.
294 o Minor features (stem tests, backport from 0.4.2.1-alpha):
295 - Change "make test-stem" so it only runs the stem tests that use
296 tor. This change makes test-stem faster and more reliable. Closes
299 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
300 - Avoid spurious errors when Appveyor CI fails before the install step.
301 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
303 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
304 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
305 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
307 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
308 - Fix a logic error that prevented the SessionGroup sub-option from
309 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
311 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
312 - On relays, properly check that a padding machine is absent before
313 logging a warning about it being absent. Fixes bug 30649; bugfix
316 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
317 - Fix a BUG() assertion that occurs within a very small race window
318 between when a client intro circuit opens and when its descriptor
319 gets cleaned up from the cache. The circuit is now closed early,
320 which will trigger a re-fetch of the descriptor and continue the
321 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
323 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
324 - Don't believe clock skew results from NETINFO cells that appear to
325 arrive before we sent the VERSIONS cells they are responding to.
326 Previously, we would accept them up to 3 minutes "in the past".
327 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
329 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
330 - Fix a compilation warning on Windows about casting a function
331 pointer for GetTickCount64(). Fixes bug 31374; bugfix
334 o Minor bugfixes (compilation, backport from 0.4.1.5):
335 - Avoid using labs() on time_t, which can cause compilation warnings
336 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
338 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
339 - Suppress spurious float-conversion warnings from GCC when calling
340 floating-point classifier functions on FreeBSD. Fixes part of bug
341 31687; bugfix on 0.3.1.5-alpha.
343 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
344 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
345 due to missing declarations of abort(), and prevent other such
346 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
348 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
349 - Fix a bug that prevented us from supporting SOCKS5 proxies that
350 want authentication along with configured (but unused!)
351 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
353 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
354 - Avoid trying to read data from closed connections, which can cause
355 needless loops in Libevent and infinite loops in Shadow. Fixes bug
356 30344; bugfix on 0.1.1.1-alpha.
358 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
359 - Allow the test-stem job to fail in Travis, because it sometimes
360 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
361 - Skip test_rebind on macOS in Travis, because it is unreliable on
362 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
363 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
364 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
366 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
367 - Avoid a set of possible code paths that could try to use freed
368 memory in routerlist_free() while Tor was exiting. Fixes bug
369 31003; bugfix on 0.1.2.2-alpha.
371 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
372 - Stop crashing after parsing an unknown descriptor purpose
373 annotation. We think this bug can only be triggered by modifying a
374 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
376 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
377 - Move the "bandwidth-file-headers" line in directory authority
378 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
381 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
382 - On abort, try harder to flush the output buffers of log messages.
383 On some platforms (macOS), log messages could be discarded when
384 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
385 - Report the tor version whenever an assertion fails. Previously, we
386 only reported the Tor version on some crashes, and some non-fatal
387 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
389 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
390 - When extracting an IPv6 address from a PF-based proxy, verify that
391 we are actually configured to receive an IPv6 address, and log an
392 internal error if not. Fixes part of bug 31687; bugfix
395 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
396 - When tor is missing descriptors for some primary entry guards,
397 make the log message less alarming. It's normal for descriptors to
398 expire, as long as tor fetches new ones soon after. Fixes bug
399 31657; bugfix on 0.3.3.1-alpha.
401 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
402 - Do not log a warning when running with an OpenSSL version other
403 than the one Tor was compiled with, if the two versions should be
404 compatible. Previously, we would warn whenever the version was
405 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
407 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
408 - Change log level of message "Hash of session info was not as
409 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
412 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
413 - Rate-limit our the logging message about the obsolete .exit
414 notation. Previously, there was no limit on this warning, which
415 could potentially be triggered many times by a hostile website.
416 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
418 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
419 - Do not log a nonfatal assertion failure when receiving a VERSIONS
420 cell on a connection using the obsolete v1 link protocol. Log a
421 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
423 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
424 - Reset the periodic events' "enabled" flag when Tor is shut down
425 cleanly. Previously, this flag was left on, which caused periodic
426 events not to be re-enabled when Tor was relaunched in-process
427 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
430 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
431 - Avoid a minor memory leak that could occur on relays when failing
432 to create a "keys" directory. Fixes bug 30148; bugfix
435 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
436 - Fix a trivial memory leak when parsing an invalid value
437 from a download schedule in the configuration. Fixes bug
438 30894; bugfix on 0.3.4.1-alpha.
440 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
441 - Fix usage of minherit() on NetBSD and other platforms that define
442 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
443 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
445 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
446 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
447 implemenation) when failing to load an onion service client
448 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
450 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
451 - When purging the DNS cache because of an out-of-memory condition,
452 try purging just the older entries at first. Previously, we would
453 always purge the whole thing. Fixes bug 29617; bugfix
456 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
457 - Avoid crashing in our tor_vasprintf() implementation on systems
458 that define neither vasprintf() nor _vscprintf(). (This bug has
459 been here long enough that we question whether people are running
460 Tor on such systems, but we're applying the fix out of caution.)
461 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
464 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
465 - Remove overly strict assertions that triggered when a pluggable
466 transport failed to launch. Fixes bug 31091; bugfix
468 - Remove an assertion in the Unix process backend. This assertion
469 would trigger when we failed to find the executable for a child
470 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
472 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
473 - Avoid crashing when starting with a corrupt keys directory where
474 the old ntor key and the new ntor key are identical. Fixes bug
475 30916; bugfix on 0.2.4.8-alpha.
477 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
478 - Correctly exclude a redundant rust build job in Travis. Fixes bug
479 31463; bugfix on 0.3.5.4-alpha.
481 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
482 - When testing port rebinding, don't busy-wait for tor to log.
483 Instead, actually sleep for a short time before polling again.
484 Also improve the formatting of control commands and log messages.
485 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
487 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
488 - Log bugs about the TLS read buffer's length only once, rather than
489 filling the logs with similar warnings. Fixes bug 31939; bugfix
492 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
493 - Always retry v2 single onion service intro and rend circuits with
494 a 3-hop path. Previously, v2 single onion services used a 3-hop
495 path when rendezvous circuits were retried after a remote or
496 delayed failure, but a 1-hop path for immediate retries. Fixes bug
497 23818; bugfix on 0.2.9.3-alpha.
498 - Make v3 single onion services fall back to a 3-hop intro, when all
499 intro points are unreachable via a 1-hop path. Previously, v3
500 single onion services failed when all intro nodes were unreachable
501 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
503 o Documentation (backport from 0.4.2.1-alpha):
504 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
505 notice.html so that operators no longer have to host it
506 themselves. Closes ticket 31089.
508 o Testing (backport from 0.4.1.2-alpha):
509 - Specify torrc paths (with empty files) when launching tor in
510 integration tests; refrain from reading user and system torrcs.
511 Resolves issue 29702.
513 o Testing (continuous integration, backport from 0.4.1.1-alpha):
514 - In Travis, show stem's tor log after failure. Closes ticket 30234.
516 o Testing (continuous integration, backport from 0.4.1.5):
517 - In Travis, make stem log a controller trace to the console, and
518 tail stem's tor log after failure. Closes ticket 30591.
519 - In Travis, only run the stem tests that use a tor binary. Closes
522 o Testing (continuous integration, backport from 0.4.2.3-alpha):
523 - Disable all but one Travis CI macOS build, to mitigate slow
524 scheduling of Travis macOS jobs. Closes ticket 32177.
525 - Run the chutney IPv6 networks as part of Travis CI. Closes
527 - Simplify the Travis CI build matrix, and optimise for build time.
529 - Use Windows Server 2019 instead of Windows Server 2016 in our
530 Appveyor builds. Closes ticket 32086.
532 o Testing (continuous integration, backport from 0.4.2.4-rc):
533 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
534 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
535 until we can fix some Bionic permissions issues (see ticket
536 32240). Related to ticket 31919.
537 - Install the mingw OpenSSL package in Appveyor. This makes sure
538 that the OpenSSL headers and libraries match in Tor's Appveyor
539 builds. (This bug was triggered by an Appveyor image update.)
540 Fixes bug 32449; bugfix on 0.3.5.6-rc.
541 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
543 o Testing (continuous integration, backport from 0.4.2.5):
544 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
545 extensions. Also activates clang's -Wtypedef-redefinition warnings.
546 Build some jobs with -std=gnu99, and some jobs without.
549 Changes in version 0.3.5.9 - 2019-12-09
550 Tor 0.3.5.9 backports serveral fixes from later releases, including
551 several that affect bridge users, relay stability, onion services,
554 o Directory authority changes (backport from 0.4.1.5):
555 - The directory authority "dizum" has a new IP address. Closes
558 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
559 - Consider our directory information to have changed when our list
560 of bridges changes. Previously, Tor would not re-compute the
561 status of its directory information when bridges changed, and
562 therefore would not realize that it was no longer able to build
563 circuits. Fixes part of bug 29875.
564 - Do not count previously configured working bridges towards our
565 total of working bridges. Previously, when Tor's list of bridges
566 changed, it would think that the old bridges were still usable,
567 and delay fetching router descriptors for the new ones. Fixes part
568 of bug 29875; bugfix on 0.3.0.1-alpha.
570 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
571 - When considering upgrading circuits from "waiting for guard" to
572 "open", always ignore circuits that are marked for close. Otherwise,
573 we can end up in the situation where a subsystem is notified that
574 a closing circuit has just opened, leading to undesirable
575 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
577 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
578 - When running with NSS, disable TLS 1.2 ciphersuites that use
579 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
580 these ciphersuites don't work -- which caused relays to fail to
581 handshake with one another when these ciphersuites were enabled.
582 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
584 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
585 - Properly clean up the introduction point map when circuits change
586 purpose from onion service circuits to pathbias, measurement, or
587 other circuit types. This should fix some service-side instances
588 of introduction point failure. Fixes bug 29034; bugfix
591 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
592 - Fix an unreachable bug in which an introduction point could try to
593 send an INTRODUCE_ACK with a status code that Trunnel would refuse
594 to encode, leading the relay to assert(). We've consolidated the
595 ABI values into Trunnel now. Fixes bug 30454; bugfix
597 - Clients can now handle unknown status codes from INTRODUCE_ACK
598 cells. (The NACK behavior will stay the same.) This will allow us
599 to extend status codes in the future without breaking the normal
600 client behavior. Fixes another part of bug 30454; bugfix
603 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
604 - Stop ignoring torrc options after an %include directive, when the
605 included directory ends with a file that does not contain any
606 config options (but does contain comments or whitespace). Fixes
607 bug 31408; bugfix on 0.3.1.1-alpha.
609 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
610 - Onion services now always use the exact number of intro points
611 configured with the HiddenServiceNumIntroductionPoints option (or
612 fewer if nodes are excluded). Before, a service could sometimes
613 pick more intro points than configured. Fixes bug 31548; bugfix
616 o Minor features (address selection, backport from 0.4.0.3-alpha):
617 - Treat the subnet 100.64.0.0/10 as public for some purposes;
618 private for others. This subnet is the RFC 6598 (Carrier Grade
619 NAT) IP range, and is deployed by many ISPs as an alternative to
620 RFC 1918 that does not break existing internal networks. Tor now
621 blocks SOCKS and control ports on these addresses and warns users
622 if client ports or ExtORPorts are listening on a RFC 6598 address.
623 Closes ticket 28525. Patch by Neel Chauhan.
625 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
626 - Make bandwidth authorities ignore relays that are reported in the
627 bandwidth file with the flag "vote=0". This change allows us to
628 report unmeasured relays for diagnostic reasons without including
629 their bandwidth in the bandwidth authorities' vote. Closes
632 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
633 - Add a "--list-modules" command to print a list of which compile-
634 time modules are enabled. Closes ticket 30452.
636 o Minor features (continuous integration, backport from 0.4.0.4-rc):
637 - On Travis Rust builds, cleanup Rust registry and refrain from
638 caching the "target/" directory to speed up builds. Resolves
641 o Minor features (continuous integration, backport from 0.4.0.5):
642 - In Travis, tell timelimit to use stem's backtrace signals, and
643 launch python directly from timelimit, so python receives the
644 signals from timelimit, rather than make. Closes ticket 30117.
646 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
647 - Remove sudo configuration lines from .travis.yml as they are no
648 longer needed with current Travis build environment. Resolves
651 o Minor features (continuous integration, backport from 0.4.1.4-rc):
652 - Our Travis configuration now uses Chutney to run some network
653 integration tests automatically. Closes ticket 29280.
655 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
656 - When building on Appveyor and Travis, pass the "-k" flag to make,
657 so that we are informed of all compilation failures, not just the
658 first one or two. Closes ticket 31372.
660 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
661 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
662 in December 2018 (of which ~122 were still functional), with a
663 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
664 in June 2019. Closes ticket 28795.
666 o Minor features (geoip, backport from 0.4.2.5):
667 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
668 Country database. Closes ticket 32685.
670 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
671 - Try to log an error from NSS (if there is any) and a more useful
672 description of our situation if we are using NSS and a call to
673 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
675 o Minor features (stem tests, backport from 0.4.2.1-alpha):
676 - Change "make test-stem" so it only runs the stem tests that use
677 tor. This change makes test-stem faster and more reliable. Closes
680 o Minor bugfixes (security, backport from 0.4.0.4-rc):
681 - Verify in more places that we are not about to create a buffer
682 with more than INT_MAX bytes, to avoid possible OOB access in the
683 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
684 fixed by Tobias Stoeckmann.
685 - Fix a potential double free bug when reading huge bandwidth files.
686 The issue is not exploitable in the current Tor network because
687 the vulnerable code is only reached when directory authorities
688 read bandwidth files, but bandwidth files come from a trusted
689 source (usually the authorities themselves). Furthermore, the
690 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
691 which are not used by any of the current authorities. Fixes bug
692 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
695 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
696 - Reset coverage state on disk after Travis CI has finished. This
697 should prevent future coverage merge errors from causing the test
698 suite for the "process" subsystem to fail. The process subsystem
699 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
701 - Terminate test-stem if it takes more than 9.5 minutes to run.
702 (Travis terminates the job after 10 minutes of no output.)
703 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
705 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
706 - Avoid spurious errors when Appveyor CI fails before the install step.
707 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
709 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
710 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
711 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
713 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
714 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
715 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
718 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
719 - Fix a logic error that prevented the SessionGroup sub-option from
720 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
722 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
723 - Fix a BUG() assertion that occurs within a very small race window
724 between when a client intro circuit opens and when its descriptor
725 gets cleaned up from the cache. The circuit is now closed early,
726 which will trigger a re-fetch of the descriptor and continue the
727 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
729 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
730 - Don't believe clock skew results from NETINFO cells that appear to
731 arrive before we sent the VERSIONS cells they are responding to.
732 Previously, we would accept them up to 3 minutes "in the past".
733 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
735 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
736 - Fix a compilation warning on Windows about casting a function
737 pointer for GetTickCount64(). Fixes bug 31374; bugfix
740 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
741 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
742 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
744 o Minor bugfixes (compilation, backport from 0.4.1.5):
745 - Avoid using labs() on time_t, which can cause compilation warnings
746 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
748 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
749 - Suppress spurious float-conversion warnings from GCC when calling
750 floating-point classifier functions on FreeBSD. Fixes part of bug
751 31687; bugfix on 0.3.1.5-alpha.
753 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
754 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
755 due to missing declarations of abort(), and prevent other such
756 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
758 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
759 - Fix a bug that prevented us from supporting SOCKS5 proxies that
760 want authentication along with configured (but unused!)
761 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
763 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
764 - Avoid trying to read data from closed connections, which can cause
765 needless loops in Libevent and infinite loops in Shadow. Fixes bug
766 30344; bugfix on 0.1.1.1-alpha.
768 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
769 - Allow the test-stem job to fail in Travis, because it sometimes
770 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
771 - Skip test_rebind on macOS in Travis, because it is unreliable on
772 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
773 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
774 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
776 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
777 - Avoid a set of possible code paths that could try to use freed
778 memory in routerlist_free() while Tor was exiting. Fixes bug
779 31003; bugfix on 0.1.2.2-alpha.
781 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
782 - Stop crashing after parsing an unknown descriptor purpose
783 annotation. We think this bug can only be triggered by modifying a
784 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
786 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
787 - Move the "bandwidth-file-headers" line in directory authority
788 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
791 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
792 - On abort, try harder to flush the output buffers of log messages.
793 On some platforms (macOS), log messages could be discarded when
794 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
795 - Report the tor version whenever an assertion fails. Previously, we
796 only reported the Tor version on some crashes, and some non-fatal
797 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
799 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
800 - When extracting an IPv6 address from a PF-based proxy, verify that
801 we are actually configured to receive an IPv6 address, and log an
802 internal error if not. Fixes part of bug 31687; bugfix
805 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
806 - When tor is missing descriptors for some primary entry guards,
807 make the log message less alarming. It's normal for descriptors to
808 expire, as long as tor fetches new ones soon after. Fixes bug
809 31657; bugfix on 0.3.3.1-alpha.
811 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
812 - Avoid logging that we are relaxing a circuit timeout when that
813 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
815 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
816 - Correct a misleading error message when IPv4Only or IPv6Only is
817 used but the resolved address can not be interpreted as an address
818 of the specified IP version. Fixes bug 13221; bugfix on
819 0.2.3.9-alpha. Patch from Kris Katterjohn.
820 - Log the correct port number for listening sockets when "auto" is
821 used to let Tor pick the port number. Previously, port 0 was
822 logged instead of the actual port number. Fixes bug 29144; bugfix
823 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
824 - Stop logging a BUG() warning when Tor is waiting for exit
825 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
827 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
828 - Do not log a warning when running with an OpenSSL version other
829 than the one Tor was compiled with, if the two versions should be
830 compatible. Previously, we would warn whenever the version was
831 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
833 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
834 - Change log level of message "Hash of session info was not as
835 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
838 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
839 - Rate-limit our the logging message about the obsolete .exit
840 notation. Previously, there was no limit on this warning, which
841 could potentially be triggered many times by a hostile website.
842 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
844 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
845 - Do not log a nonfatal assertion failure when receiving a VERSIONS
846 cell on a connection using the obsolete v1 link protocol. Log a
847 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
849 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
850 - Reset the periodic events' "enabled" flag when Tor is shut down
851 cleanly. Previously, this flag was left on, which caused periodic
852 events not to be re-enabled when Tor was relaunched in-process
853 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
856 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
857 - Avoid a minor memory leak that could occur on relays when failing
858 to create a "keys" directory. Fixes bug 30148; bugfix
861 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
862 - Fix a trivial memory leak when parsing an invalid value
863 from a download schedule in the configuration. Fixes bug
864 30894; bugfix on 0.3.4.1-alpha.
866 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
867 - Refactor the shared random state's memory management so that it
868 actually takes ownership of the shared random value pointers.
869 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
871 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
872 - Stop leaking parts of the shared random state in the shared-random
873 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
875 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
876 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
877 implemenation) when failing to load an onion service client
878 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
880 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
881 - When purging the DNS cache because of an out-of-memory condition,
882 try purging just the older entries at first. Previously, we would
883 always purge the whole thing. Fixes bug 29617; bugfix
886 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
887 - Avoid crashing in our tor_vasprintf() implementation on systems
888 that define neither vasprintf() nor _vscprintf(). (This bug has
889 been here long enough that we question whether people are running
890 Tor on such systems, but we're applying the fix out of caution.)
891 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
894 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
895 - Avoid crashing when starting with a corrupt keys directory where
896 the old ntor key and the new ntor key are identical. Fixes bug
897 30916; bugfix on 0.2.4.8-alpha.
899 o Minor bugfixes (rust, backport from 0.4.0.5):
900 - Abort on panic in all build profiles, instead of potentially
901 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
903 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
904 - Correctly exclude a redundant rust build job in Travis. Fixes bug
905 31463; bugfix on 0.3.5.4-alpha.
907 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
908 - Allow connections to single onion services to remain idle without
909 being disconnected. Previously, relays acting as rendezvous points
910 for single onion services were mistakenly closing idle rendezvous
911 circuits after 60 seconds, thinking that they were unused
912 directory-fetching circuits that had served their purpose. Fixes
913 bug 29665; bugfix on 0.2.1.26.
915 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
916 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
917 relay and bridge extra-info documents. Fixes bug 29017; bugfix
920 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
921 - Downgrade some LOG_ERR messages in the address/* tests to
922 warnings. The LOG_ERR messages were occurring when we had no
923 configured network. We were failing the unit tests, because we
924 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
925 29530; bugfix on 0.3.5.8.
926 - Fix our gcov wrapper script to look for object files at the
927 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
929 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
930 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
931 recent test-network.sh to use new chutney features in CI. Fixes
932 bug 29703; bugfix on 0.2.9.1-alpha.
933 - Fix a test failure on Windows caused by an unexpected "BUG"
934 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
937 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
938 - When testing port rebinding, don't busy-wait for tor to log.
939 Instead, actually sleep for a short time before polling again.
940 Also improve the formatting of control commands and log messages.
941 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
943 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
944 - When classifying a client's selection of TLS ciphers, if the
945 client ciphers are not yet available, do not cache the result.
946 Previously, we had cached the unavailability of the cipher list
947 and never looked again, which in turn led us to assume that the
948 client only supported the ancient V1 link protocol. This, in turn,
949 was causing Stem integration tests to stall in some cases. Fixes
950 bug 30021; bugfix on 0.2.4.8-alpha.
952 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
953 - Log bugs about the TLS read buffer's length only once, rather than
954 filling the logs with similar warnings. Fixes bug 31939; bugfix
957 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
958 - Always retry v2 single onion service intro and rend circuits with
959 a 3-hop path. Previously, v2 single onion services used a 3-hop
960 path when rendezvous circuits were retried after a remote or
961 delayed failure, but a 1-hop path for immediate retries. Fixes bug
962 23818; bugfix on 0.2.9.3-alpha.
963 - Make v3 single onion services fall back to a 3-hop intro, when all
964 intro points are unreachable via a 1-hop path. Previously, v3
965 single onion services failed when all intro nodes were unreachable
966 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
968 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
969 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
970 Windows Server 2012 R2 job. The remaining 2 jobs still provide
971 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
972 fast_finish, so failed jobs terminate the build immediately. Fixes
973 bug 29601; bugfix on 0.3.5.4-alpha.
975 o Documentation (backport from 0.4.2.1-alpha):
976 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
977 notice.html so that operators no longer have to host it
978 themselves. Closes ticket 31089.
980 o Testing (backport from 0.4.1.2-alpha):
981 - Specify torrc paths (with empty files) when launching tor in
982 integration tests; refrain from reading user and system torrcs.
983 Resolves issue 29702.
985 o Testing (continuous integration, backport from 0.4.1.1-alpha):
986 - In Travis, show stem's tor log after failure. Closes ticket 30234.
988 o Testing (continuous integration, backport from 0.4.1.5):
989 - In Travis, make stem log a controller trace to the console, and
990 tail stem's tor log after failure. Closes ticket 30591.
991 - In Travis, only run the stem tests that use a tor binary. Closes
994 o Testing (continuous integration, backport from 0.4.2.3-alpha):
995 - Disable all but one Travis CI macOS build, to mitigate slow
996 scheduling of Travis macOS jobs. Closes ticket 32177.
997 - Run the chutney IPv6 networks as part of Travis CI. Closes
999 - Simplify the Travis CI build matrix, and optimise for build time.
1000 Closes ticket 31859.
1001 - Use Windows Server 2019 instead of Windows Server 2016 in our
1002 Appveyor builds. Closes ticket 32086.
1004 o Testing (continuous integration, backport from 0.4.2.4-rc):
1005 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1006 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1007 until we can fix some Bionic permissions issues (see ticket
1008 32240). Related to ticket 31919.
1009 - Install the mingw OpenSSL package in Appveyor. This makes sure
1010 that the OpenSSL headers and libraries match in Tor's Appveyor
1011 builds. (This bug was triggered by an Appveyor image update.)
1012 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1013 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1015 o Testing (continuous integration, backport from 0.4.2.5):
1016 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
1017 extensions. Also activates clang's -Wtypedef-redefinition warnings.
1018 Build some jobs with -std=gnu99, and some jobs without.
1019 Closes ticket 32500.
1021 Changes in version 0.4.2.4-rc - 2019-11-15
1022 Tor 0.4.2.4-rc is the first release candidate in its series. It fixes
1023 several bugs from earlier versions, including a few that would result in
1024 stack traces or incorrect behavior.
1026 o Minor features (build system):
1027 - Make pkg-config use --prefix when cross-compiling, if
1028 PKG_CONFIG_PATH is not set. Closes ticket 32191.
1030 o Minor features (geoip):
1031 - Update geoip and geoip6 to the November 6 2019 Maxmind GeoLite2
1032 Country database. Closes ticket 32440.
1034 o Minor bugfixes (client, onion service v3):
1035 - Fix a BUG() assertion that occurs within a very small race window
1036 between when a client intro circuit opens and when its descriptor
1037 gets cleaned up from the cache. The circuit is now closed early,
1038 which will trigger a re-fetch of the descriptor and continue the
1039 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1041 o Minor bugfixes (code quality):
1042 - Fix "make check-includes" so it runs correctly on out-of-tree
1043 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
1045 o Minor bugfixes (configuration):
1046 - Log the option name when skipping an obsolete option. Fixes bug
1047 32295; bugfix on 0.4.2.1-alpha.
1049 o Minor bugfixes (crash):
1050 - When running Tor with an option like --verify-config or
1051 --dump-config that does not start the event loop, avoid crashing
1052 if we try to exit early because of an error. Fixes bug 32407;
1053 bugfix on 0.3.3.1-alpha.
1055 o Minor bugfixes (directory):
1056 - When checking if a directory connection is anonymous, test if the
1057 circuit was marked for close before looking at its channel. This
1058 avoids a BUG() stacktrace if the circuit was previously closed.
1059 Fixes bug 31958; bugfix on 0.4.2.1-alpha.
1061 o Minor bugfixes (shellcheck):
1062 - Fix minor shellcheck errors in the git-*.sh scripts. Fixes bug
1063 32402; bugfix on 0.4.2.1-alpha.
1064 - Start checking most scripts for shellcheck errors again. Fixes bug
1065 32402; bugfix on 0.4.2.1-alpha.
1067 o Testing (continuous integration):
1068 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1069 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1070 until we can fix some Bionic permissions issues (see ticket
1071 32240). Related to ticket 31919.
1072 - Install the mingw OpenSSL package in Appveyor. This makes sure
1073 that the OpenSSL headers and libraries match in Tor's Appveyor
1074 builds. (This bug was triggered by an Appveyor image update.)
1075 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1076 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1079 Changes in version 0.4.2.3-alpha - 2019-10-24
1080 This release fixes several bugs from the previous alpha release, and
1081 from earlier versions of Tor.
1083 o Major bugfixes (relay):
1084 - Relays now respect their AccountingMax bandwidth again. When
1085 relays entered "soft" hibernation (which typically starts when
1086 we've hit 90% of our AccountingMax), we had stopped checking
1087 whether we should enter hard hibernation. Soft hibernation refuses
1088 new connections and new circuits, but the existing circuits can
1089 continue, meaning that relays could have exceeded their configured
1090 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1092 o Major bugfixes (v3 onion services):
1093 - Onion services now always use the exact number of intro points
1094 configured with the HiddenServiceNumIntroductionPoints option (or
1095 fewer if nodes are excluded). Before, a service could sometimes
1096 pick more intro points than configured. Fixes bug 31548; bugfix
1099 o Minor feature (onion services, control port):
1100 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
1101 (v3) onion services. Previously it defaulted to RSA1024 (v2).
1102 Closes ticket 29669.
1104 o Minor features (testing):
1105 - When running tests that attempt to look up hostnames, replace the
1106 libc name lookup functions with ones that do not actually touch
1107 the network. This way, the tests complete more quickly in the
1108 presence of a slow or missing DNS resolver. Closes ticket 31841.
1110 o Minor features (testing, continuous integration):
1111 - Disable all but one Travis CI macOS build, to mitigate slow
1112 scheduling of Travis macOS jobs. Closes ticket 32177.
1113 - Run the chutney IPv6 networks as part of Travis CI. Closes
1115 - Simplify the Travis CI build matrix, and optimise for build time.
1116 Closes ticket 31859.
1117 - Use Windows Server 2019 instead of Windows Server 2016 in our
1118 Appveyor builds. Closes ticket 32086.
1120 o Minor bugfixes (build system):
1121 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
1122 32124; bugfix on 0.3.4.1-alpha.
1123 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
1125 - Stop failing when jemalloc is requested, but tcmalloc is not
1126 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
1127 - When pkg-config is not installed, or a library that depends on
1128 pkg-config is not found, tell the user what to do to fix the
1129 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
1131 o Minor bugfixes (connections):
1132 - Avoid trying to read data from closed connections, which can cause
1133 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1134 30344; bugfix on 0.1.1.1-alpha.
1136 o Minor bugfixes (error handling):
1137 - Always lock the backtrace buffer before it is used. Fixes bug
1138 31734; bugfix on 0.2.5.3-alpha.
1140 o Minor bugfixes (mainloop, periodic events, in-process API):
1141 - Reset the periodic events' "enabled" flag when Tor is shut down
1142 cleanly. Previously, this flag was left on, which caused periodic
1143 events not to be re-enabled when Tor was relaunched in-process
1144 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1147 o Minor bugfixes (process management):
1148 - Remove overly strict assertions that triggered when a pluggable
1149 transport failed to launch. Fixes bug 31091; bugfix
1151 - Remove an assertion in the Unix process backend. This assertion
1152 would trigger when we failed to find the executable for a child
1153 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
1155 o Minor bugfixes (testing):
1156 - Avoid intermittent test failures due to a test that had relied on
1157 inconsistent timing sources. Fixes bug 31995; bugfix
1159 - When testing port rebinding, don't busy-wait for tor to log.
1160 Instead, actually sleep for a short time before polling again.
1161 Also improve the formatting of control commands and log messages.
1162 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1164 o Minor bugfixes (tls, logging):
1165 - Log bugs about the TLS read buffer's length only once, rather than
1166 filling the logs with similar warnings. Fixes bug 31939; bugfix
1169 o Minor bugfixes (v3 onion services):
1170 - Fix an implicit conversion from ssize_t to size_t discovered by
1171 Coverity. Fixes bug 31682; bugfix on 0.4.2.1-alpha.
1172 - Fix a memory leak in an unlikely error code path when encoding HS
1173 DoS establish intro extension cell. Fixes bug 32063; bugfix
1175 - When cleaning up intro circuits for a v3 onion service, don't
1176 remove circuits that have an established or pending circuit, even
1177 if they ran out of retries. This way, we don't remove a circuit on
1178 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
1181 - Correct the description of "GuardLifetime". Fixes bug 31189;
1182 bugfix on 0.3.0.1-alpha.
1183 - Make clear in the man page, in both the bandwidth section and the
1184 AccountingMax section, that Tor counts in powers of two, not
1185 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
1186 bytes. Resolves ticket 32106.
1189 Changes in version 0.4.2.2-alpha - 2019-10-07
1190 This release fixes several bugs from the previous alpha release, and
1191 from earlier versions. It also includes a change in authorities, so
1192 that they begin to reject the currently unsupported release series.
1194 o Major features (directory authorities):
1195 - Directory authorities now reject relays running all currently
1196 deprecated release series. The currently supported release series
1197 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
1199 o Major bugfixes (embedded Tor):
1200 - Avoid a possible crash when restarting Tor in embedded mode and
1201 enabling a different set of publish/subscribe messages. Fixes bug
1202 31898; bugfix on 0.4.1.1-alpha.
1204 o Major bugfixes (torrc parsing):
1205 - Stop ignoring torrc options after an %include directive, when the
1206 included directory ends with a file that does not contain any
1207 config options (but does contain comments or whitespace). Fixes
1208 bug 31408; bugfix on 0.3.1.1-alpha.
1210 o Minor features (auto-formatting scripts):
1211 - When annotating C macros, never generate a line that our check-
1212 spaces script would reject. Closes ticket 31759.
1213 - When annotating C macros, try to remove cases of double-negation.
1214 Closes ticket 31779.
1216 o Minor features (continuous integration):
1217 - When building on Appveyor and Travis, pass the "-k" flag to make,
1218 so that we are informed of all compilation failures, not just the
1219 first one or two. Closes ticket 31372.
1221 o Minor features (geoip):
1222 - Update geoip and geoip6 to the October 1 2019 Maxmind GeoLite2
1223 Country database. Closes ticket 31931.
1225 o Minor features (maintenance scripts):
1226 - Add a Coccinelle script to detect bugs caused by incrementing or
1227 decrementing a variable inside a call to log_debug(). Since
1228 log_debug() is a macro whose arguments are conditionally
1229 evaluated, it is usually an error to do this. One such bug was
1230 30628, in which SENDME cells were miscounted by a decrement
1231 operator inside a log_debug() call. Closes ticket 30743.
1233 o Minor features (onion services v3):
1234 - Assist users who try to setup v2 client authorization in v3 onion
1235 services by pointing them to the right documentation. Closes
1238 o Minor bugfixes (Appveyor continuous integration):
1239 - Avoid spurious errors when Appveyor CI fails before the install
1240 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1242 o Minor bugfixes (best practices tracker):
1243 - When listing overbroad exceptions, do not also list problems, and
1244 do not list insufficiently broad exceptions. Fixes bug 31338;
1245 bugfix on 0.4.2.1-alpha.
1247 o Minor bugfixes (controller protocol):
1248 - Fix the MAPADDRESS controller command to accept one or more
1249 arguments. Previously, it required two or more arguments, and
1250 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
1252 o Minor bugfixes (logging):
1253 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
1254 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
1255 - Disable backtrace signal handlers when shutting down tor. Fixes
1256 bug 31614; bugfix on 0.2.5.2-alpha.
1257 - Rate-limit our the logging message about the obsolete .exit
1258 notation. Previously, there was no limit on this warning, which
1259 could potentially be triggered many times by a hostile website.
1260 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1261 - When initialising log domain masks, only set known log domains.
1262 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
1264 o Minor bugfixes (logging, protocol violations):
1265 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1266 cell on a connection using the obsolete v1 link protocol. Log a
1267 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1269 o Minor bugfixes (modules):
1270 - Explain what the optional Directory Authority module is, and what
1271 happens when it is disabled. Fixes bug 31825; bugfix
1274 o Minor bugfixes (multithreading):
1275 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
1276 31736; bugfix on 0.0.7.
1278 o Minor bugfixes (relay):
1279 - Avoid crashing when starting with a corrupt keys directory where
1280 the old ntor key and the new ntor key are identical. Fixes bug
1281 30916; bugfix on 0.2.4.8-alpha.
1283 o Minor bugfixes (tests, SunOS):
1284 - Avoid a map_anon_nofork test failure due to a signed/unsigned
1285 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
1287 o Code simplification and refactoring:
1288 - Refactor connection_control_process_inbuf() to reduce the size of
1289 a practracker exception. Closes ticket 31840.
1290 - Refactor the microdescs_parse_from_string() function into smaller
1291 pieces, for better comprehensibility. Closes ticket 31675.
1292 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
1293 tests and fuzzers, rather than using hard-coded values. Closes
1295 - Interface for function `decrypt_desc_layer` cleaned up. Closes
1299 - Document the signal-safe logging behaviour in the tor man page.
1300 Also add some comments to the relevant functions. Closes
1302 - Explain why we can't destroy the backtrace buffer mutex. Explain
1303 why we don't need to destroy the log mutex. Closes ticket 31736.
1304 - The Tor source code repository now includes a (somewhat dated)
1305 description of Tor's modular architecture, in doc/HACKING/design.
1306 This is based on the old "tor-guts.git" repository, which we are
1307 adopting and superseding. Closes ticket 31849.
1310 Changes in version 0.4.1.6 - 2019-09-19
1311 This release backports several bugfixes to improve stability and
1312 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
1313 or experiencing reliability issues with single onion services, should
1316 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
1317 - Tolerate systems (including some Android installations) where
1318 madvise and MADV_DONTDUMP are available at build-time, but not at
1319 run time. Previously, these systems would notice a failed syscall
1320 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
1321 - Tolerate systems (including some Linux installations) where
1322 madvise and/or MADV_DONTFORK are available at build-time, but not
1323 at run time. Previously, these systems would notice a failed
1324 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
1326 o Minor features (stem tests, backport from 0.4.2.1-alpha):
1327 - Change "make test-stem" so it only runs the stem tests that use
1328 tor. This change makes test-stem faster and more reliable. Closes
1331 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
1332 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1333 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1335 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
1336 - Add more stub functions to fix compilation on Android with link-
1337 time optimization when --disable-module-dirauth is used.
1338 Previously, these compilation settings would make the compiler
1339 look for functions that didn't exist. Fixes bug 31552; bugfix
1341 - Suppress spurious float-conversion warnings from GCC when calling
1342 floating-point classifier functions on FreeBSD. Fixes part of bug
1343 31687; bugfix on 0.3.1.5-alpha.
1345 o Minor bugfixes (controller protocol):
1346 - Fix the MAPADDRESS controller command to accept one or more
1347 arguments. Previously, it required two or more arguments, and ignored
1348 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
1350 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
1351 - When extracting an IPv6 address from a PF-based proxy, verify that
1352 we are actually configured to receive an IPv6 address, and log an
1353 internal error if not. Fixes part of bug 31687; bugfix
1356 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
1357 - When tor is missing descriptors for some primary entry guards,
1358 make the log message less alarming. It's normal for descriptors to
1359 expire, as long as tor fetches new ones soon after. Fixes bug
1360 31657; bugfix on 0.3.3.1-alpha.
1362 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
1363 - Change log level of message "Hash of session info was not as
1364 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1367 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
1368 - Correctly exclude a redundant rust build job in Travis. Fixes bug
1369 31463; bugfix on 0.3.5.4-alpha.
1371 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
1372 - Always retry v2 single onion service intro and rend circuits with
1373 a 3-hop path. Previously, v2 single onion services used a 3-hop
1374 path when rendezvous circuits were retried after a remote or
1375 delayed failure, but a 1-hop path for immediate retries. Fixes bug
1376 23818; bugfix on 0.2.9.3-alpha.
1378 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
1379 - Always retry v3 single onion service intro and rend circuits with
1380 a 3-hop path. Previously, v3 single onion services used a 3-hop
1381 path when rend circuits were retried after a remote or delayed
1382 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
1383 bugfix on 0.3.2.1-alpha.
1384 - Make v3 single onion services fall back to a 3-hop intro, when all
1385 intro points are unreachable via a 1-hop path. Previously, v3
1386 single onion services failed when all intro nodes were unreachable
1387 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
1389 o Documentation (backport from 0.4.2.1-alpha):
1390 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
1391 notice.html so that operators no longer have to host it
1392 themselves. Closes ticket 31089.
1395 Changes in version 0.4.2.1-alpha - 2019-09-17
1396 This is the first alpha release in the 0.4.2.x series. It adds new
1397 defenses for denial-of-service attacks against onion services. It also
1398 includes numerous kinds of bugfixes and refactoring to help improve
1399 Tor's stability and ease of development.
1401 o Major features (onion service v3, denial of service):
1402 - Add onion service introduction denial of service defenses. Intro
1403 points can now rate-limit client introduction requests, using
1404 parameters that can be sent by the service within the
1405 ESTABLISH_INTRO cell. If the cell extension for this is not used,
1406 the intro point will honor the consensus parameters. Closes
1409 o Major bugfixes (circuit build, guard):
1410 - When considering upgrading circuits from "waiting for guard" to
1411 "open", always ignore circuits that are marked for close.
1412 Previously we could end up in the situation where a subsystem is
1413 notified of a circuit opening, but the circuit is still marked for
1414 close, leading to undesirable behavior. Fixes bug 30871; bugfix
1417 o Major bugfixes (crash, Linux, Android):
1418 - Tolerate systems (including some Android installations) where
1419 madvise and MADV_DONTDUMP are available at build-time, but not at
1420 run time. Previously, these systems would notice a failed syscall
1421 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
1422 - Tolerate systems (including some Linux installations) where
1423 madvise and/or MADV_DONTFORK are available at build-time, but not
1424 at run time. Previously, these systems would notice a failed
1425 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
1427 o Minor features (best practices tracker):
1428 - Our best-practices tracker now integrates with our include-checker
1429 tool to keep track of how many layering violations we have not yet
1430 fixed. We hope to reduce this number over time to improve Tor's
1431 modularity. Closes ticket 31176.
1432 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
1433 practracker from the environment. We may want this for continuous
1434 integration. Closes ticket 31309.
1435 - Give a warning rather than an error when a practracker exception
1436 is violated by a small amount, add a --list-overbroad option to
1437 practracker that lists exceptions that are stricter than they need
1438 to be, and provide an environment variable for disabling
1439 practracker. Closes ticket 30752.
1440 - Our best-practices tracker now looks at headers as well as C
1441 files. Closes ticket 31175.
1443 o Minor features (build system):
1444 - Add --disable-manpage and --disable-html-manual options to
1445 configure script. This will enable shortening build times by not
1446 building documentation. Resolves issue 19381.
1448 o Minor features (compilation):
1449 - Log a more useful error message when we are compiling and one of
1450 the compile-time hardening options we have selected can be linked
1451 but not executed. Closes ticket 27530.
1453 o Minor features (configuration):
1454 - The configuration code has been extended to allow splitting
1455 configuration data across multiple objects. Previously, all
1456 configuration data needed to be kept in a single object, which
1457 tended to become bloated. Closes ticket 31240.
1459 o Minor features (continuous integration):
1460 - When running CI builds on Travis, put some random data in
1461 ~/.torrc, to make sure no tests are reading the Tor configuration
1462 file from its default location. Resolves issue 30102.
1464 o Minor features (debugging):
1465 - Log a nonfatal assertion failure if we encounter a configuration
1466 line whose command is "CLEAR" but which has a nonempty value. This
1467 should be impossible, according to the rules of our configuration
1468 line parsing. Closes ticket 31529.
1470 o Minor features (git hooks):
1471 - Our pre-commit git hook now checks for a special file before
1472 running practracker, so that practracker only runs on branches
1473 that are based on master. Since the pre-push hook calls the pre-
1474 commit hook, practracker will also only run before pushes of
1475 branches based on master. Closes ticket 30979.
1477 o Minor features (git scripts):
1478 - Add a "--" command-line argument, to separate git-push-all.sh
1479 script arguments from arguments that are passed through to git
1480 push. Closes ticket 31314.
1481 - Add a -r <remote-name> argument to git-push-all.sh, so the script
1482 can push test branches to a personal remote. Closes ticket 31314.
1483 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
1484 git-push-all.sh, which makes these scripts create, merge forward,
1485 and push test branches. Closes ticket 31314.
1486 - Add a -u argument to git-merge-forward.sh, so that the script can
1487 re-use existing test branches after a merge failure and fix.
1488 Closes ticket 31314.
1489 - Add a TOR_GIT_PUSH env var, which sets the default git push
1490 command and arguments for git-push-all.sh. Closes ticket 31314.
1491 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
1492 script push master and maint branches with a delay between each
1493 branch. These delays trigger the CI jobs in a set order, which
1494 should show the most likely failures first. Also make pushes
1495 atomic by default, and make the script pass any command-line
1496 arguments to git push. Closes ticket 29879.
1497 - Call the shellcheck script from the pre-commit hook. Closes
1499 - Skip pushing test branches that are the same as a remote
1500 maint/release/master branch in git-push-all.sh by default. Add a
1501 -s argument, so git-push-all.sh can push all test branches. Closes
1504 o Minor features (IPv6, logging):
1505 - Log IPv6 addresses as well as IPv4 addresses when describing
1506 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
1508 o Minor features (onion service v3):
1509 - Do not allow single hop clients to fetch or post an HS descriptor
1510 from an HSDir. Closes ticket 24964.
1512 o Minor features (onion service):
1513 - Disallow single-hop clients at the introduction point. We've
1514 removed Tor2web support a while back and single-hop rendezvous
1515 attempts are blocked at the relays. This change should remove load
1516 off the network from spammy clients. Close ticket 24963.
1518 o Minor features (stem tests):
1519 - Change "make test-stem" so it only runs the stem tests that use
1520 tor. This change makes test-stem faster and more reliable. Closes
1523 o Minor features (testing):
1524 - Add a script to invoke "tor --dump-config" and "tor
1525 --verify-config" with various configuration options, and see
1526 whether tor's resulting configuration or error messages are what
1527 we expect. Use it for integration testing of our +Option and
1528 /Option flags. Closes ticket 31637.
1529 - Improve test coverage for our existing configuration parsing and
1530 management API. Closes ticket 30893.
1531 - Add integration tests to make sure that practracker gives the
1532 outputs we expect. Closes ticket 31477.
1533 - The practracker self-tests are now run as part of the Tor test
1534 suite. Closes ticket 31304.
1536 o Minor features (token bucket):
1537 - Implement a generic token bucket that uses a single counter, for
1538 use in anti-DoS onion service work. Closes ticket 30687.
1540 o Minor bugfixes (best practices tracker):
1541 - Fix a few issues in the best-practices script, including tests,
1542 tab tolerance, error reporting, and directory-exclusion logic.
1543 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
1544 - When running check-best-practices, only consider files in the src
1545 subdirectory. Previously we had recursively considered all
1546 subdirectories, which made us get confused by the temporary
1547 directories made by "make distcheck". Fixes bug 31578; bugfix
1550 o Minor bugfixes (build system):
1551 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1552 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1554 o Minor bugfixes (chutney, makefiles, documentation):
1555 - "make test-network-all" now shows the warnings from each test-
1556 network.sh run on the console, so developers see new warnings
1557 early. We've also improved the documentation for this feature, and
1558 renamed a Makefile variable so the code is self-documenting. Fixes
1559 bug 30455; bugfix on 0.3.0.4-rc.
1561 o Minor bugfixes (compilation):
1562 - Add more stub functions to fix compilation on Android with link-
1563 time optimization when --disable-module-dirauth is used.
1564 Previously, these compilation settings would make the compiler
1565 look for functions that didn't exist. Fixes bug 31552; bugfix
1567 - Suppress spurious float-conversion warnings from GCC when calling
1568 floating-point classifier functions on FreeBSD. Fixes part of bug
1569 31687; bugfix on 0.3.1.5-alpha.
1571 o Minor bugfixes (configuration):
1572 - Invalid floating-point values in the configuration file are now
1573 treated as errors in the configuration. Previously, they were
1574 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
1576 o Minor bugfixes (coverity):
1577 - Add an assertion when parsing a BEGIN cell so that coverity can be
1578 sure that we are not about to dereference a NULL address. Fixes
1579 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
1580 - In our siphash implementation, when building for coverity, use
1581 memcpy in place of a switch statement, so that coverity can tell
1582 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
1583 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
1584 - Fix several coverity warnings from our unit tests. Fixes bug
1585 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
1587 o Minor bugfixes (developer tooling):
1588 - Only log git script changes in the post-merge script when the
1589 merge was to the master branch. Fixes bug 31040; bugfix
1592 o Minor bugfixes (directory authorities):
1593 - Return a distinct status when formatting annotations fails. Fixes
1594 bug 30780; bugfix on 0.2.0.8-alpha.
1596 o Minor bugfixes (error handling):
1597 - On abort, try harder to flush the output buffers of log messages.
1598 On some platforms (macOS), log messages could be discarded when
1599 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1600 - Report the tor version whenever an assertion fails. Previously, we
1601 only reported the Tor version on some crashes, and some non-fatal
1602 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1603 - When tor aborts due to an error, close log file descriptors before
1604 aborting. Closing the logs makes some OSes flush log file buffers,
1605 rather than deleting buffered log lines. Fixes bug 31594; bugfix
1608 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
1609 - When extracting an IPv6 address from a PF-based proxy, verify that
1610 we are actually configured to receive an IPv6 address, and log an
1611 internal error if not. Fixes part of bug 31687; bugfix
1614 o Minor bugfixes (git hooks):
1615 - Remove a duplicate call to practracker from the pre-push hook. The
1616 pre-push hook already calls the pre-commit hook, which calls
1617 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
1619 o Minor bugfixes (git scripts):
1620 - Stop hard-coding the bash path in the git scripts. Some OSes don't
1621 have bash in /usr/bin, others have an ancient bash at this path.
1622 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
1623 - Stop hard-coding the tor master branch name and worktree path in
1624 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
1625 - Allow git-push-all.sh to be run from any directory. Previously,
1626 the script only worked if run from an upstream worktree directory.
1627 Closes ticket 31678.
1629 o Minor bugfixes (guards):
1630 - When tor is missing descriptors for some primary entry guards,
1631 make the log message less alarming. It's normal for descriptors to
1632 expire, as long as tor fetches new ones soon after. Fixes bug
1633 31657; bugfix on 0.3.3.1-alpha.
1635 o Minor bugfixes (ipv6):
1636 - Check for private IPv6 addresses alongside their IPv4 equivalents
1637 when authorities check descriptors. Previously, we only checked
1638 for private IPv4 addresses. Fixes bug 31088; bugfix on
1639 0.2.3.21-rc. Patch by Neel Chauhan.
1640 - When parsing microdescriptors, we should check the IPv6 exit
1641 policy alongside IPv4. Previously, we checked both exit policies
1642 for only router info structures, while microdescriptors were
1643 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
1646 o Minor bugfixes (logging):
1647 - Change log level of message "Hash of session info was not as
1648 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1650 - Fix a code issue that would have broken our parsing of log domains
1651 as soon as we had 33 of them. Fortunately, we still only have 29.
1652 Fixes bug 31451; bugfix on 0.4.1.4-rc.
1654 o Minor bugfixes (memory management):
1655 - Stop leaking a small amount of memory in nt_service_install(), in
1656 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
1659 o Minor bugfixes (networking, IP addresses):
1660 - When parsing addresses via Tor's internal DNS lookup API, reject
1661 IPv4 addresses in square brackets, and accept IPv6 addresses in
1662 square brackets. This change completes the work started in 23082,
1663 making address parsing consistent between tor's internal DNS
1664 lookup and address parsing APIs. Fixes bug 30721; bugfix
1666 - When parsing addresses via Tor's internal address:port parsing and
1667 DNS lookup APIs, require IPv6 addresses with ports to have square
1668 brackets. But allow IPv6 addresses without ports, whether or not
1669 they have square brackets. Fixes bug 30721; bugfix
1672 o Minor bugfixes (onion service v3):
1673 - When purging the client descriptor cache, close any introduction
1674 point circuits associated with purged cache entries. This avoids
1675 picking those circuits later when connecting to the same
1676 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
1678 o Minor bugfixes (onion services):
1679 - In the hs_ident_circuit_t data structure, remove the unused field
1680 circuit_type and the respective argument in hs_ident_circuit_new().
1681 This field was set by clients (for introduction) and services (for
1682 introduction and rendezvous) but was never used afterwards. Fixes
1683 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
1685 o Minor bugfixes (operator tools):
1686 - Make tor-print-ed-signing-cert(1) print certificate expiration
1687 date in RFC 1123 and UNIX timestamp formats, to make output
1688 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
1690 o Minor bugfixes (rust):
1691 - Correctly exclude a redundant rust build job in Travis. Fixes bug
1692 31463; bugfix on 0.3.5.4-alpha.
1693 - Raise the minimum rustc version to 1.31.0, as checked by configure
1694 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
1696 o Minor bugfixes (sendme, code structure):
1697 - Rename the trunnel SENDME file definition from sendme.trunnel to
1698 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
1699 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
1701 o Minor bugfixes (statistics):
1702 - Stop removing the ed25519 signature if the extra info file is too
1703 big. If the signature data was removed, but the keyword was kept,
1704 this could result in an unparseable extra info file. Fixes bug
1705 30958; bugfix on 0.2.7.2-alpha.
1707 o Minor bugfixes (subsystems):
1708 - Make the subsystem init order match the subsystem module
1709 dependencies. Call windows process security APIs as early as
1710 possible. Initialize logging before network and time, so that
1711 network and time can use logging. Fixes bug 31615; bugfix
1714 o Minor bugfixes (testing):
1715 - Teach the util/socketpair_ersatz test to work correctly when we
1716 have no network stack configured. Fixes bug 30804; bugfix
1719 o Minor bugfixes (v2 single onion services):
1720 - Always retry v2 single onion service intro and rend circuits with
1721 a 3-hop path. Previously, v2 single onion services used a 3-hop
1722 path when rendezvous circuits were retried after a remote or
1723 delayed failure, but a 1-hop path for immediate retries. Fixes bug
1724 23818; bugfix on 0.2.9.3-alpha.
1726 o Minor bugfixes (v3 single onion services):
1727 - Always retry v3 single onion service intro and rend circuits with
1728 a 3-hop path. Previously, v3 single onion services used a 3-hop
1729 path when rend circuits were retried after a remote or delayed
1730 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
1731 bugfix on 0.3.2.1-alpha.
1732 - Make v3 single onion services fall back to a 3-hop intro, when all
1733 intro points are unreachable via a 1-hop path. Previously, v3
1734 single onion services failed when all intro nodes were unreachable
1735 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
1738 - Improve documentation in circuit padding subsystem. Patch by
1739 Tobias Pulls. Closes ticket 31113.
1740 - Include an example usage for IPv6 ORPort in our sample torrc.
1741 Closes ticket 31320; patch from Ali Raheem.
1742 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
1743 notice.html so that operators no longer have to host it
1744 themselves. Closes ticket 31089.
1747 - No longer include recommended package digests in votes as detailed
1748 in proposal 301. The RecommendedPackages torrc option is
1749 deprecated and will no longer have any effect. "package" lines
1750 will still be considered when computing consensuses for consensus
1751 methods that include them. (This change has no effect on the list
1752 of recommended Tor versions, which is still in use.) Closes
1754 - Remove torctl.in from contrib/dist directory. Resolves
1758 - Run shellcheck for all non-third-party shell scripts that are
1759 shipped with Tor. Closes ticket 29533.
1760 - When checking shell scripts, ignore any user-created directories.
1761 Closes ticket 30967.
1763 o Code simplification and refactoring (config handling):
1764 - Extract our variable manipulation code from confparse.c to a new
1765 lower-level typedvar.h module. Closes ticket 30864.
1766 - Lower another layer of object management from confparse.c to a
1767 more general tool. Now typed structure members are accessible via
1768 an abstract type. Implements ticket 30914.
1769 - Move our backend logic for working with configuration and state
1770 files into a lower-level library, since it no longer depends on
1771 any tor-specific functionality. Closes ticket 31626.
1772 - Numerous simplifications in configuration-handling logic: remove
1773 duplicated macro definitions, replace magical names with flags,
1774 and refactor "TestingTorNetwork" to use the same default-option
1775 logic as the rest of Tor. Closes ticket 30935.
1776 - Replace our ad-hoc set of flags for configuration variables and
1777 configuration variable types with fine-grained orthogonal flags
1778 corresponding to the actual behavior we want. Closes ticket 31625.
1780 o Code simplification and refactoring (misc):
1781 - Eliminate some uses of lower-level control reply abstractions,
1782 primarily in the onion_helper functions. Closes ticket 30889.
1783 - Rework bootstrap tracking to use the new publish-subscribe
1784 subsystem. Closes ticket 29976.
1785 - Rewrite format_node_description() and router_get_verbose_nickname()
1786 to use strlcpy() and strlcat(). The previous implementation used
1787 memcpy() and pointer arithmetic, which was error-prone. Closes
1788 ticket 31545. This is CID 1452819.
1789 - Split extrainfo_dump_to_string() into smaller functions. Closes
1791 - Use the ptrdiff_t type consistently for expressing variable
1792 offsets and pointer differences. Previously we incorrectly (but
1793 harmlessly) used int and sometimes off_t for these cases. Closes
1795 - Use the subsystems mechanism to manage the main event loop code.
1796 Closes ticket 30806.
1797 - Various simplifications and minor improvements to the circuit
1798 padding machines. Patch by Tobias Pulls. Closes tickets 31112
1801 o Documentation (hard-coded directories):
1802 - Improve the documentation for the DirAuthority and FallbackDir
1803 torrc options. Closes ticket 30955.
1805 o Documentation (tor.1 man page):
1806 - Fix typo in tor.1 man page: the option is "--help", not "-help".
1807 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
1810 Changes in version 0.4.1.5 - 2019-08-20
1811 This is the first stable release in the 0.4.1.x series. This series
1812 adds experimental circuit-level padding, authenticated SENDME cells to
1813 defend against certain attacks, and several performance improvements
1814 to save on CPU consumption. It fixes bugs in bootstrapping and v3
1815 onion services. It also includes numerous smaller features and
1816 bugfixes on earlier versions.
1818 Per our support policy, we will support the 0.4.1.x series for nine
1819 months, or until three months after the release of a stable 0.4.2.x:
1820 whichever is longer. If you need longer-term support, please stick
1821 with 0.3.5.x, which will we plan to support until Feb 2022.
1823 Below are the changes since 0.4.1.4-rc. For a complete list of changes
1824 since 0.4.0.5, see the ReleaseNotes file.
1826 o Directory authority changes:
1827 - The directory authority "dizum" has a new IP address. Closes
1830 o Minor features (circuit padding logging):
1831 - Demote noisy client-side warn logs about circuit padding to
1832 protocol warnings. Add additional log messages and circuit ID
1833 fields to help with bug 30992 and any other future issues.
1835 o Minor bugfixes (circuit padding negotiation):
1836 - Bump the circuit padding protocol version to explicitly signify
1837 that the HS setup machine support is finalized in 0.4.1.x-stable.
1838 This also means that 0.4.1.x-alpha clients will not negotiate
1839 padding with 0.4.1.x-stable relays, and 0.4.1.x-stable clients
1840 will not negotiate padding with 0.4.1.x-alpha relays (or 0.4.0.x
1841 relays). Fixes bug 31356; bugfix on 0.4.1.1-alpha.
1843 o Minor bugfixes (circuit padding):
1844 - Ignore non-padding cells on padding circuits. This addresses
1845 various warning messages from subsystems that were not expecting
1846 padding circuits. Fixes bug 30942; bugfix on 0.4.1.1-alpha.
1848 o Minor bugfixes (clock skew detection):
1849 - Don't believe clock skew results from NETINFO cells that appear to
1850 arrive before we sent the VERSIONS cells they are responding to.
1851 Previously, we would accept them up to 3 minutes "in the past".
1852 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1854 o Minor bugfixes (compatibility, standards compliance):
1855 - Fix a bug that would invoke undefined behavior on certain
1856 operating systems when trying to asprintf() a string exactly
1857 INT_MAX bytes long. We don't believe this is exploitable, but it's
1858 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
1859 Found and fixed by Tobias Stoeckmann.
1861 o Minor bugfixes (compilation warning):
1862 - Fix a compilation warning on Windows about casting a function
1863 pointer for GetTickCount64(). Fixes bug 31374; bugfix
1866 o Minor bugfixes (compilation):
1867 - Avoid using labs() on time_t, which can cause compilation warnings
1868 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1870 o Minor bugfixes (distribution):
1871 - Do not ship any temporary files found in the
1872 scripts/maint/practracker directory. Fixes bug 31311; bugfix
1875 o Testing (continuous integration):
1876 - In Travis, make stem log a controller trace to the console, and
1877 tail stem's tor log after failure. Closes ticket 30591.
1878 - In Travis, only run the stem tests that use a tor binary. Closes
1882 Changes in version 0.4.1.4-rc - 2019-07-25
1883 Tor 0.4.1.4-rc fixes a few bugs from previous versions of Tor, and
1884 updates to a new list of fallback directories. If no new bugs are
1885 found, the next release in the 0.4.1.x serious should be stable.
1887 o Major bugfixes (circuit build, guard):
1888 - When considering upgrading circuits from "waiting for guard" to
1889 "open", always ignore circuits that are marked for close. Otherwise,
1890 we can end up in the situation where a subsystem is notified that
1891 a closing circuit has just opened, leading to undesirable
1892 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
1894 o Minor features (continuous integration):
1895 - Our Travis configuration now uses Chutney to run some network
1896 integration tests automatically. Closes ticket 29280.
1898 o Minor features (fallback directory list):
1899 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
1900 in December 2018 (of which ~122 were still functional), with a
1901 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
1902 in June 2019. Closes ticket 28795.
1904 o Minor bugfixes (circuit padding):
1905 - On relays, properly check that a padding machine is absent before
1906 logging a warning about it being absent. Fixes bug 30649; bugfix
1908 - Add two NULL checks in unreachable places to silence Coverity (CID
1909 144729 and 1447291) and better future-proof ourselves. Fixes bug
1910 31024; bugfix on 0.4.1.1-alpha.
1912 o Minor bugfixes (crash on exit):
1913 - Avoid a set of possible code paths that could try to use freed
1914 memory in routerlist_free() while Tor was exiting. Fixes bug
1915 31003; bugfix on 0.1.2.2-alpha.
1917 o Minor bugfixes (logging):
1918 - Fix a conflict between the flag used for messaging-domain log
1919 messages, and the LD_NO_MOCK testing flag. Fixes bug 31080; bugfix
1922 o Minor bugfixes (memory leaks):
1923 - Fix a trivial memory leak when parsing an invalid value from a
1924 download schedule in the configuration. Fixes bug 30894; bugfix
1927 o Code simplification and refactoring:
1928 - Remove some dead code from circpad_machine_remove_token() to fix
1929 some Coverity warnings (CID 1447298). Fixes bug 31027; bugfix
1933 Changes in version 0.4.1.3-alpha - 2019-06-25
1934 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
1935 alpha, most of them from earlier release series.
1937 o Major bugfixes (Onion service reachability):
1938 - Properly clean up the introduction point map when circuits change
1939 purpose from onion service circuits to pathbias, measurement, or
1940 other circuit types. This should fix some service-side instances
1941 of introduction point failure. Fixes bug 29034; bugfix
1944 o Minor features (geoip):
1945 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
1946 Country database. Closes ticket 30852.
1948 o Minor features (logging):
1949 - Give a more useful assertion failure message if we think we have
1950 minherit() but we fail to make a region non-inheritable. Give a
1951 compile-time warning if our support for minherit() is incomplete.
1952 Closes ticket 30686.
1954 o Minor bugfixes (circuit isolation):
1955 - Fix a logic error that prevented the SessionGroup sub-option from
1956 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
1958 o Minor bugfixes (continuous integration):
1959 - Allow the test-stem job to fail in Travis, because it sometimes
1960 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
1961 - Skip test_rebind on macOS in Travis, because it is unreliable on
1962 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1963 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
1964 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1966 o Minor bugfixes (directory authorities):
1967 - Stop crashing after parsing an unknown descriptor purpose
1968 annotation. We think this bug can only be triggered by modifying a
1969 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
1971 o Minor bugfixes (pluggable transports):
1972 - When running as a bridge with pluggable transports, always publish
1973 pluggable transport information in our extrainfo descriptor, even
1974 if ExtraInfoStatistics is 0. This information is needed by
1975 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
1978 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
1979 Closes ticket 30630.
1982 Changes in version 0.4.1.2-alpha - 2019-06-06
1983 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
1984 previous alpha, and some much older. It also contains minor testing
1985 improvements, and an improvement to the security of our authenticated
1986 SENDME implementation.
1988 o Major bugfixes (bridges):
1989 - Consider our directory information to have changed when our list
1990 of bridges changes. Previously, Tor would not re-compute the
1991 status of its directory information when bridges changed, and
1992 therefore would not realize that it was no longer able to build
1993 circuits. Fixes part of bug 29875.
1994 - Do not count previously configured working bridges towards our
1995 total of working bridges. Previously, when Tor's list of bridges
1996 changed, it would think that the old bridges were still usable,
1997 and delay fetching router descriptors for the new ones. Fixes part
1998 of bug 29875; bugfix on 0.3.0.1-alpha.
2000 o Major bugfixes (flow control, SENDME):
2001 - Decrement the stream-level package window after packaging a cell.
2002 Previously, it was done inside a log_debug() call, meaning that if
2003 debug logs were not enabled, the decrement would never happen, and
2004 thus the window would be out of sync with the other end point.
2005 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
2007 o Major bugfixes (onion service reachability):
2008 - Properly clean up the introduction point map and associated state
2009 when circuits change purpose from onion service circuits to
2010 pathbias, measurement, or other circuit types. This may fix some
2011 instances of introduction point failure. Fixes bug 29034; bugfix
2014 o Minor features (authenticated SENDME):
2015 - Ensure that there is enough randomness on every circuit to prevent
2016 an attacker from successfully predicting the hashes they will need
2017 to include in authenticated SENDME cells. At a random interval, if
2018 we have not sent randomness already, we now leave some extra space
2019 at the end of a cell that we can fill with random bytes. Closes
2022 o Minor features (continuous integration):
2023 - When running coverage builds on Travis, we now set
2024 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
2027 o Minor features (maintenance):
2028 - Add a new "make autostyle" target that developers can use to apply
2029 all automatic Tor style and consistency conversions to the
2030 codebase. Closes ticket 30539.
2032 o Minor features (testing):
2033 - The circuitpadding tests now use a reproducible RNG implementation,
2034 so that if a test fails, we can learn why. Part of ticket 28878.
2035 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
2036 to set the RNG seed for tests that use a reproducible RNG. Part of
2038 - When running tests in coverage mode, take additional care to make
2039 our coverage deterministic, so that we can accurately track
2040 changes in code coverage. Closes ticket 30519.
2042 o Minor bugfixes (configuration, proxies):
2043 - Fix a bug that prevented us from supporting SOCKS5 proxies that
2044 want authentication along with configured (but unused!)
2045 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
2047 o Minor bugfixes (controller):
2048 - POSTDESCRIPTOR requests should work again. Previously, they were
2049 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
2051 - Repair the HSFETCH command so that it works again. Previously, it
2052 expected a body when it shouldn't have. Fixes bug 30646; bugfix
2055 o Minor bugfixes (developer tooling):
2056 - Fix pre-push hook to allow fixup and squash commits when pushing
2057 to non-upstream git remote. Fixes bug 30286; bugfix
2060 o Minor bugfixes (directory authority):
2061 - Move the "bandwidth-file-headers" line in directory authority
2062 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
2065 o Minor bugfixes (NetBSD):
2066 - Fix usage of minherit() on NetBSD and other platforms that define
2067 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
2068 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
2070 o Minor bugfixes (out-of-memory handler):
2071 - When purging the DNS cache because of an out-of-memory condition,
2072 try purging just the older entries at first. Previously, we would
2073 always purge the whole thing. Fixes bug 29617; bugfix
2076 o Minor bugfixes (portability):
2077 - Avoid crashing in our tor_vasprintf() implementation on systems
2078 that define neither vasprintf() nor _vscprintf(). (This bug has
2079 been here long enough that we question whether people are running
2080 Tor on such systems, but we're applying the fix out of caution.)
2081 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
2084 o Minor bugfixes (shutdown, libevent, memory safety):
2085 - Avoid use-after-free bugs when shutting down, by making sure that
2086 we shut down libevent only after shutting down all of its users.
2087 We believe these are harmless in practice, since they only occur
2088 on the shutdown path, and do not involve any attacker-controlled
2089 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
2091 o Minor bugfixes (static analysis):
2092 - Fix several spurious Coverity warnings about the unit tests, to
2093 lower our chances of missing real warnings in the future. Fixes
2094 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
2097 - Specify torrc paths (with empty files) when launching tor in
2098 integration tests; refrain from reading user and system torrcs.
2099 Resolves issue 29702.
2102 Changes in version 0.4.1.1-alpha - 2019-05-22
2103 This is the first alpha in the 0.4.1.x series. It introduces
2104 lightweight circuit padding to make some onion-service circuits harder
2105 to distinguish, includes a new "authenticated SENDME" feature to make
2106 certain denial-of-service attacks more difficult, and improves
2107 performance in several areas.
2109 o Major features (circuit padding):
2110 - Onion service clients now add padding cells at the start of their
2111 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
2112 look more like general purpose Exit traffic. The overhead for this
2113 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
2114 extra upstream cell and 10 downstream cells for INTRODUCE
2115 circuits. This feature is only enabled when also supported by the
2116 circuit's middle node. (Clients may specify fixed middle nodes
2117 with the MiddleNodes option, and may force-disable this feature
2118 with the CircuitPadding option.) Closes ticket 28634.
2120 o Major features (code organization):
2121 - Tor now includes a generic publish-subscribe message-passing
2122 subsystem that we can use to organize intermodule dependencies. We
2123 hope to use this to reduce dependencies between modules that don't
2124 need to be related, and to generally simplify our codebase. Closes
2127 o Major features (controller protocol):
2128 - Controller commands are now parsed using a generalized parsing
2129 subsystem. Previously, each controller command was responsible for
2130 parsing its own input, which led to strange inconsistencies.
2131 Closes ticket 30091.
2133 o Major features (flow control):
2134 - Implement authenticated SENDMEs as detailed in proposal 289. A
2135 SENDME cell now includes the digest of the traffic that it
2136 acknowledges, so that once an end point receives the SENDME, it
2137 can confirm the other side's knowledge of the previous cells that
2138 were sent, and prevent certain types of denial-of-service attacks.
2139 This behavior is controlled by two new consensus parameters: see
2140 the proposal for more details. Fixes ticket 26288.
2142 o Major features (performance):
2143 - Our node selection algorithm now excludes nodes in linear time.
2144 Previously, the algorithm was quadratic, which could slow down
2145 heavily used onion services. Closes ticket 30307.
2147 o Major features (performance, RNG):
2148 - Tor now constructs a fast secure pseudorandom number generator for
2149 each thread, to use when performance is critical. This PRNG is
2150 based on AES-CTR, using a buffering construction similar to
2151 libottery and the (newer) OpenBSD arc4random() code. It
2152 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
2153 small outputs. Although we believe it to be cryptographically
2154 strong, we are only using it when necessary for performance.
2155 Implements tickets 29023 and 29536.
2157 o Major bugfixes (onion service v3):
2158 - Fix an unreachable bug in which an introduction point could try to
2159 send an INTRODUCE_ACK with a status code that Trunnel would refuse
2160 to encode, leading the relay to assert(). We've consolidated the
2161 ABI values into Trunnel now. Fixes bug 30454; bugfix
2163 - Clients can now handle unknown status codes from INTRODUCE_ACK
2164 cells. (The NACK behavior will stay the same.) This will allow us
2165 to extend status codes in the future without breaking the normal
2166 client behavior. Fixes another part of bug 30454; bugfix
2169 o Minor features (circuit padding):
2170 - We now use a fast PRNG when scheduling circuit padding. Part of
2172 - Allow the padding machine designer to pick the edges of their
2173 histogram instead of trying to compute them automatically using an
2174 exponential formula. Resolves some undefined behavior in the case
2175 of small histograms and allows greater flexibility on machine
2176 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
2177 - Allow circuit padding machines to hold a circuit open until they
2178 are done padding it. Closes ticket 28780.
2180 o Minor features (compile-time modules):
2181 - Add a "--list-modules" command to print a list of which compile-
2182 time modules are enabled. Closes ticket 30452.
2184 o Minor features (continuous integration):
2185 - Remove sudo configuration lines from .travis.yml as they are no
2186 longer needed with current Travis build environment. Resolves
2188 - In Travis, show stem's tor log after failure. Closes ticket 30234.
2190 o Minor features (controller):
2191 - Add onion service version 3 support to the HSFETCH command.
2192 Previously, only version 2 onion services were supported. Closes
2193 ticket 25417. Patch by Neel Chauhan.
2195 o Minor features (debugging):
2196 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
2197 logging of additional information during assert failure. Now we
2198 can use format strings to include information for trouble
2199 shooting. Resolves ticket 29662.
2201 o Minor features (defense in depth):
2202 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
2203 case a bug causes them to be used later. Closes ticket 30176.
2204 Patch from Tobias Stoeckmann.
2205 - Tor now uses a cryptographically strong PRNG even for decisions
2206 that we do not believe are security-sensitive. Previously, for
2207 performance reasons, we had used a trivially predictable linear
2208 congruential generator algorithm for certain load-balancing and
2209 statistical sampling decisions. Now we use our fast RNG in those
2210 cases. Closes ticket 29542.
2212 o Minor features (developer tools):
2213 - Tor's "practracker" test script now checks for files and functions
2214 that seem too long and complicated. Existing overlong functions
2215 and files are accepted for now, but should eventually be
2216 refactored. Closes ticket 29221.
2217 - Add some scripts used for git maintenance to scripts/git. Closes
2219 - Call practracker from pre-push and pre-commit git hooks to let
2220 developers know if they made any code style violations. Closes
2222 - Add a script to check that each header has a well-formed and
2223 unique guard macro. Closes ticket 29756.
2225 o Minor features (geoip):
2226 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
2227 Country database. Closes ticket 30522.
2229 o Minor features (HTTP tunnel):
2230 - Return an informative web page when the HTTPTunnelPort is used as
2231 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
2233 o Minor features (IPv6, v3 onion services):
2234 - Make v3 onion services put IPv6 addresses in service descriptors.
2235 Before this change, service descriptors only contained IPv4
2236 addresses. Implements 26992.
2238 o Minor features (modularity):
2239 - The "--disable-module-dirauth" compile-time option now disables
2240 even more dirauth-only code. Closes ticket 30345.
2242 o Minor features (performance):
2243 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
2244 1.1.1 and later), since they tend to be faster than tiny-keccak.
2245 Closes ticket 28837.
2247 o Minor features (testing):
2248 - Tor's unit test code now contains helper functions to replace the
2249 PRNG with a deterministic or reproducible version for testing.
2250 Previously, various tests implemented this in various ways.
2251 Implements ticket 29732.
2252 - We now have a script, cov-test-determinism.sh, to identify places
2253 where our unit test coverage has become nondeterministic. Closes
2255 - Check that representative subsets of values of `int` and `unsigned
2256 int` can be represented by `void *`. Resolves issue 29537.
2258 o Minor bugfixes (bridge authority):
2259 - Bridge authorities now set bridges as running or non-running when
2260 about to dump their status to a file. Previously, they set bridges
2261 as running in response to a GETINFO command, but those shouldn't
2262 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
2263 Patch by Neel Chauhan.
2265 o Minor bugfixes (channel padding statistics):
2266 - Channel padding write totals and padding-enabled totals are now
2267 counted properly in relay extrainfo descriptors. Fixes bug 29231;
2268 bugfix on 0.3.1.1-alpha.
2270 o Minor bugfixes (circuit padding):
2271 - Add a "CircuitPadding" torrc option to disable circuit padding.
2272 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
2273 - Allow circuit padding machines to specify that they do not
2274 contribute much overhead, and provide consensus flags and torrc
2275 options to force clients to only use these low overhead machines.
2276 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
2277 - Provide a consensus parameter to fully disable circuit padding, to
2278 be used in emergency network overload situations. Fixes bug 30173;
2279 bugfix on 0.4.0.1-alpha.
2280 - The circuit padding subsystem will no longer schedule padding if
2281 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
2282 - Inspect a circuit-level cell queue before sending padding, to
2283 avoid sending padding while too much data is already queued. Fixes
2284 bug 29204; bugfix on 0.4.0.1-alpha.
2285 - Avoid calling monotime_absolute_usec() in circuit padding machines
2286 that do not use token removal or circuit RTT estimation. Fixes bug
2287 29085; bugfix on 0.4.0.1-alpha.
2289 o Minor bugfixes (compilation, unusual configurations):
2290 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
2291 due to missing declarations of abort(), and prevent other such
2292 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
2294 o Minor bugfixes (controller protocol):
2295 - Teach the controller parser to distinguish an object preceded by
2296 an argument list from one without. Previously, it couldn't
2297 distinguish an argument list from the first line of a multiline
2298 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
2300 o Minor bugfixes (directory authority, ipv6):
2301 - Directory authorities with IPv6 support now always mark themselves
2302 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
2303 Patch by Neel Chauhan.
2305 o Minor bugfixes (documentation):
2306 - Improve the documentation for using MapAddress with ".exit". Fixes
2307 bug 30109; bugfix on 0.1.0.1-rc.
2308 - Improve the monotonic time module and function documentation to
2309 explain what "monotonic" actually means, and document some results
2310 that have surprised people. Fixes bug 29640; bugfix
2312 - Use proper formatting when providing an example on quoting options
2313 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
2315 o Minor bugfixes (logging):
2316 - Do not log a warning when running with an OpenSSL version other
2317 than the one Tor was compiled with, if the two versions should be
2318 compatible. Previously, we would warn whenever the version was
2319 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
2320 - Warn operators when the MyFamily option is set but ContactInfo is
2321 missing, as the latter should be set too. Fixes bug 25110; bugfix
2324 o Minor bugfixes (memory leak):
2325 - Avoid a minor memory leak that could occur on relays when failing
2326 to create a "keys" directory. Fixes bug 30148; bugfix
2329 o Minor bugfixes (onion services):
2330 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
2331 implemenation) when failing to load an onion service client
2332 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
2333 - When refusing to launch a controller's HSFETCH request because of
2334 rate-limiting, respond to the controller with a new response,
2335 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
2336 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
2338 - When relaunching a circuit to a rendezvous service, mark the
2339 circuit as needing high-uptime routers as appropriate. Fixes bug
2340 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
2341 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
2342 (IPv6 support for v3 onion services is still incomplete: see
2343 ticket 23493 for details.) Fixes bug 23588; bugfix on
2344 0.3.2.1-alpha. Patch by Neel Chauhan.
2346 o Minor bugfixes (onion services, performance):
2347 - When building circuits to onion services, call tor_addr_parse()
2348 less often. Previously, we called tor_addr_parse() in
2349 circuit_is_acceptable() even if its output wasn't used. This
2350 change should improve performance when building circuits. Fixes
2351 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
2353 o Minor bugfixes (performance):
2354 - When checking whether a node is a bridge, use a fast check to make
2355 sure that its identity is set. Previously, we used a constant-time
2356 check, which is not necessary in this case. Fixes bug 30308;
2357 bugfix on 0.3.5.1-alpha.
2359 o Minor bugfixes (pluggable transports):
2360 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
2361 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
2363 o Minor bugfixes (probability distributions):
2364 - Refactor and improve parts of the probability distribution code
2365 that made Coverity complain. Fixes bug 29805; bugfix
2368 o Minor bugfixes (python):
2369 - Stop assuming that /usr/bin/python3 exists. For scripts that work
2370 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
2371 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
2373 o Minor bugfixes (relay):
2374 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
2375 is auto, act as if ExitRelay is 1. Previously, we would ignore
2376 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
2377 0.3.5.1-alpha. Patch by Neel Chauhan.
2379 o Minor bugfixes (stats):
2380 - When ExtraInfoStatistics is 0, stop including bandwidth usage
2381 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
2382 bridge statistics by country in extra-info documents. Fixes bug
2383 29018; bugfix on 0.2.4.1-alpha.
2385 o Minor bugfixes (testing):
2386 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
2387 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
2388 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
2389 - Fix some incorrect code in the v3 onion service unit tests. Fixes
2390 bug 29243; bugfix on 0.3.2.1-alpha.
2391 - In the "routerkeys/*" tests, check the return values of mkdir()
2392 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
2393 Found by Coverity as CID 1444254.
2394 - Split test_utils_general() into several smaller test functions.
2395 This makes it easier to perform resource deallocation on assert
2396 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
2397 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
2399 o Minor bugfixes (tor-resolve):
2400 - Fix a memory leak in tor-resolve that could happen if Tor gave it
2401 a malformed SOCKS response. (Memory leaks in tor-resolve don't
2402 actually matter, but it's good to fix them anyway.) Fixes bug
2403 30151; bugfix on 0.4.0.1-alpha.
2405 o Code simplification and refactoring:
2406 - Abstract out the low-level formatting of replies on the control
2407 port. Implements ticket 30007.
2408 - Add several assertions in an attempt to fix some Coverity
2409 warnings. Closes ticket 30149.
2410 - Introduce a connection_dir_buf_add() helper function that checks
2411 for compress_state of dir_connection_t and automatically writes a
2412 string to directory connection with or without compression.
2413 Resolves issue 28816.
2414 - Make the base32_decode() API return the number of bytes written,
2415 for consistency with base64_decode(). Closes ticket 28913.
2416 - Move most relay-only periodic events out of mainloop.c into the
2417 relay subsystem. Closes ticket 30414.
2418 - Refactor and encapsulate parts of the codebase that manipulate
2419 crypt_path_t objects. Resolves issue 30236.
2420 - Refactor several places in our code that Coverity incorrectly
2421 believed might have memory leaks. Closes ticket 30147.
2422 - Remove redundant return values in crypto_format, and the
2423 associated return value checks elsewhere in the code. Make the
2424 implementations in crypto_format consistent, and remove redundant
2425 code. Resolves ticket 29660.
2426 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
2427 it is not a constant-time function. Closes ticket 30309.
2428 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
2429 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
2430 bugfix on 0.3.2.1-alpha.
2431 - Simplify v3 onion service link specifier handling code. Fixes bug
2432 23576; bugfix on 0.3.2.1-alpha.
2433 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
2434 code. Resolves ticket 29108.
2435 - Split control.c into several submodules, in preparation for
2436 distributing its current responsibilities throughout the codebase.
2437 Closes ticket 29894.
2438 - Start to move responsibility for knowing about periodic events to
2439 the appropriate subsystems, so that the mainloop doesn't need to
2440 know all the periodic events in the rest of the codebase.
2441 Implements tickets 30293 and 30294.
2444 - Document how to find git commits and tags for bug fixes in
2445 CodingStandards.md. Update some file documentation. Closes
2449 - Remove the linux-tor-prio.sh script from contrib/operator-tools
2450 directory. Resolves issue 29434.
2451 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
2452 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
2455 o Code simplification and refactoring (shell scripts):
2456 - Clean up many of our shell scripts to fix shellcheck warnings.
2457 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
2458 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
2459 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
2460 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
2461 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
2462 nagios-check-tor-authority-cert (ticket 29071),
2463 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
2464 (ticket 29060), test_key_expiration.sh (ticket 30002),
2465 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
2468 o Testing (chutney):
2469 - In "make test-network-all", test IPv6-only v3 single onion
2470 services, using the chutney network single-onion-v23-ipv6-md.
2471 Closes ticket 27251.
2474 Changes in version 0.4.0.5 - 2019-05-02
2475 This is the first stable release in the 0.4.0.x series. It contains
2476 improvements for power management and bootstrap reporting, as well as
2477 preliminary backend support for circuit padding to prevent some kinds
2478 of traffic analysis. It also continues our work in refactoring Tor for
2479 long-term maintainability.
2481 Per our support policy, we will support the 0.4.0.x series for nine
2482 months, or until three months after the release of a stable 0.4.1.x:
2483 whichever is longer. If you need longer-term support, please stick
2484 with 0.3.5.x, which will we plan to support until Feb 2022.
2486 Below are the changes since 0.4.0.4-rc. For a complete list of changes
2487 since 0.3.5.7, see the ReleaseNotes file.
2489 o Minor features (continuous integration):
2490 - In Travis, tell timelimit to use stem's backtrace signals, and
2491 launch python directly from timelimit, so python receives the
2492 signals from timelimit, rather than make. Closes ticket 30117.
2494 o Minor features (diagnostic):
2495 - Add more diagnostic log messages in an attempt to solve the issue
2496 of NUL bytes appearing in a microdescriptor cache. Related to
2499 o Minor features (testing):
2500 - Use the approx_time() function when setting the "Expires" header
2501 in directory replies, to make them more testable. Needed for
2504 o Minor bugfixes (rust):
2505 - Abort on panic in all build profiles, instead of potentially
2506 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
2508 o Minor bugfixes (shellcheck):
2509 - Look for scripts in their correct locations during "make
2510 shellcheck". Previously we had looked in the wrong place during
2511 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
2513 o Minor bugfixes (testing):
2514 - Check the time in the "Expires" header using approx_time(). Fixes
2515 bug 30001; bugfix on 0.4.0.4-rc.
2517 o Minor bugfixes (UI):
2518 - Lower log level of unlink() errors during bootstrap. Fixes bug
2519 29930; bugfix on 0.4.0.1-alpha.
2522 Changes in version 0.4.0.4-rc - 2019-04-11
2523 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
2524 several bugs from earlier versions, including some that had affected
2525 stability, and one that prevented relays from working with NSS.
2527 o Major bugfixes (NSS, relay):
2528 - When running with NSS, disable TLS 1.2 ciphersuites that use
2529 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
2530 these ciphersuites don't work -- which caused relays to fail to
2531 handshake with one another when these ciphersuites were enabled.
2532 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
2534 o Minor features (bandwidth authority):
2535 - Make bandwidth authorities ignore relays that are reported in the
2536 bandwidth file with the flag "vote=0". This change allows us to
2537 report unmeasured relays for diagnostic reasons without including
2538 their bandwidth in the bandwidth authorities' vote. Closes
2540 - When a directory authority is using a bandwidth file to obtain the
2541 bandwidth values that will be included in the next vote, serve
2542 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
2545 o Minor features (circuit padding):
2546 - Stop warning about undefined behavior in the probability
2547 distribution tests. Float division by zero may technically be
2548 undefined behavior in C, but it's well defined in IEEE 754.
2549 Partial backport of 29298. Closes ticket 29527; bugfix
2552 o Minor features (continuous integration):
2553 - On Travis Rust builds, cleanup Rust registry and refrain from
2554 caching the "target/" directory to speed up builds. Resolves
2557 o Minor features (dormant mode):
2558 - Add a DormantCanceledByStartup option to tell Tor that it should
2559 treat a startup event as cancelling any previous dormant state.
2560 Integrators should use this option with caution: it should only be
2561 used if Tor is being started because of something that the user
2562 did, and not if Tor is being automatically started in the
2563 background. Closes ticket 29357.
2565 o Minor features (geoip):
2566 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
2567 Country database. Closes ticket 29992.
2569 o Minor features (NSS, diagnostic):
2570 - Try to log an error from NSS (if there is any) and a more useful
2571 description of our situation if we are using NSS and a call to
2572 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
2574 o Minor bugfixes (security):
2575 - Fix a potential double free bug when reading huge bandwidth files.
2576 The issue is not exploitable in the current Tor network because
2577 the vulnerable code is only reached when directory authorities
2578 read bandwidth files, but bandwidth files come from a trusted
2579 source (usually the authorities themselves). Furthermore, the
2580 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
2581 which are not used by any of the current authorities. Fixes bug
2582 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
2584 - Verify in more places that we are not about to create a buffer
2585 with more than INT_MAX bytes, to avoid possible OOB access in the
2586 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
2587 fixed by Tobias Stoeckmann.
2589 o Minor bugfix (continuous integration):
2590 - Reset coverage state on disk after Travis CI has finished. This
2591 should prevent future coverage merge errors from causing the test
2592 suite for the "process" subsystem to fail. The process subsystem
2593 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
2595 - Terminate test-stem if it takes more than 9.5 minutes to run.
2596 (Travis terminates the job after 10 minutes of no output.)
2597 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
2599 o Minor bugfixes (bootstrap reporting):
2600 - During bootstrap reporting, correctly distinguish pluggable
2601 transports from plain proxies. Fixes bug 28925; bugfix
2604 o Minor bugfixes (C correctness):
2605 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
2606 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
2609 o Minor bugfixes (circuitpadding testing):
2610 - Minor tweaks to avoid rare test failures related to timers and
2611 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
2613 o Minor bugfixes (directory authorities):
2614 - Actually include the bandwidth-file-digest line in directory
2615 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
2617 o Minor bugfixes (logging):
2618 - On Windows, when errors cause us to reload a consensus from disk,
2619 tell the user that we are retrying at log level "notice".
2620 Previously we only logged this information at "info", which was
2621 confusing because the errors themselves were logged at "warning".
2622 Improves previous fix for 28614. Fixes bug 30004; bugfix
2625 o Minor bugfixes (pluggable transports):
2626 - Restore old behavior when it comes to discovering the path of a
2627 given Pluggable Transport executable file. A change in
2628 0.4.0.1-alpha had broken this behavior on paths containing a
2629 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
2631 o Minor bugfixes (testing):
2632 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
2633 recent test-network.sh to use new chutney features in CI. Fixes
2634 bug 29703; bugfix on 0.2.9.1-alpha.
2635 - Fix a test failure on Windows caused by an unexpected "BUG"
2636 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
2639 o Minor bugfixes (TLS protocol):
2640 - When classifying a client's selection of TLS ciphers, if the
2641 client ciphers are not yet available, do not cache the result.
2642 Previously, we had cached the unavailability of the cipher list
2643 and never looked again, which in turn led us to assume that the
2644 client only supported the ancient V1 link protocol. This, in turn,
2645 was causing Stem integration tests to stall in some cases. Fixes
2646 bug 30021; bugfix on 0.2.4.8-alpha.
2648 o Code simplification and refactoring:
2649 - Introduce a connection_dir_buf_add() helper function that detects
2650 whether compression is in use, and adds a string accordingly.
2651 Resolves issue 28816.
2652 - Refactor handle_get_next_bandwidth() to use
2653 connection_dir_buf_add(). Implements ticket 29897.
2656 - Clarify that Tor performs stream isolation among *Port listeners
2657 by default. Resolves issue 29121.
2660 Changes in version 0.4.0.3-alpha - 2019-03-22
2661 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
2662 bugs from earlier versions.
2664 o Minor features (address selection):
2665 - Treat the subnet 100.64.0.0/10 as public for some purposes;
2666 private for others. This subnet is the RFC 6598 (Carrier Grade
2667 NAT) IP range, and is deployed by many ISPs as an alternative to
2668 RFC 1918 that does not break existing internal networks. Tor now
2669 blocks SOCKS and control ports on these addresses and warns users
2670 if client ports or ExtORPorts are listening on a RFC 6598 address.
2671 Closes ticket 28525. Patch by Neel Chauhan.
2673 o Minor features (geoip):
2674 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
2675 Country database. Closes ticket 29666.
2677 o Minor bugfixes (circuitpadding):
2678 - Inspect the circuit-level cell queue before sending padding, to
2679 avoid sending padding when too much data is queued. Fixes bug
2680 29204; bugfix on 0.4.0.1-alpha.
2682 o Minor bugfixes (logging):
2683 - Correct a misleading error message when IPv4Only or IPv6Only is
2684 used but the resolved address can not be interpreted as an address
2685 of the specified IP version. Fixes bug 13221; bugfix on
2686 0.2.3.9-alpha. Patch from Kris Katterjohn.
2687 - Log the correct port number for listening sockets when "auto" is
2688 used to let Tor pick the port number. Previously, port 0 was
2689 logged instead of the actual port number. Fixes bug 29144; bugfix
2690 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
2691 - Stop logging a BUG() warning when Tor is waiting for exit
2692 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
2694 o Minor bugfixes (memory management):
2695 - Refactor the shared random state's memory management so that it
2696 actually takes ownership of the shared random value pointers.
2697 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
2699 o Minor bugfixes (memory management, testing):
2700 - Stop leaking parts of the shared random state in the shared-random
2701 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
2703 o Minor bugfixes (pluggable transports):
2704 - Fix an assertion failure crash bug when a pluggable transport is
2705 terminated during the bootstrap phase. Fixes bug 29562; bugfix
2708 o Minor bugfixes (Rust, protover):
2709 - Add a missing "Padding" value to the Rust implementation of
2710 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
2712 o Minor bugfixes (single onion services):
2713 - Allow connections to single onion services to remain idle without
2714 being disconnected. Previously, relays acting as rendezvous points
2715 for single onion services were mistakenly closing idle rendezvous
2716 circuits after 60 seconds, thinking that they were unused
2717 directory-fetching circuits that had served their purpose. Fixes
2718 bug 29665; bugfix on 0.2.1.26.
2720 o Minor bugfixes (stats):
2721 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
2722 relay and bridge extra-info documents. Fixes bug 29017; bugfix
2725 o Minor bugfixes (testing):
2726 - Downgrade some LOG_ERR messages in the address/* tests to
2727 warnings. The LOG_ERR messages were occurring when we had no
2728 configured network. We were failing the unit tests, because we
2729 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
2730 29530; bugfix on 0.3.5.8.
2731 - Fix our gcov wrapper script to look for object files at the
2732 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
2733 - Decrease the false positive rate of stochastic probability
2734 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
2736 o Minor bugfixes (Windows, CI):
2737 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
2738 Windows Server 2012 R2 job. The remaining 2 jobs still provide
2739 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
2740 fast_finish, so failed jobs terminate the build immediately. Fixes
2741 bug 29601; bugfix on 0.3.5.4-alpha.
2744 Changes in version 0.3.5.8 - 2019-02-21
2745 Tor 0.3.5.8 backports several fixes from later releases, including fixes
2746 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
2749 It also includes a fix for a medium-severity security bug affecting Tor
2750 0.3.2.1-alpha and later. All Tor instances running an affected release
2751 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
2753 o Major bugfixes (cell scheduler, KIST, security):
2754 - Make KIST consider the outbuf length when computing what it can
2755 put in the outbuf. Previously, KIST acted as though the outbuf
2756 were empty, which could lead to the outbuf becoming too full. It
2757 is possible that an attacker could exploit this bug to cause a Tor
2758 client or relay to run out of memory and crash. Fixes bug 29168;
2759 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
2760 TROVE-2019-001 and CVE-2019-8955.
2762 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
2763 - Gracefully handle empty username/password fields in SOCKS5
2764 username/password auth message and allow SOCKS5 handshake to
2765 continue. Previously, we had rejected these handshakes, breaking
2766 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
2768 o Minor features (compilation, backport from 0.4.0.2-alpha):
2769 - Compile correctly when OpenSSL is built with engine support
2770 disabled, or with deprecated APIs disabled. Closes ticket 29026.
2771 Patches from "Mangix".
2773 o Minor features (geoip):
2774 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
2775 Country database. Closes ticket 29478.
2777 o Minor features (testing, backport from 0.4.0.2-alpha):
2778 - Treat all unexpected ERR and BUG messages as test failures. Closes
2781 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
2782 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
2783 connection waiting for a descriptor that we actually have in the
2784 cache. It turns out that this can actually happen, though it is
2785 rare. Now, tor will recover and retry the descriptor. Fixes bug
2786 28669; bugfix on 0.3.2.4-alpha.
2788 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
2789 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
2790 IPv6 socket was bound using an address family of AF_INET instead
2791 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
2794 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
2795 - Update Cargo.lock file to match the version made by the latest
2796 version of Rust, so that "make distcheck" will pass again. Fixes
2797 bug 29244; bugfix on 0.3.3.4-alpha.
2799 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
2800 - Select guards even if the consensus has expired, as long as the
2801 consensus is still reasonably live. Fixes bug 24661; bugfix
2804 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
2805 - Compile correctly on OpenBSD; previously, we were missing some
2806 headers required in order to detect it properly. Fixes bug 28938;
2807 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
2809 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
2810 - Describe the contents of the v3 onion service client authorization
2811 files correctly: They hold public keys, not private keys. Fixes
2812 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
2814 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
2815 - Rework rep_hist_log_link_protocol_counts() to iterate through all
2816 link protocol versions when logging incoming/outgoing connection
2817 counts. Tor no longer skips version 5, and we won't have to
2818 remember to update this function when new link protocol version is
2819 developed. Fixes bug 28920; bugfix on 0.2.6.10.
2821 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
2822 - Log more information at "warning" level when unable to read a
2823 private key; log more information at "info" level when unable to
2824 read a public key. We had warnings here before, but they were lost
2825 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
2827 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
2828 - The amount of total available physical memory is now determined
2829 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
2830 when it is defined and a 64-bit variant is not available. Fixes
2831 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
2833 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
2834 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
2835 than one private key for a hidden service. Fixes bug 29040; bugfix
2837 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
2838 "debug" level. Tor used to log it as a warning, which caused very
2839 long log lines to appear for some users. Fixes bug 29135; bugfix
2841 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
2842 as a warning. Instead, log it as a protocol warning, because there
2843 is nothing that relay operators can do to fix it. Fixes bug 29029;
2844 bugfix on 0.2.5.7-rc.
2846 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
2847 - Mark outdated dirservers when Tor only has a reasonably live
2848 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
2850 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
2851 - Detect and suppress "bug" warnings from the util/time test on
2852 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
2853 - Do not log an error-level message if we fail to find an IPv6
2854 network interface from the unit tests. Fixes bug 29160; bugfix
2857 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
2858 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
2859 Some users took this phrasing to mean that the mentioned guard was
2860 under their control or responsibility, which it is not. Fixes bug
2861 28895; bugfix on Tor 0.3.0.1-alpha.
2864 Changes in version 0.3.4.11 - 2019-02-21
2865 Tor 0.3.4.11 is the third stable release in its series. It includes
2866 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
2867 later. All Tor instances running an affected release should upgrade to
2868 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
2870 o Major bugfixes (cell scheduler, KIST, security):
2871 - Make KIST consider the outbuf length when computing what it can
2872 put in the outbuf. Previously, KIST acted as though the outbuf
2873 were empty, which could lead to the outbuf becoming too full. It
2874 is possible that an attacker could exploit this bug to cause a Tor
2875 client or relay to run out of memory and crash. Fixes bug 29168;
2876 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
2877 TROVE-2019-001 and CVE-2019-8955.
2879 o Minor features (geoip):
2880 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
2881 Country database. Closes ticket 29478.
2883 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
2884 - Update Cargo.lock file to match the version made by the latest
2885 version of Rust, so that "make distcheck" will pass again. Fixes
2886 bug 29244; bugfix on 0.3.3.4-alpha.
2888 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
2889 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
2890 as a warning. Instead, log it as a protocol warning, because there
2891 is nothing that relay operators can do to fix it. Fixes bug 29029;
2892 bugfix on 0.2.5.7-rc.
2895 Changes in version 0.3.3.12 - 2019-02-21
2896 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
2897 0.3.2.1-alpha and later. All Tor instances running an affected release
2898 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
2900 This release marks the end of support for the Tor 0.3.3.x series. We
2901 recommend that users switch to either the Tor 0.3.4 series (supported
2902 until at least 10 June 2019), or the Tor 0.3.5 series, which will
2903 receive long-term support until at least 1 Feb 2022.
2905 o Major bugfixes (cell scheduler, KIST, security):
2906 - Make KIST consider the outbuf length when computing what it can
2907 put in the outbuf. Previously, KIST acted as though the outbuf
2908 were empty, which could lead to the outbuf becoming too full. It
2909 is possible that an attacker could exploit this bug to cause a Tor
2910 client or relay to run out of memory and crash. Fixes bug 29168;
2911 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
2912 TROVE-2019-001 and CVE-2019-8955.
2914 o Minor features (geoip):
2915 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
2916 Country database. Closes ticket 29478.
2918 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
2919 - Update Cargo.lock file to match the version made by the latest
2920 version of Rust, so that "make distcheck" will pass again. Fixes
2921 bug 29244; bugfix on 0.3.3.4-alpha.
2923 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
2924 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
2925 as a warning. Instead, log it as a protocol warning, because there
2926 is nothing that relay operators can do to fix it. Fixes bug 29029;
2927 bugfix on 0.2.5.7-rc.
2930 Changes in version 0.4.0.2-alpha - 2019-02-21
2931 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
2932 bugs from earlier versions, including several that had broken
2933 backward compatibility.
2935 It also includes a fix for a medium-severity security bug affecting Tor
2936 0.3.2.1-alpha and later. All Tor instances running an affected release
2937 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
2939 o Major bugfixes (cell scheduler, KIST, security):
2940 - Make KIST consider the outbuf length when computing what it can
2941 put in the outbuf. Previously, KIST acted as though the outbuf
2942 were empty, which could lead to the outbuf becoming too full. It
2943 is possible that an attacker could exploit this bug to cause a Tor
2944 client or relay to run out of memory and crash. Fixes bug 29168;
2945 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
2946 TROVE-2019-001 and CVE-2019-8955.
2948 o Major bugfixes (networking):
2949 - Gracefully handle empty username/password fields in SOCKS5
2950 username/password auth messsage and allow SOCKS5 handshake to
2951 continue. Previously, we had rejected these handshakes, breaking
2952 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
2954 o Major bugfixes (windows, startup):
2955 - When reading a consensus file from disk, detect whether it was
2956 written in text mode, and re-read it in text mode if so. Always
2957 write consensus files in binary mode so that we can map them into
2958 memory later. Previously, we had written in text mode, which
2959 confused us when we tried to map the file on windows. Fixes bug
2960 28614; bugfix on 0.4.0.1-alpha.
2962 o Minor features (compilation):
2963 - Compile correctly when OpenSSL is built with engine support
2964 disabled, or with deprecated APIs disabled. Closes ticket 29026.
2965 Patches from "Mangix".
2967 o Minor features (developer tooling):
2968 - Check that bugfix versions in changes files look like Tor versions
2969 from the versions spec. Warn when bugfixes claim to be on a future
2970 release. Closes ticket 27761.
2971 - Provide a git pre-commit hook that disallows committing if we have
2972 any failures in our code and changelog formatting checks. It is
2973 now available in scripts/maint/pre-commit.git-hook. Implements
2976 o Minor features (directory authority):
2977 - When a directory authority is using a bandwidth file to obtain
2978 bandwidth values, include the digest of that file in the vote.
2979 Closes ticket 26698.
2981 o Minor features (geoip):
2982 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
2983 Country database. Closes ticket 29478.
2985 o Minor features (testing):
2986 - Treat all unexpected ERR and BUG messages as test failures. Closes
2989 o Minor bugfixes (build, compatibility, rust):
2990 - Update Cargo.lock file to match the version made by the latest
2991 version of Rust, so that "make distcheck" will pass again. Fixes
2992 bug 29244; bugfix on 0.3.3.4-alpha.
2994 o Minor bugfixes (compilation):
2995 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
2996 29169; bugfix on 0.4.0.1-alpha.
2997 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
2998 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
3000 o Minor bugfixes (documentation):
3001 - Describe the contents of the v3 onion service client authorization
3002 files correctly: They hold public keys, not private keys. Fixes
3003 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
3005 o Minor bugfixes (linux seccomp sandbox):
3006 - Fix startup crash when experimental sandbox support is enabled.
3007 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
3009 o Minor bugfixes (logging):
3010 - Avoid logging that we are relaxing a circuit timeout when that
3011 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
3012 - Log more information at "warning" level when unable to read a
3013 private key; log more information at "info" level when unable to
3014 read a public key. We had warnings here before, but they were lost
3015 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
3017 o Minor bugfixes (misc):
3018 - The amount of total available physical memory is now determined
3019 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
3020 when it is defined and a 64-bit variant is not available. Fixes
3021 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
3023 o Minor bugfixes (onion services):
3024 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
3025 than one private key for a hidden service. Fixes bug 29040; bugfix
3027 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
3028 "debug" level. Tor used to log it as a warning, which caused very
3029 long log lines to appear for some users. Fixes bug 29135; bugfix
3031 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3032 as a warning. Instead, log it as a protocol warning, because there
3033 is nothing that relay operators can do to fix it. Fixes bug 29029;
3034 bugfix on 0.2.5.7-rc.
3036 o Minor bugfixes (scheduler):
3037 - When re-adding channels to the pending list, check the correct
3038 channel's sched_heap_idx. This issue has had no effect in mainline
3039 Tor, but could have led to bugs down the road in improved versions
3040 of our circuit scheduling code. Fixes bug 29508; bugfix
3043 o Minor bugfixes (tests):
3044 - Fix intermittent failures on an adaptive padding test. Fixes one
3045 case of bug 29122; bugfix on 0.4.0.1-alpha.
3046 - Disable an unstable circuit-padding test that was failing
3047 intermittently because of an ill-defined small histogram. Such
3048 histograms will be allowed again after 29298 is implemented. Fixes
3049 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
3050 - Detect and suppress "bug" warnings from the util/time test on
3051 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
3052 - Do not log an error-level message if we fail to find an IPv6
3053 network interface from the unit tests. Fixes bug 29160; bugfix
3057 - In the manpage entry describing MapAddress torrc setting, use
3058 example IP addresses from ranges specified for use in documentation
3059 by RFC 5737. Resolves issue 28623.
3062 - Remove the old check-tor script. Resolves issue 29072.
3065 Changes in version 0.4.0.1-alpha - 2019-01-18
3066 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
3067 introduces improved features for power and bandwidth conservation,
3068 more accurate reporting of bootstrap progress for user interfaces, and
3069 an experimental backend for an exciting new adaptive padding feature.
3070 There is also the usual assortment of bugfixes and minor features, all
3073 o Major features (battery management, client, dormant mode):
3074 - When Tor is running as a client, and it is unused for a long time,
3075 it can now enter a "dormant" state. When Tor is dormant, it avoids
3076 network and CPU activity until it is reawoken either by a user
3077 request or by a controller command. For more information, see the
3078 configuration options starting with "Dormant". Implements tickets
3080 - The client's memory of whether it is "dormant", and how long it
3081 has spent idle, persists across invocations. Implements
3083 - There is a DormantOnFirstStartup option that integrators can use
3084 if they expect that in many cases, Tor will be installed but
3087 o Major features (bootstrap reporting):
3088 - When reporting bootstrap progress, report the first connection
3089 uniformly, regardless of whether it's a connection for building
3090 application circuits. This allows finer-grained reporting of early
3091 progress than previously possible, with the improvements of ticket
3092 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
3093 - When reporting bootstrap progress, treat connecting to a proxy or
3094 pluggable transport as separate from having successfully used that
3095 proxy or pluggable transport to connect to a relay. Closes tickets
3098 o Major features (circuit padding):
3099 - Implement preliminary support for the circuit padding portion of
3100 Proposal 254. The implementation supports Adaptive Padding (aka
3101 WTF-PAD) state machines for use between experimental clients and
3102 relays. Support is also provided for APE-style state machines that
3103 use probability distributions instead of histograms to specify
3104 inter-packet delay. At the moment, Tor does not provide any
3105 padding state machines that are used in normal operation: for now,
3106 this feature exists solely for experimentation. Closes
3109 o Major features (refactoring):
3110 - Tor now uses an explicit list of its own subsystems when
3111 initializing and shutting down. Previously, these systems were
3112 managed implicitly in various places throughout the codebase.
3113 (There may still be some subsystems using the old system.) Closes
3116 o Minor features (bootstrap reporting):
3117 - When reporting bootstrap progress, stop distinguishing between
3118 situations where only internal paths are available and situations
3119 where external paths are available. Previously, Tor would often
3120 erroneously report that it had only internal paths. Closes
3123 o Minor features (continuous integration):
3124 - Log Python version during each Travis CI job. Resolves
3127 o Minor features (controller):
3128 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
3129 Implements ticket 28843.
3131 o Minor features (developer tooling):
3132 - Provide a git hook script to prevent "fixup!" and "squash!"
3133 commits from ending up in the master branch, as scripts/main/pre-
3134 push.git-hook. Closes ticket 27993.
3136 o Minor features (directory authority):
3137 - Directory authorities support a new consensus algorithm, under
3138 which the family lines in microdescriptors are encoded in a
3139 canonical form. This change makes family lines more compressible
3140 in transit, and on the client. Closes ticket 28266; implements
3143 o Minor features (directory authority, relay):
3144 - Authorities now vote on a "StaleDesc" flag to indicate that a
3145 relay's descriptor is so old that the relay should upload again
3146 soon. Relays treat this flag as a signal to upload a new
3147 descriptor. This flag will eventually let us remove the
3148 'published' date from routerstatus entries, and make our consensus
3149 diffs much smaller. Closes ticket 26770; implements proposal 293.
3151 o Minor features (fallback directory mirrors):
3152 - Update the fallback whitelist based on operator opt-ins and opt-
3153 outs. Closes ticket 24805, patch by Phoul.
3155 o Minor features (FreeBSD):
3156 - On FreeBSD-based systems, warn relay operators if the
3157 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
3158 Closes ticket 28518.
3160 o Minor features (HTTP standards compliance):
3161 - Stop sending the header "Content-type: application/octet-stream"
3162 along with transparently compressed documents: this confused
3163 browsers. Closes ticket 28100.
3165 o Minor features (IPv6):
3166 - We add an option ClientAutoIPv6ORPort, to make clients randomly
3167 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
3168 every time a node is loaded from a new consensus or bridge config.
3169 We expect that this option will enable clients to bootstrap more
3170 quickly without having to determine whether they support IPv4,
3171 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
3172 - When using addrs_in_same_network_family(), avoid choosing circuit
3173 paths that pass through the same IPv6 subnet more than once.
3174 Previously, we only checked IPv4 subnets. Closes ticket 24393.
3175 Patch by Neel Chauhan.
3177 o Minor features (log messages):
3178 - Improve log message in v3 onion services that could print out
3179 negative revision counters. Closes ticket 27707. Patch
3182 o Minor features (memory usage):
3183 - Save memory by storing microdescriptor family lists with a more
3184 compact representation. Closes ticket 27359.
3185 - Tor clients now use mmap() to read consensus files from disk, so
3186 that they no longer need keep the full text of a consensus in
3187 memory when parsing it or applying a diff. Closes ticket 27244.
3189 o Minor features (parsing):
3190 - Directory authorities now validate that router descriptors and
3191 ExtraInfo documents are in a valid subset of UTF-8, and reject
3192 them if they are not. Closes ticket 27367.
3194 o Minor features (performance):
3195 - Cache the results of summarize_protocol_flags(), so that we don't
3196 have to parse the same protocol-versions string over and over.
3197 This should save us a huge number of malloc calls on startup, and
3198 may reduce memory fragmentation with some allocators. Closes
3200 - Remove a needless memset() call from get_token_arguments, thereby
3201 speeding up the tokenization of directory objects by about 20%.
3202 Closes ticket 28852.
3203 - Replace parse_short_policy() with a faster implementation, to
3204 improve microdescriptor parsing time. Closes ticket 28853.
3205 - Speed up directory parsing a little by avoiding use of the non-
3206 inlined strcmp_len() function. Closes ticket 28856.
3207 - Speed up microdescriptor parsing by about 30%, to help improve
3208 startup time. Closes ticket 28839.
3210 o Minor features (pluggable transports):
3211 - Add support for emitting STATUS updates to Tor's control port from
3212 a pluggable transport process. Closes ticket 28846.
3213 - Add support for logging to Tor's logging subsystem from a
3214 pluggable transport process. Closes ticket 28180.
3216 o Minor features (process management):
3217 - Add a new process API for handling child processes. This new API
3218 allows Tor to have bi-directional communication with child
3219 processes on both Unix and Windows. Closes ticket 28179.
3220 - Use the subsystem manager to initialize and shut down the process
3221 module. Closes ticket 28847.
3223 o Minor features (relay):
3224 - When listing relay families, list them in canonical form including
3225 the relay's own identity, and try to give a more useful set of
3226 warnings. Part of ticket 28266 and proposal 298.
3228 o Minor features (required protocols):
3229 - Before exiting because of a missing required protocol, Tor will
3230 now check the publication time of the consensus, and not exit
3231 unless the consensus is newer than the Tor program's own release
3232 date. Previously, Tor would not check the consensus publication
3233 time, and so might exit because of a missing protocol that might
3234 no longer be required in a current consensus. Implements proposal
3235 297; closes ticket 27735.
3237 o Minor features (testing):
3238 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
3239 networks. Closes ticket 28840. Patch by Rob Jansen.
3241 o Minor bugfixes (client, clock skew):
3242 - Bootstrap successfully even when Tor's clock is behind the clocks
3243 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
3244 - Select guards even if the consensus has expired, as long as the
3245 consensus is still reasonably live. Fixes bug 24661; bugfix
3248 o Minor bugfixes (compilation):
3249 - Compile correctly on OpenBSD; previously, we were missing some
3250 headers required in order to detect it properly. Fixes bug 28938;
3251 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3253 o Minor bugfixes (directory clients):
3254 - Mark outdated dirservers when Tor only has a reasonably live
3255 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
3257 o Minor bugfixes (directory mirrors):
3258 - Even when a directory mirror's clock is behind the clocks on the
3259 authorities, we now allow the mirror to serve "future"
3260 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
3262 o Minor bugfixes (DNS):
3263 - Gracefully handle an empty or absent resolve.conf file by falling
3264 back to using "localhost" as a DNS server (and hoping it works).
3265 Previously, we would just stop running as an exit. Fixes bug
3266 21900; bugfix on 0.2.1.10-alpha.
3268 o Minor bugfixes (guards):
3269 - In count_acceptable_nodes(), the minimum number is now one bridge
3270 or guard node, and two non-guard nodes for a circuit. Previously,
3271 we had added up the sum of all nodes with a descriptor, but that
3272 could cause us to build failing circuits when we had either too
3273 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
3274 0.2.3.1-alpha. Patch by Neel Chauhan.
3276 o Minor bugfixes (IPv6):
3277 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
3278 IPv6 socket was bound using an address family of AF_INET instead
3279 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
3282 o Minor bugfixes (logging):
3283 - Rework rep_hist_log_link_protocol_counts() to iterate through all
3284 link protocol versions when logging incoming/outgoing connection
3285 counts. Tor no longer skips version 5, and we won't have to
3286 remember to update this function when new link protocol version is
3287 developed. Fixes bug 28920; bugfix on 0.2.6.10.
3289 o Minor bugfixes (networking):
3290 - Introduce additional checks into tor_addr_parse() to reject
3291 certain incorrect inputs that previously were not detected. Fixes
3292 bug 23082; bugfix on 0.2.0.10-alpha.
3294 o Minor bugfixes (onion service v3, client):
3295 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
3296 connection waiting for a descriptor that we actually have in the
3297 cache. It turns out that this can actually happen, though it is
3298 rare. Now, tor will recover and retry the descriptor. Fixes bug
3299 28669; bugfix on 0.3.2.4-alpha.
3301 o Minor bugfixes (periodic events):
3302 - Refrain from calling routerlist_remove_old_routers() from
3303 check_descriptor_callback(). Instead, create a new hourly periodic
3304 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
3306 o Minor bugfixes (pluggable transports):
3307 - Make sure that data is continously read from standard output and
3308 standard error pipes of a pluggable transport child-process, to
3309 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
3310 bugfix on 0.2.3.6-alpha.
3312 o Minor bugfixes (unit tests):
3313 - Instead of relying on hs_free_all() to clean up all onion service
3314 objects in test_build_descriptors(), we now deallocate them one by
3315 one. This lets Coverity know that we are not leaking memory there
3316 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
3318 o Minor bugfixes (usability):
3319 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
3320 Some users took this phrasing to mean that the mentioned guard was
3321 under their control or responsibility, which it is not. Fixes bug
3322 28895; bugfix on Tor 0.3.0.1-alpha.
3324 o Code simplification and refactoring:
3325 - Reimplement NETINFO cell parsing and generation to rely on
3326 trunnel-generated wire format handling code. Closes ticket 27325.
3327 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
3329 - Rework SOCKS wire format handling to rely on trunnel-generated
3330 parsing/generation code. Resolves ticket 27620.
3331 - Split out bootstrap progress reporting from control.c into a
3332 separate file. Part of ticket 27402.
3333 - The .may_include files that we use to describe our directory-by-
3334 directory dependency structure now describe a noncircular
3335 dependency graph over the directories that they cover. Our
3336 checkIncludes.py tool now enforces this noncircularity. Closes
3340 - Mention that you cannot add a new onion service if Tor is already
3341 running with Sandbox enabled. Closes ticket 28560.
3342 - Improve ControlPort documentation. Mention that it accepts
3343 address:port pairs, and can be used multiple times. Closes
3345 - Document the exact output of "tor --version". Closes ticket 28889.
3348 - Stop responding to the 'GETINFO status/version/num-concurring' and
3349 'GETINFO status/version/num-versioning' control port commands, as
3350 those were deprecated back in 0.2.0.30. Also stop listing them in
3351 output of 'GETINFO info/names'. Resolves ticket 28757.
3352 - The scripts used to generate and maintain the list of fallback
3353 directories have been extracted into a new "fallback-scripts"
3354 repository. Closes ticket 27914.
3357 - Run shellcheck for scripts in the in scripts/ directory. Closes
3359 - Add unit tests for tokenize_string() and get_next_token()
3360 functions. Resolves ticket 27625.
3362 o Code simplification and refactoring (onion service v3):
3363 - Consolidate the authorized client descriptor cookie computation
3364 code from client and service into one function. Closes
3367 o Code simplification and refactoring (shell scripts):
3368 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
3370 - Fix issues that shellcheck found in chutney-git-bisect.sh.
3371 Resolves ticket 28006.
3372 - Fix issues that shellcheck found in updateRustDependencies.sh.
3373 Resolves ticket 28012.
3374 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
3375 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
3376 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
3377 - Fix shellcheck warnings in scripts/test/coverage. Resolves
3381 Changes in version 0.3.3.11 - 2019-01-07
3382 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
3383 numerous fixes, including an important fix for anyone using OpenSSL
3384 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
3385 to this version, or to a later series.
3387 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
3388 We anticipate that this will be the last release of Tor 0.3.3, unless
3389 some major bug is before then. Some time between now and then, users
3390 should switch to either the Tor 0.3.4 series (supported until at least
3391 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
3392 support until at least 1 Feb 2022.
3394 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
3395 - Fix our usage of named groups when running as a TLS 1.3 client in
3396 OpenSSL 1.1.1. Previously, we only initialized EC groups when
3397 running as a relay, which caused clients to fail to negotiate TLS
3398 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
3401 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
3402 - Fix a use-after-free error that could be caused by passing Tor an
3403 impossible set of options that would fail during options_act().
3404 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
3406 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
3407 - Only run one online rust build in Travis, to reduce network
3408 errors. Skip offline rust builds on Travis for Linux gcc, because
3409 they're redundant. Implements ticket 27252.
3410 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
3411 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
3412 Linux with default settings, because all the non-default builds
3413 use gcc on Linux. Implements ticket 27252.
3415 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
3416 - Use the Travis Homebrew addon to install packages on macOS during
3417 Travis CI. The package list is the same, but the Homebrew addon
3418 does not do a `brew update` by default. Implements ticket 27738.
3420 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
3421 - Replace the 150 fallbacks originally introduced in Tor
3422 0.3.3.1-alpha in January 2018 (of which ~115 were still
3423 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
3424 removed) generated in December 2018. Closes ticket 24803.
3426 o Minor features (geoip):
3427 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
3428 Country database. Closes ticket 29012.
3430 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
3431 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
3432 key export function from handling long labels. When this bug is
3433 detected, Tor will disable TLS 1.3. We recommend upgrading to a
3434 version of OpenSSL without this bug when it becomes available.
3435 Closes ticket 28973.
3437 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
3438 - Update relay descriptor on bandwidth changes only when the uptime
3439 is smaller than 24h, in order to reduce the efficiency of guard
3440 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
3442 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
3443 - Avoid undefined behavior in an end-of-string check when parsing
3444 the BEGIN line in a directory object. Fixes bug 28202; bugfix
3447 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
3448 - Rewrite our assertion macros so that they no longer suppress the
3449 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
3451 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
3452 - Initialize a variable unconditionally in aes_new_cipher(), since
3453 some compilers cannot tell that we always initialize it before
3454 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
3456 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
3457 - Log additional info when we get a relay that shares an ed25519 ID
3458 with a different relay, instead making a BUG() warning. Fixes bug
3459 27800; bugfix on 0.3.2.1-alpha.
3461 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
3462 - When a user requests a group-readable DataDirectory, give it to
3463 them. Previously, when the DataDirectory and the CacheDirectory
3464 were the same, the default setting (0) for
3465 CacheDirectoryGroupReadable would override the setting for
3466 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
3469 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
3470 - When the onion service directory can't be created or has the wrong
3471 permissions, do not log a stack trace. Fixes bug 27335; bugfix
3474 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
3475 - Close all SOCKS request (for the same .onion) if the newly fetched
3476 descriptor is unusable. Before that, we would close only the first
3477 one leaving the other hanging and let to time out by themselves.
3478 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
3480 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
3481 - Don't warn so loudly when Tor is unable to decode an onion
3482 descriptor. This can now happen as a normal use case if a client
3483 gets a descriptor with client authorization but the client is not
3484 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
3486 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
3487 - When deleting an ephemeral onion service (DEL_ONION), do not close
3488 any rendezvous circuits in order to let the existing client
3489 connections finish by themselves or closed by the application. The
3490 HS v2 is doing that already so now we have the same behavior for
3491 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
3493 o Minor bugfixes (HTTP tunnel):
3494 - Fix a bug warning when closing an HTTP tunnel connection due to
3495 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
3498 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
3499 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
3500 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
3502 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
3503 - Ensure circuitmux queues are empty before scheduling or sending
3504 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
3506 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
3507 - Reject protocol names containing bytes other than alphanumeric
3508 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
3511 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
3512 - Compute protover votes correctly in the rust version of the
3513 protover code. Previously, the protover rewrite in 24031 allowed
3514 repeated votes from the same voter for the same protocol version
3515 to be counted multiple times in protover_compute_vote(). Fixes bug
3516 27649; bugfix on 0.3.3.5-rc.
3517 - Reject protover names that contain invalid characters. Fixes bug
3518 27687; bugfix on 0.3.3.1-alpha.
3520 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
3521 - protover_all_supported() would attempt to allocate up to 16GB on
3522 some inputs, leading to a potential memory DoS. Fixes bug 27206;
3523 bugfix on 0.3.3.5-rc.
3525 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
3526 - Fix a potential null dereference in protover_all_supported(). Add
3527 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
3528 - Return a string that can be safely freed by C code, not one
3529 created by the rust allocator, in protover_all_supported(). Fixes
3530 bug 27740; bugfix on 0.3.3.1-alpha.
3531 - Fix an API mismatch in the rust implementation of
3532 protover_compute_vote(). This bug could have caused crashes on any
3533 directory authorities running Tor with Rust (which we do not yet
3534 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
3536 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
3537 - If a unit test running in a subprocess exits abnormally or with a
3538 nonzero status code, treat the test as having failed, even if the
3539 test reported success. Without this fix, memory leaks don't cause
3540 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
3541 bugfix on 0.2.2.4-alpha.
3543 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
3544 - Treat backtrace test failures as expected on BSD-derived systems
3545 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
3546 (FreeBSD failures have been treated as expected since 18204 in
3547 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
3549 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
3550 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
3551 bugfix on 0.3.0.1-alpha.
3554 Changes in version 0.3.4.10 - 2019-01-07
3555 Tor 0.3.4.9 is the second stable release in its series; it backports
3556 numerous fixes, including an important fix for relays, and for anyone
3557 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
3560 As a reminder, the Tor 0.3.4 series will be supported until 10 June
3561 2019. Some time between now and then, users should switch to the Tor
3562 0.3.5 series, which will receive long-term support until at least 1
3565 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
3566 - Fix our usage of named groups when running as a TLS 1.3 client in
3567 OpenSSL 1.1.1. Previously, we only initialized EC groups when
3568 running as a relay, which caused clients to fail to negotiate TLS
3569 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
3572 o Major bugfixes (relay, directory, backport from 0.3.5.7):
3573 - Always reactivate linked connections in the main loop so long as
3574 any linked connection has been active. Previously, connections
3575 serving directory information wouldn't get reactivated after the
3576 first chunk of data was sent (usually 32KB), which would prevent
3577 clients from bootstrapping. Fixes bug 28912; bugfix on
3578 0.3.4.1-alpha. Patch by "cypherpunks3".
3580 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
3581 - Always show the configure and test logs, and upload them as build
3582 artifacts, when building for Windows using Appveyor CI.
3585 o Minor features (controller, backport from 0.3.5.1-alpha):
3586 - For purposes of CIRC_BW-based dropped cell detection, track half-
3587 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
3588 bias check cells to arrive without counting it as dropped until
3589 either the END arrives, or the windows are empty. Closes
3592 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
3593 - Replace the 150 fallbacks originally introduced in Tor
3594 0.3.3.1-alpha in January 2018 (of which ~115 were still
3595 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
3596 removed) generated in December 2018. Closes ticket 24803.
3598 o Minor features (geoip):
3599 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
3600 Country database. Closes ticket 28395.
3602 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
3603 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
3604 key export function from handling long labels. When this bug is
3605 detected, Tor will disable TLS 1.3. We recommend upgrading to a
3606 version of OpenSSL without this bug when it becomes available.
3607 Closes ticket 28973.
3609 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
3610 - Initialize a variable unconditionally in aes_new_cipher(), since
3611 some compilers cannot tell that we always initialize it before
3612 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
3614 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
3615 - Avoid a logging a BUG() stacktrace when closing connection held
3616 open because the write side is rate limited but not the read side.
3617 Now, the connection read side is simply shut down until Tor is
3618 able to flush the connection and close it. Fixes bug 27750; bugfix
3621 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
3622 - Manually configure the zstd compiler options, when building using
3623 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
3624 not come with a pkg-config file. Fixes bug 28454; bugfix
3626 - Stop using an external OpenSSL install, and stop installing MSYS2
3627 packages, when building using mingw on Appveyor Windows CI. Fixes
3628 bug 28399; bugfix on 0.3.4.1-alpha.
3630 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
3631 - Explicitly specify the path to the OpenSSL library and do not
3632 download OpenSSL from Pacman, but instead use the library that is
3633 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
3635 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
3636 - When a user requests a group-readable DataDirectory, give it to
3637 them. Previously, when the DataDirectory and the CacheDirectory
3638 were the same, the default setting (0) for
3639 CacheDirectoryGroupReadable would override the setting for
3640 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
3643 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
3644 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
3645 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
3647 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
3648 - Don't warn so loudly when Tor is unable to decode an onion
3649 descriptor. This can now happen as a normal use case if a client
3650 gets a descriptor with client authorization but the client is not
3651 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
3653 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
3654 - When deleting an ephemeral onion service (DEL_ONION), do not close
3655 any rendezvous circuits in order to let the existing client
3656 connections finish by themselves or closed by the application. The
3657 HS v2 is doing that already so now we have the same behavior for
3658 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
3660 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
3661 - Update relay descriptor on bandwidth changes only when the uptime
3662 is smaller than 24h, in order to reduce the efficiency of guard
3663 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
3665 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
3666 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
3667 bugfix on 0.3.0.1-alpha.
3670 Changes in version 0.3.5.7 - 2019-01-07
3671 Tor 0.3.5.7 is the first stable release in its series; it includes
3672 compilation and portability fixes, and a fix for a severe problem
3673 affecting directory caches.
3675 The Tor 0.3.5 series includes several new features and performance
3676 improvements, including client authorization for v3 onion services,
3677 cleanups to bootstrap reporting, support for improved bandwidth-
3678 measurement tools, experimental support for NSS in place of OpenSSL,
3679 and much more. It also begins a full reorganization of Tor's code
3680 layout, for improved modularity and maintainability in the future.
3681 Finally, there is the usual set of performance improvements and
3682 bugfixes that we try to do in every release series.
3684 There are a couple of changes in the 0.3.5 that may affect
3685 compatibility. First, the default version for newly created onion
3686 services is now v3. Use the HiddenServiceVersion option if you want to
3687 override this. Second, some log messages related to bootstrapping have
3688 changed; if you use stem, you may need to update to the latest version
3689 so it will recognize them.
3691 We have designated 0.3.5 as a "long-term support" (LTS) series: we
3692 will continue to patch major bugs in typical configurations of 0.3.5
3693 until at least 1 Feb 2022. (We do not plan to provide long-term
3694 support for embedding, Rust support, NSS support, running a directory
3695 authority, or unsupported platforms. For these, you will need to stick
3696 with the latest stable release.)
3698 Below are the changes since 0.3.5.6-rc. For a complete list of changes
3699 since 0.3.4.9, see the ReleaseNotes file.
3701 o Major bugfixes (relay, directory):
3702 - Always reactivate linked connections in the main loop so long as
3703 any linked connection has been active. Previously, connections
3704 serving directory information wouldn't get reactivated after the
3705 first chunk of data was sent (usually 32KB), which would prevent
3706 clients from bootstrapping. Fixes bug 28912; bugfix on
3707 0.3.4.1-alpha. Patch by "cypherpunks3".
3709 o Minor features (compilation):
3710 - When possible, place our warning flags in a separate file, to
3711 avoid flooding verbose build logs. Closes ticket 28924.
3713 o Minor features (geoip):
3714 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
3715 Country database. Closes ticket 29012.
3717 o Minor features (OpenSSL bug workaround):
3718 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
3719 key export function from handling long labels. When this bug is
3720 detected, Tor will disable TLS 1.3. We recommend upgrading to a
3721 version of OpenSSL without this bug when it becomes available.
3722 Closes ticket 28973.
3724 o Minor features (performance):
3725 - Remove about 96% of the work from the function that we run at
3726 startup to test our curve25519_basepoint implementation. Since
3727 this function has yet to find an actual failure, we now only run
3728 it for 8 iterations instead of 200. Based on our profile
3729 information, this change should save around 8% of our startup time
3730 on typical desktops, and may have a similar effect on other
3731 platforms. Closes ticket 28838.
3732 - Stop re-validating our hardcoded Diffie-Hellman parameters on
3733 every startup. Doing this wasted time and cycles, especially on
3734 low-powered devices. Closes ticket 28851.
3736 o Minor bugfixes (compilation):
3737 - Fix compilation for Android by adding a missing header to
3738 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
3740 o Minor bugfixes (correctness):
3741 - Fix an unreached code path where we checked the value of
3742 "hostname" inside send_resolved_hostname_cell(). Previously, we
3743 used it before checking it; now we check it first. Fixes bug
3744 28879; bugfix on 0.1.2.7-alpha.
3746 o Minor bugfixes (testing):
3747 - Make sure that test_rebind.py actually obeys its timeout, even
3748 when it receives a large number of log messages. Fixes bug 28883;
3749 bugfix on 0.3.5.4-alpha.
3750 - Stop running stem's unit tests as part of "make test-stem", but
3751 continue to run stem's unit and online tests during "make test-
3752 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
3754 o Minor bugfixes (windows services):
3755 - Make Tor start correctly as an NT service again: previously it was
3756 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
3758 o Code simplification and refactoring:
3759 - When parsing a port configuration, make it more obvious to static
3760 analyzer tools that we always initialize the address. Closes
3764 Changes in version 0.3.5.6-rc - 2018-12-18
3765 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
3766 It is the first release candidate in the 0.3.5.x series; if no further
3767 huge bugs are found, our next release may be the stable 0.3.5.x.
3769 o Minor features (continuous integration, Windows):
3770 - Always show the configure and test logs, and upload them as build
3771 artifacts, when building for Windows using Appveyor CI.
3774 o Minor features (fallback directory list):
3775 - Replace the 150 fallbacks originally introduced in Tor
3776 0.3.3.1-alpha in January 2018 (of which ~115 were still
3777 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
3778 removed) generated in December 2018. Closes ticket 24803.
3780 o Minor features (geoip):
3781 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
3782 Country database. Closes ticket 28744.
3784 o Minor bugfixes (compilation):
3785 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
3786 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
3788 o Minor bugfixes (continuous integration, Windows):
3789 - Explicitly specify the path to the OpenSSL library and do not
3790 download OpenSSL from Pacman, but instead use the library that is
3791 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
3793 o Minor bugfixes (onion service v3):
3794 - When deleting an ephemeral onion service (DEL_ONION), do not close
3795 any rendezvous circuits in order to let the existing client
3796 connections finish by themselves or closed by the application. The
3797 HS v2 is doing that already so now we have the same behavior for
3798 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
3800 o Minor bugfixes (restart-in-process, boostrap):
3801 - Add missing resets of bootstrap tracking state when shutting down
3802 (regression caused by ticket 27169). Fixes bug 28524; bugfix
3805 o Minor bugfixes (testing):
3806 - Use a separate DataDirectory for the test_rebind script.
3807 Previously, this script would run using the default DataDirectory,
3808 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
3809 Patch from Taylor R Campbell.
3810 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
3811 bugfix on 0.3.0.1-alpha.
3813 o Minor bugfixes (Windows):
3814 - Correctly identify Windows 8.1, Windows 10, and Windows Server
3815 2008 and later from their NT versions. Fixes bug 28096; bugfix on
3816 0.2.2.34; reported by Keifer Bly.
3817 - On recent Windows versions, the GetVersionEx() function may report
3818 an earlier Windows version than the running OS. To avoid user
3819 confusion, add "[or later]" to Tor's version string on affected
3820 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
3822 - Remove Windows versions that were never supported by the
3823 GetVersionEx() function. Stop duplicating the latest Windows
3824 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
3825 reported by Keifer Bly.
3828 - Increase logging and tag all log entries with timestamps in
3829 test_rebind.py. Provides diagnostics for issue 28229.
3831 o Code simplification and refactoring (shared random, dirauth):
3832 - Change many tor_assert() to use BUG() instead. The idea is to not
3833 crash a dirauth but rather scream loudly with a stacktrace and let
3834 it continue run. The shared random subsystem is very resilient and
3835 if anything wrong happens with it, at worst a non coherent value
3836 will be put in the vote and discarded by the other authorities.
3837 Closes ticket 19566.
3839 o Documentation (onion services):
3840 - Document in the man page that changing ClientOnionAuthDir value or
3841 adding a new file in the directory will not work at runtime upon
3842 sending a HUP if Sandbox 1. Closes ticket 28128.
3843 - Note in the man page that the only real way to fully revoke an
3844 onion service v3 client authorization is by restarting the tor
3845 process. Closes ticket 28275.
3848 Changes in version 0.3.5.5-alpha - 2018-11-16
3849 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
3850 including several that we hope to backport to older release series in
3853 o Major bugfixes (OpenSSL, portability):
3854 - Fix our usage of named groups when running as a TLS 1.3 client in
3855 OpenSSL 1.1.1. Previously, we only initialized EC groups when
3856 running as a relay, which caused clients to fail to negotiate TLS
3857 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
3860 o Minor features (geoip):
3861 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
3862 Country database. Closes ticket 28395.
3864 o Minor bugfixes (compilation):
3865 - Initialize a variable unconditionally in aes_new_cipher(), since
3866 some compilers cannot tell that we always initialize it before
3867 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
3869 o Minor bugfixes (connection, relay):
3870 - Avoid a logging a BUG() stacktrace when closing connection held
3871 open because the write side is rate limited but not the read side.
3872 Now, the connection read side is simply shut down until Tor is
3873 able to flush the connection and close it. Fixes bug 27750; bugfix
3876 o Minor bugfixes (continuous integration, Windows):
3877 - Manually configure the zstd compiler options, when building using
3878 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
3879 not come with a pkg-config file. Fixes bug 28454; bugfix
3881 - Stop using an external OpenSSL install, and stop installing MSYS2
3882 packages, when building using mingw on Appveyor Windows CI. Fixes
3883 bug 28399; bugfix on 0.3.4.1-alpha.
3885 o Minor bugfixes (documentation):
3886 - Make Doxygen work again after the code movement in the 0.3.5
3887 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
3889 o Minor bugfixes (Linux seccomp2 sandbox):
3890 - Permit the "shutdown()" system call, which is apparently used by
3891 OpenSSL under some circumstances. Fixes bug 28183; bugfix
3894 o Minor bugfixes (logging):
3895 - Stop talking about the Named flag in log messages. Clients have
3896 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
3899 o Minor bugfixes (memory leaks):
3900 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
3901 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
3903 o Minor bugfixes (onion services):
3904 - On an intro point for a version 3 onion service, stop closing
3905 introduction circuits on an NACK. This lets the client decide
3906 whether to reuse the circuit or discard it. Previously, we closed
3907 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
3908 0.3.2.1-alpha. Patch by Neel Chaunan.
3909 - When replacing a descriptor in the client cache, make sure to
3910 close all client introduction circuits for the old descriptor, so
3911 we don't end up with unusable leftover circuits. Fixes bug 27471;
3912 bugfix on 0.3.2.1-alpha.
3915 Changes in version 0.3.5.4-alpha - 2018-11-08
3916 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
3917 improves our continuous integration support. It continues our attempts
3918 to stabilize this alpha branch and build it into a foundation for an
3919 acceptable long-term-support release.
3921 o Major bugfixes (compilation, rust):
3922 - Rust tests can now build and run successfully with the
3923 --enable-fragile-hardening option enabled. Doing this currently
3924 requires the rust beta channel; it will be possible with stable
3925 rust once Rust version 1.31 is released. Patch from Alex Crichton.
3926 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
3928 o Major bugfixes (embedding, main loop):
3929 - When DisableNetwork becomes set, actually disable periodic events
3930 that are already enabled. (Previously, we would refrain from
3931 enabling new ones, but we would leave the old ones turned on.)
3932 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
3934 o Minor features (continuous integration):
3935 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
3937 - Add new CI job to Travis configuration to run stem-based
3938 integration tests. Closes ticket 27913.
3940 o Minor features (Windows, continuous integration):
3941 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
3942 Appveyor's CI. Closes ticket 28318.
3944 o Minor bugfixes (C correctness, also in 0.3.4.9):
3945 - Avoid undefined behavior in an end-of-string check when parsing
3946 the BEGIN line in a directory object. Fixes bug 28202; bugfix
3949 o Minor bugfixes (compilation):
3950 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
3951 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3953 o Minor bugfixes (compilation, OpenSolaris):
3954 - Fix compilation on OpenSolaris and its descendants by adding a
3955 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
3958 o Minor bugfixes (configuration):
3959 - Refuse to start with relative file paths and RunAsDaemon set
3960 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
3963 o Minor bugfixes (directory authority, also in 0.3.4.9):
3964 - Log additional info when we get a relay that shares an ed25519 ID
3965 with a different relay, instead of a BUG() warning with a
3966 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
3968 o Minor bugfixes (onion service v3):
3969 - Build the service descriptor's signing key certificate before
3970 uploading, so we always have a fresh one: leaving no chances for
3971 it to expire service side. Fixes bug 27838; bugfix
3974 o Minor bugfixes (onion service v3, client authorization):
3975 - Fix an assert() when adding a client authorization for the first
3976 time and then sending a HUP signal to the service. Before that,
3977 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
3979 o Minor bugfixes (onion services):
3980 - Unless we have explicitly set HiddenServiceVersion, detect the
3981 onion service version and then look for invalid options.
3982 Previously, we did the reverse, but that broke existing configs
3983 which were pointed to a v2 service and had options like
3984 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
3985 0.3.5.1-alpha. Patch by Neel Chauhan.
3987 o Minor bugfixes (portability):
3988 - Make the OPE code (which is used for v3 onion services) run
3989 correctly on big-endian platforms. Fixes bug 28115; bugfix
3992 o Minor bugfixes (protover, rust):
3993 - Reject extra commas in version strings. Fixes bug 27197; bugfix
3996 o Minor bugfixes (relay shutdown, systemd):
3997 - Notify systemd of ShutdownWaitLength so it can be set to longer
3998 than systemd's TimeoutStopSec. In Tor's systemd service file, set
3999 TimeoutSec to 60 seconds to allow Tor some time to shut down.
4000 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
4002 o Minor bugfixes (rust, also in 0.3.4.9):
4003 - Fix a potential null dereference in protover_all_supported(). Add
4004 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4005 - Return a string that can be safely freed by C code, not one
4006 created by the rust allocator, in protover_all_supported(). Fixes
4007 bug 27740; bugfix on 0.3.3.1-alpha.
4009 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
4010 - Fix an API mismatch in the rust implementation of
4011 protover_compute_vote(). This bug could have caused crashes on any
4012 directory authorities running Tor with Rust (which we do not yet
4013 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
4015 o Minor bugfixes (testing):
4016 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
4017 27968; bugfix on 0.3.5.1-alpha.
4019 o Minor bugfixes (testing, also in 0.3.4.9):
4020 - Treat backtrace test failures as expected on BSD-derived systems
4021 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
4022 (FreeBSD failures have been treated as expected since 18204 in
4023 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
4025 o Documentation (onion service manpage):
4026 - Improve HSv3 client authorization by making some options more
4027 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
4030 Changes in version 0.3.4.9 - 2018-11-02
4031 Tor 0.3.4.9 is the second stable release in its series; it backports
4032 numerous fixes, including a fix for a bandwidth management bug that
4033 was causing memory exhaustion on relays. Anyone running an earlier
4034 version of Tor 0.3.4.9 should upgrade.
4036 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
4037 - Fix compilation on ARM (and other less-used CPUs) when compiling
4038 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
4040 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
4041 - Make sure Tor bootstraps and works properly if only the
4042 ControlPort is set. Prior to this fix, Tor would only bootstrap
4043 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
4044 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
4046 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
4047 - When our write bandwidth limit is exhausted, stop writing on the
4048 connection. Previously, we had a typo in the code that would make
4049 us stop reading instead, leading to relay connections being stuck
4050 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
4053 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
4054 - Fix a use-after-free error that could be caused by passing Tor an
4055 impossible set of options that would fail during options_act().
4056 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4058 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
4059 - Don't do a distcheck with --disable-module-dirauth in Travis.
4060 Implements ticket 27252.
4061 - Only run one online rust build in Travis, to reduce network
4062 errors. Skip offline rust builds on Travis for Linux gcc, because
4063 they're redundant. Implements ticket 27252.
4064 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4065 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4066 Linux with default settings, because all the non-default builds
4067 use gcc on Linux. Implements ticket 27252.
4069 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
4070 - Use the Travis Homebrew addon to install packages on macOS during
4071 Travis CI. The package list is the same, but the Homebrew addon
4072 does not do a `brew update` by default. Implements ticket 27738.
4074 o Minor features (geoip):
4075 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
4076 Country database. Closes ticket 27991.
4078 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
4079 - Fix an integer overflow bug in our optimized 32-bit millisecond-
4080 difference algorithm for 32-bit Apple platforms. Previously, it
4081 would overflow when calculating the difference between two times
4082 more than 47 days apart. Fixes part of bug 27139; bugfix
4084 - Improve the precision of our 32-bit millisecond difference
4085 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
4086 bugfix on 0.3.4.1-alpha.
4087 - Relax the tolerance on the mainloop/update_time_jumps test when
4088 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
4091 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
4092 - Avoid undefined behavior in an end-of-string check when parsing
4093 the BEGIN line in a directory object. Fixes bug 28202; bugfix
4096 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
4097 - Only install the necessary mingw packages during our appveyor
4098 builds. This change makes the build a little faster, and prevents
4099 a conflict with a preinstalled mingw openssl that appveyor now
4100 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
4102 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
4103 - Rewrite our assertion macros so that they no longer suppress the
4104 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4106 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
4107 - Stop reinstalling identical packages in our Windows CI. Fixes bug
4108 27464; bugfix on 0.3.4.1-alpha.
4110 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
4111 - Log additional info when we get a relay that shares an ed25519 ID
4112 with a different relay, instead making a BUG() warning. Fixes bug
4113 27800; bugfix on 0.3.2.1-alpha.
4115 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
4116 - Avoid a double-close when shutting down a stalled directory
4117 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
4119 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
4120 - Fix a bug warning when closing an HTTP tunnel connection due to an
4121 HTTP request we couldn't handle. Fixes bug 26470; bugfix
4124 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
4125 - Ensure circuitmux queues are empty before scheduling or sending
4126 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
4128 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
4129 - When the onion service directory can't be created or has the wrong
4130 permissions, do not log a stack trace. Fixes bug 27335; bugfix
4133 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
4134 - Close all SOCKS request (for the same .onion) if the newly fetched
4135 descriptor is unusable. Before that, we would close only the first
4136 one leaving the other hanging and let to time out by themselves.
4137 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
4139 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4140 - When selecting a v3 rendezvous point, don't only look at the
4141 protover, but also check whether the curve25519 onion key is
4142 present. This way we avoid picking a relay that supports the v3
4143 rendezvous but for which we don't have the microdescriptor. Fixes
4144 bug 27797; bugfix on 0.3.2.1-alpha.
4146 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
4147 - Reject protocol names containing bytes other than alphanumeric
4148 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
4151 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
4152 - Compute protover votes correctly in the rust version of the
4153 protover code. Previously, the protover rewrite in 24031 allowed
4154 repeated votes from the same voter for the same protocol version
4155 to be counted multiple times in protover_compute_vote(). Fixes bug
4156 27649; bugfix on 0.3.3.5-rc.
4157 - Reject protover names that contain invalid characters. Fixes bug
4158 27687; bugfix on 0.3.3.1-alpha.
4160 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
4161 - protover_all_supported() would attempt to allocate up to 16GB on
4162 some inputs, leading to a potential memory DoS. Fixes bug 27206;
4163 bugfix on 0.3.3.5-rc.
4165 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
4166 - Fix an API mismatch in the rust implementation of
4167 protover_compute_vote(). This bug could have caused crashes on any
4168 directory authorities running Tor with Rust (which we do not yet
4169 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
4171 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
4172 - Fix a potential null dereference in protover_all_supported(). Add
4173 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4174 - Return a string that can be safely freed by C code, not one
4175 created by the rust allocator, in protover_all_supported(). Fixes
4176 bug 27740; bugfix on 0.3.3.1-alpha.
4178 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
4179 - If a unit test running in a subprocess exits abnormally or with a
4180 nonzero status code, treat the test as having failed, even if the
4181 test reported success. Without this fix, memory leaks don't cause
4182 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
4183 bugfix on 0.2.2.4-alpha.
4185 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
4186 - Make the hs_service tests use the same time source when creating
4187 the introduction point and when testing it. Now tests work better
4188 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
4191 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
4192 - Treat backtrace test failures as expected on BSD-derived systems
4193 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
4194 (FreeBSD failures have been treated as expected since 18204 in
4195 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
4198 Changes in version 0.3.5.3-alpha - 2018-10-17
4199 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
4200 versions. One important fix for relays addresses a problem with rate-
4201 limiting code from back in 0.3.4.x: If the fix works out, we'll be
4202 backporting it soon. This release is still an alpha, but we hope it's
4203 getting closer and closer to stability.
4205 o Major features (onion services):
4206 - Version 3 onion services can now use the per-service
4207 HiddenServiceExportCircuitID option to differentiate client
4208 circuits. It communicates with the service by using the HAProxy
4209 protocol to assign virtual IP addresses to inbound client
4210 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
4212 o Major bugfixes (compilation):
4213 - Fix compilation on ARM (and other less-used CPUs) when compiling
4214 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
4216 o Major bugfixes (initialization, crash):
4217 - Fix an assertion crash that would stop Tor from starting up if it
4218 tried to activate a periodic event too early. Fixes bug 27861;
4219 bugfix on 0.3.5.1-alpha.
4221 o Major bugfixes (mainloop, bootstrap):
4222 - Make sure Tor bootstraps and works properly if only the
4223 ControlPort is set. Prior to this fix, Tor would only bootstrap
4224 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
4225 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
4227 o Major bugfixes (relay):
4228 - When our write bandwidth limit is exhausted, stop writing on the
4229 connection. Previously, we had a typo in the code that would make
4230 us stop reading instead, leading to relay connections being stuck
4231 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
4234 o Minor features (continuous integration):
4235 - Use the Travis Homebrew addon to install packages on macOS during
4236 Travis CI. The package list is the same, but the Homebrew addon
4237 does not do a `brew update` by default. Implements ticket 27738.
4238 - Report what program produced the mysterious core file that we
4239 occasionally see on Travis CI during make distcheck. Closes
4242 o Minor features (geoip):
4243 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
4244 Country database. Closes ticket 27991.
4246 o Minor bugfixes (code safety):
4247 - Rewrite our assertion macros so that they no longer suppress the
4248 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4251 o Minor bugfixes (compilation):
4252 - Compile the ed25519-donna code with a correct declaration of
4253 crypto_strongest_rand(). Previously, we built it with one type,
4254 but linked it against another in the unit tests, which caused
4255 compilation failures with LTO enabled. This could have caused
4256 other undefined behavior in the tests. Fixes bug 27728; bugfix
4259 o Minor bugfixes (compilation, netbsd):
4260 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
4263 o Minor bugfixes (continuous integration, appveyor):
4264 - Install only the necessary mingw packages during our appveyor
4265 builds. This change makes the build a little faster, and prevents
4266 a conflict with a preinstalled mingw openssl that appveyor now
4267 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
4269 o Minor bugfixes (directory permissions):
4270 - When a user requests a group-readable DataDirectory, give it to
4271 them. Previously, when the DataDirectory and the CacheDirectory
4272 were the same, the default setting (0) for
4273 CacheDirectoryGroupReadable would override the setting for
4274 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4277 o Minor bugfixes (memory leaks):
4278 - Fix a small memory leak when calling Tor with --dump-config. Fixes
4279 bug 27893; bugfix on 0.3.2.1-alpha.
4281 o Minor bugfixes (networking):
4282 - In retry_listeners_ports(), make sure that we're removing a member
4283 of old_conns smartlist at most once. Fixes bug 27808; bugfix
4285 - Refrain from attempting socket rebinding when old and new
4286 listeners are in different address families. Fixes bug 27928;
4287 bugfix on 0.3.5.1-alpha.
4289 o Minor bugfixes (onion service v3):
4290 - Stop dumping a stack trace when trying to connect to an intro
4291 point without having a descriptor for it. Fixes bug 27774; bugfix
4293 - Don't warn so loudly when Tor is unable to decode an onion
4294 descriptor. This can now happen as a normal use case if a client
4295 gets a descriptor with client authorization but the client is not
4296 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4297 - When selecting a v3 rendezvous point, don't only look at the
4298 protover, but also check whether the curve25519 onion key is
4299 present. This way we avoid picking a relay that supports the v3
4300 rendezvous but for which we don't have the microdescriptor. Fixes
4301 bug 27797; bugfix on 0.3.2.1-alpha.
4303 o Minor bugfixes (protover):
4304 - Reject protocol names containing bytes other than alphanumeric
4305 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
4308 o Minor bugfixes (testing):
4309 - Make the hs_service tests use the same time source when creating
4310 the introduction point and when testing it. Now tests work better
4311 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
4313 - In test_rebind.py, check if the Python version is in the supported
4314 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
4316 o Code simplification and refactoring:
4317 - Divide more large Tor source files -- especially ones that span
4318 multiple areas of functionality -- into smaller parts, including
4319 onion.c and main.c. Closes ticket 26747.
4320 - Divide the "routerparse.c" module into separate modules for each
4321 group of parsed objects. Closes ticket 27924.
4322 - Move protover_rust.c to the same place protover.c was moved to.
4323 Closes ticket 27814.
4324 - Split directory.c into separate pieces for client, server, and
4325 common functionality. Closes ticket 26744.
4326 - Split the non-statistics-related parts from the rephist.c and
4327 geoip.c modules. Closes ticket 27892.
4328 - Split the router.c file into relay-only and shared components, to
4329 help with future modularization. Closes ticket 27864.
4332 - In the tor-resolve(1) manpage, fix the reference to socks-
4333 extensions.txt by adding a web URL. Resolves ticket 27853.
4334 - Mention that we require Python to be 2.7 or newer for some
4335 integration tests that we ship with Tor. Resolves ticket 27677.
4338 Changes in version 0.3.5.2-alpha - 2018-09-21
4339 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
4340 that made Tor think it had run out of sockets. Anybody running a relay
4341 or an onion service on 0.3.5.1-alpha should upgrade.
4343 o Major bugfixes (relay bandwidth statistics):
4344 - When we close relayed circuits, report the data in the circuit
4345 queues as being written in our relay bandwidth stats. This
4346 mitigates guard discovery and other attacks that close circuits
4347 for the explicit purpose of noticing this discrepancy in
4348 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
4350 o Major bugfixes (socket accounting):
4351 - In our socket accounting code, count a socket as closed even when
4352 it is closed indirectly by the TLS layer. Previously, we would
4353 count these sockets as still in use, and incorrectly believe that
4354 we had run out of sockets. Fixes bug 27795; bugfix
4357 o Minor bugfixes (32-bit OSX and iOS, timing):
4358 - Fix an integer overflow bug in our optimized 32-bit millisecond-
4359 difference algorithm for 32-bit Apple platforms. Previously, it
4360 would overflow when calculating the difference between two times
4361 more than 47 days apart. Fixes part of bug 27139; bugfix
4363 - Improve the precision of our 32-bit millisecond difference
4364 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
4365 bugfix on 0.3.4.1-alpha.
4366 - Relax the tolerance on the mainloop/update_time_jumps test when
4367 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
4370 o Minor bugfixes (onion service v3):
4371 - Close all SOCKS request (for the same .onion) if the newly fetched
4372 descriptor is unusable. Before that, we would close only the first
4373 one leaving the other hanging and let to time out by themselves.
4374 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
4376 o Minor bugfixes (memory leak):
4377 - Fix an unlikely memory leak when trying to read a private key from
4378 a ridiculously large file. Fixes bug 27764; bugfix on
4379 0.3.5.1-alpha. This is CID 1439488.
4381 o Minor bugfixes (NSS):
4382 - Correctly detect failure to open a dummy TCP socket when stealing
4383 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
4386 o Minor bugfixes (rust):
4387 - protover_all_supported() would attempt to allocate up to 16GB on
4388 some inputs, leading to a potential memory DoS. Fixes bug 27206;
4389 bugfix on 0.3.3.5-rc.
4391 o Minor bugfixes (testing):
4392 - Revise the "conditionvar_timeout" test so that it succeeds even on
4393 heavily loaded systems where the test threads are not scheduled
4394 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
4396 o Code simplification and refactoring:
4397 - Divide the routerlist.c and dirserv.c modules into smaller parts.
4398 Closes ticket 27799.
4401 Changes in version 0.3.5.1-alpha - 2018-09-18
4402 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
4403 client authorization for modern (v3) onion services, improves
4404 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
4405 support for NSS in place of OpenSSL, and much more.
4407 o Major features (onion services, UI change):
4408 - For a newly created onion service, the default version is now 3.
4409 Tor still supports existing version 2 services, but the operator
4410 now needs to set "HiddenServiceVersion 2" in order to create a new
4411 version 2 service. For existing services, Tor now learns the
4412 version by reading the key file. Closes ticket 27215.
4414 o Major features (relay, UI change):
4415 - Relays no longer run as exits by default. If the "ExitRelay"
4416 option is auto (or unset), and no exit policy is specified with
4417 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
4418 Previously in this case, we allowed exit traffic and logged a
4419 warning message. Closes ticket 21530. Patch by Neel Chauhan.
4420 - Tor now validates that the ContactInfo config option is valid UTF-
4421 8 when parsing torrc. Closes ticket 27428.
4423 o Major features (bootstrap):
4424 - Don't report directory progress until after a connection to a
4425 relay or bridge has succeeded. Previously, we'd report 80%
4426 progress based on cached directory information when we couldn't
4427 even connect to the network. Closes ticket 27169.
4429 o Major features (new code layout):
4430 - Nearly all of Tor's source code has been moved around into more
4431 logical places. The "common" directory is now divided into a set
4432 of libraries in "lib", and files in the "or" directory have been
4433 split into "core" (logic absolutely needed for onion routing),
4434 "feature" (independent modules in Tor), and "app" (to configure
4435 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
4436 more information. Closes ticket 26481.
4438 This refactoring is not complete: although the libraries have been
4439 refactored to be acyclic, the main body of Tor is still too
4440 interconnected. We will attempt to improve this in the future.
4442 o Major features (onion services v3):
4443 - Implement onion service client authorization at the descriptor
4444 level: only authorized clients can decrypt a service's descriptor
4445 to find out how to contact it. A new torrc option was added to
4446 control this client side: ClientOnionAuthDir <path>. On the
4447 service side, if the "authorized_clients/" directory exists in the
4448 onion service directory path, client configurations are read from
4449 the files within. See the manpage for more details. Closes ticket
4450 27547. Patch done by Suphanat Chunhapanya (haxxpop).
4451 - Improve revision counter generation in next-gen onion services.
4452 Onion services can now scale by hosting multiple instances on
4453 different hosts without synchronization between them, which was
4454 previously impossible because descriptors would get rejected by
4455 HSDirs. Addresses ticket 25552.
4457 o Major features (portability, cryptography, experimental, TLS):
4458 - Tor now has the option to compile with the NSS library instead of
4459 OpenSSL. This feature is experimental, and we expect that bugs may
4460 remain. It is mainly intended for environments where Tor's
4461 performance is not CPU-bound, and where NSS is already known to be
4462 installed. To try it out, configure Tor with the --enable-nss
4463 flag. Closes tickets 26631, 26815, and 26816.
4465 If you are experimenting with this option and using an old cached
4466 consensus, Tor may fail to start. To solve this, delete your
4467 "cached-consensus" and "cached-microdesc-consensus" files,
4468 (if present), and restart Tor.
4470 o Major bugfixes (directory authority):
4471 - Actually check that the address we get from DirAuthority
4472 configuration line is valid IPv4. Explicitly disallow DirAuthority
4473 address to be a DNS hostname. Fixes bug 26488; bugfix
4476 o Major bugfixes (restart-in-process):
4477 - Fix a use-after-free error that could be caused by passing Tor an
4478 impossible set of options that would fail during options_act().
4479 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4481 o Minor features (admin tools):
4482 - Add a new --key-expiration option to print the expiration date of
4483 the signing cert in an ed25519_signing_cert file. Resolves
4486 o Minor features (build):
4487 - If you pass the "--enable-pic" option to configure, Tor will try
4488 to tell the compiler to build position-independent code suitable
4489 to link into a dynamic library. (The default remains -fPIE, for
4490 code suitable for a relocatable executable.) Closes ticket 23846.
4492 o Minor features (code correctness, testing):
4493 - Tor's build process now includes a "check-includes" make target to
4494 verify that no module of Tor relies on any headers from a higher-
4495 level module. We hope to use this feature over time to help
4496 refactor our codebase. Closes ticket 26447.
4498 o Minor features (code layout):
4499 - We have a new "lowest-level" error-handling API for use by code
4500 invoked from within the logging module. With this interface, the
4501 logging code is no longer at risk of calling into itself if a
4502 failure occurs while it is trying to log something. Closes
4505 o Minor features (compilation):
4506 - Tor's configure script now supports a --with-malloc= option to
4507 select your malloc implementation. Supported options are
4508 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
4509 default). Addresses part of ticket 20424. Based on a patch from
4512 o Minor features (config):
4513 - The "auto" keyword in torrc is now case-insensitive. Closes
4516 o Minor features (continuous integration):
4517 - Don't do a distcheck with --disable-module-dirauth in Travis.
4518 Implements ticket 27252.
4519 - Install libcap-dev and libseccomp2-dev so these optional
4520 dependencies get tested on Travis CI. Closes ticket 26560.
4521 - Only run one online rust build in Travis, to reduce network
4522 errors. Skip offline rust builds on Travis for Linux gcc, because
4523 they're redundant. Implements ticket 27252.
4524 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4525 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4526 Linux with default settings, because all the non-default builds
4527 use gcc on Linux. Implements ticket 27252.
4529 o Minor features (controller):
4530 - Emit CIRC_BW events as soon as we detect that we processed an
4531 invalid or otherwise dropped cell on a circuit. This allows
4532 vanguards and other controllers to react more quickly to dropped
4533 cells. Closes ticket 27678.
4534 - For purposes of CIRC_BW-based dropped cell detection, track half-
4535 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
4536 bias check cells to arrive without counting it as dropped until
4537 either the END arrives, or the windows are empty. Closes
4539 - Implement a 'GETINFO md/all' controller command to enable getting
4540 all known microdescriptors. Closes ticket 8323.
4541 - The GETINFO command now support an "uptime" argument, to return
4542 Tor's uptime in seconds. Closes ticket 25132.
4544 o Minor features (denial-of-service avoidance):
4545 - Make our OOM handler aware of the DNS cache so that it doesn't
4546 fill up the memory. This check is important for our DoS mitigation
4547 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
4549 o Minor features (development):
4550 - Tor's makefile now supports running the "clippy" Rust style tool
4551 on our Rust code. Closes ticket 22156.
4553 o Minor features (directory authority):
4554 - There is no longer an artificial upper limit on the length of
4555 bandwidth lines. Closes ticket 26223.
4556 - When a bandwidth file is used to obtain the bandwidth measurements,
4557 include this bandwidth file headers in the votes. Closes
4559 - Improved support for networks with only a single authority or a
4560 single fallback directory. Patch from Gabriel Somlo. Closes
4563 o Minor features (embedding API):
4564 - The Tor controller API now supports a function to launch Tor with
4565 a preconstructed owning controller FD, so that embedding
4566 applications don't need to manage controller ports and
4567 authentication. Closes ticket 24204.
4568 - The Tor controller API now has a function that returns the name
4569 and version of the backend implementing the API. Closes
4572 o Minor features (geoip):
4573 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
4574 Country database. Closes ticket 27631.
4576 o Minor features (memory management):
4577 - Get Libevent to use the same memory allocator as Tor, by calling
4578 event_set_mem_functions() during initialization. Resolves
4581 o Minor features (memory usage):
4582 - When not using them, store legacy TAP public onion keys in DER-
4583 encoded format, rather than as expanded public keys. This should
4584 save several megabytes on typical clients. Closes ticket 27246.
4586 o Minor features (OpenSSL):
4587 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
4588 than our own. Resolves ticket 19979.
4590 o Minor features (Rust, code quality):
4591 - Improve rust code quality in the rust protover implementation by
4592 making it more idiomatic. Includes changing an internal API to
4593 take &str instead of &String. Closes ticket 26492.
4595 o Minor features (testing):
4596 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
4597 chutney. Implements ticket 27211.
4599 o Minor features (tor-resolve):
4600 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
4601 Side-effect of the refactoring for ticket 26526.
4603 o Minor features (UI):
4604 - Log each included configuration file or directory as we read it,
4605 to provide more visibility about where Tor is reading from. Patch
4606 from Unto Sten; closes ticket 27186.
4607 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
4608 Closes ticket 26703.
4610 o Minor bugfixes (bootstrap):
4611 - Try harder to get descriptors in non-exit test networks, by using
4612 the mid weight for the third hop when there are no exits. Fixes
4613 bug 27237; bugfix on 0.2.6.2-alpha.
4615 o Minor bugfixes (C correctness):
4616 - Avoid casting smartlist index to int implicitly, as it may trigger
4617 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
4618 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
4619 - Use time_t for all values in
4620 predicted_ports_prediction_time_remaining(). Rework the code that
4621 computes difference between durations/timestamps. Fixes bug 27165;
4622 bugfix on 0.3.1.1-alpha.
4624 o Minor bugfixes (client, memory usage):
4625 - When not running as a directory cache, there is no need to store
4626 the text of the current consensus networkstatus in RAM.
4627 Previously, however, clients would store it anyway, at a cost of
4628 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
4631 o Minor bugfixes (client, reachableaddresses):
4632 - Instead of adding a "reject *:*" line to ReachableAddresses when
4633 loading the configuration, add one to the policy after parsing it
4634 in parse_reachable_addresses(). This prevents extra "reject *.*"
4635 lines from accumulating on reloads. Fixes bug 20874; bugfix on
4636 0.1.1.5-alpha. Patch by Neel Chauhan.
4638 o Minor bugfixes (code quality):
4639 - Rename sandbox_getaddrinfo() and other functions to no longer
4640 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
4641 bugfix on 0.2.7.1-alpha.
4643 o Minor bugfixes (configuration, Onion Services):
4644 - In rend_service_parse_port_config(), disallow any input to remain
4645 after address-port pair was parsed. This will catch address and
4646 port being whitespace-separated by mistake of the user. Fixes bug
4647 27044; bugfix on 0.2.9.10.
4649 o Minor bugfixes (continuous integration):
4650 - Stop reinstalling identical packages in our Windows CI. Fixes bug
4651 27464; bugfix on 0.3.4.1-alpha.
4653 o Minor bugfixes (controller):
4654 - Consider all routerinfo errors other than "not a server" to be
4655 transient for the purpose of "GETINFO exit-policy/*" controller
4656 request. Print stacktrace in the unlikely case of failing to
4657 recompute routerinfo digest. Fixes bug 27034; bugfix
4660 o Minor bugfixes (directory connection shutdown):
4661 - Avoid a double-close when shutting down a stalled directory
4662 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
4664 o Minor bugfixes (HTTP tunnel):
4665 - Fix a bug warning when closing an HTTP tunnel connection due to an
4666 HTTP request we couldn't handle. Fixes bug 26470; bugfix
4669 o Minor bugfixes (ipv6):
4670 - In addrs_in_same_network_family(), we choose the subnet size based
4671 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
4672 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
4673 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
4675 o Minor bugfixes (logging):
4676 - As a precaution, do an early return from log_addr_has_changed() if
4677 Tor is running as client. Also, log a stack trace for debugging as
4678 this function should only be called when Tor runs as server. Fixes
4679 bug 26892; bugfix on 0.1.1.9-alpha.
4680 - Refrain from mentioning bug 21018 in the logs, as it is already
4681 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
4683 o Minor bugfixes (logging, documentation):
4684 - When SafeLogging is enabled, scrub IP address in
4685 channel_tls_process_netinfo_cell(). Also, add a note to manpage
4686 that scrubbing is not guaranteed on loglevels below Notice. Fixes
4687 bug 26882; bugfix on 0.2.4.10-alpha.
4689 o Minor bugfixes (netflow padding):
4690 - Ensure circuitmux queues are empty before scheduling or sending
4691 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
4693 o Minor bugfixes (onion service v2):
4694 - Log at level "info", not "warning", in the case that we do not
4695 have a consensus when a .onion request comes in. This can happen
4696 normally while bootstrapping. Fixes bug 27040; bugfix
4699 o Minor bugfixes (onion service v3):
4700 - When the onion service directory can't be created or has the wrong
4701 permissions, do not log a stack trace. Fixes bug 27335; bugfix
4704 o Minor bugfixes (OS compatibility):
4705 - Properly handle configuration changes that move a listener to/from
4706 wildcard IP address. If the first attempt to bind a socket fails,
4707 close the old listener and try binding the socket again. Fixes bug
4708 17873; bugfix on 0.0.8pre-1.
4710 o Minor bugfixes (performance)::
4711 - Rework node_is_a_configured_bridge() to no longer call
4712 node_get_all_orports(), which was performing too many memory
4713 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
4715 o Minor bugfixes (relay statistics):
4716 - Update relay descriptor on bandwidth changes only when the uptime
4717 is smaller than 24h, in order to reduce the efficiency of guard
4718 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4720 o Minor bugfixes (relays):
4721 - Consider the fact that we'll be making direct connections to our
4722 entry and guard nodes when computing the fraction of nodes that
4723 have their descriptors. Also, if we are using bridges and there is
4724 at least one bridge with a full descriptor, treat the fraction of
4725 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
4726 Patch by Neel Chauhan.
4727 - Update the message logged on relays when DirCache is disabled.
4728 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
4729 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
4731 o Minor bugfixes (rust, protover):
4732 - Compute protover votes correctly in the rust version of the
4733 protover code. Previously, the protover rewrite in 24031 allowed
4734 repeated votes from the same voter for the same protocol version
4735 to be counted multiple times in protover_compute_vote(). Fixes bug
4736 27649; bugfix on 0.3.3.5-rc.
4737 - Reject protover names that contain invalid characters. Fixes bug
4738 27687; bugfix on 0.3.3.1-alpha.
4740 o Minor bugfixes (testing):
4741 - Fix two unit tests to work when HOME environment variable is not
4742 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
4743 - If a unit test running in a subprocess exits abnormally or with a
4744 nonzero status code, treat the test as having failed, even if the
4745 test reported success. Without this fix, memory leaks don't cause
4746 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
4747 bugfix on 0.2.2.4-alpha.
4748 - When logging a version mismatch in our openssl_version tests,
4749 report the actual offending version strings. Fixes bug 26152;
4750 bugfix on 0.2.9.1-alpha.
4751 - Fix forking tests on Windows when there is a space somewhere in
4752 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
4754 o Code simplification and refactoring:
4755 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
4756 longer needed. Closes ticket 26502.
4757 - Include paths to header files within Tor are now qualified by
4758 directory within the top-level src directory.
4759 - Many structures have been removed from the centralized "or.h"
4760 header, and moved into their own headers. This will allow us to
4761 reduce the number of places in the code that rely on each
4762 structure's contents and layout. Closes ticket 26383.
4763 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
4764 - Remove GetAdaptersAddresses_fn_t. The code that used it was
4765 removed as part of the 26481 refactor. Closes ticket 27467.
4766 - Rework Tor SOCKS server code to use Trunnel and benefit from
4767 autogenerated functions for parsing and generating SOCKS wire
4768 format. New implementation is cleaner, more maintainable and
4769 should be less prone to heartbleed-style vulnerabilities.
4770 Implements a significant fraction of ticket 3569.
4771 - Split sampled_guards_update_from_consensus() and
4772 select_entry_guard_for_circuit() into subfunctions. In
4773 entry_guards_update_primary() unite three smartlist enumerations
4774 into one and move smartlist comparison code out of the function.
4775 Closes ticket 21349.
4776 - Tor now assumes that you have standards-conformant stdint.h and
4777 inttypes.h headers when compiling. Closes ticket 26626.
4778 - Unify our bloom filter logic. Previously we had two copies of this
4779 code: one for routerlist filtering, and one for address set
4780 calculations. Closes ticket 26510.
4781 - Use the simpler strcmpstart() helper in
4782 rend_parse_v2_service_descriptor instead of strncmp(). Closes
4784 - Utility functions that can perform a DNS lookup are now wholly
4785 separated from those that can't, in separate headers and C
4786 modules. Closes ticket 26526.
4789 - Copy paragraph and URL to Tor's code of conduct document from
4790 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
4791 - Remove old instructions from INSTALL document. Closes ticket 26588.
4792 - Warn users that they should not include MyFamily line(s) in their
4793 torrc when running Tor bridge. Closes ticket 26908.
4796 - Tor no longer supports building with the dmalloc library. For
4797 debugging memory issues, we suggest using gperftools or msan
4798 instead. Closes ticket 26426.
4799 - Tor no longer attempts to run on Windows environments without the
4800 GetAdaptersAddresses() function. This function has existed since
4801 Windows XP, which is itself already older than we support.
4802 - Remove Tor2web functionality for version 2 onion services. The
4803 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
4804 (This feature was never shipped in vanilla Tor and it was only
4805 possible to use this feature by building the support at compile
4806 time. Tor2webMode is not implemented for version 3 onion services.)
4807 Closes ticket 26367.
4810 Changes in version 0.2.9.17 - 2018-09-10
4811 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
4813 o Minor features (compatibility, backport from 0.3.4.8):
4814 - Tell OpenSSL to maintain backward compatibility with previous
4815 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
4816 ciphers are disabled by default. Closes ticket 27344.
4818 o Minor features (continuous integration, backport from 0.3.4.7-rc):
4819 - Enable macOS builds in our Travis CI configuration. Closes
4821 - Install libcap-dev and libseccomp2-dev so these optional
4822 dependencies get tested on Travis CI. Closes ticket 26560.
4823 - Run asciidoc during Travis CI. Implements ticket 27087.
4824 - Use ccache in our Travis CI configuration. Closes ticket 26952.
4826 o Minor features (geoip):
4827 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
4828 Country database. Closes ticket 27089.
4830 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
4831 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
4832 tell the compiler not to include the system malloc implementation.
4833 Fixes bug 20424; bugfix on 0.2.0.20-rc.
4835 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
4836 - Silence a spurious compiler warning on the GetAdaptersAddresses
4837 function pointer cast. This issue is already fixed by 26481 in
4838 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
4839 bugfix on 0.2.3.11-alpha.
4840 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
4841 supported, and always fails. Some compilers warn about the
4842 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
4845 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
4846 - Don't link or search for pthreads when building for Windows, even
4847 if we are using build environment (like mingw) that provides a
4848 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
4850 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
4851 - Skip a pair of unreliable key generation tests on Windows, until
4852 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
4853 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
4855 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
4856 - Pass the module flags to distcheck configure, and log the flags
4857 before running configure. (Backported to 0.2.9 and later as a
4858 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
4860 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
4861 - When a Travis build fails, and showing a log fails, keep trying to
4862 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
4863 - When we use echo in Travis, don't pass a --flag as the first
4864 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
4866 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
4867 - When voting for recommended versions, make sure that all of the
4868 versions are well-formed and parsable. Fixes bug 26485; bugfix
4871 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
4872 - Fix a bug in out sandboxing rules for the openat() syscall.
4873 Previously, no openat() call would be permitted, which would break
4874 filesystem operations on recent glibc versions. Fixes bug 25440;
4875 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
4877 o Minor bugfixes (onion services, backport from 0.3.4.8):
4878 - Silence a spurious compiler warning in
4879 rend_client_send_introduction(). Fixes bug 27463; bugfix
4882 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
4883 - Log a protocol warning when single onion services or Tor2web clients
4884 fail to authenticate direct connections to relays.
4885 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
4887 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
4888 - Disable core dumps in test_bt.sh, to avoid failures in "make
4889 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
4891 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
4892 - Before running make test-network-all, delete old logs and test
4893 result files, to avoid spurious failures. Fixes bug 27295; bugfix
4896 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
4897 - Our "tortls/cert_matches_key" unit test no longer relies on
4898 OpenSSL internals. Previously, it relied on unsupported OpenSSL
4899 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
4900 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
4902 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
4903 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
4904 27185; bugfix on 0.2.2.2-alpha.
4907 Changes in version 0.3.2.12 - 2018-09-10
4908 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
4910 o Minor features (compatibility, backport from 0.3.4.8):
4911 - Tell OpenSSL to maintain backward compatibility with previous
4912 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
4913 ciphers are disabled by default. Closes ticket 27344.
4915 o Minor features (continuous integration, backport from 0.3.4.7-rc):
4916 - Enable macOS builds in our Travis CI configuration. Closes
4918 - Install libcap-dev and libseccomp2-dev so these optional
4919 dependencies get tested on Travis CI. Closes ticket 26560.
4920 - Run asciidoc during Travis CI. Implements ticket 27087.
4921 - Use ccache in our Travis CI configuration. Closes ticket 26952.
4923 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
4924 - Use cargo cache in our Travis CI configuration. Closes
4927 o Minor features (controller, backport from 0.3.4.6-rc):
4928 - The control port now exposes the list of HTTPTunnelPorts and
4929 ExtOrPorts via GETINFO net/listeners/httptunnel and
4930 net/listeners/extor respectively. Closes ticket 26647.
4932 o Minor features (directory authorities, backport from 0.3.4.7-rc):
4933 - Authorities no longer vote to make the subprotocol version
4934 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
4935 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
4937 o Minor features (geoip):
4938 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
4939 Country database. Closes ticket 27089.
4941 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
4942 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
4943 tell the compiler not to include the system malloc implementation.
4944 Fixes bug 20424; bugfix on 0.2.0.20-rc.
4945 - Don't try to use a pragma to temporarily disable the
4946 -Wunused-const-variable warning if the compiler doesn't support
4947 it. Fixes bug 26785; bugfix on 0.3.2.11.
4949 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
4950 - Silence a spurious compiler warning on the GetAdaptersAddresses
4951 function pointer cast. This issue is already fixed by 26481 in
4952 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
4953 bugfix on 0.2.3.11-alpha.
4954 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
4955 supported, and always fails. Some compilers warn about the
4956 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
4959 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
4960 - Don't link or search for pthreads when building for Windows, even
4961 if we are using build environment (like mingw) that provides a
4962 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
4964 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
4965 - Skip a pair of unreliable key generation tests on Windows, until
4966 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
4967 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
4969 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
4970 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
4971 - Pass the module flags to distcheck configure, and log the flags
4972 before running configure. (Backported to 0.2.9 and later as a
4973 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
4975 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
4976 - When a Travis build fails, and showing a log fails, keep trying to
4977 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
4978 - When we use echo in Travis, don't pass a --flag as the first
4979 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
4981 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
4982 - When voting for recommended versions, make sure that all of the
4983 versions are well-formed and parsable. Fixes bug 26485; bugfix
4986 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
4987 - Fix a bug in out sandboxing rules for the openat() syscall.
4988 Previously, no openat() call would be permitted, which would break
4989 filesystem operations on recent glibc versions. Fixes bug 25440;
4990 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
4992 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
4993 - Improve the log message when connection initiators fail to
4994 authenticate direct connections to relays. Fixes bug 26927; bugfix
4997 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
4998 - Fix bug that causes services to not ever rotate their descriptors
4999 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
5002 o Minor bugfixes (onion services, backport from 0.3.4.8):
5003 - Silence a spurious compiler warning in
5004 rend_client_send_introduction(). Fixes bug 27463; bugfix
5007 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
5008 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
5010 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
5011 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
5012 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
5013 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
5015 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5016 - Log a protocol warning when single onion services or Tor2web clients
5017 fail to authenticate direct connections to relays.
5018 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5020 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5021 - Disable core dumps in test_bt.sh, to avoid failures in "make
5022 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5024 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5025 - When running make test-network-all, use the mixed+hs-v2 network.
5026 (A previous fix to chutney removed v3 onion services from the
5027 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
5028 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
5029 - Before running make test-network-all, delete old logs and test
5030 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5033 o Minor bugfixes (testing, openssl compatibility):
5034 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
5035 internals. Previously, it relied on unsupported OpenSSL behavior in
5036 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
5037 bugfix on 0.2.5.1-alpha.
5039 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5040 - Our "tortls/cert_matches_key" unit test no longer relies on
5041 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5042 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5043 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5045 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5046 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5047 27185; bugfix on 0.2.2.2-alpha.
5050 Changes in version 0.3.3.10 - 2018-09-10
5051 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
5053 o Minor features (bug workaround, backport from 0.3.4.7-rc):
5054 - Compile correctly on systems that provide the C11 stdatomic.h
5055 header, but where C11 atomic functions don't actually compile.
5056 Closes ticket 26779; workaround for Debian issue 903709.
5058 o Minor features (compatibility, backport from 0.3.4.8):
5059 - Tell OpenSSL to maintain backward compatibility with previous
5060 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5061 ciphers are disabled by default. Closes ticket 27344.
5063 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5064 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
5065 - Enable macOS builds in our Travis CI configuration. Closes
5067 - Install libcap-dev and libseccomp2-dev so these optional
5068 dependencies get tested on Travis CI. Closes ticket 26560.
5069 - Run asciidoc during Travis CI. Implements ticket 27087.
5070 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5072 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
5073 - Use cargo cache in our Travis CI configuration. Closes
5076 o Minor features (controller, backport from 0.3.4.6-rc):
5077 - The control port now exposes the list of HTTPTunnelPorts and
5078 ExtOrPorts via GETINFO net/listeners/httptunnel and
5079 net/listeners/extor respectively. Closes ticket 26647.
5081 o Minor features (directory authorities, backport from 0.3.4.7-rc):
5082 - Authorities no longer vote to make the subprotocol version
5083 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
5084 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
5086 o Minor features (geoip):
5087 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5088 Country database. Closes ticket 27089.
5090 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5091 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5092 tell the compiler not to include the system malloc implementation.
5093 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5094 - Don't try to use a pragma to temporarily disable the
5095 -Wunused-const-variable warning if the compiler doesn't support
5096 it. Fixes bug 26785; bugfix on 0.3.2.11.
5098 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5099 - Silence a spurious compiler warning on the GetAdaptersAddresses
5100 function pointer cast. This issue is already fixed by 26481 in
5101 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5102 bugfix on 0.2.3.11-alpha.
5103 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5104 supported, and always fails. Some compilers warn about the
5105 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5108 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5109 - Don't link or search for pthreads when building for Windows, even
5110 if we are using build environment (like mingw) that provides a
5111 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5113 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5114 - Skip a pair of unreliable key generation tests on Windows, until
5115 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5116 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5118 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5119 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
5120 - Pass the module flags to distcheck configure, and log the flags
5121 before running configure. (Backported to 0.2.9 and later as a
5122 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5124 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5125 - When a Travis build fails, and showing a log fails, keep trying to
5126 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5127 - When we use echo in Travis, don't pass a --flag as the first
5128 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5130 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5131 - When voting for recommended versions, make sure that all of the
5132 versions are well-formed and parsable. Fixes bug 26485; bugfix
5135 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
5136 - Always call tor_free_all() when leaving tor_run_main(). When we
5137 did not, restarting tor in-process would cause an assertion
5138 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
5140 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5141 - Fix a bug in our sandboxing rules for the openat() syscall.
5142 Previously, no openat() call would be permitted, which would break
5143 filesystem operations on recent glibc versions. Fixes bug 25440;
5144 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5146 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
5147 - Improve the log message when connection initiators fail to
5148 authenticate direct connections to relays. Fixes bug 26927; bugfix
5151 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
5152 - Fix bug that causes services to not ever rotate their descriptors
5153 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
5156 o Minor bugfixes (onion services, backport from 0.3.4.8):
5157 - Silence a spurious compiler warning in
5158 rend_client_send_introduction(). Fixes bug 27463; bugfix
5161 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
5162 - Work around two different bugs in the OS X 10.10 and later SDKs
5163 that would prevent us from successfully targeting earlier versions
5164 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
5166 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
5167 - Fix compilation of the unit tests on GNU/Hurd, which does not
5168 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
5171 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
5172 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
5174 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
5175 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
5176 - Protover parsing was accepting the presence of whitespace in
5177 version strings, which the C implementation would choke on, e.g.
5178 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
5179 - Protover parsing was ignoring a 2nd hyphen and everything after
5180 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
5182 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
5183 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
5184 - cd to ${abs_top_builddir}/src/rust before running cargo in
5185 src/test/test_rust.sh. This makes the working directory consistent
5186 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
5188 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5189 - Log a protocol warning when single onion services or Tor2web clients
5190 fail to authenticate direct connections to relays.
5191 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5193 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5194 - Disable core dumps in test_bt.sh, to avoid failures in "make
5195 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5197 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5198 - When running make test-network-all, use the mixed+hs-v2 network.
5199 (A previous fix to chutney removed v3 onion services from the
5200 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
5201 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
5202 - Before running make test-network-all, delete old logs and test
5203 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5206 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5207 - Our "tortls/cert_matches_key" unit test no longer relies on
5208 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5209 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5210 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5212 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
5213 - Stop sending ed25519 link specifiers in v3 onion service introduce
5214 cells and descriptors, when the rendezvous or introduction point
5215 doesn't support ed25519 link authentication. Fixes bug 26627;
5216 bugfix on 0.3.2.4-alpha.
5218 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5219 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5220 27185; bugfix on 0.2.2.2-alpha.
5223 Changes in version 0.3.4.8 - 2018-09-10
5224 Tor 0.3.4.8 is the first stable release in its series; it includes
5225 compilation and portability fixes.
5227 The Tor 0.3.4 series includes improvements for running Tor in
5228 low-power and embedded environments, which should help performance in
5229 general. We've begun work on better modularity, and included preliminary
5230 changes on the directory authority side to accommodate a new bandwidth
5231 measurement system. We've also integrated more continuous-integration
5232 systems into our development process, and made corresponding changes to
5233 Tor's testing infrastructure. Finally, we've continued to refine
5234 our anti-denial-of-service code.
5236 Below are the changes since 0.3.4.7-rc. For a complete list of changes
5237 since 0.3.3.9, see the ReleaseNotes file.
5239 o Minor features (compatibility):
5240 - Tell OpenSSL to maintain backward compatibility with previous
5241 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5242 ciphers are disabled by default. Closes ticket 27344.
5244 o Minor features (continuous integration):
5245 - Log the compiler path and version during Appveyor builds.
5246 Implements ticket 27449.
5247 - Show config.log and test-suite.log after failed Appveyor builds.
5248 Also upload the zipped full logs as a build artifact. Implements
5251 o Minor bugfixes (compilation):
5252 - Silence a spurious compiler warning on the GetAdaptersAddresses
5253 function pointer cast. This issue is already fixed by 26481 in
5254 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5255 bugfix on 0.2.3.11-alpha.
5256 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5257 supported, and always fails. Some compilers warn about the
5258 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5261 o Minor bugfixes (continuous integration):
5262 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
5263 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
5264 Executables compiled for 64-bit Windows with this version of gcc
5265 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
5266 27460; bugfix on 0.3.4.1-alpha.
5267 - When a Travis build fails, and showing a log fails, keep trying to
5268 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5269 - When we use echo in Travis, don't pass a --flag as the first
5270 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5272 o Minor bugfixes (onion services):
5273 - Silence a spurious compiler warning in
5274 rend_client_send_introduction(). Fixes bug 27463; bugfix
5277 o Minor bugfixes (testing, chutney):
5278 - When running make test-network-all, use the mixed+hs-v2 network.
5279 (A previous fix to chutney removed v3 onion services from the
5280 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
5281 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
5282 - Before running make test-network-all, delete old logs and test
5283 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5286 Changes in version 0.3.4.7-rc - 2018-08-24
5287 Tor 0.3.4.7-rc fixes several small compilation, portability, and
5288 correctness issues in previous versions of Tor. This version is a
5289 release candidate: if no serious bugs are found, we expect that the
5290 stable 0.3.4 release will be (almost) the same as this release.
5292 o Minor features (bug workaround):
5293 - Compile correctly on systems that provide the C11 stdatomic.h
5294 header, but where C11 atomic functions don't actually compile.
5295 Closes ticket 26779; workaround for Debian issue 903709.
5297 o Minor features (continuous integration):
5298 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
5299 - Enable macOS builds in our Travis CI configuration. Closes
5301 - Install libcap-dev and libseccomp2-dev so these optional
5302 dependencies get tested on Travis CI. Closes ticket 26560.
5303 - Only post Appveyor IRC notifications when the build fails.
5304 Implements ticket 27275.
5305 - Run asciidoc during Travis CI. Implements ticket 27087.
5306 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5308 o Minor features (continuous integration, rust):
5309 - Use cargo cache in our Travis CI configuration. Closes
5312 o Minor features (directory authorities):
5313 - Authorities no longer vote to make the subprotocol version
5314 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
5315 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
5317 o Minor features (geoip):
5318 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5319 Country database. Closes ticket 27089.
5321 o Minor bugfixes (compilation, windows):
5322 - Don't link or search for pthreads when building for Windows, even
5323 if we are using build environment (like mingw) that provides a
5324 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5326 o Minor bugfixes (continuous integration):
5327 - Improve Appveyor CI IRC logging. Generate correct branches and
5328 URLs for pull requests and tags. Use unambiguous short commits.
5329 Fixes bug 26979; bugfix on master.
5330 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
5331 - Pass the module flags to distcheck configure, and log the flags
5332 before running configure. (Backported to 0.2.9 and later as a
5333 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5335 o Minor bugfixes (in-process restart):
5336 - Always call tor_free_all() when leaving tor_run_main(). When we
5337 did not, restarting tor in-process would cause an assertion
5338 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
5340 o Minor bugfixes (linux seccomp2 sandbox):
5341 - Fix a bug in out sandboxing rules for the openat() syscall.
5342 Previously, no openat() call would be permitted, which would break
5343 filesystem operations on recent glibc versions. Fixes bug 25440;
5344 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5346 o Minor bugfixes (onion services):
5347 - Fix bug that causes services to not ever rotate their descriptors
5348 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
5351 o Minor bugfixes (portability):
5352 - Fix compilation of the unit tests on GNU/Hurd, which does not
5353 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
5356 o Minor bugfixes (rust):
5357 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
5359 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
5360 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
5361 - Protover parsing was accepting the presence of whitespace in
5362 version strings, which the C implementation would choke on, e.g.
5363 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
5364 - Protover parsing was ignoring a 2nd hyphen and everything after
5365 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
5367 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
5368 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
5369 - cd to ${abs_top_builddir}/src/rust before running cargo in
5370 src/test/test_rust.sh. This makes the working directory consistent
5371 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
5373 o Minor bugfixes (testing, bootstrap):
5374 - When calculating bootstrap progress, check exit policies and the
5375 exit flag. Previously, Tor would only check the exit flag, which
5376 caused race conditions in small and fast networks like chutney.
5377 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
5379 o Minor bugfixes (testing, openssl compatibility):
5380 - Our "tortls/cert_matches_key" unit test no longer relies on
5381 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5382 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5383 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5385 o Minor bugfixes (Windows, compilation):
5386 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5387 27185; bugfix on 0.2.2.2-alpha.
5390 Changes in version 0.3.4.6-rc - 2018-08-06
5391 Tor 0.3.4.6-rc fixes several small compilation, portability, and
5392 correctness issues in previous versions of Tor. This version is a
5393 release candidate: if no serious bugs are found, we expect that the
5394 stable 0.3.4 release will be (almost) the same as this release.
5396 o Major bugfixes (event scheduler):
5397 - When we enable a periodic event, schedule it in the event loop
5398 rather than running it immediately. Previously, we would re-run
5399 periodic events immediately in the middle of (for example)
5400 changing our options, with unpredictable effects. Fixes bug 27003;
5401 bugfix on 0.3.4.1-alpha.
5403 o Minor features (compilation):
5404 - When building Tor, prefer to use Python 3 over Python 2, and more
5405 recent (contemplated) versions over older ones. Closes
5407 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5408 tell the compiler not to include the system malloc implementation.
5409 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5410 - Don't try to use a pragma to temporarily disable the
5411 -Wunused-const-variable warning if the compiler doesn't support
5412 it. Fixes bug 26785; bugfix on 0.3.2.11.
5414 o Minor bugfixes (continuous integration):
5415 - Skip a pair of unreliable key generation tests on Windows, until
5416 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5417 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5419 o Minor features (controller):
5420 - The control port now exposes the list of HTTPTunnelPorts and
5421 ExtOrPorts via GETINFO net/listeners/httptunnel and
5422 net/listeners/extor respectively. Closes ticket 26647.
5424 o Minor bugfixes (directory authority):
5425 - When voting for recommended versions, make sure that all of the
5426 versions are well-formed and parsable. Fixes bug 26485; bugfix
5429 o Minor features (geoip):
5430 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
5431 Country database. Closes ticket 26674.
5433 o Minor features (Rust, portability):
5434 - Rust cross-compilation is now supported. Closes ticket 25895.
5436 o Minor bugfixes (compilation):
5437 - Update build system so that tor builds again with --disable-unittests
5438 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
5439 - Fix a compilation warning on some versions of GCC when building
5440 code that calls routerinfo_get_my_routerinfo() twice, assuming
5441 that the second call will succeed if the first one did. Fixes bug
5442 26269; bugfix on 0.2.8.2-alpha.
5444 o Minor bugfixes (controller):
5445 - Report the port correctly when a port is configured to bind to
5446 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
5447 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
5448 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
5449 on 0.3.3.1-alpha. Patch by "akwizgran".
5451 o Minor bugfixes (correctness, flow control):
5452 - Upon receiving a stream-level SENDME cell, verify that our window
5453 has not grown too large. Fixes bug 26214; bugfix on svn
5456 o Minor bugfixes (memory, correctness):
5457 - Fix a number of small memory leaks identified by coverity. Fixes
5458 bug 26467; bugfix on numerous Tor versions.
5460 o Minor bugfixes (logging):
5461 - Improve the log message when connection initiators fail to
5462 authenticate direct connections to relays. Fixes bug 26927; bugfix
5465 o Minor bugfixes (portability):
5466 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
5467 26994; bugfix on 0.3.4.1-alpha.
5468 - Work around two different bugs in the OS X 10.10 and later SDKs
5469 that would prevent us from successfully targeting earlier versions
5470 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
5472 o Minor bugfixes (single onion services, Tor2web):
5473 - Log a protocol warning when single onion services or Tor2web
5474 clients fail to authenticate direct connections to relays. Fixes
5475 bug 26924; bugfix on 0.2.9.1-alpha.
5477 o Minor bugfixes (testing):
5478 - Disable core dumps in test_bt.sh, to avoid failures in "make
5479 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5481 o Minor bugfixes (testing, compatibility):
5482 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
5483 only to pass strings (rather than "bytes" objects) to the Python
5484 subprocess module. Python 3 on Windows seems to require this.
5485 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
5486 0.3.1.1-alpha (for hs_ntor_ref.py).
5488 o Minor bugfixes (v3 onion services):
5489 - Stop sending ed25519 link specifiers in v3 onion service introduce
5490 cells and descriptors, when the rendezvous or introduction point
5491 doesn't support ed25519 link authentication. Fixes bug 26627;
5492 bugfix on 0.3.2.4-alpha.
5495 Changes in version 0.3.4.5-rc - 2018-07-13
5496 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
5497 bridge relays should upgrade.
5499 o Directory authority changes:
5500 - The "Bifroest" bridge authority has been retired; the new bridge
5501 authority is "Serge", and it is operated by George from the
5502 TorBSD project. Closes ticket 26771.
5505 Changes in version 0.3.3.9 - 2018-07-13
5506 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
5507 bridge relays should upgrade.
5509 o Directory authority changes:
5510 - The "Bifroest" bridge authority has been retired; the new bridge
5511 authority is "Serge", and it is operated by George from the
5512 TorBSD project. Closes ticket 26771.
5515 Changes in version 0.3.2.11 - 2018-07-13
5516 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
5517 bridge relays should upgrade. We also take this opportunity to backport
5520 o Directory authority changes:
5521 - The "Bifroest" bridge authority has been retired; the new bridge
5522 authority is "Serge", and it is operated by George from the
5523 TorBSD project. Closes ticket 26771.
5525 o Directory authority changes (backport from 0.3.3.7):
5526 - Add an IPv6 address for the "dannenberg" directory authority.
5527 Closes ticket 26343.
5529 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
5530 - When directory authorities read a zero-byte bandwidth file, they
5531 would previously log a warning with the contents of an
5532 uninitialised buffer. They now log a warning about the empty file
5533 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
5535 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
5536 - Correctly detect when onion services get disabled after HUP. Fixes
5537 bug 25761; bugfix on 0.3.2.1.
5539 o Minor features (sandbox, backport from 0.3.3.4-alpha):
5540 - Explicitly permit the poll() system call when the Linux
5541 seccomp2-based sandbox is enabled: apparently, some versions of
5542 libc use poll() when calling getpwnam(). Closes ticket 25313.
5544 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
5545 - Update the Travis CI configuration to use the stable Rust channel,
5546 now that we have decided to require that. Closes ticket 25714.
5548 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
5549 - Our .travis.yml configuration now includes support for testing the
5550 results of "make distcheck". (It's not uncommon for "make check"
5551 to pass but "make distcheck" to fail.) Closes ticket 25814.
5552 - Our Travis CI configuration now integrates with the Coveralls
5553 coverage analysis tool. Closes ticket 25818.
5555 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
5556 - Add several checks to detect whether Tor relays are uploading
5557 their descriptors without specifying why they regenerated them.
5558 Diagnostic for ticket 25686.
5560 o Minor features (compilation, backport from 0.3.4.4-rc):
5561 - When building Tor, prefer to use Python 3 over Python 2, and more
5562 recent (contemplated) versions over older ones. Closes
5565 o Minor features (geoip):
5566 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
5567 Country database. Closes ticket 26674.
5569 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
5570 - Upon receiving a malformed connected cell, stop processing the
5571 cell immediately. Previously we would mark the connection for
5572 close, but continue processing the cell as if the connection were
5573 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
5575 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
5576 - Allow the nanosleep() system call, which glibc uses to implement
5577 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
5579 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
5580 - When running the hs_ntor_ref.py test, make sure only to pass
5581 strings (rather than "bytes" objects) to the Python subprocess
5582 module. Python 3 on Windows seems to require this. Fixes bug
5583 26535; bugfix on 0.3.1.1-alpha.
5584 - When running the ntor_ref.py test, make sure only to pass strings
5585 (rather than "bytes" objects) to the Python subprocess module.
5586 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
5589 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
5590 - Work around a change in OpenSSL 1.1.1 where return values that
5591 would previously indicate "no password" now indicate an empty
5592 password. Without this workaround, Tor instances running with
5593 OpenSSL 1.1.1 would accept descriptors that other Tor instances
5594 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
5596 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
5597 - Document that the PerConnBW{Rate,Burst} options will fall back to
5598 their corresponding consensus parameters only if those parameters
5599 are set. Previously we had claimed that these values would always
5600 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
5602 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
5603 - Fix a compilation warning on some versions of GCC when building
5604 code that calls routerinfo_get_my_routerinfo() twice, assuming
5605 that the second call will succeed if the first one did. Fixes bug
5606 26269; bugfix on 0.2.8.2-alpha.
5608 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
5609 - Don't consider Tor running as a client if the ControlPort is open,
5610 but no actual client ports are open. Fixes bug 26062; bugfix
5613 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
5614 - Prevent a possible out-of-bounds smartlist read in
5615 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
5617 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
5618 - Fix a very unlikely (impossible, we believe) null pointer
5619 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
5620 Coverity; this is CID 1430932.
5622 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
5623 - Fix a memory leak when a v3 onion service is configured and gets a
5624 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
5625 - When parsing the descriptor signature, look for the token plus an
5626 extra white-space at the end. This is more correct but also will
5627 allow us to support new fields that might start with "signature".
5628 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
5630 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
5631 - Relays now correctly block attempts to re-extend to the previous
5632 relay by Ed25519 identity. Previously they would warn in this
5633 case, but not actually reject the attempt. Fixes bug 26158; bugfix
5636 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
5637 - Avoid a crash when running with DirPort set but ORPort turned off.
5638 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
5640 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
5641 - Silence unused-const-variable warnings in zstd.h with some GCC
5642 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
5644 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
5645 - Avoid intermittent test failures due to a test that had relied on
5646 onion service introduction point creation finishing within 5
5647 seconds of real clock time. Fixes bug 25450; bugfix
5650 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
5651 - Fix a C99 compliance issue in our configuration script that caused
5652 compilation issues when compiling Tor with certain versions of
5653 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
5655 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
5656 - Fix a number of small memory leaks identified by coverity. Fixes
5657 bug 26467; bugfix on numerous Tor versions.
5659 o Code simplification and refactoring (backport from 0.3.3.5-rc):
5660 - Move the list of default directory authorities to its own file.
5661 Closes ticket 24854. Patch by "beastr0".
5664 Changes in version 0.2.9.16 - 2018-07-13
5665 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
5666 bridge relays should upgrade. We also take this opportunity to backport
5669 o Directory authority changes:
5670 - The "Bifroest" bridge authority has been retired; the new bridge
5671 authority is "Serge", and it is operated by George from the
5672 TorBSD project. Closes ticket 26771.
5674 o Directory authority changes (backport from 0.3.3.7):
5675 - Add an IPv6 address for the "dannenberg" directory authority.
5676 Closes ticket 26343.
5678 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
5679 - When directory authorities read a zero-byte bandwidth file, they
5680 would previously log a warning with the contents of an
5681 uninitialised buffer. They now log a warning about the empty file
5682 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
5684 o Minor features (sandbox, backport from 0.3.3.4-alpha):
5685 - Explicitly permit the poll() system call when the Linux
5686 seccomp2-based sandbox is enabled: apparently, some versions of
5687 libc use poll() when calling getpwnam(). Closes ticket 25313.
5689 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
5690 - Our .travis.yml configuration now includes support for testing the
5691 results of "make distcheck". (It's not uncommon for "make check"
5692 to pass but "make distcheck" to fail.) Closes ticket 25814.
5693 - Our Travis CI configuration now integrates with the Coveralls
5694 coverage analysis tool. Closes ticket 25818.
5696 o Minor features (compilation, backport from 0.3.4.4-rc):
5697 - When building Tor, prefer to use Python 3 over Python 2, and more
5698 recent (contemplated) versions over older ones. Closes
5701 o Minor features (geoip):
5702 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
5703 Country database. Closes ticket 26674.
5705 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
5706 - Upon receiving a malformed connected cell, stop processing the
5707 cell immediately. Previously we would mark the connection for
5708 close, but continue processing the cell as if the connection were
5709 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
5711 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
5712 - Allow the nanosleep() system call, which glibc uses to implement
5713 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
5715 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
5716 - When running the ntor_ref.py test, make sure only to pass strings
5717 (rather than "bytes" objects) to the Python subprocess module.
5718 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
5721 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
5722 - Work around a change in OpenSSL 1.1.1 where return values that
5723 would previously indicate "no password" now indicate an empty
5724 password. Without this workaround, Tor instances running with
5725 OpenSSL 1.1.1 would accept descriptors that other Tor instances
5726 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
5728 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
5729 - Fix a compilation warning on some versions of GCC when building
5730 code that calls routerinfo_get_my_routerinfo() twice, assuming
5731 that the second call will succeed if the first one did. Fixes bug
5732 26269; bugfix on 0.2.8.2-alpha.
5734 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
5735 - Don't consider Tor running as a client if the ControlPort is open,
5736 but no actual client ports are open. Fixes bug 26062; bugfix
5739 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
5740 - Prevent a possible out-of-bounds smartlist read in
5741 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
5743 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
5744 - Fix a very unlikely (impossible, we believe) null pointer
5745 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
5746 Coverity; this is CID 1430932.
5748 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
5749 - Fix a number of small memory leaks identified by coverity. Fixes
5750 bug 26467; bugfix on numerous Tor versions.
5752 o Code simplification and refactoring (backport from 0.3.3.5-rc):
5753 - Move the list of default directory authorities to its own file.
5754 Closes ticket 24854. Patch by "beastr0".
5757 Changes in version 0.3.4.4-rc - 2018-07-09
5758 Tor 0.3.4.4-rc fixes several small compilation, portability, and
5759 correctness issues in previous versions of Tor. This version is a
5760 release candidate: if no serious bugs are found, we expect that the
5761 stable 0.3.4 release will be (almost) the same as this release.
5763 o Minor features (compilation):
5764 - When building Tor, prefer to use Python 3 over Python 2, and more
5765 recent (contemplated) versions over older ones. Closes
5768 o Minor features (geoip):
5769 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
5770 Country database. Closes ticket 26674.
5772 o Minor features (Rust, portability):
5773 - Rust cross-compilation is now supported. Closes ticket 25895.
5775 o Minor bugfixes (compilation):
5776 - Fix a compilation warning on some versions of GCC when building
5777 code that calls routerinfo_get_my_routerinfo() twice, assuming
5778 that the second call will succeed if the first one did. Fixes bug
5779 26269; bugfix on 0.2.8.2-alpha.
5781 o Minor bugfixes (control port):
5782 - Report the port correctly when a port is configured to bind to
5783 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
5784 - Handle the HSADDRESS= argument to the HSPOST command properly.
5785 (Previously, this argument was misparsed and thus ignored.) Fixes
5786 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
5788 o Minor bugfixes (correctness, flow control):
5789 - Upon receiving a stream-level SENDME cell, verify that our window
5790 has not grown too large. Fixes bug 26214; bugfix on svn
5793 o Minor bugfixes (memory, correctness):
5794 - Fix a number of small memory leaks identified by coverity. Fixes
5795 bug 26467; bugfix on numerous Tor versions.
5797 o Minor bugfixes (testing, compatibility):
5798 - When running the hs_ntor_ref.py test, make sure only to pass
5799 strings (rather than "bytes" objects) to the Python subprocess
5800 module. Python 3 on Windows seems to require this. Fixes bug
5801 26535; bugfix on 0.3.1.1-alpha.
5802 - When running the ntor_ref.py test, make sure only to pass strings
5803 (rather than "bytes" objects) to the Python subprocess module.
5804 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
5808 Changes in version 0.3.3.8 - 2018-07-09
5809 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
5810 fixes for a memory leak affecting directory authorities.
5812 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
5813 - Stop leaking memory on directory authorities when planning to
5814 vote. This bug was crashing authorities by exhausting their
5815 memory. Fixes bug 26435; bugfix on 0.3.3.6.
5817 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
5818 - Make sure that failing tests in Rust will actually cause the build
5819 to fail: previously, they were ignored. Fixes bug 26258; bugfix
5822 o Minor features (compilation, backport from 0.3.4.4-rc):
5823 - When building Tor, prefer to use Python 3 over Python 2, and more
5824 recent (contemplated) versions over older ones. Closes
5827 o Minor features (geoip):
5828 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
5829 Country database. Closes ticket 26674.
5831 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
5832 - Add several checks to detect whether Tor relays are uploading
5833 their descriptors without specifying why they regenerated them.
5834 Diagnostic for ticket 25686.
5836 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
5837 - Don't count path selection failures as circuit build failures.
5838 This change should eliminate cases where Tor blames its guard or
5839 the network for situations like insufficient microdescriptors
5840 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
5843 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
5844 - Fix a compilation warning on some versions of GCC when building
5845 code that calls routerinfo_get_my_routerinfo() twice, assuming
5846 that the second call will succeed if the first one did. Fixes bug
5847 26269; bugfix on 0.2.8.2-alpha.
5849 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
5850 - Handle the HSADDRESS= argument to the HSPOST command properly.
5851 (Previously, this argument was misparsed and thus ignored.) Fixes
5852 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
5854 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
5855 - Fix a number of small memory leaks identified by coverity. Fixes
5856 bug 26467; bugfix on numerous Tor versions.
5858 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
5859 - Relays now correctly block attempts to re-extend to the previous
5860 relay by Ed25519 identity. Previously they would warn in this
5861 case, but not actually reject the attempt. Fixes bug 26158; bugfix
5864 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
5865 - When shutting down, Tor now clears all the flags in the control.c
5866 module. This should prevent a bug where authentication cookies are
5867 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
5869 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
5870 - When running the hs_ntor_ref.py test, make sure only to pass
5871 strings (rather than "bytes" objects) to the Python subprocess
5872 module. Python 3 on Windows seems to require this. Fixes bug
5873 26535; bugfix on 0.3.1.1-alpha.
5874 - When running the ntor_ref.py test, make sure only to pass strings
5875 (rather than "bytes" objects) to the Python subprocess module.
5876 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
5880 Changes in version 0.3.4.3-alpha - 2018-06-26
5881 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
5882 one that was causing stability issues on directory authorities.
5884 o Major bugfixes (directory authority):
5885 - Stop leaking memory on directory authorities when planning to
5886 vote. This bug was crashing authorities by exhausting their
5887 memory. Fixes bug 26435; bugfix on 0.3.3.6.
5889 o Major bugfixes (rust, testing):
5890 - Make sure that failing tests in Rust will actually cause the build
5891 to fail: previously, they were ignored. Fixes bug 26258; bugfix
5894 o Minor feature (directory authorities):
5895 - Stop warning about incomplete bw lines before the first complete
5896 bw line has been found, so that additional header lines can be
5897 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
5899 o Minor features (relay, diagnostic):
5900 - Add several checks to detect whether Tor relays are uploading
5901 their descriptors without specifying why they regenerated them.
5902 Diagnostic for ticket 25686.
5904 o Minor features (unit tests):
5905 - Test complete bandwidth measurements files, and test that
5906 incomplete bandwidth lines only give warnings when the end of the
5907 header has not been detected. Fixes bug 25947; bugfix
5910 o Minor bugfixes (compilation):
5911 - Refrain from compiling unit testing related object files when
5912 --disable-unittests is set to configure script. Fixes bug 24891;
5913 bugfix on 0.2.5.1-alpha.
5914 - When linking the libtor_testing.a library, only include the
5915 dirauth object files once. Previously, they were getting added
5916 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
5917 - The --enable-fatal-warnings flag now affects Rust code as well.
5918 Closes ticket 26245.
5920 o Minor bugfixes (onion services):
5921 - Recompute some consensus information after detecting a clock jump,
5922 or after transitioning from a non-live consensus to a live
5923 consensus. We do this to avoid having an outdated state, and
5924 miscalculating the index for next-generation onion services. Fixes
5925 bug 24977; bugfix on 0.3.2.1-alpha.
5927 o Minor bugfixes (relay):
5928 - Relays now correctly block attempts to re-extend to the previous
5929 relay by Ed25519 identity. Previously they would warn in this
5930 case, but not actually reject the attempt. Fixes bug 26158; bugfix
5933 o Minor bugfixes (testing):
5934 - Fix compilation of the doctests in the Rust crypto crate. Fixes
5935 bug 26415; bugfix on 0.3.4.1-alpha.
5936 - Instead of trying to read the geoip configuration files from
5937 within the unit tests, instead create our own ersatz files with
5938 just enough geoip data in the format we expect. Trying to read
5939 from the source directory created problems on Windows with mingw,
5940 where the build system's paths are not the same as the platform's
5941 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
5942 - Refrain from trying to get an item from an empty smartlist in
5943 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
5944 to catch improper smartlist usage. Furthermore, enable
5945 DEBUG_SMARTLIST globally when build is configured with fragile
5946 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
5949 Changes in version 0.3.3.7 - 2018-06-12
5950 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
5951 fixes for bugs affecting compatibility and stability.
5953 o Directory authority changes:
5954 - Add an IPv6 address for the "dannenberg" directory authority.
5955 Closes ticket 26343.
5957 o Minor features (geoip):
5958 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
5959 Country database. Closes ticket 26351.
5961 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
5962 - Work around a change in OpenSSL 1.1.1 where return values that
5963 would previously indicate "no password" now indicate an empty
5964 password. Without this workaround, Tor instances running with
5965 OpenSSL 1.1.1 would accept descriptors that other Tor instances
5966 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
5968 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
5969 - Silence unused-const-variable warnings in zstd.h with some GCC
5970 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
5972 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
5973 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
5974 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
5975 miscounting the total number of circuits for these field values.)
5976 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
5978 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
5979 - Prevent a possible out-of-bounds smartlist read in
5980 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
5982 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
5983 - Only select relays when they have the descriptors we prefer to use
5984 for them. This change fixes a bug where we could select a relay
5985 because it had _some_ descriptor, but reject it later with a
5986 nonfatal assertion error because it didn't have the exact one we
5987 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
5990 Changes in version 0.3.4.2-alpha - 2018-06-12
5991 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
5992 release, and forward-ports an authority-only security fix from 0.3.3.6.
5994 o Directory authority changes:
5995 - Add an IPv6 address for the "dannenberg" directory authority.
5996 Closes ticket 26343.
5998 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
5999 - Fix a bug that could have allowed an attacker to force a directory
6000 authority to use up all its RAM by passing it a maliciously
6001 crafted protocol versions string. Fixes bug 25517; bugfix on
6002 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
6004 o Minor features (continuous integration):
6005 - Add the necessary configuration files for continuous integration
6006 testing on Windows, via the Appveyor platform. Closes ticket
6007 25549. Patches from Marcin Cieślak and Isis Lovecruft.
6009 o Minor features (geoip):
6010 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
6011 Country database. Closes ticket 26351.
6013 o Minor bugfixes (compatibility, openssl):
6014 - Work around a change in OpenSSL 1.1.1 where return values that
6015 would previously indicate "no password" now indicate an empty
6016 password. Without this workaround, Tor instances running with
6017 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6018 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6020 o Minor bugfixes (compilation):
6021 - Silence unused-const-variable warnings in zstd.h with some GCC
6022 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
6023 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
6024 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
6025 - Avoid a compiler warning when casting the return value of
6026 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
6027 26283; bugfix on 0.2.4.10-alpha.
6029 o Minor bugfixes (control port):
6030 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
6031 CIRC_BW events. Previously, such cells were counted entirely in
6032 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
6035 o Minor bugfixes (controller):
6036 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
6037 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
6038 miscounting the total number of circuits for these field values.)
6039 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
6041 o Minor bugfixes (hardening):
6042 - Prevent a possible out-of-bounds smartlist read in
6043 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6045 o Minor bugfixes (onion services):
6046 - Fix a bug that blocked the creation of ephemeral v3 onion
6047 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
6049 o Minor bugfixes (test coverage tools):
6050 - Update our "cov-diff" script to handle output from the latest
6051 version of gcov, and to remove extraneous timestamp information
6052 from its output. Fixes bugs 26101 and 26102; bugfix
6056 Changes in version 0.3.3.6 - 2018-05-22
6057 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
6058 backports several important fixes from the 0.3.4.1-alpha.
6060 The Tor 0.3.3 series includes controller support and other
6061 improvements for v3 onion services, official support for embedding Tor
6062 within other applications, and our first non-trivial module written in
6063 the Rust programming language. (Rust is still not enabled by default
6064 when building Tor.) And as usual, there are numerous other smaller
6065 bugfixes, features, and improvements.
6067 Below are the changes since 0.3.3.5-rc. For a list of all changes
6068 since 0.3.2.10, see the ReleaseNotes file.
6070 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
6071 - When directory authorities read a zero-byte bandwidth file, they
6072 would previously log a warning with the contents of an
6073 uninitialised buffer. They now log a warning about the empty file
6074 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6076 o Major bugfixes (security, directory authority, denial-of-service):
6077 - Fix a bug that could have allowed an attacker to force a directory
6078 authority to use up all its RAM by passing it a maliciously
6079 crafted protocol versions string. Fixes bug 25517; bugfix on
6080 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
6082 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
6083 - Avoid a rare assertion failure in the circuit build timeout code
6084 if we fail to allow any circuits to actually complete. Fixes bug
6085 25733; bugfix on 0.2.2.2-alpha.
6087 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6088 - Avoid a crash when testing router reachability on a router that
6089 could have an ed25519 ID, but which does not. Fixes bug 25415;
6090 bugfix on 0.3.3.2-alpha.
6092 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
6093 - Correctly detect when onion services get disabled after HUP. Fixes
6094 bug 25761; bugfix on 0.3.2.1.
6096 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
6097 - Impose a limit on circuit cell queue size. The limit can be
6098 controlled by a consensus parameter. Fixes bug 25226; bugfix
6101 o Minor features (compatibility, backport from 0.3.4.1-alpha):
6102 - Avoid some compilation warnings with recent versions of LibreSSL.
6103 Closes ticket 26006.
6105 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6106 - Our .travis.yml configuration now includes support for testing the
6107 results of "make distcheck". (It's not uncommon for "make check"
6108 to pass but "make distcheck" to fail.) Closes ticket 25814.
6109 - Our Travis CI configuration now integrates with the Coveralls
6110 coverage analysis tool. Closes ticket 25818.
6112 o Minor features (geoip):
6113 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
6114 database. Closes ticket 26104.
6116 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6117 - Don't consider Tor running as a client if the ControlPort is open,
6118 but no actual client ports are open. Fixes bug 26062; bugfix
6121 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6122 - Upon receiving a malformed connected cell, stop processing the
6123 cell immediately. Previously we would mark the connection for
6124 close, but continue processing the cell as if the connection were
6125 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6127 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
6128 - Stop saying in the manual that clients cache ipv4 dns answers from
6129 exit relays. We haven't used them since 0.2.6.3-alpha, and in
6130 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
6131 we forgot to say so in the man page. Fixes bug 26052; bugfix
6134 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6135 - Allow the nanosleep() system call, which glibc uses to implement
6136 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6138 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
6139 - Fix a memory leak when a v3 onion service is configured and gets a
6140 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
6141 - When parsing the descriptor signature, look for the token plus an
6142 extra white-space at the end. This is more correct but also will
6143 allow us to support new fields that might start with "signature".
6144 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
6146 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
6147 - Avoid a crash when running with DirPort set but ORPort turned off.
6148 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
6150 o Documentation (backport from 0.3.4.1-alpha):
6151 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
6152 ticket 25857. Patch from "CTassisF".
6155 Changes in version 0.3.4.1-alpha - 2018-05-17
6156 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
6157 includes refactoring to begin reducing Tor's binary size and idle CPU
6158 usage on mobile, along with prep work for new bandwidth scanners,
6159 improvements to the experimental "vanguards" feature, and numerous
6160 other small features and bugfixes.
6162 o New system requirements:
6163 - Tor no longer tries to support old operating systems without
6164 mmap() or some local equivalent. Apparently, compilation on such
6165 systems has been broken for some time, without anybody noticing or
6166 complaining. Closes ticket 25398.
6168 o Major feature (directory authority, modularization):
6169 - The directory authority subsystem has been modularized. The code
6170 is now located in src/or/dirauth/, and is compiled in by default.
6171 To disable the module, the configure option
6172 --disable-module-dirauth has been added. This module may be
6173 disabled by default in some future release. Closes ticket 25610.
6175 o Major features (main loop, CPU usage):
6176 - When Tor is disabled (via DisableNetwork or via hibernation), it
6177 no longer needs to run any per-second events. This change should
6178 make it easier for mobile applications to disable Tor while the
6179 device is sleeping, or Tor is not running. Closes ticket 26063.
6180 - Tor no longer enables all of its periodic events by default.
6181 Previously, Tor would enable all possible main loop events,
6182 regardless of whether it needed them. Furthermore, many of these
6183 events are now disabled with Tor is hibernating or DisableNetwork
6184 is set. This is a big step towards reducing client CPU usage by
6185 reducing the amount of wake-ups the daemon does. Closes ticket
6187 - The bandwidth-limitation logic has been refactored so that
6188 bandwidth calculations are performed on-demand, rather than every
6189 TokenBucketRefillInterval milliseconds. This change should improve
6190 the granularity of our bandwidth calculations, and limit the
6191 number of times that the Tor process needs to wake up when it is
6192 idle. Closes ticket 25373.
6193 - Move responsibility for many operations from a once-per-second
6194 callback to a callback that is only scheduled as needed. Moving
6195 this functionality has allowed us to disable the callback when
6196 Tor's network is disabled. Once enough items are removed from our
6197 once-per-second callback, we can eliminate it entirely to conserve
6198 CPU when idle. The functionality removed includes: closing
6199 connections, circuits, and channels (ticket 25932); consensus
6200 voting (25937); flushing log callbacks (25951); honoring delayed
6201 SIGNEWNYM requests (25949); rescanning the consensus cache
6202 (25931); saving the state file to disk (25948); warning relay
6203 operators about unreachable ports (25952); and keeping track of
6204 Tor's uptime (26009).
6206 o Major bugfixes (directory authorities, security):
6207 - When directory authorities read a zero-byte bandwidth file, they
6208 would previously log a warning with the contents of an
6209 uninitialised buffer. They now log a warning about the empty file
6210 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6212 o Major bugfixes (crash):
6213 - Avoid a rare assertion failure in the circuit build timeout code
6214 if we fail to allow any circuits to actually complete. Fixes bug
6215 25733; bugfix on 0.2.2.2-alpha.
6217 o Major bugfixes (directory authority):
6218 - Avoid a crash when testing router reachability on a router that
6219 could have an ed25519 ID, but which does not. Fixes bug 25415;
6220 bugfix on 0.3.3.2-alpha.
6222 o Major bugfixes (onion service):
6223 - Correctly detect when onion services get disabled after HUP. Fixes
6224 bug 25761; bugfix on 0.3.2.1.
6226 o Major bugfixes (protover, voting):
6227 - Revise Rust implementation of protover to use a more memory-
6228 efficient voting algorithm and corresponding data structures, thus
6229 avoiding a potential (but small impact) DoS attack where specially
6230 crafted protocol strings would expand to several potential
6231 megabytes in memory. In the process, several portions of code were
6232 revised to be methods on new, custom types, rather than functions
6233 taking interchangeable types, thus increasing type safety of the
6234 module. Custom error types and handling were added as well, in
6235 order to facilitate better error dismissal/handling in outside
6236 crates and avoid mistakenly passing an internal error string to C
6237 over the FFI boundary. Many tests were added, and some previous
6238 differences between the C and Rust implementations have been
6239 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
6241 o Major bugfixes (relay, denial of service):
6242 - Impose a limit on circuit cell queue size. The limit can be
6243 controlled by a consensus parameter. Fixes bug 25226; bugfix
6246 o Minor features (accounting):
6247 - When Tor becomes dormant, it now uses a scheduled event to wake up
6248 at the right time. Previously, we would use the per-second timer
6249 to check whether to wake up, but we no longer have any per-second
6250 timers enabled when the network is disabled. Closes ticket 26064.
6252 o Minor features (code quality):
6253 - Add optional spell-checking for the Tor codebase, using the
6254 "misspell" program. To use this feature, run "make check-typos".
6255 Closes ticket 25024.
6257 o Minor features (compatibility):
6258 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
6259 the no-deprecated option, and builds correctly with them. Closes
6260 tickets 19429, 19981, and 25353.
6261 - Avoid some compilation warnings with recent versions of LibreSSL.
6262 Closes ticket 26006.
6264 o Minor features (compression, zstd):
6265 - When running with zstd, Tor now considers using advanced functions
6266 that the zstd maintainers have labeled as potentially unstable. To
6267 prevent breakage, Tor will only use this functionality when the
6268 runtime version of the zstd library matches the version with which
6269 Tor was compiled. Closes ticket 25162.
6271 o Minor features (configuration):
6272 - The "DownloadSchedule" options have been renamed to end with
6273 "DownloadInitialDelay". The old names are still allowed, but will
6274 produce a warning. Comma-separated lists are still permitted for
6275 these options, but all values after the first are ignored (as they
6276 have been since 0.2.9). Closes ticket 23354.
6278 o Minor features (continuous integration):
6279 - Our .travis.yml configuration now includes support for testing the
6280 results of "make distcheck". (It's not uncommon for "make check"
6281 to pass but "make distcheck" to fail.) Closes ticket 25814.
6282 - Our Travis CI configuration now integrates with the Coveralls
6283 coverage analysis tool. Closes ticket 25818.
6285 o Minor features (control port):
6286 - Introduce GETINFO "current-time/{local,utc}" to return the local
6287 and UTC times respectively in ISO format. This helps a controller
6288 like Tor Browser detect a time-related error. Closes ticket 25511.
6289 Patch by Neel Chauhan.
6290 - Introduce new fields to the CIRC_BW event. There are two new
6291 fields in each of the read and written directions. The DELIVERED
6292 fields report the total valid data on the circuit, as measured by
6293 the payload sizes of verified and error-checked relay command
6294 cells. The OVERHEAD fields report the total unused bytes in each
6295 of these cells. Closes ticket 25903.
6297 o Minor features (directory authority):
6298 - Directory authorities now open their key-pinning files as O_SYNC,
6299 to limit their chances of accidentally writing partial lines.
6300 Closes ticket 23909.
6302 o Minor features (directory authority, forward compatibility):
6303 - Make the lines of the measured bandwidth file able to contain
6304 their entries in any order. Previously, the node_id entry needed
6305 to come first. Closes ticket 26004.
6307 o Minor features (entry guards):
6308 - Introduce a new torrc option NumPrimaryGuards for controlling the
6309 number of primary guards. Closes ticket 25843.
6311 o Minor features (geoip):
6312 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
6313 database. Closes ticket 26104.
6315 o Minor features (performance):
6316 - Avoid a needless call to malloc() when processing an incoming
6317 relay cell. Closes ticket 24914.
6318 - Make our timing-wheel code run a tiny bit faster on 32-bit
6319 platforms, by preferring 32-bit math to 64-bit. Closes
6321 - Avoid a needless malloc()/free() pair every time we handle an ntor
6322 handshake. Closes ticket 25150.
6324 o Minor features (testing):
6325 - Add a unit test for voting_schedule_get_start_of_next_interval().
6326 Closes ticket 26014, and helps make unit test coverage
6328 - A new unittests module specifically for testing the functions in
6329 the (new-ish) bridges.c module has been created with new
6330 unittests, raising the code coverage percentages. Closes 25425.
6331 - We now have improved testing for addressmap_get_virtual_address()
6332 function. This should improve our test coverage, and make our test
6333 coverage more deterministic. Closes ticket 25993.
6335 o Minor features (timekeeping, circuit scheduling):
6336 - When keeping track of how busy each circuit have been recently on
6337 a given connection, use coarse-grained monotonic timers rather
6338 than gettimeofday(). This change should marginally increase
6339 accuracy and performance. Implements part of ticket 25927.
6341 o Minor bugfixes (bandwidth management):
6342 - Consider ourselves "low on write bandwidth" if we have exhausted
6343 our write bandwidth some time in the last second. This was the
6344 documented behavior before, but the actual behavior was to change
6345 this value every TokenBucketRefillInterval. Fixes bug 25828;
6346 bugfix on 0.2.3.5-alpha.
6348 o Minor bugfixes (C correctness):
6349 - Add a missing lock acquisition in the shutdown code of the control
6350 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
6351 Coverity; this is CID 1433643.
6353 o Minor bugfixes (circuit path selection):
6354 - Don't count path selection failures as circuit build failures.
6355 This change should eliminate cases where Tor blames its guard or
6356 the network for situations like insufficient microdescriptors
6357 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
6360 o Minor bugfixes (client):
6361 - Don't consider Tor running as a client if the ControlPort is open,
6362 but no actual client ports are open. Fixes bug 26062; bugfix
6365 o Minor bugfixes (code style):
6366 - Fixed multiple includes of transports.h in src/or/connection.c
6367 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
6368 - Remove the unused variable n_possible from the function
6369 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
6371 o Minor bugfixes (control interface):
6372 - Respond with more human-readable error messages to GETINFO exit-
6373 policy/* requests. Also, let controller know if an error is
6374 transient (response code 551) or not (response code 552). Fixes
6375 bug 25852; bugfix on 0.2.8.1-alpha.
6377 o Minor bugfixes (controller):
6378 - Make CIRC_BW event reflect the total of all data sent on a
6379 circuit, including padding and dropped cells. Also fix a mis-
6380 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
6381 bugfix on 0.2.5.2-alpha.
6383 o Minor bugfixes (correctness, client):
6384 - Upon receiving a malformed connected cell, stop processing the cell
6385 immediately. Previously we would mark the connection for close, but
6386 continue processing the cell as if the connection were open. Fixes bug
6387 26072; bugfix on 0.2.4.7-alpha.
6389 o Minor bugfixes (directory client):
6390 - When unverified-consensus is verified, rename it to cached-
6391 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
6392 - Fixed launching a certificate fetch always during the scheduled
6393 periodic consensus fetch by fetching only in those cases when
6394 consensus are waiting for certs. Fixes bug 24740; bugfix
6397 o Minor bugfixes (documentation):
6398 - Stop saying in the manual that clients cache ipv4 dns answers from
6399 exit relays. We haven't used them since 0.2.6.3-alpha, and in
6400 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
6401 we forgot to say so in the man page. Fixes bug 26052; bugfix
6404 o Minor bugfixes (error reporting):
6405 - Improve tolerance for directory authorities with skewed clocks.
6406 Previously, an authority with a clock more than 60 seconds ahead
6407 could cause a client with a correct clock to warn that the
6408 client's clock was behind. Now the clocks of a majority of
6409 directory authorities have to be ahead of the client before this
6410 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
6412 o Minor bugfixes (Linux seccomp2 sandbox):
6413 - Allow the nanosleep() system call, which glibc uses to implement
6414 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6416 o Minor bugfixes (onion service):
6417 - Fix a memory leak when a v3 onion service is configured and gets a
6418 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
6419 - When parsing the descriptor signature, look for the token plus an
6420 extra white-space at the end. This is more correct but also will
6421 allow us to support new fields that might start with "signature".
6422 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
6424 o Minor bugfixes (path selection):
6425 - Only select relays when they have the descriptors we prefer to use
6426 for them. This change fixes a bug where we could select a relay
6427 because it had _some_ descriptor, but reject it later with a
6428 nonfatal assertion error because it didn't have the exact one we
6429 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
6431 o Minor bugfixes (portability):
6432 - Do not align mmap length, as it is not required by POSIX, and the
6433 getpagesize function is deprecated. Fixes bug 25399; bugfix
6436 o Minor bugfixes (portability, FreeBSD):
6437 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
6438 does not stringify on FreeBSD, so we switch to tor_asprintf().
6439 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
6441 o Minor bugfixes (relay statistics):
6442 - When a relay is collecting internal statistics about how many
6443 create cell requests it has seen of each type, accurately count
6444 the requests from relays that temporarily fall out of the
6445 consensus. (To be extra conservative, we were already ignoring
6446 requests from clients in our counts, and we continue ignoring them
6447 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
6449 o Minor bugfixes (relay, crash):
6450 - Avoid a crash when running with DirPort set but ORPort turned off.
6451 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
6453 o Minor bugfixes (restart-in-process):
6454 - When shutting down, Tor now clears all the flags in the control.c
6455 module. This should prevent a bug where authentication cookies are
6456 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
6458 o Minor bugfixes (testing):
6459 - When testing workqueue event-cancellation, make sure that we
6460 actually cancel an event, and that cancel each event with equal
6461 probability. (It was previously possible, though extremely
6462 unlikely, for our event-canceling test not to cancel any events.)
6463 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
6464 - Repeat part of the test in test_client_pick_intro() a number of
6465 times, to give it consistent coverage. Fixes bug 25996; bugfix
6467 - Remove randomness from the hs_common/responsible_hsdirs test, so
6468 that it always takes the same path through the function it tests.
6469 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
6470 - Change the behavior of the "channel/outbound" test so that it
6471 never causes a 10-second rollover for the EWMA circuitmux code.
6472 Previously, this behavior would happen randomly, and result in
6473 fluctuating test coverage. Fixes bug 25994; bugfix
6475 - Use X509_new() to allocate certificates that will be freed later
6476 with X509_free(). Previously, some parts of the unit tests had
6477 used tor_malloc_zero(), which is incorrect, and which caused test
6478 failures on Windows when they were built with extra hardening.
6479 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
6481 - While running the circuit_timeout test, fix the PRNG to a
6482 deterministic AES stream, so that the test coverage from this test
6483 will itself be deterministic. Fixes bug 25995; bugfix
6486 o Minor bugfixes (vanguards):
6487 - Allow the last hop in a vanguard circuit to be the same as our
6488 first, to prevent the adversary from influencing guard node choice
6489 by choice of last hop. Also prevent the creation of A - B - A
6490 paths, or A - A paths, which are forbidden by relays. Fixes bug
6491 25870; bugfix on 0.3.3.1-alpha.
6493 o Code simplification and refactoring:
6494 - Remove duplicate code in parse_{c,s}method_line and bootstrap
6495 their functionalities into a single function. Fixes bug 6236;
6496 bugfix on 0.2.3.6-alpha.
6497 - We remove the PortForwarding and PortForwardingHelper options,
6498 related functions, and the port_forwarding tests. These options
6499 were used by the now-deprecated Vidalia to help ordinary users
6500 become Tor relays or bridges. Closes ticket 25409. Patch by
6502 - In order to make the OR and dir checking function in router.c less
6503 confusing we renamed some functions and
6504 consider_testing_reachability() has been split into
6505 router_should_check_reachability() and
6506 router_do_reachability_checks(). Also we improved the documentation
6507 in some functions. Closes ticket 18918.
6508 - Initial work to isolate Libevent usage to a handful of modules in
6509 our codebase, to simplify our call structure, and so that we can
6510 more easily change event loops in the future if needed. Closes
6512 - Introduce a function to call getsockname() and return tor_addr_t,
6513 to save a little complexity throughout the codebase. Closes
6515 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
6516 as hsdir_index is always present. Also, we move hsdir_index_t into
6517 or.h. Closes ticket 23094. Patch by Neel Chauhan.
6518 - Merge functions used for describing nodes and suppress the
6519 functions that do not allocate memory for the output buffer
6520 string. NODE_DESC_BUF_LEN constant and format_node_description()
6521 function cannot be used externally from router.c module anymore.
6522 Closes ticket 25432. Patch by valentecaio.
6523 - Our main loop has been simplified so that all important operations
6524 happen inside events. Previously, some operations had to happen
6525 outside the event loop, to prevent infinite sequences of event
6526 activations. Closes ticket 25374.
6527 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
6528 it in register_intro_circ() and service_intro_point_new(). This
6529 prevents the digest from being re-calculated each time. Closes
6530 ticket 23107. Patch by Neel Chauhan.
6531 - Refactor token-bucket implementations to use a common backend.
6532 Closes ticket 25766.
6533 - Remove extern declaration of stats_n_seconds_working variable from
6534 main, protecting its accesses with get_uptime() and reset_uptime()
6535 functions. Closes ticket 25081, patch by “valentecaio”.
6536 - Remove our previous logic for "cached gettimeofday()" -- our
6537 coarse monotonic timers are fast enough for this purpose, and far
6538 less error-prone. Implements part of ticket 25927.
6539 - Remove the return value for fascist_firewall_choose_address_base(),
6540 and sister functions such as fascist_firewall_choose_address_node()
6541 and fascist_firewall_choose_address_rs(). Also, while we're here,
6542 initialize the ap argument as leaving it uninitialized can pose a
6543 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
6544 - Rename two fields of connection_t struct. timestamp_lastwritten is
6545 renamed to timestamp_last_write_allowed and timestamp_lastread is
6546 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
6548 - Since Tor requires C99, remove our old workaround code for libc
6549 implementations where free(NULL) doesn't work. Closes ticket 24484.
6550 - Use our standard rate-limiting code to deal with excessive
6551 libevent failures, rather than the hand-rolled logic we had
6552 before. Closes ticket 26016.
6553 - We remove the return value of node_get_prim_orport() and
6554 node_get_prim_dirport(), and introduce node_get_prim_orport() in
6555 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
6556 check for a null address. Closes ticket 23873. Patch by
6558 - We switch to should_record_bridge_info() in
6559 geoip_note_client_seen() and options_need_geoip_info() instead of
6560 accessing the configuration values directly. Fixes bug 25290;
6561 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
6563 o Deprecated features:
6564 - As we are not recommending 0.2.5 anymore, we require relays that
6565 once had an ed25519 key associated with their RSA key to always
6566 have that key, instead of allowing them to drop back to a version
6567 that didn't support ed25519. This means they need to use a new RSA
6568 key if they want to downgrade to an older version of tor without
6569 ed25519. Closes ticket 20522.
6572 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
6573 ticket 25857. Patch from "CTassisF".
6576 - Directory authorities will no longer support voting according to
6577 any consensus method before consensus method 25. This keeps
6578 authorities compatible with all authorities running 0.2.9.8 and
6579 later, and does not break any clients or relays. Implements ticket
6580 24378 and proposal 290.
6581 - The PortForwarding and PortForwardingHelper features have been
6582 removed. The reasoning is, given that implementations of NAT
6583 traversal protocols within common consumer grade routers are
6584 frequently buggy, and that the target audience for a NAT punching
6585 feature is a perhaps less-technically-inclined relay operator,
6586 when the helper fails to setup traversal the problems are usually
6587 deep, ugly, and very router specific, making them horrendously
6588 impossible for technical support to reliable assist with, and thus
6589 resulting in frustration all around. Unfortunately, relay
6590 operators who would like to run relays behind NATs will need to
6591 become more familiar with the port forwarding configurations on
6592 their local router. Closes 25409.
6593 - The TestingEnableTbEmptyEvent option has been removed. It was used
6594 in testing simulations to measure how often connection buckets
6595 were emptied, in order to improve our scheduling, but it has not
6596 been actively used in years. Closes ticket 25760.
6597 - The old "round-robin" circuit multiplexer (circuitmux)
6598 implementation has been removed, along with a fairly large set of
6599 code that existed to support it. It has not been the default
6600 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
6601 but it still required an unreasonable amount of memory and CPU.
6602 Closes ticket 25268.
6605 Changes in version 0.3.3.5-rc - 2018-04-15
6606 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
6607 including some that could affect reliability or correctness.
6609 This is the first release candidate in the 0.3.3 series. If we find no
6610 new bugs or regression here, then the first stable 0.3.3 release will
6611 be nearly identical to this one.
6613 o Major bugfixes (security, protover, voting):
6614 - Revise Rust implementation of protover to use a more memory-
6615 efficient voting algorithm and corresponding data structures, thus
6616 avoiding a potential memory-based DoS attack where specially
6617 crafted protocol strings would expand to fill available memory.
6618 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
6620 o Major bugfixes (performance, load balancing):
6621 - Directory authorities no longer vote in favor of the Guard flag
6622 for relays without directory support. Starting in Tor
6623 0.3.0.1-alpha, clients have been avoiding using such relays in the
6624 Guard position, leading to increasingly broken load balancing for
6625 the 5%-or-so of Guards that don't advertise directory support.
6626 Fixes bug 22310; bugfix on 0.3.0.6.
6628 o Minor feature (continuous integration):
6629 - Update the Travis CI configuration to use the stable Rust channel,
6630 now that we have decided to require that. Closes ticket 25714.
6632 o Minor features (config options):
6633 - Change the way the default value for MaxMemInQueues is calculated.
6634 We now use 40% of the hardware RAM if the system has 8 GB RAM or
6635 more. Otherwise we use the former value of 75%. Closes
6638 o Minor features (geoip):
6639 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
6640 Country database. Closes ticket 25718.
6642 o Minor bugfixes (client):
6643 - When using a listed relay as a bridge, and also using
6644 microdescriptors, and considering that relay as a non-bridge in a
6645 circuit, treat its microdescriptor as a valid source of
6646 information about that relay. This change should prevent a non-
6647 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
6649 o Minor bugfixes (controller):
6650 - Restore the correct operation of the RESOLVE command, which had
6651 been broken since we added the ability to enable/disable DNS on
6652 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
6654 o Minor bugfixes (distribution, compilation, rust):
6655 - Build correctly when the rust dependencies submodule is loaded,
6656 but the TOR_RUST_DEPENDENCIES environment variable is not set.
6657 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
6658 - Actually include all of our Rust source in our source
6659 distributions. (Previously, a few of the files were accidentally
6660 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
6662 o Minor bugfixes (documentation):
6663 - Document that the PerConnBW{Rate,Burst} options will fall back to
6664 their corresponding consensus parameters only if those parameters
6665 are set. Previously we had claimed that these values would always
6666 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
6667 - Revert a misformatting issue in the ExitPolicy documentation.
6668 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
6670 o Minor bugfixes (exit relay DNS retries):
6671 - Re-attempt timed-out DNS queries 3 times before failure, since our
6672 timeout is 5 seconds for them, but clients wait 10-15. Also allow
6673 slightly more timeouts per resolver when an exit has multiple
6674 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
6676 o Minor bugfixes (onion services):
6677 - Re-instate counting the client HSDir fetch circuits against the
6678 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
6680 - Remove underscores from the _HSLayer{2,3}Nodes options. This
6681 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
6682 Fixes bug 25581; bugfix on 0.3.3.1-alpha
6684 o Code simplification and refactoring:
6685 - Move the list of default directory authorities to its own file.
6686 Closes ticket 24854. Patch by "beastr0".
6688 o Documentation (manpage, denial of service):
6689 - Provide more detail about the denial-of-service options, by
6690 listing each mitigation and explaining how they relate. Closes
6694 Changes in version 0.3.3.4-alpha - 2018-03-29
6695 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
6696 the alpha testing of earlier releases in its series. We are
6697 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
6699 o New system requirements:
6700 - When built with Rust, Tor now depends on version 0.2.39 of the
6701 libc crate. Closes tickets 25310 and 25664.
6703 o Major bugfixes (relay, connection):
6704 - If we have failed to connect to a relay and received a connection
6705 refused, timeout, or similar error (at the TCP level), do not try
6706 that same address/port again for 60 seconds after the failure has
6707 occurred. Fixes bug 24767; bugfix on 0.0.6.
6709 o Minor features (geoip):
6710 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
6711 Country database. Closes ticket 25469.
6713 o Minor features (log messages):
6714 - Improve log message in the out-of-memory handler to include
6715 information about memory usage from the different compression
6716 backends. Closes ticket 25372.
6718 o Minor features (sandbox):
6719 - Explicitly permit the poll() system call when the Linux
6720 seccomp2-based sandbox is enabled: apparently, some versions of
6721 libc use poll() when calling getpwnam(). Closes ticket 25313.
6723 o Minor bugfixes (C correctness):
6724 - Fix a very unlikely (impossible, we believe) null pointer
6725 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6726 Coverity; this is CID 1430932.
6728 o Minor bugfixes (channel, client):
6729 - Better identify client connection when reporting to the geoip
6730 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
6732 o Minor bugfixes (compilation):
6733 - Fix a C99 compliance issue in our configuration script that caused
6734 compilation issues when compiling Tor with certain versions of
6735 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
6737 o Minor bugfixes (controller, reliability):
6738 - Avoid a (nonfatal) assertion failure when extending a one-hop
6739 circuit from the controller to become a multihop circuit. Fixes
6740 bug 24903; bugfix on 0.2.5.2-alpha.
6742 o Major bugfixes (networking):
6743 - Tor will no longer reject IPv6 address strings from Tor Browser
6744 when they are passed as hostnames in SOCKS5 requests. Fixes bug
6745 25036, bugfix on Tor 0.3.1.2.
6747 o Minor bugfixes (networking):
6748 - string_is_valid_hostname() will not consider IP strings to be
6749 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
6751 o Minor bugfixes (onion service v3):
6752 - Avoid an assertion failure when the next onion service
6753 descriptor rotation type is out of sync with the consensus's
6754 valid-after time. Instead, log a warning message with extra
6755 information, so we can better hunt down the cause of this
6756 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
6758 o Minor bugfixes (testing):
6759 - Avoid intermittent test failures due to a test that had relied on
6760 onion service introduction point creation finishing within 5
6761 seconds of real clock time. Fixes bug 25450; bugfix
6763 - Rust crates are now automatically detected and tested. Previously,
6764 some crates were not tested by `make test-rust` due to a static
6765 string in the `src/test/test_rust.sh` script specifying which
6766 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
6768 o Minor bugfixes (testing, benchmarks):
6769 - Fix a crash when running benchmark tests on win32 systems. The
6770 crash was due to a mutex that wasn't initialized before logging
6771 and options were initialized. Fixes bug 25479; bugfix
6774 o Minor bugfixes (warnings, ipv6):
6775 - Avoid a bug warning that could occur when trying to connect to a
6776 relay over IPv6. This warning would occur on a Tor instance that
6777 downloads router descriptors, but prefers to use microdescriptors.
6778 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
6780 o Code simplification and refactoring:
6781 - Remove the old (deterministic) directory retry logic entirely:
6782 We've used exponential backoff exclusively for some time. Closes
6786 - Improved the documentation of AccountingStart parameter. Closes
6788 - Update the documentation for "Log" to include the current list of
6789 logging domains. Closes ticket 25378.
6792 Changes in version 0.3.1.10 - 2018-03-03
6793 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
6796 It includes an important security fix for a remote crash attack
6797 against directory authorities, tracked as TROVE-2018-001.
6799 This release also backports our new system for improved resistance to
6800 denial-of-service attacks against relays.
6802 This release also fixes several minor bugs and annoyances from
6805 All directory authorities should upgrade to one of the versions
6806 released today. Relays running 0.3.1.x may wish to update to one of
6807 the versions released today, for the DoS mitigations.
6809 Please note: according to our release calendar, Tor 0.3.1 will no
6810 longer be supported after 1 July 2018. If you will be running Tor
6811 after that date, you should make sure to plan to upgrade to the latest
6812 stable version, or downgrade to 0.2.9 (which will receive long-term
6815 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
6816 - Fix a protocol-list handling bug that could be used to remotely crash
6817 directory authorities with a null-pointer exception. Fixes bug 25074;
6818 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
6821 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
6822 - Give relays some defenses against the recent network overload. We
6823 start with three defenses (default parameters in parentheses).
6824 First: if a single client address makes too many concurrent
6825 connections (>100), hang up on further connections. Second: if a
6826 single client address makes circuits too quickly (more than 3 per
6827 second, with an allowed burst of 90) while also having too many
6828 connections open (3), refuse new create cells for the next while
6829 (1-2 hours). Third: if a client asks to establish a rendezvous
6830 point to you directly, ignore the request. These defenses can be
6831 manually controlled by new torrc options, but relays will also
6832 take guidance from consensus parameters, so there's no need to
6833 configure anything manually. Implements ticket 24902.
6835 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
6836 - Update the sandbox rules so that they should now work correctly
6837 with Glibc 2.26. Closes ticket 24315.
6839 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
6840 - Fix an "off by 2" error in counting rendezvous failures on the
6841 onion service side. While we thought we would stop the rendezvous
6842 attempt after one failed circuit, we were actually making three
6843 circuit attempts before giving up. Now switch to a default of 2,
6844 and allow the consensus parameter "hs_service_max_rdv_failures" to
6845 override. Fixes bug 24895; bugfix on 0.0.6.
6847 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
6848 - Add Link protocol version 5 to the supported protocols list. Fixes
6849 bug 25070; bugfix on 0.3.1.1-alpha.
6851 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
6852 - Fix a set of false positives where relays would consider
6853 connections to other relays as being client-only connections (and
6854 thus e.g. deserving different link padding schemes) if those
6855 relays fell out of the consensus briefly. Now we look only at the
6856 initial handshake and whether the connection authenticated as a
6857 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
6859 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
6860 - Make our OOM handler aware of the geoip client history cache so it
6861 doesn't fill up the memory. This check is important for IPv6 and
6862 our DoS mitigation subsystem. Closes ticket 25122.
6864 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
6865 - Change relay bandwidth reporting stats interval from 4 hours to 24
6866 hours in order to reduce the efficiency of guard discovery
6867 attacks. Fixes ticket 23856.
6869 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
6870 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
6871 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
6872 since they neither disabled TLS 1.3 nor enabled any of the
6873 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
6874 Closes ticket 24978.
6876 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
6877 - The fallback directory list has been re-generated based on the
6878 current status of the network. Tor uses fallback directories to
6879 bootstrap when it doesn't yet have up-to-date directory
6880 information. Closes ticket 24801.
6881 - Make the default DirAuthorityFallbackRate 0.1, so that clients
6882 prefer to bootstrap from fallback directory mirrors. This is a
6883 follow-up to 24679, which removed weights from the default
6884 fallbacks. Implements ticket 24681.
6886 o Minor features (geoip):
6887 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
6890 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
6891 - Use the actual observed address of an incoming relay connection,
6892 not the canonical address of the relay from its descriptor, when
6893 making decisions about how to handle the incoming connection.
6894 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
6896 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
6897 - Directory authorities, when refusing a descriptor from a rejected
6898 relay, now explicitly tell the relay (in its logs) to set a valid
6899 ContactInfo address and contact the bad-relays@ mailing list.
6900 Fixes bug 25170; bugfix on 0.2.9.1.
6902 o Minor bugfixes (address selection, backport from 0.3.2.9):
6903 - When the fascist_firewall_choose_address_ functions don't find a
6904 reachable address, set the returned address to the null address
6905 and port. This is a precautionary measure, because some callers do
6906 not check the return value. Fixes bug 24736; bugfix
6909 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
6910 - Fetch descriptors aggressively whenever we lack enough to build
6911 circuits, regardless of how many descriptors we are missing.
6912 Previously, we would delay launching the fetch when we had fewer
6913 than 15 missing descriptors, even if some of those descriptors
6914 were blocking circuits from building. Fixes bug 23985; bugfix on
6915 0.1.1.11-alpha. The effects of this bug became worse in
6916 0.3.0.3-alpha, when we began treating missing descriptors from our
6917 primary guards as a reason to delay circuits.
6918 - Don't try fetching microdescriptors from relays that have failed
6919 to deliver them in the past. Fixes bug 23817; bugfix
6922 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
6923 - Fix a signed/unsigned comparison warning introduced by our fix to
6924 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
6926 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
6927 - Avoid a crash when attempting to use the seccomp2 sandbox together
6928 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
6931 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
6932 - Fix a possible crash on malformed consensus. If a consensus had
6933 contained an unparseable protocol line, it could have made clients
6934 and relays crash with a null-pointer exception. To exploit this
6935 issue, however, an attacker would need to be able to subvert the
6936 directory authority system. Fixes bug 25251; bugfix on
6937 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
6939 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
6940 - Recover better from empty or corrupt files in the consensus cache
6941 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
6942 - When a consensus diff calculation is only partially successful,
6943 only record the successful parts as having succeeded. Partial
6944 success can happen if (for example) one compression method fails
6945 but the others succeed. Previously we misrecorded all the
6946 calculations as having succeeded, which would later cause a
6947 nonfatal assertion failure. Fixes bug 24086; bugfix
6950 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
6951 - Tor now updates its guard state when it reads a consensus
6952 regardless of whether it's missing descriptors. That makes tor use
6953 its primary guards to fetch descriptors in some edge cases where
6954 it would previously have used fallback directories. Fixes bug
6955 23862; bugfix on 0.3.0.1-alpha.
6957 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
6958 - Don't treat inability to store a cached consensus object as a bug:
6959 it can happen normally when we are out of disk space. Fixes bug
6960 24859; bugfix on 0.3.1.1-alpha.
6962 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
6963 - When queuing DESTROY cells on a channel, only queue the circuit-id
6964 and reason fields: not the entire 514-byte cell. This fix should
6965 help mitigate any bugs or attacks that fill up these queues, and
6966 free more RAM for other uses. Fixes bug 24666; bugfix
6969 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
6970 - When closing a connection via close_connection_immediately(), we
6971 mark it as "not blocked on bandwidth", to prevent later calls from
6972 trying to unblock it, and give it permission to read. This fixes a
6973 backtrace warning that can happen on relays under various
6974 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
6976 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
6977 - When selecting relays by bandwidth, avoid a rounding error that
6978 could sometimes cause load to be imbalanced incorrectly.
6979 Previously, we would always round upwards; now, we round towards
6980 the nearest integer. This had the biggest effect when a relay's
6981 weight adjustments should have given it weight 0, but it got
6982 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
6983 - When calculating the fraction of nodes that have descriptors, and
6984 all nodes in the network have zero bandwidths, count the number of
6985 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
6986 - Actually log the total bandwidth in compute_weighted_bandwidths().
6987 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
6989 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
6990 - Improve the performance of our consensus-diff application code
6991 when Tor is built with the --enable-fragile-hardening option set.
6992 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
6994 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
6995 - Don't exit the Tor process if setrlimit() fails to change the file
6996 limit (which can happen sometimes on some versions of OSX). Fixes
6997 bug 21074; bugfix on 0.0.9pre5.
6999 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
7000 - Fix a bug in the bit-counting parts of our timing-wheel code on
7001 MSVC. (Note that MSVC is still not a supported build platform, due
7002 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
7005 o Minor bugfixes (relay, partial backport):
7006 - Make the internal channel_is_client() function look at what sort
7007 of connection handshake the other side used, rather than whether
7008 the other side ever sent a create_fast cell to us. Backports part
7009 of the fixes from bugs 22805 and 24898.
7011 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
7012 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
7014 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
7015 bugfix on 0.2.9.4-alpha.
7017 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
7018 - Update the "rust dependencies" submodule to be a project-level
7019 repository, rather than a user repository. Closes ticket 25323.
7022 Changes in version 0.2.9.15 - 2018-03-03
7023 Tor 0.2.9.15 backports important security and stability bugfixes from
7026 It includes an important security fix for a remote crash attack
7027 against directory authorities, tracked as TROVE-2018-001.
7029 This release also backports our new system for improved resistance to
7030 denial-of-service attacks against relays.
7032 This release also fixes several minor bugs and annoyances from
7035 All directory authorities should upgrade to one of the versions
7036 released today. Relays running 0.2.9.x may wish to update to one of
7037 the versions released today, for the DoS mitigations.
7039 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7040 - Fix a protocol-list handling bug that could be used to remotely crash
7041 directory authorities with a null-pointer exception. Fixes bug 25074;
7042 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7045 o Major features (denial-of-service mitigation):
7046 - Give relays some defenses against the recent network overload. We
7047 start with three defenses (default parameters in parentheses).
7048 First: if a single client address makes too many concurrent
7049 connections (>100), hang up on further connections. Second: if a
7050 single client address makes circuits too quickly (more than 3 per
7051 second, with an allowed burst of 90) while also having too many
7052 connections open (3), refuse new create cells for the next while
7053 (1-2 hours). Third: if a client asks to establish a rendezvous
7054 point to you directly, ignore the request. These defenses can be
7055 manually controlled by new torrc options, but relays will also
7056 take guidance from consensus parameters, so there's no need to
7057 configure anything manually. Implements ticket 24902.
7059 o Major bugfixes (bootstrapping):
7060 - Fetch descriptors aggressively whenever we lack enough to build
7061 circuits, regardless of how many descriptors we are missing.
7062 Previously, we would delay launching the fetch when we had fewer
7063 than 15 missing descriptors, even if some of those descriptors
7064 were blocking circuits from building. Fixes bug 23985; bugfix on
7065 0.1.1.11-alpha. The effects of this bug became worse in
7066 0.3.0.3-alpha, when we began treating missing descriptors from our
7067 primary guards as a reason to delay circuits.
7069 o Major bugfixes (onion services, retry behavior):
7070 - Fix an "off by 2" error in counting rendezvous failures on the
7071 onion service side. While we thought we would stop the rendezvous
7072 attempt after one failed circuit, we were actually making three
7073 circuit attempts before giving up. Now switch to a default of 2,
7074 and allow the consensus parameter "hs_service_max_rdv_failures" to
7075 override. Fixes bug 24895; bugfix on 0.0.6.
7077 o Minor feature (relay statistics):
7078 - Change relay bandwidth reporting stats interval from 4 hours to 24
7079 hours in order to reduce the efficiency of guard discovery
7080 attacks. Fixes ticket 23856.
7082 o Minor features (compatibility, OpenSSL):
7083 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7084 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7085 since they neither disabled TLS 1.3 nor enabled any of the
7086 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7087 Closes ticket 24978.
7089 o Minor features (denial-of-service avoidance):
7090 - Make our OOM handler aware of the geoip client history cache so it
7091 doesn't fill up the memory. This check is important for IPv6 and
7092 our DoS mitigation subsystem. Closes ticket 25122.
7094 o Minor features (fallback directory mirrors):
7095 - The fallback directory list has been re-generated based on the
7096 current status of the network. Tor uses fallback directories to
7097 bootstrap when it doesn't yet have up-to-date directory
7098 information. Closes ticket 24801.
7099 - Make the default DirAuthorityFallbackRate 0.1, so that clients
7100 prefer to bootstrap from fallback directory mirrors. This is a
7101 follow-up to 24679, which removed weights from the default
7102 fallbacks. Implements ticket 24681.
7104 o Minor features (geoip):
7105 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7108 o Minor features (linux seccomp2 sandbox):
7109 - Update the sandbox rules so that they should now work correctly
7110 with Glibc 2.26. Closes ticket 24315.
7112 o Minor bugfix (channel connection):
7113 - Use the actual observed address of an incoming relay connection,
7114 not the canonical address of the relay from its descriptor, when
7115 making decisions about how to handle the incoming connection.
7116 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7118 o Minor bugfix (directory authority):
7119 - Directory authorities, when refusing a descriptor from a rejected
7120 relay, now explicitly tell the relay (in its logs) to set a valid
7121 ContactInfo address and contact the bad-relays@ mailing list.
7122 Fixes bug 25170; bugfix on 0.2.9.1.
7124 o Minor bugfixes (address selection):
7125 - When the fascist_firewall_choose_address_ functions don't find a
7126 reachable address, set the returned address to the null address
7127 and port. This is a precautionary measure, because some callers do
7128 not check the return value. Fixes bug 24736; bugfix
7131 o Minor bugfixes (compilation):
7132 - Fix a signed/unsigned comparison warning introduced by our fix to
7133 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
7135 o Minor bugfixes (control port, linux seccomp2 sandbox):
7136 - Avoid a crash when attempting to use the seccomp2 sandbox together
7137 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
7140 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
7141 - Fix a possible crash on malformed consensus. If a consensus had
7142 contained an unparseable protocol line, it could have made clients
7143 and relays crash with a null-pointer exception. To exploit this
7144 issue, however, an attacker would need to be able to subvert the
7145 directory authority system. Fixes bug 25251; bugfix on
7146 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7148 o Minor bugfixes (memory usage):
7149 - When queuing DESTROY cells on a channel, only queue the circuit-id
7150 and reason fields: not the entire 514-byte cell. This fix should
7151 help mitigate any bugs or attacks that fill up these queues, and
7152 free more RAM for other uses. Fixes bug 24666; bugfix
7155 o Minor bugfixes (network layer):
7156 - When closing a connection via close_connection_immediately(), we
7157 mark it as "not blocked on bandwidth", to prevent later calls from
7158 trying to unblock it, and give it permission to read. This fixes a
7159 backtrace warning that can happen on relays under various
7160 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
7162 o Minor bugfixes (OSX):
7163 - Don't exit the Tor process if setrlimit() fails to change the file
7164 limit (which can happen sometimes on some versions of OSX). Fixes
7165 bug 21074; bugfix on 0.0.9pre5.
7167 o Minor bugfixes (path selection):
7168 - When selecting relays by bandwidth, avoid a rounding error that
7169 could sometimes cause load to be imbalanced incorrectly.
7170 Previously, we would always round upwards; now, we round towards
7171 the nearest integer. This had the biggest effect when a relay's
7172 weight adjustments should have given it weight 0, but it got
7173 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
7174 - When calculating the fraction of nodes that have descriptors, and
7175 all nodes in the network have zero bandwidths, count the number of
7176 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
7177 - Actually log the total bandwidth in compute_weighted_bandwidths().
7178 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
7180 o Minor bugfixes (portability, msvc):
7181 - Fix a bug in the bit-counting parts of our timing-wheel code on
7182 MSVC. (Note that MSVC is still not a supported build platform, due
7183 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
7186 o Minor bugfixes (relay):
7187 - Make the internal channel_is_client() function look at what sort
7188 of connection handshake the other side used, rather than whether
7189 the other side ever sent a create_fast cell to us. Backports part
7190 of the fixes from bugs 22805 and 24898.
7192 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
7193 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
7195 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
7196 bugfix on 0.2.9.4-alpha.
7199 Changes in version 0.3.2.10 - 2018-03-03
7200 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
7201 backports a number of bugfixes, including important fixes for security
7204 It includes an important security fix for a remote crash attack
7205 against directory authorities, tracked as TROVE-2018-001.
7207 Additionally, it backports a fix for a bug whose severity we have
7208 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
7209 triggered in order to crash relays with a use-after-free pattern. As
7210 such, we are now tracking that bug as TROVE-2018-002 and
7211 CVE-2018-0491, and backporting it to earlier releases. This bug
7212 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
7215 This release also backports our new system for improved resistance to
7216 denial-of-service attacks against relays.
7218 This release also fixes several minor bugs and annoyances from
7221 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
7222 today, for the fix to TROVE-2018-002. Directory authorities should
7223 also upgrade. (Relays on earlier versions might want to update too for
7224 the DoS mitigations.)
7226 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7227 - Fix a protocol-list handling bug that could be used to remotely crash
7228 directory authorities with a null-pointer exception. Fixes bug 25074;
7229 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7232 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
7233 - Avoid adding the same channel twice in the KIST scheduler pending
7234 list, which could lead to remote denial-of-service use-after-free
7235 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
7237 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
7238 - Give relays some defenses against the recent network overload. We
7239 start with three defenses (default parameters in parentheses).
7240 First: if a single client address makes too many concurrent
7241 connections (>100), hang up on further connections. Second: if a
7242 single client address makes circuits too quickly (more than 3 per
7243 second, with an allowed burst of 90) while also having too many
7244 connections open (3), refuse new create cells for the next while
7245 (1-2 hours). Third: if a client asks to establish a rendezvous
7246 point to you directly, ignore the request. These defenses can be
7247 manually controlled by new torrc options, but relays will also
7248 take guidance from consensus parameters, so there's no need to
7249 configure anything manually. Implements ticket 24902.
7251 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
7252 - Fix an "off by 2" error in counting rendezvous failures on the
7253 onion service side. While we thought we would stop the rendezvous
7254 attempt after one failed circuit, we were actually making three
7255 circuit attempts before giving up. Now switch to a default of 2,
7256 and allow the consensus parameter "hs_service_max_rdv_failures" to
7257 override. Fixes bug 24895; bugfix on 0.0.6.
7258 - New-style (v3) onion services now obey the "max rendezvous circuit
7259 attempts" logic. Previously they would make as many rendezvous
7260 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
7261 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
7263 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
7264 - Add Link protocol version 5 to the supported protocols list. Fixes
7265 bug 25070; bugfix on 0.3.1.1-alpha.
7267 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
7268 - Fix a set of false positives where relays would consider
7269 connections to other relays as being client-only connections (and
7270 thus e.g. deserving different link padding schemes) if those
7271 relays fell out of the consensus briefly. Now we look only at the
7272 initial handshake and whether the connection authenticated as a
7273 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
7275 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
7276 - The scheduler subsystem was failing to promptly notice changes in
7277 consensus parameters, making it harder to switch schedulers
7278 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
7280 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
7281 - Make our OOM handler aware of the geoip client history cache so it
7282 doesn't fill up the memory. This check is important for IPv6 and
7283 our DoS mitigation subsystem. Closes ticket 25122.
7285 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
7286 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7287 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7288 since they neither disabled TLS 1.3 nor enabled any of the
7289 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7290 Closes ticket 24978.
7292 o Minor features (geoip):
7293 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7296 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
7297 - When logging a failure to create an onion service's descriptor,
7298 also log what the problem with the descriptor was. Diagnostic
7301 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
7302 - Use the actual observed address of an incoming relay connection,
7303 not the canonical address of the relay from its descriptor, when
7304 making decisions about how to handle the incoming connection.
7305 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7307 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
7308 - Fix a possible crash on malformed consensus. If a consensus had
7309 contained an unparseable protocol line, it could have made clients
7310 and relays crash with a null-pointer exception. To exploit this
7311 issue, however, an attacker would need to be able to subvert the
7312 directory authority system. Fixes bug 25251; bugfix on
7313 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7315 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
7316 - Directory authorities, when refusing a descriptor from a rejected
7317 relay, now explicitly tell the relay (in its logs) to set a valid
7318 ContactInfo address and contact the bad-relays@ mailing list.
7319 Fixes bug 25170; bugfix on 0.2.9.1.
7321 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
7322 - When building with Rust on OSX, link against libresolv, to work
7323 around the issue at https://github.com/rust-lang/rust/issues/46797.
7324 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
7326 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
7327 - Remove a BUG() statement when a client fetches an onion descriptor
7328 that has a lower revision counter than the one in its cache. This
7329 can happen in normal circumstances due to HSDir desync. Fixes bug
7330 24976; bugfix on 0.3.2.1-alpha.
7332 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
7333 - Don't treat inability to store a cached consensus object as a bug:
7334 it can happen normally when we are out of disk space. Fixes bug
7335 24859; bugfix on 0.3.1.1-alpha.
7337 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
7338 - Improve the performance of our consensus-diff application code
7339 when Tor is built with the --enable-fragile-hardening option set.
7340 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
7342 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
7343 - Don't exit the Tor process if setrlimit() fails to change the file
7344 limit (which can happen sometimes on some versions of OSX). Fixes
7345 bug 21074; bugfix on 0.0.9pre5.
7347 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
7348 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
7350 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
7351 bugfix on 0.2.9.4-alpha.
7353 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
7354 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
7355 25005; bugfix on 0.3.2.7-rc.
7357 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
7358 - Look at the "HSRend" protocol version, not the "HSDir" protocol
7359 version, when deciding whether a consensus entry can support the
7360 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
7361 bugfix on 0.3.2.1-alpha.
7363 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
7364 - Update the "rust dependencies" submodule to be a project-level
7365 repository, rather than a user repository. Closes ticket 25323.
7367 o Documentation (backport from 0.3.3.1-alpha)
7368 - Document that operators who run more than one relay or bridge are
7369 expected to set MyFamily and ContactInfo correctly. Closes
7373 Changes in version 0.3.3.3-alpha - 2018-03-03
7374 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
7375 It includes an important security fix for a remote crash attack
7376 against directory authorities tracked as TROVE-2018-001.
7378 Additionally, with this release, we are upgrading the severity of a
7379 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
7380 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
7381 a use-after-free pattern. As such, we are now tracking that bug as
7382 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
7383 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
7385 This release also fixes several minor bugs and annoyances from
7388 Relays running 0.3.2.x should upgrade to one of the versions released
7389 today, for the fix to TROVE-2018-002. Directory authorities should
7390 also upgrade. (Relays on earlier versions might want to update too for
7391 the DoS mitigations.)
7393 o Major bugfixes (denial-of-service, directory authority):
7394 - Fix a protocol-list handling bug that could be used to remotely crash
7395 directory authorities with a null-pointer exception. Fixes bug 25074;
7396 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7399 o Minor features (compatibility, OpenSSL):
7400 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7401 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7402 since they neither disabled TLS 1.3 nor enabled any of the
7403 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7404 Closes ticket 24978.
7406 o Minor features (logging):
7407 - Clarify the log messages produced when getrandom() or a related
7408 entropy-generation mechanism gives an error. Closes ticket 25120.
7410 o Minor features (testing):
7411 - Add a "make test-rust" target to run the rust tests only. Closes
7414 o Minor bugfixes (denial-of-service):
7415 - Fix a possible crash on malformed consensus. If a consensus had
7416 contained an unparseable protocol line, it could have made clients
7417 and relays crash with a null-pointer exception. To exploit this
7418 issue, however, an attacker would need to be able to subvert the
7419 directory authority system. Fixes bug 25251; bugfix on
7420 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7422 o Minor bugfixes (DoS mitigation):
7423 - Add extra safety checks when refilling the circuit creation bucket
7424 to ensure we never set a value above the allowed maximum burst.
7425 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
7426 - When a new consensus arrives, don't update our DoS-mitigation
7427 parameters if we aren't a public relay. Fixes bug 25223; bugfix
7430 o Minor bugfixes (man page, SocksPort):
7431 - Remove dead code from the old "SocksSocket" option, and rename
7432 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
7433 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
7435 o Minor bugfixes (performance):
7436 - Reduce the number of circuits that will be opened at once during
7437 the circuit build timeout phase. This is done by increasing the
7438 idle timeout to 3 minutes, and lowering the maximum number of
7439 concurrent learning circuits to 10. Fixes bug 24769; bugfix
7442 o Minor bugfixes (spec conformance):
7443 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
7445 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
7446 bugfix on 0.2.9.4-alpha.
7448 o Minor bugfixes (spec conformance, rust):
7449 - Resolve a denial-of-service issue caused by an infinite loop in
7450 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
7451 Also tracked as TROVE-2018-003.
7453 o Code simplification and refactoring:
7454 - Update the "rust dependencies" submodule to be a project-level
7455 repository, rather than a user repository. Closes ticket 25323.
7458 Changes in version 0.3.3.2-alpha - 2018-02-10
7459 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
7460 introduces a mechanism to handle the high loads that many relay
7461 operators have been reporting recently. It also fixes several bugs in
7462 older releases. If this new code proves reliable, we plan to backport
7463 it to older supported release series.
7465 o Major features (denial-of-service mitigation):
7466 - Give relays some defenses against the recent network overload. We
7467 start with three defenses (default parameters in parentheses).
7468 First: if a single client address makes too many concurrent
7469 connections (>100), hang up on further connections. Second: if a
7470 single client address makes circuits too quickly (more than 3 per
7471 second, with an allowed burst of 90) while also having too many
7472 connections open (3), refuse new create cells for the next while
7473 (1-2 hours). Third: if a client asks to establish a rendezvous
7474 point to you directly, ignore the request. These defenses can be
7475 manually controlled by new torrc options, but relays will also
7476 take guidance from consensus parameters, so there's no need to
7477 configure anything manually. Implements ticket 24902.
7479 o Major bugfixes (netflow padding):
7480 - Stop adding unneeded channel padding right after we finish
7481 flushing to a connection that has been trying to flush for many
7482 seconds. Instead, treat all partial or complete flushes as
7483 activity on the channel, which will defer the time until we need
7484 to add padding. This fix should resolve confusing and scary log
7485 messages like "Channel padding timeout scheduled 221453ms in the
7486 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
7488 o Major bugfixes (protocol versions):
7489 - Add Link protocol version 5 to the supported protocols list. Fixes
7490 bug 25070; bugfix on 0.3.1.1-alpha.
7492 o Major bugfixes (scheduler, consensus):
7493 - The scheduler subsystem was failing to promptly notice changes in
7494 consensus parameters, making it harder to switch schedulers
7495 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
7497 o Minor features (denial-of-service avoidance):
7498 - Make our OOM handler aware of the geoip client history cache so it
7499 doesn't fill up the memory. This check is important for IPv6 and
7500 our DoS mitigation subsystem. Closes ticket 25122.
7502 o Minor features (directory authority):
7503 - When directory authorities are unable to add signatures to a
7504 pending consensus, log the reason why. Closes ticket 24849.
7506 o Minor features (geoip):
7507 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7510 o Minor features (logging, diagnostic):
7511 - When logging a failure to create an onion service's descriptor,
7512 also log what the problem with the descriptor was. Diagnostic for
7515 o Minor bugfix (channel connection):
7516 - Use the actual observed address of an incoming relay connection,
7517 not the canonical address of the relay from its descriptor, when
7518 making decisions about how to handle the incoming connection.
7519 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7521 o Minor bugfix (directory authority):
7522 - Directory authorities, when refusing a descriptor from a rejected
7523 relay, now explicitly tell the relay (in its logs) to set a valid
7524 ContactInfo address and contact the bad-relays@ mailing list.
7525 Fixes bug 25170; bugfix on 0.2.9.1.
7527 o Minor bugfixes (all versions of Tor):
7528 - Use the "misspell" tool to detect and fix typos throughout the
7529 source code. Fixes bug 23650; bugfix on various versions of Tor.
7530 Patch from Deepesh Pathak.
7532 o Minor bugfixes (circuit, cannibalization):
7533 - Don't cannibalize preemptively-built circuits if we no longer
7534 recognize their first hop. This situation can happen if our Guard
7535 relay went off the consensus after the circuit was created. Fixes
7536 bug 24469; bugfix on 0.0.6.
7538 o Minor bugfixes (correctness):
7539 - Remove a nonworking, unnecessary check to see whether a circuit
7540 hop's identity digest was set when the circuit failed. Fixes bug
7541 24927; bugfix on 0.2.4.4-alpha.
7543 o Minor bugfixes (logging):
7544 - Don't treat inability to store a cached consensus object as a bug:
7545 it can happen normally when we are out of disk space. Fixes bug
7546 24859; bugfix on 0.3.1.1-alpha.
7547 - Fix a (mostly harmless) race condition when invoking
7548 LOG_PROTOCOL_WARN message from a subthread while the torrc options
7549 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
7551 o Minor bugfixes (onion services):
7552 - Remove a BUG() statement when a client fetches an onion descriptor
7553 that has a lower revision counter than the one in its cache. This
7554 can happen in normal circumstances due to HSDir desync. Fixes bug
7555 24976; bugfix on 0.3.2.1-alpha.
7556 - If we are configured to offer a single onion service, don't log
7557 long-term established one hop rendezvous points in the heartbeat.
7558 Fixes bug 25116; bugfix on 0.2.9.6-rc.
7560 o Minor bugfixes (performance):
7561 - Avoid calling protocol_list_supports_protocol() from inside tight
7562 loops when running with cached routerinfo_t objects. Instead,
7563 summarize the relevant protocols as flags in the routerinfo_t, as
7564 we do for routerstatus_t objects. This change simplifies our code
7565 a little, and saves a large amount of short-term memory allocation
7566 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
7568 o Minor bugfixes (Rust FFI):
7569 - Fix a minor memory leak which would happen whenever the C code
7570 would call the Rust implementation of
7571 protover_get_supported_protocols(). This was due to the C version
7572 returning a static string, whereas the Rust version newly allocated
7573 a CString to pass across the FFI boundary. Consequently, the C
7574 code was not expecting to need to free() what it was given. Fixes
7575 bug 25127; bugfix on 0.3.2.1-alpha.
7577 o Minor bugfixes (scheduler, KIST):
7578 - Avoid adding the same channel twice in the KIST scheduler pending
7579 list, which would waste CPU cycles. Fixes bug 24700; bugfix
7582 o Minor bugfixes (unit test, monotonic time):
7583 - Increase a constant (1msec to 10msec) in the monotonic time test
7584 that makes sure the nsec/usec/msec times read are synchronized.
7585 This change was needed to accommodate slow systems like armel or
7586 when the clock_gettime() is not a VDSO on the running kernel.
7587 Fixes bug 25113; bugfix on 0.2.9.1.
7589 o Minor bugfixes (v3 onion services):
7590 - Look at the "HSRend" protocol version, not the "HSDir" protocol
7591 version, when deciding whether a consensus entry can support the
7592 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
7593 bugfix on 0.3.2.1-alpha.
7595 o Code simplification and refactoring:
7596 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
7598 - Remove a series of counters used to track circuit extend attempts
7599 and connection status but that in reality we aren't using for
7600 anything other than stats logged by a SIGUSR1 signal. Closes
7603 o Documentation (man page):
7604 - The HiddenServiceVersion torrc option accepts only one number:
7605 either version 2 or 3. Closes ticket 25026; bugfix
7609 Changes in version 0.3.3.1-alpha - 2018-01-25
7610 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
7611 several new features to Tor, including several improvements to
7612 bootstrapping, and support for an experimental "vanguards" feature to
7613 resist guard discovery attacks. This series also includes better
7614 support for applications that need to embed Tor or manage v3
7617 o Major features (embedding):
7618 - There is now a documented stable API for programs that need to
7619 embed Tor. See tor_api.h for full documentation and known bugs.
7620 Closes ticket 23684.
7621 - Tor now has support for restarting in the same process.
7622 Controllers that run Tor using the "tor_api.h" interface can now
7623 restart Tor after Tor has exited. This support is incomplete,
7624 however: we fixed crash bugs that prevented it from working at
7625 all, but many bugs probably remain, including a possibility of
7626 security issues. Implements ticket 24581.
7628 o Major features (IPv6, directory documents):
7629 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
7630 consensus. This information makes it easier for IPv6 clients to
7631 bootstrap and choose reachable entry guards. Implements ticket 23826.
7632 - Add consensus method 28, which removes IPv6 ORPorts from
7633 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
7634 are redundant in microdescs. This change will be used by Tor clients
7635 on 0.2.8.x and later. (That is to say, with all Tor clients that
7636 have IPv6 bootstrap and guard support.) Implements ticket 23828.
7637 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
7638 set by different numbers of authorities. Fixes 23870
7641 o Major features (onion service v3, control port):
7642 - The control port now supports commands and events for v3 onion
7643 services. It is now possible to create ephemeral v3 services using
7644 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
7645 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
7646 DEL_ONION) have been extended to support v3 onion services. Closes
7647 ticket 20699; implements proposal 284.
7649 o Major features (onion services):
7650 - Provide torrc options to pin the second and third hops of onion
7651 service circuits to a list of nodes. The option HSLayer2Guards
7652 pins the second hop, and the option HSLayer3Guards pins the third
7653 hop. These options are for use in conjunction with experiments
7654 with "vanguards" for preventing guard enumeration attacks. Closes
7657 o Major features (rust, portability, experimental):
7658 - Tor now ships with an optional implementation of one of its
7659 smaller modules (protover.c) in the Rust programming language. To
7660 try it out, install a Rust build environment, and configure Tor
7661 with "--enable-rust --enable-cargo-online-mode". This should not
7662 cause any user-visible changes, but should help us gain more
7663 experience with Rust, and plan future Rust integration work.
7664 Implementation by Chelsea Komlo. Closes ticket 22840.
7666 o Minor features (storage, configuration):
7667 - Users can store cached directory documents somewhere other than
7668 the DataDirectory by using the CacheDirectory option. Similarly,
7669 the storage location for relay's keys can be overridden with the
7670 KeyDirectory option. Closes ticket 22703.
7672 o Major features (v3 onion services, ipv6):
7673 - When v3 onion service clients send introduce cells, they now
7674 include the IPv6 address of the rendezvous point, if it has one.
7675 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
7676 in future Tor versions, IPv6-only v3 single onion services will be
7677 able to use IPv6 addresses to connect directly to the rendezvous
7678 point. Closes ticket 23577. Patch by Neel Chauhan.
7680 o Major bugfixes (onion services, retry behavior):
7681 - Fix an "off by 2" error in counting rendezvous failures on the
7682 onion service side. While we thought we would stop the rendezvous
7683 attempt after one failed circuit, we were actually making three
7684 circuit attempts before giving up. Now switch to a default of 2,
7685 and allow the consensus parameter "hs_service_max_rdv_failures" to
7686 override. Fixes bug 24895; bugfix on 0.0.6.
7687 - New-style (v3) onion services now obey the "max rendezvous circuit
7688 attempts" logic. Previously they would make as many rendezvous
7689 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
7690 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
7692 o Major bugfixes (relays):
7693 - Fix a set of false positives where relays would consider
7694 connections to other relays as being client-only connections (and
7695 thus e.g. deserving different link padding schemes) if those
7696 relays fell out of the consensus briefly. Now we look only at the
7697 initial handshake and whether the connection authenticated as a
7698 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
7700 o Minor feature (IPv6):
7701 - Make IPv6-only clients wait for microdescs for relays, even if we
7702 were previously using descriptors (or were using them as a bridge)
7703 and have a cached descriptor for them. Implements ticket 23827.
7704 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
7705 them, rather than waiting to download microdescriptors.
7706 Implements ticket 23827.
7708 o Minor features (cleanup):
7709 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
7710 when it stops. Closes ticket 23271.
7712 o Minor features (defensive programming):
7713 - Most of the functions in Tor that free objects have been replaced
7714 with macros that free the objects and set the corresponding
7715 pointers to NULL. This change should help prevent a large class of
7716 dangling pointer bugs. Closes ticket 24337.
7717 - Where possible, the tor_free() macro now only evaluates its input
7718 once. Part of ticket 24337.
7719 - Check that microdesc ed25519 ids are non-zero in
7720 node_get_ed25519_id() before returning them. Implements ticket
7721 24001, patch by "aruna1234".
7723 o Minor features (embedding):
7724 - Tor can now start with a preauthenticated control connection
7725 created by the process that launched it. This feature is meant for
7726 use by programs that want to launch and manage a Tor process
7727 without allowing other programs to manage it as well. For more
7728 information, see the __OwningControllerFD option documented in
7729 control-spec.txt. Closes ticket 23900.
7730 - On most errors that would cause Tor to exit, it now tries to
7731 return from the tor_main() function, rather than calling the
7732 system exit() function. Most users won't notice a difference here,
7733 but it should be significant for programs that run Tor inside
7734 a separate thread: they should now be able to survive Tor's exit
7735 conditions rather than having Tor shut down the entire process.
7736 Closes ticket 23848.
7737 - Applications that want to embed Tor can now tell Tor not to
7738 register any of its own POSIX signal handlers, using the
7739 __DisableSignalHandlers option. Closes ticket 24588.
7741 o Minor features (fallback directory list):
7742 - Avoid selecting fallbacks that change their IP addresses too
7743 often. Select more fallbacks by ignoring the Guard flag, and
7744 allowing lower cutoffs for the Running and V2Dir flags. Also allow
7745 a lower bandwidth, and a higher number of fallbacks per operator
7746 (5% of the list). Implements ticket 24785.
7747 - Update the fallback whitelist and blacklist based on opt-ins and
7748 relay changes. Closes tickets 22321, 24678, 22527, 24135,
7751 o Minor features (fallback directory mirror configuration):
7752 - Add a nickname to each fallback in a C comment. This makes it
7753 easier for operators to find their relays, and allows stem to use
7754 nicknames to identify fallbacks. Implements ticket 24600.
7755 - Add a type and version header to the fallback directory mirror
7756 file. Also add a delimiter to the end of each fallback entry. This
7757 helps external parsers like stem and Relay Search. Implements
7759 - Add an extrainfo cache flag for each fallback in a C comment. This
7760 allows stem to use fallbacks to fetch extra-info documents, rather
7761 than using authorities. Implements ticket 22759.
7762 - Add the generateFallbackDirLine.py script for automatically
7763 generating fallback directory mirror lines from relay fingerprints.
7764 No more typos! Add the lookupFallbackDirContact.py script for
7765 automatically looking up operator contact info from relay
7766 fingerprints. Implements ticket 24706, patch by teor and atagar.
7767 - Reject any fallback directory mirror that serves an expired
7768 consensus. Implements ticket 20942, patch by "minik".
7769 - Remove commas and equals signs from external string inputs to the
7770 fallback list. This avoids format confusion attacks. Implements
7772 - Remove the "weight=10" line from fallback directory mirror
7773 entries. Ticket 24681 will maintain the current fallback weights
7774 by changing Tor's default fallback weight to 10. Implements
7776 - Stop logging excessive information about fallback netblocks.
7777 Implements ticket 24791.
7779 o Minor features (forward-compatibility):
7780 - If a relay supports some link authentication protocol that we do
7781 not recognize, then include that relay's ed25519 key when telling
7782 other relays to extend to it. Previously, we treated future
7783 versions as if they were too old to support ed25519 link
7784 authentication. Closes ticket 20895.
7786 o Minor features (heartbeat):
7787 - Add onion service information to our heartbeat logs, displaying
7788 stats about the activity of configured onion services. Closes
7791 o Minor features (instrumentation, development):
7792 - Add the MainloopStats option to allow developers to get
7793 instrumentation information from the main event loop via the
7794 heartbeat messages. We hope to use this to improve Tor's behavior
7795 when it's trying to sleep. Closes ticket 24605.
7797 o Minor features (log messages):
7798 - Improve a warning message that happens when we fail to re-parse an
7799 old router because of an expired certificate. Closes ticket 20020.
7800 - Make the log more quantitative when we hit MaxMemInQueues
7801 threshold exposing some values. Closes ticket 24501.
7803 o Minor features (logging, android):
7804 - Added support for the Android logging subsystem. Closes
7807 o Minor features (performance):
7808 - Support predictive circuit building for onion service circuits
7809 with multiple layers of guards. Closes ticket 23101.
7810 - Use stdatomic.h where available, rather than mutexes, to implement
7811 atomic_counter_t. Closes ticket 23953.
7813 o Minor features (performance, 32-bit):
7814 - Improve performance on 32-bit systems by avoiding 64-bit division
7815 when calculating the timestamp in milliseconds for channel padding
7816 computations. Implements ticket 24613.
7817 - Improve performance on 32-bit systems by avoiding 64-bit division
7818 when timestamping cells and buffer chunks for OOM calculations.
7819 Implements ticket 24374.
7821 o Minor features (performance, OSX, iOS):
7822 - Use the mach_approximate_time() function (when available) to
7823 implement coarse monotonic time. Having a coarse time function
7824 should avoid a large number of system calls, and improve
7825 performance slightly, especially under load. Closes ticket 24427.
7827 o Minor features (performance, windows):
7828 - Improve performance on Windows Vista and Windows 7 by adjusting
7829 TCP send window size according to the recommendation from
7830 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
7833 o Major features (relay):
7834 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
7835 operator to use a more reasonable ("reduced") exit policy, rather
7836 than the default one. If you want to run an exit node without
7837 thinking too hard about which ports to allow, this one is for you.
7838 Closes ticket 13605. Patch from Neel Chauhan.
7840 o Minor features (testing, debugging, embedding):
7841 - For development purposes, Tor now has a mode in which it runs for
7842 a few seconds, then stops, and starts again without exiting the
7843 process. This mode is meant to help us debug various issues with
7844 ticket 23847. To use this feature, compile with
7845 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
7846 environment variable. This is expected to crash a lot, and is
7847 really meant for developers only. It will likely be removed in a
7848 future release. Implements ticket 24583.
7850 o Minor bugfix (network IPv6 test):
7851 - Tor's test scripts now check if "ping -6 ::1" works when the user
7852 runs "make test-network-all". Fixes bug 24677; bugfix on
7853 0.2.9.3-alpha. Patch by "ffmancera".
7855 o Minor bugfixes (build, rust):
7856 - Fix output of autoconf checks to display success messages for Rust
7857 dependencies and a suitable rustc compiler version. Fixes bug
7858 24612; bugfix on 0.3.1.3-alpha.
7859 - When building with Rust on OSX, link against libresolv, to work
7860 around the issue at https://github.com/rust-lang/rust/issues/46797.
7861 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
7862 - Don't pass the --quiet option to cargo: it seems to suppress some
7863 errors, which is not what we want to do when building. Fixes bug
7864 24518; bugfix on 0.3.1.7.
7865 - Build correctly when building from outside Tor's source tree with
7866 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
7869 o Minor bugfixes (directory authorities, IPv6):
7870 - When creating a routerstatus (vote) from a routerinfo (descriptor),
7871 set the IPv6 address to the unspecified IPv6 address, and
7872 explicitly initialize the port to zero. Fixes bug 24488; bugfix
7875 o Minor bugfixes (fallback directory mirrors):
7876 - Make updateFallbackDirs.py search harder for python. (Some OSs
7877 don't put it in /usr/bin.) Fixes bug 24708; bugfix
7880 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
7881 - When hibernating, close connections normally and allow them to
7882 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
7884 - Do not attempt to launch self-reachability tests when entering
7885 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
7886 - Resolve several bugs related to descriptor fetching on bridge
7887 clients with bandwidth accounting enabled. (This combination is
7888 not recommended!) Fixes a case of bug 12062; bugfix
7890 - When hibernating, do not attempt to launch DNS checks. Fixes a
7891 case of bug 12062; bugfix on 0.1.2.2-alpha.
7892 - When hibernating, do not try to upload or download descriptors.
7893 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
7895 o Minor bugfixes (IPv6, bridges):
7896 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
7897 bugfix on 0.2.8.2-alpha.
7898 - Tor now sets IPv6 address in the routerstatus as well as in the
7899 router descriptors when updating addresses for a bridge. Closes
7900 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
7902 o Minor bugfixes (linux seccomp2 sandbox):
7903 - When running with the sandbox enabled, reload configuration files
7904 correctly even when %include was used. Previously we would crash.
7905 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
7907 o Minor bugfixes (memory leaks):
7908 - Avoid possible at-exit memory leaks related to use of Libevent's
7909 event_base_once() function. (This function tends to leak memory if
7910 the event_base is closed before the event fires.) Fixes bug 24584;
7911 bugfix on 0.2.8.1-alpha.
7912 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
7915 o Minor bugfixes (OSX):
7916 - Don't exit the Tor process if setrlimit() fails to change the file
7917 limit (which can happen sometimes on some versions of OSX). Fixes
7918 bug 21074; bugfix on 0.0.9pre5.
7920 o Minor bugfixes (performance, fragile-hardening):
7921 - Improve the performance of our consensus-diff application code
7922 when Tor is built with the --enable-fragile-hardening option set.
7923 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
7925 o Minor bugfixes (performance, timeouts):
7926 - Consider circuits for timeout as soon as they complete a hop. This
7927 is more accurate than applying the timeout in
7928 circuit_expire_building() because that function is only called
7929 once per second, which is now too slow for typical timeouts on the
7930 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
7931 - Use onion service circuits (and other circuits longer than 3 hops)
7932 to calculate a circuit build timeout. Previously, Tor only
7933 calculated its build timeout based on circuits that planned to be
7934 exactly 3 hops long. With this change, we include measurements
7935 from all circuits at the point where they complete their third
7936 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
7938 o Minor bugfixes (testing):
7939 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
7940 bugfix on 0.2.3.1-alpha.
7941 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
7942 25005; bugfix on 0.3.2.7-rc.
7944 o Code simplification and refactoring:
7945 - Remove /usr/athena from search path in configure.ac. Closes
7947 - Remove duplicate code in node_has_curve25519_onion_key() and
7948 node_get_curve25519_onion_key(), and add a check for a zero
7949 microdesc curve25519 onion key. Closes ticket 23966, patch by
7950 "aruna1234" and teor.
7951 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
7952 memory allocations with large numbers of OR connections (e.g.
7953 relays). Closes ticket 24119.
7954 - Separate the function that deletes ephemeral files when Tor
7956 - Small changes to Tor's buf_t API to make it suitable for use as a
7957 general-purpose safe string constructor. Closes ticket 22342.
7958 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
7959 avoid source code identifier confusion. Closes ticket 24467.
7960 - The tor_git_revision[] constant no longer needs to be redeclared
7961 by everything that links against the rest of Tor. Done as part of
7962 ticket 23845, to simplify our external API.
7963 - We make extend_info_from_node() use node_get_curve25519_onion_key()
7964 introduced in ticket 23577 to access the curve25519 public keys
7965 rather than accessing it directly. Closes ticket 23760. Patch by
7967 - Add a function to log channels' scheduler state changes to aid
7968 debugging efforts. Closes ticket 24531.
7971 - Add documentation on how to build tor with Rust dependencies
7972 without having to be online. Closes ticket 22907; bugfix
7974 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
7975 traffic. Closes ticket 24318.
7976 - Document that OutboundBindAddress doesn't apply to DNS requests.
7977 Closes ticket 22145. Patch from Aruna Maurya.
7978 - Document that operators who run more than one relay or bridge are
7979 expected to set MyFamily and ContactInfo correctly. Closes
7982 o Code simplification and refactoring (channels):
7983 - Remove the incoming and outgoing channel queues. These were never
7984 used, but still took up a step in our fast path.
7985 - The majority of the channel unit tests have been rewritten and the
7986 code coverage has now been raised to 83.6% for channel.c. Closes
7988 - Remove other dead code from the channel subsystem: All together,
7989 this cleanup has removed more than 1500 lines of code overall and
7990 adding very little except for unit test.
7992 o Code simplification and refactoring (circuit rendezvous):
7993 - Split the client-side rendezvous circuit lookup into two
7994 functions: one that returns only established circuits and another
7995 that returns all kinds of circuits. Closes ticket 23459.
7997 o Code simplification and refactoring (controller):
7998 - Make most of the variables in networkstatus_getinfo_by_purpose()
7999 const. Implements ticket 24489.
8002 Changes in version 0.3.2.9 - 2018-01-09
8003 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
8005 The 0.3.2 series includes our long-anticipated new onion service
8006 design, with numerous security features. (For more information, see
8007 our blog post at https://blog.torproject.org/fall-harvest.) We also
8008 have a new circuit scheduler algorithm for improved performance on
8009 relays everywhere (see https://blog.torproject.org/kist-and-tell),
8010 along with many smaller features and bugfixes.
8012 Per our stable release policy, we plan to support each stable release
8013 series for at least the next nine months, or for three months after
8014 the first stable release of the next series: whichever is longer. If
8015 you need a release with long-term support, we recommend that you stay
8016 with the 0.2.9 series.
8018 Below is a list of the changes since 0.3.2.8-rc. For a list of all
8019 changes since 0.3.1, see the ReleaseNotes file.
8021 o Minor features (fallback directory mirrors):
8022 - The fallback directory list has been re-generated based on the
8023 current status of the network. Tor uses fallback directories to
8024 bootstrap when it doesn't yet have up-to-date directory
8025 information. Closes ticket 24801.
8026 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8027 prefer to bootstrap from fallback directory mirrors. This is a
8028 follow-up to 24679, which removed weights from the default
8029 fallbacks. Implements ticket 24681.
8031 o Minor features (geoip):
8032 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
8035 o Minor bugfixes (address selection):
8036 - When the fascist_firewall_choose_address_ functions don't find a
8037 reachable address, set the returned address to the null address
8038 and port. This is a precautionary measure, because some callers do
8039 not check the return value. Fixes bug 24736; bugfix
8042 o Minor bugfixes (compilation):
8043 - Resolve a few shadowed-variable warnings in the onion service
8044 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
8046 o Minor bugfixes (portability, msvc):
8047 - Fix a bug in the bit-counting parts of our timing-wheel code on
8048 MSVC. (Note that MSVC is still not a supported build platform, due
8049 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
8053 Changes in version 0.3.2.8-rc - 2017-12-21
8054 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
8055 schedulers that had led servers under heavy load to overload their
8056 outgoing connections. All relay operators running earlier 0.3.2.x
8057 versions should upgrade. This version also includes a mitigation for
8058 over-full DESTROY queues leading to out-of-memory conditions: if it
8059 works, we will soon backport it to earlier release series.
8061 This is the second release candidate in the 0.3.2 series. If we find
8062 no new bugs or regression here, then the first stable 0.3.2 release
8063 will be nearly identical to this.
8065 o Major bugfixes (KIST, scheduler):
8066 - The KIST scheduler did not correctly account for data already
8067 enqueued in each connection's send socket buffer, particularly in
8068 cases when the TCP/IP congestion window was reduced between
8069 scheduler calls. This situation lead to excessive per-connection
8070 buffering in the kernel, and a potential memory DoS. Fixes bug
8071 24665; bugfix on 0.3.2.1-alpha.
8073 o Minor features (geoip):
8074 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
8077 o Minor bugfixes (hidden service v3):
8078 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
8079 the probability of reaching a service for a client missing
8080 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
8082 o Minor bugfixes (memory usage):
8083 - When queuing DESTROY cells on a channel, only queue the circuit-id
8084 and reason fields: not the entire 514-byte cell. This fix should
8085 help mitigate any bugs or attacks that fill up these queues, and
8086 free more RAM for other uses. Fixes bug 24666; bugfix
8089 o Minor bugfixes (scheduler, KIST):
8090 - Use a sane write limit for KISTLite when writing onto a connection
8091 buffer instead of using INT_MAX and shoving as much as it can.
8092 Because the OOM handler cleans up circuit queues, we are better
8093 off at keeping them in that queue instead of the connection's
8094 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
8097 Changes in version 0.3.2.7-rc - 2017-12-14
8098 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
8099 including some that could affect reliability or correctness.
8101 This is the first release candidate in the 0.3.2 series. If we find no
8102 new bugs or regression here, then the first stable 0.3.2. release will
8103 be nearly identical to this.
8105 o Major bugfixes (circuit prediction):
8106 - Fix circuit prediction logic so that a client doesn't treat a port
8107 as being "handled" by a circuit if that circuit already has
8108 isolation settings on it. This change should make Tor clients more
8109 responsive by improving their chances of having a pre-created
8110 circuit ready for use when a request arrives. Fixes bug 18859;
8111 bugfix on 0.2.3.3-alpha.
8113 o Minor features (logging):
8114 - Provide better warnings when the getrandom() syscall fails. Closes
8117 o Minor features (portability):
8118 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
8119 (It doesn't yet work with the sandbox enabled.) Closes
8122 o Minor bugfixes (bridge clients, bootstrap):
8123 - Retry directory downloads when we get our first bridge descriptor
8124 during bootstrap or while reconnecting to the network. Keep
8125 retrying every time we get a bridge descriptor, until we have a
8126 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
8127 - Stop delaying bridge descriptor fetches when we have cached bridge
8128 descriptors. Instead, only delay bridge descriptor fetches when we
8129 have at least one reachable bridge. Fixes part of bug 24367;
8130 bugfix on 0.2.0.3-alpha.
8131 - Stop delaying directory fetches when we have cached bridge
8132 descriptors. Instead, only delay bridge descriptor fetches when
8133 all our bridges are definitely unreachable. Fixes part of bug
8134 24367; bugfix on 0.2.0.3-alpha.
8136 o Minor bugfixes (compilation):
8137 - Fix a signed/unsigned comparison warning introduced by our fix to
8138 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8140 o Minor bugfixes (correctness):
8141 - Fix several places in our codebase where a C compiler would be
8142 likely to eliminate a check, based on assuming that undefined
8143 behavior had not happened elsewhere in the code. These cases are
8144 usually a sign of redundant checking or dubious arithmetic. Found
8145 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
8146 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
8149 o Minor bugfixes (onion service v3):
8150 - Fix a race where an onion service would launch a new intro circuit
8151 after closing an old one, but fail to register it before freeing
8152 the previously closed circuit. This bug was making the service
8153 unable to find the established intro circuit and thus not upload
8154 its descriptor, thus making a service unavailable for up to 24
8155 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
8157 o Minor bugfixes (scheduler, KIST):
8158 - Properly set the scheduler state of an unopened channel in the
8159 KIST scheduler main loop. This prevents a harmless but annoying
8160 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
8161 - Avoid a possible integer overflow when computing the available
8162 space on the TCP buffer of a channel. This had no security
8163 implications; but could make KIST allow too many cells on a
8164 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
8165 - Downgrade to "info" a harmless warning about the monotonic time
8166 moving backwards: This can happen on platform not supporting
8167 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
8170 Changes in version 0.3.2.6-alpha - 2017-12-01
8171 This version of Tor is the latest in the 0.3.2 alpha series. It
8172 includes fixes for several important security issues. All Tor users
8173 should upgrade to this release, or to one of the other releases coming
8176 o Major bugfixes (security):
8177 - Fix a denial of service bug where an attacker could use a
8178 malformed directory object to cause a Tor instance to pause while
8179 OpenSSL would try to read a passphrase from the terminal. (Tor
8180 instances run without a terminal, which is the case for most Tor
8181 packages, are not impacted.) Fixes bug 24246; bugfix on every
8182 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8183 Found by OSS-Fuzz as testcase 6360145429790720.
8184 - Fix a denial of service issue where an attacker could crash a
8185 directory authority using a malformed router descriptor. Fixes bug
8186 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8188 - When checking for replays in the INTRODUCE1 cell data for a
8189 (legacy) onion service, correctly detect replays in the RSA-
8190 encrypted part of the cell. We were previously checking for
8191 replays on the entire cell, but those can be circumvented due to
8192 the malleability of Tor's legacy hybrid encryption. This fix helps
8193 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8194 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8197 o Major bugfixes (security, onion service v2):
8198 - Fix a use-after-free error that could crash v2 Tor onion services
8199 when they failed to open circuits while expiring introduction
8200 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8201 also tracked as TROVE-2017-013 and CVE-2017-8823.
8203 o Major bugfixes (security, relay):
8204 - When running as a relay, make sure that we never build a path
8205 through ourselves, even in the case where we have somehow lost the
8206 version of our descriptor appearing in the consensus. Fixes part
8207 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8208 as TROVE-2017-012 and CVE-2017-8822.
8209 - When running as a relay, make sure that we never choose ourselves
8210 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
8211 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
8213 o Minor feature (relay statistics):
8214 - Change relay bandwidth reporting stats interval from 4 hours to 24
8215 hours in order to reduce the efficiency of guard discovery
8216 attacks. Fixes ticket 23856.
8218 o Minor features (directory authority):
8219 - Add an IPv6 address for the "bastet" directory authority. Closes
8222 o Minor bugfixes (client):
8223 - By default, do not enable storage of client-side DNS values. These
8224 values were unused by default previously, but they should not have
8225 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
8228 Changes in version 0.3.1.9 - 2017-12-01:
8229 Tor 0.3.1.9 backports important security and stability fixes from the
8230 0.3.2 development series. All Tor users should upgrade to this
8231 release, or to another of the releases coming out today.
8233 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8234 - Fix a denial of service bug where an attacker could use a
8235 malformed directory object to cause a Tor instance to pause while
8236 OpenSSL would try to read a passphrase from the terminal. (Tor
8237 instances run without a terminal, which is the case for most Tor
8238 packages, are not impacted.) Fixes bug 24246; bugfix on every
8239 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8240 Found by OSS-Fuzz as testcase 6360145429790720.
8241 - Fix a denial of service issue where an attacker could crash a
8242 directory authority using a malformed router descriptor. Fixes bug
8243 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8245 - When checking for replays in the INTRODUCE1 cell data for a
8246 (legacy) onion service, correctly detect replays in the RSA-
8247 encrypted part of the cell. We were previously checking for
8248 replays on the entire cell, but those can be circumvented due to
8249 the malleability of Tor's legacy hybrid encryption. This fix helps
8250 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8251 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8254 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
8255 - Fix a use-after-free error that could crash v2 Tor onion services
8256 when they failed to open circuits while expiring introduction
8257 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8258 also tracked as TROVE-2017-013 and CVE-2017-8823.
8260 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
8261 - When running as a relay, make sure that we never build a path
8262 through ourselves, even in the case where we have somehow lost the
8263 version of our descriptor appearing in the consensus. Fixes part
8264 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8265 as TROVE-2017-012 and CVE-2017-8822.
8266 - When running as a relay, make sure that we never choose ourselves
8267 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
8268 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
8270 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
8271 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8272 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8273 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8274 identifying and finding a workaround to this bug and to Moritz,
8275 Arthur Edelstein, and Roger for helping to track it down and
8278 o Minor features (bridge):
8279 - Bridges now include notice in their descriptors that they are
8280 bridges, and notice of their distribution status, based on their
8281 publication settings. Implements ticket 18329. For more fine-
8282 grained control of how a bridge is distributed, upgrade to 0.3.2.x
8285 o Minor features (directory authority, backport from 0.3.2.6-alpha):
8286 - Add an IPv6 address for the "bastet" directory authority. Closes
8289 o Minor features (geoip):
8290 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
8293 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
8294 - Avoid unnecessary calls to directory_fetches_from_authorities() on
8295 relays, to prevent spurious address resolutions and descriptor
8296 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
8297 bugfix on in 0.2.8.1-alpha.
8299 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
8300 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
8301 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
8303 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
8304 - When a circuit is marked for close, do not attempt to package any
8305 cells for channels on that circuit. Previously, we would detect
8306 this condition lower in the call stack, when we noticed that the
8307 circuit had no attached channel, and log an annoying message.
8308 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
8310 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
8311 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
8312 so it matches dir-spec.txt. Fixes bug 24262; bugfix
8315 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
8316 - Avoid a crash when transitioning from client mode to bridge mode.
8317 Previously, we would launch the worker threads whenever our
8318 "public server" mode changed, but not when our "server" mode
8319 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
8322 Changes in version 0.3.0.13 - 2017-12-01
8323 Tor 0.3.0.13 backports important security and stability bugfixes from
8324 later Tor releases. All Tor users should upgrade to this release, or
8325 to another of the releases coming out today.
8327 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
8328 2018. If you need a release with long-term support, please stick with
8329 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
8331 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8332 - Fix a denial of service bug where an attacker could use a
8333 malformed directory object to cause a Tor instance to pause while
8334 OpenSSL would try to read a passphrase from the terminal. (Tor
8335 instances run without a terminal, which is the case for most Tor
8336 packages, are not impacted.) Fixes bug 24246; bugfix on every
8337 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8338 Found by OSS-Fuzz as testcase 6360145429790720.
8339 - Fix a denial of service issue where an attacker could crash a
8340 directory authority using a malformed router descriptor. Fixes bug
8341 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8343 - When checking for replays in the INTRODUCE1 cell data for a
8344 (legacy) onion service, correctly detect replays in the RSA-
8345 encrypted part of the cell. We were previously checking for
8346 replays on the entire cell, but those can be circumvented due to
8347 the malleability of Tor's legacy hybrid encryption. This fix helps
8348 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8349 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8352 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
8353 - Fix a use-after-free error that could crash v2 Tor onion services
8354 when they failed to open circuits while expiring introduction
8355 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8356 also tracked as TROVE-2017-013 and CVE-2017-8823.
8358 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
8359 - When running as a relay, make sure that we never build a path
8360 through ourselves, even in the case where we have somehow lost the
8361 version of our descriptor appearing in the consensus. Fixes part
8362 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8363 as TROVE-2017-012 and CVE-2017-8822.
8364 - When running as a relay, make sure that we never choose ourselves
8365 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
8366 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
8368 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
8369 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8370 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8371 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8372 identifying and finding a workaround to this bug and to Moritz,
8373 Arthur Edelstein, and Roger for helping to track it down and
8376 o Minor features (security, windows, backport from 0.3.1.1-alpha):
8377 - Enable a couple of pieces of Windows hardening: one
8378 (HeapEnableTerminationOnCorruption) that has been on-by-default
8379 since Windows 8, and unavailable before Windows 7; and one
8380 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
8381 affect us, but shouldn't do any harm. Closes ticket 21953.
8383 o Minor features (bridge, backport from 0.3.1.9):
8384 - Bridges now include notice in their descriptors that they are
8385 bridges, and notice of their distribution status, based on their
8386 publication settings. Implements ticket 18329. For more fine-
8387 grained control of how a bridge is distributed, upgrade to 0.3.2.x
8390 o Minor features (directory authority, backport from 0.3.2.6-alpha):
8391 - Add an IPv6 address for the "bastet" directory authority. Closes
8394 o Minor features (geoip):
8395 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
8398 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
8399 - Avoid unnecessary calls to directory_fetches_from_authorities() on
8400 relays, to prevent spurious address resolutions and descriptor
8401 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
8402 bugfix on in 0.2.8.1-alpha.
8404 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
8405 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
8406 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
8408 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
8409 - When a circuit is marked for close, do not attempt to package any
8410 cells for channels on that circuit. Previously, we would detect
8411 this condition lower in the call stack, when we noticed that the
8412 circuit had no attached channel, and log an annoying message.
8413 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
8415 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
8416 - Avoid a crash when transitioning from client mode to bridge mode.
8417 Previously, we would launch the worker threads whenever our
8418 "public server" mode changed, but not when our "server" mode
8419 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
8421 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
8422 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
8423 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
8426 Changes in version 0.2.9.14 - 2017-12-01
8427 Tor 0.3.0.13 backports important security and stability bugfixes from
8428 later Tor releases. All Tor users should upgrade to this release, or
8429 to another of the releases coming out today.
8431 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
8432 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8433 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8434 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8435 identifying and finding a workaround to this bug and to Moritz,
8436 Arthur Edelstein, and Roger for helping to track it down and
8439 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8440 - Fix a denial of service bug where an attacker could use a
8441 malformed directory object to cause a Tor instance to pause while
8442 OpenSSL would try to read a passphrase from the terminal. (Tor
8443 instances run without a terminal, which is the case for most Tor
8444 packages, are not impacted.) Fixes bug 24246; bugfix on every
8445 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8446 Found by OSS-Fuzz as testcase 6360145429790720.
8447 - Fix a denial of service issue where an attacker could crash a
8448 directory authority using a malformed router descriptor. Fixes bug
8449 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8451 - When checking for replays in the INTRODUCE1 cell data for a
8452 (legacy) onion service, correctly detect replays in the RSA-
8453 encrypted part of the cell. We were previously checking for
8454 replays on the entire cell, but those can be circumvented due to
8455 the malleability of Tor's legacy hybrid encryption. This fix helps
8456 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8457 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8460 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
8461 - Fix a use-after-free error that could crash v2 Tor onion services
8462 when they failed to open circuits while expiring introduction
8463 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8464 also tracked as TROVE-2017-013 and CVE-2017-8823.
8466 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
8467 - When running as a relay, make sure that we never build a path
8468 through ourselves, even in the case where we have somehow lost the
8469 version of our descriptor appearing in the consensus. Fixes part
8470 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8471 as TROVE-2017-012 and CVE-2017-8822.
8473 o Minor features (bridge, backport from 0.3.1.9):
8474 - Bridges now include notice in their descriptors that they are
8475 bridges, and notice of their distribution status, based on their
8476 publication settings. Implements ticket 18329. For more fine-
8477 grained control of how a bridge is distributed, upgrade to 0.3.2.x
8480 o Minor features (directory authority, backport from 0.3.2.6-alpha):
8481 - Add an IPv6 address for the "bastet" directory authority. Closes
8484 o Minor features (geoip):
8485 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
8488 o Minor features (security, windows, backport from 0.3.1.1-alpha):
8489 - Enable a couple of pieces of Windows hardening: one
8490 (HeapEnableTerminationOnCorruption) that has been on-by-default
8491 since Windows 8, and unavailable before Windows 7; and one
8492 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
8493 affect us, but shouldn't do any harm. Closes ticket 21953.
8495 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
8496 - Avoid unnecessary calls to directory_fetches_from_authorities() on
8497 relays, to prevent spurious address resolutions and descriptor
8498 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
8499 bugfix on in 0.2.8.1-alpha.
8501 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
8502 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
8503 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
8505 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
8506 - When a circuit is marked for close, do not attempt to package any
8507 cells for channels on that circuit. Previously, we would detect
8508 this condition lower in the call stack, when we noticed that the
8509 circuit had no attached channel, and log an annoying message.
8510 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
8512 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
8513 - Avoid a crash when transitioning from client mode to bridge mode.
8514 Previously, we would launch the worker threads whenever our
8515 "public server" mode changed, but not when our "server" mode
8516 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
8518 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
8519 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
8520 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
8523 Changes in version 0.2.8.17 - 2017-12-01
8524 Tor 0.2.8.17 backports important security and stability bugfixes from
8525 later Tor releases. All Tor users should upgrade to this release, or
8526 to another of the releases coming out today.
8528 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
8529 2018. If you need a release with long-term support, please upgrade with
8530 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
8532 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8533 - Fix a denial of service bug where an attacker could use a
8534 malformed directory object to cause a Tor instance to pause while
8535 OpenSSL would try to read a passphrase from the terminal. (Tor
8536 instances run without a terminal, which is the case for most Tor
8537 packages, are not impacted.) Fixes bug 24246; bugfix on every
8538 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8539 Found by OSS-Fuzz as testcase 6360145429790720.
8540 - When checking for replays in the INTRODUCE1 cell data for a
8541 (legacy) onion service, correctly detect replays in the RSA-
8542 encrypted part of the cell. We were previously checking for
8543 replays on the entire cell, but those can be circumvented due to
8544 the malleability of Tor's legacy hybrid encryption. This fix helps
8545 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8546 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8549 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
8550 - Fix a use-after-free error that could crash v2 Tor onion services
8551 when they failed to open circuits while expiring introduction
8552 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8553 also tracked as TROVE-2017-013 and CVE-2017-8823.
8555 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
8556 - When running as a relay, make sure that we never build a path through
8557 ourselves, even in the case where we have somehow lost the version of
8558 our descriptor appearing in the consensus. Fixes part of bug 21534;
8559 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
8562 o Minor features (bridge, backport from 0.3.1.9):
8563 - Bridges now include notice in their descriptors that they are
8564 bridges, and notice of their distribution status, based on their
8565 publication settings. Implements ticket 18329. For more fine-
8566 grained control of how a bridge is distributed, upgrade to 0.3.2.x
8569 o Minor features (directory authority, backport from 0.3.2.6-alpha):
8570 - Add an IPv6 address for the "bastet" directory authority. Closes
8573 o Minor features (geoip):
8574 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
8577 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
8578 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
8579 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
8582 Changes in version 0.2.5.16 - 2017-12-01
8583 Tor 0.2.5.13 backports important security and stability bugfixes from
8584 later Tor releases. All Tor users should upgrade to this release, or
8585 to another of the releases coming out today.
8587 Note: the Tor 0.2.5 series will no longer be supported after 1 May
8588 2018. If you need a release with long-term support, please upgrade to
8589 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
8591 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8592 - Fix a denial of service bug where an attacker could use a
8593 malformed directory object to cause a Tor instance to pause while
8594 OpenSSL would try to read a passphrase from the terminal. (Tor
8595 instances run without a terminal, which is the case for most Tor
8596 packages, are not impacted.) Fixes bug 24246; bugfix on every
8597 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8598 Found by OSS-Fuzz as testcase 6360145429790720.
8599 - When checking for replays in the INTRODUCE1 cell data for a
8600 (legacy) onion service, correctly detect replays in the RSA-
8601 encrypted part of the cell. We were previously checking for
8602 replays on the entire cell, but those can be circumvented due to
8603 the malleability of Tor's legacy hybrid encryption. This fix helps
8604 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8605 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8608 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
8609 - When running as a relay, make sure that we never build a path
8610 through ourselves, even in the case where we have somehow lost the
8611 version of our descriptor appearing in the consensus. Fixes part
8612 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8613 as TROVE-2017-012 and CVE-2017-8822.
8615 o Minor features (bridge, backport from 0.3.1.9):
8616 - Bridges now include notice in their descriptors that they are
8617 bridges, and notice of their distribution status, based on their
8618 publication settings. Implements ticket 18329. For more fine-
8619 grained control of how a bridge is distributed, upgrade to 0.3.2.x
8622 o Minor features (geoip):
8623 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
8627 Changes in version 0.3.2.5-alpha - 2017-11-22
8628 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
8629 fixes several stability and reliability bugs, including a fix for
8630 intermittent bootstrapping failures that some people have been seeing
8631 since the 0.3.0.x series.
8633 Please test this alpha out -- many of these fixes will soon be
8634 backported to stable Tor versions if no additional bugs are found
8637 o Major bugfixes (bootstrapping):
8638 - Fetch descriptors aggressively whenever we lack enough to build
8639 circuits, regardless of how many descriptors we are missing.
8640 Previously, we would delay launching the fetch when we had fewer
8641 than 15 missing descriptors, even if some of those descriptors
8642 were blocking circuits from building. Fixes bug 23985; bugfix on
8643 0.1.1.11-alpha. The effects of this bug became worse in
8644 0.3.0.3-alpha, when we began treating missing descriptors from our
8645 primary guards as a reason to delay circuits.
8646 - Don't try fetching microdescriptors from relays that have failed
8647 to deliver them in the past. Fixes bug 23817; bugfix
8650 o Minor features (directory authority):
8651 - Make the "Exit" flag assignment only depend on whether the exit
8652 policy allows connections to ports 80 and 443. Previously relays
8653 would get the Exit flag if they allowed connections to one of
8654 these ports and also port 6667. Resolves ticket 23637.
8656 o Minor features (geoip):
8657 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
8660 o Minor features (linux seccomp2 sandbox):
8661 - Update the sandbox rules so that they should now work correctly
8662 with Glibc 2.26. Closes ticket 24315.
8664 o Minor features (logging):
8665 - Downgrade a pair of log messages that could occur when an exit's
8666 resolver gave us an unusual (but not forbidden) response. Closes
8668 - Improve the message we log when re-enabling circuit build timeouts
8669 after having received a consensus. Closes ticket 20963.
8671 o Minor bugfixes (compilation):
8672 - Fix a memory leak warning in one of the libevent-related
8673 configuration tests that could occur when manually specifying
8674 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
8675 Found and patched by Alex Xu.
8676 - When detecting OpenSSL on Windows from our configure script, make
8677 sure to try linking with the ws2_32 library. Fixes bug 23783;
8678 bugfix on 0.3.2.2-alpha.
8680 o Minor bugfixes (control port, linux seccomp2 sandbox):
8681 - Avoid a crash when attempting to use the seccomp2 sandbox together
8682 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8685 o Minor bugfixes (control port, onion services):
8686 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
8687 HS_DESC event when a service is not able to upload a descriptor.
8688 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
8690 o Minor bugfixes (directory cache):
8691 - Recover better from empty or corrupt files in the consensus cache
8692 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
8693 - When a consensus diff calculation is only partially successful,
8694 only record the successful parts as having succeeded. Partial
8695 success can happen if (for example) one compression method fails
8696 but the others succeed. Previously we misrecorded all the
8697 calculations as having succeeded, which would later cause a
8698 nonfatal assertion failure. Fixes bug 24086; bugfix
8701 o Minor bugfixes (logging):
8702 - Only log once if we notice that KIST support is gone. Fixes bug
8703 24158; bugfix on 0.3.2.1-alpha.
8704 - Suppress a log notice when relay descriptors arrive. We already
8705 have a bootstrap progress for this so no need to log notice
8706 everytime tor receives relay descriptors. Microdescriptors behave
8707 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
8709 o Minor bugfixes (network layer):
8710 - When closing a connection via close_connection_immediately(), we
8711 mark it as "not blocked on bandwidth", to prevent later calls from
8712 trying to unblock it, and give it permission to read. This fixes a
8713 backtrace warning that can happen on relays under various
8714 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8716 o Minor bugfixes (onion services):
8717 - The introduction circuit was being timed out too quickly while
8718 waiting for the rendezvous circuit to complete. Keep the intro
8719 circuit around longer instead of timing out and reopening new ones
8720 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
8721 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
8722 so it matches dir-spec.txt. Fixes bug 24262; bugfix
8724 - Silence a warning about failed v3 onion descriptor uploads that
8725 can happen naturally under certain edge cases. Fixes part of bug
8726 23662; bugfix on 0.3.2.1-alpha.
8728 o Minor bugfixes (tests):
8729 - Fix a memory leak in one of the bridge-distribution test cases.
8730 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
8731 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
8732 to correctly handle cases where a caller gives it an RSA key of
8733 under 160 bits. (This is not actually a bug in Tor itself, but
8734 rather in our fuzzing code.) Fixes bug 24247; bugfix on
8735 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
8738 - Add notes in man page regarding OS support for the various
8739 scheduler types. Attempt to use less jargon in the scheduler
8740 section. Closes ticket 24254.
8743 Changes in version 0.3.2.4-alpha - 2017-11-08
8744 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
8745 It fixes several stability and reliability bugs, especially including
8746 a major reliability issue that has been plaguing fast exit relays in
8749 o Major bugfixes (exit relays, DNS):
8750 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8751 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8752 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8753 identifying and finding a workaround to this bug and to Moritz,
8754 Arthur Edelstein, and Roger for helping to track it down and
8757 o Major bugfixes (scheduler, channel):
8758 - Stop processing scheduled channels if they closed while flushing
8759 cells. This can happen if the write on the connection fails
8760 leading to the channel being closed while in the scheduler loop.
8761 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
8763 o Minor features (logging, scheduler):
8764 - Introduce a SCHED_BUG() function to log extra information about
8765 the scheduler state if we ever catch a bug in the scheduler.
8766 Closes ticket 23753.
8768 o Minor features (removed deprecations):
8769 - The ClientDNSRejectInternalAddresses flag can once again be set in
8770 non-testing Tor networks, so long as they do not use the default
8771 directory authorities. This change also removes the deprecation of
8772 this flag from 0.2.9.2-alpha. Closes ticket 21031.
8774 o Minor features (testing):
8775 - Our fuzzing tests now test the encrypted portions of v3 onion
8776 service descriptors. Implements more of 21509.
8778 o Minor bugfixes (directory client):
8779 - On failure to download directory information, delay retry attempts
8780 by a random amount based on the "decorrelated jitter" algorithm.
8781 Our previous delay algorithm tended to produce extra-long delays
8782 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
8784 o Minor bugfixes (IPv6, v3 single onion services):
8785 - Remove buggy code for IPv6-only v3 single onion services, and
8786 reject attempts to configure them. This release supports IPv4,
8787 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
8788 stack v3 single onion services. Fixes bug 23820; bugfix
8791 o Minor bugfixes (logging, relay):
8792 - Give only a protocol warning when the ed25519 key is not
8793 consistent between the descriptor and microdescriptor of a relay.
8794 This can happen, for instance, if the relay has been flagged
8795 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
8797 o Minor bugfixes (manpage, onion service):
8798 - Document that the HiddenServiceNumIntroductionPoints option is
8799 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
8800 bugfix on 0.3.2.1-alpha.
8802 o Minor bugfixes (memory leaks):
8803 - Fix a minor memory leak at exit in the KIST scheduler. This bug
8804 should have no user-visible impact. Fixes bug 23774; bugfix
8806 - Fix a memory leak when decrypting a badly formatted v3 onion
8807 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
8808 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
8810 o Minor bugfixes (onion services):
8811 - Cache some needed onion service client information instead of
8812 constantly computing it over and over again. Fixes bug 23623;
8813 bugfix on 0.3.2.1-alpha.
8814 - Properly retry HSv3 descriptor fetches when missing required
8815 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
8817 o Minor bugfixes (path selection):
8818 - When selecting relays by bandwidth, avoid a rounding error that
8819 could sometimes cause load to be imbalanced incorrectly.
8820 Previously, we would always round upwards; now, we round towards
8821 the nearest integer. This had the biggest effect when a relay's
8822 weight adjustments should have given it weight 0, but it got
8823 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8824 - When calculating the fraction of nodes that have descriptors, and
8825 all nodes in the network have zero bandwidths, count the number of
8826 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8827 - Actually log the total bandwidth in compute_weighted_bandwidths().
8828 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8830 o Minor bugfixes (relay, crash):
8831 - Avoid a crash when transitioning from client mode to bridge mode.
8832 Previously, we would launch the worker threads whenever our
8833 "public server" mode changed, but not when our "server" mode
8834 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
8836 o Minor bugfixes (testing):
8837 - Fix a spurious fuzzing-only use of an uninitialized value. Found
8838 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
8839 - Test that IPv6-only clients can use microdescriptors when running
8840 "make test-network-all". Requires chutney master 61c28b9 or later.
8841 Closes ticket 24109.
8844 Changes in version 0.3.2.3-alpha - 2017-10-27
8845 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
8846 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
8847 directory authority, Bastet.
8849 o Directory authority changes:
8850 - Add "Bastet" as a ninth directory authority to the default list.
8851 Closes ticket 23910.
8852 - The directory authority "Longclaw" has changed its IP address.
8853 Closes ticket 23592.
8855 o Minor features (bridge):
8856 - Bridge relays can now set the BridgeDistribution config option to
8857 add a "bridge-distribution-request" line to their bridge
8858 descriptor, which tells BridgeDB how they'd like their bridge
8859 address to be given out. (Note that as of Oct 2017, BridgeDB does
8860 not yet implement this feature.) As a side benefit, this feature
8861 provides a way to distinguish bridge descriptors from non-bridge
8862 descriptors. Implements tickets 18329.
8864 o Minor features (client, entry guards):
8865 - Improve log messages when missing descriptors for primary guards.
8866 Resolves ticket 23670.
8868 o Minor features (geoip):
8869 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
8872 o Minor bugfixes (bridge):
8873 - Overwrite the bridge address earlier in the process of retrieving
8874 its descriptor, to make sure we reach it on the configured
8875 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
8877 o Minor bugfixes (documentation):
8878 - Document better how to read gcov, and what our gcov postprocessing
8879 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
8881 o Minor bugfixes (entry guards):
8882 - Tor now updates its guard state when it reads a consensus
8883 regardless of whether it's missing descriptors. That makes tor use
8884 its primary guards to fetch descriptors in some edge cases where
8885 it would previously have used fallback directories. Fixes bug
8886 23862; bugfix on 0.3.0.1-alpha.
8888 o Minor bugfixes (hidden service client):
8889 - When handling multiple SOCKS request for the same .onion address,
8890 only fetch the service descriptor once.
8891 - When a descriptor fetch fails with a non-recoverable error, close
8892 all pending SOCKS requests for that .onion. Fixes bug 23653;
8893 bugfix on 0.3.2.1-alpha.
8895 o Minor bugfixes (hidden service):
8896 - Always regenerate missing hidden service public key files. Prior
8897 to this, if the public key was deleted from disk, it wouldn't get
8898 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
8900 - Make sure that we have a usable ed25519 key when the intro point
8901 relay supports ed25519 link authentication. Fixes bug 24002;
8902 bugfix on 0.3.2.1-alpha.
8904 o Minor bugfixes (hidden service, v2):
8905 - When reloading configured hidden services, copy all information
8906 from the old service object. Previously, some data was omitted,
8907 causing delays in descriptor upload, and other bugs. Fixes bug
8908 23790; bugfix on 0.2.1.9-alpha.
8910 o Minor bugfixes (memory safety, defensive programming):
8911 - Clear the target address when node_get_prim_orport() returns
8912 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
8914 o Minor bugfixes (relay):
8915 - Avoid a BUG warning when receiving a dubious CREATE cell while an
8916 option transition is in progress. Fixes bug 23952; bugfix
8919 o Minor bugfixes (testing):
8920 - Adjust the GitLab CI configuration to more closely match that of
8921 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
8922 - Prevent scripts/test/coverage from attempting to move gcov output
8923 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
8924 - When running unit tests as root, skip a test that would fail
8925 because it expects a permissions error. This affects some
8926 continuous integration setups. Fixes bug 23758; bugfix
8928 - Stop unconditionally mirroring the tor repository in GitLab CI.
8929 This prevented developers from enabling GitLab CI on master. Fixes
8930 bug 23755; bugfix on 0.3.2.2-alpha.
8931 - Fix the hidden service v3 descriptor decoding fuzzing to use the
8932 latest decoding API correctly. Fixes bug 21509; bugfix
8935 o Minor bugfixes (warnings):
8936 - When we get an HTTP request on a SOCKS port, tell the user about
8937 the new HTTPTunnelPort option. Previously, we would give a "Tor is
8938 not an HTTP Proxy" message, which stopped being true when
8939 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
8943 Changes in version 0.2.5.15 - 2017-10-25
8944 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
8945 series. It also adds a new directory authority, Bastet.
8947 Note: the Tor 0.2.5 series will no longer be supported after 1 May
8948 2018. If you need a release with long-term support, please upgrade to
8949 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
8951 o Directory authority changes:
8952 - Add "Bastet" as a ninth directory authority to the default list.
8953 Closes ticket 23910.
8954 - The directory authority "Longclaw" has changed its IP address.
8955 Closes ticket 23592.
8957 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
8958 - Avoid an assertion failure bug affecting our implementation of
8959 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8960 handling of "0xx" differs from what we had expected. Fixes bug
8961 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8963 o Minor features (geoip):
8964 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
8967 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
8968 - Fix a memset() off the end of an array when packing cells. This
8969 bug should be harmless in practice, since the corrupted bytes are
8970 still in the same structure, and are always padding bytes,
8971 ignored, or immediately overwritten, depending on compiler
8972 behavior. Nevertheless, because the memset()'s purpose is to make
8973 sure that any other cell-handling bugs can't expose bytes to the
8974 network, we need to fix it. Fixes bug 22737; bugfix on
8975 0.2.4.11-alpha. Fixes CID 1401591.
8977 o Build features (backport from 0.3.1.5-alpha):
8978 - Tor's repository now includes a Travis Continuous Integration (CI)
8979 configuration file (.travis.yml). This is meant to help new
8980 developers and contributors who fork Tor to a Github repository be
8981 better able to test their changes, and understand what we expect
8982 to pass. To use this new build feature, you must fork Tor to your
8983 Github account, then go into the "Integrations" menu in the
8984 repository settings for your fork and enable Travis, then push
8985 your changes. Closes ticket 22636.
8988 Changes in version 0.2.8.16 - 2017-10-25
8989 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
8990 series, including a bugfix for a crash issue that had affected relays
8991 under memory pressure. It also adds a new directory authority, Bastet.
8993 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
8994 2018. If you need a release with long-term support, please stick with
8995 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
8997 o Directory authority changes:
8998 - Add "Bastet" as a ninth directory authority to the default list.
8999 Closes ticket 23910.
9000 - The directory authority "Longclaw" has changed its IP address.
9001 Closes ticket 23592.
9003 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9004 - Fix a timing-based assertion failure that could occur when the
9005 circuit out-of-memory handler freed a connection's output buffer.
9006 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9008 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9009 - Remove longclaw's IPv6 address, as it will soon change. Authority
9010 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9011 3/8 directory authorities with IPv6 addresses, but there are also
9012 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9014 o Minor features (geoip):
9015 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9019 Changes in version 0.2.9.13 - 2017-10-25
9020 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
9021 series, including a bugfix for a crash issue that had affected relays
9022 under memory pressure. It also adds a new directory authority, Bastet.
9024 o Directory authority changes:
9025 - Add "Bastet" as a ninth directory authority to the default list.
9026 Closes ticket 23910.
9027 - The directory authority "Longclaw" has changed its IP address.
9028 Closes ticket 23592.
9030 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9031 - Fix a timing-based assertion failure that could occur when the
9032 circuit out-of-memory handler freed a connection's output buffer.
9033 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9035 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9036 - Remove longclaw's IPv6 address, as it will soon change. Authority
9037 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9038 3/8 directory authorities with IPv6 addresses, but there are also
9039 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9041 o Minor features (geoip):
9042 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9045 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
9046 - When a directory authority rejects a descriptor or extrainfo with
9047 a given digest, mark that digest as undownloadable, so that we do
9048 not attempt to download it again over and over. We previously
9049 tried to avoid downloading such descriptors by other means, but we
9050 didn't notice if we accidentally downloaded one anyway. This
9051 behavior became problematic in 0.2.7.2-alpha, when authorities
9052 began pinning Ed25519 keys. Fixes bug 22349; bugfix
9055 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9056 - Clear the address when node_get_prim_orport() returns early.
9057 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9059 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
9060 - When running as a Windows service, set the ID of the main thread
9061 correctly. Failure to do so made us fail to send log messages to
9062 the controller in 0.2.1.16-rc, slowed down controller event
9063 delivery in 0.2.7.3-rc and later, and crash with an assertion
9064 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
9065 Patch and diagnosis from "Vort".
9068 Changes in version 0.3.0.12 - 2017-10-25
9069 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
9070 series, including a bugfix for a crash issue that had affected relays
9071 under memory pressure. It also adds a new directory authority, Bastet.
9073 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
9074 2018. If you need a release with long-term support, please stick with
9075 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9077 o Directory authority changes:
9078 - Add "Bastet" as a ninth directory authority to the default list.
9079 Closes ticket 23910.
9080 - The directory authority "Longclaw" has changed its IP address.
9081 Closes ticket 23592.
9083 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9084 - Fix a timing-based assertion failure that could occur when the
9085 circuit out-of-memory handler freed a connection's output buffer.
9086 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9088 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9089 - Remove longclaw's IPv6 address, as it will soon change. Authority
9090 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9091 3/8 directory authorities with IPv6 addresses, but there are also
9092 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9094 o Minor features (geoip):
9095 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9098 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
9099 - When a directory authority rejects a descriptor or extrainfo with
9100 a given digest, mark that digest as undownloadable, so that we do
9101 not attempt to download it again over and over. We previously
9102 tried to avoid downloading such descriptors by other means, but we
9103 didn't notice if we accidentally downloaded one anyway. This
9104 behavior became problematic in 0.2.7.2-alpha, when authorities
9105 began pinning Ed25519 keys. Fixes bug 22349; bugfix
9108 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
9109 - Avoid a possible double close of a circuit by the intro point on
9110 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9111 bugfix on 0.3.0.1-alpha.
9113 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9114 - Clear the address when node_get_prim_orport() returns early.
9115 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9117 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
9118 - When running as a Windows service, set the ID of the main thread
9119 correctly. Failure to do so made us fail to send log messages to
9120 the controller in 0.2.1.16-rc, slowed down controller event
9121 delivery in 0.2.7.3-rc and later, and crash with an assertion
9122 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
9123 Patch and diagnosis from "Vort".
9126 Changes in version 0.3.1.8 - 2017-10-25
9127 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
9128 It includes several bugfixes, including a bugfix for a crash issue
9129 that had affected relays under memory pressure. It also adds
9130 a new directory authority, Bastet.
9132 o Directory authority changes:
9133 - Add "Bastet" as a ninth directory authority to the default list.
9134 Closes ticket 23910.
9135 - The directory authority "Longclaw" has changed its IP address.
9136 Closes ticket 23592.
9138 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9139 - Fix a timing-based assertion failure that could occur when the
9140 circuit out-of-memory handler freed a connection's output buffer.
9141 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9143 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9144 - Remove longclaw's IPv6 address, as it will soon change. Authority
9145 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9146 3/8 directory authorities with IPv6 addresses, but there are also
9147 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9149 o Minor features (geoip):
9150 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9153 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
9154 - Fix a compilation warning when building with zstd support on
9155 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
9156 and fixed by Andreas Stieger.
9158 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
9159 - Handle a pathological case when decompressing Zstandard data when
9160 the output buffer size is zero. Fixes bug 23551; bugfix
9163 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
9164 - Remove the length limit on HTTP status lines that authorities can
9165 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
9167 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
9168 - Avoid a possible double close of a circuit by the intro point on
9169 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9170 bugfix on 0.3.0.1-alpha.
9172 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9173 - Clear the address when node_get_prim_orport() returns early.
9174 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9176 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
9177 - Fix additional channelpadding unit test failures by using mocked
9178 time instead of actual time for all tests. Fixes bug 23608; bugfix
9182 Changes in version 0.3.2.2-alpha - 2017-09-29
9183 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
9184 release fixes several minor bugs in the new scheduler and next-
9185 generation onion services; both features were newly added in the 0.3.2
9186 series. Other fixes in this alpha include several fixes for non-fatal
9187 tracebacks which would appear in logs.
9189 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
9190 alpha does not contain any substantial new features. Minor features
9191 include better testing and logging.
9193 The following comprises the complete list of changes included
9196 o Major bugfixes (relay, crash, assertion failure):
9197 - Fix a timing-based assertion failure that could occur when the
9198 circuit out-of-memory handler freed a connection's output buffer.
9199 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9201 o Major bugfixes (scheduler):
9202 - If a channel is put into the scheduler's pending list, then it
9203 starts closing, and then if the scheduler runs before it finishes
9204 closing, the scheduler will get stuck trying to flush its cells
9205 while the lower layers refuse to cooperate. Fix that race
9206 condition by giving the scheduler an escape method. Fixes bug
9207 23676; bugfix on 0.3.2.1-alpha.
9209 o Minor features (build, compilation):
9210 - The "check-changes" feature is now part of the "make check" tests;
9211 we'll use it to try to prevent misformed changes files from
9212 accumulating. Closes ticket 23564.
9213 - Tor builds should now fail if there are any mismatches between the
9214 C type representing a configuration variable and the C type the
9215 data-driven parser uses to store a value there. Previously, we
9216 needed to check these by hand, which sometimes led to mistakes.
9217 Closes ticket 23643.
9219 o Minor features (directory authorities):
9220 - Remove longclaw's IPv6 address, as it will soon change. Authority
9221 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9222 3/8 directory authorities with IPv6 addresses, but there are also
9223 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9225 o Minor features (hidden service, circuit, logging):
9226 - Improve logging of many callsite in the circuit subsystem to print
9227 the circuit identifier(s).
9228 - Log when we cleanup an intro point from a service so we know when
9229 and for what reason it happened. Closes ticket 23604.
9231 o Minor features (logging):
9232 - Log more circuit information whenever we are about to try to
9233 package a relay cell on a circuit with a nonexistent n_chan.
9234 Attempt to diagnose ticket 8185.
9235 - Improve info-level log identification of particular circuits, to
9236 help with debugging. Closes ticket 23645.
9238 o Minor features (relay):
9239 - When choosing which circuits can be expired as unused, consider
9240 circuits from clients even if those clients used regular CREATE
9241 cells to make them; and do not consider circuits from relays even
9242 if they were made with CREATE_FAST. Part of ticket 22805.
9244 o Minor features (robustness):
9245 - Change several fatal assertions when flushing buffers into non-
9246 fatal assertions, to prevent any recurrence of 23690.
9248 o Minor features (spec conformance, bridge, diagnostic):
9249 - When handling the USERADDR command on an ExtOrPort, warn when the
9250 transports provides a USERADDR with no port. In a future version,
9251 USERADDR commands of this format may be rejected. Detects problems
9252 related to ticket 23080.
9254 o Minor features (testing):
9255 - Add a unit test to make sure that our own generated platform
9256 string will be accepted by directory authorities. Closes
9259 o Minor bugfixes (bootstrapping):
9260 - When warning about state file clock skew, report the correct
9261 direction for the detected skew. Fixes bug 23606; bugfix
9263 - Avoid an assertion failure when logging a state file clock skew
9264 very early in bootstrapping. Fixes bug 23607; bugfix
9267 o Minor bugfixes (build, compilation):
9268 - Fix a compilation warning when building with zstd support on
9269 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
9270 and fixed by Andreas Stieger.
9271 - When searching for OpenSSL, don't accept any OpenSSL library that
9272 lacks TLSv1_1_method(): Tor doesn't build with those versions.
9273 Additionally, look in /usr/local/opt/openssl, if it's present.
9274 These changes together repair the default build on OSX systems
9275 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
9277 o Minor bugfixes (compression):
9278 - Handle a pathological case when decompressing Zstandard data when
9279 the output buffer size is zero. Fixes bug 23551; bugfix
9282 o Minor bugfixes (documentation):
9283 - Fix manpage to not refer to the obsolete (and misspelled)
9284 UseEntryGuardsAsDirectoryGuards parameter in the description of
9285 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
9287 o Minor bugfixes (hidden service v3):
9288 - Don't log an assertion failure when we can't find the right
9289 information to extend to an introduction point. In rare cases,
9290 this could happen, causing a warning, even though tor would
9291 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
9292 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
9293 much bigger so the rendezvous point can't distinguish which hidden
9294 service protocol is being used. Fixes bug 23420; bugfix
9297 o Minor bugfixes (hidden service, relay):
9298 - Avoid a possible double close of a circuit by the intro point on
9299 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9300 bugfix on 0.3.0.1-alpha.
9302 o Minor bugfixes (logging, relay shutdown, annoyance):
9303 - When a circuit is marked for close, do not attempt to package any
9304 cells for channels on that circuit. Previously, we would detect
9305 this condition lower in the call stack, when we noticed that the
9306 circuit had no attached channel, and log an annoying message.
9307 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9309 o Minor bugfixes (scheduler):
9310 - When switching schedulers due to a consensus change, we didn't
9311 give the new scheduler a chance to react to the consensus. Fix
9312 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
9313 - Make the KISTSchedRunInterval option a non negative value. With
9314 this, the way to disable KIST through the consensus is to set it
9315 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
9316 - Only notice log the selected scheduler when we switch scheduler
9317 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
9318 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
9319 by a different tv_usec data type. Fixes bug 23575; bugfix
9321 - Make a hard exit if tor is unable to pick a scheduler which can
9322 happen if the user specifies a scheduler type that is not
9323 supported and not other types in Schedulers. Fixes bug 23581;
9324 bugfix on 0.3.2.1-alpha.
9325 - Properly initialize the scheduler last run time counter so it is
9326 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
9328 o Minor bugfixes (testing):
9329 - Capture and detect several "Result does not fit" warnings in unit
9330 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
9332 - Fix additional channelpadding unit test failures by using mocked
9333 time instead of actual time for all tests. Fixes bug 23608; bugfix
9335 - The removal of some old scheduler options caused some tests to
9336 fail on BSD systems. Assume current behavior is correct and make
9337 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
9339 o Code simplification and refactoring:
9340 - Remove various ways of testing circuits and connections for
9341 "clientness"; instead, favor channel_is_client(). Part of
9344 o Deprecated features:
9345 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
9346 now deprecated; they do not apply to relays, and they have had no
9347 effect on clients since 0.2.8.x. Closes ticket 19704.
9350 - HiddenServiceVersion man page entry wasn't mentioning the now
9351 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
9352 - Clarify that the Address option is entirely about setting an
9353 advertised IPv4 address. Closes ticket 18891.
9354 - Clarify the manpage's use of the term "address" to clarify what
9355 kind of address is intended. Closes ticket 21405.
9356 - Document that onion service subdomains are allowed, and ignored.
9357 Closes ticket 18736.
9360 Changes in version 0.3.2.1-alpha - 2017-09-18
9361 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
9362 includes support for our next-generation ("v3") onion service
9363 protocol, and adds a new circuit scheduler for more responsive
9364 forwarding decisions from relays. There are also numerous other small
9365 features and bugfixes here.
9367 Below are the changes since Tor 0.3.1.7.
9369 o Major feature (scheduler, channel):
9370 - Tor now uses new schedulers to decide which circuits should
9371 deliver cells first, in order to improve congestion at relays. The
9372 first type is called "KIST" ("Kernel Informed Socket Transport"),
9373 and is only available on Linux-like systems: it uses feedback from
9374 the kernel to prevent the kernel's TCP buffers from growing too
9375 full. The second new scheduler type is called "KISTLite": it
9376 behaves the same as KIST, but runs on systems without kernel
9377 support for inspecting TCP implementation details. The old
9378 scheduler is still available, under the name "Vanilla". To change
9379 the default scheduler preference order, use the new "Schedulers"
9380 option. (The default preference order is "KIST,KISTLite,Vanilla".)
9382 Matt Traudt implemented KIST, based on research by Rob Jansen,
9383 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
9384 more information, see the design paper at
9385 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
9386 followup implementation paper at https://arxiv.org/abs/1709.01044.
9387 Closes ticket 12541.
9389 o Major features (next-generation onion services):
9390 - Tor now supports the next-generation onion services protocol for
9391 clients and services! As part of this release, the core of
9392 proposal 224 has been implemented and is available for
9393 experimentation and testing by our users. This newer version of
9394 onion services ("v3") features many improvements over the legacy
9397 a) Better crypto (replaced SHA1/DH/RSA1024
9398 with SHA3/ed25519/curve25519)
9400 b) Improved directory protocol, leaking much less information to
9403 c) Improved directory protocol, with smaller surface for
9406 d) Better onion address security against impersonation.
9408 e) More extensible introduction/rendezvous protocol.
9410 f) A cleaner and more modular codebase.
9412 You can identify a next-generation onion address by its length:
9413 they are 56 characters long, as in
9414 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
9416 In the future, we will release more options and features for v3
9417 onion services, but we first need a testing period, so that the
9418 current codebase matures and becomes more robust. Planned features
9419 include: offline keys, advanced client authorization, improved
9420 guard algorithms, and statistics. For full details, see
9423 Legacy ("v2") onion services will still work for the foreseeable
9424 future, and will remain the default until this new codebase gets
9425 tested and hardened. Service operators who want to experiment with
9426 the new system can use the 'HiddenServiceVersion 3' torrc
9427 directive along with the regular onion service configuration
9428 options. We will publish a blog post about this new feature
9431 o Major bugfixes (usability, control port):
9432 - Report trusted clock skew indications as bootstrap errors, so
9433 controllers can more easily alert users when their clocks are
9434 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
9436 o Minor features (bug detection):
9437 - Log a warning message with a stack trace for any attempt to call
9438 get_options() during option validation. This pattern has caused
9439 subtle bugs in the past. Closes ticket 22281.
9441 o Minor features (client):
9442 - You can now use Tor as a tunneled HTTP proxy: use the new
9443 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
9444 requests. Closes ticket 22407.
9445 - Add an extra check to make sure that we always use the newer guard
9446 selection code for picking our guards. Closes ticket 22779.
9447 - When downloading (micro)descriptors, don't split the list into
9448 multiple requests unless we want at least 32 descriptors.
9449 Previously, we split at 4, not 32, which led to significant
9450 overhead in HTTP request size and degradation in compression
9451 performance. Closes ticket 23220.
9453 o Minor features (command line):
9454 - Add a new commandline option, --key-expiration, which prints when
9455 the current signing key is going to expire. Implements ticket
9456 17639; patch by Isis Lovecruft.
9458 o Minor features (control port):
9459 - If an application tries to use the control port as an HTTP proxy,
9460 respond with a meaningful "This is the Tor control port" message,
9461 and log the event. Closes ticket 1667. Patch from Ravi
9463 - Provide better error message for GETINFO desc/(id|name) when not
9464 fetching router descriptors. Closes ticket 5847. Patch by
9466 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
9467 whether Tor will try to download router descriptors and
9468 microdescriptors respectively. Closes ticket 22684.
9469 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
9470 so controllers can tell whether the geoip databases are loaded.
9471 Closes ticket 23237.
9472 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
9473 events. Closes ticket 19254. Patch by "DonnchaC".
9475 o Minor features (development support):
9476 - Developers can now generate a call-graph for Tor using the
9477 "calltool" python program, which post-processes object dumps. It
9478 should work okay on many Linux and OSX platforms, and might work
9479 elsewhere too. To run it, install calltool from
9480 https://gitweb.torproject.org/user/nickm/calltool.git and run
9481 "make callgraph". Closes ticket 19307.
9483 o Minor features (ed25519):
9484 - Add validation function to checks for torsion components in
9485 ed25519 public keys, used by prop224 client-side code. Closes
9486 ticket 22006. Math help by Ian Goldberg.
9488 o Minor features (exit relay, DNS):
9489 - Improve the clarity and safety of the log message from evdns when
9490 receiving an apparently spoofed DNS reply. Closes ticket 3056.
9492 o Minor features (integration, hardening):
9493 - Add a new NoExec option to prevent Tor from running other
9494 programs. When this option is set to 1, Tor will never try to run
9495 another program, regardless of the settings of
9496 PortForwardingHelper, ClientTransportPlugin, or
9497 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
9498 without restarting Tor. Closes ticket 22976.
9500 o Minor features (logging):
9501 - Improve the warning message for specifying a relay by nickname.
9502 The previous message implied that nickname registration was still
9503 part of the Tor network design, which it isn't. Closes
9505 - If the sandbox filter fails to load, suggest to the user that
9506 their kernel might not support seccomp2. Closes ticket 23090.
9508 o Minor features (portability):
9509 - Check at configure time whether uint8_t is the same type as
9510 unsigned char. Lots of existing code already makes this
9511 assumption, and there could be strict aliasing issues if the
9512 assumption is violated. Closes ticket 22410.
9514 o Minor features (relay, configuration):
9515 - Reject attempts to use relative file paths when RunAsDaemon is
9516 set. Previously, Tor would accept these, but the directory-
9517 changing step of RunAsDaemon would give strange and/or confusing
9518 results. Closes ticket 22731.
9520 o Minor features (startup, safety):
9521 - When configured to write a PID file, Tor now exits if it is unable
9522 to do so. Previously, it would warn and continue. Closes
9525 o Minor features (static analysis):
9526 - The BUG() macro has been changed slightly so that Coverity no
9527 longer complains about dead code if the bug is impossible. Closes
9530 o Minor features (testing):
9531 - The default chutney network tests now include tests for the v3
9532 hidden service design. Make sure you have the latest version of
9533 chutney if you want to run these. Closes ticket 22437.
9534 - Add a unit test to verify that we can parse a hardcoded v2 hidden
9535 service descriptor. Closes ticket 15554.
9537 o Minor bugfixes (certificate handling):
9538 - Fix a time handling bug in Tor certificates set to expire after
9539 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
9540 Coverity as CID 1415728.
9542 o Minor bugfixes (client, usability):
9543 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
9544 SOCKS4a requests that contain IP address strings, even when
9545 SafeSocks in enabled, as this prevents user from connecting to
9546 known IP addresses without relying on DNS for resolving. SafeSocks
9547 still rejects SOCKS connections that connect to IP addresses when
9548 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
9549 bugfix on Tor 0.2.6.2-alpha.
9551 o Minor bugfixes (code correctness):
9552 - Call htons() in extend_cell_format() for encoding a 16-bit value.
9553 Previously we used ntohs(), which happens to behave the same on
9554 all the platforms we support, but which isn't really correct.
9555 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
9556 - For defense-in-depth, make the controller's write_escaped_data()
9557 function robust to extremely long inputs. Fixes bug 19281; bugfix
9558 on 0.1.1.1-alpha. Reported by Guido Vranken.
9560 o Minor bugfixes (compilation):
9561 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
9562 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9564 o Minor bugfixes (consensus expiry):
9565 - Check for adequate directory information correctly. Previously, Tor
9566 would reconsider whether it had sufficient directory information
9567 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
9569 o Minor bugfixes (directory protocol):
9570 - Directory servers now include a "Date:" http header for response
9571 codes other than 200. Clients starting with a skewed clock and a
9572 recent consensus were getting "304 Not modified" responses from
9573 directory authorities, so without the Date header, the client
9574 would never hear about a wrong clock. Fixes bug 23499; bugfix
9576 - Make clients wait for 6 seconds before trying to download a
9577 consensus from an authority. Fixes bug 17750; bugfix
9580 o Minor bugfixes (DoS-resistance):
9581 - If future code asks if there are any running bridges, without
9582 checking if bridges are enabled, log a BUG warning rather than
9583 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
9585 o Minor bugfixes (format strictness):
9586 - Restrict several data formats to decimal. Previously, the
9587 BuildTimeHistogram entries in the state file, the "bw=" entries in
9588 the bandwidth authority file, and the process IDs passed to the
9589 __OwningControllerProcess option could all be specified in hex or
9590 octal as well as in decimal. This was not an intentional feature.
9591 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
9594 o Minor bugfixes (heartbeat):
9595 - If we fail to write a heartbeat message, schedule a retry for the
9596 minimum heartbeat interval number of seconds in the future. Fixes
9597 bug 19476; bugfix on 0.2.3.1-alpha.
9599 o Minor bugfixes (linux seccomp2 sandbox, logging):
9600 - Fix some messages on unexpected errors from the seccomp2 library.
9601 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
9603 o Minor bugfixes (logging):
9604 - Remove duplicate log messages regarding opening non-local
9605 SocksPorts upon parsing config and opening listeners at startup.
9606 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
9607 - Use a more comprehensible log message when telling the user
9608 they've excluded every running exit node. Fixes bug 7890; bugfix
9610 - When logging the number of descriptors we intend to download per
9611 directory request, do not log a number higher than then the number
9612 of descriptors we're fetching in total. Fixes bug 19648; bugfix
9614 - When warning about a directory owned by the wrong user, log the
9615 actual name of the user owning the directory. Previously, we'd log
9616 the name of the process owner twice. Fixes bug 23487; bugfix
9618 - The tor specification says hop counts are 1-based, so fix two log
9619 messages that mistakenly logged 0-based hop counts. Fixes bug
9620 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
9621 Credit to Xiaofan Li for reporting this issue.
9623 o Minor bugfixes (portability):
9624 - Stop using the PATH_MAX variable, which is not defined on GNU
9625 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
9627 o Minor bugfixes (relay):
9628 - When uploading our descriptor for the first time after startup,
9629 report the reason for uploading as "Tor just started" rather than
9630 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
9631 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9632 relays, to prevent spurious address resolutions and descriptor
9633 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9634 bugfix on in 0.2.8.1-alpha.
9636 o Minor bugfixes (tests):
9637 - Fix a broken unit test for the OutboundAddress option: the parsing
9638 function was never returning an error on failure. Fixes bug 23366;
9639 bugfix on 0.3.0.3-alpha.
9640 - Fix a signed-integer overflow in the unit tests for
9641 dir/download_status_random_backoff, which was untriggered until we
9642 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
9644 o Minor bugfixes (usability, control port):
9645 - Stop making an unnecessary routerlist check in NETINFO clock skew
9646 detection; this was preventing clients from reporting NETINFO clock
9647 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
9649 o Code simplification and refactoring:
9650 - Extract the code for handling newly-open channels into a separate
9651 function from the general code to handle channel state
9652 transitions. This change simplifies our callgraph, reducing the
9653 size of the largest strongly connected component by roughly a
9654 factor of two. Closes ticket 22608.
9655 - Remove dead code for largely unused statistics on the number of
9656 times we've attempted various public key operations. Fixes bug
9657 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
9658 - Remove several now-obsolete functions for asking about old
9659 variants directory authority status. Closes ticket 22311; patch
9661 - Remove some of the code that once supported "Named" and "Unnamed"
9662 routers. Authorities no longer vote for these flags. Closes
9664 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
9665 and old hidden services, to indicate that they aren't suitable for
9666 new protocols or formats. Closes ticket 23026.
9667 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
9668 22521. Patch from Neel Chauhan.
9669 - Split the enormous circuit_send_next_onion_skin() function into
9670 multiple subfunctions. Closes ticket 22804.
9671 - Split the portions of the buffer.c module that handle particular
9672 protocols into separate modules. Part of ticket 23149.
9673 - Use our test macros more consistently, to produce more useful
9674 error messages when our unit tests fail. Add coccinelle patches to
9675 allow us to re-check for test macro uses. Closes ticket 22497.
9677 o Deprecated features:
9678 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
9679 only applies to direct unencrypted HTTP connections to your
9680 directory server, which your Tor probably isn't using. Closes
9684 - Clarify in the manual that "Sandbox 1" is only supported on Linux
9685 kernels. Closes ticket 22677.
9686 - Document all values of PublishServerDescriptor in the manpage.
9687 Closes ticket 15645.
9688 - Improve the documentation for the directory port part of the
9689 DirAuthority line. Closes ticket 20152.
9690 - Restore documentation for the authorities' "approved-routers"
9691 file. Closes ticket 21148.
9694 - The AllowDotExit option has been removed as unsafe. It has been
9695 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
9696 - The ClientDNSRejectInternalAddresses flag can no longer be set on
9697 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
9698 Closes ticket 21031.
9699 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
9700 nobody was using it any longer. Closes ticket 22377.
9703 Changes in version 0.2.8.15 - 2017-09-18
9704 Tor 0.2.8.15 backports a collection of bugfixes from later
9707 Most significantly, it includes a fix for TROVE-2017-008, a
9708 security bug that affects hidden services running with the
9709 SafeLogging option disabled. For more information, see
9710 https://trac.torproject.org/projects/tor/ticket/23490
9712 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
9713 2018. We suggest that you upgrade to the latest stable release if
9714 possible. If you can't, we recommend that you upgrade at least to
9715 0.2.9, which will be supported until 2020.
9717 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9718 - Avoid an assertion failure bug affecting our implementation of
9719 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9720 handling of "0xx" differs from what we had expected. Fixes bug
9721 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9724 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9727 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
9728 - Backport a fix for an "unused variable" warning that appeared
9729 in some versions of mingw. Fixes bug 22838; bugfix on
9732 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9733 - Fix a memset() off the end of an array when packing cells. This
9734 bug should be harmless in practice, since the corrupted bytes are
9735 still in the same structure, and are always padding bytes,
9736 ignored, or immediately overwritten, depending on compiler
9737 behavior. Nevertheless, because the memset()'s purpose is to make
9738 sure that any other cell-handling bugs can't expose bytes to the
9739 network, we need to fix it. Fixes bug 22737; bugfix on
9740 0.2.4.11-alpha. Fixes CID 1401591.
9742 o Build features (backport from 0.3.1.5-alpha):
9743 - Tor's repository now includes a Travis Continuous Integration (CI)
9744 configuration file (.travis.yml). This is meant to help new
9745 developers and contributors who fork Tor to a Github repository be
9746 better able to test their changes, and understand what we expect
9747 to pass. To use this new build feature, you must fork Tor to your
9748 Github account, then go into the "Integrations" menu in the
9749 repository settings for your fork and enable Travis, then push
9750 your changes. Closes ticket 22636.
9753 Changes in version 0.2.9.12 - 2017-09-18
9754 Tor 0.2.9.12 backports a collection of bugfixes from later
9757 Most significantly, it includes a fix for TROVE-2017-008, a
9758 security bug that affects hidden services running with the
9759 SafeLogging option disabled. For more information, see
9760 https://trac.torproject.org/projects/tor/ticket/23490
9762 o Major features (security, backport from 0.3.0.2-alpha):
9763 - Change the algorithm used to decide DNS TTLs on client and server
9764 side, to better resist DNS-based correlation attacks like the
9765 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
9766 Feamster. Now relays only return one of two possible DNS TTL
9767 values, and clients are willing to believe DNS TTL values up to 3
9768 hours long. Closes ticket 19769.
9770 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
9771 - Fix a rare crash when sending a begin cell on a circuit whose
9772 linked directory connection had already been closed. Fixes bug
9773 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
9775 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
9776 - Fix a bug that prevented exit nodes from caching DNS records for
9777 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
9779 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
9780 - Fix a typo that had prevented TPROXY-based transparent proxying
9781 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
9782 Patch from "d4fq0fQAgoJ".
9784 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9785 - Avoid an assertion failure bug affecting our implementation of
9786 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9787 handling of "0xx" differs from what we had expected. Fixes bug
9788 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9790 o Minor features (code style, backport from 0.3.1.3-alpha):
9791 - Add "Falls through" comments to our codebase, in order to silence
9792 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
9793 Stieger. Closes ticket 22446.
9795 o Minor features (geoip):
9796 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9799 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
9800 - Roll over monthly accounting at the configured hour and minute,
9801 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
9802 Found by Andrey Karpov with PVS-Studio.
9804 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
9805 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
9806 bugfix on 0.2.8.1-alpha.
9807 - Fix warnings when building with libscrypt and openssl scrypt support
9808 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
9809 - When building with certain versions the mingw C header files, avoid
9810 float-conversion warnings when calling the C functions isfinite(),
9811 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
9813 o Minor bugfixes (compilation, backport from 0.3.1.7):
9814 - Avoid compiler warnings in the unit tests for running tor_sscanf()
9815 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
9817 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
9818 - Backport a fix for an "unused variable" warning that appeared
9819 in some versions of mingw. Fixes bug 22838; bugfix on
9822 o Minor bugfixes (controller, backport from 0.3.1.7):
9823 - Do not crash when receiving a HSPOST command with an empty body.
9824 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
9825 - Do not crash when receiving a POSTDESCRIPTOR command with an
9826 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
9828 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
9829 - Avoid Coverity build warnings related to our BUG() macro. By
9830 default, Coverity treats BUG() as the Linux kernel does: an
9831 instant abort(). We need to override that so our BUG() macro
9832 doesn't prevent Coverity from analyzing functions that use it.
9833 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
9835 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9836 - Fix a memset() off the end of an array when packing cells. This
9837 bug should be harmless in practice, since the corrupted bytes are
9838 still in the same structure, and are always padding bytes,
9839 ignored, or immediately overwritten, depending on compiler
9840 behavior. Nevertheless, because the memset()'s purpose is to make
9841 sure that any other cell-handling bugs can't expose bytes to the
9842 network, we need to fix it. Fixes bug 22737; bugfix on
9843 0.2.4.11-alpha. Fixes CID 1401591.
9845 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
9846 - When setting the maximum number of connections allowed by the OS,
9847 always allow some extra file descriptors for other files. Fixes
9848 bug 22797; bugfix on 0.2.0.10-alpha.
9850 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
9851 - Avoid a sandbox failure when trying to re-bind to a socket and
9852 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
9854 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
9855 - Permit the fchmod system call, to avoid crashing on startup when
9856 starting with the seccomp2 sandbox and an unexpected set of
9857 permissions on the data directory or its contents. Fixes bug
9858 22516; bugfix on 0.2.5.4-alpha.
9860 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
9861 - Avoid a double-marked-circuit warning that could happen when we
9862 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
9865 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
9866 - Reject version numbers with non-numeric prefixes (such as +, -, or
9867 whitespace). Disallowing whitespace prevents differential version
9868 parsing between POSIX-based and Windows platforms. Fixes bug 21507
9869 and part of 21508; bugfix on 0.0.8pre1.
9871 o Build features (backport from 0.3.1.5-alpha):
9872 - Tor's repository now includes a Travis Continuous Integration (CI)
9873 configuration file (.travis.yml). This is meant to help new
9874 developers and contributors who fork Tor to a Github repository be
9875 better able to test their changes, and understand what we expect
9876 to pass. To use this new build feature, you must fork Tor to your
9877 Github account, then go into the "Integrations" menu in the
9878 repository settings for your fork and enable Travis, then push
9879 your changes. Closes ticket 22636.
9882 Changes in version 0.3.0.11 - 2017-09-18
9883 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
9886 Most significantly, it includes a fix for TROVE-2017-008, a
9887 security bug that affects hidden services running with the
9888 SafeLogging option disabled. For more information, see
9889 https://trac.torproject.org/projects/tor/ticket/23490
9891 o Minor features (code style, backport from 0.3.1.7):
9892 - Add "Falls through" comments to our codebase, in order to silence
9893 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
9894 Stieger. Closes ticket 22446.
9897 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9900 o Minor bugfixes (compilation, backport from 0.3.1.7):
9901 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
9902 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
9904 o Minor bugfixes (controller, backport from 0.3.1.7):
9905 - Do not crash when receiving a HSPOST command with an empty body.
9906 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
9907 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
9908 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
9910 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
9911 - When setting the maximum number of connections allowed by the OS,
9912 always allow some extra file descriptors for other files. Fixes
9913 bug 22797; bugfix on 0.2.0.10-alpha.
9915 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
9916 - Remove a forgotten debugging message when an introduction point
9917 successfully establishes a hidden service prop224 circuit with
9919 - Change three other log_warn() for an introduction point to
9920 protocol warnings, because they can be failure from the network
9921 and are not relevant to the operator. Fixes bug 23078; bugfix on
9922 0.3.0.1-alpha and 0.3.0.2-alpha.
9925 Changes in version 0.3.1.7 - 2017-09-18
9926 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
9928 With the 0.3.1 series, Tor now serves and downloads directory
9929 information in more compact formats, to save on bandwidth overhead. It
9930 also contains a new padding system to resist netflow-based traffic
9931 analysis, and experimental support for building parts of Tor in Rust
9932 (though no parts of Tor are in Rust yet). There are also numerous
9933 small features, bugfixes on earlier release series, and groundwork for
9934 the hidden services revamp of 0.3.2.
9936 This release also includes a fix for TROVE-2017-008, a security bug
9937 that affects hidden services running with the SafeLogging option
9938 disabled. For more information, see
9939 https://trac.torproject.org/projects/tor/ticket/23490
9941 Per our stable release policy, we plan to support each stable release
9942 series for at least the next nine months, or for three months after
9943 the first stable release of the next series: whichever is longer. If
9944 you need a release with long-term support, we recommend that you stay
9945 with the 0.2.9 series.
9947 Below is a list of the changes since 0.3.1.6-rc. For a list of all
9948 changes since 0.3.0, see the ReleaseNotes file.
9950 o Major bugfixes (security, hidden services, loggging):
9951 - Fix a bug where we could log uninitialized stack when a certain
9952 hidden service error occurred while SafeLogging was disabled.
9953 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
9954 TROVE-2017-008 and CVE-2017-0380.
9956 o Minor features (defensive programming):
9957 - Create a pair of consensus parameters, nf_pad_tor2web and
9958 nf_pad_single_onion, to disable netflow padding in the consensus
9959 for non-anonymous connections in case the overhead is high. Closes
9962 o Minor features (diagnostic):
9963 - Add a stack trace to the bug warnings that can be logged when
9964 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
9965 attempt for bug 23105.
9967 o Minor features (geoip):
9968 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9971 o Minor bugfixes (compilation):
9972 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
9973 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
9975 o Minor bugfixes (controller):
9976 - Do not crash when receiving a HSPOST command with an empty body.
9977 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
9978 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
9979 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
9981 o Minor bugfixes (relay):
9982 - Inform the geoip and rephist modules about all requests, even on
9983 relays that are only fetching microdescriptors. Fixes a bug
9984 related to 21585; bugfix on 0.3.0.1-alpha.
9986 o Minor bugfixes (unit tests):
9987 - Fix a channelpadding unit test failure on slow systems by using
9988 mocked time instead of actual time. Fixes bug 23077; bugfix
9992 Changes in version 0.3.1.6-rc - 2017-09-05
9993 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
9994 release series, including a bug that produced weird behavior on
9995 Windows directory caches.
9997 This is the first release candidate in the Tor 0.3.1 series. If we
9998 find no new bugs or regressions here, the first stable 0.3.1 release
9999 will be nearly identical to it.
10001 o Major bugfixes (windows, directory cache):
10002 - On Windows, do not try to delete cached consensus documents and
10003 diffs before they are unmapped from memory--Windows won't allow
10004 that. Instead, allow the consensus cache directory to grow larger,
10005 to hold files that might need to stay around longer. Fixes bug
10006 22752; bugfix on 0.3.1.1-alpha.
10008 o Minor features (directory authority):
10009 - Improve the message that authorities report to relays that present
10010 RSA/Ed25519 keypairs that conflict with previously pinned keys.
10011 Closes ticket 22348.
10013 o Minor features (geoip):
10014 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
10017 o Minor features (testing):
10018 - Add more tests for compression backend initialization. Closes
10021 o Minor bugfixes (directory cache):
10022 - Fix a memory leak when recovering space in the consensus cache.
10023 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
10025 o Minor bugfixes (hidden service):
10026 - Increase the number of circuits that a service is allowed to
10027 open over a specific period of time. The value was lower than it
10028 should be (8 vs 12) in the normal case of 3 introduction points.
10029 Fixes bug 22159; bugfix on 0.3.0.5-rc.
10030 - Fix a BUG warning during HSv3 descriptor decoding that could be
10031 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
10032 on 0.3.0.1-alpha. Bug found by "haxxpop".
10033 - Rate-limit the log messages if we exceed the maximum number of
10034 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
10036 o Minor bugfixes (logging, relay):
10037 - Remove a forgotten debugging message when an introduction point
10038 successfully establishes a hidden service prop224 circuit with
10040 - Change three other log_warn() for an introduction point to
10041 protocol warnings, because they can be failure from the network
10042 and are not relevant to the operator. Fixes bug 23078; bugfix on
10043 0.3.0.1-alpha and 0.3.0.2-alpha.
10045 o Minor bugfixes (relay):
10046 - When a relay is not running as a directory cache, it will no
10047 longer generate compressed consensuses and consensus diff
10048 information. Previously, this was a waste of disk and CPU. Fixes
10049 bug 23275; bugfix on 0.3.1.1-alpha.
10051 o Minor bugfixes (robustness, error handling):
10052 - Improve our handling of the cases where OpenSSL encounters a
10053 memory error while encoding keys and certificates. We haven't
10054 observed these errors in the wild, but if they do happen, we now
10055 detect and respond better. Fixes bug 19418; bugfix on all versions
10056 of Tor. Reported by Guido Vranken.
10058 o Minor bugfixes (stability):
10059 - Avoid crashing on a double-free when unable to load or process an
10060 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
10061 with the clang static analyzer.
10063 o Minor bugfixes (testing):
10064 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10065 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10066 - Port the hs_ntor handshake test to work correctly with recent
10067 versions of the pysha3 module. Fixes bug 23071; bugfix
10070 o Minor bugfixes (Windows service):
10071 - When running as a Windows service, set the ID of the main thread
10072 correctly. Failure to do so made us fail to send log messages to
10073 the controller in 0.2.1.16-rc, slowed down controller event
10074 delivery in 0.2.7.3-rc and later, and crash with an assertion
10075 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10076 Patch and diagnosis from "Vort".
10079 Changes in version 0.3.0.10 - 2017-08-02
10080 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
10081 from the current Tor alpha series. OpenBSD users and TPROXY users
10082 should upgrade; others are probably okay sticking with 0.3.0.9.
10084 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
10085 - Tor's repository now includes a Travis Continuous Integration (CI)
10086 configuration file (.travis.yml). This is meant to help new
10087 developers and contributors who fork Tor to a Github repository be
10088 better able to test their changes, and understand what we expect
10089 to pass. To use this new build feature, you must fork Tor to your
10090 Github account, then go into the "Integrations" menu in the
10091 repository settings for your fork and enable Travis, then push
10092 your changes. Closes ticket 22636.
10094 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
10095 - Fix a typo that had prevented TPROXY-based transparent proxying
10096 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10097 Patch from "d4fq0fQAgoJ".
10099 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10100 - Avoid an assertion failure bug affecting our implementation of
10101 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10102 handling of "0xbar" differs from what we had expected. Fixes bug
10103 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10105 o Minor features (backport from 0.3.1.5-alpha):
10106 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
10109 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
10110 - Roll over monthly accounting at the configured hour and minute,
10111 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
10112 Found by Andrey Karpov with PVS-Studio.
10114 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
10115 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
10116 bugfix on 0.2.8.1-alpha.
10117 - Fix warnings when building with libscrypt and openssl scrypt
10118 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10119 - When building with certain versions of the mingw C header files,
10120 avoid float-conversion warnings when calling the C functions
10121 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
10124 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10125 - Backport a fix for an "unused variable" warning that appeared
10126 in some versions of mingw. Fixes bug 22838; bugfix on
10129 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
10130 - Avoid Coverity build warnings related to our BUG() macro. By
10131 default, Coverity treats BUG() as the Linux kernel does: an
10132 instant abort(). We need to override that so our BUG() macro
10133 doesn't prevent Coverity from analyzing functions that use it.
10134 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10136 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
10137 - When rejecting a router descriptor for running an obsolete version
10138 of Tor without ntor support, warn about the obsolete tor version,
10139 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
10141 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
10142 - Avoid a sandbox failure when trying to re-bind to a socket and
10143 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10145 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
10146 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
10147 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
10150 Changes in version 0.3.1.5-alpha - 2017-08-01
10151 Tor 0.3.1.5-alpha improves the performance of consensus diff
10152 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
10153 several other bugs. If no serious bugs are found in this version, the
10154 next version will be a release candidate.
10156 This release also marks the end of support for the Tor 0.2.4.x,
10157 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
10158 further bug or security fixes. Anyone still running or distributing
10159 one of those versions should upgrade.
10161 o Major features (build system, continuous integration):
10162 - Tor's repository now includes a Travis Continuous Integration (CI)
10163 configuration file (.travis.yml). This is meant to help new
10164 developers and contributors who fork Tor to a Github repository be
10165 better able to test their changes, and understand what we expect
10166 to pass. To use this new build feature, you must fork Tor to your
10167 Github account, then go into the "Integrations" menu in the
10168 repository settings for your fork and enable Travis, then push
10169 your changes. Closes ticket 22636.
10171 o Major bugfixes (openbsd, denial-of-service):
10172 - Avoid an assertion failure bug affecting our implementation of
10173 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10174 handling of "0xbar" differs from what we had expected. Fixes bug
10175 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10177 o Major bugfixes (relay, performance):
10178 - Perform circuit handshake operations at a higher priority than we
10179 use for consensus diff creation and compression. This should
10180 prevent circuits from starving when a relay or bridge receives a
10181 new consensus, especially on lower-powered machines. Fixes bug
10182 22883; bugfix on 0.3.1.1-alpha.
10184 o Minor features (bridge authority):
10185 - Add "fingerprint" lines to the networkstatus-bridges file produced
10186 by bridge authorities. Closes ticket 22207.
10188 o Minor features (directory cache, consensus diff):
10189 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
10190 operators with low-resource environments to adjust the number of
10191 consensuses they'll store and generate diffs from. Most cache
10192 operators should leave it unchanged. Helps to work around
10195 o Minor features (geoip):
10196 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
10199 o Minor features (relay, performance):
10200 - Always start relays with at least two worker threads, to prevent
10201 priority inversion on slow tasks. Part of the fix for bug 22883.
10202 - Allow background work to be queued with different priorities, so
10203 that a big pile of slow low-priority jobs will not starve out
10204 higher priority jobs. This lays the groundwork for a fix for
10207 o Minor bugfixes (build system, rust):
10208 - Fix a problem where Rust toolchains were not being found when
10209 building without --enable-cargo-online-mode, due to setting the
10210 $HOME environment variable instead of $CARGO_HOME. Fixes bug
10211 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
10213 o Minor bugfixes (compatibility, zstd):
10214 - Write zstd epilogues correctly when the epilogue requires
10215 reallocation of the output buffer, even with zstd 1.3.0.
10216 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
10217 22927; bugfix on 0.3.1.1-alpha.
10219 o Minor bugfixes (compilation warnings):
10220 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
10221 22915; bugfix on 0.2.8.1-alpha.
10222 - Fix warnings when building with libscrypt and openssl scrypt
10223 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10224 - Compile correctly when both openssl 1.1.0 and libscrypt are
10225 detected. Previously this would cause an error. Fixes bug 22892;
10226 bugfix on 0.3.1.1-alpha.
10227 - When building with certain versions of the mingw C header files,
10228 avoid float-conversion warnings when calling the C functions
10229 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
10232 o Minor bugfixes (coverity build support):
10233 - Avoid Coverity build warnings related to our BUG() macro. By
10234 default, Coverity treats BUG() as the Linux kernel does: an
10235 instant abort(). We need to override that so our BUG() macro
10236 doesn't prevent Coverity from analyzing functions that use it.
10237 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10239 o Minor bugfixes (directory authority):
10240 - When a directory authority rejects a descriptor or extrainfo with
10241 a given digest, mark that digest as undownloadable, so that we do
10242 not attempt to download it again over and over. We previously
10243 tried to avoid downloading such descriptors by other means, but we
10244 didn't notice if we accidentally downloaded one anyway. This
10245 behavior became problematic in 0.2.7.2-alpha, when authorities
10246 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10249 o Minor bugfixes (error reporting, windows):
10250 - When formatting Windows error messages, use the English format to
10251 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
10254 o Minor bugfixes (file limits, osx):
10255 - When setting the maximum number of connections allowed by the OS,
10256 always allow some extra file descriptors for other files. Fixes
10257 bug 22797; bugfix on 0.2.0.10-alpha.
10259 o Minor bugfixes (linux seccomp2 sandbox):
10260 - Avoid a sandbox failure when trying to re-bind to a socket and
10261 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10263 o Minor bugfixes (memory leaks):
10264 - Fix a small memory leak when validating a configuration that uses
10265 two or more AF_UNIX sockets for the same port type. Fixes bug
10266 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
10268 o Minor bugfixes (unit tests):
10269 - test_consdiff_base64cmp would fail on OS X because while OS X
10270 follows the standard of (less than zero/zero/greater than zero),
10271 it doesn't follow the convention of (-1/0/+1). Make the test
10272 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
10273 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
10274 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
10277 Changes in version 0.3.1.4-alpha - 2017-06-29
10278 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
10279 to use a guard that was in the same network family as a chosen exit
10280 relay. This is a security regression; all clients running earlier
10281 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
10284 This release also fixes several other bugs introduced in 0.3.0.x
10285 and 0.3.1.x, including others that can affect bandwidth usage
10288 o New dependencies:
10289 - To build with zstd and lzma support, Tor now requires the
10290 pkg-config tool at build time. (This requirement was new in
10291 0.3.1.1-alpha, but was not noted at the time. Noting it here to
10292 close ticket 22623.)
10294 o Major bugfixes (path selection, security):
10295 - When choosing which guard to use for a circuit, avoid the exit's
10296 family along with the exit itself. Previously, the new guard
10297 selection logic avoided the exit, but did not consider its family.
10298 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
10299 006 and CVE-2017-0377.
10301 o Major bugfixes (compression, zstd):
10302 - Correctly detect a full buffer when decompressing a large zstd-
10303 compressed input. Previously, we would sometimes treat a full
10304 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
10306 o Major bugfixes (directory protocol):
10307 - Ensure that we send "304 Not modified" as HTTP status code when a
10308 client is attempting to fetch a consensus or consensus diff, and
10309 the best one we can send them is one they already have. Fixes bug
10310 22702; bugfix on 0.3.1.1-alpha.
10312 o Major bugfixes (entry guards):
10313 - When starting with an old consensus, do not add new entry guards
10314 unless the consensus is "reasonably live" (under 1 day old). Fixes
10315 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
10317 o Minor features (bug mitigation, diagnostics, logging):
10318 - Avoid an assertion failure, and log a better error message, when
10319 unable to remove a file from the consensus cache on Windows.
10320 Attempts to mitigate and diagnose bug 22752.
10322 o Minor features (geoip):
10323 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
10326 o Minor bugfixes (compression):
10327 - When compressing or decompressing a buffer, check for a failure to
10328 create a compression object. Fixes bug 22626; bugfix
10330 - When decompressing a buffer, check for extra data after the end of
10331 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
10332 - When decompressing an object received over an anonymous directory
10333 connection, if we have already decompressed it using an acceptable
10334 compression method, do not reject it for looking like an
10335 unacceptable compression method. Fixes part of bug 22670; bugfix
10337 - When serving directory votes compressed with zlib, do not claim to
10338 have compressed them with zstd. Fixes bug 22669; bugfix
10340 - When spooling compressed data to an output buffer, don't try to
10341 spool more data when there is no more data to spool and we are not
10342 trying to flush the input. Previously, we would sometimes launch
10343 compression requests with nothing to do, which interferes with our
10344 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
10346 o Minor bugfixes (defensive programming):
10347 - Detect and break out of infinite loops in our compression code. We
10348 don't think that any such loops exist now, but it's best to be
10349 safe. Closes ticket 22672.
10350 - Fix a memset() off the end of an array when packing cells. This
10351 bug should be harmless in practice, since the corrupted bytes are
10352 still in the same structure, and are always padding bytes,
10353 ignored, or immediately overwritten, depending on compiler
10354 behavior. Nevertheless, because the memset()'s purpose is to make
10355 sure that any other cell-handling bugs can't expose bytes to the
10356 network, we need to fix it. Fixes bug 22737; bugfix on
10357 0.2.4.11-alpha. Fixes CID 1401591.
10359 o Minor bugfixes (linux seccomp2 sandbox):
10360 - Permit the fchmod system call, to avoid crashing on startup when
10361 starting with the seccomp2 sandbox and an unexpected set of
10362 permissions on the data directory or its contents. Fixes bug
10363 22516; bugfix on 0.2.5.4-alpha.
10364 - Fix a crash in the LZMA module, when the sandbox was enabled, and
10365 liblzma would allocate more than 16 MB of memory. We solve this by
10366 bumping the mprotect() limit in the sandbox module from 16 MB to
10367 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
10369 o Minor bugfixes (logging):
10370 - When decompressing, do not warn if we fail to decompress using a
10371 compression method that we merely guessed. Fixes part of bug
10372 22670; bugfix on 0.1.1.14-alpha.
10373 - When decompressing, treat mismatch between content-encoding and
10374 actual compression type as a protocol warning. Fixes part of bug
10375 22670; bugfix on 0.1.1.9-alpha.
10376 - Downgrade "assigned_to_cpuworker failed" message to info-level
10377 severity. In every case that can reach it, either a better warning
10378 has already been logged, or no warning is warranted. Fixes bug
10379 22356; bugfix on 0.2.6.3-alpha.
10380 - Demote a warn that was caused by libevent delays to info if
10381 netflow padding is less than 4.5 seconds late, or to notice
10382 if it is more (4.5 seconds is the amount of time that a netflow
10383 record might be emitted after, if we chose the maximum timeout).
10384 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
10386 o Minor bugfixes (process behavior):
10387 - When exiting because of an error, always exit with a nonzero exit
10388 status. Previously, we would fail to report an error in our exit
10389 status in cases related to __OwningControllerProcess failure,
10390 lockfile contention, and Ed25519 key initialization. Fixes bug
10391 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
10392 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
10396 - Add a manpage description for the key-pinning-journal file. Closes
10398 - Correctly note that bandwidth accounting values are stored in the
10399 state file, and the bw_accounting file is now obsolete. Closes
10401 - Document more of the files in the Tor data directory, including
10402 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
10403 approved-routers, sr-random, and diff-cache. Found while fixing
10407 Changes in version 0.3.0.9 - 2017-06-29
10408 Tor 0.3.0.9 fixes a path selection bug that would allow a client
10409 to use a guard that was in the same network family as a chosen exit
10410 relay. This is a security regression; all clients running earlier
10411 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
10414 This release also backports several other bugfixes from the 0.3.1.x
10417 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
10418 - When choosing which guard to use for a circuit, avoid the exit's
10419 family along with the exit itself. Previously, the new guard
10420 selection logic avoided the exit, but did not consider its family.
10421 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
10422 006 and CVE-2017-0377.
10424 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
10425 - Don't block bootstrapping when a primary bridge is offline and we
10426 can't get its descriptor. Fixes bug 22325; fixes one case of bug
10427 21969; bugfix on 0.3.0.3-alpha.
10429 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
10430 - When starting with an old consensus, do not add new entry guards
10431 unless the consensus is "reasonably live" (under 1 day old). Fixes
10432 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
10434 o Minor features (geoip):
10435 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
10438 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
10439 - Reject version numbers with non-numeric prefixes (such as +, -, or
10440 whitespace). Disallowing whitespace prevents differential version
10441 parsing between POSIX-based and Windows platforms. Fixes bug 21507
10442 and part of 21508; bugfix on 0.0.8pre1.
10444 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
10445 - Permit the fchmod system call, to avoid crashing on startup when
10446 starting with the seccomp2 sandbox and an unexpected set of
10447 permissions on the data directory or its contents. Fixes bug
10448 22516; bugfix on 0.2.5.4-alpha.
10450 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
10451 - Fix a memset() off the end of an array when packing cells. This
10452 bug should be harmless in practice, since the corrupted bytes are
10453 still in the same structure, and are always padding bytes,
10454 ignored, or immediately overwritten, depending on compiler
10455 behavior. Nevertheless, because the memset()'s purpose is to make
10456 sure that any other cell-handling bugs can't expose bytes to the
10457 network, we need to fix it. Fixes bug 22737; bugfix on
10458 0.2.4.11-alpha. Fixes CID 1401591.
10461 Changes in version 0.3.1.3-alpha - 2017-06-08
10462 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
10463 remotely crash a hidden service with an assertion failure. Anyone
10464 running a hidden service should upgrade to this version, or to some
10465 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
10467 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
10468 that sometimes made relays unreliable, as well as several other
10469 bugfixes described below.
10471 o Major bugfixes (hidden service, relay, security):
10472 - Fix a remotely triggerable assertion failure when a hidden service
10473 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
10474 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
10475 - Fix a remotely triggerable assertion failure caused by receiving a
10476 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10477 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10480 o Major bugfixes (relay, link handshake):
10481 - When performing the v3 link handshake on a TLS connection, report
10482 that we have the x509 certificate that we actually used on that
10483 connection, even if we have changed certificates since that
10484 connection was first opened. Previously, we would claim to have
10485 used our most recent x509 link certificate, which would sometimes
10486 make the link handshake fail. Fixes one case of bug 22460; bugfix
10489 o Major bugfixes (relays, key management):
10490 - Regenerate link and authentication certificates whenever the key
10491 that signs them changes; also, regenerate link certificates
10492 whenever the signed key changes. Previously, these processes were
10493 only weakly coupled, and we relays could (for minutes to hours)
10494 wind up with an inconsistent set of keys and certificates, which
10495 other relays would not accept. Fixes two cases of bug 22460;
10496 bugfix on 0.3.0.1-alpha.
10497 - When sending an Ed25519 signing->link certificate in a CERTS cell,
10498 send the certificate that matches the x509 certificate that we
10499 used on the TLS connection. Previously, there was a race condition
10500 if the TLS context rotated after we began the TLS handshake but
10501 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
10504 o Major bugfixes (torrc, crash):
10505 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
10506 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
10508 o Minor features (code style):
10509 - Add "Falls through" comments to our codebase, in order to silence
10510 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10511 Stieger. Closes ticket 22446.
10513 o Minor features (diagnostic):
10514 - Add logging messages to try to diagnose a rare bug that seems to
10515 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
10516 think this is happening because of incorrect system clocks, but
10517 we'd like to know for certain. Diagnostic for bug 22466.
10519 o Minor bugfixes (correctness):
10520 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10521 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10523 o Minor bugfixes (directory protocol):
10524 - Check for libzstd >= 1.1, because older versions lack the
10525 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
10527 o Minor bugfixes (link handshake):
10528 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
10529 months, and regenerate it when it is within one month of expiring.
10530 Previously, we had generated this certificate at startup with a
10531 ten-year lifetime, but that could lead to weird behavior when Tor
10532 was started with a grossly inaccurate clock. Mitigates bug 22466;
10533 mitigation on 0.3.0.1-alpha.
10535 o Minor bugfixes (storage directories):
10536 - Always check for underflows in the cached storage directory usage.
10537 If the usage does underflow, re-calculate it. Also, avoid a
10538 separate underflow when the usage is not known. Fixes bug 22424;
10539 bugfix on 0.3.1.1-alpha.
10541 o Minor bugfixes (unit tests):
10542 - The unit tests now pass on systems where localhost is misconfigured
10543 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
10547 - Clarify the manpage for the (deprecated) torify script. Closes
10550 Changes in version 0.3.0.8 - 2017-06-08
10551 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
10552 remotely crash a hidden service with an assertion failure. Anyone
10553 running a hidden service should upgrade to this version, or to some
10554 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
10556 Tor 0.3.0.8 also includes fixes for several key management bugs
10557 that sometimes made relays unreliable, as well as several other
10558 bugfixes described below.
10560 o Major bugfixes (hidden service, relay, security, backport
10561 from 0.3.1.3-alpha):
10562 - Fix a remotely triggerable assertion failure when a hidden service
10563 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
10564 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
10565 - Fix a remotely triggerable assertion failure caused by receiving a
10566 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10567 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10570 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
10571 - When performing the v3 link handshake on a TLS connection, report
10572 that we have the x509 certificate that we actually used on that
10573 connection, even if we have changed certificates since that
10574 connection was first opened. Previously, we would claim to have
10575 used our most recent x509 link certificate, which would sometimes
10576 make the link handshake fail. Fixes one case of bug 22460; bugfix
10579 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
10580 - Regenerate link and authentication certificates whenever the key
10581 that signs them changes; also, regenerate link certificates
10582 whenever the signed key changes. Previously, these processes were
10583 only weakly coupled, and we relays could (for minutes to hours)
10584 wind up with an inconsistent set of keys and certificates, which
10585 other relays would not accept. Fixes two cases of bug 22460;
10586 bugfix on 0.3.0.1-alpha.
10587 - When sending an Ed25519 signing->link certificate in a CERTS cell,
10588 send the certificate that matches the x509 certificate that we
10589 used on the TLS connection. Previously, there was a race condition
10590 if the TLS context rotated after we began the TLS handshake but
10591 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
10594 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
10595 - Stop rejecting v3 hidden service descriptors because their size
10596 did not match an old padding rule. Fixes bug 22447; bugfix on
10599 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
10600 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10601 December 2016 (of which ~126 were still functional) with a list of
10602 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10603 2017. Resolves ticket 21564.
10605 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
10606 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
10607 bug 22252; bugfix on 0.2.9.3-alpha.
10609 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
10610 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10611 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10613 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
10614 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
10615 months, and regenerate it when it is within one month of expiring.
10616 Previously, we had generated this certificate at startup with a
10617 ten-year lifetime, but that could lead to weird behavior when Tor
10618 was started with a grossly inaccurate clock. Mitigates bug 22466;
10619 mitigation on 0.3.0.1-alpha.
10621 o Minor bugfixes (memory leak, directory authority, backport from
10623 - When directory authorities reject a router descriptor due to
10624 keypinning, free the router descriptor rather than leaking the
10625 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
10628 Changes in version 0.2.9.11 - 2017-06-08
10629 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
10630 remotely crash a hidden service with an assertion failure. Anyone
10631 running a hidden service should upgrade to this version, or to some
10632 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10633 are not affected by TROVE-2017-004.)
10635 Tor 0.2.9.11 also backports fixes for several key management bugs
10636 that sometimes made relays unreliable, as well as several other
10637 bugfixes described below.
10639 o Major bugfixes (hidden service, relay, security, backport
10640 from 0.3.1.3-alpha):
10641 - Fix a remotely triggerable assertion failure caused by receiving a
10642 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10643 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10646 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
10647 - When performing the v3 link handshake on a TLS connection, report
10648 that we have the x509 certificate that we actually used on that
10649 connection, even if we have changed certificates since that
10650 connection was first opened. Previously, we would claim to have
10651 used our most recent x509 link certificate, which would sometimes
10652 make the link handshake fail. Fixes one case of bug 22460; bugfix
10655 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
10656 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10657 December 2016 (of which ~126 were still functional) with a list of
10658 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10659 2017. Resolves ticket 21564.
10661 o Minor features (future-proofing, backport from 0.3.0.7):
10662 - Tor no longer refuses to download microdescriptors or descriptors if
10663 they are listed as "published in the future". This change will
10664 eventually allow us to stop listing meaningful "published" dates
10665 in microdescriptor consensuses, and thereby allow us to reduce the
10666 resources required to download consensus diffs by over 50%.
10667 Implements part of ticket 21642; implements part of proposal 275.
10669 o Minor features (directory authorities, backport from 0.3.0.4-rc)
10670 - Directory authorities now reject relays running versions
10671 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
10672 suffer from bug 20499 and don't keep their consensus cache
10673 up-to-date. Resolves ticket 20509.
10675 o Minor features (geoip):
10676 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10679 o Minor bugfixes (control port, backport from 0.3.0.6):
10680 - The GETINFO extra-info/digest/<digest> command was broken because
10681 of a wrong base16 decode return value check, introduced when
10682 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
10684 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
10685 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10686 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10688 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
10689 - The getpid() system call is now permitted under the Linux seccomp2
10690 sandbox, to avoid crashing with versions of OpenSSL (and other
10691 libraries) that attempt to learn the process's PID by using the
10692 syscall rather than the VDSO code. Fixes bug 21943; bugfix
10695 o Minor bugfixes (memory leak, directory authority, backport
10696 from 0.3.1.2-alpha):
10697 - When directory authorities reject a router descriptor due to
10698 keypinning, free the router descriptor rather than leaking the
10699 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
10701 Changes in version 0.2.8.14 - 2017-06-08
10702 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
10703 remotely crash a hidden service with an assertion failure. Anyone
10704 running a hidden service should upgrade to this version, or to some
10705 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10706 are not affected by TROVE-2017-004.)
10708 o Major bugfixes (hidden service, relay, security):
10709 - Fix a remotely triggerable assertion failure caused by receiving a
10710 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10711 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10714 o Minor features (geoip):
10715 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10718 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
10719 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10720 December 2016 (of which ~126 were still functional) with a list of
10721 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10722 2017. Resolves ticket 21564.
10724 o Minor bugfixes (correctness):
10725 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10726 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10728 Changes in version 0.2.7.8 - 2017-06-08
10729 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
10730 remotely crash a hidden service with an assertion failure. Anyone
10731 running a hidden service should upgrade to this version, or to some
10732 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10733 are not affected by TROVE-2017-004.)
10735 o Major bugfixes (hidden service, relay, security):
10736 - Fix a remotely triggerable assertion failure caused by receiving a
10737 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10738 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10741 o Minor features (geoip):
10742 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10745 o Minor bugfixes (correctness):
10746 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10747 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10750 Changes in version 0.2.6.12 - 2017-06-08
10751 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
10752 remotely crash a hidden service with an assertion failure. Anyone
10753 running a hidden service should upgrade to this version, or to some
10754 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10755 are not affected by TROVE-2017-004.)
10757 o Major bugfixes (hidden service, relay, security):
10758 - Fix a remotely triggerable assertion failure caused by receiving a
10759 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10760 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10763 o Minor features (geoip):
10764 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10767 o Minor bugfixes (correctness):
10768 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10769 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10771 Changes in version 0.2.5.14 - 2017-06-08
10772 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
10773 remotely crash a hidden service with an assertion failure. Anyone
10774 running a hidden service should upgrade to this version, or to some
10775 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10776 are not affected by TROVE-2017-004.)
10778 o Major bugfixes (hidden service, relay, security):
10779 - Fix a remotely triggerable assertion failure caused by receiving a
10780 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10781 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10784 o Minor features (geoip):
10785 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10788 o Minor bugfixes (correctness):
10789 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10790 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10792 Changes in version 0.2.4.29 - 2017-06-08
10793 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
10794 remotely crash a hidden service with an assertion failure. Anyone
10795 running a hidden service should upgrade to this version, or to some
10796 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10797 are not affected by TROVE-2017-004.)
10799 o Major bugfixes (hidden service, relay, security):
10800 - Fix a remotely triggerable assertion failure caused by receiving a
10801 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10802 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10805 o Minor features (geoip):
10806 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10809 o Minor bugfixes (correctness):
10810 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10811 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10814 Changes in version 0.3.1.2-alpha - 2017-05-26
10815 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
10816 fixes a few bugs found while testing 0.3.1.1-alpha, including a
10817 memory corruption bug that affected relay stability.
10819 o Major bugfixes (crash, relay):
10820 - Fix a memory-corruption bug in relays that set MyFamily.
10821 Previously, they would double-free MyFamily elements when making
10822 the next descriptor or when changing their configuration. Fixes
10823 bug 22368; bugfix on 0.3.1.1-alpha.
10825 o Minor bugfixes (logging):
10826 - Log a better message when a directory authority replies to an
10827 upload with an unexpected status code. Fixes bug 11121; bugfix
10830 o Minor bugfixes (memory leak, directory authority):
10831 - When directory authorities reject a router descriptor due to
10832 keypinning, free the router descriptor rather than leaking the
10833 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
10836 Changes in version 0.3.1.1-alpha - 2017-05-22
10837 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
10838 reduces the bandwidth usage for Tor's directory protocol, adds some
10839 basic padding to resist netflow-based traffic analysis and to serve as
10840 the basis of other padding in the future, and adds rust support to the
10843 It also contains numerous other small features and improvements to
10844 security, correctness, and performance.
10846 Below are the changes since 0.3.0.7.
10848 o Major features (directory protocol):
10849 - Tor relays and authorities can now serve clients an abbreviated
10850 version of the consensus document, containing only the changes
10851 since an older consensus document that the client holds. Clients
10852 now request these documents when available. When both client and
10853 server use this new protocol, they will use far less bandwidth (up
10854 to 94% less) to keep the client's consensus up-to-date. Implements
10855 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
10856 - Tor can now compress directory traffic with lzma or with zstd
10857 compression algorithms, which can deliver better bandwidth
10858 performance. Because lzma is computationally expensive, it's only
10859 used for documents that can be compressed once and served many
10860 times. Support for these algorithms requires that tor is built
10861 with the libzstd and/or liblzma libraries available. Implements
10862 proposal 278; closes ticket 21662.
10863 - Relays now perform the more expensive compression operations, and
10864 consensus diff generation, in worker threads. This separation
10865 avoids delaying the main thread when a new consensus arrives.
10867 o Major features (experimental):
10868 - Tor can now build modules written in Rust. To turn this on, pass
10869 the "--enable-rust" flag to the configure script. It's not time to
10870 get excited yet: currently, there is no actual Rust functionality
10871 beyond some simple glue code, and a notice at startup to tell you
10872 that Rust is running. Still, we hope that programmers and
10873 packagers will try building Tor with Rust support, so that we can
10874 find issues and solve portability problems. Closes ticket 22106.
10876 o Major features (traffic analysis resistance):
10877 - Connections between clients and relays now send a padding cell in
10878 each direction every 1.5 to 9.5 seconds (tunable via consensus
10879 parameters). This padding will not resist specialized
10880 eavesdroppers, but it should be enough to make many ISPs' routine
10881 network flow logging less useful in traffic analysis against
10884 Padding is negotiated using Tor's link protocol, so both relays
10885 and clients must upgrade for this to take effect. Clients may
10886 still send padding despite the relay's version by setting
10887 ConnectionPadding 1 in torrc, and may disable padding by setting
10888 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
10889 users with the torrc option ReducedConnectionPadding. Implements
10890 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
10891 - Relays will publish 24 hour totals of padding and non-padding cell
10892 counts to their extra-info descriptors, unless PaddingStatistics 0
10893 is set in torrc. These 24 hour totals are also rounded to
10894 multiples of 10000.
10896 o Major bugfixes (connection usage):
10897 - We use NETINFO cells to try to determine if both relays involved
10898 in a connection will agree on the canonical status of that
10899 connection. We prefer the connections where this is the case for
10900 extend cells, and try to close connections where relays disagree
10901 on their canonical status early. Also, we now prefer the oldest
10902 valid connection for extend cells. These two changes should reduce
10903 the number of long-term connections that are kept open between
10904 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
10905 - Relays now log hourly statistics (look for
10906 "channel_check_for_duplicates" lines) on the total number of
10907 connections to other relays. If the number of connections per
10908 relay is unexpectedly large, this log message is at notice level.
10909 Otherwise it is at info.
10911 o Major bugfixes (entry guards):
10912 - Don't block bootstrapping when a primary bridge is offline and we
10913 can't get its descriptor. Fixes bug 22325; fixes one case of bug
10914 21969; bugfix on 0.3.0.3-alpha.
10916 o Major bugfixes (linux TPROXY support):
10917 - Fix a typo that had prevented TPROXY-based transparent proxying
10918 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10919 Patch from "d4fq0fQAgoJ".
10921 o Minor features (security, windows):
10922 - Enable a couple of pieces of Windows hardening: one
10923 (HeapEnableTerminationOnCorruption) that has been on-by-default
10924 since Windows 8, and unavailable before Windows 7; and one
10925 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
10926 affect us, but shouldn't do any harm. Closes ticket 21953.
10928 o Minor features (config options):
10929 - Allow "%include" directives in torrc configuration files. These
10930 directives import the settings from other files, or from all the
10931 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
10932 - Make SAVECONF return an error when overwriting a torrc that has
10933 includes. Using SAVECONF with the FORCE option will allow it to
10934 overwrite torrc even if includes are used. Related to ticket 1922.
10935 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
10936 will work without the FORCE option. Related to ticket 1922.
10938 o Minor features (controller):
10939 - Warn the first time that a controller requests data in the long-
10940 deprecated 'GETINFO network-status' format. Closes ticket 21703.
10942 o Minor features (defaults):
10943 - The default value for UseCreateFast is now 0: clients which
10944 haven't yet received a consensus document will now use a proper
10945 ntor handshake to talk to their directory servers whenever they
10946 can. Closes ticket 21407.
10947 - Onion key rotation and expiry intervals are now defined as a
10948 network consensus parameter, per proposal 274. The default
10949 lifetime of an onion key is increased from 7 to 28 days. Old onion
10950 keys will expire after 7 days by default. This change will make
10951 consensus diffs much smaller, and save significant bandwidth.
10952 Closes ticket 21641.
10954 o Minor features (fallback directory list):
10955 - Update the fallback directory mirror whitelist and blacklist based
10956 on operator emails. Closes task 21121.
10957 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10958 December 2016 (of which ~126 were still functional) with a list of
10959 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10960 2017. Resolves ticket 21564.
10962 o Minor features (hidden services, logging):
10963 - Log a message when a hidden service descriptor has fewer
10964 introduction points than specified in
10965 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
10966 - Log a message when a hidden service reaches its introduction point
10967 circuit limit, and when that limit is reset. Follow up to ticket
10968 21594; closes ticket 21622.
10969 - Warn user if multiple entries in EntryNodes and at least one
10970 HiddenService are used together. Pinning EntryNodes along with a
10971 hidden service can be possibly harmful; for instance see ticket
10972 14917 or 21155. Closes ticket 21155.
10974 o Minor features (linux seccomp2 sandbox):
10975 - We now have a document storage backend compatible with the Linux
10976 seccomp2 sandbox. This backend is used for consensus documents and
10977 diffs between them; in the long term, we'd like to use it for
10978 unparseable directory material too. Closes ticket 21645
10979 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
10980 from 1MB to 16MB. This was necessary with the glibc allocator in
10981 order to allow worker threads to allocate more memory -- which in
10982 turn is necessary because of our new use of worker threads for
10983 compression. Closes ticket 22096.
10985 o Minor features (logging):
10986 - Log files are no longer created world-readable by default.
10987 (Previously, most distributors would store the logs in a non-
10988 world-readable location to prevent inappropriate access. This
10989 change is an extra precaution.) Closes ticket 21729; patch
10992 o Minor features (performance):
10993 - Our Keccak (SHA-3) implementation now accesses memory more
10994 efficiently, especially on little-endian systems. Closes
10996 - Add an O(1) implementation of channel_find_by_global_id(), to
10997 speed some controller functions.
10999 o Minor features (relay, configuration):
11000 - The MyFamily option may now be repeated as many times as desired,
11001 for relays that want to configure large families. Closes ticket
11002 4998; patch by Daniel Pinto.
11004 o Minor features (safety):
11005 - Add an explicit check to extrainfo_parse_entry_from_string() for
11006 NULL inputs. We don't believe this can actually happen, but it may
11007 help silence a warning from the Clang analyzer. Closes
11010 o Minor features (testing):
11011 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
11012 When Tor is compiled with this option, we disable a number of
11013 redundant memory-safety failsafes that are intended to stop bugs
11014 from becoming security issues. This makes it easier to hunt for
11015 bugs that would be security issues without the failsafes turned
11016 on. Closes ticket 21439.
11017 - Add a general event-tracing instrumentation support to Tor. This
11018 subsystem will enable developers and researchers to add fine-
11019 grained instrumentation to their Tor instances, for use when
11020 examining Tor network performance issues. There are no trace
11021 events yet, and event-tracing is off by default unless enabled at
11022 compile time. Implements ticket 13802.
11023 - Improve our version parsing tests: add tests for typical version
11024 components, add tests for invalid versions, including numeric
11025 range and non-numeric prefixes. Unit tests 21278, 21450, and
11026 21507. Partially implements 21470.
11028 o Minor bugfixes (bandwidth accounting):
11029 - Roll over monthly accounting at the configured hour and minute,
11030 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11031 Found by Andrey Karpov with PVS-Studio.
11033 o Minor bugfixes (code correctness):
11034 - Accurately identify client connections by their lack of peer
11035 authentication. This means that we bail out earlier if asked to
11036 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
11039 o Minor bugfixes (configuration):
11040 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
11041 bug 22252; bugfix on 0.2.9.3-alpha.
11043 o Minor bugfixes (connection lifespan):
11044 - Allow more control over how long TLS connections are kept open:
11045 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
11046 single option called CircuitsAvailableTimeout. Also, allow the
11047 consensus to control the default values for both this preference
11048 and the lifespan of relay-to-relay connections. Fixes bug 17592;
11049 bugfix on 0.2.5.5-alpha.
11050 - Increase the initial circuit build timeout testing frequency, to
11051 help ensure that ReducedConnectionPadding clients finish learning
11052 a timeout before their orconn would expire. The initial testing
11053 rate was set back in the days of TAP and before the Tor Browser
11054 updater, when we had to be much more careful about new clients
11055 making lots of circuits. With this change, a circuit build timeout
11056 is learned in about 15-20 minutes, instead of 100-120 minutes.
11058 o Minor bugfixes (controller):
11059 - GETINFO onions/current and onions/detached no longer respond with
11060 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
11061 - Trigger HS descriptor events on the control port when the client
11062 fails to pick a hidden service directory for a hidden service.
11063 This can happen if all the hidden service directories are in
11064 ExcludeNodes, or they have all been queried within the last 15
11065 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
11067 o Minor bugfixes (directory authority):
11068 - When rejecting a router descriptor for running an obsolete version
11069 of Tor without ntor support, warn about the obsolete tor version,
11070 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
11071 - Prevent the shared randomness subsystem from asserting when
11072 initialized by a bridge authority with an incomplete configuration
11073 file. Fixes bug 21586; bugfix on 0.2.9.8.
11075 o Minor bugfixes (exit-side DNS):
11076 - Fix an untriggerable assertion that checked the output of a
11077 libevent DNS error, so that the assertion actually behaves as
11078 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
11079 Karpov using PVS-Studio.
11081 o Minor bugfixes (fallback directories):
11082 - Make the usage example in updateFallbackDirs.py actually work, and
11083 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
11084 - Decrease the guard flag average required to be a fallback. This
11085 allows us to keep relays that have their guard flag removed when
11086 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
11087 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
11088 bugfix on 0.2.8.1-alpha.
11089 - Make sure fallback directory mirrors have the same address, port,
11090 and relay identity key for at least 30 days before they are
11091 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
11093 o Minor bugfixes (hidden services):
11094 - Stop printing a cryptic warning when a hidden service gets a
11095 request to connect to a virtual port that it hasn't configured.
11096 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
11097 - Simplify hidden service descriptor creation by using an existing
11098 flag to check if an introduction point is established. Fixes bug
11099 21599; bugfix on 0.2.7.2-alpha.
11101 o Minor bugfixes (memory leak):
11102 - Fix a small memory leak at exit from the backtrace handler code.
11103 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
11105 o Minor bugfixes (protocol, logging):
11106 - Downgrade a log statement about unexpected relay cells from "bug"
11107 to "protocol warning", because there is at least one use case
11108 where it can be triggered by a buggy tor implementation. Fixes bug
11109 21293; bugfix on 0.1.1.14-alpha.
11111 o Minor bugfixes (testing):
11112 - Use unbuffered I/O for utility functions around the
11113 process_handle_t type. This fixes unit test failures reported on
11114 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
11115 - Make display of captured unit test log messages consistent. Fixes
11116 bug 21510; bugfix on 0.2.9.3-alpha.
11117 - Make test-network.sh always call chutney's test-network.sh.
11118 Previously, this only worked on systems which had bash installed,
11119 due to some bash-specific code in the script. Fixes bug 19699;
11120 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
11122 o Minor bugfixes (voting consistency):
11123 - Reject version numbers with non-numeric prefixes (such as +, -, or
11124 whitespace). Disallowing whitespace prevents differential version
11125 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11126 and part of 21508; bugfix on 0.0.8pre1.
11128 o Minor bugfixes (windows, relay):
11129 - Resolve "Failure from drain_fd: No error" warnings on Windows
11130 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
11132 o Code simplification and refactoring:
11133 - Break up the 630-line function connection_dir_client_reached_eof()
11134 into a dozen smaller functions. This change should help
11135 maintainability and readability of the client directory code.
11136 - Isolate our use of the openssl headers so that they are only
11137 included from our crypto wrapper modules, and from tests that
11138 examine those modules' internals. Closes ticket 21841.
11139 - Simplify our API to launch directory requests, making it more
11140 extensible and less error-prone. Now it's easier to add extra
11141 headers to directory requests. Closes ticket 21646.
11142 - Our base64 decoding functions no longer overestimate the output
11143 space that they need when parsing unpadded inputs. Closes
11145 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
11146 Resolves ticket 22213.
11147 - The logic that directory caches use to spool request to clients,
11148 serving them one part at a time so as not to allocate too much
11149 memory, has been refactored for consistency. Previously there was
11150 a separate spooling implementation per type of spoolable data. Now
11151 there is one common spooling implementation, with extensible data
11152 types. Closes ticket 21651.
11153 - Tor's compression module now supports multiple backends. Part of
11154 the implementation for proposal 278; closes ticket 21663.
11157 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
11158 Closes ticket 21873.
11159 - Correct documentation about the default DataDirectory value.
11160 Closes ticket 21151.
11161 - Document the default behavior of NumEntryGuards and
11162 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
11164 - Document key=value pluggable transport arguments for Bridge lines
11165 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
11166 - Note that bandwidth-limiting options don't affect TCP headers or
11167 DNS. Closes ticket 17170.
11169 o Removed features (configuration options, all in ticket 22060):
11170 - These configuration options are now marked Obsolete, and no longer
11171 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
11172 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
11173 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
11174 in 0.2.9.2-alpha and have now been removed. The previous default
11175 behavior is now always chosen; the previous (less secure) non-
11176 default behavior is now unavailable.
11177 - CloseHSClientCircuitsImmediatelyOnTimeout and
11178 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
11179 0.2.9.2-alpha and now have been removed. HS circuits never close
11180 on circuit build timeout; they have a longer timeout period.
11181 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
11182 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
11183 (and others) to configure listen-only and advertise-only addresses.
11185 o Removed features (tools):
11186 - We've removed the tor-checkkey tool from src/tools. Long ago, we
11187 used it to help people detect RSA keys that were generated by
11188 versions of Debian affected by CVE-2008-0166. But those keys have
11189 been out of circulation for ages, and this tool is no longer
11190 required. Closes ticket 21842.
11193 Changes in version 0.3.0.7 - 2017-05-15
11194 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
11195 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
11196 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
11197 clients are not affected.
11199 o Major bugfixes (hidden service directory, security):
11200 - Fix an assertion failure in the hidden service directory code, which
11201 could be used by an attacker to remotely cause a Tor relay process to
11202 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
11203 should upgrade. This security issue is tracked as TROVE-2017-002.
11204 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
11207 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11210 o Minor features (future-proofing):
11211 - Tor no longer refuses to download microdescriptors or descriptors
11212 if they are listed as "published in the future". This change will
11213 eventually allow us to stop listing meaningful "published" dates
11214 in microdescriptor consensuses, and thereby allow us to reduce the
11215 resources required to download consensus diffs by over 50%.
11216 Implements part of ticket 21642; implements part of proposal 275.
11218 o Minor bugfixes (Linux seccomp2 sandbox):
11219 - The getpid() system call is now permitted under the Linux seccomp2
11220 sandbox, to avoid crashing with versions of OpenSSL (and other
11221 libraries) that attempt to learn the process's PID by using the
11222 syscall rather than the VDSO code. Fixes bug 21943; bugfix
11226 Changes in version 0.3.0.6 - 2017-04-26
11227 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
11229 With the 0.3.0 series, clients and relays now use Ed25519 keys to
11230 authenticate their link connections to relays, rather than the old
11231 RSA1024 keys that they used before. (Circuit crypto has been
11232 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
11233 the guard selection and replacement algorithm to behave more robustly
11234 in the presence of unreliable networks, and to resist guard-
11237 This series also includes numerous other small features and bugfixes,
11238 along with more groundwork for the upcoming hidden-services revamp.
11240 Per our stable release policy, we plan to support the Tor 0.3.0
11241 release series for at least the next nine months, or for three months
11242 after the first stable release of the 0.3.1 series: whichever is
11243 longer. If you need a release with long-term support, we recommend
11244 that you stay with the 0.2.9 series.
11246 Below are the changes since 0.3.0.5-rc. For a list of all changes
11247 since 0.2.9, see the ReleaseNotes file.
11249 o Minor features (geoip):
11250 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
11253 o Minor bugfixes (control port):
11254 - The GETINFO extra-info/digest/<digest> command was broken because
11255 of a wrong base16 decode return value check, introduced when
11256 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
11258 o Minor bugfixes (crash prevention):
11259 - Fix a (currently untriggerable, but potentially dangerous) crash
11260 bug when base32-encoding inputs whose sizes are not a multiple of
11261 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
11264 Changes in version 0.3.0.5-rc - 2017-04-05
11265 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
11266 0.3.0 release series.
11268 This is the second release candidate in the Tor 0.3.0 series, and has
11269 much fewer changes than the first. If we find no new bugs or
11270 regressions here, the first stable 0.3.0 release will be nearly
11273 o Major bugfixes (crash, directory connections):
11274 - Fix a rare crash when sending a begin cell on a circuit whose
11275 linked directory connection had already been closed. Fixes bug
11276 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
11278 o Major bugfixes (guard selection):
11279 - Fix a guard selection bug where Tor would refuse to bootstrap in
11280 some cases if the user swapped a bridge for another bridge in
11281 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
11282 Reported by "torvlnt33r".
11284 o Minor features (geoip):
11285 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
11288 o Minor bugfix (compilation):
11289 - Fix a warning when compiling hs_service.c. Previously, it had no
11290 exported symbols when compiled for libor.a, resulting in a
11291 compilation warning from clang. Fixes bug 21825; bugfix
11294 o Minor bugfixes (hidden services):
11295 - Make hidden services check for failed intro point connections,
11296 even when they have exceeded their intro point creation limit.
11297 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
11298 - Make hidden services with 8 to 10 introduction points check for
11299 failed circuits immediately after startup. Previously, they would
11300 wait for 5 minutes before performing their first checks. Fixes bug
11301 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
11303 o Minor bugfixes (memory leaks):
11304 - Fix a memory leak when using GETCONF on a port option. Fixes bug
11305 21682; bugfix on 0.3.0.3-alpha.
11307 o Minor bugfixes (relay):
11308 - Avoid a double-marked-circuit warning that could happen when we
11309 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
11312 o Minor bugfixes (tests):
11313 - Run the entry_guard_parse_from_state_full() test with the time set
11314 to a specific date. (The guard state that this test was parsing
11315 contained guards that had expired since the test was first
11316 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
11319 - Update the description of the directory server options in the
11320 manual page, to clarify that a relay no longer needs to set
11321 DirPort in order to be a directory cache. Closes ticket 21720.
11325 Changes in version 0.2.8.13 - 2017-03-03
11326 Tor 0.2.8.13 backports a security fix from later Tor
11327 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
11328 this release, if for some reason they cannot upgrade to a later
11329 release series, and if they build Tor with the --enable-expensive-hardening
11332 Note that support for Tor 0.2.8.x is ending next year: we will not issue
11333 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
11334 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11336 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11337 - Fix an integer underflow bug when comparing malformed Tor
11338 versions. This bug could crash Tor when built with
11339 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11340 0.2.9.8, which were built with -ftrapv by default. In other cases
11341 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11342 on 0.0.8pre1. Found by OSS-Fuzz.
11344 o Minor features (geoip):
11345 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11349 Changes in version 0.2.7.7 - 2017-03-03
11350 Tor 0.2.7.7 backports a number of security fixes from later Tor
11351 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
11352 this release, if for some reason they cannot upgrade to a later
11355 Note that support for Tor 0.2.7.x is ending this year: we will not issue
11356 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
11357 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11359 o Directory authority changes (backport from 0.2.8.5-rc):
11360 - Urras is no longer a directory authority. Closes ticket 19271.
11362 o Directory authority changes (backport from 0.2.9.2-alpha):
11363 - The "Tonga" bridge authority has been retired; the new bridge
11364 authority is "Bifroest". Closes tickets 19728 and 19690.
11366 o Directory authority key updates (backport from 0.2.8.1-alpha):
11367 - Update the V3 identity key for the dannenberg directory authority:
11368 it was changed on 18 November 2015. Closes task 17906. Patch
11371 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11372 - Fix a bug in parsing that could cause clients to read a single
11373 byte past the end of an allocated region. This bug could be used
11374 to cause hardened clients (built with --enable-expensive-hardening)
11375 to crash if they tried to visit a hostile hidden service. Non-
11376 hardened clients are only affected depending on the details of
11377 their platform's memory allocator. Fixes bug 21018; bugfix on
11378 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11379 2016-12-002 and as CVE-2016-1254.
11381 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
11382 - Stop a crash that could occur when a client running with DNSPort
11383 received a query with multiple address types, and the first
11384 address type was not supported. Found and fixed by Scott Dial.
11385 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11386 - Prevent a class of security bugs caused by treating the contents
11387 of a buffer chunk as if they were a NUL-terminated string. At
11388 least one such bug seems to be present in all currently used
11389 versions of Tor, and would allow an attacker to remotely crash
11390 most Tor instances, especially those compiled with extra compiler
11391 hardening. With this defense in place, such bugs can't crash Tor,
11392 though we should still fix them as they occur. Closes ticket
11393 20384 (TROVE-2016-10-001).
11395 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11396 - Avoid a difficult-to-trigger heap corruption attack when extending
11397 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11398 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11399 Reported by Guido Vranken.
11401 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11402 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11403 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11405 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11406 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11407 pointer to the previous (uninitialized) key value. The impact here
11408 should be limited to a difficult-to-trigger crash, if OpenSSL is
11409 running an engine that makes key generation failures possible, or
11410 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11411 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11414 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11415 - Fix an integer underflow bug when comparing malformed Tor
11416 versions. This bug could crash Tor when built with
11417 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11418 0.2.9.8, which were built with -ftrapv by default. In other cases
11419 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11420 on 0.0.8pre1. Found by OSS-Fuzz.
11422 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11423 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11424 zero size. Check size argument to memwipe() for underflow. Fixes
11425 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11428 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11429 - Make Tor survive errors involving connections without a
11430 corresponding event object. Previously we'd fail with an
11431 assertion; now we produce a log message. Related to bug 16248.
11433 o Minor features (geoip):
11434 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11438 Changes in version 0.2.6.11 - 2017-03-03
11439 Tor 0.2.6.11 backports a number of security fixes from later Tor
11440 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
11441 this release, if for some reason they cannot upgrade to a later
11444 Note that support for Tor 0.2.6.x is ending this year: we will not issue
11445 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
11446 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11448 o Directory authority changes (backport from 0.2.8.5-rc):
11449 - Urras is no longer a directory authority. Closes ticket 19271.
11451 o Directory authority changes (backport from 0.2.9.2-alpha):
11452 - The "Tonga" bridge authority has been retired; the new bridge
11453 authority is "Bifroest". Closes tickets 19728 and 19690.
11455 o Directory authority key updates (backport from 0.2.8.1-alpha):
11456 - Update the V3 identity key for the dannenberg directory authority:
11457 it was changed on 18 November 2015. Closes task 17906. Patch
11460 o Major features (security fixes, backport from 0.2.9.4-alpha):
11461 - Prevent a class of security bugs caused by treating the contents
11462 of a buffer chunk as if they were a NUL-terminated string. At
11463 least one such bug seems to be present in all currently used
11464 versions of Tor, and would allow an attacker to remotely crash
11465 most Tor instances, especially those compiled with extra compiler
11466 hardening. With this defense in place, such bugs can't crash Tor,
11467 though we should still fix them as they occur. Closes ticket
11468 20384 (TROVE-2016-10-001).
11470 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11471 - Fix a bug in parsing that could cause clients to read a single
11472 byte past the end of an allocated region. This bug could be used
11473 to cause hardened clients (built with --enable-expensive-hardening)
11474 to crash if they tried to visit a hostile hidden service. Non-
11475 hardened clients are only affected depending on the details of
11476 their platform's memory allocator. Fixes bug 21018; bugfix on
11477 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11478 2016-12-002 and as CVE-2016-1254.
11480 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
11481 - Stop a crash that could occur when a client running with DNSPort
11482 received a query with multiple address types, and the first
11483 address type was not supported. Found and fixed by Scott Dial.
11484 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11486 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
11487 - Fix an error that could cause us to read 4 bytes before the
11488 beginning of an openssl string. This bug could be used to cause
11489 Tor to crash on systems with unusual malloc implementations, or
11490 systems with unusual hardening installed. Fixes bug 17404; bugfix
11493 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11494 - Avoid a difficult-to-trigger heap corruption attack when extending
11495 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11496 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11497 Reported by Guido Vranken.
11499 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11500 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11501 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11503 o Major bugfixes (guard selection, backport from 0.2.7.6):
11504 - Actually look at the Guard flag when selecting a new directory
11505 guard. When we implemented the directory guard design, we
11506 accidentally started treating all relays as if they have the Guard
11507 flag during guard selection, leading to weaker anonymity and worse
11508 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
11511 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11512 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11513 pointer to the previous (uninitialized) key value. The impact here
11514 should be limited to a difficult-to-trigger crash, if OpenSSL is
11515 running an engine that makes key generation failures possible, or
11516 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11517 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11520 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11521 - Fix an integer underflow bug when comparing malformed Tor
11522 versions. This bug could crash Tor when built with
11523 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11524 0.2.9.8, which were built with -ftrapv by default. In other cases
11525 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11526 on 0.0.8pre1. Found by OSS-Fuzz.
11528 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11529 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11530 zero size. Check size argument to memwipe() for underflow. Fixes
11531 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11534 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11535 - Make Tor survive errors involving connections without a
11536 corresponding event object. Previously we'd fail with an
11537 assertion; now we produce a log message. Related to bug 16248.
11539 o Minor features (geoip):
11540 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11543 o Minor bugfixes (compilation, backport from 0.2.7.6):
11544 - Fix a compilation warning with Clang 3.6: Do not check the
11545 presence of an address which can never be NULL. Fixes bug 17781.
11548 Changes in version 0.2.5.13 - 2017-03-03
11549 Tor 0.2.5.13 backports a number of security fixes from later Tor
11550 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
11551 this release, if for some reason they cannot upgrade to a later
11554 Note that support for Tor 0.2.5.x is ending next year: we will not issue
11555 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
11556 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11558 o Directory authority changes (backport from 0.2.8.5-rc):
11559 - Urras is no longer a directory authority. Closes ticket 19271.
11561 o Directory authority changes (backport from 0.2.9.2-alpha):
11562 - The "Tonga" bridge authority has been retired; the new bridge
11563 authority is "Bifroest". Closes tickets 19728 and 19690.
11565 o Directory authority key updates (backport from 0.2.8.1-alpha):
11566 - Update the V3 identity key for the dannenberg directory authority:
11567 it was changed on 18 November 2015. Closes task 17906. Patch
11570 o Major features (security fixes, backport from 0.2.9.4-alpha):
11571 - Prevent a class of security bugs caused by treating the contents
11572 of a buffer chunk as if they were a NUL-terminated string. At
11573 least one such bug seems to be present in all currently used
11574 versions of Tor, and would allow an attacker to remotely crash
11575 most Tor instances, especially those compiled with extra compiler
11576 hardening. With this defense in place, such bugs can't crash Tor,
11577 though we should still fix them as they occur. Closes ticket
11578 20384 (TROVE-2016-10-001).
11580 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11581 - Fix a bug in parsing that could cause clients to read a single
11582 byte past the end of an allocated region. This bug could be used
11583 to cause hardened clients (built with --enable-expensive-hardening)
11584 to crash if they tried to visit a hostile hidden service. Non-
11585 hardened clients are only affected depending on the details of
11586 their platform's memory allocator. Fixes bug 21018; bugfix on
11587 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11588 2016-12-002 and as CVE-2016-1254.
11590 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
11591 - Stop a crash that could occur when a client running with DNSPort
11592 received a query with multiple address types, and the first
11593 address type was not supported. Found and fixed by Scott Dial.
11594 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11596 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
11597 - Fix an error that could cause us to read 4 bytes before the
11598 beginning of an openssl string. This bug could be used to cause
11599 Tor to crash on systems with unusual malloc implementations, or
11600 systems with unusual hardening installed. Fixes bug 17404; bugfix
11603 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11604 - Avoid a difficult-to-trigger heap corruption attack when extending
11605 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11606 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11607 Reported by Guido Vranken.
11609 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11610 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11611 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11613 o Major bugfixes (guard selection, backport from 0.2.7.6):
11614 - Actually look at the Guard flag when selecting a new directory
11615 guard. When we implemented the directory guard design, we
11616 accidentally started treating all relays as if they have the Guard
11617 flag during guard selection, leading to weaker anonymity and worse
11618 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
11621 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11622 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11623 pointer to the previous (uninitialized) key value. The impact here
11624 should be limited to a difficult-to-trigger crash, if OpenSSL is
11625 running an engine that makes key generation failures possible, or
11626 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11627 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11630 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11631 - Fix an integer underflow bug when comparing malformed Tor
11632 versions. This bug could crash Tor when built with
11633 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11634 0.2.9.8, which were built with -ftrapv by default. In other cases
11635 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11636 on 0.0.8pre1. Found by OSS-Fuzz.
11638 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11639 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11640 zero size. Check size argument to memwipe() for underflow. Fixes
11641 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11644 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11645 - Make Tor survive errors involving connections without a
11646 corresponding event object. Previously we'd fail with an
11647 assertion; now we produce a log message. Related to bug 16248.
11649 o Minor features (geoip):
11650 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11653 o Minor bugfixes (compilation, backport from 0.2.7.6):
11654 - Fix a compilation warning with Clang 3.6: Do not check the
11655 presence of an address which can never be NULL. Fixes bug 17781.
11657 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
11658 - Check for failures from crypto_early_init, and refuse to continue.
11659 A previous typo meant that we could keep going with an
11660 uninitialized crypto library, and would have OpenSSL initialize
11661 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
11662 when implementing ticket 4900. Patch by "teor".
11664 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
11665 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11666 a client authorized hidden service. Fixes bug 15823; bugfix
11670 Changes in version 0.2.4.28 - 2017-03-03
11671 Tor 0.2.4.28 backports a number of security fixes from later Tor
11672 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
11673 this release, if for some reason they cannot upgrade to a later
11676 Note that support for Tor 0.2.4.x is ending soon: we will not issue
11677 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
11678 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
11680 o Directory authority changes (backport from 0.2.8.5-rc):
11681 - Urras is no longer a directory authority. Closes ticket 19271.
11683 o Directory authority changes (backport from 0.2.9.2-alpha):
11684 - The "Tonga" bridge authority has been retired; the new bridge
11685 authority is "Bifroest". Closes tickets 19728 and 19690.
11687 o Directory authority key updates (backport from 0.2.8.1-alpha):
11688 - Update the V3 identity key for the dannenberg directory authority:
11689 it was changed on 18 November 2015. Closes task 17906. Patch
11692 o Major features (security fixes, backport from 0.2.9.4-alpha):
11693 - Prevent a class of security bugs caused by treating the contents
11694 of a buffer chunk as if they were a NUL-terminated string. At
11695 least one such bug seems to be present in all currently used
11696 versions of Tor, and would allow an attacker to remotely crash
11697 most Tor instances, especially those compiled with extra compiler
11698 hardening. With this defense in place, such bugs can't crash Tor,
11699 though we should still fix them as they occur. Closes ticket
11700 20384 (TROVE-2016-10-001).
11702 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11703 - Fix a bug in parsing that could cause clients to read a single
11704 byte past the end of an allocated region. This bug could be used
11705 to cause hardened clients (built with --enable-expensive-hardening)
11706 to crash if they tried to visit a hostile hidden service. Non-
11707 hardened clients are only affected depending on the details of
11708 their platform's memory allocator. Fixes bug 21018; bugfix on
11709 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11710 2016-12-002 and as CVE-2016-1254.
11712 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
11713 - Fix an error that could cause us to read 4 bytes before the
11714 beginning of an openssl string. This bug could be used to cause
11715 Tor to crash on systems with unusual malloc implementations, or
11716 systems with unusual hardening installed. Fixes bug 17404; bugfix
11719 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11720 - Avoid a difficult-to-trigger heap corruption attack when extending
11721 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11722 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11723 Reported by Guido Vranken.
11725 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11726 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11727 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11729 o Major bugfixes (guard selection, backport from 0.2.7.6):
11730 - Actually look at the Guard flag when selecting a new directory
11731 guard. When we implemented the directory guard design, we
11732 accidentally started treating all relays as if they have the Guard
11733 flag during guard selection, leading to weaker anonymity and worse
11734 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
11737 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11738 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11739 pointer to the previous (uninitialized) key value. The impact here
11740 should be limited to a difficult-to-trigger crash, if OpenSSL is
11741 running an engine that makes key generation failures possible, or
11742 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11743 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11746 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11747 - Fix an integer underflow bug when comparing malformed Tor
11748 versions. This bug could crash Tor when built with
11749 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11750 0.2.9.8, which were built with -ftrapv by default. In other cases
11751 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11752 on 0.0.8pre1. Found by OSS-Fuzz.
11754 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11755 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11756 zero size. Check size argument to memwipe() for underflow. Fixes
11757 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11760 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11761 - Make Tor survive errors involving connections without a
11762 corresponding event object. Previously we'd fail with an
11763 assertion; now we produce a log message. Related to bug 16248.
11765 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
11766 - Make it harder for attackers to overload hidden services with
11767 introductions, by blocking multiple introduction requests on the
11768 same circuit. Resolves ticket 15515.
11770 o Minor features (geoip):
11771 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11774 o Minor bugfixes (compilation, backport from 0.2.7.6):
11775 - Fix a compilation warning with Clang 3.6: Do not check the
11776 presence of an address which can never be NULL. Fixes bug 17781.
11778 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
11779 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11780 a client authorized hidden service. Fixes bug 15823; bugfix
11784 Changes in version 0.3.0.4-rc - 2017-03-01
11785 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
11786 0.3.0 release series, and introduces a few reliability features to
11787 keep them from coming back.
11789 This is the first release candidate in the Tor 0.3.0 series. If we
11790 find no new bugs or regressions here, the first stable 0.3.0 release
11791 will be nearly identical to it.
11793 o Major bugfixes (bridges):
11794 - When the same bridge is configured multiple times with the same
11795 identity, but at different address:port combinations, treat those
11796 bridge instances as separate guards. This fix restores the ability
11797 of clients to configure the same bridge with multiple pluggable
11798 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
11800 o Major bugfixes (hidden service directory v3):
11801 - Stop crashing on a failed v3 hidden service descriptor lookup
11802 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
11804 o Major bugfixes (parsing):
11805 - When parsing a malformed content-length field from an HTTP
11806 message, do not read off the end of the buffer. This bug was a
11807 potential remote denial-of-service attack against Tor clients and
11808 relays. A workaround was released in October 2016, to prevent this
11809 bug from crashing Tor. This is a fix for the underlying issue,
11810 which should no longer matter (if you applied the earlier patch).
11811 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
11812 using AFL (http://lcamtuf.coredump.cx/afl/).
11813 - Fix an integer underflow bug when comparing malformed Tor
11814 versions. This bug could crash Tor when built with
11815 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11816 0.2.9.8, which were built with -ftrapv by default. In other cases
11817 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11818 on 0.0.8pre1. Found by OSS-Fuzz.
11820 o Minor feature (protocol versioning):
11821 - Add new protocol version for proposal 224. HSIntro now advertises
11822 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
11824 o Minor features (directory authorities):
11825 - Directory authorities now reject descriptors that claim to be
11826 malformed versions of Tor. Helps prevent exploitation of
11828 - Reject version numbers with components that exceed INT32_MAX.
11829 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
11830 Fixes bug 21450; bugfix on 0.0.8pre1.
11831 - Directory authorities now reject relays running versions
11832 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
11833 suffer from bug 20499 and don't keep their consensus cache
11834 up-to-date. Resolves ticket 20509.
11836 o Minor features (geoip):
11837 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11840 o Minor features (reliability, crash):
11841 - Try better to detect problems in buffers where they might grow (or
11842 think they have grown) over 2 GB in size. Diagnostic for
11845 o Minor features (testing):
11846 - During 'make test-network-all', if tor logs any warnings, ask
11847 chutney to output them. Requires a recent version of chutney with
11848 the 21572 patch. Implements 21570.
11850 o Minor bugfixes (certificate expiration time):
11851 - Avoid using link certificates that don't become valid till some
11852 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
11854 o Minor bugfixes (code correctness):
11855 - Repair a couple of (unreachable or harmless) cases of the risky
11856 comparison-by-subtraction pattern that caused bug 21278.
11857 - Remove a redundant check for the UseEntryGuards option from the
11858 options_transition_affects_guards() function. Fixes bug 21492;
11859 bugfix on 0.3.0.1-alpha.
11861 o Minor bugfixes (directory mirrors):
11862 - Allow relays to use directory mirrors without a DirPort: these
11863 relays need to be contacted over their ORPorts using a begindir
11864 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
11865 - Clarify the message logged when a remote relay is unexpectedly
11866 missing an ORPort or DirPort: users were confusing this with a
11867 local port. Fixes another case of bug 20711; bugfix
11870 o Minor bugfixes (guards):
11871 - Don't warn about a missing guard state on timeout-measurement
11872 circuits: they aren't supposed to be using guards. Fixes an
11873 instance of bug 21007; bugfix on 0.3.0.1-alpha.
11874 - Silence a BUG() warning when attempting to use a guard whose
11875 descriptor we don't know, and make this scenario less likely to
11876 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
11878 o Minor bugfixes (hidden service):
11879 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
11880 cells. Previously, we were using sizeof() on a pointer, instead of
11881 the real destination buffer. Fortunately, that value was only used
11882 to double-check that there was enough room--which was already
11883 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
11885 o Minor bugfixes (testing):
11886 - Fix Raspbian build issues related to missing socket errno in
11887 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
11889 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
11890 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
11891 - Use bash in src/test/test-network.sh. This ensures we reliably
11892 call chutney's newer tools/test-network.sh when available. Fixes
11893 bug 21562; bugfix on 0.2.9.1-alpha.
11896 - Small fixes to the fuzzing documentation. Closes ticket 21472.
11899 Changes in version 0.2.9.10 - 2017-03-01
11900 Tor 0.2.9.10 backports a security fix from later Tor release. It also
11901 includes fixes for some major issues affecting directory authorities,
11902 LibreSSL compatibility, and IPv6 correctness.
11904 The Tor 0.2.9.x release series is now marked as a long-term-support
11905 series. We intend to backport security fixes to 0.2.9.x until at
11906 least January of 2020.
11908 o Major bugfixes (directory authority, 0.3.0.3-alpha):
11909 - During voting, when marking a relay as a probable sybil, do not
11910 clear its BadExit flag: sybils can still be bad in other ways
11911 too. (We still clear the other flags.) Fixes bug 21108; bugfix
11914 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
11915 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
11916 any IPv6 addresses. Instead, only reject a port over IPv6 if the
11917 exit policy rejects that port on more than an IPv6 /16 of
11918 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
11919 which rejected a relay's own IPv6 address by default. Fixes bug
11920 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
11922 o Major bugfixes (parsing, also in 0.3.0.4-rc):
11923 - Fix an integer underflow bug when comparing malformed Tor
11924 versions. This bug could crash Tor when built with
11925 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11926 0.2.9.8, which were built with -ftrapv by default. In other cases
11927 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11928 on 0.0.8pre1. Found by OSS-Fuzz.
11930 o Minor features (directory authorities, also in 0.3.0.4-rc):
11931 - Directory authorities now reject descriptors that claim to be
11932 malformed versions of Tor. Helps prevent exploitation of
11934 - Reject version numbers with components that exceed INT32_MAX.
11935 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
11936 Fixes bug 21450; bugfix on 0.0.8pre1.
11938 o Minor features (geoip):
11939 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11942 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
11943 - Autoconf now checks to determine if OpenSSL structures are opaque,
11944 instead of explicitly checking for OpenSSL version numbers. Part
11946 - Support building with recent LibreSSL code that uses opaque
11947 structures. Closes ticket 21359.
11949 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
11950 - Repair a couple of (unreachable or harmless) cases of the risky
11951 comparison-by-subtraction pattern that caused bug 21278.
11953 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
11954 - The tor-resolve command line tool now rejects hostnames over 255
11955 characters in length. Previously, it would silently truncate them,
11956 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
11957 Patch by "junglefowl".
11960 Changes in version 0.3.0.3-alpha - 2017-02-03
11961 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
11962 0.3.0.x development series, including some that could cause
11963 authorities to behave badly. There is also a fix for a longstanding
11964 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
11965 includes some smaller features and bugfixes.
11967 The Tor 0.3.0.x release series is now in patch-freeze: no additional
11968 features will be considered for inclusion in 0.3.0.x. We suspect that
11969 some bugs will probably remain, however, and we encourage people to
11972 o Major bugfixes (directory authority):
11973 - During voting, when marking a relay as a probable sybil, do not
11974 clear its BadExit flag: sybils can still be bad in other ways
11975 too. (We still clear the other flags.) Fixes bug 21108; bugfix
11977 - When deciding whether we have just found a router to be reachable,
11978 do not penalize it for not having performed an Ed25519 link
11979 handshake if it does not claim to support an Ed25519 handshake.
11980 Previously, we would treat such relays as non-running. Fixes bug
11981 21107; bugfix on 0.3.0.1-alpha.
11983 o Major bugfixes (entry guards):
11984 - Stop trying to build circuits through entry guards for which we
11985 have no descriptor. Also, stop crashing in the case that we *do*
11986 accidentally try to build a circuit in such a state. Fixes bug
11987 21242; bugfix on 0.3.0.1-alpha.
11989 o Major bugfixes (IPv6 Exits):
11990 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
11991 any IPv6 addresses. Instead, only reject a port over IPv6 if the
11992 exit policy rejects that port on more than an IPv6 /16 of
11993 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
11994 which rejected a relay's own IPv6 address by default. Fixes bug
11995 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
11997 o Minor feature (client):
11998 - Enable IPv6 traffic on the SocksPort by default. To disable this,
11999 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
12001 o Minor feature (fallback scripts):
12002 - Add a check_existing mode to updateFallbackDirs.py, which checks
12003 if fallbacks in the hard-coded list are working. Closes ticket
12004 20174. Patch by haxxpop.
12006 o Minor features (ciphersuite selection):
12007 - Clients now advertise a list of ciphersuites closer to the ones
12008 preferred by Firefox. Closes part of ticket 15426.
12009 - Allow relays to accept a wider range of ciphersuites, including
12010 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
12012 o Minor features (controller, configuration):
12013 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
12014 and so on, now comes with a __*Port variant that will not be saved
12015 to the torrc file by the controller's SAVECONF command. This
12016 change allows TorBrowser to set up a single-use domain socket for
12017 each time it launches Tor. Closes ticket 20956.
12018 - The GETCONF command can now query options that may only be
12019 meaningful in context-sensitive lists. This allows the controller
12020 to query the mixed SocksPort/__SocksPort style options introduced
12021 in feature 20956. Implements ticket 21300.
12023 o Minor features (portability, compilation):
12024 - Autoconf now checks to determine if OpenSSL structures are opaque,
12025 instead of explicitly checking for OpenSSL version numbers. Part
12027 - Support building with recent LibreSSL code that uses opaque
12028 structures. Closes ticket 21359.
12030 o Minor features (relay):
12031 - We now allow separation of exit and relay traffic to different
12032 source IP addresses, using the OutboundBindAddressExit and
12033 OutboundBindAddressOR options respectively. Closes ticket 17975.
12034 Written by Michael Sonntag.
12036 o Minor bugfix (logging):
12037 - Don't recommend the use of Tor2web in non-anonymous mode.
12038 Recommending Tor2web is a bad idea because the client loses all
12039 anonymity. Tor2web should only be used in specific cases by users
12040 who *know* and understand the issues. Fixes bug 21294; bugfix
12043 o Minor bugfixes (client):
12044 - Always recover from failures in extend_info_from_node(), in an
12045 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
12046 bugfix on 0.2.3.1-alpha.
12048 o Minor bugfixes (client, entry guards):
12049 - Fix a bug warning (with backtrace) when we fail a channel that
12050 circuits to fallback directories on it. Fixes bug 21128; bugfix
12052 - Fix a spurious bug warning (with backtrace) when removing an
12053 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
12054 - Fix a bug of the new guard algorithm where tor could stall for up
12055 to 10 minutes before retrying a guard after a long period of no
12056 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
12057 - Do not try to build circuits until we have descriptors for our
12058 primary entry guards. Related to fix for bug 21242.
12060 o Minor bugfixes (configure, autoconf):
12061 - Rename the configure option --enable-expensive-hardening to
12062 --enable-fragile-hardening. Expensive hardening makes the tor
12063 daemon abort when some kinds of issues are detected. Thus, it
12064 makes tor more at risk of remote crashes but safer against RCE or
12065 heartbleed bug category. We now try to explain this issue in a
12066 message from the configure script. Fixes bug 21290; bugfix
12069 o Minor bugfixes (controller):
12070 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
12071 20824; bugfix on 0.3.0.1-alpha.
12073 o Minor bugfixes (hidden service):
12074 - Clean up the code for expiring intro points with no associated
12075 circuits. It was causing, rarely, a service with some expiring
12076 introduction points to not open enough additional introduction
12077 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
12078 - Stop setting the torrc option HiddenServiceStatistics to "0" just
12079 because we're not a bridge or relay. Instead, we preserve whatever
12080 value the user set (or didn't set). Fixes bug 21150; bugfix
12082 - Resolve two possible underflows which could lead to creating and
12083 closing a lot of introduction point circuits in a non-stop loop.
12084 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
12086 o Minor bugfixes (portability):
12087 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
12088 It is supported by OpenBSD itself, and also by most OpenBSD
12089 variants (such as Bitrig). Fixes bug 20980; bugfix
12091 - When mapping a file of length greater than SIZE_MAX, do not
12092 silently truncate its contents. This issue could occur on 32 bit
12093 systems with large file support and files which are larger than 4
12094 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
12096 o Minor bugfixes (tor-resolve):
12097 - The tor-resolve command line tool now rejects hostnames over 255
12098 characters in length. Previously, it would silently truncate them,
12099 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
12100 Patch by "junglefowl".
12102 o Minor bugfixes (Windows services):
12103 - Be sure to initialize the monotonic time subsystem before using
12104 it, even when running as an NT service. Fixes bug 21356; bugfix
12108 Changes in version 0.3.0.2-alpha - 2017-01-23
12109 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
12110 cause relays and clients to crash, even if they were not built with
12111 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
12112 versions, and also affects 0.3.0.1-alpha: all relays running an affected
12113 version should upgrade.
12115 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
12116 time-to-live values, makes directory authorities enforce the 1-to-1
12117 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
12118 client-side onion service reachability bug, does better at selecting
12119 the set of fallback directories, and more.
12121 o Major bugfixes (security, also in 0.2.9.9):
12122 - Downgrade the "-ftrapv" option from "always on" to "only on when
12123 --enable-expensive-hardening is provided." This hardening option, like
12124 others, can turn survivable bugs into crashes--and having it on by
12125 default made a (relatively harmless) integer overflow bug into a
12126 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
12129 o Major features (security):
12130 - Change the algorithm used to decide DNS TTLs on client and server
12131 side, to better resist DNS-based correlation attacks like the
12132 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
12133 Feamster. Now relays only return one of two possible DNS TTL
12134 values, and clients are willing to believe DNS TTL values up to 3
12135 hours long. Closes ticket 19769.
12137 o Major features (directory authority, security):
12138 - The default for AuthDirPinKeys is now 1: directory authorities
12139 will reject relays where the RSA identity key matches a previously
12140 seen value, but the Ed25519 key has changed. Closes ticket 18319.
12142 o Major bugfixes (client, guard, crash):
12143 - In circuit_get_global_origin_list(), return the actual list of
12144 origin circuits. The previous version of this code returned the
12145 list of all the circuits, and could have caused strange bugs,
12146 including possible crashes. Fixes bug 21118; bugfix
12149 o Major bugfixes (client, onion service, also in 0.2.9.9):
12150 - Fix a client-side onion service reachability bug, where multiple
12151 socks requests to an onion service (or a single slow request)
12152 could cause us to mistakenly mark some of the service's
12153 introduction points as failed, and we cache that failure so
12154 eventually we run out and can't reach the service. Also resolves a
12155 mysterious "Remote server sent bogus reason code 65021" log
12156 warning. The bug was introduced in ticket 17218, where we tried to
12157 remember the circuit end reason as a uint16_t, which mangled
12158 negative values. Partially fixes bug 21056 and fixes bug 20307;
12159 bugfix on 0.2.8.1-alpha.
12161 o Major bugfixes (DNS):
12162 - Fix a bug that prevented exit nodes from caching DNS records for
12163 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
12165 o Minor features (controller):
12166 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
12167 shared-random values to the controller. Closes ticket 19925.
12169 o Minor features (entry guards):
12170 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
12171 break regression tests.
12172 - Require UseEntryGuards when UseBridges is set, in order to make
12173 sure bridges aren't bypassed. Resolves ticket 20502.
12175 o Minor features (fallback directories):
12176 - Select 200 fallback directories for each release. Closes
12178 - Allow 3 fallback relays per operator, which is safe now that we
12179 are choosing 200 fallback relays. Closes ticket 20912.
12180 - Exclude relays affected by bug 20499 from the fallback list.
12181 Exclude relays from the fallback list if they are running versions
12182 known to be affected by bug 20499, or if in our tests they deliver
12183 a stale consensus (i.e. one that expired more than 24 hours ago).
12184 Closes ticket 20539.
12185 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
12187 - Require fallback directories to have the same address and port for
12188 7 days (now that we have enough relays with this stability).
12189 Relays whose OnionOO stability timer is reset on restart by bug
12190 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
12191 this issue. Closes ticket 20880; maintains short-term fix
12193 - Require fallbacks to have flags for 90% of the time (weighted
12194 decaying average), rather than 95%. This allows at least 73% of
12195 clients to bootstrap in the first 5 seconds without contacting an
12196 authority. Part of ticket 18828.
12197 - Annotate updateFallbackDirs.py with the bandwidth and consensus
12198 weight for each candidate fallback. Closes ticket 20878.
12199 - Make it easier to change the output sort order of fallbacks.
12200 Closes ticket 20822.
12201 - Display the relay fingerprint when downloading consensuses from
12202 fallbacks. Closes ticket 20908.
12204 o Minor features (geoip, also in 0.2.9.9):
12205 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
12208 o Minor features (next-gen onion service directories):
12209 - Remove the "EnableOnionServicesV3" consensus parameter that we
12210 introduced in 0.3.0.1-alpha: relays are now always willing to act
12211 as v3 onion service directories. Resolves ticket 19899.
12213 o Minor features (linting):
12214 - Enhance the changes file linter to warn on Tor versions that are
12215 prefixed with "tor-". Closes ticket 21096.
12217 o Minor features (logging):
12218 - In several places, describe unset ed25519 keys as "<unset>",
12219 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
12221 o Minor bugfix (control protocol):
12222 - The reply to a "GETINFO config/names" request via the control
12223 protocol now spells the type "Dependent" correctly. This is a
12224 breaking change in the control protocol. (The field seems to be
12225 ignored by the most common known controllers.) Fixes bug 18146;
12226 bugfix on 0.1.1.4-alpha.
12228 o Minor bugfixes (bug resilience):
12229 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
12230 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
12231 Hans Jerry Illikainen.
12233 o Minor bugfixes (build):
12234 - Replace obsolete Autoconf macros with their modern equivalent and
12235 prevent similar issues in the future. Fixes bug 20990; bugfix
12238 o Minor bugfixes (client, guards):
12239 - Fix bug where Tor would think that there are circuits waiting for
12240 better guards even though those circuits have been freed. Fixes
12241 bug 21142; bugfix on 0.3.0.1-alpha.
12243 o Minor bugfixes (config):
12244 - Don't assert on startup when trying to get the options list and
12245 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
12246 options so of course they aren't ready yet. Fixes bug 21062;
12247 bugfix on 0.2.9.3-alpha.
12249 o Minor bugfixes (controller):
12250 - Make the GETINFO interface for inquiring about entry guards
12251 support the new guards backend. Fixes bug 20823; bugfix
12254 o Minor bugfixes (dead code):
12255 - Remove a redundant check for PidFile changes at runtime in
12256 options_transition_allowed(): this check is already performed
12257 regardless of whether the sandbox is active. Fixes bug 21123;
12258 bugfix on 0.2.5.4-alpha.
12260 o Minor bugfixes (documentation):
12261 - Update the tor manual page to document every option that can not
12262 be changed while tor is running. Fixes bug 21122.
12264 o Minor bugfixes (fallback directories):
12265 - Stop failing when a relay has no uptime data in
12266 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
12267 - Avoid checking fallback candidates' DirPorts if they are down in
12268 OnionOO. When a relay operator has multiple relays, this
12269 prioritizes relays that are up over relays that are down. Fixes
12270 bug 20926; bugfix on 0.2.8.3-alpha.
12271 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
12272 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
12274 o Minor bugfixes (guards, bootstrapping):
12275 - When connecting to a directory guard during bootstrap, do not mark
12276 the guard as successful until we receive a good-looking directory
12277 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
12279 o Minor bugfixes (onion services):
12280 - Fix the config reload pruning of old vs new services so it
12281 actually works when both ephemeral and non-ephemeral services are
12282 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
12283 - Allow the number of introduction points to be as low as 0, rather
12284 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
12286 o Minor bugfixes (IPv6):
12287 - Make IPv6-using clients try harder to find an IPv6 directory
12288 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
12289 - When IPv6 addresses have not been downloaded yet (microdesc
12290 consensus documents don't list relay IPv6 addresses), use hard-
12291 coded addresses for authorities, fallbacks, and configured
12292 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
12293 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
12295 o Minor bugfixes (memory leaks):
12296 - Fix a memory leak when configuring hidden services. Fixes bug
12297 20987; bugfix on 0.3.0.1-alpha.
12299 o Minor bugfixes (portability, also in 0.2.9.9):
12300 - Avoid crashing when Tor is built using headers that contain
12301 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
12302 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
12304 - Fix Libevent detection on platforms without Libevent 1 headers
12305 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
12307 o Minor bugfixes (relay):
12308 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
12309 initializing the keys would reset the DataDirectory to 0700
12310 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
12311 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
12313 o Minor bugfixes (testing):
12314 - Remove undefined behavior from the backtrace generator by removing
12315 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
12317 o Minor bugfixes (unit tests):
12318 - Allow the unit tests to pass even when DNS lookups of bogus
12319 addresses do not fail as expected. Fixes bug 20862 and 20863;
12320 bugfix on unit tests introduced in 0.2.8.1-alpha
12321 through 0.2.9.4-alpha.
12323 o Code simplification and refactoring:
12324 - Refactor code to manipulate global_origin_circuit_list into
12325 separate functions. Closes ticket 20921.
12327 o Documentation (formatting):
12328 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
12329 blocks were incorrectly appearing. Closes ticket 20885.
12331 o Documentation (man page):
12332 - Clarify many options in tor.1 and add some min/max values for
12333 HiddenService options. Closes ticket 21058.
12336 Changes in version 0.2.9.9 - 2017-01-23
12337 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
12338 cause relays and clients to crash, even if they were not built with
12339 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
12340 versions, and also affects 0.3.0.1-alpha: all relays running an affected
12341 version should upgrade.
12343 This release also resolves a client-side onion service reachability
12344 bug, and resolves a pair of small portability issues.
12346 o Major bugfixes (security):
12347 - Downgrade the "-ftrapv" option from "always on" to "only on when
12348 --enable-expensive-hardening is provided." This hardening option,
12349 like others, can turn survivable bugs into crashes -- and having
12350 it on by default made a (relatively harmless) integer overflow bug
12351 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
12352 bugfix on 0.2.9.1-alpha.
12354 o Major bugfixes (client, onion service):
12355 - Fix a client-side onion service reachability bug, where multiple
12356 socks requests to an onion service (or a single slow request)
12357 could cause us to mistakenly mark some of the service's
12358 introduction points as failed, and we cache that failure so
12359 eventually we run out and can't reach the service. Also resolves a
12360 mysterious "Remote server sent bogus reason code 65021" log
12361 warning. The bug was introduced in ticket 17218, where we tried to
12362 remember the circuit end reason as a uint16_t, which mangled
12363 negative values. Partially fixes bug 21056 and fixes bug 20307;
12364 bugfix on 0.2.8.1-alpha.
12366 o Minor features (geoip):
12367 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
12370 o Minor bugfixes (portability):
12371 - Avoid crashing when Tor is built using headers that contain
12372 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
12373 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
12375 - Fix Libevent detection on platforms without Libevent 1 headers
12376 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
12379 Changes in version 0.3.0.1-alpha - 2016-12-19
12380 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
12381 series. It strengthens Tor's link and circuit handshakes by
12382 identifying relays by their Ed25519 keys, improves the algorithm that
12383 clients use to choose and maintain their list of guards, and includes
12384 additional backend support for the next-generation hidden service
12385 design. It also contains numerous other small features and
12386 improvements to security, correctness, and performance.
12388 Below are the changes since 0.2.9.8.
12390 o Major features (guard selection algorithm):
12391 - Tor's guard selection algorithm has been redesigned from the
12392 ground up, to better support unreliable networks and restrictive
12393 sets of entry nodes, and to better resist guard-capture attacks by
12394 hostile local networks. Implements proposal 271; closes
12397 o Major features (next-generation hidden services):
12398 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
12399 prop224 aka "Next Generation Hidden Services". Service and clients
12400 don't use this functionality yet. Closes ticket 19043. Based on
12401 initial code by Alec Heifetz.
12402 - Relays now support the HSDir version 3 protocol, so that they can
12403 can store and serve v3 descriptors. This is part of the next-
12404 generation onion service work detailed in proposal 224. Closes
12407 o Major features (protocol, ed25519 identity keys):
12408 - Relays now use Ed25519 to prove their Ed25519 identities and to
12409 one another, and to clients. This algorithm is faster and more
12410 secure than the RSA-based handshake we've been doing until now.
12411 Implements the second big part of proposal 220; Closes
12413 - Clients now support including Ed25519 identity keys in the EXTEND2
12414 cells they generate. By default, this is controlled by a consensus
12415 parameter, currently disabled. You can turn this feature on for
12416 testing by setting ExtendByEd25519ID in your configuration. This
12417 might make your traffic appear different than the traffic
12418 generated by other users, however. Implements part of ticket
12419 15056; part of proposal 220.
12420 - Relays now understand requests to extend to other relays by their
12421 Ed25519 identity keys. When an Ed25519 identity key is included in
12422 an EXTEND2 cell, the relay will only extend the circuit if the
12423 other relay can prove ownership of that identity. Implements part
12424 of ticket 15056; part of proposal 220.
12426 o Major bugfixes (scheduler):
12427 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
12428 caused the channel scheduler to behave more or less randomly,
12429 rather than preferring channels with higher-priority circuits.
12430 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
12432 o Minor features (controller):
12433 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
12434 rather than "unrecognized." Closes ticket 20389; patch from
12437 o Minor features (diagnostic, directory client):
12438 - Warn when we find an unexpected inconsistency in directory
12439 download status objects. Prevents some negative consequences of
12442 o Minor features (directory authority):
12443 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
12444 default) to control whether authorities should try to probe relays
12445 by their Ed25519 link keys. This option will go away in a few
12446 releases--unless we encounter major trouble in our ed25519 link
12447 protocol rollout, in which case it will serve as a safety option.
12449 o Minor features (directory cache):
12450 - Relays and bridges will now refuse to serve the consensus they
12451 have if they know it is too old for a client to use. Closes
12454 o Minor features (ed25519 link handshake):
12455 - Advertise support for the ed25519 link handshake using the
12456 subprotocol-versions mechanism, so that clients can tell which
12457 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
12459 o Minor features (fingerprinting resistance, authentication):
12460 - Extend the length of RSA keys used for TLS link authentication to
12461 2048 bits. (These weren't used for forward secrecy; for forward
12462 secrecy, we used P256.) Closes ticket 13752.
12464 o Minor features (infrastructure):
12465 - Implement smartlist_add_strdup() function. Replaces the use of
12466 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
12468 o Minor bugfixes (client):
12469 - When clients that use bridges start up with a cached consensus on
12470 disk, they were ignoring it and downloading a new one. Now they
12471 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
12473 o Minor bugfixes (configuration):
12474 - Accept non-space whitespace characters after the severity level in
12475 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
12476 - Support "TByte" and "TBytes" units in options given in bytes.
12477 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
12478 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
12480 o Minor bugfixes (consensus weight):
12481 - Add new consensus method that initializes bw weights to 1 instead
12482 of 0. This prevents a zero weight from making it all the way to
12483 the end (happens in small testing networks) and causing an error.
12484 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
12486 o Minor bugfixes (descriptors):
12487 - Correctly recognise downloaded full descriptors as valid, even
12488 when using microdescriptors as circuits. This affects clients with
12489 FetchUselessDescriptors set, and may affect directory authorities.
12490 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
12492 o Minor bugfixes (directory system):
12493 - Download all consensus flavors, descriptors, and authority
12494 certificates when FetchUselessDescriptors is set, regardless of
12495 whether tor is a directory cache or not. Fixes bug 20667; bugfix
12496 on all recent tor versions.
12497 - Bridges and relays now use microdescriptors (like clients do)
12498 rather than old-style router descriptors. Now bridges will blend
12499 in with clients in terms of the circuits they build. Fixes bug
12500 6769; bugfix on 0.2.3.2-alpha.
12502 o Minor bugfixes (ed25519 certificates):
12503 - Correctly interpret ed25519 certificates that would expire some
12504 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
12506 o Minor bugfixes (hidden services):
12507 - Stop ignoring misconfigured hidden services. Instead, refuse to
12508 start tor until the misconfigurations have been corrected. Fixes
12509 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
12512 o Minor bugfixes (memory leak at exit):
12513 - Fix a small harmless memory leak at exit of the previously unused
12514 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
12517 o Minor bugfixes (util):
12518 - When finishing writing a file to disk, if we were about to replace
12519 the file with the temporary file created before and we fail to
12520 replace it, remove the temporary file so it doesn't stay on disk.
12521 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
12523 o Minor bugfixes (Windows):
12524 - Check for getpagesize before using it to mmap files. This fixes
12525 compilation in some MinGW environments. Fixes bug 20530; bugfix on
12526 0.1.2.1-alpha. Reported by "ice".
12528 o Code simplification and refactoring:
12529 - Abolish all global guard context in entrynodes.c; replace with new
12530 guard_selection_t structure as preparation for proposal 271.
12531 Closes ticket 19858.
12532 - Introduce rend_service_is_ephemeral() that tells if given onion
12533 service is ephemeral. Replace unclear NULL-checkings for service
12534 directory with this function. Closes ticket 20526.
12535 - Extract magic numbers in circuituse.c into defined variables.
12536 - Refactor circuit_is_available_for_use to remove unnecessary check.
12537 - Refactor circuit_predict_and_launch_new for readability and
12538 testability. Closes ticket 18873.
12539 - Refactor large if statement in purpose_needs_anonymity to use
12540 switch statement instead. Closes part of ticket 20077.
12541 - Refactor the hashing API to return negative values for errors, as
12542 is done as throughout the codebase. Closes ticket 20717.
12543 - Remove data structures that were used to index or_connection
12544 objects by their RSA identity digests. These structures are fully
12545 redundant with the similar structures used in the
12546 channel abstraction.
12547 - Remove duplicate code in the channel_write_*cell() functions.
12548 Closes ticket 13827; patch from Pingl.
12549 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
12550 use only purpose_needs_anonymity. Closes part of ticket 20077.
12551 - The code to generate and parse EXTEND and EXTEND2 cells has been
12552 replaced with code automatically generated by the
12556 - Include the "TBits" unit in Tor's man page. Fixes part of bug
12557 20622; bugfix on 0.2.5.1-alpha.
12558 - Change '1' to 'weight_scale' in consensus bw weights calculation
12559 comments, as that is reality. Closes ticket 20273. Patch
12561 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
12562 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
12564 - Stop the man page from incorrectly stating that HiddenServiceDir
12565 must already exist. Fixes 20486.
12566 - Clarify that when ClientRejectInternalAddresses is enabled (which
12567 is the default), multicast DNS hostnames for machines on the local
12568 network (of the form *.local) are also rejected. Closes
12571 o Removed features:
12572 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
12573 limit for relays running on a single IP applies to authority IP
12574 addresses as well as to non-authority IP addresses. Closes
12576 - The UseDirectoryGuards torrc option no longer exists: all users
12577 that use entry guards will also use directory guards. Related to
12578 proposal 271; implements part of ticket 20831.
12581 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
12582 from "overcaffeinated".
12583 - Perform the coding style checks when running the tests and fail
12584 when coding style violations are found. Closes ticket 5500.
12585 - Add tests for networkstatus_compute_bw_weights_v10.
12586 - Add unit tests circuit_predict_and_launch_new.
12587 - Extract dummy_origin_circuit_new so it can be used by other
12591 Changes in version 0.2.8.12 - 2016-12-19
12592 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
12593 below) where Tor clients could crash when attempting to visit a
12594 hostile hidden service. Clients are recommended to upgrade as packages
12595 become available for their systems.
12597 It also includes an updated list of fallback directories, backported
12600 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
12601 backported to 0.2.8 in the future.
12603 o Major bugfixes (parsing, security, backported from 0.2.9.8):
12604 - Fix a bug in parsing that could cause clients to read a single
12605 byte past the end of an allocated region. This bug could be used
12606 to cause hardened clients (built with --enable-expensive-hardening)
12607 to crash if they tried to visit a hostile hidden service. Non-
12608 hardened clients are only affected depending on the details of
12609 their platform's memory allocator. Fixes bug 21018; bugfix on
12610 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12611 2016-12-002 and as CVE-2016-1254.
12613 o Minor features (fallback directory list, backported from 0.2.9.8):
12614 - Replace the 81 remaining fallbacks of the 100 originally
12615 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
12616 fallbacks (123 new, 54 existing, 27 removed) generated in December
12617 2016. Resolves ticket 20170.
12619 o Minor features (geoip, backported from 0.2.9.7-rc):
12620 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
12624 Changes in version 0.2.9.8 - 2016-12-19
12625 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
12627 The Tor 0.2.9 series makes mandatory a number of security features
12628 that were formerly optional. It includes support for a new shared-
12629 randomness protocol that will form the basis for next generation
12630 hidden services, includes a single-hop hidden service mode for
12631 optimizing .onion services that don't actually want to be hidden,
12632 tries harder not to overload the directory authorities with excessive
12633 downloads, and supports a better protocol versioning scheme for
12634 improved compatibility with other implementations of the Tor protocol.
12636 And of course, there are numerous other bugfixes and improvements.
12638 This release also includes a fix for a medium-severity issue (bug
12639 21018 below) where Tor clients could crash when attempting to visit a
12640 hostile hidden service. Clients are recommended to upgrade as packages
12641 become available for their systems.
12643 Below are the changes since 0.2.9.7-rc. For a list of all changes
12644 since 0.2.8, see the ReleaseNotes file.
12646 o Major bugfixes (parsing, security):
12647 - Fix a bug in parsing that could cause clients to read a single
12648 byte past the end of an allocated region. This bug could be used
12649 to cause hardened clients (built with --enable-expensive-hardening)
12650 to crash if they tried to visit a hostile hidden service. Non-
12651 hardened clients are only affected depending on the details of
12652 their platform's memory allocator. Fixes bug 21018; bugfix on
12653 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12654 2016-12-002 and as CVE-2016-1254.
12656 o Minor features (fallback directory list):
12657 - Replace the 81 remaining fallbacks of the 100 originally
12658 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
12659 fallbacks (123 new, 54 existing, 27 removed) generated in December
12660 2016. Resolves ticket 20170.
12663 Changes in version 0.2.9.7-rc - 2016-12-12
12664 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
12665 including a few that had prevented tests from passing on
12668 o Minor features (geoip):
12669 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
12672 o Minor bugfix (build):
12673 - The current Git revision when building from a local repository is
12674 now detected correctly when using git worktrees. Fixes bug 20492;
12675 bugfix on 0.2.3.9-alpha.
12677 o Minor bugfixes (directory authority):
12678 - When computing old Tor protocol line version in protover, we were
12679 looking at 0.2.7.5 twice instead of a specific case for
12680 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
12682 o Minor bugfixes (download scheduling):
12683 - Resolve a "bug" warning when considering a download schedule whose
12684 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
12686 o Minor bugfixes (logging):
12687 - Downgrade a harmless log message about the
12688 pending_entry_connections list from "warn" to "info". Mitigates
12691 o Minor bugfixes (memory leak):
12692 - Fix a small memory leak when receiving AF_UNIX connections on a
12693 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
12694 - When moving a signed descriptor object from a source to an
12695 existing destination, free the allocated memory inside that
12696 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
12698 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
12699 - Fix a memory leak and use-after-free error when removing entries
12700 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
12701 0.2.5.5-alpha. Patch from "cypherpunks".
12703 o Minor bugfixes (portability):
12704 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
12705 Fixes bug 20935; bugfix on 0.2.9.6-rc.
12707 o Minor bugfixes (unit tests):
12708 - Stop expecting NetBSD unit tests to report success for ipfw. Part
12709 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
12710 - Fix tolerances in unit tests for monotonic time comparisons
12711 between nanoseconds and microseconds. Previously, we accepted a 10
12712 us difference only, which is not realistic on every platform's
12713 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
12714 - Remove a double-free in the single onion service unit test. Stop
12715 ignoring a return value. Make future changes less error-prone.
12716 Fixes bug 20864; bugfix on 0.2.9.6-rc.
12719 Changes in version 0.2.8.11 - 2016-12-08
12720 Tor 0.2.8.11 backports fixes for additional portability issues that
12721 could prevent Tor from building correctly on OSX Sierra, or with
12722 OpenSSL 1.1. Affected users should upgrade; others can safely stay
12725 o Minor bugfixes (portability):
12726 - Avoid compilation errors when building on OSX Sierra. Sierra began
12727 to support the getentropy() and clock_gettime() APIs, but created
12728 a few problems in doing so. Tor 0.2.9 has a more thorough set of
12729 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
12730 monotonic time interfaces. Fixes bug 20865. Bugfix
12733 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
12734 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
12735 architectures. Closes ticket 20588.
12738 Changes in version 0.2.8.10 - 2016-12-02
12739 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
12740 unusable after they left standby mode. It also backports fixes for
12741 a few portability issues and a small but problematic memory leak.
12743 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
12744 - When Tor leaves standby because of a new application request, open
12745 circuits as needed to serve that request. Previously, we would
12746 potentially wait a very long time. Fixes part of bug 19969; bugfix
12749 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
12750 - Clients now respond to new application stream requests immediately
12751 when they arrive, rather than waiting up to one second before
12752 starting to handle them. Fixes part of bug 19969; bugfix
12755 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
12756 - Work around a bug in the OSX 10.12 SDK that would prevent us from
12757 successfully targeting earlier versions of OSX. Resolves
12760 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
12761 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
12762 20551; bugfix on 0.2.1.1-alpha.
12764 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
12765 - Work around a memory leak in OpenSSL 1.1 when encoding public
12766 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
12768 o Minor features (geoip):
12769 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
12772 Changes in version 0.2.9.6-rc - 2016-12-02
12773 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
12774 version. We hope that it will be ready to become stable soon, and we
12775 encourage everyone to test this release. If no showstopper bugs are
12776 found here, the next 0.2.9 release will be stable.
12778 o Major bugfixes (relay, resolver, logging):
12779 - For relays that don't know their own address, avoid attempting a
12780 local hostname resolve for each descriptor we download. This
12781 will cut down on the number of "Success: chose address 'x.x.x.x'"
12782 log lines, and also avoid confusing clock jumps if the resolver
12783 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
12785 o Minor bugfixes (client, fascistfirewall):
12786 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
12787 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
12789 o Minor bugfixes (hidden services):
12790 - Stop ignoring the anonymity status of saved keys for hidden
12791 services and single onion services when first starting tor.
12792 Instead, refuse to start tor if any hidden service key has been
12793 used in a different hidden service anonymity mode. Fixes bug
12794 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
12796 o Minor bugfixes (portability):
12797 - Work around a bug in the OSX 10.12 SDK that would prevent us from
12798 successfully targeting earlier versions of OSX. Resolves
12800 - Run correctly when built on Windows build environments that
12801 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
12803 o Minor bugfixes (single onion services, Tor2web):
12804 - Stop complaining about long-term one-hop circuits deliberately
12805 created by single onion services and Tor2web. These log messages
12806 are intended to diagnose issue 8387, which relates to circuits
12807 hanging around forever for no reason. Fixes bug 20613; bugfix on
12808 0.2.9.1-alpha. Reported by "pastly".
12810 o Minor bugfixes (unit tests):
12811 - Stop spurious failures in the local interface address discovery
12812 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
12816 - Correct the minimum bandwidth value in torrc.sample, and queue a
12817 corresponding change for torrc.minimal. Closes ticket 20085.
12820 Changes in version 0.2.9.5-alpha - 2016-11-08
12821 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
12822 version. We believe one or two probably remain, and we encourage
12823 everyone to test this release.
12825 o Major bugfixes (client performance):
12826 - Clients now respond to new application stream requests immediately
12827 when they arrive, rather than waiting up to one second before
12828 starting to handle them. Fixes part of bug 19969; bugfix
12831 o Major bugfixes (client reliability):
12832 - When Tor leaves standby because of a new application request, open
12833 circuits as needed to serve that request. Previously, we would
12834 potentially wait a very long time. Fixes part of bug 19969; bugfix
12837 o Major bugfixes (download scheduling):
12838 - When using an exponential backoff schedule, do not give up on
12839 downloading just because we have failed a bunch of times. Since
12840 each delay is longer than the last, retrying indefinitely won't
12841 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
12842 - If a consensus expires while we are waiting for certificates to
12843 download, stop waiting for certificates.
12844 - If we stop waiting for certificates less than a minute after we
12845 started downloading them, do not consider the certificate download
12846 failure a separate failure. Fixes bug 20533; bugfix
12848 - Remove the maximum delay on exponential-backoff scheduling. Since
12849 we now allow an infinite number of failures (see ticket 20536), we
12850 must now allow the time to grow longer on each failure. Fixes part
12851 of bug 20534; bugfix on 0.2.9.1-alpha.
12852 - Make our initial download delays closer to those from 0.2.8. Fixes
12853 another part of bug 20534; bugfix on 0.2.9.1-alpha.
12854 - When determining when to download a directory object, handle times
12855 after 2038 if the operating system supports them. (Someday this
12856 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
12857 - When using exponential backoff in test networks, use a lower
12858 exponent, so the delays do not vary as much. This helps test
12859 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
12861 o Minor features (geoip):
12862 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
12865 o Minor bugfixes (client directory scheduling):
12866 - Treat "relay too busy to answer request" as a failed request and a
12867 reason to back off on our retry frequency. This is safe now that
12868 exponential backoffs retry indefinitely, and avoids a bug where we
12869 would reset our download schedule erroneously. Fixes bug 20593;
12870 bugfix on 0.2.9.1-alpha.
12872 o Minor bugfixes (client, logging):
12873 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
12874 assume all nodes support EXTEND2. Use ntor whenever a key is
12875 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
12876 - On DNSPort, stop logging a BUG warning on a failed hostname
12877 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
12879 o Minor bugfixes (hidden services):
12880 - When configuring hidden services, check every hidden service
12881 directory's permissions. Previously, we only checked the last
12882 hidden service. Fixes bug 20529; bugfix the work to fix 13942
12885 o Minor bugfixes (portability):
12886 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
12887 architectures. Closes ticket 20588.
12888 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
12889 removed the ECDH ciphers which caused the tests to fail on
12890 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
12891 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
12892 20551; bugfix on 0.2.1.1-alpha.
12894 o Minor bugfixes (relay bootstrap):
12895 - Ensure relays don't make multiple connections during bootstrap.
12896 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
12898 o Minor bugfixes (relay):
12899 - Work around a memory leak in OpenSSL 1.1 when encoding public
12900 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
12901 - Avoid a small memory leak when informing worker threads about
12902 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
12903 - Do not try to parallelize workers more than 16x without the user
12904 explicitly configuring us to do so, even if we do detect more than
12905 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
12907 o Minor bugfixes (single onion services):
12908 - Start correctly when creating a single onion service in a
12909 directory that did not previously exist. Fixes bug 20484; bugfix
12912 o Minor bugfixes (testing):
12913 - Avoid a unit test failure on systems with over 16 detectable CPU
12914 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
12917 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
12918 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
12919 - Module-level documentation for several more modules. Closes
12920 tickets 19287 and 19290.
12923 Changes in version 0.2.8.9 - 2016-10-17
12924 Tor 0.2.8.9 backports a fix for a security hole in previous versions
12925 of Tor that would allow a remote attacker to crash a Tor client,
12926 hidden service, relay, or authority. All Tor users should upgrade to
12927 this version, or to 0.2.9.4-alpha. Patches will be released for older
12930 o Major features (security fixes, also in 0.2.9.4-alpha):
12931 - Prevent a class of security bugs caused by treating the contents
12932 of a buffer chunk as if they were a NUL-terminated string. At
12933 least one such bug seems to be present in all currently used
12934 versions of Tor, and would allow an attacker to remotely crash
12935 most Tor instances, especially those compiled with extra compiler
12936 hardening. With this defense in place, such bugs can't crash Tor,
12937 though we should still fix them as they occur. Closes ticket
12938 20384 (TROVE-2016-10-001).
12940 o Minor features (geoip):
12941 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
12945 Changes in version 0.2.9.4-alpha - 2016-10-17
12946 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
12947 that would allow a remote attacker to crash a Tor client, hidden
12948 service, relay, or authority. All Tor users should upgrade to this
12949 version, or to 0.2.8.9. Patches will be released for older versions
12952 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
12953 previous versions of Tor, including the implementation of a feature to
12954 future- proof the Tor ecosystem against protocol changes, some bug
12955 fixes necessary for Tor Browser to use unix domain sockets correctly,
12956 and several portability improvements. We anticipate that this will be
12957 the last alpha in the Tor 0.2.9 series, and that the next release will
12958 be a release candidate.
12960 o Major features (security fixes):
12961 - Prevent a class of security bugs caused by treating the contents
12962 of a buffer chunk as if they were a NUL-terminated string. At
12963 least one such bug seems to be present in all currently used
12964 versions of Tor, and would allow an attacker to remotely crash
12965 most Tor instances, especially those compiled with extra compiler
12966 hardening. With this defense in place, such bugs can't crash Tor,
12967 though we should still fix them as they occur. Closes ticket
12968 20384 (TROVE-2016-10-001).
12970 o Major features (subprotocol versions):
12971 - Tor directory authorities now vote on a set of recommended
12972 subprotocol versions, and on a set of required subprotocol
12973 versions. Clients and relays that lack support for a _required_
12974 subprotocol version will not start; those that lack support for a
12975 _recommended_ subprotocol version will warn the user to upgrade.
12976 Closes ticket 19958; implements part of proposal 264.
12977 - Tor now uses "subprotocol versions" to indicate compatibility.
12978 Previously, versions of Tor looked at the declared Tor version of
12979 a relay to tell whether they could use a given feature. Now, they
12980 should be able to rely on its declared subprotocol versions. This
12981 change allows compatible implementations of the Tor protocol(s) to
12982 exist without pretending to be 100% bug-compatible with particular
12983 releases of Tor itself. Closes ticket 19958; implements part of
12986 o Minor feature (fallback directories):
12987 - Remove broken fallbacks from the hard-coded fallback directory
12988 list. Closes ticket 20190; patch by teor.
12990 o Minor features (client, directory):
12991 - Since authorities now omit all routers that lack the Running and
12992 Valid flags, we assume that any relay listed in the consensus must
12993 have those flags. Closes ticket 20001; implements part of
12996 o Minor features (compilation, portability):
12997 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
13000 o Minor features (development tools, etags):
13001 - Teach the "make tags" Makefile target how to correctly find
13002 "MOCK_IMPL" function definitions. Patch from nherring; closes
13005 o Minor features (geoip):
13006 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
13009 o Minor features (unix domain sockets):
13010 - When configuring a unix domain socket for a SocksPort,
13011 ControlPort, or Hidden service, you can now wrap the address in
13012 quotes, using C-style escapes inside the quotes. This allows unix
13013 domain socket paths to contain spaces.
13015 o Minor features (virtual addresses):
13016 - Increase the maximum number of bits for the IPv6 virtual network
13017 prefix from 16 to 104. In this way, the condition for address
13018 allocation is less restrictive. Closes ticket 20151; feature
13021 o Minor bugfixes (address discovery):
13022 - Stop reordering IP addresses returned by the OS. This makes it
13023 more likely that Tor will guess the same relay IP address every
13024 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
13025 Reported by René Mayrhofer, patch by "cypherpunks".
13027 o Minor bugfixes (client, unix domain sockets):
13028 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
13029 the client address is meaningless. Fixes bug 20261; bugfix
13032 o Minor bugfixes (compilation, OpenBSD):
13033 - Detect Libevent2 functions correctly on systems that provide
13034 libevent2, but where libevent1 is linked with -levent. Fixes bug
13035 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
13037 o Minor bugfixes (configuration):
13038 - When parsing quoted configuration values from the torrc file,
13039 handle windows line endings correctly. Fixes bug 19167; bugfix on
13040 0.2.0.16-alpha. Patch from "Pingl".
13042 o Minor bugfixes (getpass):
13043 - Defensively fix a non-triggerable heap corruption at do_getpass()
13044 to protect ourselves from mistakes in the future. Fixes bug
13045 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
13048 o Minor bugfixes (hidden service):
13049 - Allow hidden services to run on IPv6 addresses even when the
13050 IPv6Exit option is not set. Fixes bug 18357; bugfix
13054 - Add module-level internal documentation for 36 C files that
13055 previously didn't have a high-level overview. Closes ticket #20385.
13057 o Required libraries:
13058 - When building with OpenSSL, Tor now requires version 1.0.1 or
13059 later. OpenSSL 1.0.0 and earlier are no longer supported by the
13060 OpenSSL team, and should not be used. Closes ticket 20303.
13063 Changes in version 0.2.9.3-alpha - 2016-09-23
13064 Tor 0.2.9.3-alpha adds improved support for entities that want to make
13065 high-performance services available through the Tor .onion mechanism
13066 without themselves receiving anonymity as they host those services. It
13067 also tries harder to ensure that all steps on a circuit are using the
13068 strongest crypto possible, strengthens some TLS properties, and
13069 resolves several bugs -- including a pair of crash bugs from the 0.2.8
13070 series. Anybody running an earlier version of 0.2.9.x should upgrade.
13072 o Major bugfixes (crash, also in 0.2.8.8):
13073 - Fix a complicated crash bug that could affect Tor clients
13074 configured to use bridges when replacing a networkstatus consensus
13075 in which one of their bridges was mentioned. OpenBSD users saw
13076 more crashes here, but all platforms were potentially affected.
13077 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
13079 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
13080 - Fix a timing-dependent assertion failure that could occur when we
13081 tried to flush from a circuit after having freed its cells because
13082 of an out-of-memory condition. Fixes bug 20203; bugfix on
13083 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
13086 o Major features (circuit building, security):
13087 - Authorities, relays and clients now require ntor keys in all
13088 descriptors, for all hops (except for rare hidden service protocol
13089 cases), for all circuits, and for all other roles. Part of
13091 - Tor authorities, relays, and clients only use ntor, except for
13092 rare cases in the hidden service protocol. Part of ticket 19163.
13094 o Major features (single-hop "hidden" services):
13095 - Add experimental HiddenServiceSingleHopMode and
13096 HiddenServiceNonAnonymousMode options. When both are set to 1,
13097 every hidden service on a Tor instance becomes a non-anonymous
13098 Single Onion Service. Single Onions make one-hop (direct)
13099 connections to their introduction and rendezvous points. One-hop
13100 circuits make Single Onion servers easily locatable, but clients
13101 remain location-anonymous. This is compatible with the existing
13102 hidden service implementation, and works on the current tor
13103 network without any changes to older relays or clients. Implements
13104 proposal 260, completes ticket 17178. Patch by teor and asn.
13106 o Major features (resource management):
13107 - Tor can now notice it is about to run out of sockets, and
13108 preemptively close connections of lower priority. (This feature is
13109 off by default for now, since the current prioritizing method is
13110 yet not mature enough. You can enable it by setting
13111 "DisableOOSCheck 0", but watch out: it might close some sockets
13112 you would rather have it keep.) Closes ticket 18640.
13114 o Major bugfixes (circuit building):
13115 - Hidden service client-to-intro-point and service-to-rendezvous-
13116 point circuits use the TAP key supplied by the protocol, to avoid
13117 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
13119 o Major bugfixes (compilation, OpenBSD):
13120 - Fix a Libevent-detection bug in our autoconf script that would
13121 prevent Tor from linking successfully on OpenBSD. Patch from
13122 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
13124 o Major bugfixes (hidden services):
13125 - Clients now require hidden services to include the TAP keys for
13126 their intro points in the hidden service descriptor. This prevents
13127 an inadvertent upgrade to ntor, which a malicious hidden service
13128 could use to distinguish clients by consensus version. Fixes bug
13129 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
13131 o Minor features (security, TLS):
13132 - Servers no longer support clients that without AES ciphersuites.
13133 (3DES is no longer considered an acceptable cipher.) We believe
13134 that no such Tor clients currently exist, since Tor has required
13135 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
13137 o Minor feature (fallback directories):
13138 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
13139 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
13140 2016. Closes ticket 20190; patch by teor.
13142 o Minor features (geoip, also in 0.2.8.8):
13143 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
13146 o Minor feature (port flags):
13147 - Add new flags to the *Port options to finer control over which
13148 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
13149 and the synthetic flag OnionTrafficOnly, which is equivalent to
13150 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
13151 18693; patch by "teor".
13153 o Minor features (directory authority):
13154 - After voting, if the authorities decide that a relay is not
13155 "Valid", they no longer include it in the consensus at all. Closes
13156 ticket 20002; implements part of proposal 272.
13158 o Minor features (testing):
13159 - Disable memory protections on OpenBSD when performing our unit
13160 tests for memwipe(). The test deliberately invokes undefined
13161 behavior, and the OpenBSD protections interfere with this. Patch
13162 from "rubiate". Closes ticket 20066.
13164 o Minor features (testing, ipv6):
13165 - Add the single-onion and single-onion-ipv6 chutney targets to
13166 "make test-network-all". This requires a recent chutney version
13167 with the single onion network flavours (git c72a652 or later).
13168 Closes ticket 20072; patch by teor.
13169 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
13170 tests. Remove bridges+hs, as it's somewhat redundant. This
13171 requires a recent chutney version that supports IPv6 clients,
13172 relays, and authorities. Closes ticket 20069; patch by teor.
13174 o Minor features (Tor2web):
13175 - Make Tor2web clients respect ReachableAddresses. This feature was
13176 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
13177 0.2.8.7. Implements feature 20034. Patch by teor.
13179 o Minor features (unit tests):
13180 - We've done significant work to make the unit tests run faster.
13181 - Our link-handshake unit tests now check that when invalid
13182 handshakes fail, they fail with the error messages we expected.
13183 - Our unit testing code that captures log messages no longer
13184 prevents them from being written out if the user asked for them
13185 (by passing --debug or --info or or --notice --warn to the "test"
13186 binary). This change prevents us from missing unexpected log
13187 messages simply because we were looking for others. Related to
13189 - The unit tests now log all warning messages with the "BUG" flag.
13190 Previously, they only logged errors by default. This change will
13191 help us make our testing code more correct, and make sure that we
13192 only hit this code when we mean to. In the meantime, however,
13193 there will be more warnings in the unit test logs than before.
13194 This is preparatory work for ticket 19999.
13195 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
13196 assertion as a test failure.
13198 o Minor bug fixes (circuits):
13199 - Use the CircuitBuildTimeout option whenever
13200 LearnCircuitBuildTimeout is disabled. Previously, we would respect
13201 the option when a user disabled it, but not when it was disabled
13202 because some other option was set. Fixes bug 20073; bugfix on
13203 0.2.4.12-alpha. Patch by teor.
13205 o Minor bugfixes (allocation):
13206 - Change how we allocate memory for large chunks on buffers, to
13207 avoid a (currently impossible) integer overflow, and to waste less
13208 space when allocating unusually large chunks. Fixes bug 20081;
13209 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
13210 - Always include orconfig.h before including any other C headers.
13211 Sometimes, it includes macros that affect the behavior of the
13212 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
13213 first version to use AC_USE_SYSTEM_EXTENSIONS).
13214 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
13215 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
13216 Patch from Gisle Vanem.
13217 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
13218 They apparently require a set of annotations that we aren't
13219 currently using, and they create false positives in our pthreads
13220 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
13222 o Minor bugfixes (directory authority):
13223 - Die with a more useful error when the operator forgets to place
13224 the authority_signing_key file into the keys directory. This
13225 avoids an uninformative assert & traceback about having an invalid
13226 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
13227 - When allowing private addresses, mark Exits that only exit to
13228 private locations as such. Fixes bug 20064; bugfix
13231 o Minor bugfixes (documentation):
13232 - Document the default PathsNeededToBuildCircuits value that's used
13233 by clients when the directory authorities don't set
13234 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
13235 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
13236 - Fix manual for the User option: it takes a username, not a UID.
13237 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
13240 o Minor bugfixes (hidden services):
13241 - Stop logging intro point details to the client log on certain
13242 error conditions. Fixed as part of bug 20012; bugfix on
13243 0.2.4.8-alpha. Patch by teor.
13245 o Minor bugfixes (IPv6, testing):
13246 - Check for IPv6 correctly on Linux when running test networks.
13247 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
13249 o Minor bugfixes (Linux seccomp2 sandbox):
13250 - Add permission to run the sched_yield() and sigaltstack() system
13251 calls, in order to support versions of Tor compiled with asan or
13252 ubsan code that use these calls. Now "sandbox 1" and
13253 "--enable-expensive-hardening" should be compatible on more
13254 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
13256 o Minor bugfixes (logging):
13257 - When logging a message from the BUG() macro, be explicit about
13258 what we were asserting. Previously we were confusing what we were
13259 asserting with what the bug was. Fixes bug 20093; bugfix
13261 - When we are unable to remove the bw_accounting file, do not warn
13262 if the reason we couldn't remove it was that it didn't exist.
13263 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
13265 o Minor bugfixes (option parsing):
13266 - Count unix sockets when counting client listeners (SOCKS, Trans,
13267 NATD, and DNS). This has no user-visible behaviour changes: these
13268 options are set once, and never read. Required for correct
13269 behaviour in ticket 17178. Fixes bug 19677; bugfix on
13270 0.2.6.3-alpha. Patch by teor.
13272 o Minor bugfixes (options):
13273 - Check the consistency of UseEntryGuards and EntryNodes more
13274 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
13276 - Stop changing the configured value of UseEntryGuards on
13277 authorities and Tor2web clients. Fixes bug 20074; bugfix on
13278 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
13281 o Minor bugfixes (Tor2web):
13282 - Prevent Tor2web clients running hidden services, these services
13283 are not anonymous due to the one-hop client paths. Fixes bug
13284 19678. Patch by teor.
13286 o Minor bugfixes (unit tests):
13287 - Fix a shared-random unit test that was failing on big endian
13288 architectures due to internal representation of a integer copied
13289 to a buffer. The test is changed to take a full 32 bytes of data
13290 and use the output of a python script that make the COMMIT and
13291 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
13293 - The tor_tls_server_info_callback unit test no longer crashes when
13294 debug-level logging is turned on. Fixes bug 20041; bugfix
13298 Changes in version 0.2.8.8 - 2016-09-23
13299 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
13300 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
13301 who select public relays as their bridges.
13303 o Major bugfixes (crash):
13304 - Fix a complicated crash bug that could affect Tor clients
13305 configured to use bridges when replacing a networkstatus consensus
13306 in which one of their bridges was mentioned. OpenBSD users saw
13307 more crashes here, but all platforms were potentially affected.
13308 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
13310 o Major bugfixes (relay, OOM handler):
13311 - Fix a timing-dependent assertion failure that could occur when we
13312 tried to flush from a circuit after having freed its cells because
13313 of an out-of-memory condition. Fixes bug 20203; bugfix on
13314 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
13317 o Minor feature (fallback directories):
13318 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
13319 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
13320 2016. Closes ticket 20190; patch by teor.
13322 o Minor features (geoip):
13323 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
13327 Changes in version 0.2.9.2-alpha - 2016-08-24
13328 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
13329 several new features and bugfixes. It also includes an important
13330 authority update and an important bugfix from 0.2.8.7. Everyone who
13331 sets the ReachableAddresses option, and all bridges, are strongly
13332 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
13334 o Directory authority changes (also in 0.2.8.7):
13335 - The "Tonga" bridge authority has been retired; the new bridge
13336 authority is "Bifroest". Closes tickets 19728 and 19690.
13338 o Major bugfixes (client, security, also in 0.2.8.7):
13339 - Only use the ReachableAddresses option to restrict the first hop
13340 in a path. In earlier versions of 0.2.8.x, it would apply to
13341 every hop in the path, with a possible degradation in anonymity
13342 for anyone using an uncommon ReachableAddress setting. Fixes bug
13343 19973; bugfix on 0.2.8.2-alpha.
13345 o Major features (user interface):
13346 - Tor now supports the ability to declare options deprecated, so
13347 that we can recommend that people stop using them. Previously,
13348 this was done in an ad-hoc way. Closes ticket 19820.
13350 o Major bugfixes (directory downloads):
13351 - Avoid resetting download status for consensuses hourly, since we
13352 already have another, smarter retry mechanism. Fixes bug 8625;
13353 bugfix on 0.2.0.9-alpha.
13355 o Minor features (config):
13356 - Warn users when descriptor and port addresses are inconsistent.
13357 Mitigates bug 13953; patch by teor.
13359 o Minor features (geoip):
13360 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
13363 o Minor features (user interface):
13364 - There is a new --list-deprecated-options command-line option to
13365 list all of the deprecated options. Implemented as part of
13368 o Minor bugfixes (code style):
13369 - Fix an integer signedness conversion issue in the case conversion
13370 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
13372 o Minor bugfixes (compilation):
13373 - Build correctly on versions of libevent2 without support for
13374 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
13376 - Fix a compilation warning on GCC versions before 4.6. Our
13377 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
13378 when it is also required as an argument to the compiler pragma.
13379 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
13381 o Minor bugfixes (compilation, also in 0.2.8.7):
13382 - Remove an inappropriate "inline" in tortls.c that was causing
13383 warnings on older versions of GCC. Fixes bug 19903; bugfix
13386 o Minor bugfixes (fallback directories, also in 0.2.8.7):
13387 - Avoid logging a NULL string pointer when loading fallback
13388 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
13389 and 0.2.8.1-alpha. Report and patch by "rubiate".
13391 o Minor bugfixes (logging):
13392 - Log a more accurate message when we fail to dump a microdescriptor.
13393 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
13395 o Minor bugfixes (memory leak):
13396 - Fix a series of slow memory leaks related to parsing torrc files
13397 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
13399 o Deprecated features:
13400 - A number of DNS-cache-related sub-options for client ports are now
13401 deprecated for security reasons, and may be removed in a future
13402 version of Tor. (We believe that client-side DNS caching is a bad
13403 idea for anonymity, and you should not turn it on.) The options
13404 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
13405 UseIPv4Cache, and UseIPv6Cache.
13406 - A number of options are deprecated for security reasons, and may
13407 be removed in a future version of Tor. The options are:
13408 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
13409 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
13410 CloseHSClientCircuitsImmediatelyOnTimeout,
13411 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
13412 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
13413 UseNTorHandshake, and WarnUnsafeSocks.
13414 - The *ListenAddress options are now deprecated as unnecessary: the
13415 corresponding *Port options should be used instead. These options
13416 may someday be removed. The affected options are:
13417 ControlListenAddress, DNSListenAddress, DirListenAddress,
13418 NATDListenAddress, ORListenAddress, SocksListenAddress,
13419 and TransListenAddress.
13422 - Correct the IPv6 syntax in our documentation for the
13423 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
13426 - We no longer include the (dead, deprecated) bufferevent code in
13427 Tor. Closes ticket 19450. Based on a patch from U+039b.
13430 Changes in version 0.2.8.7 - 2016-08-24
13431 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
13432 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
13433 who sets the ReachableAddresses option, and all bridges, are strongly
13434 encouraged to upgrade.
13436 o Directory authority changes:
13437 - The "Tonga" bridge authority has been retired; the new bridge
13438 authority is "Bifroest". Closes tickets 19728 and 19690.
13440 o Major bugfixes (client, security):
13441 - Only use the ReachableAddresses option to restrict the first hop
13442 in a path. In earlier versions of 0.2.8.x, it would apply to
13443 every hop in the path, with a possible degradation in anonymity
13444 for anyone using an uncommon ReachableAddress setting. Fixes bug
13445 19973; bugfix on 0.2.8.2-alpha.
13447 o Minor features (geoip):
13448 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
13451 o Minor bugfixes (compilation):
13452 - Remove an inappropriate "inline" in tortls.c that was causing
13453 warnings on older versions of GCC. Fixes bug 19903; bugfix
13456 o Minor bugfixes (fallback directories):
13457 - Avoid logging a NULL string pointer when loading fallback
13458 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
13459 and 0.2.8.1-alpha. Report and patch by "rubiate".
13462 Changes in version 0.2.9.1-alpha - 2016-08-08
13463 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
13464 series. It improves our support for hardened builds and compiler
13465 warnings, deploys some critical infrastructure for improvements to
13466 hidden services, includes a new timing backend that we hope to use for
13467 better support for traffic padding, makes it easier for programmers to
13468 log unexpected events, and contains other small improvements to
13469 security, correctness, and performance.
13471 Below are the changes since 0.2.8.6.
13473 o New system requirements:
13474 - Tor now requires Libevent version 2.0.10-stable or later. Older
13475 versions of Libevent have less efficient backends for several
13476 platforms, and lack the DNS code that we use for our server-side
13477 DNS support. This implements ticket 19554.
13478 - Tor now requires zlib version 1.2 or later, for security,
13479 efficiency, and (eventually) gzip support. (Back when we started,
13480 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
13481 released in 2003. We recommend the latest version.)
13483 o Major features (build, hardening):
13484 - Tor now builds with -ftrapv by default on compilers that support
13485 it. This option detects signed integer overflow (which C forbids),
13486 and turns it into a hard-failure. We do not apply this option to
13487 code that needs to run in constant time to avoid side-channels;
13488 instead, we use -fwrapv in that code. Closes ticket 17983.
13489 - When --enable-expensive-hardening is selected, stop applying the
13490 clang/gcc sanitizers to code that needs to run in constant time.
13491 Although we are aware of no introduced side-channels, we are not
13492 able to prove that there are none. Related to ticket 17983.
13494 o Major features (compilation):
13495 - Our big list of extra GCC warnings is now enabled by default when
13496 building with GCC (or with anything like Clang that claims to be
13497 GCC-compatible). To make all warnings into fatal compilation
13498 errors, pass --enable-fatal-warnings to configure. Closes
13500 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
13501 turn on C and POSIX extensions. (Previously, we attempted to do
13502 this on an ad hoc basis.) Closes ticket 19139.
13504 o Major features (directory authorities, hidden services):
13505 - Directory authorities can now perform the shared randomness
13506 protocol specified by proposal 250. Using this protocol, directory
13507 authorities generate a global fresh random value every day. In the
13508 future, this value will be used by hidden services to select
13509 HSDirs. This release implements the directory authority feature;
13510 the hidden service side will be implemented in the future as part
13511 of proposal 224. Resolves ticket 16943; implements proposal 250.
13513 o Major features (downloading, random exponential backoff):
13514 - When we fail to download an object from a directory service, wait
13515 for an (exponentially increasing) randomized amount of time before
13516 retrying, rather than a fixed interval as we did before. This
13517 prevents a group of Tor instances from becoming too synchronized,
13518 or a single Tor instance from becoming too predictable, in its
13519 download schedule. Closes ticket 15942.
13521 o Major bugfixes (exit policies):
13522 - Avoid disclosing exit outbound bind addresses, configured port
13523 bind addresses, and local interface addresses in relay descriptors
13524 by default under ExitPolicyRejectPrivate. Instead, only reject
13525 these (otherwise unlisted) addresses if
13526 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
13527 0.2.7.2-alpha. Patch by teor.
13529 o Major bugfixes (hidden service client):
13530 - Allow Tor clients with appropriate controllers to work with
13531 FetchHidServDescriptors set to 0. Previously, this option also
13532 disabled descriptor cache lookup, thus breaking hidden services
13533 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
13535 o Minor features (build, hardening):
13536 - Detect and work around a libclang_rt problem that would prevent
13537 clang from finding __mulodi4() on some 32-bit platforms, and thus
13538 keep -ftrapv from linking on those systems. Closes ticket 19079.
13539 - When building on a system without runtime support for the runtime
13540 hardening options, try to log a useful warning at configuration
13541 time, rather than an incomprehensible warning at link time. If
13542 expensive hardening was requested, this warning becomes an error.
13543 Closes ticket 18895.
13545 o Minor features (code safety):
13546 - In our integer-parsing functions, ensure that maxiumum value we
13547 give is no smaller than the minimum value. Closes ticket 19063;
13550 o Minor features (controller):
13551 - Implement new GETINFO queries for all downloads that use
13552 download_status_t to schedule retries. This allows controllers to
13553 examine the schedule for pending downloads. Closes ticket 19323.
13554 - Allow controllers to configure basic client authorization on
13555 hidden services when they create them with the ADD_ONION control
13556 command. Implements ticket 15588. Patch by "special".
13557 - Fire a STATUS_SERVER controller event whenever the hibernation
13558 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
13560 o Minor features (directory authority):
13561 - Directory authorities now only give the Guard flag to a relay if
13562 they are also giving it the Stable flag. This change allows us to
13563 simplify path selection for clients. It should have minimal effect
13564 in practice, since >99% of Guards already have the Stable flag.
13565 Implements ticket 18624.
13566 - Directory authorities now write their v3-status-votes file out to
13567 disk earlier in the consensus process, so we have a record of the
13568 votes even if we abort the consensus process. Resolves
13571 o Minor features (hidden service):
13572 - Stop being so strict about the payload length of "rendezvous1"
13573 cells. We used to be locked in to the "TAP" handshake length, and
13574 now we can handle better handshakes like "ntor". Resolves
13577 o Minor features (infrastructure, time):
13578 - Tor now uses the operating system's monotonic timers (where
13579 available) for internal fine-grained timing. Previously we would
13580 look at the system clock, and then attempt to compensate for the
13581 clock running backwards. Closes ticket 18908.
13582 - Tor now includes an improved timer backend, so that we can
13583 efficiently support tens or hundreds of thousands of concurrent
13584 timers, as will be needed for some of our planned anti-traffic-
13585 analysis work. This code is based on William Ahern's "timeout.c"
13586 project, which implements a "tickless hierarchical timing wheel".
13587 Closes ticket 18365.
13589 o Minor features (logging):
13590 - Provide a more useful warning message when configured with an
13591 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
13592 - When dumping unparseable router descriptors, optionally store them
13593 in separate files, named by digest, up to a configurable size
13594 limit. You can change the size limit by setting the
13595 MaxUnparseableDescSizeToLog option, and disable this feature by
13596 setting that option to 0. Closes ticket 18322.
13597 - Add a set of macros to check nonfatal assertions, for internal
13598 use. Migrating more of our checks to these should help us avoid
13599 needless crash bugs. Closes ticket 18613.
13601 o Minor features (performance):
13602 - Change the "optimistic data" extension from "off by default" to
13603 "on by default". The default was ordinarily overridden by a
13604 consensus option, but when clients were bootstrapping for the
13605 first time, they would not have a consensus to get the option
13606 from. Changing this default saves a round-trip during startup.
13607 Closes ticket 18815.
13609 o Minor features (relay, usability):
13610 - When the directory authorities refuse a bad relay's descriptor,
13611 encourage the relay operator to contact us. Many relay operators
13612 won't notice this line in their logs, but it's a win if even a few
13613 learn why we don't like what their relay was doing. Resolves
13616 o Minor features (testing):
13617 - Let backtrace tests work correctly under AddressSanitizer. Fixes
13618 part of bug 18934; bugfix on 0.2.5.2-alpha.
13619 - Move the test-network.sh script to chutney, and modify tor's test-
13620 network.sh to call the (newer) chutney version when available.
13621 Resolves ticket 19116. Patch by teor.
13622 - Use the lcov convention for marking lines as unreachable, so that
13623 we don't count them when we're generating test coverage data.
13624 Update our coverage tools to understand this convention. Closes
13627 o Minor bugfixes (bootstrap):
13628 - Remember the directory we fetched the consensus or previous
13629 certificates from, and use it to fetch future authority
13630 certificates. This change improves bootstrapping performance.
13631 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
13633 o Minor bugfixes (build):
13634 - The test-stem and test-network makefile targets now depend only on
13635 the tor binary that they are testing. Previously, they depended on
13636 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
13637 patch from "cypherpunks".
13639 o Minor bugfixes (circuits):
13640 - Make sure extend_info_from_router() is only called on servers.
13641 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
13643 o Minor bugfixes (compilation):
13644 - When building with Clang, use a full set of GCC warnings.
13645 (Previously, we included only a subset, because of the way we
13646 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
13648 o Minor bugfixes (directory authority):
13649 - Authorities now sort the "package" lines in their votes, for ease
13650 of debugging. (They are already sorted in consensus documents.)
13651 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
13652 - When parsing a detached signature, make sure we use the length of
13653 the digest algorithm instead of an hardcoded DIGEST256_LEN in
13654 order to avoid comparing bytes out-of-bounds with a smaller digest
13655 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
13657 o Minor bugfixes (documentation):
13658 - Document the --passphrase-fd option in the tor manpage. Fixes bug
13659 19504; bugfix on 0.2.7.3-rc.
13660 - Fix the description of the --passphrase-fd option in the
13661 tor-gencert manpage. The option is used to pass the number of a
13662 file descriptor to read the passphrase from, not to read the file
13663 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
13665 o Minor bugfixes (ephemeral hidden service):
13666 - When deleting an ephemeral hidden service, close its intro points
13667 even if they are not completely open. Fixes bug 18604; bugfix
13670 o Minor bugfixes (guard selection):
13671 - Use a single entry guard even if the NumEntryGuards consensus
13672 parameter is not provided. Fixes bug 17688; bugfix
13674 - Don't mark guards as unreachable if connection_connect() fails.
13675 That function fails for local reasons, so it shouldn't reveal
13676 anything about the status of the guard. Fixes bug 14334; bugfix
13679 o Minor bugfixes (hidden service client):
13680 - Increase the minimum number of internal circuits we preemptively
13681 build from 2 to 3, so a circuit is available when a client
13682 connects to another onion service. Fixes bug 13239; bugfix
13685 o Minor bugfixes (logging):
13686 - When logging a directory ownership mismatch, log the owning
13687 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
13689 o Minor bugfixes (memory leaks):
13690 - Fix a small, uncommon memory leak that could occur when reading a
13691 truncated ed25519 key file. Fixes bug 18956; bugfix
13694 o Minor bugfixes (testing):
13695 - Allow clients to retry HSDirs much faster in test networks. Fixes
13696 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
13697 - Disable ASAN's detection of segmentation faults while running
13698 test_bt.sh, so that we can make sure that our own backtrace
13699 generation code works. Fixes another aspect of bug 18934; bugfix
13700 on 0.2.5.2-alpha. Patch from "cypherpunks".
13701 - Fix the test-network-all target on out-of-tree builds by using the
13702 correct path to the test driver script. Fixes bug 19421; bugfix
13705 o Minor bugfixes (time):
13706 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
13707 bugfix on all released tor versions.
13708 - When computing the difference between two times in milliseconds,
13709 we now round to the nearest millisecond correctly. Previously, we
13710 could sometimes round in the wrong direction. Fixes bug 19428;
13711 bugfix on 0.2.2.2-alpha.
13713 o Minor bugfixes (user interface):
13714 - Display a more accurate number of suppressed messages in the log
13715 rate-limiter. Previously, there was a potential integer overflow
13716 in the counter. Now, if the number of messages hits a maximum, the
13717 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
13719 - Fix a typo in the passphrase prompt for the ed25519 identity key.
13720 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
13722 o Code simplification and refactoring:
13723 - Remove redundant declarations of the MIN macro. Closes
13725 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
13726 Closes ticket 18462; patch from "icanhasaccount".
13727 - Split the 600-line directory_handle_command_get function into
13728 separate functions for different URL types. Closes ticket 16698.
13731 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
13732 ticket 19153. Patch from "U+039b".
13734 o Removed features:
13735 - Remove support for "GET /tor/bytes.txt" DirPort request, and
13736 "GETINFO dir-usage" controller request, which were only available
13737 via a compile-time option in Tor anyway. Feature was added in
13738 0.2.2.1-alpha. Resolves ticket 19035.
13739 - There is no longer a compile-time option to disable support for
13740 TransPort. (If you don't want TransPort; just don't use it.) Patch
13741 from "U+039b". Closes ticket 19449.
13744 - Run more workqueue tests as part of "make check". These had
13745 previously been implemented, but you needed to know special
13746 command-line options to enable them.
13747 - We now have unit tests for our code to reject zlib "compression
13748 bombs". (Fortunately, the code works fine.)
13751 Changes in version 0.2.8.6 - 2016-08-02
13753 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
13755 The Tor 0.2.8 series improves client bootstrapping performance,
13756 completes the authority-side implementation of improved identity
13757 keys for relays, and includes numerous bugfixes and performance
13758 improvements throughout the program. This release continues to
13759 improve the coverage of Tor's test suite. For a full list of
13760 changes since Tor 0.2.7, see the ReleaseNotes file.
13762 Changes since 0.2.8.5-rc:
13764 o Minor features (geoip):
13765 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
13768 o Minor bugfixes (compilation):
13769 - Fix a compilation warning in the unit tests on systems where char
13770 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
13772 o Minor bugfixes (fallback directories):
13773 - Remove 1 fallback that was on the hardcoded list, then opted-out,
13774 leaving 89 of the 100 fallbacks originally introduced in Tor
13775 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
13777 o Minor bugfixes (Linux seccomp2 sandbox):
13778 - Allow more syscalls when running with "Sandbox 1" enabled:
13779 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
13780 some systems, these are required for Tor to start. Fixes bug
13781 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
13782 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
13783 so that get_interface_address6_via_udp_socket_hack() can work.
13784 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
13787 Changes in version 0.2.8.5-rc - 2016-07-07
13788 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
13789 series. If we find no new bugs or regressions here, the first stable
13790 0.2.8 release will be identical to it. It has a few small bugfixes
13791 against previous versions.
13793 o Directory authority changes:
13794 - Urras is no longer a directory authority. Closes ticket 19271.
13796 o Major bugfixes (heartbeat):
13797 - Fix a regression that would crash Tor when the periodic
13798 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
13799 0.2.8.1-alpha. Reported by "kubaku".
13801 o Minor features (build):
13802 - Tor now again builds with the recent OpenSSL 1.1 development
13803 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
13804 - When building manual pages, set the timezone to "UTC", so that the
13805 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
13806 Patch from intrigeri.
13808 o Minor bugfixes (fallback directory selection):
13809 - Avoid errors during fallback selection if there are no eligible
13810 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
13813 o Minor bugfixes (IPv6, microdescriptors):
13814 - Don't check node addresses when we only have a routerstatus. This
13815 allows IPv6-only clients to bootstrap by fetching microdescriptors
13816 from fallback directory mirrors. (The microdescriptor consensus
13817 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
13820 o Minor bugfixes (logging):
13821 - Reduce pointlessly verbose log messages when directory servers
13822 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
13823 0.2.8.1-alpha. Patch by teor.
13824 - When a fallback directory changes its fingerprint from the hard-
13825 coded fingerprint, log a less severe, more explanatory log
13826 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
13828 o Minor bugfixes (Linux seccomp2 sandboxing):
13829 - Allow statistics to be written to disk when "Sandbox 1" is
13830 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
13831 0.2.6.1-alpha respectively.
13833 o Minor bugfixes (user interface):
13834 - Remove a warning message "Service [scrubbed] not found after
13835 descriptor upload". This message appears when one uses HSPOST
13836 control command to upload a service descriptor. Since there is
13837 only a descriptor and no service, showing this message is
13838 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
13840 o Fallback directory list:
13841 - Add a comment to the generated fallback directory list that
13842 explains how to comment out unsuitable fallbacks in a way that's
13843 compatible with the stem fallback parser.
13844 - Update fallback whitelist and blacklist based on relay operator
13845 emails. Blacklist unsuitable (non-working, over-volatile)
13846 fallbacks. Resolves ticket 19071. Patch by teor.
13847 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
13848 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
13849 ticket 19071; patch by teor.
13852 Changes in version 0.2.8.4-rc - 2016-06-15
13853 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
13854 If we find no new bugs or regressions here, the first stable 0.2.8
13855 release will be identical to it. It has a few small bugfixes against
13858 o Major bugfixes (user interface):
13859 - Correctly give a warning in the cases where a relay is specified
13860 by nickname, and one such relay is found, but it is not officially
13861 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
13863 o Minor features (build):
13864 - Tor now builds once again with the recent OpenSSL 1.1 development
13865 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
13867 o Minor features (geoip):
13868 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
13871 o Minor bugfixes (compilation):
13872 - Cause the unit tests to compile correctly on mingw64 versions that
13873 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
13875 o Minor bugfixes (downloading):
13876 - Predict more correctly whether we'll be downloading over HTTP when
13877 we determine the maximum length of a URL. This should avoid a
13878 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
13882 Changes in version 0.2.8.3-alpha - 2016-05-26
13883 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
13884 the course of the 0.2.8 development cycle. It improves the behavior of
13885 directory clients, fixes several crash bugs, fixes a gap in compiler
13886 hardening, and allows the full integration test suite to run on
13889 o Major bugfixes (security, client, DNS proxy):
13890 - Stop a crash that could occur when a client running with DNSPort
13891 received a query with multiple address types, and the first
13892 address type was not supported. Found and fixed by Scott Dial.
13893 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
13895 o Major bugfixes (security, compilation):
13896 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
13897 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
13898 cause a compiler warning, thereby making other checks fail, and
13899 needlessly disabling compiler-hardening support. Fixes one case of
13900 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
13902 o Major bugfixes (security, directory authorities):
13903 - Fix a crash and out-of-bounds write during authority voting, when
13904 the list of relays includes duplicate ed25519 identity keys. Fixes
13905 bug 19032; bugfix on 0.2.8.2-alpha.
13907 o Major bugfixes (client, bootstrapping):
13908 - Check if bootstrap consensus downloads are still needed when the
13909 linked connection attaches. This prevents tor making unnecessary
13910 begindir-style connections, which are the only directory
13911 connections tor clients make since the fix for 18483 was merged.
13912 - Fix some edge cases where consensus download connections may not
13913 have been closed, even though they were not needed. Related to fix
13915 - Make relays retry consensus downloads the correct number of times,
13916 rather than the more aggressive client retry count. Fixes part of
13918 - Stop downloading consensuses when we have a consensus, even if we
13919 don't have all the certificates for it yet. Fixes bug 18809;
13920 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
13922 o Major bugfixes (directory mirrors):
13923 - Decide whether to advertise begindir support in the the same way
13924 we decide whether to advertise our DirPort. Allowing these
13925 decisions to become out-of-sync led to surprising behavior like
13926 advertising begindir support when hibernation made us not
13927 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
13930 o Major bugfixes (IPv6 bridges, client):
13931 - Actually use IPv6 addresses when selecting directory addresses for
13932 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
13935 o Major bugfixes (key management):
13936 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13937 pointer to the previous (uninitialized) key value. The impact here
13938 should be limited to a difficult-to-trigger crash, if OpenSSL is
13939 running an engine that makes key generation failures possible, or
13940 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13941 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13944 o Major bugfixes (testing):
13945 - Fix a bug that would block 'make test-network-all' on systems where
13946 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
13947 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
13948 bugfix on 0.2.8.1-alpha.
13950 o Minor features (clients):
13951 - Make clients, onion services, and bridge relays always use an
13952 encrypted begindir connection for directory requests. Resolves
13953 ticket 18483. Patch by "teor".
13955 o Minor features (fallback directory mirrors):
13956 - Give each fallback the same weight for client selection; restrict
13957 fallbacks to one per operator; report fallback directory detail
13958 changes when rebuilding list; add new fallback directory mirrors
13959 to the whitelist; and many other minor simplifications and fixes.
13960 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
13961 0.2.8.1-alpha; patch by "teor".
13962 - Replace the 21 fallbacks generated in January 2016 and included in
13963 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
13964 2016. Closes task 17158; patch by "teor".
13966 o Minor features (geoip):
13967 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
13970 o Minor bugfixes (assert, portability):
13971 - Fix an assertion failure in memarea.c on systems where "long" is
13972 shorter than the size of a pointer. Fixes bug 18716; bugfix
13975 o Minor bugfixes (bootstrap):
13976 - Consistently use the consensus download schedule for authority
13977 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
13979 o Minor bugfixes (build):
13980 - Remove a pair of redundant AM_CONDITIONAL declarations from
13981 configure.ac. Fixes one final case of bug 17744; bugfix
13983 - Resolve warnings when building on systems that are concerned with
13984 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
13986 - When libscrypt.h is found, but no libscrypt library can be linked,
13987 treat libscrypt as absent. Fixes bug 19161; bugfix
13990 o Minor bugfixes (client):
13991 - Turn all TestingClientBootstrap* into non-testing torrc options.
13992 This changes simply renames them by removing "Testing" in front of
13993 them and they do not require TestingTorNetwork to be enabled
13994 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
13995 - Make directory node selection more reliable, mainly for IPv6-only
13996 clients and clients with few reachable addresses. Fixes bug 18929;
13997 bugfix on 0.2.8.1-alpha. Patch by "teor".
13999 o Minor bugfixes (controller, microdescriptors):
14000 - Make GETINFO dir/status-vote/current/consensus conform to the
14001 control specification by returning "551 Could not open cached
14002 consensus..." when not caching consensuses. Fixes bug 18920;
14003 bugfix on 0.2.2.6-alpha.
14005 o Minor bugfixes (crypto, portability):
14006 - The SHA3 and SHAKE routines now produce the correct output on Big
14007 Endian systems. No code calls either algorithm yet, so this is
14008 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
14009 - Tor now builds again with the recent OpenSSL 1.1 development
14010 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
14013 o Minor bugfixes (directories):
14014 - When fetching extrainfo documents, compare their SHA256 digests
14015 and Ed25519 signing key certificates with the routerinfo that led
14016 us to fetch them, rather than with the most recent routerinfo.
14017 Otherwise we generate many spurious warnings about mismatches.
14018 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
14020 o Minor bugfixes (logging):
14021 - When we can't generate a signing key because OfflineMasterKey is
14022 set, do not imply that we should have been able to load it. Fixes
14023 bug 18133; bugfix on 0.2.7.2-alpha.
14024 - Stop periodic_event_dispatch() from blasting twelve lines per
14025 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
14026 - When rejecting a misformed INTRODUCE2 cell, only log at
14027 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
14029 o Minor bugfixes (pluggable transports):
14030 - Avoid reporting a spurious error when we decide that we don't need
14031 to terminate a pluggable transport because it has already exited.
14032 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
14034 o Minor bugfixes (pointer arithmetic):
14035 - Fix a bug in memarea_alloc() that could have resulted in remote
14036 heap write access, if Tor had ever passed an unchecked size to
14037 memarea_alloc(). Fortunately, all the sizes we pass to
14038 memarea_alloc() are pre-checked to be less than 128 kilobytes.
14039 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
14042 o Minor bugfixes (relays):
14043 - Consider more config options when relays decide whether to
14044 regenerate their descriptor. Fixes more of bug 12538; bugfix
14046 - Resolve some edge cases where we might launch an ORPort
14047 reachability check even when DisableNetwork is set. Noticed while
14048 fixing bug 18616; bugfix on 0.2.3.9-alpha.
14050 o Minor bugfixes (statistics):
14051 - We now include consensus downloads via IPv6 in our directory-
14052 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
14054 o Minor bugfixes (testing):
14055 - Allow directories in small networks to bootstrap by skipping
14056 DirPort checks when the consensus has no exits. Fixes bug 19003;
14057 bugfix on 0.2.8.1-alpha. Patch by teor.
14058 - Fix a small memory leak that would occur when the
14059 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
14060 bugfix on 0.2.5.2-alpha.
14062 o Minor bugfixes (time handling):
14063 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
14064 field. Otherwise, our unit tests crash on Windows. Fixes bug
14065 18977; bugfix on 0.2.2.25-alpha.
14068 - Document the contents of the 'datadir/keys' subdirectory in the
14069 manual page. Closes ticket 17621.
14070 - Stop recommending use of nicknames to identify relays in our
14071 MapAddress documentation. Closes ticket 18312.
14074 Changes in version 0.2.8.2-alpha - 2016-03-28
14075 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
14076 bugs in earlier versions of Tor, including some that prevented
14077 authorities using Tor 0.2.7.x from running correctly. IPv6 and
14078 directory support should also be much improved.
14080 o New system requirements:
14081 - Tor no longer supports versions of OpenSSL with a broken
14082 implementation of counter mode. (This bug was present in OpenSSL
14083 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
14084 longer runs with, these versions.
14085 - Tor no longer attempts to support platforms where the "time_t"
14086 type is unsigned. (To the best of our knowledge, only OpenVMS does
14087 this, and Tor has never actually built on OpenVMS.) Closes
14089 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
14090 later (released in 2008 and 2009 respectively). If you are
14091 building Tor from the git repository instead of from the source
14092 distribution, and your tools are older than this, you will need to
14093 upgrade. Closes ticket 17732.
14095 o Major bugfixes (security, pointers):
14096 - Avoid a difficult-to-trigger heap corruption attack when extending
14097 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14098 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14099 Reported by Guido Vranken.
14101 o Major bugfixes (bridges, pluggable transports):
14102 - Modify the check for OR connections to private addresses. Allow
14103 bridges on private addresses, including pluggable transports that
14104 ignore the (potentially private) address in the bridge line. Fixes
14105 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
14107 o Major bugfixes (compilation):
14108 - Repair hardened builds under the clang compiler. Previously, our
14109 use of _FORTIFY_SOURCE would conflict with clang's address
14110 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
14112 o Major bugfixes (crash on shutdown):
14113 - Correctly handle detaching circuits from muxes when shutting down.
14114 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
14115 - Fix an assert-on-exit bug related to counting memory usage in
14116 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
14118 o Major bugfixes (crash on startup):
14119 - Fix a segfault during startup: If a Unix domain socket was
14120 configured as listener (such as a ControlSocket or a SocksPort
14121 "unix:" socket), and tor was started as root but not configured to
14122 switch to another user, tor would segfault while trying to string
14123 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
14126 o Major bugfixes (dns proxy mode, crash):
14127 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14128 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14130 o Major bugfixes (relays, bridge clients):
14131 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
14132 bridge clients use the address configured in the bridge line.
14133 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
14136 o Major bugfixes (voting):
14137 - Actually enable support for authorities to match routers by their
14138 Ed25519 identities. Previously, the code had been written, but
14139 some debugging code that had accidentally been left in the
14140 codebase made it stay turned off. Fixes bug 17702; bugfix
14142 - When collating votes by Ed25519 identities, authorities now
14143 include a "NoEdConsensus" flag if the ed25519 value (or lack
14144 thereof) for a server does not reflect the majority consensus.
14145 Related to bug 17668; bugfix on 0.2.7.2-alpha.
14146 - When generating a vote with keypinning disabled, never include two
14147 entries for the same ed25519 identity. This bug was causing
14148 authorities to generate votes that they could not parse when a
14149 router violated key pinning by changing its RSA identity but
14150 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
14151 18318. Bugfix on 0.2.7.2-alpha.
14153 o Minor features (security, win32):
14154 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
14155 attack. Fixes bug 18123; bugfix on all tor versions. Patch
14158 o Minor features (bug-resistance):
14159 - Make Tor survive errors involving connections without a
14160 corresponding event object. Previously we'd fail with an
14161 assertion; now we produce a log message. Related to bug 16248.
14163 o Minor features (build):
14164 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
14165 as having possible IPFW support. Closes ticket 18448. Patch from
14166 Steven Chamberlain.
14168 o Minor features (code hardening):
14169 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
14170 level code, to harden against accidental failures to NUL-
14171 terminate. Part of ticket 17852. Patch from jsturgix. Found
14174 o Minor features (crypto):
14175 - Validate the hard-coded Diffie-Hellman parameters and ensure that
14176 p is a safe prime, and g is a suitable generator. Closes
14179 o Minor features (geoip):
14180 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
14183 o Minor features (hidden service directory):
14184 - Streamline relay-side hsdir handling: when relays consider whether
14185 to accept an uploaded hidden service descriptor, they no longer
14186 check whether they are one of the relays in the network that is
14187 "supposed" to handle that descriptor. Implements ticket 18332.
14189 o Minor features (IPv6):
14190 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
14191 to 1, tor prefers IPv6 directory addresses.
14192 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
14193 avoids using IPv4 for client OR and directory connections.
14194 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
14195 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
14196 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
14198 o Minor features (linux seccomp2 sandbox):
14199 - Reject attempts to change our Address with "Sandbox 1" enabled.
14200 Changing Address with Sandbox turned on would never actually work,
14201 but previously it would fail in strange and confusing ways. Found
14202 while fixing 18548.
14204 o Minor features (robustness):
14205 - Exit immediately with an error message if the code attempts to use
14206 Libevent without having initialized it. This should resolve some
14207 frequently-made mistakes in our unit tests. Closes ticket 18241.
14209 o Minor features (unix domain sockets):
14210 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
14211 Unix domain sockets without checking the permissions on the parent
14212 directory. (Tor checks permissions by default because some
14213 operating systems only check permissions on the parent directory.
14214 However, some operating systems do look at permissions on the
14215 socket, and tor's default check is unneeded.) Closes ticket 18458.
14218 o Minor bugfixes (exit policies, security):
14219 - Refresh an exit relay's exit policy when interface addresses
14220 change. Previously, tor only refreshed the exit policy when the
14221 configured external address changed. Fixes bug 18208; bugfix on
14222 0.2.7.3-rc. Patch by teor.
14224 o Minor bugfixes (security, hidden services):
14225 - Prevent hidden services connecting to client-supplied rendezvous
14226 addresses that are reserved as internal or multicast. Fixes bug
14227 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
14229 o Minor bugfixes (build):
14230 - Do not link the unit tests against both the testing and non-
14231 testing versions of the static libraries. Fixes bug 18490; bugfix
14233 - Avoid spurious failures from configure files related to calling
14234 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
14235 0.2.0.1-alpha. Patch from "cypherpunks".
14236 - Silence spurious clang-scan warnings in the ed25519_donna code by
14237 explicitly initializing some objects. Fixes bug 18384; bugfix on
14238 0.2.7.2-alpha. Patch by teor.
14240 o Minor bugfixes (client, bootstrap):
14241 - Count receipt of new microdescriptors as progress towards
14242 bootstrapping. Previously, with EntryNodes set, Tor might not
14243 successfully repopulate the guard set on bootstrapping. Fixes bug
14244 16825; bugfix on 0.2.3.1-alpha.
14246 o Minor bugfixes (code correctness):
14247 - Update to the latest version of Trunnel, which tries harder to
14248 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
14249 by clang address sanitizer. Fixes bug 18373; bugfix
14252 o Minor bugfixes (configuration):
14253 - Fix a tiny memory leak when parsing a port configuration ending in
14254 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
14256 o Minor bugfixes (containers):
14257 - If we somehow attempt to construct a heap with more than
14258 1073741822 elements, avoid an integer overflow when maintaining
14259 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
14261 o Minor bugfixes (correctness):
14262 - Fix a bad memory handling bug that would occur if we had queued a
14263 cell on a channel's incoming queue. Fortunately, we can't actually
14264 queue a cell like that as our code is constructed today, but it's
14265 best to avoid this kind of error, even if there isn't any code
14266 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
14268 o Minor bugfixes (directory):
14269 - When generating a URL for a directory server on an IPv6 address,
14270 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
14271 on 0.2.3.9-alpha. Patch from Malek.
14273 o Minor bugfixes (fallback directory mirrors):
14274 - When requesting extrainfo descriptors from a trusted directory
14275 server, check whether it is an authority or a fallback directory
14276 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
14277 0.2.4.7-alpha. Reported by atagar, patch by teor.
14279 o Minor bugfixes (hidden service, client):
14280 - Handle the case where the user makes several fast consecutive
14281 requests to the same .onion address. Previously, the first six
14282 requests would each trigger a descriptor fetch, each picking a
14283 directory (there are 6 overall) and the seventh one would fail
14284 because no directories were left, thereby triggering a close on
14285 all current directory connections asking for the hidden service.
14286 The solution here is to not close the connections if we have
14287 pending directory fetches. Fixes bug 15937; bugfix
14290 o Minor bugfixes (hidden service, control port):
14291 - Add the onion address to the HS_DESC event for the UPLOADED action
14292 both on success or failure. It was previously hardcoded with
14293 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
14295 o Minor bugfixes (hidden service, directory):
14296 - Bridges now refuse "rendezvous2" (hidden service descriptor)
14297 publish attempts. Suggested by ticket 18332.
14299 o Minor bugfixes (linux seccomp2 sandbox):
14300 - Allow the setrlimit syscall, and the prlimit and prlimit64
14301 syscalls, which some libc implementations use under the hood.
14302 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
14303 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
14304 enabled and no DNS resolvers configured. This should help TAILS
14305 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
14306 - Fix the sandbox's interoperability with unix domain sockets under
14307 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
14309 o Minor bugfixes (logging):
14310 - When logging information about an unparsable networkstatus vote or
14311 consensus, do not say "vote" when we mean consensus. Fixes bug
14312 18368; bugfix on 0.2.0.8-alpha.
14313 - Scrub service name in "unrecognized service ID" log messages.
14314 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
14315 - Downgrade logs and backtraces about IP versions to info-level.
14316 Only log backtraces once each time tor runs. Assists in diagnosing
14317 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
14318 Christian, patch by teor.
14320 o Minor bugfixes (memory safety):
14321 - Avoid freeing an uninitialized pointer when opening a socket fails
14322 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
14323 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
14325 - Correctly duplicate addresses in get_interface_address6_list().
14326 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
14327 patch by "cypherpunks".
14328 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
14330 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
14331 18672; bugfix on 0.2.5.1-alpha.
14333 o Minor bugfixes (private directory):
14334 - Prevent a race condition when creating private directories. Fixes
14335 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
14336 Patch from jsturgix. Found with Flawfinder.
14338 o Minor bugfixes (test networks, IPv6):
14339 - Allow internal IPv6 addresses in descriptors in test networks.
14340 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
14343 o Minor bugfixes (testing):
14344 - We no longer disable assertions in the unit tests when coverage is
14345 enabled. Instead, we require you to say --disable-asserts-in-tests
14346 to the configure script if you need assertions disabled in the
14347 unit tests (for example, if you want to perform branch coverage).
14348 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
14350 o Minor bugfixes (time parsing):
14351 - Avoid overflow in tor_timegm when parsing dates in and after 2038
14352 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
14353 0.0.2pre14. Patch by teor.
14355 o Minor bugfixes (tor-gencert):
14356 - Correctly handle the case where an authority operator enters a
14357 passphrase but sends an EOF before sending a newline. Fixes bug
14358 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
14360 o Code simplification and refactoring:
14361 - Quote all the string interpolations in configure.ac -- even those
14362 which we are pretty sure can't contain spaces. Closes ticket
14363 17744. Patch from zerosion.
14364 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
14365 inplace, so there's no need to have a separate implementation for
14366 the non-inplace code. Closes ticket 18258. Patch from Malek.
14367 - Simplify return types for some crypto functions that can't
14368 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
14371 - Change build messages to refer to "Fedora" instead of "Fedora
14372 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
14373 Patches from "icanhasaccount" and "cypherpunks".
14375 o Removed features:
14376 - We no longer maintain an internal freelist in memarea.c.
14377 Allocators should be good enough to make this code unnecessary,
14378 and it's doubtful that it ever had any performance benefit.
14381 - Fix several warnings from clang's address sanitizer produced in
14383 - Treat backtrace test failures as expected on FreeBSD until we
14384 solve bug 17808. Closes ticket 18204.
14387 Changes in version 0.2.8.1-alpha - 2016-02-04
14388 Tor 0.2.8.1-alpha is the first alpha release in its series. It
14389 includes numerous small features and bugfixes against previous Tor
14390 versions, and numerous small infrastructure improvements. The most
14391 notable features are a set of improvements to the directory subsystem.
14393 o Major features (security, Linux):
14394 - When Tor starts as root on Linux and is told to switch user ID, it
14395 can now retain the capability to bind to low ports. By default,
14396 Tor will do this only when it's switching user ID and some low
14397 ports have been configured. You can change this behavior with the
14398 new option KeepBindCapabilities. Closes ticket 8195.
14400 o Major features (directory system):
14401 - When bootstrapping multiple consensus downloads at a time, use the
14402 first one that starts downloading, and close the rest. This
14403 reduces failures when authorities or fallback directories are slow
14404 or down. Together with the code for feature 15775, this feature
14405 should reduces failures due to fallback churn. Implements ticket
14406 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
14407 "mikeperry" and "teor".
14408 - Include a trial list of 21 default fallback directories, generated
14409 in January 2016, based on an opt-in survey of suitable relays.
14410 Doing this should make clients bootstrap more quickly and reliably,
14411 and reduce the load on the directory authorities. Closes ticket
14412 15775. Patch by "teor".
14413 Candidates identified using an OnionOO script by "weasel", "teor",
14414 "gsathya", and "karsten".
14415 - Previously only relays that explicitly opened a directory port
14416 (DirPort) accepted directory requests from clients. Now all
14417 relays, with and without a DirPort, accept and serve tunneled
14418 directory requests that they receive through their ORPort. You can
14419 disable this behavior using the new DirCache option. Closes
14422 o Major key updates:
14423 - Update the V3 identity key for the dannenberg directory authority:
14424 it was changed on 18 November 2015. Closes task 17906. Patch
14427 o Minor features (security, clock):
14428 - Warn when the system clock appears to move back in time (when the
14429 state file was last written in the future). Tor doesn't know that
14430 consensuses have expired if the clock is in the past. Patch by
14431 "teor". Implements ticket 17188.
14433 o Minor features (security, exit policies):
14434 - ExitPolicyRejectPrivate now rejects more private addresses by
14435 default. Specifically, it now rejects the relay's outbound bind
14436 addresses (if configured), and the relay's configured port
14437 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
14438 0.2.0.11-alpha. Patch by "teor".
14440 o Minor features (security, memory erasure):
14441 - Set the unused entries in a smartlist to NULL. This helped catch
14442 a (harmless) bug, and shouldn't affect performance too much.
14443 Implements ticket 17026.
14444 - Use SecureMemoryWipe() function to securely clean memory on
14445 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
14446 Implements feature 17986.
14447 - Use explicit_bzero or memset_s when present. Previously, we'd use
14448 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
14449 from <logan@hackers.mu> and <selven@hackers.mu>.
14450 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14451 zero size. Check size argument to memwipe() for underflow. Fixes
14452 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14455 o Minor features (security, RNG):
14456 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
14457 positively are not allowed to fail. Previously we depended on
14458 internal details of OpenSSL's behavior. Closes ticket 17686.
14459 - Never use the system entropy output directly for anything besides
14460 seeding the PRNG. When we want to generate important keys, instead
14461 of using system entropy directly, we now hash it with the PRNG
14462 stream. This may help resist certain attacks based on broken OS
14463 entropy implementations. Closes part of ticket 17694.
14464 - Use modern system calls (like getentropy() or getrandom()) to
14465 generate strong entropy on platforms that have them. Closes
14468 o Minor features (accounting):
14469 - Added two modes to the AccountingRule option: One for limiting
14470 only the number of bytes sent ("AccountingRule out"), and one for
14471 limiting only the number of bytes received ("AccountingRule in").
14472 Closes ticket 15989; patch from "unixninja92".
14474 o Minor features (build):
14475 - Since our build process now uses "make distcheck", we no longer
14476 force "make dist" to depend on "make check". Closes ticket 17893;
14477 patch from "cypherpunks."
14478 - Tor now builds successfully with the recent OpenSSL 1.1
14479 development branch, and with the latest LibreSSL. Closes tickets
14480 17549, 17921, and 17984.
14482 o Minor features (controller):
14483 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
14484 tickets 16774 and 17817. Patch by George Tankersley.
14485 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
14486 service descriptor from a service's local hidden service
14487 descriptor cache. Closes ticket 14846.
14488 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
14489 controllers can examine the the reject rules added by
14490 ExitPolicyRejectPrivate. This makes it easier for stem to display
14493 o Minor features (crypto):
14494 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
14496 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
14497 - When allocating a digest state object, allocate no more space than
14498 we actually need. Previously, we would allocate as much space as
14499 the state for the largest algorithm would need. This change saves
14500 up to 672 bytes per circuit. Closes ticket 17796.
14501 - Improve performance when hashing non-multiple of 8 sized buffers,
14502 based on Andrew Moon's public domain SipHash-2-4 implementation.
14503 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
14505 o Minor features (directory downloads):
14506 - Wait for busy authorities and fallback directories to become non-
14507 busy when bootstrapping. (A similar change was made in 6c443e987d
14508 for directory caches chosen from the consensus.) Closes ticket
14509 17864; patch by "teor".
14510 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
14511 directory mirrors. The default is 1; set it to 0 to disable
14512 fallbacks. Implements ticket 17576. Patch by "teor".
14514 o Minor features (geoip):
14515 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
14518 o Minor features (IPv6):
14519 - Add an argument 'ipv6=address:orport' to the DirAuthority and
14520 FallbackDir torrc options, to specify an IPv6 address for an
14521 authority or fallback directory. Add hard-coded ipv6 addresses for
14522 directory authorities that have them. Closes ticket 17327; patch
14523 from Nick Mathewson and "teor".
14524 - Add address policy assume_action support for IPv6 addresses.
14525 - Limit IPv6 mask bits to 128.
14526 - Warn when comparing against an AF_UNSPEC address in a policy, it's
14527 almost always a bug. Closes ticket 17863; patch by "teor".
14528 - Allow users to configure directory authorities and fallback
14529 directory servers with IPv6 addresses and ORPorts. Resolves
14531 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
14532 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
14533 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
14534 17638; bugfix on 0.0.2pre8. Patch by "teor".
14536 o Minor features (logging):
14537 - When logging to syslog, allow a tag to be added to the syslog
14538 identity (the string prepended to every log message). The tag can
14539 be configured with SyslogIdentityTag and defaults to none. Setting
14540 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
14543 o Minor features (portability):
14544 - Use timingsafe_memcmp() where available. Closes ticket 17944;
14545 patch from <logan@hackers.mu>.
14547 o Minor features (relay, address discovery):
14548 - Add a family argument to get_interface_addresses_raw() and
14549 subfunctions to make network interface address interogation more
14550 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
14551 types of interfaces from the operating system. Resolves
14553 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
14554 fails to enumerate interface addresses using the platform-specific
14555 API, have it rely on the UDP socket fallback technique to try and
14556 find out what IP addresses (both IPv4 and IPv6) our machine has.
14557 Resolves ticket 17951.
14559 o Minor features (replay cache):
14560 - The replay cache now uses SHA256 instead of SHA1. Implements
14561 feature 8961. Patch by "teor", issue reported by "rransom".
14563 o Minor features (unix file permissions):
14564 - Defer creation of Unix sockets until after setuid. This avoids
14565 needing CAP_CHOWN and CAP_FOWNER when using systemd's
14566 CapabilityBoundingSet, or chown and fowner when using SELinux.
14567 Implements part of ticket 17562. Patch from Jamie Nguyen.
14568 - If any directory created by Tor is marked as group readable, the
14569 filesystem group is allowed to be either the default GID or the
14570 root user. Allowing root to read the DataDirectory prevents the
14571 need for CAP_READ_SEARCH when using systemd's
14572 CapabilityBoundingSet, or dac_read_search when using SELinux.
14573 Implements part of ticket 17562. Patch from Jamie Nguyen.
14574 - Introduce a new DataDirectoryGroupReadable option. If it is set to
14575 1, the DataDirectory will be made readable by the default GID.
14576 Implements part of ticket 17562. Patch from Jamie Nguyen.
14578 o Minor bugfixes (accounting):
14579 - The max bandwidth when using 'AccountRule sum' is now correctly
14580 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
14581 from "unixninja92".
14583 o Minor bugfixes (code correctness):
14584 - When closing an entry connection, generate a warning if we should
14585 have sent an end cell for it but we haven't. Fixes bug 17876;
14586 bugfix on 0.2.3.2-alpha.
14587 - Assert that allocated memory held by the reputation code is freed
14588 according to its internal counters. Fixes bug 17753; bugfix
14590 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
14593 o Minor bugfixes (compilation):
14594 - Mark all object files that include micro-revision.i as depending
14595 on it, so as to make parallel builds more reliable. Fixes bug
14596 17826; bugfix on 0.2.5.1-alpha.
14597 - Don't try to use the pthread_condattr_setclock() function unless
14598 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
14599 17819; bugfix on 0.2.6.3-alpha.
14600 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
14602 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
14603 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
14604 - Fix search for libevent libraries on OpenBSD (and other systems
14605 that install libevent 1 and libevent 2 in parallel). Fixes bug
14606 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
14607 - Isolate environment variables meant for tests from the rest of the
14608 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
14609 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
14611 - Remove config.log only from make distclean, not from make clean.
14612 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
14614 o Minor bugfixes (crypto):
14615 - Check the return value of HMAC() and assert on failure. Fixes bug
14616 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
14618 o Minor bugfixes (fallback directories):
14619 - Mark fallbacks as "too busy" when they return a 503 response,
14620 rather than just marking authorities. Fixes bug 17572; bugfix on
14621 0.2.4.7-alpha. Patch by "teor".
14623 o Minor bugfixes (IPv6):
14624 - Update the limits in max_dl_per_request for IPv6 address length.
14625 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
14627 o Minor bugfixes (linux seccomp2 sandbox):
14628 - Fix a crash when using offline master ed25519 keys with the Linux
14629 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
14631 o Minor bugfixes (logging):
14632 - In log messages that include a function name, use __FUNCTION__
14633 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
14634 with clang __PRETTY_FUNCTION__ has extra information we don't
14635 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
14637 - Remove needless quotes from a log message about unparseable
14638 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
14640 o Minor bugfixes (portability):
14641 - Remove an #endif from configure.ac so that we correctly detect the
14642 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
14645 o Minor bugfixes (relays):
14646 - Check that both the ORPort and DirPort (if present) are reachable
14647 before publishing a relay descriptor. Otherwise, relays publish a
14648 descriptor with DirPort 0 when the DirPort reachability test takes
14649 longer than the ORPort reachability test. Fixes bug 18050; bugfix
14650 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
14652 o Minor bugfixes (relays, hidden services):
14653 - Refuse connection requests to private OR addresses unless
14654 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
14655 then refuse to send any cells to a private address. Fixes bugs
14656 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
14658 o Minor bugfixes (safe logging):
14659 - When logging a malformed hostname received through socks4, scrub
14660 it if SafeLogging says we should. Fixes bug 17419; bugfix
14663 o Minor bugfixes (statistics code):
14664 - Consistently check for overflow in round_*_to_next_multiple_of
14665 functions, and add unit tests with additional and maximal values.
14666 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
14667 - Handle edge cases in the laplace functions: avoid division by
14668 zero, avoid taking the log of zero, and silence clang type
14669 conversion warnings using round and trunc. Add unit tests for edge
14670 cases with maximal values. Fixes part of bug 13192; bugfix
14673 o Minor bugfixes (testing):
14674 - The test for log_heartbeat was incorrectly failing in timezones
14675 with non-integer offsets. Instead of comparing the end of the time
14676 string against a constant, compare it to the output of
14677 format_local_iso_time when given the correct input. Fixes bug
14678 18039; bugfix on 0.2.5.4-alpha.
14679 - Make unit tests pass on IPv6-only systems, and systems without
14680 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
14681 bugfix on 0.2.7.3-rc. Patch by "teor".
14682 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
14684 - Check the full results of SHA256 and SHA512 digests in the unit
14685 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
14687 o Code simplification and refactoring:
14688 - Move logging of redundant policy entries in
14689 policies_parse_exit_policy_internal into its own function. Closes
14690 ticket 17608; patch from "juce".
14691 - Extract the more complicated parts of circuit_mark_for_close()
14692 into a new function that we run periodically before circuits are
14693 freed. This change removes more than half of the functions
14694 currently in the "blob". Closes ticket 17218.
14695 - Clean up a little duplicated code in
14696 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
14698 - Decouple the list of streams waiting to be attached to circuits
14699 from the overall connection list. This change makes it possible to
14700 attach streams quickly while simplifying Tor's callgraph and
14701 avoiding O(N) scans of the entire connection list. Closes
14703 - When a direct directory request fails immediately on launch,
14704 instead of relaunching that request from inside the code that
14705 launches it, instead mark the connection for teardown. This change
14706 simplifies Tor's callback and prevents the directory-request
14707 launching code from invoking itself recursively. Closes
14709 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
14710 use them. Closes ticket 17926.
14713 - Add a description of the correct use of the '--keygen' command-
14714 line option. Closes ticket 17583; based on text by 's7r'.
14715 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
14716 - Explain actual minima for BandwidthRate. Closes ticket 16382.
14717 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
14718 - Mention torspec URL in the manpage and point the reader to it
14719 whenever we mention a document that belongs in torspce. Fixes
14722 o Removed features:
14723 - Remove client-side support for connecting to Tor relays running
14724 versions of Tor before 0.2.3.6-alpha. These relays didn't support
14725 the v3 TLS handshake protocol, and are no longer allowed on the
14726 Tor network. Implements the client side of ticket 11150. Based on
14727 patches by Tom van der Woerdt.
14730 - Add unit tests to check for common RNG failure modes, such as
14731 returning all zeroes, identical values, or incrementing values
14732 (OpenSSL's rand_predictable feature). Patch by "teor".
14733 - Log more information when the backtrace tests fail. Closes ticket
14734 17892. Patch from "cypherpunks."
14735 - Always test both ed25519 backends, so that we can be sure that our
14736 batch-open replacement code works. Part of ticket 16794.
14737 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
14738 portion of ticket 16831.
14739 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
14740 util_format.c, directory.c, and options_validate.c. Closes tickets
14741 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
14743 - Unit tests for directory_handle_command_get. Closes ticket 17004.
14744 Patch from Reinaldo de Souza Jr.
14747 Changes in version 0.2.7.6 - 2015-12-10
14748 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
14749 well as a minor bug in hidden service reliability.
14751 o Major bugfixes (guard selection):
14752 - Actually look at the Guard flag when selecting a new directory
14753 guard. When we implemented the directory guard design, we
14754 accidentally started treating all relays as if they have the Guard
14755 flag during guard selection, leading to weaker anonymity and worse
14756 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
14759 o Minor features (geoip):
14760 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
14763 o Minor bugfixes (compilation):
14764 - When checking for net/pfvar.h, include netinet/in.h if possible.
14765 This fixes transparent proxy detection on OpenBSD. Fixes bug
14766 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
14767 - Fix a compilation warning with Clang 3.6: Do not check the
14768 presence of an address which can never be NULL. Fixes bug 17781.
14770 o Minor bugfixes (correctness):
14771 - When displaying an IPv6 exit policy, include the mask bits
14772 correctly even when the number is greater than 31. Fixes bug
14773 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
14774 - The wrong list was used when looking up expired intro points in a
14775 rend service object, causing what we think could be reachability
14776 issues for hidden services, and triggering a BUG log. Fixes bug
14777 16702; bugfix on 0.2.7.2-alpha.
14778 - Fix undefined behavior in the tor_cert_checksig function. Fixes
14779 bug 17722; bugfix on 0.2.7.2-alpha.
14782 Changes in version 0.2.7.5 - 2015-11-20
14783 The Tor 0.2.7 release series is dedicated to the memory of Tor user
14784 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
14785 tirelessly to advocate human rights regardless of national borders,
14786 and oppose the encroachments of mass surveillance. He opposed national
14787 exceptionalism, he brought clarity to legal and policy debates, he
14788 understood and predicted the impact of mass surveillance on the world,
14789 and he laid the groundwork for resisting it. While serving on the Tor
14790 Project's board of directors, he brought us his uncompromising focus
14791 on technical excellence in the service of humankind. Caspar was an
14792 inimitable force for good and a wonderful friend. He was kind,
14793 humorous, generous, gallant, and believed we should protect one
14794 another without exception. We honor him here for his ideals, his
14795 efforts, and his accomplishments. Please honor his memory with works
14796 that would make him proud.
14798 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
14800 The 0.2.7 series adds a more secure identity key type for relays,
14801 improves cryptography performance, resolves several longstanding
14802 hidden-service performance issues, improves controller support for
14803 hidden services, and includes small bugfixes and performance
14804 improvements throughout the program. This release series also includes
14805 more tests than before, and significant simplifications to which parts
14806 of Tor invoke which others.
14808 (This release contains no code changes since 0.2.7.4-rc.)
14811 Changes in version 0.2.7.4-rc - 2015-10-21
14812 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
14813 fixes some important memory leaks, and a scary-looking (but mostly
14814 harmless in practice) invalid-read bug. It also has a few small
14815 bugfixes, notably fixes for compilation and portability on different
14816 platforms. If no further significant bounds are found, the next
14817 release will the the official stable release.
14819 o Major bugfixes (security, correctness):
14820 - Fix an error that could cause us to read 4 bytes before the
14821 beginning of an openssl string. This bug could be used to cause
14822 Tor to crash on systems with unusual malloc implementations, or
14823 systems with unusual hardening installed. Fixes bug 17404; bugfix
14826 o Major bugfixes (correctness):
14827 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
14828 bug 17401; bugfix on 0.2.7.3-rc.
14830 o Major bugfixes (memory leaks):
14831 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
14832 17398; bugfix on 0.2.6.1-alpha.
14833 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
14834 17402; bugfix on 0.2.7.3-rc.
14835 - Fix a memory leak when reading an expired signing key from disk.
14836 Fixes bug 17403; bugfix on 0.2.7.2-rc.
14838 o Minor features (geoIP):
14839 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
14842 o Minor bugfixes (compilation):
14843 - Repair compilation with the most recent (unreleased, alpha)
14844 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
14845 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
14846 17251; bugfix on 0.2.7.2-alpha.
14847 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
14848 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
14850 o Minor bugfixes (portability):
14851 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
14852 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
14855 o Minor bugfixes (sandbox):
14856 - Add the "hidserv-stats" filename to our sandbox filter for the
14857 HiddenServiceStatistics option to work properly. Fixes bug 17354;
14858 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
14860 o Minor bugfixes (testing):
14861 - Add unit tests for get_interface_address* failure cases. Fixes bug
14862 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
14863 - Fix breakage when running 'make check' with BSD make. Fixes bug
14864 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
14865 - Make the get_ifaddrs_* unit tests more tolerant of different
14866 network configurations. (Don't assume every test box has an IPv4
14867 address, and don't assume every test box has a non-localhost
14868 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
14869 - Skip backtrace tests when backtrace support is not compiled in.
14870 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
14874 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
14875 - Note that HiddenServicePorts can take a unix domain socket. Closes
14879 Changes in version 0.2.7.3-rc - 2015-09-25
14880 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
14881 contains numerous usability fixes for Ed25519 keys, safeguards against
14882 several misconfiguration problems, significant simplifications to
14883 Tor's callgraph, and numerous bugfixes and small features.
14885 This is the most tested release of Tor to date. The unit tests cover
14886 39.40% of the code, and the integration tests (accessible with "make
14887 test-full-online", requiring stem and chutney and a network
14888 connection) raise the coverage to 64.49%.
14890 o Major features (security, hidden services):
14891 - Hidden services, if using the EntryNodes option, are required to
14892 use more than one EntryNode, in order to avoid a guard discovery
14893 attack. (This would only affect people who had configured hidden
14894 services and manually specified the EntryNodes option with a
14895 single entry-node. The impact was that it would be easy to
14896 remotely identify the guard node used by such a hidden service.
14897 See ticket for more information.) Fixes ticket 14917.
14899 o Major features (Ed25519 keys, keypinning):
14900 - The key-pinning option on directory authorities is now advisory-
14901 only by default. In a future version, or when the AuthDirPinKeys
14902 option is set, pins are enforced again. Disabling key-pinning
14903 seemed like a good idea so that we can survive the fallout of any
14904 usability problems associated with Ed25519 keys. Closes
14907 o Major features (Ed25519 performance):
14908 - Improve the speed of Ed25519 operations and Curve25519 keypair
14909 generation when built targeting 32 bit x86 platforms with SSE2
14910 available. Implements ticket 16535.
14911 - Improve the runtime speed of Ed25519 signature verification by
14912 using Ed25519-donna's batch verification support. Implements
14915 o Major features (performance testing):
14916 - The test-network.sh script now supports performance testing.
14917 Requires corresponding chutney performance testing changes. Patch
14918 by "teor". Closes ticket 14175.
14920 o Major features (relay, Ed25519):
14921 - Significant usability improvements for Ed25519 key management. Log
14922 messages are better, and the code can recover from far more
14923 failure conditions. Thanks to "s7r" for reporting and diagnosing
14925 - Add a new OfflineMasterKey option to tell Tor never to try loading
14926 or generating a secret Ed25519 identity key. You can use this in
14927 combination with tor --keygen to manage offline and/or encrypted
14928 Ed25519 keys. Implements ticket 16944.
14929 - Add a --newpass option to allow changing or removing the
14930 passphrase of an encrypted key with tor --keygen. Implements part
14932 - On receiving a HUP signal, check to see whether the Ed25519
14933 signing key has changed, and reload it if so. Closes ticket 16790.
14935 o Major bugfixes (relay, Ed25519):
14936 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
14937 0.2.7.2-alpha. Reported by "s7r".
14938 - Improve handling of expired signing keys with offline master keys.
14939 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
14941 o Minor features (client-side privacy):
14942 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
14943 lifespan when IsolateSOCKSAuth and streams with SOCKS
14944 authentication are attached to the circuit. This allows
14945 applications like TorBrowser to manage circuit lifetime on their
14946 own. Implements feature 15482.
14947 - When logging malformed hostnames from SOCKS5 requests, respect
14948 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
14950 o Minor features (compilation):
14951 - Give a warning as early as possible when trying to build with an
14952 unsupported OpenSSL version. Closes ticket 16901.
14953 - Fail during configure if we're trying to build against an OpenSSL
14954 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
14955 which started requiring ECC.
14957 o Minor features (geoip):
14958 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
14961 o Minor features (hidden services):
14962 - Relays need to have the Fast flag to get the HSDir flag. As this
14963 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
14964 drop. This change should make some attacks against the hidden
14965 service directory system harder. Fixes ticket 15963.
14966 - Turn on hidden service statistics collection by setting the torrc
14967 option HiddenServiceStatistics to "1" by default. (This keeps
14968 track only of the fraction of traffic used by hidden services, and
14969 the total number of hidden services in existence.) Closes
14971 - Client now uses an introduction point failure cache to know when
14972 to fetch or keep a descriptor in their cache. Previously, failures
14973 were recorded implicitly, but not explicitly remembered. Closes
14976 o Minor features (testing, authorities, documentation):
14977 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
14978 explicitly manage consensus flags in testing networks. Patch by
14979 "robgjansen", modified by "teor". Implements part of ticket 14882.
14981 o Minor bugfixes (security, exit policies):
14982 - ExitPolicyRejectPrivate now also rejects the relay's published
14983 IPv6 address (if any), and any publicly routable IPv4 or IPv6
14984 addresses on any local interfaces. ticket 17027. Patch by "teor".
14985 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
14987 o Minor bug fixes (torrc exit policies):
14988 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
14989 produce IPv6 wildcard addresses. Previously they would produce
14990 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
14991 of bug 16069; bugfix on 0.2.4.7-alpha.
14992 - When parsing torrc ExitPolicies, we now warn for a number of cases
14993 where the user's intent is likely to differ from Tor's actual
14994 behavior. These include: using an IPv4 address with an accept6 or
14995 reject6 line; using "private" on an accept6 or reject6 line; and
14996 including any ExitPolicy lines after accept *:* or reject *:*.
14997 Related to ticket 16069.
14998 - When parsing torrc ExitPolicies, we now issue an info-level
14999 message when expanding an "accept/reject *" line to include both
15000 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
15001 - In each instance above, usage advice is provided to avoid the
15002 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
15003 16069; bugfix on 0.2.4.7-alpha.
15005 o Minor bugfixes (authority):
15006 - Don't assign "HSDir" to a router if it isn't Valid and Running.
15007 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
15008 - Downgrade log messages about Ed25519 key issues if they are in old
15009 cached router descriptors. Fixes part of bug 16286; bugfix
15011 - When we find an Ed25519 key issue in a cached descriptor, stop
15012 saying the descriptor was just "uploaded". Fixes another part of
15013 bug 16286; bugfix on 0.2.7.2-alpha.
15015 o Minor bugfixes (control port):
15016 - Repair a warning and a spurious result when getting the maximum
15017 number of file descriptors from the controller. Fixes bug 16697;
15018 bugfix on 0.2.7.2-alpha.
15020 o Minor bugfixes (correctness):
15021 - When calling channel_free_list(), avoid calling smartlist_remove()
15022 while inside a FOREACH loop. This partially reverts commit
15023 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
15024 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
15026 o Minor bugfixes (documentation):
15027 - Advise users on how to configure separate IPv4 and IPv6 exit
15028 policies in the manpage and sample torrcs. Related to ticket 16069.
15029 - Fix the usage message of tor-resolve(1) so that it no longer lists
15030 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
15031 - Fix an error in the manual page and comments for
15032 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
15033 required "ORPort connectivity". While this is true, it is in no
15034 way unique to the HSDir flag. Of all the flags, only HSDirs need a
15035 DirPort configured in order for the authorities to assign that
15036 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
15039 o Minor bugfixes (Ed25519):
15040 - Fix a memory leak when reading router descriptors with expired
15041 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
15043 o Minor bugfixes (linux seccomp2 sandbox):
15044 - Allow bridge authorities to run correctly under the seccomp2
15045 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
15046 - Allow routers with ed25519 keys to run correctly under the
15047 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
15049 o Minor bugfixes (open file limit):
15050 - Fix set_max_file_descriptors() to set by default the max open file
15051 limit to the current limit when setrlimit() fails. Fixes bug
15052 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
15054 o Minor bugfixes (portability):
15055 - Try harder to normalize the exit status of the Tor process to the
15056 standard-provided range. Fixes bug 16975; bugfix on every version
15058 - Check correctly for Windows socket errors in the workqueue
15059 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
15060 - Fix the behavior of crypto_rand_time_range() when told to consider
15061 times before 1970. (These times were possible when running in a
15062 simulated network environment where time()'s output starts at
15063 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
15064 - Restore correct operation of TLS client-cipher detection on
15065 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
15067 o Minor bugfixes (relay):
15068 - Ensure that worker threads actually exit when a fatal error or
15069 shutdown is indicated. This fix doesn't currently affect the
15070 behavior of Tor, because Tor workers never indicates fatal error
15071 or shutdown except in the unit tests. Fixes bug 16868; bugfix
15073 - Unblock threads before releasing the work queue mutex to ensure
15074 predictable scheduling behavior. Fixes bug 16644; bugfix
15077 o Code simplification and refactoring:
15078 - Change the function that's called when we need to retry all
15079 downloads so that it only reschedules the downloads to happen
15080 immediately, rather than launching them all at once itself. This
15081 further simplifies Tor's callgraph.
15082 - Move some format-parsing functions out of crypto.c and
15083 crypto_curve25519.c into crypto_format.c and/or util_format.c.
15084 - Move the client-only parts of init_keys() into a separate
15085 function. Closes ticket 16763.
15086 - Simplify the microdesc_free() implementation so that it no longer
15087 appears (to code analysis tools) to potentially invoke a huge
15088 suite of other microdesc functions.
15089 - Simply the control graph further by deferring the inner body of
15090 directory_all_unreachable() into a callback. Closes ticket 16762.
15091 - Treat the loss of an owning controller as equivalent to a SIGTERM
15092 signal. This removes a tiny amount of duplicated code, and
15093 simplifies our callgraph. Closes ticket 16788.
15094 - When generating an event to send to the controller, we no longer
15095 put the event over the network immediately. Instead, we queue
15096 these events, and use a Libevent callback to deliver them. This
15097 change simplifies Tor's callgraph by reducing the number of
15098 functions from which all other Tor functions are reachable. Closes
15100 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
15101 that try to scan or compile every file on Unix won't decide that
15103 - Remove the unused "nulterminate" argument from buf_pullup().
15106 - Recommend a 40 GB example AccountingMax in torrc.sample rather
15107 than a 4 GB max. Closes ticket 16742.
15108 - Include the TUNING document in our source tarball. It is referred
15109 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
15113 - The internal pure-C tor-fw-helper tool is now removed from the Tor
15114 distribution, in favor of the pure-Go clone available from
15115 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
15116 used by the C tor-fw-helper are not, in our opinion, very
15117 confidence- inspiring in their secure-programming techniques.
15118 Closes ticket 13338.
15119 - Remove the code that would try to aggressively flush controller
15120 connections while writing to them. This code was introduced in
15121 0.1.2.7-alpha, in order to keep output buffers from exceeding
15122 their limits. But there is no longer a maximum output buffer size,
15123 and flushing data in this way caused some undesirable recursions
15124 in our call graph. Closes ticket 16480.
15127 - Make "bridges+hs" the default test network. This tests almost all
15128 tor functionality during make test-network, while allowing tests
15129 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
15130 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
15131 (chutney). Patches by "teor".
15132 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
15133 by-side in the same parent directory. Closes ticket 16903. Patch
15135 - Use environment variables rather than autoconf substitutions to
15136 send variables from the build system to the test scripts. This
15137 change should be easier to maintain, and cause 'make distcheck' to
15138 work better than before. Fixes bug 17148.
15139 - Add a new set of callgraph analysis scripts that use clang to
15140 produce a list of which Tor functions are reachable from which
15141 other Tor functions. We're planning to use these to help simplify
15142 our code structure by identifying illogical dependencies.
15143 - Add new 'test-full' and 'test-full-online' targets to run all
15144 tests, including integration tests with stem and chutney.
15145 - Make the test-workqueue test work on Windows by initializing the
15146 network before we begin.
15147 - New make target (make test-network-all) to run multiple applicable
15148 chutney test cases. Patch from Teor; closes 16953.
15149 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
15150 functions in dns.c. Implements a portion of ticket 16831.
15151 - When building Tor with testing coverage enabled, run Chutney tests
15152 (if any) using the 'tor-cov' coverage binary.
15153 - When running test-network or test-stem, check for the absence of
15154 stem/chutney before doing any build operations.
15157 Changes in version 0.2.7.2-alpha - 2015-07-27
15158 This, the second alpha in the Tor 0.2.7 series, has a number of new
15159 features, including a way to manually pick the number of introduction
15160 points for hidden services, and the much stronger Ed25519 signing key
15161 algorithm for regular Tor relays (including support for encrypted
15162 offline identity keys in the new algorithm).
15164 Support for Ed25519 on relays is currently limited to signing router
15165 descriptors; later alphas in this series will extend Ed25519 key
15166 support to more parts of the Tor protocol.
15168 o Major features (Ed25519 identity keys, Proposal 220):
15169 - All relays now maintain a stronger identity key, using the Ed25519
15170 elliptic curve signature format. This master key is designed so
15171 that it can be kept offline. Relays also generate an online
15172 signing key, and a set of other Ed25519 keys and certificates.
15173 These are all automatically regenerated and rotated as needed.
15174 Implements part of ticket 12498.
15175 - Directory authorities now vote on Ed25519 identity keys along with
15176 RSA1024 keys. Implements part of ticket 12498.
15177 - Directory authorities track which Ed25519 identity keys have been
15178 used with which RSA1024 identity keys, and do not allow them to
15179 vary freely. Implements part of ticket 12498.
15180 - Microdescriptors now include Ed25519 identity keys. Implements
15181 part of ticket 12498.
15182 - Add support for offline encrypted Ed25519 master keys. To use this
15183 feature on your tor relay, run "tor --keygen" to make a new master
15184 key (or to make a new signing key if you already have a master
15185 key). Closes ticket 13642.
15187 o Major features (Hidden services):
15188 - Add the torrc option HiddenServiceNumIntroductionPoints, to
15189 specify a fixed number of introduction points. Its maximum value
15190 is 10 and default is 3. Using this option can increase a hidden
15191 service's reliability under load, at the cost of making it more
15192 visible that the hidden service is facing extra load. Closes
15194 - Remove the adaptive algorithm for choosing the number of
15195 introduction points, which used to change the number of
15196 introduction points (poorly) depending on the number of
15197 connections the HS sees. Closes ticket 4862.
15199 o Major features (onion key cross-certification):
15200 - Relay descriptors now include signatures of their own identity
15201 keys, made using the TAP and ntor onion keys. These signatures
15202 allow relays to prove ownership of their own onion keys. Because
15203 of this change, microdescriptors will no longer need to include
15204 RSA identity keys. Implements proposal 228; closes ticket 12499.
15206 o Major features (performance):
15207 - Improve the runtime speed of Ed25519 operations by using the
15208 public-domain Ed25519-donna by Andrew M. ("floodyberry").
15209 Implements ticket 16467.
15210 - Improve the runtime speed of the ntor handshake by using an
15211 optimized curve25519 basepoint scalarmult implementation from the
15212 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
15213 ideas by Adam Langley. Implements ticket 9663.
15215 o Major bugfixes (client-side privacy, also in 0.2.6.9):
15216 - Properly separate out each SOCKSPort when applying stream
15217 isolation. The error occurred because each port's session group
15218 was being overwritten by a default value when the listener
15219 connection was initialized. Fixes bug 16247; bugfix on
15220 0.2.6.3-alpha. Patch by "jojelino".
15222 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
15223 - Stop refusing to store updated hidden service descriptors on a
15224 client. This reverts commit 9407040c59218 (which indeed fixed bug
15225 14219, but introduced a major hidden service reachability
15226 regression detailed in bug 16381). This is a temporary fix since
15227 we can live with the minor issue in bug 14219 (it just results in
15228 some load on the network) but the regression of 16381 is too much
15229 of a setback. First-round fix for bug 16381; bugfix
15232 o Major bugfixes (hidden services):
15233 - When cannibalizing a circuit for an introduction point, always
15234 extend to the chosen exit node (creating a 4 hop circuit).
15235 Previously Tor would use the current circuit exit node, which
15236 changed the original choice of introduction point, and could cause
15237 the hidden service to skip excluded introduction points or
15238 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
15241 o Major bugfixes (open file limit):
15242 - The open file limit wasn't checked before calling
15243 tor_accept_socket_nonblocking(), which would make Tor exceed the
15244 limit. Now, before opening a new socket, Tor validates the open
15245 file limit just before, and if the max has been reached, return an
15246 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
15248 o Major bugfixes (stability, also in 0.2.6.10):
15249 - Stop crashing with an assertion failure when parsing certain kinds
15250 of malformed or truncated microdescriptors. Fixes bug 16400;
15251 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
15252 by "cypherpunks_backup".
15253 - Stop random client-side assertion failures that could occur when
15254 connecting to a busy hidden service, or connecting to a hidden
15255 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
15258 o Minor features (directory authorities, security, also in 0.2.6.9):
15259 - The HSDir flag given by authorities now requires the Stable flag.
15260 For the current network, this results in going from 2887 to 2806
15261 HSDirs. Also, it makes it harder for an attacker to launch a sybil
15262 attack by raising the effort for a relay to become Stable to
15263 require at the very least 7 days, while maintaining the 96 hours
15264 uptime requirement for HSDir. Implements ticket 8243.
15266 o Minor features (client):
15267 - Relax the validation of hostnames in SOCKS5 requests, allowing the
15268 character '_' to appear, in order to cope with domains observed in
15269 the wild that are serving non-RFC compliant records. Resolves
15271 - Relax the validation done to hostnames in SOCKS5 requests, and
15272 allow a single trailing '.' to cope with clients that pass FQDNs
15273 using that syntax to explicitly indicate that the domain name is
15274 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
15275 - Add GroupWritable and WorldWritable options to unix-socket based
15276 SocksPort and ControlPort options. These options apply to a single
15277 socket, and override {Control,Socks}SocketsGroupWritable. Closes
15280 o Minor features (control protocol):
15281 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
15282 the control protocol. Resolves ticket 15358.
15284 o Minor features (directory authorities):
15285 - Directory authorities no longer vote against the "Fast", "Stable",
15286 and "HSDir" flags just because they were going to vote against
15287 "Running": if the consensus turns out to be that the router was
15288 running, then the authority's vote should count. Patch from Peter
15289 Retzlaff; closes issue 8712.
15291 o Minor features (geoip, also in 0.2.6.10):
15292 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
15293 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
15295 o Minor features (hidden services):
15296 - Add the new options "HiddenServiceMaxStreams" and
15297 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
15298 limit the maximum number of simultaneous streams per circuit, and
15299 optionally tear down the circuit when the limit is exceeded. Part
15302 o Minor features (portability):
15303 - Use C99 variadic macros when the compiler is not GCC. This avoids
15304 failing compilations on MSVC, and fixes a log-file-based race
15305 condition in our old workarounds. Original patch from Gisle Vanem.
15307 o Minor bugfixes (compilation, also in 0.2.6.9):
15308 - Build with --enable-systemd correctly when libsystemd is
15309 installed, but systemd is not. Fixes bug 16164; bugfix on
15310 0.2.6.3-alpha. Patch from Peter Palfrader.
15312 o Minor bugfixes (controller):
15313 - Add the descriptor ID in each HS_DESC control event. It was
15314 missing, but specified in control-spec.txt. Fixes bug 15881;
15315 bugfix on 0.2.5.2-alpha.
15317 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
15318 - Check for failures from crypto_early_init, and refuse to continue.
15319 A previous typo meant that we could keep going with an
15320 uninitialized crypto library, and would have OpenSSL initialize
15321 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
15322 when implementing ticket 4900. Patch by "teor".
15324 o Minor bugfixes (hidden services):
15325 - Fix a crash when reloading configuration while at least one
15326 configured and one ephemeral hidden service exists. Fixes bug
15327 16060; bugfix on 0.2.7.1-alpha.
15328 - Avoid crashing with a double-free bug when we create an ephemeral
15329 hidden service but adding it fails for some reason. Fixes bug
15330 16228; bugfix on 0.2.7.1-alpha.
15332 o Minor bugfixes (Linux seccomp2 sandbox):
15333 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
15334 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
15336 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
15337 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
15338 these when eventfd2() support is missing. Fixes bug 16363; bugfix
15339 on 0.2.6.3-alpha. Patch from "teor".
15341 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
15342 - Fix sandboxing to work when running as a relay, by allowing the
15343 renaming of secret_id_key, and allowing the eventfd2 and futex
15344 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
15346 - Allow systemd connections to work with the Linux seccomp2 sandbox
15347 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
15350 o Minor bugfixes (relay):
15351 - Fix a rarely-encountered memory leak when failing to initialize
15352 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
15353 from "cypherpunks".
15355 o Minor bugfixes (systemd):
15356 - Fix an accidental formatting error that broke the systemd
15357 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
15358 - Tor's systemd unit file no longer contains extraneous spaces.
15359 These spaces would sometimes confuse tools like deb-systemd-
15360 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
15362 o Minor bugfixes (tests):
15363 - Use the configured Python executable when running test-stem-full.
15364 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
15366 o Minor bugfixes (tests, also in 0.2.6.9):
15367 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
15368 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
15370 o Minor bugfixes (threads, comments):
15371 - Always initialize return value in compute_desc_id in rendcommon.c
15372 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
15373 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
15374 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
15375 - Remove undefined directive-in-macro in test_util_writepid clang
15376 3.7 complains that using a preprocessor directive inside a macro
15377 invocation in test_util_writepid in test_util.c is undefined.
15378 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
15380 o Code simplification and refactoring:
15381 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
15382 to ensure they remain consistent and visible everywhere.
15383 - Remove some vestigial workarounds for the MSVC6 compiler. We
15384 haven't supported that in ages.
15385 - The link authentication code has been refactored for better
15386 testability and reliability. It now uses code generated with the
15387 "trunnel" binary encoding generator, to reduce the risk of bugs
15388 due to programmer error. Done as part of ticket 12498.
15391 - Include a specific and (hopefully) accurate documentation of the
15392 torrc file's meta-format in doc/torrc_format.txt. This is mainly
15393 of interest to people writing programs to parse or generate torrc
15394 files. This document is not a commitment to long-term
15395 compatibility; some aspects of the current format are a bit
15396 ridiculous. Closes ticket 2325.
15398 o Removed features:
15399 - Tor no longer supports copies of OpenSSL that are missing support
15400 for Elliptic Curve Cryptography. (We began using ECC when
15401 available in 0.2.4.8-alpha, for more safe and efficient key
15402 negotiation.) In particular, support for at least one of P256 or
15403 P224 is now required, with manual configuration needed if only
15404 P224 is available. Resolves ticket 16140.
15405 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
15406 on an operating system that has not upgraded to OpenSSL 1.0 or
15407 later, and you compile Tor from source, you will need to install a
15408 more recent OpenSSL to link Tor against.) These versions of
15409 OpenSSL are still supported by the OpenSSL, but the numerous
15410 cryptographic improvements in later OpenSSL releases makes them a
15411 clear choice. Resolves ticket 16034.
15412 - Remove the HidServDirectoryV2 option. Now all relays offer to
15413 store hidden service descriptors. Related to 16543.
15414 - Remove the VoteOnHidServDirectoriesV2 option, since all
15415 authorities have long set it to 1. Closes ticket 16543.
15418 - Document use of coverity, clang static analyzer, and clang dynamic
15419 undefined behavior and address sanitizers in doc/HACKING. Include
15420 detailed usage instructions in the blacklist. Patch by "teor".
15421 Closes ticket 15817.
15422 - The link authentication protocol code now has extensive tests.
15423 - The relay descriptor signature testing code now has
15425 - The test_workqueue program now runs faster, and is enabled by
15426 default as a part of "make check".
15427 - Now that OpenSSL has its own scrypt implementation, add an unit
15428 test that checks for interoperability between libscrypt_scrypt()
15429 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
15430 and rely on EVP_PBE_scrypt() whenever possible. Resolves
15434 Changes in version 0.2.6.10 - 2015-07-12
15435 Tor version 0.2.6.10 fixes some significant stability and hidden
15436 service client bugs, bulletproofs the cryptography init process, and
15437 fixes a bug when using the sandbox code with some older versions of
15438 Linux. Everyone running an older version, especially an older version
15439 of 0.2.6, should upgrade.
15441 o Major bugfixes (hidden service clients, stability):
15442 - Stop refusing to store updated hidden service descriptors on a
15443 client. This reverts commit 9407040c59218 (which indeed fixed bug
15444 14219, but introduced a major hidden service reachability
15445 regression detailed in bug 16381). This is a temporary fix since
15446 we can live with the minor issue in bug 14219 (it just results in
15447 some load on the network) but the regression of 16381 is too much
15448 of a setback. First-round fix for bug 16381; bugfix
15451 o Major bugfixes (stability):
15452 - Stop crashing with an assertion failure when parsing certain kinds
15453 of malformed or truncated microdescriptors. Fixes bug 16400;
15454 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
15455 by "cypherpunks_backup".
15456 - Stop random client-side assertion failures that could occur when
15457 connecting to a busy hidden service, or connecting to a hidden
15458 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
15461 o Minor features (geoip):
15462 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
15463 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
15465 o Minor bugfixes (crypto error-handling):
15466 - Check for failures from crypto_early_init, and refuse to continue.
15467 A previous typo meant that we could keep going with an
15468 uninitialized crypto library, and would have OpenSSL initialize
15469 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
15470 when implementing ticket 4900. Patch by "teor".
15472 o Minor bugfixes (Linux seccomp2 sandbox):
15473 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
15474 these when eventfd2() support is missing. Fixes bug 16363; bugfix
15475 on 0.2.6.3-alpha. Patch from "teor".
15478 Changes in version 0.2.6.9 - 2015-06-11
15479 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
15480 requirements for receiving an HSDir flag, and addresses some other small
15481 bugs in the systemd and sandbox code. Clients using circuit isolation
15482 should upgrade; all directory authorities should upgrade.
15484 o Major bugfixes (client-side privacy):
15485 - Properly separate out each SOCKSPort when applying stream
15486 isolation. The error occurred because each port's session group was
15487 being overwritten by a default value when the listener connection
15488 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
15491 o Minor feature (directory authorities, security):
15492 - The HSDir flag given by authorities now requires the Stable flag.
15493 For the current network, this results in going from 2887 to 2806
15494 HSDirs. Also, it makes it harder for an attacker to launch a sybil
15495 attack by raising the effort for a relay to become Stable which
15496 takes at the very least 7 days to do so and by keeping the 96
15497 hours uptime requirement for HSDir. Implements ticket 8243.
15499 o Minor bugfixes (compilation):
15500 - Build with --enable-systemd correctly when libsystemd is
15501 installed, but systemd is not. Fixes bug 16164; bugfix on
15502 0.2.6.3-alpha. Patch from Peter Palfrader.
15504 o Minor bugfixes (Linux seccomp2 sandbox):
15505 - Fix sandboxing to work when running as a relaymby renaming of
15506 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
15507 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
15508 - Allow systemd connections to work with the Linux seccomp2 sandbox
15509 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
15512 o Minor bugfixes (tests):
15513 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
15514 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
15517 Changes in version 0.2.6.8 - 2015-05-21
15518 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
15519 fixes an authority-side bug in assigning the HSDir flag. All directory
15520 authorities should upgrade.
15522 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
15523 - Revert commit that made directory authorities assign the HSDir
15524 flag to relays without a DirPort; this was bad because such relays
15525 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
15528 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
15529 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
15530 a client authorized hidden service. Fixes bug 15823; bugfix
15533 o Minor features (geoip):
15534 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
15535 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
15539 Changes in version 0.2.7.1-alpha - 2015-05-12
15540 Tor 0.2.7.1-alpha is the first alpha release in its series. It
15541 includes numerous small features and bugfixes against previous Tor
15542 versions, and numerous small infrastructure improvements. The most
15543 notable features are several new ways for controllers to interact with
15544 the hidden services subsystem.
15546 o New system requirements:
15547 - Tor no longer includes workarounds to support Libevent versions
15548 before 1.3e. Libevent 2.0 or later is recommended. Closes
15551 o Major features (controller):
15552 - Add the ADD_ONION and DEL_ONION commands that allow the creation
15553 and management of hidden services via the controller. Closes
15555 - New "GETINFO onions/current" and "GETINFO onions/detached"
15556 commands to get information about hidden services created via the
15557 controller. Part of ticket 6411.
15558 - New HSFETCH command to launch a request for a hidden service
15559 descriptor. Closes ticket 14847.
15560 - New HSPOST command to upload a hidden service descriptor. Closes
15561 ticket 3523. Patch by "DonnchaC".
15563 o Major bugfixes (hidden services):
15564 - Revert commit that made directory authorities assign the HSDir
15565 flag to relays without a DirPort; this was bad because such relays
15566 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
15569 o Minor features (clock-jump tolerance):
15570 - Recover better when our clock jumps back many hours, like might
15571 happen for Tails or Whonix users who start with a very wrong
15572 hardware clock, use Tor to discover a more accurate time, and then
15573 fix their clock. Resolves part of ticket 8766.
15575 o Minor features (command-line interface):
15576 - Make --hash-password imply --hush to prevent unnecessary noise.
15577 Closes ticket 15542. Patch from "cypherpunks".
15578 - Print a warning whenever we find a relative file path being used
15579 as torrc option. Resolves issue 14018.
15581 o Minor features (controller):
15582 - Add DirAuthority lines for default directory authorities to the
15583 output of the "GETINFO config/defaults" command if not already
15584 present. Implements ticket 14840.
15585 - Controllers can now use "GETINFO hs/client/desc/id/..." to
15586 retrieve items from the client's hidden service descriptor cache.
15587 Closes ticket 14845.
15588 - Implement a new controller command "GETINFO status/fresh-relay-
15589 descs" to fetch a descriptor/extrainfo pair that was generated on
15590 demand just for the controller's use. Implements ticket 14784.
15592 o Minor features (DoS-resistance):
15593 - Make it harder for attackers to overload hidden services with
15594 introductions, by blocking multiple introduction requests on the
15595 same circuit. Resolves ticket 15515.
15597 o Minor features (geoip):
15598 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
15599 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
15602 o Minor features (HS popularity countermeasure):
15603 - To avoid leaking HS popularity, don't cycle the introduction point
15604 when we've handled a fixed number of INTRODUCE2 cells but instead
15605 cycle it when a random number of introductions is reached, thus
15606 making it more difficult for an attacker to find out the amount of
15607 clients that have used the introduction point for a specific HS.
15608 Closes ticket 15745.
15610 o Minor features (logging):
15611 - Include the Tor version in all LD_BUG log messages, since people
15612 tend to cut and paste those into the bugtracker. Implements
15615 o Minor features (pluggable transports):
15616 - When launching managed pluggable transports on Linux systems,
15617 attempt to have the kernel deliver a SIGTERM on tor exit if the
15618 pluggable transport process is still running. Resolves
15620 - When launching managed pluggable transports, setup a valid open
15621 stdin in the child process that can be used to detect if tor has
15622 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
15623 can be used by implementations to detect this new behavior.
15624 Resolves ticket 15435.
15626 o Minor features (testing):
15627 - Add a test to verify that the compiler does not eliminate our
15628 memwipe() implementation. Closes ticket 15377.
15629 - Add make rule `check-changes` to verify the format of changes
15630 files. Closes ticket 15180.
15631 - Add unit tests for control_event_is_interesting(). Add a compile-
15632 time check that the number of events doesn't exceed the capacity
15633 of control_event_t.event_mask. Closes ticket 15431, checks for
15634 bugs similar to 13085. Patch by "teor".
15635 - Command-line argument tests moved to Stem. Resolves ticket 14806.
15636 - Integrate the ntor, backtrace, and zero-length keys tests into the
15637 automake test suite. Closes ticket 15344.
15638 - Remove assertions during builds to determine Tor's test coverage.
15639 We don't want to trigger these even in assertions, so including
15640 them artificially makes our branch coverage look worse than it is.
15641 This patch provides the new test-stem-full and coverage-html-full
15642 configure options. Implements ticket 15400.
15644 o Minor bugfixes (build):
15645 - Improve out-of-tree builds by making non-standard rules work and
15646 clean up additional files and directories. Fixes bug 15053; bugfix
15649 o Minor bugfixes (command-line interface):
15650 - When "--quiet" is provided along with "--validate-config", do not
15651 write anything to stdout on success. Fixes bug 14994; bugfix
15653 - When complaining about bad arguments to "--dump-config", use
15654 stderr, not stdout.
15656 o Minor bugfixes (configuration, unit tests):
15657 - Only add the default fallback directories when the DirAuthorities,
15658 AlternateDirAuthority, and FallbackDir directory config options
15659 are set to their defaults. The default fallback directory list is
15660 currently empty, this fix will only change tor's behavior when it
15661 has default fallback directories. Includes unit tests for
15662 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
15663 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
15665 o Minor bugfixes (correctness):
15666 - For correctness, avoid modifying a constant string in
15667 handle_control_postdescriptor. Fixes bug 15546; bugfix
15669 - Remove side-effects from tor_assert() calls. This was harmless,
15670 because we never disable assertions, but it is bad style and
15671 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
15674 o Minor bugfixes (hidden service):
15675 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
15676 a client authorized hidden service. Fixes bug 15823; bugfix
15678 - Remove an extraneous newline character from the end of hidden
15679 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
15681 o Minor bugfixes (interface):
15682 - Print usage information for --dump-config when it is used without
15683 an argument. Also, fix the error message to use different wording
15684 and add newline at the end. Fixes bug 15541; bugfix
15687 o Minor bugfixes (logs):
15688 - When building Tor under Clang, do not include an extra set of
15689 parentheses in log messages that include function names. Fixes bug
15690 15269; bugfix on every released version of Tor when compiled with
15691 recent enough Clang.
15693 o Minor bugfixes (network):
15694 - When attempting to use fallback technique for network interface
15695 lookup, disregard loopback and multicast addresses since they are
15696 unsuitable for public communications.
15698 o Minor bugfixes (statistics):
15699 - Disregard the ConnDirectionStatistics torrc options when Tor is
15700 not a relay since in that mode of operation no sensible data is
15701 being collected and because Tor might run into measurement hiccups
15702 when running as a client for some time, then becoming a relay.
15703 Fixes bug 15604; bugfix on 0.2.2.35.
15705 o Minor bugfixes (test networks):
15706 - When self-testing reachability, use ExtendAllowPrivateAddresses to
15707 determine if local/private addresses imply reachability. The
15708 previous fix used TestingTorNetwork, which implies
15709 ExtendAllowPrivateAddresses, but this excluded rare configurations
15710 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
15711 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
15712 issue discovered by CJ Ess.
15714 o Minor bugfixes (testing):
15715 - Check for matching value in server response in ntor_ref.py. Fixes
15716 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
15718 - Set the severity correctly when testing
15719 get_interface_addresses_ifaddrs() and
15720 get_interface_addresses_win32(), so that the tests fail gracefully
15721 instead of triggering an assertion. Fixes bug 15759; bugfix on
15722 0.2.6.3-alpha. Reported by Nicolas Derive.
15724 o Code simplification and refactoring:
15725 - Move the hacky fallback code out of get_interface_address6() into
15726 separate function and get it covered with unit-tests. Resolves
15728 - Refactor hidden service client-side cache lookup to intelligently
15729 report its various failure cases, and disentangle failure cases
15730 involving a lack of introduction points. Closes ticket 14391.
15731 - Use our own Base64 encoder instead of OpenSSL's, to allow more
15732 control over the output. Part of ticket 15652.
15735 - Improve the descriptions of statistics-related torrc options in
15736 the manpage to describe rationale and possible uses cases. Fixes
15738 - Improve the layout and formatting of ./configure --help messages.
15739 Closes ticket 15024. Patch from "cypherpunks".
15740 - Standardize on the term "server descriptor" in the manual page.
15741 Previously, we had used "router descriptor", "server descriptor",
15742 and "relay descriptor" interchangeably. Part of ticket 14987.
15745 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
15746 and always use the internal Base64 decoder. The internal decoder
15747 has been part of tor since 0.2.0.10-alpha, and no one should
15748 be using the OpenSSL one. Part of ticket 15652.
15749 - Remove the 'tor_strclear()' function; use memwipe() instead.
15750 Closes ticket 14922.
15752 o Removed features:
15753 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
15754 fingerprinting we now recommend pluggable transports; for forward-
15755 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
15756 - Remove the undocumented "--digests" command-line option. It
15757 complicated our build process, caused subtle build issues on
15758 multiple platforms, and is now redundant since we started
15759 including git version identifiers. Closes ticket 14742.
15760 - Tor no longer contains checks for ancient directory cache versions
15761 that didn't know about microdescriptors.
15762 - Tor no longer contains workarounds for stat files generated by
15763 super-old versions of Tor that didn't choose guards sensibly.
15766 Changes in version 0.2.4.27 - 2015-04-06
15767 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
15768 could be used by an attacker to crash hidden services, or crash clients
15769 visiting hidden services. Hidden services should upgrade as soon as
15770 possible; clients should upgrade whenever packages become available.
15772 This release also backports a simple improvement to make hidden
15773 services a bit less vulnerable to denial-of-service attacks.
15775 o Major bugfixes (security, hidden service):
15776 - Fix an issue that would allow a malicious client to trigger an
15777 assertion failure and halt a hidden service. Fixes bug 15600;
15778 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
15779 - Fix a bug that could cause a client to crash with an assertion
15780 failure when parsing a malformed hidden service descriptor. Fixes
15781 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
15783 o Minor features (DoS-resistance, hidden service):
15784 - Introduction points no longer allow multiple INTRODUCE1 cells to
15785 arrive on the same circuit. This should make it more expensive for
15786 attackers to overwhelm hidden services with introductions.
15787 Resolves ticket 15515.
15790 Changes in version 0.2.5.12 - 2015-04-06
15791 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
15792 could be used by an attacker to crash hidden services, or crash clients
15793 visiting hidden services. Hidden services should upgrade as soon as
15794 possible; clients should upgrade whenever packages become available.
15796 This release also backports a simple improvement to make hidden
15797 services a bit less vulnerable to denial-of-service attacks.
15799 o Major bugfixes (security, hidden service):
15800 - Fix an issue that would allow a malicious client to trigger an
15801 assertion failure and halt a hidden service. Fixes bug 15600;
15802 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
15803 - Fix a bug that could cause a client to crash with an assertion
15804 failure when parsing a malformed hidden service descriptor. Fixes
15805 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
15807 o Minor features (DoS-resistance, hidden service):
15808 - Introduction points no longer allow multiple INTRODUCE1 cells to
15809 arrive on the same circuit. This should make it more expensive for
15810 attackers to overwhelm hidden services with introductions.
15811 Resolves ticket 15515.
15814 Changes in version 0.2.6.7 - 2015-04-06
15815 Tor 0.2.6.7 fixes two security issues that could be used by an
15816 attacker to crash hidden services, or crash clients visiting hidden
15817 services. Hidden services should upgrade as soon as possible; clients
15818 should upgrade whenever packages become available.
15820 This release also contains two simple improvements to make hidden
15821 services a bit less vulnerable to denial-of-service attacks.
15823 o Major bugfixes (security, hidden service):
15824 - Fix an issue that would allow a malicious client to trigger an
15825 assertion failure and halt a hidden service. Fixes bug 15600;
15826 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
15827 - Fix a bug that could cause a client to crash with an assertion
15828 failure when parsing a malformed hidden service descriptor. Fixes
15829 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
15831 o Minor features (DoS-resistance, hidden service):
15832 - Introduction points no longer allow multiple INTRODUCE1 cells to
15833 arrive on the same circuit. This should make it more expensive for
15834 attackers to overwhelm hidden services with introductions.
15835 Resolves ticket 15515.
15836 - Decrease the amount of reattempts that a hidden service performs
15837 when its rendezvous circuits fail. This reduces the computational
15838 cost for running a hidden service under heavy load. Resolves
15842 Changes in version 0.2.6.6 - 2015-03-24
15843 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
15845 It adds numerous safety, security, correctness, and performance
15846 improvements. Client programs can be configured to use more kinds of
15847 sockets, AutomapHosts works better, the multithreading backend is
15848 improved, cell transmission is refactored, test coverage is much
15849 higher, more denial-of-service attacks are handled, guard selection is
15850 improved to handle long-term guards better, pluggable transports
15851 should work a bit better, and some annoying hidden service performance
15852 bugs should be addressed.
15854 o Minor bugfixes (portability):
15855 - Use the correct datatype in the SipHash-2-4 function to prevent
15856 compilers from assuming any sort of alignment. Fixes bug 15436;
15857 bugfix on 0.2.5.3-alpha.
15859 Changes in version 0.2.6.5-rc - 2015-03-18
15860 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
15861 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
15863 o Major bugfixes (client):
15864 - Avoid crashing when making certain configuration option changes on
15865 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
15868 o Major bugfixes (pluggable transports):
15869 - Initialize the extended OR Port authentication cookie before
15870 launching pluggable transports. This prevents a race condition
15871 that occurred when server-side pluggable transports would cache the
15872 authentication cookie before it has been (re)generated. Fixes bug
15873 15240; bugfix on 0.2.5.1-alpha.
15875 o Major bugfixes (portability):
15876 - Do not crash on startup when running on Solaris. Fixes a bug
15877 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
15880 o Minor features (heartbeat):
15881 - On relays, report how many connections we negotiated using each
15882 version of the Tor link protocols. This information will let us
15883 know if removing support for very old versions of the Tor
15884 protocols is harming the network. Closes ticket 15212.
15886 o Code simplification and refactoring:
15887 - Refactor main loop to extract the 'loop' part. This makes it
15888 easier to run Tor under Shadow. Closes ticket 15176.
15891 Changes in version 0.2.5.11 - 2015-03-17
15892 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
15894 It backports several bugfixes from the 0.2.6 branch, including a
15895 couple of medium-level security fixes for relays and exit nodes.
15896 It also updates the list of directory authorities.
15898 o Directory authority changes:
15899 - Remove turtles as a directory authority.
15900 - Add longclaw as a new (v3) directory authority. This implements
15901 ticket 13296. This keeps the directory authority count at 9.
15902 - The directory authority Faravahar has a new IP address. This
15903 closes ticket 14487.
15905 o Major bugfixes (crash, OSX, security):
15906 - Fix a remote denial-of-service opportunity caused by a bug in
15907 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
15910 o Major bugfixes (relay, stability, possible security):
15911 - Fix a bug that could lead to a relay crashing with an assertion
15912 failure if a buffer of exactly the wrong layout was passed to
15913 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
15914 0.2.0.10-alpha. Patch from 'cypherpunks'.
15915 - Do not assert if the 'data' pointer on a buffer is advanced to the
15916 very end of the buffer; log a BUG message instead. Only assert if
15917 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
15919 o Major bugfixes (exit node stability):
15920 - Fix an assertion failure that could occur under high DNS load.
15921 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
15922 diagnosed and fixed by "cypherpunks".
15924 o Major bugfixes (Linux seccomp2 sandbox):
15925 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
15926 crash during attempts to call wait4. Fixes bug 15088; bugfix on
15927 0.2.5.1-alpha. Patch from "sanic".
15929 o Minor features (controller):
15930 - New "GETINFO bw-event-cache" to get information about recent
15931 bandwidth events. Closes ticket 14128. Useful for controllers to
15932 get recent bandwidth history after the fix for ticket 13988.
15934 o Minor features (geoip):
15935 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
15936 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
15939 o Minor bugfixes (client, automapping):
15940 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
15941 no value follows the option. Fixes bug 14142; bugfix on
15942 0.2.4.7-alpha. Patch by "teor".
15943 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
15944 14195; bugfix on 0.1.0.1-rc.
15946 o Minor bugfixes (compilation):
15947 - Build without warnings with the stock OpenSSL srtp.h header, which
15948 has a duplicate declaration of SSL_get_selected_srtp_profile().
15949 Fixes bug 14220; this is OpenSSL's bug, not ours.
15951 o Minor bugfixes (directory authority):
15952 - Allow directory authorities to fetch more data from one another if
15953 they find themselves missing lots of votes. Previously, they had
15954 been bumping against the 10 MB queued data limit. Fixes bug 14261;
15955 bugfix on 0.1.2.5-alpha.
15956 - Enlarge the buffer to read bwauth generated files to avoid an
15957 issue when parsing the file in dirserv_read_measured_bandwidths().
15958 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
15960 o Minor bugfixes (statistics):
15961 - Increase period over which bandwidth observations are aggregated
15962 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
15964 o Minor bugfixes (preventative security, C safety):
15965 - When reading a hexadecimal, base-32, or base-64 encoded value from
15966 a string, always overwrite the whole output buffer. This prevents
15967 some bugs where we would look at (but fortunately, not reveal)
15968 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
15972 Changes in version 0.2.4.26 - 2015-03-17
15973 Tor 0.2.4.26 includes an updated list of directory authorities. It
15974 also backports a couple of stability and security bugfixes from 0.2.5
15977 o Directory authority changes:
15978 - Remove turtles as a directory authority.
15979 - Add longclaw as a new (v3) directory authority. This implements
15980 ticket 13296. This keeps the directory authority count at 9.
15981 - The directory authority Faravahar has a new IP address. This
15982 closes ticket 14487.
15984 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
15985 - Fix an assertion failure that could occur under high DNS load.
15986 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
15987 diagnosed and fixed by "cypherpunks".
15989 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
15990 - Fix a bug that could lead to a relay crashing with an assertion
15991 failure if a buffer of exactly the wrong layout was passed to
15992 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
15993 0.2.0.10-alpha. Patch from 'cypherpunks'.
15994 - Do not assert if the 'data' pointer on a buffer is advanced to the
15995 very end of the buffer; log a BUG message instead. Only assert if
15996 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
15998 o Minor features (geoip):
15999 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16000 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16003 Changes in version 0.2.6.4-rc - 2015-03-09
16004 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
16005 attacker might be able to use in order to crash certain Tor
16006 directories. It also resolves some minor issues left over from, or
16007 introduced in, Tor 0.2.6.3-alpha or earlier.
16009 o Major bugfixes (crash, OSX, security):
16010 - Fix a remote denial-of-service opportunity caused by a bug in
16011 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
16014 o Major bugfixes (relay, stability, possible security):
16015 - Fix a bug that could lead to a relay crashing with an assertion
16016 failure if a buffer of exactly the wrong layout is passed to
16017 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16018 0.2.0.10-alpha. Patch from "cypherpunks".
16019 - Do not assert if the 'data' pointer on a buffer is advanced to the
16020 very end of the buffer; log a BUG message instead. Only assert if
16021 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16023 o Major bugfixes (FreeBSD IPFW transparent proxy):
16024 - Fix address detection with FreeBSD transparent proxies, when
16025 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
16028 o Major bugfixes (Linux seccomp2 sandbox):
16029 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
16030 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
16032 - Allow AF_UNIX hidden services to be used with the seccomp2
16033 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
16034 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
16035 crash during attempts to call wait4. Fixes bug 15088; bugfix on
16036 0.2.5.1-alpha. Patch from "sanic".
16038 o Minor features (controller):
16039 - Messages about problems in the bootstrap process now include
16040 information about the server we were trying to connect to when we
16041 noticed the problem. Closes ticket 15006.
16043 o Minor features (geoip):
16044 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16045 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16048 o Minor features (logs):
16049 - Quiet some log messages in the heartbeat and at startup. Closes
16052 o Minor bugfixes (certificate handling):
16053 - If an authority operator accidentally makes a signing certificate
16054 with a future publication time, do not discard its real signing
16055 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
16056 - Remove any old authority certificates that have been superseded
16057 for at least two days. Previously, we would keep superseded
16058 certificates until they expired, if they were published close in
16059 time to the certificate that superseded them. Fixes bug 11454;
16060 bugfix on 0.2.1.8-alpha.
16062 o Minor bugfixes (compilation):
16063 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
16065 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
16068 o Minor bugfixes (testing):
16069 - Fix endianness issues in unit test for resolve_my_address() to
16070 have it pass on big endian systems. Fixes bug 14980; bugfix on
16072 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
16073 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
16074 - When running the new 'make test-stem' target, use the configured
16075 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
16076 from "cypherpunks".
16077 - When running the zero-length-keys tests, do not use the default
16078 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
16081 o Directory authority IP change:
16082 - The directory authority Faravahar has a new IP address. This
16083 closes ticket 14487.
16086 - Remove some lingering dead code that once supported mempools.
16087 Mempools were disabled by default in 0.2.5, and removed entirely
16088 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
16092 Changes in version 0.2.6.3-alpha - 2015-02-19
16093 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
16094 the 0.2.6.x series. It introduces support for more kinds of sockets,
16095 makes it harder to accidentally run an exit, improves our
16096 multithreading backend, incorporates several fixes for the
16097 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
16099 If no major regressions or security holes are found in this version,
16100 the next version will be a release candidate.
16102 o Deprecated versions:
16103 - Tor relays older than 0.2.4.18-rc are no longer allowed to
16104 advertise themselves on the network. Closes ticket 13555.
16106 o Major features (security, unix domain sockets):
16107 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
16108 applications can reach Tor without having to create AF_INET or
16109 AF_INET6 sockets, meaning they can completely disable their
16110 ability to make non-Tor network connections. To create a socket of
16111 this type, use "SocksPort unix:/path/to/socket". Implements
16113 - Support mapping hidden service virtual ports to AF_UNIX sockets.
16114 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
16115 Implements ticket 11485.
16117 o Major features (changed defaults):
16118 - Prevent relay operators from unintentionally running exits: When a
16119 relay is configured as an exit node, we now warn the user unless
16120 the "ExitRelay" option is set to 1. We warn even more loudly if
16121 the relay is configured with the default exit policy, since this
16122 can indicate accidental misconfiguration. Setting "ExitRelay 0"
16123 stops Tor from running as an exit relay. Closes ticket 10067.
16125 o Major features (directory system):
16126 - When downloading server- or microdescriptors from a directory
16127 server, we no longer launch multiple simultaneous requests to the
16128 same server. This reduces load on the directory servers,
16129 especially when directory guards are in use. Closes ticket 9969.
16130 - When downloading server- or microdescriptors over a tunneled
16131 connection, do not limit the length of our requests to what the
16132 Squid proxy is willing to handle. Part of ticket 9969.
16133 - Authorities can now vote on the correct digests and latest
16134 versions for different software packages. This allows packages
16135 that include Tor to use the Tor authority system as a way to get
16136 notified of updates and their correct digests. Implements proposal
16137 227. Closes ticket 10395.
16139 o Major features (guards):
16140 - Introduce the Guardfraction feature to improves load balancing on
16141 guard nodes. Specifically, it aims to reduce the traffic gap that
16142 guard nodes experience when they first get the Guard flag. This is
16143 a required step if we want to increase the guard lifetime to 9
16144 months or greater. Closes ticket 9321.
16146 o Major features (performance):
16147 - Make the CPU worker implementation more efficient by avoiding the
16148 kernel and lengthening pipelines. The original implementation used
16149 sockets to transfer data from the main thread to the workers, and
16150 didn't allow any thread to be assigned more than a single piece of
16151 work at once. The new implementation avoids communications
16152 overhead by making requests in shared memory, avoiding kernel IO
16153 where possible, and keeping more requests in flight at once.
16154 Implements ticket 9682.
16156 o Major features (relay):
16157 - Raise the minimum acceptable configured bandwidth rate for bridges
16158 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
16159 20 KiB/sec.) Closes ticket 13822.
16161 o Major bugfixes (exit node stability):
16162 - Fix an assertion failure that could occur under high DNS load.
16163 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16164 diagnosed and fixed by "cypherpunks".
16166 o Major bugfixes (mixed relay-client operation):
16167 - When running as a relay and client at the same time (not
16168 recommended), if we decide not to use a new guard because we want
16169 to retry older guards, only close the locally-originating circuits
16170 passing through that guard. Previously we would close all the
16171 circuits through that guard. Fixes bug 9819; bugfix on
16172 0.2.1.1-alpha. Reported by "skruffy".
16174 o Minor features (build):
16175 - New --disable-system-torrc compile-time option to prevent Tor from
16176 looking for the system-wide torrc or torrc-defaults files.
16177 Resolves ticket 13037.
16179 o Minor features (controller):
16180 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
16181 events so controllers can observe circuit isolation inputs. Closes
16183 - ControlPort now supports the unix:/path/to/socket syntax as an
16184 alternative to the ControlSocket option, for consistency with
16185 SocksPort and HiddenServicePort. Closes ticket 14451.
16186 - New "GETINFO bw-event-cache" to get information about recent
16187 bandwidth events. Closes ticket 14128. Useful for controllers to
16188 get recent bandwidth history after the fix for ticket 13988.
16190 o Minor features (Denial of service resistance):
16191 - Count the total number of bytes used storing hidden service
16192 descriptors against the value of MaxMemInQueues. If we're low on
16193 memory, and more than 20% of our memory is used holding hidden
16194 service descriptors, free them until no more than 10% of our
16195 memory holds hidden service descriptors. Free the least recently
16196 fetched descriptors first. Resolves ticket 13806.
16197 - When we have recently been under memory pressure (over 3/4 of
16198 MaxMemInQueues is allocated), then allocate smaller zlib objects
16199 for small requests. Closes ticket 11791.
16201 o Minor features (geoip):
16202 - Update geoip and geoip6 files to the January 7 2015 Maxmind
16203 GeoLite2 Country database.
16205 o Minor features (guard nodes):
16206 - Reduce the time delay before saving guard status to disk from 10
16207 minutes to 30 seconds (or from one hour to 10 minutes if
16208 AvoidDiskWrites is set). Closes ticket 12485.
16210 o Minor features (hidden service):
16211 - Make Sybil attacks against hidden services harder by changing the
16212 minimum time required to get the HSDir flag from 25 hours up to 96
16213 hours. Addresses ticket 14149.
16214 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
16215 services to disable the anti-scanning feature introduced in
16216 0.2.6.2-alpha. With this option not set, a connection to an
16217 unlisted port closes the circuit. With this option set, only a
16218 RELAY_DONE cell is sent. Closes ticket 14084.
16220 o Minor features (interface):
16221 - Implement "-f -" command-line option to read torrc configuration
16222 from standard input, if you don't want to store the torrc file in
16223 the file system. Implements feature 13865.
16225 o Minor features (logging):
16226 - Add a count of unique clients to the bridge heartbeat message.
16227 Resolves ticket 6852.
16228 - Suppress "router info incompatible with extra info" message when
16229 reading extrainfo documents from cache. (This message got loud
16230 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
16232 - Elevate hidden service authorized-client message from DEBUG to
16233 INFO. Closes ticket 14015.
16235 o Minor features (stability):
16236 - Add assertions in our hash-table iteration code to check for
16237 corrupted values that could cause infinite loops. Closes
16240 o Minor features (systemd):
16241 - Various improvements and modernizations in systemd hardening
16242 support. Closes ticket 13805. Patch from Craig Andrews.
16244 o Minor features (testing networks):
16245 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
16246 and the default on a testing network to 2 minutes. Drop the
16247 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
16248 keep the default on a testing network at 30 seconds. This reduces
16249 HS bootstrap time to around 25 seconds. Also, change the default
16250 time in test-network.sh to match. Closes ticket 13401. Patch
16252 - Create TestingDirAuthVoteHSDir to correspond to
16253 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
16254 HSDir flag for the listed relays regardless of uptime or ORPort
16255 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
16256 Partial implementation for ticket 14067. Patch by "teor".
16258 o Minor features (tor2web mode):
16259 - Introduce the config option Tor2webRendezvousPoints, which allows
16260 clients in Tor2webMode to select a specific Rendezvous Point to be
16261 used in HS circuits. This might allow better performance for
16262 Tor2Web nodes. Implements ticket 12844.
16264 o Minor bugfixes (client DNS):
16265 - Report the correct cached DNS expiration times on SOCKS port or in
16266 DNS replies. Previously, we would report everything as "never
16267 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
16268 - Avoid a small memory leak when we find a cached answer for a
16269 reverse DNS lookup in a client-side DNS cache. (Remember, client-
16270 side DNS caching is off by default, and is not recommended.) Fixes
16271 bug 14259; bugfix on 0.2.0.1-alpha.
16273 o Minor bugfixes (client, automapping):
16274 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
16275 no value follows the option. Fixes bug 14142; bugfix on
16276 0.2.4.7-alpha. Patch by "teor".
16277 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
16278 14195; bugfix on 0.1.0.1-rc.
16279 - Prevent changes to other options from removing the wildcard value
16280 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
16282 - Allow MapAddress and AutomapHostsOnResolve to work together when
16283 an address is mapped into another address type (like .onion) that
16284 must be automapped at resolve time. Fixes bug 7555; bugfix
16287 o Minor bugfixes (client, bridges):
16288 - When we are using bridges and we had a network connectivity
16289 problem, only retry connecting to our currently configured
16290 bridges, not all bridges we know about and remember using. Fixes
16291 bug 14216; bugfix on 0.2.2.17-alpha.
16293 o Minor bugfixes (client, IPv6):
16294 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
16295 flag is not set; and not because the NoIPv4Traffic flag was set.
16296 Previously we'd looked at the NoIPv4Traffic flag for both types of
16297 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
16299 o Minor bugfixes (compilation):
16300 - The address of an array in the middle of a structure will always
16301 be non-NULL. clang recognises this and complains. Disable the
16302 tautologous and redundant check to silence this warning. Fixes bug
16303 14001; bugfix on 0.2.1.2-alpha.
16304 - Avoid warnings when building with systemd 209 or later. Fixes bug
16305 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
16306 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
16307 Addresses ticket 14188.
16308 - Build without warnings with the stock OpenSSL srtp.h header, which
16309 has a duplicate declaration of SSL_get_selected_srtp_profile().
16310 Fixes bug 14220; this is OpenSSL's bug, not ours.
16311 - Do not compile any code related to Tor2Web mode when Tor2Web mode
16312 is not enabled at compile time. Previously, this code was included
16313 in a disabled state. See discussion on ticket 12844.
16314 - Remove the --disable-threads configure option again. It was
16315 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
16316 14819; bugfix on 0.2.6.2-alpha.
16318 o Minor bugfixes (controller):
16319 - Report "down" in response to the "GETINFO entry-guards" command
16320 when relays are down with an unreachable_since value. Previously,
16321 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
16322 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
16323 14116; bugfix on 0.2.2.9-alpha.
16324 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
16325 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
16327 o Minor bugfixes (directory authority):
16328 - Allow directory authorities to fetch more data from one another if
16329 they find themselves missing lots of votes. Previously, they had
16330 been bumping against the 10 MB queued data limit. Fixes bug 14261;
16331 bugfix on 0.1.2.5-alpha.
16332 - Do not attempt to download extrainfo documents which we will be
16333 unable to validate with a matching server descriptor. Fixes bug
16334 13762; bugfix on 0.2.0.1-alpha.
16335 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
16336 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
16337 - Enlarge the buffer to read bwauth generated files to avoid an
16338 issue when parsing the file in dirserv_read_measured_bandwidths().
16339 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
16341 o Minor bugfixes (file handling):
16342 - Stop failing when key files are zero-length. Instead, generate new
16343 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
16344 on all versions of Tor. Patch by "teor".
16345 - Stop generating a fresh .old RSA onion key file when the .old file
16346 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
16347 - Avoid overwriting .old key files with empty key files.
16348 - Skip loading zero-length extrainfo store, router store, stats,
16349 state, and key files.
16350 - Avoid crashing when trying to reload a torrc specified as a
16351 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
16354 o Minor bugfixes (hidden services):
16355 - Close the introduction circuit when we have no more usable intro
16356 points, instead of waiting for it to time out. This also ensures
16357 that no follow-up HS descriptor fetch is triggered when the
16358 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
16359 - When fetching a hidden service descriptor for a down service that
16360 was recently up, do not keep refetching until we try the same
16361 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
16362 - Successfully launch Tor with a nonexistent hidden service
16363 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
16364 14106; bugfix on 0.2.6.2-alpha.
16366 o Minor bugfixes (logging):
16367 - Avoid crashing when there are more log domains than entries in
16368 domain_list. Bugfix on 0.2.3.1-alpha.
16369 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
16371 - Don't log messages to stdout twice when starting up. Fixes bug
16372 13993; bugfix on 0.2.6.1-alpha.
16374 o Minor bugfixes (parsing):
16375 - Stop accepting milliseconds (or other junk) at the end of
16376 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
16377 - Support two-number and three-number version numbers correctly, in
16378 case we change the Tor versioning system in the future. Fixes bug
16379 13661; bugfix on 0.0.8pre1.
16381 o Minor bugfixes (path counting):
16382 - When deciding whether the consensus lists any exit nodes, count
16383 the number listed in the consensus, not the number we have
16384 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
16385 - When deciding whether we have any exit nodes, only examine
16386 ExitNodes when the ExitNodes option is actually set. Fixes part of
16387 bug 14918; bugfix on 0.2.6.2-alpha.
16388 - Get rid of redundant and possibly scary warnings that we are
16389 missing directory information while we bootstrap. Fixes part of
16390 bug 14918; bugfix on 0.2.6.2-alpha.
16392 o Minor bugfixes (portability):
16393 - Fix the ioctl()-based network interface lookup code so that it
16394 will work on systems that have variable-length struct ifreq, for
16396 - Fix scheduler compilation on targets where char is unsigned. Fixes
16397 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
16399 o Minor bugfixes (sandbox):
16400 - Allow glibc fatal errors to be sent to stderr before Tor exits.
16401 Previously, glibc would try to write them to /dev/tty, and the
16402 sandbox would trap the call and make Tor exit prematurely. Fixes
16403 bug 14759; bugfix on 0.2.5.1-alpha.
16405 o Minor bugfixes (shutdown):
16406 - When shutting down, always call event_del() on lingering read or
16407 write events before freeing them. Otherwise, we risk double-frees
16408 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
16411 o Minor bugfixes (small memory leaks):
16412 - Avoid leaking memory when using IPv6 virtual address mappings.
16413 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
16416 o Minor bugfixes (statistics):
16417 - Increase period over which bandwidth observations are aggregated
16418 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
16420 o Minor bugfixes (systemd support):
16421 - Fix detection and operation of systemd watchdog. Fixes part of bug
16422 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
16423 - Run correctly under systemd with the RunAsDaemon option set. Fixes
16424 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
16425 - Inform the systemd supervisor about more changes in the Tor
16426 process status. Implements part of ticket 14141. Patch from
16428 - Cause the "--disable-systemd" option to actually disable systemd
16429 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
16432 o Minor bugfixes (TLS):
16433 - Check more thoroughly throughout the TLS code for possible
16434 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
16436 o Minor bugfixes (transparent proxy):
16437 - Use getsockname, not getsockopt, to retrieve the address for a
16438 TPROXY-redirected connection. Fixes bug 13796; bugfix
16441 o Code simplification and refactoring:
16442 - Move fields related to isolating and configuring client ports into
16443 a shared structure. Previously, they were duplicated across
16444 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
16445 to copy them correctly had been the cause of at least one bug in
16446 the past. Closes ticket 8546.
16447 - Refactor the get_interface_addresses_raw() doom-function into
16448 multiple smaller and simpler subfunctions. Cover the resulting
16449 subfunctions with unit-tests. Fixes a significant portion of
16451 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
16452 only for version <= 0.2.2.24 which is now deprecated. Closes
16454 - Remove a test for a long-defunct broken version-one
16458 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
16459 for writing the OpenBSD-specific tips. Resolves ticket 13702.
16460 - Make the tor-resolve documentation match its help string and its
16461 options. Resolves part of ticket 14325.
16462 - Log a more useful error message from tor-resolve when failing to
16463 look up a hidden service address. Resolves part of ticket 14325.
16465 o Downgraded warnings:
16466 - Don't warn when we've attempted to contact a relay using the wrong
16467 ntor onion key. Closes ticket 9635.
16469 o Removed features:
16470 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
16471 longer silently accepted as an alias for "ExitNodes".
16472 - The --enable-mempool and --enable-buf-freelists options, which
16473 were originally created to work around bad malloc implementations,
16474 no longer exist. They were off-by-default in 0.2.5. Closes
16478 - Make the checkdir/perms test complete successfully even if the
16479 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
16480 - Test that tor does not fail when key files are zero-length. Check
16481 that tor generates new keys, and overwrites the empty key files.
16482 - Test that tor generates new keys when keys are missing
16483 (existing behavior).
16484 - Test that tor does not overwrite key files that already contain
16485 data (existing behavior). Tests bug 13111. Patch by "teor".
16486 - New "make test-stem" target to run stem integration tests.
16487 Requires that the "STEM_SOURCE_DIR" environment variable be set.
16488 Closes ticket 14107.
16489 - Make the test_cmdline_args.py script work correctly on Windows.
16490 Patch from Gisle Vanem.
16491 - Move the slower unit tests into a new "./src/test/test-slow"
16492 binary that can be run independently of the other tests. Closes
16494 - Avoid undefined behavior when sampling huge values from the
16495 Laplace distribution. This made unittests fail on Raspberry Pi.
16496 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
16499 Changes in version 0.2.6.2-alpha - 2014-12-31
16500 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
16501 It introduces a major new backend for deciding when to send cells on
16502 channels, which should lead down the road to big performance
16503 increases. It contains security and statistics features for better
16504 work on hidden services, and numerous bugfixes.
16506 This release contains many new unit tests, along with major
16507 performance improvements for running testing networks using Chutney.
16508 Thanks to a series of patches contributed by "teor", testing networks
16509 should now bootstrap in seconds, rather than minutes.
16511 o Major features (relay, infrastructure):
16512 - Complete revision of the code that relays use to decide which cell
16513 to send next. Formerly, we selected the best circuit to write on
16514 each channel, but we didn't select among channels in any
16515 sophisticated way. Now, we choose the best circuits globally from
16516 among those whose channels are ready to deliver traffic.
16518 This patch implements a new inter-cmux comparison API, a global
16519 high/low watermark mechanism and a global scheduler loop for
16520 transmission prioritization across all channels as well as among
16521 circuits on one channel. This schedule is currently tuned to
16522 (tolerantly) avoid making changes in network performance, but it
16523 should form the basis for major circuit performance increases in
16524 the future. Code by Andrea; tuning by Rob Jansen; implements
16527 o Major features (hidden services):
16528 - Make HS port scanning more difficult by immediately closing the
16529 circuit when a user attempts to connect to a nonexistent port.
16530 Closes ticket 13667.
16531 - Add a HiddenServiceStatistics option that allows Tor relays to
16532 gather and publish statistics about the overall size and volume of
16533 hidden service usage. Specifically, when this option is turned on,
16534 an HSDir will publish an approximate number of hidden services
16535 that have published descriptors to it the past 24 hours. Also, if
16536 a relay has acted as a hidden service rendezvous point, it will
16537 publish the approximate amount of rendezvous cells it has relayed
16538 the past 24 hours. The statistics themselves are obfuscated so
16539 that the exact values cannot be derived. For more details see
16540 proposal 238, "Better hidden service stats from Tor relays". This
16541 feature is currently disabled by default. Implements feature 13192.
16543 o Major bugfixes (client, automap):
16544 - Repair automapping with IPv6 addresses. This automapping should
16545 have worked previously, but one piece of debugging code that we
16546 inserted to detect a regression actually caused the regression to
16547 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
16548 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
16551 o Major bugfixes (hidden services):
16552 - When closing an introduction circuit that was opened in parallel
16553 with others, don't mark the introduction point as unreachable.
16554 Previously, the first successful connection to an introduction
16555 point would make the other introduction points get marked as
16556 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
16558 o Directory authority changes:
16559 - Remove turtles as a directory authority.
16560 - Add longclaw as a new (v3) directory authority. This implements
16561 ticket 13296. This keeps the directory authority count at 9.
16563 o Major removed features:
16564 - Tor clients no longer support connecting to hidden services
16565 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
16566 option has been removed. (There shouldn't be any hidden services
16567 running these versions on the network.) Closes ticket 7803.
16569 o Minor features (client):
16570 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
16571 is enabled, reject requests with IP addresses as hostnames.
16572 Resolves ticket 13315.
16574 o Minor features (controller):
16575 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
16576 write an unscheduled heartbeat message to the log. Implements
16579 o Minor features (geoip):
16580 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
16583 o Minor features (hidden services):
16584 - When re-enabling the network, don't try to build introduction
16585 circuits until we have successfully built a circuit. This makes
16586 hidden services come up faster when the network is re-enabled.
16587 Patch from "akwizgran". Closes ticket 13447.
16588 - When we fail to retrieve a hidden service descriptor, send the
16589 controller an "HS_DESC FAILED" controller event. Implements
16591 - New HiddenServiceDirGroupReadable option to cause hidden service
16592 directories and hostname files to be created group-readable. Patch
16593 from "anon", David Stainton, and "meejah". Closes ticket 11291.
16595 o Minor features (systemd):
16596 - Where supported, when running with systemd, report successful
16597 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
16598 - When running with systemd, support systemd watchdog messages. Part
16599 of ticket 11016. Patch by Michael Scherer.
16601 o Minor features (transparent proxy):
16602 - Update the transparent proxy option checks to allow for both ipfw
16603 and pf on OS X. Closes ticket 14002.
16604 - Use the correct option when using IPv6 with transparent proxy
16605 support on Linux. Resolves 13808. Patch by Francisco Blas
16608 o Minor bugfixes (preventative security, C safety):
16609 - When reading a hexadecimal, base-32, or base-64 encoded value from
16610 a string, always overwrite the whole output buffer. This prevents
16611 some bugs where we would look at (but fortunately, not reveal)
16612 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
16614 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
16615 just the part that's used. This makes it harder for data leak bugs
16616 to occur in the event of other programming failures. Resolves
16619 o Minor bugfixes (client, microdescriptors):
16620 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
16621 computing which microdescriptors to download. This keeps us from
16622 erroneous download behavior if two microdescriptor digests ever
16623 have the same first 160 bits. Fixes part of bug 13399; bugfix
16625 - Reset a router's status if its microdescriptor digest changes,
16626 even if the first 160 bits remain the same. Fixes part of bug
16627 13399; bugfix on 0.2.3.1-alpha.
16629 o Minor bugfixes (compilation):
16630 - Silence clang warnings under --enable-expensive-hardening,
16631 including implicit truncation of 64 bit values to 32 bit, const
16632 char assignment to self, tautological compare, and additional
16633 parentheses around equality tests. Fixes bug 13577; bugfix
16635 - Fix a clang warning about checking whether an address in the
16636 middle of a structure is NULL. Fixes bug 14001; bugfix
16639 o Minor bugfixes (hidden services):
16640 - Correctly send a controller event when we find that a rendezvous
16641 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
16642 - Pre-check directory permissions for new hidden-services to avoid
16643 at least one case of "Bug: Acting on config options left us in a
16644 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
16645 - When adding a new hidden service (for example, via SETCONF), Tor
16646 no longer congratulates the user for running a relay. Fixes bug
16647 13941; bugfix on 0.2.6.1-alpha.
16648 - When fetching hidden service descriptors, we now check not only
16649 for whether we got the hidden service we had in mind, but also
16650 whether we got the particular descriptors we wanted. This prevents
16651 a class of inefficient but annoying DoS attacks by hidden service
16652 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
16655 o Minor bugfixes (Linux seccomp2 sandbox):
16656 - Make transparent proxy support work along with the seccomp2
16657 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
16658 by Francisco Blas Izquierdo Riera.
16659 - Fix a memory leak in tor-resolve when running with the sandbox
16660 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
16662 o Minor bugfixes (logging):
16663 - Downgrade warnings about RSA signature failures to info log level.
16664 Emit a warning when an extra info document is found incompatible
16665 with a corresponding router descriptor. Fixes bug 9812; bugfix
16667 - Make connection_ap_handshake_attach_circuit() log the circuit ID
16668 correctly. Fixes bug 13701; bugfix on 0.0.6.
16670 o Minor bugfixes (misc):
16671 - Stop allowing invalid address patterns like "*/24" that contain
16672 both a wildcard address and a bit prefix length. This affects all
16673 our address-range parsing code. Fixes bug 7484; bugfix
16676 o Minor bugfixes (testing networks, fast startup):
16677 - Allow Tor to build circuits using a consensus with no exits. If
16678 the consensus has no exits (typical of a bootstrapping test
16679 network), allow Tor to build circuits once enough descriptors have
16680 been downloaded. This assists in bootstrapping a testing Tor
16681 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
16683 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
16684 header to directory servers. This allows us to obtain consensuses
16685 promptly when the consensus interval is very short. This assists
16686 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
16687 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
16688 - Stop assuming that private addresses are local when checking
16689 reachability in a TestingTorNetwork. Instead, when testing, assume
16690 all OR connections are remote. (This is necessary due to many test
16691 scenarios running all relays on localhost.) This assists in
16692 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
16693 0.1.0.1-rc. Patch by "teor".
16694 - Avoid building exit circuits from a consensus with no exits. Now
16695 thanks to our fix for 13718, we accept a no-exit network as not
16696 wholly lost, but we need to remember not to try to build exit
16697 circuits on it. Closes ticket 13814; patch by "teor".
16698 - Stop requiring exits to have non-zero bandwithcapacity in a
16699 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
16700 ignore exit bandwidthcapacity. This assists in bootstrapping a
16701 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
16702 on 0.2.0.3-alpha. Patch by "teor".
16703 - Add "internal" to some bootstrap statuses when no exits are
16704 available. If the consensus does not contain Exits, Tor will only
16705 build internal circuits. In this case, relevant statuses will
16706 contain the word "internal" as indicated in the Tor control-
16707 spec.txt. When bootstrap completes, Tor will be ready to build
16708 internal circuits. If a future consensus contains Exits, exit
16709 circuits may become available. Fixes part of bug 13718; bugfix on
16710 0.2.4.10-alpha. Patch by "teor".
16711 - Decrease minimum consensus interval to 10 seconds when
16712 TestingTorNetwork is set, or 5 seconds for the first consensus.
16713 Fix assumptions throughout the code that assume larger intervals.
16714 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
16716 - Avoid excluding guards from path building in minimal test
16717 networks, when we're in a test network and excluding guards would
16718 exclude all relays. This typically occurs in incredibly small tor
16719 networks, and those using "TestingAuthVoteGuard *". Fixes part of
16720 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
16722 o Code simplification and refactoring:
16723 - Stop using can_complete_circuits as a global variable; access it
16724 with a function instead.
16725 - Avoid using operators directly as macro arguments: this lets us
16726 apply coccinelle transformations to our codebase more directly.
16727 Closes ticket 13172.
16728 - Combine the functions used to parse ClientTransportPlugin and
16729 ServerTransportPlugin into a single function. Closes ticket 6456.
16730 - Add inline functions and convenience macros for inspecting channel
16731 state. Refactor the code to use convenience macros instead of
16732 checking channel state directly. Fixes issue 7356.
16733 - Document all members of was_router_added_t and rename
16734 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
16735 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
16736 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
16737 constant instead of hardcoded value. Fixes issue 13840.
16738 - Refactor our generic strmap and digestmap types into a single
16739 implementation, so that we can add a new digest256map
16743 - Document the bridge-authority-only 'networkstatus-bridges' file.
16744 Closes ticket 13713; patch from "tom".
16745 - Fix typo in PredictedPortsRelevanceTime option description in
16746 manpage. Resolves issue 13707.
16747 - Stop suggesting that users specify relays by nickname: it isn't a
16748 good idea. Also, properly cross-reference how to specify relays in
16749 all parts of manual documenting options that take a list of
16750 relays. Closes ticket 13381.
16751 - Clarify the HiddenServiceDir option description in manpage to make
16752 it clear that relative paths are taken with respect to the current
16753 working directory. Also clarify that this behavior is not
16754 guaranteed to remain indefinitely. Fixes issue 13913.
16757 - New tests for many parts of channel, relay, and circuitmux
16758 functionality. Code by Andrea; part of 9262.
16759 - New tests for parse_transport_line(). Part of ticket 6456.
16760 - In the unit tests, use chgrp() to change the group of the unit
16761 test temporary directory to the current user, so that the sticky
16762 bit doesn't interfere with tests that check directory groups.
16764 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
16768 Changes in version 0.2.6.1-alpha - 2014-10-30
16769 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
16770 includes numerous code cleanups and new tests, and fixes a large
16771 number of annoying bugs. Out-of-memory conditions are handled better
16772 than in 0.2.5, pluggable transports have improved proxy support, and
16773 clients now use optimistic data for contacting hidden services. Also,
16774 we are now more robust to changes in what we consider a parseable
16775 directory object, so that tightening restrictions does not have a risk
16776 of introducing infinite download loops.
16778 This is the first alpha release in a new series, so expect there to be
16779 bugs. Users who would rather test out a more stable branch should stay
16780 with 0.2.5.x for now.
16782 o New compiler and system requirements:
16783 - Tor 0.2.6.x requires that your compiler support more of the C99
16784 language standard than before. The 'configure' script now detects
16785 whether your compiler supports C99 mid-block declarations and
16786 designated initializers. If it does not, Tor will not compile.
16788 We may revisit this requirement if it turns out that a significant
16789 number of people need to build Tor with compilers that don't
16790 bother implementing a 15-year-old standard. Closes ticket 13233.
16791 - Tor no longer supports systems without threading support. When we
16792 began working on Tor, there were several systems that didn't have
16793 threads, or where the thread support wasn't able to run the
16794 threads of a single process on multiple CPUs. That no longer
16795 holds: every system where Tor needs to run well now has threading
16796 support. Resolves ticket 12439.
16798 o Removed platform support:
16799 - We no longer include special code to build on Windows CE; as far
16800 as we know, nobody has used Tor on Windows CE in a very long time.
16801 Closes ticket 11446.
16803 o Major features (bridges):
16804 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
16805 transports if they are configured via the "TOR_PT_PROXY"
16806 environment variable. Implements proposal 232. Resolves
16809 o Major features (client performance, hidden services):
16810 - Allow clients to use optimistic data when connecting to a hidden
16811 service, which should remove a round-trip from hidden service
16812 initialization. See proposal 181 for details. Implements
16815 o Major features (directory system):
16816 - Upon receiving an unparseable directory object, if its digest
16817 matches what we expected, then don't try to download it again.
16818 Previously, when we got a descriptor we didn't like, we would keep
16819 trying to download it over and over. Closes ticket 11243.
16821 o Major features (sample torrc):
16822 - Add a new, infrequently-changed "torrc.minimal". This file is
16823 similar to torrc.sample, but it will change as infrequently as
16824 possible, for the benefit of users whose systems prompt them for
16825 intervention whenever a default configuration file is changed.
16826 Making this change allows us to update torrc.sample to be a more
16827 generally useful "sample torrc".
16829 o Major bugfixes (directory authorities):
16830 - Do not assign the HSDir flag to relays if they are not Valid, or
16831 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
16833 o Major bugfixes (directory bandwidth performance):
16834 - Don't flush the zlib buffer aggressively when compressing
16835 directory information for clients. This should save about 7% of
16836 the bandwidth currently used for compressed descriptors and
16837 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
16839 o Minor features (security, memory wiping):
16840 - Ensure we securely wipe keys from memory after
16841 crypto_digest_get_digest and init_curve25519_keypair_from_file
16842 have finished using them. Resolves ticket 13477.
16844 o Minor features (security, out-of-memory handling):
16845 - When handling an out-of-memory condition, allocate less memory for
16846 temporary data structures. Fixes issue 10115.
16847 - When handling an out-of-memory condition, consider more types of
16848 buffers, including those on directory connections, and zlib
16849 buffers. Resolves ticket 11792.
16852 - When identity keypair is generated for first time, log a
16853 congratulatory message that links to the new relay lifecycle
16854 document. Implements feature 10427.
16856 o Minor features (client):
16857 - Clients are now willing to send optimistic data (before they
16858 receive a 'connected' cell) to relays of any version. (Relays
16859 without support for optimistic data are no longer supported on the
16860 Tor network.) Resolves ticket 13153.
16862 o Minor features (directory authorities):
16863 - Don't list relays with a bandwidth estimate of 0 in the consensus.
16864 Implements a feature proposed during discussion of bug 13000.
16865 - In tor-gencert, report an error if the user provides the same
16866 argument more than once.
16867 - If a directory authority can't find a best consensus method in the
16868 votes that it holds, it now falls back to its favorite consensus
16869 method. Previously, it fell back to method 1. Neither of these is
16870 likely to get enough signatures, but "fall back to favorite"
16871 doesn't require us to maintain support an obsolete consensus
16872 method. Implements part of proposal 215.
16874 o Minor features (logging):
16875 - On Unix-like systems, you can now use named pipes as the target of
16876 the Log option, and other options that try to append to files.
16877 Closes ticket 12061. Patch from "carlo von lynX".
16878 - When opening a log file at startup, send it every log message that
16879 we generated between startup and opening it. Previously, log
16880 messages that were generated before opening the log file were only
16881 logged to stdout. Closes ticket 6938.
16882 - Add a TruncateLogFile option to overwrite logs instead of
16883 appending to them. Closes ticket 5583.
16885 o Minor features (portability, Solaris):
16886 - Threads are no longer disabled by default on Solaris; we believe
16887 that the versions of Solaris with broken threading support are all
16888 obsolete by now. Resolves ticket 9495.
16890 o Minor features (relay):
16891 - Re-check our address after we detect a changed IP address from
16892 getsockname(). This ensures that the controller command "GETINFO
16893 address" will report the correct value. Resolves ticket 11582.
16895 - A new AccountingRule option lets Relays set whether they'd like
16896 AccountingMax to be applied separately to inbound and outbound
16897 traffic, or applied to the sum of inbound and outbound traffic.
16898 Resolves ticket 961. Patch by "chobe".
16900 o Minor features (testing networks):
16901 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
16902 the "Exit" flag regardless of their uptime, bandwidth, or exit
16903 policy. TestingTorNetwork must be set for this option to have any
16904 effect. Previously, authorities would take up to 35 minutes to
16905 give nodes the Exit flag in a test network. Partially implements
16908 o Minor features (validation):
16909 - Check all date/time values passed to tor_timegm and
16910 parse_rfc1123_time for validity, taking leap years into account.
16911 Improves HTTP header validation. Implemented with bug 13476.
16912 - In correct_tm(), limit the range of values returned by system
16913 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
16914 This means we don't have to deal with negative or too large dates,
16915 even if a clock is wrong. Otherwise we might fail to read a file
16916 written by us which includes such a date. Fixes bug 13476.
16918 o Minor bugfixes (bridge clients):
16919 - When configured to use a bridge without an identity digest (not
16920 recommended), avoid launching an extra channel to it when
16921 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
16923 o Minor bugfixes (bridges):
16924 - When DisableNetwork is set, do not launch pluggable transport
16925 plugins, and if any are running, terminate them. Fixes bug 13213;
16926 bugfix on 0.2.3.6-alpha.
16928 o Minor bugfixes (C correctness):
16929 - Fix several instances of possible integer overflow/underflow/NaN.
16930 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
16932 - In circuit_build_times_calculate_timeout() in circuitstats.c,
16933 avoid dividing by zero in the pareto calculations. This traps
16934 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
16936 - Fix an integer overflow in format_time_interval(). Fixes bug
16937 13393; bugfix on 0.2.0.10-alpha.
16938 - Set the correct day of year value when the system's localtime(_r)
16939 or gmtime(_r) functions fail to set struct tm. Not externally
16940 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
16941 - Avoid unlikely signed integer overflow in tor_timegm on systems
16942 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
16944 o Minor bugfixes (client):
16945 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
16946 BadExit flag are not considered worthy candidates. Fixes bug
16947 13066; bugfix on 0.1.2.3-alpha.
16948 - Use the consensus schedule for downloading consensuses, and not
16949 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
16950 - Handle unsupported or malformed SOCKS5 requests properly by
16951 responding with the appropriate error message before closing the
16952 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
16954 o Minor bugfixes (client, torrc):
16955 - Stop modifying the value of our DirReqStatistics torrc option just
16956 because we're not a bridge or relay. This bug was causing Tor
16957 Browser users to write "DirReqStatistics 0" in their torrc files
16958 as if they had chosen to change the config. Fixes bug 4244; bugfix
16960 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
16961 that our options have changed every time we SIGHUP. Fixes bug
16962 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
16964 o Minor bugfixes (controller):
16965 - Return an error when the second or later arguments of the
16966 "setevents" controller command are invalid events. Previously we
16967 would return success while silently skipping invalid events. Fixes
16968 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
16970 o Minor bugfixes (directory system):
16971 - Always believe that v3 directory authorities serve extra-info
16972 documents, whether they advertise "caches-extra-info" or not.
16973 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
16974 - When running as a v3 directory authority, advertise that you serve
16975 extra-info documents so that clients who want them can find them
16976 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
16977 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
16978 Previously, directories offering BRIDGE_DIRINFO and some other
16979 flag (i.e. microdescriptors or extrainfo) would be ignored when
16980 looking for bridges. Partially fixes bug 13163; bugfix
16983 o Minor bugfixes (networking):
16984 - Check for orconns and use connection_or_close_for_error() rather
16985 than connection_mark_for_close() directly in the getsockopt()
16986 failure case of connection_handle_write_impl(). Fixes bug 11302;
16987 bugfix on 0.2.4.4-alpha.
16989 o Minor bugfixes (relay):
16990 - When generating our family list, remove spaces from around the
16991 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
16992 - If our previous bandwidth estimate was 0 bytes, allow publishing a
16993 new relay descriptor immediately. Fixes bug 13000; bugfix
16996 o Minor bugfixes (testing networks):
16997 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
16998 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
16999 - Stop using the default authorities in networks which provide both
17000 AlternateDirAuthority and AlternateBridgeAuthority. Partially
17001 fixes bug 13163; bugfix on 0.2.0.13-alpha.
17003 o Minor bugfixes (testing):
17004 - Stop spawn test failures due to a race condition between the
17005 SIGCHLD handler updating the process status, and the test reading
17006 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
17008 o Minor bugfixes (testing, Windows):
17009 - Avoid passing an extra backslash when creating a temporary
17010 directory for running the unit tests on Windows. Fixes bug 12392;
17011 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
17013 o Minor bugfixes (windows):
17014 - Remove code to special-case handling of NTE_BAD_KEYSET when
17015 acquiring windows CryptoAPI context. This error can't actually
17016 occur for the parameters we're providing. Fixes bug 10816; bugfix
17019 o Minor bugfixes (zlib):
17020 - Avoid truncating a zlib stream when trying to finalize it with an
17021 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
17024 - Allow our configure script to build correctly with autoconf 2.62
17025 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
17026 - Improve the error message from ./configure to make it clear that
17027 when asciidoc has not been found, the user will have to either add
17028 --disable-asciidoc argument or install asciidoc. Resolves
17031 o Code simplification and refactoring:
17032 - Change the entry_is_live() function to take named bitfield
17033 elements instead of an unnamed list of booleans. Closes
17035 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
17036 Resolves ticket 12205.
17037 - Use calloc and reallocarray functions instead of multiply-
17038 then-malloc. This makes it less likely for us to fall victim to an
17039 integer overflow attack when allocating. Resolves ticket 12855.
17040 - Use the standard macro name SIZE_MAX, instead of our
17042 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
17043 functions which take them as arguments. Replace 0 with NO_DIRINFO
17044 in a function call for clarity. Seeks to prevent future issues
17046 - Avoid 4 null pointer errors under clang static analysis by using
17047 tor_assert() to prove that the pointers aren't null. Fixes
17049 - Rework the API of policies_parse_exit_policy() to use a bitmask to
17050 represent parsing options, instead of a confusing mess of
17051 booleans. Resolves ticket 8197.
17052 - Introduce a helper function to parse ExitPolicy in
17053 or_options_t structure.
17056 - Add a doc/TUNING document with tips for handling large numbers of
17057 TCP connections when running busy Tor relay. Update the warning
17058 message to point to this file when running out of sockets
17059 operating system is allowing to use simultaneously. Resolves
17062 o Removed features:
17063 - We no longer remind the user about configuration options that have
17064 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
17065 - Remove our old, non-weighted bandwidth-based node selection code.
17066 Previously, we used it as a fallback when we couldn't perform
17067 weighted bandwidth-based node selection. But that would only
17068 happen in the cases where we had no consensus, or when we had a
17069 consensus generated by buggy or ancient directory authorities. In
17070 either case, it's better to use the more modern, better maintained
17071 algorithm, with reasonable defaults for the weights. Closes
17073 - Remove the --disable-curve25519 configure option. Relays and
17074 clients now are required to support curve25519 and the
17076 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
17077 used to be deprecated synonyms for "StrictNodes", are now marked
17078 obsolete. Resolves ticket 12226.
17079 - Clients don't understand the BadDirectory flag in the consensus
17080 anymore, and ignore it.
17083 - Refactor the function that chooses guard nodes so that it can more
17084 easily be tested; write some tests for it.
17085 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
17086 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
17087 - Create unit tests for format_time_interval(). With bug 13393.
17088 - Add unit tests for tor_timegm signed overflow, tor_timegm and
17089 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
17090 tests (visible) fixes in bug 13476.
17091 - Add a "coverage-html" make target to generate HTML-visualized
17092 coverage results when building with --enable-coverage. (Requires
17093 lcov.) Patch from Kevin Murray.
17094 - Enable the backtrace handler (where supported) when running the
17096 - Revise all unit tests that used the legacy test_* macros to
17097 instead use the recommended tt_* macros. This patch was generated
17098 with coccinelle, to avoid manual errors. Closes ticket 13119.
17100 o Distribution (systemd):
17101 - systemd unit file: only allow tor to write to /var/lib/tor and
17102 /var/log/tor. The rest of the filesystem is accessible for reading
17103 only. Patch by intrigeri; resolves ticket 12751.
17104 - systemd unit file: ensure that the process and all its children
17105 can never gain new privileges. Patch by intrigeri; resolves
17107 - systemd unit file: set up /var/run/tor as writable for the Tor
17108 service. Patch by intrigeri; resolves ticket 13196.
17110 o Removed features (directory authorities):
17111 - Remove code that prevented authorities from listing Tor relays
17112 affected by CVE-2011-2769 as guards. These relays are already
17113 rejected altogether due to the minimum version requirement of
17114 0.2.3.16-alpha. Closes ticket 13152.
17115 - The "AuthDirRejectUnlisted" option no longer has any effect, as
17116 the fingerprints file (approved-routers) has been deprecated.
17117 - Directory authorities do not support being Naming dirauths anymore.
17118 The "NamingAuthoritativeDir" config option is now obsolete.
17119 - Directory authorities do not support giving out the BadDirectory
17121 - Directory authorities no longer advertise or support consensus
17122 methods 1 through 12 inclusive. These consensus methods were
17123 obsolete and/or insecure: maintaining the ability to support them
17124 served no good purpose. Implements part of proposal 215; closes
17127 o Testing (test-network.sh):
17128 - Stop using "echo -n", as some shells' built-in echo doesn't
17129 support "-n". Instead, use "/bin/echo -n". Partially fixes
17131 - Stop an apparent test-network hang when used with make -j2. Fixes
17133 - Add a --delay option to test-network.sh, which configures the
17134 delay before the chutney network tests for data transmission.
17135 Partially implements ticket 13161.
17138 Changes in version 0.2.5.10 - 2014-10-24
17139 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
17141 It adds several new security features, including improved
17142 denial-of-service resistance for relays, new compiler hardening
17143 options, and a system-call sandbox for hardened installations on Linux
17144 (requires seccomp2). The controller protocol has several new features,
17145 resolving IPv6 addresses should work better than before, and relays
17146 should be a little more CPU-efficient. We've added support for more
17147 OpenBSD and FreeBSD transparent proxy types. We've improved the build
17148 system and testing infrastructure to allow unit testing of more parts
17149 of the Tor codebase. Finally, we've addressed several nagging pluggable
17150 transport usability issues, and included numerous other small bugfixes
17151 and features mentioned below.
17153 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
17154 have accumulated many known flaws; everyone should upgrade.
17156 o Deprecated versions:
17157 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
17158 attention for some while.
17161 Changes in version 0.2.5.9-rc - 2014-10-20
17162 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
17163 series. It disables SSL3 in response to the recent "POODLE" attack
17164 (even though POODLE does not affect Tor). It also works around a crash
17165 bug caused by some operating systems' response to the "POODLE" attack
17166 (which does affect Tor). It also contains a few miscellaneous fixes.
17168 o Major security fixes:
17169 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
17170 today support TLS 1.0 or later, so we can safely turn off support
17171 for this old (and insecure) protocol. Fixes bug 13426.
17173 o Major bugfixes (openssl bug workaround):
17174 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
17175 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
17176 13471. This is a workaround for an OpenSSL bug.
17179 - Disable the sandbox name resolver cache when running tor-resolve:
17180 tor-resolve doesn't use the sandbox code, and turning it on was
17181 breaking attempts to do tor-resolve on a non-default server on
17182 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
17184 o Compilation fixes:
17185 - Build and run correctly on systems like OpenBSD-current that have
17186 patched OpenSSL to remove get_cipher_by_char and/or its
17187 implementations. Fixes issue 13325.
17189 o Downgraded warnings:
17190 - Downgrade the severity of the 'unexpected sendme cell from client'
17191 from 'warn' to 'protocol warning'. Closes ticket 8093.
17194 Changes in version 0.2.4.25 - 2014-10-20
17195 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
17196 (even though POODLE does not affect Tor). It also works around a crash
17197 bug caused by some operating systems' response to the "POODLE" attack
17198 (which does affect Tor).
17200 o Major security fixes (also in 0.2.5.9-rc):
17201 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
17202 today support TLS 1.0 or later, so we can safely turn off support
17203 for this old (and insecure) protocol. Fixes bug 13426.
17205 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
17206 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
17207 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
17208 13471. This is a workaround for an OpenSSL bug.
17211 Changes in version 0.2.5.8-rc - 2014-09-22
17212 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
17213 series. It fixes a bug that affects consistency and speed when
17214 connecting to hidden services, and it updates the location of one of
17215 the directory authorities.
17218 - Clients now send the correct address for their chosen rendezvous
17219 point when trying to access a hidden service. They used to send
17220 the wrong address, which would still work some of the time because
17221 they also sent the identity digest of the rendezvous point, and if
17222 the hidden service happened to try connecting to the rendezvous
17223 point from a relay that already had a connection open to it,
17224 the relay would reuse that connection. Now connections to hidden
17225 services should be more robust and faster. Also, this bug meant
17226 that clients were leaking to the hidden service whether they were
17227 on a little-endian (common) or big-endian (rare) system, which for
17228 some users might have reduced their anonymity. Fixes bug 13151;
17229 bugfix on 0.2.1.5-alpha.
17231 o Directory authority changes:
17232 - Change IP address for gabelmoo (v3 directory authority).
17235 Changes in version 0.2.4.24 - 2014-09-22
17236 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
17237 connecting to hidden services, and it updates the location of one of
17238 the directory authorities.
17241 - Clients now send the correct address for their chosen rendezvous
17242 point when trying to access a hidden service. They used to send
17243 the wrong address, which would still work some of the time because
17244 they also sent the identity digest of the rendezvous point, and if
17245 the hidden service happened to try connecting to the rendezvous
17246 point from a relay that already had a connection open to it,
17247 the relay would reuse that connection. Now connections to hidden
17248 services should be more robust and faster. Also, this bug meant
17249 that clients were leaking to the hidden service whether they were
17250 on a little-endian (common) or big-endian (rare) system, which for
17251 some users might have reduced their anonymity. Fixes bug 13151;
17252 bugfix on 0.2.1.5-alpha.
17254 o Directory authority changes:
17255 - Change IP address for gabelmoo (v3 directory authority).
17257 o Minor features (geoip):
17258 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
17262 Changes in version 0.2.5.7-rc - 2014-09-11
17263 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
17264 release series, and some long-standing bugs related to ORPort reachability
17265 testing and failure to send CREATE cells. It is the first release
17266 candidate for the Tor 0.2.5.x series.
17268 o Major bugfixes (client, startup):
17269 - Start making circuits as soon as DisabledNetwork is turned off.
17270 When Tor started with DisabledNetwork set, it would correctly
17271 conclude that it shouldn't build circuits, but it would mistakenly
17272 cache this conclusion, and continue believing it even when
17273 DisableNetwork is set to 0. Fixes the bug introduced by the fix
17274 for bug 11200; bugfix on 0.2.5.4-alpha.
17275 - Resume expanding abbreviations for command-line options. The fix
17276 for bug 4647 accidentally removed our hack from bug 586 that
17277 rewrote HashedControlPassword to __HashedControlSessionPassword
17278 when it appears on the commandline (which allowed the user to set
17279 her own HashedControlPassword in the torrc file while the
17280 controller generates a fresh session password for each run). Fixes
17281 bug 12948; bugfix on 0.2.5.1-alpha.
17282 - Warn about attempts to run hidden services and relays in the same
17283 process: that's probably not a good idea. Closes ticket 12908.
17285 o Major bugfixes (relay):
17286 - Avoid queuing or sending destroy cells for circuit ID zero when we
17287 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
17288 Found and fixed by "cypherpunks".
17289 - Fix ORPort reachability detection on relays running behind a
17290 proxy, by correctly updating the "local" mark on the controlling
17291 channel when changing the address of an or_connection_t after the
17292 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
17294 o Minor features (bridge):
17295 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
17296 cookie file for the ExtORPort g+r by default.
17298 o Minor features (geoip):
17299 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
17302 o Minor bugfixes (logging):
17303 - Reduce the log severity of the "Pluggable transport proxy does not
17304 provide any needed transports and will not be launched." message,
17305 since Tor Browser includes several ClientTransportPlugin lines in
17306 its torrc-defaults file, leading every Tor Browser user who looks
17307 at her logs to see these notices and wonder if they're dangerous.
17308 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
17309 - Downgrade "Unexpected onionskin length after decryption" warning
17310 to a protocol-warn, since there's nothing relay operators can do
17311 about a client that sends them a malformed create cell. Resolves
17312 bug 12996; bugfix on 0.0.6rc1.
17313 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
17314 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
17315 - When logging information about an EXTEND2 or EXTENDED2 cell, log
17316 their names correctly. Fixes part of bug 12700; bugfix
17318 - When logging information about a relay cell whose command we don't
17319 recognize, log its command as an integer. Fixes part of bug 12700;
17320 bugfix on 0.2.1.10-alpha.
17321 - Escape all strings from the directory connection before logging
17322 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
17324 o Minor bugfixes (controller):
17325 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
17326 bug 12864; bugfix on 0.2.5.1-alpha.
17327 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
17328 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
17331 o Minor bugfixes (compilation):
17332 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
17333 bugfix on 0.2.5.5-alpha.
17334 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
17335 0.2.5.1-alpha. Patch from "NewEraCracker".
17336 - In routerlist_assert_ok(), don't take the address of a
17337 routerinfo's cache_info member unless that routerinfo is non-NULL.
17338 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
17339 - Fix a large number of false positive warnings from the clang
17340 analyzer static analysis tool. This should make real warnings
17341 easier for clang analyzer to find. Patch from "teor". Closes
17344 o Distribution (systemd):
17345 - Verify configuration file via ExecStartPre in the systemd unit
17346 file. Patch from intrigeri; resolves ticket 12730.
17347 - Explicitly disable RunAsDaemon in the systemd unit file. Our
17348 current systemd unit uses "Type = simple", so systemd does not
17349 expect tor to fork. If the user has "RunAsDaemon 1" in their
17350 torrc, then things won't work as expected. This is e.g. the case
17351 on Debian (and derivatives), since there we pass "--defaults-torrc
17352 /usr/share/tor/tor-service-defaults-torrc" (that contains
17353 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
17357 - Adjust the URLs in the README to refer to the new locations of
17358 several documents on the website. Fixes bug 12830. Patch from
17360 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
17364 Changes in version 0.2.5.6-alpha - 2014-07-28
17365 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
17366 risk from guard rotation, and fixes a variety of other issues to get
17367 us closer to a release candidate.
17369 o Major features (also in 0.2.4.23):
17370 - Make the number of entry guards configurable via a new
17371 NumEntryGuards consensus parameter, and the number of directory
17372 guards configurable via a new NumDirectoryGuards consensus
17373 parameter. Implements ticket 12688.
17375 o Major bugfixes (also in 0.2.4.23):
17376 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
17377 implementation that caused incorrect results on 32-bit
17378 implementations when certain malformed inputs were used along with
17379 a small class of private ntor keys. This bug does not currently
17380 appear to allow an attacker to learn private keys or impersonate a
17381 Tor server, but it could provide a means to distinguish 32-bit Tor
17382 implementations from 64-bit Tor implementations. Fixes bug 12694;
17383 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
17387 - Perform circuit cleanup operations even when circuit
17388 construction operations are disabled (because the network is
17389 disabled, or because there isn't enough directory information).
17390 Previously, when we were not building predictive circuits, we
17391 were not closing expired circuits either. Fixes bug 8387; bugfix on
17392 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
17393 became more strict about when we have "enough directory information
17394 to build circuits".
17397 - Authorities now assign the Guard flag to the fastest 25% of the
17398 network (it used to be the fastest 50%). Also raise the consensus
17399 weight that guarantees the Guard flag from 250 to 2000. For the
17400 current network, this results in about 1100 guards, down from 2500.
17401 This step paves the way for moving the number of entry guards
17402 down to 1 (proposal 236) while still providing reasonable expected
17403 performance for most users. Implements ticket 12690.
17404 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
17406 - Slightly enhance the diagnostic message for bug 12184.
17408 o Minor bugfixes (also in 0.2.4.23):
17409 - Warn and drop the circuit if we receive an inbound 'relay early'
17410 cell. Those used to be normal to receive on hidden service circuits
17411 due to bug 1038, but the buggy Tor versions are long gone from
17412 the network so we can afford to resume watching for them. Resolves
17413 the rest of bug 1038; bugfix on 0.2.1.19.
17414 - Correct a confusing error message when trying to extend a circuit
17415 via the control protocol but we don't know a descriptor or
17416 microdescriptor for one of the specified relays. Fixes bug 12718;
17417 bugfix on 0.2.3.1-alpha.
17420 - Fix compilation when building with bufferevents enabled. (This
17421 configuration is still not expected to work, however.)
17422 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
17423 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
17425 - Compile correctly with builds and forks of OpenSSL (such as
17426 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
17427 0.2.1.1-alpha. Patch from "dhill".
17430 Changes in version 0.2.4.23 - 2014-07-28
17431 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
17432 guard rotation, and also backports several important fixes from the
17433 Tor 0.2.5 alpha release series.
17436 - Clients now look at the "usecreatefast" consensus parameter to
17437 decide whether to use CREATE_FAST or CREATE cells for the first hop
17438 of their circuit. This approach can improve security on connections
17439 where Tor's circuit handshake is stronger than the available TLS
17440 connection security levels, but the tradeoff is more computational
17441 load on guard relays. Implements proposal 221. Resolves ticket 9386.
17442 - Make the number of entry guards configurable via a new
17443 NumEntryGuards consensus parameter, and the number of directory
17444 guards configurable via a new NumDirectoryGuards consensus
17445 parameter. Implements ticket 12688.
17448 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
17449 implementation that caused incorrect results on 32-bit
17450 implementations when certain malformed inputs were used along with
17451 a small class of private ntor keys. This bug does not currently
17452 appear to allow an attacker to learn private keys or impersonate a
17453 Tor server, but it could provide a means to distinguish 32-bit Tor
17454 implementations from 64-bit Tor implementations. Fixes bug 12694;
17455 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
17459 - Warn and drop the circuit if we receive an inbound 'relay early'
17460 cell. Those used to be normal to receive on hidden service circuits
17461 due to bug 1038, but the buggy Tor versions are long gone from
17462 the network so we can afford to resume watching for them. Resolves
17463 the rest of bug 1038; bugfix on 0.2.1.19.
17464 - Correct a confusing error message when trying to extend a circuit
17465 via the control protocol but we don't know a descriptor or
17466 microdescriptor for one of the specified relays. Fixes bug 12718;
17467 bugfix on 0.2.3.1-alpha.
17468 - Avoid an illegal read from stack when initializing the TLS
17469 module using a version of OpenSSL without all of the ciphers
17470 used by the v2 link handshake. Fixes bug 12227; bugfix on
17471 0.2.4.8-alpha. Found by "starlight".
17474 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
17478 Changes in version 0.2.5.5-alpha - 2014-06-18
17479 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
17480 0.2.5.x release series, including a couple of DoS issues, some
17481 performance regressions, a large number of bugs affecting the Linux
17482 seccomp2 sandbox code, and various other bugfixes. It also adds
17483 diagnostic bugfixes for a few tricky issues that we're trying to
17486 o Major features (security, traffic analysis resistance):
17487 - Several major improvements to the algorithm used to decide when to
17488 close TLS connections. Previous versions of Tor closed connections
17489 at a fixed interval after the last time a non-padding cell was
17490 sent over the connection, regardless of the target of the
17491 connection. Now, we randomize the intervals by adding up to 50% of
17492 their base value, we measure the length of time since connection
17493 last had at least one circuit, and we allow connections to known
17494 ORs to remain open a little longer (15 minutes instead of 3
17495 minutes minimum). These changes should improve Tor's resistance
17496 against some kinds of traffic analysis, and lower some overhead
17497 from needlessly closed connections. Fixes ticket 6799.
17498 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
17500 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
17501 - Fix a memory leak that could occur if a microdescriptor parse
17502 fails during the tokenizing step. This bug could enable a memory
17503 exhaustion attack by directory servers. Fixes bug 11649; bugfix
17506 o Major bugfixes (security, directory authorities):
17507 - Directory authorities now include a digest of each relay's
17508 identity key as a part of its microdescriptor.
17510 This is a workaround for bug 11743 (reported by "cypherpunks"),
17511 where Tor clients do not support receiving multiple
17512 microdescriptors with the same SHA256 digest in the same
17513 consensus. When clients receive a consensus like this, they only
17514 use one of the relays. Without this fix, a hostile relay could
17515 selectively disable some client use of target relays by
17516 constructing a router descriptor with a different identity and the
17517 same microdescriptor parameters and getting the authorities to
17518 list it in a microdescriptor consensus. This fix prevents an
17519 attacker from causing a microdescriptor collision, because the
17520 router's identity is not forgeable.
17522 o Major bugfixes (relay):
17523 - Use a direct dirport connection when uploading non-anonymous
17524 descriptors to the directory authorities. Previously, relays would
17525 incorrectly use tunnel connections under a fairly wide variety of
17526 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
17527 - When a circuit accidentally has the same circuit ID for its
17528 forward and reverse direction, correctly detect the direction of
17529 cells using that circuit. Previously, this bug made roughly one
17530 circuit in a million non-functional. Fixes bug 12195; this is a
17531 bugfix on every version of Tor.
17533 o Major bugfixes (client, pluggable transports):
17534 - When managing pluggable transports, use OS notification facilities
17535 to learn if they have crashed, and don't attempt to kill any
17536 process that has already exited. Fixes bug 8746; bugfix
17539 o Minor features (diagnostic):
17540 - When logging a warning because of bug 7164, additionally check the
17541 hash table for consistency (as proposed on ticket 11737). This may
17542 help diagnose bug 7164.
17543 - When we log a heartbeat, log how many one-hop circuits we have
17544 that are at least 30 minutes old, and log status information about
17545 a few of them. This is an attempt to track down bug 8387.
17546 - When encountering an unexpected CR while writing text to a file on
17547 Windows, log the name of the file. Should help diagnosing
17549 - Give more specific warnings when a client notices that an onion
17550 handshake has failed. Fixes ticket 9635.
17551 - Add significant new logging code to attempt to diagnose bug 12184,
17552 where relays seem to run out of available circuit IDs.
17553 - Improve the diagnostic log message for bug 8387 even further to
17554 try to improve our odds of figuring out why one-hop directory
17555 circuits sometimes do not get closed.
17557 o Minor features (security, memory management):
17558 - Memory allocation tricks (mempools and buffer freelists) are now
17559 disabled by default. You can turn them back on with
17560 --enable-mempools and --enable-buf-freelists respectively. We're
17561 disabling these features because malloc performance is good enough
17562 on most platforms, and a similar feature in OpenSSL exacerbated
17563 exploitation of the Heartbleed attack. Resolves ticket 11476.
17565 o Minor features (security):
17566 - Apply the secure SipHash-2-4 function to the hash table mapping
17567 circuit IDs and channels to circuits. We missed this one when we
17568 were converting all the other hash functions to use SipHash back
17569 in 0.2.5.3-alpha. Resolves ticket 11750.
17571 o Minor features (build):
17572 - The configure script has a --disable-seccomp option to turn off
17573 support for libseccomp on systems that have it, in case it (or
17574 Tor's use of it) is broken. Resolves ticket 11628.
17576 o Minor features (other):
17577 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
17580 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
17581 - When running a hidden service, do not allow TunneledDirConns 0;
17582 this will keep the hidden service from running, and also
17583 make it publish its descriptors directly over HTTP. Fixes bug 10849;
17584 bugfix on 0.2.1.1-alpha.
17586 o Minor bugfixes (performance):
17587 - Avoid a bug where every successful connection made us recompute
17588 the flag telling us whether we have sufficient information to
17589 build circuits. Previously, we would forget our cached value
17590 whenever we successfully opened a channel (or marked a router as
17591 running or not running for any other reason), regardless of
17592 whether we had previously believed the router to be running. This
17593 forced us to run an expensive update operation far too often.
17594 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
17595 - Avoid using tor_memeq() for checking relay cell integrity. This
17596 removes a possible performance bottleneck. Fixes part of bug
17597 12169; bugfix on 0.2.1.31.
17599 o Minor bugfixes (compilation):
17600 - Fix compilation of test_status.c when building with MVSC. Bugfix
17601 on 0.2.5.4-alpha. Patch from Gisle Vanem.
17602 - Resolve GCC complaints on OpenBSD about discarding constness in
17603 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
17604 on 0.1.1.23. Patch from Dana Koch.
17605 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
17606 treatment of long and time_t as comparable types. Fixes part of
17607 bug 11633. Patch from Dana Koch.
17608 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
17609 11623; bugfix on 0.2.5.3-alpha.
17610 - When deciding whether to build the 64-bit curve25519
17611 implementation, detect platforms where we can compile 128-bit
17612 arithmetic but cannot link it. Fixes bug 11729; bugfix on
17613 0.2.4.8-alpha. Patch from "conradev".
17614 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
17615 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
17616 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
17619 o Minor bugfixes (Directory server):
17620 - When sending a compressed set of descriptors or microdescriptors,
17621 make sure to finalize the zlib stream. Previously, we would write
17622 all the compressed data, but if the last descriptor we wanted to
17623 send was missing or too old, we would not mark the stream as
17624 finished. This caused problems for decompression tools. Fixes bug
17625 11648; bugfix on 0.1.1.23.
17627 o Minor bugfixes (Linux seccomp sandbox):
17628 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
17629 11622; bugfix on 0.2.5.1-alpha.
17630 - Avoid crashing when re-opening listener ports with the seccomp
17631 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
17632 - Avoid crashing with the seccomp sandbox enabled along with
17633 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
17634 - When we receive a SIGHUP with the sandbox enabled, correctly
17635 support rotating our log files. Fixes bug 12032; bugfix
17637 - Avoid crash when running with sandboxing enabled and
17638 DirReqStatistics not disabled. Fixes bug 12035; bugfix
17640 - Fix a "BUG" warning when trying to write bridge-stats files with
17641 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
17643 - Prevent the sandbox from crashing on startup when run with the
17644 --enable-expensive-hardening configuration option. Fixes bug
17645 11477; bugfix on 0.2.5.4-alpha.
17646 - When running with DirPortFrontPage and sandboxing both enabled,
17647 reload the DirPortFrontPage correctly when restarting. Fixes bug
17648 12028; bugfix on 0.2.5.1-alpha.
17649 - Don't try to enable the sandbox when using the Tor binary to check
17650 its configuration, hash a passphrase, or so on. Doing so was
17651 crashing on startup for some users. Fixes bug 11609; bugfix
17653 - Avoid warnings when running with sandboxing and node statistics
17654 enabled at the same time. Fixes part of 12064; bugfix on
17655 0.2.5.1-alpha. Patch from Michael Wolf.
17656 - Avoid warnings when running with sandboxing enabled at the same
17657 time as cookie authentication, hidden services, or directory
17658 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
17659 - Do not allow options that require calls to exec to be enabled
17660 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
17661 bug 12043; bugfix on 0.2.5.1-alpha.
17662 - Handle failures in getpwnam()/getpwuid() when running with the
17663 User option set and the Linux syscall sandbox enabled. Fixes bug
17664 11946; bugfix on 0.2.5.1-alpha.
17665 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
17666 to avoid calling getaddrinfo() after installing the sandbox
17667 filters. Previously, it preloaded a cache with the IPv4 address
17668 for our hostname, and nothing else. Now, it loads the cache with
17669 every address that it used to initialize the Tor process. Fixes
17670 bug 11970; bugfix on 0.2.5.1-alpha.
17672 o Minor bugfixes (pluggable transports):
17673 - Enable the ExtORPortCookieAuthFile option, to allow changing the
17674 default location of the authentication token for the extended OR
17675 Port as used by sever-side pluggable transports. We had
17676 implemented this option before, but the code to make it settable
17677 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
17678 - Avoid another 60-second delay when starting Tor in a pluggable-
17679 transport-using configuration when we already have cached
17680 descriptors for our bridges. Fixes bug 11965; bugfix
17683 o Minor bugfixes (client):
17684 - Avoid "Tried to open a socket with DisableNetwork set" warnings
17685 when starting a client with bridges configured and DisableNetwork
17686 set. (Tor launcher starts Tor with DisableNetwork set the first
17687 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
17689 o Minor bugfixes (testing):
17690 - The Python parts of the test scripts now work on Python 3 as well
17691 as Python 2, so systems where '/usr/bin/python' is Python 3 will
17692 no longer have the tests break. Fixes bug 11608; bugfix
17694 - When looking for versions of python that we could run the tests
17695 with, check for "python2.7" and "python3.3"; previously we were
17696 only looking for "python", "python2", and "python3". Patch from
17697 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
17698 - Fix all valgrind warnings produced by the unit tests. There were
17699 over a thousand memory leak warnings previously, mostly produced
17700 by forgetting to free things in the unit test code. Fixes bug
17701 11618, bugfixes on many versions of Tor.
17703 o Minor bugfixes (tor-fw-helper):
17704 - Give a correct log message when tor-fw-helper fails to launch.
17705 (Previously, we would say something like "tor-fw-helper sent us a
17706 string we could not parse".) Fixes bug 9781; bugfix
17709 o Minor bugfixes (relay, threading):
17710 - Check return code on spawn_func() in cpuworker code, so that we
17711 don't think we've spawned a nonworking cpuworker and write junk to
17712 it forever. Fix related to bug 4345; bugfix on all released Tor
17713 versions. Found by "skruffy".
17714 - Use a pthread_attr to make sure that spawn_func() cannot return an
17715 error while at the same time launching a thread. Fix related to
17716 bug 4345; bugfix on all released Tor versions. Reported
17719 o Minor bugfixes (relay, oom prevention):
17720 - Correctly detect the total available system memory. We tried to do
17721 this in 0.2.5.4-alpha, but the code was set up to always return an
17722 error value, even on success. Fixes bug 11805; bugfix
17725 o Minor bugfixes (relay, other):
17726 - We now drop CREATE cells for already-existent circuit IDs and for
17727 zero-valued circuit IDs, regardless of other factors that might
17728 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
17730 - Avoid an illegal read from stack when initializing the TLS module
17731 using a version of OpenSSL without all of the ciphers used by the
17732 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
17734 - When rejecting DATA cells for stream_id zero, still count them
17735 against the circuit's deliver window so that we don't fail to send
17736 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
17738 o Minor bugfixes (logging):
17739 - Fix a misformatted log message about delayed directory fetches.
17740 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
17741 - Squelch a spurious LD_BUG message "No origin circuit for
17742 successful SOCKS stream" in certain hidden service failure cases;
17746 - Include a tor.service file in contrib/dist for use with systemd.
17747 Some distributions will be able to use this file unmodified;
17748 others will need to tweak it, or write their own. Patch from Jamie
17749 Nguyen; resolves ticket 8368.
17752 - Clean up several option names in the manpage to match their real
17753 names, add the missing documentation for a couple of testing and
17754 directory authority options, remove the documentation for a
17755 V2-directory fetching option that no longer exists. Resolves
17757 - Correct the documentation so that it lists the correct directory
17758 for the stats files. (They are in a subdirectory called "stats",
17760 - In the manpage, move more authority-only options into the
17761 directory authority section so that operators of regular directory
17762 caches don't get confused.
17765 - The contrib directory has been sorted and tidied. Before, it was
17766 an unsorted dumping ground for useful and not-so-useful things.
17767 Now, it is divided based on functionality, and the items which
17768 seemed to be nonfunctional or useless have been removed. Resolves
17769 ticket 8966; based on patches from "rl1987".
17772 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
17773 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
17774 - The TunnelDirConns and PreferTunnelledDirConns options no longer
17775 exist; tunneled directory connections have been available since
17776 0.1.2.5-alpha, and turning them off is not a good idea. This is a
17777 brute-force fix for 10849, where "TunnelDirConns 0" would break
17781 Changes in version 0.2.4.22 - 2014-05-16
17782 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
17783 alpha release series. These include blocking all authority signing
17784 keys that may have been affected by the OpenSSL "heartbleed" bug,
17785 choosing a far more secure set of TLS ciphersuites by default, closing
17786 a couple of memory leaks that could be used to run a target relay out
17787 of RAM, and several others.
17789 o Major features (security, backport from 0.2.5.4-alpha):
17790 - Block authority signing keys that were used on authorities
17791 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
17792 don't have any evidence that these keys _were_ compromised; we're
17793 doing this to be prudent.) Resolves ticket 11464.
17795 o Major bugfixes (security, OOM):
17796 - Fix a memory leak that could occur if a microdescriptor parse
17797 fails during the tokenizing step. This bug could enable a memory
17798 exhaustion attack by directory servers. Fixes bug 11649; bugfix
17801 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
17802 - The relay ciphersuite list is now generated automatically based on
17803 uniform criteria, and includes all OpenSSL ciphersuites with
17804 acceptable strength and forward secrecy. Previously, we had left
17805 some perfectly fine ciphersuites unsupported due to omission or
17806 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
17807 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
17808 - Relays now trust themselves to have a better view than clients of
17809 which TLS ciphersuites are better than others. (Thanks to bug
17810 11513, the relay list is now well-considered, whereas the client
17811 list has been chosen mainly for anti-fingerprinting purposes.)
17812 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
17813 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
17814 AES128. Resolves ticket 11528.
17815 - Clients now try to advertise the same list of ciphersuites as
17816 Firefox 28. This change enables selection of (fast) GCM
17817 ciphersuites, disables some strange old ciphers, and stops
17818 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
17819 Resolves ticket 11438.
17821 o Minor bugfixes (configuration, security):
17822 - When running a hidden service, do not allow TunneledDirConns 0:
17823 trying to set that option together with a hidden service would
17824 otherwise prevent the hidden service from running, and also make
17825 it publish its descriptors directly over HTTP. Fixes bug 10849;
17826 bugfix on 0.2.1.1-alpha.
17828 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
17829 - Avoid sending a garbage value to the controller when a circuit is
17830 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
17832 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
17833 - Stop leaking memory when we successfully resolve a PTR record.
17834 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
17836 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
17837 - Avoid 60-second delays in the bootstrapping process when Tor is
17838 launching for a second time while using bridges. Fixes bug 9229;
17839 bugfix on 0.2.0.3-alpha.
17841 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
17842 - Give the correct URL in the warning message when trying to run a
17843 relay on an ancient version of Windows. Fixes bug 9393.
17845 o Minor bugfixes (compilation):
17846 - Fix a compilation error when compiling with --disable-curve25519.
17847 Fixes bug 9700; bugfix on 0.2.4.17-rc.
17850 - Downgrade the warning severity for the the "md was still
17851 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
17852 for trying to diagnose this bug, and the current warning in
17853 earlier versions of tor achieves nothing useful. Addresses warning
17856 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
17857 - When we run out of usable circuit IDs on a channel, log only one
17858 warning for the whole channel, and describe how many circuits
17859 there were on the channel. Fixes part of ticket 11553.
17861 o Minor features (security, backport from 0.2.5.4-alpha):
17862 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
17863 leave the default at 8GBytes), to better support Raspberry Pi
17864 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
17866 o Documentation (backport from 0.2.5.4-alpha):
17867 - Correctly document that we search for a system torrc file before
17868 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
17872 Changes in version 0.2.5.4-alpha - 2014-04-25
17873 Tor 0.2.5.4-alpha includes several security and performance
17874 improvements for clients and relays, including blacklisting authority
17875 signing keys that were used while susceptible to the OpenSSL
17876 "heartbleed" bug, fixing two expensive functions on busy relays,
17877 improved TLS ciphersuite preference lists, support for run-time
17878 hardening on compilers that support AddressSanitizer, and more work on
17879 the Linux sandbox code.
17881 There are also several usability fixes for clients (especially clients
17882 that use bridges), two new TransPort protocols supported (one on
17883 OpenBSD, one on FreeBSD), and various other bugfixes.
17885 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
17886 have accumulated many known flaws; everyone should upgrade.
17888 o Major features (security):
17889 - If you don't specify MaxMemInQueues yourself, Tor now tries to
17890 pick a good value based on your total system memory. Previously,
17891 the default was always 8 GB. You can still override the default by
17892 setting MaxMemInQueues yourself. Resolves ticket 11396.
17893 - Block authority signing keys that were used on authorities
17894 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
17895 don't have any evidence that these keys _were_ compromised; we're
17896 doing this to be prudent.) Resolves ticket 11464.
17898 o Major features (relay performance):
17899 - Speed up server-side lookups of rendezvous and introduction point
17900 circuits by using hashtables instead of linear searches. These
17901 functions previously accounted between 3 and 7% of CPU usage on
17902 some busy relays. Resolves ticket 9841.
17903 - Avoid wasting CPU when extending a circuit over a channel that is
17904 nearly out of circuit IDs. Previously, we would do a linear scan
17905 over possible circuit IDs before finding one or deciding that we
17906 had exhausted our possibilities. Now, we try at most 64 random
17907 circuit IDs before deciding that we probably won't succeed. Fixes
17908 a possible root cause of ticket 11553.
17910 o Major features (seccomp2 sandbox, Linux only):
17911 - The seccomp2 sandbox can now run a test network for multiple hours
17912 without crashing. The sandbox is still experimental, and more bugs
17913 will probably turn up. To try it, enable "Sandbox 1" on a Linux
17914 host. Resolves ticket 11351.
17915 - Strengthen sandbox code: the sandbox can now test the arguments
17916 for rename(), and blocks _sysctl() entirely. Resolves another part
17918 - When the sandbox blocks a system call, it now tries to log a stack
17919 trace before exiting. Resolves ticket 11465.
17921 o Major bugfixes (TLS cipher selection):
17922 - The relay ciphersuite list is now generated automatically based on
17923 uniform criteria, and includes all OpenSSL ciphersuites with
17924 acceptable strength and forward secrecy. Previously, we had left
17925 some perfectly fine ciphersuites unsupported due to omission or
17926 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
17927 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
17928 - Relays now trust themselves to have a better view than clients of
17929 which TLS ciphersuites are better than others. (Thanks to bug
17930 11513, the relay list is now well-considered, whereas the client
17931 list has been chosen mainly for anti-fingerprinting purposes.)
17932 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
17933 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
17934 AES128. Resolves ticket 11528.
17935 - Clients now try to advertise the same list of ciphersuites as
17936 Firefox 28. This change enables selection of (fast) GCM
17937 ciphersuites, disables some strange old ciphers, and stops
17938 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
17939 Resolves ticket 11438.
17941 o Major bugfixes (bridge client):
17942 - Avoid 60-second delays in the bootstrapping process when Tor is
17943 launching for a second time while using bridges. Fixes bug 9229;
17944 bugfix on 0.2.0.3-alpha.
17946 o Minor features (transparent proxy, *BSD):
17947 - Support FreeBSD's ipfw firewall interface for TransPort ports on
17948 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
17949 10267; patch from "yurivict".
17950 - Support OpenBSD's divert-to rules with the pf firewall for
17951 transparent proxy ports. To enable it, set "TransProxyType
17952 pf-divert". This allows Tor to run a TransPort transparent proxy
17953 port on OpenBSD 4.4 or later without root privileges. See the
17954 pf.conf(5) manual page for information on configuring pf to use
17955 divert-to rules. Closes ticket 10896; patch from Dana Koch.
17957 o Minor features (security):
17958 - New --enable-expensive-hardening option to enable security
17959 hardening options that consume nontrivial amounts of CPU and
17960 memory. Right now, this includes AddressSanitizer and UbSan, which
17961 are supported in newer versions of GCC and Clang. Closes ticket
17964 o Minor features (log verbosity):
17965 - Demote the message that we give when a flushing connection times
17966 out for too long from NOTICE to INFO. It was usually meaningless.
17967 Resolves ticket 5286.
17968 - Don't log so many notice-level bootstrapping messages at startup
17969 about downloading descriptors. Previously, we'd log a notice
17970 whenever we learned about more routers. Now, we only log a notice
17971 at every 5% of progress. Fixes bug 9963.
17972 - Warn less verbosely when receiving a malformed
17973 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
17974 - When we run out of usable circuit IDs on a channel, log only one
17975 warning for the whole channel, and describe how many circuits
17976 there were on the channel. Fixes part of ticket 11553.
17978 o Minor features (relay):
17979 - If a circuit timed out for at least 3 minutes, check if we have a
17980 new external IP address, and publish a new descriptor with the new
17981 IP address if it changed. Resolves ticket 2454.
17983 o Minor features (controller):
17984 - Make the entire exit policy available from the control port via
17985 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
17987 - Because of the fix for ticket 11396, the real limit for memory
17988 usage may no longer match the configured MaxMemInQueues value. The
17989 real limit is now exposed via GETINFO limits/max-mem-in-queues.
17991 o Minor features (bridge client):
17992 - Report a more useful failure message when we can't connect to a
17993 bridge because we don't have the right pluggable transport
17994 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
17996 o Minor features (diagnostic):
17997 - Add more log messages to diagnose bug 7164, which causes
17998 intermittent "microdesc_free() called but md was still referenced"
17999 warnings. We now include more information, to figure out why we
18000 might be cleaning a microdescriptor for being too old if it's
18001 still referenced by a live node_t object.
18003 o Minor bugfixes (client, DNSPort):
18004 - When using DNSPort, try to respond to AAAA requests with AAAA
18005 answers. Previously, we hadn't looked at the request type when
18006 deciding which answer type to prefer. Fixes bug 10468; bugfix on
18008 - When receiving a DNS query for an unsupported record type, reply
18009 with no answer rather than with a NOTIMPL error. This behavior
18010 isn't correct either, but it will break fewer client programs, we
18011 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
18014 o Minor bugfixes (exit relay):
18015 - Stop leaking memory when we successfully resolve a PTR record.
18016 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
18018 o Minor bugfixes (bridge client):
18019 - Stop accepting bridge lines containing hostnames. Doing so would
18020 cause clients to perform DNS requests on the hostnames, which was
18021 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
18022 - Avoid a 60-second delay in the bootstrapping process when a Tor
18023 client with pluggable transports re-reads its configuration at
18024 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
18026 o Minor bugfixes (client, logging during bootstrap):
18027 - Warn only once if we start logging in an unsafe way. Previously,
18028 we complain as many times as we had problems. Fixes bug 9870;
18029 bugfix on 0.2.5.1-alpha.
18030 - Only report the first fatal bootstrap error on a given OR
18031 connection. This stops us from telling the controller bogus error
18032 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
18033 - Be more helpful when trying to run sandboxed on Linux without
18034 libseccomp. Instead of saying "Sandbox is not implemented on this
18035 platform", we now explain that we need to be built with
18036 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
18037 - Avoid generating spurious warnings when starting with
18038 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
18041 o Minor bugfixes (closing OR connections):
18042 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
18043 check if it's an or_connection_t and correctly call
18044 connection_or_close_for_error() rather than
18045 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
18047 - When closing all connections on setting DisableNetwork to 1, use
18048 connection_or_close_normally() rather than closing OR connections
18049 out from under the channel layer. Fixes bug 11306; bugfix on
18052 o Minor bugfixes (controller):
18053 - Avoid sending a garbage value to the controller when a circuit is
18054 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
18056 o Minor bugfixes (tor-fw-helper):
18057 - Allow tor-fw-helper to build again by adding src/ext to its
18058 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
18060 o Minor bugfixes (bridges):
18061 - Avoid potential crashes or bad behavior when launching a
18062 server-side managed proxy with ORPort or ExtORPort temporarily
18063 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
18065 o Minor bugfixes (platform-specific):
18066 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
18067 bug 11426; bugfix on 0.2.5.3-alpha.
18068 - When dumping a malformed directory object to disk, save it in
18069 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
18071 - Don't report failures from make_socket_reuseable() on incoming
18072 sockets on OSX: this can happen when incoming connections close
18073 early. Fixes bug 10081.
18075 o Minor bugfixes (trivial memory leaks):
18076 - Fix a small memory leak when signing a directory object. Fixes bug
18077 11275; bugfix on 0.2.4.13-alpha.
18078 - Free placeholder entries in our circuit table at exit; fixes a
18079 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
18080 - Don't re-initialize a second set of OpenSSL mutexes when starting
18081 up. Previously, we'd make one set of mutexes, and then immediately
18082 replace them with another. Fixes bug 11726; bugfix on
18084 - Resolve some memory leaks found by coverity in the unit tests, on
18085 exit in tor-gencert, and on a failure to compute digests for our
18086 own keys when generating a v3 networkstatus vote. These leaks
18087 should never have affected anyone in practice.
18089 o Minor bugfixes (hidden service):
18090 - Only retry attempts to connect to a chosen rendezvous point 8
18091 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
18093 o Minor bugfixes (misc code correctness):
18094 - Fix various instances of undefined behavior in channeltls.c,
18095 tor_memmem(), and eventdns.c that would cause us to construct
18096 pointers to memory outside an allocated object. (These invalid
18097 pointers were not accessed, but C does not even allow them to
18098 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
18099 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
18100 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
18101 fix some miscellaneous errors in our tests and codebase. Fixes bug
18102 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
18103 - Always check return values for unlink, munmap, UnmapViewOfFile;
18104 check strftime return values more often. In some cases all we can
18105 do is report a warning, but this may help prevent deeper bugs from
18106 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
18108 - Fix numerous warnings from the clang "scan-build" static analyzer.
18109 Some of these are programming style issues; some of them are false
18110 positives that indicated awkward code; some are undefined behavior
18111 cases related to constructing (but not using) invalid pointers;
18112 some are assumptions about API behavior; some are (harmlessly)
18113 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
18114 correct; and one or two are genuine bugs that weren't reachable
18115 from the rest of the program. Fixes bug 8793; bugfixes on many,
18119 - Build the torify.1 manpage again. Previously, we were only trying
18120 to build it when also building tor-fw-helper. That's why we didn't
18121 notice that we'd broken the ability to build it. Fixes bug 11321;
18122 bugfix on 0.2.5.1-alpha.
18123 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
18124 11061; bugfix on 0.2.4.7-alpha.
18125 - Correctly document that we search for a system torrc file before
18126 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
18128 - Resolve warnings from Doxygen.
18130 o Code simplifications and refactoring:
18131 - Remove is_internal_IP() function. Resolves ticket 4645.
18132 - Remove unused function circuit_dump_by_chan from circuitlist.c.
18133 Closes issue 9107; patch from "marek".
18134 - Change our use of the ENUM_BF macro to avoid declarations that
18137 o Deprecated versions:
18138 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
18139 attention for some while. Directory authorities no longer accept
18140 descriptors from relays running any version of Tor prior to Tor
18141 0.2.3.16-alpha. Resolves ticket 11149.
18144 - New macros in test.h to simplify writing mock-functions for unit
18145 tests. Part of ticket 11507. Patch from Dana Koch.
18146 - Complete tests for the status.c module. Resolves ticket 11507.
18147 Patch from Dana Koch.
18150 - Remove all code for the long unused v1 directory protocol.
18151 Resolves ticket 11070.
18154 Changes in version 0.2.5.3-alpha - 2014-03-22
18155 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
18156 two new anti-DoS features for Tor relays, resolves a bug that kept
18157 SOCKS5 support for IPv6 from working, fixes several annoying usability
18158 issues for bridge users, and removes more old code for unused
18161 The Tor 0.2.5.x release series is now in patch-freeze: no feature
18162 patches not already written will be considered for inclusion in 0.2.5.x.
18164 o Major features (relay security, DoS-resistance):
18165 - When deciding whether we have run out of memory and we need to
18166 close circuits, also consider memory allocated in buffers for
18167 streams attached to each circuit.
18169 This change, which extends an anti-DoS feature introduced in
18170 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
18171 better resist more memory-based DoS attacks than before. Since the
18172 MaxMemInCellQueues option now applies to all queues, it is renamed
18173 to MaxMemInQueues. This feature fixes bug 10169.
18174 - Avoid hash-flooding denial-of-service attacks by using the secure
18175 SipHash-2-4 hash function for our hashtables. Without this
18176 feature, an attacker could degrade performance of a targeted
18177 client or server by flooding their data structures with a large
18178 number of entries to be stored at the same hash table position,
18179 thereby slowing down the Tor instance. With this feature, hash
18180 table positions are derived from a randomized cryptographic key,
18181 and an attacker cannot predict which entries will collide. Closes
18183 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
18184 the default at 8GBytes), to better support Raspberry Pi users. Fixes
18185 bug 9686; bugfix on 0.2.4.14-alpha.
18187 o Minor features (bridges, pluggable transports):
18188 - Bridges now write the SHA1 digest of their identity key
18189 fingerprint (that is, a hash of a hash of their public key) to
18190 notice-level logs, and to a new hashed-fingerprint file. This
18191 information will help bridge operators look up their bridge in
18192 Globe and similar tools. Resolves ticket 10884.
18193 - Improve the message that Tor displays when running as a bridge
18194 using pluggable transports without an Extended ORPort listener.
18195 Also, log the message in the log file too. Resolves ticket 11043.
18197 o Minor features (other):
18198 - Add a new option, PredictedPortsRelevanceTime, to control how long
18199 after having received a request to connect to a given port Tor
18200 will try to keep circuits ready in anticipation of future requests
18201 for that port. Patch from "unixninja92"; implements ticket 9176.
18202 - Generate a warning if any ports are listed in the SocksPolicy,
18203 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
18204 AuthDirBadExit options. (These options only support address
18205 ranges.) Fixes part of ticket 11108.
18206 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
18209 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
18210 - Build without warnings under clang 3.4. (We have some macros that
18211 define static functions only some of which will get used later in
18212 the module. Starting with clang 3.4, these give a warning unless the
18213 unused attribute is set on them.) Resolves ticket 10904.
18214 - Fix build warnings about missing "a2x" comment when building the
18215 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
18216 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
18218 o Minor bugfixes (client):
18219 - Improve the log message when we can't connect to a hidden service
18220 because all of the hidden service directory nodes hosting its
18221 descriptor are excluded. Improves on our fix for bug 10722, which
18222 was a bugfix on 0.2.0.10-alpha.
18223 - Raise a control port warning when we fail to connect to all of
18224 our bridges. Previously, we didn't inform the controller, and
18225 the bootstrap process would stall. Fixes bug 11069; bugfix on
18227 - Exit immediately when a process-owning controller exits.
18228 Previously, tor relays would wait for a little while after their
18229 controller exited, as if they had gotten an INT signal -- but this
18230 was problematic, since there was no feedback for the user. To do a
18231 clean shutdown, controllers should send an INT signal and give Tor
18232 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
18233 - Stop attempting to connect to bridges before our pluggable
18234 transports are configured (harmless but resulted in some erroneous
18235 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
18236 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
18237 generating incorrect SOCKS5 responses, and confusing client
18238 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
18240 o Minor bugfixes (relays and bridges):
18241 - Avoid crashing on a malformed resolv.conf file when running a
18242 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
18243 - Non-exit relays no longer launch mock DNS requests to check for
18244 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
18245 non-exit relays stopped servicing DNS requests. Fixes bug 965;
18246 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
18247 - Bridges now report complete directory request statistics. Related
18248 to bug 5824; bugfix on 0.2.2.1-alpha.
18249 - Bridges now never collect statistics that were designed for
18250 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
18251 - Stop giving annoying warning messages when we decide not to launch
18252 a pluggable transport proxy that we don't need (because there are
18253 no bridges configured to use it). Resolves ticket 5018; bugfix
18255 - Give the correct URL in the warning message when trying to run a
18256 relay on an ancient version of Windows. Fixes bug 9393.
18258 o Minor bugfixes (backtrace support):
18259 - Support automatic backtraces on more platforms by using the
18260 "-fasynchronous-unwind-tables" compiler option. This option is
18261 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
18262 is on by default and table generation is not. This doesn't yet
18263 add Windows support; only Linux, OSX, and some BSDs are affected.
18264 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
18265 - Avoid strange behavior if two threads hit failed assertions at the
18266 same time and both try to log backtraces at once. (Previously, if
18267 this had happened, both threads would have stored their intermediate
18268 results in the same buffer, and generated junk outputs.) Reported by
18269 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
18270 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
18271 0.2.5.2-alpha; patch from Nick Hopper.
18273 o Minor bugfixes (unit tests):
18274 - Fix a small bug in the unit tests that might have made the tests
18275 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
18276 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
18279 - Remove all remaining code related to version-0 hidden service
18280 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
18281 the rest of bug 10841.
18284 - Document in the manpage that "KBytes" may also be written as
18285 "kilobytes" or "KB", that "Kbits" may also be written as
18286 "kilobits", and so forth. Closes ticket 9222.
18287 - Document that the ClientOnly config option overrides ORPort.
18288 Our old explanation made ClientOnly sound as though it did
18289 nothing at all. Resolves bug 9059.
18290 - Explain that SocksPolicy, DirPolicy, and similar options don't
18291 take port arguments. Fixes the other part of ticket 11108.
18292 - Fix a comment about the rend_server_descriptor_t.protocols field
18293 to more accurately describe its range. Also, make that field
18294 unsigned, to more accurately reflect its usage. Fixes bug 9099;
18295 bugfix on 0.2.1.5-alpha.
18296 - Fix the manpage's description of HiddenServiceAuthorizeClient:
18297 the maximum client name length is 16, not 19. Fixes bug 11118;
18298 bugfix on 0.2.1.6-alpha.
18300 o Code simplifications and refactoring:
18301 - Get rid of router->address, since in all cases it was just the
18302 string representation of router->addr. Resolves ticket 5528.
18304 o Test infrastructure:
18305 - Update to the latest version of tinytest.
18306 - Improve the tinytest implementation of string operation tests so
18307 that comparisons with NULL strings no longer crash the tests; they
18308 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
18311 Changes in version 0.2.4.21 - 2014-02-28
18312 Tor 0.2.4.21 further improves security against potential adversaries who
18313 find breaking 1024-bit crypto doable, and backports several stability
18314 and robustness patches from the 0.2.5 branch.
18316 o Major features (client security):
18317 - When we choose a path for a 3-hop circuit, make sure it contains
18318 at least one relay that supports the NTor circuit extension
18319 handshake. Otherwise, there is a chance that we're building
18320 a circuit that's worth attacking by an adversary who finds
18321 breaking 1024-bit crypto doable, and that chance changes the game
18322 theory. Implements ticket 9777.
18325 - Do not treat streams that fail with reason
18326 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
18327 since it could also indicate an ENETUNREACH connection error. Fixes
18328 part of bug 10777; bugfix on 0.2.4.8-alpha.
18330 o Code simplification and refactoring:
18331 - Remove data structures which were introduced to implement the
18332 CellStatistics option: they are now redundant with the new timestamp
18333 field in the regular packed_cell_t data structure, which we did
18334 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
18337 - Always clear OpenSSL bignums before freeing them -- even bignums
18338 that don't contain secrets. Resolves ticket 10793. Patch by
18340 - Build without warnings under clang 3.4. (We have some macros that
18341 define static functions only some of which will get used later in
18342 the module. Starting with clang 3.4, these give a warning unless the
18343 unused attribute is set on them.) Resolves ticket 10904.
18344 - Update geoip and geoip6 files to the February 7 2014 Maxmind
18345 GeoLite2 Country database.
18348 - Set the listen() backlog limit to the largest actually supported
18349 on the system, not to the value in a header file. Fixes bug 9716;
18350 bugfix on every released Tor.
18351 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
18352 exit node as a NOROUTE error, not an INTERNAL error, since they
18353 can apparently happen when trying to connect to the wrong sort
18354 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
18355 - Fix build warnings about missing "a2x" comment when building the
18356 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
18357 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
18358 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
18359 not entirely remove it from the connection lists. Fixes bug 9602;
18360 bugfix on 0.2.4.4-alpha.
18361 - Fix a segmentation fault in our benchmark code when running with
18362 Fedora's OpenSSL package, or any other OpenSSL that provides
18363 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
18364 - Turn "circuit handshake stats since last time" log messages into a
18365 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
18367 o Documentation fixes:
18368 - Document that all but one DirPort entry must have the NoAdvertise
18369 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
18372 Changes in version 0.2.5.2-alpha - 2014-02-13
18373 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
18374 like the "poor random number generation" fix and the "building too many
18375 circuits" fix. It also further improves security against potential
18376 adversaries who find breaking 1024-bit crypto doable, and launches
18377 pluggable transports on demand (which gets us closer to integrating
18378 pluggable transport support by default -- not to be confused with Tor
18379 bundles enabling pluggable transports and bridges by default).
18381 o Major features (client security):
18382 - When we choose a path for a 3-hop circuit, make sure it contains
18383 at least one relay that supports the NTor circuit extension
18384 handshake. Otherwise, there is a chance that we're building
18385 a circuit that's worth attacking by an adversary who finds
18386 breaking 1024-bit crypto doable, and that chance changes the game
18387 theory. Implements ticket 9777.
18388 - Clients now look at the "usecreatefast" consensus parameter to
18389 decide whether to use CREATE_FAST or CREATE cells for the first hop
18390 of their circuit. This approach can improve security on connections
18391 where Tor's circuit handshake is stronger than the available TLS
18392 connection security levels, but the tradeoff is more computational
18393 load on guard relays. Implements proposal 221. Resolves ticket 9386.
18395 o Major features (bridges):
18396 - Don't launch pluggable transport proxies if we don't have any
18397 bridges configured that would use them. Now we can list many
18398 pluggable transports, and Tor will dynamically start one when it
18399 hears a bridge address that needs it. Resolves ticket 5018.
18400 - The bridge directory authority now assigns status flags (Stable,
18401 Guard, etc) to bridges based on thresholds calculated over all
18402 Running bridges. Now bridgedb can finally make use of its features
18403 to e.g. include at least one Stable bridge in its answers. Fixes
18406 o Major features (other):
18407 - Extend ORCONN controller event to include an "ID" parameter,
18408 and add four new controller event types CONN_BW, CIRC_BW,
18409 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
18410 The new events are emitted in private Tor networks only, with the
18411 goal of being able to better track performance and load during
18412 full-network simulations. Implements proposal 218 and ticket 7359.
18413 - On some platforms (currently: recent OSX versions, glibc-based
18414 platforms that support the ELF format, and a few other
18415 Unix-like operating systems), Tor can now dump stack traces
18416 when a crash occurs or an assertion fails. By default, traces
18417 are dumped to stderr (if possible) and to any logs that are
18418 reporting errors. Implements ticket 9299.
18421 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
18422 not entirely remove it from the connection lists. Fixes bug 9602;
18423 bugfix on 0.2.4.4-alpha.
18424 - Do not treat streams that fail with reason
18425 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
18426 since it could also indicate an ENETUNREACH connection error. Fixes
18427 part of bug 10777; bugfix on 0.2.4.8-alpha.
18429 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
18430 - Do not allow OpenSSL engines to replace the PRNG, even when
18431 HardwareAccel is set. The only default builtin PRNG engine uses
18432 the Intel RDRAND instruction to replace the entire PRNG, and
18433 ignores all attempts to seed it with more entropy. That's
18434 cryptographically stupid: the right response to a new alleged
18435 entropy source is never to discard all previously used entropy
18436 sources. Fixes bug 10402; works around behavior introduced in
18437 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
18439 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
18440 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
18441 - Avoid launching spurious extra circuits when a stream is pending.
18442 This fixes a bug where any circuit that _wasn't_ unusable for new
18443 streams would be treated as if it were, causing extra circuits to
18444 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
18446 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
18447 - No longer stop reading or writing on cpuworker connections when
18448 our rate limiting buckets go empty. Now we should handle circuit
18449 handshake requests more promptly. Resolves bug 9731.
18450 - Stop trying to bootstrap all our directory information from
18451 only our first guard. Discovered while fixing bug 9946; bugfix
18454 o Minor features (bridges, pluggable transports):
18455 - Add threshold cutoffs to the networkstatus document created by
18456 the Bridge Authority. Fixes bug 1117.
18457 - On Windows, spawn background processes using the CREATE_NO_WINDOW
18458 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
18459 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
18460 Vidalia set this option for us.) Implements ticket 10297.
18462 o Minor features (security):
18463 - Always clear OpenSSL bignums before freeing them -- even bignums
18464 that don't contain secrets. Resolves ticket 10793. Patch by
18467 o Minor features (config options and command line):
18468 - Add an --allow-missing-torrc commandline option that tells Tor to
18469 run even if the configuration file specified by -f is not available.
18470 Implements ticket 10060.
18471 - Add support for the TPROXY transparent proxying facility on Linux.
18472 See documentation for the new TransProxyType option for more
18473 details. Implementation by "thomo". Closes ticket 10582.
18475 o Minor features (controller):
18476 - Add a new "HS_DESC" controller event that reports activities
18477 related to hidden service descriptors. Resolves ticket 8510.
18478 - New "DROPGUARDS" controller command to forget all current entry
18479 guards. Not recommended for ordinary use, since replacing guards
18480 too frequently makes several attacks easier. Resolves ticket 9934;
18483 o Minor features (build):
18484 - Assume that a user using ./configure --host wants to cross-compile,
18485 and give an error if we cannot find a properly named
18486 tool-chain. Add a --disable-tool-name-check option to proceed
18487 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
18488 - If we run ./configure and the compiler recognizes -fstack-protector
18489 but the linker rejects it, warn the user about a potentially missing
18490 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
18492 o Minor features (testing):
18493 - If Python is installed, "make check" now runs extra tests beyond
18494 the unit test scripts.
18495 - When bootstrapping a test network, sometimes very few relays get
18496 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
18497 specify a set of relays which should be voted Guard regardless of
18498 their uptime or bandwidth. Addresses ticket 9206.
18500 o Minor features (log messages):
18501 - When ServerTransportPlugin is set on a bridge, Tor can write more
18502 useful statistics about bridge use in its extrainfo descriptors,
18503 but only if the Extended ORPort ("ExtORPort") is set too. Add a
18504 log message to inform the user in this case. Resolves ticket 9651.
18505 - When receiving a new controller connection, log the origin address.
18506 Resolves ticket 9698; patch from "sigpipe".
18507 - When logging OpenSSL engine status at startup, log the status of
18508 more engines. Fixes ticket 10043; patch from Joshua Datko.
18509 - Turn "circuit handshake stats since last time" log messages into a
18510 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
18512 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
18513 - Improve the circuit queue out-of-memory handler. Previously, when
18514 we ran low on memory, we'd close whichever circuits had the most
18515 queued cells. Now, we close those that have the *oldest* queued
18516 cells, on the theory that those are most responsible for us
18517 running low on memory. Based on analysis from a forthcoming paper
18518 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
18519 - Generate bootstrapping status update events correctly when fetching
18520 microdescriptors. Fixes bug 9927.
18521 - Update to the October 2 2013 Maxmind GeoLite Country database.
18523 o Minor bugfixes (clients):
18524 - When closing a channel that has already been open, do not close
18525 pending circuits that were waiting to connect to the same relay.
18526 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
18529 o Minor bugfixes (relays):
18530 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
18531 exit node as a NOROUTE error, not an INTERNAL error, since they
18532 can apparently happen when trying to connect to the wrong sort
18533 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
18535 o Minor bugfixes (bridges):
18536 - Fix a bug where the first connection works to a bridge that uses a
18537 pluggable transport with client-side parameters, but we don't send
18538 the client-side parameters on subsequent connections. (We don't
18539 use any pluggable transports with client-side parameters yet,
18540 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
18541 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
18543 o Minor bugfixes (node selection):
18544 - If ExcludeNodes is set, consider non-excluded hidden service
18545 directory servers before excluded ones. Do not consider excluded
18546 hidden service directory servers at all if StrictNodes is
18547 set. (Previously, we would sometimes decide to connect to those
18548 servers, and then realize before we initiated a connection that
18549 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
18550 Reported by "mr-4".
18551 - If we set the ExitNodes option but it doesn't include any nodes
18552 that have the Exit flag, we would choose not to bootstrap. Now we
18553 bootstrap so long as ExitNodes includes nodes which can exit to
18554 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
18556 o Minor bugfixes (controller and command-line):
18557 - If changing a config option via "setconf" fails in a recoverable
18558 way, we used to nonetheless write our new control ports to the
18559 file described by the "ControlPortWriteToFile" option. Now we only
18560 write out that file if we successfully switch to the new config
18561 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
18562 - When a command-line option such as --version or --help that
18563 ordinarily implies --hush appears on the command line along with
18564 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
18565 only if it appeared later on the command line. Fixes bug 9578;
18566 bugfix on 0.2.5.1-alpha.
18568 o Minor bugfixes (code correctness):
18569 - Previously we used two temporary files when writing descriptors to
18570 disk; now we only use one. Fixes bug 1376.
18571 - Remove an erroneous (but impossible and thus harmless) pointer
18572 comparison that would have allowed compilers to skip a bounds
18573 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
18574 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
18575 - Fix an always-true assertion in pluggable transports code so it
18576 actually checks what it was trying to check. Fixes bug 10046;
18577 bugfix on 0.2.3.9-alpha. Found by "dcb".
18579 o Minor bugfixes (protocol correctness):
18580 - When receiving a VERSIONS cell with an odd number of bytes, close
18581 the connection immediately since the cell is malformed. Fixes bug
18582 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
18585 o Minor bugfixes (build):
18586 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
18587 turned off (that is, without support for v2 link handshakes). Fixes
18588 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
18589 - Fix compilation warnings and startup issues when running with
18590 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
18592 - Fix compilation on Solaris 9, which didn't like us having an
18593 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
18595 o Minor bugfixes (testing):
18596 - Fix a segmentation fault in our benchmark code when running with
18597 Fedora's OpenSSL package, or any other OpenSSL that provides
18598 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
18600 o Minor bugfixes (log messages):
18601 - Fix a bug where clients using bridges would report themselves
18602 as 50% bootstrapped even without a live consensus document.
18603 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
18604 - Suppress a warning where, if there's only one directory authority
18605 in the network, we would complain that votes and signatures cannot
18606 be uploaded to other directory authorities. Fixes bug 10842;
18607 bugfix on 0.2.2.26-beta.
18608 - Report bootstrapping progress correctly when we're downloading
18609 microdescriptors. We had updated our "do we have enough microdescs
18610 to begin building circuits?" logic most recently in 0.2.4.10-alpha
18611 (see bug 5956), but we left the bootstrap status event logic at
18612 "how far through getting 1/4 of them are we?" Fixes bug 9958;
18613 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
18615 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
18616 - Avoid a crash bug when starting with a corrupted microdescriptor
18617 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
18618 - If we fail to dump a previously cached microdescriptor to disk, avoid
18619 freeing duplicate data later on. Fixes bug 10423; bugfix on
18620 0.2.4.13-alpha. Spotted by "bobnomnom".
18622 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
18623 - Correctly log long IPv6 exit policies, instead of truncating them
18624 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
18625 - Our default TLS ecdhe groups were backwards: we meant to be using
18626 P224 for relays (for performance win) and P256 for bridges (since
18627 it is more common in the wild). Instead we had it backwards. After
18628 reconsideration, we decided that the default should be P256 on all
18629 hosts, since its security is probably better, and since P224 is
18630 reportedly used quite little in the wild. Found by "skruffy" on
18631 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
18632 - Free directory authority certificate download statuses on exit
18633 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
18635 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
18636 - If the guard we choose first doesn't answer, we would try the
18637 second guard, but once we connected to the second guard we would
18638 abandon it and retry the first one, slowing down bootstrapping.
18639 The fix is to treat all our initially chosen guards as acceptable
18640 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
18641 - Fix an assertion failure that would occur when disabling the
18642 ORPort setting on a running Tor process while accounting was
18643 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
18644 - When examining the list of network interfaces to find our address,
18645 do not consider non-running or disabled network interfaces. Fixes
18646 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
18647 - Avoid an off-by-one error when checking buffer boundaries when
18648 formatting the exit status of a pluggable transport helper.
18649 This is probably not an exploitable bug, but better safe than
18650 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
18653 o Removed code and features:
18654 - Clients now reject any directory authority certificates lacking
18655 a dir-key-crosscert element. These have been included since
18656 0.2.1.9-alpha, so there's no real reason for them to be optional
18657 any longer. Completes proposal 157. Resolves ticket 10162.
18658 - Remove all code that existed to support the v2 directory system,
18659 since there are no longer any v2 directory authorities. Resolves
18661 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
18662 options, which were used for designating authorities as "Hidden
18663 service authorities". There has been no use of hidden service
18664 authorities since 0.2.2.1-alpha, when we stopped uploading or
18665 downloading v0 hidden service descriptors. Fixes bug 10881; also
18666 part of a fix for bug 10841.
18668 o Code simplification and refactoring:
18669 - Remove some old fallback code designed to keep Tor clients working
18670 in a network with only two working relays. Elsewhere in the code we
18671 have long since stopped supporting such networks, so there wasn't
18672 much point in keeping it around. Addresses ticket 9926.
18673 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
18674 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
18675 - Remove data structures which were introduced to implement the
18676 CellStatistics option: they are now redundant with the addition
18677 of a timestamp to the regular packed_cell_t data structure, which
18678 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
18681 o Documentation (man page) fixes:
18682 - Update manpage to describe some of the files you can expect to
18683 find in Tor's DataDirectory. Addresses ticket 9839.
18684 - Document that all but one DirPort entry must have the NoAdvertise
18685 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
18687 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
18688 - Clarify the usage and risks of setting the ContactInfo torrc line
18689 for your relay or bridge. Resolves ticket 9854.
18690 - Add anchors to the manpage so we can link to the html version of
18691 the documentation for specific options. Resolves ticket 9866.
18692 - Replace remaining references to DirServer in man page and
18693 log entries. Resolves ticket 10124.
18696 - Make the "tor-gencert" tool used by directory authority operators
18697 create 2048-bit signing keys by default (rather than 1024-bit, since
18698 1024-bit is uncomfortably small these days). Addresses ticket 10324.
18701 Changes in version 0.2.4.20 - 2013-12-22
18702 Tor 0.2.4.20 fixes potentially poor random number generation for users
18703 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
18704 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
18705 and 4) have no state file in their DataDirectory (as would happen on
18706 first start). Users who generated relay or hidden service identity
18707 keys in such a situation should discard them and generate new ones.
18709 This release also fixes a logic error that caused Tor clients to build
18710 many more preemptive circuits than they actually need.
18713 - Do not allow OpenSSL engines to replace the PRNG, even when
18714 HardwareAccel is set. The only default builtin PRNG engine uses
18715 the Intel RDRAND instruction to replace the entire PRNG, and
18716 ignores all attempts to seed it with more entropy. That's
18717 cryptographically stupid: the right response to a new alleged
18718 entropy source is never to discard all previously used entropy
18719 sources. Fixes bug 10402; works around behavior introduced in
18720 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
18722 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
18723 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
18724 - Avoid launching spurious extra circuits when a stream is pending.
18725 This fixes a bug where any circuit that _wasn't_ unusable for new
18726 streams would be treated as if it were, causing extra circuits to
18727 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
18730 - Avoid a crash bug when starting with a corrupted microdescriptor
18731 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
18732 - If we fail to dump a previously cached microdescriptor to disk, avoid
18733 freeing duplicate data later on. Fixes bug 10423; bugfix on
18734 0.2.4.13-alpha. Spotted by "bobnomnom".
18737 Changes in version 0.2.4.19 - 2013-12-11
18738 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
18739 (1986-2013). Aaron worked on diverse projects including helping to guide
18740 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
18741 transparency to the U.S government's PACER documents, and contributing
18742 design and development for Tor and Tor2Web. Aaron was one of the latest
18743 martyrs in our collective fight for civil liberties and human rights,
18744 and his death is all the more painful because he was one of us.
18746 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
18747 a new circuit handshake and link encryption that use ECC to provide
18748 better security and efficiency; makes relays better manage circuit
18749 creation requests; uses "directory guards" to reduce client enumeration
18750 risks; makes bridges collect and report statistics about the pluggable
18751 transports they support; cleans up and improves our geoip database;
18752 gets much closer to IPv6 support for clients, bridges, and relays; makes
18753 directory authorities use measured bandwidths rather than advertised
18754 ones when computing flags and thresholds; disables client-side DNS
18755 caching to reduce tracking risks; and fixes a big bug in bridge
18756 reachability testing. This release introduces two new design
18757 abstractions in the code: a new "channel" abstraction between circuits
18758 and or_connections to allow for implementing alternate relay-to-relay
18759 transports, and a new "circuitmux" abstraction storing the queue of
18760 circuits for a channel. The release also includes many stability,
18761 security, and privacy fixes.
18764 Changes in version 0.2.4.18-rc - 2013-11-16
18765 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
18766 series. It takes a variety of fixes from the 0.2.5.x branch to improve
18767 stability, performance, and better handling of edge cases.
18770 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
18771 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
18772 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
18773 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
18774 them to solve bug 6033.)
18777 - No longer stop reading or writing on cpuworker connections when
18778 our rate limiting buckets go empty. Now we should handle circuit
18779 handshake requests more promptly. Resolves bug 9731.
18780 - If we are unable to save a microdescriptor to the journal, do not
18781 drop it from memory and then reattempt downloading it. Fixes bug
18782 9645; bugfix on 0.2.2.6-alpha.
18783 - Stop trying to bootstrap all our directory information from
18784 only our first guard. Discovered while fixing bug 9946; bugfix
18786 - The new channel code sometimes lost track of in-progress circuits,
18787 causing long-running clients to stop building new circuits. The
18788 fix is to always call circuit_n_chan_done(chan, 0) from
18789 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
18791 o Minor bugfixes (on 0.2.4.x):
18792 - Correctly log long IPv6 exit policies, instead of truncating them
18793 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
18794 - Our default TLS ecdhe groups were backwards: we meant to be using
18795 P224 for relays (for performance win) and P256 for bridges (since
18796 it is more common in the wild). Instead we had it backwards. After
18797 reconsideration, we decided that the default should be P256 on all
18798 hosts, since its security is probably better, and since P224 is
18799 reportedly used quite little in the wild. Found by "skruffy" on
18800 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
18801 - Free directory authority certificate download statuses on exit
18802 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
18804 o Minor bugfixes (on 0.2.3.x and earlier):
18805 - If the guard we choose first doesn't answer, we would try the
18806 second guard, but once we connected to the second guard we would
18807 abandon it and retry the first one, slowing down bootstrapping.
18808 The fix is to treat all our initially chosen guards as acceptable
18809 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
18810 - Fix an assertion failure that would occur when disabling the
18811 ORPort setting on a running Tor process while accounting was
18812 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
18813 - When examining the list of network interfaces to find our address,
18814 do not consider non-running or disabled network interfaces. Fixes
18815 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
18816 - Avoid an off-by-one error when checking buffer boundaries when
18817 formatting the exit status of a pluggable transport helper.
18818 This is probably not an exploitable bug, but better safe than
18819 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
18822 o Minor features (protecting client timestamps):
18823 - Clients no longer send timestamps in their NETINFO cells. These were
18824 not used for anything, and they provided one small way for clients
18825 to be distinguished from each other as they moved from network to
18826 network or behind NAT. Implements part of proposal 222.
18827 - Clients now round timestamps in INTRODUCE cells down to the nearest
18828 10 minutes. If a new Support022HiddenServices option is set to 0, or
18829 if it's set to "auto" and the feature is disabled in the consensus,
18830 the timestamp is sent as 0 instead. Implements part of proposal 222.
18831 - Stop sending timestamps in AUTHENTICATE cells. This is not such
18832 a big deal from a security point of view, but it achieves no actual
18833 good purpose, and isn't needed. Implements part of proposal 222.
18834 - Reduce down accuracy of timestamps in hidden service descriptors.
18835 Implements part of proposal 222.
18837 o Minor features (other):
18838 - Improve the circuit queue out-of-memory handler. Previously, when
18839 we ran low on memory, we'd close whichever circuits had the most
18840 queued cells. Now, we close those that have the *oldest* queued
18841 cells, on the theory that those are most responsible for us
18842 running low on memory. Based on analysis from a forthcoming paper
18843 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
18844 - Generate bootstrapping status update events correctly when fetching
18845 microdescriptors. Fixes bug 9927.
18846 - Update to the October 2 2013 Maxmind GeoLite Country database.
18848 o Documentation fixes:
18849 - Clarify the usage and risks of setting the ContactInfo torrc line
18850 for your relay or bridge. Resolves ticket 9854.
18851 - Add anchors to the manpage so we can link to the html version of
18852 the documentation for specific options. Resolves ticket 9866.
18853 - Replace remaining references to DirServer in man page and
18854 log entries. Resolves ticket 10124.
18857 Changes in version 0.2.5.1-alpha - 2013-10-02
18858 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
18859 on Linux, allows bridges that offer pluggable transports to report usage
18860 statistics, fixes many issues to make testing easier, and provides
18861 a pile of minor features and bugfixes that have been waiting for a
18862 release of the new branch.
18864 This is the first alpha release in a new series, so expect there to
18865 be bugs. Users who would rather test out a more stable branch should
18866 stay with 0.2.4.x for now.
18868 o Major features (security):
18869 - Use the seccomp2 syscall filtering facility on Linux to limit
18870 which system calls Tor can invoke. This is an experimental,
18871 Linux-only feature to provide defense-in-depth against unknown
18872 attacks. To try turning it on, set "Sandbox 1" in your torrc
18873 file. Please be ready to report bugs. We hope to add support
18874 for better sandboxing in the future, including more fine-grained
18875 filters, better division of responsibility, and support for more
18876 platforms. This work has been done by Cristian-Matei Toader for
18877 Google Summer of Code.
18878 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
18879 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
18880 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
18881 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
18882 them to solve bug 6033.)
18884 o Major features (other):
18885 - Add support for passing arguments to managed pluggable transport
18886 proxies. Implements ticket 3594.
18887 - Bridges now track GeoIP information and the number of their users
18888 even when pluggable transports are in use, and report usage
18889 statistics in their extra-info descriptors. Resolves tickets 4773
18891 - Make testing Tor networks bootstrap better: lower directory fetch
18892 retry schedules and maximum interval without directory requests,
18893 and raise maximum download tries. Implements ticket 6752.
18894 - Add make target 'test-network' to run tests on a Chutney network.
18895 Implements ticket 8530.
18896 - The ntor handshake is now on-by-default, no matter what the
18897 directory authorities recommend. Implements ticket 8561.
18900 - Instead of writing destroy cells directly to outgoing connection
18901 buffers, queue them and intersperse them with other outgoing cells.
18902 This can prevent a set of resource starvation conditions where too
18903 many pending destroy cells prevent data cells from actually getting
18904 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
18905 bugfix on 0.2.0.1-alpha.
18906 - If we are unable to save a microdescriptor to the journal, do not
18907 drop it from memory and then reattempt downloading it. Fixes bug
18908 9645; bugfix on 0.2.2.6-alpha.
18909 - The new channel code sometimes lost track of in-progress circuits,
18910 causing long-running clients to stop building new circuits. The
18911 fix is to always call circuit_n_chan_done(chan, 0) from
18912 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
18915 - Tor now builds each source file in two modes: a mode that avoids
18916 exposing identifiers needlessly, and another mode that exposes
18917 more identifiers for testing. This lets the compiler do better at
18918 optimizing the production code, while enabling us to take more
18919 radical measures to let the unit tests test things.
18920 - The production builds no longer include functions used only in
18921 the unit tests; all functions exposed from a module only for
18922 unit-testing are now static in production builds.
18923 - Add an --enable-coverage configuration option to make the unit
18924 tests (and a new src/or/tor-cov target) to build with gcov test
18928 - We now have rudimentary function mocking support that our unit
18929 tests can use to test functions in isolation. Function mocking
18930 lets the tests temporarily replace a function's dependencies with
18931 stub functions, so that the tests can check the function without
18932 invoking the other functions it calls.
18933 - Add more unit tests for the <circid,channel>->circuit map, and
18934 the destroy-cell-tracking code to fix bug 7912.
18935 - Unit tests for failing cases of the TAP onion handshake.
18936 - More unit tests for address-manipulation functions.
18938 o Minor features (protecting client timestamps):
18939 - Clients no longer send timestamps in their NETINFO cells. These were
18940 not used for anything, and they provided one small way for clients
18941 to be distinguished from each other as they moved from network to
18942 network or behind NAT. Implements part of proposal 222.
18943 - Clients now round timestamps in INTRODUCE cells down to the nearest
18944 10 minutes. If a new Support022HiddenServices option is set to 0, or
18945 if it's set to "auto" and the feature is disabled in the consensus,
18946 the timestamp is sent as 0 instead. Implements part of proposal 222.
18947 - Stop sending timestamps in AUTHENTICATE cells. This is not such
18948 a big deal from a security point of view, but it achieves no actual
18949 good purpose, and isn't needed. Implements part of proposal 222.
18950 - Reduce down accuracy of timestamps in hidden service descriptors.
18951 Implements part of proposal 222.
18953 o Minor features (config options):
18954 - Config (torrc) lines now handle fingerprints which are missing
18955 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
18956 - Support a --dump-config option to print some or all of the
18957 configured options. Mainly useful for debugging the command-line
18958 option parsing code. Helps resolve ticket 4647.
18959 - Raise awareness of safer logging: notify user of potentially
18960 unsafe config options, like logging more verbosely than severity
18961 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
18962 - Add a new configuration option TestingV3AuthVotingStartOffset
18963 that bootstraps a network faster by changing the timing for
18964 consensus votes. Addresses ticket 8532.
18965 - Add a new torrc option "ServerTransportOptions" that allows
18966 bridge operators to pass configuration parameters to their
18967 pluggable transports. Resolves ticket 8929.
18968 - The config (torrc) file now accepts bandwidth and space limits in
18969 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
18970 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
18973 o Minor features (build):
18974 - Add support for `--library-versions` flag. Implements ticket 6384.
18975 - Return the "unexpected sendme" warnings to a warn severity, but make
18976 them rate limited, to help diagnose ticket 8093.
18977 - Detect a missing asciidoc, and warn the user about it, during
18978 configure rather than at build time. Fixes issue 6506. Patch from
18981 o Minor features (other):
18982 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
18983 sockets in a single system call. Implements ticket 5129.
18984 - Log current accounting state (bytes sent and received + remaining
18985 time for the current accounting period) in the relay's heartbeat
18986 message. Implements ticket 5526; patch from Peter Retzlaff.
18987 - Implement the TRANSPORT_LAUNCHED control port event that
18988 notifies controllers about new launched pluggable
18989 transports. Resolves ticket 5609.
18990 - If we're using the pure-C 32-bit curve25519_donna implementation
18991 of curve25519, build it with the -fomit-frame-pointer option to
18992 make it go faster on register-starved hosts. This improves our
18993 handshake performance by about 6% on i386 hosts without nacl.
18994 Closes ticket 8109.
18995 - Update to the September 4 2013 Maxmind GeoLite Country database.
18998 - Set the listen() backlog limit to the largest actually supported
18999 on the system, not to the value in a header file. Fixes bug 9716;
19000 bugfix on every released Tor.
19001 - No longer accept malformed http headers when parsing urls from
19002 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
19003 bugfix on 0.0.6pre1.
19004 - In munge_extrainfo_into_routerinfo(), check the return value of
19005 memchr(). This would have been a serious issue if we ever passed
19006 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
19008 - On the chance that somebody manages to build Tor on a
19009 platform where time_t is unsigned, correct the way that
19010 microdesc_add_to_cache() handles negative time arguments.
19011 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
19012 - Reject relative control socket paths and emit a warning. Previously,
19013 single-component control socket paths would be rejected, but Tor
19014 would not log why it could not validate the config. Fixes bug 9258;
19015 bugfix on 0.2.3.16-alpha.
19017 o Minor bugfixes (command line):
19018 - Use a single command-line parser for parsing torrc options on the
19019 command line and for finding special command-line options to avoid
19020 inconsistent behavior for torrc option arguments that have the same
19021 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
19023 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
19024 9573; bugfix on 0.0.9pre5.
19026 o Minor fixes (build, auxiliary programs):
19027 - Stop preprocessing the "torify" script with autoconf, since
19028 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
19030 - The tor-fw-helper program now follows the standard convention and
19031 exits with status code "0" on success. Fixes bug 9030; bugfix on
19032 0.2.3.1-alpha. Patch by Arlo Breault.
19033 - Corrected ./configure advice for what openssl dev package you should
19034 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
19036 o Minor code improvements:
19037 - Remove constants and tests for PKCS1 padding; it's insecure and
19038 shouldn't be used for anything new. Fixes bug 8792; patch
19040 - Remove instances of strcpy() from the unit tests. They weren't
19041 hurting anything, since they were only in the unit tests, but it's
19042 embarrassing to have strcpy() in the code at all, and some analysis
19043 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
19044 0.2.3.8-alpha. Patch from Arlo Breault.
19046 o Removed features:
19047 - Remove migration code from when we renamed the "cached-routers"
19048 file to "cached-descriptors" back in 0.2.0.8-alpha. This
19049 incidentally resolves ticket 6502 by cleaning up the related code
19050 a bit. Patch from Akshay Hebbar.
19052 o Code simplification and refactoring:
19053 - Extract the common duplicated code for creating a subdirectory
19054 of the data directory and writing to a file in it. Fixes ticket
19055 4282; patch from Peter Retzlaff.
19056 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
19057 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
19058 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
19059 - Add a set of accessor functions for the circuit timeout data
19060 structure. Fixes ticket 6153; patch from "piet".
19061 - Clean up exit paths from connection_listener_new(). Closes ticket
19062 8789. Patch from Arlo Breault.
19063 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
19064 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
19065 - Use a doubly-linked list to implement the global circuit list.
19066 Resolves ticket 9108. Patch from Marek Majkowski.
19067 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
19070 Changes in version 0.2.4.17-rc - 2013-09-05
19071 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
19072 series. It adds an emergency step to help us tolerate the massive
19073 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
19074 circuit-level handshakes now effectively jump the queue compared to
19075 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
19076 big bug hindering bridge reachability tests.
19079 - Relays now process the new "NTor" circuit-level handshake requests
19080 with higher priority than the old "TAP" circuit-level handshake
19081 requests. We still process some TAP requests to not totally starve
19082 0.2.3 clients when NTor becomes popular. A new consensus parameter
19083 "NumNTorsPerTAP" lets us tune the balance later if we need to.
19084 Implements ticket 9574.
19087 - If the circuit build timeout logic is disabled (via the consensus,
19088 or because we are an authority), then don't build testing circuits.
19089 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
19090 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
19091 previously they did not, which prevented them from receiving
19092 successful connections from relays for self-test or bandwidth
19093 testing. Also, when a relay is extending a circuit to a bridge,
19094 it needs to send a NETINFO cell, even when the bridge hasn't sent
19095 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
19096 - If the time to download the next old-style networkstatus is in
19097 the future, do not decline to consider whether to download the
19098 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
19102 - Avoid double-closing the listener socket in our socketpair()
19103 replacement (used on Windows) in the case where the addresses on
19104 our opened sockets don't match what we expected. Fixes bug 9400;
19105 bugfix on 0.0.2pre7. Found by Coverity.
19107 o Minor fixes (config options):
19108 - Avoid overflows when the user sets MaxCircuitDirtiness to a
19109 ridiculously high value, by imposing a (ridiculously high) 30-day
19110 maximum on MaxCircuitDirtiness.
19111 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
19112 message is logged at notice, not at info.
19113 - Warn and fail if a server is configured not to advertise any
19114 ORPorts at all. (We need *something* to put in our descriptor,
19115 or we just won't work.)
19118 - Track how many "TAP" and "NTor" circuit handshake requests we get,
19119 and how many we complete, and log it every hour to help relay
19120 operators follow trends in network load. Addresses ticket 9658.
19121 - Update to the August 7 2013 Maxmind GeoLite Country database.
19124 Changes in version 0.2.4.16-rc - 2013-08-10
19125 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
19126 series. It fixes several crash bugs in the 0.2.4 branch.
19129 - Fix a bug in the voting algorithm that could yield incorrect results
19130 when a non-naming authority declared too many flags. Fixes bug 9200;
19131 bugfix on 0.2.0.3-alpha.
19132 - Fix an uninitialized read that could in some cases lead to a remote
19133 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
19134 Anybody running a hidden service on the experimental 0.2.4.x
19135 branch should upgrade. (This is, so far as we know, unrelated to
19137 - Avoid an assertion failure when processing DNS replies without the
19138 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
19139 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
19140 0.2.4.15-rc. Found by stem integration tests.
19143 - Fix an invalid memory read that occurred when a pluggable
19144 transport proxy failed its configuration protocol.
19145 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
19146 - When evaluating whether to use a connection that we haven't
19147 decided is canonical using a recent link protocol version,
19148 decide that it's canonical only if it used address _does_
19149 match the desired address. Fixes bug 9309; bugfix on
19150 0.2.4.4-alpha. Reported by skruffy.
19151 - Make the default behavior of NumDirectoryGuards be to track
19152 NumEntryGuards. Now a user who changes only NumEntryGuards will get
19153 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
19154 - Fix a spurious compilation warning with some older versions of
19155 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
19158 - Update to the July 3 2013 Maxmind GeoLite Country database.
19161 Changes in version 0.2.4.15-rc - 2013-07-01
19162 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
19163 series. It fixes a few smaller bugs, but generally appears stable.
19164 Please test it and let us know whether it is!
19167 - When receiving a new configuration file via the control port's
19168 LOADCONF command, do not treat the defaults file as absent.
19169 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
19172 - Issue a warning when running with the bufferevents backend enabled.
19173 It's still not stable, and people should know that they're likely
19174 to hit unexpected problems. Closes ticket 9147.
19177 Changes in version 0.2.4.14-alpha - 2013-06-18
19178 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
19179 present in 0.2.4.13-alpha.
19182 - When we have too much memory queued in circuits (according to a new
19183 MaxMemInCellQueues option), close the circuits consuming the most
19184 memory. This prevents us from running out of memory as a relay if
19185 circuits fill up faster than they can be drained. Fixes bug 9063;
19186 bugfix on the 54th commit of Tor. This bug is a further fix beyond
19187 bug 6252, whose fix was merged into 0.2.3.21-rc.
19189 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
19190 where we tried to solve this issue simply by imposing an upper limit
19191 on the number of queued cells for a single circuit. That approach
19192 proved to be problematic, since there are ways to provoke clients to
19193 send a number of cells in excess of any such reasonable limit. Fixes
19194 bug 9072; bugfix on 0.2.4.13-alpha.
19196 - Limit hidden service descriptors to at most ten introduction
19197 points, to slow one kind of guard enumeration. Fixes bug 9002;
19198 bugfix on 0.1.1.11-alpha.
19201 Changes in version 0.2.4.13-alpha - 2013-06-14
19202 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
19203 vulnerabilities, makes socks5 username/password circuit isolation
19204 actually actually work (this time for sure!), and cleans up a bunch
19205 of other issues in preparation for a release candidate.
19207 o Major bugfixes (robustness):
19208 - Close any circuit that has too many cells queued on it. Fixes
19209 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
19210 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
19211 - Prevent the get_freelists() function from running off the end of
19212 the list of freelists if it somehow gets an unrecognized
19213 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
19215 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
19216 when an exit connection with optimistic data succeeds immediately
19217 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
19219 - Fix a directory authority crash bug when building a consensus
19220 using an older consensus as its basis. Fixes bug 8833. Bugfix
19224 - Avoid a memory leak where we would leak a consensus body when we
19225 find that a consensus which we couldn't previously verify due to
19226 missing certificates is now verifiable. Fixes bug 8719; bugfix
19228 - We used to always request authority certificates by identity digest,
19229 meaning we'd get the newest one even when we wanted one with a
19230 different signing key. Then we would complain about being given
19231 a certificate we already had, and never get the one we really
19232 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
19233 resource to request the one we want. Fixes bug 5595; bugfix on
19235 - Follow the socks5 protocol when offering username/password
19236 authentication. The fix for bug 8117 exposed this bug, and it
19237 turns out real-world applications like Pidgin do care. Bugfix on
19238 0.2.3.2-alpha; fixes bug 8879.
19239 - Prevent failures on Windows Vista and later when rebuilding the
19240 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
19241 bugfix on 0.2.4.12-alpha.
19244 - Fix an impossible buffer overrun in the AES unit tests. Fixes
19245 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
19246 - If for some reason we fail to write a microdescriptor while
19247 rebuilding the cache, do not let the annotations from that
19248 microdescriptor linger in the cache file, and do not let the
19249 microdescriptor stay recorded as present in its old location.
19250 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
19251 - Fix a memory leak that would occur whenever a configuration
19252 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
19253 - Paste the description for PathBias parameters from the man
19254 page into or.h, so the code documents them too. Fixes bug 7982;
19255 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
19256 - Relays now treat a changed IPv6 ORPort as sufficient reason to
19257 publish an updated descriptor. Fixes bug 6026; bugfix on
19259 - When launching a resolve request on behalf of an AF_UNIX control
19260 socket, omit the address field of the new entry connection, used in
19261 subsequent controller events, rather than letting tor_dup_addr()
19262 set it to "<unknown address type>". Fixes bug 8639; bugfix on
19265 o Minor bugfixes (log messages):
19266 - Fix a scaling issue in the path bias accounting code that
19267 resulted in "Bug:" log messages from either
19268 pathbias_scale_close_rates() or pathbias_count_build_success().
19269 This represents a bugfix on a previous bugfix: the original fix
19270 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
19272 - Give a less useless error message when the user asks for an IPv4
19273 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
19277 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
19278 to tolerate bug 8093 for now.
19279 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
19280 in directory authority votes to describe whether they have enough
19281 measured bandwidths to ignore advertised (relay descriptor)
19282 bandwidth claims. Resolves ticket 8711.
19283 - Update to the June 5 2013 Maxmind GeoLite Country database.
19285 o Removed documentation:
19286 - Remove some of the older contents of doc/ as obsolete; move others
19287 to torspec.git. Fixes bug 8965.
19289 o Code simplification and refactoring:
19290 - Avoid using character buffers when constructing most directory
19291 objects: this approach was unwieldy and error-prone. Instead,
19292 build smartlists of strings, and concatenate them when done.
19295 Changes in version 0.2.4.12-alpha - 2013-04-18
19296 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
19297 process for lengthening the guard rotation period, makes directory
19298 authority opinions in the consensus a bit less gameable, makes socks5
19299 username/password circuit isolation actually work, and fixes a wide
19300 variety of other issues.
19303 - Raise the default time that a client keeps an entry guard from
19304 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
19305 2012 paper. (We would make it even longer, but we need better client
19306 load balancing first.) Also, make the guard lifetime controllable
19307 via a new GuardLifetime torrc option and a GuardLifetime consensus
19308 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
19309 - Directory authorities now prefer using measured bandwidths to
19310 advertised ones when computing flags and thresholds. Resolves
19312 - Directory authorities that have more than a threshold number
19313 of relays with measured bandwidths now treat relays with unmeasured
19314 bandwidths as having bandwidth 0. Resolves ticket 8435.
19316 o Major bugfixes (assert / resource use):
19317 - Avoid a bug where our response to TLS renegotiation under certain
19318 network conditions could lead to a busy-loop, with 100% CPU
19319 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
19320 - Avoid an assertion when we discover that we'd like to write a cell
19321 onto a closing connection: just discard the cell. Fixes another
19322 case of bug 7350; bugfix on 0.2.4.4-alpha.
19324 o Major bugfixes (client-side privacy):
19325 - When we mark a circuit as unusable for new circuits, have it
19326 continue to be unusable for new circuits even if MaxCircuitDirtiness
19327 is increased too much at the wrong time, or the system clock jumps
19328 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
19329 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
19330 which have resolved to internal addresses") is set, apply that
19331 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
19332 - When an exit relay rejects a stream with reason "exit policy", but
19333 we only know an exit policy summary (e.g. from the microdesc
19334 consensus) for it, do not mark the relay as useless for all exiting.
19335 Instead, mark just the circuit as unsuitable for that particular
19336 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
19337 - Allow applications to get proper stream isolation with
19338 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
19339 username/password authentication also offer "no authentication". Tor
19340 had previously preferred "no authentication", so the applications
19341 never actually sent Tor their auth details. Now Tor selects
19342 username/password authentication if it's offered. You can disable
19343 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
19344 bug 8117; bugfix on 0.2.3.3-alpha.
19346 o Major bugfixes (other):
19347 - When unable to find any working directory nodes to use as a
19348 directory guard, give up rather than adding the same non-working
19349 nodes to the directory guard list over and over. Fixes bug 8231;
19350 bugfix on 0.2.4.8-alpha.
19353 - Reject as invalid most directory objects containing a NUL.
19354 Belt-and-suspender fix for bug 8037.
19355 - In our testsuite, create temporary directories with a bit more
19356 entropy in their name to make name collisions less likely. Fixes
19358 - Add CACHED keyword to ADDRMAP events in the control protocol
19359 to indicate whether a DNS result will be cached or not. Resolves
19361 - Update to the April 3 2013 Maxmind GeoLite Country database.
19363 o Minor features (build):
19364 - Detect and reject attempts to build Tor with threading support
19365 when OpenSSL has been compiled without threading support.
19367 - Clarify that when autoconf is checking for nacl, it is checking
19368 specifically for nacl with a fast curve25519 implementation.
19370 - Warn if building on a platform with an unsigned time_t: there
19371 are too many places where Tor currently assumes that time_t can
19372 hold negative values. We'd like to fix them all, but probably
19375 o Minor bugfixes (build):
19376 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
19377 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
19378 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
19379 - Add the old src/or/micro-revision.i filename to CLEANFILES.
19380 On the off chance that somebody has one, it will go away as soon
19381 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
19382 - Build Tor correctly on 32-bit platforms where the compiler can build
19383 but not run code using the "uint128_t" construction. Fixes bug 8587;
19384 bugfix on 0.2.4.8-alpha.
19385 - Fix compilation warning with some versions of clang that would
19386 prefer the -Wswitch-enum compiler flag to warn about switch
19387 statements with missing enum values, even if those switch
19388 statements have a "default:" statement. Fixes bug 8598; bugfix
19391 o Minor bugfixes (protocol):
19392 - Fix the handling of a TRUNCATE cell when it arrives while the
19393 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
19394 - Fix a misframing issue when reading the version numbers in a
19395 VERSIONS cell. Previously we would recognize [00 01 00 02] as
19396 'version 1, version 2, and version 0x100', when it should have
19397 only included versions 1 and 2. Fixes bug 8059; bugfix on
19398 0.2.0.10-alpha. Reported pseudonymously.
19399 - Make the format and order of STREAM events for DNS lookups
19400 consistent among the various ways to launch DNS lookups. Fixes
19401 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
19402 - Correct our check for which versions of Tor support the EXTEND2
19403 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
19404 later, when support was really added in version 0.2.4.8-alpha.
19405 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
19407 o Minor bugfixes (other):
19408 - Correctly store microdescriptors and extrainfo descriptors with
19409 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
19410 Bug reported by "cypherpunks".
19411 - Increase the width of the field used to remember a connection's
19412 link protocol version to two bytes. Harmless for now, since the
19413 only currently recognized versions are one byte long. Reported
19414 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
19415 - If the state file's path bias counts are invalid (presumably from a
19416 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
19417 additional checks and log messages to the scaling of Path Bias
19418 counts, in case there still are remaining issues with scaling.
19419 Should help resolve bug 8235.
19420 - Eliminate several instances where we use "Nickname=ID" to refer to
19421 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
19422 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
19423 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
19425 o Minor bugfixes (syscalls):
19426 - Always check the return values of functions fcntl() and
19427 setsockopt(). We don't believe these are ever actually failing in
19428 practice, but better safe than sorry. Also, checking these return
19429 values should please analysis tools like Coverity. Patch from
19430 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
19431 - Use direct writes rather than stdio when building microdescriptor
19432 caches, in an attempt to mitigate bug 8031, or at least make it
19435 o Minor bugfixes (config):
19436 - When rejecting a configuration because we were unable to parse a
19437 quoted string, log an actual error message. Fixes bug 7950; bugfix
19439 - Behave correctly when the user disables LearnCircuitBuildTimeout
19440 but doesn't tell us what they would like the timeout to be. Fixes
19441 bug 6304; bugfix on 0.2.2.14-alpha.
19442 - When autodetecting the number of CPUs, use the number of available
19443 CPUs in preference to the number of configured CPUs. Inform the
19444 user if this reduces the number of available CPUs. Fixes bug 8002;
19445 bugfix on 0.2.3.1-alpha.
19446 - Make it an error when you set EntryNodes but disable UseGuardNodes,
19447 since it will (surprisingly to some users) ignore EntryNodes. Fixes
19448 bug 8180; bugfix on 0.2.3.11-alpha.
19449 - Allow TestingTorNetworks to override the 4096-byte minimum for
19450 the Fast threshold. Otherwise they can't bootstrap until they've
19451 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
19452 - Fix some logic errors when the user manually overrides the
19453 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
19456 o Minor bugfixes (log messages to help diagnose bugs):
19457 - If we fail to free a microdescriptor because of bug 7164, log
19458 the filename and line number from which we tried to free it.
19459 - Add another diagnostic to the heartbeat message: track and log
19460 overhead that TLS is adding to the data we write. If this is
19461 high, we are sending too little data to SSL_write at a time.
19462 Diagnostic for bug 7707.
19463 - Add more detail to a log message about relaxed timeouts, to help
19465 - Warn more aggressively when flushing microdescriptors to a
19466 microdescriptor cache fails, in an attempt to mitigate bug 8031,
19467 or at least make it more diagnosable.
19468 - Improve debugging output to help track down bug 8185 ("Bug:
19469 outgoing relay cell has n_chan==NULL. Dropping.")
19470 - Log the purpose of a path-bias testing circuit correctly.
19471 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
19473 o Minor bugfixes (0.2.4.x log messages that were too noisy):
19474 - Don't attempt to relax the timeout of already opened 1-hop circuits.
19475 They might never timeout. This should eliminate some/all cases of
19476 the relaxed timeout log message.
19477 - Use circuit creation time for network liveness evaluation. This
19478 should eliminate warning log messages about liveness caused
19479 by changes in timeout evaluation. Fixes bug 6572; bugfix on
19481 - Reduce a path bias length check from notice to info. The message
19482 is triggered when creating controller circuits. Fixes bug 8196;
19483 bugfix on 0.2.4.8-alpha.
19484 - Fix a path state issue that triggered a notice during relay startup.
19485 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
19486 - Reduce occurrences of warns about circuit purpose in
19487 connection_ap_expire_building(). Fixes bug 8477; bugfix on
19490 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
19491 - If we encounter a write failure on a SOCKS connection before we
19492 finish our SOCKS handshake, don't warn that we closed the
19493 connection before we could send a SOCKS reply. Fixes bug 8427;
19494 bugfix on 0.1.0.1-rc.
19495 - Correctly recognize that [::1] is a loopback address. Fixes
19496 bug 8377; bugfix on 0.2.1.3-alpha.
19497 - Fix a directory authority warn caused when we have a large amount
19498 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
19499 - Don't log inappropriate heartbeat messages when hibernating: a
19500 hibernating node is _expected_ to drop out of the consensus,
19501 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
19502 bugfix on 0.2.3.1-alpha.
19503 - Don't complain about bootstrapping problems while hibernating.
19504 These complaints reflect a general code problem, but not one
19505 with any problematic effects (no connections are actually
19506 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
19508 o Documentation fixes:
19509 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
19510 names match. Fixes bug 7768.
19511 - Make the torify manpage no longer refer to tsocks; torify hasn't
19512 supported tsocks since 0.2.3.14-alpha.
19513 - Make the tor manpage no longer reference tsocks.
19514 - Fix the GeoIPExcludeUnknown documentation to refer to
19515 ExcludeExitNodes rather than the currently nonexistent
19516 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
19519 - The tor-tsocks.conf is no longer distributed or installed. We
19520 recommend that tsocks users use torsocks instead. Resolves
19524 Changes in version 0.2.4.11-alpha - 2013-03-11
19525 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
19526 more robust, makes hidden service authentication work again, and
19527 resolves a DPI fingerprint for Tor's SSL transport.
19529 o Major features (directory authorities):
19530 - Directory authorities now support a new consensus method (17)
19531 where they cap the published bandwidth of servers for which
19532 insufficient bandwidth measurements exist. Fixes part of bug 2286.
19533 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
19534 serve any v2 directory information. Now we can test disabling the
19535 old deprecated v2 directory format, and see whether doing so has
19536 any effect on network load. Begins to fix bug 6783.
19537 - Directory authorities now include inside each vote a statement of
19538 the performance thresholds they used when assigning flags.
19539 Implements ticket 8151.
19541 o Major bugfixes (directory authorities):
19542 - Stop marking every relay as having been down for one hour every
19543 time we restart a directory authority. These artificial downtimes
19544 were messing with our Stable and Guard flag calculations. Fixes
19545 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
19547 o Major bugfixes (hidden services):
19548 - Allow hidden service authentication to succeed again. When we
19549 refactored the hidden service introduction code back
19550 in 0.2.4.1-alpha, we didn't update the code that checks
19551 whether authentication information is present, causing all
19552 authentication checks to return "false". Fix for bug 8207; bugfix
19553 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
19555 o Minor features (relays, bridges):
19556 - Make bridge relays check once a minute for whether their IP
19557 address has changed, rather than only every 15 minutes. Resolves
19558 bugs 1913 and 1992.
19559 - Refactor resolve_my_address() so it returns the method by which we
19560 decided our public IP address (explicitly configured, resolved from
19561 explicit hostname, guessed from interfaces, learned by gethostname).
19562 Now we can provide more helpful log messages when a relay guesses
19563 its IP address incorrectly (e.g. due to unexpected lines in
19564 /etc/hosts). Resolves ticket 2267.
19565 - Teach bridge-using clients to avoid 0.2.2 bridges when making
19566 microdescriptor-related dir requests, and only fall back to normal
19567 descriptors if none of their bridges can handle microdescriptors
19568 (as opposed to the fix in ticket 4013, which caused them to fall
19569 back to normal descriptors if *any* of their bridges preferred
19570 them). Resolves ticket 4994.
19571 - Randomize the lifetime of our SSL link certificate, so censors can't
19572 use the static value for filtering Tor flows. Resolves ticket 8443;
19573 related to ticket 4014 which was included in 0.2.2.33.
19574 - Support a new version of the link protocol that allows 4-byte circuit
19575 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
19576 a possible resource exhaustion issue. Closes ticket 7351; implements
19579 o Minor features (portability):
19580 - Tweak the curve25519-donna*.c implementations to tolerate systems
19581 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
19582 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
19583 the signs of types during autoconf. This is better than our old
19584 approach, which didn't work when cross-compiling.
19585 - Detect the sign of enum values, rather than assuming that MSC is the
19586 only compiler where enum types are all signed. Fixes bug 7727;
19587 bugfix on 0.2.4.10-alpha.
19589 o Minor features (other):
19590 - Say "KBytes" rather than "KB" in the man page (for various values
19591 of K), to further reduce confusion about whether Tor counts in
19592 units of memory or fractions of units of memory. Resolves ticket 7054.
19593 - Clear the high bit on curve25519 public keys before passing them to
19594 our backend, in case we ever wind up using a backend that doesn't do
19595 so itself. If we used such a backend, and *didn't* clear the high bit,
19596 we could wind up in a situation where users with such backends would
19597 be distinguishable from users without. Fixes bug 8121; bugfix on
19599 - Update to the March 6 2013 Maxmind GeoLite Country database.
19601 o Minor bugfixes (clients):
19602 - When we receive a RELAY_END cell with the reason DONE, or with no
19603 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
19604 status as "connection refused". Previously we reported these cases
19605 as success but then immediately closed the connection. Fixes bug
19606 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
19607 - Downgrade an assertion in connection_ap_expire_beginning to an
19608 LD_BUG message. The fix for bug 8024 should prevent this message
19609 from displaying, but just in case, a warn that we can diagnose
19610 is better than more assert crashes. Fixes bug 8065; bugfix on
19612 - Lower path use bias thresholds to .80 for notice and .60 for warn.
19613 Also make the rate limiting flags for the path use bias log messages
19614 independent from the original path bias flags. Fixes bug 8161;
19615 bugfix on 0.2.4.10-alpha.
19617 o Minor bugfixes (relays):
19618 - Stop trying to resolve our hostname so often (e.g. every time we
19619 think about doing a directory fetch). Now we reuse the cached
19620 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
19621 and 2410 (bugfix on 0.1.2.2-alpha).
19622 - Stop sending a stray "(null)" in some cases for the server status
19623 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
19625 - When choosing which stream on a formerly stalled circuit to wake
19626 first, make better use of the platform's weak RNG. Previously,
19627 we had been using the % ("modulo") operator to try to generate a
19628 1/N chance of picking each stream, but this behaves badly with
19629 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
19631 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
19632 Irix's random() only return 15 bits; Solaris's random() returns more
19633 bits but its RAND_MAX says it only returns 15, and so on. Motivated
19634 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
19636 o Minor bugfixes (directory authorities):
19637 - Directory authorities now use less space when formatting identical
19638 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
19641 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
19642 - Avoid leaking memory if we fail to compute a consensus signature
19643 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
19644 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
19646 - Fix a memory leak during safe-cookie controller authentication.
19647 Bugfix on 0.2.3.13-alpha.
19648 - Avoid memory leak of IPv6 policy content if we fail to format it into
19649 a router descriptor. Bugfix on 0.2.4.7-alpha.
19651 o Minor bugfixes (other code correctness issues):
19652 - Avoid a crash if we fail to generate an extrainfo descriptor.
19653 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
19654 this is CID 718634.
19655 - When detecting the largest possible file descriptor (in order to
19656 close all file descriptors when launching a new program), actually
19657 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
19658 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
19660 - Fix a copy-and-paste error when adding a missing A1 to a routerset
19661 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
19662 Bugfix on 0.2.4.10-alpha.
19663 - Fix an impossible-to-trigger integer overflow when estimating how
19664 long our onionskin queue would take. (This overflow would require us
19665 to accept 4 million onionskins before processing 100 of them.) Fixes
19666 bug 8210; bugfix on 0.2.4.10-alpha.
19668 o Code simplification and refactoring:
19669 - Add a wrapper function for the common "log a message with a
19673 Changes in version 0.2.4.10-alpha - 2013-02-04
19674 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
19675 certain attacks that flood the network with relays; changes the queue
19676 for circuit create requests from a sized-based limit to a time-based
19677 limit; resumes building with MSVC on Windows; and fixes a wide variety
19680 o Major bugfixes (directory authority):
19681 - When computing directory thresholds, ignore any rejected-as-sybil
19682 nodes during the computation so that they can't influence Fast,
19683 Guard, etc. (We should have done this for proposal 109.) Fixes
19685 - When marking a node as a likely sybil, reset its uptime metrics
19686 to zero, so that it cannot time towards getting marked as Guard,
19687 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
19691 - When a TLS write is partially successful but incomplete, remember
19692 that the flushed part has been flushed, and notice that bytes were
19693 actually written. Reported and fixed pseudonymously. Fixes bug
19694 7708; bugfix on Tor 0.1.0.5-rc.
19695 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
19696 ID: these could be used to create unexpected streams and circuits
19697 which would count as "present" to some parts of Tor but "absent"
19698 to others, leading to zombie circuits and streams or to a bandwidth
19699 denial-of-service. Fixes bug 7889; bugfix on every released version
19700 of Tor. Reported by "oftc_must_be_destroyed".
19701 - Rename all macros in our local copy of queue.h to begin with "TOR_".
19702 This change seems the only good way to permanently prevent conflicts
19703 with queue.h on various operating systems. Fixes bug 8107; bugfix
19706 o Major features (relay):
19707 - Instead of limiting the number of queued onionskins (aka circuit
19708 create requests) to a fixed, hard-to-configure number, we limit
19709 the size of the queue based on how many we expect to be able to
19710 process in a given amount of time. We estimate the time it will
19711 take to process an onionskin based on average processing time
19712 of previous onionskins. Closes ticket 7291. You'll never have to
19713 configure MaxOnionsPending again.
19715 o Major features (portability):
19716 - Resume building correctly with MSVC and Makefile.nmake. This patch
19717 resolves numerous bugs and fixes reported by ultramage, including
19718 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
19719 - Make the ntor and curve25519 code build correctly with MSVC.
19720 Fix on 0.2.4.8-alpha.
19723 - When directory authorities are computing thresholds for flags,
19724 never let the threshold for the Fast flag fall below 4096
19725 bytes. Also, do not consider nodes with extremely low bandwidths
19726 when deciding thresholds for various directory flags. This change
19727 should raise our threshold for Fast relays, possibly in turn
19728 improving overall network performance; see ticket 1854. Resolves
19730 - The Tor client now ignores sub-domain components of a .onion
19731 address. This change makes HTTP "virtual" hosting
19732 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
19733 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
19734 hosted on the same hidden service. Implements proposal 204.
19735 - We compute the overhead from passing onionskins back and forth to
19736 cpuworkers, and report it when dumping statistics in response to
19737 SIGUSR1. Supports ticket 7291.
19739 o Minor features (path selection):
19740 - When deciding whether we have enough descriptors to build circuits,
19741 instead of looking at raw relay counts, look at which fraction
19742 of (bandwidth-weighted) paths we're able to build. This approach
19743 keeps clients from building circuits if their paths are likely to
19744 stand out statistically. The default fraction of paths needed is
19745 taken from the consensus directory; you can override it with the
19746 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
19747 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
19748 and we have GeoIP information, also exclude all nodes with unknown
19749 countries "??" and "A1". This behavior is controlled by the
19750 new GeoIPExcludeUnknown option: you can make such nodes always
19751 excluded with "GeoIPExcludeUnknown 1", and disable the feature
19752 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
19753 gets you the default behavior. Implements feature 7706.
19754 - Path Use Bias: Perform separate accounting for successful circuit
19755 use. Keep separate statistics on stream attempt rates versus stream
19756 success rates for each guard. Provide configurable thresholds to
19757 determine when to emit log messages or disable use of guards that
19758 fail too many stream attempts. Resolves ticket 7802.
19760 o Minor features (log messages):
19761 - When learning a fingerprint for a bridge, log its corresponding
19762 transport type. Implements ticket 7896.
19763 - Improve the log message when "Bug/attack: unexpected sendme cell
19764 from client" occurs, to help us track bug 8093.
19767 - Remove a couple of extraneous semicolons that were upsetting the
19768 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
19769 bugfix on 0.2.2.1-alpha.
19770 - Remove a source of rounding error during path bias count scaling;
19771 don't count cannibalized circuits as used for path bias until we
19772 actually try to use them; and fix a circuit_package_relay_cell()
19773 warning message about n_chan==NULL. Fixes bug 7802.
19774 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
19775 actually link against nacl when we're configured to use it. Fixes
19776 bug 7972; bugfix on 0.2.4.8-alpha.
19777 - Compile correctly with the --disable-curve25519 option. Fixes
19778 bug 8153; bugfix on 0.2.4.8-alpha.
19780 o Build improvements:
19781 - Do not report status verbosely from autogen.sh unless the -v flag
19782 is specified. Fixes issue 4664. Patch from Onizuka.
19783 - Replace all calls to snprintf() outside of src/ext with
19784 tor_snprintf(). Also remove the #define to replace snprintf with
19785 _snprintf on Windows; they have different semantics, and all of
19786 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
19787 - Try to detect if we are ever building on a platform where
19788 memset(...,0,...) does not set the value of a double to 0.0. Such
19789 platforms are permitted by the C standard, though in practice
19790 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
19791 currently support them, but it's better to detect them and fail
19792 than to perform erroneously.
19794 o Removed features:
19795 - Stop exporting estimates of v2 and v3 directory traffic shares
19796 in extrainfo documents. They were unneeded and sometimes inaccurate.
19797 Also stop exporting any v2 directory request statistics. Resolves
19799 - Drop support for detecting and warning about versions of Libevent
19800 before 1.3e. Nothing reasonable ships with them any longer;
19801 warning the user about them shouldn't be needed. Resolves ticket
19804 o Code simplifications and refactoring:
19805 - Rename "isin" functions to "contains", for grammar. Resolves
19807 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
19808 with the natural logarithm function from the system libm. Resolves
19812 Changes in version 0.2.4.9-alpha - 2013-01-15
19813 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
19814 work more robustly.
19817 - Fix backward compatibility logic when receiving an embedded ntor
19818 handshake tunneled in a CREATE cell. This clears up the "Bug:
19819 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
19823 Changes in version 0.2.4.8-alpha - 2013-01-14
19824 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
19825 risks, adds a new stronger and faster circuit handshake, and offers
19826 stronger and faster link encryption when both sides support it.
19829 - Preliminary support for directory guards (proposal 207): when
19830 possible, clients now use their entry guards for non-anonymous
19831 directory requests. This can help prevent client enumeration. Note
19832 that this behavior only works when we have a usable consensus
19833 directory, and when options about what to download are more or less
19834 standard. In the future we should re-bootstrap from our guards,
19835 rather than re-bootstrapping from the preconfigured list of
19836 directory sources that ships with Tor. Resolves ticket 6526.
19837 - Tor relays and clients now support a better CREATE/EXTEND cell
19838 format, allowing the sender to specify multiple address, identity,
19839 and handshake types. Implements Robert Ransom's proposal 200;
19840 closes ticket 7199.
19842 o Major features (new circuit handshake):
19843 - Tor now supports a new circuit extension handshake designed by Ian
19844 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
19845 circuit extension handshake, later called "TAP", was a bit slow
19846 (especially on the relay side), had a fragile security proof, and
19847 used weaker keys than we'd now prefer. The new circuit handshake
19848 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
19849 function, making it significantly more secure than the older
19850 handshake, and significantly faster. Tor can use one of two built-in
19851 pure-C curve25519-donna implementations by Adam Langley, or it
19852 can link against the "nacl" library for a tuned version if present.
19854 The built-in version is very fast for 64-bit systems when building
19855 with GCC. The built-in 32-bit version is still faster than the
19856 old TAP protocol, but using libnacl is better on most such hosts.
19858 Clients don't currently use this protocol by default, since
19859 comparatively few clients support it so far. To try it, set
19860 UseNTorHandshake to 1.
19862 Implements proposal 216; closes ticket 7202.
19864 o Major features (better link encryption):
19865 - Relays can now enable the ECDHE TLS ciphersuites when available
19866 and appropriate. These ciphersuites let us negotiate forward-secure
19867 TLS secret keys more safely and more efficiently than with our
19868 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
19869 public relays prefer the (faster) P224 group, and bridges prefer
19870 the (more common) P256 group; you can override this with the
19873 Enabling these ciphers was a little tricky, since for a long time,
19874 clients had been claiming to support them without actually doing
19875 so, in order to foil fingerprinting. But with the client-side
19876 implementation of proposal 198 in 0.2.3.17-beta, clients can now
19877 match the ciphers from recent Firefox versions *and* list the
19878 ciphers they actually mean, so relays can believe such clients
19879 when they advertise ECDHE support in their TLS ClientHello messages.
19881 This feature requires clients running 0.2.3.17-beta or later,
19882 and requires both sides to be running OpenSSL 1.0.0 or later
19883 with ECC support. OpenSSL 1.0.1, with the compile-time option
19884 "enable-ec_nistp_64_gcc_128", is highly recommended.
19886 Implements the relay side of proposal 198; closes ticket 7200.
19889 - Avoid crashing when, as a relay without IPv6-exit support, a
19890 client insists on getting an IPv6 address or nothing. Fixes bug
19891 7814; bugfix on 0.2.4.7-alpha.
19894 - Improve circuit build timeout handling for hidden services.
19895 In particular: adjust build timeouts more accurately depending
19896 upon the number of hop-RTTs that a particular circuit type
19897 undergoes. Additionally, launch intro circuits in parallel
19898 if they timeout, and take the first one to reply as valid.
19899 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
19900 separate error codes; or at least, don't break for that reason.
19901 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
19902 - Update to the January 2 2013 Maxmind GeoLite Country database.
19904 o Minor features (testing):
19905 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
19906 (P-256) Diffie-Hellman handshakes to src/or/bench.
19907 - Add benchmark functions to test onion handshake performance.
19909 o Minor features (path bias detection):
19910 - Alter the Path Bias log messages to be more descriptive in terms
19911 of reporting timeouts and other statistics.
19912 - Create three levels of Path Bias log messages, as opposed to just
19913 two. These are configurable via consensus as well as via the torrc
19914 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
19915 The default values are 0.70, 0.50, and 0.30 respectively.
19916 - Separate the log message levels from the decision to drop guards,
19917 which also is available via torrc option PathBiasDropGuards.
19918 PathBiasDropGuards still defaults to 0 (off).
19919 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
19920 in combination with PathBiasExtremeRate.
19921 - Increase the default values for PathBiasScaleThreshold and
19922 PathBiasCircThreshold from (200, 20) to (300, 150).
19923 - Add in circuit usage accounting to path bias. If we try to use a
19924 built circuit but fail for any reason, it counts as path bias.
19925 Certain classes of circuits where the adversary gets to pick your
19926 destination node are exempt from this accounting. Usage accounting
19927 can be specifically disabled via consensus parameter or torrc.
19928 - Convert all internal path bias state to double-precision floating
19929 point, to avoid roundoff error and other issues.
19930 - Only record path bias information for circuits that have completed
19931 *two* hops. Assuming end-to-end tagging is the attack vector, this
19932 makes us more resilient to ambient circuit failure without any
19933 detection capability loss.
19935 o Minor bugfixes (log messages):
19936 - Rate-limit the "No circuits are opened. Relaxed timeout for a
19937 circuit with channel state open..." message to once per hour to
19938 keep it from filling the notice logs. Mitigates bug 7799 but does
19939 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
19940 - Avoid spurious warnings when configuring multiple client ports of
19941 which only some are nonlocal. Previously, we had claimed that some
19942 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
19945 o Code simplifications and refactoring:
19946 - Get rid of a couple of harmless clang warnings, where we compared
19947 enums to ints. These warnings are newly introduced in clang 3.2.
19948 - Split the onion.c file into separate modules for the onion queue
19949 and the different handshakes it supports.
19950 - Remove the marshalling/unmarshalling code for sending requests to
19951 cpuworkers over a socket, and instead just send structs. The
19952 recipient will always be the same Tor binary as the sender, so
19953 any encoding is overkill.
19956 Changes in version 0.2.4.7-alpha - 2012-12-24
19957 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
19958 directory mirrors for more robust bootstrapping; fixes more issues where
19959 clients with changing network conditions refuse to make any circuits;
19960 adds initial support for exiting to IPv6 addresses; resumes being able
19961 to update our GeoIP database, and includes the geoip6 file this time;
19962 turns off the client-side DNS cache by default due to privacy risks;
19963 and fixes a variety of other issues.
19965 o Major features (client resilience):
19966 - Add a new "FallbackDir" torrc option to use when we can't use
19967 a directory mirror from the consensus (either because we lack a
19968 consensus, or because they're all down). Currently, all authorities
19969 are fallbacks by default, and there are no other default fallbacks,
19970 but that will change. This option will allow us to give clients a
19971 longer list of servers to try to get a consensus from when first
19972 connecting to the Tor network, and thereby reduce load on the
19973 directory authorities. Implements proposal 206, "Preconfigured
19974 directory sources for bootstrapping". We also removed the old
19975 "FallbackNetworkstatus" option, since we never got it working well
19976 enough to use it. Closes bug 572.
19977 - If we have no circuits open, use a relaxed timeout (the
19978 95-percentile cutoff) until a circuit succeeds. This heuristic
19979 should allow Tor to succeed at building circuits even when the
19980 network connection drastically changes. Should help with bug 3443.
19982 o Major features (IPv6):
19983 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
19984 connectivity, then set the IPv6Exit flag to 1. Also make sure your
19985 exit policy reads as you would like: the address * applies to all
19986 address families, whereas *4 is IPv4 address only, and *6 is IPv6
19987 addresses only. On the client side, you'll need to wait until the
19988 authorities have upgraded, wait for enough exits to support IPv6,
19989 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
19990 ticket 5547, implements proposal 117 as revised in proposal 208.
19992 We DO NOT recommend that clients with actual anonymity needs start
19993 using IPv6 over Tor yet, since not enough exits support it yet.
19995 o Major features (geoip database):
19996 - Maxmind began labelling Tor relays as being in country "A1",
19997 which breaks by-country node selection inside Tor. Now we use a
19998 script to replace "A1" ("Anonymous Proxy") entries in our geoip
19999 file with real country codes. This script fixes about 90% of "A1"
20000 entries automatically and uses manual country code assignments to
20001 fix the remaining 10%. See src/config/README.geoip for details.
20002 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
20003 Country database, as modified above.
20005 o Major bugfixes (client-side DNS):
20006 - Turn off the client-side DNS cache by default. Updating and using
20007 the DNS cache is now configurable on a per-client-port
20008 level. SOCKSPort, DNSPort, etc lines may now contain
20009 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
20010 cache these types of DNS answers when we receive them from an
20011 exit node in response to an application request on this port, and
20012 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
20013 cached DNS answers of these types, we shouldn't use them. It's
20014 potentially risky to use cached DNS answers at the client, since
20015 doing so can indicate to one exit what answers we've gotten
20016 for DNS lookups in the past. With IPv6, this becomes especially
20017 problematic. Using cached DNS answers for requests on the same
20018 circuit would present less linkability risk, since all traffic
20019 on a circuit is already linkable, but it would also provide
20020 little performance benefit: the exit node caches DNS replies
20021 too. Implements a simplified version of Proposal 205. Implements
20024 o Major bugfixes (other):
20025 - Alter circuit build timeout measurement to start at the point
20026 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
20027 initialization). This should make our timeout measurements more
20028 uniform. Previously, we were sometimes including ORconn setup time
20029 in our circuit build time measurements. Should resolve bug 3443.
20030 - Fix an assertion that could trigger in hibernate_go_dormant() when
20031 closing an or_connection_t: call channel_mark_for_close() rather
20032 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
20034 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
20035 7655; bugfix on 0.2.4.6-alpha.
20038 - Add a new torrc option "ServerTransportListenAddr" to let bridge
20039 operators select the address where their pluggable transports will
20040 listen for connections. Resolves ticket 7013.
20041 - Allow an optional $ before the node identity digest in the
20042 controller command GETINFO ns/id/<identity>, for consistency with
20043 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
20044 - Log packaged cell fullness as part of the heartbeat message.
20045 Diagnosis to try to determine the extent of bug 7743.
20047 o Minor features (IPv6):
20048 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
20049 prefer to hand out virtual IPv6 addresses, since there are more of
20050 them and we can't run out. To override this behavior and make IPv4
20051 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
20052 or DNSPort you're using for resolving. Implements ticket 7571.
20053 - AutomapHostsOnResolve responses are now randomized, to avoid
20054 annoying situations where Tor is restarted and applications
20055 connect to the wrong addresses.
20056 - Never try more than 1000 times to pick a new virtual address when
20057 AutomapHostsOnResolve is set. That's good enough so long as we
20058 aren't close to handing out our entire virtual address space;
20059 if you're getting there, it's best to switch to IPv6 virtual
20063 - The ADDRMAP command can no longer generate an ill-formed error
20064 code on a failed MAPADDRESS. It now says "internal" rather than
20065 an English sentence fragment with spaces in the middle. Bugfix on
20066 Tor 0.2.0.19-alpha.
20067 - Fix log messages and comments to avoid saying "GMT" when we mean
20068 "UTC". Fixes bug 6113.
20069 - Compile on win64 using mingw64. Fixes bug 7260; patches from
20071 - Fix a crash when debugging unit tests on Windows: deallocate a
20072 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
20073 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
20076 - The DirServer option is now DirAuthority, for consistency with
20077 current naming patterns. You can still use the old DirServer form.
20079 o Code simplification and refactoring:
20080 - Move the client-side address-map/virtual-address/DNS-cache code
20081 out of connection_edge.c into a new addressmap.c module.
20082 - Remove unused code for parsing v1 directories and "running routers"
20083 documents. Fixes bug 6887.
20086 Changes in version 0.2.3.25 - 2012-11-19
20087 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
20088 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
20089 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
20090 programmer, and friend. Unstinting in his dedication to the cause of
20091 freedom, he inspired and helped many of us as we began our work on
20092 anonymity, and inspires us still. Please honor his memory by writing
20093 software to protect people's freedoms, and by helping others to do so.
20095 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
20096 significantly reduced directory overhead (via microdescriptors),
20097 enormous crypto performance improvements for fast relays on new
20098 enough hardware, a new v3 TLS handshake protocol that can better
20099 resist fingerprinting, support for protocol obfuscation plugins (aka
20100 pluggable transports), better scalability for hidden services, IPv6
20101 support for bridges, performance improvements like allowing clients
20102 to skip the first round-trip on the circuit ("optimistic data") and
20103 refilling token buckets more often, a new "stream isolation" design
20104 to isolate different applications on different circuits, and many
20105 stability, security, and privacy fixes.
20108 - Tor tries to wipe potentially sensitive data after using it, so
20109 that if some subsequent security failure exposes Tor's memory,
20110 the damage will be limited. But we had a bug where the compiler
20111 was eliminating these wipe operations when it decided that the
20112 memory was no longer visible to a (correctly running) program,
20113 hence defeating our attempt at defense in depth. We fix that
20114 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
20115 is unlikely to optimize away. Future versions of Tor may use
20116 a less ridiculously heavy approach for this. Fixes bug 7352.
20117 Reported in an article by Andrey Karpov.
20120 - Fix a harmless bug when opting against publishing a relay descriptor
20121 because DisableNetwork is set. Fixes bug 7464; bugfix on
20125 Changes in version 0.2.4.6-alpha - 2012-11-13
20126 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
20127 makes our defense-in-depth memory wiping more reliable, and begins to
20128 count IPv6 addresses in bridge statistics,
20131 - Fix an assertion failure that could occur when closing a connection
20132 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
20134 - Tor tries to wipe potentially sensitive data after using it, so
20135 that if some subsequent security failure exposes Tor's memory,
20136 the damage will be limited. But we had a bug where the compiler
20137 was eliminating these wipe operations when it decided that the
20138 memory was no longer visible to a (correctly running) program,
20139 hence defeating our attempt at defense in depth. We fix that
20140 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
20141 is unlikely to optimize away. Future versions of Tor may use
20142 a less ridiculously heavy approach for this. Fixes bug 7352.
20143 Reported in an article by Andrey Karpov.
20146 - Add GeoIP database for IPv6 addresses. The new config option
20148 - Bridge statistics now count bridge clients connecting over IPv6:
20149 bridge statistics files now list "bridge-ip-versions" and
20150 extra-info documents list "geoip6-db-digest". The control protocol
20151 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
20152 implementation by "shkoo", addressing ticket 5055.
20155 - Warn when we are binding low ports when hibernation is enabled;
20156 previously we had warned when we were _advertising_ low ports with
20157 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
20158 - Fix a harmless bug when opting against publishing a relay descriptor
20159 because DisableNetwork is set. Fixes bug 7464; bugfix on
20161 - Add warning message when a managed proxy dies during configuration.
20162 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
20163 - Fix a linking error when building tor-fw-helper without miniupnp.
20164 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
20165 - Check for closing an or_connection_t without going through correct
20166 channel functions; emit a warning and then call
20167 connection_or_close_for_error() so we don't assert as in bugs 7212
20169 - Compile correctly on compilers without C99 designated initializer
20170 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
20171 - Avoid a possible assert that can occur when channel_send_destroy() is
20172 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
20173 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
20174 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
20175 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
20176 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
20178 o Code simplification and refactoring:
20179 - Start using OpenBSD's implementation of queue.h, so that we don't
20180 need to hand-roll our own pointer and list structures whenever we
20181 need them. (We can't rely on a sys/queue.h, since some operating
20182 systems don't have them, and the ones that do have them don't all
20183 present the same extensions.)
20186 Changes in version 0.2.4.5-alpha - 2012-10-25
20187 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
20188 two important security vulnerabilities that could lead to remotely
20189 triggerable relay crashes, fix a major bug that was preventing clients
20190 from choosing suitable exit nodes, and refactor some of our code.
20192 o Major bugfixes (security, also in 0.2.3.24-rc):
20193 - Fix a group of remotely triggerable assertion failures related to
20194 incorrect link protocol negotiation. Found, diagnosed, and fixed
20195 by "some guy from France". Fix for CVE-2012-2250; bugfix on
20197 - Fix a denial of service attack by which any directory authority
20198 could crash all the others, or by which a single v2 directory
20199 authority could crash everybody downloading v2 directory
20200 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
20202 o Major bugfixes (also in 0.2.3.24-rc):
20203 - When parsing exit policy summaries from microdescriptors, we had
20204 previously been ignoring the last character in each one, so that
20205 "accept 80,443,8080" would be treated by clients as indicating
20206 a node that allows access to ports 80, 443, and 808. That would
20207 lead to clients attempting connections that could never work,
20208 and ignoring exit nodes that would support their connections. Now
20209 clients parse these exit policy summaries correctly. Fixes bug 7192;
20210 bugfix on 0.2.3.1-alpha.
20212 o Minor bugfixes (also in 0.2.3.24-rc):
20213 - Clients now consider the ClientRejectInternalAddresses config option
20214 when using a microdescriptor consensus stanza to decide whether
20215 an exit relay would allow exiting to an internal address. Fixes
20216 bug 7190; bugfix on 0.2.3.1-alpha.
20219 - Only disable TLS session ticket support when running as a TLS
20220 server. Now clients will blend better with regular Firefox
20221 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
20223 o Code simplification and refactoring:
20224 - Start using OpenBSD's implementation of queue.h (originally by
20226 - Move the entry node code from circuitbuild.c to its own file.
20227 - Move the circuit build timeout tracking code from circuitbuild.c
20231 Changes in version 0.2.3.24-rc - 2012-10-25
20232 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
20233 could lead to remotely triggerable relay crashes, and fixes
20234 a major bug that was preventing clients from choosing suitable exit
20237 o Major bugfixes (security):
20238 - Fix a group of remotely triggerable assertion failures related to
20239 incorrect link protocol negotiation. Found, diagnosed, and fixed
20240 by "some guy from France". Fix for CVE-2012-2250; bugfix on
20242 - Fix a denial of service attack by which any directory authority
20243 could crash all the others, or by which a single v2 directory
20244 authority could crash everybody downloading v2 directory
20245 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
20248 - When parsing exit policy summaries from microdescriptors, we had
20249 previously been ignoring the last character in each one, so that
20250 "accept 80,443,8080" would be treated by clients as indicating
20251 a node that allows access to ports 80, 443, and 808. That would
20252 lead to clients attempting connections that could never work,
20253 and ignoring exit nodes that would support their connections. Now
20254 clients parse these exit policy summaries correctly. Fixes bug 7192;
20255 bugfix on 0.2.3.1-alpha.
20258 - Clients now consider the ClientRejectInternalAddresses config option
20259 when using a microdescriptor consensus stanza to decide whether
20260 an exit relay would allow exiting to an internal address. Fixes
20261 bug 7190; bugfix on 0.2.3.1-alpha.
20264 Changes in version 0.2.4.4-alpha - 2012-10-20
20265 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
20266 vulnerability introduced by a change in OpenSSL, fixes a remotely
20267 triggerable assert, and adds new channel_t and circuitmux_t abstractions
20268 that will make it easier to test new connection transport and cell
20269 scheduling algorithms.
20271 o New directory authorities (also in 0.2.3.23-rc):
20272 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
20273 authority. Closes ticket 5749.
20275 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
20276 - Disable TLS session tickets. OpenSSL's implementation was giving
20277 our TLS session keys the lifetime of our TLS context objects, when
20278 perfect forward secrecy would want us to discard anything that
20279 could decrypt a link connection as soon as the link connection
20280 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
20281 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
20282 - Discard extraneous renegotiation attempts once the V3 link
20283 protocol has been initiated. Failure to do so left us open to
20284 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
20285 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
20287 o Internal abstraction features:
20288 - Introduce new channel_t abstraction between circuits and
20289 or_connection_t to allow for implementing alternate OR-to-OR
20290 transports. A channel_t is an abstract object which can either be a
20291 cell-bearing channel, which is responsible for authenticating and
20292 handshaking with the remote OR and transmitting cells to and from
20293 it, or a listening channel, which spawns new cell-bearing channels
20294 at the request of remote ORs. Implements part of ticket 6465.
20295 - Also new is the channel_tls_t subclass of channel_t, adapting it
20296 to the existing or_connection_t code. The V2/V3 protocol handshaking
20297 code which formerly resided in command.c has been moved below the
20298 channel_t abstraction layer and may be found in channeltls.c now.
20299 Implements the rest of ticket 6465.
20300 - Introduce new circuitmux_t storing the queue of circuits for
20301 a channel; this encapsulates and abstracts the queue logic and
20302 circuit selection policy, and allows the latter to be overridden
20303 easily by switching out a policy object. The existing EWMA behavior
20304 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
20306 o Required libraries:
20307 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
20308 strongly recommended.
20311 - Warn users who run hidden services on a Tor client with
20312 UseEntryGuards disabled that their hidden services will be
20313 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
20314 attack which motivated Tor to support entry guards in the first
20315 place). Resolves ticket 6889.
20316 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
20317 dhill. Resolves ticket 6982.
20318 - Option OutboundBindAddress can be specified multiple times and
20319 accepts IPv6 addresses. Resolves ticket 6876.
20321 o Minor bugfixes (also in 0.2.3.23-rc):
20322 - Don't serve or accept v2 hidden service descriptors over a
20323 relay's DirPort. It's never correct to do so, and disabling it
20324 might make it more annoying to exploit any bugs that turn up in the
20325 descriptor-parsing code. Fixes bug 7149.
20326 - Fix two cases in src/or/transports.c where we were calling
20327 fmt_addr() twice in a parameter list. Bug found by David
20328 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
20329 - Fix memory leaks whenever we logged any message about the "path
20330 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
20331 - When relays refuse a "create" cell because their queue of pending
20332 create cells is too big (typically because their cpu can't keep up
20333 with the arrival rate), send back reason "resource limit" rather
20334 than reason "internal", so network measurement scripts can get a
20335 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
20338 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
20339 - Free some more still-in-use memory at exit, to make hunting for
20340 memory leaks easier. Resolves bug 7029.
20341 - When a Tor client gets a "truncated" relay cell, the first byte of
20342 its payload specifies why the circuit was truncated. We were
20343 ignoring this 'reason' byte when tearing down the circuit, resulting
20344 in the controller not being told why the circuit closed. Now we
20345 pass the reason from the truncated cell to the controller. Bugfix
20346 on 0.1.2.3-alpha; fixes bug 7039.
20347 - Downgrade "Failed to hand off onionskin" messages to "debug"
20348 severity, since they're typically redundant with the "Your computer
20349 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
20350 - Make clients running with IPv6 bridges connect over IPv6 again,
20351 even without setting new config options ClientUseIPv6 and
20352 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
20353 - Use square brackets around IPv6 addresses in numerous places
20354 that needed them, including log messages, HTTPS CONNECT proxy
20355 requests, TransportProxy statefile entries, and pluggable transport
20356 extra-info lines. Fixes bug 7011; patch by David Fifield.
20358 o Code refactoring and cleanup:
20359 - Source files taken from other packages now reside in src/ext;
20360 previously they were scattered around the rest of Tor.
20361 - Avoid use of reserved identifiers in our C code. The C standard
20362 doesn't like us declaring anything that starts with an
20363 underscore, so let's knock it off before we get in trouble. Fix
20364 for bug 1031; bugfix on the first Tor commit.
20367 Changes in version 0.2.3.23-rc - 2012-10-20
20368 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
20369 vulnerability introduced by a change in OpenSSL, and fixes a variety
20370 of smaller bugs in preparation for the release.
20372 o New directory authorities:
20373 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
20374 authority. Closes ticket 5749.
20376 o Major bugfixes (security/privacy):
20377 - Disable TLS session tickets. OpenSSL's implementation was giving
20378 our TLS session keys the lifetime of our TLS context objects, when
20379 perfect forward secrecy would want us to discard anything that
20380 could decrypt a link connection as soon as the link connection
20381 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
20382 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
20383 - Discard extraneous renegotiation attempts once the V3 link
20384 protocol has been initiated. Failure to do so left us open to
20385 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
20386 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
20389 - Fix a possible crash bug when checking for deactivated circuits
20390 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
20391 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
20393 o Minor bugfixes (on 0.2.3.x):
20394 - Fix two cases in src/or/transports.c where we were calling
20395 fmt_addr() twice in a parameter list. Bug found by David
20396 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
20397 - Convert an assert in the pathbias code to a log message. The assert
20398 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
20399 bugfix on 0.2.3.17-beta.
20400 - Fix memory leaks whenever we logged any message about the "path
20401 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
20403 o Minor bugfixes (on 0.2.2.x and earlier):
20404 - Don't serve or accept v2 hidden service descriptors over a relay's
20405 DirPort. It's never correct to do so, and disabling it might
20406 make it more annoying to exploit any bugs that turn up in the
20407 descriptor-parsing code. Fixes bug 7149.
20408 - When relays refuse a "create" cell because their queue of pending
20409 create cells is too big (typically because their cpu can't keep up
20410 with the arrival rate), send back reason "resource limit" rather
20411 than reason "internal", so network measurement scripts can get a
20412 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
20413 - Correct file sizes when reading binary files on Cygwin, to avoid
20414 a bug where Tor would fail to read its state file. Fixes bug 6844;
20415 bugfix on 0.1.2.7-alpha.
20416 - Avoid undefined behavior when parsing the list of supported
20417 rendezvous/introduction protocols in a hidden service descriptor.
20418 Previously, Tor would have confused (as-yet-unused) protocol version
20419 numbers greater than 32 with lower ones on many platforms. Fixes
20420 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
20422 o Documentation fixes:
20423 - Clarify that hidden services are TCP only. Fixes bug 6024.
20426 Changes in version 0.2.4.3-alpha - 2012-09-22
20427 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
20428 assertion, resumes letting relays test reachability of their DirPort,
20429 and cleans up a bunch of smaller bugs.
20432 - Fix an assertion failure in tor_timegm() that could be triggered
20433 by a badly formatted directory object. Bug found by fuzzing with
20434 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
20437 - Fix a possible crash bug when checking for deactivated circuits
20438 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
20439 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
20440 - Allow routers to detect that their own DirPorts are running. When
20441 we removed support for versions_supports_begindir, we also
20442 accidentally removed the mechanism we used to self-test our
20443 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
20444 bugfix on 0.2.4.2-alpha.
20446 o Security features:
20447 - Switch to a completely time-invariant approach for picking nodes
20448 weighted by bandwidth. Our old approach would run through the
20449 part of the loop after it had made its choice slightly slower
20450 than it ran through the part of the loop before it had made its
20451 choice. Addresses ticket 6538.
20452 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
20453 by tor2web clients allows hidden services to identify tor2web
20454 clients through their repeated selection of the same rendezvous
20455 and introduction point circuit endpoints (their guards). Resolves
20459 - Enable Tor to read configuration, state, and key information from
20460 a FIFO. Previously Tor would only read from files with a positive
20461 stat.st_size. Code from meejah; fixes bug 6044.
20464 - Correct file sizes when reading binary files on Cygwin, to avoid
20465 a bug where Tor would fail to read its state file. Fixes bug 6844;
20466 bugfix on 0.1.2.7-alpha.
20467 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
20468 bugfix on 0.2.0.3-alpha.
20469 - When complaining about a client port on a public address, log
20470 which address we're complaining about. Fixes bug 4020; bugfix on
20471 0.2.3.3-alpha. Patch by Tom Fitzhenry.
20472 - Convert an assert in the pathbias code to a log message. The assert
20473 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
20474 bugfix on 0.2.3.17-beta.
20475 - Our new buildsystem was overzealous about rebuilding manpages: it
20476 would rebuild them all whenever any one of them changed. Now our
20477 dependency checking should be correct. Fixes bug 6843; bugfix on
20479 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
20480 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
20481 - Correct log printout about which address family is preferred
20482 when connecting to a bridge with both an IPv4 and IPv6 OR port.
20483 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
20485 o Minor bugfixes (code cleanliness):
20486 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
20487 with large values. This situation was untriggered, but nevertheless
20488 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
20489 - Reject consensus votes with more than 64 known-flags. We aren't even
20490 close to that limit yet, and our code doesn't handle it correctly.
20491 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
20492 - Avoid undefined behavior when parsing the list of supported
20493 rendezvous/introduction protocols in a hidden service descriptor.
20494 Previously, Tor would have confused (as-yet-unused) protocol version
20495 numbers greater than 32 with lower ones on many platforms. Fixes
20496 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
20497 - Fix handling of rendezvous client authorization types over 8.
20498 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
20499 - Fix building with older versions of GCC (2.95, for one) that don't
20500 like preprocessor directives inside macro arguments. Found by
20501 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
20502 - Switch weighted node selection rule from using a list of doubles
20503 to using a list of int64_t. This change should make the process
20504 slightly easier to debug and maintain. Needed to finish ticket 6538.
20506 o Code simplification and refactoring:
20507 - Move the generic "config" code into a new file, and have "config.c"
20508 hold only torrc- and state-related code. Resolves ticket 6823.
20509 - Move the core of our "choose a weighted element at random" logic
20510 into its own function, and give it unit tests. Now the logic is
20511 testable, and a little less fragile too.
20512 - Removed the testing_since field of node_t, which hasn't been used
20513 for anything since 0.2.0.9-alpha.
20515 o Documentation fixes:
20516 - Clarify that hidden services are TCP only. Fixes bug 6024.
20517 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
20521 Changes in version 0.2.3.22-rc - 2012-09-11
20522 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
20526 - Fix an assertion failure in tor_timegm() that could be triggered
20527 by a badly formatted directory object. Bug found by fuzzing with
20528 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
20531 - Avoid segfault when starting up having run with an extremely old
20532 version of Tor and parsing its state file. Fixes bug 6801; bugfix
20536 Changes in version 0.2.2.39 - 2012-09-11
20537 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
20541 - Fix an assertion failure in tor_timegm() that could be triggered
20542 by a badly formatted directory object. Bug found by fuzzing with
20543 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
20544 - Do not crash when comparing an address with port value 0 to an
20545 address policy. This bug could have been used to cause a remote
20546 assertion failure by or against directory authorities, or to
20547 allow some applications to crash clients. Fixes bug 6690; bugfix
20551 Changes in version 0.2.4.2-alpha - 2012-09-10
20552 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
20553 raises the default rate limiting even more, and makes the bootstrapping
20554 log messages less noisy.
20557 - Automatically forward the TCP ports of pluggable transport
20558 proxies using tor-fw-helper if PortForwarding is enabled. Implements
20562 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
20563 to 1GB/1GB. The previous defaults were intended to be "basically
20564 infinite", but it turns out they're now limiting our 100mbit+
20565 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
20566 last time we raised it).
20569 - Detect when we're running with a version of OpenSSL other than the
20570 one we compiled with. This has occasionally given people hard-to-
20572 - Log fewer lines at level "notice" about our OpenSSL and Libevent
20573 versions and capabilities when everything is going right. Resolves
20574 part of ticket 6736.
20575 - Directory authorities no long accept descriptors for any version of
20576 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
20577 These versions are insecure, unsupported, or both. Implements
20581 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
20582 to start with a triple-underscore so the controller won't touch it.
20583 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
20584 - Avoid segfault when starting up having run with an extremely old
20585 version of Tor and parsing its state file. Fixes bug 6801; bugfix
20587 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
20588 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
20589 - Don't follow the NULL pointer if microdescriptor generation fails.
20590 (This does not appear to be triggerable, but it's best to be safe.)
20591 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
20592 - Fix mis-declared dependencies on src/common/crypto.c and
20593 src/or/tor_main.c that could break out-of-tree builds under some
20594 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
20595 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
20596 6778; bugfix on 0.2.4.1-alpha.
20597 - Fix a harmless (in this case) build warning for implicitly
20598 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
20600 o Removed features:
20601 - Now that all versions before 0.2.2.x are disallowed, we no longer
20602 need to work around their missing features. Thus we can remove a
20603 bunch of compatibility code.
20605 o Code refactoring:
20606 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
20607 TCP ports to forward. In the past it only accepted two ports:
20608 the ORPort and the DirPort.
20611 Changes in version 0.2.4.1-alpha - 2012-09-05
20612 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
20613 bridgedb; lets relays use IPv6 addresses and directory authorities
20614 advertise them; and switches to a cleaner build interface.
20616 This is the first alpha release in a new series, so expect there to
20617 be bugs. Users who would rather test out a more stable branch should
20618 stay with 0.2.3.x for now.
20620 o Major features (bridges):
20621 - Bridges now report the pluggable transports they support to the
20622 bridge authority, so it can pass the supported transports on to
20623 bridgedb and/or eventually do reachability testing. Implements
20626 o Major features (IPv6):
20627 - Bridge authorities now accept IPv6 bridge addresses and include
20628 them in network status documents. Implements ticket 5534.
20629 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
20630 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
20631 to happen. Implements ticket 5535.
20632 - All kind of relays, not just bridges, can now advertise an IPv6
20633 OR port. Implements ticket 6362.
20634 - Directory authorities vote on IPv6 OR ports using the new consensus
20635 method 14. Implements ticket 6363.
20637 o Major features (build):
20638 - Switch to a nonrecursive Makefile structure. Now instead of each
20639 Makefile.am invoking other Makefile.am's, there is a master
20640 Makefile.am that includes the others. This change makes our build
20641 process slightly more maintainable, and improves parallelism for
20642 building with make -j. Original patch by Stewart Smith; various
20643 fixes by Jim Meyering.
20644 - Where available, we now use automake's "silent" make rules by
20645 default, so that warnings are easier to spot. You can get the old
20646 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
20648 o Minor features (code security and spec conformance):
20649 - Clear keys and key-derived material left on the stack in
20650 rendservice.c and rendclient.c. Check return value of
20651 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
20652 These fixes should make us more forward-secure against cold-boot
20653 attacks and the like. Fixes bug 2385.
20654 - Reject EXTEND cells sent to nonexistent streams. According to the
20655 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
20656 we were only checking for stream IDs that were currently in use.
20657 Found while hunting for more instances of bug 6271. Bugfix on
20658 0.0.2pre8, which introduced incremental circuit construction.
20660 o Minor features (streamlining);
20661 - No longer include the "opt" prefix when generating routerinfos
20662 or v2 directories: it has been needless since Tor 0.1.2. Closes
20664 - Remove some now-needless code that tried to aggressively flush
20665 OR connections as data was added to them. Since 0.2.0.1-alpha, our
20666 cell queue logic has saved us from the failure mode that this code
20667 was supposed to prevent. Removing this code will limit the number
20668 of baroque control flow paths through Tor's network logic. Reported
20669 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
20671 o Minor features (controller):
20672 - Add a "GETINFO signal/names" control port command. Implements
20674 - Provide default values for all options via "GETINFO config/defaults".
20675 Implements ticket 4971.
20677 o Minor features (IPv6):
20678 - New config option "AuthDirHasIPv6Connectivity 1" that directory
20679 authorities should set if they have IPv6 connectivity and want to
20680 do reachability tests for IPv6 relays. Implements feature 5974.
20681 - A relay with an IPv6 OR port now sends that address in NETINFO
20682 cells (in addition to its other address). Implements ticket 6364.
20684 o Minor features (log messages):
20685 - Omit the first heartbeat log message, because it never has anything
20686 useful to say, and it clutters up the bootstrapping messages.
20687 Resolves ticket 6758.
20688 - Don't log about reloading the microdescriptor cache at startup. Our
20689 bootstrap warnings are supposed to tell the user when there's a
20690 problem, and our bootstrap notices say when there isn't. Resolves
20691 ticket 6759; bugfix on 0.2.2.6-alpha.
20692 - Don't log "I learned some more directory information" when we're
20693 reading cached directory information. Reserve it for when new
20694 directory information arrives in response to a fetch. Resolves
20696 - Prevent rounding error in path bias counts when scaling
20697 them down, and use the correct scale factor default. Also demote
20698 some path bias related log messages down a level and make others
20699 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
20700 - We no longer warn so much when generating manpages from their
20703 o Code simplifications and refactoring:
20704 - Enhance our internal sscanf replacement so that we can eliminate
20705 the last remaining uses of the system sscanf. (Though those uses
20706 of sscanf were safe, sscanf itself is generally error prone, so
20707 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
20709 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
20710 - Move last_reachable and testing_since from routerinfo_t to node_t.
20711 Implements ticket 5529.
20712 - Add replaycache_t structure, functions and unit tests, then refactor
20713 rend_service_introduce() to be more clear to read, improve, debug,
20714 and test. Resolves bug 6177.
20715 - Finally remove support for malloc_good_size and malloc_usable_size.
20716 We had hoped that these functions would let us eke a little more
20717 memory out of our malloc implementation. Unfortunately, the only
20718 implementations that provided these functions are also ones that
20719 are already efficient about not overallocation: they never got us
20720 more than 7 or so bytes per allocation. Removing them saves us a
20721 little code complexity and a nontrivial amount of build complexity.
20723 o New requirements:
20724 - Tor maintainers now require Automake version 1.9 or later to build
20725 Tor from the Git repository. (Automake is not required when building
20726 from a source distribution.)
20729 Changes in version 0.2.3.21-rc - 2012-09-05
20730 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
20731 series. It fixes a trio of potential security bugs, fixes a bug where
20732 we were leaving some of the fast relays out of the microdescriptor
20733 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
20734 and cleans up other smaller issues.
20736 o Major bugfixes (security):
20737 - Tear down the circuit if we get an unexpected SENDME cell. Clients
20738 could use this trick to make their circuits receive cells faster
20739 than our flow control would have allowed, or to gum up the network,
20740 or possibly to do targeted memory denial-of-service attacks on
20741 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
20742 from July 2002, before the release of Tor 0.0.0. We had committed
20743 this patch previously, but we had to revert it because of bug 6271.
20744 Now that 6271 is fixed, this patch appears to work.
20745 - Reject any attempt to extend to an internal address. Without
20746 this fix, a router could be used to probe addresses on an internal
20747 network to see whether they were accepting connections. Fixes bug
20748 6710; bugfix on 0.0.8pre1.
20749 - Do not crash when comparing an address with port value 0 to an
20750 address policy. This bug could have been used to cause a remote
20751 assertion failure by or against directory authorities, or to
20752 allow some applications to crash clients. Fixes bug 6690; bugfix
20756 - Remove the upper bound on microdescriptor length. We were hitting
20757 the limit for routers with complex exit policies or family
20758 declarations, causing clients to not use them. Fixes the first
20759 piece of bug 6404; fix on 0.2.2.6-alpha.
20760 - Detect "ORPort 0" as meaning, uniformly, that we're not running
20761 as a relay. Previously, some of our code would treat the presence
20762 of any ORPort line as meaning that we should act like a relay,
20763 even though our new listener code would correctly not open any
20764 ORPorts for ORPort 0. Similar bugs in other Port options are also
20765 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
20768 - Avoid a pair of double-free and use-after-mark bugs that can
20769 occur with certain timings in canceled and re-received DNS
20770 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
20771 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
20772 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
20773 - Allow one-hop directory fetching circuits the full "circuit build
20774 timeout" period, rather than just half of it, before failing them
20775 and marking the relay down. This fix should help reduce cases where
20776 clients declare relays (or worse, bridges) unreachable because
20777 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
20778 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
20780 - Authorities no longer include any router in their microdescriptor
20781 consensuses for which they couldn't generate or agree on a
20782 microdescriptor. Fixes the second piece of bug 6404; fix on
20784 - Detect and reject attempts to specify both "FooPort" and
20785 "FooPort 0" in the same configuration domain. (It's still okay
20786 to have a FooPort in your configuration file, and use "FooPort 0"
20787 on the command line to disable it.) Fixes the second half of bug
20788 6507; bugfix on 0.2.3.3-alpha.
20789 - Make wildcarded addresses (that is, ones beginning with "*.") work
20790 when provided via the controller's MapAddress command. Previously,
20791 they were accepted, but we never actually noticed that they were
20792 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
20793 - Avoid crashing on a malformed state file where EntryGuardPathBias
20794 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
20795 - Add a (probably redundant) memory clear between iterations of
20796 the router status voting loop, to prevent future coding errors
20797 where data might leak between iterations of the loop. Resolves
20800 o Minor bugfixes (log messages):
20801 - Downgrade "set buildtimeout to low value" messages to "info"
20802 severity; they were never an actual problem, there was never
20803 anything reasonable to do about them, and they tended to spam logs
20804 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
20805 - Downgrade path-bias warning messages to "info". We'll try to get
20806 them working better in 0.2.4. Add internal circuit construction
20807 state to protect against the noisy warn message "Unexpectedly high
20808 circuit_successes". Also add some additional rate-limited notice
20809 messages to help determine the root cause of the warn. Fixes bug
20810 6475. Bugfix against 0.2.3.17-beta.
20811 - Move log message when unable to find a microdesc in a routerstatus
20812 entry to parse time. Previously we'd spam this warning every time
20813 we tried to figure out which microdescriptors to download. Fixes
20814 the third piece of bug 6404; fix on 0.2.3.18-rc.
20817 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
20818 change when the authority is deciding whether to accept a newly
20819 uploaded descriptor. Implements ticket 6423.
20820 - Add missing documentation for consensus and microdesc files.
20821 Resolves ticket 6732.
20824 Changes in version 0.2.2.38 - 2012-08-12
20825 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
20826 attack that could in theory leak path information.
20829 - Avoid an uninitialized memory read when reading a vote or consensus
20830 document that has an unrecognized flavor name. This read could
20831 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
20832 - Try to leak less information about what relays a client is
20833 choosing to a side-channel attacker. Previously, a Tor client would
20834 stop iterating through the list of available relays as soon as it
20835 had chosen one, thus finishing a little earlier when it picked
20836 a router earlier in the list. If an attacker can recover this
20837 timing information (nontrivial but not proven to be impossible),
20838 they could learn some coarse-grained information about which relays
20839 a client was picking (middle nodes in particular are likelier to
20840 be affected than exits). The timing attack might be mitigated by
20841 other factors (see bug 6537 for some discussion), but it's best
20842 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
20845 Changes in version 0.2.3.20-rc - 2012-08-05
20846 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
20847 series. It fixes a pair of code security bugs and a potential anonymity
20848 issue, updates our RPM spec files, and cleans up other smaller issues.
20851 - Avoid read-from-freed-memory and double-free bugs that could occur
20852 when a DNS request fails while launching it. Fixes bug 6480;
20853 bugfix on 0.2.0.1-alpha.
20854 - Avoid an uninitialized memory read when reading a vote or consensus
20855 document that has an unrecognized flavor name. This read could
20856 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
20857 - Try to leak less information about what relays a client is
20858 choosing to a side-channel attacker. Previously, a Tor client would
20859 stop iterating through the list of available relays as soon as it
20860 had chosen one, thus finishing a little earlier when it picked
20861 a router earlier in the list. If an attacker can recover this
20862 timing information (nontrivial but not proven to be impossible),
20863 they could learn some coarse-grained information about which relays
20864 a client was picking (middle nodes in particular are likelier to
20865 be affected than exits). The timing attack might be mitigated by
20866 other factors (see bug 6537 for some discussion), but it's best
20867 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
20870 - Try to make the warning when giving an obsolete SOCKSListenAddress
20871 a little more useful.
20872 - Terminate active server managed proxies if Tor stops being a
20873 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
20874 - Provide a better error message about possible OSX Asciidoc failure
20875 reasons. Fixes bug 6436.
20876 - Warn when Tor is configured to use accounting in a way that can
20877 link a hidden service to some other hidden service or public
20878 address. Resolves ticket 6490.
20881 - Check return value of fputs() when writing authority certificate
20882 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
20883 - Ignore ServerTransportPlugin lines when Tor is not configured as
20884 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
20885 - When disabling guards for having too high a proportion of failed
20886 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
20890 - Update our default RPM spec files to work with mock and rpmbuild
20891 on RHEL/Fedora. They have an updated set of dependencies and
20892 conflicts, a fix for an ancient typo when creating the "_tor"
20893 user, and better instructions. Thanks to Ondrej Mikle for the
20894 patch series. Fixes bug 6043.
20897 - Make it possible to set the TestingTorNetwork configuration
20898 option using AlternateDirAuthority and AlternateBridgeAuthority
20899 as an alternative to setting DirServer. Addresses ticket 6377.
20902 - Clarify the documentation for the Alternate*Authority options.
20904 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
20906 o Code simplification and refactoring:
20907 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
20908 10 lines. Also, don't nest them. Doing so in the past has
20909 led to hard-to-debug code. The new style is to use the
20910 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
20913 Changes in version 0.2.3.19-rc - 2012-07-06
20914 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
20915 series. It fixes the compile on Windows, reverts to a GeoIP database
20916 that isn't as broken, and fixes a flow control bug that has been around
20917 since the beginning of Tor.
20920 - Fix a bug handling SENDME cells on nonexistent streams that could
20921 result in bizarre window values. Report and patch contributed
20922 pseudonymously. Fixes part of bug 6271. This bug was introduced
20923 before the first Tor release, in svn commit r152.
20924 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
20925 June 2012 database, Maxmind marked many Tor relays as country "A1",
20926 which will cause risky behavior for clients that set EntryNodes
20927 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
20928 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
20929 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
20932 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
20933 bugfix on 0.2.1.10-alpha.
20936 Changes in version 0.2.3.18-rc - 2012-06-28
20937 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
20938 series. It fixes a few smaller bugs, but generally appears stable.
20939 Please test it and let us know whether it is!
20942 - Allow wildcarded mapaddress targets to be specified on the
20943 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
20944 - Make our linker option detection code more robust against linkers
20945 such as on FreeBSD 8, where a bad combination of options completes
20946 successfully but makes an unrunnable binary. Fixes bug 6173;
20947 bugfix on 0.2.3.17-beta.
20949 o Minor bugfixes (on 0.2.2.x and earlier):
20950 - Avoid a false positive in the util/threads unit test by increasing
20951 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
20952 - Replace "Sending publish request" log messages with "Launching
20953 upload", so that they no longer confusingly imply that we're
20954 sending something to a directory we might not even be connected
20955 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
20956 - Make sure to set *socket_error in all error cases in
20957 connection_connect(), so it can't produce a warning about
20958 errno being zero from errno_to_orconn_end_reason(). Bugfix on
20959 0.2.1.1-alpha; resolves ticket 6028.
20960 - Downgrade "Got a certificate, but we already have it" log messages
20961 from warning to info, except when we're a dirauth. Fixes bug 5238;
20962 bugfix on 0.2.1.7-alpha.
20963 - When checking for requested signatures on the latest consensus
20964 before serving it to a client, make sure to check the right
20965 consensus flavor. Bugfix on 0.2.2.6-alpha.
20966 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
20967 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
20969 o Minor bugfixes (on 0.2.3.x):
20970 - Make format_helper_exit_status() avoid unnecessary space padding
20971 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
20973 - Downgrade a message about cleaning the microdescriptor cache to
20974 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
20975 - Log a BUG message at severity INFO if we have a networkstatus with
20976 a missing entry for some microdescriptor. Continues on a patch
20978 - Improve the log message when a managed proxy fails to launch. Fixes
20979 bug 5099; bugfix on 0.2.3.6-alpha.
20980 - Don't do DNS lookups when parsing corrupted managed proxy protocol
20981 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
20982 - When formatting wildcarded address mappings for the controller,
20983 be sure to include "*." as appropriate. Partially fixes bug 6244;
20984 bugfix on 0.2.3.9-alpha.
20985 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
20986 Bugfix on 0.2.3.13-alpha.
20987 - Stop logging messages about running with circuit timeout learning
20988 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
20989 - Disable a spurious warning about reading on a marked and flushing
20990 connection. We shouldn't be doing that, but apparently we
20991 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
20992 - Fix a bug that stopped AllowDotExit from working on addresses
20993 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
20996 o Code simplification, refactoring, unit tests:
20997 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
20998 Libevent's notion of cached time when possible.
20999 - Remove duplicate code for invoking getrlimit() from control.c.
21000 - Add a unit test for the environment_variable_names_equal function.
21003 - Document the --defaults-torrc option, and the new (in 0.2.3)
21004 semantics for overriding, extending, and clearing lists of
21005 options. Closes bug 4748.
21008 Changes in version 0.2.3.17-beta - 2012-06-15
21009 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
21010 gets our TLS handshake back on track for being able to blend in with
21011 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
21012 with Vidalia, and otherwise continues to get us closer to a release
21016 - Enable gcc and ld hardening by default. Resolves ticket 5210.
21017 - Update TLS cipher list to match Firefox 8 and later. Resolves
21019 - Implement the client side of proposal 198: remove support for
21020 clients falsely claiming to support standard ciphersuites that
21021 they can actually provide. As of modern OpenSSL versions, it's not
21022 necessary to fake any standard ciphersuite, and doing so prevents
21023 us from using better ciphersuites in the future, since servers
21024 can't know whether an advertised ciphersuite is really supported or
21025 not. Some hosts -- notably, ones with very old versions of OpenSSL
21026 or where OpenSSL has been built with ECC disabled -- will stand
21027 out because of this change; TBB users should not be affected.
21030 - Change the default value for DynamicDHGroups (introduced in
21031 0.2.3.9-alpha) to 0. This feature can make Tor relays less
21032 identifiable by their use of the mod_ssl DH group, but at
21033 the cost of some usability (#4721) and bridge tracing (#6087)
21034 regressions. Resolves ticket 5598.
21035 - Send a CRLF at the end of each STATUS_* control protocol event. This
21036 bug tickled a bug in Vidalia which would make it freeze. Fixes
21037 bug 6094; bugfix on 0.2.3.16-alpha.
21040 - Disable writing on marked-for-close connections when they are
21041 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
21042 bug 5263; bugfix on 0.0.2pre13, where we first added a special
21043 case for flushing marked connections.
21044 - Detect SSL handshake even when the initial attempt to write the
21045 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
21046 - Change the AllowDotExit rules so they should actually work.
21047 We now enforce AllowDotExit only immediately after receiving an
21048 address via SOCKS or DNSPort: other sources are free to provide
21049 .exit addresses after the resolution occurs. Fixes bug 3940;
21050 bugfix on 0.2.2.1-alpha.
21051 - Fix a (harmless) integer overflow in cell statistics reported by
21052 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
21053 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
21054 right places and never depends on the consensus parameters or
21055 computes adaptive timeouts when it is disabled. Fixes bug 5049;
21056 bugfix on 0.2.2.14-alpha.
21057 - When building Tor on Windows with -DUNICODE (not default), ensure
21058 that error messages, filenames, and DNS server names are always
21059 NUL-terminated when we convert them to a single-byte encoding.
21060 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
21061 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
21062 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
21063 - Fix an edge case where TestingTorNetwork is set but the authorities
21064 and relays all have an uptime of zero, where the private Tor network
21065 could briefly lack support for hidden services. Fixes bug 3886;
21066 bugfix on 0.2.2.18-alpha.
21067 - Correct the manpage's descriptions for the default values of
21068 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
21070 - Fix the documentation for the --hush and --quiet command line
21071 options, which changed their behavior back in 0.2.3.3-alpha.
21072 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
21076 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
21077 more information to it, so that we can track it down in case it
21078 returns again. Mitigates bug 5235.
21079 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
21080 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
21081 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
21082 - Warn the user when HTTPProxy, but no other proxy type, is
21083 configured. This can cause surprising behavior: it doesn't send
21084 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
21085 directory traffic only. Resolves ticket 4663.
21086 - Issue a notice if a guard completes less than 40% of your circuits.
21087 Threshold is configurable by torrc option PathBiasNoticeRate and
21088 consensus parameter pb_noticepct. There is additional, off-by-
21089 default code to disable guards which fail too many circuits.
21090 Addresses ticket 5458.
21091 - Update to the June 6 2012 Maxmind GeoLite Country database.
21093 o Code simplifications and refactoring:
21094 - Remove validate_pluggable_transports_config(): its warning
21095 message is now handled by connection_or_connect().
21098 Changes in version 0.2.2.37 - 2012-06-06
21099 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
21100 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
21104 - Work around a bug in OpenSSL that broke renegotiation with TLS
21105 1.1 and TLS 1.2. Without this workaround, all attempts to speak
21106 the v2 Tor connection protocol when both sides were using OpenSSL
21107 1.0.1 would fail. Resolves ticket 6033.
21108 - When waiting for a client to renegotiate, don't allow it to add
21109 any bytes to the input buffer. This fixes a potential DoS issue.
21110 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
21111 - Fix an edge case where if we fetch or publish a hidden service
21112 descriptor, we might build a 4-hop circuit and then use that circuit
21113 for exiting afterwards -- even if the new last hop doesn't obey our
21114 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
21117 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
21118 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
21121 - Tell GCC and Clang to check for any errors in format strings passed
21122 to the tor_v*(print|scan)f functions.
21125 Changes in version 0.2.3.16-alpha - 2012-06-05
21126 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
21127 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
21128 currently). It also fixes a variety of smaller bugs and other cleanups
21129 that get us closer to a release candidate.
21131 o Major bugfixes (general):
21132 - Work around a bug in OpenSSL that broke renegotiation with TLS
21133 1.1 and TLS 1.2. Without this workaround, all attempts to speak
21134 the v2 Tor connection protocol when both sides were using OpenSSL
21135 1.0.1 would fail. Resolves ticket 6033.
21136 - When waiting for a client to renegotiate, don't allow it to add
21137 any bytes to the input buffer. This fixes a potential DoS issue.
21138 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
21139 - Pass correct OR address to managed proxies (like obfsproxy),
21140 even when ORListenAddress is used. Fixes bug 4865; bugfix on
21142 - The advertised platform of a router now includes only its operating
21143 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
21144 service pack level (for Windows) or its CPU architecture (for Unix).
21145 We also no longer include the "git-XYZ" tag in the version. Resolves
21148 o Major bugfixes (clients):
21149 - If we are unable to find any exit that supports our predicted ports,
21150 stop calling them predicted, so that we don't loop and build
21151 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
21152 which introduced predicted ports.
21153 - Fix an edge case where if we fetch or publish a hidden service
21154 descriptor, we might build a 4-hop circuit and then use that circuit
21155 for exiting afterwards -- even if the new last hop doesn't obey our
21156 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
21157 - Check at each new consensus whether our entry guards were picked
21158 long enough ago that we should rotate them. Previously, we only
21159 did this check at startup, which could lead to us holding a guard
21160 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
21161 - When fetching a bridge descriptor from a bridge authority,
21162 always do so anonymously, whether we have been able to open
21163 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
21164 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
21165 but we'll need to wait for bug 6010 before it's actually usable.
21167 o Major bugfixes (directory authorities):
21168 - When computing weight parameters, behave more robustly in the
21169 presence of a bad bwweightscale value. Previously, the authorities
21170 would crash if they agreed on a sufficiently broken weight_scale
21171 value: now, they use a reasonable default and carry on. Partial
21172 fix for 5786; bugfix on 0.2.2.17-alpha.
21173 - Check more thoroughly to prevent a rogue authority from
21174 double-voting on any consensus directory parameter. Previously,
21175 authorities would crash in this case if the total number of
21176 votes for any parameter exceeded the number of active voters,
21177 but would let it pass otherwise. Partial fix for bug 5786; bugfix
21181 - Rate-limit log messages when asked to connect anonymously to
21182 a private address. When these hit, they tended to hit fast and
21183 often. Also, don't bother trying to connect to addresses that we
21184 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
21185 reply makes us think we have been lied to, even when the address the
21186 client tried to connect to was "localhost." Resolves ticket 2822.
21187 - Allow packagers to insert an extra string in server descriptor
21188 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
21189 Resolves the rest of ticket 2988.
21190 - Raise the threshold of server descriptors needed (75%) and exit
21191 server descriptors needed (50%) before we will declare ourselves
21192 bootstrapped. This will make clients start building circuits a
21193 little later, but makes the initially constructed circuits less
21194 skewed and less in conflict with further directory fetches. Fixes
21196 - Close any connection that sends unrecognized junk before the
21197 handshake. Solves an issue noted in bug 4369.
21198 - Improve log messages about managed transports. Resolves ticket 5070.
21199 - Tag a bridge's descriptor as "never to be sent unencrypted".
21200 This shouldn't matter, since bridges don't open non-anonymous
21201 connections to the bridge authority and don't allow unencrypted
21202 directory connections from clients, but we might as well make
21203 sure. Closes bug 5139.
21204 - Expose our view of whether we have gone dormant to the controller,
21205 via a new "GETINFO dormant" value. Torbutton and other controllers
21206 can use this to avoid doing periodic requests through Tor while
21207 it's dormant (bug 4718). Fixes bug 5954.
21208 - Tell GCC and Clang to check for any errors in format strings passed
21209 to the tor_v*(print|scan)f functions.
21210 - Update to the May 1 2012 Maxmind GeoLite Country database.
21212 o Minor bugfixes (already included in 0.2.2.36):
21213 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
21214 Fixes bug 5346; bugfix on 0.0.8pre3.
21215 - Correct parsing of certain date types in parse_http_time().
21216 Without this patch, If-Modified-Since would behave
21217 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
21218 Esteban Manchado Velázques.
21219 - Make our number-parsing functions always treat too-large values
21220 as an error, even when those values exceed the width of the
21221 underlying type. Previously, if the caller provided these
21222 functions with minima or maxima set to the extreme values of the
21223 underlying integer type, these functions would return those
21224 values on overflow rather than treating overflow as an error.
21225 Fixes part of bug 5786; bugfix on 0.0.9.
21226 - If we hit the error case where routerlist_insert() replaces an
21227 existing (old) server descriptor, make sure to remove that
21228 server descriptor from the old_routers list. Fix related to bug
21229 1776. Bugfix on 0.2.2.18-alpha.
21230 - Clarify the behavior of MaxCircuitDirtiness with hidden service
21231 circuits. Fixes issue 5259.
21233 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
21234 - Prevent a null-pointer dereference when receiving a data cell
21235 for a nonexistent stream when the circuit in question has an
21236 empty deliver window. We don't believe this is triggerable,
21237 since we don't currently allow deliver windows to become empty,
21238 but the logic is tricky enough that it's better to make the code
21239 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
21240 - Fix a memory leak when trying to launch a DNS request when the
21241 network is disabled or the nameservers are unconfigurable. Fixes
21242 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
21243 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
21244 - Don't hold a Windows file handle open for every file mapping;
21245 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
21247 - Avoid O(n^2) performance characteristics when parsing a large
21248 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
21249 - Format more doubles with %f, not %lf. Patch from grarpamp to make
21250 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
21252 - Make our replacement implementation of strtok_r() compatible with
21253 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
21254 bugfix on 0.2.2.1-alpha.
21255 - Fix a NULL-pointer dereference on a badly formed
21256 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
21257 bugfix on 0.2.2.9-alpha.
21258 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
21259 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
21260 - Defensively refactor rend_mid_rendezvous() so that protocol
21261 violations and length checks happen in the beginning. Fixes
21263 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
21264 that IPv6 stuff will compile on MSVC, and compilation issues
21265 will be easier to track down. Fixes bug 5861.
21267 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
21268 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
21269 resource exhaustion, so that clients can adjust their load to
21270 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
21271 started using END_STREAM_REASON_RESOURCELIMIT.
21272 - Don't check for whether the address we're using for outbound
21273 connections has changed until after the outbound connection has
21274 completed. On Windows, getsockname() doesn't succeed until the
21275 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
21276 - If the configuration tries to set MyFamily on a bridge, refuse to
21277 do so, and warn about the security implications. Fixes bug 4657;
21278 bugfix on 0.2.0.3-alpha.
21279 - If the client fails to set a reasonable set of ciphersuites
21280 during its v2 handshake renegotiation, allow the renegotiation to
21281 continue nevertheless (i.e. send all the required certificates).
21282 Fixes bug 4591; bugfix on 0.2.0.20-rc.
21283 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
21284 option is set to 0 (which Vidalia version 0.2.16 now does when
21285 a SAVECONF attempt fails), perform other actions that SIGHUP
21286 usually causes (like reopening the logs). Fixes bug 5095; bugfix
21288 - If we fail to write a microdescriptor to the disk cache, do not
21289 continue replacing the old microdescriptor file. Fixes bug 2954;
21290 bugfix on 0.2.2.6-alpha.
21291 - Exit nodes don't need to fetch certificates for authorities that
21292 they don't recognize; only directory authorities, bridges,
21293 and caches need to do that. Fixes part of bug 2297; bugfix on
21295 - Correctly handle checking the permissions on the parent
21296 directory of a control socket in the root directory. Bug found
21297 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
21299 - When told to add a bridge with the same digest as a preexisting
21300 bridge but a different addr:port, change the addr:port as
21301 requested. Previously we would not notice the change. Fixes half
21302 of bug 5603; fix on 0.2.2.26-beta.
21303 - End AUTHCHALLENGE error messages (in the control protocol) with
21304 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
21306 o Minor bugfixes (on 0.2.3.x):
21307 - Turn an assertion (that the number of handshakes received as a
21308 server is not < 1) into a warning. Fixes bug 4873; bugfix on
21310 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
21311 we had reversed them when the answer was cached.) Fixes bug
21312 5723; bugfix on 0.2.3.1-alpha.
21313 - Work correctly on Linux systems with accept4 support advertised in
21314 their headers, but without accept4 support in the kernel. Fix
21315 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
21316 - When told to add a bridge with the same addr:port as a preexisting
21317 bridge but a different transport, change the transport as
21318 requested. Previously we would not notice the change. Fixes half
21319 of bug 5603; fix on 0.2.3.2-alpha.
21320 - Avoid a "double-reply" warning when replying to a SOCKS request
21321 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
21322 bugfix on 0.2.3.4-alpha.
21323 - Fix a bug where a bridge authority crashes if it has seen no
21324 directory requests when it's time to write statistics to disk.
21325 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
21327 - Don't try to open non-control listeners when DisableNetwork is set.
21328 Previously, we'd open all listeners, then immediately close them.
21329 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
21330 - Don't abort the managed proxy protocol if the managed proxy
21331 sends us an unrecognized line; ignore it instead. Fixes bug
21332 5910; bugfix on 0.2.3.9-alpha.
21333 - Fix a compile warning in crypto.c when compiling with clang 3.1.
21334 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
21335 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
21336 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
21337 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
21338 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
21339 - Resolve numerous small warnings and build issues with MSVC. Resolves
21342 o Documentation fixes:
21343 - Improve the manual's documentation for the NT Service command-line
21344 options. Addresses ticket 3964.
21345 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
21346 - Document the changes to the ORPort and DirPort options, and the
21347 fact that {OR/Dir}ListenAddress is now unnecessary (and
21348 therefore deprecated). Resolves ticket 5597.
21351 - Remove the torrc.bridge file: we don't use it for anything, and
21352 it had become badly desynchronized from torrc.sample. Resolves
21356 Changes in version 0.2.2.36 - 2012-05-24
21357 Tor 0.2.2.36 updates the addresses for two of the eight directory
21358 authorities, fixes some potential anonymity and security issues,
21359 and fixes several crash bugs.
21361 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
21362 known flaws, and nobody should be using them. You should upgrade. If
21363 you're using a Linux or BSD and its packages are obsolete, stop using
21364 those packages and upgrade anyway.
21366 o Directory authority changes:
21367 - Change IP address for maatuska (v3 directory authority).
21368 - Change IP address for ides (v3 directory authority), and rename
21372 - When building or running with any version of OpenSSL earlier
21373 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
21374 versions have a bug (CVE-2011-4576) in which their block cipher
21375 padding includes uninitialized data, potentially leaking sensitive
21376 information to any peer with whom they make a SSLv3 connection. Tor
21377 does not use SSL v3 by default, but a hostile client or server
21378 could force an SSLv3 connection in order to gain information that
21379 they shouldn't have been able to get. The best solution here is to
21380 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
21381 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
21382 to make sure that the bug can't happen.
21383 - Never use a bridge or a controller-supplied node as an exit, even
21384 if its exit policy allows it. Found by wanoskarnet. Fixes bug
21385 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
21386 and 0.2.0.3-alpha (for bridge-purpose descriptors).
21387 - Only build circuits if we have a sufficient threshold of the total
21388 descriptors that are marked in the consensus with the "Exit"
21389 flag. This mitigates an attack proposed by wanoskarnet, in which
21390 all of a client's bridges collude to restrict the exit nodes that
21391 the client knows about. Fixes bug 5343.
21392 - Provide controllers with a safer way to implement the cookie
21393 authentication mechanism. With the old method, if another locally
21394 running program could convince a controller that it was the Tor
21395 process, then that program could trick the controller into telling
21396 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
21397 authentication method uses a challenge-response approach to prevent
21398 this attack. Fixes bug 5185; implements proposal 193.
21401 - Avoid logging uninitialized data when unable to decode a hidden
21402 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
21403 - Avoid a client-side assertion failure when receiving an INTRODUCE2
21404 cell on a general purpose circuit. Fixes bug 5644; bugfix on
21406 - Fix builds when the path to sed, openssl, or sha1sum contains
21407 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
21409 - Correct our replacements for the timeradd() and timersub() functions
21410 on platforms that lack them (for example, Windows). The timersub()
21411 function is used when expiring circuits, while timeradd() is
21412 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
21413 bugfix on 0.2.2.24-alpha.
21414 - Fix the SOCKET_OK test that we use to tell when socket
21415 creation fails so that it works on Win64. Fixes part of bug 4533;
21416 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
21419 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
21420 Fixes bug 5346; bugfix on 0.0.8pre3.
21421 - Make our number-parsing functions always treat too-large values
21422 as an error, even when those values exceed the width of the
21423 underlying type. Previously, if the caller provided these
21424 functions with minima or maxima set to the extreme values of the
21425 underlying integer type, these functions would return those
21426 values on overflow rather than treating overflow as an error.
21427 Fixes part of bug 5786; bugfix on 0.0.9.
21428 - Older Linux kernels erroneously respond to strange nmap behavior
21429 by having accept() return successfully with a zero-length
21430 socket. When this happens, just close the connection. Previously,
21431 we would try harder to learn the remote address: but there was
21432 no such remote address to learn, and our method for trying to
21433 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
21434 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
21435 - Correct parsing of certain date types in parse_http_time().
21436 Without this patch, If-Modified-Since would behave
21437 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
21438 Esteban Manchado Velázques.
21439 - Change the BridgePassword feature (part of the "bridge community"
21440 design, which is not yet implemented) to use a time-independent
21441 comparison. The old behavior might have allowed an adversary
21442 to use timing to guess the BridgePassword value. Fixes bug 5543;
21443 bugfix on 0.2.0.14-alpha.
21444 - Detect and reject certain misformed escape sequences in
21445 configuration values. Previously, these values would cause us
21446 to crash if received in a torrc file or over an authenticated
21447 control port. Bug found by Esteban Manchado Velázquez, and
21448 independently by Robert Connolly from Matta Consulting who further
21449 noted that it allows a post-authentication heap overflow. Patch
21450 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
21451 bugfix on 0.2.0.16-alpha.
21452 - Fix a compile warning when using the --enable-openbsd-malloc
21453 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
21454 - During configure, detect when we're building with clang version
21455 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
21456 CFLAGS. clang doesn't support them yet.
21457 - When sending an HTTP/1.1 proxy request, include a Host header.
21458 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
21459 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
21460 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
21461 - If we hit the error case where routerlist_insert() replaces an
21462 existing (old) server descriptor, make sure to remove that
21463 server descriptor from the old_routers list. Fix related to bug
21464 1776. Bugfix on 0.2.2.18-alpha.
21466 o Minor bugfixes (documentation and log messages):
21467 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
21468 Fixes bug 4856; bugfix on Tor 0.0.6.
21469 - Update "ClientOnly" man page entry to explain that there isn't
21470 really any point to messing with it. Resolves ticket 5005.
21471 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
21472 directory authority option (introduced in Tor 0.2.2.34).
21473 - Downgrade the "We're missing a certificate" message from notice
21474 to info: people kept mistaking it for a real problem, whereas it
21475 is seldom the problem even when we are failing to bootstrap. Fixes
21476 bug 5067; bugfix on 0.2.0.10-alpha.
21477 - Correctly spell "connect" in a log message on failure to create a
21478 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
21479 - Clarify the behavior of MaxCircuitDirtiness with hidden service
21480 circuits. Fixes issue 5259.
21483 - Directory authorities now reject versions of Tor older than
21484 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
21485 inclusive. These versions accounted for only a small fraction of
21486 the Tor network, and have numerous known security issues. Resolves
21488 - Update to the May 1 2012 Maxmind GeoLite Country database.
21491 - When sending or relaying a RELAY_EARLY cell, we used to convert
21492 it to a RELAY cell if the connection was using the v1 link
21493 protocol. This was a workaround for older versions of Tor, which
21494 didn't handle RELAY_EARLY cells properly. Now that all supported
21495 versions can handle RELAY_EARLY cells, and now that we're enforcing
21496 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
21497 remove this workaround. Addresses bug 4786.
21500 Changes in version 0.2.3.15-alpha - 2012-04-30
21501 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
21502 the development branch build on Windows again.
21504 o Minor bugfixes (on 0.2.2.x and earlier):
21505 - Make sure that there are no unhandled pending TLS errors before
21506 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
21507 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
21508 Bugfix on 0.1.0.5-rc; fixes bug 4528.
21509 - Fix an assert that directory authorities could trigger on sighup
21510 during some configuration state transitions. We now don't treat
21511 it as a fatal error when the new descriptor we just generated in
21512 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
21513 - After we pick a directory mirror, we would refuse to use it if
21514 it's in our ExcludeExitNodes list, resulting in mysterious failures
21515 to bootstrap for people who just wanted to avoid exiting from
21516 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
21517 - When building with --enable-static-tor on OpenBSD, do not
21518 erroneously attempt to link -lrt. Fixes bug 5103.
21520 o Minor bugfixes (on 0.2.3.x):
21521 - When Tor is built with kernel headers from a recent (last few
21522 years) Linux kernel, do not fail to run on older (pre-2.6.28
21523 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
21524 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
21525 and 0.2.3.12-alpha.
21526 - Fix compilation with miniupnpc version 1.6; patch from
21527 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
21528 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
21529 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
21530 - Fix compilation on platforms without unistd.h, or where environ
21531 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
21534 - Directory authorities are now a little more lenient at accepting
21535 older router descriptors, or newer router descriptors that don't
21536 make big changes. This should help ameliorate past and future
21537 issues where routers think they have uploaded valid descriptors,
21538 but the authorities don't think so. Fix for ticket 2479.
21539 - Make the code that clients use to detect an address change be
21540 IPv6-aware, so that it won't fill clients' logs with error
21541 messages when trying to get the IPv4 address of an IPv6
21542 connection. Implements ticket 5537.
21544 o Removed features:
21545 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
21546 authorities needed to use it for a while to keep the network working
21547 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
21548 that was six months ago. As of now, it should no longer be needed
21552 Changes in version 0.2.3.14-alpha - 2012-04-23
21553 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
21554 candidate. It also dramatically speeds up AES: fast relays should
21555 consider switching to the newer OpenSSL library.
21557 o Directory authority changes:
21558 - Change IP address for ides (v3 directory authority), and rename
21562 - Avoid logging uninitialized data when unable to decode a hidden
21563 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
21564 - Avoid a client-side assertion failure when receiving an INTRODUCE2
21565 cell on a general purpose circuit. Fixes bug 5644; bugfix on
21567 - If authorities are unable to get a v2 consensus document from other
21568 directory authorities, they no longer fall back to fetching
21569 them from regular directory caches. Fixes bug 5635; bugfix on
21570 0.2.2.26-beta, where routers stopped downloading v2 consensus
21571 documents entirely.
21572 - When we start a Tor client with a normal consensus already cached,
21573 be willing to download a microdescriptor consensus. Fixes bug 4011;
21574 fix on 0.2.3.1-alpha.
21576 o Major features (performance):
21577 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
21578 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
21579 vectorized AES implementations as appropriate. These can be much,
21580 much faster than other AES implementations.
21582 o Minor bugfixes (0.2.2.x and earlier):
21583 - Don't launch more than 10 service-side introduction-point circuits
21584 for a hidden service in five minutes. Previously, we would consider
21585 launching more introduction-point circuits if at least one second
21586 had passed without any introduction-point circuits failing. Fixes
21587 bug 4607; bugfix on 0.0.7pre1.
21588 - Change the BridgePassword feature (part of the "bridge community"
21589 design, which is not yet implemented) to use a time-independent
21590 comparison. The old behavior might have allowed an adversary
21591 to use timing to guess the BridgePassword value. Fixes bug 5543;
21592 bugfix on 0.2.0.14-alpha.
21593 - Enforce correct return behavior of tor_vsscanf() when the '%%'
21594 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
21595 - When sending an HTTP/1.1 proxy request, include a Host header.
21596 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
21597 - Don't log that we have "decided to publish new relay descriptor"
21598 unless we are actually publishing a descriptor. Fixes bug 3942;
21599 bugfix on 0.2.2.28-beta.
21601 o Minor bugfixes (0.2.3.x):
21602 - Fix a bug where a bridge authority crashes (on a failed assert)
21603 if it has seen no directory requests when it's time to write
21604 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
21605 - Fix bug stomping on ORPort option NoListen and ignoring option
21606 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
21607 - In the testsuite, provide a large enough buffer in the tor_sscanf
21608 unit test. Otherwise we'd overrun that buffer and crash during
21609 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
21611 - Make sure we create the keys directory if it doesn't exist and we're
21612 about to store the dynamic Diffie-Hellman parameters. Fixes bug
21613 5572; bugfix on 0.2.3.13-alpha.
21614 - Fix a small memory leak when trying to decode incorrect base16
21615 authenticator during SAFECOOKIE authentication. Found by
21616 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
21619 - Add more information to a log statement that might help track down
21620 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
21621 non-IP address" messages (or any Bug messages, for that matter!),
21622 please let us know about it.
21623 - Relays now understand an IPv6 address when they get one from a
21624 directory server. Resolves ticket 4875.
21625 - Resolve IPv6 addresses in bridge and entry statistics to country
21626 code "??" which means we at least count them. Resolves ticket 5053;
21627 improves on 0.2.3.9-alpha.
21628 - Update to the April 3 2012 Maxmind GeoLite Country database.
21629 - Begin a doc/state-contents.txt file to explain the contents of
21630 the Tor state file. Fixes bug 2987.
21632 o Default torrc changes:
21633 - Stop listing "socksport 9050" in torrc.sample. We open a socks
21634 port on 9050 by default anyway, so this should not change anything
21636 - Stop mentioning the deprecated *ListenAddress options in
21637 torrc.sample. Fixes bug 5438.
21638 - Document unit of bandwidth related options in sample torrc.
21641 o Removed features:
21642 - The "torify" script no longer supports the "tsocks" socksifier
21643 tool, since tsocks doesn't support DNS and UDP right for Tor.
21644 Everyone should be using torsocks instead. Fixes bugs 3530 and
21645 5180. Based on a patch by "ugh".
21647 o Code refactoring:
21648 - Change the symmetric cipher interface so that creating and
21649 initializing a stream cipher are no longer separate functions.
21650 - Remove all internal support for unpadded RSA. We never used it, and
21651 it would be a bad idea to start.
21654 Changes in version 0.2.3.13-alpha - 2012-03-26
21655 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
21656 in managed pluggable transports, as well as providing other cleanups
21657 that get us closer to a release candidate.
21659 o Directory authority changes:
21660 - Change IP address for maatuska (v3 directory authority).
21663 - Provide controllers with a safer way to implement the cookie
21664 authentication mechanism. With the old method, if another locally
21665 running program could convince a controller that it was the Tor
21666 process, then that program could trick the controller into telling
21667 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
21668 authentication method uses a challenge-response approach to prevent
21669 this attack. Fixes bug 5185, implements proposal 193.
21670 - Never use a bridge or a controller-supplied node as an exit, even
21671 if its exit policy allows it. Found by wanoskarnet. Fixes bug
21672 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
21673 and 0.2.0.3-alpha (for bridge-purpose descriptors).
21674 - Only build circuits if we have a sufficient threshold of the total
21675 descriptors that are marked in the consensus with the "Exit"
21676 flag. This mitigates an attack proposed by wanoskarnet, in which
21677 all of a client's bridges collude to restrict the exit nodes that
21678 the client knows about. Fixes bug 5343.
21680 o Major bugfixes (on Tor 0.2.3.x):
21681 - Avoid an assert when managed proxies like obfsproxy are configured,
21682 and we receive HUP signals or setconf attempts too rapidly. This
21683 situation happens most commonly when Vidalia tries to attach to
21684 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
21685 bugfix on 0.2.3.6-alpha.
21686 - Fix a relay-side pluggable transports bug where managed proxies were
21687 unreachable from the Internet, because Tor asked them to bind on
21688 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
21689 - Stop discarding command-line arguments when TestingTorNetwork
21690 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
21691 0.2.3.9-alpha, where task 4552 added support for two layers of
21693 - Resume allowing the unit tests to run in gdb. This was accidentally
21694 made impossible when the DisableDebuggerAttachment option was
21695 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
21696 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
21697 0.2.3.11-alpha. Reported by Anthony G. Basile.
21699 o Minor bugfixes (on 0.2.2.x and earlier):
21700 - Ensure we don't cannibalize circuits that are longer than three hops
21701 already, so we don't end up making circuits with 5 or more
21702 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
21703 0.1.0.1-rc which introduced cannibalization.
21704 - Detect and reject certain misformed escape sequences in
21705 configuration values. Previously, these values would cause us
21706 to crash if received in a torrc file or over an authenticated
21707 control port. Bug found by Esteban Manchado Velázquez, and
21708 independently by Robert Connolly from Matta Consulting who further
21709 noted that it allows a post-authentication heap overflow. Patch
21710 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
21711 bugfix on 0.2.0.16-alpha.
21712 - Fix a compile warning when using the --enable-openbsd-malloc
21713 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
21714 - Directory caches no longer refuse to clean out descriptors because
21715 of missing v2 networkstatus documents, unless they're configured
21716 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
21717 0.2.2.26-beta. Patch by Daniel Bryg.
21718 - Update to the latest version of the tinytest unit testing framework.
21719 This includes a couple of bugfixes that can be relevant for
21720 running forked unit tests on Windows, and removes all reserved
21723 o Minor bugfixes (on 0.2.3.x):
21724 - On a failed pipe() call, don't leak file descriptors. Fixes bug
21725 4296; bugfix on 0.2.3.1-alpha.
21726 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
21727 until after we have received a CERTS cell. Fixes bug 4361; bugfix
21728 on 0.2.3.6-alpha. Patch by "frosty".
21729 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
21730 option, so that the IP stack doesn't decide to use it for IPv4
21731 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
21732 - Ensure that variables set in Tor's environment cannot override
21733 environment variables that Tor passes to a managed
21734 pluggable-transport proxy. Previously, Tor would pass every
21735 variable in its environment to managed proxies along with the new
21736 ones, in such a way that on many operating systems, the inherited
21737 environment variables would override those which Tor tried to
21738 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
21739 bugfix on 0.2.3.9-alpha for Windows.
21742 - A wide variety of new unit tests by Esteban Manchado Velázquez.
21743 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
21744 - Update to the March 6 2012 Maxmind GeoLite Country database.
21747 Changes in version 0.2.3.12-alpha - 2012-02-13
21748 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
21749 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
21750 when Tor is configured to use a pluggable transport like obfsproxy.
21753 - Fix builds when the path to sed, openssl, or sha1sum contains
21754 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
21756 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
21757 connections. This change should allow busy exit relays to stop
21758 running out of available sockets as quickly. Fixes bug 4950;
21759 bugfix on 0.2.2.26-beta.
21760 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
21761 would ask the bridge for microdescriptors, which are only supported
21762 in 0.2.3.x, and then fail to bootstrap when it didn't get the
21763 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
21764 - Properly set up obfsproxy's environment when in managed mode. The
21765 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
21766 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
21767 5076 and 5082; bugfix on 0.2.3.6-alpha.
21770 - Use the dead_strip option when building Tor on OS X. This reduces
21771 binary size by almost 19% when linking openssl and libevent
21772 statically, which we do for Tor Browser Bundle.
21773 - Fix broken URLs in the sample torrc file, and tell readers about
21774 the OutboundBindAddress, ExitPolicyRejectPrivate, and
21775 PublishServerDescriptor options. Addresses bug 4652.
21776 - Update to the February 7 2012 Maxmind GeoLite Country database.
21779 - Downgrade the "We're missing a certificate" message from notice
21780 to info: people kept mistaking it for a real problem, whereas it
21781 is seldom the problem even when we are failing to bootstrap. Fixes
21782 bug 5067; bugfix on 0.2.0.10-alpha.
21783 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
21784 managed pluggable transport server proxy's environment.
21785 Previously, we would put it there, even though Tor doesn't
21786 implement an 'extended server port' yet, and even though Tor
21787 almost certainly isn't listening at that address. For now, we set
21788 it to an empty string to avoid crashing older obfsproxies. Bugfix
21790 - Log the heartbeat message every HeartbeatPeriod seconds, not every
21791 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
21792 0.2.3.1-alpha. Bug reported by Scott Bennett.
21793 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
21794 bugfix on 0.2.3.11-alpha.
21795 - Update "ClientOnly" man page entry to explain that there isn't
21796 really any point to messing with it. Resolves ticket 5005.
21797 - Use the correct CVE number for CVE-2011-4576 in our comments and
21798 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
21801 o Code simplifications and refactoring:
21802 - Use the _WIN32 macro throughout our code to detect Windows.
21803 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
21807 Changes in version 0.2.3.11-alpha - 2012-01-22
21808 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
21809 the last step of the plan to limit maximum circuit length, includes
21810 a wide variety of hidden service performance and correctness fixes,
21811 works around an OpenSSL security flaw if your distro is too stubborn
21812 to upgrade, and fixes a bunch of smaller issues.
21815 - Now that Tor 0.2.0.x is completely deprecated, enable the final
21816 part of "Proposal 110: Avoiding infinite length circuits" by
21817 refusing all circuit-extend requests that do not use a relay_early
21818 cell. This change helps Tor resist a class of denial-of-service
21819 attacks by limiting the maximum circuit length.
21820 - Adjust the number of introduction points that a hidden service
21821 will try to maintain based on how long its introduction points
21822 remain in use and how many introductions they handle. Fixes
21824 - Try to use system facilities for enumerating local interface
21825 addresses, before falling back to our old approach (which was
21826 binding a UDP socket, and calling getsockname() on it). That
21827 approach was scaring OS X users whose draconian firewall
21828 software warned about binding to UDP sockets, regardless of
21829 whether packets were sent. Now we try to use getifaddrs(),
21830 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
21831 system supports. Resolves ticket 1827.
21833 o Major security workaround:
21834 - When building or running with any version of OpenSSL earlier
21835 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
21836 versions have a bug (CVE-2011-4576) in which their block cipher
21837 padding includes uninitialized data, potentially leaking sensitive
21838 information to any peer with whom they make a SSLv3 connection. Tor
21839 does not use SSL v3 by default, but a hostile client or server
21840 could force an SSLv3 connection in order to gain information that
21841 they shouldn't have been able to get. The best solution here is to
21842 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
21843 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
21844 to make sure that the bug can't happen.
21847 - Fix the SOCKET_OK test that we use to tell when socket
21848 creation fails so that it works on Win64. Fixes part of bug 4533;
21849 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
21850 - Correct our replacements for the timeradd() and timersub() functions
21851 on platforms that lack them (for example, Windows). The timersub()
21852 function is used when expiring circuits, while timeradd() is
21853 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
21854 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
21855 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
21856 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
21857 bug at runtime, not compile time, because some distributions hack
21858 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
21859 on 0.2.3.9-alpha. Found by Pascal.
21861 o Minor features (controller):
21862 - Use absolute path names when reporting the torrc filename in the
21863 control protocol, so a controller can more easily find the torrc
21864 file. Resolves bug 1101.
21865 - Extend the control protocol to report flags that control a circuit's
21866 path selection in CIRC events and in replies to 'GETINFO
21867 circuit-status'. Implements part of ticket 2411.
21868 - Extend the control protocol to report the hidden service address
21869 and current state of a hidden-service-related circuit in CIRC
21870 events and in replies to 'GETINFO circuit-status'. Implements part
21872 - When reporting the path to the cookie file to the controller,
21873 give an absolute path. Resolves ticket 4881.
21874 - Allow controllers to request an event notification whenever a
21875 circuit is cannibalized or its purpose is changed. Implements
21876 part of ticket 3457.
21877 - Include the creation time of a circuit in CIRC and CIRC2
21878 control-port events and the list produced by the 'GETINFO
21879 circuit-status' control-port command.
21881 o Minor features (directory authorities):
21882 - Directory authorities now reject versions of Tor older than
21883 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
21884 inclusive. These versions accounted for only a small fraction of
21885 the Tor network, and have numerous known security issues. Resolves
21887 - Authority operators can now vote for all relays in a given
21888 set of countries to be BadDir/BadExit/Invalid/Rejected.
21889 - Provide two consensus parameters (FastFlagMinThreshold and
21890 FastFlagMaxThreshold) to control the range of allowable bandwidths
21891 for the Fast directory flag. These allow authorities to run
21892 experiments on appropriate requirements for being a "Fast" node.
21893 The AuthDirFastGuarantee config value still applies. Implements
21895 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
21896 directory authority option (introduced in Tor 0.2.2.34).
21898 o Minor features (other):
21899 - Don't disable the DirPort when we cannot exceed our AccountingMax
21900 limit during this interval because the effective bandwidthrate is
21901 low enough. This is useful in a situation where AccountMax is only
21902 used as an additional safeguard or to provide statistics.
21903 - Prepend an informative header to generated dynamic_dh_params files.
21904 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
21905 EntryNodes will have no effect. Resolves issue 2571.
21906 - Log more useful messages when we fail to disable debugger
21908 - Log which authority we're missing votes from when we go to fetch
21909 them from the other auths.
21910 - Log (at debug level) whenever a circuit's purpose is changed.
21911 - Add missing documentation for the MaxClientCircuitsPending,
21912 UseMicrodescriptors, UserspaceIOCPBuffers, and
21913 _UseFilteringSSLBufferevents options, all introduced during
21914 the 0.2.3.x series.
21915 - Update to the January 3 2012 Maxmind GeoLite Country database.
21917 o Minor bugfixes (hidden services):
21918 - Don't close hidden service client circuits which have almost
21919 finished connecting to their destination when they reach
21920 the normal circuit-build timeout. Previously, we would close
21921 introduction circuits which are waiting for an acknowledgement
21922 from the introduction point, and rendezvous circuits which have
21923 been specified in an INTRODUCE1 cell sent to a hidden service,
21924 after the normal CBT. Now, we mark them as 'timed out', and launch
21925 another rendezvous attempt in parallel. This behavior change can
21926 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
21927 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
21928 - Don't close hidden-service-side rendezvous circuits when they
21929 reach the normal circuit-build timeout. This behavior change can
21930 be disabled using the new
21931 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
21932 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
21933 - Make sure we never mark the wrong rendezvous circuit as having
21934 had its introduction cell acknowledged by the introduction-point
21935 relay. Previously, when we received an INTRODUCE_ACK cell on a
21936 client-side hidden-service introduction circuit, we might have
21937 marked a rendezvous circuit other than the one we specified in
21938 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
21939 a warning message and interfered with the hidden service
21940 connection-establishment process. Fixes bug 4759; bugfix on
21941 0.2.3.3-alpha, when we added the stream-isolation feature which
21942 might cause Tor to open multiple rendezvous circuits for the same
21944 - Don't trigger an assertion failure when we mark a new client-side
21945 hidden-service introduction circuit for close during the process
21946 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
21949 o Minor bugfixes (log messages):
21950 - Correctly spell "connect" in a log message on failure to create a
21951 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
21953 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
21954 Fixes bug 4856; bugfix on Tor 0.0.6.
21955 - Fix the log message describing how we work around discovering
21956 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
21957 4837; bugfix on 0.2.2.9-alpha.
21958 - When logging about a disallowed .exit name, do not also call it
21959 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
21961 o Minor bugfixes (build fixes):
21962 - During configure, detect when we're building with clang version
21963 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
21964 CFLAGS. clang doesn't support them yet.
21965 - During configure, search for library containing cos function as
21966 libm lives in libcore on some platforms (BeOS/Haiku). Linking
21967 against libm was hard-coded before. Fixes the first part of bug
21968 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
21970 - Detect attempts to build Tor on (as yet hypothetical) versions
21971 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
21972 fix for bug 4533. Bugfix on 0.2.2.28-beta.
21973 - Preprocessor directives should not be put inside the arguments
21974 of a macro. This would break compilation with GCC releases prior
21975 to version 3.3. We would never recommend such an old GCC version,
21976 but it is apparently required for binary compatibility on some
21977 platforms (namely, certain builds of Haiku). Fixes the other part
21978 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
21981 o Minor bugfixes (other):
21982 - Older Linux kernels erroneously respond to strange nmap behavior
21983 by having accept() return successfully with a zero-length
21984 socket. When this happens, just close the connection. Previously,
21985 we would try harder to learn the remote address: but there was
21986 no such remote address to learn, and our method for trying to
21987 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
21988 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
21989 - Fix null-pointer access that could occur if TLS allocation failed.
21990 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
21991 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
21992 accidentally been reverted.
21993 - Fix our implementation of crypto_random_hostname() so it can't
21994 overflow on ridiculously large inputs. (No Tor version has ever
21995 provided this kind of bad inputs, but let's be correct in depth.)
21996 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
21997 - Find more places in the code that should have been testing for
21998 invalid sockets using the SOCKET_OK macro. Required for a fix
21999 for bug 4533. Bugfix on 0.2.2.28-beta.
22000 - Fix an assertion failure when, while running with bufferevents, a
22001 connection finishes connecting after it is marked for close, but
22002 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
22003 - test_util_spawn_background_ok() hardcoded the expected value
22004 for ENOENT to 2. This isn't portable as error numbers are
22005 platform specific, and particularly the hurd has ENOENT at
22006 0x40000002. Construct expected string at runtime, using the correct
22007 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
22008 - Reject attempts to disable DisableDebuggerAttachment while Tor is
22009 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
22010 - Use an appropriate-width type for sockets in tor-fw-helper on
22011 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
22014 - When sending or relaying a RELAY_EARLY cell, we used to convert
22015 it to a RELAY cell if the connection was using the v1 link
22016 protocol. This was a workaround for older versions of Tor, which
22017 didn't handle RELAY_EARLY cells properly. Now that all supported
22018 versions can handle RELAY_EARLY cells, and now that we're enforcing
22019 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
22020 remove this workaround. Addresses bug 4786.
22022 o Code simplifications and refactoring:
22023 - Use OpenSSL's built-in SSL_state_string_long() instead of our
22024 own homebrewed ssl_state_to_string() replacement. Patch from
22025 Emile Snyder. Fixes bug 4653.
22026 - Use macros to indicate OpenSSL versions, so we don't need to worry
22027 about accidental hexadecimal bit shifts.
22028 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
22030 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
22031 - Use the smartlist_add_asprintf() alias more consistently.
22032 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
22033 invalid value, rather than just -1.
22034 - Rename a handful of old identifiers, mostly related to crypto
22035 structures and crypto functions. By convention, our "create an
22036 object" functions are called "type_new()", our "free an object"
22037 functions are called "type_free()", and our types indicate that
22038 they are types only with a final "_t". But a handful of older
22039 types and functions broke these rules, with function names like
22040 "type_create" or "subsystem_op_type", or with type names like
22044 Changes in version 0.2.3.10-alpha - 2011-12-16
22045 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
22046 Tor's buffers code. Absolutely everybody should upgrade.
22048 The bug relied on an incorrect calculation when making data continuous
22049 in one of our IO buffers, if the first chunk of the buffer was
22050 misaligned by just the wrong amount. The miscalculation would allow an
22051 attacker to overflow a piece of heap-allocated memory. To mount this
22052 attack, the attacker would need to either open a SOCKS connection to
22053 Tor's SocksPort (usually restricted to localhost), or target a Tor
22054 instance configured to make its connections through a SOCKS proxy
22055 (which Tor does not do by default).
22057 Good security practice requires that all heap-overflow bugs should be
22058 presumed to be exploitable until proven otherwise, so we are treating
22059 this as a potential code execution attack. Please upgrade immediately!
22060 This bug does not affect bufferevents-based builds of Tor. Special
22061 thanks to "Vektor" for reporting this issue to us!
22063 This release also contains a few minor bugfixes for issues discovered
22067 - Fix a heap overflow bug that could occur when trying to pull
22068 data into the first chunk of a buffer, when that chunk had
22069 already had some data drained from it. Fixes CVE-2011-2778;
22070 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
22073 - If we can't attach streams to a rendezvous circuit when we
22074 finish connecting to a hidden service, clear the rendezvous
22075 circuit's stream-isolation state and try to attach streams
22076 again. Previously, we cleared rendezvous circuits' isolation
22077 state either too early (if they were freshly built) or not at all
22078 (if they had been built earlier and were cannibalized). Bugfix on
22079 0.2.3.3-alpha; fixes bug 4655.
22080 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
22081 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
22082 - Fix an assertion failure when a relay with accounting enabled
22083 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
22086 - Update to the December 6 2011 Maxmind GeoLite Country database.
22089 Changes in version 0.2.2.35 - 2011-12-16
22090 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
22091 buffers code. Absolutely everybody should upgrade.
22093 The bug relied on an incorrect calculation when making data continuous
22094 in one of our IO buffers, if the first chunk of the buffer was
22095 misaligned by just the wrong amount. The miscalculation would allow an
22096 attacker to overflow a piece of heap-allocated memory. To mount this
22097 attack, the attacker would need to either open a SOCKS connection to
22098 Tor's SocksPort (usually restricted to localhost), or target a Tor
22099 instance configured to make its connections through a SOCKS proxy
22100 (which Tor does not do by default).
22102 Good security practice requires that all heap-overflow bugs should be
22103 presumed to be exploitable until proven otherwise, so we are treating
22104 this as a potential code execution attack. Please upgrade immediately!
22105 This bug does not affect bufferevents-based builds of Tor. Special
22106 thanks to "Vektor" for reporting this issue to us!
22108 Tor 0.2.2.35 also fixes several bugs in previous versions, including
22109 crash bugs for unusual configurations, and a long-term bug that
22110 would prevent Tor from starting on Windows machines with draconian
22113 With this release, we remind everyone that 0.2.0.x has reached its
22114 formal end-of-life. Those Tor versions have many known flaws, and
22115 nobody should be using them. You should upgrade -- ideally to the
22116 0.2.2.x series. If you're using a Linux or BSD and its packages are
22117 obsolete, stop using those packages and upgrade anyway.
22119 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
22120 longer receive support after some time in early 2012.
22123 - Fix a heap overflow bug that could occur when trying to pull
22124 data into the first chunk of a buffer, when that chunk had
22125 already had some data drained from it. Fixes CVE-2011-2778;
22126 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
22127 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
22128 that it doesn't attempt to allocate a socketpair. This could cause
22129 some problems on Windows systems with overzealous firewalls. Fix for
22130 bug 4457; workaround for Libevent versions 2.0.1-alpha through
22132 - If we mark an OR connection for close based on a cell we process,
22133 don't process any further cells on it. We already avoid further
22134 reads on marked-for-close connections, but now we also discard the
22135 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
22136 which was the first version where we might mark a connection for
22137 close based on processing a cell on it.
22138 - Correctly sanity-check that we don't underflow on a memory
22139 allocation (and then assert) for hidden service introduction
22140 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
22141 bugfix on 0.2.1.5-alpha.
22142 - Fix a memory leak when we check whether a hidden service
22143 descriptor has any usable introduction points left. Fixes bug
22144 4424. Bugfix on 0.2.2.25-alpha.
22145 - Don't crash when we're running as a relay and don't have a GeoIP
22146 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
22147 we've had in the 0.2.3.x branch already.
22148 - When running as a client, do not print a misleading (and plain
22149 wrong) log message that we're collecting "directory request"
22150 statistics: clients don't collect statistics. Also don't create a
22151 useless (because empty) stats file in the stats/ directory. Fixes
22152 bug 4353; bugfix on 0.2.2.34.
22155 - Detect failure to initialize Libevent. This fix provides better
22156 detection for future instances of bug 4457.
22157 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
22158 function. This was eating up hideously large amounts of time on some
22159 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
22160 - Resolve an integer overflow bug in smartlist_ensure_capacity().
22161 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
22163 - Don't warn about unused log_mutex in log.c when building with
22164 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
22165 0.1.0.6-rc which introduced --disable-threads.
22166 - When configuring, starting, or stopping an NT service, stop
22167 immediately after the service configuration attempt has succeeded
22168 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
22169 - When sending a NETINFO cell, include the original address
22170 received for the other side, not its canonical address. Found
22171 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
22172 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
22173 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
22174 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
22175 occurred when a client tried to fetch a descriptor for a bridge
22176 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
22177 - Backport fixes for a pair of compilation warnings on Windows.
22178 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
22179 - If we had ever tried to call tor_addr_to_str on an address of
22180 unknown type, we would have done a strdup on an uninitialized
22181 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
22182 Reported by "troll_un".
22183 - Correctly detect and handle transient lookup failures from
22184 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
22185 Reported by "troll_un".
22186 - Fix null-pointer access that could occur if TLS allocation failed.
22187 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
22188 - Use tor_socket_t type for listener argument to accept(). Fixes bug
22189 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
22192 - Add two new config options for directory authorities:
22193 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
22194 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
22195 that is always sufficient to satisfy the bandwidth requirement for
22196 the Guard flag. Now it will be easier for researchers to simulate
22197 Tor networks with different values. Resolves ticket 4484.
22198 - When Tor ignores a hidden service specified in its configuration,
22199 include the hidden service's directory in the warning message.
22200 Previously, we would only tell the user that some hidden service
22201 was ignored. Bugfix on 0.0.6; fixes bug 4426.
22202 - Update to the December 6 2011 Maxmind GeoLite Country database.
22204 o Packaging changes:
22205 - Make it easier to automate expert package builds on Windows,
22206 by removing an absolute path from makensis.exe command.
22209 Changes in version 0.2.1.32 - 2011-12-16
22210 Tor 0.2.1.32 backports important security and privacy fixes for
22211 oldstable. This release is intended only for package maintainers and
22212 others who cannot use the 0.2.2 stable series. All others should be
22213 using Tor 0.2.2.x or newer.
22215 The Tor 0.2.1.x series will reach formal end-of-life some time in
22216 early 2012; we will stop releasing patches for it then.
22218 o Major bugfixes (also included in 0.2.2.x):
22219 - Correctly sanity-check that we don't underflow on a memory
22220 allocation (and then assert) for hidden service introduction
22221 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
22222 bugfix on 0.2.1.5-alpha.
22223 - Fix a heap overflow bug that could occur when trying to pull
22224 data into the first chunk of a buffer, when that chunk had
22225 already had some data drained from it. Fixes CVE-2011-2778;
22226 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
22229 - Update to the December 6 2011 Maxmind GeoLite Country database.
22232 Changes in version 0.2.3.9-alpha - 2011-12-08
22233 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
22234 a "DisableNetwork" security feature that bundles can use to avoid
22235 touching the network until bridges are configured, moves forward on
22236 the pluggable transport design, fixes a flaw in the hidden service
22237 design that unnecessarily prevented clients with wrong clocks from
22238 reaching hidden services, and fixes a wide variety of other issues.
22241 - Clients can now connect to private bridges over IPv6. Bridges
22242 still need at least one IPv4 address in order to connect to
22243 other relays. Note that we don't yet handle the case where the
22244 user has two bridge lines for the same bridge (one IPv4, one
22245 IPv6). Implements parts of proposal 186.
22246 - New "DisableNetwork" config option to prevent Tor from launching any
22247 connections or accepting any connections except on a control port.
22248 Bundles and controllers can set this option before letting Tor talk
22249 to the rest of the network, for example to prevent any connections
22250 to a non-bridge address. Packages like Orbot can also use this
22251 option to instruct Tor to save power when the network is off.
22252 - Clients and bridges can now be configured to use a separate
22253 "transport" proxy. This approach makes the censorship arms race
22254 easier by allowing bridges to use protocol obfuscation plugins. It
22255 implements the "managed proxy" part of proposal 180 (ticket 3472).
22256 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
22257 implementation. It makes AES_CTR about 7% faster than our old one
22258 (which was about 10% faster than the one OpenSSL used to provide).
22259 Resolves ticket 4526.
22260 - Add a "tor2web mode" for clients that want to connect to hidden
22261 services non-anonymously (and possibly more quickly). As a safety
22262 measure to try to keep users from turning this on without knowing
22263 what they are doing, tor2web mode must be explicitly enabled at
22264 compile time, and a copy of Tor compiled to run in tor2web mode
22265 cannot be used as a normal Tor client. Implements feature 2553.
22266 - Add experimental support for running on Windows with IOCP and no
22267 kernel-space socket buffers. This feature is controlled by a new
22268 "UserspaceIOCPBuffers" config option (off by default), which has
22269 no effect unless Tor has been built with support for bufferevents,
22270 is running on Windows, and has enabled IOCP. This may, in the long
22271 run, help solve or mitigate bug 98.
22272 - Use a more secure consensus parameter voting algorithm. Now at
22273 least three directory authorities or a majority of them must
22274 vote on a given parameter before it will be included in the
22275 consensus. Implements proposal 178.
22278 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
22279 They used to check that the timestamp was within 30 minutes
22280 of their system clock, so they could cap the size of their
22281 replay-detection cache, but that approach unnecessarily refused
22282 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
22283 the v3 intro-point protocol (the first one which sent a timestamp
22284 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
22285 - Only use the EVP interface when AES acceleration is enabled,
22286 to avoid a 5-7% performance regression. Resolves issue 4525;
22287 bugfix on 0.2.3.8-alpha.
22289 o Privacy/anonymity features (bridge detection):
22290 - Make bridge SSL certificates a bit more stealthy by using random
22291 serial numbers, in the same fashion as OpenSSL when generating
22292 self-signed certificates. Implements ticket 4584.
22293 - Introduce a new config option "DynamicDHGroups", enabled by
22294 default, which provides each bridge with a unique prime DH modulus
22295 to be used during SSL handshakes. This option attempts to help
22296 against censors who might use the Apache DH modulus as a static
22297 identifier for bridges. Addresses ticket 4548.
22299 o Minor features (new/different config options):
22300 - New configuration option "DisableDebuggerAttachment" (on by default)
22301 to prevent basic debugging attachment attempts by other processes.
22302 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
22303 - Allow MapAddress directives to specify matches against super-domains,
22304 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
22305 Implements issue 933.
22306 - Slightly change behavior of "list" options (that is, config
22307 options that can appear more than once) when they appear both in
22308 torrc and on the command line. Previously, the command-line options
22309 would be appended to the ones from torrc. Now, the command-line
22310 options override the torrc options entirely. This new behavior
22311 allows the user to override list options (like exit policies and
22312 ports to listen on) from the command line, rather than simply
22313 appending to the list.
22314 - You can get the old (appending) command-line behavior for "list"
22315 options by prefixing the option name with a "+".
22316 - You can remove all the values for a "list" option from the command
22317 line without adding any new ones by prefixing the option name
22319 - Add experimental support for a "defaults" torrc file to be parsed
22320 before the regular torrc. Torrc options override the defaults file's
22321 options in the same way that the command line overrides the torrc.
22322 The SAVECONF controller command saves only those options which
22323 differ between the current configuration and the defaults file. HUP
22324 reloads both files. (Note: This is an experimental feature; its
22325 behavior will probably be refined in future 0.2.3.x-alpha versions
22326 to better meet packagers' needs.) Implements task 4552.
22329 - Try to make the introductory warning message that Tor prints on
22330 startup more useful for actually finding help and information.
22331 Resolves ticket 2474.
22332 - Running "make version" now displays the version of Tor that
22333 we're about to build. Idea from katmagic; resolves issue 4400.
22334 - Expire old or over-used hidden service introduction points.
22335 Required by fix for bug 3460.
22336 - Move the replay-detection cache for the RSA-encrypted parts of
22337 INTRODUCE2 cells to the introduction point data structures.
22338 Previously, we would use one replay-detection cache per hidden
22339 service. Required by fix for bug 3460.
22340 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
22341 public key replay-detection cache from 60 minutes to 5 minutes. This
22342 replay-detection cache is now used only to detect multiple
22343 INTRODUCE2 cells specifying the same rendezvous point, so we can
22344 avoid launching multiple simultaneous attempts to connect to it.
22346 o Minor bugfixes (on Tor 0.2.2.x and earlier):
22347 - Resolve an integer overflow bug in smartlist_ensure_capacity().
22348 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
22350 - Fix a minor formatting issue in one of tor-gencert's error messages.
22352 - Prevent a false positive from the check-spaces script, by disabling
22353 the "whitespace between function name and (" check for functions
22355 - Fix a log message suggesting that people contact a non-existent
22356 email address. Fixes bug 3448.
22357 - Fix null-pointer access that could occur if TLS allocation failed.
22358 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
22359 - Report a real bootstrap problem to the controller on router
22360 identity mismatch. Previously we just said "foo", which probably
22361 made a lot of sense at the time. Fixes bug 4169; bugfix on
22363 - If we had ever tried to call tor_addr_to_str() on an address of
22364 unknown type, we would have done a strdup() on an uninitialized
22365 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
22366 Reported by "troll_un".
22367 - Correctly detect and handle transient lookup failures from
22368 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
22369 Reported by "troll_un".
22370 - Use tor_socket_t type for listener argument to accept(). Fixes bug
22371 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
22372 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
22373 bug 4532; found by "troll_un".
22375 o Minor bugfixes (on Tor 0.2.3.x):
22376 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
22378 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
22379 circuit for use as a hidden service client's rendezvous point.
22380 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
22381 with help from wanoskarnet.
22382 - Restore behavior of overriding SocksPort, ORPort, and similar
22383 options from the command line. Bugfix on 0.2.3.3-alpha.
22386 - Properly handle the case where the build-tree is not the same
22387 as the source tree when generating src/common/common_sha1.i,
22388 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
22389 bugfix on 0.2.0.1-alpha.
22391 o Code simplifications, cleanups, and refactorings:
22392 - Remove the pure attribute from all functions that used it
22393 previously. In many cases we assigned it incorrectly, because the
22394 functions might assert or call impure functions, and we don't have
22395 evidence that keeping the pure attribute is worthwhile. Implements
22396 changes suggested in ticket 4421.
22397 - Remove some dead code spotted by coverity. Fixes cid 432.
22398 Bugfix on 0.2.3.1-alpha, closes bug 4637.
22401 Changes in version 0.2.3.8-alpha - 2011-11-22
22402 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
22403 socketpair-related bug that has been bothering Windows users. It adds
22404 support to serve microdescriptors to controllers, so Vidalia's network
22405 map can resume listing relays (once Vidalia implements its side),
22406 and adds better support for hardware AES acceleration. Finally, it
22407 starts the process of adjusting the bandwidth cutoff for getting the
22408 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
22409 that tiny relays harm performance more than they help network capacity.
22412 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
22413 that it doesn't attempt to allocate a socketpair. This could cause
22414 some problems on Windows systems with overzealous firewalls. Fix for
22415 bug 4457; workaround for Libevent versions 2.0.1-alpha through
22417 - Correctly sanity-check that we don't underflow on a memory
22418 allocation (and then assert) for hidden service introduction
22419 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
22420 bugfix on 0.2.1.5-alpha.
22421 - Remove the artificially low cutoff of 20KB to guarantee the Fast
22422 flag. In the past few years the average relay speed has picked
22423 up, and while the "top 7/8 of the network get the Fast flag" and
22424 "all relays with 20KB or more of capacity get the Fast flag" rules
22425 used to have the same result, now the top 7/8 of the network has
22426 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
22427 - Fix a rare assertion failure when checking whether a v0 hidden
22428 service descriptor has any usable introduction points left, and
22429 we don't have enough information to build a circuit to the first
22430 intro point named in the descriptor. The HS client code in
22431 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
22432 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
22433 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
22434 - Make bridge authorities not crash when they are asked for their own
22435 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
22436 - When running as a client, do not print a misleading (and plain
22437 wrong) log message that we're collecting "directory request"
22438 statistics: clients don't collect statistics. Also don't create a
22439 useless (because empty) stats file in the stats/ directory. Fixes
22440 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
22443 - Allow Tor controllers like Vidalia to obtain the microdescriptor
22444 for a relay by identity digest or nickname. Previously,
22445 microdescriptors were only available by their own digests, so a
22446 controller would have to ask for and parse the whole microdescriptor
22447 consensus in order to look up a single relay's microdesc. Fixes
22448 bug 3832; bugfix on 0.2.3.1-alpha.
22449 - Use OpenSSL's EVP interface for AES encryption, so that all AES
22450 operations can use hardware acceleration (if present). Resolves
22453 o Minor bugfixes (on 0.2.2.x and earlier):
22454 - Detect failure to initialize Libevent. This fix provides better
22455 detection for future instances of bug 4457.
22456 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
22457 function. This was eating up hideously large amounts of time on some
22458 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
22459 - Don't warn about unused log_mutex in log.c when building with
22460 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
22461 0.1.0.6-rc which introduced --disable-threads.
22462 - Allow manual 'authenticate' commands to the controller interface
22463 from netcat (nc) as well as telnet. We were rejecting them because
22464 they didn't come with the expected whitespace at the end of the
22465 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
22466 - Fix some (not actually triggerable) buffer size checks in usage of
22467 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
22469 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
22470 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
22471 - When configuring, starting, or stopping an NT service, stop
22472 immediately after the service configuration attempt has succeeded
22473 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
22474 - When sending a NETINFO cell, include the original address
22475 received for the other side, not its canonical address. Found
22476 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
22477 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
22478 can pick them up when the tests aren't disabled. Bugfix on
22479 0.2.2.4-alpha which introduced tinytest.
22480 - Fix a memory leak when we check whether a hidden service
22481 descriptor has any usable introduction points left. Fixes bug
22482 4424. Bugfix on 0.2.2.25-alpha.
22483 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
22484 occurred when a client tried to fetch a descriptor for a bridge
22485 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
22487 o Minor bugfixes (on 0.2.3.x):
22488 - Make util unit tests build correctly with MSVC. Bugfix on
22489 0.2.3.3-alpha. Patch by Gisle Vanem.
22490 - Successfully detect AUTH_CHALLENGE cells with no recognized
22491 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
22492 Found by frosty_un.
22493 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
22494 it should still send a NETINFO cell to allow the connection to
22495 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
22497 - Log less loudly when we get an invalid authentication certificate
22498 from a source other than a directory authority: it's not unusual
22499 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
22501 - Tolerate servers with more clock skew in their authentication
22502 certificates than previously. Fixes bug 4371; bugfix on
22504 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
22505 on 0.2.3.4-alpha and 0.2.3.6-alpha.
22508 - Add two new config options for directory authorities:
22509 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
22510 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
22511 that is always sufficient to satisfy the bandwidth requirement for
22512 the Guard flag. Now it will be easier for researchers to simulate
22513 Tor networks with different values. Resolves ticket 4484.
22514 - When Tor ignores a hidden service specified in its configuration,
22515 include the hidden service's directory in the warning message.
22516 Previously, we would only tell the user that some hidden service
22517 was ignored. Bugfix on 0.0.6; fixes bug 4426.
22518 - When we fail to initialize Libevent, retry with IOCP disabled so we
22519 don't need to turn on multi-threading support in Libevent, which in
22520 turn requires a working socketpair(). This is a workaround for bug
22521 4457, which affects Libevent versions from 2.0.1-alpha through
22523 - Detect when we try to build on a platform that doesn't define
22524 AF_UNSPEC to 0. We don't work there, so refuse to compile.
22525 - Update to the November 1 2011 Maxmind GeoLite Country database.
22527 o Packaging changes:
22528 - Make it easier to automate expert package builds on Windows,
22529 by removing an absolute path from makensis.exe command.
22531 o Code simplifications and refactoring:
22532 - Remove some redundant #include directives throughout the code.
22533 Patch from Andrea Gelmini.
22534 - Unconditionally use OpenSSL's AES implementation instead of our
22535 old built-in one. OpenSSL's AES has been better for a while, and
22536 relatively few servers should still be on any version of OpenSSL
22537 that doesn't have good optimized assembly AES.
22538 - Use the name "CERTS" consistently to refer to the new cell type;
22539 we were calling it CERT in some places and CERTS in others.
22542 - Numerous new unit tests for functions in util.c and address.c by
22544 - The long-disabled benchmark tests are now split into their own
22545 ./src/test/bench binary.
22546 - The benchmark tests can now use more accurate timers than
22547 gettimeofday() when such timers are available.
22550 Changes in version 0.2.3.7-alpha - 2011-10-30
22551 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
22552 the new v3 handshake. It also resolves yet another bridge address
22556 - If we mark an OR connection for close based on a cell we process,
22557 don't process any further cells on it. We already avoid further
22558 reads on marked-for-close connections, but now we also discard the
22559 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
22560 which was the first version where we might mark a connection for
22561 close based on processing a cell on it.
22562 - Fix a double-free bug that would occur when we received an invalid
22563 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
22564 bugfix on 0.2.3.6-alpha.
22565 - Bridges no longer include their address in NETINFO cells on outgoing
22566 OR connections, to allow them to blend in better with clients.
22567 Removes another avenue for enumerating bridges. Reported by
22568 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
22569 cells were introduced.
22572 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
22573 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
22576 Changes in version 0.2.3.6-alpha - 2011-10-26
22577 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
22578 anonymity vulnerability where an attacker can deanonymize Tor
22579 users. Everybody should upgrade.
22581 This release also features support for a new v3 connection handshake
22582 protocol, and fixes to make hidden service connections more robust.
22585 - Implement a new handshake protocol (v3) for authenticating Tors to
22586 each other over TLS. It should be more resistant to fingerprinting
22587 than previous protocols, and should require less TLS hacking for
22588 future Tor implementations. Implements proposal 176.
22589 - Allow variable-length padding cells to disguise the length of
22590 Tor's TLS records. Implements part of proposal 184.
22592 o Privacy/anonymity fixes (clients):
22593 - Clients and bridges no longer send TLS certificate chains on
22594 outgoing OR connections. Previously, each client or bridge would
22595 use the same cert chain for all outgoing OR connections until
22596 its IP address changes, which allowed any relay that the client
22597 or bridge contacted to determine which entry guards it is using.
22598 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
22599 - If a relay receives a CREATE_FAST cell on a TLS connection, it
22600 no longer considers that connection as suitable for satisfying a
22601 circuit EXTEND request. Now relays can protect clients from the
22602 CVE-2011-2768 issue even if the clients haven't upgraded yet.
22603 - Directory authorities no longer assign the Guard flag to relays
22604 that haven't upgraded to the above "refuse EXTEND requests
22605 to client connections" fix. Now directory authorities can
22606 protect clients from the CVE-2011-2768 issue even if neither
22607 the clients nor the relays have upgraded yet. There's a new
22608 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
22609 to let us transition smoothly, else tomorrow there would be no
22612 o Major bugfixes (hidden services):
22613 - Improve hidden service robustness: when an attempt to connect to
22614 a hidden service ends, be willing to refetch its hidden service
22615 descriptors from each of the HSDir relays responsible for them
22616 immediately. Previously, we would not consider refetching the
22617 service's descriptors from each HSDir for 15 minutes after the last
22618 fetch, which was inconvenient if the hidden service was not running
22619 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
22620 - When one of a hidden service's introduction points appears to be
22621 unreachable, stop trying it. Previously, we would keep trying
22622 to build circuits to the introduction point until we lost the
22623 descriptor, usually because the user gave up and restarted Tor.
22624 Partly fixes bug 3825.
22625 - Don't launch a useless circuit after failing to use one of a
22626 hidden service's introduction points. Previously, we would
22627 launch a new introduction circuit, but not set the hidden service
22628 which that circuit was intended to connect to, so it would never
22629 actually be used. A different piece of code would then create a
22630 new introduction circuit correctly. Bug reported by katmagic and
22631 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
22633 o Major bugfixes (other):
22634 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
22635 that they initiated. Relays could distinguish incoming bridge
22636 connections from client connections, creating another avenue for
22637 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
22638 Found by "frosty_un".
22639 - Don't update the AccountingSoftLimitHitAt state file entry whenever
22640 tor gets started. This prevents a wrong average bandwidth
22641 estimate, which would cause relays to always start a new accounting
22642 interval at the earliest possible moment. Fixes bug 2003; bugfix
22643 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
22644 immensely in tracking this bug down.
22645 - Fix a crash bug when changing node restrictions while a DNS lookup
22646 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
22649 o Minor bugfixes (on 0.2.2.x and earlier):
22650 - When a hidden service turns an extra service-side introduction
22651 circuit into a general-purpose circuit, free the rend_data and
22652 intro_key fields first, so we won't leak memory if the circuit
22653 is cannibalized for use as another service-side introduction
22654 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
22655 - Rephrase the log message emitted if the TestSocks check is
22656 successful. Patch from Fabian Keil; fixes bug 4094.
22657 - Bridges now skip DNS self-tests, to act a little more stealthily.
22658 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
22659 bridges. Patch by "warms0x".
22660 - Remove a confusing dollar sign from the example fingerprint in the
22661 man page, and also make the example fingerprint a valid one. Fixes
22662 bug 4309; bugfix on 0.2.1.3-alpha.
22663 - Fix internal bug-checking logic that was supposed to catch
22664 failures in digest generation so that it will fail more robustly
22665 if we ask for a nonexistent algorithm. Found by Coverity Scan.
22666 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
22667 - Report any failure in init_keys() calls launched because our
22668 IP address has changed. Spotted by Coverity Scan. Bugfix on
22669 0.1.1.4-alpha; fixes CID 484.
22671 o Minor bugfixes (on 0.2.3.x):
22672 - Fix a bug in configure.in that kept it from building a configure
22673 script with autoconf versions earlier than 2.61. Fixes bug 2430;
22674 bugfix on 0.2.3.1-alpha.
22675 - Don't warn users that they are exposing a client port to the
22676 Internet if they have specified an RFC1918 address. Previously,
22677 we would warn if the user had specified any non-loopback
22678 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
22679 - Fix memory leaks in the failing cases of the new SocksPort and
22680 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
22681 fixes coverity CIDs 485, 486, and 487.
22684 - When a hidden service's introduction point times out, consider
22685 trying it again during the next attempt to connect to the
22686 HS. Previously, we would not try it again unless a newly fetched
22687 descriptor contained it. Required by fixes for bugs 1297 and 3825.
22688 - The next version of Windows will be called Windows 8, and it has
22689 a major version of 6, minor version of 2. Correctly identify that
22690 version instead of calling it "Very recent version". Resolves
22691 ticket 4153; reported by funkstar.
22692 - The Bridge Authority now writes statistics on how many bridge
22693 descriptors it gave out in total, and how many unique descriptors
22694 it gave out. It also lists how often the most and least commonly
22695 fetched descriptors were given out, as well as the median and
22696 25th/75th percentile. Implements tickets 4200 and 4294.
22697 - Update to the October 4 2011 Maxmind GeoLite Country database.
22699 o Code simplifications and refactoring:
22700 - Remove some old code to remember statistics about which descriptors
22701 we've served as a directory mirror. The feature wasn't used and
22702 is outdated now that microdescriptors are around.
22703 - Rename Tor functions that turn strings into addresses, so that
22704 "parse" indicates that no hostname resolution occurs, and
22705 "lookup" indicates that hostname resolution may occur. This
22706 should help prevent mistakes in the future. Fixes bug 3512.
22709 Changes in version 0.2.2.34 - 2011-10-26
22710 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
22711 can deanonymize Tor users. Everybody should upgrade.
22713 The attack relies on four components: 1) Clients reuse their TLS cert
22714 when talking to different relays, so relays can recognize a user by
22715 the identity key in her cert. 2) An attacker who knows the client's
22716 identity key can probe each guard relay to see if that identity key
22717 is connected to that guard relay right now. 3) A variety of active
22718 attacks in the literature (starting from "Low-Cost Traffic Analysis
22719 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
22720 discover the guard relays that a Tor user visiting the website is using.
22721 4) Clients typically pick three guards at random, so the set of guards
22722 for a given user could well be a unique fingerprint for her. This
22723 release fixes components #1 and #2, which is enough to block the attack;
22724 the other two remain as open research problems. Special thanks to
22725 "frosty_un" for reporting the issue to us!
22727 Clients should upgrade so they are no longer recognizable by the TLS
22728 certs they present. Relays should upgrade so they no longer allow a
22729 remote attacker to probe them to test whether unpatched clients are
22730 currently connected to them.
22732 This release also fixes several vulnerabilities that allow an attacker
22733 to enumerate bridge relays. Some bridge enumeration attacks still
22734 remain; see for example proposal 188.
22736 o Privacy/anonymity fixes (clients):
22737 - Clients and bridges no longer send TLS certificate chains on
22738 outgoing OR connections. Previously, each client or bridge would
22739 use the same cert chain for all outgoing OR connections until
22740 its IP address changes, which allowed any relay that the client
22741 or bridge contacted to determine which entry guards it is using.
22742 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
22743 - If a relay receives a CREATE_FAST cell on a TLS connection, it
22744 no longer considers that connection as suitable for satisfying a
22745 circuit EXTEND request. Now relays can protect clients from the
22746 CVE-2011-2768 issue even if the clients haven't upgraded yet.
22747 - Directory authorities no longer assign the Guard flag to relays
22748 that haven't upgraded to the above "refuse EXTEND requests
22749 to client connections" fix. Now directory authorities can
22750 protect clients from the CVE-2011-2768 issue even if neither
22751 the clients nor the relays have upgraded yet. There's a new
22752 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
22753 to let us transition smoothly, else tomorrow there would be no
22756 o Privacy/anonymity fixes (bridge enumeration):
22757 - Bridge relays now do their directory fetches inside Tor TLS
22758 connections, like all the other clients do, rather than connecting
22759 directly to the DirPort like public relays do. Removes another
22760 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
22761 - Bridges relays now build circuits for themselves in a more similar
22762 way to how clients build them. Removes another avenue for
22763 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
22764 when bridges were introduced.
22765 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
22766 that they initiated. Relays could distinguish incoming bridge
22767 connections from client connections, creating another avenue for
22768 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
22769 Found by "frosty_un".
22772 - Fix a crash bug when changing node restrictions while a DNS lookup
22773 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
22775 - Don't launch a useless circuit after failing to use one of a
22776 hidden service's introduction points. Previously, we would
22777 launch a new introduction circuit, but not set the hidden service
22778 which that circuit was intended to connect to, so it would never
22779 actually be used. A different piece of code would then create a
22780 new introduction circuit correctly. Bug reported by katmagic and
22781 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
22784 - Change an integer overflow check in the OpenBSD_Malloc code so
22785 that GCC is less likely to eliminate it as impossible. Patch
22786 from Mansour Moufid. Fixes bug 4059.
22787 - When a hidden service turns an extra service-side introduction
22788 circuit into a general-purpose circuit, free the rend_data and
22789 intro_key fields first, so we won't leak memory if the circuit
22790 is cannibalized for use as another service-side introduction
22791 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
22792 - Bridges now skip DNS self-tests, to act a little more stealthily.
22793 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
22794 bridges. Patch by "warms0x".
22795 - Fix internal bug-checking logic that was supposed to catch
22796 failures in digest generation so that it will fail more robustly
22797 if we ask for a nonexistent algorithm. Found by Coverity Scan.
22798 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
22799 - Report any failure in init_keys() calls launched because our
22800 IP address has changed. Spotted by Coverity Scan. Bugfix on
22801 0.1.1.4-alpha; fixes CID 484.
22803 o Minor bugfixes (log messages and documentation):
22804 - Remove a confusing dollar sign from the example fingerprint in the
22805 man page, and also make the example fingerprint a valid one. Fixes
22806 bug 4309; bugfix on 0.2.1.3-alpha.
22807 - The next version of Windows will be called Windows 8, and it has
22808 a major version of 6, minor version of 2. Correctly identify that
22809 version instead of calling it "Very recent version". Resolves
22810 ticket 4153; reported by funkstar.
22811 - Downgrade log messages about circuit timeout calibration from
22812 "notice" to "info": they don't require or suggest any human
22813 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
22814 bugfix on 0.2.2.14-alpha.
22817 - Turn on directory request statistics by default and include them in
22818 extra-info descriptors. Don't break if we have no GeoIP database.
22819 Backported from 0.2.3.1-alpha; implements ticket 3951.
22820 - Update to the October 4 2011 Maxmind GeoLite Country database.
22823 Changes in version 0.2.1.31 - 2011-10-26
22824 Tor 0.2.1.31 backports important security and privacy fixes for
22825 oldstable. This release is intended only for package maintainers and
22826 others who cannot use the 0.2.2 stable series. All others should be
22827 using Tor 0.2.2.x or newer.
22829 o Security fixes (also included in 0.2.2.x):
22830 - Replace all potentially sensitive memory comparison operations
22831 with versions whose runtime does not depend on the data being
22832 compared. This will help resist a class of attacks where an
22833 adversary can use variations in timing information to learn
22834 sensitive data. Fix for one case of bug 3122. (Safe memcmp
22835 implementation by Robert Ransom based partially on code by DJB.)
22836 - Fix an assert in parsing router descriptors containing IPv6
22837 addresses. This one took down the directory authorities when
22838 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
22840 o Privacy/anonymity fixes (also included in 0.2.2.x):
22841 - Clients and bridges no longer send TLS certificate chains on
22842 outgoing OR connections. Previously, each client or bridge would
22843 use the same cert chain for all outgoing OR connections until
22844 its IP address changes, which allowed any relay that the client
22845 or bridge contacted to determine which entry guards it is using.
22846 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
22847 - If a relay receives a CREATE_FAST cell on a TLS connection, it
22848 no longer considers that connection as suitable for satisfying a
22849 circuit EXTEND request. Now relays can protect clients from the
22850 CVE-2011-2768 issue even if the clients haven't upgraded yet.
22851 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
22852 that they initiated. Relays could distinguish incoming bridge
22853 connections from client connections, creating another avenue for
22854 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
22855 Found by "frosty_un".
22856 - When receiving a hidden service descriptor, check that it is for
22857 the hidden service we wanted. Previously, Tor would store any
22858 hidden service descriptors that a directory gave it, whether it
22859 wanted them or not. This wouldn't have let an attacker impersonate
22860 a hidden service, but it did let directories pre-seed a client
22861 with descriptors that it didn't want. Bugfix on 0.0.6.
22862 - Avoid linkability based on cached hidden service descriptors: forget
22863 all hidden service descriptors cached as a client when processing a
22864 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
22865 - Make the bridge directory authority refuse to answer directory
22866 requests for "all" descriptors. It used to include bridge
22867 descriptors in its answer, which was a major information leak.
22868 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
22869 - Don't attach new streams to old rendezvous circuits after SIGNAL
22870 NEWNYM. Previously, we would keep using an existing rendezvous
22871 circuit if it remained open (i.e. if it were kept open by a
22872 long-lived stream, or if a new stream were attached to it before
22873 Tor could notice that it was old and no longer in use). Bugfix on
22874 0.1.1.15-rc; fixes bug 3375.
22876 o Minor bugfixes (also included in 0.2.2.x):
22877 - When we restart our relay, we might get a successful connection
22878 from the outside before we've started our reachability tests,
22879 triggering a warning: "ORPort found reachable, but I have no
22880 routerinfo yet. Failing to inform controller of success." This
22881 bug was harmless unless Tor is running under a controller
22882 like Vidalia, in which case the controller would never get a
22883 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
22885 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
22886 enabled. Fixes bug 1526.
22887 - Remove undocumented option "-F" from tor-resolve: it hasn't done
22888 anything since 0.2.1.16-rc.
22889 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
22890 None of the cases where we did this before were wrong, but by making
22891 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
22892 - Fix a rare crash bug that could occur when a client was configured
22893 with a large number of bridges. Fixes bug 2629; bugfix on
22894 0.2.1.2-alpha. Bugfix by trac user "shitlei".
22895 - Correct the warning displayed when a rendezvous descriptor exceeds
22896 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
22898 - Fix an uncommon assertion failure when running with DNSPort under
22899 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
22900 - When warning about missing zlib development packages during compile,
22901 give the correct package names. Bugfix on 0.2.0.1-alpha.
22902 - Require that introduction point keys and onion keys have public
22903 exponent 65537. Bugfix on 0.2.0.10-alpha.
22904 - Do not crash when our configuration file becomes unreadable, for
22905 example due to a permissions change, between when we start up
22906 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
22908 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
22910 - Always NUL-terminate the sun_path field of a sockaddr_un before
22911 passing it to the kernel. (Not a security issue: kernels are
22912 smart enough to reject bad sockaddr_uns.) Found by Coverity;
22913 CID #428. Bugfix on Tor 0.2.0.3-alpha.
22914 - Don't stack-allocate the list of supplementary GIDs when we're
22915 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
22916 could take up to 256K, which is way too much stack. Found by
22917 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
22919 o Minor bugfixes (only in 0.2.1.x):
22920 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
22921 rely on them. Bugfix on 0.2.1.30.
22922 - Use git revisions instead of svn revisions when generating our
22923 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
22925 o Minor features (also included in 0.2.2.x):
22926 - Adjust the expiration time on our SSL session certificates to
22927 better match SSL certs seen in the wild. Resolves ticket 4014.
22928 - Allow nameservers with IPv6 address. Resolves bug 2574.
22929 - Update to the October 4 2011 Maxmind GeoLite Country database.
22932 Changes in version 0.2.3.5-alpha - 2011-09-28
22933 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
22934 bridge relays; fixes an assertion error that many users started hitting
22935 today; and adds the ability to refill token buckets more often than
22936 once per second, allowing significant performance improvements.
22939 - Bridge relays now do their directory fetches inside Tor TLS
22940 connections, like all the other clients do, rather than connecting
22941 directly to the DirPort like public relays do. Removes another
22942 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
22943 - Bridges relays now build circuits for themselves in a more similar
22944 way to how clients build them. Removes another avenue for
22945 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
22946 when bridges were introduced.
22949 - Fix an "Assertion md->held_by_node == 1 failed" error that could
22950 occur when the same microdescriptor was referenced by two node_t
22951 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
22953 o Major features (networking):
22954 - Add a new TokenBucketRefillInterval option to refill token buckets
22955 more frequently than once per second. This should improve network
22956 performance, alleviate queueing problems, and make traffic less
22957 bursty. Implements proposal 183; closes ticket 3630. Design by
22958 Florian Tschorsch and Björn Scheuermann; implementation by
22962 - Change an integer overflow check in the OpenBSD_Malloc code so
22963 that GCC is less likely to eliminate it as impossible. Patch
22964 from Mansour Moufid. Fixes bug 4059.
22966 o Minor bugfixes (usability):
22967 - Downgrade log messages about circuit timeout calibration from
22968 "notice" to "info": they don't require or suggest any human
22969 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
22970 bugfix on 0.2.2.14-alpha.
22972 o Minor features (diagnostics):
22973 - When the system call to create a listener socket fails, log the
22974 error message explaining why. This may help diagnose bug 4027.
22977 Changes in version 0.2.3.4-alpha - 2011-09-13
22978 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
22979 tweak to Tor's TLS handshake that makes relays and bridges that run
22980 this new version reachable from Iran again. It also fixes a few new
22981 bugs in 0.2.3.x, and teaches relays to recognize when they're not
22982 listed in the network consensus and republish.
22984 o Major bugfixes (also part of 0.2.2.33):
22985 - Avoid an assertion failure when reloading a configuration with
22986 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
22987 3923; bugfix on 0.2.2.25-alpha.
22989 o Minor features (security, also part of 0.2.2.33):
22990 - Check for replays of the public-key encrypted portion of an
22991 INTRODUCE1 cell, in addition to the current check for replays of
22992 the g^x value. This prevents a possible class of active attacks
22993 by an attacker who controls both an introduction point and a
22994 rendezvous point, and who uses the malleability of AES-CTR to
22995 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
22996 that these attacks are infeasible (requiring the attacker to send
22997 on the order of zettabytes of altered cells in a short interval),
22998 but we'd rather block them off in case there are any classes of
22999 this attack that we missed. Reported by Willem Pinckaers.
23001 o Minor features (also part of 0.2.2.33):
23002 - Adjust the expiration time on our SSL session certificates to
23003 better match SSL certs seen in the wild. Resolves ticket 4014.
23004 - Change the default required uptime for a relay to be accepted as
23005 a HSDir (hidden service directory) from 24 hours to 25 hours.
23006 Improves on 0.2.0.10-alpha; resolves ticket 2649.
23007 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
23008 authorities to abstain from voting on assignment of the HSDir
23009 consensus flag. Related to bug 2649.
23010 - Update to the September 6 2011 Maxmind GeoLite Country database.
23012 o Minor bugfixes (also part of 0.2.2.33):
23013 - Demote the 'replay detected' log message emitted when a hidden
23014 service receives the same Diffie-Hellman public key in two different
23015 INTRODUCE2 cells to info level. A normal Tor client can cause that
23016 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
23017 fixes part of bug 2442.
23018 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
23019 level. There is nothing that a hidden service's operator can do
23020 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
23022 - Clarify a log message specifying the characters permitted in
23023 HiddenServiceAuthorizeClient client names. Previously, the log
23024 message said that "[A-Za-z0-9+-_]" were permitted; that could have
23025 given the impression that every ASCII character between "+" and "_"
23026 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
23028 o Build fixes (also part of 0.2.2.33):
23029 - Clean up some code issues that prevented Tor from building on older
23030 BSDs. Fixes bug 3894; reported by "grarpamp".
23031 - Search for a platform-specific version of "ar" when cross-compiling.
23032 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
23035 - Fix a bug where the SocksPort option (for example) would get
23036 ignored and replaced by the default if a SocksListenAddress
23037 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
23041 - Relays now try regenerating and uploading their descriptor more
23042 frequently if they are not listed in the consensus, or if the
23043 version of their descriptor listed in the consensus is too
23044 old. This fix should prevent situations where a server declines
23045 to re-publish itself because it has done so too recently, even
23046 though the authorities decided not to list its recent-enough
23047 descriptor. Fix for bug 3327.
23050 - Relays now include a reason for regenerating their descriptors
23051 in an HTTP header when uploading to the authorities. This will
23052 make it easier to debug descriptor-upload issues in the future.
23053 - When starting as root and then changing our UID via the User
23054 control option, and we have a ControlSocket configured, make sure
23055 that the ControlSocket is owned by the same account that Tor will
23056 run under. Implements ticket 3421; fix by Jérémy Bobbio.
23059 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
23060 utility function used in the control-port code). This shouldn't
23061 ever happen unless Tor is completely out of memory, but if it did
23062 happen and Tor somehow recovered from it, Tor could have sent a log
23063 message to a control port in the middle of a reply to a controller
23064 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
23065 - Make 'FetchUselessDescriptors' cause all descriptor types and
23066 all consensus types (including microdescriptors) to get fetched.
23067 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
23069 o Code refactoring:
23070 - Make a new "entry connection" struct as an internal subtype of "edge
23071 connection", to simplify the code and make exit connections smaller.
23074 Changes in version 0.2.2.33 - 2011-09-13
23075 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
23076 TLS handshake that makes relays and bridges that run this new version
23077 reachable from Iran again.
23080 - Avoid an assertion failure when reloading a configuration with
23081 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
23082 3923; bugfix on 0.2.2.25-alpha.
23084 o Minor features (security):
23085 - Check for replays of the public-key encrypted portion of an
23086 INTRODUCE1 cell, in addition to the current check for replays of
23087 the g^x value. This prevents a possible class of active attacks
23088 by an attacker who controls both an introduction point and a
23089 rendezvous point, and who uses the malleability of AES-CTR to
23090 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
23091 that these attacks are infeasible (requiring the attacker to send
23092 on the order of zettabytes of altered cells in a short interval),
23093 but we'd rather block them off in case there are any classes of
23094 this attack that we missed. Reported by Willem Pinckaers.
23097 - Adjust the expiration time on our SSL session certificates to
23098 better match SSL certs seen in the wild. Resolves ticket 4014.
23099 - Change the default required uptime for a relay to be accepted as
23100 a HSDir (hidden service directory) from 24 hours to 25 hours.
23101 Improves on 0.2.0.10-alpha; resolves ticket 2649.
23102 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
23103 authorities to abstain from voting on assignment of the HSDir
23104 consensus flag. Related to bug 2649.
23105 - Update to the September 6 2011 Maxmind GeoLite Country database.
23107 o Minor bugfixes (documentation and log messages):
23108 - Correct the man page to explain that HashedControlPassword and
23109 CookieAuthentication can both be set, in which case either method
23110 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
23111 when we decided to allow these config options to both be set. Issue
23112 raised by bug 3898.
23113 - Demote the 'replay detected' log message emitted when a hidden
23114 service receives the same Diffie-Hellman public key in two different
23115 INTRODUCE2 cells to info level. A normal Tor client can cause that
23116 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
23117 fixes part of bug 2442.
23118 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
23119 level. There is nothing that a hidden service's operator can do
23120 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
23122 - Clarify a log message specifying the characters permitted in
23123 HiddenServiceAuthorizeClient client names. Previously, the log
23124 message said that "[A-Za-z0-9+-_]" were permitted; that could have
23125 given the impression that every ASCII character between "+" and "_"
23126 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
23129 - Provide a substitute implementation of lround() for MSVC, which
23130 apparently lacks it. Patch from Gisle Vanem.
23131 - Clean up some code issues that prevented Tor from building on older
23132 BSDs. Fixes bug 3894; reported by "grarpamp".
23133 - Search for a platform-specific version of "ar" when cross-compiling.
23134 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
23137 Changes in version 0.2.3.3-alpha - 2011-09-01
23138 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
23139 security, and provides client-side support for the microdescriptor
23140 and optimistic data features introduced earlier in the 0.2.3.x
23141 series. It also includes numerous critical bugfixes in the (optional)
23142 bufferevent-based networking backend.
23144 o Major features (stream isolation):
23145 - You can now configure Tor so that streams from different
23146 applications are isolated on different circuits, to prevent an
23147 attacker who sees your streams as they leave an exit node from
23148 linking your sessions to one another. To do this, choose some way
23149 to distinguish the applications: have them connect to different
23150 SocksPorts, or have one of them use SOCKS4 while the other uses
23151 SOCKS5, or have them pass different authentication strings to the
23152 SOCKS proxy. Then, use the new SocksPort syntax to configure the
23153 degree of isolation you need. This implements Proposal 171.
23154 - There's a new syntax for specifying multiple client ports (such as
23155 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
23156 multiple *Port entries with full addr:port syntax on each.
23157 The old *ListenAddress format is still supported, but you can't
23158 mix it with the new *Port syntax.
23160 o Major features (other):
23161 - Enable microdescriptor fetching by default for clients. This allows
23162 clients to download a much smaller amount of directory information.
23163 To disable it (and go back to the old-style consensus and
23164 descriptors), set "UseMicrodescriptors 0" in your torrc file.
23165 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
23166 "PortForwarding" config option), now supports Windows.
23167 - When using an exit relay running 0.2.3.x, clients can now
23168 "optimistically" send data before the exit relay reports that
23169 the stream has opened. This saves a round trip when starting
23170 connections where the client speaks first (such as web browsing).
23171 This behavior is controlled by a consensus parameter (currently
23172 disabled). To turn it on or off manually, use the "OptimisticData"
23173 torrc option. Implements proposal 181; code by Ian Goldberg.
23175 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
23176 - When using IOCP on Windows, we need to enable Libevent windows
23178 - The IOCP backend now works even when the user has not specified
23179 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
23180 Fixes part of bug 3752.
23181 - Correctly record the bytes we've read and written when using
23182 bufferevents, so that we can include them in our bandwidth history
23183 and advertised bandwidth. Fixes bug 3803.
23184 - Apply rate-limiting only at the bottom of a chain of filtering
23185 bufferevents. This prevents us from filling up internal read
23186 buffers and violating rate-limits when filtering bufferevents
23187 are enabled. Fixes part of bug 3804.
23188 - Add high-watermarks to the output buffers for filtered
23189 bufferevents. This prevents us from filling up internal write
23190 buffers and wasting CPU cycles when filtering bufferevents are
23191 enabled. Fixes part of bug 3804.
23192 - Correctly notice when data has been written from a bufferevent
23193 without flushing it completely. Fixes bug 3805.
23194 - Fix a bug where server-side tunneled bufferevent-based directory
23195 streams would get closed prematurely. Fixes bug 3814.
23196 - Fix a use-after-free error with per-connection rate-limiting
23197 buckets. Fixes bug 3888.
23199 o Major bugfixes (also part of 0.2.2.31-rc):
23200 - If we're configured to write our ControlPorts to disk, only write
23201 them after switching UID and creating the data directory. This way,
23202 we don't fail when starting up with a nonexistent DataDirectory
23203 and a ControlPortWriteToFile setting based on that directory. Fixes
23204 bug 3747; bugfix on Tor 0.2.2.26-beta.
23207 - Added a new CONF_CHANGED event so that controllers can be notified
23208 of any configuration changes made by other controllers, or by the
23209 user. Implements ticket 1692.
23210 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
23211 leak when using bufferevents, and lets Libevent worry about how to
23212 best copy data out of a buffer.
23213 - Replace files in stats/ rather than appending to them. Now that we
23214 include statistics in extra-info descriptors, it makes no sense to
23215 keep old statistics forever. Implements ticket 2930.
23217 o Minor features (build compatibility):
23218 - Limited, experimental support for building with nmake and MSVC.
23219 - Provide a substitute implementation of lround() for MSVC, which
23220 apparently lacks it. Patch from Gisle Vanem.
23222 o Minor features (also part of 0.2.2.31-rc):
23223 - Update to the August 2 2011 Maxmind GeoLite Country database.
23225 o Minor bugfixes (on 0.2.3.x-alpha):
23226 - Fix a spurious warning when parsing SOCKS requests with
23227 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
23228 - Get rid of a harmless warning that could happen on relays running
23229 with bufferevents. The warning was caused by someone doing an http
23230 request to a relay's orport. Also don't warn for a few related
23231 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
23233 o Minor bugfixes (on 2.2.x and earlier):
23234 - Correct the man page to explain that HashedControlPassword and
23235 CookieAuthentication can both be set, in which case either method
23236 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
23237 when we decided to allow these config options to both be set. Issue
23238 raised by bug 3898.
23239 - The "--quiet" and "--hush" options now apply not only to Tor's
23240 behavior before logs are configured, but also to Tor's behavior in
23241 the absence of configured logs. Fixes bug 3550; bugfix on
23244 o Minor bugfixes (also part of 0.2.2.31-rc):
23245 - Write several files in text mode, on OSes that distinguish text
23246 mode from binary mode (namely, Windows). These files are:
23247 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
23248 that collect those statistics; 'client_keys' and 'hostname' for
23249 hidden services that use authentication; and (in the tor-gencert
23250 utility) newly generated identity and signing keys. Previously,
23251 we wouldn't specify text mode or binary mode, leading to an
23252 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
23253 the DirRecordUsageByCountry option which would have triggered
23254 the assertion failure was added), although this assertion failure
23255 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
23256 - Selectively disable deprecation warnings on OS X because Lion
23257 started deprecating the shipped copy of openssl. Fixes bug 3643.
23258 - Remove an extra pair of quotation marks around the error
23259 message in control-port STATUS_GENERAL BUG events. Bugfix on
23260 0.1.2.6-alpha; fixes bug 3732.
23261 - When unable to format an address as a string, report its value
23262 as "???" rather than reusing the last formatted address. Bugfix
23265 o Code simplifications and refactoring:
23266 - Rewrite the listener-selection logic so that parsing which ports
23267 we want to listen on is now separate from binding to the ports
23271 - Building Tor with bufferevent support now requires Libevent
23272 2.0.13-stable or later. Previous versions of Libevent had bugs in
23273 SSL-related bufferevents and related issues that would make Tor
23274 work badly with bufferevents. Requiring 2.0.13-stable also allows
23275 Tor with bufferevents to take advantage of Libevent APIs
23276 introduced after 2.0.8-rc.
23279 Changes in version 0.2.2.32 - 2011-08-27
23280 The Tor 0.2.2 release series is dedicated to the memory of Andreas
23281 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
23282 a founder of the PETS community, a leader in our field, a mentor,
23283 and a friend. He left us with these words: "I had the possibility
23284 to contribute to this world that is not as it should be. I hope I
23285 could help in some areas to make the world a better place, and that
23286 I could also encourage other people to be engaged in improving the
23287 world. Please, stay engaged. This world needs you, your love, your
23288 initiative -- now I cannot be part of that anymore."
23290 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
23291 ready. More than two years in the making, this release features improved
23292 client performance and hidden service reliability, better compatibility
23293 for Android, correct behavior for bridges that listen on more than
23294 one address, more extensible and flexible directory object handling,
23295 better reporting of network statistics, improved code security, and
23296 many many other features and bugfixes.
23299 Changes in version 0.2.2.31-rc - 2011-08-17
23300 Tor 0.2.2.31-rc is the second and hopefully final release candidate
23301 for the Tor 0.2.2.x series.
23304 - Remove an extra pair of quotation marks around the error
23305 message in control-port STATUS_GENERAL BUG events. Bugfix on
23306 0.1.2.6-alpha; fixes bug 3732.
23307 - If we're configured to write our ControlPorts to disk, only write
23308 them after switching UID and creating the data directory. This way,
23309 we don't fail when starting up with a nonexistent DataDirectory
23310 and a ControlPortWriteToFile setting based on that directory. Fixes
23311 bug 3747; bugfix on Tor 0.2.2.26-beta.
23314 - Update to the August 2 2011 Maxmind GeoLite Country database.
23317 - Allow GETINFO fingerprint to return a fingerprint even when
23318 we have not yet built a router descriptor. Fixes bug 3577;
23319 bugfix on 0.2.0.1-alpha.
23320 - Write several files in text mode, on OSes that distinguish text
23321 mode from binary mode (namely, Windows). These files are:
23322 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
23323 that collect those statistics; 'client_keys' and 'hostname' for
23324 hidden services that use authentication; and (in the tor-gencert
23325 utility) newly generated identity and signing keys. Previously,
23326 we wouldn't specify text mode or binary mode, leading to an
23327 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
23328 the DirRecordUsageByCountry option which would have triggered
23329 the assertion failure was added), although this assertion failure
23330 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
23331 - Selectively disable deprecation warnings on OS X because Lion
23332 started deprecating the shipped copy of openssl. Fixes bug 3643.
23333 - When unable to format an address as a string, report its value
23334 as "???" rather than reusing the last formatted address. Bugfix
23338 Changes in version 0.2.3.2-alpha - 2011-07-18
23339 Tor 0.2.3.2-alpha introduces two new experimental features:
23340 microdescriptors and pluggable transports. It also continues cleaning
23341 up a variety of recently introduced features.
23344 - Clients can now use microdescriptors instead of regular descriptors
23345 to build circuits. Microdescriptors are authority-generated
23346 summaries of regular descriptors' contents, designed to change
23347 very rarely (see proposal 158 for details). This feature is
23348 designed to save bandwidth, especially for clients on slow internet
23349 connections. It's off by default for now, since nearly no caches
23350 support it, but it will be on-by-default for clients in a future
23351 version. You can use the UseMicrodescriptors option to turn it on.
23352 - Tor clients using bridges can now be configured to use a separate
23353 'transport' proxy for each bridge. This approach helps to resist
23354 censorship by allowing bridges to use protocol obfuscation
23355 plugins. It implements part of proposal 180. Implements ticket 2841.
23356 - While we're trying to bootstrap, record how many TLS connections
23357 fail in each state, and report which states saw the most failures
23358 in response to any bootstrap failures. This feature may speed up
23359 diagnosis of censorship events. Implements ticket 3116.
23361 o Major bugfixes (on 0.2.3.1-alpha):
23362 - When configuring a large set of nodes in EntryNodes (as with
23363 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
23364 random subset to be guards, and choose them in random
23365 order. Fixes bug 2798.
23366 - Tor could crash when remembering a consensus in a non-used consensus
23367 flavor without having a current consensus set. Fixes bug 3361.
23368 - Comparing an unknown address to a microdescriptor's shortened exit
23369 policy would always give a "rejected" result. Fixes bug 3599.
23370 - Using microdescriptors as a client no longer prevents Tor from
23371 uploading and downloading hidden service descriptors. Fixes
23375 - Allow nameservers with IPv6 address. Resolves bug 2574.
23376 - Accept attempts to include a password authenticator in the
23377 handshake, as supported by SOCKS5. This handles SOCKS clients that
23378 don't know how to omit a password when authenticating. Resolves
23380 - When configuring a large set of nodes in EntryNodes, and there are
23381 enough of them listed as Guard so that we don't need to consider
23382 the non-guard entries, prefer the ones listed with the Guard flag.
23383 - Check for and recover from inconsistency in the microdescriptor
23384 cache. This will make it harder for us to accidentally free a
23385 microdescriptor without removing it from the appropriate data
23386 structures. Fixes issue 3135; issue noted by "wanoskarnet".
23387 - Log SSL state transitions at log level DEBUG, log domain
23388 HANDSHAKE. This can be useful for debugging censorship events.
23389 Implements ticket 3264.
23390 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
23391 implements ticket 3439.
23393 o Minor bugfixes (on 0.2.3.1-alpha):
23394 - Do not free all general-purpose regular descriptors just
23395 because microdescriptor use is enabled. Fixes bug 3113.
23396 - Correctly link libevent_openssl when --enable-static-libevent
23397 is passed to configure. Fixes bug 3118.
23398 - Bridges should not complain during their heartbeat log messages that
23399 they are unlisted in the consensus: that's more or less the point
23400 of being a bridge. Fixes bug 3183.
23401 - Report a SIGNAL event to controllers when acting on a delayed
23402 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
23403 event to the controller if we acted on a SIGNAL NEWNYM command
23404 immediately, and otherwise not report a SIGNAL event for the
23405 command at all. Fixes bug 3349.
23406 - Fix a crash when handling the SIGNAL controller command or
23407 reporting ERR-level status events with bufferevents enabled. Found
23408 by Robert Ransom. Fixes bug 3367.
23409 - Always ship the tor-fw-helper manpage in our release tarballs.
23410 Fixes bug 3389. Reported by Stephen Walker.
23411 - Fix a class of double-mark-for-close bugs when bufferevents
23412 are enabled. Fixes bug 3403.
23413 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
23414 - Add SIGNAL to the list returned by the 'GETINFO events/names'
23415 control-port command. Fixes part of bug 3465.
23416 - Prevent using negative indices during unit test runs when read_all()
23417 fails. Spotted by coverity.
23418 - Fix a rare memory leak when checking the nodelist without it being
23419 present. Found by coverity.
23420 - Only try to download a microdescriptor-flavored consensus from
23421 a directory cache that provides them.
23423 o Minor bugfixes (on 0.2.2.x and earlier):
23424 - Assert that hidden-service-related operations are not performed
23425 using single-hop circuits. Previously, Tor would assert that
23426 client-side streams are not attached to single-hop circuits,
23427 but not that other sensitive operations on the client and service
23428 side are not performed using single-hop circuits. Fixes bug 3332;
23430 - Don't publish a new relay descriptor when we reload our onion key,
23431 unless the onion key has actually changed. Fixes bug 3263 and
23432 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
23433 - Allow GETINFO fingerprint to return a fingerprint even when
23434 we have not yet built a router descriptor. Fixes bug 3577;
23435 bugfix on 0.2.0.1-alpha.
23436 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
23437 on 0.2.2.4-alpha; fixes bug 3427.
23439 o Code simplification and refactoring:
23440 - Use tor_sscanf() in place of scanf() in more places through the
23441 code. This makes us a little more locale-independent, and
23442 should help shut up code-analysis tools that can't tell
23443 a safe sscanf string from a dangerous one.
23444 - Use tt_assert(), not tor_assert(), for checking for test failures.
23445 This makes the unit tests more able to go on in the event that
23447 - Split connection_about_to_close() into separate functions for each
23451 - On Windows, we now define the _WIN32_WINNT macros only if they
23452 are not already defined. This lets the person building Tor decide,
23453 if they want, to require a later version of Windows.
23456 Changes in version 0.2.2.30-rc - 2011-07-07
23457 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
23458 series. It fixes a few smaller bugs, but generally appears stable.
23459 Please test it and let us know whether it is!
23462 - Send a SUCCEEDED stream event to the controller when a reverse
23463 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
23464 discovered by katmagic.
23465 - Always NUL-terminate the sun_path field of a sockaddr_un before
23466 passing it to the kernel. (Not a security issue: kernels are
23467 smart enough to reject bad sockaddr_uns.) Found by Coverity;
23468 CID #428. Bugfix on Tor 0.2.0.3-alpha.
23469 - Don't stack-allocate the list of supplementary GIDs when we're
23470 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
23471 could take up to 256K, which is way too much stack. Found by
23472 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
23473 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
23474 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
23475 fixes part of bug 3465.
23476 - Fix a memory leak when receiving a descriptor for a hidden
23477 service we didn't ask for. Found by Coverity; CID #30. Bugfix
23481 - Update to the July 1 2011 Maxmind GeoLite Country database.
23484 Changes in version 0.2.2.29-beta - 2011-06-20
23485 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
23486 have bridge lines in their torrc but don't want to use them; gets
23487 us closer to having the control socket feature working on Debian;
23488 and fixes a variety of smaller bugs.
23491 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
23492 When we changed the default behavior to "use bridges if any
23493 are listed in the torrc", we surprised users who had bridges
23494 in their torrc files but who didn't actually want to use them.
23495 Partial resolution for bug 3354.
23498 - Don't attach new streams to old rendezvous circuits after SIGNAL
23499 NEWNYM. Previously, we would keep using an existing rendezvous
23500 circuit if it remained open (i.e. if it were kept open by a
23501 long-lived stream, or if a new stream were attached to it before
23502 Tor could notice that it was old and no longer in use). Bugfix on
23503 0.1.1.15-rc; fixes bug 3375.
23506 - Fix a bug when using ControlSocketsGroupWritable with User. The
23507 directory's group would be checked against the current group, not
23508 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
23509 bugfix on 0.2.2.26-beta.
23510 - Make connection_printf_to_buf()'s behavior sane. Its callers
23511 expect it to emit a CRLF iff the format string ends with CRLF;
23512 it actually emitted a CRLF iff (a) the format string ended with
23513 CRLF or (b) the resulting string was over 1023 characters long or
23514 (c) the format string did not end with CRLF *and* the resulting
23515 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
23516 fixes part of bug 3407.
23517 - Make send_control_event_impl()'s behavior sane. Its callers
23518 expect it to always emit a CRLF at the end of the string; it
23519 might have emitted extra control characters as well. Bugfix on
23520 0.1.1.9-alpha; fixes another part of bug 3407.
23521 - Make crypto_rand_int() check the value of its input correctly.
23522 Previously, it accepted values up to UINT_MAX, but could return a
23523 negative number if given a value above INT_MAX+1. Found by George
23524 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
23525 - Avoid a segfault when reading a malformed circuit build state
23526 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
23528 - When asked about a DNS record type we don't support via a
23529 client DNSPort, reply with NOTIMPL rather than an empty
23530 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
23531 - Fix a rare memory leak during stats writing. Found by coverity.
23534 - Update to the June 1 2011 Maxmind GeoLite Country database.
23536 o Code simplifications and refactoring:
23537 - Remove some dead code as indicated by coverity.
23538 - Remove a few dead assignments during router parsing. Found by
23540 - Add some forgotten return value checks during unit tests. Found
23542 - Don't use 1-bit wide signed bit fields. Found by coverity.
23545 Changes in version 0.2.2.28-beta - 2011-06-04
23546 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
23547 fixed a big bug in whether relays stay in the consensus consistently,
23548 we moved closer to handling bridges and hidden services correctly,
23549 and we started the process of better handling the dreaded "my Vidalia
23550 died, and now my Tor demands a password when I try to reconnect to it"
23554 - Don't decide to make a new descriptor when receiving a HUP signal.
23555 This bug has caused a lot of 0.2.2.x relays to disappear from the
23556 consensus periodically. Fixes the most common case of triggering
23557 bug 1810; bugfix on 0.2.2.7-alpha.
23558 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
23559 - Don't try to build descriptors if "ORPort auto" is set and we
23560 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
23562 - Resolve a crash that occurred when setting BridgeRelay to 1 with
23563 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
23564 - Apply circuit timeouts to opened hidden-service-related circuits
23565 based on the correct start time. Previously, we would apply the
23566 circuit build timeout based on time since the circuit's creation;
23567 it was supposed to be applied based on time since the circuit
23568 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
23569 - Use the same circuit timeout for client-side introduction
23570 circuits as for other four-hop circuits, rather than the timeout
23571 for single-hop directory-fetch circuits; the shorter timeout may
23572 have been appropriate with the static circuit build timeout in
23573 0.2.1.x and earlier, but caused many hidden service access attempts
23574 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
23575 on 0.2.2.2-alpha; fixes another part of bug 1297.
23576 - In ticket 2511 we fixed a case where you could use an unconfigured
23577 bridge if you had configured it as a bridge the last time you ran
23578 Tor. Now fix another edge case: if you had configured it as a bridge
23579 but then switched to a different bridge via the controller, you
23580 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
23584 - Add an __OwningControllerProcess configuration option and a
23585 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
23586 that when it exits, Tor will shut down. Implements feature 3049.
23587 - If "UseBridges 1" is set and no bridges are configured, Tor will
23588 now refuse to build any circuits until some bridges are set.
23589 If "UseBridges auto" is set, Tor will use bridges if they are
23590 configured and we are not running as a server, but otherwise will
23591 make circuits as usual. The new default is "auto". Patch by anonym,
23592 so the Tails LiveCD can stop automatically revealing you as a Tor
23596 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
23597 - Remove a trailing asterisk from "exit-policy/default" in the
23598 output of the control port command "GETINFO info/names". Bugfix
23600 - Use a wide type to hold sockets when built for 64-bit Windows builds.
23602 - Warn when the user configures two HiddenServiceDir lines that point
23603 to the same directory. Bugfix on 0.0.6 (the version introducing
23604 HiddenServiceDir); fixes bug 3289.
23605 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
23606 part of bug 2748; bugfix on 0.2.0.10-alpha.
23607 - Log malformed requests for rendezvous descriptors as protocol
23608 warnings, not warnings. Also, use a more informative log message
23609 in case someone sees it at log level warning without prior
23610 info-level messages. Fixes the other part of bug 2748; bugfix
23612 - Clear the table recording the time of the last request for each
23613 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
23614 Previously, we would clear our HS descriptor cache on SIGNAL
23615 NEWNYM, but if we had previously retrieved a descriptor (or tried
23616 to) from every directory responsible for it, we would refuse to
23617 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
23619 - Fix a log message that said "bits" while displaying a value in
23620 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
23622 - When checking for 1024-bit keys, check for 1024 bits, not 128
23623 bytes. This allows Tor to correctly discard keys of length 1017
23624 through 1023. Bugfix on 0.0.9pre5.
23627 - Relays now log the reason for publishing a new relay descriptor,
23628 so we have a better chance of hunting down instances of bug 1810.
23629 Resolves ticket 3252.
23630 - Revise most log messages that refer to nodes by nickname to
23631 instead use the "$key=nickname at address" format. This should be
23632 more useful, especially since nicknames are less and less likely
23633 to be unique. Resolves ticket 3045.
23634 - Log (at info level) when purging pieces of hidden-service-client
23635 state because of SIGNAL NEWNYM.
23638 - Remove undocumented option "-F" from tor-resolve: it hasn't done
23639 anything since 0.2.1.16-rc.
23642 Changes in version 0.2.2.27-beta - 2011-05-18
23643 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
23644 release, and also adds a few more general bugfixes.
23647 - Fix a crash bug when changing bridges in a running Tor process.
23648 Fixes bug 3213; bugfix on 0.2.2.26-beta.
23649 - When the controller configures a new bridge, don't wait 10 to 60
23650 seconds before trying to fetch its descriptor. Bugfix on
23651 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
23654 - Require that onion keys have exponent 65537 in microdescriptors too.
23655 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
23656 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
23657 Changed the limit to 512 characters by removing base64 newlines.
23658 Fixes bug 2752. Fix by Michael Yakubovich.
23659 - When a client starts or stops using bridges, never use a circuit
23660 that was built before the configuration change. This behavior could
23661 put at risk a user who uses bridges to ensure that her traffic
23662 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
23666 Changes in version 0.2.2.26-beta - 2011-05-17
23667 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
23668 also introduces a new "socksport auto" approach that should make it
23669 easier to run multiple Tors on the same system, and does a lot of
23670 cleanup to get us closer to a release candidate.
23672 o Security/privacy fixes:
23673 - Replace all potentially sensitive memory comparison operations
23674 with versions whose runtime does not depend on the data being
23675 compared. This will help resist a class of attacks where an
23676 adversary can use variations in timing information to learn
23677 sensitive data. Fix for one case of bug 3122. (Safe memcmp
23678 implementation by Robert Ransom based partially on code by DJB.)
23679 - When receiving a hidden service descriptor, check that it is for
23680 the hidden service we wanted. Previously, Tor would store any
23681 hidden service descriptors that a directory gave it, whether it
23682 wanted them or not. This wouldn't have let an attacker impersonate
23683 a hidden service, but it did let directories pre-seed a client
23684 with descriptors that it didn't want. Bugfix on 0.0.6.
23685 - On SIGHUP, do not clear out all TrackHostExits mappings, client
23686 DNS cache entries, and virtual address mappings: that's what
23687 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
23690 - The options SocksPort, ControlPort, and so on now all accept a
23691 value "auto" that opens a socket on an OS-selected port. A
23692 new ControlPortWriteToFile option tells Tor to write its
23693 actual control port or ports to a chosen file. If the option
23694 ControlPortFileGroupReadable is set, the file is created as
23695 group-readable. Now users can run two Tor clients on the same
23696 system without needing to manually mess with parameters. Resolves
23697 part of ticket 3076.
23698 - Set SO_REUSEADDR on all sockets, not just listeners. This should
23699 help busy exit nodes avoid running out of useable ports just
23700 because all the ports have been used in the near past. Resolves
23704 - New "GETINFO net/listeners/(type)" controller command to return
23705 a list of addresses and ports that are bound for listeners for a
23706 given connection type. This is useful when the user has configured
23707 "SocksPort auto" and the controller needs to know which port got
23708 chosen. Resolves another part of ticket 3076.
23709 - Add a new ControlSocketsGroupWritable configuration option: when
23710 it is turned on, ControlSockets are group-writeable by the default
23711 group of the current user. Patch by Jérémy Bobbio; implements
23713 - Tor now refuses to create a ControlSocket in a directory that is
23714 world-readable (or group-readable if ControlSocketsGroupWritable
23715 is 0). This is necessary because some operating systems do not
23716 enforce permissions on an AF_UNIX sockets. Permissions on the
23717 directory holding the socket, however, seems to work everywhere.
23718 - Rate-limit a warning about failures to download v2 networkstatus
23719 documents. Resolves part of bug 1352.
23720 - Backport code from 0.2.3.x that allows directory authorities to
23721 clean their microdescriptor caches. Needed to resolve bug 2230.
23722 - When an HTTPS proxy reports "403 Forbidden", we now explain
23723 what it means rather than calling it an unexpected status code.
23724 Closes bug 2503. Patch from Michael Yakubovich.
23725 - Update to the May 1 2011 Maxmind GeoLite Country database.
23728 - Authorities now clean their microdesc cache periodically and when
23729 reading from disk initially, not only when adding new descriptors.
23730 This prevents a bug where we could lose microdescriptors. Bugfix
23731 on 0.2.2.6-alpha. Fixes bug 2230.
23732 - Do not crash when our configuration file becomes unreadable, for
23733 example due to a permissions change, between when we start up
23734 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
23736 - Avoid a bug that would keep us from replacing a microdescriptor
23737 cache on Windows. (We would try to replace the file while still
23738 holding it open. That's fine on Unix, but Windows doesn't let us
23739 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
23740 - Add missing explanations for the authority-related torrc options
23741 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
23742 man page. Resolves issue 2379.
23743 - As an authority, do not upload our own vote or signature set to
23744 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
23745 it would get flagged as a duplicate. Resolves bug 3026.
23746 - Accept hidden service descriptors if we think we might be a hidden
23747 service directory, regardless of what our consensus says. This
23748 helps robustness, since clients and hidden services can sometimes
23749 have a more up-to-date view of the network consensus than we do,
23750 and if they think that the directory authorities list us a HSDir,
23751 we might actually be one. Related to bug 2732; bugfix on
23753 - When a controller changes TrackHostExits, remove mappings for
23754 hosts that should no longer have their exits tracked. Bugfix on
23756 - When a controller changes VirtualAddrNetwork, remove any mappings
23757 for hosts that were automapped to the old network. Bugfix on
23759 - When a controller changes one of the AutomapHosts* options, remove
23760 any mappings for hosts that should no longer be automapped. Bugfix
23762 - Do not reset the bridge descriptor download status every time we
23763 re-parse our configuration or get a configuration change. Fixes
23764 bug 3019; bugfix on 0.2.0.3-alpha.
23766 o Minor bugfixes (code cleanup):
23767 - When loading the microdesc journal, remember its current size.
23768 In 0.2.2, this helps prevent the microdesc journal from growing
23769 without limit on authorities (who are the only ones to use it in
23770 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
23771 Fix posted by "cypherpunks."
23772 - The microdesc journal is supposed to get rebuilt only if it is
23773 at least _half_ the length of the store, not _twice_ the length
23774 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
23775 - Fix a potential null-pointer dereference while computing a
23776 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
23778 - Avoid a possible null-pointer dereference when rebuilding the mdesc
23779 cache without actually having any descriptors to cache. Bugfix on
23780 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
23781 - If we fail to compute the identity digest of a v3 legacy keypair,
23782 warn, and don't use a buffer-full of junk instead. Bugfix on
23783 0.2.1.1-alpha; fixes bug 3106.
23784 - Resolve an untriggerable issue in smartlist_string_num_isin(),
23785 where if the function had ever in the future been used to check
23786 for the presence of a too-large number, it would have given an
23787 incorrect result. (Fortunately, we only used it for 16-bit
23788 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
23789 - Require that introduction point keys and onion handshake keys
23790 have a public exponent of 65537. Starts to fix bug 3207; bugfix
23793 o Removed features:
23794 - Caches no longer download and serve v2 networkstatus documents
23795 unless FetchV2Networkstatus flag is set: these documents haven't
23796 haven't been used by clients or relays since 0.2.0.x. Resolves
23800 Changes in version 0.2.3.1-alpha - 2011-05-05
23801 Tor 0.2.3.1-alpha adds some new experimental features, including support
23802 for an improved network IO backend, IOCP networking on Windows,
23803 microdescriptor caching, "fast-start" support for streams, and automatic
23804 home router configuration. There are also numerous internal improvements
23805 to try to make the code easier for developers to work with.
23807 This is the first alpha release in a new series, so expect there to be
23808 bugs. Users who would rather test out a more stable branch should
23809 stay with 0.2.2.x for now.
23812 - Tor can now optionally build with the "bufferevents" buffered IO
23813 backend provided by Libevent 2. To use this feature, make sure you
23814 have the latest possible version of Libevent, and pass the
23815 --enable-bufferevents flag to configure when building Tor from
23816 source. This feature will make our networking code more flexible,
23817 let us stack layers on each other, and let us use more efficient
23818 zero-copy transports where available.
23819 - As an experimental feature, Tor can use IOCP for networking on Windows.
23820 Once this code is tuned and optimized, it promises much better
23821 performance than the select-based backend we've used in the past. To
23822 try this feature, you must build Tor with Libevent 2, configure Tor
23823 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
23824 your torrc. There are known bugs here: only try this if you can help
23825 debug it as it breaks.
23826 - The EntryNodes option can now include country codes like {de} or IP
23827 addresses or network masks. Previously we had disallowed these options
23828 because we didn't have an efficient way to keep the list up to
23829 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
23830 - Exit nodes now accept and queue data on not-yet-connected streams.
23831 Previously, the client wasn't allowed to send data until the stream was
23832 connected, which slowed down all connections. This change will enable
23833 clients to perform a "fast-start" on streams and send data without
23834 having to wait for a confirmation that the stream has opened. (Patch
23835 from Ian Goldberg; implements the server side of Proposal 174.)
23836 - Tor now has initial support for automatic port mapping on the many
23837 home routers that support NAT-PMP or UPnP. (Not yet supported on
23838 Windows). To build the support code, you'll need to have libnatpnp
23839 library and/or the libminiupnpc library, and you'll need to enable the
23840 feature specifically by passing "--enable-upnp" and/or
23841 "--enable-natpnp" to configure. To turn it on, use the new
23842 PortForwarding option.
23843 - Caches now download, cache, and serve multiple "flavors" of the
23844 consensus, including a flavor that describes microdescriptors.
23845 - Caches now download, cache, and serve microdescriptors -- small
23846 summaries of router descriptors that are authenticated by all of the
23847 directory authorities. Once enough caches are running this code,
23848 clients will be able to save significant amounts of directory bandwidth
23849 by downloading microdescriptors instead of router descriptors.
23852 - Make logging resolution configurable with a new LogTimeGranularity
23853 option, and change the default from 1 millisecond to 1 second.
23854 Implements enhancement 1668.
23855 - We log which torrc file we're using on startup. Implements ticket
23857 - Ordinarily, Tor does not count traffic from private addresses (like
23858 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
23859 There is now a new option, CountPrivateBandwidth, to disable this
23860 behavior. Patch from Daniel Cagara.
23861 - New --enable-static-tor configure option for building Tor as
23862 statically as possible. Idea, general hackery and thoughts from
23863 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
23865 - If you set the NumCPUs option to 0, Tor will now try to detect how
23866 many CPUs you have. This is the new default behavior.
23867 - Turn on directory request statistics by default and include them in
23868 extra-info descriptors. Don't break if we have no GeoIP database.
23869 - Relays that set "ConnDirectionStatistics 1" write statistics on the
23870 bidirectional use of connections to disk every 24 hours.
23871 - Add a GeoIP file digest to the extra-info descriptor. Implements
23873 - The NodeFamily option -- which let you declare that you want to
23874 consider nodes to be part of a family whether they list themselves
23875 that way or not -- now allows IP address ranges and country codes.
23876 - Add a new 'Heartbeat' log message type to periodically log a message
23877 describing Tor's status at level Notice. This feature is meant for
23878 operators who log at notice, and want to make sure that their Tor
23879 server is still working. Implementation by George Kadianakis.
23881 o Minor bugfixes (on 0.2.2.25-alpha):
23882 - When loading the microdesc journal, remember its current size.
23883 In 0.2.2, this helps prevent the microdesc journal from growing
23884 without limit on authorities (who are the only ones to use it in
23885 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
23886 Fix posted by "cypherpunks."
23887 - The microdesc journal is supposed to get rebuilt only if it is
23888 at least _half_ the length of the store, not _twice_ the length
23889 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
23890 - If as an authority we fail to compute the identity digest of a v3
23891 legacy keypair, warn, and don't use a buffer-full of junk instead.
23892 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
23893 - Authorities now clean their microdesc cache periodically and when
23894 reading from disk initially, not only when adding new descriptors.
23895 This prevents a bug where we could lose microdescriptors. Bugfix
23898 o Minor features (controller):
23899 - Add a new SIGNAL event to the controller interface so that
23900 controllers can be notified when Tor handles a signal. Resolves
23901 issue 1955. Patch by John Brooks.
23902 - Add a new GETINFO option to get total bytes read and written. Patch
23903 from pipe, revised by atagar. Resolves ticket 2345.
23904 - Implement some GETINFO controller fields to provide information about
23905 the Tor process's pid, euid, username, and resource limits.
23908 - Our build system requires automake 1.6 or later to create the
23909 Makefile.in files. Previously, you could have used 1.4.
23910 This only affects developers and people building Tor from git;
23911 people who build Tor from the source distribution without changing
23912 the Makefile.am files should be fine.
23913 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
23914 so on. This is more robust against some of the failure modes
23915 associated with running the autotools pieces on their own.
23917 o Minor packaging issues:
23918 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
23919 already created. Patch from Andreas Stieger. Fixes bug 2573.
23921 o Code simplifications and refactoring:
23922 - A major revision to our internal node-selecting and listing logic.
23923 Tor already had at least two major ways to look at the question of
23924 "which Tor servers do we know about": a list of router descriptors,
23925 and a list of entries in the current consensus. With
23926 microdescriptors, we're adding a third. Having so many systems
23927 without an abstraction layer over them was hurting the codebase.
23928 Now, we have a new "node_t" abstraction that presents a consistent
23929 interface to a client's view of a Tor node, and holds (nearly) all
23930 of the mutable state formerly in routerinfo_t and routerstatus_t.
23931 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
23932 no longer link against Libevent: they never used it, but
23933 our library structure used to force them to link it.
23935 o Removed features:
23936 - Remove some old code to work around even older versions of Tor that
23937 used forked processes to handle DNS requests. Such versions of Tor
23938 are no longer in use as servers.
23940 o Documentation fixes:
23941 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
23942 - Add missing documentation for the authority-related torrc options
23943 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
23947 Changes in version 0.2.2.25-alpha - 2011-04-29
23948 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
23949 robust, routers no longer overreport their bandwidth, Win7 should crash
23950 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
23951 now prevents hidden service-related activity from being linkable. It
23952 provides more information to Vidalia so you can see if your bridge is
23953 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
23954 StrictNodes configuration options to make them more reliable, more
23955 understandable, and more regularly applied. If you use those options,
23956 please see the revised documentation for them in the manual page.
23959 - Relays were publishing grossly inflated bandwidth values because
23960 they were writing their state files wrong--now they write the
23961 correct value. Also, resume reading bandwidth history from the
23962 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
23963 - Improve hidden service robustness: When we find that we have
23964 extended a hidden service's introduction circuit to a relay not
23965 listed as an introduction point in the HS descriptor we currently
23966 have, retry with an introduction point from the current
23967 descriptor. Previously we would just give up. Fixes bugs 1024 and
23968 1930; bugfix on 0.2.0.10-alpha.
23969 - Clients now stop trying to use an exit node associated with a given
23970 destination by TrackHostExits if they fail to reach that exit node.
23971 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
23972 - Fix crash bug on platforms where gmtime and localtime can return
23973 NULL. Windows 7 users were running into this one. Fixes part of bug
23974 2077. Bugfix on all versions of Tor. Found by boboper.
23976 o Security and stability fixes:
23977 - Don't double-free a parsable, but invalid, microdescriptor, even if
23978 it is followed in the blob we're parsing by an unparsable
23979 microdescriptor. Fixes an issue reported in a comment on bug 2954.
23980 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
23981 - If the Nickname configuration option isn't given, Tor would pick a
23982 nickname based on the local hostname as the nickname for a relay.
23983 Because nicknames are not very important in today's Tor and the
23984 "Unnamed" nickname has been implemented, this is now problematic
23985 behavior: It leaks information about the hostname without being
23986 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
23987 introduced the Unnamed nickname. Reported by tagnaq.
23988 - Fix an uncommon assertion failure when running with DNSPort under
23989 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
23990 - Avoid linkability based on cached hidden service descriptors: forget
23991 all hidden service descriptors cached as a client when processing a
23992 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
23995 - Export GeoIP information on bridge usage to controllers even if we
23996 have not yet been running for 24 hours. Now Vidalia bridge operators
23997 can get more accurate and immediate feedback about their
23998 contributions to the network.
24000 o Major features and bugfixes (node selection):
24001 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
24002 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
24003 options. Previously, we had been ambiguous in describing what
24004 counted as an "exit" node, and what operations exactly "StrictNodes
24005 0" would permit. This created confusion when people saw nodes built
24006 through unexpected circuits, and made it hard to tell real bugs from
24007 surprises. Now the intended behavior is:
24008 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
24009 a node that delivers user traffic outside the Tor network.
24010 . "Entry", in the context of EntryNodes, means a node used as the
24011 first hop of a multihop circuit. It doesn't include direct
24012 connections to directory servers.
24013 . "ExcludeNodes" applies to all nodes.
24014 . "StrictNodes" changes the behavior of ExcludeNodes only. When
24015 StrictNodes is set, Tor should avoid all nodes listed in
24016 ExcludeNodes, even when it will make user requests fail. When
24017 StrictNodes is *not* set, then Tor should follow ExcludeNodes
24018 whenever it can, except when it must use an excluded node to
24019 perform self-tests, connect to a hidden service, provide a
24020 hidden service, fulfill a .exit request, upload directory
24021 information, or fetch directory information.
24022 Collectively, the changes to implement the behavior fix bug 1090.
24023 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
24024 a node is listed in both, it's treated as excluded.
24025 - ExcludeNodes now applies to directory nodes -- as a preference if
24026 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
24027 Don't exclude all the directory authorities and set StrictNodes to 1
24028 unless you really want your Tor to break.
24029 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
24030 - ExcludeExitNodes now overrides .exit requests.
24031 - We don't use bridges listed in ExcludeNodes.
24032 - When StrictNodes is 1:
24033 . We now apply ExcludeNodes to hidden service introduction points
24034 and to rendezvous points selected by hidden service users. This
24035 can make your hidden service less reliable: use it with caution!
24036 . If we have used ExcludeNodes on ourself, do not try relay
24037 reachability self-tests.
24038 . If we have excluded all the directory authorities, we will not
24039 even try to upload our descriptor if we're a relay.
24040 . Do not honor .exit requests to an excluded node.
24041 - Remove a misfeature that caused us to ignore the Fast/Stable flags
24042 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
24043 - When the set of permitted nodes changes, we now remove any mappings
24044 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
24046 - We never cannibalize a circuit that had excluded nodes on it, even
24047 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
24048 - Revert a change where we would be laxer about attaching streams to
24049 circuits than when building the circuits. This was meant to prevent
24050 a set of bugs where streams were never attachable, but our improved
24051 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
24052 - Keep track of how many times we launch a new circuit to handle a
24053 given stream. Too many launches could indicate an inconsistency
24054 between our "launch a circuit to handle this stream" logic and our
24055 "attach this stream to one of the available circuits" logic.
24056 - Improve log messages related to excluded nodes.
24059 - Fix a spurious warning when moving from a short month to a long
24060 month on relays with month-based BandwidthAccounting. Bugfix on
24061 0.2.2.17-alpha; fixes bug 3020.
24062 - When a client finds that an origin circuit has run out of 16-bit
24063 stream IDs, we now mark it as unusable for new streams. Previously,
24064 we would try to close the entire circuit. Bugfix on 0.0.6.
24065 - Add a forgotten cast that caused a compile warning on OS X 10.6.
24066 Bugfix on 0.2.2.24-alpha.
24067 - Be more careful about reporting the correct error from a failed
24068 connect() system call. Under some circumstances, it was possible to
24069 look at an incorrect value for errno when sending the end reason.
24070 Bugfix on 0.1.0.1-rc.
24071 - Correctly handle an "impossible" overflow cases in connection byte
24072 counting, where we write or read more than 4GB on an edge connection
24073 in a single second. Bugfix on 0.1.2.8-beta.
24074 - Correct the warning displayed when a rendezvous descriptor exceeds
24075 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
24077 - Clients and hidden services now use HSDir-flagged relays for hidden
24078 service descriptor downloads and uploads even if the relays have no
24079 DirPort set and the client has disabled TunnelDirConns. This will
24080 eventually allow us to give the HSDir flag to relays with no
24081 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
24082 - Downgrade "no current certificates known for authority" message from
24083 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
24084 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
24085 2917. Bugfix on 0.1.1.1-alpha.
24086 - Only limit the lengths of single HS descriptors, even when multiple
24087 HS descriptors are published to an HSDir relay in a single POST
24088 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
24089 - Write the current time into the LastWritten line in our state file,
24090 rather than the time from the previous write attempt. Also, stop
24091 trying to use a time of -1 in our log statements. Fixes bug 3039;
24092 bugfix on 0.2.2.14-alpha.
24093 - Be more consistent in our treatment of file system paths. "~" should
24094 get expanded to the user's home directory in the Log config option.
24095 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
24096 feature for the -f and --DataDirectory options.
24099 - Make sure every relay writes a state file at least every 12 hours.
24100 Previously, a relay could go for weeks without writing its state
24101 file, and on a crash could lose its bandwidth history, capacity
24102 estimates, client country statistics, and so on. Addresses bug 3012.
24103 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
24104 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
24105 clients are already deprecated because of security bugs.
24106 - Don't allow v0 hidden service authorities to act as clients.
24107 Required by fix for bug 3000.
24108 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
24109 by fix for bug 3000.
24110 - Ensure that no empty [dirreq-](read|write)-history lines are added
24111 to an extrainfo document. Implements ticket 2497.
24113 o Code simplification and refactoring:
24114 - Remove workaround code to handle directory responses from servers
24115 that had bug 539 (they would send HTTP status 503 responses _and_
24116 send a body too). Since only server versions before
24117 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
24118 keep the workaround in place.
24119 - Remove the old 'fuzzy time' logic. It was supposed to be used for
24120 handling calculations where we have a known amount of clock skew and
24121 an allowed amount of unknown skew. But we only used it in three
24122 places, and we never adjusted the known/unknown skew values. This is
24123 still something we might want to do someday, but if we do, we'll
24124 want to do it differently.
24125 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
24126 None of the cases where we did this before were wrong, but by making
24127 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
24128 - Use GetTempDir to find the proper temporary directory location on
24129 Windows when generating temporary files for the unit tests. Patch by
24133 Changes in version 0.2.2.24-alpha - 2011-04-08
24134 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
24135 prevented Tor clients from effectively using "multihomed" bridges,
24136 that is, bridges that listen on multiple ports or IP addresses so users
24137 can continue to use some of their addresses even if others get blocked.
24140 - Fix a bug where bridge users who configure the non-canonical
24141 address of a bridge automatically switch to its canonical
24142 address. If a bridge listens at more than one address, it should be
24143 able to advertise those addresses independently and any non-blocked
24144 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
24146 - If you configured Tor to use bridge A, and then quit and
24147 configured Tor to use bridge B instead, it would happily continue
24148 to use bridge A if it's still reachable. While this behavior is
24149 a feature if your goal is connectivity, in some scenarios it's a
24150 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
24151 - Directory authorities now use data collected from their own
24152 uptime observations when choosing whether to assign the HSDir flag
24153 to relays, instead of trusting the uptime value the relay reports in
24154 its descriptor. This change helps prevent an attack where a small
24155 set of nodes with frequently-changing identity keys can blackhole
24156 a hidden service. (Only authorities need upgrade; others will be
24157 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
24160 - When we restart our relay, we might get a successful connection
24161 from the outside before we've started our reachability tests,
24162 triggering a warning: "ORPort found reachable, but I have no
24163 routerinfo yet. Failing to inform controller of success." This
24164 bug was harmless unless Tor is running under a controller
24165 like Vidalia, in which case the controller would never get a
24166 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
24168 - Make directory authorities more accurate at recording when
24169 relays that have failed several reachability tests became
24170 unreachable, so we can provide more accuracy at assigning Stable,
24171 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
24172 - Fix an issue that prevented static linking of libevent on
24173 some platforms (notably Linux). Fixes bug 2698; bugfix on
24174 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
24175 the --with-static-libevent configure option).
24176 - We now ask the other side of a stream (the client or the exit)
24177 for more data on that stream when the amount of queued data on
24178 that stream dips low enough. Previously, we wouldn't ask the
24179 other side for more data until either it sent us more data (which
24180 it wasn't supposed to do if it had exhausted its window!) or we
24181 had completely flushed all our queued data. This flow control fix
24182 should improve throughput. Fixes bug 2756; bugfix on the earliest
24183 released versions of Tor (svn commit r152).
24184 - Avoid a double-mark-for-free warning when failing to attach a
24185 transparent proxy connection. (We thought we had fixed this in
24186 0.2.2.23-alpha, but it turns out our fix was checking the wrong
24187 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
24188 bug) and 0.2.2.23-alpha (the incorrect fix).
24189 - When warning about missing zlib development packages during compile,
24190 give the correct package names. Bugfix on 0.2.0.1-alpha.
24193 - Directory authorities now log the source of a rejected POSTed v3
24194 networkstatus vote.
24195 - Make compilation with clang possible when using
24196 --enable-gcc-warnings by removing two warning options that clang
24197 hasn't implemented yet and by fixing a few warnings. Implements
24199 - When expiring circuits, use microsecond timers rather than
24200 one-second timers. This can avoid an unpleasant situation where a
24201 circuit is launched near the end of one second and expired right
24202 near the beginning of the next, and prevent fluctuations in circuit
24204 - Use computed circuit-build timeouts to decide when to launch
24205 parallel introduction circuits for hidden services. (Previously,
24206 we would retry after 15 seconds.)
24207 - Update to the April 1 2011 Maxmind GeoLite Country database.
24210 - Create the /var/run/tor directory on startup on OpenSUSE if it is
24211 not already created. Patch from Andreas Stieger. Fixes bug 2573.
24213 o Documentation changes:
24214 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
24215 - Resolve all doxygen warnings except those for missing documentation.
24217 - Add doxygen documentation for more functions, fields, and types.
24220 Changes in version 0.2.2.23-alpha - 2011-03-08
24221 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
24222 they restart they don't lose their bandwidth capacity estimate. This
24223 release also fixes a diverse set of user-facing bugs, ranging from
24224 relays overrunning their rate limiting to clients falsely warning about
24225 clock skew to bridge descriptor leaks by our bridge directory authority.
24228 - Stop sending a CLOCK_SKEW controller status event whenever
24229 we fetch directory information from a relay that has a wrong clock.
24230 Instead, only inform the controller when it's a trusted authority
24231 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
24232 the rest of bug 1074.
24233 - Fix an assert in parsing router descriptors containing IPv6
24234 addresses. This one took down the directory authorities when
24235 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
24236 - Make the bridge directory authority refuse to answer directory
24237 requests for "all" descriptors. It used to include bridge
24238 descriptors in its answer, which was a major information leak.
24239 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
24240 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
24241 Tor would ignore their RelayBandwidthBurst setting,
24242 potentially using more bandwidth than expected. Bugfix on
24243 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
24244 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
24245 hidserv" in her torrc. The 'hidserv' argument never controlled
24246 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
24249 - Relays now save observed peak bandwidth throughput rates to their
24250 state file (along with total usage, which was already saved)
24251 so that they can determine their correct estimated bandwidth on
24252 restart. Resolves bug 1863, where Tor relays would reset their
24253 estimated bandwidth to 0 after restarting.
24254 - Directory authorities now take changes in router IP address and
24255 ORPort into account when determining router stability. Previously,
24256 if a router changed its IP or ORPort, the authorities would not
24257 treat it as having any downtime for the purposes of stability
24258 calculation, whereas clients would experience downtime since the
24259 change could take a while to propagate to them. Resolves issue 1035.
24260 - Enable Address Space Layout Randomization (ASLR) and Data Execution
24261 Prevention (DEP) by default on Windows to make it harder for
24262 attackers to exploit vulnerabilities. Patch from John Brooks.
24264 o Minor bugfixes (on 0.2.1.x and earlier):
24265 - Fix a rare crash bug that could occur when a client was configured
24266 with a large number of bridges. Fixes bug 2629; bugfix on
24267 0.2.1.2-alpha. Bugfix by trac user "shitlei".
24268 - Avoid a double mark-for-free warning when failing to attach a
24269 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
24271 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
24272 found by "cypherpunks". This bug was introduced before the first
24273 Tor release, in svn commit r110.
24274 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
24275 don't mention them in the manpage. Fixes bug 2450; issue
24276 spotted by keb and G-Lo.
24277 - Fix a bug in bandwidth history state parsing that could have been
24278 triggered if a future version of Tor ever changed the timing
24279 granularity at which bandwidth history is measured. Bugfix on
24280 Tor 0.1.1.11-alpha.
24281 - When a relay decides that its DNS is too broken for it to serve
24282 as an exit server, it advertised itself as a non-exit, but
24283 continued to act as an exit. This could create accidental
24284 partitioning opportunities for users. Instead, if a relay is
24285 going to advertise reject *:* as its exit policy, it should
24286 really act with exit policy "reject *:*". Fixes bug 2366.
24287 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
24288 - In the special case where you configure a public exit relay as your
24289 bridge, Tor would be willing to use that exit relay as the last
24290 hop in your circuit as well. Now we fail that circuit instead.
24291 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
24292 - Fix a bug with our locking implementation on Windows that couldn't
24293 correctly detect when a file was already locked. Fixes bug 2504,
24294 bugfix on 0.2.1.6-alpha.
24295 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
24296 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
24298 - Set target port in get_interface_address6() correctly. Bugfix
24299 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
24300 - Directory authorities are now more robust to hops back in time
24301 when calculating router stability. Previously, if a run of uptime
24302 or downtime appeared to be negative, the calculation could give
24303 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
24305 - Fix an assert that got triggered when using the TestingTorNetwork
24306 configuration option and then issuing a GETINFO config-text control
24307 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
24309 o Minor bugfixes (on 0.2.2.x):
24310 - Clients should not weight BadExit nodes as Exits in their node
24311 selection. Similarly, directory authorities should not count BadExit
24312 bandwidth as Exit bandwidth when computing bandwidth-weights.
24313 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
24314 - Correctly clear our dir_read/dir_write history when there is an
24315 error parsing any bw history value from the state file. Bugfix on
24316 Tor 0.2.2.15-alpha.
24317 - Resolve a bug in verifying signatures of directory objects
24318 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
24319 Fixes bug 2409. Found by "piebeer".
24320 - Bridge authorities no longer crash on SIGHUP when they try to
24321 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
24325 - Log less aggressively about circuit timeout changes, and improve
24326 some other circuit timeout messages. Resolves bug 2004.
24327 - Log a little more clearly about the times at which we're no longer
24328 accepting new connections. Resolves bug 2181.
24329 - Reject attempts at the client side to open connections to private
24330 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
24331 a randomly chosen exit node. Attempts to do so are always
24332 ill-defined, generally prevented by exit policies, and usually
24333 in error. This will also help to detect loops in transparent
24334 proxy configurations. You can disable this feature by setting
24335 "ClientRejectInternalAddresses 0" in your torrc.
24336 - Always treat failure to allocate an RSA key as an unrecoverable
24338 - Update to the March 1 2011 Maxmind GeoLite Country database.
24340 o Minor features (log subsystem):
24341 - Add documentation for configuring logging at different severities in
24342 different log domains. We've had this feature since 0.2.1.1-alpha,
24343 but for some reason it never made it into the manpage. Fixes
24345 - Make it simpler to specify "All log domains except for A and B".
24346 Previously you needed to say "[*,~A,~B]". Now you can just say
24348 - Add a "LogMessageDomains 1" option to include the domains of log
24349 messages along with the messages. Without this, there's no way
24350 to use log domains without reading the source or doing a lot
24353 o Packaging changes:
24354 - Stop shipping the Tor specs files and development proposal documents
24355 in the tarball. They are now in a separate git repository at
24356 git://git.torproject.org/torspec.git
24359 Changes in version 0.2.1.30 - 2011-02-23
24360 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
24361 change is a slight tweak to Tor's TLS handshake that makes relays
24362 and bridges that run this new version reachable from Iran again.
24363 We don't expect this tweak will win the arms race long-term, but it
24364 buys us time until we roll out a better solution.
24367 - Stop sending a CLOCK_SKEW controller status event whenever
24368 we fetch directory information from a relay that has a wrong clock.
24369 Instead, only inform the controller when it's a trusted authority
24370 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
24371 the rest of bug 1074.
24372 - Fix a bounds-checking error that could allow an attacker to
24373 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
24374 Found by "piebeer".
24375 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
24376 Tor would ignore their RelayBandwidthBurst setting,
24377 potentially using more bandwidth than expected. Bugfix on
24378 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
24379 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
24380 hidserv" in her torrc. The 'hidserv' argument never controlled
24381 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
24384 - Adjust our TLS Diffie-Hellman parameters to match those used by
24386 - Update to the February 1 2011 Maxmind GeoLite Country database.
24389 - Check for and reject overly long directory certificates and
24390 directory tokens before they have a chance to hit any assertions.
24391 Bugfix on 0.2.1.28. Found by "doorss".
24392 - Bring the logic that gathers routerinfos and assesses the
24393 acceptability of circuits into line. This prevents a Tor OP from
24394 getting locked in a cycle of choosing its local OR as an exit for a
24395 path (due to a .exit request) and then rejecting the circuit because
24396 its OR is not listed yet. It also prevents Tor clients from using an
24397 OR running in the same instance as an exit (due to a .exit request)
24398 if the OR does not meet the same requirements expected of an OR
24399 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
24401 o Packaging changes:
24402 - Stop shipping the Tor specs files and development proposal documents
24403 in the tarball. They are now in a separate git repository at
24404 git://git.torproject.org/torspec.git
24405 - Do not include Git version tags as though they are SVN tags when
24406 generating a tarball from inside a repository that has switched
24407 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
24410 Changes in version 0.2.2.22-alpha - 2011-01-25
24411 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
24412 main other change is a slight tweak to Tor's TLS handshake that makes
24413 relays and bridges that run this new version reachable from Iran again.
24414 We don't expect this tweak will win the arms race long-term, but it
24415 will buy us a bit more time until we roll out a better solution.
24418 - Fix a bounds-checking error that could allow an attacker to
24419 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
24420 Found by "piebeer".
24421 - Don't assert when changing from bridge to relay or vice versa
24422 via the controller. The assert happened because we didn't properly
24423 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
24424 bug 2433. Reported by bastik.
24427 - Adjust our TLS Diffie-Hellman parameters to match those used by
24429 - Provide a log message stating which geoip file we're parsing
24430 instead of just stating that we're parsing the geoip file.
24431 Implements ticket 2432.
24434 - Check for and reject overly long directory certificates and
24435 directory tokens before they have a chance to hit any assertions.
24436 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
24439 Changes in version 0.2.2.21-alpha - 2011-01-15
24440 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
24441 continues our recent code security audit work. The main fix resolves
24442 a remote heap overflow vulnerability that can allow remote code
24443 execution (CVE-2011-0427). Other fixes address a variety of assert
24444 and crash bugs, most of which we think are hard to exploit remotely.
24446 o Major bugfixes (security), also included in 0.2.1.29:
24447 - Fix a heap overflow bug where an adversary could cause heap
24448 corruption. This bug probably allows remote code execution
24449 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
24451 - Prevent a denial-of-service attack by disallowing any
24452 zlib-compressed data whose compression factor is implausibly
24453 high. Fixes part of bug 2324; reported by "doorss".
24454 - Zero out a few more keys in memory before freeing them. Fixes
24455 bug 2384 and part of bug 2385. These key instances found by
24456 "cypherpunks", based on Andrew Case's report about being able
24457 to find sensitive data in Tor's memory space if you have enough
24458 permissions. Bugfix on 0.0.2pre9.
24460 o Major bugfixes (crashes), also included in 0.2.1.29:
24461 - Prevent calls to Libevent from inside Libevent log handlers.
24462 This had potential to cause a nasty set of crashes, especially
24463 if running Libevent with debug logging enabled, and running
24464 Tor with a controller watching for low-severity log messages.
24465 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
24466 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
24467 underflow errors there too. Fixes the other part of bug 2324.
24468 - Fix a bug where we would assert if we ever had a
24469 cached-descriptors.new file (or another file read directly into
24470 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
24471 on 0.2.1.25. Found by doorss.
24472 - Fix some potential asserts and parsing issues with grossly
24473 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
24476 o Minor bugfixes (other), also included in 0.2.1.29:
24477 - Fix a bug with handling misformed replies to reverse DNS lookup
24478 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
24479 bug reported by doorss.
24480 - Fix compilation on mingw when a pthreads compatibility library
24481 has been installed. (We don't want to use it, so we shouldn't
24482 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
24483 - Fix a bug where we would declare that we had run out of virtual
24484 addresses when the address space was only half-exhausted. Bugfix
24486 - Correctly handle the case where AutomapHostsOnResolve is set but
24487 no virtual addresses are available. Fixes bug 2328; bugfix on
24488 0.1.2.1-alpha. Bug found by doorss.
24489 - Correctly handle wrapping around when we run out of virtual
24490 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
24492 o Minor features, also included in 0.2.1.29:
24493 - Update to the January 1 2011 Maxmind GeoLite Country database.
24494 - Introduce output size checks on all of our decryption functions.
24496 o Build changes, also included in 0.2.1.29:
24497 - Tor does not build packages correctly with Automake 1.6 and earlier;
24498 added a check to Makefile.am to make sure that we're building with
24499 Automake 1.7 or later.
24500 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
24501 because we built it with a too-old version of automake. Thus that
24502 release broke ./configure --enable-openbsd-malloc, which is popular
24503 among really fast exit relays on Linux.
24505 o Major bugfixes, new in 0.2.2.21-alpha:
24506 - Prevent crash/heap corruption when the cbtnummodes consensus
24507 parameter is set to 0 or large values. Fixes bug 2317; bugfix
24510 o Major features, new in 0.2.2.21-alpha:
24511 - Introduce minimum/maximum values that clients will believe
24512 from the consensus. Now we'll have a better chance to avoid crashes
24513 or worse when a consensus param has a weird value.
24515 o Minor features, new in 0.2.2.21-alpha:
24516 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
24517 used on bridges, and it makes bridge scanning somewhat easier.
24518 - If writing the state file to disk fails, wait up to an hour before
24519 retrying again, rather than trying again each second. Fixes bug
24520 2346; bugfix on Tor 0.1.1.3-alpha.
24521 - Make Libevent log messages get delivered to controllers later,
24522 and not from inside the Libevent log handler. This prevents unsafe
24523 reentrant Libevent calls while still letting the log messages
24525 - Detect platforms that brokenly use a signed size_t, and refuse to
24526 build there. Found and analyzed by doorss and rransom.
24527 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
24530 o Minor bugfixes, new in 0.2.2.21-alpha:
24531 - Handle SOCKS messages longer than 128 bytes long correctly, rather
24532 than waiting forever for them to finish. Fixes bug 2330; bugfix
24533 on 0.2.0.16-alpha. Found by doorss.
24534 - Add assertions to check for overflow in arguments to
24535 base32_encode() and base32_decode(); fix a signed-unsigned
24536 comparison there too. These bugs are not actually reachable in Tor,
24537 but it's good to prevent future errors too. Found by doorss.
24538 - Correctly detect failures to create DNS requests when using Libevent
24539 versions before v2. (Before Libevent 2, we used our own evdns
24540 implementation. Its return values for Libevent's evdns_resolve_*()
24541 functions are not consistent with those from Libevent.) Fixes bug
24542 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
24544 o Documentation, new in 0.2.2.21-alpha:
24545 - Document the default socks host and port (127.0.0.1:9050) for
24549 Changes in version 0.2.1.29 - 2011-01-15
24550 Tor 0.2.1.29 continues our recent code security audit work. The main
24551 fix resolves a remote heap overflow vulnerability that can allow remote
24552 code execution. Other fixes address a variety of assert and crash bugs,
24553 most of which we think are hard to exploit remotely.
24555 o Major bugfixes (security):
24556 - Fix a heap overflow bug where an adversary could cause heap
24557 corruption. This bug probably allows remote code execution
24558 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
24560 - Prevent a denial-of-service attack by disallowing any
24561 zlib-compressed data whose compression factor is implausibly
24562 high. Fixes part of bug 2324; reported by "doorss".
24563 - Zero out a few more keys in memory before freeing them. Fixes
24564 bug 2384 and part of bug 2385. These key instances found by
24565 "cypherpunks", based on Andrew Case's report about being able
24566 to find sensitive data in Tor's memory space if you have enough
24567 permissions. Bugfix on 0.0.2pre9.
24569 o Major bugfixes (crashes):
24570 - Prevent calls to Libevent from inside Libevent log handlers.
24571 This had potential to cause a nasty set of crashes, especially
24572 if running Libevent with debug logging enabled, and running
24573 Tor with a controller watching for low-severity log messages.
24574 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
24575 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
24576 underflow errors there too. Fixes the other part of bug 2324.
24577 - Fix a bug where we would assert if we ever had a
24578 cached-descriptors.new file (or another file read directly into
24579 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
24580 on 0.2.1.25. Found by doorss.
24581 - Fix some potential asserts and parsing issues with grossly
24582 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
24585 o Minor bugfixes (other):
24586 - Fix a bug with handling misformed replies to reverse DNS lookup
24587 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
24588 bug reported by doorss.
24589 - Fix compilation on mingw when a pthreads compatibility library
24590 has been installed. (We don't want to use it, so we shouldn't
24591 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
24592 - Fix a bug where we would declare that we had run out of virtual
24593 addresses when the address space was only half-exhausted. Bugfix
24595 - Correctly handle the case where AutomapHostsOnResolve is set but
24596 no virtual addresses are available. Fixes bug 2328; bugfix on
24597 0.1.2.1-alpha. Bug found by doorss.
24598 - Correctly handle wrapping around to when we run out of virtual
24599 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
24600 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
24601 because we built it with a too-old version of automake. Thus that
24602 release broke ./configure --enable-openbsd-malloc, which is popular
24603 among really fast exit relays on Linux.
24606 - Update to the January 1 2011 Maxmind GeoLite Country database.
24607 - Introduce output size checks on all of our decryption functions.
24610 - Tor does not build packages correctly with Automake 1.6 and earlier;
24611 added a check to Makefile.am to make sure that we're building with
24612 Automake 1.7 or later.
24615 Changes in version 0.2.2.20-alpha - 2010-12-17
24616 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
24617 exploitable bugs. We also fix a variety of other significant bugs,
24618 change the IP address for one of our directory authorities, and update
24619 the minimum version that Tor relays must run to join the network.
24622 - Fix a remotely exploitable bug that could be used to crash instances
24623 of Tor remotely by overflowing on the heap. Remote-code execution
24624 hasn't been confirmed, but can't be ruled out. Everyone should
24625 upgrade. Bugfix on the 0.1.1 series and later.
24626 - Fix a bug that could break accounting on 64-bit systems with large
24627 time_t values, making them hibernate for impossibly long intervals.
24628 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
24629 - Fix a logic error in directory_fetches_from_authorities() that
24630 would cause all _non_-exits refusing single-hop-like circuits
24631 to fetch from authorities, when we wanted to have _exits_ fetch
24632 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
24634 - Fix a stream fairness bug that would cause newer streams on a given
24635 circuit to get preference when reading bytes from the origin or
24636 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
24637 introduced before the first Tor release, in svn revision r152.
24639 o Directory authority changes:
24640 - Change IP address and ports for gabelmoo (v3 directory authority).
24643 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
24644 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
24645 - Fix an off-by-one error in calculating some controller command
24646 argument lengths. Fortunately, this mistake is harmless since
24647 the controller code does redundant NUL termination too. Found by
24648 boboper. Bugfix on 0.1.1.1-alpha.
24649 - Do not dereference NULL if a bridge fails to build its
24650 extra-info descriptor. Found by an anonymous commenter on
24651 Trac. Bugfix on 0.2.2.19-alpha.
24654 - Update to the December 1 2010 Maxmind GeoLite Country database.
24655 - Directory authorities now reject relays running any versions of
24656 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
24657 known bugs that keep RELAY_EARLY cells from working on rendezvous
24658 circuits. Followup to fix for bug 2081.
24659 - Directory authorities now reject relays running any version of Tor
24660 older than 0.2.0.26-rc. That version is the earliest that fetches
24661 current directory information correctly. Fixes bug 2156.
24662 - Report only the top 10 ports in exit-port stats in order not to
24663 exceed the maximum extra-info descriptor length of 50 KB. Implements
24667 Changes in version 0.2.1.28 - 2010-12-17
24668 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
24669 exploitable bugs. We also took this opportunity to change the IP address
24670 for one of our directory authorities, and to update the geoip database
24674 - Fix a remotely exploitable bug that could be used to crash instances
24675 of Tor remotely by overflowing on the heap. Remote-code execution
24676 hasn't been confirmed, but can't be ruled out. Everyone should
24677 upgrade. Bugfix on the 0.1.1 series and later.
24679 o Directory authority changes:
24680 - Change IP address and ports for gabelmoo (v3 directory authority).
24683 - Update to the December 1 2010 Maxmind GeoLite Country database.
24686 Changes in version 0.2.1.27 - 2010-11-23
24687 Yet another OpenSSL security patch broke its compatibility with Tor:
24688 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
24689 also took this opportunity to fix several crash bugs, integrate a new
24690 directory authority, and update the bundled GeoIP database.
24693 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
24694 No longer set the tlsext_host_name extension on server SSL objects;
24695 but continue to set it on client SSL objects. Our goal in setting
24696 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
24697 bugfix on 0.2.1.1-alpha.
24698 - Do not log messages to the controller while shrinking buffer
24699 freelists. Doing so would sometimes make the controller connection
24700 try to allocate a buffer chunk, which would mess up the internals
24701 of the freelist and cause an assertion failure. Fixes bug 1125;
24702 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
24703 - Learn our external IP address when we're a relay or bridge, even if
24704 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
24705 where we introduced bridge relays that don't need to publish to
24706 be useful. Fixes bug 2050.
24707 - Do even more to reject (and not just ignore) annotations on
24708 router descriptors received anywhere but from the cache. Previously
24709 we would ignore such annotations at first, but cache them to disk
24710 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
24711 - When you're using bridges and your network goes away and your
24712 bridges get marked as down, recover when you attempt a new socks
24713 connection (if the network is back), rather than waiting up to an
24714 hour to try fetching new descriptors for your bridges. Bugfix on
24715 0.2.0.3-alpha; fixes bug 1981.
24718 - Move to the November 2010 Maxmind GeoLite country db (rather
24719 than the June 2009 ip-to-country GeoIP db) for our statistics that
24720 count how many users relays are seeing from each country. Now we'll
24721 have more accurate data, especially for many African countries.
24723 o New directory authorities:
24724 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
24728 - Fix an assertion failure that could occur in directory caches or
24729 bridge users when using a very short voting interval on a testing
24730 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
24732 - Enforce multiplicity rules when parsing annotations. Bugfix on
24733 0.2.0.8-alpha. Found by piebeer.
24734 - Allow handshaking OR connections to take a full KeepalivePeriod
24735 seconds to handshake. Previously, we would close them after
24736 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
24737 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
24739 - When building with --enable-gcc-warnings on OpenBSD, disable
24740 warnings in system headers. This makes --enable-gcc-warnings
24741 pass on OpenBSD 4.8.
24744 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
24745 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
24746 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
24747 Servers can start sending this code when enough clients recognize
24748 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
24749 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
24750 Patch from mingw-san.
24753 - Remove the old debian/ directory from the main Tor distribution.
24754 The official Tor-for-debian git repository lives at the URL
24755 https://git.torproject.org/debian/tor.git
24756 - Stop shipping the old doc/website/ directory in the tarball. We
24757 changed the website format in late 2010, and what we shipped in
24758 0.2.1.26 really wasn't that useful anyway.
24761 Changes in version 0.2.2.19-alpha - 2010-11-22
24762 Yet another OpenSSL security patch broke its compatibility with Tor:
24763 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
24766 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
24767 No longer set the tlsext_host_name extension on server SSL objects;
24768 but continue to set it on client SSL objects. Our goal in setting
24769 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
24770 bugfix on 0.2.1.1-alpha.
24773 - Try harder not to exceed the maximum length of 50 KB when writing
24774 statistics to extra-info descriptors. This bug was triggered by very
24775 fast relays reporting exit-port, entry, and dirreq statistics.
24776 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
24777 - Publish a router descriptor even if generating an extra-info
24778 descriptor fails. Previously we would not publish a router
24779 descriptor without an extra-info descriptor; this can cause fast
24780 exit relays collecting exit-port statistics to drop from the
24781 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
24784 Changes in version 0.2.2.18-alpha - 2010-11-16
24785 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
24786 us lately, makes unpublished bridge relays able to detect their IP
24787 address, and fixes a wide variety of other bugs to get us much closer
24788 to a stable release.
24791 - Do even more to reject (and not just ignore) annotations on
24792 router descriptors received anywhere but from the cache. Previously
24793 we would ignore such annotations at first, but cache them to disk
24794 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
24795 - Do not log messages to the controller while shrinking buffer
24796 freelists. Doing so would sometimes make the controller connection
24797 try to allocate a buffer chunk, which would mess up the internals
24798 of the freelist and cause an assertion failure. Fixes bug 1125;
24799 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
24800 - Learn our external IP address when we're a relay or bridge, even if
24801 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
24802 where we introduced bridge relays that don't need to publish to
24803 be useful. Fixes bug 2050.
24804 - Maintain separate TLS contexts and certificates for incoming and
24805 outgoing connections in bridge relays. Previously we would use the
24806 same TLS contexts and certs for incoming and outgoing connections.
24807 Bugfix on 0.2.0.3-alpha; addresses bug 988.
24808 - Maintain separate identity keys for incoming and outgoing TLS
24809 contexts in bridge relays. Previously we would use the same
24810 identity keys for incoming and outgoing TLS contexts. Bugfix on
24811 0.2.0.3-alpha; addresses the other half of bug 988.
24812 - Avoid an assertion failure when we as an authority receive a
24813 duplicate upload of a router descriptor that we already have,
24814 but which we previously considered an obsolete descriptor.
24815 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
24816 - Avoid a crash bug triggered by looking at a dangling pointer while
24817 setting the network status consensus. Found by Robert Ransom.
24818 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
24819 - Fix a logic error where servers that _didn't_ act as exits would
24820 try to keep their server lists more aggressively up to date than
24821 exits, when it was supposed to be the other way around. Bugfix
24824 o Minor bugfixes (on Tor 0.2.1.x and earlier):
24825 - When we're trying to guess whether we know our IP address as
24826 a relay, we would log various ways that we failed to guess
24827 our address, but never log that we ended up guessing it
24828 successfully. Now add a log line to help confused and anxious
24829 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
24830 - Bring the logic that gathers routerinfos and assesses the
24831 acceptability of circuits into line. This prevents a Tor OP from
24832 getting locked in a cycle of choosing its local OR as an exit for a
24833 path (due to a .exit request) and then rejecting the circuit because
24834 its OR is not listed yet. It also prevents Tor clients from using an
24835 OR running in the same instance as an exit (due to a .exit request)
24836 if the OR does not meet the same requirements expected of an OR
24837 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
24838 - Correctly describe errors that occur when generating a TLS object.
24839 Previously we would attribute them to a failure while generating a
24840 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
24842 - Enforce multiplicity rules when parsing annotations. Bugfix on
24843 0.2.0.8-alpha. Found by piebeer.
24844 - Fix warnings that newer versions of autoconf produced during
24845 ./autogen.sh. These warnings appear to be harmless in our case,
24846 but they were extremely verbose. Fixes bug 2020.
24848 o Minor bugfixes (on Tor 0.2.2.x):
24849 - Enable protection of small arrays whenever we build with gcc
24850 hardening features, not only when also building with warnings
24851 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
24854 - Make hidden services work better in private Tor networks by not
24855 requiring any uptime to join the hidden service descriptor
24856 DHT. Implements ticket 2088.
24857 - Rate-limit the "your application is giving Tor only an IP address"
24858 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
24859 - When AllowSingleHopExits is set, print a warning to explain to the
24860 relay operator why most clients are avoiding her relay.
24861 - Update to the November 1 2010 Maxmind GeoLite Country database.
24863 o Code simplifications and refactoring:
24864 - When we fixed bug 1038 we had to put in a restriction not to send
24865 RELAY_EARLY cells on rend circuits. This was necessary as long
24866 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
24867 active. Now remove this obsolete check. Resolves bug 2081.
24868 - Some options used different conventions for uppercasing of acronyms
24869 when comparing manpage and source. Fix those in favor of the
24870 manpage, as it makes sense to capitalize acronyms.
24871 - Remove the torrc.complete file. It hasn't been kept up to date
24872 and users will have better luck checking out the manpage.
24873 - Remove the obsolete "NoPublish" option; it has been flagged
24874 as obsolete and has produced a warning since 0.1.1.18-rc.
24875 - Remove everything related to building the expert bundle for OS X.
24876 It has confused many users, doesn't work right on OS X 10.6,
24877 and is hard to get rid of once installed. Resolves bug 1274.
24880 Changes in version 0.2.2.17-alpha - 2010-09-30
24881 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
24882 to use one-hop circuits (which can put the exit relays at higher risk,
24883 plus unbalance the network); fixes a big bug in bandwidth accounting
24884 for relays that want to limit their monthly bandwidth use; fixes a
24885 big pile of bugs in how clients tolerate temporary network failure;
24886 and makes our adaptive circuit build timeout feature (which improves
24887 client performance if your network is fast while not breaking things
24888 if your network is slow) better handle bad networks.
24891 - Exit relays now try harder to block exit attempts from unknown
24892 relays, to make it harder for people to use them as one-hop proxies
24893 a la tortunnel. Controlled by the refuseunknownexits consensus
24894 parameter (currently enabled), or you can override it on your
24895 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
24897 o Major bugfixes (0.2.1.x and earlier):
24898 - Fix a bug in bandwidth accounting that could make us use twice
24899 the intended bandwidth when our interval start changes due to
24900 daylight saving time. Now we tolerate skew in stored vs computed
24901 interval starts: if the start of the period changes by no more than
24902 50% of the period's duration, we remember bytes that we transferred
24903 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
24904 - Always search the Windows system directory for system DLLs, and
24905 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
24906 - When you're using bridges and your network goes away and your
24907 bridges get marked as down, recover when you attempt a new socks
24908 connection (if the network is back), rather than waiting up to an
24909 hour to try fetching new descriptors for your bridges. Bugfix on
24910 0.2.0.3-alpha; fixes bug 1981.
24912 o Major bugfixes (on 0.2.2.x):
24913 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
24915 - Fix a segfault that could happen when operating a bridge relay with
24916 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
24917 - The consensus bandwidth-weights (used by clients to choose fast
24918 relays) entered an unexpected edge case in September where
24919 Exits were much scarcer than Guards, resulting in bad weight
24920 recommendations. Now we compute them using new constraints that
24921 should succeed in all cases. Also alter directory authorities to
24922 not include the bandwidth-weights line if they fail to produce
24923 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
24924 - When weighting bridges during path selection, we used to trust
24925 the bandwidths they provided in their descriptor, only capping them
24926 at 10MB/s. This turned out to be problematic for two reasons:
24927 Bridges could claim to handle a lot more traffic then they
24928 actually would, thus making more clients pick them and have a
24929 pretty effective DoS attack. The other issue is that new bridges
24930 that might not have a good estimate for their bw capacity yet
24931 would not get used at all unless no other bridges are available
24932 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
24934 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
24935 - Ignore cannibalized circuits when recording circuit build times.
24936 This should provide for a minor performance improvement for hidden
24937 service users using 0.2.2.14-alpha, and should remove two spurious
24938 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
24939 - Simplify the logic that causes us to decide if the network is
24940 unavailable for purposes of recording circuit build times. If we
24941 receive no cells whatsoever for the entire duration of a circuit's
24942 full measured lifetime, the network is probably down. Also ignore
24943 one-hop directory fetching circuit timeouts when calculating our
24944 circuit build times. These changes should hopefully reduce the
24945 cases where we see ridiculous circuit build timeouts for people
24946 with spotty wireless connections. Fixes part of bug 1772; bugfix
24948 - Prevent the circuit build timeout from becoming larger than
24949 the maximum build time we have ever seen. Also, prevent the time
24950 period for measurement circuits from becoming larger than twice that
24951 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
24954 - When we run out of directory information such that we can't build
24955 circuits, but then get enough that we can build circuits, log when
24956 we actually construct a circuit, so the user has a better chance of
24957 knowing what's going on. Fixes bug 1362.
24958 - Be more generous with how much bandwidth we'd use up (with
24959 accounting enabled) before entering "soft hibernation". Previously,
24960 we'd refuse new connections and circuits once we'd used up 95% of
24961 our allotment. Now, we use up 95% of our allotment, AND make sure
24962 that we have no more than 500MB (or 3 hours of expected traffic,
24963 whichever is lower) remaining before we enter soft hibernation.
24964 - If we've configured EntryNodes and our network goes away and/or all
24965 our entrynodes get marked down, optimistically retry them all when
24966 a new socks application request appears. Fixes bug 1882.
24967 - Add some more defensive programming for architectures that can't
24968 handle unaligned integer accesses. We don't know of any actual bugs
24969 right now, but that's the best time to fix them. Fixes bug 1943.
24970 - Support line continuations in the torrc config file. If a line
24971 ends with a single backslash character, the newline is ignored, and
24972 the configuration value is treated as continuing on the next line.
24975 o Minor bugfixes (on 0.2.1.x and earlier):
24976 - For bandwidth accounting, calculate our expected bandwidth rate
24977 based on the time during which we were active and not in
24978 soft-hibernation during the last interval. Previously, we were
24979 also considering the time spent in soft-hibernation. If this
24980 was a long time, we would wind up underestimating our bandwidth
24981 by a lot, and skewing our wakeup time towards the start of the
24982 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
24984 o Minor bugfixes (on 0.2.2.x):
24985 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
24986 which were disabled by the circuit build timeout changes in
24987 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
24988 - Make sure we don't warn about missing bandwidth weights when
24989 choosing bridges or other relays not in the consensus. Bugfix on
24990 0.2.2.10-alpha; fixes bug 1805.
24991 - In our logs, do not double-report signatures from unrecognized
24992 authorities both as "from unknown authority" and "not
24993 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
24996 Changes in version 0.2.2.16-alpha - 2010-09-17
24997 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
24998 evident at exit relays), and also continues to resolve all the little
24999 bugs that have been filling up trac lately.
25001 o Major bugfixes (stream-level fairness):
25002 - When receiving a circuit-level SENDME for a blocked circuit, try
25003 to package cells fairly from all the streams that had previously
25004 been blocked on that circuit. Previously, we had started with the
25005 oldest stream, and allowed each stream to potentially exhaust
25006 the circuit's package window. This gave older streams on any
25007 given circuit priority over newer ones. Fixes bug 1937. Detected
25008 originally by Camilo Viecco. This bug was introduced before the
25009 first Tor release, in svn commit r152: it is the new winner of
25010 the longest-lived bug prize.
25011 - When the exit relay got a circuit-level sendme cell, it started
25012 reading on the exit streams, even if had 500 cells queued in the
25013 circuit queue already, so the circuit queue just grew and grew in
25014 some cases. We fix this by not re-enabling reading on receipt of a
25015 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
25016 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
25018 - Newly created streams were allowed to read cells onto circuits,
25019 even if the circuit's cell queue was blocked and waiting to drain.
25020 This created potential unfairness, as older streams would be
25021 blocked, but newer streams would gladly fill the queue completely.
25022 We add code to detect this situation and prevent any stream from
25023 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
25027 - Update to the September 1 2010 Maxmind GeoLite Country database.
25028 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
25029 not. This would lead to a cookie that is still not group readable.
25030 Closes bug 1843. Suggested by katmagic.
25031 - When logging a rate-limited warning, we now mention how many messages
25032 got suppressed since the last warning.
25033 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
25034 do individual connection-level rate limiting of clients. The torrc
25035 config options with the same names trump the consensus params, if
25036 both are present. Replaces the old "bwconnrate" and "bwconnburst"
25037 consensus params which were broken from 0.2.2.7-alpha through
25038 0.2.2.14-alpha. Closes bug 1947.
25039 - When a router changes IP address or port, authorities now launch
25040 a new reachability test for it. Implements ticket 1899.
25041 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
25042 2 no signature, 4 required" messages about consensus signatures
25043 easier to read, and make sure they get logged at the same severity
25044 as the messages explaining which keys are which. Fixes bug 1290.
25045 - Don't warn when we have a consensus that we can't verify because
25046 of missing certificates, unless those certificates are ones
25047 that we have been trying and failing to download. Fixes bug 1145.
25048 - If you configure your bridge with a known identity fingerprint,
25049 and the bridge authority is unreachable (as it is in at least
25050 one country now), fall back to directly requesting the descriptor
25051 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
25053 - When building with --enable-gcc-warnings on OpenBSD, disable
25054 warnings in system headers. This makes --enable-gcc-warnings
25055 pass on OpenBSD 4.8.
25057 o Minor bugfixes (on 0.2.1.x and earlier):
25058 - Authorities will now attempt to download consensuses if their
25059 own efforts to make a live consensus have failed. This change
25060 means authorities that restart will fetch a valid consensus, and
25061 it means authorities that didn't agree with the current consensus
25062 will still fetch and serve it if it has enough signatures. Bugfix
25063 on 0.2.0.9-alpha; fixes bug 1300.
25064 - Ensure DNS requests launched by "RESOLVE" commands from the
25065 controller respect the __LeaveStreamsUnattached setconf options. The
25066 same goes for requests launched via DNSPort or transparent
25067 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
25068 - Allow handshaking OR connections to take a full KeepalivePeriod
25069 seconds to handshake. Previously, we would close them after
25070 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
25071 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
25073 - Rate-limit "Failed to hand off onionskin" warnings.
25074 - Never relay a cell for a circuit we have already destroyed.
25075 Between marking a circuit as closeable and finally closing it,
25076 it may have been possible for a few queued cells to get relayed,
25077 even though they would have been immediately dropped by the next
25078 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
25079 - Never queue a cell for a circuit that's already been marked
25081 - Never vote for a server as "Running" if we have a descriptor for
25082 it claiming to be hibernating, and that descriptor was published
25083 more recently than our last contact with the server. Bugfix on
25084 0.2.0.3-alpha; fixes bug 911.
25085 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
25088 o Minor bugfixes (on 0.2.2.x):
25089 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
25090 down if a directory fetch fails and you've configured either
25091 bridges or EntryNodes. The intent was to mark the relay as down
25092 _unless_ you're using bridges or EntryNodes, since if you are
25093 then you could quickly run out of entry points.
25094 - Fix the Windows directory-listing code. A bug introduced in
25095 0.2.2.14-alpha could make Windows directory servers forget to load
25096 some of their cached v2 networkstatus files.
25097 - Really allow clients to use relays as bridges. Fixes bug 1776;
25098 bugfix on 0.2.2.15-alpha.
25099 - Demote a warn to info that happens when the CellStatistics option
25100 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
25101 Reported by Moritz Bartl.
25102 - On Windows, build correctly either with or without Unicode support.
25103 This is necessary so that Tor can support fringe platforms like
25104 Windows 98 (which has no Unicode), or Windows CE (which has no
25105 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
25108 - Add a unit test for cross-platform directory-listing code.
25111 Changes in version 0.2.2.15-alpha - 2010-08-18
25112 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
25113 fixes a variety of other bugs that were preventing performance
25114 experiments from moving forward, fixes several bothersome memory leaks,
25115 and generally closes a lot of smaller bugs that have been filling up
25119 - Stop assigning the HSDir flag to relays that disable their
25120 DirPort (and thus will refuse to answer directory requests). This
25121 fix should dramatically improve the reachability of hidden services:
25122 hidden services and hidden service clients pick six HSDir relays
25123 to store and retrieve the hidden service descriptor, and currently
25124 about half of the HSDir relays will refuse to work. Bugfix on
25125 0.2.0.10-alpha; fixes part of bug 1693.
25126 - The PerConnBWRate and Burst config options, along with the
25127 bwconnrate and bwconnburst consensus params, initialized each conn's
25128 token bucket values only when the connection is established. Now we
25129 update them if the config options change, and update them every time
25130 we get a new consensus. Otherwise we can encounter an ugly edge
25131 case where we initialize an OR conn to client-level bandwidth,
25132 but then later the relay joins the consensus and we leave it
25133 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
25134 - Fix a regression that caused Tor to rebind its ports if it receives
25135 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
25138 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
25139 should give us approximately 40-50% more Guard-flagged nodes,
25140 improving the anonymity the Tor network can provide and also
25141 decreasing the dropoff in throughput that relays experience when
25142 they first get the Guard flag.
25143 - Allow enabling or disabling the *Statistics config options while
25147 - Update to the August 1 2010 Maxmind GeoLite Country database.
25148 - Have the controller interface give a more useful message than
25149 "Internal Error" in response to failed GETINFO requests.
25150 - Warn when the same option is provided more than once in a torrc
25151 file, on the command line, or in a single SETCONF statement, and
25152 the option is one that only accepts a single line. Closes bug 1384.
25153 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
25154 Patch from mingw-san.
25155 - Add support for the country code "{??}" in torrc options like
25156 ExcludeNodes, to indicate all routers of unknown country. Closes
25158 - Relays report the number of bytes spent on answering directory
25159 requests in extra-info descriptors similar to {read,write}-history.
25160 Implements enhancement 1790.
25162 o Minor bugfixes (on 0.2.1.x and earlier):
25163 - Complain if PublishServerDescriptor is given multiple arguments that
25164 include 0 or 1. This configuration will be rejected in the future.
25165 Bugfix on 0.2.0.1-alpha; closes bug 1107.
25166 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
25167 Bugfix on 0.2.0.13-alpha; closes bug 928.
25168 - Change "Application request when we're believed to be offline."
25169 notice to "Application request when we haven't used client
25170 functionality lately.", to clarify that it's not an error. Bugfix
25171 on 0.0.9.3; fixes bug 1222.
25172 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
25173 would return "551 Internal error" rather than "552 Unrecognized key
25174 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
25175 - Users can't configure a regular relay to be their bridge. It didn't
25176 work because when Tor fetched the bridge descriptor, it found
25177 that it already had it, and didn't realize that the purpose of the
25178 descriptor had changed. Now we replace routers with a purpose other
25179 than bridge with bridge descriptors when fetching them. Bugfix on
25180 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
25181 refetch the descriptor with router purpose 'general', disabling
25183 - Fix a rare bug in rend_fn unit tests: we would fail a test when
25184 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
25185 on 0.2.0.10-alpha; fixes bug 1808.
25186 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
25187 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
25188 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
25189 Servers can start sending this code when enough clients recognize
25190 it. Also update the spec to reflect this new reason. Bugfix on
25191 0.1.0.1-rc; fixes part of bug 1793.
25192 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
25193 when we switch from being a public relay to a bridge. Otherwise
25194 there will still be clients that see the relay in their consensus,
25195 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
25197 - Instead of giving an assertion failure on an internal mismatch
25198 on estimated freelist size, just log a BUG warning and try later.
25199 Mitigates but does not fix bug 1125.
25200 - Fix an assertion failure that could occur in caches or bridge users
25201 when using a very short voting interval on a testing network.
25202 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
25204 o Minor bugfixes (on 0.2.2.x):
25205 - Alter directory authorities to always consider Exit-flagged nodes
25206 as potential Guard nodes in their votes. The actual decision to
25207 use Exits as Guards is done in the consensus bandwidth weights.
25208 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
25209 - When the controller is reporting the purpose of circuits that
25210 didn't finish building before the circuit build timeout, it was
25211 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
25212 - Our libevent version parsing code couldn't handle versions like
25213 1.4.14b-stable and incorrectly warned the user about using an
25214 old and broken version of libevent. Treat 1.4.14b-stable like
25215 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
25217 - Don't use substitution references like $(VAR:MOD) when
25218 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
25219 '$(:x)' to 'x' rather than the empty string. This bites us in
25220 doc/ when configured with --disable-asciidoc. Bugfix on
25221 0.2.2.9-alpha; fixes bug 1773.
25222 - Remove a spurious hidden service server-side log notice about
25223 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
25225 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
25227 - Correctly report written bytes on linked connections. Found while
25228 implementing 1790. Bugfix on 0.2.2.4-alpha.
25229 - Fix three memory leaks: one in circuit_build_times_parse_state(),
25230 one in dirvote_add_signatures_to_pending_consensus(), and one every
25231 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
25232 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
25234 o Code simplifications and refactoring:
25235 - Take a first step towards making or.h smaller by splitting out
25236 function definitions for all source files in src/or/. Leave
25237 structures and defines in or.h for now.
25238 - Remove a bunch of unused function declarations as well as a block of
25239 #if 0'd code from the unit tests. Closes bug 1824.
25240 - New unit tests for exit-port history statistics; refactored exit
25241 statistics code to be more easily tested.
25242 - Remove the old debian/ directory from the main Tor distribution.
25243 The official Tor-for-debian git repository lives at the URL
25244 https://git.torproject.org/debian/tor.git
25247 Changes in version 0.2.2.14-alpha - 2010-07-12
25248 Tor 0.2.2.14-alpha greatly improves client-side handling of
25249 circuit build timeouts, which are used to estimate speed and improve
25250 performance. We also move to a much better GeoIP database, port Tor to
25251 Windows CE, introduce new compile flags that improve code security,
25252 add an eighth v3 directory authority, and address a lot of more
25256 - Tor directory authorities no longer crash when started with a
25257 cached-microdesc-consensus file in their data directory. Bugfix
25258 on 0.2.2.6-alpha; fixes bug 1532.
25259 - Treat an unset $HOME like an empty $HOME rather than triggering an
25260 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
25261 - Ignore negative and large circuit build timeout values that can
25262 happen during a suspend or hibernate. These values caused various
25263 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
25264 - Alter calculation of Pareto distribution parameter 'Xm' for
25265 Circuit Build Timeout learning to use the weighted average of the
25266 top N=3 modes (because we have three entry guards). Considering
25267 multiple modes should improve the timeout calculation in some cases,
25268 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
25270 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
25271 right censored distribution model. This approach improves over the
25272 synthetic timeout generation approach that was producing insanely
25273 high timeout values. Now we calculate build timeouts using truncated
25274 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
25275 - Do not close circuits that are under construction when they reach
25276 the circuit build timeout. Instead, leave them building (but do not
25277 use them) for up until the time corresponding to the 95th percentile
25278 on the Pareto CDF or 60 seconds, whichever is greater. This is done
25279 to provide better data for the new Pareto model. This percentile
25280 can be controlled by the consensus.
25283 - Move to the June 2010 Maxmind GeoLite country db (rather than the
25284 June 2009 ip-to-country GeoIP db) for our statistics that count
25285 how many users relays are seeing from each country. Now we have
25286 more accurate data for many African countries.
25287 - Port Tor to build and run correctly on Windows CE systems, using
25288 the wcecompat library. Contributed by Valerio Lupi.
25289 - New "--enable-gcc-hardening" ./configure flag (off by default)
25290 to turn on gcc compile time hardening options. It ensures
25291 that signed ints have defined behavior (-fwrapv), enables
25292 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
25293 with canaries (-fstack-protector-all), turns on ASLR protection if
25294 supported by the kernel (-fPIE, -pie), and adds additional security
25295 related warnings. Verified to work on Mac OS X and Debian Lenny.
25296 - New "--enable-linker-hardening" ./configure flag (off by default)
25297 to turn on ELF specific hardening features (relro, now). This does
25298 not work with Mac OS X or any other non-ELF binary format.
25300 o New directory authorities:
25301 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
25305 - New config option "WarnUnsafeSocks 0" disables the warning that
25306 occurs whenever Tor receives a socks handshake using a version of
25307 the socks protocol that can only provide an IP address (rather
25308 than a hostname). Setups that do DNS locally over Tor are fine,
25309 and we shouldn't spam the logs in that case.
25310 - Convert the HACKING file to asciidoc, and add a few new sections
25311 to it, explaining how we use Git, how we make changelogs, and
25312 what should go in a patch.
25313 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
25314 event, to give information on the current rate of circuit timeouts
25315 over our stored history.
25316 - Add ability to disable circuit build time learning via consensus
25317 parameter and via a LearnCircuitBuildTimeout config option. Also
25318 automatically disable circuit build time calculation if we are
25319 either a AuthoritativeDirectory, or if we fail to write our state
25320 file. Fixes bug 1296.
25321 - More gracefully handle corrupt state files, removing asserts
25322 in favor of saving a backup and resetting state.
25323 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
25327 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
25329 - When a2x fails, mention that the user could disable manpages instead
25330 of trying to fix their asciidoc installation.
25331 - Where available, use Libevent 2.0's periodic timers so that our
25332 once-per-second cleanup code gets called even more closely to
25333 once per second than it would otherwise. Fixes bug 943.
25334 - If you run a bridge that listens on multiple IP addresses, and
25335 some user configures a bridge address that uses a different IP
25336 address than your bridge writes in its router descriptor, and the
25337 user doesn't specify an identity key, their Tor would discard the
25338 descriptor because "it isn't one of our configured bridges", and
25339 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
25340 Bugfix on 0.2.0.3-alpha.
25341 - If OpenSSL fails to make a duplicate of a private or public key, log
25342 an error message and try to exit cleanly. May help with debugging
25343 if bug 1209 ever remanifests.
25344 - Save a couple bytes in memory allocation every time we escape
25345 certain characters in a string. Patch from Florian Zumbiehl.
25346 - Make it explicit that we don't cannibalize one-hop circuits. This
25347 happens in the wild, but doesn't turn out to be a problem because
25348 we fortunately don't use those circuits. Many thanks to outofwords
25349 for the initial analysis and to swissknife who confirmed that
25350 two-hop circuits are actually created.
25351 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
25352 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
25353 - Eliminate a case where a circuit build time warning was displayed
25354 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
25357 Changes in version 0.2.1.26 - 2010-05-02
25358 Tor 0.2.1.26 addresses the recent connection and memory overload
25359 problems we've been seeing on relays, especially relays with their
25360 DirPort open. If your relay has been crashing, or you turned it off
25361 because it used too many resources, give this release a try.
25363 This release also fixes yet another instance of broken OpenSSL libraries
25364 that was causing some relays to drop out of the consensus.
25367 - Teach relays to defend themselves from connection overload. Relays
25368 now close idle circuits early if it looks like they were intended
25369 for directory fetches. Relays are also more aggressive about closing
25370 TLS connections that have no circuits on them. Such circuits are
25371 unlikely to be re-used, and tens of thousands of them were piling
25372 up at the fast relays, causing the relays to run out of sockets
25373 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
25374 their directory fetches over TLS).
25375 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
25376 that claim to be earlier than 0.9.8m, but which have in reality
25377 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
25378 behavior. Possible fix for some cases of bug 1346.
25379 - Directory mirrors were fetching relay descriptors only from v2
25380 directory authorities, rather than v3 authorities like they should.
25381 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
25382 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
25385 - Finally get rid of the deprecated and now harmful notion of "clique
25386 mode", where directory authorities maintain TLS connections to
25390 - In the util/threads test, no longer free the test_mutex before all
25391 worker threads have finished. Bugfix on 0.2.1.6-alpha.
25392 - The master thread could starve the worker threads quite badly on
25393 certain systems, causing them to run only partially in the allowed
25394 window. This resulted in test failures. Now the master thread sleeps
25395 occasionally for a few microseconds while the two worker-threads
25396 compete for the mutex. Bugfix on 0.2.0.1-alpha.
25399 Changes in version 0.2.2.13-alpha - 2010-04-24
25400 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
25401 problems we've been seeing on relays, especially relays with their
25402 DirPort open. If your relay has been crashing, or you turned it off
25403 because it used too many resources, give this release a try.
25406 - Teach relays to defend themselves from connection overload. Relays
25407 now close idle circuits early if it looks like they were intended
25408 for directory fetches. Relays are also more aggressive about closing
25409 TLS connections that have no circuits on them. Such circuits are
25410 unlikely to be re-used, and tens of thousands of them were piling
25411 up at the fast relays, causing the relays to run out of sockets
25412 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
25413 their directory fetches over TLS).
25416 - Finally get rid of the deprecated and now harmful notion of "clique
25417 mode", where directory authorities maintain TLS connections to
25419 - Directory authorities now do an immediate reachability check as soon
25420 as they hear about a new relay. This change should slightly reduce
25421 the time between setting up a relay and getting listed as running
25422 in the consensus. It should also improve the time between setting
25423 up a bridge and seeing use by bridge users.
25424 - Directory authorities no longer launch a TLS connection to every
25425 relay as they startup. Now that we have 2k+ descriptors cached,
25426 the resulting network hiccup is becoming a burden. Besides,
25427 authorities already avoid voting about Running for the first half
25428 hour of their uptime.
25431 Changes in version 0.2.2.12-alpha - 2010-04-20
25432 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
25433 handle and vote on descriptors. It was causing relays to drop out of
25437 - Many relays have been falling out of the consensus lately because
25438 not enough authorities know about their descriptor for them to get
25439 a majority of votes. When we deprecated the v2 directory protocol,
25440 we got rid of the only way that v3 authorities can hear from each
25441 other about other descriptors. Now authorities examine every v3
25442 vote for new descriptors, and fetch them from that authority. Bugfix
25444 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
25445 and a warning in or.h related to bandwidth_weight_rule_t that
25446 prevented clean compile on OS X. Fixes bug 1363; bugfix on
25448 - Fix a segfault on relays when DirReqStatistics is enabled
25449 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
25453 - Demote a confusing TLS warning that relay operators might get when
25454 someone tries to talk to their OrPort. It is neither the operator's
25455 fault nor can they do anything about it. Fixes bug 1364; bugfix
25459 Changes in version 0.2.2.11-alpha - 2010-04-15
25460 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
25461 libraries that was causing some relays to drop out of the consensus.
25464 - Directory mirrors were fetching relay descriptors only from v2
25465 directory authorities, rather than v3 authorities like they should.
25466 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
25467 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
25468 - Fix a parsing error that made every possible value of
25469 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
25470 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
25471 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
25472 about the option without breaking older ones.
25473 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
25474 that claim to be earlier than 0.9.8m, but which have in reality
25475 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
25476 behavior. Possible fix for some cases of bug 1346.
25479 - Experiment with a more aggressive approach to preventing clients
25480 from making one-hop exit streams. Exit relays who want to try it
25481 out can set "RefuseUnknownExits 1" in their torrc, and then look
25482 for "Attempt by %s to open a stream" log messages. Let us know
25484 - Add support for statically linking zlib by specifying
25485 --enable-static-zlib, to go with our support for statically linking
25486 openssl and libevent. Resolves bug 1358.
25489 - Fix a segfault that happens whenever a Tor client that is using
25490 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
25492 - When we cleaned up the contrib/tor-exit-notice.html file, we left
25493 out the first line. Fixes bug 1295.
25494 - When building the manpage from a tarball, we required asciidoc, but
25495 the asciidoc -> roff/html conversion was already done for the
25496 tarball. Make 'make' complain only when we need asciidoc (either
25497 because we're compiling directly from git, or because we altered
25498 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
25499 - When none of the directory authorities vote on any params, Tor
25500 segfaulted when trying to make the consensus from the votes. We
25501 didn't trigger the bug in practice, because authorities do include
25502 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
25505 - In the util/threads test, no longer free the test_mutex before all
25506 worker threads have finished. Bugfix on 0.2.1.6-alpha.
25507 - The master thread could starve the worker threads quite badly on
25508 certain systems, causing them to run only partially in the allowed
25509 window. This resulted in test failures. Now the master thread sleeps
25510 occasionally for a few microseconds while the two worker-threads
25511 compete for the mutex. Bugfix on 0.2.0.1-alpha.
25514 Changes in version 0.2.2.10-alpha - 2010-03-07
25515 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
25516 could prevent relays from guessing their IP address correctly. It also
25517 starts the groundwork for another client-side performance boost, since
25518 currently we're not making efficient use of relays that have both the
25519 Guard flag and the Exit flag.
25522 - Fix a regression from our patch for bug 1244 that caused relays
25523 to guess their IP address incorrectly if they didn't set Address
25524 in their torrc and/or their address fails to resolve. Bugfix on
25525 0.2.2.9-alpha; fixes bug 1269.
25527 o Major features (performance):
25528 - Directory authorities now compute consensus weightings that instruct
25529 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
25530 and no flag. Clients that use these weightings will distribute
25531 network load more evenly across these different relay types. The
25532 weightings are in the consensus so we can change them globally in
25533 the future. Extra thanks to "outofwords" for finding some nasty
25534 security bugs in the first implementation of this feature.
25536 o Minor features (performance):
25537 - Always perform router selections using weighted relay bandwidth,
25538 even if we don't need a high capacity circuit at the time. Non-fast
25539 circuits now only differ from fast ones in that they can use relays
25540 not marked with the Fast flag. This "feature" could turn out to
25541 be a horrible bug; we should investigate more before it goes into
25545 - Allow disabling building of the manpages. Skipping the manpage
25546 speeds up the build considerably.
25548 o Minor bugfixes (on 0.2.2.x):
25549 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
25550 Bugfix on 0.2.2.9-alpha.
25551 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
25552 config option. Bugfix on 0.2.2.7-alpha.
25553 - Ship the asciidoc-helper file in the tarball, so that people can
25554 build from source if they want to, and touching the .1.txt files
25555 doesn't break the build. Bugfix on 0.2.2.9-alpha.
25557 o Minor bugfixes (on 0.2.1.x or earlier):
25558 - Fix a dereference-then-NULL-check sequence when publishing
25559 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
25561 - Fix another dereference-then-NULL-check sequence. Bugfix on
25562 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
25563 - Make sure we treat potentially not NUL-terminated strings correctly.
25564 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
25566 o Code simplifications and refactoring:
25567 - Fix some urls in the exit notice file and make it XHTML1.1 strict
25568 compliant. Based on a patch from Christian Kujau.
25569 - Don't use sed in asciidoc-helper anymore.
25570 - Make the build process fail if asciidoc cannot be found and
25571 building with asciidoc isn't disabled.
25574 Changes in version 0.2.2.9-alpha - 2010-02-22
25575 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
25576 location of a directory authority, and cleans up a bunch of small bugs.
25578 o Directory authority changes:
25579 - Change IP address for dannenberg (v3 directory authority), and
25580 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
25581 service directory authority) from the list.
25584 - Make Tor work again on the latest OS X: when deciding whether to
25585 use strange flags to turn TLS renegotiation on, detect the OpenSSL
25586 version at run-time, not compile time. We need to do this because
25587 Apple doesn't update its dev-tools headers when it updates its
25588 libraries in a security patch.
25589 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
25590 that could happen on 32-bit platforms with 64-bit time_t. Also fix
25591 a memory leak when requesting a hidden service descriptor we've
25592 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
25594 - Authorities could be tricked into giving out the Exit flag to relays
25595 that didn't allow exiting to any ports. This bug could screw
25596 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
25597 1238. Bug discovered by Martin Kowalczyk.
25598 - When freeing a session key, zero it out completely. We only zeroed
25599 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
25600 patched by ekir. Fixes bug 1254.
25603 - Fix static compilation by listing the openssl libraries in the right
25604 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
25605 - Resume handling .exit hostnames in a special way: originally we
25606 stripped the .exit part and used the requested exit relay. In
25607 0.2.2.1-alpha we stopped treating them in any special way, meaning
25608 if you use a .exit address then Tor will pass it on to the exit
25609 relay. Now we reject the .exit stream outright, since that behavior
25610 might be more expected by the user. Found and diagnosed by Scott
25611 Bennett and Downie on or-talk.
25612 - Don't spam the controller with events when we have no file
25613 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
25614 for log messages was already solved from bug 748.)
25615 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
25617 - Make the DNSPort option work with libevent 2.x. Don't alter the
25618 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
25619 - Emit a GUARD DROPPED controller event for a case we missed.
25620 - Make more fields in the controller protocol case-insensitive, since
25621 control-spec.txt said they were.
25622 - Refactor resolve_my_address() to not use gethostbyname() anymore.
25623 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
25624 - Fix a spec conformance issue: the network-status-version token
25625 must be the first token in a v3 consensus or vote. Discovered by
25626 parakeep. Bugfix on 0.2.0.3-alpha.
25628 o Code simplifications and refactoring:
25629 - Generate our manpage and HTML documentation using Asciidoc. This
25630 change should make it easier to maintain the documentation, and
25631 produce nicer HTML.
25632 - Remove the --enable-iphone option. According to reports from Marco
25633 Bonetti, Tor builds fine without any special tweaking on recent
25634 iPhone SDK versions.
25635 - Removed some unnecessary files from the source distribution. The
25636 AUTHORS file has now been merged into the people page on the
25637 website. The roadmaps and design doc can now be found in the
25638 projects directory in svn.
25639 - Enabled various circuit build timeout constants to be controlled
25640 by consensus parameters. Also set better defaults for these
25641 parameters based on experimentation on broadband and simulated
25642 high latency links.
25645 - The 'EXTENDCIRCUIT' control port command can now be used with
25646 a circ id of 0 and no path. This feature will cause Tor to build
25647 a new 'fast' general purpose circuit using its own path selection
25649 - Added a BUILDTIMEOUT_SET controller event to describe changes
25650 to the circuit build timeout.
25651 - Future-proof the controller protocol a bit by ignoring keyword
25652 arguments we do not recognize.
25653 - Expand homedirs passed to tor-checkkey. This should silence a
25654 coverity complaint about passing a user-supplied string into
25655 open() without checking it.
25658 Changes in version 0.2.1.25 - 2010-03-16
25659 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
25660 prevent relays from guessing their IP address correctly. It also fixes
25661 several minor potential security bugs.
25664 - Fix a regression from our patch for bug 1244 that caused relays
25665 to guess their IP address incorrectly if they didn't set Address
25666 in their torrc and/or their address fails to resolve. Bugfix on
25667 0.2.1.23; fixes bug 1269.
25668 - When freeing a session key, zero it out completely. We only zeroed
25669 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
25670 patched by ekir. Fixes bug 1254.
25673 - Fix a dereference-then-NULL-check sequence when publishing
25674 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
25676 - Fix another dereference-then-NULL-check sequence. Bugfix on
25677 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
25678 - Make sure we treat potentially not NUL-terminated strings correctly.
25679 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
25683 Changes in version 0.2.1.24 - 2010-02-21
25684 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
25688 - Work correctly out-of-the-box with even more vendor-patched versions
25689 of OpenSSL. In particular, make it so Debian and OS X don't need
25690 customized patches to run/build.
25693 Changes in version 0.2.1.23 - 2010-02-13
25694 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
25695 again on the latest OS X, and updates the location of a directory
25698 o Major bugfixes (performance):
25699 - We were selecting our guards uniformly at random, and then weighting
25700 which of our guards we'd use uniformly at random. This imbalance
25701 meant that Tor clients were severely limited on throughput (and
25702 probably latency too) by the first hop in their circuit. Now we
25703 select guards weighted by currently advertised bandwidth. We also
25704 automatically discard guards picked using the old algorithm. Fixes
25705 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
25708 - Make Tor work again on the latest OS X: when deciding whether to
25709 use strange flags to turn TLS renegotiation on, detect the OpenSSL
25710 version at run-time, not compile time. We need to do this because
25711 Apple doesn't update its dev-tools headers when it updates its
25712 libraries in a security patch.
25713 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
25714 that could happen on 32-bit platforms with 64-bit time_t. Also fix
25715 a memory leak when requesting a hidden service descriptor we've
25716 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
25719 o Directory authority changes:
25720 - Change IP address for dannenberg (v3 directory authority), and
25721 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
25722 service directory authority) from the list.
25725 - Refactor resolve_my_address() to not use gethostbyname() anymore.
25726 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
25729 - Avoid a mad rush at the beginning of each month when each client
25730 rotates half of its guards. Instead we spread the rotation out
25731 throughout the month, but we still avoid leaving a precise timestamp
25732 in the state file about when we first picked the guard. Improves
25733 over the behavior introduced in 0.1.2.17.
25736 Changes in version 0.2.2.8-alpha - 2010-01-26
25737 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
25738 causing bridge relays to disappear. If you're running a bridge,
25742 - Fix a memory corruption bug on bridges that occurred during the
25743 inclusion of stats data in extra-info descriptors. Also fix the
25744 interface for geoip_get_bridge_stats* to prevent similar bugs in
25745 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
25746 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
25749 - Ignore OutboundBindAddress when connecting to localhost.
25750 Connections to localhost need to come _from_ localhost, or else
25751 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
25755 Changes in version 0.2.2.7-alpha - 2010-01-19
25756 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
25757 as laying the groundwork for further relay-side performance fixes. It
25758 also starts cleaning up client behavior with respect to the EntryNodes,
25759 ExitNodes, and StrictNodes config options.
25761 This release also rotates two directory authority keys, due to a
25762 security breach of some of the Torproject servers.
25764 o Directory authority changes:
25765 - Rotate keys (both v3 identity and relay identity) for moria1
25768 o Major features (performance):
25769 - We were selecting our guards uniformly at random, and then weighting
25770 which of our guards we'd use uniformly at random. This imbalance
25771 meant that Tor clients were severely limited on throughput (and
25772 probably latency too) by the first hop in their circuit. Now we
25773 select guards weighted by currently advertised bandwidth. We also
25774 automatically discard guards picked using the old algorithm. Fixes
25775 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
25776 - When choosing which cells to relay first, relays can now favor
25777 circuits that have been quiet recently, to provide lower latency
25778 for low-volume circuits. By default, relays enable or disable this
25779 feature based on a setting in the consensus. You can override
25780 this default by using the new "CircuitPriorityHalflife" config
25781 option. Design and code by Ian Goldberg, Can Tang, and Chris
25783 - Add separate per-conn write limiting to go with the per-conn read
25784 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
25785 but never per-conn write limits.
25786 - New consensus params "bwconnrate" and "bwconnburst" to let us
25787 rate-limit client connections as they enter the network. It's
25788 controlled in the consensus so we can turn it on and off for
25789 experiments. It's starting out off. Based on proposal 163.
25791 o Major features (relay selection options):
25792 - Switch to a StrictNodes config option, rather than the previous
25793 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
25794 "StrictExcludeNodes" option.
25795 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
25796 change during a config reload, mark and discard all our origin
25797 circuits. This fix should address edge cases where we change the
25798 config options and but then choose a circuit that we created before
25800 - If EntryNodes or ExitNodes are set, be more willing to use an
25801 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
25803 - Make EntryNodes config option much more aggressive even when
25804 StrictNodes is not set. Before it would prepend your requested
25805 entrynodes to your list of guard nodes, but feel free to use others
25806 after that. Now it chooses only from your EntryNodes if any of
25807 those are available, and only falls back to others if a) they're
25808 all down and b) StrictNodes is not set.
25809 - Now we refresh your entry guards from EntryNodes at each consensus
25810 fetch -- rather than just at startup and then they slowly rot as
25811 the network changes.
25814 - Stop bridge directory authorities from answering dbg-stability.txt
25815 directory queries, which would let people fetch a list of all
25816 bridge identities they track. Bugfix on 0.2.1.6-alpha.
25819 - Log a notice when we get a new control connection. Now it's easier
25820 for security-conscious users to recognize when a local application
25821 is knocking on their controller door. Suggested by bug 1196.
25822 - New config option "CircuitStreamTimeout" to override our internal
25823 timeout schedule for how many seconds until we detach a stream from
25824 a circuit and try a new circuit. If your network is particularly
25825 slow, you might want to set this to a number like 60.
25826 - New controller command "getinfo config-text". It returns the
25827 contents that Tor would write if you send it a SAVECONF command,
25828 so the controller can write the file to disk itself.
25829 - New options for SafeLogging to allow scrubbing only log messages
25830 generated while acting as a relay.
25831 - Ship the bridges spec file in the tarball too.
25832 - Avoid a mad rush at the beginning of each month when each client
25833 rotates half of its guards. Instead we spread the rotation out
25834 throughout the month, but we still avoid leaving a precise timestamp
25835 in the state file about when we first picked the guard. Improves
25836 over the behavior introduced in 0.1.2.17.
25838 o Minor bugfixes (compiling):
25839 - Fix compilation on OS X 10.3, which has a stub mlockall() but
25840 hides it. Bugfix on 0.2.2.6-alpha.
25841 - Fix compilation on Solaris by removing support for the
25842 DisableAllSwap config option. Solaris doesn't have an rlimit for
25843 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
25846 o Minor bugfixes (crashes):
25847 - Do not segfault when writing buffer stats when we haven't observed
25848 a single circuit to report about. Found by Fabian Lanze. Bugfix on
25850 - If we're in the pathological case where there's no exit bandwidth
25851 but there is non-exit bandwidth, or no guard bandwidth but there
25852 is non-guard bandwidth, don't crash during path selection. Bugfix
25854 - Fix an impossible-to-actually-trigger buffer overflow in relay
25855 descriptor generation. Bugfix on 0.1.0.15.
25857 o Minor bugfixes (privacy):
25858 - Fix an instance where a Tor directory mirror might accidentally
25859 log the IP address of a misbehaving Tor client. Bugfix on
25861 - Don't list Windows capabilities in relay descriptors. We never made
25862 use of them, and maybe it's a bad idea to publish them. Bugfix
25865 o Minor bugfixes (other):
25866 - Resolve an edge case in path weighting that could make us misweight
25867 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
25868 - Fix statistics on client numbers by country as seen by bridges that
25869 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
25870 intervals instead of variable 12-to-48-hour intervals.
25871 - After we free an internal connection structure, overwrite it
25872 with a different memory value than we use for overwriting a freed
25873 internal circuit structure. Should help with debugging. Suggested
25875 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
25878 o Removed features:
25879 - Remove the HSAuthorityRecordStats option that version 0 hidden
25880 service authorities could have used to track statistics of overall
25881 hidden service usage.
25884 Changes in version 0.2.1.22 - 2010-01-19
25885 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
25886 authorities -- it would tell you its whole history of bridge descriptors
25887 if you make the right directory request. This stable update also
25888 rotates two of the seven v3 directory authority keys and locations.
25890 o Directory authority changes:
25891 - Rotate keys (both v3 identity and relay identity) for moria1
25895 - Stop bridge directory authorities from answering dbg-stability.txt
25896 directory queries, which would let people fetch a list of all
25897 bridge identities they track. Bugfix on 0.2.1.6-alpha.
25900 Changes in version 0.2.1.21 - 2009-12-21
25901 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
25902 library. If you use Tor on Linux / Unix and you're getting SSL
25903 renegotiation errors, upgrading should help. We also recommend an
25904 upgrade if you're an exit relay.
25907 - Work around a security feature in OpenSSL 0.9.8l that prevents our
25908 handshake from working unless we explicitly tell OpenSSL that we
25909 are using SSL renegotiation safely. We are, of course, but OpenSSL
25910 0.9.8l won't work unless we say we are.
25911 - Avoid crashing if the client is trying to upload many bytes and the
25912 circuit gets torn down at the same time, or if the flip side
25913 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
25916 - Do not refuse to learn about authority certs and v2 networkstatus
25917 documents that are older than the latest consensus. This bug might
25918 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
25919 Spotted and fixed by xmux.
25920 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
25921 trigger platform-specific option misparsing case found by Coverity
25923 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
25924 trigger assert. Fixes bug 1173.
25927 Changes in version 0.2.2.6-alpha - 2009-11-19
25928 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
25929 support for the new lower-footprint "microdescriptor" directory design,
25930 future-proofing our consensus format against new hash functions or
25931 other changes, and an Android port. It also makes Tor compatible with
25932 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
25935 - Directory authorities can now create, vote on, and serve multiple
25936 parallel formats of directory data as part of their voting process.
25937 Partially implements Proposal 162: "Publish the consensus in
25939 - Directory authorities can now agree on and publish small summaries
25940 of router information that clients can use in place of regular
25941 server descriptors. This transition will eventually allow clients
25942 to use far less bandwidth for downloading information about the
25943 network. Begins the implementation of Proposal 158: "Clients
25944 download consensus + microdescriptors".
25945 - The directory voting system is now extensible to use multiple hash
25946 algorithms for signatures and resource selection. Newer formats
25947 are signed with SHA256, with a possibility for moving to a better
25948 hash algorithm in the future.
25949 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
25950 current and future memory pages via mlockall(). On supported
25951 platforms (modern Linux and probably BSD but not Windows or OS X),
25952 this should effectively disable any and all attempts to page out
25953 memory. This option requires that you start your Tor as root --
25954 if you use DisableAllSwap, please consider using the User option
25955 to properly reduce the privileges of your Tor.
25956 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
25957 to help Tor build correctly for Android phones.
25960 - Work around a security feature in OpenSSL 0.9.8l that prevents our
25961 handshake from working unless we explicitly tell OpenSSL that we
25962 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
25963 won't work unless we say we are.
25966 - Fix a crash bug when trying to initialize the evdns module in
25967 Libevent 2. Bugfix on 0.2.1.16-rc.
25968 - Stop logging at severity 'warn' when some other Tor client tries
25969 to establish a circuit with us using weak DH keys. It's a protocol
25970 violation, but that doesn't mean ordinary users need to hear about
25971 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
25972 - Do not refuse to learn about authority certs and v2 networkstatus
25973 documents that are older than the latest consensus. This bug might
25974 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
25975 Spotted and fixed by xmux.
25976 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
25977 - If all authorities restart at once right before a consensus vote,
25978 nobody will vote about "Running", and clients will get a consensus
25979 with no usable relays. Instead, authorities refuse to build a
25980 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
25981 - If your relay can't keep up with the number of incoming create
25982 cells, it would log one warning per failure into your logs. Limit
25983 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
25984 - Bridges now use "reject *:*" as their default exit policy. Bugfix
25985 on 0.2.0.3-alpha; fixes bug 1113.
25986 - Fix a memory leak on directory authorities during voting that was
25987 introduced in 0.2.2.1-alpha. Found via valgrind.
25990 Changes in version 0.2.1.20 - 2009-10-15
25991 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
25992 services at once, prepares for more performance improvements, and
25993 fixes a bunch of smaller bugs.
25995 The Windows and OS X bundles also include a more recent Vidalia,
25996 and switch from Privoxy to Polipo.
25998 The OS X installers are now drag and drop. It's best to un-install
25999 Tor/Vidalia and then install this new bundle, rather than upgrade. If
26000 you want to upgrade, you'll need to update the paths for Tor and Polipo
26001 in the Vidalia Settings window.
26004 - Send circuit or stream sendme cells when our window has decreased
26005 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
26006 by Karsten when testing the "reduce circuit window" performance
26007 patch. Bugfix on the 54th commit on Tor -- from July 2002,
26008 before the release of Tor 0.0.0. This is the new winner of the
26010 - Fix a remotely triggerable memory leak when a consensus document
26011 contains more than one signature from the same voter. Bugfix on
26013 - Avoid segfault in rare cases when finishing an introduction circuit
26014 as a client and finding out that we don't have an introduction key
26015 for it. Fixes bug 1073. Reported by Aaron Swartz.
26018 - Tor now reads the "circwindow" parameter out of the consensus,
26019 and uses that value for its circuit package window rather than the
26020 default of 1000 cells. Begins the implementation of proposal 168.
26022 o New directory authorities:
26023 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
26025 - Move moria1 and tonga to alternate IP addresses.
26028 - Fix a signed/unsigned compile warning in 0.2.1.19.
26029 - Fix possible segmentation fault on directory authorities. Bugfix on
26031 - Fix an extremely rare infinite recursion bug that could occur if
26032 we tried to log a message after shutting down the log subsystem.
26033 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
26034 - Fix an obscure bug where hidden services on 64-bit big-endian
26035 systems might mis-read the timestamp in v3 introduce cells, and
26036 refuse to connect back to the client. Discovered by "rotor".
26037 Bugfix on 0.2.1.6-alpha.
26038 - We were triggering a CLOCK_SKEW controller status event whenever
26039 we connect via the v2 connection protocol to any relay that has
26040 a wrong clock. Instead, we should only inform the controller when
26041 it's a trusted authority that claims our clock is wrong. Bugfix
26042 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
26043 - We were telling the controller about CHECKING_REACHABILITY and
26044 REACHABILITY_FAILED status events whenever we launch a testing
26045 circuit or notice that one has failed. Instead, only tell the
26046 controller when we want to inform the user of overall success or
26047 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
26049 - Don't warn when we're using a circuit that ends with a node
26050 excluded in ExcludeExitNodes, but the circuit is not used to access
26051 the outside world. This should help fix bug 1090. Bugfix on
26053 - Work around a small memory leak in some versions of OpenSSL that
26054 stopped the memory used by the hostname TLS extension from being
26058 - Add a "getinfo status/accepted-server-descriptor" controller
26059 command, which is the recommended way for controllers to learn
26060 whether our server descriptor has been successfully received by at
26061 least on directory authority. Un-recommend good-server-descriptor
26062 getinfo and status events until we have a better design for them.
26065 Changes in version 0.2.2.5-alpha - 2009-10-11
26066 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
26069 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
26071 o Directory authorities:
26072 - Temporarily (just for this release) move dizum to an alternate
26076 Changes in version 0.2.2.4-alpha - 2009-10-10
26077 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
26078 introduces a new unit test framework, shifts directry authority
26079 addresses around to reduce the impact from recent blocking events,
26080 and fixes a few smaller bugs.
26083 - Fix several more asserts in the circuit_build_times code, for
26084 example one that causes Tor to fail to start once we have
26085 accumulated 5000 build times in the state file. Bugfixes on
26086 0.2.2.2-alpha; fixes bug 1108.
26088 o New directory authorities:
26089 - Move moria1 and Tonga to alternate IP addresses.
26092 - Log SSL state transitions at debug level during handshake, and
26093 include SSL states in error messages. This may help debug future
26094 SSL handshake issues.
26095 - Add a new "Handshake" log domain for activities that happen
26096 during the TLS handshake.
26097 - Revert to the "June 3 2009" ip-to-country file. The September one
26098 seems to have removed most US IP addresses.
26099 - Directory authorities now reject Tor relays with versions less than
26100 0.1.2.14. This step cuts out four relays from the current network,
26101 none of which are very big.
26104 - Fix a couple of smaller issues with gathering statistics. Bugfixes
26106 - Fix two memory leaks in the error case of
26107 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
26108 - Don't count one-hop circuits when we're estimating how long it
26109 takes circuits to build on average. Otherwise we'll set our circuit
26110 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
26111 - Directory authorities no longer change their opinion of, or vote on,
26112 whether a router is Running, unless they have themselves been
26113 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
26116 o Code simplifications and refactoring:
26117 - Revise our unit tests to use the "tinytest" framework, so we
26118 can run tests in their own processes, have smarter setup/teardown
26119 code, and so on. The unit test code has moved to its own
26120 subdirectory, and has been split into multiple modules.
26123 Changes in version 0.2.2.3-alpha - 2009-09-23
26124 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
26127 - Fix an overzealous assert in our new circuit build timeout code.
26128 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
26131 - If the networkstatus consensus tells us that we should use a
26132 negative circuit package window, ignore it. Otherwise we'll
26133 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
26136 Changes in version 0.2.2.2-alpha - 2009-09-21
26137 Tor 0.2.2.2-alpha introduces our latest performance improvement for
26138 clients: Tor tracks the average time it takes to build a circuit, and
26139 avoids using circuits that take too long to build. For fast connections,
26140 this feature can cut your expected latency in half. For slow or flaky
26141 connections, it could ruin your Tor experience. Let us know if it does!
26144 - Tor now tracks how long it takes to build client-side circuits
26145 over time, and adapts its timeout to local network performance.
26146 Since a circuit that takes a long time to build will also provide
26147 bad performance, we get significant latency improvements by
26148 discarding the slowest 20% of circuits. Specifically, Tor creates
26149 circuits more aggressively than usual until it has enough data
26150 points for a good timeout estimate. Implements proposal 151.
26151 We are especially looking for reports (good and bad) from users with
26152 both EDGE and broadband connections that can move from broadband
26153 to EDGE and find out if the build-time data in the .tor/state gets
26154 reset without loss of Tor usability. You should also see a notice
26155 log message telling you that Tor has reset its timeout.
26156 - Directory authorities can now vote on arbitrary integer values as
26157 part of the consensus process. This is designed to help set
26158 network-wide parameters. Implements proposal 167.
26159 - Tor now reads the "circwindow" parameter out of the consensus,
26160 and uses that value for its circuit package window rather than the
26161 default of 1000 cells. Begins the implementation of proposal 168.
26164 - Fix a remotely triggerable memory leak when a consensus document
26165 contains more than one signature from the same voter. Bugfix on
26169 - Fix an extremely rare infinite recursion bug that could occur if
26170 we tried to log a message after shutting down the log subsystem.
26171 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
26172 - Fix parsing for memory or time units given without a space between
26173 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
26174 - A networkstatus vote must contain exactly one signature. Spec
26175 conformance issue. Bugfix on 0.2.0.3-alpha.
26176 - Fix an obscure bug where hidden services on 64-bit big-endian
26177 systems might mis-read the timestamp in v3 introduce cells, and
26178 refuse to connect back to the client. Discovered by "rotor".
26179 Bugfix on 0.2.1.6-alpha.
26180 - We were triggering a CLOCK_SKEW controller status event whenever
26181 we connect via the v2 connection protocol to any relay that has
26182 a wrong clock. Instead, we should only inform the controller when
26183 it's a trusted authority that claims our clock is wrong. Bugfix
26184 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
26185 - We were telling the controller about CHECKING_REACHABILITY and
26186 REACHABILITY_FAILED status events whenever we launch a testing
26187 circuit or notice that one has failed. Instead, only tell the
26188 controller when we want to inform the user of overall success or
26189 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
26191 - Don't warn when we're using a circuit that ends with a node
26192 excluded in ExcludeExitNodes, but the circuit is not used to access
26193 the outside world. This should help fix bug 1090, but more problems
26194 remain. Bugfix on 0.2.1.6-alpha.
26195 - Work around a small memory leak in some versions of OpenSSL that
26196 stopped the memory used by the hostname TLS extension from being
26198 - Make our 'torify' script more portable; if we have only one of
26199 'torsocks' or 'tsocks' installed, don't complain to the user;
26200 and explain our warning about tsocks better.
26203 - Add a "getinfo status/accepted-server-descriptor" controller
26204 command, which is the recommended way for controllers to learn
26205 whether our server descriptor has been successfully received by at
26206 least on directory authority. Un-recommend good-server-descriptor
26207 getinfo and status events until we have a better design for them.
26208 - Update to the "September 4 2009" ip-to-country file.
26211 Changes in version 0.2.2.1-alpha - 2009-08-26
26212 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
26213 Tor clients to bootstrap on networks where only port 80 is reachable,
26214 makes it more straightforward to support hardware crypto accelerators,
26215 and starts the groundwork for gathering stats safely at relays.
26218 - Start the process of disabling ".exit" address notation, since it
26219 can be used for a variety of esoteric application-level attacks
26220 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
26223 o New directory authorities:
26224 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
26228 - New AccelName and AccelDir options add support for dynamic OpenSSL
26229 hardware crypto acceleration engines.
26230 - Tor now supports tunneling all of its outgoing connections over
26231 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
26232 configuration options. Code by Christopher Davis.
26235 - Send circuit or stream sendme cells when our window has decreased
26236 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
26237 by Karsten when testing the "reduce circuit window" performance
26238 patch. Bugfix on the 54th commit on Tor -- from July 2002,
26239 before the release of Tor 0.0.0. This is the new winner of the
26242 o New options for gathering stats safely:
26243 - Directory mirrors that set "DirReqStatistics 1" write statistics
26244 about directory requests to disk every 24 hours. As compared to the
26245 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
26246 1) stats are written to disk exactly every 24 hours; 2) estimated
26247 shares of v2 and v3 requests are determined as mean values, not at
26248 the end of a measurement period; 3) unresolved requests are listed
26249 with country code '??'; 4) directories also measure download times.
26250 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
26251 number of exit streams and transferred bytes per port to disk every
26253 - Relays that set "CellStatistics 1" write statistics on how long
26254 cells spend in their circuit queues to disk every 24 hours.
26255 - Entry nodes that set "EntryStatistics 1" write statistics on the
26256 rough number and origins of connecting clients to disk every 24
26258 - Relays that write any of the above statistics to disk and set
26259 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
26260 their extra-info documents.
26263 - New --digests command-line switch to output the digests of the
26264 source files Tor was built with.
26265 - The "torify" script now uses torsocks where available.
26266 - The memarea code now uses a sentinel value at the end of each area
26267 to make sure nothing writes beyond the end of an area. This might
26268 help debug some conceivable causes of bug 930.
26269 - Time and memory units in the configuration file can now be set to
26270 fractional units. For example, "2.5 GB" is now a valid value for
26272 - Certain Tor clients (such as those behind check.torproject.org) may
26273 want to fetch the consensus in an extra early manner. To enable this
26274 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
26275 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
26276 as only certain clients who must have this information sooner should
26278 - Instead of adding the svn revision to the Tor version string, report
26279 the git commit (when we're building from a git checkout).
26282 - If any of the v3 certs we download are unparseable, we should
26283 actually notice the failure so we don't retry indefinitely. Bugfix
26284 on 0.2.0.x; reported by "rotator".
26285 - If the cached cert file is unparseable, warn but don't exit.
26286 - Fix possible segmentation fault on directory authorities. Bugfix on
26288 - When Tor fails to parse a descriptor of any kind, dump it to disk.
26289 Might help diagnosing bug 1051.
26291 o Deprecated and removed features:
26292 - The controller no longer accepts the old obsolete "addr-mappings/"
26293 or "unregistered-servers-" GETINFO values.
26294 - Hidden services no longer publish version 0 descriptors, and clients
26295 do not request or use version 0 descriptors. However, the old hidden
26296 service authorities still accept and serve version 0 descriptors
26297 when contacted by older hidden services/clients.
26298 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
26299 always on; using them is necessary for correct forward-compatible
26301 - Remove support for .noconnect style addresses. Nobody was using
26302 them, and they provided another avenue for detecting Tor users
26303 via application-level web tricks.
26305 o Packaging changes:
26306 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
26307 installer bundles. See
26308 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
26309 for details of what's new in Vidalia 0.2.3.
26310 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
26311 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
26312 configuration file, rather than the old Privoxy.
26313 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
26314 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
26315 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
26316 better compatibility with OS X 10.6, aka Snow Leopard.
26317 - OS X Vidalia Bundle: The multi-package installer is now replaced
26318 by a simple drag and drop to the /Applications folder. This change
26319 occurred with the upgrade to Vidalia 0.2.3.
26322 Changes in version 0.2.1.19 - 2009-07-28
26323 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
26324 services on Tor 0.2.1.3-alpha through 0.2.1.18.
26327 - Make accessing hidden services on 0.2.1.x work right again.
26328 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
26329 part of patch provided by "optimist".
26332 - When a relay/bridge is writing out its identity key fingerprint to
26333 the "fingerprint" file and to its logs, write it without spaces. Now
26334 it will look like the fingerprints in our bridges documentation,
26335 and confuse fewer users.
26338 - Relays no longer publish a new server descriptor if they change
26339 their MaxAdvertisedBandwidth config option but it doesn't end up
26340 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
26341 fixes bug 1026. Patch from Sebastian.
26342 - Avoid leaking memory every time we get a create cell but we have
26343 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
26344 fixes bug 1034. Reported by BarkerJr.
26347 Changes in version 0.2.1.18 - 2009-07-24
26348 Tor 0.2.1.18 lays the foundations for performance improvements,
26349 adds status events to help users diagnose bootstrap problems, adds
26350 optional authentication/authorization for hidden services, fixes a
26351 variety of potential anonymity problems, and includes a huge pile of
26352 other features and bug fixes.
26355 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
26358 Changes in version 0.2.1.17-rc - 2009-07-07
26359 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
26360 candidate for the 0.2.1.x series. It lays the groundwork for further
26361 client performance improvements, and also fixes a big bug with directory
26362 authorities that were causing them to assign Guard and Stable flags
26365 The Windows bundles also finally include the geoip database that we
26366 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
26367 should actually install Torbutton rather than giving you a cryptic
26368 failure message (oops).
26371 - Clients now use the bandwidth values in the consensus, rather than
26372 the bandwidth values in each relay descriptor. This approach opens
26373 the door to more accurate bandwidth estimates once the directory
26374 authorities start doing active measurements. Implements more of
26378 - When Tor clients restart after 1-5 days, they discard all their
26379 cached descriptors as too old, but they still use the cached
26380 consensus document. This approach is good for robustness, but
26381 bad for performance: since they don't know any bandwidths, they
26382 end up choosing at random rather than weighting their choice by
26383 speed. Fixed by the above feature of putting bandwidths in the
26384 consensus. Bugfix on 0.2.0.x.
26385 - Directory authorities were neglecting to mark relays down in their
26386 internal histories if the relays fall off the routerlist without
26387 ever being found unreachable. So there were relays in the histories
26388 that haven't been seen for eight months, and are listed as being
26389 up for eight months. This wreaked havoc on the "median wfu"
26390 and "median mtbf" calculations, in turn making Guard and Stable
26391 flags very wrong, hurting network performance. Fixes bugs 696 and
26392 969. Bugfix on 0.2.0.6-alpha.
26395 - Serve the DirPortFrontPage page even when we have been approaching
26396 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
26397 - The control port would close the connection before flushing long
26398 replies, such as the network consensus, if a QUIT command was issued
26399 before the reply had completed. Now, the control port flushes all
26400 pending replies before closing the connection. Also fixed a spurious
26401 warning when a QUIT command is issued after a malformed or rejected
26402 AUTHENTICATE command, but before the connection was closed. Patch
26403 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
26404 - When we can't find an intro key for a v2 hidden service descriptor,
26405 fall back to the v0 hidden service descriptor and log a bug message.
26406 Workaround for bug 1024.
26407 - Fix a log message that did not respect the SafeLogging option.
26411 - If we're a relay and we change our IP address, be more verbose
26412 about the reason that made us change. Should help track down
26413 further bugs for relays on dynamic IP addresses.
26416 Changes in version 0.2.0.35 - 2009-06-24
26418 - Avoid crashing in the presence of certain malformed descriptors.
26419 Found by lark, and by automated fuzzing.
26420 - Fix an edge case where a malicious exit relay could convince a
26421 controller that the client's DNS question resolves to an internal IP
26422 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
26425 - Finally fix the bug where dynamic-IP relays disappear when their
26426 IP address changes: directory mirrors were mistakenly telling
26427 them their old address if they asked via begin_dir, so they
26428 never got an accurate answer about their new address, so they
26429 just vanished after a day. For belt-and-suspenders, relays that
26430 don't set Address in their config now avoid using begin_dir for
26431 all direct connections. Should fix bugs 827, 883, and 900.
26432 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
26433 that would occur on some exit nodes when DNS failures and timeouts
26434 occurred in certain patterns. Fix for bug 957.
26437 - When starting with a cache over a few days old, do not leak
26438 memory for the obsolete router descriptors in it. Bugfix on
26439 0.2.0.33; fixes bug 672.
26440 - Hidden service clients didn't use a cached service descriptor that
26441 was older than 15 minutes, but wouldn't fetch a new one either,
26442 because there was already one in the cache. Now, fetch a v2
26443 descriptor unless the same descriptor was added to the cache within
26444 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
26447 Changes in version 0.2.1.16-rc - 2009-06-20
26448 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
26449 a bunch of minor bugs.
26452 - Fix an edge case where a malicious exit relay could convince a
26453 controller that the client's DNS question resolves to an internal IP
26454 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
26456 o Major performance improvements (on 0.2.0.x):
26457 - Disable and refactor some debugging checks that forced a linear scan
26458 over the whole server-side DNS cache. These accounted for over 50%
26459 of CPU time on a relatively busy exit node's gprof profile. Found
26461 - Disable some debugging checks that appeared in exit node profile
26465 - Update to the "June 3 2009" ip-to-country file.
26466 - Do not have tor-resolve automatically refuse all .onion addresses;
26467 if AutomapHostsOnResolve is set in your torrc, this will work fine.
26469 o Minor bugfixes (on 0.2.0.x):
26470 - Log correct error messages for DNS-related network errors on
26472 - Fix a race condition that could cause crashes or memory corruption
26473 when running as a server with a controller listening for log
26475 - Avoid crashing when we have a policy specified in a DirPolicy or
26476 SocksPolicy or ReachableAddresses option with ports set on it,
26477 and we re-load the policy. May fix bug 996.
26478 - Hidden service clients didn't use a cached service descriptor that
26479 was older than 15 minutes, but wouldn't fetch a new one either,
26480 because there was already one in the cache. Now, fetch a v2
26481 descriptor unless the same descriptor was added to the cache within
26482 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
26484 o Minor bugfixes (on 0.2.1.x):
26485 - Don't warn users about low port and hibernation mix when they
26486 provide a *ListenAddress directive to fix that. Bugfix on
26488 - When switching back and forth between bridge mode, do not start
26489 gathering GeoIP data until two hours have passed.
26490 - Do not complain that the user has requested an excluded node as
26491 an exit when the node is not really an exit. This could happen
26492 because the circuit was for testing, or an introduction point.
26496 Changes in version 0.2.1.15-rc - 2009-05-25
26497 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
26498 series. It fixes a major bug on fast exit relays, as well as a variety
26499 of more minor bugs.
26501 o Major bugfixes (on 0.2.0.x):
26502 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
26503 that would occur on some exit nodes when DNS failures and timeouts
26504 occurred in certain patterns. Fix for bug 957.
26506 o Minor bugfixes (on 0.2.0.x):
26507 - Actually return -1 in the error case for read_bandwidth_usage().
26508 Harmless bug, since we currently don't care about the return value
26509 anywhere. Bugfix on 0.2.0.9-alpha.
26510 - Provide a more useful log message if bug 977 (related to buffer
26511 freelists) ever reappears, and do not crash right away.
26512 - Fix an assertion failure on 64-bit platforms when we allocated
26513 memory right up to the end of a memarea, then realigned the memory
26514 one step beyond the end. Fixes a possible cause of bug 930.
26515 - Protect the count of open sockets with a mutex, so we can't
26516 corrupt it when two threads are closing or opening sockets at once.
26517 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
26518 - Don't allow a bridge to publish its router descriptor to a
26519 non-bridge directory authority. Fixes part of bug 932.
26520 - When we change to or from being a bridge, reset our counts of
26521 client usage by country. Fixes bug 932.
26522 - Fix a bug that made stream bandwidth get misreported to the
26524 - Stop using malloc_usable_size() to use more area than we had
26525 actually allocated: it was safe, but made valgrind really unhappy.
26526 - Fix a memory leak when v3 directory authorities load their keys
26527 and cert from disk. Bugfix on 0.2.0.1-alpha.
26529 o Minor bugfixes (on 0.2.1.x):
26530 - Fix use of freed memory when deciding to mark a non-addable
26531 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
26534 Changes in version 0.2.1.14-rc - 2009-04-12
26535 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
26536 series. It begins fixing some major performance problems, and also
26537 finally addresses the bug that was causing relays on dynamic IP
26538 addresses to fall out of the directory.
26541 - Clients replace entry guards that were chosen more than a few months
26542 ago. This change should significantly improve client performance,
26543 especially once more people upgrade, since relays that have been
26544 a guard for a long time are currently overloaded.
26546 o Major bugfixes (on 0.2.0):
26547 - Finally fix the bug where dynamic-IP relays disappear when their
26548 IP address changes: directory mirrors were mistakenly telling
26549 them their old address if they asked via begin_dir, so they
26550 never got an accurate answer about their new address, so they
26551 just vanished after a day. For belt-and-suspenders, relays that
26552 don't set Address in their config now avoid using begin_dir for
26553 all direct connections. Should fix bugs 827, 883, and 900.
26554 - Relays were falling out of the networkstatus consensus for
26555 part of a day if they changed their local config but the
26556 authorities discarded their new descriptor as "not sufficiently
26557 different". Now directory authorities accept a descriptor as changed
26558 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
26559 patch by Sebastian.
26560 - Avoid crashing in the presence of certain malformed descriptors.
26561 Found by lark, and by automated fuzzing.
26564 - When generating circuit events with verbose nicknames for
26565 controllers, try harder to look up nicknames for routers on a
26566 circuit. (Previously, we would look in the router descriptors we had
26567 for nicknames, but not in the consensus.) Partial fix for bug 941.
26568 - If the bridge config line doesn't specify a port, assume 443.
26569 This makes bridge lines a bit smaller and easier for users to
26571 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
26572 bytes (aka 20KB/s), to match our documentation. Also update
26573 directory authorities so they always assign the Fast flag to relays
26574 with 20KB/s of capacity. Now people running relays won't suddenly
26575 find themselves not seeing any use, if the network gets faster
26577 - Update to the "April 3 2009" ip-to-country file.
26580 - Avoid trying to print raw memory to the logs when we decide to
26581 give up on downloading a given relay descriptor. Bugfix on
26583 - In tor-resolve, when the Tor client to use is specified by
26584 <hostname>:<port>, actually use the specified port rather than
26585 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
26586 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
26587 - When starting with a cache over a few days old, do not leak
26588 memory for the obsolete router descriptors in it. Bugfix on
26590 - Avoid double-free on list of successfully uploaded hidden
26591 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
26592 - Change memarea_strndup() implementation to work even when
26593 duplicating a string at the end of a page. This bug was
26594 harmless for now, but could have meant crashes later. Fix by
26595 lark. Bugfix on 0.2.1.1-alpha.
26596 - Limit uploaded directory documents to be 16M rather than 500K.
26597 The directory authorities were refusing v3 consensus votes from
26598 other authorities, since the votes are now 504K. Fixes bug 959;
26599 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
26600 - Directory authorities should never send a 503 "busy" response to
26601 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
26605 Changes in version 0.2.1.13-alpha - 2009-03-09
26606 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
26607 cleanups. We're finally getting close to a release candidate.
26610 - Correctly update the list of which countries we exclude as
26611 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
26612 lark. Bugfix on 0.2.1.6-alpha.
26614 o Minor bugfixes (on 0.2.0.x and earlier):
26615 - Automatically detect MacOSX versions earlier than 10.4.0, and
26616 disable kqueue from inside Tor when running with these versions.
26617 We previously did this from the startup script, but that was no
26618 help to people who didn't use the startup script. Resolves bug 863.
26619 - When we had picked an exit node for a connection, but marked it as
26620 "optional", and it turned out we had no onion key for the exit,
26621 stop wanting that exit and try again. This situation may not
26622 be possible now, but will probably become feasible with proposal
26623 158. Spotted by rovv. Fixes another case of bug 752.
26624 - Clients no longer cache certificates for authorities they do not
26625 recognize. Bugfix on 0.2.0.9-alpha.
26626 - When we can't transmit a DNS request due to a network error, retry
26627 it after a while, and eventually transmit a failing response to
26628 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
26629 - If the controller claimed responsibility for a stream, but that
26630 stream never finished making its connection, it would live
26631 forever in circuit_wait state. Now we close it after SocksTimeout
26632 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
26633 - Drop begin cells to a hidden service if they come from the middle
26634 of a circuit. Patch from lark.
26635 - When we erroneously receive two EXTEND cells for the same circuit
26636 ID on the same connection, drop the second. Patch from lark.
26637 - Fix a crash that occurs on exit nodes when a nameserver request
26638 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
26639 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
26641 - Do not assume that a stack-allocated character array will be
26642 64-bit aligned on platforms that demand that uint64_t access is
26643 aligned. Possible fix for bug 604.
26644 - Parse dates and IPv4 addresses in a locale- and libc-independent
26645 manner, to avoid platform-dependent behavior on malformed input.
26646 - Build correctly when configured to build outside the main source
26647 path. Patch from Michael Gold.
26648 - We were already rejecting relay begin cells with destination port
26649 of 0. Now also reject extend cells with destination port or address
26650 of 0. Suggested by lark.
26652 o Minor bugfixes (on 0.2.1.x):
26653 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
26654 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
26655 - If we're an exit node, scrub the IP address to which we are exiting
26656 in the logs. Bugfix on 0.2.1.8-alpha.
26659 - On Linux, use the prctl call to re-enable core dumps when the user
26661 - New controller event NEWCONSENSUS that lists the networkstatus
26662 lines for every recommended relay. Now controllers like Torflow
26663 can keep up-to-date on which relays they should be using.
26664 - Update to the "February 26 2009" ip-to-country file.
26667 Changes in version 0.2.0.34 - 2009-02-08
26668 Tor 0.2.0.34 features several more security-related fixes. You should
26669 upgrade, especially if you run an exit relay (remote crash) or a
26670 directory authority (remote infinite loop), or you're on an older
26671 (pre-XP) or not-recently-patched Windows (remote exploit).
26673 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
26674 have many known flaws, and nobody should be using them. You should
26675 upgrade. If you're using a Linux or BSD and its packages are obsolete,
26676 stop using those packages and upgrade anyway.
26679 - Fix an infinite-loop bug on handling corrupt votes under certain
26680 circumstances. Bugfix on 0.2.0.8-alpha.
26681 - Fix a temporary DoS vulnerability that could be performed by
26682 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
26683 - Avoid a potential crash on exit nodes when processing malformed
26684 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
26685 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
26686 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
26689 - Fix compilation on systems where time_t is a 64-bit integer.
26690 Patch from Matthias Drochner.
26691 - Don't consider expiring already-closed client connections. Fixes
26692 bug 893. Bugfix on 0.0.2pre20.
26695 Changes in version 0.2.1.12-alpha - 2009-02-08
26696 Tor 0.2.1.12-alpha features several more security-related fixes. You
26697 should upgrade, especially if you run an exit relay (remote crash) or
26698 a directory authority (remote infinite loop), or you're on an older
26699 (pre-XP) or not-recently-patched Windows (remote exploit). It also
26700 includes a big pile of minor bugfixes and cleanups.
26703 - Fix an infinite-loop bug on handling corrupt votes under certain
26704 circumstances. Bugfix on 0.2.0.8-alpha.
26705 - Fix a temporary DoS vulnerability that could be performed by
26706 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
26707 - Avoid a potential crash on exit nodes when processing malformed
26708 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
26711 - Let controllers actually ask for the "clients_seen" event for
26712 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
26713 reported by Matt Edman.
26714 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
26716 - Fix a bug in address parsing that was preventing bridges or hidden
26717 service targets from being at IPv6 addresses.
26718 - Solve a bug that kept hardware crypto acceleration from getting
26719 enabled when accounting was turned on. Fixes bug 907. Bugfix on
26721 - Remove a bash-ism from configure.in to build properly on non-Linux
26722 platforms. Bugfix on 0.2.1.1-alpha.
26723 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
26724 headers. Bugfix on 0.2.0.10-alpha.
26725 - Don't consider expiring already-closed client connections. Fixes
26726 bug 893. Bugfix on 0.0.2pre20.
26727 - Fix another interesting corner-case of bug 891 spotted by rovv:
26728 Previously, if two hosts had different amounts of clock drift, and
26729 one of them created a new connection with just the wrong timing,
26730 the other might decide to deprecate the new connection erroneously.
26731 Bugfix on 0.1.1.13-alpha.
26732 - Resolve a very rare crash bug that could occur when the user forced
26733 a nameserver reconfiguration during the middle of a nameserver
26734 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
26735 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
26736 Bugfix on 0.2.1.7-alpha.
26737 - If we're using bridges and our network goes away, be more willing
26738 to forgive our bridges and try again when we get an application
26739 request. Bugfix on 0.2.0.x.
26742 - Support platforms where time_t is 64 bits long. (Congratulations,
26743 NetBSD!) Patch from Matthias Drochner.
26744 - Add a 'getinfo status/clients-seen' controller command, in case
26745 controllers want to hear clients_seen events but connect late.
26748 - Disable GCC's strict alias optimization by default, to avoid the
26749 likelihood of its introducing subtle bugs whenever our code violates
26750 the letter of C99's alias rules.
26753 Changes in version 0.2.0.33 - 2009-01-21
26754 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
26755 useful to users. It also finally fixes a bug where a relay or client
26756 that's been off for many days would take a long time to bootstrap.
26758 This update also fixes an important security-related bug reported by
26759 Ilja van Sprundel. You should upgrade. (We'll send out more details
26760 about the bug once people have had some time to upgrade.)
26763 - Fix a heap-corruption bug that may be remotely triggerable on
26764 some platforms. Reported by Ilja van Sprundel.
26767 - When a stream at an exit relay is in state "resolving" or
26768 "connecting" and it receives an "end" relay cell, the exit relay
26769 would silently ignore the end cell and not close the stream. If
26770 the client never closes the circuit, then the exit relay never
26771 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
26772 reported by "wood".
26773 - When sending CREATED cells back for a given circuit, use a 64-bit
26774 connection ID to find the right connection, rather than an addr:port
26775 combination. Now that we can have multiple OR connections between
26776 the same ORs, it is no longer possible to use addr:port to uniquely
26777 identify a connection.
26778 - Bridge relays that had DirPort set to 0 would stop fetching
26779 descriptors shortly after startup, and then briefly resume
26780 after a new bandwidth test and/or after publishing a new bridge
26781 descriptor. Bridge users that try to bootstrap from them would
26782 get a recent networkstatus but would get descriptors from up to
26783 18 hours earlier, meaning most of the descriptors were obsolete
26784 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
26785 - Prevent bridge relays from serving their 'extrainfo' document
26786 to anybody who asks, now that extrainfo docs include potentially
26787 sensitive aggregated client geoip summaries. Bugfix on
26789 - If the cached networkstatus consensus is more than five days old,
26790 discard it rather than trying to use it. In theory it could be
26791 useful because it lists alternate directory mirrors, but in practice
26792 it just means we spend many minutes trying directory mirrors that
26793 are long gone from the network. Also discard router descriptors as
26794 we load them if they are more than five days old, since the onion
26795 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
26798 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
26799 could make gcc generate non-functional binary search code. Bugfix
26801 - Build correctly on platforms without socklen_t.
26802 - Compile without warnings on solaris.
26803 - Avoid potential crash on internal error during signature collection.
26804 Fixes bug 864. Patch from rovv.
26805 - Correct handling of possible malformed authority signing key
26806 certificates with internal signature types. Fixes bug 880.
26807 Bugfix on 0.2.0.3-alpha.
26808 - Fix a hard-to-trigger resource leak when logging credential status.
26810 - When we can't initialize DNS because the network is down, do not
26811 automatically stop Tor from starting. Instead, we retry failed
26812 dns_init() every 10 minutes, and change the exit policy to reject
26813 *:* until one succeeds. Fixes bug 691.
26814 - Use 64 bits instead of 32 bits for connection identifiers used with
26815 the controller protocol, to greatly reduce risk of identifier reuse.
26816 - When we're choosing an exit node for a circuit, and we have
26817 no pending streams, choose a good general exit rather than one that
26818 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
26819 - Fix another case of assuming, when a specific exit is requested,
26820 that we know more than the user about what hosts it allows.
26821 Fixes one case of bug 752. Patch from rovv.
26822 - Clip the MaxCircuitDirtiness config option to a minimum of 10
26823 seconds. Warn the user if lower values are given in the
26824 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
26825 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
26826 user if lower values are given in the configuration. Bugfix on
26827 0.1.1.17-rc. Patch by Sebastian.
26828 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
26829 the cache because we already had a v0 descriptor with the same ID.
26830 Bugfix on 0.2.0.18-alpha.
26831 - Fix a race condition when freeing keys shared between main thread
26832 and CPU workers that could result in a memory leak. Bugfix on
26833 0.1.0.1-rc. Fixes bug 889.
26834 - Send a valid END cell back when a client tries to connect to a
26835 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
26836 840. Patch from rovv.
26837 - Check which hops rendezvous stream cells are associated with to
26838 prevent possible guess-the-streamid injection attacks from
26839 intermediate hops. Fixes another case of bug 446. Based on patch
26841 - If a broken client asks a non-exit router to connect somewhere,
26842 do not even do the DNS lookup before rejecting the connection.
26843 Fixes another case of bug 619. Patch from rovv.
26844 - When a relay gets a create cell it can't decrypt (e.g. because it's
26845 using the wrong onion key), we were dropping it and letting the
26846 client time out. Now actually answer with a destroy cell. Fixes
26847 bug 904. Bugfix on 0.0.2pre8.
26849 o Minor bugfixes (hidden services):
26850 - Do not throw away existing introduction points on SIGHUP. Bugfix on
26851 0.0.6pre1. Patch by Karsten. Fixes bug 874.
26854 - Report the case where all signatures in a detached set are rejected
26855 differently than the case where there is an error handling the
26857 - When we realize that another process has modified our cached
26858 descriptors, print out a more useful error message rather than
26859 triggering an assertion. Fixes bug 885. Patch from Karsten.
26860 - Implement the 0x20 hack to better resist DNS poisoning: set the
26861 case on outgoing DNS requests randomly, and reject responses that do
26862 not match the case correctly. This logic can be disabled with the
26863 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
26864 of servers that do not reliably preserve case in replies. See
26865 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
26867 - Check DNS replies for more matching fields to better resist DNS
26869 - Never use OpenSSL compression: it wastes RAM and CPU trying to
26870 compress cells, which are basically all encrypted, compressed, or
26874 Changes in version 0.2.1.11-alpha - 2009-01-20
26875 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
26876 week it will take a long time to bootstrap again" bug. It also fixes
26877 an important security-related bug reported by Ilja van Sprundel. You
26878 should upgrade. (We'll send out more details about the bug once people
26879 have had some time to upgrade.)
26882 - Fix a heap-corruption bug that may be remotely triggerable on
26883 some platforms. Reported by Ilja van Sprundel.
26886 - Discard router descriptors as we load them if they are more than
26887 five days old. Otherwise if Tor is off for a long time and then
26888 starts with cached descriptors, it will try to use the onion
26889 keys in those obsolete descriptors when building circuits. Bugfix
26890 on 0.2.0.x. Fixes bug 887.
26893 - Try to make sure that the version of Libevent we're running with
26894 is binary-compatible with the one we built with. May address bug
26896 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
26897 for bug 905. Bugfix on 0.2.1.7-alpha.
26898 - Add a new --enable-local-appdata configuration switch to change
26899 the default location of the datadir on win32 from APPDATA to
26900 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
26901 entirely. Patch from coderman.
26904 - Make outbound DNS packets respect the OutboundBindAddress setting.
26905 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
26906 - When our circuit fails at the first hop (e.g. we get a destroy
26907 cell back), avoid using that OR connection anymore, and also
26908 tell all the one-hop directory requests waiting for it that they
26909 should fail. Bugfix on 0.2.1.3-alpha.
26910 - In the torify(1) manpage, mention that tsocks will leak your
26914 Changes in version 0.2.1.10-alpha - 2009-01-06
26915 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
26916 would make the bridge relay not so useful if it had DirPort set to 0,
26917 and one that could let an attacker learn a little bit of information
26918 about the bridge's users), and a bug that would cause your Tor relay
26919 to ignore a circuit create request it can't decrypt (rather than reply
26920 with an error). It also fixes a wide variety of other bugs.
26923 - If the cached networkstatus consensus is more than five days old,
26924 discard it rather than trying to use it. In theory it could
26925 be useful because it lists alternate directory mirrors, but in
26926 practice it just means we spend many minutes trying directory
26927 mirrors that are long gone from the network. Helps bug 887 a bit;
26929 - Bridge relays that had DirPort set to 0 would stop fetching
26930 descriptors shortly after startup, and then briefly resume
26931 after a new bandwidth test and/or after publishing a new bridge
26932 descriptor. Bridge users that try to bootstrap from them would
26933 get a recent networkstatus but would get descriptors from up to
26934 18 hours earlier, meaning most of the descriptors were obsolete
26935 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
26936 - Prevent bridge relays from serving their 'extrainfo' document
26937 to anybody who asks, now that extrainfo docs include potentially
26938 sensitive aggregated client geoip summaries. Bugfix on
26942 - New controller event "clients_seen" to report a geoip-based summary
26943 of which countries we've seen clients from recently. Now controllers
26944 like Vidalia can show bridge operators that they're actually making
26946 - Build correctly against versions of OpenSSL 0.9.8 or later built
26947 without support for deprecated functions.
26948 - Update to the "December 19 2008" ip-to-country file.
26950 o Minor bugfixes (on 0.2.0.x):
26951 - Authorities now vote for the Stable flag for any router whose
26952 weighted MTBF is at least 5 days, regardless of the mean MTBF.
26953 - Do not remove routers as too old if we do not have any consensus
26954 document. Bugfix on 0.2.0.7-alpha.
26955 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
26956 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
26957 - When an exit relay resolves a stream address to a local IP address,
26958 do not just keep retrying that same exit relay over and
26959 over. Instead, just close the stream. Addresses bug 872. Bugfix
26960 on 0.2.0.32. Patch from rovv.
26961 - If a hidden service sends us an END cell, do not consider
26962 retrying the connection; just close it. Patch from rovv.
26963 - When we made bridge authorities stop serving bridge descriptors over
26964 unencrypted links, we also broke DirPort reachability testing for
26965 bridges. So bridges with a non-zero DirPort were printing spurious
26966 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
26967 - When a relay gets a create cell it can't decrypt (e.g. because it's
26968 using the wrong onion key), we were dropping it and letting the
26969 client time out. Now actually answer with a destroy cell. Fixes
26970 bug 904. Bugfix on 0.0.2pre8.
26971 - Squeeze 2-5% out of client performance (according to oprofile) by
26972 improving the implementation of some policy-manipulation functions.
26974 o Minor bugfixes (on 0.2.1.x):
26975 - Make get_interface_address() function work properly again; stop
26976 guessing the wrong parts of our address as our address.
26977 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
26978 send on that circuit. Otherwise we might violate the proposal-110
26979 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
26981 - When we're sending non-EXTEND cells to the first hop in a circuit,
26982 for example to use an encrypted directory connection, we don't need
26983 to use RELAY_EARLY cells: the first hop knows what kind of cell
26984 it is, and nobody else can even see the cell type. Conserving
26985 RELAY_EARLY cells makes it easier to cannibalize circuits like
26987 - Stop logging nameserver addresses in reverse order.
26988 - If we are retrying a directory download slowly over and over, do
26989 not automatically give up after the 254th failure. Bugfix on
26991 - Resume reporting accurate "stream end" reasons to the local control
26992 port. They were lost in the changes for Proposal 148. Bugfix on
26995 o Deprecated and removed features:
26996 - The old "tor --version --version" command, which would print out
26997 the subversion "Id" of most of the source files, is now removed. It
26998 turned out to be less useful than we'd expected, and harder to
27001 o Code simplifications and refactoring:
27002 - Change our header file guard macros to be less likely to conflict
27003 with system headers. Adam Langley noticed that we were conflicting
27004 with log.h on Android.
27005 - Tool-assisted documentation cleanup. Nearly every function or
27006 static variable in Tor should have its own documentation now.
27009 Changes in version 0.2.1.9-alpha - 2008-12-25
27010 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
27012 o New directory authorities:
27013 - gabelmoo (the authority run by Karsten Loesing) now has a new
27017 - Never use a connection with a mismatched address to extend a
27018 circuit, unless that connection is canonical. A canonical
27019 connection is one whose address is authenticated by the router's
27020 identity key, either in a NETINFO cell or in a router descriptor.
27021 - Avoid a possible memory corruption bug when receiving hidden service
27022 descriptors. Bugfix on 0.2.1.6-alpha.
27025 - Fix a logic error that would automatically reject all but the first
27026 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
27027 part of bug 813/868. Bug spotted by coderman.
27028 - When a stream at an exit relay is in state "resolving" or
27029 "connecting" and it receives an "end" relay cell, the exit relay
27030 would silently ignore the end cell and not close the stream. If
27031 the client never closes the circuit, then the exit relay never
27032 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
27033 reported by "wood".
27034 - When we can't initialize DNS because the network is down, do not
27035 automatically stop Tor from starting. Instead, retry failed
27036 dns_init() every 10 minutes, and change the exit policy to reject
27037 *:* until one succeeds. Fixes bug 691.
27040 - Give a better error message when an overzealous init script says
27041 "sudo -u username tor --user username". Makes Bug 882 easier for
27043 - When a directory authority gives us a new guess for our IP address,
27044 log which authority we used. Hopefully this will help us debug
27045 the recent complaints about bad IP address guesses.
27046 - Detect svn revision properly when we're using git-svn.
27047 - Try not to open more than one descriptor-downloading connection
27048 to an authority at once. This should reduce load on directory
27049 authorities. Fixes bug 366.
27050 - Add cross-certification to newly generated certificates, so that
27051 a signing key is enough information to look up a certificate.
27052 Partial implementation of proposal 157.
27053 - Start serving certificates by <identity digest, signing key digest>
27054 pairs. Partial implementation of proposal 157.
27055 - Clients now never report any stream end reason except 'MISC'.
27056 Implements proposal 148.
27057 - On platforms with a maximum syslog string length, truncate syslog
27058 messages to that length ourselves, rather than relying on the
27059 system to do it for us.
27060 - Optimize out calls to time(NULL) that occur for every IO operation,
27061 or for every cell. On systems where time() is a slow syscall,
27062 this fix will be slightly helpful.
27063 - Exit servers can now answer resolve requests for ip6.arpa addresses.
27064 - When we download a descriptor that we then immediately (as
27065 a directory authority) reject, do not retry downloading it right
27066 away. Should save some bandwidth on authorities. Fix for bug
27067 888. Patch by Sebastian Hahn.
27068 - When a download gets us zero good descriptors, do not notify
27069 Tor that new directory information has arrived.
27070 - Avoid some nasty corner cases in the logic for marking connections
27071 as too old or obsolete or noncanonical for circuits. Partial
27074 o Minor features (controller):
27075 - New CONSENSUS_ARRIVED event to note when a new consensus has
27076 been fetched and validated.
27077 - When we realize that another process has modified our cached
27078 descriptors file, print out a more useful error message rather
27079 than triggering an assertion. Fixes bug 885. Patch from Karsten.
27080 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
27081 controllers to prevent SIGHUP from reloading the
27082 configuration. Fixes bug 856.
27085 - Resume using the correct "REASON=" stream when telling the
27086 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
27087 - When a canonical connection appears later in our internal list
27088 than a noncanonical one for a given OR ID, always use the
27089 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
27091 - Clip the MaxCircuitDirtiness config option to a minimum of 10
27092 seconds. Warn the user if lower values are given in the
27093 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
27094 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
27095 user if lower values are given in the configuration. Bugfix on
27096 0.1.1.17-rc. Patch by Sebastian.
27097 - Fix a race condition when freeing keys shared between main thread
27098 and CPU workers that could result in a memory leak. Bugfix on
27099 0.1.0.1-rc. Fixes bug 889.
27101 o Minor bugfixes (hidden services):
27102 - Do not throw away existing introduction points on SIGHUP (bugfix on
27103 0.0.6pre1); also, do not stall hidden services because we're
27104 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
27105 by John Brooks. Patch by Karsten. Fixes bug 874.
27106 - Fix a memory leak when we decline to add a v2 rendezvous
27107 descriptor to the cache because we already had a v0 descriptor
27108 with the same ID. Bugfix on 0.2.0.18-alpha.
27110 o Deprecated and removed features:
27111 - RedirectExits has been removed. It was deprecated since
27113 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
27114 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
27115 - Cell pools are now always enabled; --disable-cell-pools is ignored.
27117 o Code simplifications and refactoring:
27118 - Rename the confusing or_is_obsolete field to the more appropriate
27119 is_bad_for_new_circs, and move it to or_connection_t where it
27121 - Move edge-only flags from connection_t to edge_connection_t: not
27122 only is this better coding, but on machines of plausible alignment,
27123 it should save 4-8 bytes per connection_t. "Every little bit helps."
27124 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
27125 for consistency; keep old option working for backward compatibility.
27126 - Simplify the code for finding connections to use for a circuit.
27129 Changes in version 0.2.1.8-alpha - 2008-12-08
27130 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
27131 builds better on unusual platforms like Solaris and old OS X, and
27132 fixes a variety of other issues.
27135 - New DirPortFrontPage option that takes an html file and publishes
27136 it as "/" on the DirPort. Now relay operators can provide a
27137 disclaimer without needing to set up a separate webserver. There's
27138 a sample disclaimer in contrib/tor-exit-notice.html.
27141 - When the client is choosing entry guards, now it selects at most
27142 one guard from a given relay family. Otherwise we could end up with
27143 all of our entry points into the network run by the same operator.
27144 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
27147 - Fix a DOS opportunity during the voting signature collection process
27148 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
27149 - Fix a possible segfault when establishing an exit connection. Bugfix
27153 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
27155 - Made Tor a little less aggressive about deleting expired
27156 certificates. Partial fix for bug 854.
27157 - Stop doing unaligned memory access that generated bus errors on
27158 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
27159 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
27160 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
27161 - Make USR2 log-level switch take effect immediately. Bugfix on
27163 - If one win32 nameserver fails to get added, continue adding the
27164 rest, and don't automatically fail.
27165 - Use fcntl() for locking when flock() is not available. Should fix
27166 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
27167 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
27168 could make gcc generate non-functional binary search code. Bugfix
27170 - Build correctly on platforms without socklen_t.
27171 - Avoid potential crash on internal error during signature collection.
27172 Fixes bug 864. Patch from rovv.
27173 - Do not use C's stdio library for writing to log files. This will
27174 improve logging performance by a minute amount, and will stop
27175 leaking fds when our disk is full. Fixes bug 861.
27176 - Stop erroneous use of O_APPEND in cases where we did not in fact
27177 want to re-seek to the end of a file before every last write().
27178 - Correct handling of possible malformed authority signing key
27179 certificates with internal signature types. Fixes bug 880. Bugfix
27181 - Fix a hard-to-trigger resource leak when logging credential status.
27185 - Directory mirrors no longer fetch the v1 directory or
27186 running-routers files. They are obsolete, and nobody asks for them
27187 anymore. This is the first step to making v1 authorities obsolete.
27189 o Minor features (controller):
27190 - Return circuit purposes in response to GETINFO circuit-status. Fixes
27194 Changes in version 0.2.0.32 - 2008-11-20
27195 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
27196 packages (and maybe other packages) noticed by Theo de Raadt, fixes
27197 a smaller security flaw that might allow an attacker to access local
27198 services, further improves hidden service performance, and fixes a
27199 variety of other issues.
27202 - The "User" and "Group" config options did not clear the
27203 supplementary group entries for the Tor process. The "User" option
27204 is now more robust, and we now set the groups to the specified
27205 user's primary group. The "Group" option is now ignored. For more
27206 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
27207 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
27208 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
27209 - The "ClientDNSRejectInternalAddresses" config option wasn't being
27210 consistently obeyed: if an exit relay refuses a stream because its
27211 exit policy doesn't allow it, we would remember what IP address
27212 the relay said the destination address resolves to, even if it's
27213 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
27216 - Fix a DOS opportunity during the voting signature collection process
27217 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
27219 o Major bugfixes (hidden services):
27220 - When fetching v0 and v2 rendezvous service descriptors in parallel,
27221 we were failing the whole hidden service request when the v0
27222 descriptor fetch fails, even if the v2 fetch is still pending and
27223 might succeed. Similarly, if the last v2 fetch fails, we were
27224 failing the whole hidden service request even if a v0 fetch is
27225 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
27226 - When extending a circuit to a hidden service directory to upload a
27227 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
27228 requests failed, because the router descriptor has not been
27229 downloaded yet. In these cases, do not attempt to upload the
27230 rendezvous descriptor, but wait until the router descriptor is
27231 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
27232 descriptor from a hidden service directory for which the router
27233 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
27237 - Fix several infrequent memory leaks spotted by Coverity.
27238 - When testing for libevent functions, set the LDFLAGS variable
27239 correctly. Found by Riastradh.
27240 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
27241 bootstrapping with tunneled directory connections. Bugfix on
27242 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
27243 - When asked to connect to A.B.exit:80, if we don't know the IP for A
27244 and we know that server B rejects most-but-not all connections to
27245 port 80, we would previously reject the connection. Now, we assume
27246 the user knows what they were asking for. Fixes bug 752. Bugfix
27247 on 0.0.9rc5. Diagnosed by BarkerJr.
27248 - If we overrun our per-second write limits a little, count this as
27249 having used up our write allocation for the second, and choke
27250 outgoing directory writes. Previously, we had only counted this when
27251 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
27252 Bugfix on 0.2.0.x (??).
27253 - Remove the old v2 directory authority 'lefkada' from the default
27254 list. It has been gone for many months.
27255 - Stop doing unaligned memory access that generated bus errors on
27256 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
27257 - Make USR2 log-level switch take effect immediately. Bugfix on
27260 o Minor bugfixes (controller):
27261 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
27262 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
27265 Changes in version 0.2.1.7-alpha - 2008-11-08
27266 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
27267 packages (and maybe other packages) noticed by Theo de Raadt, fixes
27268 a smaller security flaw that might allow an attacker to access local
27269 services, adds better defense against DNS poisoning attacks on exit
27270 relays, further improves hidden service performance, and fixes a
27271 variety of other issues.
27274 - The "ClientDNSRejectInternalAddresses" config option wasn't being
27275 consistently obeyed: if an exit relay refuses a stream because its
27276 exit policy doesn't allow it, we would remember what IP address
27277 the relay said the destination address resolves to, even if it's
27278 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
27279 - The "User" and "Group" config options did not clear the
27280 supplementary group entries for the Tor process. The "User" option
27281 is now more robust, and we now set the groups to the specified
27282 user's primary group. The "Group" option is now ignored. For more
27283 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
27284 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
27285 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
27286 - Do not use or believe expired v3 authority certificates. Patch
27287 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
27290 - Now NodeFamily and MyFamily config options allow spaces in
27291 identity fingerprints, so it's easier to paste them in.
27292 Suggested by Lucky Green.
27293 - Implement the 0x20 hack to better resist DNS poisoning: set the
27294 case on outgoing DNS requests randomly, and reject responses that do
27295 not match the case correctly. This logic can be disabled with the
27296 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
27297 of servers that do not reliably preserve case in replies. See
27298 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
27300 - Preserve case in replies to DNSPort requests in order to support
27301 the 0x20 hack for resisting DNS poisoning attacks.
27303 o Hidden service performance improvements:
27304 - When the client launches an introduction circuit, retry with a
27305 new circuit after 30 seconds rather than 60 seconds.
27306 - Launch a second client-side introduction circuit in parallel
27307 after a delay of 15 seconds (based on work by Christian Wilms).
27308 - Hidden services start out building five intro circuits rather
27309 than three, and when the first three finish they publish a service
27310 descriptor using those. Now we publish our service descriptor much
27311 faster after restart.
27314 - Minor fix in the warning messages when you're having problems
27315 bootstrapping; also, be more forgiving of bootstrap problems when
27316 we're still making incremental progress on a given bootstrap phase.
27317 - When we're choosing an exit node for a circuit, and we have
27318 no pending streams, choose a good general exit rather than one that
27319 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
27320 - Send a valid END cell back when a client tries to connect to a
27321 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
27322 840. Patch from rovv.
27323 - If a broken client asks a non-exit router to connect somewhere,
27324 do not even do the DNS lookup before rejecting the connection.
27325 Fixes another case of bug 619. Patch from rovv.
27326 - Fix another case of assuming, when a specific exit is requested,
27327 that we know more than the user about what hosts it allows.
27328 Fixes another case of bug 752. Patch from rovv.
27329 - Check which hops rendezvous stream cells are associated with to
27330 prevent possible guess-the-streamid injection attacks from
27331 intermediate hops. Fixes another case of bug 446. Based on patch
27333 - Avoid using a negative right-shift when comparing 32-bit
27334 addresses. Possible fix for bug 845 and bug 811.
27335 - Make the assert_circuit_ok() function work correctly on circuits that
27336 have already been marked for close.
27337 - Fix read-off-the-end-of-string error in unit tests when decoding
27338 introduction points.
27339 - Fix uninitialized size field for memory area allocation: may improve
27340 memory performance during directory parsing.
27341 - Treat duplicate certificate fetches as failures, so that we do
27342 not try to re-fetch an expired certificate over and over and over.
27343 - Do not say we're fetching a certificate when we'll in fact skip it
27344 because of a pending download.
27347 Changes in version 0.2.1.6-alpha - 2008-09-30
27348 Tor 0.2.1.6-alpha further improves performance and robustness of
27349 hidden services, starts work on supporting per-country relay selection,
27350 and fixes a variety of smaller issues.
27353 - Implement proposal 121: make it possible to build hidden services
27354 that only certain clients are allowed to connect to. This is
27355 enforced at several points, so that unauthorized clients are unable
27356 to send INTRODUCE cells to the service, or even (depending on the
27357 type of authentication) to learn introduction points. This feature
27358 raises the bar for certain kinds of active attacks against hidden
27359 services. Code by Karsten Loesing.
27360 - Relays now store and serve v2 hidden service descriptors by default,
27361 i.e., the new default value for HidServDirectoryV2 is 1. This is
27362 the last step in proposal 114, which aims to make hidden service
27363 lookups more reliable.
27364 - Start work to allow node restrictions to include country codes. The
27365 syntax to exclude nodes in a country with country code XX is
27366 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
27367 refinement to decide what config options should take priority if
27368 you ask to both use a particular node and exclude it.
27369 - Allow ExitNodes list to include IP ranges and country codes, just
27370 like the Exclude*Nodes lists. Patch from Robert Hogan.
27373 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
27374 Tor to fail to start if you had it configured to use a bridge
27375 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
27376 - When extending a circuit to a hidden service directory to upload a
27377 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
27378 requests failed, because the router descriptor had not been
27379 downloaded yet. In these cases, we now wait until the router
27380 descriptor is downloaded, and then retry. Likewise, clients
27381 now skip over a hidden service directory if they don't yet have
27382 its router descriptor, rather than futilely requesting it and
27383 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
27385 - When fetching v0 and v2 rendezvous service descriptors in parallel,
27386 we were failing the whole hidden service request when the v0
27387 descriptor fetch fails, even if the v2 fetch is still pending and
27388 might succeed. Similarly, if the last v2 fetch fails, we were
27389 failing the whole hidden service request even if a v0 fetch is
27390 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
27391 - DNS replies need to have names matching their requests, but
27392 these names should be in the questions section, not necessarily
27393 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
27396 - Update to the "September 1 2008" ip-to-country file.
27397 - Allow ports 465 and 587 in the default exit policy again. We had
27398 rejected them in 0.1.0.15, because back in 2005 they were commonly
27399 misconfigured and ended up as spam targets. We hear they are better
27400 locked down these days.
27401 - Use a lockfile to make sure that two Tor processes are not
27402 simultaneously running with the same datadir.
27403 - Serve the latest v3 networkstatus consensus via the control
27404 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
27405 - Better logging about stability/reliability calculations on directory
27407 - Drop the requirement to have an open dir port for storing and
27408 serving v2 hidden service descriptors.
27409 - Directory authorities now serve a /tor/dbg-stability.txt URL to
27410 help debug WFU and MTBF calculations.
27411 - Implement most of Proposal 152: allow specialized servers to permit
27412 single-hop circuits, and clients to use those servers to build
27413 single-hop circuits when using a specialized controller. Patch
27414 from Josh Albrecht. Resolves feature request 768.
27415 - Add a -p option to tor-resolve for specifying the SOCKS port: some
27416 people find host:port too confusing.
27417 - Make TrackHostExit mappings expire a while after their last use, not
27418 after their creation. Patch from Robert Hogan.
27419 - Provide circuit purposes along with circuit events to the controller.
27422 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
27424 - Fixed some memory leaks -- some quite frequent, some almost
27425 impossible to trigger -- based on results from Coverity.
27426 - When testing for libevent functions, set the LDFLAGS variable
27427 correctly. Found by Riastradh.
27428 - Fix an assertion bug in parsing policy-related options; possible fix
27430 - Catch and report a few more bootstrapping failure cases when Tor
27431 fails to establish a TCP connection. Cleanup on 0.2.1.x.
27432 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
27433 bootstrapping with tunneled directory connections. Bugfix on
27434 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
27435 - When asked to connect to A.B.exit:80, if we don't know the IP for A
27436 and we know that server B rejects most-but-not all connections to
27437 port 80, we would previously reject the connection. Now, we assume
27438 the user knows what they were asking for. Fixes bug 752. Bugfix
27439 on 0.0.9rc5. Diagnosed by BarkerJr.
27440 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
27441 service directories if they have no advertised dir port. Bugfix
27443 - If we overrun our per-second write limits a little, count this as
27444 having used up our write allocation for the second, and choke
27445 outgoing directory writes. Previously, we had only counted this when
27446 we had met our limits precisely. Fixes bug 824. Patch by rovv.
27447 Bugfix on 0.2.0.x (??).
27448 - Avoid a "0 divided by 0" calculation when calculating router uptime
27449 at directory authorities. Bugfix on 0.2.0.8-alpha.
27450 - Make DNS resolved controller events into "CLOSED", not
27451 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
27453 - Fix a bug where an unreachable relay would establish enough
27454 reachability testing circuits to do a bandwidth test -- if
27455 we already have a connection to the middle hop of the testing
27456 circuit, then it could establish the last hop by using the existing
27457 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
27458 circuits no longer use entry guards in 0.2.1.3-alpha.
27459 - If we have correct permissions on $datadir, we complain to stdout
27460 and fail to start. But dangerous permissions on
27461 $datadir/cached-status/ would cause us to open a log and complain
27462 there. Now complain to stdout and fail to start in both cases. Fixes
27463 bug 820, reported by seeess.
27464 - Remove the old v2 directory authority 'lefkada' from the default
27465 list. It has been gone for many months.
27467 o Code simplifications and refactoring:
27468 - Revise the connection_new functions so that a more typesafe variant
27469 exists. This will work better with Coverity, and let us find any
27470 actual mistakes we're making here.
27471 - Refactor unit testing logic so that dmalloc can be used sensibly
27472 with unit tests to check for memory leaks.
27473 - Move all hidden-service related fields from connection and circuit
27474 structure to substructures: this way they won't eat so much memory.
27477 Changes in version 0.2.0.31 - 2008-09-03
27478 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
27479 a big bug we're seeing where in rare cases traffic from one Tor stream
27480 gets mixed into another stream, and fixes a variety of smaller issues.
27483 - Make sure that two circuits can never exist on the same connection
27484 with the same circuit ID, even if one is marked for close. This
27485 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
27486 - Relays now reject risky extend cells: if the extend cell includes
27487 a digest of all zeroes, or asks to extend back to the relay that
27488 sent the extend cell, tear down the circuit. Ideas suggested
27490 - If not enough of our entry guards are available so we add a new
27491 one, we might use the new one even if it overlapped with the
27492 current circuit's exit relay (or its family). Anonymity bugfix
27493 pointed out by rovv.
27496 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
27497 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
27498 - Correctly detect the presence of the linux/netfilter_ipv4.h header
27499 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
27500 - Pick size of default geoip filename string correctly on windows.
27501 Fixes bug 806. Bugfix on 0.2.0.30.
27502 - Make the autoconf script accept the obsolete --with-ssl-dir
27503 option as an alias for the actually-working --with-openssl-dir
27504 option. Fix the help documentation to recommend --with-openssl-dir.
27505 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
27506 - When using the TransPort option on OpenBSD, and using the User
27507 option to change UID and drop privileges, make sure to open
27508 /dev/pf before dropping privileges. Fixes bug 782. Patch from
27509 Christopher Davis. Bugfix on 0.1.2.1-alpha.
27510 - Try to attach connections immediately upon receiving a RENDEZVOUS2
27511 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
27512 on the client side when connecting to a hidden service. Bugfix
27513 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
27514 - When closing an application-side connection because its circuit is
27515 getting torn down, generate the stream event correctly. Bugfix on
27516 0.1.2.x. Anonymous patch.
27519 Changes in version 0.2.1.5-alpha - 2008-08-31
27520 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
27521 in a lot of the infrastructure for adding authorization to hidden
27522 services, lays the groundwork for having clients read their load
27523 balancing information out of the networkstatus consensus rather than
27524 the individual router descriptors, addresses two potential anonymity
27525 issues, and fixes a variety of smaller issues.
27528 - Convert many internal address representations to optionally hold
27530 - Generate and accept IPv6 addresses in many protocol elements.
27531 - Make resolver code handle nameservers located at ipv6 addresses.
27532 - Begin implementation of proposal 121 ("Client authorization for
27533 hidden services"): configure hidden services with client
27534 authorization, publish descriptors for them, and configure
27535 authorization data for hidden services at clients. The next
27536 step is to actually access hidden services that perform client
27538 - More progress toward proposal 141: Network status consensus
27539 documents and votes now contain bandwidth information for each
27540 router and a summary of that router's exit policy. Eventually this
27541 will be used by clients so that they do not have to download every
27542 known descriptor before building circuits.
27544 o Major bugfixes (on 0.2.0.x and before):
27545 - When sending CREATED cells back for a given circuit, use a 64-bit
27546 connection ID to find the right connection, rather than an addr:port
27547 combination. Now that we can have multiple OR connections between
27548 the same ORs, it is no longer possible to use addr:port to uniquely
27549 identify a connection.
27550 - Relays now reject risky extend cells: if the extend cell includes
27551 a digest of all zeroes, or asks to extend back to the relay that
27552 sent the extend cell, tear down the circuit. Ideas suggested
27554 - If not enough of our entry guards are available so we add a new
27555 one, we might use the new one even if it overlapped with the
27556 current circuit's exit relay (or its family). Anonymity bugfix
27557 pointed out by rovv.
27560 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
27561 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
27562 - When using the TransPort option on OpenBSD, and using the User
27563 option to change UID and drop privileges, make sure to open /dev/pf
27564 before dropping privileges. Fixes bug 782. Patch from Christopher
27565 Davis. Bugfix on 0.1.2.1-alpha.
27566 - Correctly detect the presence of the linux/netfilter_ipv4.h header
27567 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
27568 - Add a missing safe_str() call for a debug log message.
27569 - Use 64 bits instead of 32 bits for connection identifiers used with
27570 the controller protocol, to greatly reduce risk of identifier reuse.
27571 - Make the autoconf script accept the obsolete --with-ssl-dir
27572 option as an alias for the actually-working --with-openssl-dir
27573 option. Fix the help documentation to recommend --with-openssl-dir.
27574 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
27577 - Rate-limit too-many-sockets messages: when they happen, they happen
27578 a lot. Resolves bug 748.
27579 - Resist DNS poisoning a little better by making sure that names in
27580 answer sections match.
27581 - Print the SOCKS5 error message string as well as the error code
27582 when a tor-resolve request fails. Patch from Jacob.
27585 Changes in version 0.2.1.4-alpha - 2008-08-04
27586 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
27589 - The address part of exit policies was not correctly written
27590 to router descriptors. This generated router descriptors that failed
27591 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
27593 - Tor triggered a false assert when extending a circuit to a relay
27594 but we already have a connection open to that relay. Noticed by
27595 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
27598 - Fix a hidden service logging bug: in some edge cases, the router
27599 descriptor of a previously picked introduction point becomes
27600 obsolete and we need to give up on it rather than continually
27601 complaining that it has become obsolete. Observed by xiando. Bugfix
27604 o Removed features:
27605 - Take out the TestVia config option, since it was a workaround for
27606 a bug that was fixed in Tor 0.1.1.21.
27609 Changes in version 0.2.1.3-alpha - 2008-08-03
27610 Tor 0.2.1.3-alpha implements most of the pieces to prevent
27611 infinite-length circuit attacks (see proposal 110); fixes a bug that
27612 might cause exit relays to corrupt streams they send back; allows
27613 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
27614 ExcludeExitNodes config options; and fixes a big pile of bugs.
27616 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
27617 - Send a bootstrap problem "warn" event on the first problem if the
27618 reason is NO_ROUTE (that is, our network is down).
27621 - Implement most of proposal 110: The first K cells to be sent
27622 along a circuit are marked as special "early" cells; only K "early"
27623 cells will be allowed. Once this code is universal, we can block
27624 certain kinds of DOS attack by requiring that EXTEND commands must
27625 be sent using an "early" cell.
27628 - Try to attach connections immediately upon receiving a RENDEZVOUS2
27629 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
27630 on the client side when connecting to a hidden service. Bugfix
27631 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
27632 - Ensure that two circuits can never exist on the same connection
27633 with the same circuit ID, even if one is marked for close. This
27634 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
27637 - When relays do their initial bandwidth measurement, don't limit
27638 to just our entry guards for the test circuits. Otherwise we tend
27639 to have multiple test circuits going through a single entry guard,
27640 which makes our bandwidth test less accurate. Fixes part of bug 654;
27641 patch contributed by Josh Albrecht.
27642 - Add an ExcludeExitNodes option so users can list a set of nodes
27643 that should be be excluded from the exit node position, but
27644 allowed elsewhere. Implements proposal 151.
27645 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
27646 ExcludeNodes and ExcludeExitNodes lists.
27647 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
27648 be more efficient. Formerly it was quadratic in the number of
27649 servers; now it should be linear. Fixes bug 509.
27650 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
27651 and n_conn_id_digest fields into a separate structure that's
27652 only needed when the circuit has not yet attached to an n_conn.
27655 - Change the contrib/tor.logrotate script so it makes the new
27656 logs as "_tor:_tor" rather than the default, which is generally
27657 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
27658 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
27659 warnings (occasionally), but it can also cause the compiler to
27660 eliminate error-checking code. Suggested by Peter Gutmann.
27661 - When a hidden service is giving up on an introduction point candidate
27662 that was not included in the last published rendezvous descriptor,
27663 don't reschedule publication of the next descriptor. Fixes bug 763.
27665 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
27666 HiddenServiceExcludeNodes as obsolete: they never worked properly,
27667 and nobody claims to be using them. Fixes bug 754. Bugfix on
27668 0.1.0.1-rc. Patch from Christian Wilms.
27669 - Fix a small alignment and memory-wasting bug on buffer chunks.
27672 o Minor bugfixes (controller):
27673 - When closing an application-side connection because its circuit
27674 is getting torn down, generate the stream event correctly.
27675 Bugfix on 0.1.2.x. Anonymous patch.
27677 o Removed features:
27678 - Remove all backward-compatibility code to support relays running
27679 versions of Tor so old that they no longer work at all on the
27683 Changes in version 0.2.0.30 - 2008-07-15
27685 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
27686 warnings (occasionally), but it can also cause the compiler to
27687 eliminate error-checking code. Suggested by Peter Gutmann.
27690 Changes in version 0.2.0.29-rc - 2008-07-08
27691 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
27692 hidden-service performance bugs, and fixes a bunch of smaller bugs.
27695 - If you have more than one bridge but don't know their keys,
27696 you would only launch a request for the descriptor of the first one
27697 on your list. (Tor considered launching requests for the others, but
27698 found that it already had a connection on the way for $0000...0000
27699 so it didn't open another.) Bugfix on 0.2.0.x.
27700 - If you have more than one bridge but don't know their keys, and the
27701 connection to one of the bridges failed, you would cancel all
27702 pending bridge connections. (After all, they all have the same
27703 digest.) Bugfix on 0.2.0.x.
27704 - When a hidden service was trying to establish an introduction point,
27705 and Tor had built circuits preemptively for such purposes, we
27706 were ignoring all the preemptive circuits and launching a new one
27707 instead. Bugfix on 0.2.0.14-alpha.
27708 - When a hidden service was trying to establish an introduction point,
27709 and Tor *did* manage to reuse one of the preemptively built
27710 circuits, it didn't correctly remember which one it used,
27711 so it asked for another one soon after, until there were no
27712 more preemptive circuits, at which point it launched one from
27713 scratch. Bugfix on 0.0.9.x.
27714 - Make directory servers include the X-Your-Address-Is: http header in
27715 their responses even for begin_dir conns. Now clients who only
27716 ever use begin_dir connections still have a way to learn their IP
27717 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
27720 - Fix a macro/CPP interaction that was confusing some compilers:
27721 some GCCs don't like #if/#endif pairs inside macro arguments.
27723 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
27724 Fixes bug 704; fix from Steven Murdoch.
27725 - When opening /dev/null in finish_daemonize(), do not pass the
27726 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
27727 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
27728 - Correctly detect transparent proxy support on Linux hosts that
27729 require in.h to be included before netfilter_ipv4.h. Patch
27731 - Disallow session resumption attempts during the renegotiation
27732 stage of the v2 handshake protocol. Clients should never be trying
27733 session resumption at this point, but apparently some did, in
27734 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
27735 found by Geoff Goodell.
27738 Changes in version 0.2.1.2-alpha - 2008-06-20
27739 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
27740 make it easier to set up your own private Tor network; fixes several
27741 big bugs with using more than one bridge relay; fixes a big bug with
27742 offering hidden services quickly after Tor starts; and uses a better
27743 API for reporting potential bootstrapping problems to the controller.
27746 - New TestingTorNetwork config option to allow adjustment of
27747 previously constant values that, while reasonable, could slow
27748 bootstrapping. Implements proposal 135. Patch from Karsten.
27751 - If you have more than one bridge but don't know their digests,
27752 you would only learn a request for the descriptor of the first one
27753 on your list. (Tor considered launching requests for the others, but
27754 found that it already had a connection on the way for $0000...0000
27755 so it didn't open another.) Bugfix on 0.2.0.x.
27756 - If you have more than one bridge but don't know their digests,
27757 and the connection to one of the bridges failed, you would cancel
27758 all pending bridge connections. (After all, they all have the
27759 same digest.) Bugfix on 0.2.0.x.
27760 - When establishing a hidden service, introduction points that
27761 originate from cannibalized circuits are completely ignored and not
27762 included in rendezvous service descriptors. This might be another
27763 reason for delay in making a hidden service available. Bugfix
27764 from long ago (0.0.9.x?)
27767 - Allow OpenSSL to use dynamic locks if it wants.
27768 - When building a consensus, do not include routers that are down.
27769 This will cut down 30% to 40% on consensus size. Implements
27771 - In directory authorities' approved-routers files, allow
27772 fingerprints with or without space.
27773 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
27774 controller can query our current bootstrap state in case it attaches
27775 partway through and wants to catch up.
27776 - Send an initial "Starting" bootstrap status event, so we have a
27777 state to start out in.
27780 - Asking for a conditional consensus at .../consensus/<fingerprints>
27781 would crash a dirserver if it did not already have a
27782 consensus. Bugfix on 0.2.1.1-alpha.
27783 - Clean up some macro/CPP interactions: some GCC versions don't like
27784 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
27787 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
27788 - Directory authorities shouldn't complain about bootstrapping
27789 problems just because they do a lot of reachability testing and
27790 some of the connection attempts fail.
27791 - Start sending "count" and "recommendation" key/value pairs in
27792 bootstrap problem status events, so the controller can hear about
27793 problems even before Tor decides they're worth reporting for sure.
27794 - If you're using bridges, generate "bootstrap problem" warnings
27795 as soon as you run out of working bridges, rather than waiting
27796 for ten failures -- which will never happen if you have less than
27798 - If we close our OR connection because there's been a circuit
27799 pending on it for too long, we were telling our bootstrap status
27800 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
27803 Changes in version 0.2.1.1-alpha - 2008-06-13
27804 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
27805 were making the Tor process bloat especially on Linux; makes our TLS
27806 handshake blend in better; sends "bootstrap phase" status events to
27807 the controller, so it can keep the user informed of progress (and
27808 problems) fetching directory information and establishing circuits;
27809 and adds a variety of smaller features.
27812 - More work on making our TLS handshake blend in: modify the list
27813 of ciphers advertised by OpenSSL in client mode to even more
27814 closely resemble a common web browser. We cheat a little so that
27815 we can advertise ciphers that the locally installed OpenSSL doesn't
27817 - Start sending "bootstrap phase" status events to the controller,
27818 so it can keep the user informed of progress fetching directory
27819 information and establishing circuits. Also inform the controller
27820 if we think we're stuck at a particular bootstrap phase. Implements
27822 - Resume using OpenSSL's RAND_poll() for better (and more portable)
27823 cross-platform entropy collection again. We used to use it, then
27824 stopped using it because of a bug that could crash systems that
27825 called RAND_poll when they had a lot of fds open. It looks like the
27826 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
27827 at startup, and to call RAND_poll() when we reseed later only if
27828 we have a non-buggy OpenSSL version.
27831 - When we choose to abandon a new entry guard because we think our
27832 older ones might be better, close any circuits pending on that
27833 new entry guard connection. This fix should make us recover much
27834 faster when our network is down and then comes back. Bugfix on
27835 0.1.2.8-beta; found by lodger.
27837 o Memory fixes and improvements:
27838 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
27839 to avoid unused RAM in buffer chunks and memory pools.
27840 - Speed up parsing and cut down on memory fragmentation by using
27841 stack-style allocations for parsing directory objects. Previously,
27842 this accounted for over 40% of allocations from within Tor's code
27843 on a typical directory cache.
27844 - Use a Bloom filter rather than a digest-based set to track which
27845 descriptors we need to keep around when we're cleaning out old
27846 router descriptors. This speeds up the computation significantly,
27847 and may reduce fragmentation.
27848 - Reduce the default smartlist size from 32 to 16; it turns out that
27849 most smartlists hold around 8-12 elements tops.
27850 - Make dumpstats() log the fullness and size of openssl-internal
27852 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
27853 patch to their OpenSSL, turn it on to save memory on servers. This
27854 patch will (with any luck) get included in a mainline distribution
27856 - Never use OpenSSL compression: it wastes RAM and CPU trying to
27857 compress cells, which are basically all encrypted, compressed,
27861 - Stop reloading the router list from disk for no reason when we
27862 run out of reachable directory mirrors. Once upon a time reloading
27863 it would set the 'is_running' flag back to 1 for them. It hasn't
27864 done that for a long time.
27865 - In very rare situations new hidden service descriptors were
27866 published earlier than 30 seconds after the last change to the
27867 service. (We currently think that a hidden service descriptor
27868 that's been stable for 30 seconds is worth publishing.)
27871 - Allow separate log levels to be configured for different logging
27872 domains. For example, this allows one to log all notices, warnings,
27873 or errors, plus all memory management messages of level debug or
27874 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
27875 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
27876 and stop using a warning that had become unfixably verbose under
27878 - New --hush command-line option similar to --quiet. While --quiet
27879 disables all logging to the console on startup, --hush limits the
27880 output to messages of warning and error severity.
27881 - Servers support a new URL scheme for consensus downloads that
27882 allows the client to specify which authorities are trusted.
27883 The server then only sends the consensus if the client will trust
27884 it. Otherwise a 404 error is sent back. Clients use this
27885 new scheme when the server supports it (meaning it's running
27886 0.2.1.1-alpha or later). Implements proposal 134.
27887 - New configure/torrc options (--enable-geoip-stats,
27888 DirRecordUsageByCountry) to record how many IPs we've served
27889 directory info to in each country code, how many status documents
27890 total we've sent to each country code, and what share of the total
27891 directory requests we should expect to see.
27892 - Use the TLS1 hostname extension to more closely resemble browser
27894 - Lots of new unit tests.
27895 - Add a macro to implement the common pattern of iterating through
27896 two parallel lists in lockstep.
27899 Changes in version 0.2.0.28-rc - 2008-06-13
27900 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
27901 performance bug, and fixes a bunch of smaller bugs.
27904 - Fix a bug where, when we were choosing the 'end stream reason' to
27905 put in our relay end cell that we send to the exit relay, Tor
27906 clients on Windows were sometimes sending the wrong 'reason'. The
27907 anonymity problem is that exit relays may be able to guess whether
27908 the client is running Windows, thus helping partition the anonymity
27909 set. Down the road we should stop sending reasons to exit relays,
27910 or otherwise prevent future versions of this bug.
27913 - While setting up a hidden service, some valid introduction circuits
27914 were overlooked and abandoned. This might be the reason for
27915 the long delay in making a hidden service available. Bugfix on
27919 - Update to the "June 9 2008" ip-to-country file.
27920 - Run 'make test' as part of 'make dist', so we stop releasing so
27921 many development snapshots that fail their unit tests.
27924 - When we're checking if we have enough dir info for each relay
27925 to begin establishing circuits, make sure that we actually have
27926 the descriptor listed in the consensus, not just any descriptor.
27928 - Bridge relays no longer print "xx=0" in their extrainfo document
27929 for every single country code in the geoip db. Bugfix on
27931 - Only warn when we fail to load the geoip file if we were planning to
27932 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
27933 - If we change our MaxAdvertisedBandwidth and then reload torrc,
27934 Tor won't realize it should publish a new relay descriptor. Fixes
27935 bug 688, reported by mfr. Bugfix on 0.1.2.x.
27936 - When we haven't had any application requests lately, don't bother
27937 logging that we have expired a bunch of descriptors. Bugfix
27939 - Make relay cells written on a connection count as non-padding when
27940 tracking how long a connection has been in use. Bugfix on
27941 0.2.0.1-alpha. Spotted by lodger.
27942 - Fix unit tests in 0.2.0.27-rc.
27943 - Fix compile on Windows.
27946 Changes in version 0.2.0.27-rc - 2008-06-03
27947 Tor 0.2.0.27-rc adds a few features we left out of the earlier
27948 release candidates. In particular, we now include an IP-to-country
27949 GeoIP database, so controllers can easily look up what country a
27950 given relay is in, and so bridge relays can give us some sanitized
27951 summaries about which countries are making use of bridges. (See proposal
27952 126-geoip-fetching.txt for details.)
27955 - Include an IP-to-country GeoIP file in the tarball, so bridge
27956 relays can report sanitized summaries of the usage they're seeing.
27959 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
27960 Robert Hogan. Fixes the first part of bug 681.
27961 - Make bridge authorities never serve extrainfo docs.
27962 - Add support to detect Libevent versions in the 1.4.x series
27964 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
27965 - Include a new contrib/tor-exit-notice.html file that exit relay
27966 operators can put on their website to help reduce abuse queries.
27969 - When tunneling an encrypted directory connection, and its first
27970 circuit fails, do not leave it unattached and ask the controller
27971 to deal. Fixes the second part of bug 681.
27972 - Make bridge authorities correctly expire old extrainfo documents
27976 Changes in version 0.2.0.26-rc - 2008-05-13
27977 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
27978 in Debian's OpenSSL packages. All users running any 0.2.0.x version
27979 should upgrade, whether they're running Debian or not.
27981 o Major security fixes:
27982 - Use new V3 directory authority keys on the tor26, gabelmoo, and
27983 moria1 V3 directory authorities. The old keys were generated with
27984 a vulnerable version of Debian's OpenSSL package, and must be
27985 considered compromised. Other authorities' keys were not generated
27986 with an affected version of OpenSSL.
27989 - List authority signatures as "unrecognized" based on DirServer
27990 lines, not on cert cache. Bugfix on 0.2.0.x.
27993 - Add a new V3AuthUseLegacyKey option to make it easier for
27994 authorities to change their identity keys if they have to.
27997 Changes in version 0.2.0.25-rc - 2008-04-23
27998 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
28001 - Remember to initialize threading before initializing logging.
28002 Otherwise, many BSD-family implementations will crash hard on
28003 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
28006 - Authorities correctly free policies on bad servers on
28007 exit. Fixes bug 672. Bugfix on 0.2.0.x.
28010 Changes in version 0.2.0.24-rc - 2008-04-22
28011 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
28012 v3 directory authority, makes relays with dynamic IP addresses and no
28013 DirPort notice more quickly when their IP address changes, fixes a few
28014 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
28016 o New directory authorities:
28017 - Take lefkada out of the list of v3 directory authorities, since
28018 it has been down for months.
28019 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
28023 - Detect address changes more quickly on non-directory mirror
28024 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
28026 o Minor features (security):
28027 - Reject requests for reverse-dns lookup of names that are in
28028 a private address space. Patch from lodger.
28029 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
28032 o Minor bugfixes (crashes):
28033 - Avoid a rare assert that can trigger when Tor doesn't have much
28034 directory information yet and it tries to fetch a v2 hidden
28035 service descriptor. Fixes bug 651, reported by nwf.
28036 - Initialize log mutex before initializing dmalloc. Otherwise,
28037 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
28038 - Use recursive pthread mutexes in order to avoid deadlock when
28039 logging debug-level messages to a controller. Bug spotted by nwf,
28040 bugfix on 0.2.0.16-alpha.
28042 o Minor bugfixes (resource management):
28043 - Keep address policies from leaking memory: start their refcount
28044 at 1, not 2. Bugfix on 0.2.0.16-alpha.
28045 - Free authority certificates on exit, so they don't look like memory
28046 leaks. Bugfix on 0.2.0.19-alpha.
28047 - Free static hashtables for policy maps and for TLS connections on
28048 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
28049 - Avoid allocating extra space when computing consensuses on 64-bit
28050 platforms. Bug spotted by aakova.
28052 o Minor bugfixes (misc):
28053 - Do not read the configuration file when we've only been told to
28054 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
28055 based on patch from Sebastian Hahn.
28056 - Exit relays that are used as a client can now reach themselves
28057 using the .exit notation, rather than just launching an infinite
28058 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
28059 - When attempting to open a logfile fails, tell us why.
28060 - Fix a dumb bug that was preventing us from knowing that we should
28061 preemptively build circuits to handle expected directory requests.
28062 Fixes bug 660. Bugfix on 0.1.2.x.
28063 - Warn less verbosely about clock skew from netinfo cells from
28064 untrusted sources. Fixes bug 663.
28065 - Make controller stream events for DNS requests more consistent,
28066 by adding "new stream" events for DNS requests, and removing
28067 spurious "stream closed" events" for cached reverse resolves.
28068 Patch from mwenge. Fixes bug 646.
28069 - Correctly notify one-hop connections when a circuit build has
28070 failed. Possible fix for bug 669. Found by lodger.
28073 Changes in version 0.2.0.23-rc - 2008-03-24
28074 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
28075 makes bootstrapping faster if the first directory mirror you contact
28076 is down. The bundles also include the new Vidalia 0.1.2 release.
28079 - When a tunneled directory request is made to a directory server
28080 that's down, notice after 30 seconds rather than 120 seconds. Also,
28081 fail any begindir streams that are pending on it, so they can
28082 retry elsewhere. This was causing multi-minute delays on bootstrap.
28085 Changes in version 0.2.0.22-rc - 2008-03-18
28086 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
28087 enables encrypted directory connections by default for non-relays, fixes
28088 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
28089 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
28092 - Enable encrypted directory connections by default for non-relays,
28093 so censor tools that block Tor directory connections based on their
28094 plaintext patterns will no longer work. This means Tor works in
28095 certain censored countries by default again.
28098 - Make sure servers always request certificates from clients during
28099 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
28100 - Do not enter a CPU-eating loop when a connection is closed in
28101 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
28102 diagnosed by lodger; bugfix on 0.2.0.20-rc.
28103 - Fix assertion failure that could occur when a blocked circuit
28104 became unblocked, and it had pending client DNS requests. Bugfix
28105 on 0.2.0.1-alpha. Fixes bug 632.
28107 o Minor bugfixes (on 0.1.2.x):
28108 - Generate "STATUS_SERVER" events rather than misspelled
28109 "STATUS_SEVER" events. Caught by mwenge.
28110 - When counting the number of bytes written on a TLS connection,
28111 look at the BIO actually used for writing to the network, not
28112 at the BIO used (sometimes) to buffer data for the network.
28113 Looking at different BIOs could result in write counts on the
28114 order of ULONG_MAX. Fixes bug 614.
28115 - On Windows, correctly detect errors when listing the contents of
28116 a directory. Fix from lodger.
28118 o Minor bugfixes (on 0.2.0.x):
28119 - Downgrade "sslv3 alert handshake failure" message to INFO.
28120 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
28121 left BandwidthRate and BandwidthBurst at the default, we would be
28122 silently limited by those defaults. Now raise them to match the
28123 RelayBandwidth* values.
28124 - Fix the SVK version detection logic to work correctly on a branch.
28125 - Make --enable-openbsd-malloc work correctly on Linux with alpha
28126 CPUs. Fixes bug 625.
28127 - Logging functions now check that the passed severity is sane.
28128 - Use proper log levels in the testsuite call of
28129 get_interface_address6().
28130 - When using a nonstandard malloc, do not use the platform values for
28131 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
28132 - Make the openbsd malloc code use 8k pages on alpha CPUs and
28134 - Detect mismatched page sizes when using --enable-openbsd-malloc.
28135 - Avoid double-marked-for-close warning when certain kinds of invalid
28136 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
28137 for bug 617. Bugfix on 0.2.0.1-alpha.
28138 - Make sure that the "NULL-means-reject *:*" convention is followed by
28139 all the policy manipulation functions, avoiding some possible crash
28140 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
28141 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
28142 actually works, and doesn't warn about every single reverse lookup.
28143 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
28146 - Only log guard node status when guard node status has changed.
28147 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
28148 make "INFO" 75% less verbose.
28151 Changes in version 0.2.0.21-rc - 2008-03-02
28152 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
28153 makes Tor work well with Vidalia again, fixes a rare assert bug,
28154 and fixes a pair of more minor bugs. The bundles also include Vidalia
28155 0.1.0 and Torbutton 1.1.16.
28158 - The control port should declare that it requires password auth
28159 when HashedControlSessionPassword is set too. Patch from Matt Edman;
28160 bugfix on 0.2.0.20-rc. Fixes bug 615.
28161 - Downgrade assert in connection_buckets_decrement() to a log message.
28162 This may help us solve bug 614, and in any case will make its
28163 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
28164 - We were sometimes miscounting the number of bytes read from the
28165 network, causing our rate limiting to not be followed exactly.
28166 Bugfix on 0.2.0.16-alpha. Reported by lodger.
28169 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
28170 OpenSSL versions should have been working fine. Diagnosis and patch
28171 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
28172 Bugfix on 0.2.0.20-rc.
28175 Changes in version 0.2.0.20-rc - 2008-02-24
28176 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
28177 makes more progress towards normalizing Tor's TLS handshake, makes
28178 hidden services work better again, helps relays bootstrap if they don't
28179 know their IP address, adds optional support for linking in openbsd's
28180 allocator or tcmalloc, allows really fast relays to scale past 15000
28181 sockets, and fixes a bunch of minor bugs reported by Veracode.
28184 - Enable the revised TLS handshake based on the one designed by
28185 Steven Murdoch in proposal 124, as revised in proposal 130. It
28186 includes version negotiation for OR connections as described in
28187 proposal 105. The new handshake is meant to be harder for censors
28188 to fingerprint, and it adds the ability to detect certain kinds of
28189 man-in-the-middle traffic analysis attacks. The version negotiation
28190 feature will allow us to improve Tor's link protocol more safely
28192 - Choose which bridge to use proportional to its advertised bandwidth,
28193 rather than uniformly at random. This should speed up Tor for
28194 bridge users. Also do this for people who set StrictEntryNodes.
28195 - When a TrackHostExits-chosen exit fails too many times in a row,
28196 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
28199 - Resolved problems with (re-)fetching hidden service descriptors.
28200 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
28201 and 0.2.0.19-alpha.
28202 - If we only ever used Tor for hidden service lookups or posts, we
28203 would stop building circuits and start refusing connections after
28204 24 hours, since we falsely believed that Tor was dormant. Reported
28205 by nwf; bugfix on 0.1.2.x.
28206 - Servers that don't know their own IP address should go to the
28207 authorities for their first directory fetch, even if their DirPort
28208 is off or if they don't know they're reachable yet. This will help
28209 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
28210 - When counting the number of open sockets, count not only the number
28211 of sockets we have received from the socket() call, but also
28212 the number we've gotten from accept() and socketpair(). This bug
28213 made us fail to count all sockets that we were using for incoming
28214 connections. Bugfix on 0.2.0.x.
28215 - Fix code used to find strings within buffers, when those strings
28216 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
28217 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
28218 - Add a new __HashedControlSessionPassword option for controllers
28219 to use for one-off session password hashes that shouldn't get
28220 saved to disk by SAVECONF --- Vidalia users were accumulating a
28221 pile of HashedControlPassword lines in their torrc files, one for
28222 each time they had restarted Tor and then clicked Save. Make Tor
28223 automatically convert "HashedControlPassword" to this new option but
28224 only when it's given on the command line. Partial fix for bug 586.
28226 o Minor features (performance):
28227 - Tune parameters for cell pool allocation to minimize amount of
28229 - Add OpenBSD malloc code from phk as an optional malloc
28230 replacement on Linux: some glibc libraries do very poorly
28231 with Tor's memory allocation patterns. Pass
28232 --enable-openbsd-malloc to get the replacement malloc code.
28233 - Add a --with-tcmalloc option to the configure script to link
28234 against tcmalloc (if present). Does not yet search for
28235 non-system include paths.
28236 - Stop imposing an arbitrary maximum on the number of file descriptors
28237 used for busy servers. Bug reported by Olaf Selke; patch from
28240 o Minor features (other):
28241 - When SafeLogging is disabled, log addresses along with all TLS
28243 - When building with --enable-gcc-warnings, check for whether Apple's
28244 warning "-Wshorten-64-to-32" is available.
28245 - Add a --passphrase-fd argument to the tor-gencert command for
28248 o Minor bugfixes (memory leaks and code problems):
28249 - We were leaking a file descriptor if Tor started with a zero-length
28250 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
28251 - Detect size overflow in zlib code. Reported by Justin Ferguson and
28253 - We were comparing the raw BridgePassword entry with a base64'ed
28254 version of it, when handling a "/tor/networkstatus-bridges"
28255 directory request. Now compare correctly. Noticed by Veracode.
28256 - Recover from bad tracked-since value in MTBF-history file.
28257 Should fix bug 537.
28258 - Alter the code that tries to recover from unhandled write
28259 errors, to not try to flush onto a socket that's given us
28260 unhandled errors. Bugfix on 0.1.2.x.
28261 - Make Unix controlsockets work correctly on OpenBSD. Patch from
28262 tup. Bugfix on 0.2.0.3-alpha.
28264 o Minor bugfixes (other):
28265 - If we have an extra-info document for our server, always make
28266 it available on the control port, even if we haven't gotten
28267 a copy of it from an authority yet. Patch from mwenge.
28268 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
28269 - Directory mirrors no longer include a guess at the client's IP
28270 address if the connection appears to be coming from the same /24
28271 network; it was producing too many wrong guesses.
28272 - Make the new hidden service code respect the SafeLogging setting.
28273 Bugfix on 0.2.0.x. Patch from Karsten.
28274 - When starting as an authority, do not overwrite all certificates
28275 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
28276 - If we're trying to flush the last bytes on a connection (for
28277 example, when answering a directory request), reset the
28278 time-to-give-up timeout every time we manage to write something
28279 on the socket. Bugfix on 0.1.2.x.
28280 - Change the behavior of "getinfo status/good-server-descriptor"
28281 so it doesn't return failure when any authority disappears.
28282 - Even though the man page said that "TrackHostExits ." should
28283 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
28284 - Report TLS "zero return" case as a "clean close" and "IO error"
28285 as a "close". Stop calling closes "unexpected closes": existing
28286 Tors don't use SSL_close(), so having a connection close without
28287 the TLS shutdown handshake is hardly unexpected.
28288 - Send NAMESERVER_STATUS messages for a single failed nameserver
28291 o Code simplifications and refactoring:
28292 - Remove the tor_strpartition function: its logic was confused,
28293 and it was only used for one thing that could be implemented far
28297 Changes in version 0.2.0.19-alpha - 2008-02-09
28298 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
28299 handshake, makes path selection for relays more secure and IP address
28300 guessing more robust, and generally fixes a lot of bugs in preparation
28301 for calling the 0.2.0 branch stable.
28304 - Do not include recognizeable strings in the commonname part of
28305 Tor's x509 certificates.
28308 - If we're a relay, avoid picking ourselves as an introduction point,
28309 a rendezvous point, or as the final hop for internal circuits. Bug
28310 reported by taranis and lodger. Bugfix on 0.1.2.x.
28311 - Patch from "Andrew S. Lists" to catch when we contact a directory
28312 mirror at IP address X and he says we look like we're coming from
28313 IP address X. Bugfix on 0.1.2.x.
28315 o Minor features (security):
28316 - Be more paranoid about overwriting sensitive memory on free(),
28317 as a defensive programming tactic to ensure forward secrecy.
28319 o Minor features (directory authority):
28320 - Actually validate the options passed to AuthDirReject,
28321 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
28322 - Reject router descriptors with out-of-range bandwidthcapacity or
28323 bandwidthburst values.
28325 o Minor features (controller):
28326 - Reject controller commands over 1MB in length. This keeps rogue
28327 processes from running us out of memory.
28329 o Minor features (misc):
28330 - Give more descriptive well-formedness errors for out-of-range
28331 hidden service descriptor/protocol versions.
28332 - Make memory debugging information describe more about history
28333 of cell allocation, so we can help reduce our memory use.
28335 o Deprecated features (controller):
28336 - The status/version/num-versioning and status/version/num-concurring
28337 GETINFO options are no longer useful in the v3 directory protocol:
28338 treat them as deprecated, and warn when they're used.
28341 - When our consensus networkstatus has been expired for a while, stop
28342 being willing to build circuits using it. Fixes bug 401. Bugfix
28344 - Directory caches now fetch certificates from all authorities
28345 listed in a networkstatus consensus, even when they do not
28346 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
28347 - When connecting to a bridge without specifying its key, insert
28348 the connection into the identity-to-connection map as soon as
28349 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
28350 - Detect versions of OS X where malloc_good_size() is present in the
28351 library but never actually declared. Resolves bug 587. Bugfix
28353 - Stop incorrectly truncating zlib responses to directory authority
28354 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
28355 - Stop recommending that every server operator send mail to tor-ops.
28356 Resolves bug 597. Bugfix on 0.1.2.x.
28357 - Don't trigger an assert if we start a directory authority with a
28358 private IP address (like 127.0.0.1).
28359 - Avoid possible failures when generating a directory with routers
28360 with over-long versions strings, or too many flags set. Bugfix
28362 - If an attempt to launch a DNS resolve request over the control
28363 port fails because we have overrun the limit on the number of
28364 connections, tell the controller that the request has failed.
28365 - Avoid using too little bandwidth when our clock skips a few
28366 seconds. Bugfix on 0.1.2.x.
28367 - Fix shell error when warning about missing packages in configure
28368 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
28369 - Do not become confused when receiving a spurious VERSIONS-like
28370 cell from a confused v1 client. Bugfix on 0.2.0.x.
28371 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
28372 introduction points for a hidden service have failed. Patch from
28373 Karsten Loesing. Bugfix on 0.2.0.x.
28375 o Code simplifications and refactoring:
28376 - Remove some needless generality from cpuworker code, for improved
28378 - Stop overloading the circuit_t.onionskin field for both "onionskin
28379 from a CREATE cell that we are waiting for a cpuworker to be
28380 assigned" and "onionskin from an EXTEND cell that we are going to
28381 send to an OR as soon as we are connected". Might help with bug 600.
28382 - Add an in-place version of aes_crypt() so that we can avoid doing a
28383 needless memcpy() call on each cell payload.
28386 Changes in version 0.2.0.18-alpha - 2008-01-25
28387 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
28388 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
28389 that can warn or reject connections to ports generally associated with
28390 vulnerable-plaintext protocols.
28392 o New directory authorities:
28393 - Set up dannenberg (run by CCC) as the sixth v3 directory
28397 - Fix a major memory leak when attempting to use the v2 TLS
28398 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
28399 - We accidentally enabled the under-development v2 TLS handshake
28400 code, which was causing log entries like "TLS error while
28401 renegotiating handshake". Disable it again. Resolves bug 590.
28402 - We were computing the wrong Content-Length: header for directory
28403 responses that need to be compressed on the fly, causing clients
28404 asking for those items to always fail. Bugfix on 0.2.0.x; partially
28408 - Avoid going directly to the directory authorities even if you're a
28409 relay, if you haven't found yourself reachable yet or if you've
28410 decided not to advertise your dirport yet. Addresses bug 556.
28411 - If we've gone 12 hours since our last bandwidth check, and we
28412 estimate we have less than 50KB bandwidth capacity but we could
28413 handle more, do another bandwidth test.
28414 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
28415 Tor can warn and/or refuse connections to ports commonly used with
28416 vulnerable-plaintext protocols. Currently we warn on ports 23,
28417 109, 110, and 143, but we don't reject any.
28420 - When we setconf ClientOnly to 1, close any current OR and Dir
28421 listeners. Reported by mwenge.
28422 - When we get a consensus that's been signed by more people than
28423 we expect, don't log about it; it's not a big deal. Reported
28427 - Don't answer "/tor/networkstatus-bridges" directory requests if
28428 the request isn't encrypted.
28429 - Make "ClientOnly 1" config option disable directory ports too.
28430 - Patches from Karsten Loesing to make v2 hidden services more
28431 robust: work even when there aren't enough HSDir relays available;
28432 retry when a v2 rend desc fetch fails; but don't retry if we
28433 already have a usable v0 rend desc.
28436 Changes in version 0.2.0.17-alpha - 2008-01-17
28437 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
28440 - Make the tor-gencert man page get included correctly in the tarball.
28443 Changes in version 0.2.0.16-alpha - 2008-01-17
28444 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
28445 Loesing, and generally cleans up a lot of features and minor bugs.
28447 o New directory authorities:
28448 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
28451 o Major performance improvements:
28452 - Switch our old ring buffer implementation for one more like that
28453 used by free Unix kernels. The wasted space in a buffer with 1mb
28454 of data will now be more like 8k than 1mb. The new implementation
28455 also avoids realloc();realloc(); patterns that can contribute to
28456 memory fragmentation.
28459 - Configuration files now accept C-style strings as values. This
28460 helps encode characters not allowed in the current configuration
28461 file format, such as newline or #. Addresses bug 557.
28462 - Although we fixed bug 539 (where servers would send HTTP status 503
28463 responses _and_ send a body too), there are still servers out
28464 there that haven't upgraded. Therefore, make clients parse such
28465 bodies when they receive them.
28466 - When we're not serving v2 directory information, there is no reason
28467 to actually keep any around. Remove the obsolete files and directory
28468 on startup if they are very old and we aren't going to serve them.
28470 o Minor performance improvements:
28471 - Reference-count and share copies of address policy entries; only 5%
28472 of them were actually distinct.
28473 - Never walk through the list of logs if we know that no log is
28474 interested in a given message.
28477 - When an authority has not signed a consensus, do not try to
28478 download a nonexistent "certificate with key 00000000". Bugfix
28479 on 0.2.0.x. Fixes bug 569.
28480 - Fix a rare assert error when we're closing one of our threads:
28481 use a mutex to protect the list of logs, so we never write to the
28482 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
28483 bug 575, which is kind of the revenge of bug 222.
28484 - Patch from Karsten Loesing to complain less at both the client
28485 and the relay when a relay used to have the HSDir flag but doesn't
28486 anymore, and we try to upload a hidden service descriptor.
28487 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
28489 - Do not try to download missing certificates until we have tried
28490 to check our fallback consensus. Fixes bug 583.
28491 - Make bridges round reported GeoIP stats info up to the nearest
28492 estimate, not down. Now we can distinguish between "0 people from
28493 this country" and "1 person from this country".
28494 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
28495 - Avoid possible segfault if key generation fails in
28496 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
28497 - Avoid segfault in the case where a badly behaved v2 versioning
28498 directory sends a signed networkstatus with missing client-versions.
28500 - Avoid segfaults on certain complex invocations of
28501 router_get_by_hexdigest(). Bugfix on 0.1.2.
28502 - Correct bad index on array access in parse_http_time(). Bugfix
28504 - Fix possible bug in vote generation when server versions are present
28505 but client versions are not.
28506 - Fix rare bug on REDIRECTSTREAM control command when called with no
28507 port set: it could erroneously report an error when none had
28509 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
28510 compressing large objects and find ourselves with more than 4k
28511 left over. Bugfix on 0.2.0.
28512 - Fix a small memory leak when setting up a hidden service.
28513 - Fix a few memory leaks that could in theory happen under bizarre
28515 - Fix an assert if we post a general-purpose descriptor via the
28516 control port but that descriptor isn't mentioned in our current
28517 network consensus. Bug reported by Jon McLachlan; bugfix on
28520 o Minor features (controller):
28521 - Get NS events working again. Patch from tup.
28522 - The GETCONF command now escapes and quotes configuration values
28523 that don't otherwise fit into the torrc file.
28524 - The SETCONF command now handles quoted values correctly.
28526 o Minor features (directory authorities):
28527 - New configuration options to override default maximum number of
28528 servers allowed on a single IP address. This is important for
28529 running a test network on a single host.
28530 - Actually implement the -s option to tor-gencert.
28531 - Add a manual page for tor-gencert.
28533 o Minor features (bridges):
28534 - Bridge authorities no longer serve bridge descriptors over
28535 unencrypted connections.
28537 o Minor features (other):
28538 - Add hidden services and DNSPorts to the list of things that make
28539 Tor accept that it has running ports. Change starting Tor with no
28540 ports from a fatal error to a warning; we might change it back if
28541 this turns out to confuse anybody. Fixes bug 579.
28544 Changes in version 0.1.2.19 - 2008-01-17
28545 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
28546 exit policy a little bit more conservative so it's safer to run an
28547 exit relay on a home system, and fixes a variety of smaller issues.
28550 - Exit policies now reject connections that are addressed to a
28551 relay's public (external) IP address too, unless
28552 ExitPolicyRejectPrivate is turned off. We do this because too
28553 many relays are running nearby to services that trust them based
28554 on network address.
28557 - When the clock jumps forward a lot, do not allow the bandwidth
28558 buckets to become negative. Fixes bug 544.
28559 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
28560 on every successful resolve. Reported by Mike Perry.
28561 - Purge old entries from the "rephist" database and the hidden
28562 service descriptor database even when DirPort is zero.
28563 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
28564 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
28565 crashing or mis-answering these requests.
28566 - When we decide to send a 503 response to a request for servers, do
28567 not then also send the server descriptors: this defeats the whole
28568 purpose. Fixes bug 539.
28571 - Changing the ExitPolicyRejectPrivate setting should cause us to
28572 rebuild our server descriptor.
28573 - Fix handling of hex nicknames when answering controller requests for
28574 networkstatus by name, or when deciding whether to warn about
28575 unknown routers in a config option. (Patch from mwenge.)
28576 - Fix a couple of hard-to-trigger autoconf problems that could result
28577 in really weird results on platforms whose sys/types.h files define
28578 nonstandard integer types.
28579 - Don't try to create the datadir when running --verify-config or
28580 --hash-password. Resolves bug 540.
28581 - If we were having problems getting a particular descriptor from the
28582 directory caches, and then we learned about a new descriptor for
28583 that router, we weren't resetting our failure count. Reported
28585 - Although we fixed bug 539 (where servers would send HTTP status 503
28586 responses _and_ send a body too), there are still servers out there
28587 that haven't upgraded. Therefore, make clients parse such bodies
28588 when they receive them.
28589 - Run correctly on systems where rlim_t is larger than unsigned long.
28590 This includes some 64-bit systems.
28591 - Run correctly on platforms (like some versions of OS X 10.5) where
28592 the real limit for number of open files is OPEN_FILES, not rlim_max
28593 from getrlimit(RLIMIT_NOFILES).
28594 - Avoid a spurious free on base64 failure.
28595 - Avoid segfaults on certain complex invocations of
28596 router_get_by_hexdigest().
28597 - Fix rare bug on REDIRECTSTREAM control command when called with no
28598 port set: it could erroneously report an error when none had
28602 Changes in version 0.2.0.15-alpha - 2007-12-25
28603 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
28604 features added in 0.2.0.13-alpha.
28607 - Fix several remotely triggerable asserts based on DirPort requests
28608 for a v2 or v3 networkstatus object before we were prepared. This
28609 was particularly bad for 0.2.0.13 and later bridge relays, who
28610 would never have a v2 networkstatus and would thus always crash
28611 when used. Bugfixes on 0.2.0.x.
28612 - Estimate the v3 networkstatus size more accurately, rather than
28613 estimating it at zero bytes and giving it artificially high priority
28614 compared to other directory requests. Bugfix on 0.2.0.x.
28617 - Fix configure.in logic for cross-compilation.
28618 - When we load a bridge descriptor from the cache, and it was
28619 previously unreachable, mark it as retriable so we won't just
28620 ignore it. Also, try fetching a new copy immediately. Bugfixes
28622 - The bridge GeoIP stats were counting other relays, for example
28623 self-reachability and authority-reachability tests.
28626 - Support compilation to target iPhone; patch from cjacker huang.
28627 To build for iPhone, pass the --enable-iphone option to configure.
28630 Changes in version 0.2.0.14-alpha - 2007-12-23
28632 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
28633 without a datadirectory from a previous Tor install. Reported
28635 - Fix a crash when we fetch a descriptor that turns out to be
28636 unexpected (it used to be in our networkstatus when we started
28637 fetching it, but it isn't in our current networkstatus), and we
28638 aren't using bridges. Bugfix on 0.2.0.x.
28639 - Fix a crash when accessing hidden services: it would work the first
28640 time you use a given introduction point for your service, but
28641 on subsequent requests we'd be using garbage memory. Fixed by
28642 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
28643 - Fix a crash when we load a bridge descriptor from disk but we don't
28644 currently have a Bridge line for it in our torrc. Bugfix on
28648 - If bridge authorities set BridgePassword, they will serve a
28649 snapshot of known bridge routerstatuses from their DirPort to
28650 anybody who knows that password. Unset by default.
28653 - Make the unit tests build again.
28654 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
28655 - Make PublishServerDescriptor default to 1, so the default doesn't
28656 have to change as we invent new directory protocol versions.
28657 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
28658 be included unless sys/time.h is already included. Fixes
28659 bug 553. Bugfix on 0.2.0.x.
28660 - If we receive a general-purpose descriptor and then receive an
28661 identical bridge-purpose descriptor soon after, don't discard
28662 the next one as a duplicate.
28665 - If BridgeRelay is set to 1, then the default for
28666 PublishServerDescriptor is now "bridge" rather than "v2,v3".
28667 - If the user sets RelayBandwidthRate but doesn't set
28668 RelayBandwidthBurst, then make them equal rather than erroring out.
28671 Changes in version 0.2.0.13-alpha - 2007-12-21
28672 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
28673 Goodell, fixes many more bugs, and adds a lot of infrastructure for
28676 o New directory authorities:
28677 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
28681 - Only update guard status (usable / not usable) once we have
28682 enough directory information. This was causing us to always pick
28683 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
28684 causing us to discard all our guards on startup if we hadn't been
28685 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
28686 - Purge old entries from the "rephist" database and the hidden
28687 service descriptor databases even when DirPort is zero. Bugfix
28689 - We were ignoring our RelayBandwidthRate for the first 30 seconds
28690 after opening a circuit -- even a relayed circuit. Bugfix on
28692 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
28693 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
28694 crashing or mis-answering these types of requests.
28695 - Relays were publishing their server descriptor to v1 and v2
28696 directory authorities, but they didn't try publishing to v3-only
28697 authorities. Fix this; and also stop publishing to v1 authorities.
28699 - When we were reading router descriptors from cache, we were ignoring
28700 the annotations -- so for example we were reading in bridge-purpose
28701 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
28702 - When we decided to send a 503 response to a request for servers, we
28703 were then also sending the server descriptors: this defeats the
28704 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
28707 - Bridge relays now behave like clients with respect to time
28708 intervals for downloading new consensus documents -- otherwise they
28709 stand out. Bridge users now wait until the end of the interval,
28710 so their bridge relay will be sure to have a new consensus document.
28711 - Three new config options (AlternateDirAuthority,
28712 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
28713 user selectively replace the default directory authorities by type,
28714 rather than the all-or-nothing replacement that DirServer offers.
28715 - Tor can now be configured to read a GeoIP file from disk in one
28716 of two formats. This can be used by controllers to map IP addresses
28717 to countries. Eventually, it may support exit-by-country.
28718 - When possible, bridge relays remember which countries users
28719 are coming from, and report aggregate information in their
28720 extra-info documents, so that the bridge authorities can learn
28721 where Tor is blocked.
28722 - Bridge directory authorities now do reachability testing on the
28723 bridges they know. They provide router status summaries to the
28724 controller via "getinfo ns/purpose/bridge", and also dump summaries
28725 to a file periodically.
28726 - Stop fetching directory info so aggressively if your DirPort is
28727 on but your ORPort is off; stop fetching v2 dir info entirely.
28728 You can override these choices with the new FetchDirInfoEarly
28732 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
28733 consensus documents when there are too many relays at a single
28734 IP address. Now clear it in v2 network status documents too, and
28735 also clear it in routerinfo_t when the relay is no longer listed
28736 in the relevant networkstatus document.
28737 - Don't crash if we get an unexpected value for the
28738 PublishServerDescriptor config option. Reported by Matt Edman;
28739 bugfix on 0.2.0.9-alpha.
28740 - Our new v2 hidden service descriptor format allows descriptors
28741 that have no introduction points. But Tor crashed when we tried
28742 to build a descriptor with no intro points (and it would have
28743 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
28744 by Karsten Loesing.
28745 - Fix building with dmalloc 5.5.2 with glibc.
28746 - Reject uploaded descriptors and extrainfo documents if they're
28747 huge. Otherwise we'll cache them all over the network and it'll
28748 clog everything up. Reported by Aljosha Judmayer.
28749 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
28750 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
28751 - When the DANGEROUS_VERSION controller status event told us we're
28752 running an obsolete version, it used the string "OLD" to describe
28753 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
28754 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
28755 - If we can't expand our list of entry guards (e.g. because we're
28756 using bridges or we have StrictEntryNodes set), don't mark relays
28757 down when they fail a directory request. Otherwise we're too quick
28758 to mark all our entry points down. Bugfix on 0.1.2.x.
28759 - Fix handling of hex nicknames when answering controller requests for
28760 networkstatus by name, or when deciding whether to warn about unknown
28761 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
28762 - Fix a couple of hard-to-trigger autoconf problems that could result
28763 in really weird results on platforms whose sys/types.h files define
28764 nonstandard integer types. Bugfix on 0.1.2.x.
28765 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
28766 - Don't crash on name lookup when we have no current consensus. Fixes
28767 bug 538; bugfix on 0.2.0.x.
28768 - Only Tors that want to mirror the v2 directory info should
28769 create the "cached-status" directory in their datadir. (All Tors
28770 used to create it.) Bugfix on 0.2.0.9-alpha.
28771 - Directory authorities should only automatically download Extra Info
28772 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
28775 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
28776 consumers. (We already do this on HUP.)
28777 - Authorities and caches fetch the v2 networkstatus documents
28778 less often, now that v3 is encouraged.
28779 - Add a new config option BridgeRelay that specifies you want to
28780 be a bridge relay. Right now the only difference is that it makes
28781 you answer begin_dir requests, and it makes you cache dir info,
28782 even if your DirPort isn't on.
28783 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
28784 ask about source, timestamp of arrival, purpose, etc. We need
28785 something like this to help Vidalia not do GeoIP lookups on bridge
28787 - Allow multiple HashedControlPassword config lines, to support
28788 multiple controller passwords.
28789 - Authorities now decide whether they're authoritative for a given
28790 router based on the router's purpose.
28791 - New config options AuthDirBadDir and AuthDirListBadDirs for
28792 authorities to mark certain relays as "bad directories" in the
28793 networkstatus documents. Also supports the "!baddir" directive in
28794 the approved-routers file.
28797 Changes in version 0.2.0.12-alpha - 2007-11-16
28798 This twelfth development snapshot fixes some more build problems as
28799 well as a few minor bugs.
28802 - Make it build on OpenBSD again. Patch from tup.
28803 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
28804 package-building for Red Hat, OS X, etc.
28806 o Minor bugfixes (on 0.1.2.x):
28807 - Changing the ExitPolicyRejectPrivate setting should cause us to
28808 rebuild our server descriptor.
28810 o Minor bugfixes (on 0.2.0.x):
28811 - When we're lacking a consensus, don't try to perform rendezvous
28812 operations. Reported by Karsten Loesing.
28813 - Fix a small memory leak whenever we decide against using a
28814 newly picked entry guard. Reported by Mike Perry.
28815 - When authorities detected more than two relays running on the same
28816 IP address, they were clearing all the status flags but forgetting
28817 to clear the "hsdir" flag. So clients were being told that a
28818 given relay was the right choice for a v2 hsdir lookup, yet they
28819 never had its descriptor because it was marked as 'not running'
28821 - If we're trying to fetch a bridge descriptor and there's no way
28822 the bridge authority could help us (for example, we don't know
28823 a digest, or there is no bridge authority), don't be so eager to
28824 fall back to asking the bridge authority.
28825 - If we're using bridges or have strictentrynodes set, and our
28826 chosen exit is in the same family as all our bridges/entry guards,
28827 then be flexible about families.
28830 - When we negotiate a v2 link-layer connection (not yet implemented),
28831 accept RELAY_EARLY cells and turn them into RELAY cells if we've
28832 negotiated a v1 connection for their next step. Initial code for
28836 Changes in version 0.2.0.11-alpha - 2007-11-12
28837 This eleventh development snapshot fixes some build problems with
28838 the previous snapshot. It also includes a more secure-by-default exit
28839 policy for relays, fixes an enormous memory leak for exit relays, and
28840 fixes another bug where servers were falling out of the directory list.
28843 - Exit policies now reject connections that are addressed to a
28844 relay's public (external) IP address too, unless
28845 ExitPolicyRejectPrivate is turned off. We do this because too
28846 many relays are running nearby to services that trust them based
28847 on network address. Bugfix on 0.1.2.x.
28850 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
28851 on every successful resolve. Reported by Mike Perry; bugfix
28853 - On authorities, never downgrade to old router descriptors simply
28854 because they're listed in the consensus. This created a catch-22
28855 where we wouldn't list a new descriptor because there was an
28856 old one in the consensus, and we couldn't get the new one in the
28857 consensus because we wouldn't list it. Possible fix for bug 548.
28858 Also, this might cause bug 543 to appear on authorities; if so,
28859 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
28861 o Packaging fixes on 0.2.0.10-alpha:
28862 - We were including instructions about what to do with the
28863 src/config/fallback-consensus file, but we weren't actually
28864 including it in the tarball. Disable all of that for now.
28867 - Allow people to say PreferTunnelledDirConns rather than
28868 PreferTunneledDirConns, for those alternate-spellers out there.
28871 - Don't reevaluate all the information from our consensus document
28872 just because we've downloaded a v2 networkstatus that we intend
28873 to cache. Fixes bug 545; bugfix on 0.2.0.x.
28876 Changes in version 0.2.0.10-alpha - 2007-11-10
28877 This tenth development snapshot adds a third v3 directory authority
28878 run by Mike Perry, adds most of Karsten Loesing's new hidden service
28879 descriptor format, fixes a bad crash bug and new bridge bugs introduced
28880 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
28881 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
28882 addresses many more minor issues.
28884 o New directory authorities:
28885 - Set up ides (run by Mike Perry) as the third v3 directory authority.
28888 - Allow tunnelled directory connections to ask for an encrypted
28889 "begin_dir" connection or an anonymized "uses a full Tor circuit"
28890 connection independently. Now we can make anonymized begin_dir
28891 connections for (e.g.) more secure hidden service posting and
28893 - More progress on proposal 114: code from Karsten Loesing to
28894 implement new hidden service descriptor format.
28895 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
28896 accommodate the growing number of servers that use the default
28897 and are reaching it.
28898 - Directory authorities use a new formula for selecting which nodes
28899 to advertise as Guards: they must be in the top 7/8 in terms of
28900 how long we have known about them, and above the median of those
28901 nodes in terms of weighted fractional uptime.
28902 - Make "not enough dir info yet" warnings describe *why* Tor feels
28903 it doesn't have enough directory info yet.
28906 - Stop servers from crashing if they set a Family option (or
28907 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
28909 - Make bridge users work again -- the move to v3 directories in
28910 0.2.0.9-alpha had introduced a number of bugs that made bridges
28911 no longer work for clients.
28912 - When the clock jumps forward a lot, do not allow the bandwidth
28913 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
28915 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
28916 - When the consensus lists a router descriptor that we previously were
28917 mirroring, but that we considered non-canonical, reload the
28918 descriptor as canonical. This fixes bug 543 where Tor servers
28919 would start complaining after a few days that they don't have
28920 enough directory information to build a circuit.
28921 - Consider replacing the current consensus when certificates arrive
28922 that make the pending consensus valid. Previously, we were only
28923 considering replacement when the new certs _didn't_ help.
28924 - Fix an assert error on startup if we didn't already have the
28925 consensus and certs cached in our datadirectory: we were caching
28926 the consensus in consensus_waiting_for_certs but then free'ing it
28928 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
28929 Request) if we need more v3 certs but we've already got pending
28930 requests for all of them.
28931 - Correctly back off from failing certificate downloads. Fixes
28933 - Authorities don't vote on the Running flag if they have been running
28934 for less than 30 minutes themselves. Fixes bug 547, where a newly
28935 started authority would vote that everyone was down.
28937 o New requirements:
28938 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
28939 it, it had no AES, and it hasn't seen any security patches since
28943 - Clients now hold circuitless TLS connections open for 1.5 times
28944 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
28945 rebuild a new circuit over them within that timeframe. Previously,
28946 they held them open only for KeepalivePeriod (5 minutes).
28947 - Use "If-Modified-Since" to avoid retrieving consensus
28948 networkstatuses that we already have.
28949 - When we have no consensus, check FallbackNetworkstatusFile (defaults
28950 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
28951 we start knowing some directory caches.
28952 - When we receive a consensus from the future, warn about skew.
28953 - Improve skew reporting: try to give the user a better log message
28954 about how skewed they are, and how much this matters.
28955 - When we have a certificate for an authority, believe that
28956 certificate's claims about the authority's IP address.
28957 - New --quiet command-line option to suppress the default console log.
28958 Good in combination with --hash-password.
28959 - Authorities send back an X-Descriptor-Not-New header in response to
28960 an accepted-but-discarded descriptor upload. Partially implements
28962 - Make the log message for "tls error. breaking." more useful.
28963 - Better log messages about certificate downloads, to attempt to
28964 track down the second incarnation of bug 546.
28966 o Minor features (bridges):
28967 - If bridge users set UpdateBridgesFromAuthority, but the digest
28968 they ask for is a 404 from the bridge authority, they now fall
28969 back to trying the bridge directly.
28970 - Bridges now use begin_dir to publish their server descriptor to
28971 the bridge authority, even when they haven't set TunnelDirConns.
28973 o Minor features (controller):
28974 - When reporting clock skew, and we know that the clock is _at least
28975 as skewed_ as some value, but we don't know the actual value,
28976 report the value as a "minimum skew."
28979 - Update linux-tor-prio.sh script to allow QoS based on the uid of
28980 the Tor process. Patch from Marco Bonetti with tweaks from Mike
28984 - Refuse to start if both ORPort and UseBridges are set. Bugfix
28985 on 0.2.0.x, suggested by Matt Edman.
28986 - Don't stop fetching descriptors when FetchUselessDescriptors is
28987 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
28988 reported by tup and ioerror.
28989 - Better log message on vote from unknown authority.
28990 - Don't log "Launching 0 request for 0 router" message.
28992 o Minor bugfixes (memory leaks):
28993 - Stop leaking memory every time we parse a v3 certificate. Bugfix
28995 - Stop leaking memory every time we load a v3 certificate. Bugfix
28996 on 0.2.0.1-alpha. Fixes bug 536.
28997 - Stop leaking a cached networkstatus on exit. Bugfix on
28999 - Stop leaking voter information every time we free a consensus.
29000 Bugfix on 0.2.0.3-alpha.
29001 - Stop leaking signed data every time we check a voter signature.
29002 Bugfix on 0.2.0.3-alpha.
29003 - Stop leaking a signature every time we fail to parse a consensus or
29004 a vote. Bugfix on 0.2.0.3-alpha.
29005 - Stop leaking v2_download_status_map on shutdown. Bugfix on
29007 - Stop leaking conn->nickname every time we make a connection to a
29008 Tor relay without knowing its expected identity digest (e.g. when
29009 using bridges). Bugfix on 0.2.0.3-alpha.
29011 - Minor bugfixes (portability):
29012 - Run correctly on platforms where rlim_t is larger than unsigned
29013 long, and/or where the real limit for number of open files is
29014 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
29015 particular, these may be needed for OS X 10.5.
29018 Changes in version 0.1.2.18 - 2007-10-28
29019 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
29020 hidden service introduction that were causing huge delays, and a big
29021 bug that was causing some servers to disappear from the network status
29022 lists for a few hours each day.
29024 o Major bugfixes (crashes):
29025 - If a connection is shut down abruptly because of something that
29026 happened inside connection_flushed_some(), do not call
29027 connection_finished_flushing(). Should fix bug 451:
29028 "connection_stop_writing: Assertion conn->write_event failed"
29029 Bugfix on 0.1.2.7-alpha.
29030 - Fix possible segfaults in functions called from
29031 rend_process_relay_cell().
29033 o Major bugfixes (hidden services):
29034 - Hidden services were choosing introduction points uniquely by
29035 hexdigest, but when constructing the hidden service descriptor
29036 they merely wrote the (potentially ambiguous) nickname.
29037 - Clients now use the v2 intro format for hidden service
29038 connections: they specify their chosen rendezvous point by identity
29039 digest rather than by (potentially ambiguous) nickname. These
29040 changes could speed up hidden service connections dramatically.
29042 o Major bugfixes (other):
29043 - Stop publishing a new server descriptor just because we get a
29044 HUP signal. This led (in a roundabout way) to some servers getting
29045 dropped from the networkstatus lists for a few hours each day.
29046 - When looking for a circuit to cannibalize, consider family as well
29047 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
29048 circuit cannibalization).
29049 - When a router wasn't listed in a new networkstatus, we were leaving
29050 the flags for that router alone -- meaning it remained Named,
29051 Running, etc -- even though absence from the networkstatus means
29052 that it shouldn't be considered to exist at all anymore. Now we
29053 clear all the flags for routers that fall out of the networkstatus
29054 consensus. Fixes bug 529.
29057 - Don't try to access (or alter) the state file when running
29058 --list-fingerprint or --verify-config or --hash-password. Resolves
29060 - When generating information telling us how to extend to a given
29061 router, do not try to include the nickname if it is
29062 absent. Resolves bug 467.
29063 - Fix a user-triggerable segfault in expand_filename(). (There isn't
29064 a way to trigger this remotely.)
29065 - When sending a status event to the controller telling it that an
29066 OR address is reachable, set the port correctly. (Previously we
29067 were reporting the dir port.)
29068 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
29069 command. Bugfix on 0.1.2.17.
29070 - When loading bandwidth history, do not believe any information in
29071 the future. Fixes bug 434.
29072 - When loading entry guard information, do not believe any information
29074 - When we have our clock set far in the future and generate an
29075 onion key, then re-set our clock to be correct, we should not stop
29076 the onion key from getting rotated.
29077 - On some platforms, accept() can return a broken address. Detect
29078 this more quietly, and deal accordingly. Fixes bug 483.
29079 - It's not actually an error to find a non-pending entry in the DNS
29080 cache when canceling a pending resolve. Don't log unless stuff
29081 is fishy. Resolves bug 463.
29082 - Don't reset trusted dir server list when we set a configuration
29083 option. Patch from Robert Hogan.
29084 - Don't try to create the datadir when running --verify-config or
29085 --hash-password. Resolves bug 540.
29088 Changes in version 0.2.0.9-alpha - 2007-10-24
29089 This ninth development snapshot switches clients to the new v3 directory
29090 system; allows servers to be listed in the network status even when they
29091 have the same nickname as a registered server; and fixes many other
29092 bugs including a big one that was causing some servers to disappear
29093 from the network status lists for a few hours each day.
29095 o Major features (directory system):
29096 - Clients now download v3 consensus networkstatus documents instead
29097 of v2 networkstatus documents. Clients and caches now base their
29098 opinions about routers on these consensus documents. Clients only
29099 download router descriptors listed in the consensus.
29100 - Authorities now list servers who have the same nickname as
29101 a different named server, but list them with a new flag,
29102 "Unnamed". Now we can list servers that happen to pick the same
29103 nickname as a server that registered two years ago and then
29104 disappeared. Partially implements proposal 122.
29105 - If the consensus lists a router as "Unnamed", the name is assigned
29106 to a different router: do not identify the router by that name.
29107 Partially implements proposal 122.
29108 - Authorities can now come to a consensus on which method to use to
29109 compute the consensus. This gives us forward compatibility.
29112 - Stop publishing a new server descriptor just because we HUP or
29113 when we find our DirPort to be reachable but won't actually publish
29114 it. New descriptors without any real changes are dropped by the
29115 authorities, and can screw up our "publish every 18 hours" schedule.
29117 - When a router wasn't listed in a new networkstatus, we were leaving
29118 the flags for that router alone -- meaning it remained Named,
29119 Running, etc -- even though absence from the networkstatus means
29120 that it shouldn't be considered to exist at all anymore. Now we
29121 clear all the flags for routers that fall out of the networkstatus
29122 consensus. Fixes bug 529; bugfix on 0.1.2.x.
29123 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
29124 extrainfo documents and then discard them immediately for not
29125 matching the latest router. Bugfix on 0.2.0.1-alpha.
29127 o Minor features (v3 directory protocol):
29128 - Allow tor-gencert to generate a new certificate without replacing
29130 - Allow certificates to include an address.
29131 - When we change our directory-cache settings, reschedule all voting
29132 and download operations.
29133 - Reattempt certificate downloads immediately on failure, as long as
29134 we haven't failed a threshold number of times yet.
29135 - Delay retrying consensus downloads while we're downloading
29136 certificates to verify the one we just got. Also, count getting a
29137 consensus that we already have (or one that isn't valid) as a failure,
29138 and count failing to get the certificates after 20 minutes as a
29140 - Build circuits and download descriptors even if our consensus is a
29141 little expired. (This feature will go away once authorities are
29144 o Minor features (router descriptor cache):
29145 - If we find a cached-routers file that's been sitting around for more
29146 than 28 days unmodified, then most likely it's a leftover from
29147 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
29149 - When we (as a cache) download a descriptor because it was listed
29150 in a consensus, remember when the consensus was supposed to expire,
29151 and don't expire the descriptor until then.
29153 o Minor features (performance):
29154 - Call routerlist_remove_old_routers() much less often. This should
29155 speed startup, especially on directory caches.
29156 - Don't try to launch new descriptor downloads quite so often when we
29157 already have enough directory information to build circuits.
29158 - Base64 decoding was actually showing up on our profile when parsing
29159 the initial descriptor file; switch to an in-process all-at-once
29160 implementation that's about 3.5x times faster than calling out to
29163 o Minor features (compilation):
29164 - Detect non-ASCII platforms (if any still exist) and refuse to
29165 build there: some of our code assumes that 'A' is 65 and so on.
29167 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
29168 - Make the "next period" votes into "current period" votes immediately
29169 after publishing the consensus; avoid a heisenbug that made them
29170 stick around indefinitely.
29171 - When we discard a vote as a duplicate, do not report this as
29173 - Treat missing v3 keys or certificates as an error when running as a
29174 v3 directory authority.
29175 - When we're configured to be a v3 authority, but we're only listed
29176 as a non-v3 authority in our DirServer line for ourself, correct
29178 - If an authority doesn't have a qualified hostname, just put
29179 its address in the vote. This fixes the problem where we referred to
29180 "moria on moria:9031."
29181 - Distinguish between detached signatures for the wrong period, and
29182 detached signatures for a divergent vote.
29183 - Fix a small memory leak when computing a consensus.
29184 - When there's no consensus, we were forming a vote every 30
29185 minutes, but writing the "valid-after" line in our vote based
29186 on our configured V3AuthVotingInterval: so unless the intervals
29187 matched up, we immediately rejected our own vote because it didn't
29188 start at the voting interval that caused us to construct a vote.
29190 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
29191 - Delete unverified-consensus when the real consensus is set.
29192 - Consider retrying a consensus networkstatus fetch immediately
29193 after one fails: don't wait 60 seconds to notice.
29194 - When fetching a consensus as a cache, wait until a newer consensus
29195 should exist before trying to replace the current one.
29196 - Use a more forgiving schedule for retrying failed consensus
29197 downloads than for other types.
29199 o Minor bugfixes (other directory issues):
29200 - Correct the implementation of "download votes by digest." Bugfix on
29202 - Authorities no longer send back "400 you're unreachable please fix
29203 it" errors to Tor servers that aren't online all the time. We're
29204 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
29206 o Minor bugfixes (controller):
29207 - Don't reset trusted dir server list when we set a configuration
29208 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
29209 - Respond to INT and TERM SIGNAL commands before we execute the
29210 signal, in case the signal shuts us down. We had a patch in
29211 0.1.2.1-alpha that tried to do this by queueing the response on
29212 the connection's buffer before shutting down, but that really
29213 isn't the same thing at all. Bug located by Matt Edman.
29215 o Minor bugfixes (misc):
29216 - Correctly check for bad options to the "PublishServerDescriptor"
29217 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
29218 - Stop leaking memory on failing case of base32_decode, and make
29219 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
29220 - Don't try to download extrainfo documents when we're trying to
29221 fetch enough directory info to build a circuit: having enough
29222 info should get priority. Bugfix on 0.2.0.x.
29223 - Don't complain that "your server has not managed to confirm that its
29224 ports are reachable" if we haven't been able to build any circuits
29225 yet. Bug found by spending four hours without a v3 consensus. Bugfix
29227 - Detect the reason for failing to mmap a descriptor file we just
29228 wrote, and give a more useful log message. Fixes bug 533. Bugfix
29231 o Code simplifications and refactoring:
29232 - Remove support for the old bw_accounting file: we've been storing
29233 bandwidth accounting information in the state file since
29234 0.1.2.5-alpha. This may result in bandwidth accounting errors
29235 if you try to upgrade from 0.1.1.x or earlier, or if you try to
29236 downgrade to 0.1.1.x or earlier.
29237 - New convenience code to locate a file within the DataDirectory.
29238 - Move non-authority functionality out of dirvote.c.
29239 - Refactor the arguments for router_pick_{directory_|trusteddir}server
29240 so that they all take the same named flags.
29243 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
29244 Unix users an easy way to script their Tor process (e.g. by
29245 adjusting bandwidth based on the time of the day).
29248 Changes in version 0.2.0.8-alpha - 2007-10-12
29249 This eighth development snapshot fixes a crash bug that's been bothering
29250 us since February 2007, lets bridge authorities store a list of bridge
29251 descriptors they've seen, gets v3 directory voting closer to working,
29252 starts caching v3 directory consensus documents on directory mirrors,
29253 and fixes a variety of smaller issues including some minor memory leaks.
29255 o Major features (router descriptor cache):
29256 - Store routers in a file called cached-descriptors instead of in
29257 cached-routers. Initialize cached-descriptors from cached-routers
29258 if the old format is around. The new format allows us to store
29259 annotations along with descriptors.
29260 - Use annotations to record the time we received each descriptor, its
29261 source, and its purpose.
29262 - Disable the SETROUTERPURPOSE controller command: it is now
29264 - Controllers should now specify cache=no or cache=yes when using
29265 the +POSTDESCRIPTOR command.
29266 - Bridge authorities now write bridge descriptors to disk, meaning
29267 we can export them to other programs and begin distributing them
29270 o Major features (directory authorities):
29271 - When a v3 authority is missing votes or signatures, it now tries
29273 - Directory authorities track weighted fractional uptime as well as
29274 weighted mean-time-between failures. WFU is suitable for deciding
29275 whether a node is "usually up", while MTBF is suitable for deciding
29276 whether a node is "likely to stay up." We need both, because
29277 "usually up" is a good requirement for guards, while "likely to
29278 stay up" is a good requirement for long-lived connections.
29280 o Major features (v3 directory system):
29281 - Caches now download v3 network status documents as needed,
29282 and download the descriptors listed in them.
29283 - All hosts now attempt to download and keep fresh v3 authority
29284 certificates, and re-attempt after failures.
29285 - More internal-consistency checks for vote parsing.
29287 o Major bugfixes (crashes):
29288 - If a connection is shut down abruptly because of something that
29289 happened inside connection_flushed_some(), do not call
29290 connection_finished_flushing(). Should fix bug 451. Bugfix on
29293 o Major bugfixes (performance):
29294 - Fix really bad O(n^2) performance when parsing a long list of
29295 routers: Instead of searching the entire list for an "extra-info "
29296 string which usually wasn't there, once for every routerinfo
29297 we read, just scan lines forward until we find one we like.
29299 - When we add data to a write buffer in response to the data on that
29300 write buffer getting low because of a flush, do not consider the
29301 newly added data as a candidate for immediate flushing, but rather
29302 make it wait until the next round of writing. Otherwise, we flush
29303 and refill recursively, and a single greedy TLS connection can
29304 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
29306 o Minor features (v3 authority system):
29307 - Add more ways for tools to download the votes that lead to the
29309 - Send a 503 when low on bandwidth and a vote, consensus, or
29310 certificate is requested.
29311 - If-modified-since is now implemented properly for all kinds of
29312 certificate requests.
29314 o Minor bugfixes (network statuses):
29315 - Tweak the implementation of proposal 109 slightly: allow at most
29316 two Tor servers on the same IP address, except if it's the location
29317 of a directory authority, in which case allow five. Bugfix on
29320 o Minor bugfixes (controller):
29321 - When sending a status event to the controller telling it that an
29322 OR address is reachable, set the port correctly. (Previously we
29323 were reporting the dir port.) Bugfix on 0.1.2.x.
29325 o Minor bugfixes (v3 directory system):
29326 - Fix logic to look up a cert by its signing key digest. Bugfix on
29328 - Only change the reply to a vote to "OK" if it's not already
29329 set. This gets rid of annoying "400 OK" log messages, which may
29330 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
29331 - When we get a valid consensus, recompute the voting schedule.
29332 - Base the valid-after time of a vote on the consensus voting
29333 schedule, not on our preferred schedule.
29334 - Make the return values and messages from signature uploads and
29335 downloads more sensible.
29336 - Fix a memory leak when serving votes and consensus documents, and
29337 another when serving certificates.
29339 o Minor bugfixes (performance):
29340 - Use a slightly simpler string hashing algorithm (copying Python's
29341 instead of Java's) and optimize our digest hashing algorithm to take
29342 advantage of 64-bit platforms and to remove some possibly-costly
29344 - Fix a minor memory leak whenever we parse guards from our state
29345 file. Bugfix on 0.2.0.7-alpha.
29346 - Fix a minor memory leak whenever we write out a file. Bugfix on
29348 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
29349 command. Bugfix on 0.2.0.5-alpha.
29351 o Minor bugfixes (portability):
29352 - On some platforms, accept() can return a broken address. Detect
29353 this more quietly, and deal accordingly. Fixes bug 483.
29354 - Stop calling tor_strlower() on uninitialized memory in some cases.
29355 Bugfix in 0.2.0.7-alpha.
29357 o Minor bugfixes (usability):
29358 - Treat some 403 responses from directory servers as INFO rather than
29359 WARN-severity events.
29360 - It's not actually an error to find a non-pending entry in the DNS
29361 cache when canceling a pending resolve. Don't log unless stuff is
29362 fishy. Resolves bug 463.
29364 o Minor bugfixes (anonymity):
29365 - Never report that we've used more bandwidth than we're willing to
29366 relay: it leaks how much non-relay traffic we're using. Resolves
29368 - When looking for a circuit to cannibalize, consider family as well
29369 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
29370 circuit cannibalization).
29372 o Code simplifications and refactoring:
29373 - Make a bunch of functions static. Remove some dead code.
29374 - Pull out about a third of the really big routerlist.c; put it in a
29375 new module, networkstatus.c.
29376 - Merge the extra fields in local_routerstatus_t back into
29377 routerstatus_t: we used to need one routerstatus_t for each
29378 authority's opinion, plus a local_routerstatus_t for the locally
29379 computed consensus opinion. To save space, we put the locally
29380 modified fields into local_routerstatus_t, and only the common
29381 stuff into routerstatus_t. But once v3 directories are in use,
29382 clients and caches will no longer need to hold authority opinions;
29383 thus, the rationale for keeping the types separate is now gone.
29384 - Make the code used to reschedule and reattempt downloads more
29386 - Turn all 'Are we a directory server/mirror?' logic into a call to
29388 - Remove the code to generate the oldest (v1) directory format.
29389 The code has been disabled since 0.2.0.5-alpha.
29392 Changes in version 0.2.0.7-alpha - 2007-09-21
29393 This seventh development snapshot makes bridges work again, makes bridge
29394 authorities work for the first time, fixes two huge performance flaws
29395 in hidden services, and fixes a variety of minor issues.
29397 o New directory authorities:
29398 - Set up moria1 and tor26 as the first v3 directory authorities. See
29399 doc/spec/dir-spec.txt for details on the new directory design.
29401 o Major bugfixes (crashes):
29402 - Fix possible segfaults in functions called from
29403 rend_process_relay_cell(). Bugfix on 0.1.2.x.
29405 o Major bugfixes (bridges):
29406 - Fix a bug that made servers send a "404 Not found" in response to
29407 attempts to fetch their server descriptor. This caused Tor servers
29408 to take many minutes to establish reachability for their DirPort,
29409 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
29410 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
29411 users configure that and specify a bridge with an identity
29412 fingerprint, now they will lookup the bridge descriptor at the
29413 default bridge authority via a one-hop tunnel, but once circuits
29414 are established they will switch to a three-hop tunnel for later
29415 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
29417 o Major bugfixes (hidden services):
29418 - Hidden services were choosing introduction points uniquely by
29419 hexdigest, but when constructing the hidden service descriptor
29420 they merely wrote the (potentially ambiguous) nickname.
29421 - Clients now use the v2 intro format for hidden service
29422 connections: they specify their chosen rendezvous point by identity
29423 digest rather than by (potentially ambiguous) nickname. Both
29424 are bugfixes on 0.1.2.x, and they could speed up hidden service
29425 connections dramatically. Thanks to Karsten Loesing.
29427 o Minor features (security):
29428 - As a client, do not believe any server that tells us that an
29429 address maps to an internal address space.
29430 - Make it possible to enable HashedControlPassword and
29431 CookieAuthentication at the same time.
29433 o Minor features (guard nodes):
29434 - Tag every guard node in our state file with the version that
29435 we believe added it, or with our own version if we add it. This way,
29436 if a user temporarily runs an old version of Tor and then switches
29437 back to a new one, she doesn't automatically lose her guards.
29439 o Minor features (speed):
29440 - When implementing AES counter mode, update only the portions of the
29441 counter buffer that need to change, and don't keep separate
29442 network-order and host-order counters when they are the same (i.e.,
29443 on big-endian hosts.)
29445 o Minor features (controller):
29446 - Accept LF instead of CRLF on controller, since some software has a
29447 hard time generating real Internet newlines.
29448 - Add GETINFO values for the server status events
29449 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
29452 o Removed features:
29453 - Routers no longer include bandwidth-history lines in their
29454 descriptors; this information is already available in extra-info
29455 documents, and including it in router descriptors took up 60%
29456 (!) of compressed router descriptor downloads. Completes
29457 implementation of proposal 104.
29458 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
29459 and TorControl.py, as they use the old v0 controller protocol,
29460 and are obsoleted by TorFlow anyway.
29461 - Drop support for v1 rendezvous descriptors, since we never used
29462 them anyway, and the code has probably rotted by now. Based on
29463 patch from Karsten Loesing.
29464 - On OSX, stop warning the user that kqueue support in libevent is
29465 "experimental", since it seems to have worked fine for ages.
29468 - When generating information telling us how to extend to a given
29469 router, do not try to include the nickname if it is absent. Fixes
29470 bug 467. Bugfix on 0.2.0.3-alpha.
29471 - Fix a user-triggerable (but not remotely-triggerable) segfault
29472 in expand_filename(). Bugfix on 0.1.2.x.
29473 - Fix a memory leak when freeing incomplete requests from DNSPort.
29474 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
29475 - Don't try to access (or alter) the state file when running
29476 --list-fingerprint or --verify-config or --hash-password. (Resolves
29477 bug 499.) Bugfix on 0.1.2.x.
29478 - Servers used to decline to publish their DirPort if their
29479 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
29480 were below a threshold. Now they only look at BandwidthRate and
29481 RelayBandwidthRate. Bugfix on 0.1.2.x.
29482 - Remove an optimization in the AES counter-mode code that assumed
29483 that the counter never exceeded 2^68. When the counter can be set
29484 arbitrarily as an IV (as it is by Karsten's new hidden services
29485 code), this assumption no longer holds. Bugfix on 0.1.2.x.
29486 - Resume listing "AUTHORITY" flag for authorities in network status.
29487 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
29489 o Code simplifications and refactoring:
29490 - Revamp file-writing logic so we don't need to have the entire
29491 contents of a file in memory at once before we write to disk. Tor,
29493 - Turn "descriptor store" into a full-fledged type.
29494 - Move all NT services code into a separate source file.
29495 - Unify all code that computes medians, percentile elements, etc.
29496 - Get rid of a needless malloc when parsing address policies.
29499 Changes in version 0.1.2.17 - 2007-08-30
29500 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
29501 X bundles. Vidalia 0.0.14 makes authentication required for the
29502 ControlPort in the default configuration, which addresses important
29503 security risks. Everybody who uses Vidalia (or another controller)
29506 In addition, this Tor update fixes major load balancing problems with
29507 path selection, which should speed things up a lot once many people
29510 o Major bugfixes (security):
29511 - We removed support for the old (v0) control protocol. It has been
29512 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
29513 become more of a headache than it's worth.
29515 o Major bugfixes (load balancing):
29516 - When choosing nodes for non-guard positions, weight guards
29517 proportionally less, since they already have enough load. Patch
29519 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
29520 will allow fast Tor servers to get more attention.
29521 - When we're upgrading from an old Tor version, forget our current
29522 guards and pick new ones according to the new weightings. These
29523 three load balancing patches could raise effective network capacity
29524 by a factor of four. Thanks to Mike Perry for measurements.
29526 o Major bugfixes (stream expiration):
29527 - Expire not-yet-successful application streams in all cases if
29528 they've been around longer than SocksTimeout. Right now there are
29529 some cases where the stream will live forever, demanding a new
29530 circuit every 15 seconds. Fixes bug 454; reported by lodger.
29532 o Minor features (controller):
29533 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
29534 is valid before any authentication has been received. It tells
29535 a controller what kind of authentication is expected, and what
29536 protocol is spoken. Implements proposal 119.
29538 o Minor bugfixes (performance):
29539 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
29540 greatly speeding up loading cached-routers from disk on startup.
29541 - Disable sentinel-based debugging for buffer code: we squashed all
29542 the bugs that this was supposed to detect a long time ago, and now
29543 its only effect is to change our buffer sizes from nice powers of
29544 two (which platform mallocs tend to like) to values slightly over
29545 powers of two (which make some platform mallocs sad).
29547 o Minor bugfixes (misc):
29548 - If exit bandwidth ever exceeds one third of total bandwidth, then
29549 use the correct formula to weight exit nodes when choosing paths.
29550 Based on patch from Mike Perry.
29551 - Choose perfectly fairly among routers when choosing by bandwidth and
29552 weighting by fraction of bandwidth provided by exits. Previously, we
29553 would choose with only approximate fairness, and correct ourselves
29554 if we ran off the end of the list.
29555 - If we require CookieAuthentication but we fail to write the
29556 cookie file, we would warn but not exit, and end up in a state
29557 where no controller could authenticate. Now we exit.
29558 - If we require CookieAuthentication, stop generating a new cookie
29559 every time we change any piece of our config.
29560 - Refuse to start with certain directory authority keys, and
29561 encourage people using them to stop.
29562 - Terminate multi-line control events properly. Original patch
29564 - Fix a minor memory leak when we fail to find enough suitable
29565 servers to choose a circuit.
29566 - Stop leaking part of the descriptor when we run into a particularly
29567 unparseable piece of it.
29570 Changes in version 0.2.0.6-alpha - 2007-08-26
29571 This sixth development snapshot features a new Vidalia version in the
29572 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
29573 the ControlPort in the default configuration, which addresses important
29576 In addition, this snapshot fixes major load balancing problems
29577 with path selection, which should speed things up a lot once many
29578 people have upgraded. The directory authorities also use a new
29579 mean-time-between-failure approach to tracking which servers are stable,
29580 rather than just looking at the most recent uptime.
29582 o New directory authorities:
29583 - Set up Tonga as the default bridge directory authority.
29586 - Directory authorities now track servers by weighted
29587 mean-times-between-failures. When we have 4 or more days of data,
29588 use measured MTBF rather than declared uptime to decide whether
29589 to call a router Stable. Implements proposal 108.
29591 o Major bugfixes (load balancing):
29592 - When choosing nodes for non-guard positions, weight guards
29593 proportionally less, since they already have enough load. Patch
29595 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
29596 will allow fast Tor servers to get more attention.
29597 - When we're upgrading from an old Tor version, forget our current
29598 guards and pick new ones according to the new weightings. These
29599 three load balancing patches could raise effective network capacity
29600 by a factor of four. Thanks to Mike Perry for measurements.
29602 o Major bugfixes (descriptor parsing):
29603 - Handle unexpected whitespace better in malformed descriptors. Bug
29604 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
29607 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
29608 GETINFO for Torstat to use until it can switch to using extrainfos.
29609 - Optionally (if built with -DEXPORTMALLINFO) export the output
29610 of mallinfo via http, as tor/mallinfo.txt. Only accessible
29614 - Do not intermix bridge routers with controller-added
29615 routers. (Bugfix on 0.2.0.x)
29616 - Do not fail with an assert when accept() returns an unexpected
29617 address family. Addresses but does not wholly fix bug 483. (Bugfix
29619 - Let directory authorities startup even when they can't generate
29620 a descriptor immediately, e.g. because they don't know their
29622 - Stop putting the authentication cookie in a file called "0"
29623 in your working directory if you don't specify anything for the
29624 new CookieAuthFile option. Reported by Matt Edman.
29625 - Make it possible to read the PROTOCOLINFO response in a way that
29626 conforms to our control-spec. Reported by Matt Edman.
29627 - Fix a minor memory leak when we fail to find enough suitable
29628 servers to choose a circuit. Bugfix on 0.1.2.x.
29629 - Stop leaking part of the descriptor when we run into a particularly
29630 unparseable piece of it. Bugfix on 0.1.2.x.
29631 - Unmap the extrainfo cache file on exit.
29634 Changes in version 0.2.0.5-alpha - 2007-08-19
29635 This fifth development snapshot fixes compilation on Windows again;
29636 fixes an obnoxious client-side bug that slowed things down and put
29637 extra load on the network; gets us closer to using the v3 directory
29638 voting scheme; makes it easier for Tor controllers to use cookie-based
29639 authentication; and fixes a variety of other bugs.
29641 o Removed features:
29642 - Version 1 directories are no longer generated in full. Instead,
29643 authorities generate and serve "stub" v1 directories that list
29644 no servers. This will stop Tor versions 0.1.0.x and earlier from
29645 working, but (for security reasons) nobody should be running those
29648 o Major bugfixes (compilation, 0.2.0.x):
29649 - Try to fix Win32 compilation again: improve checking for IPv6 types.
29650 - Try to fix MSVC compilation: build correctly on platforms that do
29651 not define s6_addr16 or s6_addr32.
29652 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
29655 o Major bugfixes (stream expiration):
29656 - Expire not-yet-successful application streams in all cases if
29657 they've been around longer than SocksTimeout. Right now there are
29658 some cases where the stream will live forever, demanding a new
29659 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
29660 reported by lodger.
29662 o Minor features (directory servers):
29663 - When somebody requests a list of statuses or servers, and we have
29664 none of those, return a 404 rather than an empty 200.
29666 o Minor features (directory voting):
29667 - Store v3 consensus status consensuses on disk, and reload them
29670 o Minor features (security):
29671 - Warn about unsafe ControlPort configurations.
29672 - Refuse to start with certain directory authority keys, and
29673 encourage people using them to stop.
29675 o Minor features (controller):
29676 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
29677 is valid before any authentication has been received. It tells
29678 a controller what kind of authentication is expected, and what
29679 protocol is spoken. Implements proposal 119.
29680 - New config option CookieAuthFile to choose a new location for the
29681 cookie authentication file, and config option
29682 CookieAuthFileGroupReadable to make it group-readable.
29684 o Minor features (unit testing):
29685 - Add command-line arguments to unit-test executable so that we can
29686 invoke any chosen test from the command line rather than having
29687 to run the whole test suite at once; and so that we can turn on
29688 logging for the unit tests.
29690 o Minor bugfixes (on 0.1.2.x):
29691 - If we require CookieAuthentication but we fail to write the
29692 cookie file, we would warn but not exit, and end up in a state
29693 where no controller could authenticate. Now we exit.
29694 - If we require CookieAuthentication, stop generating a new cookie
29695 every time we change any piece of our config.
29696 - When loading bandwidth history, do not believe any information in
29697 the future. Fixes bug 434.
29698 - When loading entry guard information, do not believe any information
29700 - When we have our clock set far in the future and generate an
29701 onion key, then re-set our clock to be correct, we should not stop
29702 the onion key from getting rotated.
29703 - Clean up torrc sample config file.
29704 - Do not automatically run configure from autogen.sh. This
29705 non-standard behavior tended to annoy people who have built other
29708 o Minor bugfixes (on 0.2.0.x):
29709 - Fix a bug with AutomapHostsOnResolve that would always cause
29710 the second request to fail. Bug reported by Kate. Bugfix on
29712 - Fix a bug in ADDRMAP controller replies that would sometimes
29713 try to print a NULL. Patch from tup.
29714 - Read v3 directory authority keys from the right location.
29715 - Numerous bugfixes to directory voting code.
29718 Changes in version 0.1.2.16 - 2007-08-01
29719 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
29720 remote attacker in certain situations to rewrite the user's torrc
29721 configuration file. This can completely compromise anonymity of users
29722 in most configurations, including those running the Vidalia bundles,
29723 TorK, etc. Or worse.
29725 o Major security fixes:
29726 - Close immediately after missing authentication on control port;
29727 do not allow multiple authentication attempts.
29730 Changes in version 0.2.0.4-alpha - 2007-08-01
29731 This fourth development snapshot fixes a critical security vulnerability
29732 for most users, specifically those running Vidalia, TorK, etc. Everybody
29733 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
29735 o Major security fixes:
29736 - Close immediately after missing authentication on control port;
29737 do not allow multiple authentication attempts.
29739 o Major bugfixes (compilation):
29740 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
29743 o Minor features (performance):
29744 - Be even more aggressive about releasing RAM from small
29745 empty buffers. Thanks to our free-list code, this shouldn't be too
29746 performance-intensive.
29747 - Disable sentinel-based debugging for buffer code: we squashed all
29748 the bugs that this was supposed to detect a long time ago, and
29749 now its only effect is to change our buffer sizes from nice
29750 powers of two (which platform mallocs tend to like) to values
29751 slightly over powers of two (which make some platform mallocs sad).
29752 - Log malloc statistics from mallinfo() on platforms where it
29756 Changes in version 0.2.0.3-alpha - 2007-07-29
29757 This third development snapshot introduces new experimental
29758 blocking-resistance features and a preliminary version of the v3
29759 directory voting design, and includes many other smaller features
29763 - The first pieces of our "bridge" design for blocking-resistance
29764 are implemented. People can run bridge directory authorities;
29765 people can run bridges; and people can configure their Tor clients
29766 with a set of bridges to use as the first hop into the Tor network.
29767 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
29769 - Create listener connections before we setuid to the configured
29770 User and Group. Now non-Windows users can choose port values
29771 under 1024, start Tor as root, and have Tor bind those ports
29772 before it changes to another UID. (Windows users could already
29774 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
29775 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
29776 on "vserver" accounts. (Patch from coderman.)
29777 - Be even more aggressive about separating local traffic from relayed
29778 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
29780 o Major features (experimental):
29781 - First cut of code for "v3 dir voting": directory authorities will
29782 vote on a common network status document rather than each publishing
29783 their own opinion. This code needs more testing and more corner-case
29784 handling before it's ready for use.
29787 - Directory authorities now call routers Fast if their bandwidth is
29788 at least 100KB/s, and consider their bandwidth adequate to be a
29789 Guard if it is at least 250KB/s, no matter the medians. This fix
29790 complements proposal 107. [Bugfix on 0.1.2.x]
29791 - Directory authorities now never mark more than 3 servers per IP as
29792 Valid and Running. (Implements proposal 109, by Kevin Bauer and
29794 - Minor change to organizationName and commonName generation
29795 procedures in TLS certificates during Tor handshakes, to invalidate
29796 some earlier censorware approaches. This is not a long-term
29797 solution, but applying it will give us a bit of time to look into
29798 the epidemiology of countermeasures as they spread.
29800 o Major bugfixes (directory):
29801 - Rewrite directory tokenization code to never run off the end of
29802 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
29804 o Minor features (controller):
29805 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
29806 match requests to applications. (Patch from Robert Hogan.)
29807 - Report address and port correctly on connections to DNSPort. (Patch
29808 from Robert Hogan.)
29809 - Add a RESOLVE command to launch hostname lookups. (Original patch
29810 from Robert Hogan.)
29811 - Add GETINFO status/enough-dir-info to let controllers tell whether
29812 Tor has downloaded sufficient directory information. (Patch
29814 - You can now use the ControlSocket option to tell Tor to listen for
29815 controller connections on Unix domain sockets on systems that
29816 support them. (Patch from Peter Palfrader.)
29817 - STREAM NEW events are generated for DNSPort requests and for
29818 tunneled directory connections. (Patch from Robert Hogan.)
29819 - New "GETINFO address-mappings/*" command to get address mappings
29820 with expiry information. "addr-mappings/*" is now deprecated.
29823 o Minor features (misc):
29824 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
29826 - The tor-gencert tool for v3 directory authorities now creates all
29827 files as readable to the file creator only, and write-protects
29828 the authority identity key.
29829 - When dumping memory usage, list bytes used in buffer memory
29831 - When running with dmalloc, dump more stats on hup and on exit.
29832 - Directory authorities now fail quickly and (relatively) harmlessly
29833 if they generate a network status document that is somehow
29836 o Traffic load balancing improvements:
29837 - If exit bandwidth ever exceeds one third of total bandwidth, then
29838 use the correct formula to weight exit nodes when choosing paths.
29839 (Based on patch from Mike Perry.)
29840 - Choose perfectly fairly among routers when choosing by bandwidth and
29841 weighting by fraction of bandwidth provided by exits. Previously, we
29842 would choose with only approximate fairness, and correct ourselves
29843 if we ran off the end of the list. [Bugfix on 0.1.2.x]
29845 o Performance improvements:
29846 - Be more aggressive with freeing buffer RAM or putting it on the
29848 - Use Critical Sections rather than Mutexes for synchronizing threads
29849 on win32; Mutexes are heavier-weight, and designed for synchronizing
29852 o Deprecated and removed features:
29853 - RedirectExits is now deprecated.
29854 - Stop allowing address masks that do not correspond to bit prefixes.
29855 We have warned about these for a really long time; now it's time
29856 to reject them. (Patch from croup.)
29858 o Minor bugfixes (directory):
29859 - Fix another crash bug related to extra-info caching. (Bug found by
29860 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
29861 - Directories no longer return a "304 not modified" when they don't
29862 have the networkstatus the client asked for. Also fix a memory
29863 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
29864 - We had accidentally labelled 0.1.2.x directory servers as not
29865 suitable for begin_dir requests, and had labelled no directory
29866 servers as suitable for uploading extra-info documents. [Bugfix
29869 o Minor bugfixes (dns):
29870 - Fix a crash when DNSPort is set more than once. (Patch from Robert
29871 Hogan.) [Bugfix on 0.2.0.2-alpha]
29872 - Add DNSPort connections to the global connection list, so that we
29873 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
29875 - Fix a dangling reference that could lead to a crash when DNSPort is
29876 changed or closed (Patch from Robert Hogan.) [Bugfix on
29879 o Minor bugfixes (controller):
29880 - Provide DNS expiry times in GMT, not in local time. For backward
29881 compatibility, ADDRMAP events only provide GMT expiry in an extended
29882 field. "GETINFO address-mappings" always does the right thing.
29883 - Use CRLF line endings properly in NS events.
29884 - Terminate multi-line control events properly. (Original patch
29885 from tup.) [Bugfix on 0.1.2.x-alpha]
29886 - Do not include spaces in SOURCE_ADDR fields in STREAM
29887 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
29890 Changes in version 0.1.2.15 - 2007-07-17
29891 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
29892 problems, fixes compilation on BSD, and fixes a variety of other
29893 bugs. Everybody should upgrade.
29895 o Major bugfixes (compilation):
29896 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
29898 o Major bugfixes (crashes):
29899 - Try even harder not to dereference the first character after
29900 an mmap(). Reported by lodger.
29901 - Fix a crash bug in directory authorities when we re-number the
29902 routerlist while inserting a new router.
29903 - When the cached-routers file is an even multiple of the page size,
29904 don't run off the end and crash. (Fixes bug 455; based on idea
29906 - Fix eventdns.c behavior on Solaris: It is critical to include
29907 orconfig.h _before_ sys/types.h, so that we can get the expected
29908 definition of _FILE_OFFSET_BITS.
29910 o Major bugfixes (security):
29911 - Fix a possible buffer overrun when using BSD natd support. Bug
29913 - When sending destroy cells from a circuit's origin, don't include
29914 the reason for tearing down the circuit. The spec says we didn't,
29915 and now we actually don't. Reported by lodger.
29916 - Keep streamids from different exits on a circuit separate. This
29917 bug may have allowed other routers on a given circuit to inject
29918 cells into streams. Reported by lodger; fixes bug 446.
29919 - If there's a never-before-connected-to guard node in our list,
29920 never choose any guards past it. This way we don't expand our
29921 guard list unless we need to.
29923 o Minor bugfixes (guard nodes):
29924 - Weight guard selection by bandwidth, so that low-bandwidth nodes
29925 don't get overused as guards.
29927 o Minor bugfixes (directory):
29928 - Correctly count the number of authorities that recommend each
29929 version. Previously, we were under-counting by 1.
29930 - Fix a potential crash bug when we load many server descriptors at
29931 once and some of them make others of them obsolete. Fixes bug 458.
29933 o Minor bugfixes (hidden services):
29934 - Stop tearing down the whole circuit when the user asks for a
29935 connection to a port that the hidden service didn't configure.
29938 o Minor bugfixes (misc):
29939 - On Windows, we were preventing other processes from reading
29940 cached-routers while Tor was running. Reported by janbar.
29941 - Fix a possible (but very unlikely) bug in picking routers by
29942 bandwidth. Add a log message to confirm that it is in fact
29943 unlikely. Patch from lodger.
29944 - Backport a couple of memory leak fixes.
29945 - Backport miscellaneous cosmetic bugfixes.
29948 Changes in version 0.2.0.2-alpha - 2007-06-02
29949 o Major bugfixes on 0.2.0.1-alpha:
29950 - Fix an assertion failure related to servers without extra-info digests.
29951 Resolves bugs 441 and 442.
29953 o Minor features (directory):
29954 - Support "If-Modified-Since" when answering HTTP requests for
29955 directories, running-routers documents, and network-status documents.
29956 (There's no need to support it for router descriptors, since those
29957 are downloaded by descriptor digest.)
29959 o Minor build issues:
29960 - Clear up some MIPSPro compiler warnings.
29961 - When building from a tarball on a machine that happens to have SVK
29962 installed, report the micro-revision as whatever version existed
29963 in the tarball, not as "x".
29966 Changes in version 0.2.0.1-alpha - 2007-06-01
29967 This early development snapshot provides new features for people running
29968 Tor as both a client and a server (check out the new RelayBandwidth
29969 config options); lets Tor run as a DNS proxy; and generally moves us
29970 forward on a lot of fronts.
29972 o Major features, server usability:
29973 - New config options RelayBandwidthRate and RelayBandwidthBurst:
29974 a separate set of token buckets for relayed traffic. Right now
29975 relayed traffic is defined as answers to directory requests, and
29976 OR connections that don't have any local circuits on them.
29978 o Major features, client usability:
29979 - A client-side DNS proxy feature to replace the need for
29980 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
29981 for DNS requests on port 9999, use the Tor network to resolve them
29982 anonymously, and send the reply back like a regular DNS server.
29983 The code still only implements a subset of DNS.
29984 - Make PreferTunneledDirConns and TunnelDirConns work even when
29985 we have no cached directory info. This means Tor clients can now
29986 do all of their connections protected by TLS.
29988 o Major features, performance and efficiency:
29989 - Directory authorities accept and serve "extra info" documents for
29990 routers. These documents contain fields from router descriptors
29991 that aren't usually needed, and that use a lot of excess
29992 bandwidth. Once these fields are removed from router descriptors,
29993 the bandwidth savings should be about 60%. [Partially implements
29995 - Servers upload extra-info documents to any authority that accepts
29996 them. Authorities (and caches that have been configured to download
29997 extra-info documents) download them as needed. [Partially implements
29999 - Change the way that Tor buffers data that it is waiting to write.
30000 Instead of queueing data cells in an enormous ring buffer for each
30001 client->OR or OR->OR connection, we now queue cells on a separate
30002 queue for each circuit. This lets us use less slack memory, and
30003 will eventually let us be smarter about prioritizing different kinds
30005 - Use memory pools to allocate cells with better speed and memory
30006 efficiency, especially on platforms where malloc() is inefficient.
30007 - Stop reading on edge connections when their corresponding circuit
30008 buffers are full; start again as the circuits empty out.
30010 o Major features, other:
30011 - Add an HSAuthorityRecordStats option that hidden service authorities
30012 can use to track statistics of overall hidden service usage without
30013 logging information that would be very useful to an attacker.
30014 - Start work implementing multi-level keys for directory authorities:
30015 Add a standalone tool to generate key certificates. (Proposal 103.)
30018 - Directory authorities now call routers Stable if they have an
30019 uptime of at least 30 days, even if that's not the median uptime
30020 in the network. Implements proposal 107, suggested by Kevin Bauer
30023 o Minor fixes (resource management):
30024 - Count the number of open sockets separately from the number
30025 of active connection_t objects. This will let us avoid underusing
30026 our allocated connection limit.
30027 - We no longer use socket pairs to link an edge connection to an
30028 anonymous directory connection or a DirPort test connection.
30029 Instead, we track the link internally and transfer the data
30030 in-process. This saves two sockets per "linked" connection (at the
30031 client and at the server), and avoids the nasty Windows socketpair()
30033 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
30034 for every single inactive connection_t. Free items from the
30035 4k/16k-buffer free lists when they haven't been used for a while.
30037 o Minor features (build):
30038 - Make autoconf search for libevent, openssl, and zlib consistently.
30039 - Update deprecated macros in configure.in.
30040 - When warning about missing headers, tell the user to let us
30041 know if the compile succeeds anyway, so we can downgrade the
30043 - Include the current subversion revision as part of the version
30044 string: either fetch it directly if we're in an SVN checkout, do
30045 some magic to guess it if we're in an SVK checkout, or use
30046 the last-detected version if we're building from a .tar.gz.
30047 Use this version consistently in log messages.
30049 o Minor features (logging):
30050 - Always prepend "Bug: " to any log message about a bug.
30051 - Put a platform string (e.g. "Linux i686") in the startup log
30052 message, so when people paste just their logs, we know if it's
30053 OpenBSD or Windows or what.
30054 - When logging memory usage, break down memory used in buffers by
30057 o Minor features (directory system):
30058 - New config option V2AuthoritativeDirectory that all directory
30059 authorities should set. This will let future authorities choose
30060 not to serve V2 directory information.
30061 - Directory authorities allow multiple router descriptors and/or extra
30062 info documents to be uploaded in a single go. This will make
30063 implementing proposal 104 simpler.
30065 o Minor features (controller):
30066 - Add a new config option __DisablePredictedCircuits designed for
30067 use by the controller, when we don't want Tor to build any circuits
30069 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
30070 so we can exit from the middle of the circuit.
30071 - Implement "getinfo status/circuit-established".
30072 - Implement "getinfo status/version/..." so a controller can tell
30073 whether the current version is recommended, and whether any versions
30074 are good, and how many authorities agree. (Patch from shibz.)
30076 o Minor features (hidden services):
30077 - Allow multiple HiddenServicePort directives with the same virtual
30078 port; when they occur, the user is sent round-robin to one
30079 of the target ports chosen at random. Partially fixes bug 393 by
30080 adding limited ad-hoc round-robining.
30082 o Minor features (other):
30084 - Add a new AutomapHostsOnResolve option: when it is enabled, any
30085 resolve request for hosts matching a given pattern causes Tor to
30086 generate an internal virtual address mapping for that host. This
30087 allows DNSPort to work sensibly with hidden service users. By
30088 default, .exit and .onion addresses are remapped; the list of
30089 patterns can be reconfigured with AutomapHostsSuffixes.
30090 - Add an "-F" option to tor-resolve to force a resolve for a .onion
30091 address. Thanks to the AutomapHostsOnResolve option, this is no
30092 longer a completely silly thing to do.
30093 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
30094 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
30095 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
30096 minus 1 byte: the actual maximum declared bandwidth.
30098 o Removed features:
30099 - Removed support for the old binary "version 0" controller protocol.
30100 This has been deprecated since 0.1.1, and warnings have been issued
30101 since 0.1.2. When we encounter a v0 control message, we now send
30102 back an error and close the connection.
30103 - Remove the old "dns worker" server DNS code: it hasn't been default
30104 since 0.1.2.2-alpha, and all the servers seem to be using the new
30107 o Minor bugfixes (portability):
30108 - Even though Windows is equally happy with / and \ as path separators,
30109 try to use \ consistently on Windows and / consistently on Unix: it
30110 makes the log messages nicer.
30111 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
30112 - Read resolv.conf files correctly on platforms where read() returns
30113 partial results on small file reads.
30115 o Minor bugfixes (directory):
30116 - Correctly enforce that elements of directory objects do not appear
30117 more often than they are allowed to appear.
30118 - When we are reporting the DirServer line we just parsed, we were
30119 logging the second stanza of the key fingerprint, not the first.
30121 o Minor bugfixes (logging):
30122 - When we hit an EOF on a log (probably because we're shutting down),
30123 don't try to remove the log from the list: just mark it as
30124 unusable. (Bulletproofs against bug 222.)
30126 o Minor bugfixes (other):
30127 - In the exitlist script, only consider the most recently published
30128 server descriptor for each server. Also, when the user requests
30129 a list of servers that _reject_ connections to a given address,
30130 explicitly exclude the IPs that also have servers that accept
30131 connections to that address. (Resolves bug 405.)
30132 - Stop allowing hibernating servers to be "stable" or "fast".
30133 - On Windows, we were preventing other processes from reading
30134 cached-routers while Tor was running. (Reported by janbar)
30135 - Make the NodeFamilies config option work. (Reported by
30136 lodger -- it has never actually worked, even though we added it
30138 - Check return values from pthread_mutex functions.
30139 - Don't save non-general-purpose router descriptors to the disk cache,
30140 because we have no way of remembering what their purpose was when
30142 - Add even more asserts to hunt down bug 417.
30143 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
30144 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
30145 Add a log message to confirm that it is in fact unlikely.
30147 o Minor bugfixes (controller):
30148 - Make 'getinfo fingerprint' return a 551 error if we're not a
30149 server, so we match what the control spec claims we do. Reported
30151 - Fix a typo in an error message when extendcircuit fails that
30152 caused us to not follow the \r\n-based delimiter protocol. Reported
30155 o Code simplifications and refactoring:
30156 - Stop passing around circuit_t and crypt_path_t pointers that are
30157 implicit in other procedure arguments.
30158 - Drop the old code to choke directory connections when the
30159 corresponding OR connections got full: thanks to the cell queue
30160 feature, OR conns don't get full any more.
30161 - Make dns_resolve() handle attaching connections to circuits
30162 properly, so the caller doesn't have to.
30163 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
30164 - Keep the connection array as a dynamic smartlist_t, rather than as
30165 a fixed-sized array. This is important, as the number of connections
30166 is becoming increasingly decoupled from the number of sockets.
30169 Changes in version 0.1.2.14 - 2007-05-25
30170 Tor 0.1.2.14 changes the addresses of two directory authorities (this
30171 change especially affects those who serve or use hidden services),
30172 and fixes several other crash- and security-related bugs.
30174 o Directory authority changes:
30175 - Two directory authorities (moria1 and moria2) just moved to new
30176 IP addresses. This change will particularly affect those who serve
30177 or use hidden services.
30179 o Major bugfixes (crashes):
30180 - If a directory server runs out of space in the connection table
30181 as it's processing a begin_dir request, it will free the exit stream
30182 but leave it attached to the circuit, leading to unpredictable
30183 behavior. (Reported by seeess, fixes bug 425.)
30184 - Fix a bug in dirserv_remove_invalid() that would cause authorities
30185 to corrupt memory under some really unlikely scenarios.
30186 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
30187 - Avoid segfaults when reading from mmaped descriptor file. (Reported
30190 o Major bugfixes (security):
30191 - When choosing an entry guard for a circuit, avoid using guards
30192 that are in the same family as the chosen exit -- not just guards
30193 that are exactly the chosen exit. (Reported by lodger.)
30195 o Major bugfixes (resource management):
30196 - If a directory authority is down, skip it when deciding where to get
30197 networkstatus objects or descriptors. Otherwise we keep asking
30198 every 10 seconds forever. Fixes bug 384.
30199 - Count it as a failure if we fetch a valid network-status but we
30200 don't want to keep it. Otherwise we'll keep fetching it and keep
30201 not wanting to keep it. Fixes part of bug 422.
30202 - If all of our dirservers have given us bad or no networkstatuses
30203 lately, then stop hammering them once per minute even when we
30204 think they're failed. Fixes another part of bug 422.
30207 - Actually set the purpose correctly for descriptors inserted with
30208 purpose=controller.
30209 - When we have k non-v2 authorities in our DirServer config,
30210 we ignored the last k authorities in the list when updating our
30212 - Correctly back-off from requesting router descriptors that we are
30213 having a hard time downloading.
30214 - Read resolv.conf files correctly on platforms where read() returns
30215 partial results on small file reads.
30216 - Don't rebuild the entire router store every time we get 32K of
30217 routers: rebuild it when the journal gets very large, or when
30218 the gaps in the store get very large.
30221 - When routers publish SVN revisions in their router descriptors,
30222 authorities now include those versions correctly in networkstatus
30224 - Warn when using a version of libevent before 1.3b to run a server on
30225 OSX or BSD: these versions interact badly with userspace threads.
30228 Changes in version 0.1.2.13 - 2007-04-24
30229 This release features some major anonymity fixes, such as safer path
30230 selection; better client performance; faster bootstrapping, better
30231 address detection, and better DNS support for servers; write limiting as
30232 well as read limiting to make servers easier to run; and a huge pile of
30233 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
30235 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
30236 of the Freenode IRC network, remembering his patience and vision for
30237 free speech on the Internet.
30240 - Fix a memory leak when we ask for "all" networkstatuses and we
30241 get one we don't recognize.
30242 - Add more asserts to hunt down bug 417.
30243 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
30246 Changes in version 0.1.2.12-rc - 2007-03-16
30248 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
30249 directory information requested inside Tor connections (i.e. via
30250 begin_dir cells). It only triggered when the same connection was
30251 serving other data at the same time. Reported by seeess.
30254 - When creating a circuit via the controller, send a 'launched'
30255 event when we're done, so we follow the spec better.
30258 Changes in version 0.1.2.11-rc - 2007-03-15
30259 o Minor bugfixes (controller), reported by daejees:
30260 - Correct the control spec to match how the code actually responds
30261 to 'getinfo addr-mappings/*'.
30262 - The control spec described a GUARDS event, but the code
30263 implemented a GUARD event. Standardize on GUARD, but let people
30264 ask for GUARDS too.
30267 Changes in version 0.1.2.10-rc - 2007-03-07
30268 o Major bugfixes (Windows):
30269 - Do not load the NT services library functions (which may not exist)
30270 just to detect if we're a service trying to shut down. Now we run
30271 on Win98 and friends again.
30273 o Minor bugfixes (other):
30274 - Clarify a couple of log messages.
30275 - Fix a misleading socks5 error number.
30278 Changes in version 0.1.2.9-rc - 2007-03-02
30279 o Major bugfixes (Windows):
30280 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
30281 of the usual GCC "%llu". This prevents a bug when saving 64-bit
30282 int configuration values: the high-order 32 bits would get
30283 truncated. In particular, we were being bitten by the default
30284 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
30285 and maybe also bug 397.)
30287 o Minor bugfixes (performance):
30288 - Use OpenSSL's AES implementation on platforms where it's faster.
30289 This could save us as much as 10% CPU usage.
30291 o Minor bugfixes (server):
30292 - Do not rotate onion key immediately after setting it for the first
30295 o Minor bugfixes (directory authorities):
30296 - Stop calling servers that have been hibernating for a long time
30297 "stable". Also, stop letting hibernating or obsolete servers affect
30298 uptime and bandwidth cutoffs.
30299 - Stop listing hibernating servers in the v1 directory.
30301 o Minor bugfixes (hidden services):
30302 - Upload hidden service descriptors slightly less often, to reduce
30303 load on authorities.
30305 o Minor bugfixes (other):
30306 - Fix an assert that could trigger if a controller quickly set then
30307 cleared EntryNodes. Bug found by Udo van den Heuvel.
30308 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
30310 - Fix a potential race condition in the rpm installer. Found by
30312 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
30313 of 2 as indicating that the server is completely bad; it sometimes
30314 means that the server is just bad for the request in question. (may fix
30315 the last of bug 326.)
30316 - Disable encrypted directory connections when we don't have a server
30317 descriptor for the destination. We'll get this working again in
30321 Changes in version 0.1.2.8-beta - 2007-02-26
30322 o Major bugfixes (crashes):
30323 - Stop crashing when the controller asks us to resetconf more than
30324 one config option at once. (Vidalia 0.0.11 does this.)
30325 - Fix a crash that happened on Win98 when we're given command-line
30326 arguments: don't try to load NT service functions from advapi32.dll
30327 except when we need them. (Bug introduced in 0.1.2.7-alpha;
30329 - Fix a longstanding obscure crash bug that could occur when
30330 we run out of DNS worker processes. (Resolves bug 390.)
30332 o Major bugfixes (hidden services):
30333 - Correctly detect whether hidden service descriptor downloads are
30334 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
30336 o Major bugfixes (accounting):
30337 - When we start during an accounting interval before it's time to wake
30338 up, remember to wake up at the correct time. (May fix bug 342.)
30340 o Minor bugfixes (controller):
30341 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
30342 clear the corresponding on_circuit variable, and remember later
30343 that we don't need to send a redundant CLOSED event. Resolves part
30345 - Report events where a resolve succeeded or where we got a socks
30346 protocol error correctly, rather than calling both of them
30348 - Change reported stream target addresses to IP consistently when
30349 we finally get the IP from an exit node.
30350 - Send log messages to the controller even if they happen to be very
30353 o Minor bugfixes (other):
30354 - Display correct results when reporting which versions are
30355 recommended, and how recommended they are. (Resolves bug 383.)
30356 - Improve our estimates for directory bandwidth to be less random:
30357 guess that an unrecognized directory will have the average bandwidth
30358 from all known directories, not that it will have the average
30359 bandwidth from those directories earlier than it on the list.
30360 - If we start a server with ClientOnly 1, then set ClientOnly to 0
30361 and hup, stop triggering an assert based on an empty onion_key.
30362 - On platforms with no working mmap() equivalent, don't warn the
30363 user when cached-routers doesn't exist.
30364 - Warn the user when mmap() [or its equivalent] fails for some reason
30365 other than file-not-found.
30366 - Don't warn the user when cached-routers.new doesn't exist: that's
30367 perfectly fine when starting up for the first time.
30368 - When EntryNodes are configured, rebuild the guard list to contain,
30369 in order: the EntryNodes that were guards before; the rest of the
30370 EntryNodes; the nodes that were guards before.
30371 - Mask out all signals in sub-threads; only the libevent signal
30372 handler should be processing them. This should prevent some crashes
30373 on some machines using pthreads. (Patch from coderman.)
30374 - Fix switched arguments on memset in the implementation of
30375 tor_munmap() for systems with no mmap() call.
30376 - When Tor receives a router descriptor that it asked for, but
30377 no longer wants (because it has received fresh networkstatuses
30378 in the meantime), do not warn the user. Cache the descriptor if
30379 we're a cache; drop it if we aren't.
30380 - Make earlier entry guards _really_ get retried when the network
30382 - On a malformed DNS reply, always give an error to the corresponding
30384 - Build with recent libevents on platforms that do not define the
30385 nonstandard types "u_int8_t" and friends.
30387 o Minor features (controller):
30388 - Warn the user when an application uses the obsolete binary v0
30389 control protocol. We're planning to remove support for it during
30390 the next development series, so it's good to give people some
30392 - Add STREAM_BW events to report per-entry-stream bandwidth
30393 use. (Patch from Robert Hogan.)
30394 - Rate-limit SIGNEWNYM signals in response to controllers that
30395 impolitely generate them for every single stream. (Patch from
30396 mwenge; closes bug 394.)
30397 - Make REMAP stream events have a SOURCE (cache or exit), and
30398 make them generated in every case where we get a successful
30399 connected or resolved cell.
30401 o Minor bugfixes (performance):
30402 - Call router_have_min_dir_info half as often. (This is showing up in
30403 some profiles, but not others.)
30404 - When using GCC, make log_debug never get called at all, and its
30405 arguments never get evaluated, when no debug logs are configured.
30406 (This is showing up in some profiles, but not others.)
30409 - Remove some never-implemented options. Mark PathlenCoinWeight as
30411 - Implement proposal 106: Stop requiring clients to have well-formed
30412 certificates; stop checking nicknames in certificates. (Clients
30413 have certificates so that they can look like Tor servers, but in
30414 the future we might want to allow them to look like regular TLS
30415 clients instead. Nicknames in certificates serve no purpose other
30416 than making our protocol easier to recognize on the wire.)
30417 - Revise messages on handshake failure again to be even more clear about
30418 which are incoming connections and which are outgoing.
30419 - Discard any v1 directory info that's over 1 month old (for
30420 directories) or over 1 week old (for running-routers lists).
30421 - Do not warn when individual nodes in the configuration's EntryNodes,
30422 ExitNodes, etc are down: warn only when all possible nodes
30423 are down. (Fixes bug 348.)
30424 - Always remove expired routers and networkstatus docs before checking
30425 whether we have enough information to build circuits. (Fixes
30427 - Put a lower-bound on MaxAdvertisedBandwidth.
30430 Changes in version 0.1.2.7-alpha - 2007-02-06
30431 o Major bugfixes (rate limiting):
30432 - Servers decline directory requests much more aggressively when
30433 they're low on bandwidth. Otherwise they end up queueing more and
30434 more directory responses, which can't be good for latency.
30435 - But never refuse directory requests from local addresses.
30436 - Fix a memory leak when sending a 503 response for a networkstatus
30438 - Be willing to read or write on local connections (e.g. controller
30439 connections) even when the global rate limiting buckets are empty.
30440 - If our system clock jumps back in time, don't publish a negative
30441 uptime in the descriptor. Also, don't let the global rate limiting
30442 buckets go absurdly negative.
30443 - Flush local controller connection buffers periodically as we're
30444 writing to them, so we avoid queueing 4+ megabytes of data before
30447 o Major bugfixes (NT services):
30448 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
30449 command-line flag so that admins can override the default by saying
30450 "tor --service install --user "SomeUser"". This will not affect
30451 existing installed services. Also, warn the user that the service
30452 will look for its configuration file in the service user's
30453 %appdata% directory. (We can't do the 'hardwire the user's appdata
30454 directory' trick any more, since we may not have read access to that
30457 o Major bugfixes (other):
30458 - Previously, we would cache up to 16 old networkstatus documents
30459 indefinitely, if they came from nontrusted authorities. Now we
30460 discard them if they are more than 10 days old.
30461 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
30463 - Detect and reject malformed DNS responses containing circular
30465 - If exits are rare enough that we're not marking exits as guards,
30466 ignore exit bandwidth when we're deciding the required bandwidth
30468 - When we're handling a directory connection tunneled over Tor,
30469 don't fill up internal memory buffers with all the data we want
30470 to tunnel; instead, only add it if the OR connection that will
30471 eventually receive it has some room for it. (This can lead to
30472 slowdowns in tunneled dir connections; a better solution will have
30473 to wait for 0.2.0.)
30475 o Minor bugfixes (dns):
30476 - Add some defensive programming to eventdns.c in an attempt to catch
30477 possible memory-stomping bugs.
30478 - Detect and reject DNS replies containing IPv4 or IPv6 records with
30479 an incorrect number of bytes. (Previously, we would ignore the
30481 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
30482 in the correct order, and doesn't crash.
30483 - Free memory held in recently-completed DNS lookup attempts on exit.
30484 This was not a memory leak, but may have been hiding memory leaks.
30485 - Handle TTL values correctly on reverse DNS lookups.
30486 - Treat failure to parse resolv.conf as an error.
30488 o Minor bugfixes (other):
30489 - Fix crash with "tor --list-fingerprint" (reported by seeess).
30490 - When computing clock skew from directory HTTP headers, consider what
30491 time it was when we finished asking for the directory, not what
30493 - Expire socks connections if they spend too long waiting for the
30494 handshake to finish. Previously we would let them sit around for
30495 days, if the connecting application didn't close them either.
30496 - And if the socks handshake hasn't started, don't send a
30497 "DNS resolve socks failed" handshake reply; just close it.
30498 - Stop using C functions that OpenBSD's linker doesn't like.
30499 - Don't launch requests for descriptors unless we have networkstatuses
30500 from at least half of the authorities. This delays the first
30501 download slightly under pathological circumstances, but can prevent
30502 us from downloading a bunch of descriptors we don't need.
30503 - Do not log IPs with TLS failures for incoming TLS
30504 connections. (Fixes bug 382.)
30505 - If the user asks to use invalid exit nodes, be willing to use
30507 - Stop using the reserved ac_cv namespace in our configure script.
30508 - Call stat() slightly less often; use fstat() when possible.
30509 - Refactor the way we handle pending circuits when an OR connection
30510 completes or fails, in an attempt to fix a rare crash bug.
30511 - Only rewrite a conn's address based on X-Forwarded-For: headers
30512 if it's a parseable public IP address; and stop adding extra quotes
30513 to the resulting address.
30516 - Weight directory requests by advertised bandwidth. Now we can
30517 let servers enable write limiting but still allow most clients to
30518 succeed at their directory requests. (We still ignore weights when
30519 choosing a directory authority; I hope this is a feature.)
30522 - Create a new file ReleaseNotes which was the old ChangeLog. The
30523 new ChangeLog file now includes the summaries for all development
30525 - Check for addresses with invalid characters at the exit as well
30526 as at the client, and warn less verbosely when they fail. You can
30527 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
30528 - Adapt a patch from goodell to let the contrib/exitlist script
30529 take arguments rather than require direct editing.
30530 - Inform the server operator when we decide not to advertise a
30531 DirPort due to AccountingMax enabled or a low BandwidthRate. It
30532 was confusing Zax, so now we're hopefully more helpful.
30533 - Bring us one step closer to being able to establish an encrypted
30534 directory tunnel without knowing a descriptor first. Still not
30535 ready yet. As part of the change, now assume we can use a
30536 create_fast cell if we don't know anything about a router.
30537 - Allow exit nodes to use nameservers running on ports other than 53.
30538 - Servers now cache reverse DNS replies.
30539 - Add an --ignore-missing-torrc command-line option so that we can
30540 get the "use sensible defaults if the configuration file doesn't
30541 exist" behavior even when specifying a torrc location on the command
30544 o Minor features (controller):
30545 - Track reasons for OR connection failure; make these reasons
30546 available via the controller interface. (Patch from Mike Perry.)
30547 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
30548 can learn when clients are sending malformed hostnames to Tor.
30549 - Clean up documentation for controller status events.
30550 - Add a REMAP status to stream events to note that a stream's
30551 address has changed because of a cached address or a MapAddress
30555 Changes in version 0.1.2.6-alpha - 2007-01-09
30557 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
30558 connection handles more than 4 gigs in either direction, we crash.
30559 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
30560 advertised exit node, somebody might try to exit from us when
30561 we're bootstrapping and before we've built our descriptor yet.
30562 Refuse the connection rather than crashing.
30565 - Warn if we (as a server) find that we've resolved an address that we
30566 weren't planning to resolve.
30567 - Warn that using select() on any libevent version before 1.1 will be
30568 unnecessarily slow (even for select()).
30569 - Flush ERR-level controller status events just like we currently
30570 flush ERR-level log events, so that a Tor shutdown doesn't prevent
30571 the controller from learning about current events.
30573 o Minor features (more controller status events):
30574 - Implement EXTERNAL_ADDRESS server status event so controllers can
30575 learn when our address changes.
30576 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
30577 can learn when directories reject our descriptor.
30578 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
30579 can learn when a client application is speaking a non-socks protocol
30581 - Implement DANGEROUS_SOCKS client status event so controllers
30582 can learn when a client application is leaking DNS addresses.
30583 - Implement BUG general status event so controllers can learn when
30584 Tor is unhappy about its internal invariants.
30585 - Implement CLOCK_SKEW general status event so controllers can learn
30586 when Tor thinks the system clock is set incorrectly.
30587 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
30588 server status events so controllers can learn when their descriptors
30589 are accepted by a directory.
30590 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
30591 server status events so controllers can learn about Tor's progress in
30592 deciding whether it's reachable from the outside.
30593 - Implement BAD_LIBEVENT general status event so controllers can learn
30594 when we have a version/method combination in libevent that needs to
30596 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
30597 and DNS_USELESS server status events so controllers can learn
30598 about changes to DNS server status.
30600 o Minor features (directory):
30601 - Authorities no longer recommend exits as guards if this would shift
30602 too much load to the exit nodes.
30605 Changes in version 0.1.2.5-alpha - 2007-01-06
30607 - Enable write limiting as well as read limiting. Now we sacrifice
30608 capacity if we're pushing out lots of directory traffic, rather
30609 than overrunning the user's intended bandwidth limits.
30610 - Include TLS overhead when counting bandwidth usage; previously, we
30611 would count only the bytes sent over TLS, but not the bytes used
30613 - Support running the Tor service with a torrc not in the same
30614 directory as tor.exe and default to using the torrc located in
30615 the %appdata%\Tor\ of the user who installed the service. Patch
30617 - Servers now check for the case when common DNS requests are going to
30618 wildcarded addresses (i.e. all getting the same answer), and change
30619 their exit policy to reject *:* if it's happening.
30620 - Implement BEGIN_DIR cells, so we can connect to the directory
30621 server via TLS to do encrypted directory requests rather than
30622 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
30623 config options if you like.
30625 o Minor features (config and docs):
30626 - Start using the state file to store bandwidth accounting data:
30627 the bw_accounting file is now obsolete. We'll keep generating it
30628 for a while for people who are still using 0.1.2.4-alpha.
30629 - Try to batch changes to the state file so that we do as few
30630 disk writes as possible while still storing important things in
30632 - The state file and the bw_accounting file get saved less often when
30633 the AvoidDiskWrites config option is set.
30634 - Make PIDFile work on Windows (untested).
30635 - Add internal descriptions for a bunch of configuration options:
30636 accessible via controller interface and in comments in saved
30638 - Reject *:563 (NNTPS) in the default exit policy. We already reject
30639 NNTP by default, so this seems like a sensible addition.
30640 - Clients now reject hostnames with invalid characters. This should
30641 avoid some inadvertent info leaks. Add an option
30642 AllowNonRFC953Hostnames to disable this behavior, in case somebody
30643 is running a private network with hosts called @, !, and #.
30644 - Add a maintainer script to tell us which options are missing
30645 documentation: "make check-docs".
30646 - Add a new address-spec.txt document to describe our special-case
30647 addresses: .exit, .onion, and .noconnnect.
30649 o Minor features (DNS):
30650 - Ongoing work on eventdns infrastructure: now it has dns server
30651 and ipv6 support. One day Tor will make use of it.
30652 - Add client-side caching for reverse DNS lookups.
30653 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
30654 - When we change nameservers or IP addresses, reset and re-launch
30655 our tests for DNS hijacking.
30657 o Minor features (directory):
30658 - Authorities now specify server versions in networkstatus. This adds
30659 about 2% to the size of compressed networkstatus docs, and allows
30660 clients to tell which servers support BEGIN_DIR and which don't.
30661 The implementation is forward-compatible with a proposed future
30662 protocol version scheme not tied to Tor versions.
30663 - DirServer configuration lines now have an orport= option so
30664 clients can open encrypted tunnels to the authorities without
30665 having downloaded their descriptors yet. Enabled for moria1,
30666 moria2, tor26, and lefkada now in the default configuration.
30667 - Directory servers are more willing to send a 503 "busy" if they
30668 are near their write limit, especially for v1 directory requests.
30669 Now they can use their limited bandwidth for actual Tor traffic.
30670 - Clients track responses with status 503 from dirservers. After a
30671 dirserver has given us a 503, we try not to use it until an hour has
30672 gone by, or until we have no dirservers that haven't given us a 503.
30673 - When we get a 503 from a directory, and we're not a server, we don't
30674 count the failure against the total number of failures allowed
30675 for the thing we're trying to download.
30676 - Report X-Your-Address-Is correctly from tunneled directory
30677 connections; don't report X-Your-Address-Is when it's an internal
30678 address; and never believe reported remote addresses when they're
30680 - Protect against an unlikely DoS attack on directory servers.
30681 - Add a BadDirectory flag to network status docs so that authorities
30682 can (eventually) tell clients about caches they believe to be
30685 o Minor features (controller):
30686 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
30687 - Reimplement GETINFO so that info/names stays in sync with the
30689 - Implement "GETINFO fingerprint".
30690 - Implement "SETEVENTS GUARD" so controllers can get updates on
30691 entry guard status as it changes.
30693 o Minor features (clean up obsolete pieces):
30694 - Remove some options that have been deprecated since at least
30695 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
30696 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
30697 to set log options.
30698 - We no longer look for identity and onion keys in "identity.key" and
30699 "onion.key" -- these were replaced by secret_id_key and
30700 secret_onion_key in 0.0.8pre1.
30701 - We no longer require unrecognized directory entries to be
30704 o Major bugfixes (security):
30705 - Stop sending the HttpProxyAuthenticator string to directory
30706 servers when directory connections are tunnelled through Tor.
30707 - Clients no longer store bandwidth history in the state file.
30708 - Do not log introduction points for hidden services if SafeLogging
30710 - When generating bandwidth history, round down to the nearest
30711 1k. When storing accounting data, round up to the nearest 1k.
30712 - When we're running as a server, remember when we last rotated onion
30713 keys, so that we will rotate keys once they're a week old even if
30714 we never stay up for a week ourselves.
30716 o Major bugfixes (other):
30717 - Fix a longstanding bug in eventdns that prevented the count of
30718 timed-out resolves from ever being reset. This bug caused us to
30719 give up on a nameserver the third time it timed out, and try it
30720 10 seconds later... and to give up on it every time it timed out
30722 - Take out the '5 second' timeout from the connection retry
30723 schedule. Now the first connect attempt will wait a full 10
30724 seconds before switching to a new circuit. Perhaps this will help
30725 a lot. Based on observations from Mike Perry.
30726 - Fix a bug on the Windows implementation of tor_mmap_file() that
30727 would prevent the cached-routers file from ever loading. Reported
30731 - Fix an assert failure when a directory authority sets
30732 AuthDirRejectUnlisted and then receives a descriptor from an
30733 unlisted router. Reported by seeess.
30734 - Avoid a double-free when parsing malformed DirServer lines.
30735 - Fix a bug when a BSD-style PF socket is first used. Patch from
30737 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
30738 to resolve an address at a given exit node even when they ask for
30740 - Servers no longer ever list themselves in their "family" line,
30741 even if configured to do so. This makes it easier to configure
30742 family lists conveniently.
30743 - When running as a server, don't fall back to 127.0.0.1 when no
30744 nameservers are configured in /etc/resolv.conf; instead, make the
30745 user fix resolv.conf or specify nameservers explicitly. (Resolves
30747 - Stop accepting certain malformed ports in configured exit policies.
30748 - Don't re-write the fingerprint file every restart, unless it has
30750 - Stop warning when a single nameserver fails: only warn when _all_ of
30751 our nameservers have failed. Also, when we only have one nameserver,
30752 raise the threshold for deciding that the nameserver is dead.
30753 - Directory authorities now only decide that routers are reachable
30754 if their identity keys are as expected.
30755 - When the user uses bad syntax in the Log config line, stop
30756 suggesting other bad syntax as a replacement.
30757 - Correctly detect ipv6 DNS capability on OpenBSD.
30759 o Minor bugfixes (controller):
30760 - Report the circuit number correctly in STREAM CLOSED events. Bug
30761 reported by Mike Perry.
30762 - Do not report bizarre values for results of accounting GETINFOs
30763 when the last second's write or read exceeds the allotted bandwidth.
30764 - Report "unrecognized key" rather than an empty string when the
30765 controller tries to fetch a networkstatus that doesn't exist.
30768 Changes in version 0.1.1.26 - 2006-12-14
30769 o Security bugfixes:
30770 - Stop sending the HttpProxyAuthenticator string to directory
30771 servers when directory connections are tunnelled through Tor.
30772 - Clients no longer store bandwidth history in the state file.
30773 - Do not log introduction points for hidden services if SafeLogging
30777 - Fix an assert failure when a directory authority sets
30778 AuthDirRejectUnlisted and then receives a descriptor from an
30779 unlisted router (reported by seeess).
30782 Changes in version 0.1.2.4-alpha - 2006-12-03
30784 - Add support for using natd; this allows FreeBSDs earlier than
30785 5.1.2 to have ipfw send connections through Tor without using
30786 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
30789 - Make all connections to addresses of the form ".noconnect"
30790 immediately get closed. This lets application/controller combos
30791 successfully test whether they're talking to the same Tor by
30792 watching for STREAM events.
30793 - Make cross.sh cross-compilation script work even when autogen.sh
30794 hasn't been run. (Patch from Michael Mohr.)
30795 - Statistics dumped by -USR2 now include a breakdown of public key
30796 operations, for profiling.
30799 - Fix a major leak when directory authorities parse their
30800 approved-routers list, a minor memory leak when we fail to pick
30801 an exit node, and a few rare leaks on errors.
30802 - Handle TransPort connections even when the server sends data before
30803 the client sends data. Previously, the connection would just hang
30804 until the client sent data. (Patch from tup based on patch from
30806 - Avoid assert failure when our cached-routers file is empty on
30810 - Don't log spurious warnings when we see a circuit close reason we
30811 don't recognize; it's probably just from a newer version of Tor.
30812 - Have directory authorities allow larger amounts of drift in uptime
30813 without replacing the server descriptor: previously, a server that
30814 restarted every 30 minutes could have 48 "interesting" descriptors
30816 - Start linking to the Tor specification and Tor reference manual
30817 correctly in the Windows installer.
30818 - Add Vidalia to the OS X uninstaller script, so when we uninstall
30819 Tor/Privoxy we also uninstall Vidalia.
30820 - Resume building on Irix64, and fix a lot of warnings from its
30821 MIPSpro C compiler.
30822 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
30823 when we're running as a client.
30826 Changes in version 0.1.1.25 - 2006-11-04
30828 - When a client asks us to resolve (rather than connect to)
30829 an address, and we have a cached answer, give them the cached
30830 answer. Previously, we would give them no answer at all.
30831 - We were building exactly the wrong circuits when we predict
30832 hidden service requirements, meaning Tor would have to build all
30833 its circuits on demand.
30834 - If none of our live entry guards have a high uptime, but we
30835 require a guard with a high uptime, try adding a new guard before
30836 we give up on the requirement. This patch should make long-lived
30837 connections more stable on average.
30838 - When testing reachability of our DirPort, don't launch new
30839 tests when there's already one in progress -- unreachable
30840 servers were stacking up dozens of testing streams.
30842 o Security bugfixes:
30843 - When the user sends a NEWNYM signal, clear the client-side DNS
30844 cache too. Otherwise we continue to act on previous information.
30847 - Avoid a memory corruption bug when creating a hash table for
30849 - Avoid possibility of controller-triggered crash when misusing
30850 certain commands from a v0 controller on platforms that do not
30851 handle printf("%s",NULL) gracefully.
30852 - Avoid infinite loop on unexpected controller input.
30853 - Don't log spurious warnings when we see a circuit close reason we
30854 don't recognize; it's probably just from a newer version of Tor.
30855 - Add Vidalia to the OS X uninstaller script, so when we uninstall
30856 Tor/Privoxy we also uninstall Vidalia.
30859 Changes in version 0.1.2.3-alpha - 2006-10-29
30861 - Prepare for servers to publish descriptors less often: never
30862 discard a descriptor simply for being too old until either it is
30863 recommended by no authorities, or until we get a better one for
30864 the same router. Make caches consider retaining old recommended
30865 routers for even longer.
30866 - If most authorities set a BadExit flag for a server, clients
30867 don't think of it as a general-purpose exit. Clients only consider
30868 authorities that advertise themselves as listing bad exits.
30869 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
30870 headers for content, so that we can work better in the presence of
30871 caching HTTP proxies.
30872 - Allow authorities to list nodes as bad exits by fingerprint or by
30875 o Minor features, controller:
30876 - Add a REASON field to CIRC events; for backward compatibility, this
30877 field is sent only to controllers that have enabled the extended
30878 event format. Also, add additional reason codes to explain why
30879 a given circuit has been destroyed or truncated. (Patches from
30881 - Add a REMOTE_REASON field to extended CIRC events to tell the
30882 controller about why a remote OR told us to close a circuit.
30883 - Stream events also now have REASON and REMOTE_REASON fields,
30884 working much like those for circuit events.
30885 - There's now a GETINFO ns/... field so that controllers can ask Tor
30886 about the current status of a router.
30887 - A new event type "NS" to inform a controller when our opinion of
30888 a router's status has changed.
30889 - Add a GETINFO events/names and GETINFO features/names so controllers
30890 can tell which events and features are supported.
30891 - A new CLEARDNSCACHE signal to allow controllers to clear the
30892 client-side DNS cache without expiring circuits.
30894 o Security bugfixes:
30895 - When the user sends a NEWNYM signal, clear the client-side DNS
30896 cache too. Otherwise we continue to act on previous information.
30899 - Avoid sending junk to controllers or segfaulting when a controller
30900 uses EVENT_NEW_DESC with verbose nicknames.
30901 - Stop triggering asserts if the controller tries to extend hidden
30902 service circuits (reported by mwenge).
30903 - Avoid infinite loop on unexpected controller input.
30904 - When the controller does a "GETINFO network-status", tell it
30905 about even those routers whose descriptors are very old, and use
30906 long nicknames where appropriate.
30907 - Change NT service functions to be loaded on demand. This lets us
30908 build with MinGW without breaking Tor for Windows 98 users.
30909 - Do DirPort reachability tests less often, since a single test
30910 chews through many circuits before giving up.
30911 - In the hidden service example in torrc.sample, stop recommending
30912 esoteric and discouraged hidden service options.
30913 - When stopping an NT service, wait up to 10 sec for it to actually
30914 stop. Patch from Matt Edman; resolves bug 295.
30915 - Fix handling of verbose nicknames with ORCONN controller events:
30916 make them show up exactly when requested, rather than exactly when
30918 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
30919 printing a duplicate "$" in the keys we send (reported by mwenge).
30920 - Correctly set maximum connection limit on Cygwin. (This time
30922 - Try to detect Windows correctly when cross-compiling.
30923 - Detect the size of the routers file correctly even if it is
30924 corrupted (on systems without mmap) or not page-aligned (on systems
30925 with mmap). This bug was harmless.
30926 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
30927 to open a stream fails; now we do in more cases. This should
30928 make clients able to find a good exit faster in some cases, since
30929 unhandleable requests will now get an error rather than timing out.
30930 - Resolve two memory leaks when rebuilding the on-disk router cache
30931 (reported by fookoowa).
30932 - Clean up minor code warnings suggested by the MIPSpro C compiler,
30933 and reported by some Centos users.
30934 - Controller signals now work on non-Unix platforms that don't define
30935 SIGUSR1 and SIGUSR2 the way we expect.
30936 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
30937 values before failing, and always enables eventdns.
30938 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
30939 Try to fix this in configure.in by checking for most functions
30940 before we check for libevent.
30943 Changes in version 0.1.2.2-alpha - 2006-10-07
30945 - Make our async eventdns library on-by-default for Tor servers,
30946 and plan to deprecate the separate dnsworker threads.
30947 - Add server-side support for "reverse" DNS lookups (using PTR
30948 records so clients can determine the canonical hostname for a given
30949 IPv4 address). Only supported by servers using eventdns; servers
30950 now announce in their descriptors whether they support eventdns.
30951 - Specify and implement client-side SOCKS5 interface for reverse DNS
30952 lookups (see doc/socks-extensions.txt).
30953 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
30954 connect to directory servers through Tor. Previously, clients needed
30955 to find Tor exits to make private connections to directory servers.
30956 - Avoid choosing Exit nodes for entry or middle hops when the
30957 total bandwidth available from non-Exit nodes is much higher than
30958 the total bandwidth available from Exit nodes.
30959 - Workaround for name servers (like Earthlink's) that hijack failing
30960 DNS requests and replace the no-such-server answer with a "helpful"
30961 redirect to an advertising-driven search portal. Also work around
30962 DNS hijackers who "helpfully" decline to hijack known-invalid
30963 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
30964 lets you turn it off.
30965 - Send out a burst of long-range padding cells once we've established
30966 that we're reachable. Spread them over 4 circuits, so hopefully
30967 a few will be fast. This exercises our bandwidth and bootstraps
30968 us into the directory more quickly.
30970 o New/improved config options:
30971 - Add new config option "ResolvConf" to let the server operator
30972 choose an alternate resolve.conf file when using eventdns.
30973 - Add an "EnforceDistinctSubnets" option to control our "exclude
30974 servers on the same /16" behavior. It's still on by default; this
30975 is mostly for people who want to operate private test networks with
30976 all the machines on the same subnet.
30977 - If one of our entry guards is on the ExcludeNodes list, or the
30978 directory authorities don't think it's a good guard, treat it as
30979 if it were unlisted: stop using it as a guard, and throw it off
30980 the guards list if it stays that way for a long time.
30981 - Allow directory authorities to be marked separately as authorities
30982 for the v1 directory protocol, the v2 directory protocol, and
30983 as hidden service directories, to make it easier to retire old
30984 authorities. V1 authorities should set "HSAuthoritativeDir 1"
30985 to continue being hidden service authorities too.
30986 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
30988 o Minor features, controller:
30989 - Fix CIRC controller events so that controllers can learn the
30990 identity digests of non-Named servers used in circuit paths.
30991 - Let controllers ask for more useful identifiers for servers. Instead
30992 of learning identity digests for un-Named servers and nicknames
30993 for Named servers, the new identifiers include digest, nickname,
30994 and indication of Named status. Off by default; see control-spec.txt
30995 for more information.
30996 - Add a "getinfo address" controller command so it can display Tor's
30997 best guess to the user.
30998 - New controller event to alert the controller when our server
30999 descriptor has changed.
31000 - Give more meaningful errors on controller authentication failure.
31002 o Minor features, other:
31003 - When asked to resolve a hostname, don't use non-exit servers unless
31004 requested to do so. This allows servers with broken DNS to be
31005 useful to the network.
31006 - Divide eventdns log messages into warn and info messages.
31007 - Reserve the nickname "Unnamed" for routers that can't pick
31008 a hostname: any router can call itself Unnamed; directory
31009 authorities will never allocate Unnamed to any particular router;
31010 clients won't believe that any router is the canonical Unnamed.
31011 - Only include function names in log messages for info/debug messages.
31012 For notice/warn/err, the content of the message should be clear on
31013 its own, and printing the function name only confuses users.
31014 - Avoid some false positives during reachability testing: don't try
31015 to test via a server that's on the same /24 as us.
31016 - If we fail to build a circuit to an intended enclave, and it's
31017 not mandatory that we use that enclave, stop wanting it.
31018 - When eventdns is enabled, allow multithreaded builds on NetBSD and
31019 OpenBSD. (We had previously disabled threads on these platforms
31020 because they didn't have working thread-safe resolver functions.)
31022 o Major bugfixes, anonymity/security:
31023 - If a client asked for a server by name, and there's a named server
31024 in our network-status but we don't have its descriptor yet, we
31025 could return an unnamed server instead.
31026 - Fix NetBSD bug that could allow someone to force uninitialized RAM
31027 to be sent to a server's DNS resolver. This only affects NetBSD
31028 and other platforms that do not bounds-check tolower().
31029 - Reject (most) attempts to use Tor circuits with length one. (If
31030 many people start using Tor as a one-hop proxy, exit nodes become
31031 a more attractive target for compromise.)
31032 - Just because your DirPort is open doesn't mean people should be
31033 able to remotely teach you about hidden service descriptors. Now
31034 only accept rendezvous posts if you've got HSAuthoritativeDir set.
31036 o Major bugfixes, other:
31037 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
31038 - When a client asks the server to resolve (not connect to)
31039 an address, and it has a cached answer, give them the cached answer.
31040 Previously, the server would give them no answer at all.
31041 - Allow really slow clients to not hang up five minutes into their
31042 directory downloads (suggested by Adam J. Richter).
31043 - We were building exactly the wrong circuits when we anticipated
31044 hidden service requirements, meaning Tor would have to build all
31045 its circuits on demand.
31046 - Avoid crashing when we mmap a router cache file of size 0.
31047 - When testing reachability of our DirPort, don't launch new
31048 tests when there's already one in progress -- unreachable
31049 servers were stacking up dozens of testing streams.
31051 o Minor bugfixes, correctness:
31052 - If we're a directory mirror and we ask for "all" network status
31053 documents, we would discard status documents from authorities
31054 we don't recognize.
31055 - Avoid a memory corruption bug when creating a hash table for
31057 - Avoid controller-triggered crash when misusing certain commands
31058 from a v0 controller on platforms that do not handle
31059 printf("%s",NULL) gracefully.
31060 - Don't crash when a controller sends a third argument to an
31061 "extendcircuit" request.
31062 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
31063 response; fix error code when "getinfo dir/status/" fails.
31064 - Avoid crash when telling controller stream-status and a stream
31066 - Patch from Adam Langley to fix assert() in eventdns.c.
31067 - Fix a debug log message in eventdns to say "X resolved to Y"
31068 instead of "X resolved to X".
31069 - Make eventdns give strings for DNS errors, not just error numbers.
31070 - Track unreachable entry guards correctly: don't conflate
31071 'unreachable by us right now' with 'listed as down by the directory
31072 authorities'. With the old code, if a guard was unreachable by
31073 us but listed as running, it would clog our guard list forever.
31074 - Behave correctly in case we ever have a network with more than
31075 2GB/s total advertised capacity.
31076 - Make TrackExitHosts case-insensitive, and fix the behavior of
31077 ".suffix" TrackExitHosts items to avoid matching in the middle of
31079 - Finally fix the openssl warnings from newer gccs that believe that
31080 ignoring a return value is okay, but casting a return value and
31081 then ignoring it is a sign of madness.
31082 - Prevent the contrib/exitlist script from printing the same
31083 result more than once.
31084 - Patch from Steve Hildrey: Generate network status correctly on
31085 non-versioning dirservers.
31086 - Don't listen to the X-Your-Address-Is hint if you did the lookup
31087 via Tor; otherwise you'll think you're the exit node's IP address.
31089 o Minor bugfixes, performance:
31090 - Two small performance improvements on parsing descriptors.
31091 - Major performance improvement on inserting descriptors: change
31092 algorithm from O(n^2) to O(n).
31093 - Make the common memory allocation path faster on machines where
31094 malloc(0) returns a pointer.
31095 - Start remembering X-Your-Address-Is directory hints even if you're
31096 a client, so you can become a server more smoothly.
31097 - Avoid duplicate entries on MyFamily line in server descriptor.
31099 o Packaging, features:
31100 - Remove architecture from OS X builds. The official builds are
31101 now universal binaries.
31102 - The Debian package now uses --verify-config when (re)starting,
31103 to distinguish configuration errors from other errors.
31104 - Update RPMs to require libevent 1.1b.
31106 o Packaging, bugfixes:
31107 - Patches so Tor builds with MinGW on Windows.
31108 - Patches so Tor might run on Cygwin again.
31109 - Resume building on non-gcc compilers and ancient gcc. Resume
31110 building with the -O0 compile flag. Resume building cleanly on
31112 - Run correctly on OS X platforms with case-sensitive filesystems.
31113 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
31114 - Add autoconf checks so Tor can build on Solaris x86 again.
31117 - Documented (and renamed) ServerDNSSearchDomains and
31118 ServerDNSResolvConfFile options.
31119 - Be clearer that the *ListenAddress directives can be repeated
31123 Changes in version 0.1.1.24 - 2006-09-29
31125 - Allow really slow clients to not hang up five minutes into their
31126 directory downloads (suggested by Adam J. Richter).
31127 - Fix major performance regression from 0.1.0.x: instead of checking
31128 whether we have enough directory information every time we want to
31129 do something, only check when the directory information has changed.
31130 This should improve client CPU usage by 25-50%.
31131 - Don't crash if, after a server has been running for a while,
31132 it can't resolve its hostname.
31135 - Allow Tor to start when RunAsDaemon is set but no logs are set.
31136 - Don't crash when the controller receives a third argument to an
31137 "extendcircuit" request.
31138 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
31139 response; fix error code when "getinfo dir/status/" fails.
31140 - Fix configure.in to not produce broken configure files with
31141 more recent versions of autoconf. Thanks to Clint for his auto*
31143 - Fix security bug on NetBSD that could allow someone to force
31144 uninitialized RAM to be sent to a server's DNS resolver. This
31145 only affects NetBSD and other platforms that do not bounds-check
31147 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
31148 methods: these are known to be buggy.
31149 - If we're a directory mirror and we ask for "all" network status
31150 documents, we would discard status documents from authorities
31151 we don't recognize.
31154 Changes in version 0.1.2.1-alpha - 2006-08-27
31156 - Add "eventdns" async dns library from Adam Langley, tweaked to
31157 build on OSX and Windows. Only enabled if you pass the
31158 --enable-eventdns argument to configure.
31159 - Allow servers with no hostname or IP address to learn their
31160 IP address by asking the directory authorities. This code only
31161 kicks in when you would normally have exited with a "no address"
31162 error. Nothing's authenticated, so use with care.
31163 - Rather than waiting a fixed amount of time between retrying
31164 application connections, we wait only 5 seconds for the first,
31165 10 seconds for the second, and 15 seconds for each retry after
31166 that. Hopefully this will improve the expected user experience.
31167 - Patch from Tup to add support for transparent AP connections:
31168 this basically bundles the functionality of trans-proxy-tor
31169 into the Tor mainline. Now hosts with compliant pf/netfilter
31170 implementations can redirect TCP connections straight to Tor
31171 without diverting through SOCKS. Needs docs.
31172 - Busy directory servers save lots of memory by spooling server
31173 descriptors, v1 directories, and v2 networkstatus docs to buffers
31174 as needed rather than en masse. Also mmap the cached-routers
31175 files, so we don't need to keep the whole thing in memory too.
31176 - Automatically avoid picking more than one node from the same
31177 /16 network when constructing a circuit.
31178 - Revise and clean up the torrc.sample that we ship with; add
31179 a section for BandwidthRate and BandwidthBurst.
31182 - Split circuit_t into origin_circuit_t and or_circuit_t, and
31183 split connection_t into edge, or, dir, control, and base structs.
31184 These will save quite a bit of memory on busy servers, and they'll
31185 also help us track down bugs in the code and bugs in the spec.
31186 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
31187 or later. Log when we are doing this, so we can diagnose it when
31188 it fails. (Also, recommend libevent 1.1b for kqueue and
31189 win32 methods; deprecate libevent 1.0b harder; make libevent
31190 recommendation system saner.)
31191 - Start being able to build universal binaries on OS X (thanks
31193 - Export the default exit policy via the control port, so controllers
31194 don't need to guess what it is / will be later.
31195 - Add a man page entry for ProtocolWarnings.
31196 - Add TestVia config option to the man page.
31197 - Remove even more protocol-related warnings from Tor server logs,
31198 such as bad TLS handshakes and malformed begin cells.
31199 - Stop fetching descriptors if you're not a dir mirror and you
31200 haven't tried to establish any circuits lately. [This currently
31201 causes some dangerous behavior, because when you start up again
31202 you'll use your ancient server descriptors.]
31203 - New DirPort behavior: if you have your dirport set, you download
31204 descriptors aggressively like a directory mirror, whether or not
31205 your ORPort is set.
31206 - Get rid of the router_retry_connections notion. Now routers
31207 no longer try to rebuild long-term connections to directory
31208 authorities, and directory authorities no longer try to rebuild
31209 long-term connections to all servers. We still don't hang up
31210 connections in these two cases though -- we need to look at it
31211 more carefully to avoid flapping, and we likely need to wait til
31212 0.1.1.x is obsolete.
31213 - Drop compatibility with obsolete Tors that permit create cells
31214 to have the wrong circ_id_type.
31215 - Re-enable per-connection rate limiting. Get rid of the "OP
31216 bandwidth" concept. Lay groundwork for "bandwidth classes" --
31217 separate global buckets that apply depending on what sort of conn
31219 - Start publishing one minute or so after we find our ORPort
31220 to be reachable. This will help reduce the number of descriptors
31221 we have for ourselves floating around, since it's quite likely
31222 other things (e.g. DirPort) will change during that minute too.
31223 - Fork the v1 directory protocol into its own spec document,
31224 and mark dir-spec.txt as the currently correct (v2) spec.
31227 - When we find our DirPort to be reachable, publish a new descriptor
31228 so we'll tell the world (reported by pnx).
31229 - Publish a new descriptor after we hup/reload. This is important
31230 if our config has changed such that we'll want to start advertising
31231 our DirPort now, etc.
31232 - Allow Tor to start when RunAsDaemon is set but no logs are set.
31233 - When we have a state file we cannot parse, tell the user and
31234 move it aside. Now we avoid situations where the user starts
31235 Tor in 1904, Tor writes a state file with that timestamp in it,
31236 the user fixes her clock, and Tor refuses to start.
31237 - Fix configure.in to not produce broken configure files with
31238 more recent versions of autoconf. Thanks to Clint for his auto*
31240 - "tor --verify-config" now exits with -1(255) or 0 depending on
31241 whether the config options are bad or good.
31242 - Resolve bug 321 when using dnsworkers: append a period to every
31243 address we resolve at the exit node, so that we do not accidentally
31244 pick up local addresses, and so that failing searches are retried
31245 in the resolver search domains. (This is already solved for
31246 eventdns.) (This breaks Blossom servers for now.)
31247 - If we are using an exit enclave and we can't connect, e.g. because
31248 its webserver is misconfigured to not listen on localhost, then
31249 back off and try connecting from somewhere else before we fail.
31252 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
31253 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
31254 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
31255 when the IP address is mapped through MapAddress to a hostname.
31256 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
31257 useless IPv6 DNS resolves.
31258 - Patch suggested by Karsten Loesing: respond to SIGNAL command
31259 before we execute the signal, in case the signal shuts us down.
31260 - Clean up AllowInvalidNodes man page entry.
31261 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
31262 - Add more asserts to track down an assert error on a windows Tor
31263 server with connection_add being called with socket == -1.
31264 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
31265 - Fix misleading log messages: an entry guard that is "unlisted",
31266 as well as not known to be "down" (because we've never heard
31267 of it), is not therefore "up".
31268 - Remove code to special-case "-cvs" ending, since it has not
31269 actually mattered since 0.0.9.
31270 - Make our socks5 handling more robust to broken socks clients:
31271 throw out everything waiting on the buffer in between socks
31272 handshake phases, since they can't possibly (so the theory
31273 goes) have predicted what we plan to respond to them.
31276 Changes in version 0.1.1.23 - 2006-07-30
31278 - Fast Tor servers, especially exit nodes, were triggering asserts
31279 due to a bug in handling the list of pending DNS resolves. Some
31280 bugs still remain here; we're hunting them.
31281 - Entry guards could crash clients by sending unexpected input.
31282 - More fixes on reachability testing: if you find yourself reachable,
31283 then don't ever make any client requests (so you stop predicting
31284 circuits), then hup or have your clock jump, then later your IP
31285 changes, you won't think circuits are working, so you won't try to
31286 test reachability, so you won't publish.
31289 - Avoid a crash if the controller does a resetconf firewallports
31290 and then a setconf fascistfirewall=1.
31291 - Avoid an integer underflow when the dir authority decides whether
31292 a router is stable: we might wrongly label it stable, and compute
31293 a slightly wrong median stability, when a descriptor is published
31295 - Fix a place where we might trigger an assert if we can't build our
31296 own server descriptor yet.
31299 Changes in version 0.1.1.22 - 2006-07-05
31301 - Fix a big bug that was causing servers to not find themselves
31302 reachable if they changed IP addresses. Since only 0.1.1.22+
31303 servers can do reachability testing correctly, now we automatically
31304 make sure to test via one of these.
31305 - Fix to allow clients and mirrors to learn directory info from
31306 descriptor downloads that get cut off partway through.
31307 - Directory authorities had a bug in deciding if a newly published
31308 descriptor was novel enough to make everybody want a copy -- a few
31309 servers seem to be publishing new descriptors many times a minute.
31311 - Fix a rare bug that was causing some servers to complain about
31312 "closing wedged cpuworkers" and skip some circuit create requests.
31313 - Make the Exit flag in directory status documents actually work.
31316 Changes in version 0.1.1.21 - 2006-06-10
31317 o Crash and assert fixes from 0.1.1.20:
31318 - Fix a rare crash on Tor servers that have enabled hibernation.
31319 - Fix a seg fault on startup for Tor networks that use only one
31320 directory authority.
31321 - Fix an assert from a race condition that occurs on Tor servers
31322 while exiting, where various threads are trying to log that they're
31323 exiting, and delete the logs, at the same time.
31324 - Make our unit tests pass again on certain obscure platforms.
31327 - Add support for building SUSE RPM packages.
31328 - Speed up initial bootstrapping for clients: if we are making our
31329 first ever connection to any entry guard, then don't mark it down
31331 - When only one Tor server in the network is labelled as a guard,
31332 and we've already picked him, we would cycle endlessly picking him
31333 again, being unhappy about it, etc. Now we specifically exclude
31334 current guards when picking a new guard.
31335 - Servers send create cells more reliably after the TLS connection
31336 is established: we were sometimes forgetting to send half of them
31337 when we had more than one pending.
31338 - If we get a create cell that asks us to extend somewhere, but the
31339 Tor server there doesn't match the expected digest, we now send
31340 a destroy cell back, rather than silently doing nothing.
31341 - Make options->RedirectExit work again.
31342 - Make cookie authentication for the controller work again.
31343 - Stop being picky about unusual characters in the arguments to
31344 mapaddress. It's none of our business.
31345 - Add a new config option "TestVia" that lets you specify preferred
31346 middle hops to use for test circuits. Perhaps this will let me
31347 debug the reachability problems better.
31349 o Log / documentation fixes:
31350 - If we're a server and some peer has a broken TLS certificate, don't
31351 log about it unless ProtocolWarnings is set, i.e., we want to hear
31352 about protocol violations by others.
31353 - Fix spelling of VirtualAddrNetwork in man page.
31354 - Add a better explanation at the top of the autogenerated torrc file
31355 about what happened to our old torrc.
31358 Changes in version 0.1.1.20 - 2006-05-23
31360 - Downgrade a log severity where servers complain that they're
31362 - Avoid a compile warning on FreeBSD.
31363 - Remove string size limit on NEWDESC messages; solve bug 291.
31364 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
31365 more thoroughly when we're running on windows.
31368 Changes in version 0.1.1.19-rc - 2006-05-03
31370 - Regenerate our local descriptor if it's dirty and we try to use
31371 it locally (e.g. if it changes during reachability detection).
31372 - If we setconf our ORPort to 0, we continued to listen on the
31373 old ORPort and receive connections.
31374 - Avoid a second warning about machine/limits.h on Debian
31376 - Be willing to add our own routerinfo into the routerlist.
31377 Now authorities will include themselves in their directories
31378 and network-statuses.
31379 - Stop trying to upload rendezvous descriptors to every
31380 directory authority: only try the v1 authorities.
31381 - Servers no longer complain when they think they're not
31382 registered with the directory authorities. There were too many
31384 - Backport dist-rpm changes so rpms can be built without errors.
31387 - Implement an option, VirtualAddrMask, to set which addresses
31388 get handed out in response to mapaddress requests. This works
31389 around a bug in tsocks where 127.0.0.0/8 is never socksified.
31392 Changes in version 0.1.1.18-rc - 2006-04-10
31394 - Work harder to download live network-statuses from all the
31395 directory authorities we know about. Improve the threshold
31396 decision logic so we're more robust to edge cases.
31397 - When fetching rendezvous descriptors, we were willing to ask
31398 v2 authorities too, which would always return 404.
31401 - Stop listing down or invalid nodes in the v1 directory. This will
31402 reduce its bulk by about 1/3, and reduce load on directory
31404 - When deciding whether a router is Fast or Guard-worthy, consider
31405 his advertised BandwidthRate and not just the BandwidthCapacity.
31406 - No longer ship INSTALL and README files -- they are useless now.
31407 - Force rpmbuild to behave and honor target_cpu.
31408 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
31409 - Start to include translated versions of the tor-doc-*.html
31410 files, along with the screenshots. Still needs more work.
31411 - Start sending back 512 and 451 errors if mapaddress fails,
31412 rather than not sending anything back at all.
31413 - When we fail to bind or listen on an incoming or outgoing
31414 socket, we should close it before failing. otherwise we just
31415 leak it. (thanks to weasel for finding.)
31416 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
31417 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
31418 - Make NoPublish (even though deprecated) work again.
31419 - Fix a minor security flaw where a versioning auth dirserver
31420 could list a recommended version many times in a row to make
31421 clients more convinced that it's recommended.
31422 - Fix crash bug if there are two unregistered servers running
31423 with the same nickname, one of them is down, and you ask for
31424 them by nickname in your EntryNodes or ExitNodes. Also, try
31425 to pick the one that's running rather than an arbitrary one.
31426 - Fix an infinite loop we could hit if we go offline for too long.
31427 - Complain when we hit WSAENOBUFS on recv() or write() too.
31428 Perhaps this will help us hunt the bug.
31429 - If you're not a versioning dirserver, don't put the string
31430 "client-versions \nserver-versions \n" in your network-status.
31431 - Lower the minimum required number of file descriptors to 1000,
31432 so we can have some overhead for Valgrind on Linux, where the
31433 default ulimit -n is 1024.
31436 - Add tor.dizum.com as the fifth authoritative directory server.
31437 - Add a new config option FetchUselessDescriptors, off by default,
31438 for when you plan to run "exitlist" on your client and you want
31439 to know about even the non-running descriptors.
31442 Changes in version 0.1.1.17-rc - 2006-03-28
31444 - Clients and servers since 0.1.1.10-alpha have been expiring
31445 connections whenever they are idle for 5 minutes and they *do*
31446 have circuits on them. Oops. With this new version, clients will
31447 discard their previous entry guard choices and avoid choosing
31448 entry guards running these flawed versions.
31449 - Fix memory leak when uncompressing concatenated zlib streams. This
31450 was causing substantial leaks over time on Tor servers.
31451 - The v1 directory was including servers as much as 48 hours old,
31452 because that's how the new routerlist->routers works. Now only
31453 include them if they're 20 hours old or less.
31456 - Resume building on irix64, netbsd 2.0, etc.
31457 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
31459 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
31460 and it is confusing some users.
31461 - Mirrors stop caching the v1 directory so often.
31462 - Make the max number of old descriptors that a cache will hold
31463 rise with the number of directory authorities, so we can scale.
31464 - Change our win32 uname() hack to be more forgiving about what
31465 win32 versions it thinks it's found.
31468 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
31470 - When the controller's *setconf commands fail, collect an error
31471 message in a string and hand it back to the controller.
31472 - Make the v2 dir's "Fast" flag based on relative capacity, just
31473 like "Stable" is based on median uptime. Name everything in the
31474 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
31475 - Log server fingerprint on startup, so new server operators don't
31476 have to go hunting around their filesystem for it.
31477 - Return a robots.txt on our dirport to discourage google indexing.
31478 - Let the controller ask for GETINFO dir/status/foo so it can ask
31479 directly rather than connecting to the dir port. Only works when
31480 dirport is set for now.
31482 o New config options rather than constants in the code:
31483 - SocksTimeout: How long do we let a socks connection wait
31484 unattached before we fail it?
31485 - CircuitBuildTimeout: Cull non-open circuits that were born
31486 at least this many seconds ago.
31487 - CircuitIdleTimeout: Cull open clean circuits that were born
31488 at least this many seconds ago.
31491 Changes in version 0.1.1.16-rc - 2006-03-18
31492 o Bugfixes on 0.1.1.15-rc:
31493 - Fix assert when the controller asks to attachstream a connect-wait
31494 or resolve-wait stream.
31495 - Now do address rewriting when the controller asks us to attach
31496 to a particular circuit too. This will let Blossom specify
31497 "moria2.exit" without having to learn what moria2's IP address is.
31498 - Make the "tor --verify-config" command-line work again, so people
31499 can automatically check if their torrc will parse.
31500 - Authoritative dirservers no longer require an open connection from
31501 a server to consider him "reachable". We need this change because
31502 when we add new auth dirservers, old servers won't know not to
31504 - Let Tor build on Sun CC again.
31505 - Fix an off-by-one buffer size in dirserv.c that magically never
31506 hit our three authorities but broke sjmurdoch's own tor network.
31507 - If we as a directory mirror don't know of any v1 directory
31508 authorities, then don't try to cache any v1 directories.
31509 - Stop warning about unknown servers in our family when they are
31510 given as hex digests.
31511 - Stop complaining as quickly to the server operator that he
31512 hasn't registered his nickname/key binding.
31513 - Various cleanups so we can add new V2 Auth Dirservers.
31514 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
31515 reflect the updated flags in our v2 dir protocol.
31516 - Resume allowing non-printable characters for exit streams (both
31517 for connecting and for resolving). Now we tolerate applications
31518 that don't follow the RFCs. But continue to block malformed names
31521 o Bugfixes on 0.1.0.x:
31522 - Fix assert bug in close_logs(): when we close and delete logs,
31523 remove them all from the global "logfiles" list.
31524 - Fix minor integer overflow in calculating when we expect to use up
31525 our bandwidth allocation before hibernating.
31526 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
31527 there are multiple SSLs installed with different versions.
31528 - When we try to be a server and Address is not explicitly set and
31529 our hostname resolves to a private IP address, try to use an
31530 interface address if it has a public address. Now Windows machines
31531 that think of themselves as localhost can work by default.
31534 - Let the controller ask for GETINFO dir/server/foo so it can ask
31535 directly rather than connecting to the dir port.
31536 - Let the controller tell us about certain router descriptors
31537 that it doesn't want Tor to use in circuits. Implement
31538 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
31539 - New config option SafeSocks to reject all application connections
31540 using unsafe socks protocols. Defaults to off.
31543 Changes in version 0.1.1.15-rc - 2006-03-11
31544 o Bugfixes and cleanups:
31545 - When we're printing strings from the network, don't try to print
31546 non-printable characters. This protects us against shell escape
31547 sequence exploits, and also against attacks to fool humans into
31548 misreading their logs.
31549 - Fix a bug where Tor would fail to establish any connections if you
31550 left it off for 24 hours and then started it: we were happy with
31551 the obsolete network statuses, but they all referred to router
31552 descriptors that were too old to fetch, so we ended up with no
31553 valid router descriptors.
31554 - Fix a seg fault in the controller's "getinfo orconn-status"
31555 command while listing status on incoming handshaking connections.
31556 Introduce a status name "NEW" for these connections.
31557 - If we get a linelist or linelist_s config option from the torrc
31558 (e.g. ExitPolicy) and it has no value, warn and skip rather than
31559 silently resetting it to its default.
31560 - Don't abandon entry guards until they've been down or gone for
31562 - Cleaner and quieter log messages.
31565 - New controller signal NEWNYM that makes new application requests
31566 use clean circuits.
31567 - Add a new circuit purpose 'controller' to let the controller ask
31568 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
31569 controller command to let you specify the purpose if you're
31570 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
31571 command to let you change a circuit's purpose after it's been
31573 - Accept "private:*" in routerdesc exit policies; not generated yet
31574 because older Tors do not understand it.
31575 - Add BSD-style contributed startup script "rc.subr" from Peter
31579 Changes in version 0.1.1.14-alpha - 2006-02-20
31580 o Bugfixes on 0.1.1.x:
31581 - Don't die if we ask for a stdout or stderr log (even implicitly)
31582 and we're set to RunAsDaemon -- just warn.
31583 - We still had a few bugs in the OR connection rotation code that
31584 caused directory servers to slowly aggregate connections to other
31585 fast Tor servers. This time for sure!
31586 - Make log entries on Win32 include the name of the function again.
31587 - We were treating a pair of exit policies if they were equal even
31588 if one said accept and the other said reject -- causing us to
31589 not always publish a new descriptor since we thought nothing
31591 - Retry pending server downloads as well as pending networkstatus
31592 downloads when we unexpectedly get a socks request.
31593 - We were ignoring the IS_FAST flag in the directory status,
31594 meaning we were willing to pick trivial-bandwidth nodes for "fast"
31596 - If the controller's SAVECONF command fails (e.g. due to file
31597 permissions), let the controller know that it failed.
31600 - If we're trying to be a Tor server and running Windows 95/98/ME
31601 as a server, explain that we'll likely crash.
31602 - When we're a server, a client asks for an old-style directory,
31603 and our write bucket is empty, don't give it to him. This way
31604 small servers can continue to serve the directory *sometimes*,
31605 without getting overloaded.
31606 - Compress exit policies even more -- look for duplicate lines
31608 - Clients now honor the "guard" flag in the router status when
31609 picking entry guards, rather than looking at is_fast or is_stable.
31610 - Retain unrecognized lines in $DATADIR/state file, so that we can
31611 be forward-compatible.
31612 - Generate 18.0.0.0/8 address policy format in descs when we can;
31613 warn when the mask is not reducible to a bit-prefix.
31614 - Let the user set ControlListenAddress in the torrc. This can be
31615 dangerous, but there are some cases (like a secured LAN) where it
31617 - Split ReachableAddresses into ReachableDirAddresses and
31618 ReachableORAddresses, so we can restrict Dir conns to port 80
31619 and OR conns to port 443.
31620 - Now we can target arch and OS in rpm builds (contributed by
31621 Phobos). Also make the resulting dist-rpm filename match the
31623 - New config options to help controllers: FetchServerDescriptors
31624 and FetchHidServDescriptors for whether to fetch server
31625 info and hidserv info or let the controller do it, and
31626 PublishServerDescriptor and PublishHidServDescriptors.
31627 - Also let the controller set the __AllDirActionsPrivate config
31628 option if you want all directory fetches/publishes to happen via
31629 Tor (it assumes your controller bootstraps your circuits).
31632 Changes in version 0.1.0.17 - 2006-02-17
31633 o Crash bugfixes on 0.1.0.x:
31634 - When servers with a non-zero DirPort came out of hibernation,
31635 sometimes they would trigger an assert.
31637 o Other important bugfixes:
31638 - On platforms that don't have getrlimit (like Windows), we were
31639 artificially constraining ourselves to a max of 1024
31640 connections. Now just assume that we can handle as many as 15000
31641 connections. Hopefully this won't cause other problems.
31643 o Backported features:
31644 - When we're a server, a client asks for an old-style directory,
31645 and our write bucket is empty, don't give it to him. This way
31646 small servers can continue to serve the directory *sometimes*,
31647 without getting overloaded.
31648 - Whenever you get a 503 in response to a directory fetch, try
31649 once more. This will become important once servers start sending
31650 503's whenever they feel busy.
31651 - Fetch a new directory every 120 minutes, not every 40 minutes.
31652 Now that we have hundreds of thousands of users running the old
31653 directory algorithm, it's starting to hurt a lot.
31654 - Bump up the period for forcing a hidden service descriptor upload
31655 from 20 minutes to 1 hour.
31658 Changes in version 0.1.1.13-alpha - 2006-02-09
31659 o Crashes in 0.1.1.x:
31660 - When you tried to setconf ORPort via the controller, Tor would
31661 crash. So people using TorCP to become a server were sad.
31662 - Solve (I hope) the stack-smashing bug that we were seeing on fast
31663 servers. The problem appears to be something do with OpenSSL's
31664 random number generation, or how we call it, or something. Let me
31665 know if the crashes continue.
31666 - Turn crypto hardware acceleration off by default, until we find
31667 somebody smart who can test it for us. (It appears to produce
31668 seg faults in at least some cases.)
31669 - Fix a rare assert error when we've tried all intro points for
31670 a hidden service and we try fetching the service descriptor again:
31671 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
31674 - Fix a major load balance bug: we were round-robining in 16 KB
31675 chunks, and servers with bandwidthrate of 20 KB, while downloading
31676 a 600 KB directory, would starve their other connections. Now we
31677 try to be a bit more fair.
31678 - Dir authorities and mirrors were never expiring the newest
31679 descriptor for each server, causing memory and directory bloat.
31680 - Fix memory-bloating and connection-bloating bug on servers: We
31681 were never closing any connection that had ever had a circuit on
31682 it, because we were checking conn->n_circuits == 0, yet we had a
31683 bug that let it go negative.
31684 - Make Tor work using squid as your http proxy again -- squid
31685 returns an error if you ask for a URL that's too long, and it uses
31686 a really generic error message. Plus, many people are behind a
31687 transparent squid so they don't even realize it.
31688 - On platforms that don't have getrlimit (like Windows), we were
31689 artificially constraining ourselves to a max of 1024
31690 connections. Now just assume that we can handle as many as 15000
31691 connections. Hopefully this won't cause other problems.
31692 - Add a new config option ExitPolicyRejectPrivate which defaults to
31693 1. This means all exit policies will begin with rejecting private
31694 addresses, unless the server operator explicitly turns it off.
31697 - Clients no longer download descriptors for non-running
31699 - Before we add new directory authorities, we should make it
31700 clear that only v1 authorities should receive/publish hidden
31701 service descriptors.
31704 - As soon as we've fetched some more directory info, immediately
31705 try to download more server descriptors. This way we don't have
31706 a 10 second pause during initial bootstrapping.
31707 - Remove even more loud log messages that the server operator can't
31709 - When we're running an obsolete or un-recommended version, make
31710 the log message more clear about what the problem is and what
31711 versions *are* still recommended.
31712 - Provide a more useful warn message when our onion queue gets full:
31713 the CPU is too slow or the exit policy is too liberal.
31714 - Don't warn when we receive a 503 from a dirserver/cache -- this
31715 will pave the way for them being able to refuse if they're busy.
31716 - When we fail to bind a listener, try to provide a more useful
31717 log message: e.g., "Is Tor already running?"
31718 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
31719 Goldberg can prove things about our handshake protocol more
31721 - MaxConn has been obsolete for a while now. Document the ConnLimit
31722 config option, which is a *minimum* number of file descriptors
31723 that must be available else Tor refuses to start.
31724 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
31725 if you log to syslog and want something other than LOG_DAEMON.
31726 - Make dirservers generate a separate "guard" flag to mean,
31727 "would make a good entry guard". Make clients parse it and vote
31728 on it. Not used by clients yet.
31729 - Implement --with-libevent-dir option to ./configure. Also, improve
31730 search techniques to find libevent, and use those for openssl too.
31731 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
31732 - Only start testing reachability once we've established a
31733 circuit. This will make startup on dirservers less noisy.
31734 - Don't try to upload hidden service descriptors until we have
31735 established a circuit.
31736 - Fix the controller's "attachstream 0" command to treat conn like
31737 it just connected, doing address remapping, handling .exit and
31738 .onion idioms, and so on. Now we're more uniform in making sure
31739 that the controller hears about new and closing connections.
31742 Changes in version 0.1.1.12-alpha - 2006-01-11
31743 o Bugfixes on 0.1.1.x:
31744 - The fix to close duplicate server connections was closing all
31745 Tor client connections if they didn't establish a circuit
31746 quickly enough. Oops.
31747 - Fix minor memory issue (double-free) that happened on exit.
31749 o Bugfixes on 0.1.0.x:
31750 - Tor didn't warn when it failed to open a log file.
31753 Changes in version 0.1.1.11-alpha - 2006-01-10
31754 o Crashes in 0.1.1.x:
31755 - Include all the assert/crash fixes from 0.1.0.16.
31756 - If you start Tor and then quit very quickly, there were some
31757 races that tried to free things that weren't allocated yet.
31758 - Fix a rare memory stomp if you're running hidden services.
31759 - Fix segfault when specifying DirServer in config without nickname.
31760 - Fix a seg fault when you finish connecting to a server but at
31761 that moment you dump his server descriptor.
31762 - Extendcircuit and Attachstream controller commands would
31763 assert/crash if you don't give them enough arguments.
31764 - Fix an assert error when we're out of space in the connection_list
31765 and we try to post a hidden service descriptor (reported by weasel).
31766 - If you specify a relative torrc path and you set RunAsDaemon in
31767 your torrc, then it chdir()'s to the new directory. If you HUP,
31768 it tries to load the new torrc location, fails, and exits.
31769 The fix: no longer allow a relative path to torrc using -f.
31772 - Implement "entry guards": automatically choose a handful of entry
31773 nodes and stick with them for all circuits. Only pick new guards
31774 when the ones you have are unsuitable, and if the old guards
31775 become suitable again, switch back. This will increase security
31776 dramatically against certain end-point attacks. The EntryNodes
31777 config option now provides some hints about which entry guards you
31778 want to use most; and StrictEntryNodes means to only use those.
31779 - New directory logic: download by descriptor digest, not by
31780 fingerprint. Caches try to download all listed digests from
31781 authorities; clients try to download "best" digests from caches.
31782 This avoids partitioning and isolating attacks better.
31783 - Make the "stable" router flag in network-status be the median of
31784 the uptimes of running valid servers, and make clients pay
31785 attention to the network-status flags. Thus the cutoff adapts
31786 to the stability of the network as a whole, making IRC, IM, etc
31787 connections more reliable.
31790 - Tor servers with dynamic IP addresses were needing to wait 18
31791 hours before they could start doing reachability testing using
31792 the new IP address and ports. This is because they were using
31793 the internal descriptor to learn what to test, yet they were only
31794 rebuilding the descriptor once they decided they were reachable.
31795 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
31796 to download certain server descriptors, throw them away, and then
31797 fetch them again after 30 minutes. Now mirrors throw away these
31798 server descriptors so clients can't get them.
31799 - We were leaving duplicate connections to other ORs open for a week,
31800 rather than closing them once we detect a duplicate. This only
31801 really affected authdirservers, but it affected them a lot.
31802 - Spread the authdirservers' reachability testing over the entire
31803 testing interval, so we don't try to do 500 TLS's at once every
31807 - If the network is down, and we try to connect to a conn because
31808 we have a circuit in mind, and we timeout (30 seconds) because the
31809 network never answers, we were expiring the circuit, but we weren't
31810 obsoleting the connection or telling the entry_guards functions.
31811 - Some Tor servers process billions of cells per day. These statistics
31812 need to be uint64_t's.
31813 - Check for integer overflows in more places, when adding elements
31814 to smartlists. This could possibly prevent a buffer overflow
31815 on malicious huge inputs. I don't see any, but I haven't looked
31817 - ReachableAddresses kept growing new "reject *:*" lines on every
31819 - When you "setconf log" via the controller, it should remove all
31820 logs. We were automatically adding back in a "log notice stdout".
31821 - Newly bootstrapped Tor networks couldn't establish hidden service
31822 circuits until they had nodes with high uptime. Be more tolerant.
31823 - We were marking servers down when they could not answer every piece
31824 of the directory request we sent them. This was far too harsh.
31825 - Fix the torify (tsocks) config file to not use Tor for localhost
31827 - Directory authorities now go to the proper authority when asking for
31828 a networkstatus, even when they want a compressed one.
31829 - Fix a harmless bug that was causing Tor servers to log
31830 "Got an end because of misc error, but we're not an AP. Closing."
31831 - Authorities were treating their own descriptor changes as cosmetic,
31832 meaning the descriptor available in the network-status and the
31833 descriptor that clients downloaded were different.
31834 - The OS X installer was adding a symlink for tor_resolve but
31835 the binary was called tor-resolve (reported by Thomas Hardly).
31836 - Workaround a problem with some http proxies where they refuse GET
31837 requests that specify "Content-Length: 0" (reported by Adrian).
31838 - Fix wrong log message when you add a "HiddenServiceNodes" config
31839 line without any HiddenServiceDir line (reported by Chris Thomas).
31842 - Write the TorVersion into the state file so we have a prayer of
31843 keeping forward and backward compatibility.
31844 - Revive the FascistFirewall config option rather than eliminating it:
31845 now it's a synonym for ReachableAddresses *:80,*:443.
31846 - Clients choose directory servers from the network status lists,
31847 not from their internal list of router descriptors. Now they can
31848 go to caches directly rather than needing to go to authorities
31850 - Directory authorities ignore router descriptors that have only
31851 cosmetic differences: do this for 0.1.0.x servers now too.
31852 - Add a new flag to network-status indicating whether the server
31853 can answer v2 directory requests too.
31854 - Authdirs now stop whining so loudly about bad descriptors that
31855 they fetch from other dirservers. So when there's a log complaint,
31856 it's for sure from a freshly uploaded descriptor.
31857 - Reduce memory requirements in our structs by changing the order
31859 - There used to be two ways to specify your listening ports in a
31860 server descriptor: on the "router" line and with a separate "ports"
31861 line. Remove support for the "ports" line.
31862 - New config option "AuthDirRejectUnlisted" for auth dirservers as
31863 a panic button: if we get flooded with unusable servers we can
31864 revert to only listing servers in the approved-routers file.
31865 - Auth dir servers can now mark a fingerprint as "!reject" or
31866 "!invalid" in the approved-routers file (as its nickname), to
31867 refuse descriptors outright or include them but marked as invalid.
31868 - Servers store bandwidth history across restarts/crashes.
31869 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
31870 get a better idea of why their circuits failed. Not used yet.
31871 - Directory mirrors now cache up to 16 unrecognized network-status
31872 docs. Now we can add new authdirservers and they'll be cached too.
31873 - When picking a random directory, prefer non-authorities if any
31875 - New controller option "getinfo desc/all-recent" to fetch the
31876 latest server descriptor for every router that Tor knows about.
31879 Changes in version 0.1.0.16 - 2006-01-02
31880 o Crash bugfixes on 0.1.0.x:
31881 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
31882 corrupting the heap, losing FDs, or crashing when we need to resize
31883 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
31884 - It turns out sparc64 platforms crash on unaligned memory access
31885 too -- so detect and avoid this.
31886 - Handle truncated compressed data correctly (by detecting it and
31888 - Fix possible-but-unlikely free(NULL) in control.c.
31889 - When we were closing connections, there was a rare case that
31890 stomped on memory, triggering seg faults and asserts.
31891 - Avoid potential infinite recursion when building a descriptor. (We
31892 don't know that it ever happened, but better to fix it anyway.)
31893 - We were neglecting to unlink marked circuits from soon-to-close OR
31894 connections, which caused some rare scribbling on freed memory.
31895 - Fix a memory stomping race bug when closing the joining point of two
31896 rendezvous circuits.
31897 - Fix an assert in time parsing found by Steven Murdoch.
31899 o Other bugfixes on 0.1.0.x:
31900 - When we're doing reachability testing, provide more useful log
31901 messages so the operator knows what to expect.
31902 - Do not check whether DirPort is reachable when we are suppressing
31903 advertising it because of hibernation.
31904 - When building with -static or on Solaris, we sometimes needed -ldl.
31905 - When we're deciding whether a stream has enough circuits around
31906 that can handle it, count the freshly dirty ones and not the ones
31907 that are so dirty they won't be able to handle it.
31908 - When we're expiring old circuits, we had a logic error that caused
31909 us to close new rendezvous circuits rather than old ones.
31910 - Give a more helpful log message when you try to change ORPort via
31911 the controller: you should upgrade Tor if you want that to work.
31912 - We were failing to parse Tor versions that start with "Tor ".
31913 - Tolerate faulty streams better: when a stream fails for reason
31914 exitpolicy, stop assuming that the router is lying about his exit
31915 policy. When a stream fails for reason misc, allow it to retry just
31916 as if it was resolvefailed. When a stream has failed three times,
31917 reset its failure count so we can try again and get all three tries.
31920 Changes in version 0.1.1.10-alpha - 2005-12-11
31921 o Correctness bugfixes on 0.1.0.x:
31922 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
31923 corrupting the heap, losing FDs, or crashing when we need to resize
31924 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
31925 - Stop doing the complex voodoo overkill checking for insecure
31926 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
31927 - When we were closing connections, there was a rare case that
31928 stomped on memory, triggering seg faults and asserts.
31929 - We were neglecting to unlink marked circuits from soon-to-close OR
31930 connections, which caused some rare scribbling on freed memory.
31931 - When we're deciding whether a stream has enough circuits around
31932 that can handle it, count the freshly dirty ones and not the ones
31933 that are so dirty they won't be able to handle it.
31934 - Recover better from TCP connections to Tor servers that are
31935 broken but don't tell you (it happens!); and rotate TLS
31936 connections once a week.
31937 - When we're expiring old circuits, we had a logic error that caused
31938 us to close new rendezvous circuits rather than old ones.
31939 - Fix a scary-looking but apparently harmless bug where circuits
31940 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
31941 servers, and never switch to state CIRCUIT_STATE_OPEN.
31942 - When building with -static or on Solaris, we sometimes needed to
31944 - Give a useful message when people run Tor as the wrong user,
31945 rather than telling them to start chowning random directories.
31946 - We were failing to inform the controller about new .onion streams.
31948 o Security bugfixes on 0.1.0.x:
31949 - Refuse server descriptors if the fingerprint line doesn't match
31950 the included identity key. Tor doesn't care, but other apps (and
31951 humans) might actually be trusting the fingerprint line.
31952 - We used to kill the circuit when we receive a relay command we
31953 don't recognize. Now we just drop it.
31954 - Start obeying our firewall options more rigorously:
31955 . If we can't get to a dirserver directly, try going via Tor.
31956 . Don't ever try to connect (as a client) to a place our
31957 firewall options forbid.
31958 . If we specify a proxy and also firewall options, obey the
31959 firewall options even when we're using the proxy: some proxies
31960 can only proxy to certain destinations.
31961 - Fix a bug found by Lasse Overlier: when we were making internal
31962 circuits (intended to be cannibalized later for rendezvous and
31963 introduction circuits), we were picking them so that they had
31964 useful exit nodes. There was no need for this, and it actually
31965 aids some statistical attacks.
31966 - Start treating internal circuits and exit circuits separately.
31967 It's important to keep them separate because internal circuits
31968 have their last hops picked like middle hops, rather than like
31969 exit hops. So exiting on them will break the user's expectations.
31971 o Bugfixes on 0.1.1.x:
31972 - Take out the mis-feature where we tried to detect IP address
31973 flapping for people with DynDNS, and chose not to upload a new
31974 server descriptor sometimes.
31975 - Try to be compatible with OpenSSL 0.9.6 again.
31976 - Log fix: when the controller is logging about .onion addresses,
31977 sometimes it didn't include the ".onion" part of the address.
31978 - Don't try to modify options->DirServers internally -- if the
31979 user didn't specify any, just add the default ones directly to
31980 the trusted dirserver list. This fixes a bug where people running
31981 controllers would use SETCONF on some totally unrelated config
31982 option, and Tor would start yelling at them about changing their
31984 - Let the controller's redirectstream command specify a port, in
31985 case the controller wants to change that too.
31986 - When we requested a pile of server descriptors, we sometimes
31987 accidentally launched a duplicate request for the first one.
31988 - Bugfix for trackhostexits: write down the fingerprint of the
31989 chosen exit, not its nickname, because the chosen exit might not
31991 - When parsing foo.exit, if foo is unknown, and we are leaving
31992 circuits unattached, set the chosen_exit field and leave the
31993 address empty. This matters because controllers got confused
31995 - Directory authorities no longer try to download server
31996 descriptors that they know they will reject.
31998 o Features and updates:
31999 - Replace balanced trees with hash tables: this should make stuff
32000 significantly faster.
32001 - Resume using the AES counter-mode implementation that we ship,
32002 rather than OpenSSL's. Ours is significantly faster.
32003 - Many other CPU and memory improvements.
32004 - Add a new config option FastFirstHopPK (on by default) so clients
32005 do a trivial crypto handshake for their first hop, since TLS has
32006 already taken care of confidentiality and authentication.
32007 - Add a new config option TestSocks so people can see if their
32008 applications are using socks4, socks4a, socks5-with-ip, or
32009 socks5-with-hostname. This way they don't have to keep mucking
32010 with tcpdump and wondering if something got cached somewhere.
32011 - Warn when listening on a public address for socks. I suspect a
32012 lot of people are setting themselves up as open socks proxies,
32013 and they have no idea that jerks on the Internet are using them,
32014 since they simply proxy the traffic into the Tor network.
32015 - Add "private:*" as an alias in configuration for policies. Now
32016 you can simplify your exit policy rather than needing to list
32017 every single internal or nonroutable network space.
32018 - Add a new controller event type that allows controllers to get
32019 all server descriptors that were uploaded to a router in its role
32020 as authoritative dirserver.
32021 - Start shipping socks-extensions.txt, tor-doc-unix.html,
32022 tor-doc-server.html, and stylesheet.css in the tarball.
32023 - Stop shipping tor-doc.html in the tarball.
32026 Changes in version 0.1.1.9-alpha - 2005-11-15
32027 o Usability improvements:
32028 - Start calling it FooListenAddress rather than FooBindAddress,
32029 since few of our users know what it means to bind an address
32031 - Reduce clutter in server logs. We're going to try to make
32032 them actually usable now. New config option ProtocolWarnings that
32033 lets you hear about how _other Tors_ are breaking the protocol. Off
32035 - Divide log messages into logging domains. Once we put some sort
32036 of interface on this, it will let people looking at more verbose
32037 log levels specify the topics they want to hear more about.
32038 - Make directory servers return better http 404 error messages
32039 instead of a generic "Servers unavailable".
32040 - Check for even more Windows version flags when writing the platform
32041 string in server descriptors, and note any we don't recognize.
32042 - Clean up more of the OpenSSL memory when exiting, so we can detect
32043 memory leaks better.
32044 - Make directory authorities be non-versioning, non-naming by
32045 default. Now we can add new directory servers without requiring
32046 their operators to pay close attention.
32047 - When logging via syslog, include the pid whenever we provide
32048 a log entry. Suggested by Todd Fries.
32050 o Performance improvements:
32051 - Directory servers now silently throw away new descriptors that
32052 haven't changed much if the timestamps are similar. We do this to
32053 tolerate older Tor servers that upload a new descriptor every 15
32054 minutes. (It seemed like a good idea at the time.)
32055 - Inline bottleneck smartlist functions; use fast versions by default.
32056 - Add a "Map from digest to void*" abstraction digestmap_t so we
32057 can do less hex encoding/decoding. Use it in router_get_by_digest()
32058 to resolve a performance bottleneck.
32059 - Allow tor_gzip_uncompress to extract as much as possible from
32060 truncated compressed data. Try to extract as many
32061 descriptors as possible from truncated http responses (when
32062 DIR_PURPOSE_FETCH_ROUTERDESC).
32063 - Make circ->onionskin a pointer, not a static array. moria2 was using
32064 125000 circuit_t's after it had been up for a few weeks, which
32065 translates to 20+ megs of wasted space.
32066 - The private half of our EDH handshake keys are now chosen out
32067 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
32069 o Security improvements:
32070 - Start making directory caches retain old routerinfos, so soon
32071 clients can start asking by digest of descriptor rather than by
32072 fingerprint of server.
32073 - Add half our entropy from RAND_poll in OpenSSL. This knows how
32074 to use egd (if present), openbsd weirdness (if present), vms/os2
32075 weirdness (if we ever port there), and more in the future.
32077 o Bugfixes on 0.1.0.x:
32078 - Do round-robin writes of at most 16 kB per write. This might be
32079 more fair on loaded Tor servers, and it might resolve our Windows
32080 crash bug. It might also slow things down.
32081 - Our TLS handshakes were generating a single public/private
32082 keypair for the TLS context, rather than making a new one for
32083 each new connections. Oops. (But we were still rotating them
32084 periodically, so it's not so bad.)
32085 - When we were cannibalizing a circuit with a particular exit
32086 node in mind, we weren't checking to see if that exit node was
32087 already present earlier in the circuit. Oops.
32088 - When a Tor server's IP changes (e.g. from a dyndns address),
32089 upload a new descriptor so clients will learn too.
32090 - Really busy servers were keeping enough circuits open on stable
32091 connections that they were wrapping around the circuit_id
32092 space. (It's only two bytes.) This exposed a bug where we would
32093 feel free to reuse a circuit_id even if it still exists but has
32094 been marked for close. Try to fix this bug. Some bug remains.
32095 - If we would close a stream early (e.g. it asks for a .exit that
32096 we know would refuse it) but the LeaveStreamsUnattached config
32097 option is set by the controller, then don't close it.
32099 o Bugfixes on 0.1.1.8-alpha:
32100 - Fix a big pile of memory leaks, some of them serious.
32101 - Do not try to download a routerdesc if we would immediately reject
32103 - Resume inserting a newline between all router descriptors when
32104 generating (old style) signed directories, since our spec says
32106 - When providing content-type application/octet-stream for
32107 server descriptors using .z, we were leaving out the
32108 content-encoding header. Oops. (Everything tolerated this just
32109 fine, but that doesn't mean we need to be part of the problem.)
32110 - Fix a potential seg fault in getconf and getinfo using version 1
32111 of the controller protocol.
32112 - Avoid crash: do not check whether DirPort is reachable when we
32113 are suppressing it because of hibernation.
32114 - Make --hash-password not crash on exit.
32117 Changes in version 0.1.1.8-alpha - 2005-10-07
32118 o New features (major):
32119 - Clients don't download or use the directory anymore. Now they
32120 download and use network-statuses from the trusted dirservers,
32121 and fetch individual server descriptors as needed from mirrors.
32122 See dir-spec.txt for all the gory details.
32123 - Be more conservative about whether to advertise our DirPort.
32124 The main change is to not advertise if we're running at capacity
32125 and either a) we could hibernate or b) our capacity is low and
32126 we're using a default DirPort.
32127 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
32129 o New features (minor):
32130 - Try to be smart about when to retry network-status and
32131 server-descriptor fetches. Still needs some tuning.
32132 - Stop parsing, storing, or using running-routers output (but
32133 mirrors still cache and serve it).
32134 - Consider a threshold of versioning dirservers (dirservers who have
32135 an opinion about which Tor versions are still recommended) before
32136 deciding whether to warn the user that he's obsolete.
32137 - Dirservers can now reject/invalidate by key and IP, with the
32138 config options "AuthDirInvalid" and "AuthDirReject". This is
32139 useful since currently we automatically list servers as running
32140 and usable even if we know they're jerks.
32141 - Provide dire warnings to any users who set DirServer; move it out
32142 of torrc.sample and into torrc.complete.
32143 - Add MyFamily to torrc.sample in the server section.
32144 - Add nicknames to the DirServer line, so we can refer to them
32145 without requiring all our users to memorize their IP addresses.
32146 - When we get an EOF or a timeout on a directory connection, note
32147 how many bytes of serverdesc we are dropping. This will help
32148 us determine whether it is smart to parse incomplete serverdesc
32150 - Add a new function to "change pseudonyms" -- that is, to stop
32151 using any currently-dirty circuits for new streams, so we don't
32152 link new actions to old actions. Currently it's only called on
32153 HUP (or SIGNAL RELOAD).
32154 - On sighup, if UseHelperNodes changed to 1, use new circuits.
32155 - Start using RAND_bytes rather than RAND_pseudo_bytes from
32156 OpenSSL. Also, reseed our entropy every hour, not just at
32157 startup. And entropy in 512-bit chunks, not 160-bit chunks.
32159 o Fixes on 0.1.1.7-alpha:
32160 - Nobody ever implemented EVENT_ADDRMAP for control protocol
32161 version 0, so don't let version 0 controllers ask for it.
32162 - If you requested something with too many newlines via the
32163 v1 controller protocol, you could crash tor.
32164 - Fix a number of memory leaks, including some pretty serious ones.
32165 - Re-enable DirPort testing again, so Tor servers will be willing
32166 to advertise their DirPort if it's reachable.
32167 - On TLS handshake, only check the other router's nickname against
32168 its expected nickname if is_named is set.
32170 o Fixes forward-ported from 0.1.0.15:
32171 - Don't crash when we don't have any spare file descriptors and we
32172 try to spawn a dns or cpu worker.
32173 - Make the numbers in read-history and write-history into uint64s,
32174 so they don't overflow and publish negatives in the descriptor.
32176 o Fixes on 0.1.0.x:
32177 - For the OS X package's modified privoxy config file, comment
32178 out the "logfile" line so we don't log everything passed
32180 - We were whining about using socks4 or socks5-with-local-lookup
32181 even when it's an IP in the "virtual" range we designed exactly
32183 - We were leaking some memory every time the client changes IPs.
32184 - Never call free() on tor_malloc()d memory. This will help us
32185 use dmalloc to detect memory leaks.
32186 - Check for named servers when looking them up by nickname;
32187 warn when we'recalling a non-named server by its nickname;
32188 don't warn twice about the same name.
32189 - Try to list MyFamily elements by key, not by nickname, and warn
32190 if we've not heard of the server.
32191 - Make windows platform detection (uname equivalent) smarter.
32192 - It turns out sparc64 doesn't like unaligned access either.
32195 Changes in version 0.1.0.15 - 2005-09-23
32196 o Bugfixes on 0.1.0.x:
32197 - Reject ports 465 and 587 (spam targets) in default exit policy.
32198 - Don't crash when we don't have any spare file descriptors and we
32199 try to spawn a dns or cpu worker.
32200 - Get rid of IgnoreVersion undocumented config option, and make us
32201 only warn, never exit, when we're running an obsolete version.
32202 - Don't try to print a null string when your server finds itself to
32203 be unreachable and the Address config option is empty.
32204 - Make the numbers in read-history and write-history into uint64s,
32205 so they don't overflow and publish negatives in the descriptor.
32206 - Fix a minor memory leak in smartlist_string_remove().
32207 - We were only allowing ourselves to upload a server descriptor at
32208 most every 20 minutes, even if it changed earlier than that.
32209 - Clean up log entries that pointed to old URLs.
32212 Changes in version 0.1.1.7-alpha - 2005-09-14
32213 o Fixes on 0.1.1.6-alpha:
32214 - Exit servers were crashing when people asked them to make a
32215 connection to an address not in their exit policy.
32216 - Looking up a non-existent stream for a v1 control connection would
32218 - Fix a seg fault if we ask a dirserver for a descriptor by
32219 fingerprint but he doesn't know about him.
32220 - SETCONF was appending items to linelists, not clearing them.
32221 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
32222 out and refuse the setconf if it would fail.
32223 - Downgrade the dirserver log messages when whining about
32227 - Add Peter Palfrader's check-tor script to tor/contrib/
32228 It lets you easily check whether a given server (referenced by
32229 nickname) is reachable by you.
32230 - Numerous changes to move towards client-side v2 directories. Not
32233 o Fixes on 0.1.0.x:
32234 - If the user gave tor an odd number of command-line arguments,
32235 we were silently ignoring the last one. Now we complain and fail.
32236 [This wins the oldest-bug prize -- this bug has been present since
32237 November 2002, as released in Tor 0.0.0.]
32238 - Do not use unaligned memory access on alpha, mips, or mipsel.
32239 It *works*, but is very slow, so we treat them as if it doesn't.
32240 - Retry directory requests if we fail to get an answer we like
32241 from a given dirserver (we were retrying before, but only if
32242 we fail to connect).
32243 - When writing the RecommendedVersions line, sort them first.
32244 - When the client asked for a rendezvous port that the hidden
32245 service didn't want to provide, we were sending an IP address
32246 back along with the end cell. Fortunately, it was zero. But stop
32248 - Correct "your server is reachable" log entries to indicate that
32249 it was self-testing that told us so.
32252 Changes in version 0.1.1.6-alpha - 2005-09-09
32253 o Fixes on 0.1.1.5-alpha:
32254 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
32255 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
32256 - Fix bug with tor_memmem finding a match at the end of the string.
32257 - Make unit tests run without segfaulting.
32258 - Resolve some solaris x86 compile warnings.
32259 - Handle duplicate lines in approved-routers files without warning.
32260 - Fix bug where as soon as a server refused any requests due to his
32261 exit policy (e.g. when we ask for localhost and he tells us that's
32262 127.0.0.1 and he won't do it), we decided he wasn't obeying his
32263 exit policy using him for any exits.
32264 - Only do openssl hardware accelerator stuff if openssl version is
32267 o New controller features/fixes:
32268 - Add a "RESETCONF" command so you can set config options like
32269 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
32270 a config option in the torrc with no value, then it clears it
32271 entirely (rather than setting it to its default).
32272 - Add a "GETINFO config-file" to tell us where torrc is.
32273 - Avoid sending blank lines when GETINFO replies should be empty.
32274 - Add a QUIT command for the controller (for using it manually).
32275 - Fix a bug in SAVECONF that was adding default dirservers and
32276 other redundant entries to the torrc file.
32278 o Start on the new directory design:
32279 - Generate, publish, cache, serve new network-status format.
32280 - Publish individual descriptors (by fingerprint, by "all", and by
32282 - Publish client and server recommended versions separately.
32283 - Allow tor_gzip_uncompress() to handle multiple concatenated
32284 compressed strings. Serve compressed groups of router
32285 descriptors. The compression logic here could be more
32287 - Distinguish v1 authorities (all currently trusted directories)
32288 from v2 authorities (all trusted directories).
32289 - Change DirServers config line to note which dirs are v1 authorities.
32290 - Add configuration option "V1AuthoritativeDirectory 1" which
32291 moria1, moria2, and tor26 should set.
32292 - Remove option when getting directory cache to see whether they
32293 support running-routers; they all do now. Replace it with one
32294 to see whether caches support v2 stuff.
32297 - Dirservers now do their own external reachability testing of each
32298 Tor server, and only list them as running if they've been found to
32299 be reachable. We also send back warnings to the server's logs if
32300 it uploads a descriptor that we already believe is unreachable.
32301 - Implement exit enclaves: if we know an IP address for the
32302 destination, and there's a running Tor server at that address
32303 which allows exit to the destination, then extend the circuit to
32304 that exit first. This provides end-to-end encryption and end-to-end
32305 authentication. Also, if the user wants a .exit address or enclave,
32306 use 4 hops rather than 3, and cannibalize a general circ for it
32308 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
32309 controller. Also, rotate dns and cpu workers if the controller
32310 changes options that will affect them; and initialize the dns
32311 worker cache tree whether or not we start out as a server.
32312 - Only upload a new server descriptor when options change, 18
32313 hours have passed, uptime is reset, or bandwidth changes a lot.
32314 - Check [X-]Forwarded-For headers in HTTP requests when generating
32315 log messages. This lets people run dirservers (and caches) behind
32316 Apache but still know which IP addresses are causing warnings.
32318 o Config option changes:
32319 - Replace (Fascist)Firewall* config options with a new
32320 ReachableAddresses option that understands address policies.
32321 For example, "ReachableAddresses *:80,*:443"
32322 - Get rid of IgnoreVersion undocumented config option, and make us
32323 only warn, never exit, when we're running an obsolete version.
32324 - Make MonthlyAccountingStart config option truly obsolete now.
32326 o Fixes on 0.1.0.x:
32327 - Reject ports 465 and 587 in the default exit policy, since
32328 people have started using them for spam too.
32329 - It turns out we couldn't bootstrap a network since we added
32330 reachability detection in 0.1.0.1-rc. Good thing the Tor network
32331 has never gone down. Add an AssumeReachable config option to let
32332 servers and dirservers bootstrap. When we're trying to build a
32333 high-uptime or high-bandwidth circuit but there aren't enough
32334 suitable servers, try being less picky rather than simply failing.
32335 - Our logic to decide if the OR we connected to was the right guy
32336 was brittle and maybe open to a mitm for unverified routers.
32337 - We weren't cannibalizing circuits correctly for
32338 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
32339 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
32340 build those from scratch. This should make hidden services faster.
32341 - Predict required circuits better, with an eye toward making hidden
32342 services faster on the service end.
32343 - Retry streams if the exit node sends back a 'misc' failure. This
32344 should result in fewer random failures. Also, after failing
32345 from resolve failed or misc, reset the num failures, so we give
32346 it a fair shake next time we try.
32347 - Clean up the rendezvous warn log msgs, and downgrade some to info.
32348 - Reduce severity on logs about dns worker spawning and culling.
32349 - When we're shutting down and we do something like try to post a
32350 server descriptor or rendezvous descriptor, don't complain that
32351 we seem to be unreachable. Of course we are, we're shutting down.
32352 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
32353 We don't use them yet, but maybe one day our DNS resolver will be
32354 able to discover them.
32355 - Make ContactInfo mandatory for authoritative directory servers.
32356 - Require server descriptors to list IPv4 addresses -- hostnames
32357 are no longer allowed. This also fixes some potential security
32358 problems with people providing hostnames as their address and then
32359 preferentially resolving them to partition users.
32360 - Change log line for unreachability to explicitly suggest /etc/hosts
32361 as the culprit. Also make it clearer what IP address and ports we're
32362 testing for reachability.
32363 - Put quotes around user-supplied strings when logging so users are
32364 more likely to realize if they add bad characters (like quotes)
32366 - Let auth dir servers start without specifying an Address config
32368 - Make unit tests (and other invocations that aren't the real Tor)
32369 run without launching listeners, creating subdirectories, and so on.
32372 Changes in version 0.1.1.5-alpha - 2005-08-08
32373 o Bugfixes included in 0.1.0.14.
32375 o Bugfixes on 0.1.0.x:
32376 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
32377 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
32378 it would silently using ignore the 6668.
32381 Changes in version 0.1.0.14 - 2005-08-08
32382 o Bugfixes on 0.1.0.x:
32383 - Fix the other half of the bug with crypto handshakes
32385 - Fix an assert trigger if you send a 'signal term' via the
32386 controller when it's listening for 'event info' messages.
32389 Changes in version 0.1.1.4-alpha - 2005-08-04
32390 o Bugfixes included in 0.1.0.13.
32393 - Improve tor_gettimeofday() granularity on windows.
32394 - Make clients regenerate their keys when their IP address changes.
32395 - Implement some more GETINFO goodness: expose helper nodes, config
32396 options, getinfo keys.
32399 Changes in version 0.1.0.13 - 2005-08-04
32400 o Bugfixes on 0.1.0.x:
32401 - Fix a critical bug in the security of our crypto handshakes.
32402 - Fix a size_t underflow in smartlist_join_strings2() that made
32403 it do bad things when you hand it an empty smartlist.
32404 - Fix Windows installer to ship Tor license (thanks to Aphex for
32405 pointing out this oversight) and put a link to the doc directory
32407 - Explicitly set no-unaligned-access for sparc: it turns out the
32408 new gcc's let you compile broken code, but that doesn't make it
32412 Changes in version 0.1.1.3-alpha - 2005-07-23
32413 o Bugfixes on 0.1.1.2-alpha:
32414 - Fix a bug in handling the controller's "post descriptor"
32416 - Fix several bugs in handling the controller's "extend circuit"
32418 - Fix a bug in handling the controller's "stream status" event.
32419 - Fix an assert failure if we have a controller listening for
32420 circuit events and we go offline.
32421 - Re-allow hidden service descriptors to publish 0 intro points.
32422 - Fix a crash when generating your hidden service descriptor if
32423 you don't have enough intro points already.
32425 o New features on 0.1.1.2-alpha:
32426 - New controller function "getinfo accounting", to ask how
32427 many bytes we've used in this time period.
32428 - Experimental support for helper nodes: a lot of the risk from
32429 a small static adversary comes because users pick new random
32430 nodes every time they rebuild a circuit. Now users will try to
32431 stick to the same small set of entry nodes if they can. Not
32432 enabled by default yet.
32434 o Bugfixes on 0.1.0.12:
32435 - If you're an auth dir server, always publish your dirport,
32436 even if you haven't yet found yourself to be reachable.
32437 - Fix a size_t underflow in smartlist_join_strings2() that made
32438 it do bad things when you hand it an empty smartlist.
32441 Changes in version 0.1.0.12 - 2005-07-18
32442 o New directory servers:
32443 - tor26 has changed IP address.
32445 o Bugfixes on 0.1.0.x:
32446 - Fix a possible double-free in tor_gzip_uncompress().
32447 - When --disable-threads is set, do not search for or link against
32448 pthreads libraries.
32449 - Don't trigger an assert if an authoritative directory server
32450 claims its dirport is 0.
32451 - Fix bug with removing Tor as an NT service: some people were
32452 getting "The service did not return an error." Thanks to Matt
32456 Changes in version 0.1.1.2-alpha - 2005-07-15
32457 o New directory servers:
32458 - tor26 has changed IP address.
32460 o Bugfixes on 0.1.0.x, crashes/leaks:
32461 - Port the servers-not-obeying-their-exit-policies fix from
32463 - Fix an fd leak in start_daemon().
32464 - On Windows, you can't always reopen a port right after you've
32465 closed it. So change retry_listeners() to only close and re-open
32466 ports that have changed.
32467 - Fix a possible double-free in tor_gzip_uncompress().
32469 o Bugfixes on 0.1.0.x, usability:
32470 - When tor_socketpair() fails in Windows, give a reasonable
32471 Windows-style errno back.
32472 - Let people type "tor --install" as well as "tor -install" when
32474 want to make it an NT service.
32475 - NT service patch from Matt Edman to improve error messages.
32476 - When the controller asks for a config option with an abbreviated
32477 name, give the full name in our response.
32478 - Correct the man page entry on TrackHostExitsExpire.
32479 - Looks like we were never delivering deflated (i.e. compressed)
32480 running-routers lists, even when asked. Oops.
32481 - When --disable-threads is set, do not search for or link against
32482 pthreads libraries.
32484 o Bugfixes on 0.1.1.x:
32485 - Fix a seg fault with autodetecting which controller version is
32489 - New hidden service descriptor format: put a version in it, and
32490 let people specify introduction/rendezvous points that aren't
32491 in "the directory" (which is subjective anyway).
32492 - Allow the DEBUG controller event to work again. Mark certain log
32493 entries as "don't tell this to controllers", so we avoid cycles.
32496 Changes in version 0.1.0.11 - 2005-06-30
32497 o Bugfixes on 0.1.0.x:
32498 - Fix major security bug: servers were disregarding their
32499 exit policies if clients behaved unexpectedly.
32500 - Make OS X init script check for missing argument, so we don't
32501 confuse users who invoke it incorrectly.
32502 - Fix a seg fault in "tor --hash-password foo".
32503 - The MAPADDRESS control command was broken.
32506 Changes in version 0.1.1.1-alpha - 2005-06-29
32508 - Make OS X init script check for missing argument, so we don't
32509 confuse users who invoke it incorrectly.
32510 - Fix a seg fault in "tor --hash-password foo".
32511 - Fix a possible way to DoS dirservers.
32512 - When we complain that your exit policy implicitly allows local or
32513 private address spaces, name them explicitly so operators can
32515 - Make the log message less scary when all the dirservers are
32516 temporarily unreachable.
32517 - We were printing the number of idle dns workers incorrectly when
32521 - Revised controller protocol (version 1) that uses ascii rather
32522 than binary. Add supporting libraries in python and java so you
32523 can use the controller from your applications without caring how
32524 our protocol works.
32525 - Spiffy new support for crypto hardware accelerators. Can somebody
32529 Changes in version 0.0.9.10 - 2005-06-16
32530 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
32531 - Refuse relay cells that claim to have a length larger than the
32532 maximum allowed. This prevents a potential attack that could read
32533 arbitrary memory (e.g. keys) from an exit server's process
32537 Changes in version 0.1.0.10 - 2005-06-14
32538 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
32539 libevent before 1.1a.
32542 Changes in version 0.1.0.9-rc - 2005-06-09
32544 - Reset buf->highwater every time buf_shrink() is called, not just on
32545 a successful shrink. This was causing significant memory bloat.
32546 - Fix buffer overflow when checking hashed passwords.
32547 - Security fix: if seeding the RNG on Win32 fails, quit.
32548 - Allow seeding the RNG on Win32 even when you're not running as
32550 - Disable threading on Solaris too. Something is wonky with it,
32551 cpuworkers, and reentrant libs.
32552 - Reenable the part of the code that tries to flush as soon as an
32553 OR outbuf has a full TLS record available. Perhaps this will make
32554 OR outbufs not grow as huge except in rare cases, thus saving lots
32555 of CPU time plus memory.
32556 - Reject malformed .onion addresses rather then passing them on as
32557 normal web requests.
32558 - Adapt patch from Adam Langley: fix possible memory leak in
32559 tor_lookup_hostname().
32560 - Initialize libevent later in the startup process, so the logs are
32561 already established by the time we start logging libevent warns.
32562 - Use correct errno on win32 if libevent fails.
32563 - Check and warn about known-bad/slow libevent versions.
32564 - Pay more attention to the ClientOnly config option.
32565 - Have torctl.in/tor.sh.in check for location of su binary (needed
32567 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
32568 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
32569 HttpProxyAuthenticator
32570 - Stop warning about sigpipes in the logs. We're going to
32571 pretend that getting these occasionally is normal and fine.
32572 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
32574 installer screens; and don't put stuff into StartupItems unless
32575 the user asks you to.
32576 - Require servers that use the default dirservers to have public IP
32577 addresses. We have too many servers that are configured with private
32578 IPs and their admins never notice the log entries complaining that
32579 their descriptors are being rejected.
32580 - Add OSX uninstall instructions. An actual uninstall script will
32584 Changes in version 0.1.0.8-rc - 2005-05-23
32586 - It turns out that kqueue on OS X 10.3.9 was causing kernel
32587 panics. Disable kqueue on all OS X Tors.
32588 - Fix RPM: remove duplicate line accidentally added to the rpm
32590 - Disable threads on openbsd too, since its gethostaddr is not
32592 - Tolerate libevent 0.8 since it still works, even though it's
32594 - Enable building on Red Hat 9.0 again.
32595 - Allow the middle hop of the testing circuit to be running any
32596 version, now that most of them have the bugfix to let them connect
32597 to unknown servers. This will allow reachability testing to work
32598 even when 0.0.9.7-0.0.9.9 become obsolete.
32599 - Handle relay cells with rh.length too large. This prevents
32600 a potential attack that could read arbitrary memory (maybe even
32601 keys) from the exit server's process.
32602 - We screwed up the dirport reachability testing when we don't yet
32603 have a cached version of the directory. Hopefully now fixed.
32604 - Clean up router_load_single_router() (used by the controller),
32605 so it doesn't seg fault on error.
32606 - Fix a minor memory leak when somebody establishes an introduction
32607 point at your Tor server.
32608 - If a socks connection ends because read fails, don't warn that
32609 you're not sending a socks reply back.
32612 - Add HttpProxyAuthenticator config option too, that works like
32613 the HttpsProxyAuthenticator config option.
32614 - Encode hashed controller passwords in hex instead of base64,
32615 to make it easier to write controllers.
32618 Changes in version 0.1.0.7-rc - 2005-05-17
32620 - Fix a bug in the OS X package installer that prevented it from
32621 installing on Tiger.
32622 - Fix a script bug in the OS X package installer that made it
32623 complain during installation.
32624 - Find libevent even if it's hiding in /usr/local/ and your
32625 CFLAGS and LDFLAGS don't tell you to look there.
32626 - Be able to link with libevent as a shared library (the default
32627 after 1.0d), even if it's hiding in /usr/local/lib and even
32628 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
32629 assuming you're running gcc. Otherwise fail and give a useful
32631 - Fix a bug in the RPM packager: set home directory for _tor to
32632 something more reasonable when first installing.
32633 - Free a minor amount of memory that is still reachable on exit.
32636 Changes in version 0.1.0.6-rc - 2005-05-14
32638 - Implement --disable-threads configure option. Disable threads on
32639 netbsd by default, because it appears to have no reentrant resolver
32641 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
32642 release (1.1) detects and disables kqueue if it's broken.
32643 - Append default exit policy before checking for implicit internal
32644 addresses. Now we don't log a bunch of complaints on startup
32645 when using the default exit policy.
32646 - Some people were putting "Address " in their torrc, and they had
32647 a buggy resolver that resolved " " to 0.0.0.0. Oops.
32648 - If DataDir is ~/.tor, and that expands to /.tor, then default to
32649 LOCALSTATEDIR/tor instead.
32650 - Fix fragmented-message bug in TorControl.py.
32651 - Resolve a minor bug which would prevent unreachable dirports
32652 from getting suppressed in the published descriptor.
32653 - When the controller gave us a new descriptor, we weren't resolving
32654 it immediately, so Tor would think its address was 0.0.0.0 until
32655 we fetched a new directory.
32656 - Fix an uppercase/lowercase case error in suppressing a bogus
32657 libevent warning on some Linuxes.
32660 - Begin scrubbing sensitive strings from logs by default. Turn off
32661 the config option SafeLogging if you need to do debugging.
32662 - Switch to a new buffer management algorithm, which tries to avoid
32663 reallocing and copying quite as much. In first tests it looks like
32664 it uses *more* memory on average, but less cpu.
32665 - First cut at support for "create-fast" cells. Clients can use
32666 these when extending to their first hop, since the TLS already
32667 provides forward secrecy and authentication. Not enabled on
32669 - When dirservers refuse a router descriptor, we now log its
32670 contactinfo, platform, and the poster's IP address.
32671 - Call tor_free_all instead of connections_free_all after forking, to
32672 save memory on systems that need to fork.
32673 - Whine at you if you're a server and you don't set your contactinfo.
32674 - Implement --verify-config command-line option to check if your torrc
32675 is valid without actually launching Tor.
32676 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
32677 rather than just rejecting it.
32680 Changes in version 0.1.0.5-rc - 2005-04-27
32682 - Stop trying to print a null pointer if an OR conn fails because
32683 we didn't like its cert.
32685 - Switch our internal buffers implementation to use a ring buffer,
32686 to hopefully improve performance for fast servers a lot.
32687 - Add HttpsProxyAuthenticator support (basic auth only), based
32688 on patch from Adam Langley.
32689 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
32690 the fast servers that have been joining lately.
32691 - Give hidden service accesses extra time on the first attempt,
32692 since 60 seconds is often only barely enough. This might improve
32694 - Improve performance for dirservers: stop re-parsing the whole
32695 directory every time you regenerate it.
32696 - Add more debugging info to help us find the weird dns freebsd
32697 pthreads bug; cleaner debug messages to help track future issues.
32700 Changes in version 0.0.9.9 - 2005-04-23
32701 o Bugfixes on 0.0.9.x:
32702 - If unofficial Tor clients connect and send weird TLS certs, our
32703 Tor server triggers an assert. This release contains a minimal
32704 backport from the broader fix that we put into 0.1.0.4-rc.
32707 Changes in version 0.1.0.4-rc - 2005-04-23
32709 - If unofficial Tor clients connect and send weird TLS certs, our
32710 Tor server triggers an assert. Stop asserting, and start handling
32711 TLS errors better in other situations too.
32712 - When the controller asks us to tell it about all the debug-level
32713 logs, it turns out we were generating debug-level logs while
32714 telling it about them, which turns into a bad loop. Now keep
32715 track of whether you're sending a debug log to the controller,
32716 and don't log when you are.
32717 - Fix the "postdescriptor" feature of the controller interface: on
32718 non-complete success, only say "done" once.
32720 - Clients are now willing to load balance over up to 2mB, not 1mB,
32721 of advertised bandwidth capacity.
32722 - Add a NoPublish config option, so you can be a server (e.g. for
32723 testing running Tor servers in other Tor networks) without
32724 publishing your descriptor to the primary dirservers.
32727 Changes in version 0.1.0.3-rc - 2005-04-08
32728 o Improvements on 0.1.0.2-rc:
32729 - Client now retries when streams end early for 'hibernating' or
32730 'resource limit' reasons, rather than failing them.
32731 - More automated handling for dirserver operators:
32732 - Automatically approve nodes running 0.1.0.2-rc or later,
32733 now that the the reachability detection stuff is working.
32734 - Now we allow two unverified servers with the same nickname
32735 but different keys. But if a nickname is verified, only that
32736 nickname+key are allowed.
32737 - If you're an authdirserver connecting to an address:port,
32738 and it's not the OR you were expecting, forget about that
32739 descriptor. If he *was* the one you were expecting, then forget
32740 about all other descriptors for that address:port.
32741 - Allow servers to publish descriptors from 12 hours in the future.
32742 Corollary: only whine about clock skew from the dirserver if
32743 he's a trusted dirserver (since now even verified servers could
32744 have quite wrong clocks).
32745 - Adjust maximum skew and age for rendezvous descriptors: let skew
32746 be 48 hours rather than 90 minutes.
32747 - Efficiency improvements:
32748 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
32749 it much faster to look up a circuit for each relay cell.
32750 - Remove most calls to assert_all_pending_dns_resolves_ok(),
32751 since they're eating our cpu on exit nodes.
32752 - Stop wasting time doing a case insensitive comparison for every
32753 dns name every time we do any lookup. Canonicalize the names to
32754 lowercase and be done with it.
32755 - Start sending 'truncated' cells back rather than destroy cells,
32756 if the circuit closes in front of you. This means we won't have
32757 to abandon partially built circuits.
32758 - Only warn once per nickname from add_nickname_list_to_smartlist
32759 per failure, so an entrynode or exitnode choice that's down won't
32761 - Put a note in the torrc about abuse potential with the default
32763 - Revise control spec and implementation to allow all log messages to
32764 be sent to controller with their severities intact (suggested by
32765 Matt Edman). Update TorControl to handle new log event types.
32766 - Provide better explanation messages when controller's POSTDESCRIPTOR
32768 - Stop putting nodename in the Platform string in server descriptors.
32769 It doesn't actually help, and it is confusing/upsetting some people.
32771 o Bugfixes on 0.1.0.2-rc:
32772 - We were printing the host mask wrong in exit policies in server
32773 descriptors. This isn't a critical bug though, since we were still
32774 obeying the exit policy internally.
32775 - Fix Tor when compiled with libevent but without pthreads: move
32776 connection_unregister() from _connection_free() to
32778 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
32779 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
32780 when we look through the connection array, we'll find any of the
32781 cpu/dnsworkers. This is no good.
32783 o Bugfixes on 0.0.9.8:
32784 - Fix possible bug on threading platforms (e.g. win32) which was
32785 leaking a file descriptor whenever a cpuworker or dnsworker died.
32786 - When using preferred entry or exit nodes, ignore whether the
32787 circuit wants uptime or capacity. They asked for the nodes, they
32789 - chdir() to your datadirectory at the *end* of the daemonize process,
32790 not the beginning. This was a problem because the first time you
32791 run tor, if your datadir isn't there, and you have runasdaemon set
32792 to 1, it will try to chdir to it before it tries to create it. Oops.
32793 - Handle changed router status correctly when dirserver reloads
32794 fingerprint file. We used to be dropping all unverified descriptors
32795 right then. The bug was hidden because we would immediately
32796 fetch a directory from another dirserver, which would include the
32797 descriptors we just dropped.
32798 - When we're connecting to an OR and he's got a different nickname/key
32799 than we were expecting, only complain loudly if we're an OP or a
32800 dirserver. Complaining loudly to the OR admins just confuses them.
32801 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
32802 artificially capped at 500kB.
32805 Changes in version 0.0.9.8 - 2005-04-07
32806 o Bugfixes on 0.0.9.x:
32807 - We have a bug that I haven't found yet. Sometimes, very rarely,
32808 cpuworkers get stuck in the 'busy' state, even though the cpuworker
32809 thinks of itself as idle. This meant that no new circuits ever got
32810 established. Here's a workaround to kill any cpuworker that's been
32811 busy for more than 100 seconds.
32814 Changes in version 0.1.0.2-rc - 2005-04-01
32815 o Bugfixes on 0.1.0.1-rc:
32816 - Fixes on reachability detection:
32817 - Don't check for reachability while hibernating.
32818 - If ORPort is reachable but DirPort isn't, still publish the
32819 descriptor, but zero out DirPort until it's found reachable.
32820 - When building testing circs for ORPort testing, use only
32821 high-bandwidth nodes, so fewer circuits fail.
32822 - Complain about unreachable ORPort separately from unreachable
32823 DirPort, so the user knows what's going on.
32824 - Make sure we only conclude ORPort reachability if we didn't
32825 initiate the conn. Otherwise we could falsely conclude that
32826 we're reachable just because we connected to the guy earlier
32827 and he used that same pipe to extend to us.
32828 - Authdirservers shouldn't do ORPort reachability detection,
32829 since they're in clique mode, so it will be rare to find a
32830 server not already connected to them.
32831 - When building testing circuits, always pick middle hops running
32832 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
32833 bug. (This is a kludge; it will go away when 0.0.9.x becomes
32835 - When we decide we're reachable, actually publish our descriptor
32837 - Fix bug in redirectstream in the controller.
32838 - Fix the state descriptor strings so logs don't claim edge streams
32839 are in a different state than they actually are.
32840 - Use recent libevent features when possible (this only really affects
32841 win32 and osx right now, because the new libevent with these
32842 features hasn't been released yet). Add code to suppress spurious
32844 - Prevent possible segfault in connection_close_unattached_ap().
32845 - Fix newlines on torrc in win32.
32846 - Improve error msgs when tor-resolve fails.
32848 o Improvements on 0.0.9.x:
32849 - New experimental script tor/contrib/ExerciseServer.py (needs more
32850 work) that uses the controller interface to build circuits and
32851 fetch pages over them. This will help us bootstrap servers that
32852 have lots of capacity but haven't noticed it yet.
32853 - New experimental script tor/contrib/PathDemo.py (needs more work)
32854 that uses the controller interface to let you choose whole paths
32856 "<hostname>.<path,separated by dots>.<length of path>.path"
32857 - When we've connected to an OR and handshaked but didn't like
32858 the result, we were closing the conn without sending destroy
32859 cells back for pending circuits. Now send those destroys.
32862 Changes in version 0.0.9.7 - 2005-04-01
32863 o Bugfixes on 0.0.9.x:
32864 - Fix another race crash bug (thanks to Glenn Fink for reporting).
32865 - Compare identity to identity, not to nickname, when extending to
32866 a router not already in the directory. This was preventing us from
32867 extending to unknown routers. Oops.
32868 - Make sure to create OS X Tor user in <500 range, so we aren't
32869 creating actual system users.
32870 - Note where connection-that-hasn't-sent-end was marked, and fix
32871 a few really loud instances of this harmless bug (it's fixed more
32875 Changes in version 0.1.0.1-rc - 2005-03-28
32877 - Add reachability testing. Your Tor server will automatically try
32878 to see if its ORPort and DirPort are reachable from the outside,
32879 and it won't upload its descriptor until it decides they are.
32880 - Handle unavailable hidden services better. Handle slow or busy
32881 hidden services better.
32882 - Add support for CONNECTing through https proxies, with "HttpsProxy"
32884 - New exit policy: accept most low-numbered ports, rather than
32885 rejecting most low-numbered ports.
32886 - More Tor controller support (still experimental). See
32887 http://tor.eff.org/doc/control-spec.txt for all the new features,
32888 including signals to emulate unix signals from any platform;
32889 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
32890 closestream; closecircuit; etc.
32891 - Make nt services work and start on startup on win32 (based on
32892 patch by Matt Edman).
32893 - Add a new AddressMap config directive to rewrite incoming socks
32894 addresses. This lets you, for example, declare an implicit
32895 required exit node for certain sites.
32896 - Add a new TrackHostExits config directive to trigger addressmaps
32897 for certain incoming socks addresses -- for sites that break when
32898 your exit keeps changing (based on patch by Mike Perry).
32899 - Redo the client-side dns cache so it's just an addressmap too.
32900 - Notice when our IP changes, and reset stats/uptime/reachability.
32901 - When an application is using socks5, give him the whole variety of
32902 potential socks5 responses (connect refused, host unreachable, etc),
32903 rather than just "success" or "failure".
32904 - A more sane version numbering system. See
32905 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
32906 - New contributed script "exitlist": a simple python script to
32907 parse directories and find Tor nodes that exit to listed
32909 - New contributed script "privoxy-tor-toggle" to toggle whether
32910 Privoxy uses Tor. Seems to be configured for Debian by default.
32911 - Report HTTP reasons to client when getting a response from directory
32912 servers -- so you can actually know what went wrong.
32913 - New config option MaxAdvertisedBandwidth which lets you advertise
32914 a low bandwidthrate (to not attract as many circuits) while still
32915 allowing a higher bandwidthrate in reality.
32917 o Robustness/stability fixes:
32918 - Make Tor use Niels Provos's libevent instead of its current
32919 poll-but-sometimes-select mess. This will let us use faster async
32920 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
32922 - pthread support now too. This was forced because when we forked,
32923 we ended up wasting a lot of duplicate ram over time. Also switch
32924 to foo_r versions of some library calls to allow reentry and
32926 - Better handling for heterogeneous / unreliable nodes:
32927 - Annotate circuits w/ whether they aim to contain high uptime nodes
32928 and/or high capacity nodes. When building circuits, choose
32930 - This means that every single node in an intro rend circuit,
32931 not just the last one, will have a minimum uptime.
32932 - New config option LongLivedPorts to indicate application streams
32933 that will want high uptime circuits.
32934 - Servers reset uptime when a dir fetch entirely fails. This
32935 hopefully reflects stability of the server's network connectivity.
32936 - If somebody starts his tor server in Jan 2004 and then fixes his
32937 clock, don't make his published uptime be a year.
32938 - Reset published uptime when you wake up from hibernation.
32939 - Introduce a notion of 'internal' circs, which are chosen without
32940 regard to the exit policy of the last hop. Intro and rendezvous
32941 circs must be internal circs, to avoid leaking information. Resolve
32942 and connect streams can use internal circs if they want.
32943 - New circuit pooling algorithm: make sure to have enough circs around
32944 to satisfy any predicted ports, and also make sure to have 2 internal
32945 circs around if we've required internal circs lately (and with high
32946 uptime if we've seen that lately too).
32947 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
32948 which describes how often we retry making new circuits if current
32949 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
32950 how long we're willing to make use of an already-dirty circuit.
32951 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
32952 circ as necessary, if there are any completed ones lying around
32953 when we try to launch one.
32954 - Make hidden services try to establish a rendezvous for 30 seconds,
32955 rather than for n (where n=3) attempts to build a circuit.
32956 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
32957 "ShutdownWaitLength".
32958 - Try to be more zealous about calling connection_edge_end when
32959 things go bad with edge conns in connection.c.
32960 - Revise tor-spec to add more/better stream end reasons.
32961 - Revise all calls to connection_edge_end to avoid sending "misc",
32962 and to take errno into account where possible.
32965 - Fix a race condition that can trigger an assert, when we have a
32966 pending create cell and an OR connection fails right then.
32967 - Fix several double-mark-for-close bugs, e.g. where we were finding
32968 a conn for a cell even if that conn is already marked for close.
32969 - Make sequence of log messages when starting on win32 with no config
32970 file more reasonable.
32971 - When choosing an exit node for a new non-internal circ, don't take
32972 into account whether it'll be useful for any pending x.onion
32973 addresses -- it won't.
32974 - Turn addr_policy_compare from a tristate to a quadstate; this should
32975 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
32976 for google.com" problem.
32977 - Make "platform" string in descriptor more accurate for Win32 servers,
32978 so it's not just "unknown platform".
32979 - Fix an edge case in parsing config options (thanks weasel).
32980 If they say "--" on the commandline, it's not an option.
32981 - Reject odd-looking addresses at the client (e.g. addresses that
32982 contain a colon), rather than having the server drop them because
32984 - tor-resolve requests were ignoring .exit if there was a working circuit
32985 they could use instead.
32986 - REUSEADDR on normal platforms means you can rebind to the port
32987 right after somebody else has let it go. But REUSEADDR on win32
32988 means to let you bind to the port _even when somebody else
32989 already has it bound_! So, don't do that on Win32.
32990 - Change version parsing logic: a version is "obsolete" if it is not
32991 recommended and (1) there is a newer recommended version in the
32992 same series, or (2) there are no recommended versions in the same
32993 series, but there are some recommended versions in a newer series.
32994 A version is "new" if it is newer than any recommended version in
32996 - Stop most cases of hanging up on a socks connection without sending
33000 - Require BandwidthRate to be at least 20kB/s for servers.
33001 - When a dirserver causes you to give a warn, mention which dirserver
33003 - New config option DirAllowPrivateAddresses for authdirservers.
33004 Now by default they refuse router descriptors that have non-IP or
33005 private-IP addresses.
33006 - Stop publishing socksport in the directory, since it's not
33007 actually meant to be public. For compatibility, publish a 0 there
33009 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
33010 smart" value, that is low for servers and high for clients.
33011 - If our clock jumps forward by 100 seconds or more, assume something
33012 has gone wrong with our network and abandon all not-yet-used circs.
33013 - Warn when exit policy implicitly allows local addresses.
33014 - If we get an incredibly skewed timestamp from a dirserver mirror
33015 that isn't a verified OR, don't warn -- it's probably him that's
33017 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
33018 cookies to disk and doesn't log each web request to disk. (Thanks
33019 to Brett Carrington for pointing this out.)
33020 - When a client asks us for a dir mirror and we don't have one,
33021 launch an attempt to get a fresh one.
33022 - If we're hibernating and we get a SIGINT, exit immediately.
33023 - Add --with-dmalloc ./configure option, to track memory leaks.
33024 - And try to free all memory on closing, so we can detect what
33026 - Cache local dns resolves correctly even when they're .exit
33028 - Give a better warning when some other server advertises an
33029 ORPort that is actually an apache running ssl.
33030 - Add "opt hibernating 1" to server descriptor to make it clearer
33031 whether the server is hibernating.
33034 Changes in version 0.0.9.6 - 2005-03-24
33035 o Bugfixes on 0.0.9.x (crashes and asserts):
33036 - Add new end stream reasons to maintenance branch. Fix bug where
33037 reason (8) could trigger an assert. Prevent bug from recurring.
33038 - Apparently win32 stat wants paths to not end with a slash.
33039 - Fix assert triggers in assert_cpath_layer_ok(), where we were
33040 blowing away the circuit that conn->cpath_layer points to, then
33041 checking to see if the circ is well-formed. Backport check to make
33042 sure we dont use the cpath on a closed connection.
33043 - Prevent circuit_resume_edge_reading_helper() from trying to package
33044 inbufs for marked-for-close streams.
33045 - Don't crash on hup if your options->address has become unresolvable.
33046 - Some systems (like OS X) sometimes accept() a connection and tell
33047 you the remote host is 0.0.0.0:0. If this happens, due to some
33048 other mis-features, we get confused; so refuse the conn for now.
33050 o Bugfixes on 0.0.9.x (other):
33051 - Fix harmless but scary "Unrecognized content encoding" warn message.
33052 - Add new stream error reason: TORPROTOCOL reason means "you are not
33053 speaking a version of Tor I understand; say bye-bye to your stream."
33054 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
33055 into the future, now that we are more tolerant of skew. This
33056 resolves a bug where a Tor server would refuse to cache a directory
33057 because all the directories it gets are too far in the future;
33058 yet the Tor server never logs any complaints about clock skew.
33059 - Mac packaging magic: make man pages useable, and do not overwrite
33060 existing torrc files.
33061 - Make OS X log happily to /var/log/tor/tor.log
33064 Changes in version 0.0.9.5 - 2005-02-22
33065 o Bugfixes on 0.0.9.x:
33066 - Fix an assert race at exit nodes when resolve requests fail.
33067 - Stop picking unverified dir mirrors--it only leads to misery.
33068 - Patch from Matt Edman to make NT services work better. Service
33069 support is still not compiled into the executable by default.
33070 - Patch from Dmitri Bely so the Tor service runs better under
33071 the win32 SYSTEM account.
33072 - Make tor-resolve actually work (?) on Win32.
33073 - Fix a sign bug when getrlimit claims to have 4+ billion
33074 file descriptors available.
33075 - Stop refusing to start when bandwidthburst == bandwidthrate.
33076 - When create cells have been on the onion queue more than five
33077 seconds, just send back a destroy and take them off the list.
33080 Changes in version 0.0.9.4 - 2005-02-03
33081 o Bugfixes on 0.0.9:
33082 - Fix an assert bug that took down most of our servers: when
33083 a server claims to have 1 GB of bandwidthburst, don't
33085 - Don't crash as badly if we have spawned the max allowed number
33086 of dnsworkers, or we're out of file descriptors.
33087 - Block more file-sharing ports in the default exit policy.
33088 - MaxConn is now automatically set to the hard limit of max
33089 file descriptors we're allowed (ulimit -n), minus a few for
33091 - Give a clearer message when servers need to raise their
33092 ulimit -n when they start running out of file descriptors.
33093 - SGI Compatibility patches from Jan Schaumann.
33094 - Tolerate a corrupt cached directory better.
33095 - When a dirserver hasn't approved your server, list which one.
33096 - Go into soft hibernation after 95% of the bandwidth is used,
33097 not 99%. This is especially important for daily hibernators who
33098 have a small accounting max. Hopefully it will result in fewer
33099 cut connections when the hard hibernation starts.
33100 - Load-balance better when using servers that claim more than
33101 800kB/s of capacity.
33102 - Make NT services work (experimental, only used if compiled in).
33105 Changes in version 0.0.9.3 - 2005-01-21
33106 o Bugfixes on 0.0.9:
33107 - Backport the cpu use fixes from main branch, so busy servers won't
33108 need as much processor time.
33109 - Work better when we go offline and then come back, or when we
33110 run Tor at boot before the network is up. We do this by
33111 optimistically trying to fetch a new directory whenever an
33112 application request comes in and we think we're offline -- the
33113 human is hopefully a good measure of when the network is back.
33114 - Backport some minimal hidserv bugfixes: keep rend circuits open as
33115 long as you keep using them; actually publish hidserv descriptors
33116 shortly after they change, rather than waiting 20-40 minutes.
33117 - Enable Mac startup script by default.
33118 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
33119 - When you update AllowUnverifiedNodes or FirewallPorts via the
33120 controller's setconf feature, we were always appending, never
33122 - When you update HiddenServiceDir via setconf, it was screwing up
33123 the order of reading the lines, making it fail.
33124 - Do not rewrite a cached directory back to the cache; otherwise we
33125 will think it is recent and not fetch a newer one on startup.
33126 - Workaround for webservers that lie about Content-Encoding: Tor
33127 now tries to autodetect compressed directories and compression
33128 itself. This lets us Proxypass dir fetches through apache.
33131 Changes in version 0.0.9.2 - 2005-01-04
33132 o Bugfixes on 0.0.9 (crashes and asserts):
33133 - Fix an assert on startup when the disk is full and you're logging
33135 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
33136 style address, then we'd crash.
33137 - Fix an assert trigger when the running-routers string we get from
33138 a dirserver is broken.
33139 - Make worker threads start and run on win32. Now win32 servers
33141 - Bandaid (not actually fix, but now it doesn't crash) an assert
33142 where the dns worker dies mysteriously and the main Tor process
33143 doesn't remember anything about the address it was resolving.
33145 o Bugfixes on 0.0.9 (Win32):
33146 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
33147 name out of the warning/assert messages.
33148 - Fix a superficial "unhandled error on read" bug on win32.
33149 - The win32 installer no longer requires a click-through for our
33150 license, since our Free Software license grants rights but does not
33152 - Win32: When connecting to a dirserver fails, try another one
33153 immediately. (This was already working for non-win32 Tors.)
33154 - Stop trying to parse $HOME on win32 when hunting for default
33156 - Make tor-resolve.c work on win32 by calling network_init().
33158 o Bugfixes on 0.0.9 (other):
33159 - Make 0.0.9.x build on Solaris again.
33160 - Due to a fencepost error, we were blowing away the \n when reporting
33161 confvalue items in the controller. So asking for multiple config
33162 values at once couldn't work.
33163 - When listing circuits that are pending on an opening OR connection,
33164 if we're an OR we were listing circuits that *end* at us as
33165 being pending on every listener, dns/cpu worker, etc. Stop that.
33166 - Dirservers were failing to create 'running-routers' or 'directory'
33167 strings if we had more than some threshold of routers. Fix them so
33168 they can handle any number of routers.
33169 - Fix a superficial "Duplicate mark for close" bug.
33170 - Stop checking for clock skew for OR connections, even for servers.
33171 - Fix a fencepost error that was chopping off the last letter of any
33172 nickname that is the maximum allowed nickname length.
33173 - Update URLs in log messages so they point to the new website.
33174 - Fix a potential problem in mangling server private keys while
33175 writing to disk (not triggered yet, as far as we know).
33176 - Include the licenses for other free software we include in Tor,
33177 now that we're shipping binary distributions more regularly.
33180 Changes in version 0.0.9.1 - 2004-12-15
33181 o Bugfixes on 0.0.9:
33182 - Make hibernation actually work.
33183 - Make HashedControlPassword config option work.
33184 - When we're reporting event circuit status to a controller,
33185 don't use the stream status code.
33188 Changes in version 0.0.9 - 2004-12-12
33190 - Clean up manpage and torrc.sample file.
33191 - Clean up severities and text of log warnings.
33193 - Make servers trigger an assert when they enter hibernation.
33196 Changes in version 0.0.9rc7 - 2004-12-08
33197 o Bugfixes on 0.0.9rc:
33198 - Fix a stack-trashing crash when an exit node begins hibernating.
33199 - Avoid looking at unallocated memory while considering which
33200 ports we need to build circuits to cover.
33201 - Stop a sigpipe: when an 'end' cell races with eof from the app,
33202 we shouldn't hold-open-until-flush if the eof arrived first.
33203 - Fix a bug with init_cookie_authentication() in the controller.
33204 - When recommending new-format log lines, if the upper bound is
33205 LOG_ERR, leave it implicit.
33207 o Bugfixes on 0.0.8.1:
33208 - Fix a whole slew of memory leaks.
33209 - Fix isspace() and friends so they still make Solaris happy
33210 but also so they don't trigger asserts on win32.
33211 - Fix parse_iso_time on platforms without strptime (eg win32).
33212 - win32: tolerate extra "readable" events better.
33213 - win32: when being multithreaded, leave parent fdarray open.
33214 - Make unit tests work on win32.
33217 Changes in version 0.0.9rc6 - 2004-12-06
33218 o Bugfixes on 0.0.9pre:
33219 - Clean up some more integer underflow opportunities (not exploitable
33221 - While hibernating, hup should not regrow our listeners.
33222 - Send an end to the streams we close when we hibernate, rather
33223 than just chopping them off.
33224 - React to eof immediately on non-open edge connections.
33226 o Bugfixes on 0.0.8.1:
33227 - Calculate timeout for waiting for a connected cell from the time
33228 we sent the begin cell, not from the time the stream started. If
33229 it took a long time to establish the circuit, we would time out
33230 right after sending the begin cell.
33231 - Fix router_compare_addr_to_addr_policy: it was not treating a port
33232 of * as always matching, so we were picking reject *:* nodes as
33233 exit nodes too. Oops.
33236 - New circuit building strategy: keep a list of ports that we've
33237 used in the past 6 hours, and always try to have 2 circuits open
33238 or on the way that will handle each such port. Seed us with port
33239 80 so web users won't complain that Tor is "slow to start up".
33240 - Make kill -USR1 dump more useful stats about circuits.
33241 - When warning about retrying or giving up, print the address, so
33242 the user knows which one it's talking about.
33243 - If you haven't used a clean circuit in an hour, throw it away,
33244 just to be on the safe side. (This means after 6 hours a totally
33245 unused Tor client will have no circuits open.)
33248 Changes in version 0.0.9rc5 - 2004-12-01
33249 o Bugfixes on 0.0.8.1:
33250 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
33251 - Let resolve conns retry/expire also, rather than sticking around
33253 - If we are using select, make sure we stay within FD_SETSIZE.
33255 o Bugfixes on 0.0.9pre:
33256 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
33257 but doesn't seem to be currently; thanks to Ilja van Sprundel for
33259 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
33260 instead. Impose minima and maxima for all *Period options; impose
33261 even tighter maxima for fetching if we are a caching dirserver.
33262 Clip rather than rejecting.
33263 - Fetch cached running-routers from servers that serve it (that is,
33264 authdirservers and servers running 0.0.9rc5-cvs or later.)
33267 - Accept *:706 (silc) in default exit policy.
33268 - Implement new versioning format for post 0.1.
33269 - Support "foo.nickname.exit" addresses, to let Alice request the
33270 address "foo" as viewed by exit node "nickname". Based on a patch
33272 - Make tor --version --version dump the cvs Id of every file.
33275 Changes in version 0.0.9rc4 - 2004-11-28
33276 o Bugfixes on 0.0.8.1:
33277 - Make windows sockets actually non-blocking (oops), and handle
33278 win32 socket errors better.
33280 o Bugfixes on 0.0.9rc1:
33281 - Actually catch the -USR2 signal.
33284 Changes in version 0.0.9rc3 - 2004-11-25
33285 o Bugfixes on 0.0.8.1:
33286 - Flush the log file descriptor after we print "Tor opening log file",
33287 so we don't see those messages days later.
33289 o Bugfixes on 0.0.9rc1:
33290 - Make tor-resolve work again.
33291 - Avoid infinite loop in tor-resolve if tor hangs up on it.
33292 - Fix an assert trigger for clients/servers handling resolves.
33295 Changes in version 0.0.9rc2 - 2004-11-24
33296 o Bugfixes on 0.0.9rc1:
33297 - I broke socks5 support while fixing the eof bug.
33298 - Allow unitless bandwidths and intervals; they default to bytes
33300 - New servers don't start out hibernating; they are active until
33301 they run out of bytes, so they have a better estimate of how
33302 long it takes, and so their operators can know they're working.
33305 Changes in version 0.0.9rc1 - 2004-11-23
33306 o Bugfixes on 0.0.8.1:
33307 - Finally fix a bug that's been plaguing us for a year:
33308 With high load, circuit package window was reaching 0. Whenever
33309 we got a circuit-level sendme, we were reading a lot on each
33310 socket, but only writing out a bit. So we would eventually reach
33311 eof. This would be noticed and acted on even when there were still
33312 bytes sitting in the inbuf.
33313 - When poll() is interrupted, we shouldn't believe the revents values.
33315 o Bugfixes on 0.0.9pre6:
33316 - Fix hibernate bug that caused pre6 to be broken.
33317 - Don't keep rephist info for routers that haven't had activity for
33318 24 hours. (This matters now that clients have keys, since we track
33320 - Never call close_temp_logs while validating log options.
33321 - Fix backslash-escaping on tor.sh.in and torctl.in.
33324 - Implement weekly/monthly/daily accounting: now you specify your
33325 hibernation properties by
33326 AccountingMax N bytes|KB|MB|GB|TB
33327 AccountingStart day|week|month [day] HH:MM
33328 Defaults to "month 1 0:00".
33329 - Let bandwidth and interval config options be specified as 5 bytes,
33330 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
33331 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
33332 get back to normal.)
33333 - If your requested entry or exit node has advertised bandwidth 0,
33335 - Be more greedy about filling up relay cells -- we try reading again
33336 once we've processed the stuff we read, in case enough has arrived
33337 to fill the last cell completely.
33338 - Apply NT service patch from Osamu Fujino. Still needs more work.
33341 Changes in version 0.0.9pre6 - 2004-11-15
33342 o Bugfixes on 0.0.8.1:
33343 - Fix assert failure on malformed socks4a requests.
33344 - Use identity comparison, not nickname comparison, to choose which
33345 half of circuit-ID-space each side gets to use. This is needed
33346 because sometimes we think of a router as a nickname, and sometimes
33347 as a hex ID, and we can't predict what the other side will do.
33348 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
33349 write() call will fail and we handle it there.
33350 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
33351 and smartlist_len, which are two major profiling offenders.
33353 o Bugfixes on 0.0.9pre5:
33354 - Fix a bug in read_all that was corrupting config files on windows.
33355 - When we're raising the max number of open file descriptors to
33356 'unlimited', don't log that we just raised it to '-1'.
33357 - Include event code with events, as required by control-spec.txt.
33358 - Don't give a fingerprint when clients do --list-fingerprint:
33359 it's misleading, because it will never be the same again.
33360 - Stop using strlcpy in tor_strndup, since it was slowing us
33362 - Remove warn on startup about missing cached-directory file.
33363 - Make kill -USR1 work again.
33364 - Hibernate if we start tor during the "wait for wakeup-time" phase
33365 of an accounting interval. Log our hibernation plans better.
33366 - Authoritative dirservers now also cache their directory, so they
33367 have it on start-up.
33370 - Fetch running-routers; cache running-routers; compress
33371 running-routers; serve compressed running-routers.z
33372 - Add NSI installer script contributed by J Doe.
33373 - Commit VC6 and VC7 workspace/project files.
33374 - Commit a tor.spec for making RPM files, with help from jbash.
33375 - Add contrib/torctl.in contributed by Glenn Fink.
33376 - Implement the control-spec's SAVECONF command, to write your
33377 configuration to torrc.
33378 - Get cookie authentication for the controller closer to working.
33379 - Include control-spec.txt in the tarball.
33380 - When set_conf changes our server descriptor, upload a new copy.
33381 But don't upload it too often if there are frequent changes.
33382 - Document authentication config in man page, and document signals
33384 - Clean up confusing parts of man page and torrc.sample.
33385 - Make expand_filename handle ~ and ~username.
33386 - Use autoconf to enable largefile support where necessary. Use
33387 ftello where available, since ftell can fail at 2GB.
33388 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
33389 log more informatively.
33390 - Give a slightly more useful output for "tor -h".
33391 - Refuse application socks connections to port 0.
33392 - Check clock skew for verified servers, but allow unverified
33393 servers and clients to have any clock skew.
33394 - Break DirFetchPostPeriod into:
33395 - DirFetchPeriod for fetching full directory,
33396 - StatusFetchPeriod for fetching running-routers,
33397 - DirPostPeriod for posting server descriptor,
33398 - RendPostPeriod for posting hidden service descriptors.
33399 - Make sure the hidden service descriptors are at a random offset
33400 from each other, to hinder linkability.
33403 Changes in version 0.0.9pre5 - 2004-11-09
33404 o Bugfixes on 0.0.9pre4:
33405 - Fix a seg fault in unit tests (doesn't affect main program).
33406 - Fix an assert bug where a hidden service provider would fail if
33407 the first hop of his rendezvous circuit was down.
33408 - Hidden service operators now correctly handle version 1 style
33409 INTRODUCE1 cells (nobody generates them still, so not a critical
33411 - If do_hup fails, actually notice.
33412 - Handle more errnos from accept() without closing the listener.
33413 Some OpenBSD machines were closing their listeners because
33414 they ran out of file descriptors.
33415 - Send resolve cells to exit routers that are running a new
33416 enough version of the resolve code to work right.
33417 - Better handling of winsock includes on non-MSV win32 compilers.
33418 - Some people had wrapped their tor client/server in a script
33419 that would restart it whenever it died. This did not play well
33420 with our "shut down if your version is obsolete" code. Now people
33421 don't fetch a new directory if their local cached version is
33423 - Make our autogen.sh work on ksh as well as bash.
33426 - Hibernation: New config option "AccountingMaxKB" lets you
33427 set how many KBytes per month you want to allow your server to
33428 consume. Rather than spreading those bytes out evenly over the
33429 month, we instead hibernate for some of the month and pop up
33430 at a deterministic time, work until the bytes are consumed, then
33431 hibernate again. Config option "MonthlyAccountingStart" lets you
33432 specify which day of the month your billing cycle starts on.
33433 - Control interface: a separate program can now talk to your
33434 client/server over a socket, and get/set config options, receive
33435 notifications of circuits and streams starting/finishing/dying,
33436 bandwidth used, etc. The next step is to get some GUIs working.
33437 Let us know if you want to help out. See doc/control-spec.txt .
33438 - Ship a contrib/tor-control.py as an example script to interact
33439 with the control port.
33440 - "tor --hash-password zzyxz" will output a salted password for
33441 use in authenticating to the control interface.
33442 - New log format in config:
33443 "Log minsev[-maxsev] stdout|stderr|syslog" or
33444 "Log minsev[-maxsev] file /var/foo"
33447 - DirPolicy config option, to let people reject incoming addresses
33448 from their dirserver.
33449 - "tor --list-fingerprint" will list your identity key fingerprint
33451 - Add "pass" target for RedirectExit, to make it easier to break
33452 out of a sequence of RedirectExit rules.
33453 - Clients now generate a TLS cert too, in preparation for having
33454 them act more like real nodes.
33455 - Ship src/win32/ in the tarball, so people can use it to build.
33456 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
33458 - New "router-status" line in directory, to better bind each verified
33459 nickname to its identity key.
33460 - Deprecate unofficial config option abbreviations, and abbreviations
33461 not on the command line.
33462 - Add a pure-C tor-resolve implementation.
33463 - Use getrlimit and friends to ensure we can reach MaxConn (currently
33464 1024) file descriptors.
33466 o Code security improvements, inspired by Ilja:
33467 - Replace sprintf with snprintf. (I think they were all safe, but
33469 - Replace strcpy/strncpy with strlcpy in more places.
33470 - Avoid strcat; use snprintf or strlcat instead.
33471 - snprintf wrapper with consistent (though not C99) overflow behavior.
33474 Changes in version 0.0.9pre4 - 2004-10-17
33475 o Bugfixes on 0.0.9pre3:
33476 - If the server doesn't specify an exit policy, use the real default
33477 exit policy, not reject *:*.
33478 - Ignore fascistfirewall when uploading/downloading hidden service
33479 descriptors, since we go through Tor for those; and when using
33480 an HttpProxy, since we assume it can reach them all.
33481 - When looking for an authoritative dirserver, use only the ones
33482 configured at boot. Don't bother looking in the directory.
33483 - The rest of the fix for get_default_conf_file() on older win32.
33484 - Make 'Routerfile' config option obsolete.
33487 - New 'MyFamily nick1,...' config option for a server to
33488 specify other servers that shouldn't be used in the same circuit
33489 with it. Only believed if nick1 also specifies us.
33490 - New 'NodeFamily nick1,nick2,...' config option for a client to
33491 specify nodes that it doesn't want to use in the same circuit.
33492 - New 'Redirectexit pattern address:port' config option for a
33493 server to redirect exit connections, e.g. to a local squid.
33496 Changes in version 0.0.9pre3 - 2004-10-13
33497 o Bugfixes on 0.0.8.1:
33498 - Better torrc example lines for dirbindaddress and orbindaddress.
33499 - Improved bounds checking on parsed ints (e.g. config options and
33500 the ones we find in directories.)
33501 - Better handling of size_t vs int, so we're more robust on 64
33503 - Fix the rest of the bug where a newly started OR would appear
33504 as unverified even after we've added his fingerprint and hupped
33506 - Fix a bug from 0.0.7: when read() failed on a stream, we would
33507 close it without sending back an end. So 'connection refused'
33508 would simply be ignored and the user would get no response.
33510 o Bugfixes on 0.0.9pre2:
33511 - Serving the cached-on-disk directory to people is bad. We now
33512 provide no directory until we've fetched a fresh one.
33513 - Workaround for bug on windows where cached-directories get crlf
33515 - Make get_default_conf_file() work on older windows too.
33516 - If we write a *:* exit policy line in the descriptor, don't write
33517 any more exit policy lines.
33520 - Use only 0.0.9pre1 and later servers for resolve cells.
33521 - Make the dirservers file obsolete.
33522 - Include a dir-signing-key token in directories to tell the
33523 parsing entity which key is being used to sign.
33524 - Remove the built-in bulky default dirservers string.
33525 - New config option "Dirserver %s:%d [fingerprint]", which can be
33526 repeated as many times as needed. If no dirservers specified,
33527 default to moria1,moria2,tor26.
33528 - Make moria2 advertise a dirport of 80, so people behind firewalls
33529 will be able to get a directory.
33530 - Http proxy support
33531 - Dirservers translate requests for http://%s:%d/x to /x
33532 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
33533 be routed through this host.
33534 - Clients ask for /tor/x rather than /x for new enough dirservers.
33535 This way we can one day coexist peacefully with apache.
33536 - Clients specify a "Host: %s%d" http header, to be compatible
33537 with more proxies, and so running squid on an exit node can work.
33540 Changes in version 0.0.8.1 - 2004-10-13
33542 - Fix a seg fault that can be triggered remotely for Tor
33543 clients/servers with an open dirport.
33544 - Fix a rare assert trigger, where routerinfos for entries in
33545 our cpath would expire while we're building the path.
33546 - Fix a bug in OutboundBindAddress so it (hopefully) works.
33547 - Fix a rare seg fault for people running hidden services on
33548 intermittent connections.
33549 - Fix a bug in parsing opt keywords with objects.
33550 - Fix a stale pointer assert bug when a stream detaches and
33552 - Fix a string format vulnerability (probably not exploitable)
33553 in reporting stats locally.
33554 - Fix an assert trigger: sometimes launching circuits can fail
33555 immediately, e.g. because too many circuits have failed recently.
33556 - Fix a compile warning on 64 bit platforms.
33559 Changes in version 0.0.9pre2 - 2004-10-03
33561 - Make fetching a cached directory work for 64-bit platforms too.
33562 - Make zlib.h a required header, not an optional header.
33565 Changes in version 0.0.9pre1 - 2004-10-01
33567 - Stop using separate defaults for no-config-file and
33568 empty-config-file. Now you have to explicitly turn off SocksPort,
33569 if you don't want it open.
33570 - Fix a bug in OutboundBindAddress so it (hopefully) works.
33571 - Improve man page to mention more of the 0.0.8 features.
33572 - Fix a rare seg fault for people running hidden services on
33573 intermittent connections.
33574 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
33576 - Fix more dns related bugs: send back resolve_failed and end cells
33577 more reliably when the resolve fails, rather than closing the
33578 circuit and then trying to send the cell. Also attach dummy resolve
33579 connections to a circuit *before* calling dns_resolve(), to fix
33580 a bug where cached answers would never be sent in RESOLVED cells.
33581 - When we run out of disk space, or other log writing error, don't
33582 crash. Just stop logging to that log and continue.
33583 - We were starting to daemonize before we opened our logs, so if
33584 there were any problems opening logs, we would complain to stderr,
33585 which wouldn't work, and then mysteriously exit.
33586 - Fix a rare bug where sometimes a verified OR would connect to us
33587 before he'd uploaded his descriptor, which would cause us to
33588 assign conn->nickname as though he's unverified. Now we look through
33589 the fingerprint list to see if he's there.
33590 - Fix a rare assert trigger, where routerinfos for entries in
33591 our cpath would expire while we're building the path.
33594 - Clients can ask dirservers for /dir.z to get a compressed version
33595 of the directory. Only works for servers running 0.0.9, of course.
33596 - Make clients cache directories and use them to seed their router
33597 lists at startup. This means clients have a datadir again.
33598 - Configuration infrastructure support for warning on obsolete
33600 - Respond to content-encoding headers by trying to uncompress as
33602 - Reply with a deflated directory when a client asks for "dir.z".
33603 We could use allow-encodings instead, but allow-encodings isn't
33604 specified in HTTP 1.0.
33605 - Raise the max dns workers from 50 to 100.
33606 - Discourage people from setting their dirfetchpostperiod more often
33607 than once per minute.
33608 - Protect dirservers from overzealous descriptor uploading -- wait
33609 10 seconds after directory gets dirty, before regenerating.
33612 Changes in version 0.0.8 - 2004-08-25
33613 o Port it to SunOS 5.9 / Athena
33616 Changes in version 0.0.8rc2 - 2004-08-20
33617 o Make it compile on cygwin again.
33618 o When picking unverified routers, skip those with low uptime and/or
33619 low bandwidth, depending on what properties you care about.
33622 Changes in version 0.0.8rc1 - 2004-08-18
33623 o Changes from 0.0.7.3:
33625 - Fix assert triggers: if the other side returns an address 0.0.0.0,
33626 don't put it into the client dns cache.
33627 - If a begin failed due to exit policy, but we believe the IP address
33628 should have been allowed, switch that router to exitpolicy reject *:*
33629 until we get our next directory.
33631 - Clients choose nodes proportional to advertised bandwidth.
33632 - Avoid using nodes with low uptime as introduction points.
33633 - Handle servers with dynamic IP addresses: don't replace
33634 options->Address with the resolved one at startup, and
33635 detect our address right before we make a routerinfo each time.
33636 - 'FascistFirewall' option to pick dirservers and ORs on specific
33637 ports; plus 'FirewallPorts' config option to tell FascistFirewall
33638 which ports are open. (Defaults to 80,443)
33639 - Be more aggressive about trying to make circuits when the network
33640 has changed (e.g. when you unsuspend your laptop).
33641 - Check for time skew on http headers; report date in response to
33643 - If the entrynode config line has only one node, don't pick it as
33645 - Add strict{entry|exit}nodes config options. If set to 1, then
33646 we refuse to build circuits that don't include the specified entry
33648 - OutboundBindAddress config option, to bind to a specific
33649 IP address for outgoing connect()s.
33650 - End truncated log entries (e.g. directories) with "[truncated]".
33652 o Patches to 0.0.8preX:
33654 - Patches to compile and run on win32 again (maybe)?
33655 - Fix crash when looking for ~/.torrc with no $HOME set.
33656 - Fix a race bug in the unit tests.
33657 - Handle verified/unverified name collisions better when new
33658 routerinfo's arrive in a directory.
33659 - Sometimes routers were getting entered into the stats before
33660 we'd assigned their identity_digest. Oops.
33661 - Only pick and establish intro points after we've gotten a
33664 - AllowUnverifiedNodes config option to let circuits choose no-name
33665 routers in entry,middle,exit,introduction,rendezvous positions.
33666 Allow middle and rendezvous positions by default.
33667 - Add a man page for tor-resolve.
33670 Changes in version 0.0.7.3 - 2004-08-12
33671 o Stop dnsworkers from triggering an assert failure when you
33672 ask them to resolve the host "".
33675 Changes in version 0.0.8pre3 - 2004-08-09
33676 o Changes from 0.0.7.2:
33677 - Allow multiple ORs with same nickname in routerlist -- now when
33678 people give us one identity key for a nickname, then later
33679 another, we don't constantly complain until the first expires.
33680 - Remember used bandwidth (both in and out), and publish 15-minute
33681 snapshots for the past day into our descriptor.
33682 - You can now fetch $DIRURL/running-routers to get just the
33683 running-routers line, not the whole descriptor list. (But
33684 clients don't use this yet.)
33685 - When people mistakenly use Tor as an http proxy, point them
33686 at the tor-doc.html rather than the INSTALL.
33687 - Remove our mostly unused -- and broken -- hex_encode()
33688 function. Use base16_encode() instead. (Thanks to Timo Lindfors
33689 for pointing out this bug.)
33690 - Rotate onion keys every 12 hours, not every 2 hours, so we have
33691 fewer problems with people using the wrong key.
33692 - Change the default exit policy to reject the default edonkey,
33693 kazaa, gnutella ports.
33694 - Add replace_file() to util.[ch] to handle win32's rename().
33696 o Changes from 0.0.8preX:
33697 - Fix two bugs in saving onion keys to disk when rotating, so
33698 hopefully we'll get fewer people using old onion keys.
33699 - Fix an assert error that was making SocksPolicy not work.
33700 - Be willing to expire routers that have an open dirport -- it's
33701 just the authoritative dirservers we want to not forget.
33702 - Reject tor-resolve requests for .onion addresses early, so we
33703 don't build a whole rendezvous circuit and then fail.
33704 - When you're warning a server that he's unverified, don't cry
33705 wolf unpredictably.
33706 - Fix a race condition: don't try to extend onto a connection
33707 that's still handshaking.
33708 - For servers in clique mode, require the conn to be open before
33709 you'll choose it for your path.
33710 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
33711 end relay cell, etc.
33712 - Measure bandwidth capacity over the last 24 hours, not just 12
33713 - Bugfix: authoritative dirservers were making and signing a new
33714 directory for each client, rather than reusing the cached one.
33717 Changes in version 0.0.8pre2 - 2004-08-04
33718 o Changes from 0.0.7.2:
33720 - Check directory signature _before_ you decide whether you're
33721 you're running an obsolete version and should exit.
33722 - Check directory signature _before_ you parse the running-routers
33723 list to decide who's running or verified.
33724 - Bugfixes and features:
33725 - Check return value of fclose while writing to disk, so we don't
33726 end up with broken files when servers run out of disk space.
33727 - Log a warning if the user uses an unsafe socks variant, so people
33728 are more likely to learn about privoxy or socat.
33729 - Dirservers now include RFC1123-style dates in the HTTP headers,
33730 which one day we will use to better detect clock skew.
33732 o Changes from 0.0.8pre1:
33733 - Make it compile without warnings again on win32.
33734 - Log a warning if you're running an unverified server, to let you
33735 know you might want to get it verified.
33736 - Only pick a default nickname if you plan to be a server.
33739 Changes in version 0.0.8pre1 - 2004-07-23
33741 - Made our unit tests compile again on OpenBSD 3.5, and tor
33742 itself compile again on OpenBSD on a sparc64.
33743 - We were neglecting milliseconds when logging on win32, so
33744 everything appeared to happen at the beginning of each second.
33746 o Protocol changes:
33747 - 'Extend' relay cell payloads now include the digest of the
33748 intended next hop's identity key. Now we can verify that we're
33749 extending to the right router, and also extend to routers we
33750 hadn't heard of before.
33753 - Tor nodes can now act as relays (with an advertised ORPort)
33754 without being manually verified by the dirserver operators.
33755 - Uploaded descriptors of unverified routers are now accepted
33756 by the dirservers, and included in the directory.
33757 - Verified routers are listed by nickname in the running-routers
33758 list; unverified routers are listed as "$<fingerprint>".
33759 - We now use hash-of-identity-key in most places rather than
33760 nickname or addr:port, for improved security/flexibility.
33761 - To avoid Sybil attacks, paths still use only verified servers.
33762 But now we have a chance to play around with hybrid approaches.
33763 - Nodes track bandwidth usage to estimate capacity (not used yet).
33764 - ClientOnly option for nodes that never want to become servers.
33765 - Directory caching.
33766 - "AuthoritativeDir 1" option for the official dirservers.
33767 - Now other nodes (clients and servers) will cache the latest
33768 directory they've pulled down.
33769 - They can enable their DirPort to serve it to others.
33770 - Clients will pull down a directory from any node with an open
33771 DirPort, and check the signature/timestamp correctly.
33772 - Authoritative dirservers now fetch directories from other
33773 authdirservers, to stay better synced.
33774 - Running-routers list tells who's down also, along with noting
33775 if they're verified (listed by nickname) or unverified (listed
33777 - Allow dirservers to serve running-router list separately.
33778 This isn't used yet.
33779 - ORs connect-on-demand to other ORs
33780 - If you get an extend cell to an OR you're not connected to,
33781 connect, handshake, and forward the create cell.
33782 - The authoritative dirservers stay connected to everybody,
33783 and everybody stays connected to 0.0.7 servers, but otherwise
33784 clients/servers expire unused connections after 5 minutes.
33785 - When servers get a sigint, they delay 30 seconds (refusing new
33786 connections) then exit. A second sigint causes immediate exit.
33787 - File and name management:
33788 - Look for .torrc if no CONFDIR "torrc" is found.
33789 - If no datadir is defined, then choose, make, and secure ~/.tor
33791 - If torrc not found, exitpolicy reject *:*.
33792 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
33793 - If no nickname is defined, derive default from hostname.
33794 - Rename secret key files, e.g. identity.key -> secret_id_key,
33795 to discourage people from mailing their identity key to tor-ops.
33796 - Refuse to build a circuit before the directory has arrived --
33797 it won't work anyway, since you won't know the right onion keys
33799 - Try other dirservers immediately if the one you try is down. This
33800 should tolerate down dirservers better now.
33801 - Parse tor version numbers so we can do an is-newer-than check
33802 rather than an is-in-the-list check.
33803 - New socks command 'resolve', to let us shim gethostbyname()
33805 - A 'tor_resolve' script to access the socks resolve functionality.
33806 - A new socks-extensions.txt doc file to describe our
33807 interpretation and extensions to the socks protocols.
33808 - Add a ContactInfo option, which gets published in descriptor.
33809 - Publish OR uptime in descriptor (and thus in directory) too.
33810 - Write tor version at the top of each log file
33811 - New docs in the tarball:
33813 - Document that you should proxy your SSL traffic too.
33816 Changes in version 0.0.7.2 - 2004-07-07
33817 o A better fix for the 0.0.0.0 problem, that will hopefully
33818 eliminate the remaining related assertion failures.
33821 Changes in version 0.0.7.1 - 2004-07-04
33822 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
33823 since internally we use 0.0.0.0 to signify "not yet resolved".
33826 Changes in version 0.0.7 - 2004-06-07
33827 o Updated the man page to reflect the new features.
33830 Changes in version 0.0.7rc2 - 2004-06-06
33831 o Changes from 0.0.7rc1:
33832 - Make it build on Win32 again.
33833 o Changes from 0.0.6.2:
33834 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
33838 Changes in version 0.0.7rc1 - 2004-06-02
33840 - On sighup, we were adding another log without removing the first
33841 one. So log messages would get duplicated n times for n sighups.
33842 - Several cases of using a connection after we'd freed it. The
33843 problem was that connections that are pending resolve are in both
33844 the pending_resolve tree, and also the circuit's resolving_streams
33845 list. When you want to remove one, you must remove it from both.
33846 - Fix a double-mark-for-close where an end cell arrived for a
33847 resolving stream, and then the resolve failed.
33848 - Check directory signatures based on name of signer, not on whom
33849 we got the directory from. This will let us cache directories more
33852 - Crank up some of our constants to handle more users.
33855 Changes in version 0.0.7pre1 - 2004-06-02
33856 o Fixes for crashes and other obnoxious bugs:
33857 - Fix an epipe bug: sometimes when directory connections failed
33858 to connect, we would give them a chance to flush before closing
33860 - When we detached from a circuit because of resolvefailed, we
33861 would immediately try the same circuit twice more, and then
33862 give up on the resolve thinking we'd tried three different
33864 - Limit the number of intro circuits we'll attempt to build for a
33865 hidden service per 15-minute period.
33866 - Check recommended-software string *early*, before actually parsing
33867 the directory. Thus we can detect an obsolete version and exit,
33868 even if the new directory format doesn't parse.
33869 o Fixes for security bugs:
33870 - Remember which nodes are dirservers when you startup, and if a
33871 random OR enables his dirport, don't automatically assume he's
33872 a trusted dirserver.
33874 - Directory connections were asking the wrong poll socket to
33875 start writing, and not asking themselves to start writing.
33876 - When we detached from a circuit because we sent a begin but
33877 didn't get a connected, we would use it again the first time;
33878 but after that we would correctly switch to a different one.
33879 - Stop warning when the first onion decrypt attempt fails; they
33880 will sometimes legitimately fail now that we rotate keys.
33881 - Override unaligned-access-ok check when $host_cpu is ia64 or
33882 arm. Apparently they allow it but the kernel whines.
33883 - Dirservers try to reconnect periodically too, in case connections
33885 - Fix some memory leaks in directory servers.
33886 - Allow backslash in Win32 filenames.
33887 - Made Tor build complain-free on FreeBSD, hopefully without
33888 breaking other BSD builds. We'll see.
33890 - Doxygen markup on all functions and global variables.
33891 - Make directory functions update routerlist, not replace it. So
33892 now directory disagreements are not so critical a problem.
33893 - Remove the upper limit on number of descriptors in a dirserver's
33894 directory (not that we were anywhere close).
33895 - Allow multiple logfiles at different severity ranges.
33896 - Allow *BindAddress to specify ":port" rather than setting *Port
33897 separately. Allow multiple instances of each BindAddress config
33898 option, so you can bind to multiple interfaces if you want.
33899 - Allow multiple exit policy lines, which are processed in order.
33900 Now we don't need that huge line with all the commas in it.
33901 - Enable accept/reject policies on SOCKS connections, so you can bind
33902 to 0.0.0.0 but still control who can use your OP.
33905 Changes in version 0.0.6.2 - 2004-05-16
33906 o Our integrity-checking digest was checking only the most recent cell,
33907 not the previous cells like we'd thought.
33908 Thanks to Stefan Mark for finding the flaw!
33911 Changes in version 0.0.6.1 - 2004-05-06
33912 o Fix two bugs in our AES counter-mode implementation (this affected
33913 onion-level stream encryption, but not TLS-level). It turns
33914 out we were doing something much more akin to a 16-character
33915 polyalphabetic cipher. Oops.
33916 Thanks to Stefan Mark for finding the flaw!
33917 o Retire moria3 as a directory server, and add tor26 as a directory
33921 Changes in version 0.0.6 - 2004-05-02
33922 [version bump only]
33925 Changes in version 0.0.6rc4 - 2004-05-01
33926 o Update the built-in dirservers list to use the new directory format
33927 o Fix a rare seg fault: if a node offering a hidden service attempts
33928 to build a circuit to Alice's rendezvous point and fails before it
33929 reaches the last hop, it retries with a different circuit, but
33931 o Handle windows socket errors correctly.
33934 Changes in version 0.0.6rc3 - 2004-04-28
33935 o Don't expire non-general excess circuits (if we had enough
33936 circuits open, we were expiring rendezvous circuits -- even
33937 when they had a stream attached. oops.)
33938 o Fetch randomness from /dev/urandom better (not via fopen/fread)
33939 o Better debugging for tls errors
33940 o Some versions of openssl have an SSL_pending function that erroneously
33941 returns bytes when there is a non-application record pending.
33942 o Set Content-Type on the directory and hidserv descriptor.
33943 o Remove IVs from cipher code, since AES-ctr has none.
33944 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
33945 o We were using an array of length zero in a few places.
33946 o win32's gethostbyname can't resolve an IP to an IP.
33947 o win32's close can't close a socket.
33950 Changes in version 0.0.6rc2 - 2004-04-26
33951 o Fix a bug where we were closing tls connections intermittently.
33952 It turns out openssl keeps its errors around -- so if an error
33953 happens, and you don't ask about it, and then another openssl
33954 operation happens and succeeds, and you ask if there was an error,
33955 it tells you about the first error. Fun fun.
33956 o Fix a bug that's been lurking since 27 may 03 (!)
33957 When passing back a destroy cell, we would use the wrong circ id.
33958 'Mostly harmless', but still worth fixing.
33959 o Since we don't support truncateds much, don't bother sending them;
33960 just close the circ.
33961 o check for <machine/limits.h> so we build on NetBSD again (I hope).
33962 o don't crash if a conn that sent a begin has suddenly lost its circuit
33963 (this was quite rare).
33966 Changes in version 0.0.6rc1 - 2004-04-25
33967 o We now rotate link (tls context) keys and onion keys.
33968 o CREATE cells now include oaep padding, so you can tell
33969 if you decrypted them correctly.
33970 o Add bandwidthburst to server descriptor.
33971 o Directories now say which dirserver signed them.
33972 o Use a tor_assert macro that logs failed assertions too.
33975 Changes in version 0.0.6pre5 - 2004-04-18
33976 o changes from 0.0.6pre4:
33977 - make tor build on broken freebsd 5.2 installs
33978 - fix a failed assert when you try an intro point, get a nack, and try
33979 a second one and it works.
33980 - when alice uses a port that the hidden service doesn't accept,
33981 it now sends back an end cell (denied by exit policy). otherwise
33982 alice would just have to wait to time out.
33983 - fix another rare bug: when we had tried all the intro
33984 points for a hidden service, we fetched the descriptor
33985 again, but we left our introcirc thinking it had already
33986 sent an intro, so it kept waiting for a response...
33987 - bugfix: when you sleep your hidden-service laptop, as soon
33988 as it wakes up it tries to upload a service descriptor, but
33989 socketpair fails for some reason (localhost not up yet?).
33990 now we simply give up on that upload, and we'll try again later.
33991 i'd still like to find the bug though.
33992 - if an intro circ waiting for an ack dies before getting one, then
33994 - we were reusing stale service descriptors and refetching usable
33998 Changes in version 0.0.6pre4 - 2004-04-14
33999 o changes from 0.0.6pre3:
34000 - when bob fails to connect to the rendezvous point, and his
34001 circ didn't fail because of the rendezvous point itself, then
34002 he retries a couple of times
34003 - we expire introduction and rendezvous circs more thoroughly
34004 (sometimes they were hanging around forever)
34005 - we expire unattached rendezvous streams that have been around
34006 too long (they were sticking around forever).
34007 - fix a measly fencepost error that was crashing everybody with
34011 Changes in version 0.0.6pre3 - 2004-04-14
34012 o changes from 0.0.6pre2:
34013 - make hup work again
34014 - fix some memory leaks for dirservers
34015 - allow more skew in rendezvous descriptor timestamps, to help
34016 handle people like blanu who don't know what time it is
34017 - normal circs are 3 hops, but some rend/intro circs are 4, if
34018 the initiator doesn't get to choose the last hop
34019 - send acks for introductions, so alice can know whether to try
34021 - bob publishes intro points more correctly
34022 o changes from 0.0.5:
34023 - fix an assert trigger that's been plaguing us since the days
34024 of 0.0.2prexx (thanks weasel!)
34025 - retry stream correctly when we fail to connect because of
34026 exit-policy-reject (should try another) or can't-resolve-address
34027 (also should try another, because dns on random internet servers
34029 - when we hup a dirserver and we've *removed* a server from the
34030 approved-routers list, now we remove that server from the
34031 in-memory directories too
34034 Changes in version 0.0.6pre2 - 2004-04-08
34035 o We fixed our base32 implementation. Now it works on all architectures.
34038 Changes in version 0.0.6pre1 - 2004-04-08
34040 - Hidden services and rendezvous points are implemented. Go to
34041 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
34042 hidden services. (This only works via a socks4a proxy such as
34043 Privoxy, and currently it's quite slow.)
34046 Changes in version 0.0.5 - 2004-03-30
34047 [version bump only]
34050 Changes in version 0.0.5rc3 - 2004-03-29
34051 o Install torrc as torrc.sample -- we no longer clobber your
34053 o Re-enable recommendedversion checking (we broke it in rc2, oops)
34054 o Add in a 'notice' log level for things the operator should hear
34055 but that aren't warnings
34058 Changes in version 0.0.5rc2 - 2004-03-29
34059 o Hold socks connection open until reply is flushed (if possible)
34060 o Make exit nodes resolve IPs to IPs immediately, rather than asking
34061 the dns farm to do it.
34062 o Fix c99 aliasing warnings in rephist.c
34063 o Don't include server descriptors that are older than 24 hours in the
34065 o Give socks 'reject' replies their whole 15s to attempt to flush,
34066 rather than seeing the 60s timeout and assuming the flush had failed.
34067 o Clean automake droppings from the cvs repository
34070 Changes in version 0.0.5rc1 - 2004-03-28
34071 o Fix mangled-state bug in directory fetching (was causing sigpipes).
34072 o Only build circuits after we've fetched the directory: clients were
34073 using only the directory servers before they'd fetched a directory.
34074 This also means longer startup time; so it goes.
34075 o Fix an assert trigger where an OP would fail to handshake, and we'd
34076 expect it to have a nickname.
34077 o Work around a tsocks bug: do a socks reject when AP connection dies
34078 early, else tsocks goes into an infinite loop.
34081 Changes in version 0.0.4 - 2004-03-26
34082 o When connecting to a dirserver or OR and the network is down,
34086 Changes in version 0.0.3 - 2004-03-26
34087 o Warn and fail if server chose a nickname with illegal characters
34088 o Port to Solaris and Sparc:
34089 - include missing header fcntl.h
34090 - have autoconf find -lsocket -lnsl automatically
34091 - deal with hardware word alignment
34092 - make uname() work (solaris has a different return convention)
34093 - switch from using signal() to sigaction()
34094 o Preliminary work on reputation system:
34095 - Keep statistics on success/fail of connect attempts; they're published
34096 by kill -USR1 currently.
34097 - Add a RunTesting option to try to learn link state by creating test
34098 circuits, even when SocksPort is off.
34099 - Remove unused open circuits when there are too many.
34102 Changes in version 0.0.2 - 2004-03-19
34103 - Include strlcpy and strlcat for safer string ops
34104 - define INADDR_NONE so we compile (but still not run) on solaris
34107 Changes in version 0.0.2pre27 - 2004-03-14
34109 - Allow internal tor networks (we were rejecting internal IPs,
34110 now we allow them if they're set explicitly).
34111 - And fix a few endian issues.
34114 Changes in version 0.0.2pre26 - 2004-03-14
34116 - If a stream times out after 15s without a connected cell, don't
34117 try that circuit again: try a new one.
34118 - Retry streams at most 4 times. Then give up.
34119 - When a dirserver gets a descriptor from an unknown router, it
34120 logs its fingerprint (so the dirserver operator can choose to
34121 accept it even without mail from the server operator).
34122 - Inform unapproved servers when we reject their descriptors.
34123 - Make tor build on Windows again. It works as a client, who knows
34125 - Clearer instructions in the torrc for how to set up a server.
34126 - Be more efficient about reading fd's when our global token bucket
34127 (used for rate limiting) becomes empty.
34129 - Stop asserting that computers always go forward in time. It's
34131 - When we sent a cell (e.g. destroy) and then marked an OR connection
34132 expired, we might close it before finishing a flush if the other
34133 side isn't reading right then.
34134 - Don't allow dirservers to start if they haven't defined
34135 RecommendedVersions
34136 - We were caching transient dns failures. Oops.
34137 - Prevent servers from publishing an internal IP as their address.
34138 - Address a strcat vulnerability in circuit.c
34141 Changes in version 0.0.2pre25 - 2004-03-04
34143 - Put the OR's IP in its router descriptor, not its fqdn. That way
34144 we'll stop being stalled by gethostbyname for nodes with flaky dns,
34147 - If the user typed in an address that didn't resolve, the server
34151 Changes in version 0.0.2pre24 - 2004-03-03
34153 - Fix an assertion failure in dns.c, where we were trying to dequeue
34154 a pending dns resolve even if it wasn't pending
34155 - Fix a spurious socks5 warning about still trying to write after the
34156 connection is finished.
34157 - Hold certain marked_for_close connections open until they're finished
34158 flushing, rather than losing bytes by closing them too early.
34159 - Correctly report the reason for ending a stream
34160 - Remove some duplicate calls to connection_mark_for_close
34161 - Put switch_id and start_daemon earlier in the boot sequence, so it
34162 will actually try to chdir() to options.DataDirectory
34163 - Make 'make test' exit(1) if a test fails; fix some unit tests
34164 - Make tor fail when you use a config option it doesn't know about,
34165 rather than warn and continue.
34166 - Make --version work
34167 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
34170 Changes in version 0.0.2pre23 - 2004-02-29
34172 - Print a statement when the first circ is finished, so the user
34173 knows it's working.
34174 - If a relay cell is unrecognized at the end of the circuit,
34175 send back a destroy. (So attacks to mutate cells are more
34177 - New config option 'excludenodes' to avoid certain nodes for circuits.
34178 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
34179 so you can collect coredumps there.
34181 - Fix a bug in tls flushing where sometimes data got wedged and
34182 didn't flush until more data got sent. Hopefully this bug was
34183 a big factor in the random delays we were seeing.
34184 - Make 'connected' cells include the resolved IP, so the client
34185 dns cache actually gets populated.
34186 - Disallow changing from ORPort=0 to ORPort>0 on hup.
34187 - When we time-out on a stream and detach from the circuit, send an
34188 end cell down it first.
34189 - Only warn about an unknown router (in exitnodes, entrynodes,
34190 excludenodes) after we've fetched a directory.
34193 Changes in version 0.0.2pre22 - 2004-02-26
34195 - Servers publish less revealing uname information in descriptors.
34196 - More memory tracking and assertions, to crash more usefully when
34198 - If the default torrc isn't there, just use some default defaults.
34199 Plus provide an internal dirservers file if they don't have one.
34200 - When the user tries to use Tor as an http proxy, give them an http
34201 501 failure explaining that we're a socks proxy.
34202 - Dump a new router.desc on hup, to help confused people who change
34203 their exit policies and then wonder why router.desc doesn't reflect
34205 - Clean up the generic tor.sh init script that we ship with.
34207 - If the exit stream is pending on the resolve, and a destroy arrives,
34208 then the stream wasn't getting removed from the pending list. I
34209 think this was the one causing recent server crashes.
34210 - Use a more robust poll on OSX 10.3, since their poll is flaky.
34211 - When it couldn't resolve any dirservers, it was useless from then on.
34212 Now it reloads the RouterFile (or default dirservers) if it has no
34214 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
34215 many users don't even *have* a /usr/local/sbin/.
34218 Changes in version 0.0.2pre21 - 2004-02-18
34220 - There's a ChangeLog file that actually reflects the changelog.
34221 - There's a 'torify' wrapper script, with an accompanying
34222 tor-tsocks.conf, that simplifies the process of using tsocks for
34223 tor. It even has a man page.
34224 - The tor binary gets installed to sbin rather than bin now.
34225 - Retry streams where the connected cell hasn't arrived in 15 seconds
34226 - Clean up exit policy handling -- get the default out of the torrc,
34227 so we can update it without forcing each server operator to fix
34229 - Allow imaps and pop3s in default exit policy
34231 - Prevent picking middleman nodes as the last node in the circuit
34234 Changes in version 0.0.2pre20 - 2004-01-30
34236 - We now have a deb package, and it's in debian unstable. Go to
34237 it, apt-getters. :)
34238 - I've split the TotalBandwidth option into BandwidthRate (how many
34239 bytes per second you want to allow, long-term) and
34240 BandwidthBurst (how many bytes you will allow at once before the cap
34241 kicks in). This better token bucket approach lets you, say, set
34242 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
34243 performance while not exceeding your monthly bandwidth quota.
34244 - Push out a tls record's worth of data once you've got it, rather
34245 than waiting until you've read everything waiting to be read. This
34246 may improve performance by pipelining better. We'll see.
34247 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
34248 from failed circuits (if they haven't been connected yet) and attach
34250 - Expire old streams that haven't managed to connect. Some day we'll
34251 have them reattach to new circuits instead.
34254 - Fix several memory leaks that were causing servers to become bloated
34256 - Fix a few very rare assert triggers. A few more remain.
34257 - Setuid to User _before_ complaining about running as root.
34260 Changes in version 0.0.2pre19 - 2004-01-07
34262 - Fix deadlock condition in dns farm. We were telling a child to die by
34263 closing the parent's file descriptor to him. But newer children were
34264 inheriting the open file descriptor from the parent, and since they
34265 weren't closing it, the socket never closed, so the child never read
34266 eof, so he never knew to exit. Similarly, dns workers were holding
34267 open other sockets, leading to all sorts of chaos.
34268 - New cleaner daemon() code for forking and backgrounding.
34269 - If you log to a file, it now prints an entry at the top of the
34270 logfile so you know it's working.
34271 - The onionskin challenge length was 30 bytes longer than necessary.
34272 - Started to patch up the spec so it's not quite so out of date.
34275 Changes in version 0.0.2pre18 - 2004-01-02
34277 - Fix endian issues with the 'integrity' field in the relay header.
34278 - Fix a potential bug where connections in state
34279 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
34282 Changes in version 0.0.2pre17 - 2003-12-30
34284 - Made --debuglogfile (or any second log file, actually) work.
34285 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
34286 adversary could force us into an infinite loop.
34289 - Each onionskin handshake now includes a hash of the computed key,
34290 to prove the server's identity and help perfect forward secrecy.
34291 - Changed cell size from 256 to 512 bytes (working toward compatibility
34293 - Changed cell length to 2 bytes, and moved it to the relay header.
34294 - Implemented end-to-end integrity checking for the payloads of
34296 - Separated streamid from 'recognized' (otherwise circuits will get
34297 messed up when we try to have streams exit from the middle). We
34298 use the integrity-checking to confirm that a cell is addressed to
34300 - Randomize the initial circid and streamid values, so an adversary who
34301 breaks into a node can't learn how many circuits or streams have
34305 Changes in version 0.0.2pre16 - 2003-12-14
34307 - Fixed a bug that made HUP trigger an assert
34308 - Fixed a bug where a circuit that immediately failed wasn't being
34309 counted as a failed circuit in counting retries.
34312 - Now we close the circuit when we get a truncated cell: otherwise we're
34313 open to an anonymity attack where a bad node in the path truncates
34314 the circuit and then we open streams at him.
34315 - Add port ranges to exit policies
34316 - Add a conservative default exit policy
34317 - Warn if you're running tor as root
34318 - on HUP, retry OR connections and close/rebind listeners
34319 - options.EntryNodes: try these nodes first when picking the first node
34320 - options.ExitNodes: if your best choices happen to include any of
34321 your preferred exit nodes, you choose among just those preferred
34323 - options.ExcludedNodes: nodes that are never picked in path building
34326 Changes in version 0.0.2pre15 - 2003-12-03
34327 o Robustness and bugfixes:
34328 - Sometimes clients would cache incorrect DNS resolves, which would
34329 really screw things up.
34330 - An OP that goes offline would slowly leak all its sockets and stop
34332 - A wide variety of bugfixes in exit node selection, exit policy
34333 handling, and processing pending streams when a new circuit is
34335 - Pick nodes for a path only from those the directory says are up
34336 - Choose randomly from all running dirservers, not always the first one
34337 - Increase allowed http header size for directory fetch.
34338 - Stop writing to stderr (if we're daemonized it will be closed).
34339 - Enable -g always, so cores will be more useful to me.
34340 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
34343 - Wrote a man page. It lists commonly used options.
34346 - Change default loglevel to warn.
34347 - Make PidFile default to null rather than littering in your CWD.
34348 - OnionRouter config option is now obsolete. Instead it just checks
34350 - Moved to a single unified torrc file for both clients and servers.
34353 Changes in version 0.0.2pre14 - 2003-11-29
34354 o Robustness and bugfixes:
34355 - Force the admin to make the DataDirectory himself
34356 - to get ownership/permissions right
34357 - so clients no longer make a DataDirectory and then never use it
34358 - fix bug where a client who was offline for 45 minutes would never
34359 pull down a directory again
34360 - fix (or at least hide really well) the dns assert bug that was
34361 causing server crashes
34362 - warnings and improved robustness wrt clockskew for certs
34363 - use the native daemon(3) to daemonize, when available
34364 - exit if bind() fails
34365 - exit if neither socksport nor orport is defined
34366 - include our own tor_timegm (Win32 doesn't have its own)
34367 - bugfix for win32 with lots of connections
34368 - fix minor bias in PRNG
34369 - make dirserver more robust to corrupt cached directory
34372 - Wrote the design document (woo)
34374 o Circuit building and exit policies:
34375 - Circuits no longer try to use nodes that the directory has told them
34377 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
34378 bitcounts (18.0.0.0/8).
34379 - Make AP connections standby for a circuit if no suitable circuit
34380 exists, rather than failing
34381 - Circuits choose exit node based on addr/port, exit policies, and
34382 which AP connections are standing by
34383 - Bump min pathlen from 2 to 3
34384 - Relay end cells have a payload to describe why the stream ended.
34385 - If the stream failed because of exit policy, try again with a new
34387 - Clients have a dns cache to remember resolved addresses.
34388 - Notice more quickly when we have no working circuits
34391 - APPort is now called SocksPort
34392 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
34394 - RecommendedVersions is now a config variable rather than
34395 hardcoded (for dirservers)
34396 - Reloads config on HUP
34397 - Usage info on -h or --help
34398 - If you set User and Group config vars, it'll setu/gid to them.
34401 Changes in version 0.0.2pre13 - 2003-10-19
34402 o General stability:
34403 - SSL_write no longer fails when it returns WANTWRITE and the number
34404 of bytes in the buf has changed by the next SSL_write call.
34405 - Fix segfault fetching directory when network is down
34406 - Fix a variety of minor memory leaks
34407 - Dirservers reload the fingerprints file on HUP, so I don't have
34408 to take down the network when I approve a new router
34409 - Default server config file has explicit Address line to specify fqdn
34412 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
34413 - Make listener connections not ever alloc bufs
34415 o Autoconf improvements:
34416 - don't clobber an external CFLAGS in ./configure
34417 - Make install now works
34418 - create var/lib/tor on make install
34419 - autocreate a tor.sh initscript to help distribs
34420 - autocreate the torrc and sample-server-torrc with correct paths
34422 o Log files and Daemonizing now work:
34423 - If --DebugLogFile is specified, log to it at -l debug
34424 - If --LogFile is specified, use it instead of commandline
34425 - If --RunAsDaemon is set, tor forks and backgrounds on startup