1 Changes in version 0.4.5.2-alpha - 2020-11-23
2 Tor 0.4.5.2-alpha is the second alpha release in the 0.4.5.x series.
3 It fixes several bugs present in earlier releases, including one that
4 made it impractical to run relays on Windows. It also adds a few small
5 safety features to improve Tor's behavior in the presence of strange
6 compile-time options, misbehaving proxies, and future versions
9 o Major bugfixes (relay, windows):
10 - Fix a bug in our implementation of condition variables on Windows.
11 Previously, a relay on Windows would use 100% CPU after running
12 for some time. Because of this change, Tor now require Windows
13 Vista or later to build and run. Fixes bug 30187; bugfix on
14 0.2.6.3-alpha. (This bug became more serious in 0.3.1.1-alpha with
15 the introduction of consensus diffs.) Patch by Daniel Pinto.
17 o Minor features (compilation):
18 - Disable deprecation warnings when building with OpenSSL 3.0.0 or
19 later. There are a number of APIs newly deprecated in OpenSSL
20 3.0.0 that Tor still requires. (A later version of Tor will try to
21 stop depending on these APIs.) Closes ticket 40165.
23 o Minor features (protocol, proxy support, defense in depth):
24 - Respond more deliberately to misbehaving proxies that leave
25 leftover data on their connections, so as to make Tor even less
26 likely to allow the proxies to pass their data off as having come
27 from a relay. Closes ticket 40017.
29 o Minor features (safety):
30 - Log a warning at startup if Tor is built with compile-time options
31 that are likely to make it less stable or reliable. Closes
34 o Minor bugfixes (circuit, handshake):
35 - In the v3 handshaking code, use connection_or_change_state() to
36 change the state. Previously, we changed the state directly, but
37 this did not pass the state change to the pubsub or channel
38 objects, potentially leading to bugs. Fixes bug 32880; bugfix on
39 0.2.3.6-alpha. Patch by Neel Chauhan.
41 o Minor bugfixes (compilation):
42 - Use the correct 'ranlib' program when building libtor.a.
43 Previously we used the default ranlib, which broke some kinds of
44 cross-compilation. Fixes bug 40172; bugfix on 0.4.5.1-alpha.
45 - Remove a duplicate typedef in metrics_store.c. Fixes bug 40177;
46 bugfix on 0.4.5.1-alpha.
47 - When USDT tracing is enabled, and STAP_PROBEV() is missing, don't
48 attempt to build. Linux supports that macro but not the BSDs.
49 Fixes bug 40174; bugfix on 0.4.5.1-alpha.
51 o Minor bugfixes (configuration):
52 - Exit Tor on a misconfiguration when the Bridge line is configured
53 to use a transport but no corresponding ClientTransportPlugin can
54 be found. Prior to this fix, Tor would attempt to connect to the
55 bridge directly without using the transport, making it easier for
56 adversaries to notice the bridge. Fixes bug 25528; bugfix
58 - Fix an issue where an ORPort was compared with other kinds of
59 ports, when it should have been only checked against other
60 ORPorts. This bug would lead to "DirPort auto" getting ignored.
61 Fixes bug 40195; bugfix on 0.4.5.1-alpha.
62 - Fix a bug where a second non-ORPort with a variant family (ex:
63 SocksPort [::1]:9050) would be ignored due to a configuration
64 parsing error. Fixes bug 40183; bugfix on 0.4.5.1-alpha.
66 o Minor bugfixes (crash, relay, signing key):
67 - Avoid assertion failures when we run Tor from the command line
68 with `--key-expiration sign`, but an ORPort is not set. Fixes bug
69 40015; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
71 o Minor bugfixes (logging):
72 - Remove trailing whitespace from control event log messages. Fixes
73 bug 32178; bugfix on 0.1.1.1-alpha. Based on a patch by
75 - Turn warning-level log message about SENDME failure into a debug-
76 level message. (This event can happen naturally, and is no reason
77 for concern). Fixes bug 40142; bugfix on 0.4.1.1-alpha.
79 o Minor bugfixes (relay, address discovery):
80 - Don't trigger an IP change when no new valid IP can be found.
81 Fixes bug 40071; bugfix on 0.4.5.1-alpha.
82 - When attempting to discover our IP, use a simple test circuit,
83 rather than a descriptor fetch: the same address information is
84 present in NETINFO cells, and is better authenticated there. Fixes
85 bug 40071; bugfix on 0.4.5.1-alpha.
87 o Minor bugfixes (testing):
88 - Fix the `config/parse_tcp_proxy_line` test so that it works
89 correctly on systems where the DNS provider hijacks invalid
90 queries. Fixes part of bug 40179; bugfix on 0.4.3.1-alpha.
91 - Fix unit tests that used newly generated list of routers so that
92 they check them with respect to the date when they were generated,
93 not with respect to the current time. Fixes bug 40187; bugfix
95 - Fix our Python reference-implementation for the v3 onion service
96 handshake so that it works correctly with the version of hashlib
97 provided by Python 3.9. Fixes part of bug 40179; bugfix
99 - Fix the `tortls/openssl/log_one_error` test to work with OpenSSL
100 3.0.0. Fixes bug 40170; bugfix on 0.2.8.1-alpha.
102 o Removed features (controller):
103 - Remove the "GETINFO network-status" controller command. It has
104 been deprecated since 0.3.1.1-alpha. Closes ticket 22473.
107 Changes in version 0.4.4.6 - 2020-11-12
108 Tor 0.4.4.6 is the second stable release in the 0.4.4.x series. It
109 backports fixes from later releases, including a fix for TROVE-2020-
110 005, a security issue that could be used, under certain cases, by an
111 adversary to observe traffic patterns on a limited number of circuits
112 intended for a different relay.
114 o Major bugfixes (security, backport from 0.4.5.1-alpha):
115 - When completing a channel, relays now check more thoroughly to
116 make sure that it matches any pending circuits before attaching
117 those circuits. Previously, address correctness and Ed25519
118 identities were not checked in this case, but only when extending
119 circuits on an existing channel. Fixes bug 40080; bugfix on
120 0.2.7.2-alpha. Resolves TROVE-2020-005.
122 o Minor features (directory authorities, backport from 0.4.5.1-alpha):
123 - Authorities now list a different set of protocols as required and
124 recommended. These lists have been chosen so that only truly
125 recommended and/or required protocols are included, and so that
126 clients using 0.2.9 or later will continue to work (even though
127 they are not supported), whereas only relays running 0.3.5 or
128 later will meet the requirements. Closes ticket 40162.
129 - Make it possible to specify multiple ConsensusParams torrc lines.
130 Now directory authority operators can for example put the main
131 ConsensusParams config in one torrc file and then add to it from a
132 different torrc file. Closes ticket 40164.
134 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
135 - Tor no longer allows subprotocol versions larger than 63.
136 Previously version numbers up to UINT32_MAX were allowed, which
137 significantly complicated our code. Implements proposal 318;
140 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
141 - Fix a rendezvous cache unit test that was triggering an underflow
142 on the global rend cache allocation. Fixes bug 40125; bugfix
144 - Fix another rendezvous cache unit test that was triggering an
145 underflow on the global rend cache allocation. Fixes bug 40126;
146 bugfix on 0.2.8.1-alpha.
148 o Minor bugfixes (compilation, backport from 0.4.5.1-alpha):
149 - Fix compiler warnings that would occur when building with
150 "--enable-all-bugs-are-fatal" and "--disable-module-relay" at the
151 same time. Fixes bug 40129; bugfix on 0.4.4.1-alpha.
152 - Resolve a compilation warning that could occur in
153 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
155 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
156 - Remove a debug logging statement that uselessly spammed the logs.
157 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
159 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
160 - Avoid a fatal assert() when failing to create a listener
161 connection for an address that was in use. Fixes bug 40073; bugfix
164 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
165 - For HSFETCH commands on v2 onion services addresses, check the
166 length of bytes decoded, not the base32 length. Fixes bug 34400;
167 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
170 Changes in version 0.4.3.7 - 2020-11-12
171 Tor 0.4.3.7 backports several bugfixes from later releases. It
172 includes a fix for TROVE-2020-005, a security issue that could be
173 used, under certain cases, by an adversary to observe traffic patterns
174 on a limited number of circuits intended for a different relay.
176 Please be aware that support for the 0.4.3.x series will end on 15
177 February 2021. Please upgrade to 0.4.4.x or 0.4.5.x before then, or
178 downgrade to 0.3.5.x, which will be supported until at least 1
181 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
182 - Replace the 148 fallback directories originally included in Tor
183 0.4.1.4-rc (of which around 105 are still functional) with a list
184 of 144 fallbacks generated in July 2020. Closes ticket 40061.
186 o Major bugfixes (security, backport from 0.4.5.1-alpha):
187 - When completing a channel, relays now check more thoroughly to
188 make sure that it matches any pending circuits before attaching
189 those circuits. Previously, address correctness and Ed25519
190 identities were not checked in this case, but only when extending
191 circuits on an existing channel. Fixes bug 40080; bugfix on
192 0.2.7.2-alpha. Resolves TROVE-2020-005.
194 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
195 - When running with NSS enabled, make sure that NSS knows to expect
196 nonblocking sockets. Previously, we set our TCP sockets as
197 nonblocking, but did not tell NSS, which in turn could lead to
198 unexpected blocking behavior. Fixes bug 40035; bugfix
201 o Minor features (security, backport from 0.4.4.4-rc):
202 - Channels using obsolete versions of the Tor link protocol are no
203 longer allowed to circumvent address-canonicity checks. (This is
204 only a minor issue, since such channels have no way to set ed25519
205 keys, and therefore should always be rejected for circuits that
206 specify ed25519 identities.) Closes ticket 40081.
208 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
209 - Tor no longer allows subprotocol versions larger than 63.
210 Previously version numbers up to UINT32_MAX were allowed, which
211 significantly complicated our code. Implements proposal 318;
214 o Minor features (tests, backport from 0.4.4.5):
215 - Our "make check" target now runs the unit tests in 8 parallel
216 chunks. Doing this speeds up hardened CI builds by more than a
217 factor of two. Closes ticket 40098.
219 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
220 - Fix a rendezvous cache unit test that was triggering an underflow
221 on the global rend cache allocation. Fixes bug 40125; bugfix
223 - Fix another rendezvous cache unit test that was triggering an
224 underflow on the global rend cache allocation. Fixes bug 40126;
225 bugfix on 0.2.8.1-alpha.
227 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
228 - Fix a correctness bug that could cause an assertion failure if we
229 ever tried using the buf_move_all() function with an empty input
230 buffer. As far as we know, no released versions of Tor do this.
231 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
233 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
234 - Remove a debug logging statement that uselessly spammed the logs.
235 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
237 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
238 - On a bridge, treat all connections from an ExtORPort as remote by
239 default for the purposes of rate-limiting. Previously, bridges
240 would treat the connection as local unless they explicitly
241 received a "USERADDR" command. ExtORPort connections still count
242 as local if there is a USERADDR command with an explicit local
243 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
245 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
246 - Avoid a fatal assert() when failing to create a listener
247 connection for an address that was in use. Fixes bug 40073; bugfix
250 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
251 - Adjust the rules for when to warn about having too many
252 connections to other relays. Previously we'd tolerate up to 1.5
253 connections per relay on average. Now we tolerate more connections
254 for directory authorities, and raise the number of total
255 connections we need to see before we warn. Fixes bug 33880; bugfix
258 o Minor bugfixes (tests, 0.4.4.5):
259 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
260 on its own. Previously, it would exit with an error. Fixes bug
261 40099; bugfix on 0.2.8.1-alpha.
263 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
264 - For HSFETCH commands on v2 onion services addresses, check the
265 length of bytes decoded, not the base32 length. Fixes bug 34400;
266 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
268 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
269 - Fix a bug that prevented Tor from starting if its log file grew
270 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
272 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
273 - Add a deprecation warning for version 2 onion services. Closes
276 o Removed features (backport from 0.4.4.3-alpha):
277 - Our "check-local" test target no longer tries to use the
278 Coccinelle semantic patching tool parse all the C files. While it
279 is a good idea to try to make sure Coccinelle works on our C
280 before we run a Coccinelle patch, doing so on every test run has
281 proven to be disruptive. You can still run this tool manually with
282 "make check-cocci". Closes ticket 40030. ticket 40030.
285 Changes in version 0.3.5.12 - 2020-11-12
286 Tor 0.4.3.7 backports several bugfixes from later releases. It
287 includes a fix for TROVE-2020-005, a security issue that could be
288 used, under certain cases, by an adversary to observe traffic patterns
289 on a limited number of circuits intended for a different relay.
291 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
292 - Replace the 148 fallback directories originally included in Tor
293 0.4.1.4-rc (of which around 105 are still functional) with a list
294 of 144 fallbacks generated in July 2020. Closes ticket 40061.
296 o Major bugfixes (security, backport from 0.4.5.1-alpha):
297 - When completing a channel, relays now check more thoroughly to
298 make sure that it matches any pending circuits before attaching
299 those circuits. Previously, address correctness and Ed25519
300 identities were not checked in this case, but only when extending
301 circuits on an existing channel. Fixes bug 40080; bugfix on
302 0.2.7.2-alpha. Resolves TROVE-2020-005.
304 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
305 - When running with NSS enabled, make sure that NSS knows to expect
306 nonblocking sockets. Previously, we set our TCP sockets as
307 nonblocking, but did not tell NSS, which in turn could lead to
308 unexpected blocking behavior. Fixes bug 40035; bugfix
311 o Minor features (security, backport from 0.4.4.4-rc):
312 - Channels using obsolete versions of the Tor link protocol are no
313 longer allowed to circumvent address-canonicity checks. (This is
314 only a minor issue, since such channels have no way to set ed25519
315 keys, and therefore should always be rejected for circuits that
316 specify ed25519 identities.) Closes ticket 40081.
318 o Minor features (debugging, directory system):
319 - Don't crash when we find a non-guard with a guard-fraction value
320 set. Instead, log a bug warning, in an attempt to figure out how
321 this happened. Diagnostic for ticket 32868.
323 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
324 - Tor no longer allows subprotocol versions larger than 63.
325 Previously version numbers up to UINT32_MAX were allowed, which
326 significantly complicated our code. Implements proposal 318;
329 o Minor features (tests, backport from 0.4.4.5):
330 - Our "make check" target now runs the unit tests in 8 parallel
331 chunks. Doing this speeds up hardened CI builds by more than a
332 factor of two. Closes ticket 40098.
334 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
335 - Fix a rendezvous cache unit test that was triggering an underflow
336 on the global rend cache allocation. Fixes bug 40125; bugfix
338 - Fix another rendezvous cache unit test that was triggering an
339 underflow on the global rend cache allocation. Fixes bug 40126;
340 bugfix on 0.2.8.1-alpha.
342 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
343 - Fix a correctness bug that could cause an assertion failure if we
344 ever tried using the buf_move_all() function with an empty input
345 buffer. As far as we know, no released versions of Tor do this.
346 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
348 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
349 - Remove a debug logging statement that uselessly spammed the logs.
350 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
352 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
353 - On a bridge, treat all connections from an ExtORPort as remote by
354 default for the purposes of rate-limiting. Previously, bridges
355 would treat the connection as local unless they explicitly
356 received a "USERADDR" command. ExtORPort connections still count
357 as local if there is a USERADDR command with an explicit local
358 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
360 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
361 - Avoid a fatal assert() when failing to create a listener
362 connection for an address that was in use. Fixes bug 40073; bugfix
365 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
366 - Adjust the rules for when to warn about having too many
367 connections to other relays. Previously we'd tolerate up to 1.5
368 connections per relay on average. Now we tolerate more connections
369 for directory authorities, and raise the number of total
370 connections we need to see before we warn. Fixes bug 33880; bugfix
373 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
374 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
375 descriptors, when the IPv6 port was configured as "auto". Fixes
376 bug 32588; bugfix on 0.2.3.9-alpha.
378 o Minor bugfixes (tests, 0.4.4.5):
379 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
380 on its own. Previously, it would exit with an error. Fixes bug
381 40099; bugfix on 0.2.8.1-alpha.
383 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
384 - Fix a bug that prevented Tor from starting if its log file grew
385 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
387 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
388 - Add a deprecation warning for version 2 onion services. Closes
392 Changes in version 0.4.5.1-alpha - 2020-11-01
393 Tor 0.4.5.1-alpha is the first alpha release in the 0.4.5.x series. It
394 improves support for IPv6, address discovery and self-testing, code
397 This release also fixes TROVE-2020-005, a security issue that could be
398 used, under certain cases, by an adversary to observe traffic patterns
399 on a limited number of circuits intended for a different relay. To
400 mount this attack, the adversary would need to actively extend
401 circuits to an incorrect address, as well as compromise a relay's
402 legacy RSA-1024 key. We'll be backporting this fix to other release
403 series soon, after it has had some testing.
405 Here are the changes since 0.4.4.5.
407 o Major features (build):
408 - When building Tor, first link all object files into a single
409 static library. This may help with embedding Tor in other
410 programs. Note that most Tor functions do not constitute a part of
411 a stable or supported API: only those functions in tor_api.h
412 should be used if embedding Tor. Closes ticket 40127.
414 o Major features (metrics):
415 - Introduce a new MetricsPort which exposes, through an HTTP
416 interface, a series of metrics that tor collects at runtime. At
417 the moment, the only supported output format is Prometheus data
418 model. Closes ticket 40063. See the manual page for more
419 information and security considerations.
420 o Major features (relay, IPv6):
421 - The torrc option Address now supports IPv6. This unifies our
422 address discovery interface to support IPv4, IPv6, and hostnames.
424 - Launch IPv4 and IPv6 ORPort self-test circuits on relays and
425 bridges. Closes ticket 33222.
426 - Relays now automatically bind on IPv6 for their ORPort, unless
427 specified otherwise with the IPv4Only flag. Closes ticket 33246.
428 - When a relay with IPv6 support is told to open a connection to
429 another relay, and the extend cell lists both IPv4 and IPv6
430 addresses, the first relay now picks randomly which address to
431 use. Closes ticket 33220.
432 - Relays now track their IPv6 ORPort reachability separately from
433 the reachability of their IPv4 ORPort. They will not publish a
434 descriptor unless _both_ ports appear to be externally reachable.
437 o Major features (tracing):
438 - Add event-tracing library support for USDT and LTTng-UST, and a
439 few tracepoints in the circuit subsystem. More will come
440 incrementally. This feature is compiled out by default: it needs
441 to be enabled at configure time. See documentation in
442 doc/HACKING/Tracing.md. Closes ticket 32910.
444 o Major bugfixes (security):
445 - When completing a channel, relays now check more thoroughly to
446 make sure that it matches any pending circuits before attaching
447 those circuits. Previously, address correctness and Ed25519
448 identities were not checked in this case, but only when extending
449 circuits on an existing channel. Fixes bug 40080; bugfix on
450 0.2.7.2-alpha. Resolves TROVE-2020-005.
452 o Major bugfixes (TLS, buffer):
453 - When attempting to read N bytes on a TLS connection, really try to
454 read all N bytes. Previously, Tor would stop reading after the
455 first TLS record, which can be smaller than the N bytes requested,
456 and not check for more data until the next mainloop event. Fixes
457 bug 40006; bugfix on 0.1.0.5-rc.
459 o Minor features (address discovery):
460 - If no Address statements are found, relays now prioritize guessing
461 their address by looking at the local interface instead of the
462 local hostname. If the interface address can't be found, the local
463 hostname is used. Closes ticket 33238.
465 o Minor features (admin tools):
466 - Add a new --format argument to -key-expiration option to allow
467 specifying the time format of the expiration date. Adds Unix
468 timestamp format support. Patch by Daniel Pinto. Closes
471 o Minor features (bootstrap reporting):
472 - When reporting bootstrapping status on a relay, do not consider
473 connections that have never been the target of an origin circuit.
474 Previously, all connection failures were treated as potential
475 bootstrapping failures, including connections that had been opened
476 because of client requests. Closes ticket 25061.
478 o Minor features (build):
479 - When running the configure script, try to detect version
480 mismatches between the OpenSSL headers and libraries, and suggest
481 that the user should try "--with-openssl-dir". Closes 40138.
482 - If the configure script has given any warnings, remind the user
483 about them at the end of the script. Related to 40138.
485 o Minor features (configuration):
486 - Allow using wildcards (* and ?) with the %include option on
487 configuration files. Closes ticket 25140. Patch by Daniel Pinto.
488 - Allow the configuration options EntryNodes, ExcludeNodes,
489 ExcludeExitNodes, ExitNodes, MiddleNodes, HSLayer2Nodes and
490 HSLayer3Nodes to be specified multiple times. Closes ticket 28361.
491 Patch by Daniel Pinto.
493 o Minor features (control port):
494 - Add a DROPTIMEOUTS command to drop circuit build timeout history
495 and reset the current timeout. Closes ticket 40002.
496 - When a stream enters the AP_CONN_STATE_CONTROLLER_WAIT status,
497 send a control port event. Closes ticket 32190. Patch by
499 - Introduce GETINFO "stats/ntor/{assigned/requested}" and
500 "stats/tap/{assigned/requested}" to get the NTor and TAP circuit
501 onion handshake counts respectively. Closes ticket 28279. Patch by
504 o Minor features (control port, IPv6):
505 - Tor relays now try to report to the controller when they are
506 launching an IPv6 self-test. Closes ticket 34068.
507 - Introduce "GETINFO address/v4" and "GETINFO address/v6" in the
508 control port to fetch the Tor host's respective IPv4 or IPv6
509 address. We keep "GETINFO address" for backwards-compatibility.
510 Closes ticket 40039. Patch by Neel Chauhan.
512 o Minor features (directory authorities):
513 - Authorities now list a different set of protocols as required and
514 recommended. These lists have been chosen so that only truly
515 recommended and/or required protocols are included, and so that
516 clients using 0.2.9 or later will continue to work (even though
517 they are not supported), whereas only relays running 0.3.5 or
518 later will meet the requirements. Closes ticket 40162.
519 - Add a new consensus method 30 that removes the unnecessary "="
520 padding from ntor-onion-key. Closes ticket 7869. Patch by
522 - Directory authorities now reject descriptors from relays running
523 Tor versions from the obsolete 0.4.1 series. Resolves ticket
524 34357. Patch by Neel Chauhan.
525 - Make it possible to specify multiple ConsensusParams torrc lines.
526 Now directory authority operators can for example put the main
527 ConsensusParams config in one torrc file and then add to it from a
528 different torrc file. Closes ticket 40164.
529 - The AssumeReachable option no longer stops directory authorities
530 from checking whether other relays are running. A new
531 AuthDirTestReachability option can be used to disable these
532 checks. Closes ticket 34445.
533 - When looking for possible Sybil attacks, also consider IPv6
534 addresses. Two routers are considered to have "the same" address
535 by this metric if they are in the same /64 network. Patch from
536 Maurice Pibouin. Closes ticket 7193.
538 o Minor features (directory authorities, IPv6):
539 - Make authorities add their IPv6 ORPort (if any) to the trusted
540 servers list. Authorities previously added only their IPv4
541 addresses. Closes ticket 32822.
543 o Minor features (ed25519, relay):
544 - Save a relay's base64-encoded ed25519 identity key to the data
545 directory in a file named fingerprint-ed25519. Closes ticket
546 30642. Patch by Neel Chauhan.
548 o Minor features (heartbeat):
549 - Include the total number of inbound and outbound IPv4 and IPv6
550 connections in the heartbeat message. Closes ticket 29113.
552 o Minor features (IPv6, ExcludeNodes):
553 - Handle IPv6 addresses in ExcludeNodes; previously they were
554 ignored. Closes ticket 34065. Patch by Neel Chauhan.
556 o Minor features (logging):
557 - Add the running glibc version to the log, and the compiled glibc
558 version to the library list returned when using --library-versions.
559 Patch from Daniel Pinto. Closes ticket 40047.
560 - Consider an HTTP 301 response to be an error (like a 404) when
561 processing a directory response. Closes ticket 40053.
562 - Log directory fetch statistics as a single line. Closes
564 - Provide more complete descriptions of our connections when logging
565 about them. Closes ticket 40041.
566 - When describing a relay in the logs, we now include its ed25519
567 identity. Closes ticket 22668.
569 o Minor features (onion services):
570 - Only overwrite an onion service's existing hostname file if its
571 contents are wrong. This enables read-only onion-service
572 directories. Resolves ticket 40062. Patch by Neel Chauhan.
574 o Minor features (pluggable transports):
575 - Add an OutboundBindAddressPT option to allow users to specify
576 which IPv4 and IPv6 address pluggable transports should use for
577 outgoing IP packets. Tor does not have a way to enforce that the
578 pluggable transport honors this option, so each pluggable transport
579 needs to implement support on its own. Closes ticket 5304.
581 o Minor features (relay address tracking):
582 - We now store relay addresses for OR connections in a more logical
583 way. Previously we would sometimes overwrite the actual address of
584 a connection with a "canonical address", and then store the "real
585 address" elsewhere to remember it. We now track the "canonical
586 address" elsewhere for the cases where we need it, and leave the
587 connection's address alone. Closes ticket 33898.
589 o Minor features (relay):
590 - If a relay is unable to discover its address, attempt to learn it
591 from the NETINFO cell. Closes ticket 40022.
592 - Log immediately when launching a relay self-check. Previously we
593 would try to log before launching checks, or approximately when we
594 intended to launch checks, but this tended to be error-prone.
597 o Minor features (relay, address discovery):
598 - If Address option is not found in torrc, attempt to learn our
599 address with the configured ORPort address if any. Closes
602 o Minor features (relay, IPv6):
603 - Add an AssumeReachableIPv6 option to disable self-checking IPv6
604 reachability. Closes part of ticket 33224.
605 - Add new "assume-reachable" and "assume-reachable-ipv6" consensus
606 parameters to be used in an emergency to tell relays that they
607 should publish even if they cannot complete their ORPort self-
608 checks. Closes ticket 34064 and part of 33224.
609 - Allow relays to send IPv6-only extend cells. Closes ticket 33222.
610 - Declare support for the Relay=3 subprotocol version. Closes
612 - When launching IPv6 ORPort self-test circuits, make sure that the
613 second-last hop can initiate an IPv6 extend. Closes ticket 33222.
615 o Minor features (specification update):
616 - Several fields in microdescriptors, router descriptors, and
617 consensus documents that were formerly optional are now required.
618 Implements proposal 315; closes ticket 40132.
620 o Minor features (state management):
621 - When loading the state file, remove entries from the statefile
622 that have been obsolete for a long time. Ordinarily Tor preserves
623 unrecognized entries in order to keep forward-compatibility, but
624 these entries have not actually been used in any release since
625 before 0.3.5.x. Closes ticket 40137.
627 o Minor features (statistics, ipv6):
628 - Relays now publish IPv6-specific counts of single-direction versus
629 bidirectional relay connections. Closes ticket 33264.
630 - Relays now publish their IPv6 read and write statistics over time,
631 if statistics are enabled. Closes ticket 33263.
633 o Minor features (subprotocol versions):
634 - Tor no longer allows subprotocol versions larger than 63.
635 Previously version numbers up to UINT32_MAX were allowed, which
636 significantly complicated our code. Implements proposal 318;
638 - Use the new limitations on subprotocol versions due to proposal
639 318 to simplify our implementation. Part of ticket 40133.
641 o Minor features (testing configuration):
642 - The TestingTorNetwork option no longer implicitly sets
643 AssumeReachable to 1. This change allows us to test relays' self-
644 testing mechanisms, and to test authorities' relay-testing
645 functionality. Closes ticket 34446.
647 o Minor features (testing):
648 - Added unit tests for channel_matches_target_addr_for_extend().
649 Closes Ticket 33919. Patch by MrSquanchee.
651 o Minor features (tests, v2 onion services):
652 - Fix a rendezvous cache unit test that was triggering an underflow
653 on the global rend cache allocation. Fixes bug 40125; bugfix
655 - Fix another rendezvous cache unit test that was triggering an
656 underflow on the global rend cache allocation. Fixes bug 40126;
657 bugfix on 0.2.8.1-alpha.
659 o Minor bugfixes (circuit padding):
660 - When circpad_send_padding_cell_for_callback is called,
661 `is_padding_timer_scheduled` flag was not reset. Now it is set to
662 0 at the top of that function. Fixes bug 32671; bugfix
664 - Add a per-circuit padding machine instance counter, so we can
665 differentiate between shutdown requests for old machines on a
666 circuit. Fixes bug 30992; bugfix on 0.4.1.1-alpha.
667 - Add the ability to keep circuit padding machines if they match a
668 set of circuit states or purposes. This allows us to have machines
669 that start up under some conditions but don't shut down under
670 others. We now use this mask to avoid starting up introduction
671 circuit padding again after the machines have already completed.
672 Fixes bug 32040; bugfix on 0.4.1.1-alpha.
674 o Minor bugfixes (compatibility):
675 - Strip '\r' characters when reading text files on Unix platforms.
676 This should resolve an issue where a relay operator migrates a
677 relay from Windows to Unix, but does not change the line ending of
678 Tor's various state files to match the platform, and the CRLF line
679 endings from Windows end up leaking into other files such as the
680 extra-info document. Fixes bug 33781; bugfix on 0.0.9pre5.
682 o Minor bugfixes (compilation):
683 - Fix compiler warnings that would occur when building with
684 "--enable-all-bugs-are-fatal" and "--disable-module-relay" at the
685 same time. Fixes bug 40129; bugfix on 0.4.4.1-alpha.
686 - Resolve a compilation warning that could occur in
687 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
689 o Minor bugfixes (configuration):
690 - Fix bug where %including a pattern ending with */ would include
691 files and folders (instead of folders only) in versions of glibc <
692 2.19. Fixes bug 40141; bugfix on 0.4.5.0-alpha-dev. Patch by
695 o Minor bugfixes (control port):
696 - Make sure we send the SOCKS request address in relay begin cells
697 when a stream is attached with the purpose
698 CIRCUIT_PURPOSE_CONTROLLER. Fixes bug 33124; bugfix on 0.0.5.
699 Patch by Neel Chauhan.
701 o Minor bugfixes (logging):
702 - Remove a debug logging statement that uselessly spammed the logs.
703 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
704 - When logging a rate-limited message about how many messages have
705 been suppressed in the last N seconds, give an accurate value for
706 N, rounded up to the nearest minute. Previously we would report
707 the size of the rate-limiting interval, regardless of when the
708 messages started to occur. Fixes bug 19431; bugfix
711 o Minor bugfixes (relay configuration, crash):
712 - Avoid a fatal assert() when failing to create a listener
713 connection for an address that was in use. Fixes bug 40073; bugfix
716 o Minor bugfixes (rust, protocol versions):
717 - Declare support for the onion service introduction point denial of
718 service extensions when building with Rust. Fixes bug 34248;
719 bugfix on 0.4.2.1-alpha.
720 - Make Rust protocol version support checks consistent with the
721 undocumented error behavior of the corresponding C code. Fixes bug
722 34251; bugfix on 0.3.3.5-rc.
724 o Minor bugfixes (self-testing):
725 - When receiving an incoming circuit, only accept it as evidence
726 that we are reachable if the declared address of its channel is
727 the same address we think that we have. Otherwise, it could be
728 evidence that we're reachable on some other address. Fixes bug
729 20165; bugfix on 0.1.0.1-rc.
731 o Minor bugfixes (spec conformance):
732 - Use the correct key type when generating signing->link
733 certificates. Fixes bug 40124; bugfix on 0.2.7.2-alpha.
735 o Minor bugfixes (subprotocol versions):
736 - Consistently reject extra commas, instead of only rejecting
737 leading commas. Fixes bug 27194; bugfix on 0.2.9.4-alpha.
738 - In summarize_protover_flags(), treat empty strings the same as
739 NULL. This prevents protocols_known from being set. Previously, we
740 treated empty strings as normal strings, which led to
741 protocols_known being set. Fixes bug 34232; bugfix on
742 0.3.3.2-alpha. Patch by Neel Chauhan.
744 o Minor bugfixes (v2 onion services):
745 - For HSFETCH commands on v2 onion services addresses, check the
746 length of bytes decoded, not the base32 length. Fixes bug 34400;
747 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
749 o Code simplification and refactoring:
750 - Add and use a set of functions to perform down-casts on constant
751 connection and channel pointers. Closes ticket 40046.
752 - Refactor our code that logs descriptions of connections, channels,
753 and the peers on them, to use a single call path. This change
754 enables us to refactor the data types that they use, and eliminates
755 many confusing usages of those types. Closes ticket 40041.
756 - Refactor some common node selection code into a single function.
758 - Remove the now-redundant 'outbuf_flushlen' field from our
759 connection type. It was previously used for an older version of
760 our rate-limiting logic. Closes ticket 33097.
761 - Rename "fascist_firewall_*" identifiers to "reachable_addr_*"
762 instead, for consistency with other code. Closes ticket 18106.
763 - Rename functions about "advertised" ports which are not in fact
764 guaranteed to return the ports that have been advertised. Closes
766 - Split implementation of several command line options from
767 options_init_from_torrc into smaller isolated functions. Patch by
768 Daniel Pinto. Closes ticket 40102.
769 - When an extend cell is missing an IPv4 or IPv6 address, fill in
770 the address from the extend info. This is similar to what was done
771 in ticket 33633 for ed25519 keys. Closes ticket 33816. Patch by
774 o Deprecated features:
775 - The "non-builtin" argument to the "--dump-config" command is now
776 deprecated. When it works, it behaves the same as "short", which
777 you should use instead. Closes ticket 33398.
780 - Replace URLs from our old bugtracker so that they refer to the new
781 bugtracker and wiki. Closes ticket 40101.
784 - We no longer ship or build a "tor.service" file for use with
785 systemd. No distribution included this script unmodified, and we
786 don't have the expertise ourselves to maintain this in a way that
787 all the various systemd-based distributions can use. Closes
789 - We no longer ship support for the Android logging API. Modern
790 versions of Android can use the syslog API instead. Closes
792 - The "optimistic data" feature is now always on; there is no longer
793 an option to disable it from the torrc file or from the consensus
794 directory. Closes part of 40139.
795 - The "usecreatefast" network parameter is now removed; there is no
796 longer an option for authorities to turn it off. Closes part
800 - Add unit tests for bandwidth statistics manipulation functions.
801 Closes ticket 33812. Patch by MrSquanchee.
803 o Code simplification and refactoring (autoconf):
804 - Remove autoconf checks for unused funcs and headers. Closes ticket
805 31699; Patch by @bduszel
807 o Code simplification and refactoring (maintainer scripts):
808 - Disable by default the pre-commit hook. Use the environment
809 variable TOR_EXTRA_PRE_COMMIT_CHECKS in order to run it.
810 Furthermore, stop running practracker in the pre-commit hook and
811 make check-local. Closes ticket 40019.
813 o Code simplification and refactoring (relay address):
814 - Most of IPv4 representation was using "uint32_t". It has now been
815 moved to use the internal "tor_addr_t" interface instead. This is
816 so we can properly integrate IPv6 along IPv4 with common
817 interfaces. Closes ticket 40043.
819 o Documentation (manual page):
820 - Move them from doc/ to doc/man/. Closes ticket 40044.
821 - Describe the status of the "Sandbox" option more accurately. It is
822 no longer "experimental", but it _is_ dependent on kernel and libc
823 versions. Closes ticket 23378.
825 o Documentation (tracing):
826 - Document in depth the circuit subsystem trace events in the new
827 doc/tracing/EventsCircuit.md. Closes ticket 40036.
830 Changes in version 0.4.4.5 - 2020-09-15
831 Tor 0.4.4.5 is the first stable release in the 0.4.4.x series. This
832 series improves our guard selection algorithms, adds v3 onion balance
833 support, improves the amount of code that can be disabled when running
834 without relay support, and includes numerous small bugfixes and
835 enhancements. It also lays the ground for some IPv6 features that
836 we'll be developing more in the next (0.4.5) series.
838 Per our support policy, we support each stable release series for nine
839 months after its first stable release, or three months after the first
840 stable release of the next series: whichever is longer. This means
841 that 0.4.4.x will be supported until around June 2021--or later, if
842 0.4.5.x is later than anticipated.
844 Note also that support for 0.4.2.x has just ended; support for 0.4.3
845 will continue until Feb 15, 2021. We still plan to continue supporting
846 0.3.5.x, our long-term stable series, until Feb 2022.
848 Below are the changes since 0.4.4.4-rc. For a complete list of changes
849 since 0.4.3.6, see the ReleaseNotes file.
851 o Major bugfixes (onion services, DoS):
852 - Correct handling of parameters for the onion service DoS defense.
853 Previously, the consensus parameters for the onion service DoS
854 defenses were overwriting the parameters set by the service
855 operator using HiddenServiceEnableIntroDoSDefense. Fixes bug
856 40109; bugfix on 0.4.2.1-alpha.
858 o Major bugfixes (stats, onion services):
859 - Fix a bug where we were undercounting the Tor network's total
860 onion service traffic, by ignoring any traffic originating from
861 clients. Now we count traffic from both clients and services.
862 Fixes bug 40117; bugfix on 0.2.6.2-alpha.
864 o Minor features (control port):
865 - If a ClientName was specified in ONION_CLIENT_AUTH_ADD for an
866 onion service, display it when we use ONION_CLIENT_AUTH_VIEW.
867 Closes ticket 40089. Patch by Neel Chauhan.
869 o Minor features (denial-of-service memory limiter):
870 - Allow the user to configure even lower values for the
871 MaxMemInQueues parameter. Relays now enforce a minimum of 64 MB,
872 when previously the minimum was 256 MB. On clients, there is no
873 minimum. Relays and clients will both warn if the value is set so
874 low that Tor is likely to stop working. Closes ticket 24308.
876 o Minor features (tests):
877 - Our "make check" target now runs the unit tests in 8 parallel
878 chunks. Doing this speeds up hardened CI builds by more than a
879 factor of two. Closes ticket 40098.
881 o Minor bugfixes (guard selection algorithm):
882 - Avoid needless guard-related warning when upgrading from 0.4.3 to
883 0.4.4. Fixes bug 40105; bugfix on 0.4.4.1-alpha.
885 o Minor bugfixes (tests):
886 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
887 on its own. Previously, it would exit with an error. Fixes bug
888 40099; bugfix on 0.2.8.1-alpha.
891 Changes in version 0.4.4.3-alpha - 2020-07-27
892 Tor 0.4.4.3-alpha fixes several annoyances in previous versions,
893 including one affecting NSS users, and several affecting the Linux
896 o Major features (fallback directory list):
897 - Replace the 148 fallback directories originally included in Tor
898 0.4.1.4-rc (of which around 105 are still functional) with a list
899 of 144 fallbacks generated in July 2020. Closes ticket 40061.
901 o Major bugfixes (NSS):
902 - When running with NSS enabled, make sure that NSS knows to expect
903 nonblocking sockets. Previously, we set our TCP sockets as
904 nonblocking, but did not tell NSS, which in turn could lead to
905 unexpected blocking behavior. Fixes bug 40035; bugfix
908 o Minor bugfixes (linux seccomp2 sandbox):
909 - Fix a regression on sandboxing rules for the openat() syscall. The
910 fix for bug 25440 fixed the problem on systems with glibc >= 2.27
911 but broke with versions of glibc. We now choose a rule based on
912 the glibc version. Patch from Daniel Pinto. Fixes bug 27315;
914 - Makes the seccomp sandbox allow the correct syscall for opendir
915 according to the running glibc version. This fixes crashes when
916 reloading torrc with sandbox enabled when running on glibc 2.15 to
917 2.21 and 2.26. Patch from Daniel Pinto. Fixes bug 40020; bugfix
920 o Minor bugfixes (relay, usability):
921 - Adjust the rules for when to warn about having too many
922 connections to other relays. Previously we'd tolerate up to 1.5
923 connections per relay on average. Now we tolerate more connections
924 for directory authorities, and raise the number of total
925 connections we need to see before we warn. Fixes bug 33880; bugfix
929 - Replace most http:// URLs in our code and documentation with
930 https:// URLs. (We have left unchanged the code in src/ext/, and
931 the text in LICENSE.) Closes ticket 31812. Patch from Jeremy Rand.
934 - Our "check-local" test target no longer tries to use the
935 Coccinelle semantic patching tool parse all the C files. While it
936 is a good idea to try to make sure Coccinelle works on our C
937 before we run a Coccinelle patch, doing so on every test run has
938 proven to be disruptive. You can still run this tool manually with
939 "make check-cocci". Closes ticket 40030.
942 Changes in version 0.3.5.11 - 2020-07-09
943 Tor 0.3.5.11 backports fixes from later tor releases, including several
944 usability, portability, and reliability fixes.
946 This release also fixes TROVE-2020-001, a medium-severity denial of
947 service vulnerability affecting all versions of Tor when compiled with
948 the NSS encryption library. (This is not the default configuration.)
949 Using this vulnerability, an attacker could cause an affected Tor
950 instance to crash remotely. This issue is also tracked as CVE-2020-
951 15572. Anybody running a version of Tor built with the NSS library
952 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
955 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
956 - Fix a crash due to an out-of-bound memory access when Tor is
957 compiled with NSS support. Fixes bug 33119; bugfix on
958 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
961 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
962 - Fix a bug that was preventing DoS defenses from running on bridges
963 with a pluggable transport. Previously, the DoS subsystem was not
964 given the transport name of the client connection, thus failed to
965 find the GeoIP cache entry for that client address. Fixes bug
966 33491; bugfix on 0.3.3.2-alpha.
968 o Minor features (testing, backport from 0.4.3.4-rc):
969 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
970 variable to specify a list of space-separated test cases that
971 should not be executed. We will use this to disable certain tests
972 that are failing on Appveyor because of mismatched OpenSSL
973 libraries. Part of ticket 33643.
975 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
976 - Use the correct 64-bit printf format when compiling with MINGW on
977 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
979 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
980 - Warn if the ContactInfo field is not set, and tell the relay
981 operator that not having a ContactInfo field set might cause their
982 relay to get rejected in the future. Fixes bug 33361; bugfix
985 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
986 - Resume use of preemptively-built circuits when UseEntryGuards is set
987 to 0. We accidentally disabled this feature with that config
988 setting, leading to slower load times. Fixes bug 34303; bugfix
991 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
992 - Avoid compiler warnings from Clang 10 related to the use of GCC-
993 style "/* falls through */" comments. Both Clang and GCC allow
994 __attribute__((fallthrough)) instead, so that's what we're using
995 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
997 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
998 - Fix a compiler warning on platforms with 32-bit time_t values.
999 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1001 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
1002 - When starting Tor any time after the first time in a process,
1003 register the thread in which it is running as the main thread.
1004 Previously, we only did this on Windows, which could lead to bugs
1005 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1008 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
1009 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1010 if we are not running on Windows. Previously, non-Windows hosts
1011 would reject these line-endings in certain positions, making
1012 certain key files hard to move from one host to another. Fixes bug
1013 33032; bugfix on 0.3.5.1-alpha.
1015 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1016 - Downgrade a noisy log message that could occur naturally when
1017 receiving an extrainfo document that we no longer want. Fixes bug
1018 16016; bugfix on 0.2.6.3-alpha.
1020 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
1021 - Remove a BUG() warning that would cause a stack trace if an onion
1022 service descriptor was freed while we were waiting for a
1023 rendezvous circuit to complete. Fixes bug 28992; bugfix
1026 o Testing (CI, backport from 0.4.3.4-rc):
1027 - In our Appveyor Windows CI, copy required DLLs to test and app
1028 directories, before running tor's tests. This ensures that tor.exe
1029 and test*.exe use the correct version of each DLL. This fix is not
1030 required, but we hope it will avoid DLL search issues in future.
1031 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1032 - On Appveyor, skip the crypto/openssl_version test, which is
1033 failing because of a mismatched library installation. Fix
1037 Changes in version 0.4.2.8 - 2020-07-09
1038 Tor 0.4.2.8 backports various fixes from later releases, including
1039 several that affect usability and portability.
1041 This release also fixes TROVE-2020-001, a medium-severity denial of
1042 service vulnerability affecting all versions of Tor when compiled with
1043 the NSS encryption library. (This is not the default configuration.)
1044 Using this vulnerability, an attacker could cause an affected Tor
1045 instance to crash remotely. This issue is also tracked as CVE-2020-
1046 15572. Anybody running a version of Tor built with the NSS library
1047 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1050 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1051 - Fix a crash due to an out-of-bound memory access when Tor is
1052 compiled with NSS support. Fixes bug 33119; bugfix on
1053 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1056 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
1057 - Fix a bug that was preventing DoS defenses from running on bridges
1058 with a pluggable transport. Previously, the DoS subsystem was not
1059 given the transport name of the client connection, thus failed to
1060 find the GeoIP cache entry for that client address. Fixes bug
1061 33491; bugfix on 0.3.3.2-alpha.
1063 o Minor feature (sendme, flow control, backport form 0.4.3.4-rc):
1064 - Default to sending SENDME version 1 cells. (Clients are already
1065 sending these, because of a consensus parameter telling them to do
1066 so: this change only affects what clients would do if the
1067 consensus didn't contain a recommendation.) Closes ticket 33623.
1069 o Minor features (diagnostic, backport from 0.4.3.3-alpha):
1070 - Improve assertions and add some memory-poisoning code to try to
1071 track down possible causes of a rare crash (32564) in the EWMA
1072 code. Closes ticket 33290.
1074 o Minor features (testing, backport from 0.4.3.4-rc):
1075 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
1076 variable to specify a list of space-separated test cases that
1077 should not be executed. We will use this to disable certain tests
1078 that are failing on Appveyor because of mismatched OpenSSL
1079 libraries. Part of ticket 33643.
1081 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1082 - Use the correct 64-bit printf format when compiling with MINGW on
1083 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1085 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
1086 - Warn if the ContactInfo field is not set, and tell the relay
1087 operator that not having a ContactInfo field set might cause their
1088 relay to get rejected in the future. Fixes bug 33361; bugfix
1091 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1092 - Resume use of preemptively-built circuits when UseEntryGuards is set
1093 to 0. We accidentally disabled this feature with that config
1094 setting, leading to slower load times. Fixes bug 34303; bugfix
1097 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
1098 - Avoid compiler warnings from Clang 10 related to the use of GCC-
1099 style "/* falls through */" comments. Both Clang and GCC allow
1100 __attribute__((fallthrough)) instead, so that's what we're using
1101 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
1102 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
1105 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1106 - Fix a compiler warning on platforms with 32-bit time_t values.
1107 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1109 o Minor bugfixes (controller protocol, backport from 0.4.3.2-alpha):
1110 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
1111 report them as SIGNAL events. Previously we would log a bug
1112 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
1114 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
1115 - When starting Tor any time after the first time in a process,
1116 register the thread in which it is running as the main thread.
1117 Previously, we only did this on Windows, which could lead to bugs
1118 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1121 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
1122 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1123 if we are not running on Windows. Previously, non-Windows hosts
1124 would reject these line-endings in certain positions, making
1125 certain key files hard to move from one host to another. Fixes bug
1126 33032; bugfix on 0.3.5.1-alpha.
1128 o Minor bugfixes (logging, backport from 0.4.3.2-rc):
1129 - When logging a bug, do not say "Future instances of this warning
1130 will be silenced" unless we are actually going to silence them.
1131 Previously we would say this whenever a BUG() check failed in the
1132 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
1134 o Minor bugfixes (logging, backport from 0.4.3.4-rc):
1135 - Flush stderr, stdout, and file logs during shutdown, if supported
1136 by the OS. This change helps make sure that any final logs are
1137 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
1139 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1140 - Downgrade a noisy log message that could occur naturally when
1141 receiving an extrainfo document that we no longer want. Fixes bug
1142 16016; bugfix on 0.2.6.3-alpha.
1144 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
1145 - Remove a BUG() warning that would cause a stack trace if an onion
1146 service descriptor was freed while we were waiting for a
1147 rendezvous circuit to complete. Fixes bug 28992; bugfix
1150 o Testing (CI, backport from 0.4.3.4-rc):
1151 - In our Appveyor Windows CI, copy required DLLs to test and app
1152 directories, before running tor's tests. This ensures that tor.exe
1153 and test*.exe use the correct version of each DLL. This fix is not
1154 required, but we hope it will avoid DLL search issues in future.
1155 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1156 - On Appveyor, skip the crypto/openssl_version test, which is
1157 failing because of a mismatched library installation. Fix
1161 Changes in version 0.4.3.6 - 2020-07-09
1162 Tor 0.4.3.6 backports several bugfixes from later releases, including
1163 some affecting usability.
1165 This release also fixes TROVE-2020-001, a medium-severity denial of
1166 service vulnerability affecting all versions of Tor when compiled with
1167 the NSS encryption library. (This is not the default configuration.)
1168 Using this vulnerability, an attacker could cause an affected Tor
1169 instance to crash remotely. This issue is also tracked as CVE-2020-
1170 15572. Anybody running a version of Tor built with the NSS library
1171 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1174 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1175 - Fix a crash due to an out-of-bound memory access when Tor is
1176 compiled with NSS support. Fixes bug 33119; bugfix on
1177 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1180 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1181 - Use the correct 64-bit printf format when compiling with MINGW on
1182 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1184 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1185 - Resume use of preemptively-built circuits when UseEntryGuards is set
1186 to 0. We accidentally disabled this feature with that config
1187 setting, leading to slower load times. Fixes bug 34303; bugfix
1190 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1191 - Fix a compiler warning on platforms with 32-bit time_t values.
1192 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1194 o Minor bugfixes (linux seccomp sandbox, nss, backport from 0.4.4.1-alpha):
1195 - Fix a startup crash when tor is compiled with --enable-nss and
1196 sandbox support is enabled. Fixes bug 34130; bugfix on
1197 0.3.5.1-alpha. Patch by Daniel Pinto.
1199 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1200 - Downgrade a noisy log message that could occur naturally when
1201 receiving an extrainfo document that we no longer want. Fixes bug
1202 16016; bugfix on 0.2.6.3-alpha.
1204 o Minor bugfixes (manual page, backport from 0.4.4.1-alpha):
1205 - Update the man page to reflect that MinUptimeHidServDirectoryV2
1206 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
1208 o Minor bugfixes (onion service v3, backport from 0.4.4.1-alpha):
1209 - Prevent an assert() that would occur when cleaning the client
1210 descriptor cache, and attempting to close circuits for a non-
1211 decrypted descriptor (lacking client authorization). Fixes bug
1212 33458; bugfix on 0.4.2.1-alpha.
1214 o Minor bugfixes (portability, backport from 0.4.4.1-alpha):
1215 - Fix a portability error in the configure script, where we were
1216 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
1218 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
1219 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
1220 descriptors, when the IPv6 port was configured as "auto". Fixes
1221 bug 32588; bugfix on 0.2.3.9-alpha.
1223 o Documentation (backport from 0.4.4.1-alpha):
1224 - Fix several doxygen warnings related to imbalanced groups. Closes
1228 Changes in version 0.4.4.2-alpha - 2020-07-09
1229 This is the second alpha release in the 0.4.4.x series. It fixes a few
1230 bugs in the previous release, and solves a few usability,
1231 compatibility, and portability issues.
1233 This release also fixes TROVE-2020-001, a medium-severity denial of
1234 service vulnerability affecting all versions of Tor when compiled with
1235 the NSS encryption library. (This is not the default configuration.)
1236 Using this vulnerability, an attacker could cause an affected Tor
1237 instance to crash remotely. This issue is also tracked as CVE-2020-
1238 15572. Anybody running a version of Tor built with the NSS library
1239 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1242 o Major bugfixes (NSS, security):
1243 - Fix a crash due to an out-of-bound memory access when Tor is
1244 compiled with NSS support. Fixes bug 33119; bugfix on
1245 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1248 o Minor features (bootstrap reporting):
1249 - Report more detailed reasons for bootstrap failure when the
1250 failure happens due to a TLS error. Previously we would just call
1251 these errors "MISC" when they happened during read, and "DONE"
1252 when they happened during any other TLS operation. Closes
1255 o Minor features (directory authority):
1256 - Authorities now recommend the protocol versions that are supported
1257 by Tor 0.3.5 and later. (Earlier versions of Tor have been
1258 deprecated since January of this year.) This recommendation will
1259 cause older clients and relays to give a warning on startup, or
1260 when they download a consensus directory. Closes ticket 32696.
1262 o Minor features (entry guards):
1263 - Reinstate support for GUARD NEW/UP/DOWN control port events.
1264 Closes ticket 40001.
1266 o Minor features (linux seccomp2 sandbox, portability):
1267 - Allow Tor to build on platforms where it doesn't know how to
1268 report which syscall caused the linux seccomp2 sandbox to fail.
1269 This change should make the sandbox code more portable to less
1270 common Linux architectures. Closes ticket 34382.
1271 - Permit the unlinkat() syscall, which some Libc implementations use
1272 to implement unlink(). Closes ticket 33346.
1274 o Minor bugfix (CI, Windows):
1275 - Use the correct 64-bit printf format when compiling with MINGW on
1276 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1278 o Minor bugfix (onion service v3 client):
1279 - Remove a BUG() warning that could occur naturally. Fixes bug
1280 34087; bugfix on 0.3.2.1-alpha.
1282 o Minor bugfix (SOCKS, onion service client):
1283 - Detect v3 onion service addresses of the wrong length when
1284 returning the F6 ExtendedErrors code. Fixes bug 33873; bugfix
1287 o Minor bugfixes (compiler warnings):
1288 - Fix a compiler warning on platforms with 32-bit time_t values.
1289 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1291 o Minor bugfixes (control port, onion service):
1292 - Consistently use 'address' in "Invalid v3 address" response to
1293 ONION_CLIENT_AUTH commands. Previously, we would sometimes say
1294 'addr'. Fixes bug 40005; bugfix on 0.4.3.1-alpha.
1296 o Minor bugfixes (logging):
1297 - Downgrade a noisy log message that could occur naturally when
1298 receiving an extrainfo document that we no longer want. Fixes bug
1299 16016; bugfix on 0.2.6.3-alpha.
1301 o Minor bugfixes (onion services v3):
1302 - Avoid a non-fatal assertion failure in certain edge-cases when
1303 opening an intro circuit as a client. Fixes bug 34084; bugfix
1306 o Deprecated features (onion service v2):
1307 - Add a deprecation warning for version 2 onion services. Closes
1310 o Removed features (IPv6, revert):
1311 - Revert the change in the default value of ClientPreferIPv6OrPort:
1312 it breaks the torsocks use case. The SOCKS resolve command has no
1313 mechanism to ask for a specific address family (v4 or v6), and so
1314 prioritizing IPv6 when an IPv4 address is requested on the SOCKS
1315 interface resulted in a failure. Tor Browser explicitly sets
1316 PreferIPv6, so this should not affect the majority of our users.
1317 Closes ticket 33796; bugfix on 0.4.4.1-alpha.
1320 Changes in version 0.4.4.1-alpha - 2020-06-16
1321 This is the first alpha release in the 0.4.4.x series. It improves
1322 our guard selection algorithms, improves the amount of code that
1323 can be disabled when running without relay support, and includes numerous
1324 small bugfixes and enhancements. It also lays the ground for some IPv6
1325 features that we'll be developing more in the next (0.4.5) series.
1327 Here are the changes since 0.4.3.5.
1329 o Major features (Proposal 310, performance + security):
1330 - Implements Proposal 310, "Bandaid on guard selection". Proposal
1331 310 solves load-balancing issues with older versions of the guard
1332 selection algorithm, and improves its security. Under this new
1333 algorithm, a newly selected guard never becomes Primary unless all
1334 previously sampled guards are unreachable. Implements
1335 recommendation from 32088. (Proposal 310 is linked to the CLAPS
1336 project researching optimal client location-aware path selections.
1337 This project is a collaboration between the UCLouvain Crypto Group,
1338 the U.S. Naval Research Laboratory, and Princeton University.)
1340 o Major features (IPv6, relay):
1341 - Consider IPv6-only EXTEND2 cells valid on relays. Log a protocol
1342 warning if the IPv4 or IPv6 address is an internal address, and
1343 internal addresses are not allowed. But continue to use the other
1344 address, if it is valid. Closes ticket 33817.
1345 - If a relay can extend over IPv4 and IPv6, and both addresses are
1346 provided, it chooses between them uniformly at random. Closes
1348 - Re-use existing IPv6 connections for circuit extends. Closes
1350 - Relays may extend circuits over IPv6, if the relay has an IPv6
1351 ORPort, and the client supplies the other relay's IPv6 ORPort in
1352 the EXTEND2 cell. IPv6 extends will be used by the relay IPv6
1353 ORPort self-tests in 33222. Closes ticket 33817.
1355 o Major features (v3 onion services):
1356 - Allow v3 onion services to act as OnionBalance backend instances,
1357 by using the HiddenServiceOnionBalanceInstance torrc option.
1358 Closes ticket 32709.
1360 o Minor feature (developer tools):
1361 - Add a script to help check the alphabetical ordering of option
1362 names in the manual page. Closes ticket 33339.
1364 o Minor feature (onion service client, SOCKS5):
1365 - Add 3 new SocksPort ExtendedErrors (F2, F3, F7) that reports back
1366 new type of onion service connection failures. The semantics of
1367 these error codes are documented in proposal 309. Closes
1370 o Minor feature (onion service v3):
1371 - If a service cannot upload its descriptor(s), log why at INFO
1372 level. Closes ticket 33400; bugfix on 0.3.2.1-alpha.
1374 o Minor feature (python scripts):
1375 - Stop assuming that /usr/bin/python exists. Instead of using a
1376 hardcoded path in scripts that still use Python 2, use
1377 /usr/bin/env, similarly to the scripts that use Python 3. Fixes
1378 bug 33192; bugfix on 0.4.2.
1380 o Minor features (client-only compilation):
1381 - Disable more code related to the ext_orport protocol when
1382 compiling without support for relay mode. Closes ticket 33368.
1383 - Disable more of our self-testing code when support for relay mode
1384 is disabled. Closes ticket 33370.
1386 o Minor features (code safety):
1387 - Check for failures of tor_inet_ntop() and tor_inet_ntoa()
1388 functions in DNS and IP address processing code, and adjust
1389 codepaths to make them less likely to crash entire Tor instances.
1390 Resolves issue 33788.
1392 o Minor features (compilation size):
1393 - Most server-side DNS code is now disabled when building without
1394 support for relay mode. Closes ticket 33366.
1396 o Minor features (continuous integration):
1397 - Run unit-test and integration test (Stem, Chutney) jobs with
1398 ALL_BUGS_ARE_FATAL macro being enabled on Travis and Appveyor.
1399 Resolves ticket 32143.
1401 o Minor features (control port):
1402 - Return a descriptive error message from the 'GETINFO status/fresh-
1403 relay-descs' command on the control port. Previously, we returned
1404 a generic error of "Error generating descriptor". Closes ticket
1405 32873. Patch by Neel Chauhan.
1407 o Minor features (developer tooling):
1408 - Refrain from listing all .a files that are generated by the Tor
1409 build in .gitignore. Add a single wildcard *.a entry that covers
1410 all of them for present and future. Closes ticket 33642.
1411 - Add a script ("git-install-tools.sh") to install git hooks and
1412 helper scripts. Closes ticket 33451.
1414 o Minor features (directory authority, shared random):
1415 - Refactor more authority-only parts of the shared-random scheduling
1416 code to reside in the dirauth module, and to be disabled when
1417 compiling with --disable-module-dirauth. Closes ticket 33436.
1419 o Minor features (directory):
1420 - Remember the number of bytes we have downloaded for each directory
1421 purpose while bootstrapping, and while fully bootstrapped. Log
1422 this information as part of the heartbeat message. Closes
1425 o Minor features (IPv6 support):
1426 - Adds IPv6 support to tor_addr_is_valid(). Adds tests for the above
1427 changes and tor_addr_is_null(). Closes ticket 33679. Patch
1429 - Allow clients and relays to send dual-stack and IPv6-only EXTEND2
1430 cells. Parse dual-stack and IPv6-only EXTEND2 cells on relays.
1431 Closes ticket 33901.
1433 o Minor features (logging):
1434 - When trying to find our own address, add debug-level logging to
1435 report the sources of candidate addresses. Closes ticket 32888.
1437 o Minor features (testing, architecture):
1438 - Our test scripts now double-check that subsystem initialization
1439 order is consistent with the inter-module dependencies established
1440 by our .may_include files. Implements ticket 31634.
1441 - Initialize all subsystems at the beginning of our unit test
1442 harness, to avoid crashes due to uninitialized subsystems. Follow-
1443 up from ticket 33316.
1445 o Minor features (v3 onion services):
1446 - Add v3 onion service status to the dumpstats() call which is
1447 triggered by a SIGUSR1 signal. Previously, we only did v2 onion
1448 services. Closes ticket 24844. Patch by Neel Chauhan.
1450 o Minor features (windows):
1451 - Add support for console control signals like Ctrl+C in Windows.
1452 Closes ticket 34211. Patch from Damon Harris (TheDcoder).
1454 o Minor bugfix (onion service v3):
1455 - Prevent an assert() that would occur when cleaning the client
1456 descriptor cache, and attempting to close circuits for a non-
1457 decrypted descriptor (lacking client authorization). Fixes bug
1458 33458; bugfix on 0.4.2.1-alpha.
1460 o Minor bugfix (refactoring):
1461 - Lift circuit_build_times_disabled() out of the
1462 circuit_expire_building() loop, to save CPU time when there are
1463 many circuits open. Fixes bug 33977; bugfix on 0.3.5.9.
1465 o Minor bugfixes (client performance):
1466 - Resume use of preemptively-built circuits when UseEntryGuards is set
1467 to 0. We accidentally disabled this feature with that config
1468 setting, leading to slower load times. Fixes bug 34303; bugfix
1471 o Minor bugfixes (directory authorities):
1472 - Directory authorities now reject votes that arrive too late. In
1473 particular, once an authority has started fetching missing votes,
1474 it no longer accepts new votes posted by other authorities. This
1475 change helps prevent a consensus split, where only some authorities
1476 have the late vote. Fixes bug 4631; bugfix on 0.2.0.5-alpha.
1478 o Minor bugfixes (git scripts):
1479 - Stop executing the checked-out pre-commit hook from the pre-push
1480 hook. Instead, execute the copy in the user's git directory. Fixes
1481 bug 33284; bugfix on 0.4.1.1-alpha.
1483 o Minor bugfixes (initialization):
1484 - Initialize the subsystems in our code in an order more closely
1485 corresponding to their dependencies, so that every system is
1486 initialized before the ones that (theoretically) depend on it.
1487 Fixes bug 33316; bugfix on 0.4.0.1-alpha.
1489 o Minor bugfixes (IPv4, relay):
1490 - Check for invalid zero IPv4 addresses and ports when sending and
1491 receiving extend cells. Fixes bug 33900; bugfix on 0.2.4.8-alpha.
1493 o Minor bugfixes (IPv6, relay):
1494 - Consider IPv6 addresses when checking if a connection is
1495 canonical. In 17604, relays assumed that a remote relay could
1496 consider an IPv6 connection canonical, but did not set the
1497 canonical flag on their side of the connection. Fixes bug 33899;
1498 bugfix on 0.3.1.1-alpha.
1499 - Log IPv6 addresses on connections where this relay is the
1500 responder. Previously, responding relays would replace the remote
1501 IPv6 address with the IPv4 address from the consensus. Fixes bug
1502 33899; bugfix on 0.3.1.1-alpha.
1504 o Minor bugfixes (linux seccomp sandbox nss):
1505 - Fix a startup crash when tor is compiled with --enable-nss and
1506 sandbox support is enabled. Fixes bug 34130; bugfix on
1507 0.3.5.1-alpha. Patch by Daniel Pinto.
1509 o Minor bugfixes (logging, testing):
1510 - Make all of tor's assertion macros support the ALL_BUGS_ARE_FATAL
1511 and DISABLE_ASSERTS_IN_UNIT_TESTS debugging modes. (IF_BUG_ONCE()
1512 used to log a non-fatal warning, regardless of the debugging
1513 mode.) Fixes bug 33917; bugfix on 0.2.9.1-alpha.
1515 o Minor bugfixes (logs):
1516 - Remove surprising empty line in the INFO-level log about circuit
1517 build timeout. Fixes bug 33531; bugfix on 0.3.3.1-alpha.
1519 o Minor bugfixes (mainloop):
1520 - Better guard against growing a buffer past its maximum 2GB in
1521 size. Fixes bug 33131; bugfix on 0.3.0.4-rc.
1523 o Minor bugfixes (manual page):
1524 - Update the man page to reflect that MinUptimeHidServDirectoryV2
1525 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
1527 o Minor bugfixes (onion service v3, client):
1528 - Remove a BUG() that was causing a stacktrace when a descriptor
1529 changed at an unexpected time. Fixes bug 28992; bugfix
1532 o Minor bugfixes (onion service, logging):
1533 - Fix a typo in a log message PublishHidServDescriptors is set to 0.
1534 Fixes bug 33779; bugfix on 0.3.2.1-alpha.
1536 o Minor bugfixes (portability):
1537 - Fix a portability error in the configure script, where we were
1538 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
1540 o Minor bugfixes (protocol versions):
1541 - Sort tor's supported protocol version lists, as recommended by the
1542 tor directory specification. Fixes bug 33285; bugfix
1545 o Minor bugfixes (relays):
1546 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
1547 descriptors, when the IPv6 port was configured as "auto". Fixes
1548 bug 32588; bugfix on 0.2.3.9-alpha.
1550 o Code simplification and refactoring:
1551 - Define and use a new constant TOR_ADDRPORT_BUF_LEN which is like
1552 TOR_ADDR_BUF_LEN but includes enough space for an IP address,
1553 brackets, separating colon, and port number. Closes ticket 33956.
1554 Patch by Neel Chauhan.
1555 - Merge the orconn and ocirc events into the "core" subsystem, which
1556 manages or connections and origin circuits. Previously they were
1557 isolated in subsystems of their own.
1558 - Move LOG_PROTOCOL_WARN to app/config. Resolves a dependency
1559 inversion. Closes ticket 33633.
1560 - Move the circuit extend code to the relay module. Split the
1561 circuit extend function into smaller functions. Closes
1563 - Rewrite port_parse_config() to use the default port flags from
1564 port_cfg_new(). Closes ticket 32994. Patch by MrSquanchee.
1565 - Updated comments in 'scheduler.c' to reflect old code changes, and
1566 simplified the scheduler channel state change code. Closes
1570 - Document the limitations of using %include on config files with
1571 seccomp sandbox enabled. Fixes documentation bug 34133; bugfix on
1572 0.3.1.1-alpha. Patch by Daniel Pinto.
1573 - Fix several doxygen warnings related to imbalanced groups. Closes
1577 - Remove the ClientAutoIPv6ORPort option. This option attempted to
1578 randomly choose between IPv4 and IPv6 for client connections, and
1579 wasn't a true implementation of Happy Eyeballs. Often, this option
1580 failed on IPv4-only or IPv6-only connections. Closes ticket 32905.
1581 Patch by Neel Chauhan.
1582 - Stop shipping contrib/dist/rc.subr file, as it is not being used
1583 on FreeBSD anymore. Closes issue 31576.
1586 - Add a basic IPv6 test to "make test-network". This test only runs
1587 when the local machine has an IPv6 stack. Closes ticket 33300.
1588 - Add test-network-ipv4 and test-network-ipv6 jobs to the Makefile.
1589 These jobs run the IPv4-only and dual-stack chutney flavours from
1590 test-network-all. Closes ticket 33280.
1591 - Remove a redundant distcheck job. Closes ticket 33194.
1592 - Run the test-network-ipv6 Makefile target in the Travis CI IPv6
1593 chutney job. This job runs on macOS, so it's a bit slow. Closes
1595 - Sort the Travis jobs in order of speed. Putting the slowest jobs
1596 first takes full advantage of Travis job concurrency. Closes
1598 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1599 previously configured to fast_finish (which requires
1600 allow_failure), to speed up the build. Closes ticket 33195.
1601 - Test v3 onion services to tor's mixed IPv4 chutney network. And
1602 add a mixed IPv6 chutney network. These networks are used in the
1603 test-network-all, test-network-ipv4, and test-network-ipv6 make
1604 targets. Closes ticket 33334.
1605 - Use the "bridges+hs-v23" chutney network flavour in "make test-
1606 network". This test requires a recent version of chutney (mid-
1607 February 2020). Closes ticket 28208.
1608 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1609 tool to produce detailed diagnostic output. Closes ticket 32792.
1611 o Code simplification and refactoring (onion service):
1612 - Refactor configuration parsing to use the new config subsystem
1613 code. Closes ticket 33014.
1615 o Code simplification and refactoring (relay address):
1616 - Move a series of functions related to address resolving into their
1617 own files. Closes ticket 33789.
1619 o Documentation (manual page):
1620 - Add cross reference links and a table of contents to the HTML tor
1621 manual page. Closes ticket 33369. Work by Swati Thacker as part of
1622 Google Season of Docs.
1623 - Alphabetize the Denial of Service Mitigation Options, Directory
1624 Authority Server Options, Hidden Service Options, and Testing
1625 Network Options sections of the tor(1) manual page. Closes ticket
1626 33275. Work by Swati Thacker as part of Google Season of Docs.
1627 - Refrain from mentioning nicknames in manpage section for MyFamily
1628 torrc option. Resolves issue 33417.
1629 - Updated the options set by TestingTorNetwork in the manual page.
1630 Closes ticket 33778.
1633 Changes in version 0.4.3.5 - 2020-05-15
1634 Tor 0.4.3.5 is the first stable release in the 0.4.3.x series. This
1635 series adds support for building without relay code enabled, and
1636 implements functionality needed for OnionBalance with v3 onion
1637 services. It includes significant refactoring of our configuration and
1638 controller functionality, and fixes numerous smaller bugs and
1641 Per our support policy, we support each stable release series for nine
1642 months after its first stable release, or three months after the first
1643 stable release of the next series: whichever is longer. This means
1644 that 0.4.3.x will be supported until around February 2021--later, if
1645 0.4.4.x is later than anticipated.
1647 Note also that support for 0.4.1.x is about to end on May 20 of this
1648 year; 0.4.2.x will be supported until September 15. We still plan to
1649 continue supporting 0.3.5.x, our long-term stable series, until
1652 Below are the changes since 0.4.3.4-rc. For a complete list of changes
1653 since 0.4.2.6, see the ReleaseNotes file.
1655 o Minor bugfixes (compiler compatibility):
1656 - Avoid compiler warnings from Clang 10 related to the use of GCC-
1657 style "/* falls through */" comments. Both Clang and GCC allow
1658 __attribute__((fallthrough)) instead, so that's what we're using
1659 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
1660 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
1663 o Minor bugfixes (logging):
1664 - Stop truncating IPv6 addresses and ports in channel and connection
1665 logs. Fixes bug 33918; bugfix on 0.2.4.4-alpha.
1666 - Fix a logic error in a log message about whether an address was
1667 invalid. Previously, the code would never report that onion
1668 addresses were onion addresses. Fixes bug 34131; bugfix
1672 Changes in version 0.4.3.4-rc - 2020-04-13
1673 Tor 0.4.3.4-rc is the first release candidate in its series. It fixes
1674 several bugs from earlier versions, including one affecting DoS
1675 defenses on bridges using pluggable transports.
1677 o Major bugfixes (DoS defenses, bridges, pluggable transport):
1678 - Fix a bug that was preventing DoS defenses from running on bridges
1679 with a pluggable transport. Previously, the DoS subsystem was not
1680 given the transport name of the client connection, thus failed to
1681 find the GeoIP cache entry for that client address. Fixes bug
1682 33491; bugfix on 0.3.3.2-alpha.
1684 o Minor feature (sendme, flow control):
1685 - Default to sending SENDME version 1 cells. (Clients are already
1686 sending these, because of a consensus parameter telling them to do
1687 so: this change only affects what clients would do if the
1688 consensus didn't contain a recommendation.) Closes ticket 33623.
1690 o Minor features (testing):
1691 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
1692 variable to specify a list of space-separated test cases that
1693 should not be executed. We will use this to disable certain tests
1694 that are failing on Appveyor because of mismatched OpenSSL
1695 libraries. Part of ticket 33643.
1697 o Minor bugfixes (--disable-module-relay):
1698 - Fix an assertion failure when Tor is built without the relay
1699 module, and then invoked with the "User" option. Fixes bug 33668;
1700 bugfix on 0.4.3.1-alpha.
1702 o Minor bugfixes (--disable-module-relay,--disable-module-dirauth):
1703 - Set some output arguments in the relay and dirauth module stubs,
1704 to guard against future stub argument handling bugs like 33668.
1705 Fixes bug 33674; bugfix on 0.4.3.1-alpha.
1707 o Minor bugfixes (build system):
1708 - Correctly output the enabled module in the configure summary.
1709 Before that, the list shown was just plain wrong. Fixes bug 33646;
1710 bugfix on 0.4.3.2-alpha.
1712 o Minor bugfixes (client, IPv6):
1713 - Stop forcing all non-SocksPorts to prefer IPv6 exit connections.
1714 Instead, prefer IPv6 connections by default, but allow users to
1715 change their configs using the "NoPreferIPv6" port flag. Fixes bug
1716 33608; bugfix on 0.4.3.1-alpha.
1717 - Revert PreferIPv6 set by default on the SocksPort because it broke
1718 the torsocks use case. Tor doesn't have a way for an application
1719 to request the hostname to be resolved for a specific IP version,
1720 but torsocks requires that. Up until now, IPv4 was used by default
1721 so torsocks is expecting that, and can't handle a possible IPv6
1722 being returned. Fixes bug 33804; bugfix on 0.4.3.1-alpha.
1724 o Minor bugfixes (key portability):
1725 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1726 if we are not running on Windows. Previously, non-Windows hosts
1727 would reject these line-endings in certain positions, making
1728 certain key files hard to move from one host to another. Fixes bug
1729 33032; bugfix on 0.3.5.1-alpha.
1731 o Minor bugfixes (logging):
1732 - Flush stderr, stdout, and file logs during shutdown, if supported
1733 by the OS. This change helps make sure that any final logs are
1734 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
1735 - Stop closing stderr and stdout during shutdown. Closing these file
1736 descriptors can hide sanitiser logs. Fixes bug 33087; bugfix
1739 o Minor bugfixes (onion services v3):
1740 - Relax severity of a log message that can appear naturally when
1741 decoding onion service descriptors as a relay. Also add some
1742 diagnostics to debug any future bugs in that area. Fixes bug
1743 31669; bugfix on 0.3.0.1-alpha.
1744 - Block a client-side assertion by disallowing the registration of
1745 an x25519 client auth key that's all zeroes. Fixes bug 33545;
1746 bugfix on 0.4.3.1-alpha. Based on patch from "cypherpunks".
1748 o Code simplification and refactoring:
1749 - Disable our coding standards best practices tracker in our git
1750 hooks. (0.4.3 branches only.) Closes ticket 33678.
1753 - Avoid conflicts between the fake sockets in tor's unit tests, and
1754 real file descriptors. Resolves issues running unit tests with
1755 GitHub Actions, where the process that embeds or launches the
1756 tests has already opened a large number of file descriptors. Fixes
1757 bug 33782; bugfix on 0.2.8.1-alpha. Found and fixed by
1761 - In our Appveyor Windows CI, copy required DLLs to test and app
1762 directories, before running tor's tests. This ensures that tor.exe
1763 and test*.exe use the correct version of each DLL. This fix is not
1764 required, but we hope it will avoid DLL search issues in future.
1765 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1766 - On Appveyor, skip the crypto/openssl_version test, which is
1767 failing because of a mismatched library installation. Fix
1771 Changes in version 0.4.3.3-alpha - 2020-03-18
1772 Tor 0.4.3.3-alpha fixes several bugs in previous releases, including
1773 TROVE-2020-002, a major denial-of-service vulnerability that affected
1774 all released Tor instances since 0.2.1.5-alpha. Using this
1775 vulnerability, an attacker could cause Tor instances to consume a huge
1776 amount of CPU, disrupting their operations for several seconds or
1777 minutes. This attack could be launched by anybody against a relay, or
1778 by a directory cache against any client that had connected to it. The
1779 attacker could launch this attack as much as they wanted, thereby
1780 disrupting service or creating patterns that could aid in traffic
1781 analysis. This issue was found by OSS-Fuzz, and is also tracked
1784 We do not have reason to believe that this attack is currently being
1785 exploited in the wild, but nonetheless we advise everyone to upgrade
1786 as soon as packages are available.
1788 o Major bugfixes (security, denial-of-service):
1789 - Fix a denial-of-service bug that could be used by anyone to
1790 consume a bunch of CPU on any Tor relay or authority, or by
1791 directories to consume a bunch of CPU on clients or hidden
1792 services. Because of the potential for CPU consumption to
1793 introduce observable timing patterns, we are treating this as a
1794 high-severity security issue. Fixes bug 33119; bugfix on
1795 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
1796 as TROVE-2020-002 and CVE-2020-10592.
1798 o Major bugfixes (circuit padding, memory leak):
1799 - Avoid a remotely triggered memory leak in the case that a circuit
1800 padding machine is somehow negotiated twice on the same circuit.
1801 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
1802 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
1804 o Major bugfixes (directory authority):
1805 - Directory authorities will now send a 503 (not enough bandwidth)
1806 code to clients when under bandwidth pressure. Known relays and
1807 other authorities will always be answered regardless of the
1808 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
1810 o Minor features (diagnostic):
1811 - Improve assertions and add some memory-poisoning code to try to
1812 track down possible causes of a rare crash (32564) in the EWMA
1813 code. Closes ticket 33290.
1815 o Minor features (directory authorities):
1816 - Directory authorities now reject descriptors from relays running
1817 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
1818 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
1820 o Minor features (usability):
1821 - Include more information when failing to parse a configuration
1822 value. This should make it easier to tell what's going wrong when
1823 a configuration file doesn't parse. Closes ticket 33460.
1825 o Minor bugfix (relay, configuration):
1826 - Warn if the ContactInfo field is not set, and tell the relay
1827 operator that not having a ContactInfo field set might cause their
1828 relay to get rejected in the future. Fixes bug 33361; bugfix
1831 o Minor bugfixes (coding best practices checks):
1832 - Allow the "practracker" script to read unicode files when using
1833 Python 2. We made the script use unicode literals in 0.4.3.1-alpha,
1834 but didn't change the codec for opening files. Fixes bug 33374;
1835 bugfix on 0.4.3.1-alpha.
1837 o Minor bugfixes (continuous integration):
1838 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
1841 o Minor bugfixes (onion service v3, client):
1842 - Remove a BUG() warning that would cause a stack trace if an onion
1843 service descriptor was freed while we were waiting for a
1844 rendezvous circuit to complete. Fixes bug 28992; bugfix
1847 o Minor bugfixes (onion services v3):
1848 - Fix an assertion failure that could result from a corrupted
1849 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1850 bugfix on 0.3.3.1-alpha. This issue is also tracked
1853 o Documentation (manpage):
1854 - Alphabetize the Server and Directory server sections of the tor
1855 manpage. Also split Statistics options into their own section of
1856 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
1857 Google Season of Docs.
1858 - Document the __OwningControllerProcess torrc option and specify
1859 its polling interval. Resolves issue 32971.
1861 o Testing (Travis CI):
1862 - Remove a redundant distcheck job. Closes ticket 33194.
1863 - Sort the Travis jobs in order of speed: putting the slowest jobs
1864 first takes full advantage of Travis job concurrency. Closes
1866 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1867 previously configured to fast_finish (which requires
1868 allow_failure), to speed up the build. Closes ticket 33195.
1869 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1870 tool to produce detailed diagnostic output. Closes ticket 32792.
1873 Changes in version 0.4.2.7 - 2020-03-18
1874 This is the third stable release in the 0.4.2.x series. It backports
1875 numerous fixes from later releases, including a fix for TROVE-2020-
1876 002, a major denial-of-service vulnerability that affected all
1877 released Tor instances since 0.2.1.5-alpha. Using this vulnerability,
1878 an attacker could cause Tor instances to consume a huge amount of CPU,
1879 disrupting their operations for several seconds or minutes. This
1880 attack could be launched by anybody against a relay, or by a directory
1881 cache against any client that had connected to it. The attacker could
1882 launch this attack as much as they wanted, thereby disrupting service
1883 or creating patterns that could aid in traffic analysis. This issue
1884 was found by OSS-Fuzz, and is also tracked as CVE-2020-10592.
1886 We do not have reason to believe that this attack is currently being
1887 exploited in the wild, but nonetheless we advise everyone to upgrade
1888 as soon as packages are available.
1890 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
1891 - Fix a denial-of-service bug that could be used by anyone to
1892 consume a bunch of CPU on any Tor relay or authority, or by
1893 directories to consume a bunch of CPU on clients or hidden
1894 services. Because of the potential for CPU consumption to
1895 introduce observable timing patterns, we are treating this as a
1896 high-severity security issue. Fixes bug 33119; bugfix on
1897 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
1898 as TROVE-2020-002 and CVE-2020-10592.
1900 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
1901 - Avoid a remotely triggered memory leak in the case that a circuit
1902 padding machine is somehow negotiated twice on the same circuit.
1903 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
1904 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
1906 o Major bugfixes (directory authority, backport from 0.4.3.3-alpha):
1907 - Directory authorities will now send a 503 (not enough bandwidth)
1908 code to clients when under bandwidth pressure. Known relays and
1909 other authorities will always be answered regardless of the
1910 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
1912 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
1913 - Stop allowing failures on the Travis CI stem tests job. It looks
1914 like all the stem hangs we were seeing before are now fixed.
1915 Closes ticket 33075.
1917 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
1918 - Lowercase the configured value of BridgeDistribution before adding
1919 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
1921 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
1922 - If we encounter a bug when flushing a buffer to a TLS connection,
1923 only log the bug once per invocation of the Tor process.
1924 Previously we would log with every occurrence, which could cause
1925 us to run out of disk space. Fixes bug 33093; bugfix
1928 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
1929 - Fix an assertion failure that could result from a corrupted
1930 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1931 bugfix on 0.3.3.1-alpha. This issue is also tracked
1934 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
1935 - Fix a syntax warning given by newer versions of Rust that was
1936 creating problems for our continuous integration. Fixes bug 33212;
1937 bugfix on 0.3.5.1-alpha.
1939 o Testing (Travis CI, backport from 0.4.3.3-alpha):
1940 - Remove a redundant distcheck job. Closes ticket 33194.
1941 - Sort the Travis jobs in order of speed: putting the slowest jobs
1942 first takes full advantage of Travis job concurrency. Closes
1944 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1945 previously configured to fast_finish (which requires
1946 allow_failure), to speed up the build. Closes ticket 33195.
1947 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1948 tool to produce detailed diagnostic output. Closes ticket 32792.
1951 Changes in version 0.4.1.9 - 2020-03-18
1952 Tor 0.4.1.9 backports important fixes from later Tor releases,
1953 including a fix for TROVE-2020-002, a major denial-of-service
1954 vulnerability that affected all released Tor instances since
1955 0.2.1.5-alpha. Using this vulnerability, an attacker could cause Tor
1956 instances to consume a huge amount of CPU, disrupting their operations
1957 for several seconds or minutes. This attack could be launched by
1958 anybody against a relay, or by a directory cache against any client
1959 that had connected to it. The attacker could launch this attack as
1960 much as they wanted, thereby disrupting service or creating patterns
1961 that could aid in traffic analysis. This issue was found by OSS-Fuzz,
1962 and is also tracked as CVE-2020-10592.
1964 We do not have reason to believe that this attack is currently being
1965 exploited in the wild, but nonetheless we advise everyone to upgrade
1966 as soon as packages are available.
1968 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
1969 - Fix a denial-of-service bug that could be used by anyone to
1970 consume a bunch of CPU on any Tor relay or authority, or by
1971 directories to consume a bunch of CPU on clients or hidden
1972 services. Because of the potential for CPU consumption to
1973 introduce observable timing patterns, we are treating this as a
1974 high-severity security issue. Fixes bug 33119; bugfix on
1975 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
1976 as TROVE-2020-002 and CVE-2020-10592.
1978 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
1979 - Avoid a remotely triggered memory leak in the case that a circuit
1980 padding machine is somehow negotiated twice on the same circuit.
1981 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
1982 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
1984 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
1985 - Lowercase the configured value of BridgeDistribution before adding
1986 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
1988 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
1989 - If we encounter a bug when flushing a buffer to a TLS connection,
1990 only log the bug once per invocation of the Tor process.
1991 Previously we would log with every occurrence, which could cause
1992 us to run out of disk space. Fixes bug 33093; bugfix
1995 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
1996 - Fix an assertion failure that could result from a corrupted
1997 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1998 bugfix on 0.3.3.1-alpha. This issue is also tracked
2001 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2002 - Fix a syntax warning given by newer versions of Rust that was
2003 creating problems for our continuous integration. Fixes bug 33212;
2004 bugfix on 0.3.5.1-alpha.
2006 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2007 - Remove a redundant distcheck job. Closes ticket 33194.
2008 - Sort the Travis jobs in order of speed: putting the slowest jobs
2009 first takes full advantage of Travis job concurrency. Closes
2011 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2012 previously configured to fast_finish (which requires
2013 allow_failure), to speed up the build. Closes ticket 33195.
2014 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2015 tool to produce detailed diagnostic output. Closes ticket 32792.
2018 Changes in version 0.3.5.10 - 2020-03-18
2019 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
2020 fix for TROVE-2020-002, a major denial-of-service vulnerability that
2021 affected all released Tor instances since 0.2.1.5-alpha. Using this
2022 vulnerability, an attacker could cause Tor instances to consume a huge
2023 amount of CPU, disrupting their operations for several seconds or
2024 minutes. This attack could be launched by anybody against a relay, or
2025 by a directory cache against any client that had connected to it. The
2026 attacker could launch this attack as much as they wanted, thereby
2027 disrupting service or creating patterns that could aid in traffic
2028 analysis. This issue was found by OSS-Fuzz, and is also tracked
2031 We do not have reason to believe that this attack is currently being
2032 exploited in the wild, but nonetheless we advise everyone to upgrade
2033 as soon as packages are available.
2035 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2036 - Fix a denial-of-service bug that could be used by anyone to
2037 consume a bunch of CPU on any Tor relay or authority, or by
2038 directories to consume a bunch of CPU on clients or hidden
2039 services. Because of the potential for CPU consumption to
2040 introduce observable timing patterns, we are treating this as a
2041 high-severity security issue. Fixes bug 33119; bugfix on
2042 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2043 as TROVE-2020-002 and CVE-2020-10592.
2045 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2046 - Correct how we use libseccomp. Particularly, stop assuming that
2047 rules are applied in a particular order or that more rules are
2048 processed after the first match. Neither is the case! In
2049 libseccomp <2.4.0 this lead to some rules having no effect.
2050 libseccomp 2.4.0 changed how rules are generated, leading to a
2051 different ordering, which in turn led to a fatal crash during
2052 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2055 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
2056 - Stop allowing failures on the Travis CI stem tests job. It looks
2057 like all the stem hangs we were seeing before are now fixed.
2058 Closes ticket 33075.
2060 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2061 - Lowercase the configured value of BridgeDistribution before adding
2062 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2064 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
2065 - When running Tor with an option like --verify-config or
2066 --dump-config that does not start the event loop, avoid crashing
2067 if we try to exit early because of an error. Fixes bug 32407;
2068 bugfix on 0.3.3.1-alpha.
2070 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2071 - If we encounter a bug when flushing a buffer to a TLS connection,
2072 only log the bug once per invocation of the Tor process.
2073 Previously we would log with every occurrence, which could cause
2074 us to run out of disk space. Fixes bug 33093; bugfix
2077 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2078 - Fix an assertion failure that could result from a corrupted
2079 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2080 bugfix on 0.3.3.1-alpha. This issue is also tracked
2083 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2084 - Fix a syntax warning given by newer versions of Rust that was
2085 creating problems for our continuous integration. Fixes bug 33212;
2086 bugfix on 0.3.5.1-alpha.
2088 o Testing (backport from 0.4.3.1-alpha):
2089 - Re-enable the Travis CI macOS Chutney build, but don't let it
2090 prevent the Travis job from finishing. (The Travis macOS jobs are
2091 slow, so we don't want to have it delay the whole CI process.)
2092 Closes ticket 32629.
2093 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2094 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2095 fix the sandbox errors in 32722. Closes ticket 32240.
2097 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2098 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2100 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2101 - Remove a redundant distcheck job. Closes ticket 33194.
2102 - Sort the Travis jobs in order of speed: putting the slowest jobs
2103 first takes full advantage of Travis job concurrency. Closes
2105 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2106 previously configured to fast_finish (which requires
2107 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2108 tool to produce detailed diagnostic output. Closes ticket 32792.
2111 Changes in version 0.4.3.2-alpha - 2020-02-10
2112 This is the second stable alpha release in the Tor 0.4.3.x series. It
2113 fixes several bugs present in the previous alpha release. Anybody
2114 running the previous alpha should upgrade, and look for bugs in this
2117 o Major bugfixes (onion service client, authorization):
2118 - On a NEWNYM signal, purge entries from the ephemeral client
2119 authorization cache. The permanent ones are kept. Fixes bug 33139;
2120 bugfix on 0.4.3.1-alpha.
2122 o Minor features (best practices tracker):
2123 - Practracker now supports a --regen-overbroad option to regenerate
2124 the exceptions file, but only to revise exceptions to be _less_
2125 tolerant of best-practices violations. Closes ticket 32372.
2127 o Minor features (continuous integration):
2128 - Run Doxygen Makefile target on Travis, so we can learn about
2129 regressions in our internal documentation. Closes ticket 32455.
2130 - Stop allowing failures on the Travis CI stem tests job. It looks
2131 like all the stem hangs we were seeing before are now fixed.
2132 Closes ticket 33075.
2134 o Minor bugfixes (build system):
2135 - Revise configure options that were either missing or incorrect in
2136 the configure summary. Fixes bug 32230; bugfix on 0.4.3.1-alpha.
2138 o Minor bugfixes (controller protocol):
2139 - Fix a memory leak introduced by refactoring of control reply
2140 formatting code. Fixes bug 33039; bugfix on 0.4.3.1-alpha.
2141 - Fix a memory leak in GETINFO responses. Fixes bug 33103; bugfix
2143 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
2144 report them as SIGNAL events. Previously we would log a bug
2145 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
2147 o Minor bugfixes (logging):
2148 - If we encounter a bug when flushing a buffer to a TLS connection,
2149 only log the bug once per invocation of the Tor process.
2150 Previously we would log with every occurrence, which could cause
2151 us to run out of disk space. Fixes bug 33093; bugfix
2153 - When logging a bug, do not say "Future instances of this warning
2154 will be silenced" unless we are actually going to silence them.
2155 Previously we would say this whenever a BUG() check failed in the
2156 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
2158 o Minor bugfixes (onion service v2):
2159 - Move a series of v2 onion service warnings to protocol-warning
2160 level because they can all be triggered remotely by a malformed
2161 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
2163 o Minor bugfixes (onion service v3, client authorization):
2164 - When removing client authorization credentials using the control
2165 port, also remove the associated descriptor, so the onion service
2166 can no longer be contacted. Fixes bug 33148; bugfix
2169 o Minor bugfixes (pluggable transports):
2170 - When receiving a message on standard error from a pluggable
2171 transport, log it at info level, rather than as a warning. Fixes
2172 bug 33005; bugfix on 0.4.0.1-alpha.
2174 o Minor bugfixes (rust, build):
2175 - Fix a syntax warning given by newer versions of Rust that was
2176 creating problems for our continuous integration. Fixes bug 33212;
2177 bugfix on 0.3.5.1-alpha.
2179 o Minor bugfixes (TLS bug handling):
2180 - When encountering a bug in buf_read_from_tls(), return a "MISC"
2181 error code rather than "WANTWRITE". This change might help avoid
2182 some CPU-wasting loops if the bug is ever triggered. Bug reported
2183 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
2185 o Code simplification and refactoring (mainloop):
2186 - Simplify the ip_address_changed() function by removing redundant
2187 checks. Closes ticket 33091.
2189 o Documentation (manpage):
2190 - Split "Circuit Timeout" options and "Node Selection" options into
2191 their own sections of the tor manpage. Closes tickets 32928 and
2192 32929. Work by Swati Thacker as part of Google Season of Docs.
2195 Changes in version 0.4.2.6 - 2020-01-30
2196 This is the second stable release in the 0.4.2.x series. It backports
2197 several bugfixes from 0.4.3.1-alpha, including some that had affected
2198 the Linux seccomp2 sandbox or Windows services. If you're running with
2199 one of those configurations, you'll probably want to upgrade;
2200 otherwise, you should be fine with 0.4.2.5.
2202 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2203 - Correct how we use libseccomp. Particularly, stop assuming that
2204 rules are applied in a particular order or that more rules are
2205 processed after the first match. Neither is the case! In
2206 libseccomp <2.4.0 this led to some rules having no effect.
2207 libseccomp 2.4.0 changed how rules are generated, leading to a
2208 different ordering, which in turn led to a fatal crash during
2209 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2211 - Fix crash when reloading logging configuration while the
2212 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2213 0.4.1.7. Patch by Peter Gerber.
2215 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
2216 - Use GCC/Clang's printf-checking feature to make sure that
2217 tor_assertf() arguments are correctly typed. Fixes bug 32765;
2218 bugfix on 0.4.1.1-alpha.
2220 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
2221 - Avoid a possible crash when trying to log a (fatal) assertion
2222 failure about mismatched magic numbers in configuration objects.
2223 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
2225 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
2226 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
2227 test_practracker.sh script. Doing so caused a test failure. Fixes
2228 bug 32705; bugfix on 0.4.2.1-alpha.
2229 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
2230 skipping practracker checks. Fixes bug 32705; bugfix
2233 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
2234 - Initialize the publish/subscribe system when running as a windows
2235 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
2237 o Testing (backport from 0.4.3.1-alpha):
2238 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2239 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2240 fix the sandbox errors in 32722. Closes ticket 32240.
2241 - Re-enable the Travis CI macOS Chutney build, but don't let it
2242 prevent the Travis job from finishing. (The Travis macOS jobs are
2243 slow, so we don't want to have it delay the whole CI process.)
2244 Closes ticket 32629.
2246 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2247 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2250 Changes in version 0.4.1.8 - 2020-01-30
2251 This release backports several bugfixes from later release series,
2252 including some that had affected the Linux seccomp2 sandbox or Windows
2253 services. If you're running with one of those configurations, you'll
2254 probably want to upgrade; otherwise, you should be fine with your
2255 current version of 0.4.1.x.
2257 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2258 - Correct how we use libseccomp. Particularly, stop assuming that
2259 rules are applied in a particular order or that more rules are
2260 processed after the first match. Neither is the case! In
2261 libseccomp <2.4.0 this led to some rules having no effect.
2262 libseccomp 2.4.0 changed how rules are generated, leading to a
2263 different ordering, which in turn led to a fatal crash during
2264 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2266 - Fix crash when reloading logging configuration while the
2267 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2268 0.4.1.7. Patch by Peter Gerber.
2270 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
2271 - When running Tor with an option like --verify-config or
2272 --dump-config that does not start the event loop, avoid crashing
2273 if we try to exit early because of an error. Fixes bug 32407;
2274 bugfix on 0.3.3.1-alpha.
2276 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
2277 - Initialize the publish/subscribe system when running as a windows
2278 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
2280 o Testing (backport from 0.4.3.1-alpha):
2281 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2282 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2283 fix the sandbox errors in 32722. Closes ticket 32240.
2284 - Re-enable the Travis CI macOS Chutney build, but don't let it
2285 prevent the Travis job from finishing. (The Travis macOS jobs are
2286 slow, so we don't want to have it delay the whole CI process.)
2287 Closes ticket 32629.
2289 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2290 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2293 Changes in version 0.4.3.1-alpha - 2020-01-22
2294 This is the first alpha release in the 0.4.3.x series. It includes
2295 improved support for application integration of onion services, support
2296 for building in a client-only mode, and newly improved internal
2297 documentation (online at https://src-ref.docs.torproject.org/tor/). It
2298 also has numerous other small bugfixes and features, as well as
2299 improvements to our code's internal organization that should help us
2300 write better code in the future.
2302 o New system requirements:
2303 - When building Tor, you now need to have Python 3 in order to run
2304 the integration tests. (Python 2 is officially unsupported
2305 upstream, as of 1 Jan 2020.) Closes ticket 32608.
2307 o Major features (build system):
2308 - The relay code can now be disabled using the --disable-module-relay
2309 configure option. When this option is set, we also disable the
2310 dirauth module. Closes ticket 32123.
2311 - When Tor is compiled --disable-module-relay, we also omit the code
2312 used to act as a directory cache. Closes ticket 32487.
2314 o Major features (directory authority, ed25519):
2315 - Add support for banning a relay's ed25519 keys in the approved-
2316 routers file. This will help us migrate away from RSA keys in the
2317 future. Previously, only RSA keys could be banned in approved-
2318 routers. Resolves ticket 22029. Patch by Neel Chauhan.
2320 o Major features (onion service, controller):
2321 - New control port commands to manage client-side onion service
2322 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
2323 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
2324 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
2326 o Major features (onion service, SOCKS5):
2327 - Introduce a new SocksPort flag, ExtendedErrors, to support more
2328 detailed error codes in information for applications that support
2329 them. Closes ticket 30382; implements proposal 304.
2331 o Major features (proxy):
2332 - In addition to its current supported proxy types (HTTP CONNECT,
2333 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
2334 HAProxy server. A new torrc option was added to specify the
2335 address/port of the server: TCPProxy <protocol> <host>:<port>.
2336 Currently the only supported protocol for the option is haproxy.
2337 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
2339 o Major bugfixes (linux seccomp sandbox):
2340 - Correct how we use libseccomp. Particularly, stop assuming that
2341 rules are applied in a particular order or that more rules are
2342 processed after the first match. Neither is the case! In
2343 libseccomp <2.4.0 this led to some rules having no effect.
2344 libseccomp 2.4.0 changed how rules are generated, leading to a
2345 different ordering, which in turn led to a fatal crash during
2346 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2348 - Fix crash when reloading logging configuration while the
2349 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2350 0.4.1.7. Patch by Peter Gerber.
2352 o Major bugfixes (networking):
2353 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
2354 and accept strings as well as binary addresses. Fixes bug 32315;
2355 bugfix on 0.3.5.1-alpha.
2357 o Major bugfixes (onion service):
2358 - Report HS circuit failure back into the HS subsystem so we take
2359 appropriate action with regards to the client introduction point
2360 failure cache. This improves reachability of onion services, since
2361 now clients notice failing introduction circuits properly. Fixes
2362 bug 32020; bugfix on 0.3.2.1-alpha.
2364 o Minor feature (configure, build system):
2365 - Output a list of enabled/disabled features at the end of the
2366 configure process in a pleasing way. Closes ticket 31373.
2368 o Minor feature (heartbeat, onion service):
2369 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
2370 message. Closes ticket 31371.
2372 o Minor features (configuration validation):
2373 - Configuration validation can now be done by per-module callbacks,
2374 rather than a global validation function. This will let us reduce
2375 the size of config.c and some of its more cumbersome functions.
2376 Closes ticket 31241.
2378 o Minor features (configuration):
2379 - If a configured hardware crypto accelerator in AccelName is
2380 prefixed with "!", Tor now exits when it cannot be found. Closes
2382 - We now use flag-driven logic to warn about obsolete configuration
2383 fields, so that we can include their names. In 0.4.2, we used a
2384 special type, which prevented us from generating good warnings.
2385 Implements ticket 32404.
2387 o Minor features (controller):
2388 - Add stream isolation data to STREAM event. Closes ticket 19859.
2389 - Implement a new GETINFO command to fetch microdescriptor
2390 consensus. Closes ticket 31684.
2392 o Minor features (debugging, directory system):
2393 - Don't crash when we find a non-guard with a guard-fraction value
2394 set. Instead, log a bug warning, in an attempt to figure out how
2395 this happened. Diagnostic for ticket 32868.
2397 o Minor features (defense in depth):
2398 - Add additional checks around tor_vasprintf() usage, in case the
2399 function returns an error. Patch by Tobias Stoeckmann. Fixes
2402 o Minor features (developer tooling):
2403 - Remove the 0.2.9.x series branches from git scripts (git-merge-
2404 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
2405 Closes ticket 32772.
2407 o Minor features (developer tools):
2408 - Add a check_cocci_parse.sh script that checks that new code is
2409 parseable by Coccinelle. Add an exceptions file for unparseable
2410 files, and run the script from travis CI. Closes ticket 31919.
2411 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
2412 target. Closes ticket 31919.
2413 - Add a rename_c_identifiers.py tool to rename a bunch of C
2414 identifiers at once, and generate a well-formed commit message
2415 describing the change. This should help with refactoring. Closes
2417 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
2418 semantic patching tool with the correct flags. These flags are
2419 fairly easy to forget, and these scripts should help us use
2420 Coccinelle more effectively in the future. Closes ticket 31705.
2422 o Minor features (Doxygen):
2423 - Update Doxygen configuration file to a more recent template (from
2424 1.8.15). Closes ticket 32110.
2425 - "make doxygen" now works with out-of-tree builds. Closes
2427 - Make sure that doxygen outputs documentation for all of our C
2428 files. Previously, some were missing @file declarations, causing
2429 them to be ignored. Closes ticket 32307.
2430 - Our "make doxygen" target now respects --enable-fatal-warnings by
2431 default, and does not warn about items that are missing
2432 documentation. To warn about missing documentation, run configure
2433 with the "--enable-missing-doc-warnings" flag: doing so suspends
2434 fatal warnings for doxygen. Closes ticket 32385.
2436 o Minor features (git scripts):
2437 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
2438 customisation. Closes ticket 32347.
2439 - Add git-setup-dirs.sh, which sets up an upstream git repository
2440 and worktrees for tor maintainers. Closes ticket 29603.
2441 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
2442 remote. Closes ticket 32347.
2443 - Call the check_cocci_parse.sh script from the git commit and push
2444 hooks. Closes ticket 31919.
2445 - Make git-push-all.sh skip unchanged branches when pushing to
2446 upstream. The script already skipped unchanged test branches.
2447 Closes ticket 32216.
2448 - Make git-setup-dirs.sh create a master symlink in the worktree
2449 directory. Closes ticket 32347.
2450 - Skip unmodified source files when doing some existing git hook
2451 checks. Related to ticket 31919.
2453 o Minor features (IPv6, client):
2454 - Make Tor clients tell dual-stack exits that they prefer IPv6
2455 connections. This change is equivalent to setting the PreferIPv6
2456 flag on SOCKSPorts (and most other listener ports). Tor Browser
2457 has been setting this flag for some time, and we want to remove a
2458 client distinguisher at exits. Closes ticket 32637.
2460 o Minor features (portability, android):
2461 - When building for Android, disable some tests that depend on $HOME
2462 and/or pwdb, which Android doesn't have. Closes ticket 32825.
2463 Patch from Hans-Christoph Steiner.
2465 o Minor features (relay modularity):
2466 - Split the relay and server pluggable transport config code into
2467 separate files in the relay module. Disable this code when the
2468 relay module is disabled. Closes part of ticket 32213.
2469 - When the relay module is disabled, reject attempts to set the
2470 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
2471 ServerTransport* options, rather than ignoring the values of these
2472 options. Closes part of ticket 32213.
2474 o Minor features (relay):
2475 - When the relay module is disabled, change the default config so
2476 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
2478 o Minor features (release tools):
2479 - Port our ChangeLog formatting and sorting tools to Python 3.
2480 Closes ticket 32704.
2482 o Minor features (testing):
2483 - Detect some common failure cases for test_parseconf.sh in
2484 src/test/conf_failures. Closes ticket 32451.
2485 - Allow test_parseconf.sh to test expected log outputs for successful
2486 configs, as well as failed configs. Closes ticket 32451.
2487 - The test_parseconf.sh script now supports result variants for any
2488 combination of the optional libraries lzma, nss, and zstd. Closes
2491 o Minor features (tests, Android):
2492 - When running the unit tests on Android, create temporary files in
2493 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
2494 patch from Hans-Christoph Steiner.
2496 o Minor bugfixes (bridges):
2497 - Lowercase the configured value of BridgeDistribution before adding
2498 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2500 o Minor bugfixes (build system):
2501 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
2502 bugfix on 0.4.1.2-alpha.
2504 o Minor bugfixes (configuration handling):
2505 - Make control_event_conf_changed() take in a config_line_t instead
2506 of a smartlist of alternating key/value entries. Fixes bug 31531;
2507 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
2509 o Minor bugfixes (configuration):
2510 - Check for multiplication overflow when parsing memory units inside
2511 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
2512 - When dumping the configuration, stop adding a trailing space after
2513 the option name when there is no option value. This issue only
2514 affects options that accept an empty value or list. (Most options
2515 reject empty values, or delete the entire line from the dumped
2516 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
2517 - Avoid changing the user's value of HardwareAccel as stored by
2518 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
2519 bug 32382; bugfix on 0.2.2.1-alpha.
2520 - When creating a KeyDirectory with the same location as the
2521 DataDirectory (not recommended), respect the DataDirectory's
2522 group-readable setting if one has not been set for the
2523 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
2525 o Minor bugfixes (controller):
2526 - In routerstatus_has_changed(), check all the fields that are
2527 output over the control port. Fixes bug 20218; bugfix
2530 o Minor bugfixes (correctness checks):
2531 - Use GCC/Clang's printf-checking feature to make sure that
2532 tor_assertf() arguments are correctly typed. Fixes bug 32765;
2533 bugfix on 0.4.1.1-alpha.
2535 o Minor bugfixes (developer tools):
2536 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
2537 31336; bugfix on 0.4.1.2-alpha.
2539 o Minor bugfixes (dirauth module):
2540 - Split the dirauth config code into a separate file in the dirauth
2541 module. Disable this code when the dirauth module is disabled.
2542 Closes ticket 32213.
2543 - When the dirauth module is disabled, reject attempts to set the
2544 AuthoritativeDir option, rather than ignoring the value of the
2545 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
2547 o Minor bugfixes (embedded Tor):
2548 - When starting Tor any time after the first time in a process,
2549 register the thread in which it is running as the main thread.
2550 Previously, we only did this on Windows, which could lead to bugs
2551 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
2554 o Minor bugfixes (git scripts):
2555 - Avoid sleeping before the last push in git-push-all.sh. Closes
2557 - Forward all unrecognised arguments in git-push-all.sh to git push.
2558 Closes ticket 32216.
2560 o Minor bugfixes (hidden service v3):
2561 - Do not rely on a "circuit established" flag for intro circuits but
2562 instead always query the HS circuit map. This is to avoid sync
2563 issue with that flag and the map. Fixes bug 32094; bugfix
2566 o Minor bugfixes (logging, crash):
2567 - Avoid a possible crash when trying to log a (fatal) assertion
2568 failure about mismatched magic numbers in configuration objects.
2569 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
2571 o Minor bugfixes (onion service v2):
2572 - When sending the INTRO cell for a v2 Onion Service, look at the
2573 failure cache alongside timeout values to check if the intro point
2574 is marked as failed. Previously, we only looked at the relay
2575 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
2578 o Minor bugfixes (onion services v3, client):
2579 - Properly handle the client rendezvous circuit timeout. Previously
2580 Tor would sometimes timeout a rendezvous circuit awaiting the
2581 introduction ACK, and find itself unable to re-establish all
2582 circuits because the rendezvous circuit timed out too early. Fixes
2583 bug 32021; bugfix on 0.3.2.1-alpha.
2585 o Minor bugfixes (onion services):
2586 - In cancel_descriptor_fetches(), use
2587 connection_list_by_type_purpose() instead of
2588 connection_list_by_type_state(). Fixes bug 32639; bugfix on
2589 0.3.2.1-alpha. Patch by Neel Chauhan.
2591 o Minor bugfixes (scripts):
2592 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
2593 bugfix on 0.4.0.1-alpha.
2595 o Minor bugfixes (test):
2596 - Use the same code to find the tor binary in all of our test
2597 scripts. This change makes sure we are always using the coverage
2598 binary when coverage is enabled. Fixes bug 32368; bugfix
2601 o Minor bugfixes (testing):
2602 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
2603 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
2604 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
2605 test_practracker.sh script. Doing so caused a test failure. Fixes
2606 bug 32705; bugfix on 0.4.2.1-alpha.
2607 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
2608 skipping practracker checks. Fixes bug 32705; bugfix
2611 o Minor bugfixes (tests):
2612 - Our option-validation tests no longer depend on specially
2613 configured non-default, non-passing sets of options. Previously,
2614 the tests had been written to assume that options would _not_ be
2615 set to their defaults, which led to needless complexity and
2616 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
2618 o Minor bugfixes (windows service):
2619 - Initialize the publish/subscribe system when running as a windows
2620 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
2622 o Deprecated features:
2623 - Deprecate the ClientAutoIPv6ORPort option. This option was not
2624 true "Happy Eyeballs", and often failed on connections that
2625 weren't reliably dual-stack. Closes ticket 32942. Patch by
2629 - Provide a quickstart guide for a Circuit Padding Framework, and
2630 documentation for researchers to implement and study circuit
2631 padding machines. Closes ticket 28804.
2632 - Add documentation in 'HelpfulTools.md' to describe how to build a
2633 tag file. Closes ticket 32779.
2634 - Create a high-level description of the long-term software
2635 architecture goals. Closes ticket 32206.
2636 - Describe the --dump-config command in the manual page. Closes
2638 - Unite coding advice from this_not_that.md in torguts repo into our
2639 coding standards document. Resolves ticket 31853.
2642 - Our Doxygen configuration no longer generates LaTeX output. The
2643 reference manual produced by doing this was over 4000 pages long,
2644 and generally unusable. Closes ticket 32099.
2645 - The option "TestingEstimatedDescriptorPropagationTime" is now
2646 marked as obsolete. It has had no effect since 0.3.0.7, when
2647 clients stopped rejecting consensuses "from the future". Closes
2649 - We no longer support consensus methods before method 28; these
2650 methods were only used by authorities running versions of Tor that
2651 are now at end-of-life. In effect, this means that clients,
2652 relays, and authorities now assume that authorities will be
2653 running version 0.3.5.x or later. Closes ticket 32695.
2656 - Add more test cases for tor's UTF-8 validation function. Also,
2657 check the arguments passed to the function for consistency. Closes
2659 - Improve test coverage for relay and dirauth config code, focusing
2660 on option validation and normalization. Closes ticket 32213.
2661 - Improve the consistency of test_parseconf.sh output, and run all
2662 the tests, even if one fails. Closes ticket 32213.
2663 - Re-enable the Travis CI macOS Chutney build, but don't let it
2664 prevent the Travis job from finishing. (The Travis macOS jobs are
2665 slow, so we don't want to have it delay the whole CI process.)
2666 Closes ticket 32629.
2667 - Run the practracker unit tests in the pre-commit git hook. Closes
2669 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2670 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2671 fix the sandbox errors in 32722. Closes ticket 32240.
2673 o Code simplification and refactoring (channel):
2674 - Channel layer had a variable length cell handler that was not used
2675 and thus removed. Closes ticket 32892.
2677 o Code simplification and refactoring (configuration):
2678 - Immutability is now implemented as a flag on individual
2679 configuration options rather than as part of the option-transition
2680 checking code. Closes ticket 32344.
2681 - Instead of keeping a list of configuration options to check for
2682 relative paths, check all the options whose type is "FILENAME".
2683 Solves part of ticket 32339.
2684 - Our default log (which ordinarily sends NOTICE-level messages to
2685 standard output) is now handled in a more logical manner.
2686 Previously, we replaced the configured log options if they were
2687 empty. Now, we interpret an empty set of log options as meaning
2688 "use the default log". Closes ticket 31999.
2689 - Remove some unused arguments from the options_validate() function,
2690 to simplify our code and tests. Closes ticket 32187.
2691 - Simplify the options_validate() code so that it looks at the
2692 default options directly, rather than taking default options as an
2693 argument. This change lets us simplify its interface. Closes
2695 - Use our new configuration architecture to move most authority-
2696 related options to the directory authority module. Closes
2698 - When parsing the command line, handle options that determine our
2699 "quiet level" and our mode of operation (e.g., --dump-config and
2700 so on) all in one table. Closes ticket 32003.
2702 o Code simplification and refactoring (controller):
2703 - Create a new abstraction for formatting control protocol reply
2704 lines based on key-value pairs. Refactor some existing control
2705 protocol code to take advantage of this. Closes ticket 30984.
2706 - Create a helper function that can fetch network status or
2707 microdesc consensuses. Closes ticket 31684.
2709 o Code simplification and refactoring (dirauth modularization):
2710 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
2711 Closes ticket 32163.
2712 - Replace some confusing identifiers in process_descs.c. Closes
2714 - Simplify some relay and dirauth config code. Closes ticket 32213.
2716 o Code simplification and refactoring (misc):
2717 - Make all the structs we declare follow the same naming convention
2718 of ending with "_t". Closes ticket 32415.
2719 - Move and rename some configuration-related code for clarity.
2720 Closes ticket 32304.
2721 - Our include.am files are now broken up by subdirectory.
2722 Previously, src/core/include.am covered all of the subdirectories
2723 in "core", "feature", and "app". Closes ticket 32137.
2724 - Remove underused NS*() macros from test code: they make our tests
2725 more confusing, especially for code-formatting tools. Closes
2728 o Code simplification and refactoring (relay modularization):
2729 - Disable relay_periodic when the relay module is disabled. Closes
2731 - Disable relay_sys when the relay module is disabled. Closes
2734 o Code simplification and refactoring (tool support):
2735 - Add numerous missing dependencies to our include files, so that
2736 they can be included in different reasonable orders and still
2737 compile. Addresses part of ticket 32764.
2738 - Fix some parts of our code that were difficult for Coccinelle to
2739 parse. Related to ticket 31705.
2740 - Fix some small issues in our code that prevented automatic
2741 formatting tools from working. Addresses part of ticket 32764.
2743 o Documentation (manpage):
2744 - Alphabetize the Client Options section of the tor manpage. Closes
2746 - Alphabetize the General Options section of the tor manpage. Closes
2748 - In the tor(1) manpage, reword and improve formatting of the
2749 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
2750 32277. Based on work by Swati Thacker as part of Google Season
2752 - In the tor(1) manpage, reword and improve formatting of the FILES,
2753 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
2754 Swati Thacker as part of Google Season of Docs.
2756 o Testing (circuit, EWMA):
2757 - Add unit tests for circuitmux and EWMA subsystems. Closes
2760 o Testing (continuous integration):
2761 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2764 Changes in version 0.4.2.5 - 2019-12-09
2765 This is the first stable release in the 0.4.2.x series. This series
2766 improves reliability and stability, and includes several stability and
2767 correctness improvements for onion services. It also fixes many smaller
2768 bugs present in previous series.
2770 Per our support policy, we will support the 0.4.2.x series for nine
2771 months, or until three months after the release of a stable 0.4.3.x:
2772 whichever is longer. If you need longer-term support, please stick
2773 with 0.3.5.x, which will we plan to support until Feb 2022.
2775 Per our support policy, we will support the 0.4.2.x series for nine
2776 months, or until three months after the release of a stable 0.4.3.x:
2777 whichever is longer. If you need longer-term support, please stick
2778 with 0.3.5.x, which will we plan to support until Feb 2022.
2780 Below are the changes since 0.4.1.4-rc. For a complete list of changes
2781 since 0.4.1.5, see the ReleaseNotes file.
2783 o Minor features (geoip):
2784 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
2785 Country database. Closes ticket 32685.
2788 - Require C99 standards-conforming code in Travis CI, but allow GNU
2789 gcc extensions. Also activates clang's -Wtypedef-redefinition
2790 warnings. Build some jobs with -std=gnu99, and some jobs without.
2791 Closes ticket 32500.
2794 Changes in version 0.4.1.7 - 2019-12-09
2795 This release backports several bugfixes to improve stability and
2796 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
2797 including all relays relying on AccountingMax, should upgrade.
2799 o Major features (directory authorities, backport from 0.4.2.2-alpha):
2800 - Directory authorities now reject relays running all currently
2801 deprecated release series. The currently supported release series
2802 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
2804 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
2805 - Avoid a possible crash when restarting Tor in embedded mode and
2806 enabling a different set of publish/subscribe messages. Fixes bug
2807 31898; bugfix on 0.4.1.1-alpha.
2809 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
2810 - Relays now respect their AccountingMax bandwidth again. When
2811 relays entered "soft" hibernation (which typically starts when
2812 we've hit 90% of our AccountingMax), we had stopped checking
2813 whether we should enter hard hibernation. Soft hibernation refuses
2814 new connections and new circuits, but the existing circuits can
2815 continue, meaning that relays could have exceeded their configured
2816 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
2818 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
2819 - Stop ignoring torrc options after an %include directive, when the
2820 included directory ends with a file that does not contain any
2821 config options (but does contain comments or whitespace). Fixes
2822 bug 31408; bugfix on 0.3.1.1-alpha.
2824 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
2825 - Onion services now always use the exact number of intro points
2826 configured with the HiddenServiceNumIntroductionPoints option (or
2827 fewer if nodes are excluded). Before, a service could sometimes
2828 pick more intro points than configured. Fixes bug 31548; bugfix
2831 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
2832 - When building on Appveyor and Travis, pass the "-k" flag to make,
2833 so that we are informed of all compilation failures, not just the
2834 first one or two. Closes ticket 31372.
2836 o Minor features (geoip, backport from 0.4.2.5):
2837 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
2838 Country database. Closes ticket 32685.
2840 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
2841 - Avoid spurious errors when Appveyor CI fails before the install step.
2842 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2844 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
2845 - Fix a BUG() assertion that occurs within a very small race window
2846 between when a client intro circuit opens and when its descriptor
2847 gets cleaned up from the cache. The circuit is now closed early,
2848 which will trigger a re-fetch of the descriptor and continue the
2849 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2851 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
2852 - Avoid trying to read data from closed connections, which can cause
2853 needless loops in Libevent and infinite loops in Shadow. Fixes bug
2854 30344; bugfix on 0.1.1.1-alpha.
2856 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
2857 - On abort, try harder to flush the output buffers of log messages.
2858 On some platforms (macOS), log messages could be discarded when
2859 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2860 - Report the tor version whenever an assertion fails. Previously, we
2861 only reported the Tor version on some crashes, and some non-fatal
2862 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2863 - When tor aborts due to an error, close log file descriptors before
2864 aborting. Closing the logs makes some OSes flush log file buffers,
2865 rather than deleting buffered log lines. Fixes bug 31594; bugfix
2868 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
2869 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
2870 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
2871 - Disable backtrace signal handlers when shutting down tor. Fixes
2872 bug 31614; bugfix on 0.2.5.2-alpha.
2873 - Rate-limit our the logging message about the obsolete .exit
2874 notation. Previously, there was no limit on this warning, which
2875 could potentially be triggered many times by a hostile website.
2876 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2878 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
2879 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2880 cell on a connection using the obsolete v1 link protocol. Log a
2881 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2883 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
2884 - Reset the periodic events' "enabled" flag when Tor is shut down
2885 cleanly. Previously, this flag was left on, which caused periodic
2886 events not to be re-enabled when Tor was relaunched in-process
2887 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2890 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
2891 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
2892 31736; bugfix on 0.0.7.
2894 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
2895 - Remove overly strict assertions that triggered when a pluggable
2896 transport failed to launch. Fixes bug 31091; bugfix
2898 - Remove an assertion in the Unix process backend. This assertion
2899 would trigger when we failed to find the executable for a child
2900 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2902 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
2903 - Avoid crashing when starting with a corrupt keys directory where
2904 the old ntor key and the new ntor key are identical. Fixes bug
2905 30916; bugfix on 0.2.4.8-alpha.
2907 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
2908 - When testing port rebinding, don't busy-wait for tor to log.
2909 Instead, actually sleep for a short time before polling again.
2910 Also improve the formatting of control commands and log messages.
2911 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2913 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
2914 - Avoid a map_anon_nofork test failure due to a signed/unsigned
2915 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
2917 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
2918 - Log bugs about the TLS read buffer's length only once, rather than
2919 filling the logs with similar warnings. Fixes bug 31939; bugfix
2922 o Documentation (backport from 0.4.2.2-alpha):
2923 - Explain why we can't destroy the backtrace buffer mutex. Explain
2924 why we don't need to destroy the log mutex. Closes ticket 31736.
2926 o Testing (continuous integration, backport from 0.4.2.3-alpha):
2927 - Disable all but one Travis CI macOS build, to mitigate slow
2928 scheduling of Travis macOS jobs. Closes ticket 32177.
2929 - Run the chutney IPv6 networks as part of Travis CI. Closes
2931 - Simplify the Travis CI build matrix, and optimise for build time.
2932 Closes ticket 31859.
2933 - Use Windows Server 2019 instead of Windows Server 2016 in our
2934 Appveyor builds. Closes ticket 32086.
2936 o Testing (continuous integration, backport from 0.4.2.4-rc):
2937 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2938 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2939 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2940 until we can fix some Bionic permissions issues (see ticket
2941 32240). Related to ticket 31919.
2942 - Install the mingw OpenSSL package in Appveyor. This makes sure
2943 that the OpenSSL headers and libraries match in Tor's Appveyor
2944 builds. (This bug was triggered by an Appveyor image update.)
2945 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2947 o Testing (continuous integration, backport from 0.4.2.5):
2948 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2949 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2950 Build some jobs with -std=gnu99, and some jobs without.
2951 Closes ticket 32500.
2954 Changes in version 0.4.0.6 - 2019-12-09
2955 This is the second stable release in the 0.4.0.x series. This release
2956 backports several bugfixes to improve stability and correctness. Anyone
2957 experiencing build problems or crashes with 0.4.0.5, including all relays
2958 relying on AccountingMax, should upgrade.
2960 Note that, per our support policy, support for the 0.4.0.x series will end
2961 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
2962 latest stable release, or downgrade to 0.3.5.x, which will get long-term
2963 support until 1 Feb 2022.
2965 o Directory authority changes (backport from 0.4.1.5):
2966 - The directory authority "dizum" has a new IP address. Closes
2969 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
2970 - Consider our directory information to have changed when our list
2971 of bridges changes. Previously, Tor would not re-compute the
2972 status of its directory information when bridges changed, and
2973 therefore would not realize that it was no longer able to build
2974 circuits. Fixes part of bug 29875.
2975 - Do not count previously configured working bridges towards our
2976 total of working bridges. Previously, when Tor's list of bridges
2977 changed, it would think that the old bridges were still usable,
2978 and delay fetching router descriptors for the new ones. Fixes part
2979 of bug 29875; bugfix on 0.3.0.1-alpha.
2981 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
2982 - When considering upgrading circuits from "waiting for guard" to
2983 "open", always ignore circuits that are marked for close. Otherwise,
2984 we can end up in the situation where a subsystem is notified that
2985 a closing circuit has just opened, leading to undesirable
2986 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
2988 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
2989 - Properly clean up the introduction point map when circuits change
2990 purpose from onion service circuits to pathbias, measurement, or
2991 other circuit types. This should fix some service-side instances
2992 of introduction point failure. Fixes bug 29034; bugfix
2995 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
2996 - Fix an unreachable bug in which an introduction point could try to
2997 send an INTRODUCE_ACK with a status code that Trunnel would refuse
2998 to encode, leading the relay to assert(). We've consolidated the
2999 ABI values into Trunnel now. Fixes bug 30454; bugfix
3001 - Clients can now handle unknown status codes from INTRODUCE_ACK
3002 cells. (The NACK behavior will stay the same.) This will allow us
3003 to extend status codes in the future without breaking the normal
3004 client behavior. Fixes another part of bug 30454; bugfix
3007 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
3008 - Relays now respect their AccountingMax bandwidth again. When
3009 relays entered "soft" hibernation (which typically starts when
3010 we've hit 90% of our AccountingMax), we had stopped checking
3011 whether we should enter hard hibernation. Soft hibernation refuses
3012 new connections and new circuits, but the existing circuits can
3013 continue, meaning that relays could have exceeded their configured
3014 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3016 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3017 - Stop ignoring torrc options after an %include directive, when the
3018 included directory ends with a file that does not contain any
3019 config options (but does contain comments or whitespace). Fixes
3020 bug 31408; bugfix on 0.3.1.1-alpha.
3022 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3023 - Onion services now always use the exact number of intro points
3024 configured with the HiddenServiceNumIntroductionPoints option (or
3025 fewer if nodes are excluded). Before, a service could sometimes
3026 pick more intro points than configured. Fixes bug 31548; bugfix
3029 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
3030 - Add a "--list-modules" command to print a list of which compile-
3031 time modules are enabled. Closes ticket 30452.
3033 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
3034 - Remove sudo configuration lines from .travis.yml as they are no
3035 longer needed with current Travis build environment. Resolves
3038 o Minor features (continuous integration, backport from 0.4.1.4-rc):
3039 - Our Travis configuration now uses Chutney to run some network
3040 integration tests automatically. Closes ticket 29280.
3042 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
3043 - When building on Appveyor and Travis, pass the "-k" flag to make,
3044 so that we are informed of all compilation failures, not just the
3045 first one or two. Closes ticket 31372.
3047 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
3048 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
3049 in December 2018 (of which ~122 were still functional), with a
3050 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
3051 in June 2019. Closes ticket 28795.
3053 o Minor features (geoip, backport from 0.4.2.5):
3054 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3055 Country database. Closes ticket 32685.
3057 o Minor features (stem tests, backport from 0.4.2.1-alpha):
3058 - Change "make test-stem" so it only runs the stem tests that use
3059 tor. This change makes test-stem faster and more reliable. Closes
3062 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
3063 - Avoid spurious errors when Appveyor CI fails before the install step.
3064 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3066 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
3067 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3068 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3070 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
3071 - Fix a logic error that prevented the SessionGroup sub-option from
3072 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3074 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
3075 - On relays, properly check that a padding machine is absent before
3076 logging a warning about it being absent. Fixes bug 30649; bugfix
3079 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
3080 - Fix a BUG() assertion that occurs within a very small race window
3081 between when a client intro circuit opens and when its descriptor
3082 gets cleaned up from the cache. The circuit is now closed early,
3083 which will trigger a re-fetch of the descriptor and continue the
3084 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3086 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
3087 - Don't believe clock skew results from NETINFO cells that appear to
3088 arrive before we sent the VERSIONS cells they are responding to.
3089 Previously, we would accept them up to 3 minutes "in the past".
3090 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3092 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
3093 - Fix a compilation warning on Windows about casting a function
3094 pointer for GetTickCount64(). Fixes bug 31374; bugfix
3097 o Minor bugfixes (compilation, backport from 0.4.1.5):
3098 - Avoid using labs() on time_t, which can cause compilation warnings
3099 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3101 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
3102 - Suppress spurious float-conversion warnings from GCC when calling
3103 floating-point classifier functions on FreeBSD. Fixes part of bug
3104 31687; bugfix on 0.3.1.5-alpha.
3106 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
3107 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3108 due to missing declarations of abort(), and prevent other such
3109 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3111 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
3112 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3113 want authentication along with configured (but unused!)
3114 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3116 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3117 - Avoid trying to read data from closed connections, which can cause
3118 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3119 30344; bugfix on 0.1.1.1-alpha.
3121 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
3122 - Allow the test-stem job to fail in Travis, because it sometimes
3123 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3124 - Skip test_rebind on macOS in Travis, because it is unreliable on
3125 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3126 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3127 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3129 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
3130 - Avoid a set of possible code paths that could try to use freed
3131 memory in routerlist_free() while Tor was exiting. Fixes bug
3132 31003; bugfix on 0.1.2.2-alpha.
3134 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
3135 - Stop crashing after parsing an unknown descriptor purpose
3136 annotation. We think this bug can only be triggered by modifying a
3137 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3139 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
3140 - Move the "bandwidth-file-headers" line in directory authority
3141 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3144 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3145 - On abort, try harder to flush the output buffers of log messages.
3146 On some platforms (macOS), log messages could be discarded when
3147 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3148 - Report the tor version whenever an assertion fails. Previously, we
3149 only reported the Tor version on some crashes, and some non-fatal
3150 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3152 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
3153 - When extracting an IPv6 address from a PF-based proxy, verify that
3154 we are actually configured to receive an IPv6 address, and log an
3155 internal error if not. Fixes part of bug 31687; bugfix
3158 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
3159 - When tor is missing descriptors for some primary entry guards,
3160 make the log message less alarming. It's normal for descriptors to
3161 expire, as long as tor fetches new ones soon after. Fixes bug
3162 31657; bugfix on 0.3.3.1-alpha.
3164 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
3165 - Do not log a warning when running with an OpenSSL version other
3166 than the one Tor was compiled with, if the two versions should be
3167 compatible. Previously, we would warn whenever the version was
3168 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3170 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
3171 - Change log level of message "Hash of session info was not as
3172 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
3175 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
3176 - Rate-limit our the logging message about the obsolete .exit
3177 notation. Previously, there was no limit on this warning, which
3178 could potentially be triggered many times by a hostile website.
3179 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3181 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
3182 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3183 cell on a connection using the obsolete v1 link protocol. Log a
3184 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3186 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
3187 - Reset the periodic events' "enabled" flag when Tor is shut down
3188 cleanly. Previously, this flag was left on, which caused periodic
3189 events not to be re-enabled when Tor was relaunched in-process
3190 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3193 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
3194 - Avoid a minor memory leak that could occur on relays when failing
3195 to create a "keys" directory. Fixes bug 30148; bugfix
3198 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
3199 - Fix a trivial memory leak when parsing an invalid value
3200 from a download schedule in the configuration. Fixes bug
3201 30894; bugfix on 0.3.4.1-alpha.
3203 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
3204 - Fix usage of minherit() on NetBSD and other platforms that define
3205 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
3206 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
3208 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
3209 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3210 implemenation) when failing to load an onion service client
3211 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3213 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
3214 - When purging the DNS cache because of an out-of-memory condition,
3215 try purging just the older entries at first. Previously, we would
3216 always purge the whole thing. Fixes bug 29617; bugfix
3219 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
3220 - Avoid crashing in our tor_vasprintf() implementation on systems
3221 that define neither vasprintf() nor _vscprintf(). (This bug has
3222 been here long enough that we question whether people are running
3223 Tor on such systems, but we're applying the fix out of caution.)
3224 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3227 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
3228 - Remove overly strict assertions that triggered when a pluggable
3229 transport failed to launch. Fixes bug 31091; bugfix
3231 - Remove an assertion in the Unix process backend. This assertion
3232 would trigger when we failed to find the executable for a child
3233 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
3235 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
3236 - Avoid crashing when starting with a corrupt keys directory where
3237 the old ntor key and the new ntor key are identical. Fixes bug
3238 30916; bugfix on 0.2.4.8-alpha.
3240 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
3241 - Correctly exclude a redundant rust build job in Travis. Fixes bug
3242 31463; bugfix on 0.3.5.4-alpha.
3244 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
3245 - When testing port rebinding, don't busy-wait for tor to log.
3246 Instead, actually sleep for a short time before polling again.
3247 Also improve the formatting of control commands and log messages.
3248 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3250 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
3251 - Log bugs about the TLS read buffer's length only once, rather than
3252 filling the logs with similar warnings. Fixes bug 31939; bugfix
3255 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
3256 - Always retry v2 single onion service intro and rend circuits with
3257 a 3-hop path. Previously, v2 single onion services used a 3-hop
3258 path when rendezvous circuits were retried after a remote or
3259 delayed failure, but a 1-hop path for immediate retries. Fixes bug
3260 23818; bugfix on 0.2.9.3-alpha.
3261 - Make v3 single onion services fall back to a 3-hop intro, when all
3262 intro points are unreachable via a 1-hop path. Previously, v3
3263 single onion services failed when all intro nodes were unreachable
3264 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
3266 o Documentation (backport from 0.4.2.1-alpha):
3267 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
3268 notice.html so that operators no longer have to host it
3269 themselves. Closes ticket 31089.
3271 o Testing (backport from 0.4.1.2-alpha):
3272 - Specify torrc paths (with empty files) when launching tor in
3273 integration tests; refrain from reading user and system torrcs.
3274 Resolves issue 29702.
3276 o Testing (continuous integration, backport from 0.4.1.1-alpha):
3277 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3279 o Testing (continuous integration, backport from 0.4.1.5):
3280 - In Travis, make stem log a controller trace to the console, and
3281 tail stem's tor log after failure. Closes ticket 30591.
3282 - In Travis, only run the stem tests that use a tor binary. Closes
3285 o Testing (continuous integration, backport from 0.4.2.3-alpha):
3286 - Disable all but one Travis CI macOS build, to mitigate slow
3287 scheduling of Travis macOS jobs. Closes ticket 32177.
3288 - Run the chutney IPv6 networks as part of Travis CI. Closes
3290 - Simplify the Travis CI build matrix, and optimise for build time.
3291 Closes ticket 31859.
3292 - Use Windows Server 2019 instead of Windows Server 2016 in our
3293 Appveyor builds. Closes ticket 32086.
3295 o Testing (continuous integration, backport from 0.4.2.4-rc):
3296 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3297 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3298 until we can fix some Bionic permissions issues (see ticket
3299 32240). Related to ticket 31919.
3300 - Install the mingw OpenSSL package in Appveyor. This makes sure
3301 that the OpenSSL headers and libraries match in Tor's Appveyor
3302 builds. (This bug was triggered by an Appveyor image update.)
3303 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3304 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3306 o Testing (continuous integration, backport from 0.4.2.5):
3307 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
3308 extensions. Also activates clang's -Wtypedef-redefinition warnings.
3309 Build some jobs with -std=gnu99, and some jobs without.
3310 Closes ticket 32500.
3312 Changes in version 0.3.5.9 - 2019-12-09
3313 Tor 0.3.5.9 backports serveral fixes from later releases, including
3314 several that affect bridge users, relay stability, onion services,
3317 o Directory authority changes (backport from 0.4.1.5):
3318 - The directory authority "dizum" has a new IP address. Closes
3321 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
3322 - Consider our directory information to have changed when our list
3323 of bridges changes. Previously, Tor would not re-compute the
3324 status of its directory information when bridges changed, and
3325 therefore would not realize that it was no longer able to build
3326 circuits. Fixes part of bug 29875.
3327 - Do not count previously configured working bridges towards our
3328 total of working bridges. Previously, when Tor's list of bridges
3329 changed, it would think that the old bridges were still usable,
3330 and delay fetching router descriptors for the new ones. Fixes part
3331 of bug 29875; bugfix on 0.3.0.1-alpha.
3333 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
3334 - When considering upgrading circuits from "waiting for guard" to
3335 "open", always ignore circuits that are marked for close. Otherwise,
3336 we can end up in the situation where a subsystem is notified that
3337 a closing circuit has just opened, leading to undesirable
3338 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
3340 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
3341 - When running with NSS, disable TLS 1.2 ciphersuites that use
3342 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
3343 these ciphersuites don't work -- which caused relays to fail to
3344 handshake with one another when these ciphersuites were enabled.
3345 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
3347 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
3348 - Properly clean up the introduction point map when circuits change
3349 purpose from onion service circuits to pathbias, measurement, or
3350 other circuit types. This should fix some service-side instances
3351 of introduction point failure. Fixes bug 29034; bugfix
3354 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
3355 - Fix an unreachable bug in which an introduction point could try to
3356 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3357 to encode, leading the relay to assert(). We've consolidated the
3358 ABI values into Trunnel now. Fixes bug 30454; bugfix
3360 - Clients can now handle unknown status codes from INTRODUCE_ACK
3361 cells. (The NACK behavior will stay the same.) This will allow us
3362 to extend status codes in the future without breaking the normal
3363 client behavior. Fixes another part of bug 30454; bugfix
3366 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3367 - Stop ignoring torrc options after an %include directive, when the
3368 included directory ends with a file that does not contain any
3369 config options (but does contain comments or whitespace). Fixes
3370 bug 31408; bugfix on 0.3.1.1-alpha.
3372 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3373 - Onion services now always use the exact number of intro points
3374 configured with the HiddenServiceNumIntroductionPoints option (or
3375 fewer if nodes are excluded). Before, a service could sometimes
3376 pick more intro points than configured. Fixes bug 31548; bugfix
3379 o Minor features (address selection, backport from 0.4.0.3-alpha):
3380 - Treat the subnet 100.64.0.0/10 as public for some purposes;
3381 private for others. This subnet is the RFC 6598 (Carrier Grade
3382 NAT) IP range, and is deployed by many ISPs as an alternative to
3383 RFC 1918 that does not break existing internal networks. Tor now
3384 blocks SOCKS and control ports on these addresses and warns users
3385 if client ports or ExtORPorts are listening on a RFC 6598 address.
3386 Closes ticket 28525. Patch by Neel Chauhan.
3388 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
3389 - Make bandwidth authorities ignore relays that are reported in the
3390 bandwidth file with the flag "vote=0". This change allows us to
3391 report unmeasured relays for diagnostic reasons without including
3392 their bandwidth in the bandwidth authorities' vote. Closes
3395 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
3396 - Add a "--list-modules" command to print a list of which compile-
3397 time modules are enabled. Closes ticket 30452.
3399 o Minor features (continuous integration, backport from 0.4.0.4-rc):
3400 - On Travis Rust builds, cleanup Rust registry and refrain from
3401 caching the "target/" directory to speed up builds. Resolves
3404 o Minor features (continuous integration, backport from 0.4.0.5):
3405 - In Travis, tell timelimit to use stem's backtrace signals, and
3406 launch python directly from timelimit, so python receives the
3407 signals from timelimit, rather than make. Closes ticket 30117.
3409 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
3410 - Remove sudo configuration lines from .travis.yml as they are no
3411 longer needed with current Travis build environment. Resolves
3414 o Minor features (continuous integration, backport from 0.4.1.4-rc):
3415 - Our Travis configuration now uses Chutney to run some network
3416 integration tests automatically. Closes ticket 29280.
3418 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
3419 - When building on Appveyor and Travis, pass the "-k" flag to make,
3420 so that we are informed of all compilation failures, not just the
3421 first one or two. Closes ticket 31372.
3423 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
3424 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
3425 in December 2018 (of which ~122 were still functional), with a
3426 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
3427 in June 2019. Closes ticket 28795.
3429 o Minor features (geoip, backport from 0.4.2.5):
3430 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3431 Country database. Closes ticket 32685.
3433 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
3434 - Try to log an error from NSS (if there is any) and a more useful
3435 description of our situation if we are using NSS and a call to
3436 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
3438 o Minor features (stem tests, backport from 0.4.2.1-alpha):
3439 - Change "make test-stem" so it only runs the stem tests that use
3440 tor. This change makes test-stem faster and more reliable. Closes
3443 o Minor bugfixes (security, backport from 0.4.0.4-rc):
3444 - Verify in more places that we are not about to create a buffer
3445 with more than INT_MAX bytes, to avoid possible OOB access in the
3446 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
3447 fixed by Tobias Stoeckmann.
3448 - Fix a potential double free bug when reading huge bandwidth files.
3449 The issue is not exploitable in the current Tor network because
3450 the vulnerable code is only reached when directory authorities
3451 read bandwidth files, but bandwidth files come from a trusted
3452 source (usually the authorities themselves). Furthermore, the
3453 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
3454 which are not used by any of the current authorities. Fixes bug
3455 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
3458 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
3459 - Reset coverage state on disk after Travis CI has finished. This
3460 should prevent future coverage merge errors from causing the test
3461 suite for the "process" subsystem to fail. The process subsystem
3462 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
3464 - Terminate test-stem if it takes more than 9.5 minutes to run.
3465 (Travis terminates the job after 10 minutes of no output.)
3466 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
3468 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
3469 - Avoid spurious errors when Appveyor CI fails before the install step.
3470 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3472 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
3473 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3474 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3476 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
3477 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
3478 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
3481 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
3482 - Fix a logic error that prevented the SessionGroup sub-option from
3483 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3485 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
3486 - Fix a BUG() assertion that occurs within a very small race window
3487 between when a client intro circuit opens and when its descriptor
3488 gets cleaned up from the cache. The circuit is now closed early,
3489 which will trigger a re-fetch of the descriptor and continue the
3490 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3492 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
3493 - Don't believe clock skew results from NETINFO cells that appear to
3494 arrive before we sent the VERSIONS cells they are responding to.
3495 Previously, we would accept them up to 3 minutes "in the past".
3496 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3498 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
3499 - Fix a compilation warning on Windows about casting a function
3500 pointer for GetTickCount64(). Fixes bug 31374; bugfix
3503 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
3504 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
3505 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
3507 o Minor bugfixes (compilation, backport from 0.4.1.5):
3508 - Avoid using labs() on time_t, which can cause compilation warnings
3509 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3511 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
3512 - Suppress spurious float-conversion warnings from GCC when calling
3513 floating-point classifier functions on FreeBSD. Fixes part of bug
3514 31687; bugfix on 0.3.1.5-alpha.
3516 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
3517 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3518 due to missing declarations of abort(), and prevent other such
3519 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3521 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
3522 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3523 want authentication along with configured (but unused!)
3524 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3526 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3527 - Avoid trying to read data from closed connections, which can cause
3528 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3529 30344; bugfix on 0.1.1.1-alpha.
3531 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
3532 - Allow the test-stem job to fail in Travis, because it sometimes
3533 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3534 - Skip test_rebind on macOS in Travis, because it is unreliable on
3535 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3536 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3537 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3539 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
3540 - Avoid a set of possible code paths that could try to use freed
3541 memory in routerlist_free() while Tor was exiting. Fixes bug
3542 31003; bugfix on 0.1.2.2-alpha.
3544 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
3545 - Stop crashing after parsing an unknown descriptor purpose
3546 annotation. We think this bug can only be triggered by modifying a
3547 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3549 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
3550 - Move the "bandwidth-file-headers" line in directory authority
3551 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3554 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3555 - On abort, try harder to flush the output buffers of log messages.
3556 On some platforms (macOS), log messages could be discarded when
3557 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3558 - Report the tor version whenever an assertion fails. Previously, we
3559 only reported the Tor version on some crashes, and some non-fatal
3560 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3562 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
3563 - When extracting an IPv6 address from a PF-based proxy, verify that
3564 we are actually configured to receive an IPv6 address, and log an
3565 internal error if not. Fixes part of bug 31687; bugfix
3568 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
3569 - When tor is missing descriptors for some primary entry guards,
3570 make the log message less alarming. It's normal for descriptors to
3571 expire, as long as tor fetches new ones soon after. Fixes bug
3572 31657; bugfix on 0.3.3.1-alpha.
3574 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
3575 - Avoid logging that we are relaxing a circuit timeout when that
3576 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
3578 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
3579 - Correct a misleading error message when IPv4Only or IPv6Only is
3580 used but the resolved address can not be interpreted as an address
3581 of the specified IP version. Fixes bug 13221; bugfix on
3582 0.2.3.9-alpha. Patch from Kris Katterjohn.
3583 - Log the correct port number for listening sockets when "auto" is
3584 used to let Tor pick the port number. Previously, port 0 was
3585 logged instead of the actual port number. Fixes bug 29144; bugfix
3586 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3587 - Stop logging a BUG() warning when Tor is waiting for exit
3588 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
3590 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
3591 - Do not log a warning when running with an OpenSSL version other
3592 than the one Tor was compiled with, if the two versions should be
3593 compatible. Previously, we would warn whenever the version was
3594 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3596 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
3597 - Change log level of message "Hash of session info was not as
3598 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
3601 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
3602 - Rate-limit our the logging message about the obsolete .exit
3603 notation. Previously, there was no limit on this warning, which
3604 could potentially be triggered many times by a hostile website.
3605 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3607 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
3608 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3609 cell on a connection using the obsolete v1 link protocol. Log a
3610 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3612 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
3613 - Reset the periodic events' "enabled" flag when Tor is shut down
3614 cleanly. Previously, this flag was left on, which caused periodic
3615 events not to be re-enabled when Tor was relaunched in-process
3616 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3619 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
3620 - Avoid a minor memory leak that could occur on relays when failing
3621 to create a "keys" directory. Fixes bug 30148; bugfix
3624 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
3625 - Fix a trivial memory leak when parsing an invalid value
3626 from a download schedule in the configuration. Fixes bug
3627 30894; bugfix on 0.3.4.1-alpha.
3629 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
3630 - Refactor the shared random state's memory management so that it
3631 actually takes ownership of the shared random value pointers.
3632 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
3634 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
3635 - Stop leaking parts of the shared random state in the shared-random
3636 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
3638 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
3639 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3640 implemenation) when failing to load an onion service client
3641 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3643 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
3644 - When purging the DNS cache because of an out-of-memory condition,
3645 try purging just the older entries at first. Previously, we would
3646 always purge the whole thing. Fixes bug 29617; bugfix
3649 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
3650 - Avoid crashing in our tor_vasprintf() implementation on systems
3651 that define neither vasprintf() nor _vscprintf(). (This bug has
3652 been here long enough that we question whether people are running
3653 Tor on such systems, but we're applying the fix out of caution.)
3654 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3657 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
3658 - Avoid crashing when starting with a corrupt keys directory where
3659 the old ntor key and the new ntor key are identical. Fixes bug
3660 30916; bugfix on 0.2.4.8-alpha.
3662 o Minor bugfixes (rust, backport from 0.4.0.5):
3663 - Abort on panic in all build profiles, instead of potentially
3664 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
3666 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
3667 - Correctly exclude a redundant rust build job in Travis. Fixes bug
3668 31463; bugfix on 0.3.5.4-alpha.
3670 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
3671 - Allow connections to single onion services to remain idle without
3672 being disconnected. Previously, relays acting as rendezvous points
3673 for single onion services were mistakenly closing idle rendezvous
3674 circuits after 60 seconds, thinking that they were unused
3675 directory-fetching circuits that had served their purpose. Fixes
3676 bug 29665; bugfix on 0.2.1.26.
3678 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
3679 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
3680 relay and bridge extra-info documents. Fixes bug 29017; bugfix
3683 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
3684 - Downgrade some LOG_ERR messages in the address/* tests to
3685 warnings. The LOG_ERR messages were occurring when we had no
3686 configured network. We were failing the unit tests, because we
3687 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
3688 29530; bugfix on 0.3.5.8.
3689 - Fix our gcov wrapper script to look for object files at the
3690 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
3692 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
3693 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
3694 recent test-network.sh to use new chutney features in CI. Fixes
3695 bug 29703; bugfix on 0.2.9.1-alpha.
3696 - Fix a test failure on Windows caused by an unexpected "BUG"
3697 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
3700 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
3701 - When testing port rebinding, don't busy-wait for tor to log.
3702 Instead, actually sleep for a short time before polling again.
3703 Also improve the formatting of control commands and log messages.
3704 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3706 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
3707 - When classifying a client's selection of TLS ciphers, if the
3708 client ciphers are not yet available, do not cache the result.
3709 Previously, we had cached the unavailability of the cipher list
3710 and never looked again, which in turn led us to assume that the
3711 client only supported the ancient V1 link protocol. This, in turn,
3712 was causing Stem integration tests to stall in some cases. Fixes
3713 bug 30021; bugfix on 0.2.4.8-alpha.
3715 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
3716 - Log bugs about the TLS read buffer's length only once, rather than
3717 filling the logs with similar warnings. Fixes bug 31939; bugfix
3720 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
3721 - Always retry v2 single onion service intro and rend circuits with
3722 a 3-hop path. Previously, v2 single onion services used a 3-hop
3723 path when rendezvous circuits were retried after a remote or
3724 delayed failure, but a 1-hop path for immediate retries. Fixes bug
3725 23818; bugfix on 0.2.9.3-alpha.
3726 - Make v3 single onion services fall back to a 3-hop intro, when all
3727 intro points are unreachable via a 1-hop path. Previously, v3
3728 single onion services failed when all intro nodes were unreachable
3729 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
3731 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
3732 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
3733 Windows Server 2012 R2 job. The remaining 2 jobs still provide
3734 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
3735 fast_finish, so failed jobs terminate the build immediately. Fixes
3736 bug 29601; bugfix on 0.3.5.4-alpha.
3738 o Documentation (backport from 0.4.2.1-alpha):
3739 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
3740 notice.html so that operators no longer have to host it
3741 themselves. Closes ticket 31089.
3743 o Testing (backport from 0.4.1.2-alpha):
3744 - Specify torrc paths (with empty files) when launching tor in
3745 integration tests; refrain from reading user and system torrcs.
3746 Resolves issue 29702.
3748 o Testing (continuous integration, backport from 0.4.1.1-alpha):
3749 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3751 o Testing (continuous integration, backport from 0.4.1.5):
3752 - In Travis, make stem log a controller trace to the console, and
3753 tail stem's tor log after failure. Closes ticket 30591.
3754 - In Travis, only run the stem tests that use a tor binary. Closes
3757 o Testing (continuous integration, backport from 0.4.2.3-alpha):
3758 - Disable all but one Travis CI macOS build, to mitigate slow
3759 scheduling of Travis macOS jobs. Closes ticket 32177.
3760 - Run the chutney IPv6 networks as part of Travis CI. Closes
3762 - Simplify the Travis CI build matrix, and optimise for build time.
3763 Closes ticket 31859.
3764 - Use Windows Server 2019 instead of Windows Server 2016 in our
3765 Appveyor builds. Closes ticket 32086.
3767 o Testing (continuous integration, backport from 0.4.2.4-rc):
3768 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3769 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3770 until we can fix some Bionic permissions issues (see ticket
3771 32240). Related to ticket 31919.
3772 - Install the mingw OpenSSL package in Appveyor. This makes sure
3773 that the OpenSSL headers and libraries match in Tor's Appveyor
3774 builds. (This bug was triggered by an Appveyor image update.)
3775 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3776 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3778 o Testing (continuous integration, backport from 0.4.2.5):
3779 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
3780 extensions. Also activates clang's -Wtypedef-redefinition warnings.
3781 Build some jobs with -std=gnu99, and some jobs without.
3782 Closes ticket 32500.
3784 Changes in version 0.4.2.4-rc - 2019-11-15
3785 Tor 0.4.2.4-rc is the first release candidate in its series. It fixes
3786 several bugs from earlier versions, including a few that would result in
3787 stack traces or incorrect behavior.
3789 o Minor features (build system):
3790 - Make pkg-config use --prefix when cross-compiling, if
3791 PKG_CONFIG_PATH is not set. Closes ticket 32191.
3793 o Minor features (geoip):
3794 - Update geoip and geoip6 to the November 6 2019 Maxmind GeoLite2
3795 Country database. Closes ticket 32440.
3797 o Minor bugfixes (client, onion service v3):
3798 - Fix a BUG() assertion that occurs within a very small race window
3799 between when a client intro circuit opens and when its descriptor
3800 gets cleaned up from the cache. The circuit is now closed early,
3801 which will trigger a re-fetch of the descriptor and continue the
3802 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3804 o Minor bugfixes (code quality):
3805 - Fix "make check-includes" so it runs correctly on out-of-tree
3806 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
3808 o Minor bugfixes (configuration):
3809 - Log the option name when skipping an obsolete option. Fixes bug
3810 32295; bugfix on 0.4.2.1-alpha.
3812 o Minor bugfixes (crash):
3813 - When running Tor with an option like --verify-config or
3814 --dump-config that does not start the event loop, avoid crashing
3815 if we try to exit early because of an error. Fixes bug 32407;
3816 bugfix on 0.3.3.1-alpha.
3818 o Minor bugfixes (directory):
3819 - When checking if a directory connection is anonymous, test if the
3820 circuit was marked for close before looking at its channel. This
3821 avoids a BUG() stacktrace if the circuit was previously closed.
3822 Fixes bug 31958; bugfix on 0.4.2.1-alpha.
3824 o Minor bugfixes (shellcheck):
3825 - Fix minor shellcheck errors in the git-*.sh scripts. Fixes bug
3826 32402; bugfix on 0.4.2.1-alpha.
3827 - Start checking most scripts for shellcheck errors again. Fixes bug
3828 32402; bugfix on 0.4.2.1-alpha.
3830 o Testing (continuous integration):
3831 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3832 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3833 until we can fix some Bionic permissions issues (see ticket
3834 32240). Related to ticket 31919.
3835 - Install the mingw OpenSSL package in Appveyor. This makes sure
3836 that the OpenSSL headers and libraries match in Tor's Appveyor
3837 builds. (This bug was triggered by an Appveyor image update.)
3838 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3839 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3842 Changes in version 0.4.2.3-alpha - 2019-10-24
3843 This release fixes several bugs from the previous alpha release, and
3844 from earlier versions of Tor.
3846 o Major bugfixes (relay):
3847 - Relays now respect their AccountingMax bandwidth again. When
3848 relays entered "soft" hibernation (which typically starts when
3849 we've hit 90% of our AccountingMax), we had stopped checking
3850 whether we should enter hard hibernation. Soft hibernation refuses
3851 new connections and new circuits, but the existing circuits can
3852 continue, meaning that relays could have exceeded their configured
3853 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3855 o Major bugfixes (v3 onion services):
3856 - Onion services now always use the exact number of intro points
3857 configured with the HiddenServiceNumIntroductionPoints option (or
3858 fewer if nodes are excluded). Before, a service could sometimes
3859 pick more intro points than configured. Fixes bug 31548; bugfix
3862 o Minor feature (onion services, control port):
3863 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
3864 (v3) onion services. Previously it defaulted to RSA1024 (v2).
3865 Closes ticket 29669.
3867 o Minor features (testing):
3868 - When running tests that attempt to look up hostnames, replace the
3869 libc name lookup functions with ones that do not actually touch
3870 the network. This way, the tests complete more quickly in the
3871 presence of a slow or missing DNS resolver. Closes ticket 31841.
3873 o Minor features (testing, continuous integration):
3874 - Disable all but one Travis CI macOS build, to mitigate slow
3875 scheduling of Travis macOS jobs. Closes ticket 32177.
3876 - Run the chutney IPv6 networks as part of Travis CI. Closes
3878 - Simplify the Travis CI build matrix, and optimise for build time.
3879 Closes ticket 31859.
3880 - Use Windows Server 2019 instead of Windows Server 2016 in our
3881 Appveyor builds. Closes ticket 32086.
3883 o Minor bugfixes (build system):
3884 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
3885 32124; bugfix on 0.3.4.1-alpha.
3886 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
3888 - Stop failing when jemalloc is requested, but tcmalloc is not
3889 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
3890 - When pkg-config is not installed, or a library that depends on
3891 pkg-config is not found, tell the user what to do to fix the
3892 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
3894 o Minor bugfixes (connections):
3895 - Avoid trying to read data from closed connections, which can cause
3896 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3897 30344; bugfix on 0.1.1.1-alpha.
3899 o Minor bugfixes (error handling):
3900 - Always lock the backtrace buffer before it is used. Fixes bug
3901 31734; bugfix on 0.2.5.3-alpha.
3903 o Minor bugfixes (mainloop, periodic events, in-process API):
3904 - Reset the periodic events' "enabled" flag when Tor is shut down
3905 cleanly. Previously, this flag was left on, which caused periodic
3906 events not to be re-enabled when Tor was relaunched in-process
3907 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3910 o Minor bugfixes (process management):
3911 - Remove overly strict assertions that triggered when a pluggable
3912 transport failed to launch. Fixes bug 31091; bugfix
3914 - Remove an assertion in the Unix process backend. This assertion
3915 would trigger when we failed to find the executable for a child
3916 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
3918 o Minor bugfixes (testing):
3919 - Avoid intermittent test failures due to a test that had relied on
3920 inconsistent timing sources. Fixes bug 31995; bugfix
3922 - When testing port rebinding, don't busy-wait for tor to log.
3923 Instead, actually sleep for a short time before polling again.
3924 Also improve the formatting of control commands and log messages.
3925 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3927 o Minor bugfixes (tls, logging):
3928 - Log bugs about the TLS read buffer's length only once, rather than
3929 filling the logs with similar warnings. Fixes bug 31939; bugfix
3932 o Minor bugfixes (v3 onion services):
3933 - Fix an implicit conversion from ssize_t to size_t discovered by
3934 Coverity. Fixes bug 31682; bugfix on 0.4.2.1-alpha.
3935 - Fix a memory leak in an unlikely error code path when encoding HS
3936 DoS establish intro extension cell. Fixes bug 32063; bugfix
3938 - When cleaning up intro circuits for a v3 onion service, don't
3939 remove circuits that have an established or pending circuit, even
3940 if they ran out of retries. This way, we don't remove a circuit on
3941 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
3944 - Correct the description of "GuardLifetime". Fixes bug 31189;
3945 bugfix on 0.3.0.1-alpha.
3946 - Make clear in the man page, in both the bandwidth section and the
3947 AccountingMax section, that Tor counts in powers of two, not
3948 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
3949 bytes. Resolves ticket 32106.
3952 Changes in version 0.4.2.2-alpha - 2019-10-07
3953 This release fixes several bugs from the previous alpha release, and
3954 from earlier versions. It also includes a change in authorities, so
3955 that they begin to reject the currently unsupported release series.
3957 o Major features (directory authorities):
3958 - Directory authorities now reject relays running all currently
3959 deprecated release series. The currently supported release series
3960 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
3962 o Major bugfixes (embedded Tor):
3963 - Avoid a possible crash when restarting Tor in embedded mode and
3964 enabling a different set of publish/subscribe messages. Fixes bug
3965 31898; bugfix on 0.4.1.1-alpha.
3967 o Major bugfixes (torrc parsing):
3968 - Stop ignoring torrc options after an %include directive, when the
3969 included directory ends with a file that does not contain any
3970 config options (but does contain comments or whitespace). Fixes
3971 bug 31408; bugfix on 0.3.1.1-alpha.
3973 o Minor features (auto-formatting scripts):
3974 - When annotating C macros, never generate a line that our check-
3975 spaces script would reject. Closes ticket 31759.
3976 - When annotating C macros, try to remove cases of double-negation.
3977 Closes ticket 31779.
3979 o Minor features (continuous integration):
3980 - When building on Appveyor and Travis, pass the "-k" flag to make,
3981 so that we are informed of all compilation failures, not just the
3982 first one or two. Closes ticket 31372.
3984 o Minor features (geoip):
3985 - Update geoip and geoip6 to the October 1 2019 Maxmind GeoLite2
3986 Country database. Closes ticket 31931.
3988 o Minor features (maintenance scripts):
3989 - Add a Coccinelle script to detect bugs caused by incrementing or
3990 decrementing a variable inside a call to log_debug(). Since
3991 log_debug() is a macro whose arguments are conditionally
3992 evaluated, it is usually an error to do this. One such bug was
3993 30628, in which SENDME cells were miscounted by a decrement
3994 operator inside a log_debug() call. Closes ticket 30743.
3996 o Minor features (onion services v3):
3997 - Assist users who try to setup v2 client authorization in v3 onion
3998 services by pointing them to the right documentation. Closes
4001 o Minor bugfixes (Appveyor continuous integration):
4002 - Avoid spurious errors when Appveyor CI fails before the install
4003 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
4005 o Minor bugfixes (best practices tracker):
4006 - When listing overbroad exceptions, do not also list problems, and
4007 do not list insufficiently broad exceptions. Fixes bug 31338;
4008 bugfix on 0.4.2.1-alpha.
4010 o Minor bugfixes (controller protocol):
4011 - Fix the MAPADDRESS controller command to accept one or more
4012 arguments. Previously, it required two or more arguments, and
4013 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
4015 o Minor bugfixes (logging):
4016 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
4017 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
4018 - Disable backtrace signal handlers when shutting down tor. Fixes
4019 bug 31614; bugfix on 0.2.5.2-alpha.
4020 - Rate-limit our the logging message about the obsolete .exit
4021 notation. Previously, there was no limit on this warning, which
4022 could potentially be triggered many times by a hostile website.
4023 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
4024 - When initialising log domain masks, only set known log domains.
4025 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
4027 o Minor bugfixes (logging, protocol violations):
4028 - Do not log a nonfatal assertion failure when receiving a VERSIONS
4029 cell on a connection using the obsolete v1 link protocol. Log a
4030 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
4032 o Minor bugfixes (modules):
4033 - Explain what the optional Directory Authority module is, and what
4034 happens when it is disabled. Fixes bug 31825; bugfix
4037 o Minor bugfixes (multithreading):
4038 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
4039 31736; bugfix on 0.0.7.
4041 o Minor bugfixes (relay):
4042 - Avoid crashing when starting with a corrupt keys directory where
4043 the old ntor key and the new ntor key are identical. Fixes bug
4044 30916; bugfix on 0.2.4.8-alpha.
4046 o Minor bugfixes (tests, SunOS):
4047 - Avoid a map_anon_nofork test failure due to a signed/unsigned
4048 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
4050 o Code simplification and refactoring:
4051 - Refactor connection_control_process_inbuf() to reduce the size of
4052 a practracker exception. Closes ticket 31840.
4053 - Refactor the microdescs_parse_from_string() function into smaller
4054 pieces, for better comprehensibility. Closes ticket 31675.
4055 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
4056 tests and fuzzers, rather than using hard-coded values. Closes
4058 - Interface for function `decrypt_desc_layer` cleaned up. Closes
4062 - Document the signal-safe logging behaviour in the tor man page.
4063 Also add some comments to the relevant functions. Closes
4065 - Explain why we can't destroy the backtrace buffer mutex. Explain
4066 why we don't need to destroy the log mutex. Closes ticket 31736.
4067 - The Tor source code repository now includes a (somewhat dated)
4068 description of Tor's modular architecture, in doc/HACKING/design.
4069 This is based on the old "tor-guts.git" repository, which we are
4070 adopting and superseding. Closes ticket 31849.
4073 Changes in version 0.4.1.6 - 2019-09-19
4074 This release backports several bugfixes to improve stability and
4075 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
4076 or experiencing reliability issues with single onion services, should
4079 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
4080 - Tolerate systems (including some Android installations) where
4081 madvise and MADV_DONTDUMP are available at build-time, but not at
4082 run time. Previously, these systems would notice a failed syscall
4083 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
4084 - Tolerate systems (including some Linux installations) where
4085 madvise and/or MADV_DONTFORK are available at build-time, but not
4086 at run time. Previously, these systems would notice a failed
4087 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
4089 o Minor features (stem tests, backport from 0.4.2.1-alpha):
4090 - Change "make test-stem" so it only runs the stem tests that use
4091 tor. This change makes test-stem faster and more reliable. Closes
4094 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
4095 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
4096 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
4098 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
4099 - Add more stub functions to fix compilation on Android with link-
4100 time optimization when --disable-module-dirauth is used.
4101 Previously, these compilation settings would make the compiler
4102 look for functions that didn't exist. Fixes bug 31552; bugfix
4104 - Suppress spurious float-conversion warnings from GCC when calling
4105 floating-point classifier functions on FreeBSD. Fixes part of bug
4106 31687; bugfix on 0.3.1.5-alpha.
4108 o Minor bugfixes (controller protocol):
4109 - Fix the MAPADDRESS controller command to accept one or more
4110 arguments. Previously, it required two or more arguments, and ignored
4111 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
4113 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
4114 - When extracting an IPv6 address from a PF-based proxy, verify that
4115 we are actually configured to receive an IPv6 address, and log an
4116 internal error if not. Fixes part of bug 31687; bugfix
4119 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
4120 - When tor is missing descriptors for some primary entry guards,
4121 make the log message less alarming. It's normal for descriptors to
4122 expire, as long as tor fetches new ones soon after. Fixes bug
4123 31657; bugfix on 0.3.3.1-alpha.
4125 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
4126 - Change log level of message "Hash of session info was not as
4127 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4130 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
4131 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4132 31463; bugfix on 0.3.5.4-alpha.
4134 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
4135 - Always retry v2 single onion service intro and rend circuits with
4136 a 3-hop path. Previously, v2 single onion services used a 3-hop
4137 path when rendezvous circuits were retried after a remote or
4138 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4139 23818; bugfix on 0.2.9.3-alpha.
4141 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
4142 - Always retry v3 single onion service intro and rend circuits with
4143 a 3-hop path. Previously, v3 single onion services used a 3-hop
4144 path when rend circuits were retried after a remote or delayed
4145 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
4146 bugfix on 0.3.2.1-alpha.
4147 - Make v3 single onion services fall back to a 3-hop intro, when all
4148 intro points are unreachable via a 1-hop path. Previously, v3
4149 single onion services failed when all intro nodes were unreachable
4150 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4152 o Documentation (backport from 0.4.2.1-alpha):
4153 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4154 notice.html so that operators no longer have to host it
4155 themselves. Closes ticket 31089.
4158 Changes in version 0.4.2.1-alpha - 2019-09-17
4159 This is the first alpha release in the 0.4.2.x series. It adds new
4160 defenses for denial-of-service attacks against onion services. It also
4161 includes numerous kinds of bugfixes and refactoring to help improve
4162 Tor's stability and ease of development.
4164 o Major features (onion service v3, denial of service):
4165 - Add onion service introduction denial of service defenses. Intro
4166 points can now rate-limit client introduction requests, using
4167 parameters that can be sent by the service within the
4168 ESTABLISH_INTRO cell. If the cell extension for this is not used,
4169 the intro point will honor the consensus parameters. Closes
4172 o Major bugfixes (circuit build, guard):
4173 - When considering upgrading circuits from "waiting for guard" to
4174 "open", always ignore circuits that are marked for close.
4175 Previously we could end up in the situation where a subsystem is
4176 notified of a circuit opening, but the circuit is still marked for
4177 close, leading to undesirable behavior. Fixes bug 30871; bugfix
4180 o Major bugfixes (crash, Linux, Android):
4181 - Tolerate systems (including some Android installations) where
4182 madvise and MADV_DONTDUMP are available at build-time, but not at
4183 run time. Previously, these systems would notice a failed syscall
4184 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
4185 - Tolerate systems (including some Linux installations) where
4186 madvise and/or MADV_DONTFORK are available at build-time, but not
4187 at run time. Previously, these systems would notice a failed
4188 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
4190 o Minor features (best practices tracker):
4191 - Our best-practices tracker now integrates with our include-checker
4192 tool to keep track of how many layering violations we have not yet
4193 fixed. We hope to reduce this number over time to improve Tor's
4194 modularity. Closes ticket 31176.
4195 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
4196 practracker from the environment. We may want this for continuous
4197 integration. Closes ticket 31309.
4198 - Give a warning rather than an error when a practracker exception
4199 is violated by a small amount, add a --list-overbroad option to
4200 practracker that lists exceptions that are stricter than they need
4201 to be, and provide an environment variable for disabling
4202 practracker. Closes ticket 30752.
4203 - Our best-practices tracker now looks at headers as well as C
4204 files. Closes ticket 31175.
4206 o Minor features (build system):
4207 - Add --disable-manpage and --disable-html-manual options to
4208 configure script. This will enable shortening build times by not
4209 building documentation. Resolves issue 19381.
4211 o Minor features (compilation):
4212 - Log a more useful error message when we are compiling and one of
4213 the compile-time hardening options we have selected can be linked
4214 but not executed. Closes ticket 27530.
4216 o Minor features (configuration):
4217 - The configuration code has been extended to allow splitting
4218 configuration data across multiple objects. Previously, all
4219 configuration data needed to be kept in a single object, which
4220 tended to become bloated. Closes ticket 31240.
4222 o Minor features (continuous integration):
4223 - When running CI builds on Travis, put some random data in
4224 ~/.torrc, to make sure no tests are reading the Tor configuration
4225 file from its default location. Resolves issue 30102.
4227 o Minor features (debugging):
4228 - Log a nonfatal assertion failure if we encounter a configuration
4229 line whose command is "CLEAR" but which has a nonempty value. This
4230 should be impossible, according to the rules of our configuration
4231 line parsing. Closes ticket 31529.
4233 o Minor features (git hooks):
4234 - Our pre-commit git hook now checks for a special file before
4235 running practracker, so that practracker only runs on branches
4236 that are based on master. Since the pre-push hook calls the pre-
4237 commit hook, practracker will also only run before pushes of
4238 branches based on master. Closes ticket 30979.
4240 o Minor features (git scripts):
4241 - Add a "--" command-line argument, to separate git-push-all.sh
4242 script arguments from arguments that are passed through to git
4243 push. Closes ticket 31314.
4244 - Add a -r <remote-name> argument to git-push-all.sh, so the script
4245 can push test branches to a personal remote. Closes ticket 31314.
4246 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
4247 git-push-all.sh, which makes these scripts create, merge forward,
4248 and push test branches. Closes ticket 31314.
4249 - Add a -u argument to git-merge-forward.sh, so that the script can
4250 re-use existing test branches after a merge failure and fix.
4251 Closes ticket 31314.
4252 - Add a TOR_GIT_PUSH env var, which sets the default git push
4253 command and arguments for git-push-all.sh. Closes ticket 31314.
4254 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
4255 script push master and maint branches with a delay between each
4256 branch. These delays trigger the CI jobs in a set order, which
4257 should show the most likely failures first. Also make pushes
4258 atomic by default, and make the script pass any command-line
4259 arguments to git push. Closes ticket 29879.
4260 - Call the shellcheck script from the pre-commit hook. Closes
4262 - Skip pushing test branches that are the same as a remote
4263 maint/release/master branch in git-push-all.sh by default. Add a
4264 -s argument, so git-push-all.sh can push all test branches. Closes
4267 o Minor features (IPv6, logging):
4268 - Log IPv6 addresses as well as IPv4 addresses when describing
4269 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
4271 o Minor features (onion service v3):
4272 - Do not allow single hop clients to fetch or post an HS descriptor
4273 from an HSDir. Closes ticket 24964.
4275 o Minor features (onion service):
4276 - Disallow single-hop clients at the introduction point. We've
4277 removed Tor2web support a while back and single-hop rendezvous
4278 attempts are blocked at the relays. This change should remove load
4279 off the network from spammy clients. Close ticket 24963.
4281 o Minor features (stem tests):
4282 - Change "make test-stem" so it only runs the stem tests that use
4283 tor. This change makes test-stem faster and more reliable. Closes
4286 o Minor features (testing):
4287 - Add a script to invoke "tor --dump-config" and "tor
4288 --verify-config" with various configuration options, and see
4289 whether tor's resulting configuration or error messages are what
4290 we expect. Use it for integration testing of our +Option and
4291 /Option flags. Closes ticket 31637.
4292 - Improve test coverage for our existing configuration parsing and
4293 management API. Closes ticket 30893.
4294 - Add integration tests to make sure that practracker gives the
4295 outputs we expect. Closes ticket 31477.
4296 - The practracker self-tests are now run as part of the Tor test
4297 suite. Closes ticket 31304.
4299 o Minor features (token bucket):
4300 - Implement a generic token bucket that uses a single counter, for
4301 use in anti-DoS onion service work. Closes ticket 30687.
4303 o Minor bugfixes (best practices tracker):
4304 - Fix a few issues in the best-practices script, including tests,
4305 tab tolerance, error reporting, and directory-exclusion logic.
4306 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
4307 - When running check-best-practices, only consider files in the src
4308 subdirectory. Previously we had recursively considered all
4309 subdirectories, which made us get confused by the temporary
4310 directories made by "make distcheck". Fixes bug 31578; bugfix
4313 o Minor bugfixes (build system):
4314 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
4315 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
4317 o Minor bugfixes (chutney, makefiles, documentation):
4318 - "make test-network-all" now shows the warnings from each test-
4319 network.sh run on the console, so developers see new warnings
4320 early. We've also improved the documentation for this feature, and
4321 renamed a Makefile variable so the code is self-documenting. Fixes
4322 bug 30455; bugfix on 0.3.0.4-rc.
4324 o Minor bugfixes (compilation):
4325 - Add more stub functions to fix compilation on Android with link-
4326 time optimization when --disable-module-dirauth is used.
4327 Previously, these compilation settings would make the compiler
4328 look for functions that didn't exist. Fixes bug 31552; bugfix
4330 - Suppress spurious float-conversion warnings from GCC when calling
4331 floating-point classifier functions on FreeBSD. Fixes part of bug
4332 31687; bugfix on 0.3.1.5-alpha.
4334 o Minor bugfixes (configuration):
4335 - Invalid floating-point values in the configuration file are now
4336 treated as errors in the configuration. Previously, they were
4337 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
4339 o Minor bugfixes (coverity):
4340 - Add an assertion when parsing a BEGIN cell so that coverity can be
4341 sure that we are not about to dereference a NULL address. Fixes
4342 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
4343 - In our siphash implementation, when building for coverity, use
4344 memcpy in place of a switch statement, so that coverity can tell
4345 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
4346 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
4347 - Fix several coverity warnings from our unit tests. Fixes bug
4348 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
4350 o Minor bugfixes (developer tooling):
4351 - Only log git script changes in the post-merge script when the
4352 merge was to the master branch. Fixes bug 31040; bugfix
4355 o Minor bugfixes (directory authorities):
4356 - Return a distinct status when formatting annotations fails. Fixes
4357 bug 30780; bugfix on 0.2.0.8-alpha.
4359 o Minor bugfixes (error handling):
4360 - On abort, try harder to flush the output buffers of log messages.
4361 On some platforms (macOS), log messages could be discarded when
4362 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4363 - Report the tor version whenever an assertion fails. Previously, we
4364 only reported the Tor version on some crashes, and some non-fatal
4365 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4366 - When tor aborts due to an error, close log file descriptors before
4367 aborting. Closing the logs makes some OSes flush log file buffers,
4368 rather than deleting buffered log lines. Fixes bug 31594; bugfix
4371 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
4372 - When extracting an IPv6 address from a PF-based proxy, verify that
4373 we are actually configured to receive an IPv6 address, and log an
4374 internal error if not. Fixes part of bug 31687; bugfix
4377 o Minor bugfixes (git hooks):
4378 - Remove a duplicate call to practracker from the pre-push hook. The
4379 pre-push hook already calls the pre-commit hook, which calls
4380 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
4382 o Minor bugfixes (git scripts):
4383 - Stop hard-coding the bash path in the git scripts. Some OSes don't
4384 have bash in /usr/bin, others have an ancient bash at this path.
4385 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
4386 - Stop hard-coding the tor master branch name and worktree path in
4387 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
4388 - Allow git-push-all.sh to be run from any directory. Previously,
4389 the script only worked if run from an upstream worktree directory.
4390 Closes ticket 31678.
4392 o Minor bugfixes (guards):
4393 - When tor is missing descriptors for some primary entry guards,
4394 make the log message less alarming. It's normal for descriptors to
4395 expire, as long as tor fetches new ones soon after. Fixes bug
4396 31657; bugfix on 0.3.3.1-alpha.
4398 o Minor bugfixes (ipv6):
4399 - Check for private IPv6 addresses alongside their IPv4 equivalents
4400 when authorities check descriptors. Previously, we only checked
4401 for private IPv4 addresses. Fixes bug 31088; bugfix on
4402 0.2.3.21-rc. Patch by Neel Chauhan.
4403 - When parsing microdescriptors, we should check the IPv6 exit
4404 policy alongside IPv4. Previously, we checked both exit policies
4405 for only router info structures, while microdescriptors were
4406 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
4409 o Minor bugfixes (logging):
4410 - Change log level of message "Hash of session info was not as
4411 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4413 - Fix a code issue that would have broken our parsing of log domains
4414 as soon as we had 33 of them. Fortunately, we still only have 29.
4415 Fixes bug 31451; bugfix on 0.4.1.4-rc.
4417 o Minor bugfixes (memory management):
4418 - Stop leaking a small amount of memory in nt_service_install(), in
4419 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
4422 o Minor bugfixes (networking, IP addresses):
4423 - When parsing addresses via Tor's internal DNS lookup API, reject
4424 IPv4 addresses in square brackets, and accept IPv6 addresses in
4425 square brackets. This change completes the work started in 23082,
4426 making address parsing consistent between tor's internal DNS
4427 lookup and address parsing APIs. Fixes bug 30721; bugfix
4429 - When parsing addresses via Tor's internal address:port parsing and
4430 DNS lookup APIs, require IPv6 addresses with ports to have square
4431 brackets. But allow IPv6 addresses without ports, whether or not
4432 they have square brackets. Fixes bug 30721; bugfix
4435 o Minor bugfixes (onion service v3):
4436 - When purging the client descriptor cache, close any introduction
4437 point circuits associated with purged cache entries. This avoids
4438 picking those circuits later when connecting to the same
4439 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
4441 o Minor bugfixes (onion services):
4442 - In the hs_ident_circuit_t data structure, remove the unused field
4443 circuit_type and the respective argument in hs_ident_circuit_new().
4444 This field was set by clients (for introduction) and services (for
4445 introduction and rendezvous) but was never used afterwards. Fixes
4446 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
4448 o Minor bugfixes (operator tools):
4449 - Make tor-print-ed-signing-cert(1) print certificate expiration
4450 date in RFC 1123 and UNIX timestamp formats, to make output
4451 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
4453 o Minor bugfixes (rust):
4454 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4455 31463; bugfix on 0.3.5.4-alpha.
4456 - Raise the minimum rustc version to 1.31.0, as checked by configure
4457 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
4459 o Minor bugfixes (sendme, code structure):
4460 - Rename the trunnel SENDME file definition from sendme.trunnel to
4461 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
4462 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
4464 o Minor bugfixes (statistics):
4465 - Stop removing the ed25519 signature if the extra info file is too
4466 big. If the signature data was removed, but the keyword was kept,
4467 this could result in an unparseable extra info file. Fixes bug
4468 30958; bugfix on 0.2.7.2-alpha.
4470 o Minor bugfixes (subsystems):
4471 - Make the subsystem init order match the subsystem module
4472 dependencies. Call windows process security APIs as early as
4473 possible. Initialize logging before network and time, so that
4474 network and time can use logging. Fixes bug 31615; bugfix
4477 o Minor bugfixes (testing):
4478 - Teach the util/socketpair_ersatz test to work correctly when we
4479 have no network stack configured. Fixes bug 30804; bugfix
4482 o Minor bugfixes (v2 single onion services):
4483 - Always retry v2 single onion service intro and rend circuits with
4484 a 3-hop path. Previously, v2 single onion services used a 3-hop
4485 path when rendezvous circuits were retried after a remote or
4486 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4487 23818; bugfix on 0.2.9.3-alpha.
4489 o Minor bugfixes (v3 single onion services):
4490 - Always retry v3 single onion service intro and rend circuits with
4491 a 3-hop path. Previously, v3 single onion services used a 3-hop
4492 path when rend circuits were retried after a remote or delayed
4493 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
4494 bugfix on 0.3.2.1-alpha.
4495 - Make v3 single onion services fall back to a 3-hop intro, when all
4496 intro points are unreachable via a 1-hop path. Previously, v3
4497 single onion services failed when all intro nodes were unreachable
4498 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4501 - Improve documentation in circuit padding subsystem. Patch by
4502 Tobias Pulls. Closes ticket 31113.
4503 - Include an example usage for IPv6 ORPort in our sample torrc.
4504 Closes ticket 31320; patch from Ali Raheem.
4505 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4506 notice.html so that operators no longer have to host it
4507 themselves. Closes ticket 31089.
4510 - No longer include recommended package digests in votes as detailed
4511 in proposal 301. The RecommendedPackages torrc option is
4512 deprecated and will no longer have any effect. "package" lines
4513 will still be considered when computing consensuses for consensus
4514 methods that include them. (This change has no effect on the list
4515 of recommended Tor versions, which is still in use.) Closes
4517 - Remove torctl.in from contrib/dist directory. Resolves
4521 - Run shellcheck for all non-third-party shell scripts that are
4522 shipped with Tor. Closes ticket 29533.
4523 - When checking shell scripts, ignore any user-created directories.
4524 Closes ticket 30967.
4526 o Code simplification and refactoring (config handling):
4527 - Extract our variable manipulation code from confparse.c to a new
4528 lower-level typedvar.h module. Closes ticket 30864.
4529 - Lower another layer of object management from confparse.c to a
4530 more general tool. Now typed structure members are accessible via
4531 an abstract type. Implements ticket 30914.
4532 - Move our backend logic for working with configuration and state
4533 files into a lower-level library, since it no longer depends on
4534 any tor-specific functionality. Closes ticket 31626.
4535 - Numerous simplifications in configuration-handling logic: remove
4536 duplicated macro definitions, replace magical names with flags,
4537 and refactor "TestingTorNetwork" to use the same default-option
4538 logic as the rest of Tor. Closes ticket 30935.
4539 - Replace our ad-hoc set of flags for configuration variables and
4540 configuration variable types with fine-grained orthogonal flags
4541 corresponding to the actual behavior we want. Closes ticket 31625.
4543 o Code simplification and refactoring (misc):
4544 - Eliminate some uses of lower-level control reply abstractions,
4545 primarily in the onion_helper functions. Closes ticket 30889.
4546 - Rework bootstrap tracking to use the new publish-subscribe
4547 subsystem. Closes ticket 29976.
4548 - Rewrite format_node_description() and router_get_verbose_nickname()
4549 to use strlcpy() and strlcat(). The previous implementation used
4550 memcpy() and pointer arithmetic, which was error-prone. Closes
4551 ticket 31545. This is CID 1452819.
4552 - Split extrainfo_dump_to_string() into smaller functions. Closes
4554 - Use the ptrdiff_t type consistently for expressing variable
4555 offsets and pointer differences. Previously we incorrectly (but
4556 harmlessly) used int and sometimes off_t for these cases. Closes
4558 - Use the subsystems mechanism to manage the main event loop code.
4559 Closes ticket 30806.
4560 - Various simplifications and minor improvements to the circuit
4561 padding machines. Patch by Tobias Pulls. Closes tickets 31112
4564 o Documentation (hard-coded directories):
4565 - Improve the documentation for the DirAuthority and FallbackDir
4566 torrc options. Closes ticket 30955.
4568 o Documentation (tor.1 man page):
4569 - Fix typo in tor.1 man page: the option is "--help", not "-help".
4570 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
4573 Changes in version 0.4.1.5 - 2019-08-20
4574 This is the first stable release in the 0.4.1.x series. This series
4575 adds experimental circuit-level padding, authenticated SENDME cells to
4576 defend against certain attacks, and several performance improvements
4577 to save on CPU consumption. It fixes bugs in bootstrapping and v3
4578 onion services. It also includes numerous smaller features and
4579 bugfixes on earlier versions.
4581 Per our support policy, we will support the 0.4.1.x series for nine
4582 months, or until three months after the release of a stable 0.4.2.x:
4583 whichever is longer. If you need longer-term support, please stick
4584 with 0.3.5.x, which will we plan to support until Feb 2022.
4586 Below are the changes since 0.4.1.4-rc. For a complete list of changes
4587 since 0.4.0.5, see the ReleaseNotes file.
4589 o Directory authority changes:
4590 - The directory authority "dizum" has a new IP address. Closes
4593 o Minor features (circuit padding logging):
4594 - Demote noisy client-side warn logs about circuit padding to
4595 protocol warnings. Add additional log messages and circuit ID
4596 fields to help with bug 30992 and any other future issues.
4598 o Minor bugfixes (circuit padding negotiation):
4599 - Bump the circuit padding protocol version to explicitly signify
4600 that the HS setup machine support is finalized in 0.4.1.x-stable.
4601 This also means that 0.4.1.x-alpha clients will not negotiate
4602 padding with 0.4.1.x-stable relays, and 0.4.1.x-stable clients
4603 will not negotiate padding with 0.4.1.x-alpha relays (or 0.4.0.x
4604 relays). Fixes bug 31356; bugfix on 0.4.1.1-alpha.
4606 o Minor bugfixes (circuit padding):
4607 - Ignore non-padding cells on padding circuits. This addresses
4608 various warning messages from subsystems that were not expecting
4609 padding circuits. Fixes bug 30942; bugfix on 0.4.1.1-alpha.
4611 o Minor bugfixes (clock skew detection):
4612 - Don't believe clock skew results from NETINFO cells that appear to
4613 arrive before we sent the VERSIONS cells they are responding to.
4614 Previously, we would accept them up to 3 minutes "in the past".
4615 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4617 o Minor bugfixes (compatibility, standards compliance):
4618 - Fix a bug that would invoke undefined behavior on certain
4619 operating systems when trying to asprintf() a string exactly
4620 INT_MAX bytes long. We don't believe this is exploitable, but it's
4621 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
4622 Found and fixed by Tobias Stoeckmann.
4624 o Minor bugfixes (compilation warning):
4625 - Fix a compilation warning on Windows about casting a function
4626 pointer for GetTickCount64(). Fixes bug 31374; bugfix
4629 o Minor bugfixes (compilation):
4630 - Avoid using labs() on time_t, which can cause compilation warnings
4631 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4633 o Minor bugfixes (distribution):
4634 - Do not ship any temporary files found in the
4635 scripts/maint/practracker directory. Fixes bug 31311; bugfix
4638 o Testing (continuous integration):
4639 - In Travis, make stem log a controller trace to the console, and
4640 tail stem's tor log after failure. Closes ticket 30591.
4641 - In Travis, only run the stem tests that use a tor binary. Closes
4645 Changes in version 0.4.1.4-rc - 2019-07-25
4646 Tor 0.4.1.4-rc fixes a few bugs from previous versions of Tor, and
4647 updates to a new list of fallback directories. If no new bugs are
4648 found, the next release in the 0.4.1.x serious should be stable.
4650 o Major bugfixes (circuit build, guard):
4651 - When considering upgrading circuits from "waiting for guard" to
4652 "open", always ignore circuits that are marked for close. Otherwise,
4653 we can end up in the situation where a subsystem is notified that
4654 a closing circuit has just opened, leading to undesirable
4655 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
4657 o Minor features (continuous integration):
4658 - Our Travis configuration now uses Chutney to run some network
4659 integration tests automatically. Closes ticket 29280.
4661 o Minor features (fallback directory list):
4662 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
4663 in December 2018 (of which ~122 were still functional), with a
4664 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
4665 in June 2019. Closes ticket 28795.
4667 o Minor bugfixes (circuit padding):
4668 - On relays, properly check that a padding machine is absent before
4669 logging a warning about it being absent. Fixes bug 30649; bugfix
4671 - Add two NULL checks in unreachable places to silence Coverity (CID
4672 144729 and 1447291) and better future-proof ourselves. Fixes bug
4673 31024; bugfix on 0.4.1.1-alpha.
4675 o Minor bugfixes (crash on exit):
4676 - Avoid a set of possible code paths that could try to use freed
4677 memory in routerlist_free() while Tor was exiting. Fixes bug
4678 31003; bugfix on 0.1.2.2-alpha.
4680 o Minor bugfixes (logging):
4681 - Fix a conflict between the flag used for messaging-domain log
4682 messages, and the LD_NO_MOCK testing flag. Fixes bug 31080; bugfix
4685 o Minor bugfixes (memory leaks):
4686 - Fix a trivial memory leak when parsing an invalid value from a
4687 download schedule in the configuration. Fixes bug 30894; bugfix
4690 o Code simplification and refactoring:
4691 - Remove some dead code from circpad_machine_remove_token() to fix
4692 some Coverity warnings (CID 1447298). Fixes bug 31027; bugfix
4696 Changes in version 0.4.1.3-alpha - 2019-06-25
4697 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
4698 alpha, most of them from earlier release series.
4700 o Major bugfixes (Onion service reachability):
4701 - Properly clean up the introduction point map when circuits change
4702 purpose from onion service circuits to pathbias, measurement, or
4703 other circuit types. This should fix some service-side instances
4704 of introduction point failure. Fixes bug 29034; bugfix
4707 o Minor features (geoip):
4708 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
4709 Country database. Closes ticket 30852.
4711 o Minor features (logging):
4712 - Give a more useful assertion failure message if we think we have
4713 minherit() but we fail to make a region non-inheritable. Give a
4714 compile-time warning if our support for minherit() is incomplete.
4715 Closes ticket 30686.
4717 o Minor bugfixes (circuit isolation):
4718 - Fix a logic error that prevented the SessionGroup sub-option from
4719 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
4721 o Minor bugfixes (continuous integration):
4722 - Allow the test-stem job to fail in Travis, because it sometimes
4723 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
4724 - Skip test_rebind on macOS in Travis, because it is unreliable on
4725 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4726 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
4727 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4729 o Minor bugfixes (directory authorities):
4730 - Stop crashing after parsing an unknown descriptor purpose
4731 annotation. We think this bug can only be triggered by modifying a
4732 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
4734 o Minor bugfixes (pluggable transports):
4735 - When running as a bridge with pluggable transports, always publish
4736 pluggable transport information in our extrainfo descriptor, even
4737 if ExtraInfoStatistics is 0. This information is needed by
4738 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
4741 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
4742 Closes ticket 30630.
4745 Changes in version 0.4.1.2-alpha - 2019-06-06
4746 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
4747 previous alpha, and some much older. It also contains minor testing
4748 improvements, and an improvement to the security of our authenticated
4749 SENDME implementation.
4751 o Major bugfixes (bridges):
4752 - Consider our directory information to have changed when our list
4753 of bridges changes. Previously, Tor would not re-compute the
4754 status of its directory information when bridges changed, and
4755 therefore would not realize that it was no longer able to build
4756 circuits. Fixes part of bug 29875.
4757 - Do not count previously configured working bridges towards our
4758 total of working bridges. Previously, when Tor's list of bridges
4759 changed, it would think that the old bridges were still usable,
4760 and delay fetching router descriptors for the new ones. Fixes part
4761 of bug 29875; bugfix on 0.3.0.1-alpha.
4763 o Major bugfixes (flow control, SENDME):
4764 - Decrement the stream-level package window after packaging a cell.
4765 Previously, it was done inside a log_debug() call, meaning that if
4766 debug logs were not enabled, the decrement would never happen, and
4767 thus the window would be out of sync with the other end point.
4768 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
4770 o Major bugfixes (onion service reachability):
4771 - Properly clean up the introduction point map and associated state
4772 when circuits change purpose from onion service circuits to
4773 pathbias, measurement, or other circuit types. This may fix some
4774 instances of introduction point failure. Fixes bug 29034; bugfix
4777 o Minor features (authenticated SENDME):
4778 - Ensure that there is enough randomness on every circuit to prevent
4779 an attacker from successfully predicting the hashes they will need
4780 to include in authenticated SENDME cells. At a random interval, if
4781 we have not sent randomness already, we now leave some extra space
4782 at the end of a cell that we can fill with random bytes. Closes
4785 o Minor features (continuous integration):
4786 - When running coverage builds on Travis, we now set
4787 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
4790 o Minor features (maintenance):
4791 - Add a new "make autostyle" target that developers can use to apply
4792 all automatic Tor style and consistency conversions to the
4793 codebase. Closes ticket 30539.
4795 o Minor features (testing):
4796 - The circuitpadding tests now use a reproducible RNG implementation,
4797 so that if a test fails, we can learn why. Part of ticket 28878.
4798 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
4799 to set the RNG seed for tests that use a reproducible RNG. Part of
4801 - When running tests in coverage mode, take additional care to make
4802 our coverage deterministic, so that we can accurately track
4803 changes in code coverage. Closes ticket 30519.
4805 o Minor bugfixes (configuration, proxies):
4806 - Fix a bug that prevented us from supporting SOCKS5 proxies that
4807 want authentication along with configured (but unused!)
4808 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
4810 o Minor bugfixes (controller):
4811 - POSTDESCRIPTOR requests should work again. Previously, they were
4812 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
4814 - Repair the HSFETCH command so that it works again. Previously, it
4815 expected a body when it shouldn't have. Fixes bug 30646; bugfix
4818 o Minor bugfixes (developer tooling):
4819 - Fix pre-push hook to allow fixup and squash commits when pushing
4820 to non-upstream git remote. Fixes bug 30286; bugfix
4823 o Minor bugfixes (directory authority):
4824 - Move the "bandwidth-file-headers" line in directory authority
4825 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
4828 o Minor bugfixes (NetBSD):
4829 - Fix usage of minherit() on NetBSD and other platforms that define
4830 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
4831 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
4833 o Minor bugfixes (out-of-memory handler):
4834 - When purging the DNS cache because of an out-of-memory condition,
4835 try purging just the older entries at first. Previously, we would
4836 always purge the whole thing. Fixes bug 29617; bugfix
4839 o Minor bugfixes (portability):
4840 - Avoid crashing in our tor_vasprintf() implementation on systems
4841 that define neither vasprintf() nor _vscprintf(). (This bug has
4842 been here long enough that we question whether people are running
4843 Tor on such systems, but we're applying the fix out of caution.)
4844 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
4847 o Minor bugfixes (shutdown, libevent, memory safety):
4848 - Avoid use-after-free bugs when shutting down, by making sure that
4849 we shut down libevent only after shutting down all of its users.
4850 We believe these are harmless in practice, since they only occur
4851 on the shutdown path, and do not involve any attacker-controlled
4852 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
4854 o Minor bugfixes (static analysis):
4855 - Fix several spurious Coverity warnings about the unit tests, to
4856 lower our chances of missing real warnings in the future. Fixes
4857 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
4860 - Specify torrc paths (with empty files) when launching tor in
4861 integration tests; refrain from reading user and system torrcs.
4862 Resolves issue 29702.
4865 Changes in version 0.4.1.1-alpha - 2019-05-22
4866 This is the first alpha in the 0.4.1.x series. It introduces
4867 lightweight circuit padding to make some onion-service circuits harder
4868 to distinguish, includes a new "authenticated SENDME" feature to make
4869 certain denial-of-service attacks more difficult, and improves
4870 performance in several areas.
4872 o Major features (circuit padding):
4873 - Onion service clients now add padding cells at the start of their
4874 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
4875 look more like general purpose Exit traffic. The overhead for this
4876 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
4877 extra upstream cell and 10 downstream cells for INTRODUCE
4878 circuits. This feature is only enabled when also supported by the
4879 circuit's middle node. (Clients may specify fixed middle nodes
4880 with the MiddleNodes option, and may force-disable this feature
4881 with the CircuitPadding option.) Closes ticket 28634.
4883 o Major features (code organization):
4884 - Tor now includes a generic publish-subscribe message-passing
4885 subsystem that we can use to organize intermodule dependencies. We
4886 hope to use this to reduce dependencies between modules that don't
4887 need to be related, and to generally simplify our codebase. Closes
4890 o Major features (controller protocol):
4891 - Controller commands are now parsed using a generalized parsing
4892 subsystem. Previously, each controller command was responsible for
4893 parsing its own input, which led to strange inconsistencies.
4894 Closes ticket 30091.
4896 o Major features (flow control):
4897 - Implement authenticated SENDMEs as detailed in proposal 289. A
4898 SENDME cell now includes the digest of the traffic that it
4899 acknowledges, so that once an end point receives the SENDME, it
4900 can confirm the other side's knowledge of the previous cells that
4901 were sent, and prevent certain types of denial-of-service attacks.
4902 This behavior is controlled by two new consensus parameters: see
4903 the proposal for more details. Fixes ticket 26288.
4905 o Major features (performance):
4906 - Our node selection algorithm now excludes nodes in linear time.
4907 Previously, the algorithm was quadratic, which could slow down
4908 heavily used onion services. Closes ticket 30307.
4910 o Major features (performance, RNG):
4911 - Tor now constructs a fast secure pseudorandom number generator for
4912 each thread, to use when performance is critical. This PRNG is
4913 based on AES-CTR, using a buffering construction similar to
4914 libottery and the (newer) OpenBSD arc4random() code. It
4915 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
4916 small outputs. Although we believe it to be cryptographically
4917 strong, we are only using it when necessary for performance.
4918 Implements tickets 29023 and 29536.
4920 o Major bugfixes (onion service v3):
4921 - Fix an unreachable bug in which an introduction point could try to
4922 send an INTRODUCE_ACK with a status code that Trunnel would refuse
4923 to encode, leading the relay to assert(). We've consolidated the
4924 ABI values into Trunnel now. Fixes bug 30454; bugfix
4926 - Clients can now handle unknown status codes from INTRODUCE_ACK
4927 cells. (The NACK behavior will stay the same.) This will allow us
4928 to extend status codes in the future without breaking the normal
4929 client behavior. Fixes another part of bug 30454; bugfix
4932 o Minor features (circuit padding):
4933 - We now use a fast PRNG when scheduling circuit padding. Part of
4935 - Allow the padding machine designer to pick the edges of their
4936 histogram instead of trying to compute them automatically using an
4937 exponential formula. Resolves some undefined behavior in the case
4938 of small histograms and allows greater flexibility on machine
4939 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
4940 - Allow circuit padding machines to hold a circuit open until they
4941 are done padding it. Closes ticket 28780.
4943 o Minor features (compile-time modules):
4944 - Add a "--list-modules" command to print a list of which compile-
4945 time modules are enabled. Closes ticket 30452.
4947 o Minor features (continuous integration):
4948 - Remove sudo configuration lines from .travis.yml as they are no
4949 longer needed with current Travis build environment. Resolves
4951 - In Travis, show stem's tor log after failure. Closes ticket 30234.
4953 o Minor features (controller):
4954 - Add onion service version 3 support to the HSFETCH command.
4955 Previously, only version 2 onion services were supported. Closes
4956 ticket 25417. Patch by Neel Chauhan.
4958 o Minor features (debugging):
4959 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
4960 logging of additional information during assert failure. Now we
4961 can use format strings to include information for trouble
4962 shooting. Resolves ticket 29662.
4964 o Minor features (defense in depth):
4965 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
4966 case a bug causes them to be used later. Closes ticket 30176.
4967 Patch from Tobias Stoeckmann.
4968 - Tor now uses a cryptographically strong PRNG even for decisions
4969 that we do not believe are security-sensitive. Previously, for
4970 performance reasons, we had used a trivially predictable linear
4971 congruential generator algorithm for certain load-balancing and
4972 statistical sampling decisions. Now we use our fast RNG in those
4973 cases. Closes ticket 29542.
4975 o Minor features (developer tools):
4976 - Tor's "practracker" test script now checks for files and functions
4977 that seem too long and complicated. Existing overlong functions
4978 and files are accepted for now, but should eventually be
4979 refactored. Closes ticket 29221.
4980 - Add some scripts used for git maintenance to scripts/git. Closes
4982 - Call practracker from pre-push and pre-commit git hooks to let
4983 developers know if they made any code style violations. Closes
4985 - Add a script to check that each header has a well-formed and
4986 unique guard macro. Closes ticket 29756.
4988 o Minor features (geoip):
4989 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
4990 Country database. Closes ticket 30522.
4992 o Minor features (HTTP tunnel):
4993 - Return an informative web page when the HTTPTunnelPort is used as
4994 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
4996 o Minor features (IPv6, v3 onion services):
4997 - Make v3 onion services put IPv6 addresses in service descriptors.
4998 Before this change, service descriptors only contained IPv4
4999 addresses. Implements 26992.
5001 o Minor features (modularity):
5002 - The "--disable-module-dirauth" compile-time option now disables
5003 even more dirauth-only code. Closes ticket 30345.
5005 o Minor features (performance):
5006 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
5007 1.1.1 and later), since they tend to be faster than tiny-keccak.
5008 Closes ticket 28837.
5010 o Minor features (testing):
5011 - Tor's unit test code now contains helper functions to replace the
5012 PRNG with a deterministic or reproducible version for testing.
5013 Previously, various tests implemented this in various ways.
5014 Implements ticket 29732.
5015 - We now have a script, cov-test-determinism.sh, to identify places
5016 where our unit test coverage has become nondeterministic. Closes
5018 - Check that representative subsets of values of `int` and `unsigned
5019 int` can be represented by `void *`. Resolves issue 29537.
5021 o Minor bugfixes (bridge authority):
5022 - Bridge authorities now set bridges as running or non-running when
5023 about to dump their status to a file. Previously, they set bridges
5024 as running in response to a GETINFO command, but those shouldn't
5025 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
5026 Patch by Neel Chauhan.
5028 o Minor bugfixes (channel padding statistics):
5029 - Channel padding write totals and padding-enabled totals are now
5030 counted properly in relay extrainfo descriptors. Fixes bug 29231;
5031 bugfix on 0.3.1.1-alpha.
5033 o Minor bugfixes (circuit padding):
5034 - Add a "CircuitPadding" torrc option to disable circuit padding.
5035 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
5036 - Allow circuit padding machines to specify that they do not
5037 contribute much overhead, and provide consensus flags and torrc
5038 options to force clients to only use these low overhead machines.
5039 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
5040 - Provide a consensus parameter to fully disable circuit padding, to
5041 be used in emergency network overload situations. Fixes bug 30173;
5042 bugfix on 0.4.0.1-alpha.
5043 - The circuit padding subsystem will no longer schedule padding if
5044 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
5045 - Inspect a circuit-level cell queue before sending padding, to
5046 avoid sending padding while too much data is already queued. Fixes
5047 bug 29204; bugfix on 0.4.0.1-alpha.
5048 - Avoid calling monotime_absolute_usec() in circuit padding machines
5049 that do not use token removal or circuit RTT estimation. Fixes bug
5050 29085; bugfix on 0.4.0.1-alpha.
5052 o Minor bugfixes (compilation, unusual configurations):
5053 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
5054 due to missing declarations of abort(), and prevent other such
5055 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
5057 o Minor bugfixes (controller protocol):
5058 - Teach the controller parser to distinguish an object preceded by
5059 an argument list from one without. Previously, it couldn't
5060 distinguish an argument list from the first line of a multiline
5061 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
5063 o Minor bugfixes (directory authority, ipv6):
5064 - Directory authorities with IPv6 support now always mark themselves
5065 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
5066 Patch by Neel Chauhan.
5068 o Minor bugfixes (documentation):
5069 - Improve the documentation for using MapAddress with ".exit". Fixes
5070 bug 30109; bugfix on 0.1.0.1-rc.
5071 - Improve the monotonic time module and function documentation to
5072 explain what "monotonic" actually means, and document some results
5073 that have surprised people. Fixes bug 29640; bugfix
5075 - Use proper formatting when providing an example on quoting options
5076 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
5078 o Minor bugfixes (logging):
5079 - Do not log a warning when running with an OpenSSL version other
5080 than the one Tor was compiled with, if the two versions should be
5081 compatible. Previously, we would warn whenever the version was
5082 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
5083 - Warn operators when the MyFamily option is set but ContactInfo is
5084 missing, as the latter should be set too. Fixes bug 25110; bugfix
5087 o Minor bugfixes (memory leak):
5088 - Avoid a minor memory leak that could occur on relays when failing
5089 to create a "keys" directory. Fixes bug 30148; bugfix
5092 o Minor bugfixes (onion services):
5093 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
5094 implemenation) when failing to load an onion service client
5095 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
5096 - When refusing to launch a controller's HSFETCH request because of
5097 rate-limiting, respond to the controller with a new response,
5098 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
5099 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
5101 - When relaunching a circuit to a rendezvous service, mark the
5102 circuit as needing high-uptime routers as appropriate. Fixes bug
5103 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
5104 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
5105 (IPv6 support for v3 onion services is still incomplete: see
5106 ticket 23493 for details.) Fixes bug 23588; bugfix on
5107 0.3.2.1-alpha. Patch by Neel Chauhan.
5109 o Minor bugfixes (onion services, performance):
5110 - When building circuits to onion services, call tor_addr_parse()
5111 less often. Previously, we called tor_addr_parse() in
5112 circuit_is_acceptable() even if its output wasn't used. This
5113 change should improve performance when building circuits. Fixes
5114 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
5116 o Minor bugfixes (performance):
5117 - When checking whether a node is a bridge, use a fast check to make
5118 sure that its identity is set. Previously, we used a constant-time
5119 check, which is not necessary in this case. Fixes bug 30308;
5120 bugfix on 0.3.5.1-alpha.
5122 o Minor bugfixes (pluggable transports):
5123 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
5124 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
5126 o Minor bugfixes (probability distributions):
5127 - Refactor and improve parts of the probability distribution code
5128 that made Coverity complain. Fixes bug 29805; bugfix
5131 o Minor bugfixes (python):
5132 - Stop assuming that /usr/bin/python3 exists. For scripts that work
5133 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
5134 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
5136 o Minor bugfixes (relay):
5137 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
5138 is auto, act as if ExitRelay is 1. Previously, we would ignore
5139 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
5140 0.3.5.1-alpha. Patch by Neel Chauhan.
5142 o Minor bugfixes (stats):
5143 - When ExtraInfoStatistics is 0, stop including bandwidth usage
5144 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
5145 bridge statistics by country in extra-info documents. Fixes bug
5146 29018; bugfix on 0.2.4.1-alpha.
5148 o Minor bugfixes (testing):
5149 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
5150 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
5151 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
5152 - Fix some incorrect code in the v3 onion service unit tests. Fixes
5153 bug 29243; bugfix on 0.3.2.1-alpha.
5154 - In the "routerkeys/*" tests, check the return values of mkdir()
5155 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
5156 Found by Coverity as CID 1444254.
5157 - Split test_utils_general() into several smaller test functions.
5158 This makes it easier to perform resource deallocation on assert
5159 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
5160 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
5162 o Minor bugfixes (tor-resolve):
5163 - Fix a memory leak in tor-resolve that could happen if Tor gave it
5164 a malformed SOCKS response. (Memory leaks in tor-resolve don't
5165 actually matter, but it's good to fix them anyway.) Fixes bug
5166 30151; bugfix on 0.4.0.1-alpha.
5168 o Code simplification and refactoring:
5169 - Abstract out the low-level formatting of replies on the control
5170 port. Implements ticket 30007.
5171 - Add several assertions in an attempt to fix some Coverity
5172 warnings. Closes ticket 30149.
5173 - Introduce a connection_dir_buf_add() helper function that checks
5174 for compress_state of dir_connection_t and automatically writes a
5175 string to directory connection with or without compression.
5176 Resolves issue 28816.
5177 - Make the base32_decode() API return the number of bytes written,
5178 for consistency with base64_decode(). Closes ticket 28913.
5179 - Move most relay-only periodic events out of mainloop.c into the
5180 relay subsystem. Closes ticket 30414.
5181 - Refactor and encapsulate parts of the codebase that manipulate
5182 crypt_path_t objects. Resolves issue 30236.
5183 - Refactor several places in our code that Coverity incorrectly
5184 believed might have memory leaks. Closes ticket 30147.
5185 - Remove redundant return values in crypto_format, and the
5186 associated return value checks elsewhere in the code. Make the
5187 implementations in crypto_format consistent, and remove redundant
5188 code. Resolves ticket 29660.
5189 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
5190 it is not a constant-time function. Closes ticket 30309.
5191 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
5192 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
5193 bugfix on 0.3.2.1-alpha.
5194 - Simplify v3 onion service link specifier handling code. Fixes bug
5195 23576; bugfix on 0.3.2.1-alpha.
5196 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
5197 code. Resolves ticket 29108.
5198 - Split control.c into several submodules, in preparation for
5199 distributing its current responsibilities throughout the codebase.
5200 Closes ticket 29894.
5201 - Start to move responsibility for knowing about periodic events to
5202 the appropriate subsystems, so that the mainloop doesn't need to
5203 know all the periodic events in the rest of the codebase.
5204 Implements tickets 30293 and 30294.
5207 - Document how to find git commits and tags for bug fixes in
5208 CodingStandards.md. Update some file documentation. Closes
5212 - Remove the linux-tor-prio.sh script from contrib/operator-tools
5213 directory. Resolves issue 29434.
5214 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
5215 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
5218 o Code simplification and refactoring (shell scripts):
5219 - Clean up many of our shell scripts to fix shellcheck warnings.
5220 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
5221 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
5222 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
5223 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
5224 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
5225 nagios-check-tor-authority-cert (ticket 29071),
5226 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
5227 (ticket 29060), test_key_expiration.sh (ticket 30002),
5228 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
5231 o Testing (chutney):
5232 - In "make test-network-all", test IPv6-only v3 single onion
5233 services, using the chutney network single-onion-v23-ipv6-md.
5234 Closes ticket 27251.
5237 Changes in version 0.4.0.5 - 2019-05-02
5238 This is the first stable release in the 0.4.0.x series. It contains
5239 improvements for power management and bootstrap reporting, as well as
5240 preliminary backend support for circuit padding to prevent some kinds
5241 of traffic analysis. It also continues our work in refactoring Tor for
5242 long-term maintainability.
5244 Per our support policy, we will support the 0.4.0.x series for nine
5245 months, or until three months after the release of a stable 0.4.1.x:
5246 whichever is longer. If you need longer-term support, please stick
5247 with 0.3.5.x, which will we plan to support until Feb 2022.
5249 Below are the changes since 0.4.0.4-rc. For a complete list of changes
5250 since 0.3.5.7, see the ReleaseNotes file.
5252 o Minor features (continuous integration):
5253 - In Travis, tell timelimit to use stem's backtrace signals, and
5254 launch python directly from timelimit, so python receives the
5255 signals from timelimit, rather than make. Closes ticket 30117.
5257 o Minor features (diagnostic):
5258 - Add more diagnostic log messages in an attempt to solve the issue
5259 of NUL bytes appearing in a microdescriptor cache. Related to
5262 o Minor features (testing):
5263 - Use the approx_time() function when setting the "Expires" header
5264 in directory replies, to make them more testable. Needed for
5267 o Minor bugfixes (rust):
5268 - Abort on panic in all build profiles, instead of potentially
5269 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
5271 o Minor bugfixes (shellcheck):
5272 - Look for scripts in their correct locations during "make
5273 shellcheck". Previously we had looked in the wrong place during
5274 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
5276 o Minor bugfixes (testing):
5277 - Check the time in the "Expires" header using approx_time(). Fixes
5278 bug 30001; bugfix on 0.4.0.4-rc.
5280 o Minor bugfixes (UI):
5281 - Lower log level of unlink() errors during bootstrap. Fixes bug
5282 29930; bugfix on 0.4.0.1-alpha.
5285 Changes in version 0.4.0.4-rc - 2019-04-11
5286 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
5287 several bugs from earlier versions, including some that had affected
5288 stability, and one that prevented relays from working with NSS.
5290 o Major bugfixes (NSS, relay):
5291 - When running with NSS, disable TLS 1.2 ciphersuites that use
5292 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
5293 these ciphersuites don't work -- which caused relays to fail to
5294 handshake with one another when these ciphersuites were enabled.
5295 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
5297 o Minor features (bandwidth authority):
5298 - Make bandwidth authorities ignore relays that are reported in the
5299 bandwidth file with the flag "vote=0". This change allows us to
5300 report unmeasured relays for diagnostic reasons without including
5301 their bandwidth in the bandwidth authorities' vote. Closes
5303 - When a directory authority is using a bandwidth file to obtain the
5304 bandwidth values that will be included in the next vote, serve
5305 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
5308 o Minor features (circuit padding):
5309 - Stop warning about undefined behavior in the probability
5310 distribution tests. Float division by zero may technically be
5311 undefined behavior in C, but it's well defined in IEEE 754.
5312 Partial backport of 29298. Closes ticket 29527; bugfix
5315 o Minor features (continuous integration):
5316 - On Travis Rust builds, cleanup Rust registry and refrain from
5317 caching the "target/" directory to speed up builds. Resolves
5320 o Minor features (dormant mode):
5321 - Add a DormantCanceledByStartup option to tell Tor that it should
5322 treat a startup event as cancelling any previous dormant state.
5323 Integrators should use this option with caution: it should only be
5324 used if Tor is being started because of something that the user
5325 did, and not if Tor is being automatically started in the
5326 background. Closes ticket 29357.
5328 o Minor features (geoip):
5329 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
5330 Country database. Closes ticket 29992.
5332 o Minor features (NSS, diagnostic):
5333 - Try to log an error from NSS (if there is any) and a more useful
5334 description of our situation if we are using NSS and a call to
5335 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
5337 o Minor bugfixes (security):
5338 - Fix a potential double free bug when reading huge bandwidth files.
5339 The issue is not exploitable in the current Tor network because
5340 the vulnerable code is only reached when directory authorities
5341 read bandwidth files, but bandwidth files come from a trusted
5342 source (usually the authorities themselves). Furthermore, the
5343 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
5344 which are not used by any of the current authorities. Fixes bug
5345 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
5347 - Verify in more places that we are not about to create a buffer
5348 with more than INT_MAX bytes, to avoid possible OOB access in the
5349 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
5350 fixed by Tobias Stoeckmann.
5352 o Minor bugfix (continuous integration):
5353 - Reset coverage state on disk after Travis CI has finished. This
5354 should prevent future coverage merge errors from causing the test
5355 suite for the "process" subsystem to fail. The process subsystem
5356 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
5358 - Terminate test-stem if it takes more than 9.5 minutes to run.
5359 (Travis terminates the job after 10 minutes of no output.)
5360 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
5362 o Minor bugfixes (bootstrap reporting):
5363 - During bootstrap reporting, correctly distinguish pluggable
5364 transports from plain proxies. Fixes bug 28925; bugfix
5367 o Minor bugfixes (C correctness):
5368 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
5369 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
5372 o Minor bugfixes (circuitpadding testing):
5373 - Minor tweaks to avoid rare test failures related to timers and
5374 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
5376 o Minor bugfixes (directory authorities):
5377 - Actually include the bandwidth-file-digest line in directory
5378 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
5380 o Minor bugfixes (logging):
5381 - On Windows, when errors cause us to reload a consensus from disk,
5382 tell the user that we are retrying at log level "notice".
5383 Previously we only logged this information at "info", which was
5384 confusing because the errors themselves were logged at "warning".
5385 Improves previous fix for 28614. Fixes bug 30004; bugfix
5388 o Minor bugfixes (pluggable transports):
5389 - Restore old behavior when it comes to discovering the path of a
5390 given Pluggable Transport executable file. A change in
5391 0.4.0.1-alpha had broken this behavior on paths containing a
5392 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
5394 o Minor bugfixes (testing):
5395 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
5396 recent test-network.sh to use new chutney features in CI. Fixes
5397 bug 29703; bugfix on 0.2.9.1-alpha.
5398 - Fix a test failure on Windows caused by an unexpected "BUG"
5399 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
5402 o Minor bugfixes (TLS protocol):
5403 - When classifying a client's selection of TLS ciphers, if the
5404 client ciphers are not yet available, do not cache the result.
5405 Previously, we had cached the unavailability of the cipher list
5406 and never looked again, which in turn led us to assume that the
5407 client only supported the ancient V1 link protocol. This, in turn,
5408 was causing Stem integration tests to stall in some cases. Fixes
5409 bug 30021; bugfix on 0.2.4.8-alpha.
5411 o Code simplification and refactoring:
5412 - Introduce a connection_dir_buf_add() helper function that detects
5413 whether compression is in use, and adds a string accordingly.
5414 Resolves issue 28816.
5415 - Refactor handle_get_next_bandwidth() to use
5416 connection_dir_buf_add(). Implements ticket 29897.
5419 - Clarify that Tor performs stream isolation among *Port listeners
5420 by default. Resolves issue 29121.
5423 Changes in version 0.4.0.3-alpha - 2019-03-22
5424 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
5425 bugs from earlier versions.
5427 o Minor features (address selection):
5428 - Treat the subnet 100.64.0.0/10 as public for some purposes;
5429 private for others. This subnet is the RFC 6598 (Carrier Grade
5430 NAT) IP range, and is deployed by many ISPs as an alternative to
5431 RFC 1918 that does not break existing internal networks. Tor now
5432 blocks SOCKS and control ports on these addresses and warns users
5433 if client ports or ExtORPorts are listening on a RFC 6598 address.
5434 Closes ticket 28525. Patch by Neel Chauhan.
5436 o Minor features (geoip):
5437 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
5438 Country database. Closes ticket 29666.
5440 o Minor bugfixes (circuitpadding):
5441 - Inspect the circuit-level cell queue before sending padding, to
5442 avoid sending padding when too much data is queued. Fixes bug
5443 29204; bugfix on 0.4.0.1-alpha.
5445 o Minor bugfixes (logging):
5446 - Correct a misleading error message when IPv4Only or IPv6Only is
5447 used but the resolved address can not be interpreted as an address
5448 of the specified IP version. Fixes bug 13221; bugfix on
5449 0.2.3.9-alpha. Patch from Kris Katterjohn.
5450 - Log the correct port number for listening sockets when "auto" is
5451 used to let Tor pick the port number. Previously, port 0 was
5452 logged instead of the actual port number. Fixes bug 29144; bugfix
5453 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5454 - Stop logging a BUG() warning when Tor is waiting for exit
5455 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
5457 o Minor bugfixes (memory management):
5458 - Refactor the shared random state's memory management so that it
5459 actually takes ownership of the shared random value pointers.
5460 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
5462 o Minor bugfixes (memory management, testing):
5463 - Stop leaking parts of the shared random state in the shared-random
5464 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
5466 o Minor bugfixes (pluggable transports):
5467 - Fix an assertion failure crash bug when a pluggable transport is
5468 terminated during the bootstrap phase. Fixes bug 29562; bugfix
5471 o Minor bugfixes (Rust, protover):
5472 - Add a missing "Padding" value to the Rust implementation of
5473 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
5475 o Minor bugfixes (single onion services):
5476 - Allow connections to single onion services to remain idle without
5477 being disconnected. Previously, relays acting as rendezvous points
5478 for single onion services were mistakenly closing idle rendezvous
5479 circuits after 60 seconds, thinking that they were unused
5480 directory-fetching circuits that had served their purpose. Fixes
5481 bug 29665; bugfix on 0.2.1.26.
5483 o Minor bugfixes (stats):
5484 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
5485 relay and bridge extra-info documents. Fixes bug 29017; bugfix
5488 o Minor bugfixes (testing):
5489 - Downgrade some LOG_ERR messages in the address/* tests to
5490 warnings. The LOG_ERR messages were occurring when we had no
5491 configured network. We were failing the unit tests, because we
5492 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
5493 29530; bugfix on 0.3.5.8.
5494 - Fix our gcov wrapper script to look for object files at the
5495 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
5496 - Decrease the false positive rate of stochastic probability
5497 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
5499 o Minor bugfixes (Windows, CI):
5500 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
5501 Windows Server 2012 R2 job. The remaining 2 jobs still provide
5502 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
5503 fast_finish, so failed jobs terminate the build immediately. Fixes
5504 bug 29601; bugfix on 0.3.5.4-alpha.
5507 Changes in version 0.3.5.8 - 2019-02-21
5508 Tor 0.3.5.8 backports several fixes from later releases, including fixes
5509 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
5512 It also includes a fix for a medium-severity security bug affecting Tor
5513 0.3.2.1-alpha and later. All Tor instances running an affected release
5514 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
5516 o Major bugfixes (cell scheduler, KIST, security):
5517 - Make KIST consider the outbuf length when computing what it can
5518 put in the outbuf. Previously, KIST acted as though the outbuf
5519 were empty, which could lead to the outbuf becoming too full. It
5520 is possible that an attacker could exploit this bug to cause a Tor
5521 client or relay to run out of memory and crash. Fixes bug 29168;
5522 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5523 TROVE-2019-001 and CVE-2019-8955.
5525 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
5526 - Gracefully handle empty username/password fields in SOCKS5
5527 username/password auth message and allow SOCKS5 handshake to
5528 continue. Previously, we had rejected these handshakes, breaking
5529 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
5531 o Minor features (compilation, backport from 0.4.0.2-alpha):
5532 - Compile correctly when OpenSSL is built with engine support
5533 disabled, or with deprecated APIs disabled. Closes ticket 29026.
5534 Patches from "Mangix".
5536 o Minor features (geoip):
5537 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
5538 Country database. Closes ticket 29478.
5540 o Minor features (testing, backport from 0.4.0.2-alpha):
5541 - Treat all unexpected ERR and BUG messages as test failures. Closes
5544 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
5545 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
5546 connection waiting for a descriptor that we actually have in the
5547 cache. It turns out that this can actually happen, though it is
5548 rare. Now, tor will recover and retry the descriptor. Fixes bug
5549 28669; bugfix on 0.3.2.4-alpha.
5551 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
5552 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
5553 IPv6 socket was bound using an address family of AF_INET instead
5554 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
5557 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
5558 - Update Cargo.lock file to match the version made by the latest
5559 version of Rust, so that "make distcheck" will pass again. Fixes
5560 bug 29244; bugfix on 0.3.3.4-alpha.
5562 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
5563 - Select guards even if the consensus has expired, as long as the
5564 consensus is still reasonably live. Fixes bug 24661; bugfix
5567 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
5568 - Compile correctly on OpenBSD; previously, we were missing some
5569 headers required in order to detect it properly. Fixes bug 28938;
5570 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5572 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
5573 - Describe the contents of the v3 onion service client authorization
5574 files correctly: They hold public keys, not private keys. Fixes
5575 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
5577 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
5578 - Rework rep_hist_log_link_protocol_counts() to iterate through all
5579 link protocol versions when logging incoming/outgoing connection
5580 counts. Tor no longer skips version 5, and we won't have to
5581 remember to update this function when new link protocol version is
5582 developed. Fixes bug 28920; bugfix on 0.2.6.10.
5584 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
5585 - Log more information at "warning" level when unable to read a
5586 private key; log more information at "info" level when unable to
5587 read a public key. We had warnings here before, but they were lost
5588 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
5590 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
5591 - The amount of total available physical memory is now determined
5592 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
5593 when it is defined and a 64-bit variant is not available. Fixes
5594 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
5596 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
5597 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
5598 than one private key for a hidden service. Fixes bug 29040; bugfix
5600 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
5601 "debug" level. Tor used to log it as a warning, which caused very
5602 long log lines to appear for some users. Fixes bug 29135; bugfix
5604 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5605 as a warning. Instead, log it as a protocol warning, because there
5606 is nothing that relay operators can do to fix it. Fixes bug 29029;
5607 bugfix on 0.2.5.7-rc.
5609 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
5610 - Mark outdated dirservers when Tor only has a reasonably live
5611 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
5613 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
5614 - Detect and suppress "bug" warnings from the util/time test on
5615 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
5616 - Do not log an error-level message if we fail to find an IPv6
5617 network interface from the unit tests. Fixes bug 29160; bugfix
5620 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
5621 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
5622 Some users took this phrasing to mean that the mentioned guard was
5623 under their control or responsibility, which it is not. Fixes bug
5624 28895; bugfix on Tor 0.3.0.1-alpha.
5627 Changes in version 0.3.4.11 - 2019-02-21
5628 Tor 0.3.4.11 is the third stable release in its series. It includes
5629 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
5630 later. All Tor instances running an affected release should upgrade to
5631 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
5633 o Major bugfixes (cell scheduler, KIST, security):
5634 - Make KIST consider the outbuf length when computing what it can
5635 put in the outbuf. Previously, KIST acted as though the outbuf
5636 were empty, which could lead to the outbuf becoming too full. It
5637 is possible that an attacker could exploit this bug to cause a Tor
5638 client or relay to run out of memory and crash. Fixes bug 29168;
5639 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5640 TROVE-2019-001 and CVE-2019-8955.
5642 o Minor features (geoip):
5643 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
5644 Country database. Closes ticket 29478.
5646 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
5647 - Update Cargo.lock file to match the version made by the latest
5648 version of Rust, so that "make distcheck" will pass again. Fixes
5649 bug 29244; bugfix on 0.3.3.4-alpha.
5651 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
5652 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5653 as a warning. Instead, log it as a protocol warning, because there
5654 is nothing that relay operators can do to fix it. Fixes bug 29029;
5655 bugfix on 0.2.5.7-rc.
5658 Changes in version 0.3.3.12 - 2019-02-21
5659 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
5660 0.3.2.1-alpha and later. All Tor instances running an affected release
5661 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
5663 This release marks the end of support for the Tor 0.3.3.x series. We
5664 recommend that users switch to either the Tor 0.3.4 series (supported
5665 until at least 10 June 2019), or the Tor 0.3.5 series, which will
5666 receive long-term support until at least 1 Feb 2022.
5668 o Major bugfixes (cell scheduler, KIST, security):
5669 - Make KIST consider the outbuf length when computing what it can
5670 put in the outbuf. Previously, KIST acted as though the outbuf
5671 were empty, which could lead to the outbuf becoming too full. It
5672 is possible that an attacker could exploit this bug to cause a Tor
5673 client or relay to run out of memory and crash. Fixes bug 29168;
5674 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5675 TROVE-2019-001 and CVE-2019-8955.
5677 o Minor features (geoip):
5678 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
5679 Country database. Closes ticket 29478.
5681 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
5682 - Update Cargo.lock file to match the version made by the latest
5683 version of Rust, so that "make distcheck" will pass again. Fixes
5684 bug 29244; bugfix on 0.3.3.4-alpha.
5686 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
5687 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5688 as a warning. Instead, log it as a protocol warning, because there
5689 is nothing that relay operators can do to fix it. Fixes bug 29029;
5690 bugfix on 0.2.5.7-rc.
5693 Changes in version 0.4.0.2-alpha - 2019-02-21
5694 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
5695 bugs from earlier versions, including several that had broken
5696 backward compatibility.
5698 It also includes a fix for a medium-severity security bug affecting Tor
5699 0.3.2.1-alpha and later. All Tor instances running an affected release
5700 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
5702 o Major bugfixes (cell scheduler, KIST, security):
5703 - Make KIST consider the outbuf length when computing what it can
5704 put in the outbuf. Previously, KIST acted as though the outbuf
5705 were empty, which could lead to the outbuf becoming too full. It
5706 is possible that an attacker could exploit this bug to cause a Tor
5707 client or relay to run out of memory and crash. Fixes bug 29168;
5708 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5709 TROVE-2019-001 and CVE-2019-8955.
5711 o Major bugfixes (networking):
5712 - Gracefully handle empty username/password fields in SOCKS5
5713 username/password auth messsage and allow SOCKS5 handshake to
5714 continue. Previously, we had rejected these handshakes, breaking
5715 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
5717 o Major bugfixes (windows, startup):
5718 - When reading a consensus file from disk, detect whether it was
5719 written in text mode, and re-read it in text mode if so. Always
5720 write consensus files in binary mode so that we can map them into
5721 memory later. Previously, we had written in text mode, which
5722 confused us when we tried to map the file on windows. Fixes bug
5723 28614; bugfix on 0.4.0.1-alpha.
5725 o Minor features (compilation):
5726 - Compile correctly when OpenSSL is built with engine support
5727 disabled, or with deprecated APIs disabled. Closes ticket 29026.
5728 Patches from "Mangix".
5730 o Minor features (developer tooling):
5731 - Check that bugfix versions in changes files look like Tor versions
5732 from the versions spec. Warn when bugfixes claim to be on a future
5733 release. Closes ticket 27761.
5734 - Provide a git pre-commit hook that disallows committing if we have
5735 any failures in our code and changelog formatting checks. It is
5736 now available in scripts/maint/pre-commit.git-hook. Implements
5739 o Minor features (directory authority):
5740 - When a directory authority is using a bandwidth file to obtain
5741 bandwidth values, include the digest of that file in the vote.
5742 Closes ticket 26698.
5744 o Minor features (geoip):
5745 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
5746 Country database. Closes ticket 29478.
5748 o Minor features (testing):
5749 - Treat all unexpected ERR and BUG messages as test failures. Closes
5752 o Minor bugfixes (build, compatibility, rust):
5753 - Update Cargo.lock file to match the version made by the latest
5754 version of Rust, so that "make distcheck" will pass again. Fixes
5755 bug 29244; bugfix on 0.3.3.4-alpha.
5757 o Minor bugfixes (compilation):
5758 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
5759 29169; bugfix on 0.4.0.1-alpha.
5760 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
5761 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
5763 o Minor bugfixes (documentation):
5764 - Describe the contents of the v3 onion service client authorization
5765 files correctly: They hold public keys, not private keys. Fixes
5766 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
5768 o Minor bugfixes (linux seccomp sandbox):
5769 - Fix startup crash when experimental sandbox support is enabled.
5770 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
5772 o Minor bugfixes (logging):
5773 - Avoid logging that we are relaxing a circuit timeout when that
5774 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
5775 - Log more information at "warning" level when unable to read a
5776 private key; log more information at "info" level when unable to
5777 read a public key. We had warnings here before, but they were lost
5778 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
5780 o Minor bugfixes (misc):
5781 - The amount of total available physical memory is now determined
5782 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
5783 when it is defined and a 64-bit variant is not available. Fixes
5784 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
5786 o Minor bugfixes (onion services):
5787 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
5788 than one private key for a hidden service. Fixes bug 29040; bugfix
5790 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
5791 "debug" level. Tor used to log it as a warning, which caused very
5792 long log lines to appear for some users. Fixes bug 29135; bugfix
5794 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5795 as a warning. Instead, log it as a protocol warning, because there
5796 is nothing that relay operators can do to fix it. Fixes bug 29029;
5797 bugfix on 0.2.5.7-rc.
5799 o Minor bugfixes (scheduler):
5800 - When re-adding channels to the pending list, check the correct
5801 channel's sched_heap_idx. This issue has had no effect in mainline
5802 Tor, but could have led to bugs down the road in improved versions
5803 of our circuit scheduling code. Fixes bug 29508; bugfix
5806 o Minor bugfixes (tests):
5807 - Fix intermittent failures on an adaptive padding test. Fixes one
5808 case of bug 29122; bugfix on 0.4.0.1-alpha.
5809 - Disable an unstable circuit-padding test that was failing
5810 intermittently because of an ill-defined small histogram. Such
5811 histograms will be allowed again after 29298 is implemented. Fixes
5812 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
5813 - Detect and suppress "bug" warnings from the util/time test on
5814 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
5815 - Do not log an error-level message if we fail to find an IPv6
5816 network interface from the unit tests. Fixes bug 29160; bugfix
5820 - In the manpage entry describing MapAddress torrc setting, use
5821 example IP addresses from ranges specified for use in documentation
5822 by RFC 5737. Resolves issue 28623.
5825 - Remove the old check-tor script. Resolves issue 29072.
5828 Changes in version 0.4.0.1-alpha - 2019-01-18
5829 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
5830 introduces improved features for power and bandwidth conservation,
5831 more accurate reporting of bootstrap progress for user interfaces, and
5832 an experimental backend for an exciting new adaptive padding feature.
5833 There is also the usual assortment of bugfixes and minor features, all
5836 o Major features (battery management, client, dormant mode):
5837 - When Tor is running as a client, and it is unused for a long time,
5838 it can now enter a "dormant" state. When Tor is dormant, it avoids
5839 network and CPU activity until it is reawoken either by a user
5840 request or by a controller command. For more information, see the
5841 configuration options starting with "Dormant". Implements tickets
5843 - The client's memory of whether it is "dormant", and how long it
5844 has spent idle, persists across invocations. Implements
5846 - There is a DormantOnFirstStartup option that integrators can use
5847 if they expect that in many cases, Tor will be installed but
5850 o Major features (bootstrap reporting):
5851 - When reporting bootstrap progress, report the first connection
5852 uniformly, regardless of whether it's a connection for building
5853 application circuits. This allows finer-grained reporting of early
5854 progress than previously possible, with the improvements of ticket
5855 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
5856 - When reporting bootstrap progress, treat connecting to a proxy or
5857 pluggable transport as separate from having successfully used that
5858 proxy or pluggable transport to connect to a relay. Closes tickets
5861 o Major features (circuit padding):
5862 - Implement preliminary support for the circuit padding portion of
5863 Proposal 254. The implementation supports Adaptive Padding (aka
5864 WTF-PAD) state machines for use between experimental clients and
5865 relays. Support is also provided for APE-style state machines that
5866 use probability distributions instead of histograms to specify
5867 inter-packet delay. At the moment, Tor does not provide any
5868 padding state machines that are used in normal operation: for now,
5869 this feature exists solely for experimentation. Closes
5872 o Major features (refactoring):
5873 - Tor now uses an explicit list of its own subsystems when
5874 initializing and shutting down. Previously, these systems were
5875 managed implicitly in various places throughout the codebase.
5876 (There may still be some subsystems using the old system.) Closes
5879 o Minor features (bootstrap reporting):
5880 - When reporting bootstrap progress, stop distinguishing between
5881 situations where only internal paths are available and situations
5882 where external paths are available. Previously, Tor would often
5883 erroneously report that it had only internal paths. Closes
5886 o Minor features (continuous integration):
5887 - Log Python version during each Travis CI job. Resolves
5890 o Minor features (controller):
5891 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
5892 Implements ticket 28843.
5894 o Minor features (developer tooling):
5895 - Provide a git hook script to prevent "fixup!" and "squash!"
5896 commits from ending up in the master branch, as scripts/main/pre-
5897 push.git-hook. Closes ticket 27993.
5899 o Minor features (directory authority):
5900 - Directory authorities support a new consensus algorithm, under
5901 which the family lines in microdescriptors are encoded in a
5902 canonical form. This change makes family lines more compressible
5903 in transit, and on the client. Closes ticket 28266; implements
5906 o Minor features (directory authority, relay):
5907 - Authorities now vote on a "StaleDesc" flag to indicate that a
5908 relay's descriptor is so old that the relay should upload again
5909 soon. Relays treat this flag as a signal to upload a new
5910 descriptor. This flag will eventually let us remove the
5911 'published' date from routerstatus entries, and make our consensus
5912 diffs much smaller. Closes ticket 26770; implements proposal 293.
5914 o Minor features (fallback directory mirrors):
5915 - Update the fallback whitelist based on operator opt-ins and opt-
5916 outs. Closes ticket 24805, patch by Phoul.
5918 o Minor features (FreeBSD):
5919 - On FreeBSD-based systems, warn relay operators if the
5920 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
5921 Closes ticket 28518.
5923 o Minor features (HTTP standards compliance):
5924 - Stop sending the header "Content-type: application/octet-stream"
5925 along with transparently compressed documents: this confused
5926 browsers. Closes ticket 28100.
5928 o Minor features (IPv6):
5929 - We add an option ClientAutoIPv6ORPort, to make clients randomly
5930 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
5931 every time a node is loaded from a new consensus or bridge config.
5932 We expect that this option will enable clients to bootstrap more
5933 quickly without having to determine whether they support IPv4,
5934 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
5935 - When using addrs_in_same_network_family(), avoid choosing circuit
5936 paths that pass through the same IPv6 subnet more than once.
5937 Previously, we only checked IPv4 subnets. Closes ticket 24393.
5938 Patch by Neel Chauhan.
5940 o Minor features (log messages):
5941 - Improve log message in v3 onion services that could print out
5942 negative revision counters. Closes ticket 27707. Patch
5945 o Minor features (memory usage):
5946 - Save memory by storing microdescriptor family lists with a more
5947 compact representation. Closes ticket 27359.
5948 - Tor clients now use mmap() to read consensus files from disk, so
5949 that they no longer need keep the full text of a consensus in
5950 memory when parsing it or applying a diff. Closes ticket 27244.
5952 o Minor features (parsing):
5953 - Directory authorities now validate that router descriptors and
5954 ExtraInfo documents are in a valid subset of UTF-8, and reject
5955 them if they are not. Closes ticket 27367.
5957 o Minor features (performance):
5958 - Cache the results of summarize_protocol_flags(), so that we don't
5959 have to parse the same protocol-versions string over and over.
5960 This should save us a huge number of malloc calls on startup, and
5961 may reduce memory fragmentation with some allocators. Closes
5963 - Remove a needless memset() call from get_token_arguments, thereby
5964 speeding up the tokenization of directory objects by about 20%.
5965 Closes ticket 28852.
5966 - Replace parse_short_policy() with a faster implementation, to
5967 improve microdescriptor parsing time. Closes ticket 28853.
5968 - Speed up directory parsing a little by avoiding use of the non-
5969 inlined strcmp_len() function. Closes ticket 28856.
5970 - Speed up microdescriptor parsing by about 30%, to help improve
5971 startup time. Closes ticket 28839.
5973 o Minor features (pluggable transports):
5974 - Add support for emitting STATUS updates to Tor's control port from
5975 a pluggable transport process. Closes ticket 28846.
5976 - Add support for logging to Tor's logging subsystem from a
5977 pluggable transport process. Closes ticket 28180.
5979 o Minor features (process management):
5980 - Add a new process API for handling child processes. This new API
5981 allows Tor to have bi-directional communication with child
5982 processes on both Unix and Windows. Closes ticket 28179.
5983 - Use the subsystem manager to initialize and shut down the process
5984 module. Closes ticket 28847.
5986 o Minor features (relay):
5987 - When listing relay families, list them in canonical form including
5988 the relay's own identity, and try to give a more useful set of
5989 warnings. Part of ticket 28266 and proposal 298.
5991 o Minor features (required protocols):
5992 - Before exiting because of a missing required protocol, Tor will
5993 now check the publication time of the consensus, and not exit
5994 unless the consensus is newer than the Tor program's own release
5995 date. Previously, Tor would not check the consensus publication
5996 time, and so might exit because of a missing protocol that might
5997 no longer be required in a current consensus. Implements proposal
5998 297; closes ticket 27735.
6000 o Minor features (testing):
6001 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
6002 networks. Closes ticket 28840. Patch by Rob Jansen.
6004 o Minor bugfixes (client, clock skew):
6005 - Bootstrap successfully even when Tor's clock is behind the clocks
6006 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
6007 - Select guards even if the consensus has expired, as long as the
6008 consensus is still reasonably live. Fixes bug 24661; bugfix
6011 o Minor bugfixes (compilation):
6012 - Compile correctly on OpenBSD; previously, we were missing some
6013 headers required in order to detect it properly. Fixes bug 28938;
6014 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
6016 o Minor bugfixes (directory clients):
6017 - Mark outdated dirservers when Tor only has a reasonably live
6018 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
6020 o Minor bugfixes (directory mirrors):
6021 - Even when a directory mirror's clock is behind the clocks on the
6022 authorities, we now allow the mirror to serve "future"
6023 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
6025 o Minor bugfixes (DNS):
6026 - Gracefully handle an empty or absent resolve.conf file by falling
6027 back to using "localhost" as a DNS server (and hoping it works).
6028 Previously, we would just stop running as an exit. Fixes bug
6029 21900; bugfix on 0.2.1.10-alpha.
6031 o Minor bugfixes (guards):
6032 - In count_acceptable_nodes(), the minimum number is now one bridge
6033 or guard node, and two non-guard nodes for a circuit. Previously,
6034 we had added up the sum of all nodes with a descriptor, but that
6035 could cause us to build failing circuits when we had either too
6036 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
6037 0.2.3.1-alpha. Patch by Neel Chauhan.
6039 o Minor bugfixes (IPv6):
6040 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
6041 IPv6 socket was bound using an address family of AF_INET instead
6042 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
6045 o Minor bugfixes (logging):
6046 - Rework rep_hist_log_link_protocol_counts() to iterate through all
6047 link protocol versions when logging incoming/outgoing connection
6048 counts. Tor no longer skips version 5, and we won't have to
6049 remember to update this function when new link protocol version is
6050 developed. Fixes bug 28920; bugfix on 0.2.6.10.
6052 o Minor bugfixes (networking):
6053 - Introduce additional checks into tor_addr_parse() to reject
6054 certain incorrect inputs that previously were not detected. Fixes
6055 bug 23082; bugfix on 0.2.0.10-alpha.
6057 o Minor bugfixes (onion service v3, client):
6058 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
6059 connection waiting for a descriptor that we actually have in the
6060 cache. It turns out that this can actually happen, though it is
6061 rare. Now, tor will recover and retry the descriptor. Fixes bug
6062 28669; bugfix on 0.3.2.4-alpha.
6064 o Minor bugfixes (periodic events):
6065 - Refrain from calling routerlist_remove_old_routers() from
6066 check_descriptor_callback(). Instead, create a new hourly periodic
6067 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
6069 o Minor bugfixes (pluggable transports):
6070 - Make sure that data is continously read from standard output and
6071 standard error pipes of a pluggable transport child-process, to
6072 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
6073 bugfix on 0.2.3.6-alpha.
6075 o Minor bugfixes (unit tests):
6076 - Instead of relying on hs_free_all() to clean up all onion service
6077 objects in test_build_descriptors(), we now deallocate them one by
6078 one. This lets Coverity know that we are not leaking memory there
6079 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
6081 o Minor bugfixes (usability):
6082 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
6083 Some users took this phrasing to mean that the mentioned guard was
6084 under their control or responsibility, which it is not. Fixes bug
6085 28895; bugfix on Tor 0.3.0.1-alpha.
6087 o Code simplification and refactoring:
6088 - Reimplement NETINFO cell parsing and generation to rely on
6089 trunnel-generated wire format handling code. Closes ticket 27325.
6090 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
6092 - Rework SOCKS wire format handling to rely on trunnel-generated
6093 parsing/generation code. Resolves ticket 27620.
6094 - Split out bootstrap progress reporting from control.c into a
6095 separate file. Part of ticket 27402.
6096 - The .may_include files that we use to describe our directory-by-
6097 directory dependency structure now describe a noncircular
6098 dependency graph over the directories that they cover. Our
6099 checkIncludes.py tool now enforces this noncircularity. Closes
6103 - Mention that you cannot add a new onion service if Tor is already
6104 running with Sandbox enabled. Closes ticket 28560.
6105 - Improve ControlPort documentation. Mention that it accepts
6106 address:port pairs, and can be used multiple times. Closes
6108 - Document the exact output of "tor --version". Closes ticket 28889.
6111 - Stop responding to the 'GETINFO status/version/num-concurring' and
6112 'GETINFO status/version/num-versioning' control port commands, as
6113 those were deprecated back in 0.2.0.30. Also stop listing them in
6114 output of 'GETINFO info/names'. Resolves ticket 28757.
6115 - The scripts used to generate and maintain the list of fallback
6116 directories have been extracted into a new "fallback-scripts"
6117 repository. Closes ticket 27914.
6120 - Run shellcheck for scripts in the in scripts/ directory. Closes
6122 - Add unit tests for tokenize_string() and get_next_token()
6123 functions. Resolves ticket 27625.
6125 o Code simplification and refactoring (onion service v3):
6126 - Consolidate the authorized client descriptor cookie computation
6127 code from client and service into one function. Closes
6130 o Code simplification and refactoring (shell scripts):
6131 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
6133 - Fix issues that shellcheck found in chutney-git-bisect.sh.
6134 Resolves ticket 28006.
6135 - Fix issues that shellcheck found in updateRustDependencies.sh.
6136 Resolves ticket 28012.
6137 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
6138 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
6139 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
6140 - Fix shellcheck warnings in scripts/test/coverage. Resolves
6144 Changes in version 0.3.3.11 - 2019-01-07
6145 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
6146 numerous fixes, including an important fix for anyone using OpenSSL
6147 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
6148 to this version, or to a later series.
6150 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
6151 We anticipate that this will be the last release of Tor 0.3.3, unless
6152 some major bug is before then. Some time between now and then, users
6153 should switch to either the Tor 0.3.4 series (supported until at least
6154 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
6155 support until at least 1 Feb 2022.
6157 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
6158 - Fix our usage of named groups when running as a TLS 1.3 client in
6159 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6160 running as a relay, which caused clients to fail to negotiate TLS
6161 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6164 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
6165 - Fix a use-after-free error that could be caused by passing Tor an
6166 impossible set of options that would fail during options_act().
6167 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
6169 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
6170 - Only run one online rust build in Travis, to reduce network
6171 errors. Skip offline rust builds on Travis for Linux gcc, because
6172 they're redundant. Implements ticket 27252.
6173 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
6174 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
6175 Linux with default settings, because all the non-default builds
6176 use gcc on Linux. Implements ticket 27252.
6178 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
6179 - Use the Travis Homebrew addon to install packages on macOS during
6180 Travis CI. The package list is the same, but the Homebrew addon
6181 does not do a `brew update` by default. Implements ticket 27738.
6183 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
6184 - Replace the 150 fallbacks originally introduced in Tor
6185 0.3.3.1-alpha in January 2018 (of which ~115 were still
6186 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6187 removed) generated in December 2018. Closes ticket 24803.
6189 o Minor features (geoip):
6190 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
6191 Country database. Closes ticket 29012.
6193 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
6194 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6195 key export function from handling long labels. When this bug is
6196 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6197 version of OpenSSL without this bug when it becomes available.
6198 Closes ticket 28973.
6200 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
6201 - Update relay descriptor on bandwidth changes only when the uptime
6202 is smaller than 24h, in order to reduce the efficiency of guard
6203 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
6205 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
6206 - Avoid undefined behavior in an end-of-string check when parsing
6207 the BEGIN line in a directory object. Fixes bug 28202; bugfix
6210 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
6211 - Rewrite our assertion macros so that they no longer suppress the
6212 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
6214 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
6215 - Initialize a variable unconditionally in aes_new_cipher(), since
6216 some compilers cannot tell that we always initialize it before
6217 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6219 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
6220 - Log additional info when we get a relay that shares an ed25519 ID
6221 with a different relay, instead making a BUG() warning. Fixes bug
6222 27800; bugfix on 0.3.2.1-alpha.
6224 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
6225 - When a user requests a group-readable DataDirectory, give it to
6226 them. Previously, when the DataDirectory and the CacheDirectory
6227 were the same, the default setting (0) for
6228 CacheDirectoryGroupReadable would override the setting for
6229 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
6232 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
6233 - When the onion service directory can't be created or has the wrong
6234 permissions, do not log a stack trace. Fixes bug 27335; bugfix
6237 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
6238 - Close all SOCKS request (for the same .onion) if the newly fetched
6239 descriptor is unusable. Before that, we would close only the first
6240 one leaving the other hanging and let to time out by themselves.
6241 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
6243 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
6244 - Don't warn so loudly when Tor is unable to decode an onion
6245 descriptor. This can now happen as a normal use case if a client
6246 gets a descriptor with client authorization but the client is not
6247 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
6249 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
6250 - When deleting an ephemeral onion service (DEL_ONION), do not close
6251 any rendezvous circuits in order to let the existing client
6252 connections finish by themselves or closed by the application. The
6253 HS v2 is doing that already so now we have the same behavior for
6254 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
6256 o Minor bugfixes (HTTP tunnel):
6257 - Fix a bug warning when closing an HTTP tunnel connection due to
6258 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
6261 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
6262 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
6263 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
6265 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
6266 - Ensure circuitmux queues are empty before scheduling or sending
6267 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
6269 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
6270 - Reject protocol names containing bytes other than alphanumeric
6271 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
6274 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
6275 - Compute protover votes correctly in the rust version of the
6276 protover code. Previously, the protover rewrite in 24031 allowed
6277 repeated votes from the same voter for the same protocol version
6278 to be counted multiple times in protover_compute_vote(). Fixes bug
6279 27649; bugfix on 0.3.3.5-rc.
6280 - Reject protover names that contain invalid characters. Fixes bug
6281 27687; bugfix on 0.3.3.1-alpha.
6283 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
6284 - protover_all_supported() would attempt to allocate up to 16GB on
6285 some inputs, leading to a potential memory DoS. Fixes bug 27206;
6286 bugfix on 0.3.3.5-rc.
6288 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
6289 - Fix a potential null dereference in protover_all_supported(). Add
6290 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
6291 - Return a string that can be safely freed by C code, not one
6292 created by the rust allocator, in protover_all_supported(). Fixes
6293 bug 27740; bugfix on 0.3.3.1-alpha.
6294 - Fix an API mismatch in the rust implementation of
6295 protover_compute_vote(). This bug could have caused crashes on any
6296 directory authorities running Tor with Rust (which we do not yet
6297 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
6299 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
6300 - If a unit test running in a subprocess exits abnormally or with a
6301 nonzero status code, treat the test as having failed, even if the
6302 test reported success. Without this fix, memory leaks don't cause
6303 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
6304 bugfix on 0.2.2.4-alpha.
6306 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
6307 - Treat backtrace test failures as expected on BSD-derived systems
6308 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
6309 (FreeBSD failures have been treated as expected since 18204 in
6310 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
6312 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
6313 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
6314 bugfix on 0.3.0.1-alpha.
6317 Changes in version 0.3.4.10 - 2019-01-07
6318 Tor 0.3.4.9 is the second stable release in its series; it backports
6319 numerous fixes, including an important fix for relays, and for anyone
6320 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
6323 As a reminder, the Tor 0.3.4 series will be supported until 10 June
6324 2019. Some time between now and then, users should switch to the Tor
6325 0.3.5 series, which will receive long-term support until at least 1
6328 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
6329 - Fix our usage of named groups when running as a TLS 1.3 client in
6330 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6331 running as a relay, which caused clients to fail to negotiate TLS
6332 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6335 o Major bugfixes (relay, directory, backport from 0.3.5.7):
6336 - Always reactivate linked connections in the main loop so long as
6337 any linked connection has been active. Previously, connections
6338 serving directory information wouldn't get reactivated after the
6339 first chunk of data was sent (usually 32KB), which would prevent
6340 clients from bootstrapping. Fixes bug 28912; bugfix on
6341 0.3.4.1-alpha. Patch by "cypherpunks3".
6343 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
6344 - Always show the configure and test logs, and upload them as build
6345 artifacts, when building for Windows using Appveyor CI.
6348 o Minor features (controller, backport from 0.3.5.1-alpha):
6349 - For purposes of CIRC_BW-based dropped cell detection, track half-
6350 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
6351 bias check cells to arrive without counting it as dropped until
6352 either the END arrives, or the windows are empty. Closes
6355 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
6356 - Replace the 150 fallbacks originally introduced in Tor
6357 0.3.3.1-alpha in January 2018 (of which ~115 were still
6358 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6359 removed) generated in December 2018. Closes ticket 24803.
6361 o Minor features (geoip):
6362 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
6363 Country database. Closes ticket 28395.
6365 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
6366 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6367 key export function from handling long labels. When this bug is
6368 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6369 version of OpenSSL without this bug when it becomes available.
6370 Closes ticket 28973.
6372 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
6373 - Initialize a variable unconditionally in aes_new_cipher(), since
6374 some compilers cannot tell that we always initialize it before
6375 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6377 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
6378 - Avoid a logging a BUG() stacktrace when closing connection held
6379 open because the write side is rate limited but not the read side.
6380 Now, the connection read side is simply shut down until Tor is
6381 able to flush the connection and close it. Fixes bug 27750; bugfix
6384 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
6385 - Manually configure the zstd compiler options, when building using
6386 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
6387 not come with a pkg-config file. Fixes bug 28454; bugfix
6389 - Stop using an external OpenSSL install, and stop installing MSYS2
6390 packages, when building using mingw on Appveyor Windows CI. Fixes
6391 bug 28399; bugfix on 0.3.4.1-alpha.
6393 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
6394 - Explicitly specify the path to the OpenSSL library and do not
6395 download OpenSSL from Pacman, but instead use the library that is
6396 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
6398 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
6399 - When a user requests a group-readable DataDirectory, give it to
6400 them. Previously, when the DataDirectory and the CacheDirectory
6401 were the same, the default setting (0) for
6402 CacheDirectoryGroupReadable would override the setting for
6403 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
6406 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
6407 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
6408 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
6410 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
6411 - Don't warn so loudly when Tor is unable to decode an onion
6412 descriptor. This can now happen as a normal use case if a client
6413 gets a descriptor with client authorization but the client is not
6414 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
6416 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
6417 - When deleting an ephemeral onion service (DEL_ONION), do not close
6418 any rendezvous circuits in order to let the existing client
6419 connections finish by themselves or closed by the application. The
6420 HS v2 is doing that already so now we have the same behavior for
6421 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
6423 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
6424 - Update relay descriptor on bandwidth changes only when the uptime
6425 is smaller than 24h, in order to reduce the efficiency of guard
6426 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
6428 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
6429 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
6430 bugfix on 0.3.0.1-alpha.
6433 Changes in version 0.3.5.7 - 2019-01-07
6434 Tor 0.3.5.7 is the first stable release in its series; it includes
6435 compilation and portability fixes, and a fix for a severe problem
6436 affecting directory caches.
6438 The Tor 0.3.5 series includes several new features and performance
6439 improvements, including client authorization for v3 onion services,
6440 cleanups to bootstrap reporting, support for improved bandwidth-
6441 measurement tools, experimental support for NSS in place of OpenSSL,
6442 and much more. It also begins a full reorganization of Tor's code
6443 layout, for improved modularity and maintainability in the future.
6444 Finally, there is the usual set of performance improvements and
6445 bugfixes that we try to do in every release series.
6447 There are a couple of changes in the 0.3.5 that may affect
6448 compatibility. First, the default version for newly created onion
6449 services is now v3. Use the HiddenServiceVersion option if you want to
6450 override this. Second, some log messages related to bootstrapping have
6451 changed; if you use stem, you may need to update to the latest version
6452 so it will recognize them.
6454 We have designated 0.3.5 as a "long-term support" (LTS) series: we
6455 will continue to patch major bugs in typical configurations of 0.3.5
6456 until at least 1 Feb 2022. (We do not plan to provide long-term
6457 support for embedding, Rust support, NSS support, running a directory
6458 authority, or unsupported platforms. For these, you will need to stick
6459 with the latest stable release.)
6461 Below are the changes since 0.3.5.6-rc. For a complete list of changes
6462 since 0.3.4.9, see the ReleaseNotes file.
6464 o Major bugfixes (relay, directory):
6465 - Always reactivate linked connections in the main loop so long as
6466 any linked connection has been active. Previously, connections
6467 serving directory information wouldn't get reactivated after the
6468 first chunk of data was sent (usually 32KB), which would prevent
6469 clients from bootstrapping. Fixes bug 28912; bugfix on
6470 0.3.4.1-alpha. Patch by "cypherpunks3".
6472 o Minor features (compilation):
6473 - When possible, place our warning flags in a separate file, to
6474 avoid flooding verbose build logs. Closes ticket 28924.
6476 o Minor features (geoip):
6477 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
6478 Country database. Closes ticket 29012.
6480 o Minor features (OpenSSL bug workaround):
6481 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6482 key export function from handling long labels. When this bug is
6483 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6484 version of OpenSSL without this bug when it becomes available.
6485 Closes ticket 28973.
6487 o Minor features (performance):
6488 - Remove about 96% of the work from the function that we run at
6489 startup to test our curve25519_basepoint implementation. Since
6490 this function has yet to find an actual failure, we now only run
6491 it for 8 iterations instead of 200. Based on our profile
6492 information, this change should save around 8% of our startup time
6493 on typical desktops, and may have a similar effect on other
6494 platforms. Closes ticket 28838.
6495 - Stop re-validating our hardcoded Diffie-Hellman parameters on
6496 every startup. Doing this wasted time and cycles, especially on
6497 low-powered devices. Closes ticket 28851.
6499 o Minor bugfixes (compilation):
6500 - Fix compilation for Android by adding a missing header to
6501 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
6503 o Minor bugfixes (correctness):
6504 - Fix an unreached code path where we checked the value of
6505 "hostname" inside send_resolved_hostname_cell(). Previously, we
6506 used it before checking it; now we check it first. Fixes bug
6507 28879; bugfix on 0.1.2.7-alpha.
6509 o Minor bugfixes (testing):
6510 - Make sure that test_rebind.py actually obeys its timeout, even
6511 when it receives a large number of log messages. Fixes bug 28883;
6512 bugfix on 0.3.5.4-alpha.
6513 - Stop running stem's unit tests as part of "make test-stem", but
6514 continue to run stem's unit and online tests during "make test-
6515 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
6517 o Minor bugfixes (windows services):
6518 - Make Tor start correctly as an NT service again: previously it was
6519 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
6521 o Code simplification and refactoring:
6522 - When parsing a port configuration, make it more obvious to static
6523 analyzer tools that we always initialize the address. Closes
6527 Changes in version 0.3.5.6-rc - 2018-12-18
6528 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
6529 It is the first release candidate in the 0.3.5.x series; if no further
6530 huge bugs are found, our next release may be the stable 0.3.5.x.
6532 o Minor features (continuous integration, Windows):
6533 - Always show the configure and test logs, and upload them as build
6534 artifacts, when building for Windows using Appveyor CI.
6537 o Minor features (fallback directory list):
6538 - Replace the 150 fallbacks originally introduced in Tor
6539 0.3.3.1-alpha in January 2018 (of which ~115 were still
6540 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6541 removed) generated in December 2018. Closes ticket 24803.
6543 o Minor features (geoip):
6544 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
6545 Country database. Closes ticket 28744.
6547 o Minor bugfixes (compilation):
6548 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
6549 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
6551 o Minor bugfixes (continuous integration, Windows):
6552 - Explicitly specify the path to the OpenSSL library and do not
6553 download OpenSSL from Pacman, but instead use the library that is
6554 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
6556 o Minor bugfixes (onion service v3):
6557 - When deleting an ephemeral onion service (DEL_ONION), do not close
6558 any rendezvous circuits in order to let the existing client
6559 connections finish by themselves or closed by the application. The
6560 HS v2 is doing that already so now we have the same behavior for
6561 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
6563 o Minor bugfixes (restart-in-process, boostrap):
6564 - Add missing resets of bootstrap tracking state when shutting down
6565 (regression caused by ticket 27169). Fixes bug 28524; bugfix
6568 o Minor bugfixes (testing):
6569 - Use a separate DataDirectory for the test_rebind script.
6570 Previously, this script would run using the default DataDirectory,
6571 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
6572 Patch from Taylor R Campbell.
6573 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
6574 bugfix on 0.3.0.1-alpha.
6576 o Minor bugfixes (Windows):
6577 - Correctly identify Windows 8.1, Windows 10, and Windows Server
6578 2008 and later from their NT versions. Fixes bug 28096; bugfix on
6579 0.2.2.34; reported by Keifer Bly.
6580 - On recent Windows versions, the GetVersionEx() function may report
6581 an earlier Windows version than the running OS. To avoid user
6582 confusion, add "[or later]" to Tor's version string on affected
6583 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
6585 - Remove Windows versions that were never supported by the
6586 GetVersionEx() function. Stop duplicating the latest Windows
6587 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
6588 reported by Keifer Bly.
6591 - Increase logging and tag all log entries with timestamps in
6592 test_rebind.py. Provides diagnostics for issue 28229.
6594 o Code simplification and refactoring (shared random, dirauth):
6595 - Change many tor_assert() to use BUG() instead. The idea is to not
6596 crash a dirauth but rather scream loudly with a stacktrace and let
6597 it continue run. The shared random subsystem is very resilient and
6598 if anything wrong happens with it, at worst a non coherent value
6599 will be put in the vote and discarded by the other authorities.
6600 Closes ticket 19566.
6602 o Documentation (onion services):
6603 - Document in the man page that changing ClientOnionAuthDir value or
6604 adding a new file in the directory will not work at runtime upon
6605 sending a HUP if Sandbox 1. Closes ticket 28128.
6606 - Note in the man page that the only real way to fully revoke an
6607 onion service v3 client authorization is by restarting the tor
6608 process. Closes ticket 28275.
6611 Changes in version 0.3.5.5-alpha - 2018-11-16
6612 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
6613 including several that we hope to backport to older release series in
6616 o Major bugfixes (OpenSSL, portability):
6617 - Fix our usage of named groups when running as a TLS 1.3 client in
6618 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6619 running as a relay, which caused clients to fail to negotiate TLS
6620 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6623 o Minor features (geoip):
6624 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
6625 Country database. Closes ticket 28395.
6627 o Minor bugfixes (compilation):
6628 - Initialize a variable unconditionally in aes_new_cipher(), since
6629 some compilers cannot tell that we always initialize it before
6630 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6632 o Minor bugfixes (connection, relay):
6633 - Avoid a logging a BUG() stacktrace when closing connection held
6634 open because the write side is rate limited but not the read side.
6635 Now, the connection read side is simply shut down until Tor is
6636 able to flush the connection and close it. Fixes bug 27750; bugfix
6639 o Minor bugfixes (continuous integration, Windows):
6640 - Manually configure the zstd compiler options, when building using
6641 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
6642 not come with a pkg-config file. Fixes bug 28454; bugfix
6644 - Stop using an external OpenSSL install, and stop installing MSYS2
6645 packages, when building using mingw on Appveyor Windows CI. Fixes
6646 bug 28399; bugfix on 0.3.4.1-alpha.
6648 o Minor bugfixes (documentation):
6649 - Make Doxygen work again after the code movement in the 0.3.5
6650 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
6652 o Minor bugfixes (Linux seccomp2 sandbox):
6653 - Permit the "shutdown()" system call, which is apparently used by
6654 OpenSSL under some circumstances. Fixes bug 28183; bugfix
6657 o Minor bugfixes (logging):
6658 - Stop talking about the Named flag in log messages. Clients have
6659 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
6662 o Minor bugfixes (memory leaks):
6663 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
6664 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
6666 o Minor bugfixes (onion services):
6667 - On an intro point for a version 3 onion service, stop closing
6668 introduction circuits on an NACK. This lets the client decide
6669 whether to reuse the circuit or discard it. Previously, we closed
6670 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
6671 0.3.2.1-alpha. Patch by Neel Chaunan.
6672 - When replacing a descriptor in the client cache, make sure to
6673 close all client introduction circuits for the old descriptor, so
6674 we don't end up with unusable leftover circuits. Fixes bug 27471;
6675 bugfix on 0.3.2.1-alpha.
6678 Changes in version 0.3.5.4-alpha - 2018-11-08
6679 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
6680 improves our continuous integration support. It continues our attempts
6681 to stabilize this alpha branch and build it into a foundation for an
6682 acceptable long-term-support release.
6684 o Major bugfixes (compilation, rust):
6685 - Rust tests can now build and run successfully with the
6686 --enable-fragile-hardening option enabled. Doing this currently
6687 requires the rust beta channel; it will be possible with stable
6688 rust once Rust version 1.31 is released. Patch from Alex Crichton.
6689 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
6691 o Major bugfixes (embedding, main loop):
6692 - When DisableNetwork becomes set, actually disable periodic events
6693 that are already enabled. (Previously, we would refrain from
6694 enabling new ones, but we would leave the old ones turned on.)
6695 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
6697 o Minor features (continuous integration):
6698 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
6700 - Add new CI job to Travis configuration to run stem-based
6701 integration tests. Closes ticket 27913.
6703 o Minor features (Windows, continuous integration):
6704 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
6705 Appveyor's CI. Closes ticket 28318.
6707 o Minor bugfixes (C correctness, also in 0.3.4.9):
6708 - Avoid undefined behavior in an end-of-string check when parsing
6709 the BEGIN line in a directory object. Fixes bug 28202; bugfix
6712 o Minor bugfixes (compilation):
6713 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
6714 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
6716 o Minor bugfixes (compilation, OpenSolaris):
6717 - Fix compilation on OpenSolaris and its descendants by adding a
6718 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
6721 o Minor bugfixes (configuration):
6722 - Refuse to start with relative file paths and RunAsDaemon set
6723 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
6726 o Minor bugfixes (directory authority, also in 0.3.4.9):
6727 - Log additional info when we get a relay that shares an ed25519 ID
6728 with a different relay, instead of a BUG() warning with a
6729 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
6731 o Minor bugfixes (onion service v3):
6732 - Build the service descriptor's signing key certificate before
6733 uploading, so we always have a fresh one: leaving no chances for
6734 it to expire service side. Fixes bug 27838; bugfix
6737 o Minor bugfixes (onion service v3, client authorization):
6738 - Fix an assert() when adding a client authorization for the first
6739 time and then sending a HUP signal to the service. Before that,
6740 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
6742 o Minor bugfixes (onion services):
6743 - Unless we have explicitly set HiddenServiceVersion, detect the
6744 onion service version and then look for invalid options.
6745 Previously, we did the reverse, but that broke existing configs
6746 which were pointed to a v2 service and had options like
6747 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
6748 0.3.5.1-alpha. Patch by Neel Chauhan.
6750 o Minor bugfixes (portability):
6751 - Make the OPE code (which is used for v3 onion services) run
6752 correctly on big-endian platforms. Fixes bug 28115; bugfix
6755 o Minor bugfixes (protover, rust):
6756 - Reject extra commas in version strings. Fixes bug 27197; bugfix
6759 o Minor bugfixes (relay shutdown, systemd):
6760 - Notify systemd of ShutdownWaitLength so it can be set to longer
6761 than systemd's TimeoutStopSec. In Tor's systemd service file, set
6762 TimeoutSec to 60 seconds to allow Tor some time to shut down.
6763 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
6765 o Minor bugfixes (rust, also in 0.3.4.9):
6766 - Fix a potential null dereference in protover_all_supported(). Add
6767 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
6768 - Return a string that can be safely freed by C code, not one
6769 created by the rust allocator, in protover_all_supported(). Fixes
6770 bug 27740; bugfix on 0.3.3.1-alpha.
6772 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
6773 - Fix an API mismatch in the rust implementation of
6774 protover_compute_vote(). This bug could have caused crashes on any
6775 directory authorities running Tor with Rust (which we do not yet
6776 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
6778 o Minor bugfixes (testing):
6779 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
6780 27968; bugfix on 0.3.5.1-alpha.
6782 o Minor bugfixes (testing, also in 0.3.4.9):
6783 - Treat backtrace test failures as expected on BSD-derived systems
6784 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
6785 (FreeBSD failures have been treated as expected since 18204 in
6786 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
6788 o Documentation (onion service manpage):
6789 - Improve HSv3 client authorization by making some options more
6790 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
6793 Changes in version 0.3.4.9 - 2018-11-02
6794 Tor 0.3.4.9 is the second stable release in its series; it backports
6795 numerous fixes, including a fix for a bandwidth management bug that
6796 was causing memory exhaustion on relays. Anyone running an earlier
6797 version of Tor 0.3.4.9 should upgrade.
6799 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
6800 - Fix compilation on ARM (and other less-used CPUs) when compiling
6801 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
6803 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
6804 - Make sure Tor bootstraps and works properly if only the
6805 ControlPort is set. Prior to this fix, Tor would only bootstrap
6806 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
6807 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
6809 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
6810 - When our write bandwidth limit is exhausted, stop writing on the
6811 connection. Previously, we had a typo in the code that would make
6812 us stop reading instead, leading to relay connections being stuck
6813 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
6816 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
6817 - Fix a use-after-free error that could be caused by passing Tor an
6818 impossible set of options that would fail during options_act().
6819 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
6821 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
6822 - Don't do a distcheck with --disable-module-dirauth in Travis.
6823 Implements ticket 27252.
6824 - Only run one online rust build in Travis, to reduce network
6825 errors. Skip offline rust builds on Travis for Linux gcc, because
6826 they're redundant. Implements ticket 27252.
6827 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
6828 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
6829 Linux with default settings, because all the non-default builds
6830 use gcc on Linux. Implements ticket 27252.
6832 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
6833 - Use the Travis Homebrew addon to install packages on macOS during
6834 Travis CI. The package list is the same, but the Homebrew addon
6835 does not do a `brew update` by default. Implements ticket 27738.
6837 o Minor features (geoip):
6838 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
6839 Country database. Closes ticket 27991.
6841 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
6842 - Fix an integer overflow bug in our optimized 32-bit millisecond-
6843 difference algorithm for 32-bit Apple platforms. Previously, it
6844 would overflow when calculating the difference between two times
6845 more than 47 days apart. Fixes part of bug 27139; bugfix
6847 - Improve the precision of our 32-bit millisecond difference
6848 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
6849 bugfix on 0.3.4.1-alpha.
6850 - Relax the tolerance on the mainloop/update_time_jumps test when
6851 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
6854 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
6855 - Avoid undefined behavior in an end-of-string check when parsing
6856 the BEGIN line in a directory object. Fixes bug 28202; bugfix
6859 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
6860 - Only install the necessary mingw packages during our appveyor
6861 builds. This change makes the build a little faster, and prevents
6862 a conflict with a preinstalled mingw openssl that appveyor now
6863 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
6865 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
6866 - Rewrite our assertion macros so that they no longer suppress the
6867 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
6869 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
6870 - Stop reinstalling identical packages in our Windows CI. Fixes bug
6871 27464; bugfix on 0.3.4.1-alpha.
6873 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
6874 - Log additional info when we get a relay that shares an ed25519 ID
6875 with a different relay, instead making a BUG() warning. Fixes bug
6876 27800; bugfix on 0.3.2.1-alpha.
6878 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
6879 - Avoid a double-close when shutting down a stalled directory
6880 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
6882 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
6883 - Fix a bug warning when closing an HTTP tunnel connection due to an
6884 HTTP request we couldn't handle. Fixes bug 26470; bugfix
6887 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
6888 - Ensure circuitmux queues are empty before scheduling or sending
6889 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
6891 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
6892 - When the onion service directory can't be created or has the wrong
6893 permissions, do not log a stack trace. Fixes bug 27335; bugfix
6896 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
6897 - Close all SOCKS request (for the same .onion) if the newly fetched
6898 descriptor is unusable. Before that, we would close only the first
6899 one leaving the other hanging and let to time out by themselves.
6900 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
6902 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
6903 - When selecting a v3 rendezvous point, don't only look at the
6904 protover, but also check whether the curve25519 onion key is
6905 present. This way we avoid picking a relay that supports the v3
6906 rendezvous but for which we don't have the microdescriptor. Fixes
6907 bug 27797; bugfix on 0.3.2.1-alpha.
6909 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
6910 - Reject protocol names containing bytes other than alphanumeric
6911 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
6914 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
6915 - Compute protover votes correctly in the rust version of the
6916 protover code. Previously, the protover rewrite in 24031 allowed
6917 repeated votes from the same voter for the same protocol version
6918 to be counted multiple times in protover_compute_vote(). Fixes bug
6919 27649; bugfix on 0.3.3.5-rc.
6920 - Reject protover names that contain invalid characters. Fixes bug
6921 27687; bugfix on 0.3.3.1-alpha.
6923 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
6924 - protover_all_supported() would attempt to allocate up to 16GB on
6925 some inputs, leading to a potential memory DoS. Fixes bug 27206;
6926 bugfix on 0.3.3.5-rc.
6928 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
6929 - Fix an API mismatch in the rust implementation of
6930 protover_compute_vote(). This bug could have caused crashes on any
6931 directory authorities running Tor with Rust (which we do not yet
6932 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
6934 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
6935 - Fix a potential null dereference in protover_all_supported(). Add
6936 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
6937 - Return a string that can be safely freed by C code, not one
6938 created by the rust allocator, in protover_all_supported(). Fixes
6939 bug 27740; bugfix on 0.3.3.1-alpha.
6941 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
6942 - If a unit test running in a subprocess exits abnormally or with a
6943 nonzero status code, treat the test as having failed, even if the
6944 test reported success. Without this fix, memory leaks don't cause
6945 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
6946 bugfix on 0.2.2.4-alpha.
6948 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
6949 - Make the hs_service tests use the same time source when creating
6950 the introduction point and when testing it. Now tests work better
6951 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
6954 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
6955 - Treat backtrace test failures as expected on BSD-derived systems
6956 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
6957 (FreeBSD failures have been treated as expected since 18204 in
6958 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
6961 Changes in version 0.3.5.3-alpha - 2018-10-17
6962 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
6963 versions. One important fix for relays addresses a problem with rate-
6964 limiting code from back in 0.3.4.x: If the fix works out, we'll be
6965 backporting it soon. This release is still an alpha, but we hope it's
6966 getting closer and closer to stability.
6968 o Major features (onion services):
6969 - Version 3 onion services can now use the per-service
6970 HiddenServiceExportCircuitID option to differentiate client
6971 circuits. It communicates with the service by using the HAProxy
6972 protocol to assign virtual IP addresses to inbound client
6973 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
6975 o Major bugfixes (compilation):
6976 - Fix compilation on ARM (and other less-used CPUs) when compiling
6977 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
6979 o Major bugfixes (initialization, crash):
6980 - Fix an assertion crash that would stop Tor from starting up if it
6981 tried to activate a periodic event too early. Fixes bug 27861;
6982 bugfix on 0.3.5.1-alpha.
6984 o Major bugfixes (mainloop, bootstrap):
6985 - Make sure Tor bootstraps and works properly if only the
6986 ControlPort is set. Prior to this fix, Tor would only bootstrap
6987 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
6988 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
6990 o Major bugfixes (relay):
6991 - When our write bandwidth limit is exhausted, stop writing on the
6992 connection. Previously, we had a typo in the code that would make
6993 us stop reading instead, leading to relay connections being stuck
6994 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
6997 o Minor features (continuous integration):
6998 - Use the Travis Homebrew addon to install packages on macOS during
6999 Travis CI. The package list is the same, but the Homebrew addon
7000 does not do a `brew update` by default. Implements ticket 27738.
7001 - Report what program produced the mysterious core file that we
7002 occasionally see on Travis CI during make distcheck. Closes
7005 o Minor features (geoip):
7006 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
7007 Country database. Closes ticket 27991.
7009 o Minor bugfixes (code safety):
7010 - Rewrite our assertion macros so that they no longer suppress the
7011 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
7014 o Minor bugfixes (compilation):
7015 - Compile the ed25519-donna code with a correct declaration of
7016 crypto_strongest_rand(). Previously, we built it with one type,
7017 but linked it against another in the unit tests, which caused
7018 compilation failures with LTO enabled. This could have caused
7019 other undefined behavior in the tests. Fixes bug 27728; bugfix
7022 o Minor bugfixes (compilation, netbsd):
7023 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
7026 o Minor bugfixes (continuous integration, appveyor):
7027 - Install only the necessary mingw packages during our appveyor
7028 builds. This change makes the build a little faster, and prevents
7029 a conflict with a preinstalled mingw openssl that appveyor now
7030 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
7032 o Minor bugfixes (directory permissions):
7033 - When a user requests a group-readable DataDirectory, give it to
7034 them. Previously, when the DataDirectory and the CacheDirectory
7035 were the same, the default setting (0) for
7036 CacheDirectoryGroupReadable would override the setting for
7037 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
7040 o Minor bugfixes (memory leaks):
7041 - Fix a small memory leak when calling Tor with --dump-config. Fixes
7042 bug 27893; bugfix on 0.3.2.1-alpha.
7044 o Minor bugfixes (networking):
7045 - In retry_listeners_ports(), make sure that we're removing a member
7046 of old_conns smartlist at most once. Fixes bug 27808; bugfix
7048 - Refrain from attempting socket rebinding when old and new
7049 listeners are in different address families. Fixes bug 27928;
7050 bugfix on 0.3.5.1-alpha.
7052 o Minor bugfixes (onion service v3):
7053 - Stop dumping a stack trace when trying to connect to an intro
7054 point without having a descriptor for it. Fixes bug 27774; bugfix
7056 - Don't warn so loudly when Tor is unable to decode an onion
7057 descriptor. This can now happen as a normal use case if a client
7058 gets a descriptor with client authorization but the client is not
7059 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
7060 - When selecting a v3 rendezvous point, don't only look at the
7061 protover, but also check whether the curve25519 onion key is
7062 present. This way we avoid picking a relay that supports the v3
7063 rendezvous but for which we don't have the microdescriptor. Fixes
7064 bug 27797; bugfix on 0.3.2.1-alpha.
7066 o Minor bugfixes (protover):
7067 - Reject protocol names containing bytes other than alphanumeric
7068 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
7071 o Minor bugfixes (testing):
7072 - Make the hs_service tests use the same time source when creating
7073 the introduction point and when testing it. Now tests work better
7074 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
7076 - In test_rebind.py, check if the Python version is in the supported
7077 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
7079 o Code simplification and refactoring:
7080 - Divide more large Tor source files -- especially ones that span
7081 multiple areas of functionality -- into smaller parts, including
7082 onion.c and main.c. Closes ticket 26747.
7083 - Divide the "routerparse.c" module into separate modules for each
7084 group of parsed objects. Closes ticket 27924.
7085 - Move protover_rust.c to the same place protover.c was moved to.
7086 Closes ticket 27814.
7087 - Split directory.c into separate pieces for client, server, and
7088 common functionality. Closes ticket 26744.
7089 - Split the non-statistics-related parts from the rephist.c and
7090 geoip.c modules. Closes ticket 27892.
7091 - Split the router.c file into relay-only and shared components, to
7092 help with future modularization. Closes ticket 27864.
7095 - In the tor-resolve(1) manpage, fix the reference to socks-
7096 extensions.txt by adding a web URL. Resolves ticket 27853.
7097 - Mention that we require Python to be 2.7 or newer for some
7098 integration tests that we ship with Tor. Resolves ticket 27677.
7101 Changes in version 0.3.5.2-alpha - 2018-09-21
7102 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
7103 that made Tor think it had run out of sockets. Anybody running a relay
7104 or an onion service on 0.3.5.1-alpha should upgrade.
7106 o Major bugfixes (relay bandwidth statistics):
7107 - When we close relayed circuits, report the data in the circuit
7108 queues as being written in our relay bandwidth stats. This
7109 mitigates guard discovery and other attacks that close circuits
7110 for the explicit purpose of noticing this discrepancy in
7111 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
7113 o Major bugfixes (socket accounting):
7114 - In our socket accounting code, count a socket as closed even when
7115 it is closed indirectly by the TLS layer. Previously, we would
7116 count these sockets as still in use, and incorrectly believe that
7117 we had run out of sockets. Fixes bug 27795; bugfix
7120 o Minor bugfixes (32-bit OSX and iOS, timing):
7121 - Fix an integer overflow bug in our optimized 32-bit millisecond-
7122 difference algorithm for 32-bit Apple platforms. Previously, it
7123 would overflow when calculating the difference between two times
7124 more than 47 days apart. Fixes part of bug 27139; bugfix
7126 - Improve the precision of our 32-bit millisecond difference
7127 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
7128 bugfix on 0.3.4.1-alpha.
7129 - Relax the tolerance on the mainloop/update_time_jumps test when
7130 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
7133 o Minor bugfixes (onion service v3):
7134 - Close all SOCKS request (for the same .onion) if the newly fetched
7135 descriptor is unusable. Before that, we would close only the first
7136 one leaving the other hanging and let to time out by themselves.
7137 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
7139 o Minor bugfixes (memory leak):
7140 - Fix an unlikely memory leak when trying to read a private key from
7141 a ridiculously large file. Fixes bug 27764; bugfix on
7142 0.3.5.1-alpha. This is CID 1439488.
7144 o Minor bugfixes (NSS):
7145 - Correctly detect failure to open a dummy TCP socket when stealing
7146 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
7149 o Minor bugfixes (rust):
7150 - protover_all_supported() would attempt to allocate up to 16GB on
7151 some inputs, leading to a potential memory DoS. Fixes bug 27206;
7152 bugfix on 0.3.3.5-rc.
7154 o Minor bugfixes (testing):
7155 - Revise the "conditionvar_timeout" test so that it succeeds even on
7156 heavily loaded systems where the test threads are not scheduled
7157 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
7159 o Code simplification and refactoring:
7160 - Divide the routerlist.c and dirserv.c modules into smaller parts.
7161 Closes ticket 27799.
7164 Changes in version 0.3.5.1-alpha - 2018-09-18
7165 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
7166 client authorization for modern (v3) onion services, improves
7167 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
7168 support for NSS in place of OpenSSL, and much more.
7170 o Major features (onion services, UI change):
7171 - For a newly created onion service, the default version is now 3.
7172 Tor still supports existing version 2 services, but the operator
7173 now needs to set "HiddenServiceVersion 2" in order to create a new
7174 version 2 service. For existing services, Tor now learns the
7175 version by reading the key file. Closes ticket 27215.
7177 o Major features (relay, UI change):
7178 - Relays no longer run as exits by default. If the "ExitRelay"
7179 option is auto (or unset), and no exit policy is specified with
7180 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
7181 Previously in this case, we allowed exit traffic and logged a
7182 warning message. Closes ticket 21530. Patch by Neel Chauhan.
7183 - Tor now validates that the ContactInfo config option is valid UTF-
7184 8 when parsing torrc. Closes ticket 27428.
7186 o Major features (bootstrap):
7187 - Don't report directory progress until after a connection to a
7188 relay or bridge has succeeded. Previously, we'd report 80%
7189 progress based on cached directory information when we couldn't
7190 even connect to the network. Closes ticket 27169.
7192 o Major features (new code layout):
7193 - Nearly all of Tor's source code has been moved around into more
7194 logical places. The "common" directory is now divided into a set
7195 of libraries in "lib", and files in the "or" directory have been
7196 split into "core" (logic absolutely needed for onion routing),
7197 "feature" (independent modules in Tor), and "app" (to configure
7198 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
7199 more information. Closes ticket 26481.
7201 This refactoring is not complete: although the libraries have been
7202 refactored to be acyclic, the main body of Tor is still too
7203 interconnected. We will attempt to improve this in the future.
7205 o Major features (onion services v3):
7206 - Implement onion service client authorization at the descriptor
7207 level: only authorized clients can decrypt a service's descriptor
7208 to find out how to contact it. A new torrc option was added to
7209 control this client side: ClientOnionAuthDir <path>. On the
7210 service side, if the "authorized_clients/" directory exists in the
7211 onion service directory path, client configurations are read from
7212 the files within. See the manpage for more details. Closes ticket
7213 27547. Patch done by Suphanat Chunhapanya (haxxpop).
7214 - Improve revision counter generation in next-gen onion services.
7215 Onion services can now scale by hosting multiple instances on
7216 different hosts without synchronization between them, which was
7217 previously impossible because descriptors would get rejected by
7218 HSDirs. Addresses ticket 25552.
7220 o Major features (portability, cryptography, experimental, TLS):
7221 - Tor now has the option to compile with the NSS library instead of
7222 OpenSSL. This feature is experimental, and we expect that bugs may
7223 remain. It is mainly intended for environments where Tor's
7224 performance is not CPU-bound, and where NSS is already known to be
7225 installed. To try it out, configure Tor with the --enable-nss
7226 flag. Closes tickets 26631, 26815, and 26816.
7228 If you are experimenting with this option and using an old cached
7229 consensus, Tor may fail to start. To solve this, delete your
7230 "cached-consensus" and "cached-microdesc-consensus" files,
7231 (if present), and restart Tor.
7233 o Major bugfixes (directory authority):
7234 - Actually check that the address we get from DirAuthority
7235 configuration line is valid IPv4. Explicitly disallow DirAuthority
7236 address to be a DNS hostname. Fixes bug 26488; bugfix
7239 o Major bugfixes (restart-in-process):
7240 - Fix a use-after-free error that could be caused by passing Tor an
7241 impossible set of options that would fail during options_act().
7242 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
7244 o Minor features (admin tools):
7245 - Add a new --key-expiration option to print the expiration date of
7246 the signing cert in an ed25519_signing_cert file. Resolves
7249 o Minor features (build):
7250 - If you pass the "--enable-pic" option to configure, Tor will try
7251 to tell the compiler to build position-independent code suitable
7252 to link into a dynamic library. (The default remains -fPIE, for
7253 code suitable for a relocatable executable.) Closes ticket 23846.
7255 o Minor features (code correctness, testing):
7256 - Tor's build process now includes a "check-includes" make target to
7257 verify that no module of Tor relies on any headers from a higher-
7258 level module. We hope to use this feature over time to help
7259 refactor our codebase. Closes ticket 26447.
7261 o Minor features (code layout):
7262 - We have a new "lowest-level" error-handling API for use by code
7263 invoked from within the logging module. With this interface, the
7264 logging code is no longer at risk of calling into itself if a
7265 failure occurs while it is trying to log something. Closes
7268 o Minor features (compilation):
7269 - Tor's configure script now supports a --with-malloc= option to
7270 select your malloc implementation. Supported options are
7271 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
7272 default). Addresses part of ticket 20424. Based on a patch from
7275 o Minor features (config):
7276 - The "auto" keyword in torrc is now case-insensitive. Closes
7279 o Minor features (continuous integration):
7280 - Don't do a distcheck with --disable-module-dirauth in Travis.
7281 Implements ticket 27252.
7282 - Install libcap-dev and libseccomp2-dev so these optional
7283 dependencies get tested on Travis CI. Closes ticket 26560.
7284 - Only run one online rust build in Travis, to reduce network
7285 errors. Skip offline rust builds on Travis for Linux gcc, because
7286 they're redundant. Implements ticket 27252.
7287 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
7288 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
7289 Linux with default settings, because all the non-default builds
7290 use gcc on Linux. Implements ticket 27252.
7292 o Minor features (controller):
7293 - Emit CIRC_BW events as soon as we detect that we processed an
7294 invalid or otherwise dropped cell on a circuit. This allows
7295 vanguards and other controllers to react more quickly to dropped
7296 cells. Closes ticket 27678.
7297 - For purposes of CIRC_BW-based dropped cell detection, track half-
7298 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
7299 bias check cells to arrive without counting it as dropped until
7300 either the END arrives, or the windows are empty. Closes
7302 - Implement a 'GETINFO md/all' controller command to enable getting
7303 all known microdescriptors. Closes ticket 8323.
7304 - The GETINFO command now support an "uptime" argument, to return
7305 Tor's uptime in seconds. Closes ticket 25132.
7307 o Minor features (denial-of-service avoidance):
7308 - Make our OOM handler aware of the DNS cache so that it doesn't
7309 fill up the memory. This check is important for our DoS mitigation
7310 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
7312 o Minor features (development):
7313 - Tor's makefile now supports running the "clippy" Rust style tool
7314 on our Rust code. Closes ticket 22156.
7316 o Minor features (directory authority):
7317 - There is no longer an artificial upper limit on the length of
7318 bandwidth lines. Closes ticket 26223.
7319 - When a bandwidth file is used to obtain the bandwidth measurements,
7320 include this bandwidth file headers in the votes. Closes
7322 - Improved support for networks with only a single authority or a
7323 single fallback directory. Patch from Gabriel Somlo. Closes
7326 o Minor features (embedding API):
7327 - The Tor controller API now supports a function to launch Tor with
7328 a preconstructed owning controller FD, so that embedding
7329 applications don't need to manage controller ports and
7330 authentication. Closes ticket 24204.
7331 - The Tor controller API now has a function that returns the name
7332 and version of the backend implementing the API. Closes
7335 o Minor features (geoip):
7336 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
7337 Country database. Closes ticket 27631.
7339 o Minor features (memory management):
7340 - Get Libevent to use the same memory allocator as Tor, by calling
7341 event_set_mem_functions() during initialization. Resolves
7344 o Minor features (memory usage):
7345 - When not using them, store legacy TAP public onion keys in DER-
7346 encoded format, rather than as expanded public keys. This should
7347 save several megabytes on typical clients. Closes ticket 27246.
7349 o Minor features (OpenSSL):
7350 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
7351 than our own. Resolves ticket 19979.
7353 o Minor features (Rust, code quality):
7354 - Improve rust code quality in the rust protover implementation by
7355 making it more idiomatic. Includes changing an internal API to
7356 take &str instead of &String. Closes ticket 26492.
7358 o Minor features (testing):
7359 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
7360 chutney. Implements ticket 27211.
7362 o Minor features (tor-resolve):
7363 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
7364 Side-effect of the refactoring for ticket 26526.
7366 o Minor features (UI):
7367 - Log each included configuration file or directory as we read it,
7368 to provide more visibility about where Tor is reading from. Patch
7369 from Unto Sten; closes ticket 27186.
7370 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
7371 Closes ticket 26703.
7373 o Minor bugfixes (bootstrap):
7374 - Try harder to get descriptors in non-exit test networks, by using
7375 the mid weight for the third hop when there are no exits. Fixes
7376 bug 27237; bugfix on 0.2.6.2-alpha.
7378 o Minor bugfixes (C correctness):
7379 - Avoid casting smartlist index to int implicitly, as it may trigger
7380 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
7381 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
7382 - Use time_t for all values in
7383 predicted_ports_prediction_time_remaining(). Rework the code that
7384 computes difference between durations/timestamps. Fixes bug 27165;
7385 bugfix on 0.3.1.1-alpha.
7387 o Minor bugfixes (client, memory usage):
7388 - When not running as a directory cache, there is no need to store
7389 the text of the current consensus networkstatus in RAM.
7390 Previously, however, clients would store it anyway, at a cost of
7391 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
7394 o Minor bugfixes (client, reachableaddresses):
7395 - Instead of adding a "reject *:*" line to ReachableAddresses when
7396 loading the configuration, add one to the policy after parsing it
7397 in parse_reachable_addresses(). This prevents extra "reject *.*"
7398 lines from accumulating on reloads. Fixes bug 20874; bugfix on
7399 0.1.1.5-alpha. Patch by Neel Chauhan.
7401 o Minor bugfixes (code quality):
7402 - Rename sandbox_getaddrinfo() and other functions to no longer
7403 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
7404 bugfix on 0.2.7.1-alpha.
7406 o Minor bugfixes (configuration, Onion Services):
7407 - In rend_service_parse_port_config(), disallow any input to remain
7408 after address-port pair was parsed. This will catch address and
7409 port being whitespace-separated by mistake of the user. Fixes bug
7410 27044; bugfix on 0.2.9.10.
7412 o Minor bugfixes (continuous integration):
7413 - Stop reinstalling identical packages in our Windows CI. Fixes bug
7414 27464; bugfix on 0.3.4.1-alpha.
7416 o Minor bugfixes (controller):
7417 - Consider all routerinfo errors other than "not a server" to be
7418 transient for the purpose of "GETINFO exit-policy/*" controller
7419 request. Print stacktrace in the unlikely case of failing to
7420 recompute routerinfo digest. Fixes bug 27034; bugfix
7423 o Minor bugfixes (directory connection shutdown):
7424 - Avoid a double-close when shutting down a stalled directory
7425 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
7427 o Minor bugfixes (HTTP tunnel):
7428 - Fix a bug warning when closing an HTTP tunnel connection due to an
7429 HTTP request we couldn't handle. Fixes bug 26470; bugfix
7432 o Minor bugfixes (ipv6):
7433 - In addrs_in_same_network_family(), we choose the subnet size based
7434 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
7435 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
7436 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
7438 o Minor bugfixes (logging):
7439 - As a precaution, do an early return from log_addr_has_changed() if
7440 Tor is running as client. Also, log a stack trace for debugging as
7441 this function should only be called when Tor runs as server. Fixes
7442 bug 26892; bugfix on 0.1.1.9-alpha.
7443 - Refrain from mentioning bug 21018 in the logs, as it is already
7444 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
7446 o Minor bugfixes (logging, documentation):
7447 - When SafeLogging is enabled, scrub IP address in
7448 channel_tls_process_netinfo_cell(). Also, add a note to manpage
7449 that scrubbing is not guaranteed on loglevels below Notice. Fixes
7450 bug 26882; bugfix on 0.2.4.10-alpha.
7452 o Minor bugfixes (netflow padding):
7453 - Ensure circuitmux queues are empty before scheduling or sending
7454 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
7456 o Minor bugfixes (onion service v2):
7457 - Log at level "info", not "warning", in the case that we do not
7458 have a consensus when a .onion request comes in. This can happen
7459 normally while bootstrapping. Fixes bug 27040; bugfix
7462 o Minor bugfixes (onion service v3):
7463 - When the onion service directory can't be created or has the wrong
7464 permissions, do not log a stack trace. Fixes bug 27335; bugfix
7467 o Minor bugfixes (OS compatibility):
7468 - Properly handle configuration changes that move a listener to/from
7469 wildcard IP address. If the first attempt to bind a socket fails,
7470 close the old listener and try binding the socket again. Fixes bug
7471 17873; bugfix on 0.0.8pre-1.
7473 o Minor bugfixes (performance)::
7474 - Rework node_is_a_configured_bridge() to no longer call
7475 node_get_all_orports(), which was performing too many memory
7476 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
7478 o Minor bugfixes (relay statistics):
7479 - Update relay descriptor on bandwidth changes only when the uptime
7480 is smaller than 24h, in order to reduce the efficiency of guard
7481 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
7483 o Minor bugfixes (relays):
7484 - Consider the fact that we'll be making direct connections to our
7485 entry and guard nodes when computing the fraction of nodes that
7486 have their descriptors. Also, if we are using bridges and there is
7487 at least one bridge with a full descriptor, treat the fraction of
7488 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
7489 Patch by Neel Chauhan.
7490 - Update the message logged on relays when DirCache is disabled.
7491 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
7492 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
7494 o Minor bugfixes (rust, protover):
7495 - Compute protover votes correctly in the rust version of the
7496 protover code. Previously, the protover rewrite in 24031 allowed
7497 repeated votes from the same voter for the same protocol version
7498 to be counted multiple times in protover_compute_vote(). Fixes bug
7499 27649; bugfix on 0.3.3.5-rc.
7500 - Reject protover names that contain invalid characters. Fixes bug
7501 27687; bugfix on 0.3.3.1-alpha.
7503 o Minor bugfixes (testing):
7504 - Fix two unit tests to work when HOME environment variable is not
7505 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
7506 - If a unit test running in a subprocess exits abnormally or with a
7507 nonzero status code, treat the test as having failed, even if the
7508 test reported success. Without this fix, memory leaks don't cause
7509 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
7510 bugfix on 0.2.2.4-alpha.
7511 - When logging a version mismatch in our openssl_version tests,
7512 report the actual offending version strings. Fixes bug 26152;
7513 bugfix on 0.2.9.1-alpha.
7514 - Fix forking tests on Windows when there is a space somewhere in
7515 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
7517 o Code simplification and refactoring:
7518 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
7519 longer needed. Closes ticket 26502.
7520 - Include paths to header files within Tor are now qualified by
7521 directory within the top-level src directory.
7522 - Many structures have been removed from the centralized "or.h"
7523 header, and moved into their own headers. This will allow us to
7524 reduce the number of places in the code that rely on each
7525 structure's contents and layout. Closes ticket 26383.
7526 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
7527 - Remove GetAdaptersAddresses_fn_t. The code that used it was
7528 removed as part of the 26481 refactor. Closes ticket 27467.
7529 - Rework Tor SOCKS server code to use Trunnel and benefit from
7530 autogenerated functions for parsing and generating SOCKS wire
7531 format. New implementation is cleaner, more maintainable and
7532 should be less prone to heartbleed-style vulnerabilities.
7533 Implements a significant fraction of ticket 3569.
7534 - Split sampled_guards_update_from_consensus() and
7535 select_entry_guard_for_circuit() into subfunctions. In
7536 entry_guards_update_primary() unite three smartlist enumerations
7537 into one and move smartlist comparison code out of the function.
7538 Closes ticket 21349.
7539 - Tor now assumes that you have standards-conformant stdint.h and
7540 inttypes.h headers when compiling. Closes ticket 26626.
7541 - Unify our bloom filter logic. Previously we had two copies of this
7542 code: one for routerlist filtering, and one for address set
7543 calculations. Closes ticket 26510.
7544 - Use the simpler strcmpstart() helper in
7545 rend_parse_v2_service_descriptor instead of strncmp(). Closes
7547 - Utility functions that can perform a DNS lookup are now wholly
7548 separated from those that can't, in separate headers and C
7549 modules. Closes ticket 26526.
7552 - Copy paragraph and URL to Tor's code of conduct document from
7553 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
7554 - Remove old instructions from INSTALL document. Closes ticket 26588.
7555 - Warn users that they should not include MyFamily line(s) in their
7556 torrc when running Tor bridge. Closes ticket 26908.
7559 - Tor no longer supports building with the dmalloc library. For
7560 debugging memory issues, we suggest using gperftools or msan
7561 instead. Closes ticket 26426.
7562 - Tor no longer attempts to run on Windows environments without the
7563 GetAdaptersAddresses() function. This function has existed since
7564 Windows XP, which is itself already older than we support.
7565 - Remove Tor2web functionality for version 2 onion services. The
7566 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
7567 (This feature was never shipped in vanilla Tor and it was only
7568 possible to use this feature by building the support at compile
7569 time. Tor2webMode is not implemented for version 3 onion services.)
7570 Closes ticket 26367.
7573 Changes in version 0.2.9.17 - 2018-09-10
7574 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
7576 o Minor features (compatibility, backport from 0.3.4.8):
7577 - Tell OpenSSL to maintain backward compatibility with previous
7578 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7579 ciphers are disabled by default. Closes ticket 27344.
7581 o Minor features (continuous integration, backport from 0.3.4.7-rc):
7582 - Enable macOS builds in our Travis CI configuration. Closes
7584 - Install libcap-dev and libseccomp2-dev so these optional
7585 dependencies get tested on Travis CI. Closes ticket 26560.
7586 - Run asciidoc during Travis CI. Implements ticket 27087.
7587 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7589 o Minor features (geoip):
7590 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7591 Country database. Closes ticket 27089.
7593 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
7594 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7595 tell the compiler not to include the system malloc implementation.
7596 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7598 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
7599 - Silence a spurious compiler warning on the GetAdaptersAddresses
7600 function pointer cast. This issue is already fixed by 26481 in
7601 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7602 bugfix on 0.2.3.11-alpha.
7603 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7604 supported, and always fails. Some compilers warn about the
7605 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
7608 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
7609 - Don't link or search for pthreads when building for Windows, even
7610 if we are using build environment (like mingw) that provides a
7611 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
7613 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
7614 - Skip a pair of unreliable key generation tests on Windows, until
7615 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7616 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7618 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
7619 - Pass the module flags to distcheck configure, and log the flags
7620 before running configure. (Backported to 0.2.9 and later as a
7621 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
7623 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
7624 - When a Travis build fails, and showing a log fails, keep trying to
7625 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
7626 - When we use echo in Travis, don't pass a --flag as the first
7627 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
7629 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
7630 - When voting for recommended versions, make sure that all of the
7631 versions are well-formed and parsable. Fixes bug 26485; bugfix
7634 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
7635 - Fix a bug in out sandboxing rules for the openat() syscall.
7636 Previously, no openat() call would be permitted, which would break
7637 filesystem operations on recent glibc versions. Fixes bug 25440;
7638 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
7640 o Minor bugfixes (onion services, backport from 0.3.4.8):
7641 - Silence a spurious compiler warning in
7642 rend_client_send_introduction(). Fixes bug 27463; bugfix
7645 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
7646 - Log a protocol warning when single onion services or Tor2web clients
7647 fail to authenticate direct connections to relays.
7648 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
7650 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
7651 - Disable core dumps in test_bt.sh, to avoid failures in "make
7652 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
7654 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
7655 - Before running make test-network-all, delete old logs and test
7656 result files, to avoid spurious failures. Fixes bug 27295; bugfix
7659 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
7660 - Our "tortls/cert_matches_key" unit test no longer relies on
7661 OpenSSL internals. Previously, it relied on unsupported OpenSSL
7662 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
7663 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
7665 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
7666 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
7667 27185; bugfix on 0.2.2.2-alpha.
7670 Changes in version 0.3.2.12 - 2018-09-10
7671 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
7673 o Minor features (compatibility, backport from 0.3.4.8):
7674 - Tell OpenSSL to maintain backward compatibility with previous
7675 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7676 ciphers are disabled by default. Closes ticket 27344.
7678 o Minor features (continuous integration, backport from 0.3.4.7-rc):
7679 - Enable macOS builds in our Travis CI configuration. Closes
7681 - Install libcap-dev and libseccomp2-dev so these optional
7682 dependencies get tested on Travis CI. Closes ticket 26560.
7683 - Run asciidoc during Travis CI. Implements ticket 27087.
7684 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7686 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
7687 - Use cargo cache in our Travis CI configuration. Closes
7690 o Minor features (controller, backport from 0.3.4.6-rc):
7691 - The control port now exposes the list of HTTPTunnelPorts and
7692 ExtOrPorts via GETINFO net/listeners/httptunnel and
7693 net/listeners/extor respectively. Closes ticket 26647.
7695 o Minor features (directory authorities, backport from 0.3.4.7-rc):
7696 - Authorities no longer vote to make the subprotocol version
7697 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
7698 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
7700 o Minor features (geoip):
7701 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7702 Country database. Closes ticket 27089.
7704 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
7705 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7706 tell the compiler not to include the system malloc implementation.
7707 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7708 - Don't try to use a pragma to temporarily disable the
7709 -Wunused-const-variable warning if the compiler doesn't support
7710 it. Fixes bug 26785; bugfix on 0.3.2.11.
7712 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
7713 - Silence a spurious compiler warning on the GetAdaptersAddresses
7714 function pointer cast. This issue is already fixed by 26481 in
7715 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7716 bugfix on 0.2.3.11-alpha.
7717 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7718 supported, and always fails. Some compilers warn about the
7719 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
7722 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
7723 - Don't link or search for pthreads when building for Windows, even
7724 if we are using build environment (like mingw) that provides a
7725 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
7727 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
7728 - Skip a pair of unreliable key generation tests on Windows, until
7729 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7730 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7732 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
7733 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
7734 - Pass the module flags to distcheck configure, and log the flags
7735 before running configure. (Backported to 0.2.9 and later as a
7736 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
7738 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
7739 - When a Travis build fails, and showing a log fails, keep trying to
7740 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
7741 - When we use echo in Travis, don't pass a --flag as the first
7742 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
7744 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
7745 - When voting for recommended versions, make sure that all of the
7746 versions are well-formed and parsable. Fixes bug 26485; bugfix
7749 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
7750 - Fix a bug in out sandboxing rules for the openat() syscall.
7751 Previously, no openat() call would be permitted, which would break
7752 filesystem operations on recent glibc versions. Fixes bug 25440;
7753 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
7755 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
7756 - Improve the log message when connection initiators fail to
7757 authenticate direct connections to relays. Fixes bug 26927; bugfix
7760 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
7761 - Fix bug that causes services to not ever rotate their descriptors
7762 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
7765 o Minor bugfixes (onion services, backport from 0.3.4.8):
7766 - Silence a spurious compiler warning in
7767 rend_client_send_introduction(). Fixes bug 27463; bugfix
7770 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
7771 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
7773 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
7774 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
7775 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
7776 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
7778 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
7779 - Log a protocol warning when single onion services or Tor2web clients
7780 fail to authenticate direct connections to relays.
7781 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
7783 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
7784 - Disable core dumps in test_bt.sh, to avoid failures in "make
7785 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
7787 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
7788 - When running make test-network-all, use the mixed+hs-v2 network.
7789 (A previous fix to chutney removed v3 onion services from the
7790 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
7791 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
7792 - Before running make test-network-all, delete old logs and test
7793 result files, to avoid spurious failures. Fixes bug 27295; bugfix
7796 o Minor bugfixes (testing, openssl compatibility):
7797 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
7798 internals. Previously, it relied on unsupported OpenSSL behavior in
7799 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
7800 bugfix on 0.2.5.1-alpha.
7802 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
7803 - Our "tortls/cert_matches_key" unit test no longer relies on
7804 OpenSSL internals. Previously, it relied on unsupported OpenSSL
7805 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
7806 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
7808 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
7809 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
7810 27185; bugfix on 0.2.2.2-alpha.
7813 Changes in version 0.3.3.10 - 2018-09-10
7814 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
7816 o Minor features (bug workaround, backport from 0.3.4.7-rc):
7817 - Compile correctly on systems that provide the C11 stdatomic.h
7818 header, but where C11 atomic functions don't actually compile.
7819 Closes ticket 26779; workaround for Debian issue 903709.
7821 o Minor features (compatibility, backport from 0.3.4.8):
7822 - Tell OpenSSL to maintain backward compatibility with previous
7823 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7824 ciphers are disabled by default. Closes ticket 27344.
7826 o Minor features (continuous integration, backport from 0.3.4.7-rc):
7827 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
7828 - Enable macOS builds in our Travis CI configuration. Closes
7830 - Install libcap-dev and libseccomp2-dev so these optional
7831 dependencies get tested on Travis CI. Closes ticket 26560.
7832 - Run asciidoc during Travis CI. Implements ticket 27087.
7833 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7835 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
7836 - Use cargo cache in our Travis CI configuration. Closes
7839 o Minor features (controller, backport from 0.3.4.6-rc):
7840 - The control port now exposes the list of HTTPTunnelPorts and
7841 ExtOrPorts via GETINFO net/listeners/httptunnel and
7842 net/listeners/extor respectively. Closes ticket 26647.
7844 o Minor features (directory authorities, backport from 0.3.4.7-rc):
7845 - Authorities no longer vote to make the subprotocol version
7846 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
7847 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
7849 o Minor features (geoip):
7850 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7851 Country database. Closes ticket 27089.
7853 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
7854 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7855 tell the compiler not to include the system malloc implementation.
7856 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7857 - Don't try to use a pragma to temporarily disable the
7858 -Wunused-const-variable warning if the compiler doesn't support
7859 it. Fixes bug 26785; bugfix on 0.3.2.11.
7861 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
7862 - Silence a spurious compiler warning on the GetAdaptersAddresses
7863 function pointer cast. This issue is already fixed by 26481 in
7864 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7865 bugfix on 0.2.3.11-alpha.
7866 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7867 supported, and always fails. Some compilers warn about the
7868 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
7871 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
7872 - Don't link or search for pthreads when building for Windows, even
7873 if we are using build environment (like mingw) that provides a
7874 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
7876 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
7877 - Skip a pair of unreliable key generation tests on Windows, until
7878 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7879 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7881 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
7882 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
7883 - Pass the module flags to distcheck configure, and log the flags
7884 before running configure. (Backported to 0.2.9 and later as a
7885 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
7887 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
7888 - When a Travis build fails, and showing a log fails, keep trying to
7889 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
7890 - When we use echo in Travis, don't pass a --flag as the first
7891 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
7893 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
7894 - When voting for recommended versions, make sure that all of the
7895 versions are well-formed and parsable. Fixes bug 26485; bugfix
7898 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
7899 - Always call tor_free_all() when leaving tor_run_main(). When we
7900 did not, restarting tor in-process would cause an assertion
7901 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
7903 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
7904 - Fix a bug in our sandboxing rules for the openat() syscall.
7905 Previously, no openat() call would be permitted, which would break
7906 filesystem operations on recent glibc versions. Fixes bug 25440;
7907 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
7909 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
7910 - Improve the log message when connection initiators fail to
7911 authenticate direct connections to relays. Fixes bug 26927; bugfix
7914 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
7915 - Fix bug that causes services to not ever rotate their descriptors
7916 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
7919 o Minor bugfixes (onion services, backport from 0.3.4.8):
7920 - Silence a spurious compiler warning in
7921 rend_client_send_introduction(). Fixes bug 27463; bugfix
7924 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
7925 - Work around two different bugs in the OS X 10.10 and later SDKs
7926 that would prevent us from successfully targeting earlier versions
7927 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
7929 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
7930 - Fix compilation of the unit tests on GNU/Hurd, which does not
7931 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
7934 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
7935 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
7937 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
7938 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
7939 - Protover parsing was accepting the presence of whitespace in
7940 version strings, which the C implementation would choke on, e.g.
7941 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
7942 - Protover parsing was ignoring a 2nd hyphen and everything after
7943 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
7945 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
7946 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
7947 - cd to ${abs_top_builddir}/src/rust before running cargo in
7948 src/test/test_rust.sh. This makes the working directory consistent
7949 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
7951 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
7952 - Log a protocol warning when single onion services or Tor2web clients
7953 fail to authenticate direct connections to relays.
7954 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
7956 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
7957 - Disable core dumps in test_bt.sh, to avoid failures in "make
7958 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
7960 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
7961 - When running make test-network-all, use the mixed+hs-v2 network.
7962 (A previous fix to chutney removed v3 onion services from the
7963 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
7964 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
7965 - Before running make test-network-all, delete old logs and test
7966 result files, to avoid spurious failures. Fixes bug 27295; bugfix
7969 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
7970 - Our "tortls/cert_matches_key" unit test no longer relies on
7971 OpenSSL internals. Previously, it relied on unsupported OpenSSL
7972 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
7973 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
7975 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
7976 - Stop sending ed25519 link specifiers in v3 onion service introduce
7977 cells and descriptors, when the rendezvous or introduction point
7978 doesn't support ed25519 link authentication. Fixes bug 26627;
7979 bugfix on 0.3.2.4-alpha.
7981 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
7982 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
7983 27185; bugfix on 0.2.2.2-alpha.
7986 Changes in version 0.3.4.8 - 2018-09-10
7987 Tor 0.3.4.8 is the first stable release in its series; it includes
7988 compilation and portability fixes.
7990 The Tor 0.3.4 series includes improvements for running Tor in
7991 low-power and embedded environments, which should help performance in
7992 general. We've begun work on better modularity, and included preliminary
7993 changes on the directory authority side to accommodate a new bandwidth
7994 measurement system. We've also integrated more continuous-integration
7995 systems into our development process, and made corresponding changes to
7996 Tor's testing infrastructure. Finally, we've continued to refine
7997 our anti-denial-of-service code.
7999 Below are the changes since 0.3.4.7-rc. For a complete list of changes
8000 since 0.3.3.9, see the ReleaseNotes file.
8002 o Minor features (compatibility):
8003 - Tell OpenSSL to maintain backward compatibility with previous
8004 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
8005 ciphers are disabled by default. Closes ticket 27344.
8007 o Minor features (continuous integration):
8008 - Log the compiler path and version during Appveyor builds.
8009 Implements ticket 27449.
8010 - Show config.log and test-suite.log after failed Appveyor builds.
8011 Also upload the zipped full logs as a build artifact. Implements
8014 o Minor bugfixes (compilation):
8015 - Silence a spurious compiler warning on the GetAdaptersAddresses
8016 function pointer cast. This issue is already fixed by 26481 in
8017 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
8018 bugfix on 0.2.3.11-alpha.
8019 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
8020 supported, and always fails. Some compilers warn about the
8021 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
8024 o Minor bugfixes (continuous integration):
8025 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
8026 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
8027 Executables compiled for 64-bit Windows with this version of gcc
8028 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
8029 27460; bugfix on 0.3.4.1-alpha.
8030 - When a Travis build fails, and showing a log fails, keep trying to
8031 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
8032 - When we use echo in Travis, don't pass a --flag as the first
8033 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
8035 o Minor bugfixes (onion services):
8036 - Silence a spurious compiler warning in
8037 rend_client_send_introduction(). Fixes bug 27463; bugfix
8040 o Minor bugfixes (testing, chutney):
8041 - When running make test-network-all, use the mixed+hs-v2 network.
8042 (A previous fix to chutney removed v3 onion services from the
8043 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
8044 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
8045 - Before running make test-network-all, delete old logs and test
8046 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8049 Changes in version 0.3.4.7-rc - 2018-08-24
8050 Tor 0.3.4.7-rc fixes several small compilation, portability, and
8051 correctness issues in previous versions of Tor. This version is a
8052 release candidate: if no serious bugs are found, we expect that the
8053 stable 0.3.4 release will be (almost) the same as this release.
8055 o Minor features (bug workaround):
8056 - Compile correctly on systems that provide the C11 stdatomic.h
8057 header, but where C11 atomic functions don't actually compile.
8058 Closes ticket 26779; workaround for Debian issue 903709.
8060 o Minor features (continuous integration):
8061 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
8062 - Enable macOS builds in our Travis CI configuration. Closes
8064 - Install libcap-dev and libseccomp2-dev so these optional
8065 dependencies get tested on Travis CI. Closes ticket 26560.
8066 - Only post Appveyor IRC notifications when the build fails.
8067 Implements ticket 27275.
8068 - Run asciidoc during Travis CI. Implements ticket 27087.
8069 - Use ccache in our Travis CI configuration. Closes ticket 26952.
8071 o Minor features (continuous integration, rust):
8072 - Use cargo cache in our Travis CI configuration. Closes
8075 o Minor features (directory authorities):
8076 - Authorities no longer vote to make the subprotocol version
8077 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
8078 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
8080 o Minor features (geoip):
8081 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
8082 Country database. Closes ticket 27089.
8084 o Minor bugfixes (compilation, windows):
8085 - Don't link or search for pthreads when building for Windows, even
8086 if we are using build environment (like mingw) that provides a
8087 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
8089 o Minor bugfixes (continuous integration):
8090 - Improve Appveyor CI IRC logging. Generate correct branches and
8091 URLs for pull requests and tags. Use unambiguous short commits.
8092 Fixes bug 26979; bugfix on master.
8093 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
8094 - Pass the module flags to distcheck configure, and log the flags
8095 before running configure. (Backported to 0.2.9 and later as a
8096 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
8098 o Minor bugfixes (in-process restart):
8099 - Always call tor_free_all() when leaving tor_run_main(). When we
8100 did not, restarting tor in-process would cause an assertion
8101 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
8103 o Minor bugfixes (linux seccomp2 sandbox):
8104 - Fix a bug in out sandboxing rules for the openat() syscall.
8105 Previously, no openat() call would be permitted, which would break
8106 filesystem operations on recent glibc versions. Fixes bug 25440;
8107 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
8109 o Minor bugfixes (onion services):
8110 - Fix bug that causes services to not ever rotate their descriptors
8111 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
8114 o Minor bugfixes (portability):
8115 - Fix compilation of the unit tests on GNU/Hurd, which does not
8116 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
8119 o Minor bugfixes (rust):
8120 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
8122 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
8123 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
8124 - Protover parsing was accepting the presence of whitespace in
8125 version strings, which the C implementation would choke on, e.g.
8126 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
8127 - Protover parsing was ignoring a 2nd hyphen and everything after
8128 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
8130 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
8131 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
8132 - cd to ${abs_top_builddir}/src/rust before running cargo in
8133 src/test/test_rust.sh. This makes the working directory consistent
8134 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
8136 o Minor bugfixes (testing, bootstrap):
8137 - When calculating bootstrap progress, check exit policies and the
8138 exit flag. Previously, Tor would only check the exit flag, which
8139 caused race conditions in small and fast networks like chutney.
8140 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
8142 o Minor bugfixes (testing, openssl compatibility):
8143 - Our "tortls/cert_matches_key" unit test no longer relies on
8144 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8145 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8146 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8148 o Minor bugfixes (Windows, compilation):
8149 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8150 27185; bugfix on 0.2.2.2-alpha.
8153 Changes in version 0.3.4.6-rc - 2018-08-06
8154 Tor 0.3.4.6-rc fixes several small compilation, portability, and
8155 correctness issues in previous versions of Tor. This version is a
8156 release candidate: if no serious bugs are found, we expect that the
8157 stable 0.3.4 release will be (almost) the same as this release.
8159 o Major bugfixes (event scheduler):
8160 - When we enable a periodic event, schedule it in the event loop
8161 rather than running it immediately. Previously, we would re-run
8162 periodic events immediately in the middle of (for example)
8163 changing our options, with unpredictable effects. Fixes bug 27003;
8164 bugfix on 0.3.4.1-alpha.
8166 o Minor features (compilation):
8167 - When building Tor, prefer to use Python 3 over Python 2, and more
8168 recent (contemplated) versions over older ones. Closes
8170 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
8171 tell the compiler not to include the system malloc implementation.
8172 Fixes bug 20424; bugfix on 0.2.0.20-rc.
8173 - Don't try to use a pragma to temporarily disable the
8174 -Wunused-const-variable warning if the compiler doesn't support
8175 it. Fixes bug 26785; bugfix on 0.3.2.11.
8177 o Minor bugfixes (continuous integration):
8178 - Skip a pair of unreliable key generation tests on Windows, until
8179 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
8180 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
8182 o Minor features (controller):
8183 - The control port now exposes the list of HTTPTunnelPorts and
8184 ExtOrPorts via GETINFO net/listeners/httptunnel and
8185 net/listeners/extor respectively. Closes ticket 26647.
8187 o Minor bugfixes (directory authority):
8188 - When voting for recommended versions, make sure that all of the
8189 versions are well-formed and parsable. Fixes bug 26485; bugfix
8192 o Minor features (geoip):
8193 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8194 Country database. Closes ticket 26674.
8196 o Minor features (Rust, portability):
8197 - Rust cross-compilation is now supported. Closes ticket 25895.
8199 o Minor bugfixes (compilation):
8200 - Update build system so that tor builds again with --disable-unittests
8201 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
8202 - Fix a compilation warning on some versions of GCC when building
8203 code that calls routerinfo_get_my_routerinfo() twice, assuming
8204 that the second call will succeed if the first one did. Fixes bug
8205 26269; bugfix on 0.2.8.2-alpha.
8207 o Minor bugfixes (controller):
8208 - Report the port correctly when a port is configured to bind to
8209 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
8210 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
8211 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
8212 on 0.3.3.1-alpha. Patch by "akwizgran".
8214 o Minor bugfixes (correctness, flow control):
8215 - Upon receiving a stream-level SENDME cell, verify that our window
8216 has not grown too large. Fixes bug 26214; bugfix on svn
8219 o Minor bugfixes (memory, correctness):
8220 - Fix a number of small memory leaks identified by coverity. Fixes
8221 bug 26467; bugfix on numerous Tor versions.
8223 o Minor bugfixes (logging):
8224 - Improve the log message when connection initiators fail to
8225 authenticate direct connections to relays. Fixes bug 26927; bugfix
8228 o Minor bugfixes (portability):
8229 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
8230 26994; bugfix on 0.3.4.1-alpha.
8231 - Work around two different bugs in the OS X 10.10 and later SDKs
8232 that would prevent us from successfully targeting earlier versions
8233 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
8235 o Minor bugfixes (single onion services, Tor2web):
8236 - Log a protocol warning when single onion services or Tor2web
8237 clients fail to authenticate direct connections to relays. Fixes
8238 bug 26924; bugfix on 0.2.9.1-alpha.
8240 o Minor bugfixes (testing):
8241 - Disable core dumps in test_bt.sh, to avoid failures in "make
8242 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8244 o Minor bugfixes (testing, compatibility):
8245 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
8246 only to pass strings (rather than "bytes" objects) to the Python
8247 subprocess module. Python 3 on Windows seems to require this.
8248 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
8249 0.3.1.1-alpha (for hs_ntor_ref.py).
8251 o Minor bugfixes (v3 onion services):
8252 - Stop sending ed25519 link specifiers in v3 onion service introduce
8253 cells and descriptors, when the rendezvous or introduction point
8254 doesn't support ed25519 link authentication. Fixes bug 26627;
8255 bugfix on 0.3.2.4-alpha.
8258 Changes in version 0.3.4.5-rc - 2018-07-13
8259 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
8260 bridge relays should upgrade.
8262 o Directory authority changes:
8263 - The "Bifroest" bridge authority has been retired; the new bridge
8264 authority is "Serge", and it is operated by George from the
8265 TorBSD project. Closes ticket 26771.
8268 Changes in version 0.3.3.9 - 2018-07-13
8269 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
8270 bridge relays should upgrade.
8272 o Directory authority changes:
8273 - The "Bifroest" bridge authority has been retired; the new bridge
8274 authority is "Serge", and it is operated by George from the
8275 TorBSD project. Closes ticket 26771.
8278 Changes in version 0.3.2.11 - 2018-07-13
8279 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
8280 bridge relays should upgrade. We also take this opportunity to backport
8283 o Directory authority changes:
8284 - The "Bifroest" bridge authority has been retired; the new bridge
8285 authority is "Serge", and it is operated by George from the
8286 TorBSD project. Closes ticket 26771.
8288 o Directory authority changes (backport from 0.3.3.7):
8289 - Add an IPv6 address for the "dannenberg" directory authority.
8290 Closes ticket 26343.
8292 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
8293 - When directory authorities read a zero-byte bandwidth file, they
8294 would previously log a warning with the contents of an
8295 uninitialised buffer. They now log a warning about the empty file
8296 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8298 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
8299 - Correctly detect when onion services get disabled after HUP. Fixes
8300 bug 25761; bugfix on 0.3.2.1.
8302 o Minor features (sandbox, backport from 0.3.3.4-alpha):
8303 - Explicitly permit the poll() system call when the Linux
8304 seccomp2-based sandbox is enabled: apparently, some versions of
8305 libc use poll() when calling getpwnam(). Closes ticket 25313.
8307 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
8308 - Update the Travis CI configuration to use the stable Rust channel,
8309 now that we have decided to require that. Closes ticket 25714.
8311 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
8312 - Our .travis.yml configuration now includes support for testing the
8313 results of "make distcheck". (It's not uncommon for "make check"
8314 to pass but "make distcheck" to fail.) Closes ticket 25814.
8315 - Our Travis CI configuration now integrates with the Coveralls
8316 coverage analysis tool. Closes ticket 25818.
8318 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
8319 - Add several checks to detect whether Tor relays are uploading
8320 their descriptors without specifying why they regenerated them.
8321 Diagnostic for ticket 25686.
8323 o Minor features (compilation, backport from 0.3.4.4-rc):
8324 - When building Tor, prefer to use Python 3 over Python 2, and more
8325 recent (contemplated) versions over older ones. Closes
8328 o Minor features (geoip):
8329 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8330 Country database. Closes ticket 26674.
8332 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
8333 - Upon receiving a malformed connected cell, stop processing the
8334 cell immediately. Previously we would mark the connection for
8335 close, but continue processing the cell as if the connection were
8336 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
8338 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
8339 - Allow the nanosleep() system call, which glibc uses to implement
8340 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
8342 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
8343 - When running the hs_ntor_ref.py test, make sure only to pass
8344 strings (rather than "bytes" objects) to the Python subprocess
8345 module. Python 3 on Windows seems to require this. Fixes bug
8346 26535; bugfix on 0.3.1.1-alpha.
8347 - When running the ntor_ref.py test, make sure only to pass strings
8348 (rather than "bytes" objects) to the Python subprocess module.
8349 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
8352 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
8353 - Work around a change in OpenSSL 1.1.1 where return values that
8354 would previously indicate "no password" now indicate an empty
8355 password. Without this workaround, Tor instances running with
8356 OpenSSL 1.1.1 would accept descriptors that other Tor instances
8357 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
8359 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
8360 - Document that the PerConnBW{Rate,Burst} options will fall back to
8361 their corresponding consensus parameters only if those parameters
8362 are set. Previously we had claimed that these values would always
8363 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
8365 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
8366 - Fix a compilation warning on some versions of GCC when building
8367 code that calls routerinfo_get_my_routerinfo() twice, assuming
8368 that the second call will succeed if the first one did. Fixes bug
8369 26269; bugfix on 0.2.8.2-alpha.
8371 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
8372 - Don't consider Tor running as a client if the ControlPort is open,
8373 but no actual client ports are open. Fixes bug 26062; bugfix
8376 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
8377 - Prevent a possible out-of-bounds smartlist read in
8378 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
8380 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
8381 - Fix a very unlikely (impossible, we believe) null pointer
8382 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
8383 Coverity; this is CID 1430932.
8385 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
8386 - Fix a memory leak when a v3 onion service is configured and gets a
8387 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
8388 - When parsing the descriptor signature, look for the token plus an
8389 extra white-space at the end. This is more correct but also will
8390 allow us to support new fields that might start with "signature".
8391 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
8393 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
8394 - Relays now correctly block attempts to re-extend to the previous
8395 relay by Ed25519 identity. Previously they would warn in this
8396 case, but not actually reject the attempt. Fixes bug 26158; bugfix
8399 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
8400 - Avoid a crash when running with DirPort set but ORPort turned off.
8401 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
8403 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
8404 - Silence unused-const-variable warnings in zstd.h with some GCC
8405 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
8407 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
8408 - Avoid intermittent test failures due to a test that had relied on
8409 onion service introduction point creation finishing within 5
8410 seconds of real clock time. Fixes bug 25450; bugfix
8413 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
8414 - Fix a C99 compliance issue in our configuration script that caused
8415 compilation issues when compiling Tor with certain versions of
8416 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
8418 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
8419 - Fix a number of small memory leaks identified by coverity. Fixes
8420 bug 26467; bugfix on numerous Tor versions.
8422 o Code simplification and refactoring (backport from 0.3.3.5-rc):
8423 - Move the list of default directory authorities to its own file.
8424 Closes ticket 24854. Patch by "beastr0".
8427 Changes in version 0.2.9.16 - 2018-07-13
8428 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
8429 bridge relays should upgrade. We also take this opportunity to backport
8432 o Directory authority changes:
8433 - The "Bifroest" bridge authority has been retired; the new bridge
8434 authority is "Serge", and it is operated by George from the
8435 TorBSD project. Closes ticket 26771.
8437 o Directory authority changes (backport from 0.3.3.7):
8438 - Add an IPv6 address for the "dannenberg" directory authority.
8439 Closes ticket 26343.
8441 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
8442 - When directory authorities read a zero-byte bandwidth file, they
8443 would previously log a warning with the contents of an
8444 uninitialised buffer. They now log a warning about the empty file
8445 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8447 o Minor features (sandbox, backport from 0.3.3.4-alpha):
8448 - Explicitly permit the poll() system call when the Linux
8449 seccomp2-based sandbox is enabled: apparently, some versions of
8450 libc use poll() when calling getpwnam(). Closes ticket 25313.
8452 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
8453 - Our .travis.yml configuration now includes support for testing the
8454 results of "make distcheck". (It's not uncommon for "make check"
8455 to pass but "make distcheck" to fail.) Closes ticket 25814.
8456 - Our Travis CI configuration now integrates with the Coveralls
8457 coverage analysis tool. Closes ticket 25818.
8459 o Minor features (compilation, backport from 0.3.4.4-rc):
8460 - When building Tor, prefer to use Python 3 over Python 2, and more
8461 recent (contemplated) versions over older ones. Closes
8464 o Minor features (geoip):
8465 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8466 Country database. Closes ticket 26674.
8468 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
8469 - Upon receiving a malformed connected cell, stop processing the
8470 cell immediately. Previously we would mark the connection for
8471 close, but continue processing the cell as if the connection were
8472 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
8474 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
8475 - Allow the nanosleep() system call, which glibc uses to implement
8476 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
8478 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
8479 - When running the ntor_ref.py test, make sure only to pass strings
8480 (rather than "bytes" objects) to the Python subprocess module.
8481 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
8484 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
8485 - Work around a change in OpenSSL 1.1.1 where return values that
8486 would previously indicate "no password" now indicate an empty
8487 password. Without this workaround, Tor instances running with
8488 OpenSSL 1.1.1 would accept descriptors that other Tor instances
8489 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
8491 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
8492 - Fix a compilation warning on some versions of GCC when building
8493 code that calls routerinfo_get_my_routerinfo() twice, assuming
8494 that the second call will succeed if the first one did. Fixes bug
8495 26269; bugfix on 0.2.8.2-alpha.
8497 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
8498 - Don't consider Tor running as a client if the ControlPort is open,
8499 but no actual client ports are open. Fixes bug 26062; bugfix
8502 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
8503 - Prevent a possible out-of-bounds smartlist read in
8504 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
8506 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
8507 - Fix a very unlikely (impossible, we believe) null pointer
8508 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
8509 Coverity; this is CID 1430932.
8511 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
8512 - Fix a number of small memory leaks identified by coverity. Fixes
8513 bug 26467; bugfix on numerous Tor versions.
8515 o Code simplification and refactoring (backport from 0.3.3.5-rc):
8516 - Move the list of default directory authorities to its own file.
8517 Closes ticket 24854. Patch by "beastr0".
8520 Changes in version 0.3.4.4-rc - 2018-07-09
8521 Tor 0.3.4.4-rc fixes several small compilation, portability, and
8522 correctness issues in previous versions of Tor. This version is a
8523 release candidate: if no serious bugs are found, we expect that the
8524 stable 0.3.4 release will be (almost) the same as this release.
8526 o Minor features (compilation):
8527 - When building Tor, prefer to use Python 3 over Python 2, and more
8528 recent (contemplated) versions over older ones. Closes
8531 o Minor features (geoip):
8532 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8533 Country database. Closes ticket 26674.
8535 o Minor features (Rust, portability):
8536 - Rust cross-compilation is now supported. Closes ticket 25895.
8538 o Minor bugfixes (compilation):
8539 - Fix a compilation warning on some versions of GCC when building
8540 code that calls routerinfo_get_my_routerinfo() twice, assuming
8541 that the second call will succeed if the first one did. Fixes bug
8542 26269; bugfix on 0.2.8.2-alpha.
8544 o Minor bugfixes (control port):
8545 - Report the port correctly when a port is configured to bind to
8546 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
8547 - Handle the HSADDRESS= argument to the HSPOST command properly.
8548 (Previously, this argument was misparsed and thus ignored.) Fixes
8549 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
8551 o Minor bugfixes (correctness, flow control):
8552 - Upon receiving a stream-level SENDME cell, verify that our window
8553 has not grown too large. Fixes bug 26214; bugfix on svn
8556 o Minor bugfixes (memory, correctness):
8557 - Fix a number of small memory leaks identified by coverity. Fixes
8558 bug 26467; bugfix on numerous Tor versions.
8560 o Minor bugfixes (testing, compatibility):
8561 - When running the hs_ntor_ref.py test, make sure only to pass
8562 strings (rather than "bytes" objects) to the Python subprocess
8563 module. Python 3 on Windows seems to require this. Fixes bug
8564 26535; bugfix on 0.3.1.1-alpha.
8565 - When running the ntor_ref.py test, make sure only to pass strings
8566 (rather than "bytes" objects) to the Python subprocess module.
8567 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
8571 Changes in version 0.3.3.8 - 2018-07-09
8572 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
8573 fixes for a memory leak affecting directory authorities.
8575 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
8576 - Stop leaking memory on directory authorities when planning to
8577 vote. This bug was crashing authorities by exhausting their
8578 memory. Fixes bug 26435; bugfix on 0.3.3.6.
8580 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
8581 - Make sure that failing tests in Rust will actually cause the build
8582 to fail: previously, they were ignored. Fixes bug 26258; bugfix
8585 o Minor features (compilation, backport from 0.3.4.4-rc):
8586 - When building Tor, prefer to use Python 3 over Python 2, and more
8587 recent (contemplated) versions over older ones. Closes
8590 o Minor features (geoip):
8591 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8592 Country database. Closes ticket 26674.
8594 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
8595 - Add several checks to detect whether Tor relays are uploading
8596 their descriptors without specifying why they regenerated them.
8597 Diagnostic for ticket 25686.
8599 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
8600 - Don't count path selection failures as circuit build failures.
8601 This change should eliminate cases where Tor blames its guard or
8602 the network for situations like insufficient microdescriptors
8603 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
8606 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
8607 - Fix a compilation warning on some versions of GCC when building
8608 code that calls routerinfo_get_my_routerinfo() twice, assuming
8609 that the second call will succeed if the first one did. Fixes bug
8610 26269; bugfix on 0.2.8.2-alpha.
8612 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
8613 - Handle the HSADDRESS= argument to the HSPOST command properly.
8614 (Previously, this argument was misparsed and thus ignored.) Fixes
8615 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
8617 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
8618 - Fix a number of small memory leaks identified by coverity. Fixes
8619 bug 26467; bugfix on numerous Tor versions.
8621 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
8622 - Relays now correctly block attempts to re-extend to the previous
8623 relay by Ed25519 identity. Previously they would warn in this
8624 case, but not actually reject the attempt. Fixes bug 26158; bugfix
8627 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
8628 - When shutting down, Tor now clears all the flags in the control.c
8629 module. This should prevent a bug where authentication cookies are
8630 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
8632 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
8633 - When running the hs_ntor_ref.py test, make sure only to pass
8634 strings (rather than "bytes" objects) to the Python subprocess
8635 module. Python 3 on Windows seems to require this. Fixes bug
8636 26535; bugfix on 0.3.1.1-alpha.
8637 - When running the ntor_ref.py test, make sure only to pass strings
8638 (rather than "bytes" objects) to the Python subprocess module.
8639 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
8643 Changes in version 0.3.4.3-alpha - 2018-06-26
8644 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
8645 one that was causing stability issues on directory authorities.
8647 o Major bugfixes (directory authority):
8648 - Stop leaking memory on directory authorities when planning to
8649 vote. This bug was crashing authorities by exhausting their
8650 memory. Fixes bug 26435; bugfix on 0.3.3.6.
8652 o Major bugfixes (rust, testing):
8653 - Make sure that failing tests in Rust will actually cause the build
8654 to fail: previously, they were ignored. Fixes bug 26258; bugfix
8657 o Minor feature (directory authorities):
8658 - Stop warning about incomplete bw lines before the first complete
8659 bw line has been found, so that additional header lines can be
8660 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
8662 o Minor features (relay, diagnostic):
8663 - Add several checks to detect whether Tor relays are uploading
8664 their descriptors without specifying why they regenerated them.
8665 Diagnostic for ticket 25686.
8667 o Minor features (unit tests):
8668 - Test complete bandwidth measurements files, and test that
8669 incomplete bandwidth lines only give warnings when the end of the
8670 header has not been detected. Fixes bug 25947; bugfix
8673 o Minor bugfixes (compilation):
8674 - Refrain from compiling unit testing related object files when
8675 --disable-unittests is set to configure script. Fixes bug 24891;
8676 bugfix on 0.2.5.1-alpha.
8677 - When linking the libtor_testing.a library, only include the
8678 dirauth object files once. Previously, they were getting added
8679 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
8680 - The --enable-fatal-warnings flag now affects Rust code as well.
8681 Closes ticket 26245.
8683 o Minor bugfixes (onion services):
8684 - Recompute some consensus information after detecting a clock jump,
8685 or after transitioning from a non-live consensus to a live
8686 consensus. We do this to avoid having an outdated state, and
8687 miscalculating the index for next-generation onion services. Fixes
8688 bug 24977; bugfix on 0.3.2.1-alpha.
8690 o Minor bugfixes (relay):
8691 - Relays now correctly block attempts to re-extend to the previous
8692 relay by Ed25519 identity. Previously they would warn in this
8693 case, but not actually reject the attempt. Fixes bug 26158; bugfix
8696 o Minor bugfixes (testing):
8697 - Fix compilation of the doctests in the Rust crypto crate. Fixes
8698 bug 26415; bugfix on 0.3.4.1-alpha.
8699 - Instead of trying to read the geoip configuration files from
8700 within the unit tests, instead create our own ersatz files with
8701 just enough geoip data in the format we expect. Trying to read
8702 from the source directory created problems on Windows with mingw,
8703 where the build system's paths are not the same as the platform's
8704 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
8705 - Refrain from trying to get an item from an empty smartlist in
8706 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
8707 to catch improper smartlist usage. Furthermore, enable
8708 DEBUG_SMARTLIST globally when build is configured with fragile
8709 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
8712 Changes in version 0.3.3.7 - 2018-06-12
8713 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
8714 fixes for bugs affecting compatibility and stability.
8716 o Directory authority changes:
8717 - Add an IPv6 address for the "dannenberg" directory authority.
8718 Closes ticket 26343.
8720 o Minor features (geoip):
8721 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
8722 Country database. Closes ticket 26351.
8724 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
8725 - Work around a change in OpenSSL 1.1.1 where return values that
8726 would previously indicate "no password" now indicate an empty
8727 password. Without this workaround, Tor instances running with
8728 OpenSSL 1.1.1 would accept descriptors that other Tor instances
8729 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
8731 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
8732 - Silence unused-const-variable warnings in zstd.h with some GCC
8733 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
8735 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
8736 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
8737 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
8738 miscounting the total number of circuits for these field values.)
8739 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
8741 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
8742 - Prevent a possible out-of-bounds smartlist read in
8743 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
8745 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
8746 - Only select relays when they have the descriptors we prefer to use
8747 for them. This change fixes a bug where we could select a relay
8748 because it had _some_ descriptor, but reject it later with a
8749 nonfatal assertion error because it didn't have the exact one we
8750 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
8753 Changes in version 0.3.4.2-alpha - 2018-06-12
8754 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
8755 release, and forward-ports an authority-only security fix from 0.3.3.6.
8757 o Directory authority changes:
8758 - Add an IPv6 address for the "dannenberg" directory authority.
8759 Closes ticket 26343.
8761 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
8762 - Fix a bug that could have allowed an attacker to force a directory
8763 authority to use up all its RAM by passing it a maliciously
8764 crafted protocol versions string. Fixes bug 25517; bugfix on
8765 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
8767 o Minor features (continuous integration):
8768 - Add the necessary configuration files for continuous integration
8769 testing on Windows, via the Appveyor platform. Closes ticket
8770 25549. Patches from Marcin Cieślak and Isis Lovecruft.
8772 o Minor features (geoip):
8773 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
8774 Country database. Closes ticket 26351.
8776 o Minor bugfixes (compatibility, openssl):
8777 - Work around a change in OpenSSL 1.1.1 where return values that
8778 would previously indicate "no password" now indicate an empty
8779 password. Without this workaround, Tor instances running with
8780 OpenSSL 1.1.1 would accept descriptors that other Tor instances
8781 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
8783 o Minor bugfixes (compilation):
8784 - Silence unused-const-variable warnings in zstd.h with some GCC
8785 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
8786 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
8787 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
8788 - Avoid a compiler warning when casting the return value of
8789 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
8790 26283; bugfix on 0.2.4.10-alpha.
8792 o Minor bugfixes (control port):
8793 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
8794 CIRC_BW events. Previously, such cells were counted entirely in
8795 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
8798 o Minor bugfixes (controller):
8799 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
8800 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
8801 miscounting the total number of circuits for these field values.)
8802 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
8804 o Minor bugfixes (hardening):
8805 - Prevent a possible out-of-bounds smartlist read in
8806 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
8808 o Minor bugfixes (onion services):
8809 - Fix a bug that blocked the creation of ephemeral v3 onion
8810 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
8812 o Minor bugfixes (test coverage tools):
8813 - Update our "cov-diff" script to handle output from the latest
8814 version of gcov, and to remove extraneous timestamp information
8815 from its output. Fixes bugs 26101 and 26102; bugfix
8819 Changes in version 0.3.3.6 - 2018-05-22
8820 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
8821 backports several important fixes from the 0.3.4.1-alpha.
8823 The Tor 0.3.3 series includes controller support and other
8824 improvements for v3 onion services, official support for embedding Tor
8825 within other applications, and our first non-trivial module written in
8826 the Rust programming language. (Rust is still not enabled by default
8827 when building Tor.) And as usual, there are numerous other smaller
8828 bugfixes, features, and improvements.
8830 Below are the changes since 0.3.3.5-rc. For a list of all changes
8831 since 0.3.2.10, see the ReleaseNotes file.
8833 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
8834 - When directory authorities read a zero-byte bandwidth file, they
8835 would previously log a warning with the contents of an
8836 uninitialised buffer. They now log a warning about the empty file
8837 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8839 o Major bugfixes (security, directory authority, denial-of-service):
8840 - Fix a bug that could have allowed an attacker to force a directory
8841 authority to use up all its RAM by passing it a maliciously
8842 crafted protocol versions string. Fixes bug 25517; bugfix on
8843 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
8845 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
8846 - Avoid a rare assertion failure in the circuit build timeout code
8847 if we fail to allow any circuits to actually complete. Fixes bug
8848 25733; bugfix on 0.2.2.2-alpha.
8850 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
8851 - Avoid a crash when testing router reachability on a router that
8852 could have an ed25519 ID, but which does not. Fixes bug 25415;
8853 bugfix on 0.3.3.2-alpha.
8855 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
8856 - Correctly detect when onion services get disabled after HUP. Fixes
8857 bug 25761; bugfix on 0.3.2.1.
8859 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
8860 - Impose a limit on circuit cell queue size. The limit can be
8861 controlled by a consensus parameter. Fixes bug 25226; bugfix
8864 o Minor features (compatibility, backport from 0.3.4.1-alpha):
8865 - Avoid some compilation warnings with recent versions of LibreSSL.
8866 Closes ticket 26006.
8868 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
8869 - Our .travis.yml configuration now includes support for testing the
8870 results of "make distcheck". (It's not uncommon for "make check"
8871 to pass but "make distcheck" to fail.) Closes ticket 25814.
8872 - Our Travis CI configuration now integrates with the Coveralls
8873 coverage analysis tool. Closes ticket 25818.
8875 o Minor features (geoip):
8876 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
8877 database. Closes ticket 26104.
8879 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
8880 - Don't consider Tor running as a client if the ControlPort is open,
8881 but no actual client ports are open. Fixes bug 26062; bugfix
8884 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
8885 - Upon receiving a malformed connected cell, stop processing the
8886 cell immediately. Previously we would mark the connection for
8887 close, but continue processing the cell as if the connection were
8888 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
8890 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
8891 - Stop saying in the manual that clients cache ipv4 dns answers from
8892 exit relays. We haven't used them since 0.2.6.3-alpha, and in
8893 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
8894 we forgot to say so in the man page. Fixes bug 26052; bugfix
8897 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
8898 - Allow the nanosleep() system call, which glibc uses to implement
8899 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
8901 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
8902 - Fix a memory leak when a v3 onion service is configured and gets a
8903 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
8904 - When parsing the descriptor signature, look for the token plus an
8905 extra white-space at the end. This is more correct but also will
8906 allow us to support new fields that might start with "signature".
8907 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
8909 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
8910 - Avoid a crash when running with DirPort set but ORPort turned off.
8911 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
8913 o Documentation (backport from 0.3.4.1-alpha):
8914 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
8915 ticket 25857. Patch from "CTassisF".
8918 Changes in version 0.3.4.1-alpha - 2018-05-17
8919 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
8920 includes refactoring to begin reducing Tor's binary size and idle CPU
8921 usage on mobile, along with prep work for new bandwidth scanners,
8922 improvements to the experimental "vanguards" feature, and numerous
8923 other small features and bugfixes.
8925 o New system requirements:
8926 - Tor no longer tries to support old operating systems without
8927 mmap() or some local equivalent. Apparently, compilation on such
8928 systems has been broken for some time, without anybody noticing or
8929 complaining. Closes ticket 25398.
8931 o Major feature (directory authority, modularization):
8932 - The directory authority subsystem has been modularized. The code
8933 is now located in src/or/dirauth/, and is compiled in by default.
8934 To disable the module, the configure option
8935 --disable-module-dirauth has been added. This module may be
8936 disabled by default in some future release. Closes ticket 25610.
8938 o Major features (main loop, CPU usage):
8939 - When Tor is disabled (via DisableNetwork or via hibernation), it
8940 no longer needs to run any per-second events. This change should
8941 make it easier for mobile applications to disable Tor while the
8942 device is sleeping, or Tor is not running. Closes ticket 26063.
8943 - Tor no longer enables all of its periodic events by default.
8944 Previously, Tor would enable all possible main loop events,
8945 regardless of whether it needed them. Furthermore, many of these
8946 events are now disabled with Tor is hibernating or DisableNetwork
8947 is set. This is a big step towards reducing client CPU usage by
8948 reducing the amount of wake-ups the daemon does. Closes ticket
8950 - The bandwidth-limitation logic has been refactored so that
8951 bandwidth calculations are performed on-demand, rather than every
8952 TokenBucketRefillInterval milliseconds. This change should improve
8953 the granularity of our bandwidth calculations, and limit the
8954 number of times that the Tor process needs to wake up when it is
8955 idle. Closes ticket 25373.
8956 - Move responsibility for many operations from a once-per-second
8957 callback to a callback that is only scheduled as needed. Moving
8958 this functionality has allowed us to disable the callback when
8959 Tor's network is disabled. Once enough items are removed from our
8960 once-per-second callback, we can eliminate it entirely to conserve
8961 CPU when idle. The functionality removed includes: closing
8962 connections, circuits, and channels (ticket 25932); consensus
8963 voting (25937); flushing log callbacks (25951); honoring delayed
8964 SIGNEWNYM requests (25949); rescanning the consensus cache
8965 (25931); saving the state file to disk (25948); warning relay
8966 operators about unreachable ports (25952); and keeping track of
8967 Tor's uptime (26009).
8969 o Major bugfixes (directory authorities, security):
8970 - When directory authorities read a zero-byte bandwidth file, they
8971 would previously log a warning with the contents of an
8972 uninitialised buffer. They now log a warning about the empty file
8973 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8975 o Major bugfixes (crash):
8976 - Avoid a rare assertion failure in the circuit build timeout code
8977 if we fail to allow any circuits to actually complete. Fixes bug
8978 25733; bugfix on 0.2.2.2-alpha.
8980 o Major bugfixes (directory authority):
8981 - Avoid a crash when testing router reachability on a router that
8982 could have an ed25519 ID, but which does not. Fixes bug 25415;
8983 bugfix on 0.3.3.2-alpha.
8985 o Major bugfixes (onion service):
8986 - Correctly detect when onion services get disabled after HUP. Fixes
8987 bug 25761; bugfix on 0.3.2.1.
8989 o Major bugfixes (protover, voting):
8990 - Revise Rust implementation of protover to use a more memory-
8991 efficient voting algorithm and corresponding data structures, thus
8992 avoiding a potential (but small impact) DoS attack where specially
8993 crafted protocol strings would expand to several potential
8994 megabytes in memory. In the process, several portions of code were
8995 revised to be methods on new, custom types, rather than functions
8996 taking interchangeable types, thus increasing type safety of the
8997 module. Custom error types and handling were added as well, in
8998 order to facilitate better error dismissal/handling in outside
8999 crates and avoid mistakenly passing an internal error string to C
9000 over the FFI boundary. Many tests were added, and some previous
9001 differences between the C and Rust implementations have been
9002 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
9004 o Major bugfixes (relay, denial of service):
9005 - Impose a limit on circuit cell queue size. The limit can be
9006 controlled by a consensus parameter. Fixes bug 25226; bugfix
9009 o Minor features (accounting):
9010 - When Tor becomes dormant, it now uses a scheduled event to wake up
9011 at the right time. Previously, we would use the per-second timer
9012 to check whether to wake up, but we no longer have any per-second
9013 timers enabled when the network is disabled. Closes ticket 26064.
9015 o Minor features (code quality):
9016 - Add optional spell-checking for the Tor codebase, using the
9017 "misspell" program. To use this feature, run "make check-typos".
9018 Closes ticket 25024.
9020 o Minor features (compatibility):
9021 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
9022 the no-deprecated option, and builds correctly with them. Closes
9023 tickets 19429, 19981, and 25353.
9024 - Avoid some compilation warnings with recent versions of LibreSSL.
9025 Closes ticket 26006.
9027 o Minor features (compression, zstd):
9028 - When running with zstd, Tor now considers using advanced functions
9029 that the zstd maintainers have labeled as potentially unstable. To
9030 prevent breakage, Tor will only use this functionality when the
9031 runtime version of the zstd library matches the version with which
9032 Tor was compiled. Closes ticket 25162.
9034 o Minor features (configuration):
9035 - The "DownloadSchedule" options have been renamed to end with
9036 "DownloadInitialDelay". The old names are still allowed, but will
9037 produce a warning. Comma-separated lists are still permitted for
9038 these options, but all values after the first are ignored (as they
9039 have been since 0.2.9). Closes ticket 23354.
9041 o Minor features (continuous integration):
9042 - Our .travis.yml configuration now includes support for testing the
9043 results of "make distcheck". (It's not uncommon for "make check"
9044 to pass but "make distcheck" to fail.) Closes ticket 25814.
9045 - Our Travis CI configuration now integrates with the Coveralls
9046 coverage analysis tool. Closes ticket 25818.
9048 o Minor features (control port):
9049 - Introduce GETINFO "current-time/{local,utc}" to return the local
9050 and UTC times respectively in ISO format. This helps a controller
9051 like Tor Browser detect a time-related error. Closes ticket 25511.
9052 Patch by Neel Chauhan.
9053 - Introduce new fields to the CIRC_BW event. There are two new
9054 fields in each of the read and written directions. The DELIVERED
9055 fields report the total valid data on the circuit, as measured by
9056 the payload sizes of verified and error-checked relay command
9057 cells. The OVERHEAD fields report the total unused bytes in each
9058 of these cells. Closes ticket 25903.
9060 o Minor features (directory authority):
9061 - Directory authorities now open their key-pinning files as O_SYNC,
9062 to limit their chances of accidentally writing partial lines.
9063 Closes ticket 23909.
9065 o Minor features (directory authority, forward compatibility):
9066 - Make the lines of the measured bandwidth file able to contain
9067 their entries in any order. Previously, the node_id entry needed
9068 to come first. Closes ticket 26004.
9070 o Minor features (entry guards):
9071 - Introduce a new torrc option NumPrimaryGuards for controlling the
9072 number of primary guards. Closes ticket 25843.
9074 o Minor features (geoip):
9075 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
9076 database. Closes ticket 26104.
9078 o Minor features (performance):
9079 - Avoid a needless call to malloc() when processing an incoming
9080 relay cell. Closes ticket 24914.
9081 - Make our timing-wheel code run a tiny bit faster on 32-bit
9082 platforms, by preferring 32-bit math to 64-bit. Closes
9084 - Avoid a needless malloc()/free() pair every time we handle an ntor
9085 handshake. Closes ticket 25150.
9087 o Minor features (testing):
9088 - Add a unit test for voting_schedule_get_start_of_next_interval().
9089 Closes ticket 26014, and helps make unit test coverage
9091 - A new unittests module specifically for testing the functions in
9092 the (new-ish) bridges.c module has been created with new
9093 unittests, raising the code coverage percentages. Closes 25425.
9094 - We now have improved testing for addressmap_get_virtual_address()
9095 function. This should improve our test coverage, and make our test
9096 coverage more deterministic. Closes ticket 25993.
9098 o Minor features (timekeeping, circuit scheduling):
9099 - When keeping track of how busy each circuit have been recently on
9100 a given connection, use coarse-grained monotonic timers rather
9101 than gettimeofday(). This change should marginally increase
9102 accuracy and performance. Implements part of ticket 25927.
9104 o Minor bugfixes (bandwidth management):
9105 - Consider ourselves "low on write bandwidth" if we have exhausted
9106 our write bandwidth some time in the last second. This was the
9107 documented behavior before, but the actual behavior was to change
9108 this value every TokenBucketRefillInterval. Fixes bug 25828;
9109 bugfix on 0.2.3.5-alpha.
9111 o Minor bugfixes (C correctness):
9112 - Add a missing lock acquisition in the shutdown code of the control
9113 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
9114 Coverity; this is CID 1433643.
9116 o Minor bugfixes (circuit path selection):
9117 - Don't count path selection failures as circuit build failures.
9118 This change should eliminate cases where Tor blames its guard or
9119 the network for situations like insufficient microdescriptors
9120 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
9123 o Minor bugfixes (client):
9124 - Don't consider Tor running as a client if the ControlPort is open,
9125 but no actual client ports are open. Fixes bug 26062; bugfix
9128 o Minor bugfixes (code style):
9129 - Fixed multiple includes of transports.h in src/or/connection.c
9130 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
9131 - Remove the unused variable n_possible from the function
9132 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
9134 o Minor bugfixes (control interface):
9135 - Respond with more human-readable error messages to GETINFO exit-
9136 policy/* requests. Also, let controller know if an error is
9137 transient (response code 551) or not (response code 552). Fixes
9138 bug 25852; bugfix on 0.2.8.1-alpha.
9140 o Minor bugfixes (controller):
9141 - Make CIRC_BW event reflect the total of all data sent on a
9142 circuit, including padding and dropped cells. Also fix a mis-
9143 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
9144 bugfix on 0.2.5.2-alpha.
9146 o Minor bugfixes (correctness, client):
9147 - Upon receiving a malformed connected cell, stop processing the cell
9148 immediately. Previously we would mark the connection for close, but
9149 continue processing the cell as if the connection were open. Fixes bug
9150 26072; bugfix on 0.2.4.7-alpha.
9152 o Minor bugfixes (directory client):
9153 - When unverified-consensus is verified, rename it to cached-
9154 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
9155 - Fixed launching a certificate fetch always during the scheduled
9156 periodic consensus fetch by fetching only in those cases when
9157 consensus are waiting for certs. Fixes bug 24740; bugfix
9160 o Minor bugfixes (documentation):
9161 - Stop saying in the manual that clients cache ipv4 dns answers from
9162 exit relays. We haven't used them since 0.2.6.3-alpha, and in
9163 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
9164 we forgot to say so in the man page. Fixes bug 26052; bugfix
9167 o Minor bugfixes (error reporting):
9168 - Improve tolerance for directory authorities with skewed clocks.
9169 Previously, an authority with a clock more than 60 seconds ahead
9170 could cause a client with a correct clock to warn that the
9171 client's clock was behind. Now the clocks of a majority of
9172 directory authorities have to be ahead of the client before this
9173 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
9175 o Minor bugfixes (Linux seccomp2 sandbox):
9176 - Allow the nanosleep() system call, which glibc uses to implement
9177 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
9179 o Minor bugfixes (onion service):
9180 - Fix a memory leak when a v3 onion service is configured and gets a
9181 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
9182 - When parsing the descriptor signature, look for the token plus an
9183 extra white-space at the end. This is more correct but also will
9184 allow us to support new fields that might start with "signature".
9185 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
9187 o Minor bugfixes (path selection):
9188 - Only select relays when they have the descriptors we prefer to use
9189 for them. This change fixes a bug where we could select a relay
9190 because it had _some_ descriptor, but reject it later with a
9191 nonfatal assertion error because it didn't have the exact one we
9192 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
9194 o Minor bugfixes (portability):
9195 - Do not align mmap length, as it is not required by POSIX, and the
9196 getpagesize function is deprecated. Fixes bug 25399; bugfix
9199 o Minor bugfixes (portability, FreeBSD):
9200 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
9201 does not stringify on FreeBSD, so we switch to tor_asprintf().
9202 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
9204 o Minor bugfixes (relay statistics):
9205 - When a relay is collecting internal statistics about how many
9206 create cell requests it has seen of each type, accurately count
9207 the requests from relays that temporarily fall out of the
9208 consensus. (To be extra conservative, we were already ignoring
9209 requests from clients in our counts, and we continue ignoring them
9210 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
9212 o Minor bugfixes (relay, crash):
9213 - Avoid a crash when running with DirPort set but ORPort turned off.
9214 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
9216 o Minor bugfixes (restart-in-process):
9217 - When shutting down, Tor now clears all the flags in the control.c
9218 module. This should prevent a bug where authentication cookies are
9219 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
9221 o Minor bugfixes (testing):
9222 - When testing workqueue event-cancellation, make sure that we
9223 actually cancel an event, and that cancel each event with equal
9224 probability. (It was previously possible, though extremely
9225 unlikely, for our event-canceling test not to cancel any events.)
9226 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
9227 - Repeat part of the test in test_client_pick_intro() a number of
9228 times, to give it consistent coverage. Fixes bug 25996; bugfix
9230 - Remove randomness from the hs_common/responsible_hsdirs test, so
9231 that it always takes the same path through the function it tests.
9232 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
9233 - Change the behavior of the "channel/outbound" test so that it
9234 never causes a 10-second rollover for the EWMA circuitmux code.
9235 Previously, this behavior would happen randomly, and result in
9236 fluctuating test coverage. Fixes bug 25994; bugfix
9238 - Use X509_new() to allocate certificates that will be freed later
9239 with X509_free(). Previously, some parts of the unit tests had
9240 used tor_malloc_zero(), which is incorrect, and which caused test
9241 failures on Windows when they were built with extra hardening.
9242 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
9244 - While running the circuit_timeout test, fix the PRNG to a
9245 deterministic AES stream, so that the test coverage from this test
9246 will itself be deterministic. Fixes bug 25995; bugfix
9249 o Minor bugfixes (vanguards):
9250 - Allow the last hop in a vanguard circuit to be the same as our
9251 first, to prevent the adversary from influencing guard node choice
9252 by choice of last hop. Also prevent the creation of A - B - A
9253 paths, or A - A paths, which are forbidden by relays. Fixes bug
9254 25870; bugfix on 0.3.3.1-alpha.
9256 o Code simplification and refactoring:
9257 - Remove duplicate code in parse_{c,s}method_line and bootstrap
9258 their functionalities into a single function. Fixes bug 6236;
9259 bugfix on 0.2.3.6-alpha.
9260 - We remove the PortForwarding and PortForwardingHelper options,
9261 related functions, and the port_forwarding tests. These options
9262 were used by the now-deprecated Vidalia to help ordinary users
9263 become Tor relays or bridges. Closes ticket 25409. Patch by
9265 - In order to make the OR and dir checking function in router.c less
9266 confusing we renamed some functions and
9267 consider_testing_reachability() has been split into
9268 router_should_check_reachability() and
9269 router_do_reachability_checks(). Also we improved the documentation
9270 in some functions. Closes ticket 18918.
9271 - Initial work to isolate Libevent usage to a handful of modules in
9272 our codebase, to simplify our call structure, and so that we can
9273 more easily change event loops in the future if needed. Closes
9275 - Introduce a function to call getsockname() and return tor_addr_t,
9276 to save a little complexity throughout the codebase. Closes
9278 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
9279 as hsdir_index is always present. Also, we move hsdir_index_t into
9280 or.h. Closes ticket 23094. Patch by Neel Chauhan.
9281 - Merge functions used for describing nodes and suppress the
9282 functions that do not allocate memory for the output buffer
9283 string. NODE_DESC_BUF_LEN constant and format_node_description()
9284 function cannot be used externally from router.c module anymore.
9285 Closes ticket 25432. Patch by valentecaio.
9286 - Our main loop has been simplified so that all important operations
9287 happen inside events. Previously, some operations had to happen
9288 outside the event loop, to prevent infinite sequences of event
9289 activations. Closes ticket 25374.
9290 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
9291 it in register_intro_circ() and service_intro_point_new(). This
9292 prevents the digest from being re-calculated each time. Closes
9293 ticket 23107. Patch by Neel Chauhan.
9294 - Refactor token-bucket implementations to use a common backend.
9295 Closes ticket 25766.
9296 - Remove extern declaration of stats_n_seconds_working variable from
9297 main, protecting its accesses with get_uptime() and reset_uptime()
9298 functions. Closes ticket 25081, patch by “valentecaio”.
9299 - Remove our previous logic for "cached gettimeofday()" -- our
9300 coarse monotonic timers are fast enough for this purpose, and far
9301 less error-prone. Implements part of ticket 25927.
9302 - Remove the return value for fascist_firewall_choose_address_base(),
9303 and sister functions such as fascist_firewall_choose_address_node()
9304 and fascist_firewall_choose_address_rs(). Also, while we're here,
9305 initialize the ap argument as leaving it uninitialized can pose a
9306 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
9307 - Rename two fields of connection_t struct. timestamp_lastwritten is
9308 renamed to timestamp_last_write_allowed and timestamp_lastread is
9309 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
9311 - Since Tor requires C99, remove our old workaround code for libc
9312 implementations where free(NULL) doesn't work. Closes ticket 24484.
9313 - Use our standard rate-limiting code to deal with excessive
9314 libevent failures, rather than the hand-rolled logic we had
9315 before. Closes ticket 26016.
9316 - We remove the return value of node_get_prim_orport() and
9317 node_get_prim_dirport(), and introduce node_get_prim_orport() in
9318 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
9319 check for a null address. Closes ticket 23873. Patch by
9321 - We switch to should_record_bridge_info() in
9322 geoip_note_client_seen() and options_need_geoip_info() instead of
9323 accessing the configuration values directly. Fixes bug 25290;
9324 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
9326 o Deprecated features:
9327 - As we are not recommending 0.2.5 anymore, we require relays that
9328 once had an ed25519 key associated with their RSA key to always
9329 have that key, instead of allowing them to drop back to a version
9330 that didn't support ed25519. This means they need to use a new RSA
9331 key if they want to downgrade to an older version of tor without
9332 ed25519. Closes ticket 20522.
9335 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
9336 ticket 25857. Patch from "CTassisF".
9339 - Directory authorities will no longer support voting according to
9340 any consensus method before consensus method 25. This keeps
9341 authorities compatible with all authorities running 0.2.9.8 and
9342 later, and does not break any clients or relays. Implements ticket
9343 24378 and proposal 290.
9344 - The PortForwarding and PortForwardingHelper features have been
9345 removed. The reasoning is, given that implementations of NAT
9346 traversal protocols within common consumer grade routers are
9347 frequently buggy, and that the target audience for a NAT punching
9348 feature is a perhaps less-technically-inclined relay operator,
9349 when the helper fails to setup traversal the problems are usually
9350 deep, ugly, and very router specific, making them horrendously
9351 impossible for technical support to reliable assist with, and thus
9352 resulting in frustration all around. Unfortunately, relay
9353 operators who would like to run relays behind NATs will need to
9354 become more familiar with the port forwarding configurations on
9355 their local router. Closes 25409.
9356 - The TestingEnableTbEmptyEvent option has been removed. It was used
9357 in testing simulations to measure how often connection buckets
9358 were emptied, in order to improve our scheduling, but it has not
9359 been actively used in years. Closes ticket 25760.
9360 - The old "round-robin" circuit multiplexer (circuitmux)
9361 implementation has been removed, along with a fairly large set of
9362 code that existed to support it. It has not been the default
9363 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
9364 but it still required an unreasonable amount of memory and CPU.
9365 Closes ticket 25268.
9368 Changes in version 0.3.3.5-rc - 2018-04-15
9369 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
9370 including some that could affect reliability or correctness.
9372 This is the first release candidate in the 0.3.3 series. If we find no
9373 new bugs or regression here, then the first stable 0.3.3 release will
9374 be nearly identical to this one.
9376 o Major bugfixes (security, protover, voting):
9377 - Revise Rust implementation of protover to use a more memory-
9378 efficient voting algorithm and corresponding data structures, thus
9379 avoiding a potential memory-based DoS attack where specially
9380 crafted protocol strings would expand to fill available memory.
9381 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
9383 o Major bugfixes (performance, load balancing):
9384 - Directory authorities no longer vote in favor of the Guard flag
9385 for relays without directory support. Starting in Tor
9386 0.3.0.1-alpha, clients have been avoiding using such relays in the
9387 Guard position, leading to increasingly broken load balancing for
9388 the 5%-or-so of Guards that don't advertise directory support.
9389 Fixes bug 22310; bugfix on 0.3.0.6.
9391 o Minor feature (continuous integration):
9392 - Update the Travis CI configuration to use the stable Rust channel,
9393 now that we have decided to require that. Closes ticket 25714.
9395 o Minor features (config options):
9396 - Change the way the default value for MaxMemInQueues is calculated.
9397 We now use 40% of the hardware RAM if the system has 8 GB RAM or
9398 more. Otherwise we use the former value of 75%. Closes
9401 o Minor features (geoip):
9402 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
9403 Country database. Closes ticket 25718.
9405 o Minor bugfixes (client):
9406 - When using a listed relay as a bridge, and also using
9407 microdescriptors, and considering that relay as a non-bridge in a
9408 circuit, treat its microdescriptor as a valid source of
9409 information about that relay. This change should prevent a non-
9410 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
9412 o Minor bugfixes (controller):
9413 - Restore the correct operation of the RESOLVE command, which had
9414 been broken since we added the ability to enable/disable DNS on
9415 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
9417 o Minor bugfixes (distribution, compilation, rust):
9418 - Build correctly when the rust dependencies submodule is loaded,
9419 but the TOR_RUST_DEPENDENCIES environment variable is not set.
9420 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
9421 - Actually include all of our Rust source in our source
9422 distributions. (Previously, a few of the files were accidentally
9423 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
9425 o Minor bugfixes (documentation):
9426 - Document that the PerConnBW{Rate,Burst} options will fall back to
9427 their corresponding consensus parameters only if those parameters
9428 are set. Previously we had claimed that these values would always
9429 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
9430 - Revert a misformatting issue in the ExitPolicy documentation.
9431 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
9433 o Minor bugfixes (exit relay DNS retries):
9434 - Re-attempt timed-out DNS queries 3 times before failure, since our
9435 timeout is 5 seconds for them, but clients wait 10-15. Also allow
9436 slightly more timeouts per resolver when an exit has multiple
9437 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
9439 o Minor bugfixes (onion services):
9440 - Re-instate counting the client HSDir fetch circuits against the
9441 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
9443 - Remove underscores from the _HSLayer{2,3}Nodes options. This
9444 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
9445 Fixes bug 25581; bugfix on 0.3.3.1-alpha
9447 o Code simplification and refactoring:
9448 - Move the list of default directory authorities to its own file.
9449 Closes ticket 24854. Patch by "beastr0".
9451 o Documentation (manpage, denial of service):
9452 - Provide more detail about the denial-of-service options, by
9453 listing each mitigation and explaining how they relate. Closes
9457 Changes in version 0.3.3.4-alpha - 2018-03-29
9458 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
9459 the alpha testing of earlier releases in its series. We are
9460 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
9462 o New system requirements:
9463 - When built with Rust, Tor now depends on version 0.2.39 of the
9464 libc crate. Closes tickets 25310 and 25664.
9466 o Major bugfixes (relay, connection):
9467 - If we have failed to connect to a relay and received a connection
9468 refused, timeout, or similar error (at the TCP level), do not try
9469 that same address/port again for 60 seconds after the failure has
9470 occurred. Fixes bug 24767; bugfix on 0.0.6.
9472 o Minor features (geoip):
9473 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
9474 Country database. Closes ticket 25469.
9476 o Minor features (log messages):
9477 - Improve log message in the out-of-memory handler to include
9478 information about memory usage from the different compression
9479 backends. Closes ticket 25372.
9481 o Minor features (sandbox):
9482 - Explicitly permit the poll() system call when the Linux
9483 seccomp2-based sandbox is enabled: apparently, some versions of
9484 libc use poll() when calling getpwnam(). Closes ticket 25313.
9486 o Minor bugfixes (C correctness):
9487 - Fix a very unlikely (impossible, we believe) null pointer
9488 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
9489 Coverity; this is CID 1430932.
9491 o Minor bugfixes (channel, client):
9492 - Better identify client connection when reporting to the geoip
9493 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
9495 o Minor bugfixes (compilation):
9496 - Fix a C99 compliance issue in our configuration script that caused
9497 compilation issues when compiling Tor with certain versions of
9498 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
9500 o Minor bugfixes (controller, reliability):
9501 - Avoid a (nonfatal) assertion failure when extending a one-hop
9502 circuit from the controller to become a multihop circuit. Fixes
9503 bug 24903; bugfix on 0.2.5.2-alpha.
9505 o Major bugfixes (networking):
9506 - Tor will no longer reject IPv6 address strings from Tor Browser
9507 when they are passed as hostnames in SOCKS5 requests. Fixes bug
9508 25036, bugfix on Tor 0.3.1.2.
9510 o Minor bugfixes (networking):
9511 - string_is_valid_hostname() will not consider IP strings to be
9512 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
9514 o Minor bugfixes (onion service v3):
9515 - Avoid an assertion failure when the next onion service
9516 descriptor rotation type is out of sync with the consensus's
9517 valid-after time. Instead, log a warning message with extra
9518 information, so we can better hunt down the cause of this
9519 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
9521 o Minor bugfixes (testing):
9522 - Avoid intermittent test failures due to a test that had relied on
9523 onion service introduction point creation finishing within 5
9524 seconds of real clock time. Fixes bug 25450; bugfix
9526 - Rust crates are now automatically detected and tested. Previously,
9527 some crates were not tested by `make test-rust` due to a static
9528 string in the `src/test/test_rust.sh` script specifying which
9529 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
9531 o Minor bugfixes (testing, benchmarks):
9532 - Fix a crash when running benchmark tests on win32 systems. The
9533 crash was due to a mutex that wasn't initialized before logging
9534 and options were initialized. Fixes bug 25479; bugfix
9537 o Minor bugfixes (warnings, ipv6):
9538 - Avoid a bug warning that could occur when trying to connect to a
9539 relay over IPv6. This warning would occur on a Tor instance that
9540 downloads router descriptors, but prefers to use microdescriptors.
9541 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
9543 o Code simplification and refactoring:
9544 - Remove the old (deterministic) directory retry logic entirely:
9545 We've used exponential backoff exclusively for some time. Closes
9549 - Improved the documentation of AccountingStart parameter. Closes
9551 - Update the documentation for "Log" to include the current list of
9552 logging domains. Closes ticket 25378.
9555 Changes in version 0.3.1.10 - 2018-03-03
9556 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
9559 It includes an important security fix for a remote crash attack
9560 against directory authorities, tracked as TROVE-2018-001.
9562 This release also backports our new system for improved resistance to
9563 denial-of-service attacks against relays.
9565 This release also fixes several minor bugs and annoyances from
9568 All directory authorities should upgrade to one of the versions
9569 released today. Relays running 0.3.1.x may wish to update to one of
9570 the versions released today, for the DoS mitigations.
9572 Please note: according to our release calendar, Tor 0.3.1 will no
9573 longer be supported after 1 July 2018. If you will be running Tor
9574 after that date, you should make sure to plan to upgrade to the latest
9575 stable version, or downgrade to 0.2.9 (which will receive long-term
9578 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
9579 - Fix a protocol-list handling bug that could be used to remotely crash
9580 directory authorities with a null-pointer exception. Fixes bug 25074;
9581 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
9584 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
9585 - Give relays some defenses against the recent network overload. We
9586 start with three defenses (default parameters in parentheses).
9587 First: if a single client address makes too many concurrent
9588 connections (>100), hang up on further connections. Second: if a
9589 single client address makes circuits too quickly (more than 3 per
9590 second, with an allowed burst of 90) while also having too many
9591 connections open (3), refuse new create cells for the next while
9592 (1-2 hours). Third: if a client asks to establish a rendezvous
9593 point to you directly, ignore the request. These defenses can be
9594 manually controlled by new torrc options, but relays will also
9595 take guidance from consensus parameters, so there's no need to
9596 configure anything manually. Implements ticket 24902.
9598 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
9599 - Update the sandbox rules so that they should now work correctly
9600 with Glibc 2.26. Closes ticket 24315.
9602 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
9603 - Fix an "off by 2" error in counting rendezvous failures on the
9604 onion service side. While we thought we would stop the rendezvous
9605 attempt after one failed circuit, we were actually making three
9606 circuit attempts before giving up. Now switch to a default of 2,
9607 and allow the consensus parameter "hs_service_max_rdv_failures" to
9608 override. Fixes bug 24895; bugfix on 0.0.6.
9610 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
9611 - Add Link protocol version 5 to the supported protocols list. Fixes
9612 bug 25070; bugfix on 0.3.1.1-alpha.
9614 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
9615 - Fix a set of false positives where relays would consider
9616 connections to other relays as being client-only connections (and
9617 thus e.g. deserving different link padding schemes) if those
9618 relays fell out of the consensus briefly. Now we look only at the
9619 initial handshake and whether the connection authenticated as a
9620 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
9622 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
9623 - Make our OOM handler aware of the geoip client history cache so it
9624 doesn't fill up the memory. This check is important for IPv6 and
9625 our DoS mitigation subsystem. Closes ticket 25122.
9627 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
9628 - Change relay bandwidth reporting stats interval from 4 hours to 24
9629 hours in order to reduce the efficiency of guard discovery
9630 attacks. Fixes ticket 23856.
9632 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
9633 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
9634 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
9635 since they neither disabled TLS 1.3 nor enabled any of the
9636 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
9637 Closes ticket 24978.
9639 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
9640 - The fallback directory list has been re-generated based on the
9641 current status of the network. Tor uses fallback directories to
9642 bootstrap when it doesn't yet have up-to-date directory
9643 information. Closes ticket 24801.
9644 - Make the default DirAuthorityFallbackRate 0.1, so that clients
9645 prefer to bootstrap from fallback directory mirrors. This is a
9646 follow-up to 24679, which removed weights from the default
9647 fallbacks. Implements ticket 24681.
9649 o Minor features (geoip):
9650 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
9653 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
9654 - Use the actual observed address of an incoming relay connection,
9655 not the canonical address of the relay from its descriptor, when
9656 making decisions about how to handle the incoming connection.
9657 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
9659 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
9660 - Directory authorities, when refusing a descriptor from a rejected
9661 relay, now explicitly tell the relay (in its logs) to set a valid
9662 ContactInfo address and contact the bad-relays@ mailing list.
9663 Fixes bug 25170; bugfix on 0.2.9.1.
9665 o Minor bugfixes (address selection, backport from 0.3.2.9):
9666 - When the fascist_firewall_choose_address_ functions don't find a
9667 reachable address, set the returned address to the null address
9668 and port. This is a precautionary measure, because some callers do
9669 not check the return value. Fixes bug 24736; bugfix
9672 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
9673 - Fetch descriptors aggressively whenever we lack enough to build
9674 circuits, regardless of how many descriptors we are missing.
9675 Previously, we would delay launching the fetch when we had fewer
9676 than 15 missing descriptors, even if some of those descriptors
9677 were blocking circuits from building. Fixes bug 23985; bugfix on
9678 0.1.1.11-alpha. The effects of this bug became worse in
9679 0.3.0.3-alpha, when we began treating missing descriptors from our
9680 primary guards as a reason to delay circuits.
9681 - Don't try fetching microdescriptors from relays that have failed
9682 to deliver them in the past. Fixes bug 23817; bugfix
9685 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
9686 - Fix a signed/unsigned comparison warning introduced by our fix to
9687 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
9689 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
9690 - Avoid a crash when attempting to use the seccomp2 sandbox together
9691 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
9694 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
9695 - Fix a possible crash on malformed consensus. If a consensus had
9696 contained an unparseable protocol line, it could have made clients
9697 and relays crash with a null-pointer exception. To exploit this
9698 issue, however, an attacker would need to be able to subvert the
9699 directory authority system. Fixes bug 25251; bugfix on
9700 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
9702 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
9703 - Recover better from empty or corrupt files in the consensus cache
9704 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
9705 - When a consensus diff calculation is only partially successful,
9706 only record the successful parts as having succeeded. Partial
9707 success can happen if (for example) one compression method fails
9708 but the others succeed. Previously we misrecorded all the
9709 calculations as having succeeded, which would later cause a
9710 nonfatal assertion failure. Fixes bug 24086; bugfix
9713 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
9714 - Tor now updates its guard state when it reads a consensus
9715 regardless of whether it's missing descriptors. That makes tor use
9716 its primary guards to fetch descriptors in some edge cases where
9717 it would previously have used fallback directories. Fixes bug
9718 23862; bugfix on 0.3.0.1-alpha.
9720 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
9721 - Don't treat inability to store a cached consensus object as a bug:
9722 it can happen normally when we are out of disk space. Fixes bug
9723 24859; bugfix on 0.3.1.1-alpha.
9725 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
9726 - When queuing DESTROY cells on a channel, only queue the circuit-id
9727 and reason fields: not the entire 514-byte cell. This fix should
9728 help mitigate any bugs or attacks that fill up these queues, and
9729 free more RAM for other uses. Fixes bug 24666; bugfix
9732 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
9733 - When closing a connection via close_connection_immediately(), we
9734 mark it as "not blocked on bandwidth", to prevent later calls from
9735 trying to unblock it, and give it permission to read. This fixes a
9736 backtrace warning that can happen on relays under various
9737 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9739 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
9740 - When selecting relays by bandwidth, avoid a rounding error that
9741 could sometimes cause load to be imbalanced incorrectly.
9742 Previously, we would always round upwards; now, we round towards
9743 the nearest integer. This had the biggest effect when a relay's
9744 weight adjustments should have given it weight 0, but it got
9745 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9746 - When calculating the fraction of nodes that have descriptors, and
9747 all nodes in the network have zero bandwidths, count the number of
9748 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9749 - Actually log the total bandwidth in compute_weighted_bandwidths().
9750 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9752 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
9753 - Improve the performance of our consensus-diff application code
9754 when Tor is built with the --enable-fragile-hardening option set.
9755 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
9757 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
9758 - Don't exit the Tor process if setrlimit() fails to change the file
9759 limit (which can happen sometimes on some versions of OSX). Fixes
9760 bug 21074; bugfix on 0.0.9pre5.
9762 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
9763 - Fix a bug in the bit-counting parts of our timing-wheel code on
9764 MSVC. (Note that MSVC is still not a supported build platform, due
9765 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
9768 o Minor bugfixes (relay, partial backport):
9769 - Make the internal channel_is_client() function look at what sort
9770 of connection handshake the other side used, rather than whether
9771 the other side ever sent a create_fast cell to us. Backports part
9772 of the fixes from bugs 22805 and 24898.
9774 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
9775 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
9777 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
9778 bugfix on 0.2.9.4-alpha.
9780 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
9781 - Update the "rust dependencies" submodule to be a project-level
9782 repository, rather than a user repository. Closes ticket 25323.
9785 Changes in version 0.2.9.15 - 2018-03-03
9786 Tor 0.2.9.15 backports important security and stability bugfixes from
9789 It includes an important security fix for a remote crash attack
9790 against directory authorities, tracked as TROVE-2018-001.
9792 This release also backports our new system for improved resistance to
9793 denial-of-service attacks against relays.
9795 This release also fixes several minor bugs and annoyances from
9798 All directory authorities should upgrade to one of the versions
9799 released today. Relays running 0.2.9.x may wish to update to one of
9800 the versions released today, for the DoS mitigations.
9802 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
9803 - Fix a protocol-list handling bug that could be used to remotely crash
9804 directory authorities with a null-pointer exception. Fixes bug 25074;
9805 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
9808 o Major features (denial-of-service mitigation):
9809 - Give relays some defenses against the recent network overload. We
9810 start with three defenses (default parameters in parentheses).
9811 First: if a single client address makes too many concurrent
9812 connections (>100), hang up on further connections. Second: if a
9813 single client address makes circuits too quickly (more than 3 per
9814 second, with an allowed burst of 90) while also having too many
9815 connections open (3), refuse new create cells for the next while
9816 (1-2 hours). Third: if a client asks to establish a rendezvous
9817 point to you directly, ignore the request. These defenses can be
9818 manually controlled by new torrc options, but relays will also
9819 take guidance from consensus parameters, so there's no need to
9820 configure anything manually. Implements ticket 24902.
9822 o Major bugfixes (bootstrapping):
9823 - Fetch descriptors aggressively whenever we lack enough to build
9824 circuits, regardless of how many descriptors we are missing.
9825 Previously, we would delay launching the fetch when we had fewer
9826 than 15 missing descriptors, even if some of those descriptors
9827 were blocking circuits from building. Fixes bug 23985; bugfix on
9828 0.1.1.11-alpha. The effects of this bug became worse in
9829 0.3.0.3-alpha, when we began treating missing descriptors from our
9830 primary guards as a reason to delay circuits.
9832 o Major bugfixes (onion services, retry behavior):
9833 - Fix an "off by 2" error in counting rendezvous failures on the
9834 onion service side. While we thought we would stop the rendezvous
9835 attempt after one failed circuit, we were actually making three
9836 circuit attempts before giving up. Now switch to a default of 2,
9837 and allow the consensus parameter "hs_service_max_rdv_failures" to
9838 override. Fixes bug 24895; bugfix on 0.0.6.
9840 o Minor feature (relay statistics):
9841 - Change relay bandwidth reporting stats interval from 4 hours to 24
9842 hours in order to reduce the efficiency of guard discovery
9843 attacks. Fixes ticket 23856.
9845 o Minor features (compatibility, OpenSSL):
9846 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
9847 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
9848 since they neither disabled TLS 1.3 nor enabled any of the
9849 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
9850 Closes ticket 24978.
9852 o Minor features (denial-of-service avoidance):
9853 - Make our OOM handler aware of the geoip client history cache so it
9854 doesn't fill up the memory. This check is important for IPv6 and
9855 our DoS mitigation subsystem. Closes ticket 25122.
9857 o Minor features (fallback directory mirrors):
9858 - The fallback directory list has been re-generated based on the
9859 current status of the network. Tor uses fallback directories to
9860 bootstrap when it doesn't yet have up-to-date directory
9861 information. Closes ticket 24801.
9862 - Make the default DirAuthorityFallbackRate 0.1, so that clients
9863 prefer to bootstrap from fallback directory mirrors. This is a
9864 follow-up to 24679, which removed weights from the default
9865 fallbacks. Implements ticket 24681.
9867 o Minor features (geoip):
9868 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
9871 o Minor features (linux seccomp2 sandbox):
9872 - Update the sandbox rules so that they should now work correctly
9873 with Glibc 2.26. Closes ticket 24315.
9875 o Minor bugfix (channel connection):
9876 - Use the actual observed address of an incoming relay connection,
9877 not the canonical address of the relay from its descriptor, when
9878 making decisions about how to handle the incoming connection.
9879 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
9881 o Minor bugfix (directory authority):
9882 - Directory authorities, when refusing a descriptor from a rejected
9883 relay, now explicitly tell the relay (in its logs) to set a valid
9884 ContactInfo address and contact the bad-relays@ mailing list.
9885 Fixes bug 25170; bugfix on 0.2.9.1.
9887 o Minor bugfixes (address selection):
9888 - When the fascist_firewall_choose_address_ functions don't find a
9889 reachable address, set the returned address to the null address
9890 and port. This is a precautionary measure, because some callers do
9891 not check the return value. Fixes bug 24736; bugfix
9894 o Minor bugfixes (compilation):
9895 - Fix a signed/unsigned comparison warning introduced by our fix to
9896 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
9898 o Minor bugfixes (control port, linux seccomp2 sandbox):
9899 - Avoid a crash when attempting to use the seccomp2 sandbox together
9900 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
9903 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
9904 - Fix a possible crash on malformed consensus. If a consensus had
9905 contained an unparseable protocol line, it could have made clients
9906 and relays crash with a null-pointer exception. To exploit this
9907 issue, however, an attacker would need to be able to subvert the
9908 directory authority system. Fixes bug 25251; bugfix on
9909 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
9911 o Minor bugfixes (memory usage):
9912 - When queuing DESTROY cells on a channel, only queue the circuit-id
9913 and reason fields: not the entire 514-byte cell. This fix should
9914 help mitigate any bugs or attacks that fill up these queues, and
9915 free more RAM for other uses. Fixes bug 24666; bugfix
9918 o Minor bugfixes (network layer):
9919 - When closing a connection via close_connection_immediately(), we
9920 mark it as "not blocked on bandwidth", to prevent later calls from
9921 trying to unblock it, and give it permission to read. This fixes a
9922 backtrace warning that can happen on relays under various
9923 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9925 o Minor bugfixes (OSX):
9926 - Don't exit the Tor process if setrlimit() fails to change the file
9927 limit (which can happen sometimes on some versions of OSX). Fixes
9928 bug 21074; bugfix on 0.0.9pre5.
9930 o Minor bugfixes (path selection):
9931 - When selecting relays by bandwidth, avoid a rounding error that
9932 could sometimes cause load to be imbalanced incorrectly.
9933 Previously, we would always round upwards; now, we round towards
9934 the nearest integer. This had the biggest effect when a relay's
9935 weight adjustments should have given it weight 0, but it got
9936 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9937 - When calculating the fraction of nodes that have descriptors, and
9938 all nodes in the network have zero bandwidths, count the number of
9939 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9940 - Actually log the total bandwidth in compute_weighted_bandwidths().
9941 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9943 o Minor bugfixes (portability, msvc):
9944 - Fix a bug in the bit-counting parts of our timing-wheel code on
9945 MSVC. (Note that MSVC is still not a supported build platform, due
9946 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
9949 o Minor bugfixes (relay):
9950 - Make the internal channel_is_client() function look at what sort
9951 of connection handshake the other side used, rather than whether
9952 the other side ever sent a create_fast cell to us. Backports part
9953 of the fixes from bugs 22805 and 24898.
9955 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
9956 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
9958 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
9959 bugfix on 0.2.9.4-alpha.
9962 Changes in version 0.3.2.10 - 2018-03-03
9963 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
9964 backports a number of bugfixes, including important fixes for security
9967 It includes an important security fix for a remote crash attack
9968 against directory authorities, tracked as TROVE-2018-001.
9970 Additionally, it backports a fix for a bug whose severity we have
9971 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
9972 triggered in order to crash relays with a use-after-free pattern. As
9973 such, we are now tracking that bug as TROVE-2018-002 and
9974 CVE-2018-0491, and backporting it to earlier releases. This bug
9975 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
9978 This release also backports our new system for improved resistance to
9979 denial-of-service attacks against relays.
9981 This release also fixes several minor bugs and annoyances from
9984 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
9985 today, for the fix to TROVE-2018-002. Directory authorities should
9986 also upgrade. (Relays on earlier versions might want to update too for
9987 the DoS mitigations.)
9989 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
9990 - Fix a protocol-list handling bug that could be used to remotely crash
9991 directory authorities with a null-pointer exception. Fixes bug 25074;
9992 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
9995 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
9996 - Avoid adding the same channel twice in the KIST scheduler pending
9997 list, which could lead to remote denial-of-service use-after-free
9998 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
10000 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
10001 - Give relays some defenses against the recent network overload. We
10002 start with three defenses (default parameters in parentheses).
10003 First: if a single client address makes too many concurrent
10004 connections (>100), hang up on further connections. Second: if a
10005 single client address makes circuits too quickly (more than 3 per
10006 second, with an allowed burst of 90) while also having too many
10007 connections open (3), refuse new create cells for the next while
10008 (1-2 hours). Third: if a client asks to establish a rendezvous
10009 point to you directly, ignore the request. These defenses can be
10010 manually controlled by new torrc options, but relays will also
10011 take guidance from consensus parameters, so there's no need to
10012 configure anything manually. Implements ticket 24902.
10014 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
10015 - Fix an "off by 2" error in counting rendezvous failures on the
10016 onion service side. While we thought we would stop the rendezvous
10017 attempt after one failed circuit, we were actually making three
10018 circuit attempts before giving up. Now switch to a default of 2,
10019 and allow the consensus parameter "hs_service_max_rdv_failures" to
10020 override. Fixes bug 24895; bugfix on 0.0.6.
10021 - New-style (v3) onion services now obey the "max rendezvous circuit
10022 attempts" logic. Previously they would make as many rendezvous
10023 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
10024 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
10026 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
10027 - Add Link protocol version 5 to the supported protocols list. Fixes
10028 bug 25070; bugfix on 0.3.1.1-alpha.
10030 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
10031 - Fix a set of false positives where relays would consider
10032 connections to other relays as being client-only connections (and
10033 thus e.g. deserving different link padding schemes) if those
10034 relays fell out of the consensus briefly. Now we look only at the
10035 initial handshake and whether the connection authenticated as a
10036 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
10038 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
10039 - The scheduler subsystem was failing to promptly notice changes in
10040 consensus parameters, making it harder to switch schedulers
10041 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
10043 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
10044 - Make our OOM handler aware of the geoip client history cache so it
10045 doesn't fill up the memory. This check is important for IPv6 and
10046 our DoS mitigation subsystem. Closes ticket 25122.
10048 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
10049 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
10050 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
10051 since they neither disabled TLS 1.3 nor enabled any of the
10052 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
10053 Closes ticket 24978.
10055 o Minor features (geoip):
10056 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
10059 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
10060 - When logging a failure to create an onion service's descriptor,
10061 also log what the problem with the descriptor was. Diagnostic
10064 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
10065 - Use the actual observed address of an incoming relay connection,
10066 not the canonical address of the relay from its descriptor, when
10067 making decisions about how to handle the incoming connection.
10068 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
10070 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
10071 - Fix a possible crash on malformed consensus. If a consensus had
10072 contained an unparseable protocol line, it could have made clients
10073 and relays crash with a null-pointer exception. To exploit this
10074 issue, however, an attacker would need to be able to subvert the
10075 directory authority system. Fixes bug 25251; bugfix on
10076 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
10078 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
10079 - Directory authorities, when refusing a descriptor from a rejected
10080 relay, now explicitly tell the relay (in its logs) to set a valid
10081 ContactInfo address and contact the bad-relays@ mailing list.
10082 Fixes bug 25170; bugfix on 0.2.9.1.
10084 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
10085 - When building with Rust on OSX, link against libresolv, to work
10086 around the issue at https://github.com/rust-lang/rust/issues/46797.
10087 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
10089 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
10090 - Remove a BUG() statement when a client fetches an onion descriptor
10091 that has a lower revision counter than the one in its cache. This
10092 can happen in normal circumstances due to HSDir desync. Fixes bug
10093 24976; bugfix on 0.3.2.1-alpha.
10095 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
10096 - Don't treat inability to store a cached consensus object as a bug:
10097 it can happen normally when we are out of disk space. Fixes bug
10098 24859; bugfix on 0.3.1.1-alpha.
10100 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
10101 - Improve the performance of our consensus-diff application code
10102 when Tor is built with the --enable-fragile-hardening option set.
10103 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
10105 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
10106 - Don't exit the Tor process if setrlimit() fails to change the file
10107 limit (which can happen sometimes on some versions of OSX). Fixes
10108 bug 21074; bugfix on 0.0.9pre5.
10110 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
10111 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
10113 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
10114 bugfix on 0.2.9.4-alpha.
10116 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
10117 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
10118 25005; bugfix on 0.3.2.7-rc.
10120 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
10121 - Look at the "HSRend" protocol version, not the "HSDir" protocol
10122 version, when deciding whether a consensus entry can support the
10123 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
10124 bugfix on 0.3.2.1-alpha.
10126 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
10127 - Update the "rust dependencies" submodule to be a project-level
10128 repository, rather than a user repository. Closes ticket 25323.
10130 o Documentation (backport from 0.3.3.1-alpha)
10131 - Document that operators who run more than one relay or bridge are
10132 expected to set MyFamily and ContactInfo correctly. Closes
10136 Changes in version 0.3.3.3-alpha - 2018-03-03
10137 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
10138 It includes an important security fix for a remote crash attack
10139 against directory authorities tracked as TROVE-2018-001.
10141 Additionally, with this release, we are upgrading the severity of a
10142 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
10143 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
10144 a use-after-free pattern. As such, we are now tracking that bug as
10145 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
10146 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
10148 This release also fixes several minor bugs and annoyances from
10151 Relays running 0.3.2.x should upgrade to one of the versions released
10152 today, for the fix to TROVE-2018-002. Directory authorities should
10153 also upgrade. (Relays on earlier versions might want to update too for
10154 the DoS mitigations.)
10156 o Major bugfixes (denial-of-service, directory authority):
10157 - Fix a protocol-list handling bug that could be used to remotely crash
10158 directory authorities with a null-pointer exception. Fixes bug 25074;
10159 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
10162 o Minor features (compatibility, OpenSSL):
10163 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
10164 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
10165 since they neither disabled TLS 1.3 nor enabled any of the
10166 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
10167 Closes ticket 24978.
10169 o Minor features (logging):
10170 - Clarify the log messages produced when getrandom() or a related
10171 entropy-generation mechanism gives an error. Closes ticket 25120.
10173 o Minor features (testing):
10174 - Add a "make test-rust" target to run the rust tests only. Closes
10177 o Minor bugfixes (denial-of-service):
10178 - Fix a possible crash on malformed consensus. If a consensus had
10179 contained an unparseable protocol line, it could have made clients
10180 and relays crash with a null-pointer exception. To exploit this
10181 issue, however, an attacker would need to be able to subvert the
10182 directory authority system. Fixes bug 25251; bugfix on
10183 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
10185 o Minor bugfixes (DoS mitigation):
10186 - Add extra safety checks when refilling the circuit creation bucket
10187 to ensure we never set a value above the allowed maximum burst.
10188 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
10189 - When a new consensus arrives, don't update our DoS-mitigation
10190 parameters if we aren't a public relay. Fixes bug 25223; bugfix
10193 o Minor bugfixes (man page, SocksPort):
10194 - Remove dead code from the old "SocksSocket" option, and rename
10195 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
10196 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
10198 o Minor bugfixes (performance):
10199 - Reduce the number of circuits that will be opened at once during
10200 the circuit build timeout phase. This is done by increasing the
10201 idle timeout to 3 minutes, and lowering the maximum number of
10202 concurrent learning circuits to 10. Fixes bug 24769; bugfix
10205 o Minor bugfixes (spec conformance):
10206 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
10208 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
10209 bugfix on 0.2.9.4-alpha.
10211 o Minor bugfixes (spec conformance, rust):
10212 - Resolve a denial-of-service issue caused by an infinite loop in
10213 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
10214 Also tracked as TROVE-2018-003.
10216 o Code simplification and refactoring:
10217 - Update the "rust dependencies" submodule to be a project-level
10218 repository, rather than a user repository. Closes ticket 25323.
10221 Changes in version 0.3.3.2-alpha - 2018-02-10
10222 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
10223 introduces a mechanism to handle the high loads that many relay
10224 operators have been reporting recently. It also fixes several bugs in
10225 older releases. If this new code proves reliable, we plan to backport
10226 it to older supported release series.
10228 o Major features (denial-of-service mitigation):
10229 - Give relays some defenses against the recent network overload. We
10230 start with three defenses (default parameters in parentheses).
10231 First: if a single client address makes too many concurrent
10232 connections (>100), hang up on further connections. Second: if a
10233 single client address makes circuits too quickly (more than 3 per
10234 second, with an allowed burst of 90) while also having too many
10235 connections open (3), refuse new create cells for the next while
10236 (1-2 hours). Third: if a client asks to establish a rendezvous
10237 point to you directly, ignore the request. These defenses can be
10238 manually controlled by new torrc options, but relays will also
10239 take guidance from consensus parameters, so there's no need to
10240 configure anything manually. Implements ticket 24902.
10242 o Major bugfixes (netflow padding):
10243 - Stop adding unneeded channel padding right after we finish
10244 flushing to a connection that has been trying to flush for many
10245 seconds. Instead, treat all partial or complete flushes as
10246 activity on the channel, which will defer the time until we need
10247 to add padding. This fix should resolve confusing and scary log
10248 messages like "Channel padding timeout scheduled 221453ms in the
10249 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
10251 o Major bugfixes (protocol versions):
10252 - Add Link protocol version 5 to the supported protocols list. Fixes
10253 bug 25070; bugfix on 0.3.1.1-alpha.
10255 o Major bugfixes (scheduler, consensus):
10256 - The scheduler subsystem was failing to promptly notice changes in
10257 consensus parameters, making it harder to switch schedulers
10258 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
10260 o Minor features (denial-of-service avoidance):
10261 - Make our OOM handler aware of the geoip client history cache so it
10262 doesn't fill up the memory. This check is important for IPv6 and
10263 our DoS mitigation subsystem. Closes ticket 25122.
10265 o Minor features (directory authority):
10266 - When directory authorities are unable to add signatures to a
10267 pending consensus, log the reason why. Closes ticket 24849.
10269 o Minor features (geoip):
10270 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
10273 o Minor features (logging, diagnostic):
10274 - When logging a failure to create an onion service's descriptor,
10275 also log what the problem with the descriptor was. Diagnostic for
10278 o Minor bugfix (channel connection):
10279 - Use the actual observed address of an incoming relay connection,
10280 not the canonical address of the relay from its descriptor, when
10281 making decisions about how to handle the incoming connection.
10282 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
10284 o Minor bugfix (directory authority):
10285 - Directory authorities, when refusing a descriptor from a rejected
10286 relay, now explicitly tell the relay (in its logs) to set a valid
10287 ContactInfo address and contact the bad-relays@ mailing list.
10288 Fixes bug 25170; bugfix on 0.2.9.1.
10290 o Minor bugfixes (all versions of Tor):
10291 - Use the "misspell" tool to detect and fix typos throughout the
10292 source code. Fixes bug 23650; bugfix on various versions of Tor.
10293 Patch from Deepesh Pathak.
10295 o Minor bugfixes (circuit, cannibalization):
10296 - Don't cannibalize preemptively-built circuits if we no longer
10297 recognize their first hop. This situation can happen if our Guard
10298 relay went off the consensus after the circuit was created. Fixes
10299 bug 24469; bugfix on 0.0.6.
10301 o Minor bugfixes (correctness):
10302 - Remove a nonworking, unnecessary check to see whether a circuit
10303 hop's identity digest was set when the circuit failed. Fixes bug
10304 24927; bugfix on 0.2.4.4-alpha.
10306 o Minor bugfixes (logging):
10307 - Don't treat inability to store a cached consensus object as a bug:
10308 it can happen normally when we are out of disk space. Fixes bug
10309 24859; bugfix on 0.3.1.1-alpha.
10310 - Fix a (mostly harmless) race condition when invoking
10311 LOG_PROTOCOL_WARN message from a subthread while the torrc options
10312 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
10314 o Minor bugfixes (onion services):
10315 - Remove a BUG() statement when a client fetches an onion descriptor
10316 that has a lower revision counter than the one in its cache. This
10317 can happen in normal circumstances due to HSDir desync. Fixes bug
10318 24976; bugfix on 0.3.2.1-alpha.
10319 - If we are configured to offer a single onion service, don't log
10320 long-term established one hop rendezvous points in the heartbeat.
10321 Fixes bug 25116; bugfix on 0.2.9.6-rc.
10323 o Minor bugfixes (performance):
10324 - Avoid calling protocol_list_supports_protocol() from inside tight
10325 loops when running with cached routerinfo_t objects. Instead,
10326 summarize the relevant protocols as flags in the routerinfo_t, as
10327 we do for routerstatus_t objects. This change simplifies our code
10328 a little, and saves a large amount of short-term memory allocation
10329 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
10331 o Minor bugfixes (Rust FFI):
10332 - Fix a minor memory leak which would happen whenever the C code
10333 would call the Rust implementation of
10334 protover_get_supported_protocols(). This was due to the C version
10335 returning a static string, whereas the Rust version newly allocated
10336 a CString to pass across the FFI boundary. Consequently, the C
10337 code was not expecting to need to free() what it was given. Fixes
10338 bug 25127; bugfix on 0.3.2.1-alpha.
10340 o Minor bugfixes (scheduler, KIST):
10341 - Avoid adding the same channel twice in the KIST scheduler pending
10342 list, which would waste CPU cycles. Fixes bug 24700; bugfix
10345 o Minor bugfixes (unit test, monotonic time):
10346 - Increase a constant (1msec to 10msec) in the monotonic time test
10347 that makes sure the nsec/usec/msec times read are synchronized.
10348 This change was needed to accommodate slow systems like armel or
10349 when the clock_gettime() is not a VDSO on the running kernel.
10350 Fixes bug 25113; bugfix on 0.2.9.1.
10352 o Minor bugfixes (v3 onion services):
10353 - Look at the "HSRend" protocol version, not the "HSDir" protocol
10354 version, when deciding whether a consensus entry can support the
10355 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
10356 bugfix on 0.3.2.1-alpha.
10358 o Code simplification and refactoring:
10359 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
10361 - Remove a series of counters used to track circuit extend attempts
10362 and connection status but that in reality we aren't using for
10363 anything other than stats logged by a SIGUSR1 signal. Closes
10366 o Documentation (man page):
10367 - The HiddenServiceVersion torrc option accepts only one number:
10368 either version 2 or 3. Closes ticket 25026; bugfix
10372 Changes in version 0.3.3.1-alpha - 2018-01-25
10373 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
10374 several new features to Tor, including several improvements to
10375 bootstrapping, and support for an experimental "vanguards" feature to
10376 resist guard discovery attacks. This series also includes better
10377 support for applications that need to embed Tor or manage v3
10380 o Major features (embedding):
10381 - There is now a documented stable API for programs that need to
10382 embed Tor. See tor_api.h for full documentation and known bugs.
10383 Closes ticket 23684.
10384 - Tor now has support for restarting in the same process.
10385 Controllers that run Tor using the "tor_api.h" interface can now
10386 restart Tor after Tor has exited. This support is incomplete,
10387 however: we fixed crash bugs that prevented it from working at
10388 all, but many bugs probably remain, including a possibility of
10389 security issues. Implements ticket 24581.
10391 o Major features (IPv6, directory documents):
10392 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
10393 consensus. This information makes it easier for IPv6 clients to
10394 bootstrap and choose reachable entry guards. Implements ticket 23826.
10395 - Add consensus method 28, which removes IPv6 ORPorts from
10396 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
10397 are redundant in microdescs. This change will be used by Tor clients
10398 on 0.2.8.x and later. (That is to say, with all Tor clients that
10399 have IPv6 bootstrap and guard support.) Implements ticket 23828.
10400 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
10401 set by different numbers of authorities. Fixes 23870
10404 o Major features (onion service v3, control port):
10405 - The control port now supports commands and events for v3 onion
10406 services. It is now possible to create ephemeral v3 services using
10407 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
10408 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
10409 DEL_ONION) have been extended to support v3 onion services. Closes
10410 ticket 20699; implements proposal 284.
10412 o Major features (onion services):
10413 - Provide torrc options to pin the second and third hops of onion
10414 service circuits to a list of nodes. The option HSLayer2Guards
10415 pins the second hop, and the option HSLayer3Guards pins the third
10416 hop. These options are for use in conjunction with experiments
10417 with "vanguards" for preventing guard enumeration attacks. Closes
10420 o Major features (rust, portability, experimental):
10421 - Tor now ships with an optional implementation of one of its
10422 smaller modules (protover.c) in the Rust programming language. To
10423 try it out, install a Rust build environment, and configure Tor
10424 with "--enable-rust --enable-cargo-online-mode". This should not
10425 cause any user-visible changes, but should help us gain more
10426 experience with Rust, and plan future Rust integration work.
10427 Implementation by Chelsea Komlo. Closes ticket 22840.
10429 o Minor features (storage, configuration):
10430 - Users can store cached directory documents somewhere other than
10431 the DataDirectory by using the CacheDirectory option. Similarly,
10432 the storage location for relay's keys can be overridden with the
10433 KeyDirectory option. Closes ticket 22703.
10435 o Major features (v3 onion services, ipv6):
10436 - When v3 onion service clients send introduce cells, they now
10437 include the IPv6 address of the rendezvous point, if it has one.
10438 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
10439 in future Tor versions, IPv6-only v3 single onion services will be
10440 able to use IPv6 addresses to connect directly to the rendezvous
10441 point. Closes ticket 23577. Patch by Neel Chauhan.
10443 o Major bugfixes (onion services, retry behavior):
10444 - Fix an "off by 2" error in counting rendezvous failures on the
10445 onion service side. While we thought we would stop the rendezvous
10446 attempt after one failed circuit, we were actually making three
10447 circuit attempts before giving up. Now switch to a default of 2,
10448 and allow the consensus parameter "hs_service_max_rdv_failures" to
10449 override. Fixes bug 24895; bugfix on 0.0.6.
10450 - New-style (v3) onion services now obey the "max rendezvous circuit
10451 attempts" logic. Previously they would make as many rendezvous
10452 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
10453 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
10455 o Major bugfixes (relays):
10456 - Fix a set of false positives where relays would consider
10457 connections to other relays as being client-only connections (and
10458 thus e.g. deserving different link padding schemes) if those
10459 relays fell out of the consensus briefly. Now we look only at the
10460 initial handshake and whether the connection authenticated as a
10461 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
10463 o Minor feature (IPv6):
10464 - Make IPv6-only clients wait for microdescs for relays, even if we
10465 were previously using descriptors (or were using them as a bridge)
10466 and have a cached descriptor for them. Implements ticket 23827.
10467 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
10468 them, rather than waiting to download microdescriptors.
10469 Implements ticket 23827.
10471 o Minor features (cleanup):
10472 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
10473 when it stops. Closes ticket 23271.
10475 o Minor features (defensive programming):
10476 - Most of the functions in Tor that free objects have been replaced
10477 with macros that free the objects and set the corresponding
10478 pointers to NULL. This change should help prevent a large class of
10479 dangling pointer bugs. Closes ticket 24337.
10480 - Where possible, the tor_free() macro now only evaluates its input
10481 once. Part of ticket 24337.
10482 - Check that microdesc ed25519 ids are non-zero in
10483 node_get_ed25519_id() before returning them. Implements ticket
10484 24001, patch by "aruna1234".
10486 o Minor features (embedding):
10487 - Tor can now start with a preauthenticated control connection
10488 created by the process that launched it. This feature is meant for
10489 use by programs that want to launch and manage a Tor process
10490 without allowing other programs to manage it as well. For more
10491 information, see the __OwningControllerFD option documented in
10492 control-spec.txt. Closes ticket 23900.
10493 - On most errors that would cause Tor to exit, it now tries to
10494 return from the tor_main() function, rather than calling the
10495 system exit() function. Most users won't notice a difference here,
10496 but it should be significant for programs that run Tor inside
10497 a separate thread: they should now be able to survive Tor's exit
10498 conditions rather than having Tor shut down the entire process.
10499 Closes ticket 23848.
10500 - Applications that want to embed Tor can now tell Tor not to
10501 register any of its own POSIX signal handlers, using the
10502 __DisableSignalHandlers option. Closes ticket 24588.
10504 o Minor features (fallback directory list):
10505 - Avoid selecting fallbacks that change their IP addresses too
10506 often. Select more fallbacks by ignoring the Guard flag, and
10507 allowing lower cutoffs for the Running and V2Dir flags. Also allow
10508 a lower bandwidth, and a higher number of fallbacks per operator
10509 (5% of the list). Implements ticket 24785.
10510 - Update the fallback whitelist and blacklist based on opt-ins and
10511 relay changes. Closes tickets 22321, 24678, 22527, 24135,
10514 o Minor features (fallback directory mirror configuration):
10515 - Add a nickname to each fallback in a C comment. This makes it
10516 easier for operators to find their relays, and allows stem to use
10517 nicknames to identify fallbacks. Implements ticket 24600.
10518 - Add a type and version header to the fallback directory mirror
10519 file. Also add a delimiter to the end of each fallback entry. This
10520 helps external parsers like stem and Relay Search. Implements
10522 - Add an extrainfo cache flag for each fallback in a C comment. This
10523 allows stem to use fallbacks to fetch extra-info documents, rather
10524 than using authorities. Implements ticket 22759.
10525 - Add the generateFallbackDirLine.py script for automatically
10526 generating fallback directory mirror lines from relay fingerprints.
10527 No more typos! Add the lookupFallbackDirContact.py script for
10528 automatically looking up operator contact info from relay
10529 fingerprints. Implements ticket 24706, patch by teor and atagar.
10530 - Reject any fallback directory mirror that serves an expired
10531 consensus. Implements ticket 20942, patch by "minik".
10532 - Remove commas and equals signs from external string inputs to the
10533 fallback list. This avoids format confusion attacks. Implements
10535 - Remove the "weight=10" line from fallback directory mirror
10536 entries. Ticket 24681 will maintain the current fallback weights
10537 by changing Tor's default fallback weight to 10. Implements
10539 - Stop logging excessive information about fallback netblocks.
10540 Implements ticket 24791.
10542 o Minor features (forward-compatibility):
10543 - If a relay supports some link authentication protocol that we do
10544 not recognize, then include that relay's ed25519 key when telling
10545 other relays to extend to it. Previously, we treated future
10546 versions as if they were too old to support ed25519 link
10547 authentication. Closes ticket 20895.
10549 o Minor features (heartbeat):
10550 - Add onion service information to our heartbeat logs, displaying
10551 stats about the activity of configured onion services. Closes
10554 o Minor features (instrumentation, development):
10555 - Add the MainloopStats option to allow developers to get
10556 instrumentation information from the main event loop via the
10557 heartbeat messages. We hope to use this to improve Tor's behavior
10558 when it's trying to sleep. Closes ticket 24605.
10560 o Minor features (log messages):
10561 - Improve a warning message that happens when we fail to re-parse an
10562 old router because of an expired certificate. Closes ticket 20020.
10563 - Make the log more quantitative when we hit MaxMemInQueues
10564 threshold exposing some values. Closes ticket 24501.
10566 o Minor features (logging, android):
10567 - Added support for the Android logging subsystem. Closes
10570 o Minor features (performance):
10571 - Support predictive circuit building for onion service circuits
10572 with multiple layers of guards. Closes ticket 23101.
10573 - Use stdatomic.h where available, rather than mutexes, to implement
10574 atomic_counter_t. Closes ticket 23953.
10576 o Minor features (performance, 32-bit):
10577 - Improve performance on 32-bit systems by avoiding 64-bit division
10578 when calculating the timestamp in milliseconds for channel padding
10579 computations. Implements ticket 24613.
10580 - Improve performance on 32-bit systems by avoiding 64-bit division
10581 when timestamping cells and buffer chunks for OOM calculations.
10582 Implements ticket 24374.
10584 o Minor features (performance, OSX, iOS):
10585 - Use the mach_approximate_time() function (when available) to
10586 implement coarse monotonic time. Having a coarse time function
10587 should avoid a large number of system calls, and improve
10588 performance slightly, especially under load. Closes ticket 24427.
10590 o Minor features (performance, windows):
10591 - Improve performance on Windows Vista and Windows 7 by adjusting
10592 TCP send window size according to the recommendation from
10593 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
10596 o Major features (relay):
10597 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
10598 operator to use a more reasonable ("reduced") exit policy, rather
10599 than the default one. If you want to run an exit node without
10600 thinking too hard about which ports to allow, this one is for you.
10601 Closes ticket 13605. Patch from Neel Chauhan.
10603 o Minor features (testing, debugging, embedding):
10604 - For development purposes, Tor now has a mode in which it runs for
10605 a few seconds, then stops, and starts again without exiting the
10606 process. This mode is meant to help us debug various issues with
10607 ticket 23847. To use this feature, compile with
10608 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
10609 environment variable. This is expected to crash a lot, and is
10610 really meant for developers only. It will likely be removed in a
10611 future release. Implements ticket 24583.
10613 o Minor bugfix (network IPv6 test):
10614 - Tor's test scripts now check if "ping -6 ::1" works when the user
10615 runs "make test-network-all". Fixes bug 24677; bugfix on
10616 0.2.9.3-alpha. Patch by "ffmancera".
10618 o Minor bugfixes (build, rust):
10619 - Fix output of autoconf checks to display success messages for Rust
10620 dependencies and a suitable rustc compiler version. Fixes bug
10621 24612; bugfix on 0.3.1.3-alpha.
10622 - When building with Rust on OSX, link against libresolv, to work
10623 around the issue at https://github.com/rust-lang/rust/issues/46797.
10624 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
10625 - Don't pass the --quiet option to cargo: it seems to suppress some
10626 errors, which is not what we want to do when building. Fixes bug
10627 24518; bugfix on 0.3.1.7.
10628 - Build correctly when building from outside Tor's source tree with
10629 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
10632 o Minor bugfixes (directory authorities, IPv6):
10633 - When creating a routerstatus (vote) from a routerinfo (descriptor),
10634 set the IPv6 address to the unspecified IPv6 address, and
10635 explicitly initialize the port to zero. Fixes bug 24488; bugfix
10638 o Minor bugfixes (fallback directory mirrors):
10639 - Make updateFallbackDirs.py search harder for python. (Some OSs
10640 don't put it in /usr/bin.) Fixes bug 24708; bugfix
10643 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
10644 - When hibernating, close connections normally and allow them to
10645 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
10647 - Do not attempt to launch self-reachability tests when entering
10648 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
10649 - Resolve several bugs related to descriptor fetching on bridge
10650 clients with bandwidth accounting enabled. (This combination is
10651 not recommended!) Fixes a case of bug 12062; bugfix
10653 - When hibernating, do not attempt to launch DNS checks. Fixes a
10654 case of bug 12062; bugfix on 0.1.2.2-alpha.
10655 - When hibernating, do not try to upload or download descriptors.
10656 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
10658 o Minor bugfixes (IPv6, bridges):
10659 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
10660 bugfix on 0.2.8.2-alpha.
10661 - Tor now sets IPv6 address in the routerstatus as well as in the
10662 router descriptors when updating addresses for a bridge. Closes
10663 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
10665 o Minor bugfixes (linux seccomp2 sandbox):
10666 - When running with the sandbox enabled, reload configuration files
10667 correctly even when %include was used. Previously we would crash.
10668 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
10670 o Minor bugfixes (memory leaks):
10671 - Avoid possible at-exit memory leaks related to use of Libevent's
10672 event_base_once() function. (This function tends to leak memory if
10673 the event_base is closed before the event fires.) Fixes bug 24584;
10674 bugfix on 0.2.8.1-alpha.
10675 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
10678 o Minor bugfixes (OSX):
10679 - Don't exit the Tor process if setrlimit() fails to change the file
10680 limit (which can happen sometimes on some versions of OSX). Fixes
10681 bug 21074; bugfix on 0.0.9pre5.
10683 o Minor bugfixes (performance, fragile-hardening):
10684 - Improve the performance of our consensus-diff application code
10685 when Tor is built with the --enable-fragile-hardening option set.
10686 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
10688 o Minor bugfixes (performance, timeouts):
10689 - Consider circuits for timeout as soon as they complete a hop. This
10690 is more accurate than applying the timeout in
10691 circuit_expire_building() because that function is only called
10692 once per second, which is now too slow for typical timeouts on the
10693 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
10694 - Use onion service circuits (and other circuits longer than 3 hops)
10695 to calculate a circuit build timeout. Previously, Tor only
10696 calculated its build timeout based on circuits that planned to be
10697 exactly 3 hops long. With this change, we include measurements
10698 from all circuits at the point where they complete their third
10699 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
10701 o Minor bugfixes (testing):
10702 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
10703 bugfix on 0.2.3.1-alpha.
10704 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
10705 25005; bugfix on 0.3.2.7-rc.
10707 o Code simplification and refactoring:
10708 - Remove /usr/athena from search path in configure.ac. Closes
10710 - Remove duplicate code in node_has_curve25519_onion_key() and
10711 node_get_curve25519_onion_key(), and add a check for a zero
10712 microdesc curve25519 onion key. Closes ticket 23966, patch by
10713 "aruna1234" and teor.
10714 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
10715 memory allocations with large numbers of OR connections (e.g.
10716 relays). Closes ticket 24119.
10717 - Separate the function that deletes ephemeral files when Tor
10719 - Small changes to Tor's buf_t API to make it suitable for use as a
10720 general-purpose safe string constructor. Closes ticket 22342.
10721 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
10722 avoid source code identifier confusion. Closes ticket 24467.
10723 - The tor_git_revision[] constant no longer needs to be redeclared
10724 by everything that links against the rest of Tor. Done as part of
10725 ticket 23845, to simplify our external API.
10726 - We make extend_info_from_node() use node_get_curve25519_onion_key()
10727 introduced in ticket 23577 to access the curve25519 public keys
10728 rather than accessing it directly. Closes ticket 23760. Patch by
10730 - Add a function to log channels' scheduler state changes to aid
10731 debugging efforts. Closes ticket 24531.
10734 - Add documentation on how to build tor with Rust dependencies
10735 without having to be online. Closes ticket 22907; bugfix
10737 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
10738 traffic. Closes ticket 24318.
10739 - Document that OutboundBindAddress doesn't apply to DNS requests.
10740 Closes ticket 22145. Patch from Aruna Maurya.
10741 - Document that operators who run more than one relay or bridge are
10742 expected to set MyFamily and ContactInfo correctly. Closes
10745 o Code simplification and refactoring (channels):
10746 - Remove the incoming and outgoing channel queues. These were never
10747 used, but still took up a step in our fast path.
10748 - The majority of the channel unit tests have been rewritten and the
10749 code coverage has now been raised to 83.6% for channel.c. Closes
10751 - Remove other dead code from the channel subsystem: All together,
10752 this cleanup has removed more than 1500 lines of code overall and
10753 adding very little except for unit test.
10755 o Code simplification and refactoring (circuit rendezvous):
10756 - Split the client-side rendezvous circuit lookup into two
10757 functions: one that returns only established circuits and another
10758 that returns all kinds of circuits. Closes ticket 23459.
10760 o Code simplification and refactoring (controller):
10761 - Make most of the variables in networkstatus_getinfo_by_purpose()
10762 const. Implements ticket 24489.
10765 Changes in version 0.3.2.9 - 2018-01-09
10766 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
10768 The 0.3.2 series includes our long-anticipated new onion service
10769 design, with numerous security features. (For more information, see
10770 our blog post at https://blog.torproject.org/fall-harvest.) We also
10771 have a new circuit scheduler algorithm for improved performance on
10772 relays everywhere (see https://blog.torproject.org/kist-and-tell),
10773 along with many smaller features and bugfixes.
10775 Per our stable release policy, we plan to support each stable release
10776 series for at least the next nine months, or for three months after
10777 the first stable release of the next series: whichever is longer. If
10778 you need a release with long-term support, we recommend that you stay
10779 with the 0.2.9 series.
10781 Below is a list of the changes since 0.3.2.8-rc. For a list of all
10782 changes since 0.3.1, see the ReleaseNotes file.
10784 o Minor features (fallback directory mirrors):
10785 - The fallback directory list has been re-generated based on the
10786 current status of the network. Tor uses fallback directories to
10787 bootstrap when it doesn't yet have up-to-date directory
10788 information. Closes ticket 24801.
10789 - Make the default DirAuthorityFallbackRate 0.1, so that clients
10790 prefer to bootstrap from fallback directory mirrors. This is a
10791 follow-up to 24679, which removed weights from the default
10792 fallbacks. Implements ticket 24681.
10794 o Minor features (geoip):
10795 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
10798 o Minor bugfixes (address selection):
10799 - When the fascist_firewall_choose_address_ functions don't find a
10800 reachable address, set the returned address to the null address
10801 and port. This is a precautionary measure, because some callers do
10802 not check the return value. Fixes bug 24736; bugfix
10805 o Minor bugfixes (compilation):
10806 - Resolve a few shadowed-variable warnings in the onion service
10807 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
10809 o Minor bugfixes (portability, msvc):
10810 - Fix a bug in the bit-counting parts of our timing-wheel code on
10811 MSVC. (Note that MSVC is still not a supported build platform, due
10812 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
10816 Changes in version 0.3.2.8-rc - 2017-12-21
10817 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
10818 schedulers that had led servers under heavy load to overload their
10819 outgoing connections. All relay operators running earlier 0.3.2.x
10820 versions should upgrade. This version also includes a mitigation for
10821 over-full DESTROY queues leading to out-of-memory conditions: if it
10822 works, we will soon backport it to earlier release series.
10824 This is the second release candidate in the 0.3.2 series. If we find
10825 no new bugs or regression here, then the first stable 0.3.2 release
10826 will be nearly identical to this.
10828 o Major bugfixes (KIST, scheduler):
10829 - The KIST scheduler did not correctly account for data already
10830 enqueued in each connection's send socket buffer, particularly in
10831 cases when the TCP/IP congestion window was reduced between
10832 scheduler calls. This situation lead to excessive per-connection
10833 buffering in the kernel, and a potential memory DoS. Fixes bug
10834 24665; bugfix on 0.3.2.1-alpha.
10836 o Minor features (geoip):
10837 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
10840 o Minor bugfixes (hidden service v3):
10841 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
10842 the probability of reaching a service for a client missing
10843 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
10845 o Minor bugfixes (memory usage):
10846 - When queuing DESTROY cells on a channel, only queue the circuit-id
10847 and reason fields: not the entire 514-byte cell. This fix should
10848 help mitigate any bugs or attacks that fill up these queues, and
10849 free more RAM for other uses. Fixes bug 24666; bugfix
10852 o Minor bugfixes (scheduler, KIST):
10853 - Use a sane write limit for KISTLite when writing onto a connection
10854 buffer instead of using INT_MAX and shoving as much as it can.
10855 Because the OOM handler cleans up circuit queues, we are better
10856 off at keeping them in that queue instead of the connection's
10857 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
10860 Changes in version 0.3.2.7-rc - 2017-12-14
10861 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
10862 including some that could affect reliability or correctness.
10864 This is the first release candidate in the 0.3.2 series. If we find no
10865 new bugs or regression here, then the first stable 0.3.2. release will
10866 be nearly identical to this.
10868 o Major bugfixes (circuit prediction):
10869 - Fix circuit prediction logic so that a client doesn't treat a port
10870 as being "handled" by a circuit if that circuit already has
10871 isolation settings on it. This change should make Tor clients more
10872 responsive by improving their chances of having a pre-created
10873 circuit ready for use when a request arrives. Fixes bug 18859;
10874 bugfix on 0.2.3.3-alpha.
10876 o Minor features (logging):
10877 - Provide better warnings when the getrandom() syscall fails. Closes
10880 o Minor features (portability):
10881 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
10882 (It doesn't yet work with the sandbox enabled.) Closes
10885 o Minor bugfixes (bridge clients, bootstrap):
10886 - Retry directory downloads when we get our first bridge descriptor
10887 during bootstrap or while reconnecting to the network. Keep
10888 retrying every time we get a bridge descriptor, until we have a
10889 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
10890 - Stop delaying bridge descriptor fetches when we have cached bridge
10891 descriptors. Instead, only delay bridge descriptor fetches when we
10892 have at least one reachable bridge. Fixes part of bug 24367;
10893 bugfix on 0.2.0.3-alpha.
10894 - Stop delaying directory fetches when we have cached bridge
10895 descriptors. Instead, only delay bridge descriptor fetches when
10896 all our bridges are definitely unreachable. Fixes part of bug
10897 24367; bugfix on 0.2.0.3-alpha.
10899 o Minor bugfixes (compilation):
10900 - Fix a signed/unsigned comparison warning introduced by our fix to
10901 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
10903 o Minor bugfixes (correctness):
10904 - Fix several places in our codebase where a C compiler would be
10905 likely to eliminate a check, based on assuming that undefined
10906 behavior had not happened elsewhere in the code. These cases are
10907 usually a sign of redundant checking or dubious arithmetic. Found
10908 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
10909 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
10912 o Minor bugfixes (onion service v3):
10913 - Fix a race where an onion service would launch a new intro circuit
10914 after closing an old one, but fail to register it before freeing
10915 the previously closed circuit. This bug was making the service
10916 unable to find the established intro circuit and thus not upload
10917 its descriptor, thus making a service unavailable for up to 24
10918 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
10920 o Minor bugfixes (scheduler, KIST):
10921 - Properly set the scheduler state of an unopened channel in the
10922 KIST scheduler main loop. This prevents a harmless but annoying
10923 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
10924 - Avoid a possible integer overflow when computing the available
10925 space on the TCP buffer of a channel. This had no security
10926 implications; but could make KIST allow too many cells on a
10927 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
10928 - Downgrade to "info" a harmless warning about the monotonic time
10929 moving backwards: This can happen on platform not supporting
10930 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
10933 Changes in version 0.3.2.6-alpha - 2017-12-01
10934 This version of Tor is the latest in the 0.3.2 alpha series. It
10935 includes fixes for several important security issues. All Tor users
10936 should upgrade to this release, or to one of the other releases coming
10939 o Major bugfixes (security):
10940 - Fix a denial of service bug where an attacker could use a
10941 malformed directory object to cause a Tor instance to pause while
10942 OpenSSL would try to read a passphrase from the terminal. (Tor
10943 instances run without a terminal, which is the case for most Tor
10944 packages, are not impacted.) Fixes bug 24246; bugfix on every
10945 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10946 Found by OSS-Fuzz as testcase 6360145429790720.
10947 - Fix a denial of service issue where an attacker could crash a
10948 directory authority using a malformed router descriptor. Fixes bug
10949 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
10951 - When checking for replays in the INTRODUCE1 cell data for a
10952 (legacy) onion service, correctly detect replays in the RSA-
10953 encrypted part of the cell. We were previously checking for
10954 replays on the entire cell, but those can be circumvented due to
10955 the malleability of Tor's legacy hybrid encryption. This fix helps
10956 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10957 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10960 o Major bugfixes (security, onion service v2):
10961 - Fix a use-after-free error that could crash v2 Tor onion services
10962 when they failed to open circuits while expiring introduction
10963 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10964 also tracked as TROVE-2017-013 and CVE-2017-8823.
10966 o Major bugfixes (security, relay):
10967 - When running as a relay, make sure that we never build a path
10968 through ourselves, even in the case where we have somehow lost the
10969 version of our descriptor appearing in the consensus. Fixes part
10970 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10971 as TROVE-2017-012 and CVE-2017-8822.
10972 - When running as a relay, make sure that we never choose ourselves
10973 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
10974 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
10976 o Minor feature (relay statistics):
10977 - Change relay bandwidth reporting stats interval from 4 hours to 24
10978 hours in order to reduce the efficiency of guard discovery
10979 attacks. Fixes ticket 23856.
10981 o Minor features (directory authority):
10982 - Add an IPv6 address for the "bastet" directory authority. Closes
10985 o Minor bugfixes (client):
10986 - By default, do not enable storage of client-side DNS values. These
10987 values were unused by default previously, but they should not have
10988 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
10991 Changes in version 0.3.1.9 - 2017-12-01:
10992 Tor 0.3.1.9 backports important security and stability fixes from the
10993 0.3.2 development series. All Tor users should upgrade to this
10994 release, or to another of the releases coming out today.
10996 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10997 - Fix a denial of service bug where an attacker could use a
10998 malformed directory object to cause a Tor instance to pause while
10999 OpenSSL would try to read a passphrase from the terminal. (Tor
11000 instances run without a terminal, which is the case for most Tor
11001 packages, are not impacted.) Fixes bug 24246; bugfix on every
11002 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11003 Found by OSS-Fuzz as testcase 6360145429790720.
11004 - Fix a denial of service issue where an attacker could crash a
11005 directory authority using a malformed router descriptor. Fixes bug
11006 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11008 - When checking for replays in the INTRODUCE1 cell data for a
11009 (legacy) onion service, correctly detect replays in the RSA-
11010 encrypted part of the cell. We were previously checking for
11011 replays on the entire cell, but those can be circumvented due to
11012 the malleability of Tor's legacy hybrid encryption. This fix helps
11013 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11014 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11017 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11018 - Fix a use-after-free error that could crash v2 Tor onion services
11019 when they failed to open circuits while expiring introduction
11020 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11021 also tracked as TROVE-2017-013 and CVE-2017-8823.
11023 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11024 - When running as a relay, make sure that we never build a path
11025 through ourselves, even in the case where we have somehow lost the
11026 version of our descriptor appearing in the consensus. Fixes part
11027 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11028 as TROVE-2017-012 and CVE-2017-8822.
11029 - When running as a relay, make sure that we never choose ourselves
11030 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
11031 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
11033 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
11034 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11035 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11036 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11037 identifying and finding a workaround to this bug and to Moritz,
11038 Arthur Edelstein, and Roger for helping to track it down and
11041 o Minor features (bridge):
11042 - Bridges now include notice in their descriptors that they are
11043 bridges, and notice of their distribution status, based on their
11044 publication settings. Implements ticket 18329. For more fine-
11045 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11048 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11049 - Add an IPv6 address for the "bastet" directory authority. Closes
11052 o Minor features (geoip):
11053 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11056 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
11057 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11058 relays, to prevent spurious address resolutions and descriptor
11059 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11060 bugfix on in 0.2.8.1-alpha.
11062 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
11063 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
11064 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11066 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
11067 - When a circuit is marked for close, do not attempt to package any
11068 cells for channels on that circuit. Previously, we would detect
11069 this condition lower in the call stack, when we noticed that the
11070 circuit had no attached channel, and log an annoying message.
11071 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11073 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
11074 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
11075 so it matches dir-spec.txt. Fixes bug 24262; bugfix
11078 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
11079 - Avoid a crash when transitioning from client mode to bridge mode.
11080 Previously, we would launch the worker threads whenever our
11081 "public server" mode changed, but not when our "server" mode
11082 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11085 Changes in version 0.3.0.13 - 2017-12-01
11086 Tor 0.3.0.13 backports important security and stability bugfixes from
11087 later Tor releases. All Tor users should upgrade to this release, or
11088 to another of the releases coming out today.
11090 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
11091 2018. If you need a release with long-term support, please stick with
11092 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11094 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11095 - Fix a denial of service bug where an attacker could use a
11096 malformed directory object to cause a Tor instance to pause while
11097 OpenSSL would try to read a passphrase from the terminal. (Tor
11098 instances run without a terminal, which is the case for most Tor
11099 packages, are not impacted.) Fixes bug 24246; bugfix on every
11100 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11101 Found by OSS-Fuzz as testcase 6360145429790720.
11102 - Fix a denial of service issue where an attacker could crash a
11103 directory authority using a malformed router descriptor. Fixes bug
11104 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11106 - When checking for replays in the INTRODUCE1 cell data for a
11107 (legacy) onion service, correctly detect replays in the RSA-
11108 encrypted part of the cell. We were previously checking for
11109 replays on the entire cell, but those can be circumvented due to
11110 the malleability of Tor's legacy hybrid encryption. This fix helps
11111 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11112 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11115 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11116 - Fix a use-after-free error that could crash v2 Tor onion services
11117 when they failed to open circuits while expiring introduction
11118 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11119 also tracked as TROVE-2017-013 and CVE-2017-8823.
11121 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11122 - When running as a relay, make sure that we never build a path
11123 through ourselves, even in the case where we have somehow lost the
11124 version of our descriptor appearing in the consensus. Fixes part
11125 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11126 as TROVE-2017-012 and CVE-2017-8822.
11127 - When running as a relay, make sure that we never choose ourselves
11128 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
11129 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
11131 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
11132 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11133 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11134 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11135 identifying and finding a workaround to this bug and to Moritz,
11136 Arthur Edelstein, and Roger for helping to track it down and
11139 o Minor features (security, windows, backport from 0.3.1.1-alpha):
11140 - Enable a couple of pieces of Windows hardening: one
11141 (HeapEnableTerminationOnCorruption) that has been on-by-default
11142 since Windows 8, and unavailable before Windows 7; and one
11143 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11144 affect us, but shouldn't do any harm. Closes ticket 21953.
11146 o Minor features (bridge, backport from 0.3.1.9):
11147 - Bridges now include notice in their descriptors that they are
11148 bridges, and notice of their distribution status, based on their
11149 publication settings. Implements ticket 18329. For more fine-
11150 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11153 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11154 - Add an IPv6 address for the "bastet" directory authority. Closes
11157 o Minor features (geoip):
11158 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11161 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
11162 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11163 relays, to prevent spurious address resolutions and descriptor
11164 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11165 bugfix on in 0.2.8.1-alpha.
11167 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
11168 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
11169 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11171 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
11172 - When a circuit is marked for close, do not attempt to package any
11173 cells for channels on that circuit. Previously, we would detect
11174 this condition lower in the call stack, when we noticed that the
11175 circuit had no attached channel, and log an annoying message.
11176 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11178 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
11179 - Avoid a crash when transitioning from client mode to bridge mode.
11180 Previously, we would launch the worker threads whenever our
11181 "public server" mode changed, but not when our "server" mode
11182 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11184 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
11185 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11186 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11189 Changes in version 0.2.9.14 - 2017-12-01
11190 Tor 0.3.0.13 backports important security and stability bugfixes from
11191 later Tor releases. All Tor users should upgrade to this release, or
11192 to another of the releases coming out today.
11194 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
11195 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11196 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11197 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11198 identifying and finding a workaround to this bug and to Moritz,
11199 Arthur Edelstein, and Roger for helping to track it down and
11202 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11203 - Fix a denial of service bug where an attacker could use a
11204 malformed directory object to cause a Tor instance to pause while
11205 OpenSSL would try to read a passphrase from the terminal. (Tor
11206 instances run without a terminal, which is the case for most Tor
11207 packages, are not impacted.) Fixes bug 24246; bugfix on every
11208 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11209 Found by OSS-Fuzz as testcase 6360145429790720.
11210 - Fix a denial of service issue where an attacker could crash a
11211 directory authority using a malformed router descriptor. Fixes bug
11212 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11214 - When checking for replays in the INTRODUCE1 cell data for a
11215 (legacy) onion service, correctly detect replays in the RSA-
11216 encrypted part of the cell. We were previously checking for
11217 replays on the entire cell, but those can be circumvented due to
11218 the malleability of Tor's legacy hybrid encryption. This fix helps
11219 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11220 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11223 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11224 - Fix a use-after-free error that could crash v2 Tor onion services
11225 when they failed to open circuits while expiring introduction
11226 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11227 also tracked as TROVE-2017-013 and CVE-2017-8823.
11229 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11230 - When running as a relay, make sure that we never build a path
11231 through ourselves, even in the case where we have somehow lost the
11232 version of our descriptor appearing in the consensus. Fixes part
11233 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11234 as TROVE-2017-012 and CVE-2017-8822.
11236 o Minor features (bridge, backport from 0.3.1.9):
11237 - Bridges now include notice in their descriptors that they are
11238 bridges, and notice of their distribution status, based on their
11239 publication settings. Implements ticket 18329. For more fine-
11240 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11243 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11244 - Add an IPv6 address for the "bastet" directory authority. Closes
11247 o Minor features (geoip):
11248 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11251 o Minor features (security, windows, backport from 0.3.1.1-alpha):
11252 - Enable a couple of pieces of Windows hardening: one
11253 (HeapEnableTerminationOnCorruption) that has been on-by-default
11254 since Windows 8, and unavailable before Windows 7; and one
11255 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11256 affect us, but shouldn't do any harm. Closes ticket 21953.
11258 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
11259 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11260 relays, to prevent spurious address resolutions and descriptor
11261 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11262 bugfix on in 0.2.8.1-alpha.
11264 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
11265 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
11266 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11268 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
11269 - When a circuit is marked for close, do not attempt to package any
11270 cells for channels on that circuit. Previously, we would detect
11271 this condition lower in the call stack, when we noticed that the
11272 circuit had no attached channel, and log an annoying message.
11273 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11275 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
11276 - Avoid a crash when transitioning from client mode to bridge mode.
11277 Previously, we would launch the worker threads whenever our
11278 "public server" mode changed, but not when our "server" mode
11279 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11281 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
11282 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11283 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11286 Changes in version 0.2.8.17 - 2017-12-01
11287 Tor 0.2.8.17 backports important security and stability bugfixes from
11288 later Tor releases. All Tor users should upgrade to this release, or
11289 to another of the releases coming out today.
11291 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
11292 2018. If you need a release with long-term support, please upgrade with
11293 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11295 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11296 - Fix a denial of service bug where an attacker could use a
11297 malformed directory object to cause a Tor instance to pause while
11298 OpenSSL would try to read a passphrase from the terminal. (Tor
11299 instances run without a terminal, which is the case for most Tor
11300 packages, are not impacted.) Fixes bug 24246; bugfix on every
11301 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11302 Found by OSS-Fuzz as testcase 6360145429790720.
11303 - When checking for replays in the INTRODUCE1 cell data for a
11304 (legacy) onion service, correctly detect replays in the RSA-
11305 encrypted part of the cell. We were previously checking for
11306 replays on the entire cell, but those can be circumvented due to
11307 the malleability of Tor's legacy hybrid encryption. This fix helps
11308 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11309 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11312 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11313 - Fix a use-after-free error that could crash v2 Tor onion services
11314 when they failed to open circuits while expiring introduction
11315 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11316 also tracked as TROVE-2017-013 and CVE-2017-8823.
11318 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11319 - When running as a relay, make sure that we never build a path through
11320 ourselves, even in the case where we have somehow lost the version of
11321 our descriptor appearing in the consensus. Fixes part of bug 21534;
11322 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
11325 o Minor features (bridge, backport from 0.3.1.9):
11326 - Bridges now include notice in their descriptors that they are
11327 bridges, and notice of their distribution status, based on their
11328 publication settings. Implements ticket 18329. For more fine-
11329 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11332 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11333 - Add an IPv6 address for the "bastet" directory authority. Closes
11336 o Minor features (geoip):
11337 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11340 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
11341 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11342 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11345 Changes in version 0.2.5.16 - 2017-12-01
11346 Tor 0.2.5.13 backports important security and stability bugfixes from
11347 later Tor releases. All Tor users should upgrade to this release, or
11348 to another of the releases coming out today.
11350 Note: the Tor 0.2.5 series will no longer be supported after 1 May
11351 2018. If you need a release with long-term support, please upgrade to
11352 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11354 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11355 - Fix a denial of service bug where an attacker could use a
11356 malformed directory object to cause a Tor instance to pause while
11357 OpenSSL would try to read a passphrase from the terminal. (Tor
11358 instances run without a terminal, which is the case for most Tor
11359 packages, are not impacted.) Fixes bug 24246; bugfix on every
11360 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11361 Found by OSS-Fuzz as testcase 6360145429790720.
11362 - When checking for replays in the INTRODUCE1 cell data for a
11363 (legacy) onion service, correctly detect replays in the RSA-
11364 encrypted part of the cell. We were previously checking for
11365 replays on the entire cell, but those can be circumvented due to
11366 the malleability of Tor's legacy hybrid encryption. This fix helps
11367 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11368 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11371 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11372 - When running as a relay, make sure that we never build a path
11373 through ourselves, even in the case where we have somehow lost the
11374 version of our descriptor appearing in the consensus. Fixes part
11375 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11376 as TROVE-2017-012 and CVE-2017-8822.
11378 o Minor features (bridge, backport from 0.3.1.9):
11379 - Bridges now include notice in their descriptors that they are
11380 bridges, and notice of their distribution status, based on their
11381 publication settings. Implements ticket 18329. For more fine-
11382 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11385 o Minor features (geoip):
11386 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11390 Changes in version 0.3.2.5-alpha - 2017-11-22
11391 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
11392 fixes several stability and reliability bugs, including a fix for
11393 intermittent bootstrapping failures that some people have been seeing
11394 since the 0.3.0.x series.
11396 Please test this alpha out -- many of these fixes will soon be
11397 backported to stable Tor versions if no additional bugs are found
11400 o Major bugfixes (bootstrapping):
11401 - Fetch descriptors aggressively whenever we lack enough to build
11402 circuits, regardless of how many descriptors we are missing.
11403 Previously, we would delay launching the fetch when we had fewer
11404 than 15 missing descriptors, even if some of those descriptors
11405 were blocking circuits from building. Fixes bug 23985; bugfix on
11406 0.1.1.11-alpha. The effects of this bug became worse in
11407 0.3.0.3-alpha, when we began treating missing descriptors from our
11408 primary guards as a reason to delay circuits.
11409 - Don't try fetching microdescriptors from relays that have failed
11410 to deliver them in the past. Fixes bug 23817; bugfix
11413 o Minor features (directory authority):
11414 - Make the "Exit" flag assignment only depend on whether the exit
11415 policy allows connections to ports 80 and 443. Previously relays
11416 would get the Exit flag if they allowed connections to one of
11417 these ports and also port 6667. Resolves ticket 23637.
11419 o Minor features (geoip):
11420 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11423 o Minor features (linux seccomp2 sandbox):
11424 - Update the sandbox rules so that they should now work correctly
11425 with Glibc 2.26. Closes ticket 24315.
11427 o Minor features (logging):
11428 - Downgrade a pair of log messages that could occur when an exit's
11429 resolver gave us an unusual (but not forbidden) response. Closes
11431 - Improve the message we log when re-enabling circuit build timeouts
11432 after having received a consensus. Closes ticket 20963.
11434 o Minor bugfixes (compilation):
11435 - Fix a memory leak warning in one of the libevent-related
11436 configuration tests that could occur when manually specifying
11437 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
11438 Found and patched by Alex Xu.
11439 - When detecting OpenSSL on Windows from our configure script, make
11440 sure to try linking with the ws2_32 library. Fixes bug 23783;
11441 bugfix on 0.3.2.2-alpha.
11443 o Minor bugfixes (control port, linux seccomp2 sandbox):
11444 - Avoid a crash when attempting to use the seccomp2 sandbox together
11445 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
11448 o Minor bugfixes (control port, onion services):
11449 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
11450 HS_DESC event when a service is not able to upload a descriptor.
11451 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
11453 o Minor bugfixes (directory cache):
11454 - Recover better from empty or corrupt files in the consensus cache
11455 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
11456 - When a consensus diff calculation is only partially successful,
11457 only record the successful parts as having succeeded. Partial
11458 success can happen if (for example) one compression method fails
11459 but the others succeed. Previously we misrecorded all the
11460 calculations as having succeeded, which would later cause a
11461 nonfatal assertion failure. Fixes bug 24086; bugfix
11464 o Minor bugfixes (logging):
11465 - Only log once if we notice that KIST support is gone. Fixes bug
11466 24158; bugfix on 0.3.2.1-alpha.
11467 - Suppress a log notice when relay descriptors arrive. We already
11468 have a bootstrap progress for this so no need to log notice
11469 everytime tor receives relay descriptors. Microdescriptors behave
11470 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
11472 o Minor bugfixes (network layer):
11473 - When closing a connection via close_connection_immediately(), we
11474 mark it as "not blocked on bandwidth", to prevent later calls from
11475 trying to unblock it, and give it permission to read. This fixes a
11476 backtrace warning that can happen on relays under various
11477 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
11479 o Minor bugfixes (onion services):
11480 - The introduction circuit was being timed out too quickly while
11481 waiting for the rendezvous circuit to complete. Keep the intro
11482 circuit around longer instead of timing out and reopening new ones
11483 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
11484 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
11485 so it matches dir-spec.txt. Fixes bug 24262; bugfix
11487 - Silence a warning about failed v3 onion descriptor uploads that
11488 can happen naturally under certain edge cases. Fixes part of bug
11489 23662; bugfix on 0.3.2.1-alpha.
11491 o Minor bugfixes (tests):
11492 - Fix a memory leak in one of the bridge-distribution test cases.
11493 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
11494 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
11495 to correctly handle cases where a caller gives it an RSA key of
11496 under 160 bits. (This is not actually a bug in Tor itself, but
11497 rather in our fuzzing code.) Fixes bug 24247; bugfix on
11498 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
11501 - Add notes in man page regarding OS support for the various
11502 scheduler types. Attempt to use less jargon in the scheduler
11503 section. Closes ticket 24254.
11506 Changes in version 0.3.2.4-alpha - 2017-11-08
11507 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
11508 It fixes several stability and reliability bugs, especially including
11509 a major reliability issue that has been plaguing fast exit relays in
11512 o Major bugfixes (exit relays, DNS):
11513 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11514 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11515 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11516 identifying and finding a workaround to this bug and to Moritz,
11517 Arthur Edelstein, and Roger for helping to track it down and
11520 o Major bugfixes (scheduler, channel):
11521 - Stop processing scheduled channels if they closed while flushing
11522 cells. This can happen if the write on the connection fails
11523 leading to the channel being closed while in the scheduler loop.
11524 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
11526 o Minor features (logging, scheduler):
11527 - Introduce a SCHED_BUG() function to log extra information about
11528 the scheduler state if we ever catch a bug in the scheduler.
11529 Closes ticket 23753.
11531 o Minor features (removed deprecations):
11532 - The ClientDNSRejectInternalAddresses flag can once again be set in
11533 non-testing Tor networks, so long as they do not use the default
11534 directory authorities. This change also removes the deprecation of
11535 this flag from 0.2.9.2-alpha. Closes ticket 21031.
11537 o Minor features (testing):
11538 - Our fuzzing tests now test the encrypted portions of v3 onion
11539 service descriptors. Implements more of 21509.
11541 o Minor bugfixes (directory client):
11542 - On failure to download directory information, delay retry attempts
11543 by a random amount based on the "decorrelated jitter" algorithm.
11544 Our previous delay algorithm tended to produce extra-long delays
11545 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
11547 o Minor bugfixes (IPv6, v3 single onion services):
11548 - Remove buggy code for IPv6-only v3 single onion services, and
11549 reject attempts to configure them. This release supports IPv4,
11550 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
11551 stack v3 single onion services. Fixes bug 23820; bugfix
11554 o Minor bugfixes (logging, relay):
11555 - Give only a protocol warning when the ed25519 key is not
11556 consistent between the descriptor and microdescriptor of a relay.
11557 This can happen, for instance, if the relay has been flagged
11558 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
11560 o Minor bugfixes (manpage, onion service):
11561 - Document that the HiddenServiceNumIntroductionPoints option is
11562 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
11563 bugfix on 0.3.2.1-alpha.
11565 o Minor bugfixes (memory leaks):
11566 - Fix a minor memory leak at exit in the KIST scheduler. This bug
11567 should have no user-visible impact. Fixes bug 23774; bugfix
11569 - Fix a memory leak when decrypting a badly formatted v3 onion
11570 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
11571 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
11573 o Minor bugfixes (onion services):
11574 - Cache some needed onion service client information instead of
11575 constantly computing it over and over again. Fixes bug 23623;
11576 bugfix on 0.3.2.1-alpha.
11577 - Properly retry HSv3 descriptor fetches when missing required
11578 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
11580 o Minor bugfixes (path selection):
11581 - When selecting relays by bandwidth, avoid a rounding error that
11582 could sometimes cause load to be imbalanced incorrectly.
11583 Previously, we would always round upwards; now, we round towards
11584 the nearest integer. This had the biggest effect when a relay's
11585 weight adjustments should have given it weight 0, but it got
11586 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
11587 - When calculating the fraction of nodes that have descriptors, and
11588 all nodes in the network have zero bandwidths, count the number of
11589 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
11590 - Actually log the total bandwidth in compute_weighted_bandwidths().
11591 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
11593 o Minor bugfixes (relay, crash):
11594 - Avoid a crash when transitioning from client mode to bridge mode.
11595 Previously, we would launch the worker threads whenever our
11596 "public server" mode changed, but not when our "server" mode
11597 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11599 o Minor bugfixes (testing):
11600 - Fix a spurious fuzzing-only use of an uninitialized value. Found
11601 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
11602 - Test that IPv6-only clients can use microdescriptors when running
11603 "make test-network-all". Requires chutney master 61c28b9 or later.
11604 Closes ticket 24109.
11607 Changes in version 0.3.2.3-alpha - 2017-10-27
11608 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
11609 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
11610 directory authority, Bastet.
11612 o Directory authority changes:
11613 - Add "Bastet" as a ninth directory authority to the default list.
11614 Closes ticket 23910.
11615 - The directory authority "Longclaw" has changed its IP address.
11616 Closes ticket 23592.
11618 o Minor features (bridge):
11619 - Bridge relays can now set the BridgeDistribution config option to
11620 add a "bridge-distribution-request" line to their bridge
11621 descriptor, which tells BridgeDB how they'd like their bridge
11622 address to be given out. (Note that as of Oct 2017, BridgeDB does
11623 not yet implement this feature.) As a side benefit, this feature
11624 provides a way to distinguish bridge descriptors from non-bridge
11625 descriptors. Implements tickets 18329.
11627 o Minor features (client, entry guards):
11628 - Improve log messages when missing descriptors for primary guards.
11629 Resolves ticket 23670.
11631 o Minor features (geoip):
11632 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11635 o Minor bugfixes (bridge):
11636 - Overwrite the bridge address earlier in the process of retrieving
11637 its descriptor, to make sure we reach it on the configured
11638 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
11640 o Minor bugfixes (documentation):
11641 - Document better how to read gcov, and what our gcov postprocessing
11642 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
11644 o Minor bugfixes (entry guards):
11645 - Tor now updates its guard state when it reads a consensus
11646 regardless of whether it's missing descriptors. That makes tor use
11647 its primary guards to fetch descriptors in some edge cases where
11648 it would previously have used fallback directories. Fixes bug
11649 23862; bugfix on 0.3.0.1-alpha.
11651 o Minor bugfixes (hidden service client):
11652 - When handling multiple SOCKS request for the same .onion address,
11653 only fetch the service descriptor once.
11654 - When a descriptor fetch fails with a non-recoverable error, close
11655 all pending SOCKS requests for that .onion. Fixes bug 23653;
11656 bugfix on 0.3.2.1-alpha.
11658 o Minor bugfixes (hidden service):
11659 - Always regenerate missing hidden service public key files. Prior
11660 to this, if the public key was deleted from disk, it wouldn't get
11661 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
11663 - Make sure that we have a usable ed25519 key when the intro point
11664 relay supports ed25519 link authentication. Fixes bug 24002;
11665 bugfix on 0.3.2.1-alpha.
11667 o Minor bugfixes (hidden service, v2):
11668 - When reloading configured hidden services, copy all information
11669 from the old service object. Previously, some data was omitted,
11670 causing delays in descriptor upload, and other bugs. Fixes bug
11671 23790; bugfix on 0.2.1.9-alpha.
11673 o Minor bugfixes (memory safety, defensive programming):
11674 - Clear the target address when node_get_prim_orport() returns
11675 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11677 o Minor bugfixes (relay):
11678 - Avoid a BUG warning when receiving a dubious CREATE cell while an
11679 option transition is in progress. Fixes bug 23952; bugfix
11682 o Minor bugfixes (testing):
11683 - Adjust the GitLab CI configuration to more closely match that of
11684 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
11685 - Prevent scripts/test/coverage from attempting to move gcov output
11686 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
11687 - When running unit tests as root, skip a test that would fail
11688 because it expects a permissions error. This affects some
11689 continuous integration setups. Fixes bug 23758; bugfix
11691 - Stop unconditionally mirroring the tor repository in GitLab CI.
11692 This prevented developers from enabling GitLab CI on master. Fixes
11693 bug 23755; bugfix on 0.3.2.2-alpha.
11694 - Fix the hidden service v3 descriptor decoding fuzzing to use the
11695 latest decoding API correctly. Fixes bug 21509; bugfix
11698 o Minor bugfixes (warnings):
11699 - When we get an HTTP request on a SOCKS port, tell the user about
11700 the new HTTPTunnelPort option. Previously, we would give a "Tor is
11701 not an HTTP Proxy" message, which stopped being true when
11702 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
11706 Changes in version 0.2.5.15 - 2017-10-25
11707 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
11708 series. It also adds a new directory authority, Bastet.
11710 Note: the Tor 0.2.5 series will no longer be supported after 1 May
11711 2018. If you need a release with long-term support, please upgrade to
11712 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11714 o Directory authority changes:
11715 - Add "Bastet" as a ninth directory authority to the default list.
11716 Closes ticket 23910.
11717 - The directory authority "Longclaw" has changed its IP address.
11718 Closes ticket 23592.
11720 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11721 - Avoid an assertion failure bug affecting our implementation of
11722 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11723 handling of "0xx" differs from what we had expected. Fixes bug
11724 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11726 o Minor features (geoip):
11727 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11730 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
11731 - Fix a memset() off the end of an array when packing cells. This
11732 bug should be harmless in practice, since the corrupted bytes are
11733 still in the same structure, and are always padding bytes,
11734 ignored, or immediately overwritten, depending on compiler
11735 behavior. Nevertheless, because the memset()'s purpose is to make
11736 sure that any other cell-handling bugs can't expose bytes to the
11737 network, we need to fix it. Fixes bug 22737; bugfix on
11738 0.2.4.11-alpha. Fixes CID 1401591.
11740 o Build features (backport from 0.3.1.5-alpha):
11741 - Tor's repository now includes a Travis Continuous Integration (CI)
11742 configuration file (.travis.yml). This is meant to help new
11743 developers and contributors who fork Tor to a Github repository be
11744 better able to test their changes, and understand what we expect
11745 to pass. To use this new build feature, you must fork Tor to your
11746 Github account, then go into the "Integrations" menu in the
11747 repository settings for your fork and enable Travis, then push
11748 your changes. Closes ticket 22636.
11751 Changes in version 0.2.8.16 - 2017-10-25
11752 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
11753 series, including a bugfix for a crash issue that had affected relays
11754 under memory pressure. It also adds a new directory authority, Bastet.
11756 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
11757 2018. If you need a release with long-term support, please stick with
11758 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11760 o Directory authority changes:
11761 - Add "Bastet" as a ninth directory authority to the default list.
11762 Closes ticket 23910.
11763 - The directory authority "Longclaw" has changed its IP address.
11764 Closes ticket 23592.
11766 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11767 - Fix a timing-based assertion failure that could occur when the
11768 circuit out-of-memory handler freed a connection's output buffer.
11769 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11771 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11772 - Remove longclaw's IPv6 address, as it will soon change. Authority
11773 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11774 3/8 directory authorities with IPv6 addresses, but there are also
11775 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11777 o Minor features (geoip):
11778 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11782 Changes in version 0.2.9.13 - 2017-10-25
11783 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
11784 series, including a bugfix for a crash issue that had affected relays
11785 under memory pressure. It also adds a new directory authority, Bastet.
11787 o Directory authority changes:
11788 - Add "Bastet" as a ninth directory authority to the default list.
11789 Closes ticket 23910.
11790 - The directory authority "Longclaw" has changed its IP address.
11791 Closes ticket 23592.
11793 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11794 - Fix a timing-based assertion failure that could occur when the
11795 circuit out-of-memory handler freed a connection's output buffer.
11796 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11798 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11799 - Remove longclaw's IPv6 address, as it will soon change. Authority
11800 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11801 3/8 directory authorities with IPv6 addresses, but there are also
11802 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11804 o Minor features (geoip):
11805 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11808 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
11809 - When a directory authority rejects a descriptor or extrainfo with
11810 a given digest, mark that digest as undownloadable, so that we do
11811 not attempt to download it again over and over. We previously
11812 tried to avoid downloading such descriptors by other means, but we
11813 didn't notice if we accidentally downloaded one anyway. This
11814 behavior became problematic in 0.2.7.2-alpha, when authorities
11815 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11818 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
11819 - Clear the address when node_get_prim_orport() returns early.
11820 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11822 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
11823 - When running as a Windows service, set the ID of the main thread
11824 correctly. Failure to do so made us fail to send log messages to
11825 the controller in 0.2.1.16-rc, slowed down controller event
11826 delivery in 0.2.7.3-rc and later, and crash with an assertion
11827 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11828 Patch and diagnosis from "Vort".
11831 Changes in version 0.3.0.12 - 2017-10-25
11832 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
11833 series, including a bugfix for a crash issue that had affected relays
11834 under memory pressure. It also adds a new directory authority, Bastet.
11836 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
11837 2018. If you need a release with long-term support, please stick with
11838 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11840 o Directory authority changes:
11841 - Add "Bastet" as a ninth directory authority to the default list.
11842 Closes ticket 23910.
11843 - The directory authority "Longclaw" has changed its IP address.
11844 Closes ticket 23592.
11846 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11847 - Fix a timing-based assertion failure that could occur when the
11848 circuit out-of-memory handler freed a connection's output buffer.
11849 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11851 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11852 - Remove longclaw's IPv6 address, as it will soon change. Authority
11853 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11854 3/8 directory authorities with IPv6 addresses, but there are also
11855 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11857 o Minor features (geoip):
11858 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11861 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
11862 - When a directory authority rejects a descriptor or extrainfo with
11863 a given digest, mark that digest as undownloadable, so that we do
11864 not attempt to download it again over and over. We previously
11865 tried to avoid downloading such descriptors by other means, but we
11866 didn't notice if we accidentally downloaded one anyway. This
11867 behavior became problematic in 0.2.7.2-alpha, when authorities
11868 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11871 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
11872 - Avoid a possible double close of a circuit by the intro point on
11873 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
11874 bugfix on 0.3.0.1-alpha.
11876 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
11877 - Clear the address when node_get_prim_orport() returns early.
11878 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11880 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
11881 - When running as a Windows service, set the ID of the main thread
11882 correctly. Failure to do so made us fail to send log messages to
11883 the controller in 0.2.1.16-rc, slowed down controller event
11884 delivery in 0.2.7.3-rc and later, and crash with an assertion
11885 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11886 Patch and diagnosis from "Vort".
11889 Changes in version 0.3.1.8 - 2017-10-25
11890 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
11891 It includes several bugfixes, including a bugfix for a crash issue
11892 that had affected relays under memory pressure. It also adds
11893 a new directory authority, Bastet.
11895 o Directory authority changes:
11896 - Add "Bastet" as a ninth directory authority to the default list.
11897 Closes ticket 23910.
11898 - The directory authority "Longclaw" has changed its IP address.
11899 Closes ticket 23592.
11901 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11902 - Fix a timing-based assertion failure that could occur when the
11903 circuit out-of-memory handler freed a connection's output buffer.
11904 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11906 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11907 - Remove longclaw's IPv6 address, as it will soon change. Authority
11908 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11909 3/8 directory authorities with IPv6 addresses, but there are also
11910 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11912 o Minor features (geoip):
11913 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11916 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
11917 - Fix a compilation warning when building with zstd support on
11918 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
11919 and fixed by Andreas Stieger.
11921 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
11922 - Handle a pathological case when decompressing Zstandard data when
11923 the output buffer size is zero. Fixes bug 23551; bugfix
11926 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
11927 - Remove the length limit on HTTP status lines that authorities can
11928 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
11930 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
11931 - Avoid a possible double close of a circuit by the intro point on
11932 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
11933 bugfix on 0.3.0.1-alpha.
11935 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
11936 - Clear the address when node_get_prim_orport() returns early.
11937 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11939 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
11940 - Fix additional channelpadding unit test failures by using mocked
11941 time instead of actual time for all tests. Fixes bug 23608; bugfix
11945 Changes in version 0.3.2.2-alpha - 2017-09-29
11946 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
11947 release fixes several minor bugs in the new scheduler and next-
11948 generation onion services; both features were newly added in the 0.3.2
11949 series. Other fixes in this alpha include several fixes for non-fatal
11950 tracebacks which would appear in logs.
11952 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
11953 alpha does not contain any substantial new features. Minor features
11954 include better testing and logging.
11956 The following comprises the complete list of changes included
11959 o Major bugfixes (relay, crash, assertion failure):
11960 - Fix a timing-based assertion failure that could occur when the
11961 circuit out-of-memory handler freed a connection's output buffer.
11962 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11964 o Major bugfixes (scheduler):
11965 - If a channel is put into the scheduler's pending list, then it
11966 starts closing, and then if the scheduler runs before it finishes
11967 closing, the scheduler will get stuck trying to flush its cells
11968 while the lower layers refuse to cooperate. Fix that race
11969 condition by giving the scheduler an escape method. Fixes bug
11970 23676; bugfix on 0.3.2.1-alpha.
11972 o Minor features (build, compilation):
11973 - The "check-changes" feature is now part of the "make check" tests;
11974 we'll use it to try to prevent misformed changes files from
11975 accumulating. Closes ticket 23564.
11976 - Tor builds should now fail if there are any mismatches between the
11977 C type representing a configuration variable and the C type the
11978 data-driven parser uses to store a value there. Previously, we
11979 needed to check these by hand, which sometimes led to mistakes.
11980 Closes ticket 23643.
11982 o Minor features (directory authorities):
11983 - Remove longclaw's IPv6 address, as it will soon change. Authority
11984 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11985 3/8 directory authorities with IPv6 addresses, but there are also
11986 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11988 o Minor features (hidden service, circuit, logging):
11989 - Improve logging of many callsite in the circuit subsystem to print
11990 the circuit identifier(s).
11991 - Log when we cleanup an intro point from a service so we know when
11992 and for what reason it happened. Closes ticket 23604.
11994 o Minor features (logging):
11995 - Log more circuit information whenever we are about to try to
11996 package a relay cell on a circuit with a nonexistent n_chan.
11997 Attempt to diagnose ticket 8185.
11998 - Improve info-level log identification of particular circuits, to
11999 help with debugging. Closes ticket 23645.
12001 o Minor features (relay):
12002 - When choosing which circuits can be expired as unused, consider
12003 circuits from clients even if those clients used regular CREATE
12004 cells to make them; and do not consider circuits from relays even
12005 if they were made with CREATE_FAST. Part of ticket 22805.
12007 o Minor features (robustness):
12008 - Change several fatal assertions when flushing buffers into non-
12009 fatal assertions, to prevent any recurrence of 23690.
12011 o Minor features (spec conformance, bridge, diagnostic):
12012 - When handling the USERADDR command on an ExtOrPort, warn when the
12013 transports provides a USERADDR with no port. In a future version,
12014 USERADDR commands of this format may be rejected. Detects problems
12015 related to ticket 23080.
12017 o Minor features (testing):
12018 - Add a unit test to make sure that our own generated platform
12019 string will be accepted by directory authorities. Closes
12022 o Minor bugfixes (bootstrapping):
12023 - When warning about state file clock skew, report the correct
12024 direction for the detected skew. Fixes bug 23606; bugfix
12026 - Avoid an assertion failure when logging a state file clock skew
12027 very early in bootstrapping. Fixes bug 23607; bugfix
12030 o Minor bugfixes (build, compilation):
12031 - Fix a compilation warning when building with zstd support on
12032 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
12033 and fixed by Andreas Stieger.
12034 - When searching for OpenSSL, don't accept any OpenSSL library that
12035 lacks TLSv1_1_method(): Tor doesn't build with those versions.
12036 Additionally, look in /usr/local/opt/openssl, if it's present.
12037 These changes together repair the default build on OSX systems
12038 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
12040 o Minor bugfixes (compression):
12041 - Handle a pathological case when decompressing Zstandard data when
12042 the output buffer size is zero. Fixes bug 23551; bugfix
12045 o Minor bugfixes (documentation):
12046 - Fix manpage to not refer to the obsolete (and misspelled)
12047 UseEntryGuardsAsDirectoryGuards parameter in the description of
12048 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
12050 o Minor bugfixes (hidden service v3):
12051 - Don't log an assertion failure when we can't find the right
12052 information to extend to an introduction point. In rare cases,
12053 this could happen, causing a warning, even though tor would
12054 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
12055 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
12056 much bigger so the rendezvous point can't distinguish which hidden
12057 service protocol is being used. Fixes bug 23420; bugfix
12060 o Minor bugfixes (hidden service, relay):
12061 - Avoid a possible double close of a circuit by the intro point on
12062 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
12063 bugfix on 0.3.0.1-alpha.
12065 o Minor bugfixes (logging, relay shutdown, annoyance):
12066 - When a circuit is marked for close, do not attempt to package any
12067 cells for channels on that circuit. Previously, we would detect
12068 this condition lower in the call stack, when we noticed that the
12069 circuit had no attached channel, and log an annoying message.
12070 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
12072 o Minor bugfixes (scheduler):
12073 - When switching schedulers due to a consensus change, we didn't
12074 give the new scheduler a chance to react to the consensus. Fix
12075 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
12076 - Make the KISTSchedRunInterval option a non negative value. With
12077 this, the way to disable KIST through the consensus is to set it
12078 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
12079 - Only notice log the selected scheduler when we switch scheduler
12080 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
12081 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
12082 by a different tv_usec data type. Fixes bug 23575; bugfix
12084 - Make a hard exit if tor is unable to pick a scheduler which can
12085 happen if the user specifies a scheduler type that is not
12086 supported and not other types in Schedulers. Fixes bug 23581;
12087 bugfix on 0.3.2.1-alpha.
12088 - Properly initialize the scheduler last run time counter so it is
12089 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
12091 o Minor bugfixes (testing):
12092 - Capture and detect several "Result does not fit" warnings in unit
12093 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
12095 - Fix additional channelpadding unit test failures by using mocked
12096 time instead of actual time for all tests. Fixes bug 23608; bugfix
12098 - The removal of some old scheduler options caused some tests to
12099 fail on BSD systems. Assume current behavior is correct and make
12100 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
12102 o Code simplification and refactoring:
12103 - Remove various ways of testing circuits and connections for
12104 "clientness"; instead, favor channel_is_client(). Part of
12107 o Deprecated features:
12108 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
12109 now deprecated; they do not apply to relays, and they have had no
12110 effect on clients since 0.2.8.x. Closes ticket 19704.
12113 - HiddenServiceVersion man page entry wasn't mentioning the now
12114 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
12115 - Clarify that the Address option is entirely about setting an
12116 advertised IPv4 address. Closes ticket 18891.
12117 - Clarify the manpage's use of the term "address" to clarify what
12118 kind of address is intended. Closes ticket 21405.
12119 - Document that onion service subdomains are allowed, and ignored.
12120 Closes ticket 18736.
12123 Changes in version 0.3.2.1-alpha - 2017-09-18
12124 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
12125 includes support for our next-generation ("v3") onion service
12126 protocol, and adds a new circuit scheduler for more responsive
12127 forwarding decisions from relays. There are also numerous other small
12128 features and bugfixes here.
12130 Below are the changes since Tor 0.3.1.7.
12132 o Major feature (scheduler, channel):
12133 - Tor now uses new schedulers to decide which circuits should
12134 deliver cells first, in order to improve congestion at relays. The
12135 first type is called "KIST" ("Kernel Informed Socket Transport"),
12136 and is only available on Linux-like systems: it uses feedback from
12137 the kernel to prevent the kernel's TCP buffers from growing too
12138 full. The second new scheduler type is called "KISTLite": it
12139 behaves the same as KIST, but runs on systems without kernel
12140 support for inspecting TCP implementation details. The old
12141 scheduler is still available, under the name "Vanilla". To change
12142 the default scheduler preference order, use the new "Schedulers"
12143 option. (The default preference order is "KIST,KISTLite,Vanilla".)
12145 Matt Traudt implemented KIST, based on research by Rob Jansen,
12146 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
12147 more information, see the design paper at
12148 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
12149 followup implementation paper at https://arxiv.org/abs/1709.01044.
12150 Closes ticket 12541.
12152 o Major features (next-generation onion services):
12153 - Tor now supports the next-generation onion services protocol for
12154 clients and services! As part of this release, the core of
12155 proposal 224 has been implemented and is available for
12156 experimentation and testing by our users. This newer version of
12157 onion services ("v3") features many improvements over the legacy
12160 a) Better crypto (replaced SHA1/DH/RSA1024
12161 with SHA3/ed25519/curve25519)
12163 b) Improved directory protocol, leaking much less information to
12166 c) Improved directory protocol, with smaller surface for
12169 d) Better onion address security against impersonation.
12171 e) More extensible introduction/rendezvous protocol.
12173 f) A cleaner and more modular codebase.
12175 You can identify a next-generation onion address by its length:
12176 they are 56 characters long, as in
12177 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
12179 In the future, we will release more options and features for v3
12180 onion services, but we first need a testing period, so that the
12181 current codebase matures and becomes more robust. Planned features
12182 include: offline keys, advanced client authorization, improved
12183 guard algorithms, and statistics. For full details, see
12186 Legacy ("v2") onion services will still work for the foreseeable
12187 future, and will remain the default until this new codebase gets
12188 tested and hardened. Service operators who want to experiment with
12189 the new system can use the 'HiddenServiceVersion 3' torrc
12190 directive along with the regular onion service configuration
12191 options. We will publish a blog post about this new feature
12194 o Major bugfixes (usability, control port):
12195 - Report trusted clock skew indications as bootstrap errors, so
12196 controllers can more easily alert users when their clocks are
12197 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
12199 o Minor features (bug detection):
12200 - Log a warning message with a stack trace for any attempt to call
12201 get_options() during option validation. This pattern has caused
12202 subtle bugs in the past. Closes ticket 22281.
12204 o Minor features (client):
12205 - You can now use Tor as a tunneled HTTP proxy: use the new
12206 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
12207 requests. Closes ticket 22407.
12208 - Add an extra check to make sure that we always use the newer guard
12209 selection code for picking our guards. Closes ticket 22779.
12210 - When downloading (micro)descriptors, don't split the list into
12211 multiple requests unless we want at least 32 descriptors.
12212 Previously, we split at 4, not 32, which led to significant
12213 overhead in HTTP request size and degradation in compression
12214 performance. Closes ticket 23220.
12216 o Minor features (command line):
12217 - Add a new commandline option, --key-expiration, which prints when
12218 the current signing key is going to expire. Implements ticket
12219 17639; patch by Isis Lovecruft.
12221 o Minor features (control port):
12222 - If an application tries to use the control port as an HTTP proxy,
12223 respond with a meaningful "This is the Tor control port" message,
12224 and log the event. Closes ticket 1667. Patch from Ravi
12226 - Provide better error message for GETINFO desc/(id|name) when not
12227 fetching router descriptors. Closes ticket 5847. Patch by
12229 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
12230 whether Tor will try to download router descriptors and
12231 microdescriptors respectively. Closes ticket 22684.
12232 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
12233 so controllers can tell whether the geoip databases are loaded.
12234 Closes ticket 23237.
12235 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
12236 events. Closes ticket 19254. Patch by "DonnchaC".
12238 o Minor features (development support):
12239 - Developers can now generate a call-graph for Tor using the
12240 "calltool" python program, which post-processes object dumps. It
12241 should work okay on many Linux and OSX platforms, and might work
12242 elsewhere too. To run it, install calltool from
12243 https://gitweb.torproject.org/user/nickm/calltool.git and run
12244 "make callgraph". Closes ticket 19307.
12246 o Minor features (ed25519):
12247 - Add validation function to checks for torsion components in
12248 ed25519 public keys, used by prop224 client-side code. Closes
12249 ticket 22006. Math help by Ian Goldberg.
12251 o Minor features (exit relay, DNS):
12252 - Improve the clarity and safety of the log message from evdns when
12253 receiving an apparently spoofed DNS reply. Closes ticket 3056.
12255 o Minor features (integration, hardening):
12256 - Add a new NoExec option to prevent Tor from running other
12257 programs. When this option is set to 1, Tor will never try to run
12258 another program, regardless of the settings of
12259 PortForwardingHelper, ClientTransportPlugin, or
12260 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
12261 without restarting Tor. Closes ticket 22976.
12263 o Minor features (logging):
12264 - Improve the warning message for specifying a relay by nickname.
12265 The previous message implied that nickname registration was still
12266 part of the Tor network design, which it isn't. Closes
12268 - If the sandbox filter fails to load, suggest to the user that
12269 their kernel might not support seccomp2. Closes ticket 23090.
12271 o Minor features (portability):
12272 - Check at configure time whether uint8_t is the same type as
12273 unsigned char. Lots of existing code already makes this
12274 assumption, and there could be strict aliasing issues if the
12275 assumption is violated. Closes ticket 22410.
12277 o Minor features (relay, configuration):
12278 - Reject attempts to use relative file paths when RunAsDaemon is
12279 set. Previously, Tor would accept these, but the directory-
12280 changing step of RunAsDaemon would give strange and/or confusing
12281 results. Closes ticket 22731.
12283 o Minor features (startup, safety):
12284 - When configured to write a PID file, Tor now exits if it is unable
12285 to do so. Previously, it would warn and continue. Closes
12288 o Minor features (static analysis):
12289 - The BUG() macro has been changed slightly so that Coverity no
12290 longer complains about dead code if the bug is impossible. Closes
12293 o Minor features (testing):
12294 - The default chutney network tests now include tests for the v3
12295 hidden service design. Make sure you have the latest version of
12296 chutney if you want to run these. Closes ticket 22437.
12297 - Add a unit test to verify that we can parse a hardcoded v2 hidden
12298 service descriptor. Closes ticket 15554.
12300 o Minor bugfixes (certificate handling):
12301 - Fix a time handling bug in Tor certificates set to expire after
12302 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
12303 Coverity as CID 1415728.
12305 o Minor bugfixes (client, usability):
12306 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
12307 SOCKS4a requests that contain IP address strings, even when
12308 SafeSocks in enabled, as this prevents user from connecting to
12309 known IP addresses without relying on DNS for resolving. SafeSocks
12310 still rejects SOCKS connections that connect to IP addresses when
12311 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
12312 bugfix on Tor 0.2.6.2-alpha.
12314 o Minor bugfixes (code correctness):
12315 - Call htons() in extend_cell_format() for encoding a 16-bit value.
12316 Previously we used ntohs(), which happens to behave the same on
12317 all the platforms we support, but which isn't really correct.
12318 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
12319 - For defense-in-depth, make the controller's write_escaped_data()
12320 function robust to extremely long inputs. Fixes bug 19281; bugfix
12321 on 0.1.1.1-alpha. Reported by Guido Vranken.
12323 o Minor bugfixes (compilation):
12324 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
12325 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
12327 o Minor bugfixes (consensus expiry):
12328 - Check for adequate directory information correctly. Previously, Tor
12329 would reconsider whether it had sufficient directory information
12330 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
12332 o Minor bugfixes (directory protocol):
12333 - Directory servers now include a "Date:" http header for response
12334 codes other than 200. Clients starting with a skewed clock and a
12335 recent consensus were getting "304 Not modified" responses from
12336 directory authorities, so without the Date header, the client
12337 would never hear about a wrong clock. Fixes bug 23499; bugfix
12339 - Make clients wait for 6 seconds before trying to download a
12340 consensus from an authority. Fixes bug 17750; bugfix
12343 o Minor bugfixes (DoS-resistance):
12344 - If future code asks if there are any running bridges, without
12345 checking if bridges are enabled, log a BUG warning rather than
12346 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
12348 o Minor bugfixes (format strictness):
12349 - Restrict several data formats to decimal. Previously, the
12350 BuildTimeHistogram entries in the state file, the "bw=" entries in
12351 the bandwidth authority file, and the process IDs passed to the
12352 __OwningControllerProcess option could all be specified in hex or
12353 octal as well as in decimal. This was not an intentional feature.
12354 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
12357 o Minor bugfixes (heartbeat):
12358 - If we fail to write a heartbeat message, schedule a retry for the
12359 minimum heartbeat interval number of seconds in the future. Fixes
12360 bug 19476; bugfix on 0.2.3.1-alpha.
12362 o Minor bugfixes (linux seccomp2 sandbox, logging):
12363 - Fix some messages on unexpected errors from the seccomp2 library.
12364 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
12366 o Minor bugfixes (logging):
12367 - Remove duplicate log messages regarding opening non-local
12368 SocksPorts upon parsing config and opening listeners at startup.
12369 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
12370 - Use a more comprehensible log message when telling the user
12371 they've excluded every running exit node. Fixes bug 7890; bugfix
12373 - When logging the number of descriptors we intend to download per
12374 directory request, do not log a number higher than then the number
12375 of descriptors we're fetching in total. Fixes bug 19648; bugfix
12377 - When warning about a directory owned by the wrong user, log the
12378 actual name of the user owning the directory. Previously, we'd log
12379 the name of the process owner twice. Fixes bug 23487; bugfix
12381 - The tor specification says hop counts are 1-based, so fix two log
12382 messages that mistakenly logged 0-based hop counts. Fixes bug
12383 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
12384 Credit to Xiaofan Li for reporting this issue.
12386 o Minor bugfixes (portability):
12387 - Stop using the PATH_MAX variable, which is not defined on GNU
12388 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
12390 o Minor bugfixes (relay):
12391 - When uploading our descriptor for the first time after startup,
12392 report the reason for uploading as "Tor just started" rather than
12393 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
12394 - Avoid unnecessary calls to directory_fetches_from_authorities() on
12395 relays, to prevent spurious address resolutions and descriptor
12396 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
12397 bugfix on in 0.2.8.1-alpha.
12399 o Minor bugfixes (tests):
12400 - Fix a broken unit test for the OutboundAddress option: the parsing
12401 function was never returning an error on failure. Fixes bug 23366;
12402 bugfix on 0.3.0.3-alpha.
12403 - Fix a signed-integer overflow in the unit tests for
12404 dir/download_status_random_backoff, which was untriggered until we
12405 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
12407 o Minor bugfixes (usability, control port):
12408 - Stop making an unnecessary routerlist check in NETINFO clock skew
12409 detection; this was preventing clients from reporting NETINFO clock
12410 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
12412 o Code simplification and refactoring:
12413 - Extract the code for handling newly-open channels into a separate
12414 function from the general code to handle channel state
12415 transitions. This change simplifies our callgraph, reducing the
12416 size of the largest strongly connected component by roughly a
12417 factor of two. Closes ticket 22608.
12418 - Remove dead code for largely unused statistics on the number of
12419 times we've attempted various public key operations. Fixes bug
12420 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
12421 - Remove several now-obsolete functions for asking about old
12422 variants directory authority status. Closes ticket 22311; patch
12424 - Remove some of the code that once supported "Named" and "Unnamed"
12425 routers. Authorities no longer vote for these flags. Closes
12427 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
12428 and old hidden services, to indicate that they aren't suitable for
12429 new protocols or formats. Closes ticket 23026.
12430 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
12431 22521. Patch from Neel Chauhan.
12432 - Split the enormous circuit_send_next_onion_skin() function into
12433 multiple subfunctions. Closes ticket 22804.
12434 - Split the portions of the buffer.c module that handle particular
12435 protocols into separate modules. Part of ticket 23149.
12436 - Use our test macros more consistently, to produce more useful
12437 error messages when our unit tests fail. Add coccinelle patches to
12438 allow us to re-check for test macro uses. Closes ticket 22497.
12440 o Deprecated features:
12441 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
12442 only applies to direct unencrypted HTTP connections to your
12443 directory server, which your Tor probably isn't using. Closes
12447 - Clarify in the manual that "Sandbox 1" is only supported on Linux
12448 kernels. Closes ticket 22677.
12449 - Document all values of PublishServerDescriptor in the manpage.
12450 Closes ticket 15645.
12451 - Improve the documentation for the directory port part of the
12452 DirAuthority line. Closes ticket 20152.
12453 - Restore documentation for the authorities' "approved-routers"
12454 file. Closes ticket 21148.
12456 o Removed features:
12457 - The AllowDotExit option has been removed as unsafe. It has been
12458 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
12459 - The ClientDNSRejectInternalAddresses flag can no longer be set on
12460 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
12461 Closes ticket 21031.
12462 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
12463 nobody was using it any longer. Closes ticket 22377.
12466 Changes in version 0.2.8.15 - 2017-09-18
12467 Tor 0.2.8.15 backports a collection of bugfixes from later
12470 Most significantly, it includes a fix for TROVE-2017-008, a
12471 security bug that affects hidden services running with the
12472 SafeLogging option disabled. For more information, see
12473 https://trac.torproject.org/projects/tor/ticket/23490
12475 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
12476 2018. We suggest that you upgrade to the latest stable release if
12477 possible. If you can't, we recommend that you upgrade at least to
12478 0.2.9, which will be supported until 2020.
12480 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
12481 - Avoid an assertion failure bug affecting our implementation of
12482 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
12483 handling of "0xx" differs from what we had expected. Fixes bug
12484 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
12487 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
12490 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
12491 - Backport a fix for an "unused variable" warning that appeared
12492 in some versions of mingw. Fixes bug 22838; bugfix on
12495 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
12496 - Fix a memset() off the end of an array when packing cells. This
12497 bug should be harmless in practice, since the corrupted bytes are
12498 still in the same structure, and are always padding bytes,
12499 ignored, or immediately overwritten, depending on compiler
12500 behavior. Nevertheless, because the memset()'s purpose is to make
12501 sure that any other cell-handling bugs can't expose bytes to the
12502 network, we need to fix it. Fixes bug 22737; bugfix on
12503 0.2.4.11-alpha. Fixes CID 1401591.
12505 o Build features (backport from 0.3.1.5-alpha):
12506 - Tor's repository now includes a Travis Continuous Integration (CI)
12507 configuration file (.travis.yml). This is meant to help new
12508 developers and contributors who fork Tor to a Github repository be
12509 better able to test their changes, and understand what we expect
12510 to pass. To use this new build feature, you must fork Tor to your
12511 Github account, then go into the "Integrations" menu in the
12512 repository settings for your fork and enable Travis, then push
12513 your changes. Closes ticket 22636.
12516 Changes in version 0.2.9.12 - 2017-09-18
12517 Tor 0.2.9.12 backports a collection of bugfixes from later
12520 Most significantly, it includes a fix for TROVE-2017-008, a
12521 security bug that affects hidden services running with the
12522 SafeLogging option disabled. For more information, see
12523 https://trac.torproject.org/projects/tor/ticket/23490
12525 o Major features (security, backport from 0.3.0.2-alpha):
12526 - Change the algorithm used to decide DNS TTLs on client and server
12527 side, to better resist DNS-based correlation attacks like the
12528 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
12529 Feamster. Now relays only return one of two possible DNS TTL
12530 values, and clients are willing to believe DNS TTL values up to 3
12531 hours long. Closes ticket 19769.
12533 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
12534 - Fix a rare crash when sending a begin cell on a circuit whose
12535 linked directory connection had already been closed. Fixes bug
12536 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
12538 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
12539 - Fix a bug that prevented exit nodes from caching DNS records for
12540 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
12542 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
12543 - Fix a typo that had prevented TPROXY-based transparent proxying
12544 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
12545 Patch from "d4fq0fQAgoJ".
12547 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
12548 - Avoid an assertion failure bug affecting our implementation of
12549 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
12550 handling of "0xx" differs from what we had expected. Fixes bug
12551 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
12553 o Minor features (code style, backport from 0.3.1.3-alpha):
12554 - Add "Falls through" comments to our codebase, in order to silence
12555 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
12556 Stieger. Closes ticket 22446.
12558 o Minor features (geoip):
12559 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
12562 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
12563 - Roll over monthly accounting at the configured hour and minute,
12564 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
12565 Found by Andrey Karpov with PVS-Studio.
12567 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
12568 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
12569 bugfix on 0.2.8.1-alpha.
12570 - Fix warnings when building with libscrypt and openssl scrypt support
12571 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
12572 - When building with certain versions the mingw C header files, avoid
12573 float-conversion warnings when calling the C functions isfinite(),
12574 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
12576 o Minor bugfixes (compilation, backport from 0.3.1.7):
12577 - Avoid compiler warnings in the unit tests for running tor_sscanf()
12578 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
12580 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
12581 - Backport a fix for an "unused variable" warning that appeared
12582 in some versions of mingw. Fixes bug 22838; bugfix on
12585 o Minor bugfixes (controller, backport from 0.3.1.7):
12586 - Do not crash when receiving a HSPOST command with an empty body.
12587 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
12588 - Do not crash when receiving a POSTDESCRIPTOR command with an
12589 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
12591 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
12592 - Avoid Coverity build warnings related to our BUG() macro. By
12593 default, Coverity treats BUG() as the Linux kernel does: an
12594 instant abort(). We need to override that so our BUG() macro
12595 doesn't prevent Coverity from analyzing functions that use it.
12596 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
12598 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
12599 - Fix a memset() off the end of an array when packing cells. This
12600 bug should be harmless in practice, since the corrupted bytes are
12601 still in the same structure, and are always padding bytes,
12602 ignored, or immediately overwritten, depending on compiler
12603 behavior. Nevertheless, because the memset()'s purpose is to make
12604 sure that any other cell-handling bugs can't expose bytes to the
12605 network, we need to fix it. Fixes bug 22737; bugfix on
12606 0.2.4.11-alpha. Fixes CID 1401591.
12608 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
12609 - When setting the maximum number of connections allowed by the OS,
12610 always allow some extra file descriptors for other files. Fixes
12611 bug 22797; bugfix on 0.2.0.10-alpha.
12613 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
12614 - Avoid a sandbox failure when trying to re-bind to a socket and
12615 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
12617 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
12618 - Permit the fchmod system call, to avoid crashing on startup when
12619 starting with the seccomp2 sandbox and an unexpected set of
12620 permissions on the data directory or its contents. Fixes bug
12621 22516; bugfix on 0.2.5.4-alpha.
12623 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
12624 - Avoid a double-marked-circuit warning that could happen when we
12625 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
12628 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
12629 - Reject version numbers with non-numeric prefixes (such as +, -, or
12630 whitespace). Disallowing whitespace prevents differential version
12631 parsing between POSIX-based and Windows platforms. Fixes bug 21507
12632 and part of 21508; bugfix on 0.0.8pre1.
12634 o Build features (backport from 0.3.1.5-alpha):
12635 - Tor's repository now includes a Travis Continuous Integration (CI)
12636 configuration file (.travis.yml). This is meant to help new
12637 developers and contributors who fork Tor to a Github repository be
12638 better able to test their changes, and understand what we expect
12639 to pass. To use this new build feature, you must fork Tor to your
12640 Github account, then go into the "Integrations" menu in the
12641 repository settings for your fork and enable Travis, then push
12642 your changes. Closes ticket 22636.
12645 Changes in version 0.3.0.11 - 2017-09-18
12646 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
12649 Most significantly, it includes a fix for TROVE-2017-008, a
12650 security bug that affects hidden services running with the
12651 SafeLogging option disabled. For more information, see
12652 https://trac.torproject.org/projects/tor/ticket/23490
12654 o Minor features (code style, backport from 0.3.1.7):
12655 - Add "Falls through" comments to our codebase, in order to silence
12656 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
12657 Stieger. Closes ticket 22446.
12660 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
12663 o Minor bugfixes (compilation, backport from 0.3.1.7):
12664 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
12665 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
12667 o Minor bugfixes (controller, backport from 0.3.1.7):
12668 - Do not crash when receiving a HSPOST command with an empty body.
12669 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
12670 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
12671 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
12673 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
12674 - When setting the maximum number of connections allowed by the OS,
12675 always allow some extra file descriptors for other files. Fixes
12676 bug 22797; bugfix on 0.2.0.10-alpha.
12678 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
12679 - Remove a forgotten debugging message when an introduction point
12680 successfully establishes a hidden service prop224 circuit with
12682 - Change three other log_warn() for an introduction point to
12683 protocol warnings, because they can be failure from the network
12684 and are not relevant to the operator. Fixes bug 23078; bugfix on
12685 0.3.0.1-alpha and 0.3.0.2-alpha.
12688 Changes in version 0.3.1.7 - 2017-09-18
12689 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
12691 With the 0.3.1 series, Tor now serves and downloads directory
12692 information in more compact formats, to save on bandwidth overhead. It
12693 also contains a new padding system to resist netflow-based traffic
12694 analysis, and experimental support for building parts of Tor in Rust
12695 (though no parts of Tor are in Rust yet). There are also numerous
12696 small features, bugfixes on earlier release series, and groundwork for
12697 the hidden services revamp of 0.3.2.
12699 This release also includes a fix for TROVE-2017-008, a security bug
12700 that affects hidden services running with the SafeLogging option
12701 disabled. For more information, see
12702 https://trac.torproject.org/projects/tor/ticket/23490
12704 Per our stable release policy, we plan to support each stable release
12705 series for at least the next nine months, or for three months after
12706 the first stable release of the next series: whichever is longer. If
12707 you need a release with long-term support, we recommend that you stay
12708 with the 0.2.9 series.
12710 Below is a list of the changes since 0.3.1.6-rc. For a list of all
12711 changes since 0.3.0, see the ReleaseNotes file.
12713 o Major bugfixes (security, hidden services, loggging):
12714 - Fix a bug where we could log uninitialized stack when a certain
12715 hidden service error occurred while SafeLogging was disabled.
12716 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
12717 TROVE-2017-008 and CVE-2017-0380.
12719 o Minor features (defensive programming):
12720 - Create a pair of consensus parameters, nf_pad_tor2web and
12721 nf_pad_single_onion, to disable netflow padding in the consensus
12722 for non-anonymous connections in case the overhead is high. Closes
12725 o Minor features (diagnostic):
12726 - Add a stack trace to the bug warnings that can be logged when
12727 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
12728 attempt for bug 23105.
12730 o Minor features (geoip):
12731 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
12734 o Minor bugfixes (compilation):
12735 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
12736 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
12738 o Minor bugfixes (controller):
12739 - Do not crash when receiving a HSPOST command with an empty body.
12740 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
12741 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
12742 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
12744 o Minor bugfixes (relay):
12745 - Inform the geoip and rephist modules about all requests, even on
12746 relays that are only fetching microdescriptors. Fixes a bug
12747 related to 21585; bugfix on 0.3.0.1-alpha.
12749 o Minor bugfixes (unit tests):
12750 - Fix a channelpadding unit test failure on slow systems by using
12751 mocked time instead of actual time. Fixes bug 23077; bugfix
12755 Changes in version 0.3.1.6-rc - 2017-09-05
12756 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
12757 release series, including a bug that produced weird behavior on
12758 Windows directory caches.
12760 This is the first release candidate in the Tor 0.3.1 series. If we
12761 find no new bugs or regressions here, the first stable 0.3.1 release
12762 will be nearly identical to it.
12764 o Major bugfixes (windows, directory cache):
12765 - On Windows, do not try to delete cached consensus documents and
12766 diffs before they are unmapped from memory--Windows won't allow
12767 that. Instead, allow the consensus cache directory to grow larger,
12768 to hold files that might need to stay around longer. Fixes bug
12769 22752; bugfix on 0.3.1.1-alpha.
12771 o Minor features (directory authority):
12772 - Improve the message that authorities report to relays that present
12773 RSA/Ed25519 keypairs that conflict with previously pinned keys.
12774 Closes ticket 22348.
12776 o Minor features (geoip):
12777 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
12780 o Minor features (testing):
12781 - Add more tests for compression backend initialization. Closes
12784 o Minor bugfixes (directory cache):
12785 - Fix a memory leak when recovering space in the consensus cache.
12786 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
12788 o Minor bugfixes (hidden service):
12789 - Increase the number of circuits that a service is allowed to
12790 open over a specific period of time. The value was lower than it
12791 should be (8 vs 12) in the normal case of 3 introduction points.
12792 Fixes bug 22159; bugfix on 0.3.0.5-rc.
12793 - Fix a BUG warning during HSv3 descriptor decoding that could be
12794 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
12795 on 0.3.0.1-alpha. Bug found by "haxxpop".
12796 - Rate-limit the log messages if we exceed the maximum number of
12797 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
12799 o Minor bugfixes (logging, relay):
12800 - Remove a forgotten debugging message when an introduction point
12801 successfully establishes a hidden service prop224 circuit with
12803 - Change three other log_warn() for an introduction point to
12804 protocol warnings, because they can be failure from the network
12805 and are not relevant to the operator. Fixes bug 23078; bugfix on
12806 0.3.0.1-alpha and 0.3.0.2-alpha.
12808 o Minor bugfixes (relay):
12809 - When a relay is not running as a directory cache, it will no
12810 longer generate compressed consensuses and consensus diff
12811 information. Previously, this was a waste of disk and CPU. Fixes
12812 bug 23275; bugfix on 0.3.1.1-alpha.
12814 o Minor bugfixes (robustness, error handling):
12815 - Improve our handling of the cases where OpenSSL encounters a
12816 memory error while encoding keys and certificates. We haven't
12817 observed these errors in the wild, but if they do happen, we now
12818 detect and respond better. Fixes bug 19418; bugfix on all versions
12819 of Tor. Reported by Guido Vranken.
12821 o Minor bugfixes (stability):
12822 - Avoid crashing on a double-free when unable to load or process an
12823 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
12824 with the clang static analyzer.
12826 o Minor bugfixes (testing):
12827 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
12828 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
12829 - Port the hs_ntor handshake test to work correctly with recent
12830 versions of the pysha3 module. Fixes bug 23071; bugfix
12833 o Minor bugfixes (Windows service):
12834 - When running as a Windows service, set the ID of the main thread
12835 correctly. Failure to do so made us fail to send log messages to
12836 the controller in 0.2.1.16-rc, slowed down controller event
12837 delivery in 0.2.7.3-rc and later, and crash with an assertion
12838 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
12839 Patch and diagnosis from "Vort".
12842 Changes in version 0.3.0.10 - 2017-08-02
12843 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
12844 from the current Tor alpha series. OpenBSD users and TPROXY users
12845 should upgrade; others are probably okay sticking with 0.3.0.9.
12847 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
12848 - Tor's repository now includes a Travis Continuous Integration (CI)
12849 configuration file (.travis.yml). This is meant to help new
12850 developers and contributors who fork Tor to a Github repository be
12851 better able to test their changes, and understand what we expect
12852 to pass. To use this new build feature, you must fork Tor to your
12853 Github account, then go into the "Integrations" menu in the
12854 repository settings for your fork and enable Travis, then push
12855 your changes. Closes ticket 22636.
12857 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
12858 - Fix a typo that had prevented TPROXY-based transparent proxying
12859 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
12860 Patch from "d4fq0fQAgoJ".
12862 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
12863 - Avoid an assertion failure bug affecting our implementation of
12864 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
12865 handling of "0xbar" differs from what we had expected. Fixes bug
12866 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
12868 o Minor features (backport from 0.3.1.5-alpha):
12869 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
12872 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
12873 - Roll over monthly accounting at the configured hour and minute,
12874 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
12875 Found by Andrey Karpov with PVS-Studio.
12877 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
12878 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
12879 bugfix on 0.2.8.1-alpha.
12880 - Fix warnings when building with libscrypt and openssl scrypt
12881 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
12882 - When building with certain versions of the mingw C header files,
12883 avoid float-conversion warnings when calling the C functions
12884 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
12887 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
12888 - Backport a fix for an "unused variable" warning that appeared
12889 in some versions of mingw. Fixes bug 22838; bugfix on
12892 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
12893 - Avoid Coverity build warnings related to our BUG() macro. By
12894 default, Coverity treats BUG() as the Linux kernel does: an
12895 instant abort(). We need to override that so our BUG() macro
12896 doesn't prevent Coverity from analyzing functions that use it.
12897 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
12899 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
12900 - When rejecting a router descriptor for running an obsolete version
12901 of Tor without ntor support, warn about the obsolete tor version,
12902 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
12904 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
12905 - Avoid a sandbox failure when trying to re-bind to a socket and
12906 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
12908 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
12909 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
12910 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
12913 Changes in version 0.3.1.5-alpha - 2017-08-01
12914 Tor 0.3.1.5-alpha improves the performance of consensus diff
12915 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
12916 several other bugs. If no serious bugs are found in this version, the
12917 next version will be a release candidate.
12919 This release also marks the end of support for the Tor 0.2.4.x,
12920 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
12921 further bug or security fixes. Anyone still running or distributing
12922 one of those versions should upgrade.
12924 o Major features (build system, continuous integration):
12925 - Tor's repository now includes a Travis Continuous Integration (CI)
12926 configuration file (.travis.yml). This is meant to help new
12927 developers and contributors who fork Tor to a Github repository be
12928 better able to test their changes, and understand what we expect
12929 to pass. To use this new build feature, you must fork Tor to your
12930 Github account, then go into the "Integrations" menu in the
12931 repository settings for your fork and enable Travis, then push
12932 your changes. Closes ticket 22636.
12934 o Major bugfixes (openbsd, denial-of-service):
12935 - Avoid an assertion failure bug affecting our implementation of
12936 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
12937 handling of "0xbar" differs from what we had expected. Fixes bug
12938 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
12940 o Major bugfixes (relay, performance):
12941 - Perform circuit handshake operations at a higher priority than we
12942 use for consensus diff creation and compression. This should
12943 prevent circuits from starving when a relay or bridge receives a
12944 new consensus, especially on lower-powered machines. Fixes bug
12945 22883; bugfix on 0.3.1.1-alpha.
12947 o Minor features (bridge authority):
12948 - Add "fingerprint" lines to the networkstatus-bridges file produced
12949 by bridge authorities. Closes ticket 22207.
12951 o Minor features (directory cache, consensus diff):
12952 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
12953 operators with low-resource environments to adjust the number of
12954 consensuses they'll store and generate diffs from. Most cache
12955 operators should leave it unchanged. Helps to work around
12958 o Minor features (geoip):
12959 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
12962 o Minor features (relay, performance):
12963 - Always start relays with at least two worker threads, to prevent
12964 priority inversion on slow tasks. Part of the fix for bug 22883.
12965 - Allow background work to be queued with different priorities, so
12966 that a big pile of slow low-priority jobs will not starve out
12967 higher priority jobs. This lays the groundwork for a fix for
12970 o Minor bugfixes (build system, rust):
12971 - Fix a problem where Rust toolchains were not being found when
12972 building without --enable-cargo-online-mode, due to setting the
12973 $HOME environment variable instead of $CARGO_HOME. Fixes bug
12974 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
12976 o Minor bugfixes (compatibility, zstd):
12977 - Write zstd epilogues correctly when the epilogue requires
12978 reallocation of the output buffer, even with zstd 1.3.0.
12979 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
12980 22927; bugfix on 0.3.1.1-alpha.
12982 o Minor bugfixes (compilation warnings):
12983 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
12984 22915; bugfix on 0.2.8.1-alpha.
12985 - Fix warnings when building with libscrypt and openssl scrypt
12986 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
12987 - Compile correctly when both openssl 1.1.0 and libscrypt are
12988 detected. Previously this would cause an error. Fixes bug 22892;
12989 bugfix on 0.3.1.1-alpha.
12990 - When building with certain versions of the mingw C header files,
12991 avoid float-conversion warnings when calling the C functions
12992 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
12995 o Minor bugfixes (coverity build support):
12996 - Avoid Coverity build warnings related to our BUG() macro. By
12997 default, Coverity treats BUG() as the Linux kernel does: an
12998 instant abort(). We need to override that so our BUG() macro
12999 doesn't prevent Coverity from analyzing functions that use it.
13000 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
13002 o Minor bugfixes (directory authority):
13003 - When a directory authority rejects a descriptor or extrainfo with
13004 a given digest, mark that digest as undownloadable, so that we do
13005 not attempt to download it again over and over. We previously
13006 tried to avoid downloading such descriptors by other means, but we
13007 didn't notice if we accidentally downloaded one anyway. This
13008 behavior became problematic in 0.2.7.2-alpha, when authorities
13009 began pinning Ed25519 keys. Fixes bug 22349; bugfix
13012 o Minor bugfixes (error reporting, windows):
13013 - When formatting Windows error messages, use the English format to
13014 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
13017 o Minor bugfixes (file limits, osx):
13018 - When setting the maximum number of connections allowed by the OS,
13019 always allow some extra file descriptors for other files. Fixes
13020 bug 22797; bugfix on 0.2.0.10-alpha.
13022 o Minor bugfixes (linux seccomp2 sandbox):
13023 - Avoid a sandbox failure when trying to re-bind to a socket and
13024 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
13026 o Minor bugfixes (memory leaks):
13027 - Fix a small memory leak when validating a configuration that uses
13028 two or more AF_UNIX sockets for the same port type. Fixes bug
13029 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
13031 o Minor bugfixes (unit tests):
13032 - test_consdiff_base64cmp would fail on OS X because while OS X
13033 follows the standard of (less than zero/zero/greater than zero),
13034 it doesn't follow the convention of (-1/0/+1). Make the test
13035 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
13036 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
13037 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
13040 Changes in version 0.3.1.4-alpha - 2017-06-29
13041 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
13042 to use a guard that was in the same network family as a chosen exit
13043 relay. This is a security regression; all clients running earlier
13044 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
13047 This release also fixes several other bugs introduced in 0.3.0.x
13048 and 0.3.1.x, including others that can affect bandwidth usage
13051 o New dependencies:
13052 - To build with zstd and lzma support, Tor now requires the
13053 pkg-config tool at build time. (This requirement was new in
13054 0.3.1.1-alpha, but was not noted at the time. Noting it here to
13055 close ticket 22623.)
13057 o Major bugfixes (path selection, security):
13058 - When choosing which guard to use for a circuit, avoid the exit's
13059 family along with the exit itself. Previously, the new guard
13060 selection logic avoided the exit, but did not consider its family.
13061 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
13062 006 and CVE-2017-0377.
13064 o Major bugfixes (compression, zstd):
13065 - Correctly detect a full buffer when decompressing a large zstd-
13066 compressed input. Previously, we would sometimes treat a full
13067 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
13069 o Major bugfixes (directory protocol):
13070 - Ensure that we send "304 Not modified" as HTTP status code when a
13071 client is attempting to fetch a consensus or consensus diff, and
13072 the best one we can send them is one they already have. Fixes bug
13073 22702; bugfix on 0.3.1.1-alpha.
13075 o Major bugfixes (entry guards):
13076 - When starting with an old consensus, do not add new entry guards
13077 unless the consensus is "reasonably live" (under 1 day old). Fixes
13078 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
13080 o Minor features (bug mitigation, diagnostics, logging):
13081 - Avoid an assertion failure, and log a better error message, when
13082 unable to remove a file from the consensus cache on Windows.
13083 Attempts to mitigate and diagnose bug 22752.
13085 o Minor features (geoip):
13086 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
13089 o Minor bugfixes (compression):
13090 - When compressing or decompressing a buffer, check for a failure to
13091 create a compression object. Fixes bug 22626; bugfix
13093 - When decompressing a buffer, check for extra data after the end of
13094 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
13095 - When decompressing an object received over an anonymous directory
13096 connection, if we have already decompressed it using an acceptable
13097 compression method, do not reject it for looking like an
13098 unacceptable compression method. Fixes part of bug 22670; bugfix
13100 - When serving directory votes compressed with zlib, do not claim to
13101 have compressed them with zstd. Fixes bug 22669; bugfix
13103 - When spooling compressed data to an output buffer, don't try to
13104 spool more data when there is no more data to spool and we are not
13105 trying to flush the input. Previously, we would sometimes launch
13106 compression requests with nothing to do, which interferes with our
13107 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
13109 o Minor bugfixes (defensive programming):
13110 - Detect and break out of infinite loops in our compression code. We
13111 don't think that any such loops exist now, but it's best to be
13112 safe. Closes ticket 22672.
13113 - Fix a memset() off the end of an array when packing cells. This
13114 bug should be harmless in practice, since the corrupted bytes are
13115 still in the same structure, and are always padding bytes,
13116 ignored, or immediately overwritten, depending on compiler
13117 behavior. Nevertheless, because the memset()'s purpose is to make
13118 sure that any other cell-handling bugs can't expose bytes to the
13119 network, we need to fix it. Fixes bug 22737; bugfix on
13120 0.2.4.11-alpha. Fixes CID 1401591.
13122 o Minor bugfixes (linux seccomp2 sandbox):
13123 - Permit the fchmod system call, to avoid crashing on startup when
13124 starting with the seccomp2 sandbox and an unexpected set of
13125 permissions on the data directory or its contents. Fixes bug
13126 22516; bugfix on 0.2.5.4-alpha.
13127 - Fix a crash in the LZMA module, when the sandbox was enabled, and
13128 liblzma would allocate more than 16 MB of memory. We solve this by
13129 bumping the mprotect() limit in the sandbox module from 16 MB to
13130 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
13132 o Minor bugfixes (logging):
13133 - When decompressing, do not warn if we fail to decompress using a
13134 compression method that we merely guessed. Fixes part of bug
13135 22670; bugfix on 0.1.1.14-alpha.
13136 - When decompressing, treat mismatch between content-encoding and
13137 actual compression type as a protocol warning. Fixes part of bug
13138 22670; bugfix on 0.1.1.9-alpha.
13139 - Downgrade "assigned_to_cpuworker failed" message to info-level
13140 severity. In every case that can reach it, either a better warning
13141 has already been logged, or no warning is warranted. Fixes bug
13142 22356; bugfix on 0.2.6.3-alpha.
13143 - Demote a warn that was caused by libevent delays to info if
13144 netflow padding is less than 4.5 seconds late, or to notice
13145 if it is more (4.5 seconds is the amount of time that a netflow
13146 record might be emitted after, if we chose the maximum timeout).
13147 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
13149 o Minor bugfixes (process behavior):
13150 - When exiting because of an error, always exit with a nonzero exit
13151 status. Previously, we would fail to report an error in our exit
13152 status in cases related to __OwningControllerProcess failure,
13153 lockfile contention, and Ed25519 key initialization. Fixes bug
13154 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
13155 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
13159 - Add a manpage description for the key-pinning-journal file. Closes
13161 - Correctly note that bandwidth accounting values are stored in the
13162 state file, and the bw_accounting file is now obsolete. Closes
13164 - Document more of the files in the Tor data directory, including
13165 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
13166 approved-routers, sr-random, and diff-cache. Found while fixing
13170 Changes in version 0.3.0.9 - 2017-06-29
13171 Tor 0.3.0.9 fixes a path selection bug that would allow a client
13172 to use a guard that was in the same network family as a chosen exit
13173 relay. This is a security regression; all clients running earlier
13174 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
13177 This release also backports several other bugfixes from the 0.3.1.x
13180 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
13181 - When choosing which guard to use for a circuit, avoid the exit's
13182 family along with the exit itself. Previously, the new guard
13183 selection logic avoided the exit, but did not consider its family.
13184 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
13185 006 and CVE-2017-0377.
13187 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
13188 - Don't block bootstrapping when a primary bridge is offline and we
13189 can't get its descriptor. Fixes bug 22325; fixes one case of bug
13190 21969; bugfix on 0.3.0.3-alpha.
13192 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
13193 - When starting with an old consensus, do not add new entry guards
13194 unless the consensus is "reasonably live" (under 1 day old). Fixes
13195 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
13197 o Minor features (geoip):
13198 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
13201 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
13202 - Reject version numbers with non-numeric prefixes (such as +, -, or
13203 whitespace). Disallowing whitespace prevents differential version
13204 parsing between POSIX-based and Windows platforms. Fixes bug 21507
13205 and part of 21508; bugfix on 0.0.8pre1.
13207 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
13208 - Permit the fchmod system call, to avoid crashing on startup when
13209 starting with the seccomp2 sandbox and an unexpected set of
13210 permissions on the data directory or its contents. Fixes bug
13211 22516; bugfix on 0.2.5.4-alpha.
13213 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
13214 - Fix a memset() off the end of an array when packing cells. This
13215 bug should be harmless in practice, since the corrupted bytes are
13216 still in the same structure, and are always padding bytes,
13217 ignored, or immediately overwritten, depending on compiler
13218 behavior. Nevertheless, because the memset()'s purpose is to make
13219 sure that any other cell-handling bugs can't expose bytes to the
13220 network, we need to fix it. Fixes bug 22737; bugfix on
13221 0.2.4.11-alpha. Fixes CID 1401591.
13224 Changes in version 0.3.1.3-alpha - 2017-06-08
13225 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
13226 remotely crash a hidden service with an assertion failure. Anyone
13227 running a hidden service should upgrade to this version, or to some
13228 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
13230 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
13231 that sometimes made relays unreliable, as well as several other
13232 bugfixes described below.
13234 o Major bugfixes (hidden service, relay, security):
13235 - Fix a remotely triggerable assertion failure when a hidden service
13236 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
13237 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
13238 - Fix a remotely triggerable assertion failure caused by receiving a
13239 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13240 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13243 o Major bugfixes (relay, link handshake):
13244 - When performing the v3 link handshake on a TLS connection, report
13245 that we have the x509 certificate that we actually used on that
13246 connection, even if we have changed certificates since that
13247 connection was first opened. Previously, we would claim to have
13248 used our most recent x509 link certificate, which would sometimes
13249 make the link handshake fail. Fixes one case of bug 22460; bugfix
13252 o Major bugfixes (relays, key management):
13253 - Regenerate link and authentication certificates whenever the key
13254 that signs them changes; also, regenerate link certificates
13255 whenever the signed key changes. Previously, these processes were
13256 only weakly coupled, and we relays could (for minutes to hours)
13257 wind up with an inconsistent set of keys and certificates, which
13258 other relays would not accept. Fixes two cases of bug 22460;
13259 bugfix on 0.3.0.1-alpha.
13260 - When sending an Ed25519 signing->link certificate in a CERTS cell,
13261 send the certificate that matches the x509 certificate that we
13262 used on the TLS connection. Previously, there was a race condition
13263 if the TLS context rotated after we began the TLS handshake but
13264 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
13267 o Major bugfixes (torrc, crash):
13268 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
13269 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
13271 o Minor features (code style):
13272 - Add "Falls through" comments to our codebase, in order to silence
13273 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
13274 Stieger. Closes ticket 22446.
13276 o Minor features (diagnostic):
13277 - Add logging messages to try to diagnose a rare bug that seems to
13278 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
13279 think this is happening because of incorrect system clocks, but
13280 we'd like to know for certain. Diagnostic for bug 22466.
13282 o Minor bugfixes (correctness):
13283 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13284 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13286 o Minor bugfixes (directory protocol):
13287 - Check for libzstd >= 1.1, because older versions lack the
13288 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
13290 o Minor bugfixes (link handshake):
13291 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
13292 months, and regenerate it when it is within one month of expiring.
13293 Previously, we had generated this certificate at startup with a
13294 ten-year lifetime, but that could lead to weird behavior when Tor
13295 was started with a grossly inaccurate clock. Mitigates bug 22466;
13296 mitigation on 0.3.0.1-alpha.
13298 o Minor bugfixes (storage directories):
13299 - Always check for underflows in the cached storage directory usage.
13300 If the usage does underflow, re-calculate it. Also, avoid a
13301 separate underflow when the usage is not known. Fixes bug 22424;
13302 bugfix on 0.3.1.1-alpha.
13304 o Minor bugfixes (unit tests):
13305 - The unit tests now pass on systems where localhost is misconfigured
13306 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
13310 - Clarify the manpage for the (deprecated) torify script. Closes
13313 Changes in version 0.3.0.8 - 2017-06-08
13314 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
13315 remotely crash a hidden service with an assertion failure. Anyone
13316 running a hidden service should upgrade to this version, or to some
13317 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
13319 Tor 0.3.0.8 also includes fixes for several key management bugs
13320 that sometimes made relays unreliable, as well as several other
13321 bugfixes described below.
13323 o Major bugfixes (hidden service, relay, security, backport
13324 from 0.3.1.3-alpha):
13325 - Fix a remotely triggerable assertion failure when a hidden service
13326 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
13327 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
13328 - Fix a remotely triggerable assertion failure caused by receiving a
13329 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13330 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13333 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
13334 - When performing the v3 link handshake on a TLS connection, report
13335 that we have the x509 certificate that we actually used on that
13336 connection, even if we have changed certificates since that
13337 connection was first opened. Previously, we would claim to have
13338 used our most recent x509 link certificate, which would sometimes
13339 make the link handshake fail. Fixes one case of bug 22460; bugfix
13342 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
13343 - Regenerate link and authentication certificates whenever the key
13344 that signs them changes; also, regenerate link certificates
13345 whenever the signed key changes. Previously, these processes were
13346 only weakly coupled, and we relays could (for minutes to hours)
13347 wind up with an inconsistent set of keys and certificates, which
13348 other relays would not accept. Fixes two cases of bug 22460;
13349 bugfix on 0.3.0.1-alpha.
13350 - When sending an Ed25519 signing->link certificate in a CERTS cell,
13351 send the certificate that matches the x509 certificate that we
13352 used on the TLS connection. Previously, there was a race condition
13353 if the TLS context rotated after we began the TLS handshake but
13354 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
13357 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
13358 - Stop rejecting v3 hidden service descriptors because their size
13359 did not match an old padding rule. Fixes bug 22447; bugfix on
13362 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
13363 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
13364 December 2016 (of which ~126 were still functional) with a list of
13365 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
13366 2017. Resolves ticket 21564.
13368 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
13369 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
13370 bug 22252; bugfix on 0.2.9.3-alpha.
13372 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
13373 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13374 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13376 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
13377 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
13378 months, and regenerate it when it is within one month of expiring.
13379 Previously, we had generated this certificate at startup with a
13380 ten-year lifetime, but that could lead to weird behavior when Tor
13381 was started with a grossly inaccurate clock. Mitigates bug 22466;
13382 mitigation on 0.3.0.1-alpha.
13384 o Minor bugfixes (memory leak, directory authority, backport from
13386 - When directory authorities reject a router descriptor due to
13387 keypinning, free the router descriptor rather than leaking the
13388 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
13391 Changes in version 0.2.9.11 - 2017-06-08
13392 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
13393 remotely crash a hidden service with an assertion failure. Anyone
13394 running a hidden service should upgrade to this version, or to some
13395 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13396 are not affected by TROVE-2017-004.)
13398 Tor 0.2.9.11 also backports fixes for several key management bugs
13399 that sometimes made relays unreliable, as well as several other
13400 bugfixes described below.
13402 o Major bugfixes (hidden service, relay, security, backport
13403 from 0.3.1.3-alpha):
13404 - Fix a remotely triggerable assertion failure caused by receiving a
13405 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13406 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13409 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
13410 - When performing the v3 link handshake on a TLS connection, report
13411 that we have the x509 certificate that we actually used on that
13412 connection, even if we have changed certificates since that
13413 connection was first opened. Previously, we would claim to have
13414 used our most recent x509 link certificate, which would sometimes
13415 make the link handshake fail. Fixes one case of bug 22460; bugfix
13418 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
13419 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
13420 December 2016 (of which ~126 were still functional) with a list of
13421 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
13422 2017. Resolves ticket 21564.
13424 o Minor features (future-proofing, backport from 0.3.0.7):
13425 - Tor no longer refuses to download microdescriptors or descriptors if
13426 they are listed as "published in the future". This change will
13427 eventually allow us to stop listing meaningful "published" dates
13428 in microdescriptor consensuses, and thereby allow us to reduce the
13429 resources required to download consensus diffs by over 50%.
13430 Implements part of ticket 21642; implements part of proposal 275.
13432 o Minor features (directory authorities, backport from 0.3.0.4-rc)
13433 - Directory authorities now reject relays running versions
13434 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
13435 suffer from bug 20499 and don't keep their consensus cache
13436 up-to-date. Resolves ticket 20509.
13438 o Minor features (geoip):
13439 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13442 o Minor bugfixes (control port, backport from 0.3.0.6):
13443 - The GETINFO extra-info/digest/<digest> command was broken because
13444 of a wrong base16 decode return value check, introduced when
13445 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
13447 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
13448 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13449 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13451 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
13452 - The getpid() system call is now permitted under the Linux seccomp2
13453 sandbox, to avoid crashing with versions of OpenSSL (and other
13454 libraries) that attempt to learn the process's PID by using the
13455 syscall rather than the VDSO code. Fixes bug 21943; bugfix
13458 o Minor bugfixes (memory leak, directory authority, backport
13459 from 0.3.1.2-alpha):
13460 - When directory authorities reject a router descriptor due to
13461 keypinning, free the router descriptor rather than leaking the
13462 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
13464 Changes in version 0.2.8.14 - 2017-06-08
13465 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
13466 remotely crash a hidden service with an assertion failure. Anyone
13467 running a hidden service should upgrade to this version, or to some
13468 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13469 are not affected by TROVE-2017-004.)
13471 o Major bugfixes (hidden service, relay, security):
13472 - Fix a remotely triggerable assertion failure caused by receiving a
13473 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13474 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13477 o Minor features (geoip):
13478 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13481 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
13482 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
13483 December 2016 (of which ~126 were still functional) with a list of
13484 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
13485 2017. Resolves ticket 21564.
13487 o Minor bugfixes (correctness):
13488 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13489 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13491 Changes in version 0.2.7.8 - 2017-06-08
13492 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
13493 remotely crash a hidden service with an assertion failure. Anyone
13494 running a hidden service should upgrade to this version, or to some
13495 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13496 are not affected by TROVE-2017-004.)
13498 o Major bugfixes (hidden service, relay, security):
13499 - Fix a remotely triggerable assertion failure caused by receiving a
13500 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13501 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13504 o Minor features (geoip):
13505 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13508 o Minor bugfixes (correctness):
13509 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13510 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13513 Changes in version 0.2.6.12 - 2017-06-08
13514 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
13515 remotely crash a hidden service with an assertion failure. Anyone
13516 running a hidden service should upgrade to this version, or to some
13517 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13518 are not affected by TROVE-2017-004.)
13520 o Major bugfixes (hidden service, relay, security):
13521 - Fix a remotely triggerable assertion failure caused by receiving a
13522 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13523 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13526 o Minor features (geoip):
13527 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13530 o Minor bugfixes (correctness):
13531 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13532 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13534 Changes in version 0.2.5.14 - 2017-06-08
13535 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
13536 remotely crash a hidden service with an assertion failure. Anyone
13537 running a hidden service should upgrade to this version, or to some
13538 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13539 are not affected by TROVE-2017-004.)
13541 o Major bugfixes (hidden service, relay, security):
13542 - Fix a remotely triggerable assertion failure caused by receiving a
13543 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13544 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13547 o Minor features (geoip):
13548 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13551 o Minor bugfixes (correctness):
13552 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13553 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13555 Changes in version 0.2.4.29 - 2017-06-08
13556 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
13557 remotely crash a hidden service with an assertion failure. Anyone
13558 running a hidden service should upgrade to this version, or to some
13559 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13560 are not affected by TROVE-2017-004.)
13562 o Major bugfixes (hidden service, relay, security):
13563 - Fix a remotely triggerable assertion failure caused by receiving a
13564 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13565 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13568 o Minor features (geoip):
13569 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13572 o Minor bugfixes (correctness):
13573 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13574 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13577 Changes in version 0.3.1.2-alpha - 2017-05-26
13578 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
13579 fixes a few bugs found while testing 0.3.1.1-alpha, including a
13580 memory corruption bug that affected relay stability.
13582 o Major bugfixes (crash, relay):
13583 - Fix a memory-corruption bug in relays that set MyFamily.
13584 Previously, they would double-free MyFamily elements when making
13585 the next descriptor or when changing their configuration. Fixes
13586 bug 22368; bugfix on 0.3.1.1-alpha.
13588 o Minor bugfixes (logging):
13589 - Log a better message when a directory authority replies to an
13590 upload with an unexpected status code. Fixes bug 11121; bugfix
13593 o Minor bugfixes (memory leak, directory authority):
13594 - When directory authorities reject a router descriptor due to
13595 keypinning, free the router descriptor rather than leaking the
13596 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
13599 Changes in version 0.3.1.1-alpha - 2017-05-22
13600 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
13601 reduces the bandwidth usage for Tor's directory protocol, adds some
13602 basic padding to resist netflow-based traffic analysis and to serve as
13603 the basis of other padding in the future, and adds rust support to the
13606 It also contains numerous other small features and improvements to
13607 security, correctness, and performance.
13609 Below are the changes since 0.3.0.7.
13611 o Major features (directory protocol):
13612 - Tor relays and authorities can now serve clients an abbreviated
13613 version of the consensus document, containing only the changes
13614 since an older consensus document that the client holds. Clients
13615 now request these documents when available. When both client and
13616 server use this new protocol, they will use far less bandwidth (up
13617 to 94% less) to keep the client's consensus up-to-date. Implements
13618 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
13619 - Tor can now compress directory traffic with lzma or with zstd
13620 compression algorithms, which can deliver better bandwidth
13621 performance. Because lzma is computationally expensive, it's only
13622 used for documents that can be compressed once and served many
13623 times. Support for these algorithms requires that tor is built
13624 with the libzstd and/or liblzma libraries available. Implements
13625 proposal 278; closes ticket 21662.
13626 - Relays now perform the more expensive compression operations, and
13627 consensus diff generation, in worker threads. This separation
13628 avoids delaying the main thread when a new consensus arrives.
13630 o Major features (experimental):
13631 - Tor can now build modules written in Rust. To turn this on, pass
13632 the "--enable-rust" flag to the configure script. It's not time to
13633 get excited yet: currently, there is no actual Rust functionality
13634 beyond some simple glue code, and a notice at startup to tell you
13635 that Rust is running. Still, we hope that programmers and
13636 packagers will try building Tor with Rust support, so that we can
13637 find issues and solve portability problems. Closes ticket 22106.
13639 o Major features (traffic analysis resistance):
13640 - Connections between clients and relays now send a padding cell in
13641 each direction every 1.5 to 9.5 seconds (tunable via consensus
13642 parameters). This padding will not resist specialized
13643 eavesdroppers, but it should be enough to make many ISPs' routine
13644 network flow logging less useful in traffic analysis against
13647 Padding is negotiated using Tor's link protocol, so both relays
13648 and clients must upgrade for this to take effect. Clients may
13649 still send padding despite the relay's version by setting
13650 ConnectionPadding 1 in torrc, and may disable padding by setting
13651 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
13652 users with the torrc option ReducedConnectionPadding. Implements
13653 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
13654 - Relays will publish 24 hour totals of padding and non-padding cell
13655 counts to their extra-info descriptors, unless PaddingStatistics 0
13656 is set in torrc. These 24 hour totals are also rounded to
13657 multiples of 10000.
13659 o Major bugfixes (connection usage):
13660 - We use NETINFO cells to try to determine if both relays involved
13661 in a connection will agree on the canonical status of that
13662 connection. We prefer the connections where this is the case for
13663 extend cells, and try to close connections where relays disagree
13664 on their canonical status early. Also, we now prefer the oldest
13665 valid connection for extend cells. These two changes should reduce
13666 the number of long-term connections that are kept open between
13667 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
13668 - Relays now log hourly statistics (look for
13669 "channel_check_for_duplicates" lines) on the total number of
13670 connections to other relays. If the number of connections per
13671 relay is unexpectedly large, this log message is at notice level.
13672 Otherwise it is at info.
13674 o Major bugfixes (entry guards):
13675 - Don't block bootstrapping when a primary bridge is offline and we
13676 can't get its descriptor. Fixes bug 22325; fixes one case of bug
13677 21969; bugfix on 0.3.0.3-alpha.
13679 o Major bugfixes (linux TPROXY support):
13680 - Fix a typo that had prevented TPROXY-based transparent proxying
13681 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
13682 Patch from "d4fq0fQAgoJ".
13684 o Minor features (security, windows):
13685 - Enable a couple of pieces of Windows hardening: one
13686 (HeapEnableTerminationOnCorruption) that has been on-by-default
13687 since Windows 8, and unavailable before Windows 7; and one
13688 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
13689 affect us, but shouldn't do any harm. Closes ticket 21953.
13691 o Minor features (config options):
13692 - Allow "%include" directives in torrc configuration files. These
13693 directives import the settings from other files, or from all the
13694 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
13695 - Make SAVECONF return an error when overwriting a torrc that has
13696 includes. Using SAVECONF with the FORCE option will allow it to
13697 overwrite torrc even if includes are used. Related to ticket 1922.
13698 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
13699 will work without the FORCE option. Related to ticket 1922.
13701 o Minor features (controller):
13702 - Warn the first time that a controller requests data in the long-
13703 deprecated 'GETINFO network-status' format. Closes ticket 21703.
13705 o Minor features (defaults):
13706 - The default value for UseCreateFast is now 0: clients which
13707 haven't yet received a consensus document will now use a proper
13708 ntor handshake to talk to their directory servers whenever they
13709 can. Closes ticket 21407.
13710 - Onion key rotation and expiry intervals are now defined as a
13711 network consensus parameter, per proposal 274. The default
13712 lifetime of an onion key is increased from 7 to 28 days. Old onion
13713 keys will expire after 7 days by default. This change will make
13714 consensus diffs much smaller, and save significant bandwidth.
13715 Closes ticket 21641.
13717 o Minor features (fallback directory list):
13718 - Update the fallback directory mirror whitelist and blacklist based
13719 on operator emails. Closes task 21121.
13720 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
13721 December 2016 (of which ~126 were still functional) with a list of
13722 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
13723 2017. Resolves ticket 21564.
13725 o Minor features (hidden services, logging):
13726 - Log a message when a hidden service descriptor has fewer
13727 introduction points than specified in
13728 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
13729 - Log a message when a hidden service reaches its introduction point
13730 circuit limit, and when that limit is reset. Follow up to ticket
13731 21594; closes ticket 21622.
13732 - Warn user if multiple entries in EntryNodes and at least one
13733 HiddenService are used together. Pinning EntryNodes along with a
13734 hidden service can be possibly harmful; for instance see ticket
13735 14917 or 21155. Closes ticket 21155.
13737 o Minor features (linux seccomp2 sandbox):
13738 - We now have a document storage backend compatible with the Linux
13739 seccomp2 sandbox. This backend is used for consensus documents and
13740 diffs between them; in the long term, we'd like to use it for
13741 unparseable directory material too. Closes ticket 21645
13742 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
13743 from 1MB to 16MB. This was necessary with the glibc allocator in
13744 order to allow worker threads to allocate more memory -- which in
13745 turn is necessary because of our new use of worker threads for
13746 compression. Closes ticket 22096.
13748 o Minor features (logging):
13749 - Log files are no longer created world-readable by default.
13750 (Previously, most distributors would store the logs in a non-
13751 world-readable location to prevent inappropriate access. This
13752 change is an extra precaution.) Closes ticket 21729; patch
13755 o Minor features (performance):
13756 - Our Keccak (SHA-3) implementation now accesses memory more
13757 efficiently, especially on little-endian systems. Closes
13759 - Add an O(1) implementation of channel_find_by_global_id(), to
13760 speed some controller functions.
13762 o Minor features (relay, configuration):
13763 - The MyFamily option may now be repeated as many times as desired,
13764 for relays that want to configure large families. Closes ticket
13765 4998; patch by Daniel Pinto.
13767 o Minor features (safety):
13768 - Add an explicit check to extrainfo_parse_entry_from_string() for
13769 NULL inputs. We don't believe this can actually happen, but it may
13770 help silence a warning from the Clang analyzer. Closes
13773 o Minor features (testing):
13774 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
13775 When Tor is compiled with this option, we disable a number of
13776 redundant memory-safety failsafes that are intended to stop bugs
13777 from becoming security issues. This makes it easier to hunt for
13778 bugs that would be security issues without the failsafes turned
13779 on. Closes ticket 21439.
13780 - Add a general event-tracing instrumentation support to Tor. This
13781 subsystem will enable developers and researchers to add fine-
13782 grained instrumentation to their Tor instances, for use when
13783 examining Tor network performance issues. There are no trace
13784 events yet, and event-tracing is off by default unless enabled at
13785 compile time. Implements ticket 13802.
13786 - Improve our version parsing tests: add tests for typical version
13787 components, add tests for invalid versions, including numeric
13788 range and non-numeric prefixes. Unit tests 21278, 21450, and
13789 21507. Partially implements 21470.
13791 o Minor bugfixes (bandwidth accounting):
13792 - Roll over monthly accounting at the configured hour and minute,
13793 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
13794 Found by Andrey Karpov with PVS-Studio.
13796 o Minor bugfixes (code correctness):
13797 - Accurately identify client connections by their lack of peer
13798 authentication. This means that we bail out earlier if asked to
13799 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
13802 o Minor bugfixes (configuration):
13803 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
13804 bug 22252; bugfix on 0.2.9.3-alpha.
13806 o Minor bugfixes (connection lifespan):
13807 - Allow more control over how long TLS connections are kept open:
13808 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
13809 single option called CircuitsAvailableTimeout. Also, allow the
13810 consensus to control the default values for both this preference
13811 and the lifespan of relay-to-relay connections. Fixes bug 17592;
13812 bugfix on 0.2.5.5-alpha.
13813 - Increase the initial circuit build timeout testing frequency, to
13814 help ensure that ReducedConnectionPadding clients finish learning
13815 a timeout before their orconn would expire. The initial testing
13816 rate was set back in the days of TAP and before the Tor Browser
13817 updater, when we had to be much more careful about new clients
13818 making lots of circuits. With this change, a circuit build timeout
13819 is learned in about 15-20 minutes, instead of 100-120 minutes.
13821 o Minor bugfixes (controller):
13822 - GETINFO onions/current and onions/detached no longer respond with
13823 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
13824 - Trigger HS descriptor events on the control port when the client
13825 fails to pick a hidden service directory for a hidden service.
13826 This can happen if all the hidden service directories are in
13827 ExcludeNodes, or they have all been queried within the last 15
13828 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
13830 o Minor bugfixes (directory authority):
13831 - When rejecting a router descriptor for running an obsolete version
13832 of Tor without ntor support, warn about the obsolete tor version,
13833 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
13834 - Prevent the shared randomness subsystem from asserting when
13835 initialized by a bridge authority with an incomplete configuration
13836 file. Fixes bug 21586; bugfix on 0.2.9.8.
13838 o Minor bugfixes (exit-side DNS):
13839 - Fix an untriggerable assertion that checked the output of a
13840 libevent DNS error, so that the assertion actually behaves as
13841 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
13842 Karpov using PVS-Studio.
13844 o Minor bugfixes (fallback directories):
13845 - Make the usage example in updateFallbackDirs.py actually work, and
13846 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
13847 - Decrease the guard flag average required to be a fallback. This
13848 allows us to keep relays that have their guard flag removed when
13849 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
13850 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
13851 bugfix on 0.2.8.1-alpha.
13852 - Make sure fallback directory mirrors have the same address, port,
13853 and relay identity key for at least 30 days before they are
13854 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
13856 o Minor bugfixes (hidden services):
13857 - Stop printing a cryptic warning when a hidden service gets a
13858 request to connect to a virtual port that it hasn't configured.
13859 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
13860 - Simplify hidden service descriptor creation by using an existing
13861 flag to check if an introduction point is established. Fixes bug
13862 21599; bugfix on 0.2.7.2-alpha.
13864 o Minor bugfixes (memory leak):
13865 - Fix a small memory leak at exit from the backtrace handler code.
13866 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
13868 o Minor bugfixes (protocol, logging):
13869 - Downgrade a log statement about unexpected relay cells from "bug"
13870 to "protocol warning", because there is at least one use case
13871 where it can be triggered by a buggy tor implementation. Fixes bug
13872 21293; bugfix on 0.1.1.14-alpha.
13874 o Minor bugfixes (testing):
13875 - Use unbuffered I/O for utility functions around the
13876 process_handle_t type. This fixes unit test failures reported on
13877 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
13878 - Make display of captured unit test log messages consistent. Fixes
13879 bug 21510; bugfix on 0.2.9.3-alpha.
13880 - Make test-network.sh always call chutney's test-network.sh.
13881 Previously, this only worked on systems which had bash installed,
13882 due to some bash-specific code in the script. Fixes bug 19699;
13883 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
13885 o Minor bugfixes (voting consistency):
13886 - Reject version numbers with non-numeric prefixes (such as +, -, or
13887 whitespace). Disallowing whitespace prevents differential version
13888 parsing between POSIX-based and Windows platforms. Fixes bug 21507
13889 and part of 21508; bugfix on 0.0.8pre1.
13891 o Minor bugfixes (windows, relay):
13892 - Resolve "Failure from drain_fd: No error" warnings on Windows
13893 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
13895 o Code simplification and refactoring:
13896 - Break up the 630-line function connection_dir_client_reached_eof()
13897 into a dozen smaller functions. This change should help
13898 maintainability and readability of the client directory code.
13899 - Isolate our use of the openssl headers so that they are only
13900 included from our crypto wrapper modules, and from tests that
13901 examine those modules' internals. Closes ticket 21841.
13902 - Simplify our API to launch directory requests, making it more
13903 extensible and less error-prone. Now it's easier to add extra
13904 headers to directory requests. Closes ticket 21646.
13905 - Our base64 decoding functions no longer overestimate the output
13906 space that they need when parsing unpadded inputs. Closes
13908 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
13909 Resolves ticket 22213.
13910 - The logic that directory caches use to spool request to clients,
13911 serving them one part at a time so as not to allocate too much
13912 memory, has been refactored for consistency. Previously there was
13913 a separate spooling implementation per type of spoolable data. Now
13914 there is one common spooling implementation, with extensible data
13915 types. Closes ticket 21651.
13916 - Tor's compression module now supports multiple backends. Part of
13917 the implementation for proposal 278; closes ticket 21663.
13920 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
13921 Closes ticket 21873.
13922 - Correct documentation about the default DataDirectory value.
13923 Closes ticket 21151.
13924 - Document the default behavior of NumEntryGuards and
13925 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
13927 - Document key=value pluggable transport arguments for Bridge lines
13928 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
13929 - Note that bandwidth-limiting options don't affect TCP headers or
13930 DNS. Closes ticket 17170.
13932 o Removed features (configuration options, all in ticket 22060):
13933 - These configuration options are now marked Obsolete, and no longer
13934 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
13935 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
13936 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
13937 in 0.2.9.2-alpha and have now been removed. The previous default
13938 behavior is now always chosen; the previous (less secure) non-
13939 default behavior is now unavailable.
13940 - CloseHSClientCircuitsImmediatelyOnTimeout and
13941 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
13942 0.2.9.2-alpha and now have been removed. HS circuits never close
13943 on circuit build timeout; they have a longer timeout period.
13944 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
13945 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
13946 (and others) to configure listen-only and advertise-only addresses.
13948 o Removed features (tools):
13949 - We've removed the tor-checkkey tool from src/tools. Long ago, we
13950 used it to help people detect RSA keys that were generated by
13951 versions of Debian affected by CVE-2008-0166. But those keys have
13952 been out of circulation for ages, and this tool is no longer
13953 required. Closes ticket 21842.
13956 Changes in version 0.3.0.7 - 2017-05-15
13957 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
13958 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
13959 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
13960 clients are not affected.
13962 o Major bugfixes (hidden service directory, security):
13963 - Fix an assertion failure in the hidden service directory code, which
13964 could be used by an attacker to remotely cause a Tor relay process to
13965 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
13966 should upgrade. This security issue is tracked as TROVE-2017-002.
13967 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
13970 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13973 o Minor features (future-proofing):
13974 - Tor no longer refuses to download microdescriptors or descriptors
13975 if they are listed as "published in the future". This change will
13976 eventually allow us to stop listing meaningful "published" dates
13977 in microdescriptor consensuses, and thereby allow us to reduce the
13978 resources required to download consensus diffs by over 50%.
13979 Implements part of ticket 21642; implements part of proposal 275.
13981 o Minor bugfixes (Linux seccomp2 sandbox):
13982 - The getpid() system call is now permitted under the Linux seccomp2
13983 sandbox, to avoid crashing with versions of OpenSSL (and other
13984 libraries) that attempt to learn the process's PID by using the
13985 syscall rather than the VDSO code. Fixes bug 21943; bugfix
13989 Changes in version 0.3.0.6 - 2017-04-26
13990 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
13992 With the 0.3.0 series, clients and relays now use Ed25519 keys to
13993 authenticate their link connections to relays, rather than the old
13994 RSA1024 keys that they used before. (Circuit crypto has been
13995 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
13996 the guard selection and replacement algorithm to behave more robustly
13997 in the presence of unreliable networks, and to resist guard-
14000 This series also includes numerous other small features and bugfixes,
14001 along with more groundwork for the upcoming hidden-services revamp.
14003 Per our stable release policy, we plan to support the Tor 0.3.0
14004 release series for at least the next nine months, or for three months
14005 after the first stable release of the 0.3.1 series: whichever is
14006 longer. If you need a release with long-term support, we recommend
14007 that you stay with the 0.2.9 series.
14009 Below are the changes since 0.3.0.5-rc. For a list of all changes
14010 since 0.2.9, see the ReleaseNotes file.
14012 o Minor features (geoip):
14013 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
14016 o Minor bugfixes (control port):
14017 - The GETINFO extra-info/digest/<digest> command was broken because
14018 of a wrong base16 decode return value check, introduced when
14019 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
14021 o Minor bugfixes (crash prevention):
14022 - Fix a (currently untriggerable, but potentially dangerous) crash
14023 bug when base32-encoding inputs whose sizes are not a multiple of
14024 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
14027 Changes in version 0.3.0.5-rc - 2017-04-05
14028 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
14029 0.3.0 release series.
14031 This is the second release candidate in the Tor 0.3.0 series, and has
14032 much fewer changes than the first. If we find no new bugs or
14033 regressions here, the first stable 0.3.0 release will be nearly
14036 o Major bugfixes (crash, directory connections):
14037 - Fix a rare crash when sending a begin cell on a circuit whose
14038 linked directory connection had already been closed. Fixes bug
14039 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
14041 o Major bugfixes (guard selection):
14042 - Fix a guard selection bug where Tor would refuse to bootstrap in
14043 some cases if the user swapped a bridge for another bridge in
14044 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
14045 Reported by "torvlnt33r".
14047 o Minor features (geoip):
14048 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
14051 o Minor bugfix (compilation):
14052 - Fix a warning when compiling hs_service.c. Previously, it had no
14053 exported symbols when compiled for libor.a, resulting in a
14054 compilation warning from clang. Fixes bug 21825; bugfix
14057 o Minor bugfixes (hidden services):
14058 - Make hidden services check for failed intro point connections,
14059 even when they have exceeded their intro point creation limit.
14060 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
14061 - Make hidden services with 8 to 10 introduction points check for
14062 failed circuits immediately after startup. Previously, they would
14063 wait for 5 minutes before performing their first checks. Fixes bug
14064 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
14066 o Minor bugfixes (memory leaks):
14067 - Fix a memory leak when using GETCONF on a port option. Fixes bug
14068 21682; bugfix on 0.3.0.3-alpha.
14070 o Minor bugfixes (relay):
14071 - Avoid a double-marked-circuit warning that could happen when we
14072 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
14075 o Minor bugfixes (tests):
14076 - Run the entry_guard_parse_from_state_full() test with the time set
14077 to a specific date. (The guard state that this test was parsing
14078 contained guards that had expired since the test was first
14079 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
14082 - Update the description of the directory server options in the
14083 manual page, to clarify that a relay no longer needs to set
14084 DirPort in order to be a directory cache. Closes ticket 21720.
14088 Changes in version 0.2.8.13 - 2017-03-03
14089 Tor 0.2.8.13 backports a security fix from later Tor
14090 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
14091 this release, if for some reason they cannot upgrade to a later
14092 release series, and if they build Tor with the --enable-expensive-hardening
14095 Note that support for Tor 0.2.8.x is ending next year: we will not issue
14096 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
14097 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
14099 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14100 - Fix an integer underflow bug when comparing malformed Tor
14101 versions. This bug could crash Tor when built with
14102 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14103 0.2.9.8, which were built with -ftrapv by default. In other cases
14104 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14105 on 0.0.8pre1. Found by OSS-Fuzz.
14107 o Minor features (geoip):
14108 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14112 Changes in version 0.2.7.7 - 2017-03-03
14113 Tor 0.2.7.7 backports a number of security fixes from later Tor
14114 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
14115 this release, if for some reason they cannot upgrade to a later
14118 Note that support for Tor 0.2.7.x is ending this year: we will not issue
14119 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
14120 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
14122 o Directory authority changes (backport from 0.2.8.5-rc):
14123 - Urras is no longer a directory authority. Closes ticket 19271.
14125 o Directory authority changes (backport from 0.2.9.2-alpha):
14126 - The "Tonga" bridge authority has been retired; the new bridge
14127 authority is "Bifroest". Closes tickets 19728 and 19690.
14129 o Directory authority key updates (backport from 0.2.8.1-alpha):
14130 - Update the V3 identity key for the dannenberg directory authority:
14131 it was changed on 18 November 2015. Closes task 17906. Patch
14134 o Major bugfixes (parsing, security, backport from 0.2.9.8):
14135 - Fix a bug in parsing that could cause clients to read a single
14136 byte past the end of an allocated region. This bug could be used
14137 to cause hardened clients (built with --enable-expensive-hardening)
14138 to crash if they tried to visit a hostile hidden service. Non-
14139 hardened clients are only affected depending on the details of
14140 their platform's memory allocator. Fixes bug 21018; bugfix on
14141 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14142 2016-12-002 and as CVE-2016-1254.
14144 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
14145 - Stop a crash that could occur when a client running with DNSPort
14146 received a query with multiple address types, and the first
14147 address type was not supported. Found and fixed by Scott Dial.
14148 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14149 - Prevent a class of security bugs caused by treating the contents
14150 of a buffer chunk as if they were a NUL-terminated string. At
14151 least one such bug seems to be present in all currently used
14152 versions of Tor, and would allow an attacker to remotely crash
14153 most Tor instances, especially those compiled with extra compiler
14154 hardening. With this defense in place, such bugs can't crash Tor,
14155 though we should still fix them as they occur. Closes ticket
14156 20384 (TROVE-2016-10-001).
14158 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
14159 - Avoid a difficult-to-trigger heap corruption attack when extending
14160 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14161 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14162 Reported by Guido Vranken.
14164 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
14165 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14166 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14168 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
14169 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14170 pointer to the previous (uninitialized) key value. The impact here
14171 should be limited to a difficult-to-trigger crash, if OpenSSL is
14172 running an engine that makes key generation failures possible, or
14173 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14174 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14177 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14178 - Fix an integer underflow bug when comparing malformed Tor
14179 versions. This bug could crash Tor when built with
14180 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14181 0.2.9.8, which were built with -ftrapv by default. In other cases
14182 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14183 on 0.0.8pre1. Found by OSS-Fuzz.
14185 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
14186 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14187 zero size. Check size argument to memwipe() for underflow. Fixes
14188 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14191 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
14192 - Make Tor survive errors involving connections without a
14193 corresponding event object. Previously we'd fail with an
14194 assertion; now we produce a log message. Related to bug 16248.
14196 o Minor features (geoip):
14197 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14201 Changes in version 0.2.6.11 - 2017-03-03
14202 Tor 0.2.6.11 backports a number of security fixes from later Tor
14203 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
14204 this release, if for some reason they cannot upgrade to a later
14207 Note that support for Tor 0.2.6.x is ending this year: we will not issue
14208 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
14209 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
14211 o Directory authority changes (backport from 0.2.8.5-rc):
14212 - Urras is no longer a directory authority. Closes ticket 19271.
14214 o Directory authority changes (backport from 0.2.9.2-alpha):
14215 - The "Tonga" bridge authority has been retired; the new bridge
14216 authority is "Bifroest". Closes tickets 19728 and 19690.
14218 o Directory authority key updates (backport from 0.2.8.1-alpha):
14219 - Update the V3 identity key for the dannenberg directory authority:
14220 it was changed on 18 November 2015. Closes task 17906. Patch
14223 o Major features (security fixes, backport from 0.2.9.4-alpha):
14224 - Prevent a class of security bugs caused by treating the contents
14225 of a buffer chunk as if they were a NUL-terminated string. At
14226 least one such bug seems to be present in all currently used
14227 versions of Tor, and would allow an attacker to remotely crash
14228 most Tor instances, especially those compiled with extra compiler
14229 hardening. With this defense in place, such bugs can't crash Tor,
14230 though we should still fix them as they occur. Closes ticket
14231 20384 (TROVE-2016-10-001).
14233 o Major bugfixes (parsing, security, backport from 0.2.9.8):
14234 - Fix a bug in parsing that could cause clients to read a single
14235 byte past the end of an allocated region. This bug could be used
14236 to cause hardened clients (built with --enable-expensive-hardening)
14237 to crash if they tried to visit a hostile hidden service. Non-
14238 hardened clients are only affected depending on the details of
14239 their platform's memory allocator. Fixes bug 21018; bugfix on
14240 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14241 2016-12-002 and as CVE-2016-1254.
14243 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
14244 - Stop a crash that could occur when a client running with DNSPort
14245 received a query with multiple address types, and the first
14246 address type was not supported. Found and fixed by Scott Dial.
14247 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14249 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
14250 - Fix an error that could cause us to read 4 bytes before the
14251 beginning of an openssl string. This bug could be used to cause
14252 Tor to crash on systems with unusual malloc implementations, or
14253 systems with unusual hardening installed. Fixes bug 17404; bugfix
14256 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
14257 - Avoid a difficult-to-trigger heap corruption attack when extending
14258 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14259 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14260 Reported by Guido Vranken.
14262 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
14263 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14264 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14266 o Major bugfixes (guard selection, backport from 0.2.7.6):
14267 - Actually look at the Guard flag when selecting a new directory
14268 guard. When we implemented the directory guard design, we
14269 accidentally started treating all relays as if they have the Guard
14270 flag during guard selection, leading to weaker anonymity and worse
14271 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
14274 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
14275 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14276 pointer to the previous (uninitialized) key value. The impact here
14277 should be limited to a difficult-to-trigger crash, if OpenSSL is
14278 running an engine that makes key generation failures possible, or
14279 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14280 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14283 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14284 - Fix an integer underflow bug when comparing malformed Tor
14285 versions. This bug could crash Tor when built with
14286 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14287 0.2.9.8, which were built with -ftrapv by default. In other cases
14288 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14289 on 0.0.8pre1. Found by OSS-Fuzz.
14291 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
14292 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14293 zero size. Check size argument to memwipe() for underflow. Fixes
14294 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14297 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
14298 - Make Tor survive errors involving connections without a
14299 corresponding event object. Previously we'd fail with an
14300 assertion; now we produce a log message. Related to bug 16248.
14302 o Minor features (geoip):
14303 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14306 o Minor bugfixes (compilation, backport from 0.2.7.6):
14307 - Fix a compilation warning with Clang 3.6: Do not check the
14308 presence of an address which can never be NULL. Fixes bug 17781.
14311 Changes in version 0.2.5.13 - 2017-03-03
14312 Tor 0.2.5.13 backports a number of security fixes from later Tor
14313 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
14314 this release, if for some reason they cannot upgrade to a later
14317 Note that support for Tor 0.2.5.x is ending next year: we will not issue
14318 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
14319 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
14321 o Directory authority changes (backport from 0.2.8.5-rc):
14322 - Urras is no longer a directory authority. Closes ticket 19271.
14324 o Directory authority changes (backport from 0.2.9.2-alpha):
14325 - The "Tonga" bridge authority has been retired; the new bridge
14326 authority is "Bifroest". Closes tickets 19728 and 19690.
14328 o Directory authority key updates (backport from 0.2.8.1-alpha):
14329 - Update the V3 identity key for the dannenberg directory authority:
14330 it was changed on 18 November 2015. Closes task 17906. Patch
14333 o Major features (security fixes, backport from 0.2.9.4-alpha):
14334 - Prevent a class of security bugs caused by treating the contents
14335 of a buffer chunk as if they were a NUL-terminated string. At
14336 least one such bug seems to be present in all currently used
14337 versions of Tor, and would allow an attacker to remotely crash
14338 most Tor instances, especially those compiled with extra compiler
14339 hardening. With this defense in place, such bugs can't crash Tor,
14340 though we should still fix them as they occur. Closes ticket
14341 20384 (TROVE-2016-10-001).
14343 o Major bugfixes (parsing, security, backport from 0.2.9.8):
14344 - Fix a bug in parsing that could cause clients to read a single
14345 byte past the end of an allocated region. This bug could be used
14346 to cause hardened clients (built with --enable-expensive-hardening)
14347 to crash if they tried to visit a hostile hidden service. Non-
14348 hardened clients are only affected depending on the details of
14349 their platform's memory allocator. Fixes bug 21018; bugfix on
14350 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14351 2016-12-002 and as CVE-2016-1254.
14353 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
14354 - Stop a crash that could occur when a client running with DNSPort
14355 received a query with multiple address types, and the first
14356 address type was not supported. Found and fixed by Scott Dial.
14357 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14359 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
14360 - Fix an error that could cause us to read 4 bytes before the
14361 beginning of an openssl string. This bug could be used to cause
14362 Tor to crash on systems with unusual malloc implementations, or
14363 systems with unusual hardening installed. Fixes bug 17404; bugfix
14366 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
14367 - Avoid a difficult-to-trigger heap corruption attack when extending
14368 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14369 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14370 Reported by Guido Vranken.
14372 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
14373 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14374 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14376 o Major bugfixes (guard selection, backport from 0.2.7.6):
14377 - Actually look at the Guard flag when selecting a new directory
14378 guard. When we implemented the directory guard design, we
14379 accidentally started treating all relays as if they have the Guard
14380 flag during guard selection, leading to weaker anonymity and worse
14381 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
14384 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
14385 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14386 pointer to the previous (uninitialized) key value. The impact here
14387 should be limited to a difficult-to-trigger crash, if OpenSSL is
14388 running an engine that makes key generation failures possible, or
14389 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14390 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14393 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14394 - Fix an integer underflow bug when comparing malformed Tor
14395 versions. This bug could crash Tor when built with
14396 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14397 0.2.9.8, which were built with -ftrapv by default. In other cases
14398 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14399 on 0.0.8pre1. Found by OSS-Fuzz.
14401 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
14402 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14403 zero size. Check size argument to memwipe() for underflow. Fixes
14404 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14407 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
14408 - Make Tor survive errors involving connections without a
14409 corresponding event object. Previously we'd fail with an
14410 assertion; now we produce a log message. Related to bug 16248.
14412 o Minor features (geoip):
14413 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14416 o Minor bugfixes (compilation, backport from 0.2.7.6):
14417 - Fix a compilation warning with Clang 3.6: Do not check the
14418 presence of an address which can never be NULL. Fixes bug 17781.
14420 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
14421 - Check for failures from crypto_early_init, and refuse to continue.
14422 A previous typo meant that we could keep going with an
14423 uninitialized crypto library, and would have OpenSSL initialize
14424 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
14425 when implementing ticket 4900. Patch by "teor".
14427 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
14428 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
14429 a client authorized hidden service. Fixes bug 15823; bugfix
14433 Changes in version 0.2.4.28 - 2017-03-03
14434 Tor 0.2.4.28 backports a number of security fixes from later Tor
14435 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
14436 this release, if for some reason they cannot upgrade to a later
14439 Note that support for Tor 0.2.4.x is ending soon: we will not issue
14440 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
14441 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
14443 o Directory authority changes (backport from 0.2.8.5-rc):
14444 - Urras is no longer a directory authority. Closes ticket 19271.
14446 o Directory authority changes (backport from 0.2.9.2-alpha):
14447 - The "Tonga" bridge authority has been retired; the new bridge
14448 authority is "Bifroest". Closes tickets 19728 and 19690.
14450 o Directory authority key updates (backport from 0.2.8.1-alpha):
14451 - Update the V3 identity key for the dannenberg directory authority:
14452 it was changed on 18 November 2015. Closes task 17906. Patch
14455 o Major features (security fixes, backport from 0.2.9.4-alpha):
14456 - Prevent a class of security bugs caused by treating the contents
14457 of a buffer chunk as if they were a NUL-terminated string. At
14458 least one such bug seems to be present in all currently used
14459 versions of Tor, and would allow an attacker to remotely crash
14460 most Tor instances, especially those compiled with extra compiler
14461 hardening. With this defense in place, such bugs can't crash Tor,
14462 though we should still fix them as they occur. Closes ticket
14463 20384 (TROVE-2016-10-001).
14465 o Major bugfixes (parsing, security, backport from 0.2.9.8):
14466 - Fix a bug in parsing that could cause clients to read a single
14467 byte past the end of an allocated region. This bug could be used
14468 to cause hardened clients (built with --enable-expensive-hardening)
14469 to crash if they tried to visit a hostile hidden service. Non-
14470 hardened clients are only affected depending on the details of
14471 their platform's memory allocator. Fixes bug 21018; bugfix on
14472 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14473 2016-12-002 and as CVE-2016-1254.
14475 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
14476 - Fix an error that could cause us to read 4 bytes before the
14477 beginning of an openssl string. This bug could be used to cause
14478 Tor to crash on systems with unusual malloc implementations, or
14479 systems with unusual hardening installed. Fixes bug 17404; bugfix
14482 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
14483 - Avoid a difficult-to-trigger heap corruption attack when extending
14484 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14485 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14486 Reported by Guido Vranken.
14488 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
14489 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14490 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14492 o Major bugfixes (guard selection, backport from 0.2.7.6):
14493 - Actually look at the Guard flag when selecting a new directory
14494 guard. When we implemented the directory guard design, we
14495 accidentally started treating all relays as if they have the Guard
14496 flag during guard selection, leading to weaker anonymity and worse
14497 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
14500 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
14501 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14502 pointer to the previous (uninitialized) key value. The impact here
14503 should be limited to a difficult-to-trigger crash, if OpenSSL is
14504 running an engine that makes key generation failures possible, or
14505 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14506 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14509 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14510 - Fix an integer underflow bug when comparing malformed Tor
14511 versions. This bug could crash Tor when built with
14512 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14513 0.2.9.8, which were built with -ftrapv by default. In other cases
14514 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14515 on 0.0.8pre1. Found by OSS-Fuzz.
14517 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
14518 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14519 zero size. Check size argument to memwipe() for underflow. Fixes
14520 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14523 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
14524 - Make Tor survive errors involving connections without a
14525 corresponding event object. Previously we'd fail with an
14526 assertion; now we produce a log message. Related to bug 16248.
14528 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
14529 - Make it harder for attackers to overload hidden services with
14530 introductions, by blocking multiple introduction requests on the
14531 same circuit. Resolves ticket 15515.
14533 o Minor features (geoip):
14534 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14537 o Minor bugfixes (compilation, backport from 0.2.7.6):
14538 - Fix a compilation warning with Clang 3.6: Do not check the
14539 presence of an address which can never be NULL. Fixes bug 17781.
14541 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
14542 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
14543 a client authorized hidden service. Fixes bug 15823; bugfix
14547 Changes in version 0.3.0.4-rc - 2017-03-01
14548 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
14549 0.3.0 release series, and introduces a few reliability features to
14550 keep them from coming back.
14552 This is the first release candidate in the Tor 0.3.0 series. If we
14553 find no new bugs or regressions here, the first stable 0.3.0 release
14554 will be nearly identical to it.
14556 o Major bugfixes (bridges):
14557 - When the same bridge is configured multiple times with the same
14558 identity, but at different address:port combinations, treat those
14559 bridge instances as separate guards. This fix restores the ability
14560 of clients to configure the same bridge with multiple pluggable
14561 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
14563 o Major bugfixes (hidden service directory v3):
14564 - Stop crashing on a failed v3 hidden service descriptor lookup
14565 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
14567 o Major bugfixes (parsing):
14568 - When parsing a malformed content-length field from an HTTP
14569 message, do not read off the end of the buffer. This bug was a
14570 potential remote denial-of-service attack against Tor clients and
14571 relays. A workaround was released in October 2016, to prevent this
14572 bug from crashing Tor. This is a fix for the underlying issue,
14573 which should no longer matter (if you applied the earlier patch).
14574 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
14575 using AFL (http://lcamtuf.coredump.cx/afl/).
14576 - Fix an integer underflow bug when comparing malformed Tor
14577 versions. This bug could crash Tor when built with
14578 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14579 0.2.9.8, which were built with -ftrapv by default. In other cases
14580 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14581 on 0.0.8pre1. Found by OSS-Fuzz.
14583 o Minor feature (protocol versioning):
14584 - Add new protocol version for proposal 224. HSIntro now advertises
14585 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
14587 o Minor features (directory authorities):
14588 - Directory authorities now reject descriptors that claim to be
14589 malformed versions of Tor. Helps prevent exploitation of
14591 - Reject version numbers with components that exceed INT32_MAX.
14592 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
14593 Fixes bug 21450; bugfix on 0.0.8pre1.
14594 - Directory authorities now reject relays running versions
14595 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
14596 suffer from bug 20499 and don't keep their consensus cache
14597 up-to-date. Resolves ticket 20509.
14599 o Minor features (geoip):
14600 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14603 o Minor features (reliability, crash):
14604 - Try better to detect problems in buffers where they might grow (or
14605 think they have grown) over 2 GB in size. Diagnostic for
14608 o Minor features (testing):
14609 - During 'make test-network-all', if tor logs any warnings, ask
14610 chutney to output them. Requires a recent version of chutney with
14611 the 21572 patch. Implements 21570.
14613 o Minor bugfixes (certificate expiration time):
14614 - Avoid using link certificates that don't become valid till some
14615 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
14617 o Minor bugfixes (code correctness):
14618 - Repair a couple of (unreachable or harmless) cases of the risky
14619 comparison-by-subtraction pattern that caused bug 21278.
14620 - Remove a redundant check for the UseEntryGuards option from the
14621 options_transition_affects_guards() function. Fixes bug 21492;
14622 bugfix on 0.3.0.1-alpha.
14624 o Minor bugfixes (directory mirrors):
14625 - Allow relays to use directory mirrors without a DirPort: these
14626 relays need to be contacted over their ORPorts using a begindir
14627 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
14628 - Clarify the message logged when a remote relay is unexpectedly
14629 missing an ORPort or DirPort: users were confusing this with a
14630 local port. Fixes another case of bug 20711; bugfix
14633 o Minor bugfixes (guards):
14634 - Don't warn about a missing guard state on timeout-measurement
14635 circuits: they aren't supposed to be using guards. Fixes an
14636 instance of bug 21007; bugfix on 0.3.0.1-alpha.
14637 - Silence a BUG() warning when attempting to use a guard whose
14638 descriptor we don't know, and make this scenario less likely to
14639 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
14641 o Minor bugfixes (hidden service):
14642 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
14643 cells. Previously, we were using sizeof() on a pointer, instead of
14644 the real destination buffer. Fortunately, that value was only used
14645 to double-check that there was enough room--which was already
14646 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
14648 o Minor bugfixes (testing):
14649 - Fix Raspbian build issues related to missing socket errno in
14650 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
14652 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
14653 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
14654 - Use bash in src/test/test-network.sh. This ensures we reliably
14655 call chutney's newer tools/test-network.sh when available. Fixes
14656 bug 21562; bugfix on 0.2.9.1-alpha.
14659 - Small fixes to the fuzzing documentation. Closes ticket 21472.
14662 Changes in version 0.2.9.10 - 2017-03-01
14663 Tor 0.2.9.10 backports a security fix from later Tor release. It also
14664 includes fixes for some major issues affecting directory authorities,
14665 LibreSSL compatibility, and IPv6 correctness.
14667 The Tor 0.2.9.x release series is now marked as a long-term-support
14668 series. We intend to backport security fixes to 0.2.9.x until at
14669 least January of 2020.
14671 o Major bugfixes (directory authority, 0.3.0.3-alpha):
14672 - During voting, when marking a relay as a probable sybil, do not
14673 clear its BadExit flag: sybils can still be bad in other ways
14674 too. (We still clear the other flags.) Fixes bug 21108; bugfix
14677 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
14678 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
14679 any IPv6 addresses. Instead, only reject a port over IPv6 if the
14680 exit policy rejects that port on more than an IPv6 /16 of
14681 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
14682 which rejected a relay's own IPv6 address by default. Fixes bug
14683 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
14685 o Major bugfixes (parsing, also in 0.3.0.4-rc):
14686 - Fix an integer underflow bug when comparing malformed Tor
14687 versions. This bug could crash Tor when built with
14688 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14689 0.2.9.8, which were built with -ftrapv by default. In other cases
14690 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14691 on 0.0.8pre1. Found by OSS-Fuzz.
14693 o Minor features (directory authorities, also in 0.3.0.4-rc):
14694 - Directory authorities now reject descriptors that claim to be
14695 malformed versions of Tor. Helps prevent exploitation of
14697 - Reject version numbers with components that exceed INT32_MAX.
14698 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
14699 Fixes bug 21450; bugfix on 0.0.8pre1.
14701 o Minor features (geoip):
14702 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14705 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
14706 - Autoconf now checks to determine if OpenSSL structures are opaque,
14707 instead of explicitly checking for OpenSSL version numbers. Part
14709 - Support building with recent LibreSSL code that uses opaque
14710 structures. Closes ticket 21359.
14712 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
14713 - Repair a couple of (unreachable or harmless) cases of the risky
14714 comparison-by-subtraction pattern that caused bug 21278.
14716 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
14717 - The tor-resolve command line tool now rejects hostnames over 255
14718 characters in length. Previously, it would silently truncate them,
14719 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
14720 Patch by "junglefowl".
14723 Changes in version 0.3.0.3-alpha - 2017-02-03
14724 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
14725 0.3.0.x development series, including some that could cause
14726 authorities to behave badly. There is also a fix for a longstanding
14727 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
14728 includes some smaller features and bugfixes.
14730 The Tor 0.3.0.x release series is now in patch-freeze: no additional
14731 features will be considered for inclusion in 0.3.0.x. We suspect that
14732 some bugs will probably remain, however, and we encourage people to
14735 o Major bugfixes (directory authority):
14736 - During voting, when marking a relay as a probable sybil, do not
14737 clear its BadExit flag: sybils can still be bad in other ways
14738 too. (We still clear the other flags.) Fixes bug 21108; bugfix
14740 - When deciding whether we have just found a router to be reachable,
14741 do not penalize it for not having performed an Ed25519 link
14742 handshake if it does not claim to support an Ed25519 handshake.
14743 Previously, we would treat such relays as non-running. Fixes bug
14744 21107; bugfix on 0.3.0.1-alpha.
14746 o Major bugfixes (entry guards):
14747 - Stop trying to build circuits through entry guards for which we
14748 have no descriptor. Also, stop crashing in the case that we *do*
14749 accidentally try to build a circuit in such a state. Fixes bug
14750 21242; bugfix on 0.3.0.1-alpha.
14752 o Major bugfixes (IPv6 Exits):
14753 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
14754 any IPv6 addresses. Instead, only reject a port over IPv6 if the
14755 exit policy rejects that port on more than an IPv6 /16 of
14756 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
14757 which rejected a relay's own IPv6 address by default. Fixes bug
14758 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
14760 o Minor feature (client):
14761 - Enable IPv6 traffic on the SocksPort by default. To disable this,
14762 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
14764 o Minor feature (fallback scripts):
14765 - Add a check_existing mode to updateFallbackDirs.py, which checks
14766 if fallbacks in the hard-coded list are working. Closes ticket
14767 20174. Patch by haxxpop.
14769 o Minor features (ciphersuite selection):
14770 - Clients now advertise a list of ciphersuites closer to the ones
14771 preferred by Firefox. Closes part of ticket 15426.
14772 - Allow relays to accept a wider range of ciphersuites, including
14773 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
14775 o Minor features (controller, configuration):
14776 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
14777 and so on, now comes with a __*Port variant that will not be saved
14778 to the torrc file by the controller's SAVECONF command. This
14779 change allows TorBrowser to set up a single-use domain socket for
14780 each time it launches Tor. Closes ticket 20956.
14781 - The GETCONF command can now query options that may only be
14782 meaningful in context-sensitive lists. This allows the controller
14783 to query the mixed SocksPort/__SocksPort style options introduced
14784 in feature 20956. Implements ticket 21300.
14786 o Minor features (portability, compilation):
14787 - Autoconf now checks to determine if OpenSSL structures are opaque,
14788 instead of explicitly checking for OpenSSL version numbers. Part
14790 - Support building with recent LibreSSL code that uses opaque
14791 structures. Closes ticket 21359.
14793 o Minor features (relay):
14794 - We now allow separation of exit and relay traffic to different
14795 source IP addresses, using the OutboundBindAddressExit and
14796 OutboundBindAddressOR options respectively. Closes ticket 17975.
14797 Written by Michael Sonntag.
14799 o Minor bugfix (logging):
14800 - Don't recommend the use of Tor2web in non-anonymous mode.
14801 Recommending Tor2web is a bad idea because the client loses all
14802 anonymity. Tor2web should only be used in specific cases by users
14803 who *know* and understand the issues. Fixes bug 21294; bugfix
14806 o Minor bugfixes (client):
14807 - Always recover from failures in extend_info_from_node(), in an
14808 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
14809 bugfix on 0.2.3.1-alpha.
14811 o Minor bugfixes (client, entry guards):
14812 - Fix a bug warning (with backtrace) when we fail a channel that
14813 circuits to fallback directories on it. Fixes bug 21128; bugfix
14815 - Fix a spurious bug warning (with backtrace) when removing an
14816 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
14817 - Fix a bug of the new guard algorithm where tor could stall for up
14818 to 10 minutes before retrying a guard after a long period of no
14819 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
14820 - Do not try to build circuits until we have descriptors for our
14821 primary entry guards. Related to fix for bug 21242.
14823 o Minor bugfixes (configure, autoconf):
14824 - Rename the configure option --enable-expensive-hardening to
14825 --enable-fragile-hardening. Expensive hardening makes the tor
14826 daemon abort when some kinds of issues are detected. Thus, it
14827 makes tor more at risk of remote crashes but safer against RCE or
14828 heartbleed bug category. We now try to explain this issue in a
14829 message from the configure script. Fixes bug 21290; bugfix
14832 o Minor bugfixes (controller):
14833 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
14834 20824; bugfix on 0.3.0.1-alpha.
14836 o Minor bugfixes (hidden service):
14837 - Clean up the code for expiring intro points with no associated
14838 circuits. It was causing, rarely, a service with some expiring
14839 introduction points to not open enough additional introduction
14840 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
14841 - Stop setting the torrc option HiddenServiceStatistics to "0" just
14842 because we're not a bridge or relay. Instead, we preserve whatever
14843 value the user set (or didn't set). Fixes bug 21150; bugfix
14845 - Resolve two possible underflows which could lead to creating and
14846 closing a lot of introduction point circuits in a non-stop loop.
14847 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
14849 o Minor bugfixes (portability):
14850 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
14851 It is supported by OpenBSD itself, and also by most OpenBSD
14852 variants (such as Bitrig). Fixes bug 20980; bugfix
14854 - When mapping a file of length greater than SIZE_MAX, do not
14855 silently truncate its contents. This issue could occur on 32 bit
14856 systems with large file support and files which are larger than 4
14857 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
14859 o Minor bugfixes (tor-resolve):
14860 - The tor-resolve command line tool now rejects hostnames over 255
14861 characters in length. Previously, it would silently truncate them,
14862 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
14863 Patch by "junglefowl".
14865 o Minor bugfixes (Windows services):
14866 - Be sure to initialize the monotonic time subsystem before using
14867 it, even when running as an NT service. Fixes bug 21356; bugfix
14871 Changes in version 0.3.0.2-alpha - 2017-01-23
14872 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
14873 cause relays and clients to crash, even if they were not built with
14874 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
14875 versions, and also affects 0.3.0.1-alpha: all relays running an affected
14876 version should upgrade.
14878 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
14879 time-to-live values, makes directory authorities enforce the 1-to-1
14880 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
14881 client-side onion service reachability bug, does better at selecting
14882 the set of fallback directories, and more.
14884 o Major bugfixes (security, also in 0.2.9.9):
14885 - Downgrade the "-ftrapv" option from "always on" to "only on when
14886 --enable-expensive-hardening is provided." This hardening option, like
14887 others, can turn survivable bugs into crashes--and having it on by
14888 default made a (relatively harmless) integer overflow bug into a
14889 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
14892 o Major features (security):
14893 - Change the algorithm used to decide DNS TTLs on client and server
14894 side, to better resist DNS-based correlation attacks like the
14895 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
14896 Feamster. Now relays only return one of two possible DNS TTL
14897 values, and clients are willing to believe DNS TTL values up to 3
14898 hours long. Closes ticket 19769.
14900 o Major features (directory authority, security):
14901 - The default for AuthDirPinKeys is now 1: directory authorities
14902 will reject relays where the RSA identity key matches a previously
14903 seen value, but the Ed25519 key has changed. Closes ticket 18319.
14905 o Major bugfixes (client, guard, crash):
14906 - In circuit_get_global_origin_list(), return the actual list of
14907 origin circuits. The previous version of this code returned the
14908 list of all the circuits, and could have caused strange bugs,
14909 including possible crashes. Fixes bug 21118; bugfix
14912 o Major bugfixes (client, onion service, also in 0.2.9.9):
14913 - Fix a client-side onion service reachability bug, where multiple
14914 socks requests to an onion service (or a single slow request)
14915 could cause us to mistakenly mark some of the service's
14916 introduction points as failed, and we cache that failure so
14917 eventually we run out and can't reach the service. Also resolves a
14918 mysterious "Remote server sent bogus reason code 65021" log
14919 warning. The bug was introduced in ticket 17218, where we tried to
14920 remember the circuit end reason as a uint16_t, which mangled
14921 negative values. Partially fixes bug 21056 and fixes bug 20307;
14922 bugfix on 0.2.8.1-alpha.
14924 o Major bugfixes (DNS):
14925 - Fix a bug that prevented exit nodes from caching DNS records for
14926 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
14928 o Minor features (controller):
14929 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
14930 shared-random values to the controller. Closes ticket 19925.
14932 o Minor features (entry guards):
14933 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
14934 break regression tests.
14935 - Require UseEntryGuards when UseBridges is set, in order to make
14936 sure bridges aren't bypassed. Resolves ticket 20502.
14938 o Minor features (fallback directories):
14939 - Select 200 fallback directories for each release. Closes
14941 - Allow 3 fallback relays per operator, which is safe now that we
14942 are choosing 200 fallback relays. Closes ticket 20912.
14943 - Exclude relays affected by bug 20499 from the fallback list.
14944 Exclude relays from the fallback list if they are running versions
14945 known to be affected by bug 20499, or if in our tests they deliver
14946 a stale consensus (i.e. one that expired more than 24 hours ago).
14947 Closes ticket 20539.
14948 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
14950 - Require fallback directories to have the same address and port for
14951 7 days (now that we have enough relays with this stability).
14952 Relays whose OnionOO stability timer is reset on restart by bug
14953 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
14954 this issue. Closes ticket 20880; maintains short-term fix
14956 - Require fallbacks to have flags for 90% of the time (weighted
14957 decaying average), rather than 95%. This allows at least 73% of
14958 clients to bootstrap in the first 5 seconds without contacting an
14959 authority. Part of ticket 18828.
14960 - Annotate updateFallbackDirs.py with the bandwidth and consensus
14961 weight for each candidate fallback. Closes ticket 20878.
14962 - Make it easier to change the output sort order of fallbacks.
14963 Closes ticket 20822.
14964 - Display the relay fingerprint when downloading consensuses from
14965 fallbacks. Closes ticket 20908.
14967 o Minor features (geoip, also in 0.2.9.9):
14968 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
14971 o Minor features (next-gen onion service directories):
14972 - Remove the "EnableOnionServicesV3" consensus parameter that we
14973 introduced in 0.3.0.1-alpha: relays are now always willing to act
14974 as v3 onion service directories. Resolves ticket 19899.
14976 o Minor features (linting):
14977 - Enhance the changes file linter to warn on Tor versions that are
14978 prefixed with "tor-". Closes ticket 21096.
14980 o Minor features (logging):
14981 - In several places, describe unset ed25519 keys as "<unset>",
14982 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
14984 o Minor bugfix (control protocol):
14985 - The reply to a "GETINFO config/names" request via the control
14986 protocol now spells the type "Dependent" correctly. This is a
14987 breaking change in the control protocol. (The field seems to be
14988 ignored by the most common known controllers.) Fixes bug 18146;
14989 bugfix on 0.1.1.4-alpha.
14991 o Minor bugfixes (bug resilience):
14992 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
14993 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
14994 Hans Jerry Illikainen.
14996 o Minor bugfixes (build):
14997 - Replace obsolete Autoconf macros with their modern equivalent and
14998 prevent similar issues in the future. Fixes bug 20990; bugfix
15001 o Minor bugfixes (client, guards):
15002 - Fix bug where Tor would think that there are circuits waiting for
15003 better guards even though those circuits have been freed. Fixes
15004 bug 21142; bugfix on 0.3.0.1-alpha.
15006 o Minor bugfixes (config):
15007 - Don't assert on startup when trying to get the options list and
15008 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
15009 options so of course they aren't ready yet. Fixes bug 21062;
15010 bugfix on 0.2.9.3-alpha.
15012 o Minor bugfixes (controller):
15013 - Make the GETINFO interface for inquiring about entry guards
15014 support the new guards backend. Fixes bug 20823; bugfix
15017 o Minor bugfixes (dead code):
15018 - Remove a redundant check for PidFile changes at runtime in
15019 options_transition_allowed(): this check is already performed
15020 regardless of whether the sandbox is active. Fixes bug 21123;
15021 bugfix on 0.2.5.4-alpha.
15023 o Minor bugfixes (documentation):
15024 - Update the tor manual page to document every option that can not
15025 be changed while tor is running. Fixes bug 21122.
15027 o Minor bugfixes (fallback directories):
15028 - Stop failing when a relay has no uptime data in
15029 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
15030 - Avoid checking fallback candidates' DirPorts if they are down in
15031 OnionOO. When a relay operator has multiple relays, this
15032 prioritizes relays that are up over relays that are down. Fixes
15033 bug 20926; bugfix on 0.2.8.3-alpha.
15034 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
15035 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
15037 o Minor bugfixes (guards, bootstrapping):
15038 - When connecting to a directory guard during bootstrap, do not mark
15039 the guard as successful until we receive a good-looking directory
15040 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
15042 o Minor bugfixes (onion services):
15043 - Fix the config reload pruning of old vs new services so it
15044 actually works when both ephemeral and non-ephemeral services are
15045 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
15046 - Allow the number of introduction points to be as low as 0, rather
15047 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
15049 o Minor bugfixes (IPv6):
15050 - Make IPv6-using clients try harder to find an IPv6 directory
15051 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
15052 - When IPv6 addresses have not been downloaded yet (microdesc
15053 consensus documents don't list relay IPv6 addresses), use hard-
15054 coded addresses for authorities, fallbacks, and configured
15055 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
15056 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
15058 o Minor bugfixes (memory leaks):
15059 - Fix a memory leak when configuring hidden services. Fixes bug
15060 20987; bugfix on 0.3.0.1-alpha.
15062 o Minor bugfixes (portability, also in 0.2.9.9):
15063 - Avoid crashing when Tor is built using headers that contain
15064 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
15065 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
15067 - Fix Libevent detection on platforms without Libevent 1 headers
15068 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
15070 o Minor bugfixes (relay):
15071 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
15072 initializing the keys would reset the DataDirectory to 0700
15073 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
15074 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
15076 o Minor bugfixes (testing):
15077 - Remove undefined behavior from the backtrace generator by removing
15078 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
15080 o Minor bugfixes (unit tests):
15081 - Allow the unit tests to pass even when DNS lookups of bogus
15082 addresses do not fail as expected. Fixes bug 20862 and 20863;
15083 bugfix on unit tests introduced in 0.2.8.1-alpha
15084 through 0.2.9.4-alpha.
15086 o Code simplification and refactoring:
15087 - Refactor code to manipulate global_origin_circuit_list into
15088 separate functions. Closes ticket 20921.
15090 o Documentation (formatting):
15091 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
15092 blocks were incorrectly appearing. Closes ticket 20885.
15094 o Documentation (man page):
15095 - Clarify many options in tor.1 and add some min/max values for
15096 HiddenService options. Closes ticket 21058.
15099 Changes in version 0.2.9.9 - 2017-01-23
15100 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
15101 cause relays and clients to crash, even if they were not built with
15102 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
15103 versions, and also affects 0.3.0.1-alpha: all relays running an affected
15104 version should upgrade.
15106 This release also resolves a client-side onion service reachability
15107 bug, and resolves a pair of small portability issues.
15109 o Major bugfixes (security):
15110 - Downgrade the "-ftrapv" option from "always on" to "only on when
15111 --enable-expensive-hardening is provided." This hardening option,
15112 like others, can turn survivable bugs into crashes -- and having
15113 it on by default made a (relatively harmless) integer overflow bug
15114 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
15115 bugfix on 0.2.9.1-alpha.
15117 o Major bugfixes (client, onion service):
15118 - Fix a client-side onion service reachability bug, where multiple
15119 socks requests to an onion service (or a single slow request)
15120 could cause us to mistakenly mark some of the service's
15121 introduction points as failed, and we cache that failure so
15122 eventually we run out and can't reach the service. Also resolves a
15123 mysterious "Remote server sent bogus reason code 65021" log
15124 warning. The bug was introduced in ticket 17218, where we tried to
15125 remember the circuit end reason as a uint16_t, which mangled
15126 negative values. Partially fixes bug 21056 and fixes bug 20307;
15127 bugfix on 0.2.8.1-alpha.
15129 o Minor features (geoip):
15130 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
15133 o Minor bugfixes (portability):
15134 - Avoid crashing when Tor is built using headers that contain
15135 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
15136 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
15138 - Fix Libevent detection on platforms without Libevent 1 headers
15139 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
15142 Changes in version 0.3.0.1-alpha - 2016-12-19
15143 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
15144 series. It strengthens Tor's link and circuit handshakes by
15145 identifying relays by their Ed25519 keys, improves the algorithm that
15146 clients use to choose and maintain their list of guards, and includes
15147 additional backend support for the next-generation hidden service
15148 design. It also contains numerous other small features and
15149 improvements to security, correctness, and performance.
15151 Below are the changes since 0.2.9.8.
15153 o Major features (guard selection algorithm):
15154 - Tor's guard selection algorithm has been redesigned from the
15155 ground up, to better support unreliable networks and restrictive
15156 sets of entry nodes, and to better resist guard-capture attacks by
15157 hostile local networks. Implements proposal 271; closes
15160 o Major features (next-generation hidden services):
15161 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
15162 prop224 aka "Next Generation Hidden Services". Service and clients
15163 don't use this functionality yet. Closes ticket 19043. Based on
15164 initial code by Alec Heifetz.
15165 - Relays now support the HSDir version 3 protocol, so that they can
15166 can store and serve v3 descriptors. This is part of the next-
15167 generation onion service work detailed in proposal 224. Closes
15170 o Major features (protocol, ed25519 identity keys):
15171 - Relays now use Ed25519 to prove their Ed25519 identities and to
15172 one another, and to clients. This algorithm is faster and more
15173 secure than the RSA-based handshake we've been doing until now.
15174 Implements the second big part of proposal 220; Closes
15176 - Clients now support including Ed25519 identity keys in the EXTEND2
15177 cells they generate. By default, this is controlled by a consensus
15178 parameter, currently disabled. You can turn this feature on for
15179 testing by setting ExtendByEd25519ID in your configuration. This
15180 might make your traffic appear different than the traffic
15181 generated by other users, however. Implements part of ticket
15182 15056; part of proposal 220.
15183 - Relays now understand requests to extend to other relays by their
15184 Ed25519 identity keys. When an Ed25519 identity key is included in
15185 an EXTEND2 cell, the relay will only extend the circuit if the
15186 other relay can prove ownership of that identity. Implements part
15187 of ticket 15056; part of proposal 220.
15189 o Major bugfixes (scheduler):
15190 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
15191 caused the channel scheduler to behave more or less randomly,
15192 rather than preferring channels with higher-priority circuits.
15193 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
15195 o Minor features (controller):
15196 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
15197 rather than "unrecognized." Closes ticket 20389; patch from
15200 o Minor features (diagnostic, directory client):
15201 - Warn when we find an unexpected inconsistency in directory
15202 download status objects. Prevents some negative consequences of
15205 o Minor features (directory authority):
15206 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
15207 default) to control whether authorities should try to probe relays
15208 by their Ed25519 link keys. This option will go away in a few
15209 releases--unless we encounter major trouble in our ed25519 link
15210 protocol rollout, in which case it will serve as a safety option.
15212 o Minor features (directory cache):
15213 - Relays and bridges will now refuse to serve the consensus they
15214 have if they know it is too old for a client to use. Closes
15217 o Minor features (ed25519 link handshake):
15218 - Advertise support for the ed25519 link handshake using the
15219 subprotocol-versions mechanism, so that clients can tell which
15220 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
15222 o Minor features (fingerprinting resistance, authentication):
15223 - Extend the length of RSA keys used for TLS link authentication to
15224 2048 bits. (These weren't used for forward secrecy; for forward
15225 secrecy, we used P256.) Closes ticket 13752.
15227 o Minor features (infrastructure):
15228 - Implement smartlist_add_strdup() function. Replaces the use of
15229 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
15231 o Minor bugfixes (client):
15232 - When clients that use bridges start up with a cached consensus on
15233 disk, they were ignoring it and downloading a new one. Now they
15234 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
15236 o Minor bugfixes (configuration):
15237 - Accept non-space whitespace characters after the severity level in
15238 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
15239 - Support "TByte" and "TBytes" units in options given in bytes.
15240 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
15241 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
15243 o Minor bugfixes (consensus weight):
15244 - Add new consensus method that initializes bw weights to 1 instead
15245 of 0. This prevents a zero weight from making it all the way to
15246 the end (happens in small testing networks) and causing an error.
15247 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
15249 o Minor bugfixes (descriptors):
15250 - Correctly recognise downloaded full descriptors as valid, even
15251 when using microdescriptors as circuits. This affects clients with
15252 FetchUselessDescriptors set, and may affect directory authorities.
15253 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
15255 o Minor bugfixes (directory system):
15256 - Download all consensus flavors, descriptors, and authority
15257 certificates when FetchUselessDescriptors is set, regardless of
15258 whether tor is a directory cache or not. Fixes bug 20667; bugfix
15259 on all recent tor versions.
15260 - Bridges and relays now use microdescriptors (like clients do)
15261 rather than old-style router descriptors. Now bridges will blend
15262 in with clients in terms of the circuits they build. Fixes bug
15263 6769; bugfix on 0.2.3.2-alpha.
15265 o Minor bugfixes (ed25519 certificates):
15266 - Correctly interpret ed25519 certificates that would expire some
15267 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
15269 o Minor bugfixes (hidden services):
15270 - Stop ignoring misconfigured hidden services. Instead, refuse to
15271 start tor until the misconfigurations have been corrected. Fixes
15272 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
15275 o Minor bugfixes (memory leak at exit):
15276 - Fix a small harmless memory leak at exit of the previously unused
15277 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
15280 o Minor bugfixes (util):
15281 - When finishing writing a file to disk, if we were about to replace
15282 the file with the temporary file created before and we fail to
15283 replace it, remove the temporary file so it doesn't stay on disk.
15284 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
15286 o Minor bugfixes (Windows):
15287 - Check for getpagesize before using it to mmap files. This fixes
15288 compilation in some MinGW environments. Fixes bug 20530; bugfix on
15289 0.1.2.1-alpha. Reported by "ice".
15291 o Code simplification and refactoring:
15292 - Abolish all global guard context in entrynodes.c; replace with new
15293 guard_selection_t structure as preparation for proposal 271.
15294 Closes ticket 19858.
15295 - Introduce rend_service_is_ephemeral() that tells if given onion
15296 service is ephemeral. Replace unclear NULL-checkings for service
15297 directory with this function. Closes ticket 20526.
15298 - Extract magic numbers in circuituse.c into defined variables.
15299 - Refactor circuit_is_available_for_use to remove unnecessary check.
15300 - Refactor circuit_predict_and_launch_new for readability and
15301 testability. Closes ticket 18873.
15302 - Refactor large if statement in purpose_needs_anonymity to use
15303 switch statement instead. Closes part of ticket 20077.
15304 - Refactor the hashing API to return negative values for errors, as
15305 is done as throughout the codebase. Closes ticket 20717.
15306 - Remove data structures that were used to index or_connection
15307 objects by their RSA identity digests. These structures are fully
15308 redundant with the similar structures used in the
15309 channel abstraction.
15310 - Remove duplicate code in the channel_write_*cell() functions.
15311 Closes ticket 13827; patch from Pingl.
15312 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
15313 use only purpose_needs_anonymity. Closes part of ticket 20077.
15314 - The code to generate and parse EXTEND and EXTEND2 cells has been
15315 replaced with code automatically generated by the
15319 - Include the "TBits" unit in Tor's man page. Fixes part of bug
15320 20622; bugfix on 0.2.5.1-alpha.
15321 - Change '1' to 'weight_scale' in consensus bw weights calculation
15322 comments, as that is reality. Closes ticket 20273. Patch
15324 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
15325 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
15327 - Stop the man page from incorrectly stating that HiddenServiceDir
15328 must already exist. Fixes 20486.
15329 - Clarify that when ClientRejectInternalAddresses is enabled (which
15330 is the default), multicast DNS hostnames for machines on the local
15331 network (of the form *.local) are also rejected. Closes
15334 o Removed features:
15335 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
15336 limit for relays running on a single IP applies to authority IP
15337 addresses as well as to non-authority IP addresses. Closes
15339 - The UseDirectoryGuards torrc option no longer exists: all users
15340 that use entry guards will also use directory guards. Related to
15341 proposal 271; implements part of ticket 20831.
15344 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
15345 from "overcaffeinated".
15346 - Perform the coding style checks when running the tests and fail
15347 when coding style violations are found. Closes ticket 5500.
15348 - Add tests for networkstatus_compute_bw_weights_v10.
15349 - Add unit tests circuit_predict_and_launch_new.
15350 - Extract dummy_origin_circuit_new so it can be used by other
15354 Changes in version 0.2.8.12 - 2016-12-19
15355 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
15356 below) where Tor clients could crash when attempting to visit a
15357 hostile hidden service. Clients are recommended to upgrade as packages
15358 become available for their systems.
15360 It also includes an updated list of fallback directories, backported
15363 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
15364 backported to 0.2.8 in the future.
15366 o Major bugfixes (parsing, security, backported from 0.2.9.8):
15367 - Fix a bug in parsing that could cause clients to read a single
15368 byte past the end of an allocated region. This bug could be used
15369 to cause hardened clients (built with --enable-expensive-hardening)
15370 to crash if they tried to visit a hostile hidden service. Non-
15371 hardened clients are only affected depending on the details of
15372 their platform's memory allocator. Fixes bug 21018; bugfix on
15373 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
15374 2016-12-002 and as CVE-2016-1254.
15376 o Minor features (fallback directory list, backported from 0.2.9.8):
15377 - Replace the 81 remaining fallbacks of the 100 originally
15378 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
15379 fallbacks (123 new, 54 existing, 27 removed) generated in December
15380 2016. Resolves ticket 20170.
15382 o Minor features (geoip, backported from 0.2.9.7-rc):
15383 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
15387 Changes in version 0.2.9.8 - 2016-12-19
15388 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
15390 The Tor 0.2.9 series makes mandatory a number of security features
15391 that were formerly optional. It includes support for a new shared-
15392 randomness protocol that will form the basis for next generation
15393 hidden services, includes a single-hop hidden service mode for
15394 optimizing .onion services that don't actually want to be hidden,
15395 tries harder not to overload the directory authorities with excessive
15396 downloads, and supports a better protocol versioning scheme for
15397 improved compatibility with other implementations of the Tor protocol.
15399 And of course, there are numerous other bugfixes and improvements.
15401 This release also includes a fix for a medium-severity issue (bug
15402 21018 below) where Tor clients could crash when attempting to visit a
15403 hostile hidden service. Clients are recommended to upgrade as packages
15404 become available for their systems.
15406 Below are the changes since 0.2.9.7-rc. For a list of all changes
15407 since 0.2.8, see the ReleaseNotes file.
15409 o Major bugfixes (parsing, security):
15410 - Fix a bug in parsing that could cause clients to read a single
15411 byte past the end of an allocated region. This bug could be used
15412 to cause hardened clients (built with --enable-expensive-hardening)
15413 to crash if they tried to visit a hostile hidden service. Non-
15414 hardened clients are only affected depending on the details of
15415 their platform's memory allocator. Fixes bug 21018; bugfix on
15416 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
15417 2016-12-002 and as CVE-2016-1254.
15419 o Minor features (fallback directory list):
15420 - Replace the 81 remaining fallbacks of the 100 originally
15421 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
15422 fallbacks (123 new, 54 existing, 27 removed) generated in December
15423 2016. Resolves ticket 20170.
15426 Changes in version 0.2.9.7-rc - 2016-12-12
15427 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
15428 including a few that had prevented tests from passing on
15431 o Minor features (geoip):
15432 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
15435 o Minor bugfix (build):
15436 - The current Git revision when building from a local repository is
15437 now detected correctly when using git worktrees. Fixes bug 20492;
15438 bugfix on 0.2.3.9-alpha.
15440 o Minor bugfixes (directory authority):
15441 - When computing old Tor protocol line version in protover, we were
15442 looking at 0.2.7.5 twice instead of a specific case for
15443 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
15445 o Minor bugfixes (download scheduling):
15446 - Resolve a "bug" warning when considering a download schedule whose
15447 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
15449 o Minor bugfixes (logging):
15450 - Downgrade a harmless log message about the
15451 pending_entry_connections list from "warn" to "info". Mitigates
15454 o Minor bugfixes (memory leak):
15455 - Fix a small memory leak when receiving AF_UNIX connections on a
15456 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
15457 - When moving a signed descriptor object from a source to an
15458 existing destination, free the allocated memory inside that
15459 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
15461 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
15462 - Fix a memory leak and use-after-free error when removing entries
15463 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
15464 0.2.5.5-alpha. Patch from "cypherpunks".
15466 o Minor bugfixes (portability):
15467 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
15468 Fixes bug 20935; bugfix on 0.2.9.6-rc.
15470 o Minor bugfixes (unit tests):
15471 - Stop expecting NetBSD unit tests to report success for ipfw. Part
15472 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
15473 - Fix tolerances in unit tests for monotonic time comparisons
15474 between nanoseconds and microseconds. Previously, we accepted a 10
15475 us difference only, which is not realistic on every platform's
15476 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
15477 - Remove a double-free in the single onion service unit test. Stop
15478 ignoring a return value. Make future changes less error-prone.
15479 Fixes bug 20864; bugfix on 0.2.9.6-rc.
15482 Changes in version 0.2.8.11 - 2016-12-08
15483 Tor 0.2.8.11 backports fixes for additional portability issues that
15484 could prevent Tor from building correctly on OSX Sierra, or with
15485 OpenSSL 1.1. Affected users should upgrade; others can safely stay
15488 o Minor bugfixes (portability):
15489 - Avoid compilation errors when building on OSX Sierra. Sierra began
15490 to support the getentropy() and clock_gettime() APIs, but created
15491 a few problems in doing so. Tor 0.2.9 has a more thorough set of
15492 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
15493 monotonic time interfaces. Fixes bug 20865. Bugfix
15496 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
15497 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
15498 architectures. Closes ticket 20588.
15501 Changes in version 0.2.8.10 - 2016-12-02
15502 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
15503 unusable after they left standby mode. It also backports fixes for
15504 a few portability issues and a small but problematic memory leak.
15506 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
15507 - When Tor leaves standby because of a new application request, open
15508 circuits as needed to serve that request. Previously, we would
15509 potentially wait a very long time. Fixes part of bug 19969; bugfix
15512 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
15513 - Clients now respond to new application stream requests immediately
15514 when they arrive, rather than waiting up to one second before
15515 starting to handle them. Fixes part of bug 19969; bugfix
15518 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
15519 - Work around a bug in the OSX 10.12 SDK that would prevent us from
15520 successfully targeting earlier versions of OSX. Resolves
15523 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
15524 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
15525 20551; bugfix on 0.2.1.1-alpha.
15527 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
15528 - Work around a memory leak in OpenSSL 1.1 when encoding public
15529 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
15531 o Minor features (geoip):
15532 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
15535 Changes in version 0.2.9.6-rc - 2016-12-02
15536 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
15537 version. We hope that it will be ready to become stable soon, and we
15538 encourage everyone to test this release. If no showstopper bugs are
15539 found here, the next 0.2.9 release will be stable.
15541 o Major bugfixes (relay, resolver, logging):
15542 - For relays that don't know their own address, avoid attempting a
15543 local hostname resolve for each descriptor we download. This
15544 will cut down on the number of "Success: chose address 'x.x.x.x'"
15545 log lines, and also avoid confusing clock jumps if the resolver
15546 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
15548 o Minor bugfixes (client, fascistfirewall):
15549 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
15550 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
15552 o Minor bugfixes (hidden services):
15553 - Stop ignoring the anonymity status of saved keys for hidden
15554 services and single onion services when first starting tor.
15555 Instead, refuse to start tor if any hidden service key has been
15556 used in a different hidden service anonymity mode. Fixes bug
15557 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
15559 o Minor bugfixes (portability):
15560 - Work around a bug in the OSX 10.12 SDK that would prevent us from
15561 successfully targeting earlier versions of OSX. Resolves
15563 - Run correctly when built on Windows build environments that
15564 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
15566 o Minor bugfixes (single onion services, Tor2web):
15567 - Stop complaining about long-term one-hop circuits deliberately
15568 created by single onion services and Tor2web. These log messages
15569 are intended to diagnose issue 8387, which relates to circuits
15570 hanging around forever for no reason. Fixes bug 20613; bugfix on
15571 0.2.9.1-alpha. Reported by "pastly".
15573 o Minor bugfixes (unit tests):
15574 - Stop spurious failures in the local interface address discovery
15575 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
15579 - Correct the minimum bandwidth value in torrc.sample, and queue a
15580 corresponding change for torrc.minimal. Closes ticket 20085.
15583 Changes in version 0.2.9.5-alpha - 2016-11-08
15584 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
15585 version. We believe one or two probably remain, and we encourage
15586 everyone to test this release.
15588 o Major bugfixes (client performance):
15589 - Clients now respond to new application stream requests immediately
15590 when they arrive, rather than waiting up to one second before
15591 starting to handle them. Fixes part of bug 19969; bugfix
15594 o Major bugfixes (client reliability):
15595 - When Tor leaves standby because of a new application request, open
15596 circuits as needed to serve that request. Previously, we would
15597 potentially wait a very long time. Fixes part of bug 19969; bugfix
15600 o Major bugfixes (download scheduling):
15601 - When using an exponential backoff schedule, do not give up on
15602 downloading just because we have failed a bunch of times. Since
15603 each delay is longer than the last, retrying indefinitely won't
15604 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
15605 - If a consensus expires while we are waiting for certificates to
15606 download, stop waiting for certificates.
15607 - If we stop waiting for certificates less than a minute after we
15608 started downloading them, do not consider the certificate download
15609 failure a separate failure. Fixes bug 20533; bugfix
15611 - Remove the maximum delay on exponential-backoff scheduling. Since
15612 we now allow an infinite number of failures (see ticket 20536), we
15613 must now allow the time to grow longer on each failure. Fixes part
15614 of bug 20534; bugfix on 0.2.9.1-alpha.
15615 - Make our initial download delays closer to those from 0.2.8. Fixes
15616 another part of bug 20534; bugfix on 0.2.9.1-alpha.
15617 - When determining when to download a directory object, handle times
15618 after 2038 if the operating system supports them. (Someday this
15619 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
15620 - When using exponential backoff in test networks, use a lower
15621 exponent, so the delays do not vary as much. This helps test
15622 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
15624 o Minor features (geoip):
15625 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
15628 o Minor bugfixes (client directory scheduling):
15629 - Treat "relay too busy to answer request" as a failed request and a
15630 reason to back off on our retry frequency. This is safe now that
15631 exponential backoffs retry indefinitely, and avoids a bug where we
15632 would reset our download schedule erroneously. Fixes bug 20593;
15633 bugfix on 0.2.9.1-alpha.
15635 o Minor bugfixes (client, logging):
15636 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
15637 assume all nodes support EXTEND2. Use ntor whenever a key is
15638 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
15639 - On DNSPort, stop logging a BUG warning on a failed hostname
15640 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
15642 o Minor bugfixes (hidden services):
15643 - When configuring hidden services, check every hidden service
15644 directory's permissions. Previously, we only checked the last
15645 hidden service. Fixes bug 20529; bugfix the work to fix 13942
15648 o Minor bugfixes (portability):
15649 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
15650 architectures. Closes ticket 20588.
15651 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
15652 removed the ECDH ciphers which caused the tests to fail on
15653 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
15654 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
15655 20551; bugfix on 0.2.1.1-alpha.
15657 o Minor bugfixes (relay bootstrap):
15658 - Ensure relays don't make multiple connections during bootstrap.
15659 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
15661 o Minor bugfixes (relay):
15662 - Work around a memory leak in OpenSSL 1.1 when encoding public
15663 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
15664 - Avoid a small memory leak when informing worker threads about
15665 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
15666 - Do not try to parallelize workers more than 16x without the user
15667 explicitly configuring us to do so, even if we do detect more than
15668 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
15670 o Minor bugfixes (single onion services):
15671 - Start correctly when creating a single onion service in a
15672 directory that did not previously exist. Fixes bug 20484; bugfix
15675 o Minor bugfixes (testing):
15676 - Avoid a unit test failure on systems with over 16 detectable CPU
15677 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
15680 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
15681 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
15682 - Module-level documentation for several more modules. Closes
15683 tickets 19287 and 19290.
15686 Changes in version 0.2.8.9 - 2016-10-17
15687 Tor 0.2.8.9 backports a fix for a security hole in previous versions
15688 of Tor that would allow a remote attacker to crash a Tor client,
15689 hidden service, relay, or authority. All Tor users should upgrade to
15690 this version, or to 0.2.9.4-alpha. Patches will be released for older
15693 o Major features (security fixes, also in 0.2.9.4-alpha):
15694 - Prevent a class of security bugs caused by treating the contents
15695 of a buffer chunk as if they were a NUL-terminated string. At
15696 least one such bug seems to be present in all currently used
15697 versions of Tor, and would allow an attacker to remotely crash
15698 most Tor instances, especially those compiled with extra compiler
15699 hardening. With this defense in place, such bugs can't crash Tor,
15700 though we should still fix them as they occur. Closes ticket
15701 20384 (TROVE-2016-10-001).
15703 o Minor features (geoip):
15704 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
15708 Changes in version 0.2.9.4-alpha - 2016-10-17
15709 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
15710 that would allow a remote attacker to crash a Tor client, hidden
15711 service, relay, or authority. All Tor users should upgrade to this
15712 version, or to 0.2.8.9. Patches will be released for older versions
15715 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
15716 previous versions of Tor, including the implementation of a feature to
15717 future- proof the Tor ecosystem against protocol changes, some bug
15718 fixes necessary for Tor Browser to use unix domain sockets correctly,
15719 and several portability improvements. We anticipate that this will be
15720 the last alpha in the Tor 0.2.9 series, and that the next release will
15721 be a release candidate.
15723 o Major features (security fixes):
15724 - Prevent a class of security bugs caused by treating the contents
15725 of a buffer chunk as if they were a NUL-terminated string. At
15726 least one such bug seems to be present in all currently used
15727 versions of Tor, and would allow an attacker to remotely crash
15728 most Tor instances, especially those compiled with extra compiler
15729 hardening. With this defense in place, such bugs can't crash Tor,
15730 though we should still fix them as they occur. Closes ticket
15731 20384 (TROVE-2016-10-001).
15733 o Major features (subprotocol versions):
15734 - Tor directory authorities now vote on a set of recommended
15735 subprotocol versions, and on a set of required subprotocol
15736 versions. Clients and relays that lack support for a _required_
15737 subprotocol version will not start; those that lack support for a
15738 _recommended_ subprotocol version will warn the user to upgrade.
15739 Closes ticket 19958; implements part of proposal 264.
15740 - Tor now uses "subprotocol versions" to indicate compatibility.
15741 Previously, versions of Tor looked at the declared Tor version of
15742 a relay to tell whether they could use a given feature. Now, they
15743 should be able to rely on its declared subprotocol versions. This
15744 change allows compatible implementations of the Tor protocol(s) to
15745 exist without pretending to be 100% bug-compatible with particular
15746 releases of Tor itself. Closes ticket 19958; implements part of
15749 o Minor feature (fallback directories):
15750 - Remove broken fallbacks from the hard-coded fallback directory
15751 list. Closes ticket 20190; patch by teor.
15753 o Minor features (client, directory):
15754 - Since authorities now omit all routers that lack the Running and
15755 Valid flags, we assume that any relay listed in the consensus must
15756 have those flags. Closes ticket 20001; implements part of
15759 o Minor features (compilation, portability):
15760 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
15763 o Minor features (development tools, etags):
15764 - Teach the "make tags" Makefile target how to correctly find
15765 "MOCK_IMPL" function definitions. Patch from nherring; closes
15768 o Minor features (geoip):
15769 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
15772 o Minor features (unix domain sockets):
15773 - When configuring a unix domain socket for a SocksPort,
15774 ControlPort, or Hidden service, you can now wrap the address in
15775 quotes, using C-style escapes inside the quotes. This allows unix
15776 domain socket paths to contain spaces.
15778 o Minor features (virtual addresses):
15779 - Increase the maximum number of bits for the IPv6 virtual network
15780 prefix from 16 to 104. In this way, the condition for address
15781 allocation is less restrictive. Closes ticket 20151; feature
15784 o Minor bugfixes (address discovery):
15785 - Stop reordering IP addresses returned by the OS. This makes it
15786 more likely that Tor will guess the same relay IP address every
15787 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
15788 Reported by René Mayrhofer, patch by "cypherpunks".
15790 o Minor bugfixes (client, unix domain sockets):
15791 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
15792 the client address is meaningless. Fixes bug 20261; bugfix
15795 o Minor bugfixes (compilation, OpenBSD):
15796 - Detect Libevent2 functions correctly on systems that provide
15797 libevent2, but where libevent1 is linked with -levent. Fixes bug
15798 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
15800 o Minor bugfixes (configuration):
15801 - When parsing quoted configuration values from the torrc file,
15802 handle windows line endings correctly. Fixes bug 19167; bugfix on
15803 0.2.0.16-alpha. Patch from "Pingl".
15805 o Minor bugfixes (getpass):
15806 - Defensively fix a non-triggerable heap corruption at do_getpass()
15807 to protect ourselves from mistakes in the future. Fixes bug
15808 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
15811 o Minor bugfixes (hidden service):
15812 - Allow hidden services to run on IPv6 addresses even when the
15813 IPv6Exit option is not set. Fixes bug 18357; bugfix
15817 - Add module-level internal documentation for 36 C files that
15818 previously didn't have a high-level overview. Closes ticket #20385.
15820 o Required libraries:
15821 - When building with OpenSSL, Tor now requires version 1.0.1 or
15822 later. OpenSSL 1.0.0 and earlier are no longer supported by the
15823 OpenSSL team, and should not be used. Closes ticket 20303.
15826 Changes in version 0.2.9.3-alpha - 2016-09-23
15827 Tor 0.2.9.3-alpha adds improved support for entities that want to make
15828 high-performance services available through the Tor .onion mechanism
15829 without themselves receiving anonymity as they host those services. It
15830 also tries harder to ensure that all steps on a circuit are using the
15831 strongest crypto possible, strengthens some TLS properties, and
15832 resolves several bugs -- including a pair of crash bugs from the 0.2.8
15833 series. Anybody running an earlier version of 0.2.9.x should upgrade.
15835 o Major bugfixes (crash, also in 0.2.8.8):
15836 - Fix a complicated crash bug that could affect Tor clients
15837 configured to use bridges when replacing a networkstatus consensus
15838 in which one of their bridges was mentioned. OpenBSD users saw
15839 more crashes here, but all platforms were potentially affected.
15840 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
15842 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
15843 - Fix a timing-dependent assertion failure that could occur when we
15844 tried to flush from a circuit after having freed its cells because
15845 of an out-of-memory condition. Fixes bug 20203; bugfix on
15846 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
15849 o Major features (circuit building, security):
15850 - Authorities, relays and clients now require ntor keys in all
15851 descriptors, for all hops (except for rare hidden service protocol
15852 cases), for all circuits, and for all other roles. Part of
15854 - Tor authorities, relays, and clients only use ntor, except for
15855 rare cases in the hidden service protocol. Part of ticket 19163.
15857 o Major features (single-hop "hidden" services):
15858 - Add experimental HiddenServiceSingleHopMode and
15859 HiddenServiceNonAnonymousMode options. When both are set to 1,
15860 every hidden service on a Tor instance becomes a non-anonymous
15861 Single Onion Service. Single Onions make one-hop (direct)
15862 connections to their introduction and rendezvous points. One-hop
15863 circuits make Single Onion servers easily locatable, but clients
15864 remain location-anonymous. This is compatible with the existing
15865 hidden service implementation, and works on the current tor
15866 network without any changes to older relays or clients. Implements
15867 proposal 260, completes ticket 17178. Patch by teor and asn.
15869 o Major features (resource management):
15870 - Tor can now notice it is about to run out of sockets, and
15871 preemptively close connections of lower priority. (This feature is
15872 off by default for now, since the current prioritizing method is
15873 yet not mature enough. You can enable it by setting
15874 "DisableOOSCheck 0", but watch out: it might close some sockets
15875 you would rather have it keep.) Closes ticket 18640.
15877 o Major bugfixes (circuit building):
15878 - Hidden service client-to-intro-point and service-to-rendezvous-
15879 point circuits use the TAP key supplied by the protocol, to avoid
15880 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
15882 o Major bugfixes (compilation, OpenBSD):
15883 - Fix a Libevent-detection bug in our autoconf script that would
15884 prevent Tor from linking successfully on OpenBSD. Patch from
15885 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
15887 o Major bugfixes (hidden services):
15888 - Clients now require hidden services to include the TAP keys for
15889 their intro points in the hidden service descriptor. This prevents
15890 an inadvertent upgrade to ntor, which a malicious hidden service
15891 could use to distinguish clients by consensus version. Fixes bug
15892 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
15894 o Minor features (security, TLS):
15895 - Servers no longer support clients that without AES ciphersuites.
15896 (3DES is no longer considered an acceptable cipher.) We believe
15897 that no such Tor clients currently exist, since Tor has required
15898 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
15900 o Minor feature (fallback directories):
15901 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
15902 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
15903 2016. Closes ticket 20190; patch by teor.
15905 o Minor features (geoip, also in 0.2.8.8):
15906 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
15909 o Minor feature (port flags):
15910 - Add new flags to the *Port options to finer control over which
15911 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
15912 and the synthetic flag OnionTrafficOnly, which is equivalent to
15913 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
15914 18693; patch by "teor".
15916 o Minor features (directory authority):
15917 - After voting, if the authorities decide that a relay is not
15918 "Valid", they no longer include it in the consensus at all. Closes
15919 ticket 20002; implements part of proposal 272.
15921 o Minor features (testing):
15922 - Disable memory protections on OpenBSD when performing our unit
15923 tests for memwipe(). The test deliberately invokes undefined
15924 behavior, and the OpenBSD protections interfere with this. Patch
15925 from "rubiate". Closes ticket 20066.
15927 o Minor features (testing, ipv6):
15928 - Add the single-onion and single-onion-ipv6 chutney targets to
15929 "make test-network-all". This requires a recent chutney version
15930 with the single onion network flavours (git c72a652 or later).
15931 Closes ticket 20072; patch by teor.
15932 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
15933 tests. Remove bridges+hs, as it's somewhat redundant. This
15934 requires a recent chutney version that supports IPv6 clients,
15935 relays, and authorities. Closes ticket 20069; patch by teor.
15937 o Minor features (Tor2web):
15938 - Make Tor2web clients respect ReachableAddresses. This feature was
15939 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
15940 0.2.8.7. Implements feature 20034. Patch by teor.
15942 o Minor features (unit tests):
15943 - We've done significant work to make the unit tests run faster.
15944 - Our link-handshake unit tests now check that when invalid
15945 handshakes fail, they fail with the error messages we expected.
15946 - Our unit testing code that captures log messages no longer
15947 prevents them from being written out if the user asked for them
15948 (by passing --debug or --info or or --notice --warn to the "test"
15949 binary). This change prevents us from missing unexpected log
15950 messages simply because we were looking for others. Related to
15952 - The unit tests now log all warning messages with the "BUG" flag.
15953 Previously, they only logged errors by default. This change will
15954 help us make our testing code more correct, and make sure that we
15955 only hit this code when we mean to. In the meantime, however,
15956 there will be more warnings in the unit test logs than before.
15957 This is preparatory work for ticket 19999.
15958 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
15959 assertion as a test failure.
15961 o Minor bug fixes (circuits):
15962 - Use the CircuitBuildTimeout option whenever
15963 LearnCircuitBuildTimeout is disabled. Previously, we would respect
15964 the option when a user disabled it, but not when it was disabled
15965 because some other option was set. Fixes bug 20073; bugfix on
15966 0.2.4.12-alpha. Patch by teor.
15968 o Minor bugfixes (allocation):
15969 - Change how we allocate memory for large chunks on buffers, to
15970 avoid a (currently impossible) integer overflow, and to waste less
15971 space when allocating unusually large chunks. Fixes bug 20081;
15972 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
15973 - Always include orconfig.h before including any other C headers.
15974 Sometimes, it includes macros that affect the behavior of the
15975 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
15976 first version to use AC_USE_SYSTEM_EXTENSIONS).
15977 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
15978 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
15979 Patch from Gisle Vanem.
15980 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
15981 They apparently require a set of annotations that we aren't
15982 currently using, and they create false positives in our pthreads
15983 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
15985 o Minor bugfixes (directory authority):
15986 - Die with a more useful error when the operator forgets to place
15987 the authority_signing_key file into the keys directory. This
15988 avoids an uninformative assert & traceback about having an invalid
15989 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
15990 - When allowing private addresses, mark Exits that only exit to
15991 private locations as such. Fixes bug 20064; bugfix
15994 o Minor bugfixes (documentation):
15995 - Document the default PathsNeededToBuildCircuits value that's used
15996 by clients when the directory authorities don't set
15997 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
15998 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
15999 - Fix manual for the User option: it takes a username, not a UID.
16000 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
16003 o Minor bugfixes (hidden services):
16004 - Stop logging intro point details to the client log on certain
16005 error conditions. Fixed as part of bug 20012; bugfix on
16006 0.2.4.8-alpha. Patch by teor.
16008 o Minor bugfixes (IPv6, testing):
16009 - Check for IPv6 correctly on Linux when running test networks.
16010 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
16012 o Minor bugfixes (Linux seccomp2 sandbox):
16013 - Add permission to run the sched_yield() and sigaltstack() system
16014 calls, in order to support versions of Tor compiled with asan or
16015 ubsan code that use these calls. Now "sandbox 1" and
16016 "--enable-expensive-hardening" should be compatible on more
16017 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
16019 o Minor bugfixes (logging):
16020 - When logging a message from the BUG() macro, be explicit about
16021 what we were asserting. Previously we were confusing what we were
16022 asserting with what the bug was. Fixes bug 20093; bugfix
16024 - When we are unable to remove the bw_accounting file, do not warn
16025 if the reason we couldn't remove it was that it didn't exist.
16026 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
16028 o Minor bugfixes (option parsing):
16029 - Count unix sockets when counting client listeners (SOCKS, Trans,
16030 NATD, and DNS). This has no user-visible behaviour changes: these
16031 options are set once, and never read. Required for correct
16032 behaviour in ticket 17178. Fixes bug 19677; bugfix on
16033 0.2.6.3-alpha. Patch by teor.
16035 o Minor bugfixes (options):
16036 - Check the consistency of UseEntryGuards and EntryNodes more
16037 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
16039 - Stop changing the configured value of UseEntryGuards on
16040 authorities and Tor2web clients. Fixes bug 20074; bugfix on
16041 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
16044 o Minor bugfixes (Tor2web):
16045 - Prevent Tor2web clients running hidden services, these services
16046 are not anonymous due to the one-hop client paths. Fixes bug
16047 19678. Patch by teor.
16049 o Minor bugfixes (unit tests):
16050 - Fix a shared-random unit test that was failing on big endian
16051 architectures due to internal representation of a integer copied
16052 to a buffer. The test is changed to take a full 32 bytes of data
16053 and use the output of a python script that make the COMMIT and
16054 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
16056 - The tor_tls_server_info_callback unit test no longer crashes when
16057 debug-level logging is turned on. Fixes bug 20041; bugfix
16061 Changes in version 0.2.8.8 - 2016-09-23
16062 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
16063 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
16064 who select public relays as their bridges.
16066 o Major bugfixes (crash):
16067 - Fix a complicated crash bug that could affect Tor clients
16068 configured to use bridges when replacing a networkstatus consensus
16069 in which one of their bridges was mentioned. OpenBSD users saw
16070 more crashes here, but all platforms were potentially affected.
16071 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
16073 o Major bugfixes (relay, OOM handler):
16074 - Fix a timing-dependent assertion failure that could occur when we
16075 tried to flush from a circuit after having freed its cells because
16076 of an out-of-memory condition. Fixes bug 20203; bugfix on
16077 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
16080 o Minor feature (fallback directories):
16081 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
16082 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
16083 2016. Closes ticket 20190; patch by teor.
16085 o Minor features (geoip):
16086 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
16090 Changes in version 0.2.9.2-alpha - 2016-08-24
16091 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
16092 several new features and bugfixes. It also includes an important
16093 authority update and an important bugfix from 0.2.8.7. Everyone who
16094 sets the ReachableAddresses option, and all bridges, are strongly
16095 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
16097 o Directory authority changes (also in 0.2.8.7):
16098 - The "Tonga" bridge authority has been retired; the new bridge
16099 authority is "Bifroest". Closes tickets 19728 and 19690.
16101 o Major bugfixes (client, security, also in 0.2.8.7):
16102 - Only use the ReachableAddresses option to restrict the first hop
16103 in a path. In earlier versions of 0.2.8.x, it would apply to
16104 every hop in the path, with a possible degradation in anonymity
16105 for anyone using an uncommon ReachableAddress setting. Fixes bug
16106 19973; bugfix on 0.2.8.2-alpha.
16108 o Major features (user interface):
16109 - Tor now supports the ability to declare options deprecated, so
16110 that we can recommend that people stop using them. Previously,
16111 this was done in an ad-hoc way. Closes ticket 19820.
16113 o Major bugfixes (directory downloads):
16114 - Avoid resetting download status for consensuses hourly, since we
16115 already have another, smarter retry mechanism. Fixes bug 8625;
16116 bugfix on 0.2.0.9-alpha.
16118 o Minor features (config):
16119 - Warn users when descriptor and port addresses are inconsistent.
16120 Mitigates bug 13953; patch by teor.
16122 o Minor features (geoip):
16123 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
16126 o Minor features (user interface):
16127 - There is a new --list-deprecated-options command-line option to
16128 list all of the deprecated options. Implemented as part of
16131 o Minor bugfixes (code style):
16132 - Fix an integer signedness conversion issue in the case conversion
16133 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
16135 o Minor bugfixes (compilation):
16136 - Build correctly on versions of libevent2 without support for
16137 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
16139 - Fix a compilation warning on GCC versions before 4.6. Our
16140 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
16141 when it is also required as an argument to the compiler pragma.
16142 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
16144 o Minor bugfixes (compilation, also in 0.2.8.7):
16145 - Remove an inappropriate "inline" in tortls.c that was causing
16146 warnings on older versions of GCC. Fixes bug 19903; bugfix
16149 o Minor bugfixes (fallback directories, also in 0.2.8.7):
16150 - Avoid logging a NULL string pointer when loading fallback
16151 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
16152 and 0.2.8.1-alpha. Report and patch by "rubiate".
16154 o Minor bugfixes (logging):
16155 - Log a more accurate message when we fail to dump a microdescriptor.
16156 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
16158 o Minor bugfixes (memory leak):
16159 - Fix a series of slow memory leaks related to parsing torrc files
16160 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
16162 o Deprecated features:
16163 - A number of DNS-cache-related sub-options for client ports are now
16164 deprecated for security reasons, and may be removed in a future
16165 version of Tor. (We believe that client-side DNS caching is a bad
16166 idea for anonymity, and you should not turn it on.) The options
16167 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
16168 UseIPv4Cache, and UseIPv6Cache.
16169 - A number of options are deprecated for security reasons, and may
16170 be removed in a future version of Tor. The options are:
16171 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
16172 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
16173 CloseHSClientCircuitsImmediatelyOnTimeout,
16174 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
16175 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
16176 UseNTorHandshake, and WarnUnsafeSocks.
16177 - The *ListenAddress options are now deprecated as unnecessary: the
16178 corresponding *Port options should be used instead. These options
16179 may someday be removed. The affected options are:
16180 ControlListenAddress, DNSListenAddress, DirListenAddress,
16181 NATDListenAddress, ORListenAddress, SocksListenAddress,
16182 and TransListenAddress.
16185 - Correct the IPv6 syntax in our documentation for the
16186 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
16189 - We no longer include the (dead, deprecated) bufferevent code in
16190 Tor. Closes ticket 19450. Based on a patch from U+039b.
16193 Changes in version 0.2.8.7 - 2016-08-24
16194 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
16195 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
16196 who sets the ReachableAddresses option, and all bridges, are strongly
16197 encouraged to upgrade.
16199 o Directory authority changes:
16200 - The "Tonga" bridge authority has been retired; the new bridge
16201 authority is "Bifroest". Closes tickets 19728 and 19690.
16203 o Major bugfixes (client, security):
16204 - Only use the ReachableAddresses option to restrict the first hop
16205 in a path. In earlier versions of 0.2.8.x, it would apply to
16206 every hop in the path, with a possible degradation in anonymity
16207 for anyone using an uncommon ReachableAddress setting. Fixes bug
16208 19973; bugfix on 0.2.8.2-alpha.
16210 o Minor features (geoip):
16211 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
16214 o Minor bugfixes (compilation):
16215 - Remove an inappropriate "inline" in tortls.c that was causing
16216 warnings on older versions of GCC. Fixes bug 19903; bugfix
16219 o Minor bugfixes (fallback directories):
16220 - Avoid logging a NULL string pointer when loading fallback
16221 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
16222 and 0.2.8.1-alpha. Report and patch by "rubiate".
16225 Changes in version 0.2.9.1-alpha - 2016-08-08
16226 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
16227 series. It improves our support for hardened builds and compiler
16228 warnings, deploys some critical infrastructure for improvements to
16229 hidden services, includes a new timing backend that we hope to use for
16230 better support for traffic padding, makes it easier for programmers to
16231 log unexpected events, and contains other small improvements to
16232 security, correctness, and performance.
16234 Below are the changes since 0.2.8.6.
16236 o New system requirements:
16237 - Tor now requires Libevent version 2.0.10-stable or later. Older
16238 versions of Libevent have less efficient backends for several
16239 platforms, and lack the DNS code that we use for our server-side
16240 DNS support. This implements ticket 19554.
16241 - Tor now requires zlib version 1.2 or later, for security,
16242 efficiency, and (eventually) gzip support. (Back when we started,
16243 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
16244 released in 2003. We recommend the latest version.)
16246 o Major features (build, hardening):
16247 - Tor now builds with -ftrapv by default on compilers that support
16248 it. This option detects signed integer overflow (which C forbids),
16249 and turns it into a hard-failure. We do not apply this option to
16250 code that needs to run in constant time to avoid side-channels;
16251 instead, we use -fwrapv in that code. Closes ticket 17983.
16252 - When --enable-expensive-hardening is selected, stop applying the
16253 clang/gcc sanitizers to code that needs to run in constant time.
16254 Although we are aware of no introduced side-channels, we are not
16255 able to prove that there are none. Related to ticket 17983.
16257 o Major features (compilation):
16258 - Our big list of extra GCC warnings is now enabled by default when
16259 building with GCC (or with anything like Clang that claims to be
16260 GCC-compatible). To make all warnings into fatal compilation
16261 errors, pass --enable-fatal-warnings to configure. Closes
16263 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
16264 turn on C and POSIX extensions. (Previously, we attempted to do
16265 this on an ad hoc basis.) Closes ticket 19139.
16267 o Major features (directory authorities, hidden services):
16268 - Directory authorities can now perform the shared randomness
16269 protocol specified by proposal 250. Using this protocol, directory
16270 authorities generate a global fresh random value every day. In the
16271 future, this value will be used by hidden services to select
16272 HSDirs. This release implements the directory authority feature;
16273 the hidden service side will be implemented in the future as part
16274 of proposal 224. Resolves ticket 16943; implements proposal 250.
16276 o Major features (downloading, random exponential backoff):
16277 - When we fail to download an object from a directory service, wait
16278 for an (exponentially increasing) randomized amount of time before
16279 retrying, rather than a fixed interval as we did before. This
16280 prevents a group of Tor instances from becoming too synchronized,
16281 or a single Tor instance from becoming too predictable, in its
16282 download schedule. Closes ticket 15942.
16284 o Major bugfixes (exit policies):
16285 - Avoid disclosing exit outbound bind addresses, configured port
16286 bind addresses, and local interface addresses in relay descriptors
16287 by default under ExitPolicyRejectPrivate. Instead, only reject
16288 these (otherwise unlisted) addresses if
16289 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
16290 0.2.7.2-alpha. Patch by teor.
16292 o Major bugfixes (hidden service client):
16293 - Allow Tor clients with appropriate controllers to work with
16294 FetchHidServDescriptors set to 0. Previously, this option also
16295 disabled descriptor cache lookup, thus breaking hidden services
16296 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
16298 o Minor features (build, hardening):
16299 - Detect and work around a libclang_rt problem that would prevent
16300 clang from finding __mulodi4() on some 32-bit platforms, and thus
16301 keep -ftrapv from linking on those systems. Closes ticket 19079.
16302 - When building on a system without runtime support for the runtime
16303 hardening options, try to log a useful warning at configuration
16304 time, rather than an incomprehensible warning at link time. If
16305 expensive hardening was requested, this warning becomes an error.
16306 Closes ticket 18895.
16308 o Minor features (code safety):
16309 - In our integer-parsing functions, ensure that maxiumum value we
16310 give is no smaller than the minimum value. Closes ticket 19063;
16313 o Minor features (controller):
16314 - Implement new GETINFO queries for all downloads that use
16315 download_status_t to schedule retries. This allows controllers to
16316 examine the schedule for pending downloads. Closes ticket 19323.
16317 - Allow controllers to configure basic client authorization on
16318 hidden services when they create them with the ADD_ONION control
16319 command. Implements ticket 15588. Patch by "special".
16320 - Fire a STATUS_SERVER controller event whenever the hibernation
16321 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
16323 o Minor features (directory authority):
16324 - Directory authorities now only give the Guard flag to a relay if
16325 they are also giving it the Stable flag. This change allows us to
16326 simplify path selection for clients. It should have minimal effect
16327 in practice, since >99% of Guards already have the Stable flag.
16328 Implements ticket 18624.
16329 - Directory authorities now write their v3-status-votes file out to
16330 disk earlier in the consensus process, so we have a record of the
16331 votes even if we abort the consensus process. Resolves
16334 o Minor features (hidden service):
16335 - Stop being so strict about the payload length of "rendezvous1"
16336 cells. We used to be locked in to the "TAP" handshake length, and
16337 now we can handle better handshakes like "ntor". Resolves
16340 o Minor features (infrastructure, time):
16341 - Tor now uses the operating system's monotonic timers (where
16342 available) for internal fine-grained timing. Previously we would
16343 look at the system clock, and then attempt to compensate for the
16344 clock running backwards. Closes ticket 18908.
16345 - Tor now includes an improved timer backend, so that we can
16346 efficiently support tens or hundreds of thousands of concurrent
16347 timers, as will be needed for some of our planned anti-traffic-
16348 analysis work. This code is based on William Ahern's "timeout.c"
16349 project, which implements a "tickless hierarchical timing wheel".
16350 Closes ticket 18365.
16352 o Minor features (logging):
16353 - Provide a more useful warning message when configured with an
16354 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
16355 - When dumping unparseable router descriptors, optionally store them
16356 in separate files, named by digest, up to a configurable size
16357 limit. You can change the size limit by setting the
16358 MaxUnparseableDescSizeToLog option, and disable this feature by
16359 setting that option to 0. Closes ticket 18322.
16360 - Add a set of macros to check nonfatal assertions, for internal
16361 use. Migrating more of our checks to these should help us avoid
16362 needless crash bugs. Closes ticket 18613.
16364 o Minor features (performance):
16365 - Change the "optimistic data" extension from "off by default" to
16366 "on by default". The default was ordinarily overridden by a
16367 consensus option, but when clients were bootstrapping for the
16368 first time, they would not have a consensus to get the option
16369 from. Changing this default saves a round-trip during startup.
16370 Closes ticket 18815.
16372 o Minor features (relay, usability):
16373 - When the directory authorities refuse a bad relay's descriptor,
16374 encourage the relay operator to contact us. Many relay operators
16375 won't notice this line in their logs, but it's a win if even a few
16376 learn why we don't like what their relay was doing. Resolves
16379 o Minor features (testing):
16380 - Let backtrace tests work correctly under AddressSanitizer. Fixes
16381 part of bug 18934; bugfix on 0.2.5.2-alpha.
16382 - Move the test-network.sh script to chutney, and modify tor's test-
16383 network.sh to call the (newer) chutney version when available.
16384 Resolves ticket 19116. Patch by teor.
16385 - Use the lcov convention for marking lines as unreachable, so that
16386 we don't count them when we're generating test coverage data.
16387 Update our coverage tools to understand this convention. Closes
16390 o Minor bugfixes (bootstrap):
16391 - Remember the directory we fetched the consensus or previous
16392 certificates from, and use it to fetch future authority
16393 certificates. This change improves bootstrapping performance.
16394 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
16396 o Minor bugfixes (build):
16397 - The test-stem and test-network makefile targets now depend only on
16398 the tor binary that they are testing. Previously, they depended on
16399 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
16400 patch from "cypherpunks".
16402 o Minor bugfixes (circuits):
16403 - Make sure extend_info_from_router() is only called on servers.
16404 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
16406 o Minor bugfixes (compilation):
16407 - When building with Clang, use a full set of GCC warnings.
16408 (Previously, we included only a subset, because of the way we
16409 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
16411 o Minor bugfixes (directory authority):
16412 - Authorities now sort the "package" lines in their votes, for ease
16413 of debugging. (They are already sorted in consensus documents.)
16414 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
16415 - When parsing a detached signature, make sure we use the length of
16416 the digest algorithm instead of an hardcoded DIGEST256_LEN in
16417 order to avoid comparing bytes out-of-bounds with a smaller digest
16418 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
16420 o Minor bugfixes (documentation):
16421 - Document the --passphrase-fd option in the tor manpage. Fixes bug
16422 19504; bugfix on 0.2.7.3-rc.
16423 - Fix the description of the --passphrase-fd option in the
16424 tor-gencert manpage. The option is used to pass the number of a
16425 file descriptor to read the passphrase from, not to read the file
16426 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
16428 o Minor bugfixes (ephemeral hidden service):
16429 - When deleting an ephemeral hidden service, close its intro points
16430 even if they are not completely open. Fixes bug 18604; bugfix
16433 o Minor bugfixes (guard selection):
16434 - Use a single entry guard even if the NumEntryGuards consensus
16435 parameter is not provided. Fixes bug 17688; bugfix
16437 - Don't mark guards as unreachable if connection_connect() fails.
16438 That function fails for local reasons, so it shouldn't reveal
16439 anything about the status of the guard. Fixes bug 14334; bugfix
16442 o Minor bugfixes (hidden service client):
16443 - Increase the minimum number of internal circuits we preemptively
16444 build from 2 to 3, so a circuit is available when a client
16445 connects to another onion service. Fixes bug 13239; bugfix
16448 o Minor bugfixes (logging):
16449 - When logging a directory ownership mismatch, log the owning
16450 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
16452 o Minor bugfixes (memory leaks):
16453 - Fix a small, uncommon memory leak that could occur when reading a
16454 truncated ed25519 key file. Fixes bug 18956; bugfix
16457 o Minor bugfixes (testing):
16458 - Allow clients to retry HSDirs much faster in test networks. Fixes
16459 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
16460 - Disable ASAN's detection of segmentation faults while running
16461 test_bt.sh, so that we can make sure that our own backtrace
16462 generation code works. Fixes another aspect of bug 18934; bugfix
16463 on 0.2.5.2-alpha. Patch from "cypherpunks".
16464 - Fix the test-network-all target on out-of-tree builds by using the
16465 correct path to the test driver script. Fixes bug 19421; bugfix
16468 o Minor bugfixes (time):
16469 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
16470 bugfix on all released tor versions.
16471 - When computing the difference between two times in milliseconds,
16472 we now round to the nearest millisecond correctly. Previously, we
16473 could sometimes round in the wrong direction. Fixes bug 19428;
16474 bugfix on 0.2.2.2-alpha.
16476 o Minor bugfixes (user interface):
16477 - Display a more accurate number of suppressed messages in the log
16478 rate-limiter. Previously, there was a potential integer overflow
16479 in the counter. Now, if the number of messages hits a maximum, the
16480 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
16482 - Fix a typo in the passphrase prompt for the ed25519 identity key.
16483 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
16485 o Code simplification and refactoring:
16486 - Remove redundant declarations of the MIN macro. Closes
16488 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
16489 Closes ticket 18462; patch from "icanhasaccount".
16490 - Split the 600-line directory_handle_command_get function into
16491 separate functions for different URL types. Closes ticket 16698.
16494 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
16495 ticket 19153. Patch from "U+039b".
16497 o Removed features:
16498 - Remove support for "GET /tor/bytes.txt" DirPort request, and
16499 "GETINFO dir-usage" controller request, which were only available
16500 via a compile-time option in Tor anyway. Feature was added in
16501 0.2.2.1-alpha. Resolves ticket 19035.
16502 - There is no longer a compile-time option to disable support for
16503 TransPort. (If you don't want TransPort; just don't use it.) Patch
16504 from "U+039b". Closes ticket 19449.
16507 - Run more workqueue tests as part of "make check". These had
16508 previously been implemented, but you needed to know special
16509 command-line options to enable them.
16510 - We now have unit tests for our code to reject zlib "compression
16511 bombs". (Fortunately, the code works fine.)
16514 Changes in version 0.2.8.6 - 2016-08-02
16516 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
16518 The Tor 0.2.8 series improves client bootstrapping performance,
16519 completes the authority-side implementation of improved identity
16520 keys for relays, and includes numerous bugfixes and performance
16521 improvements throughout the program. This release continues to
16522 improve the coverage of Tor's test suite. For a full list of
16523 changes since Tor 0.2.7, see the ReleaseNotes file.
16525 Changes since 0.2.8.5-rc:
16527 o Minor features (geoip):
16528 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
16531 o Minor bugfixes (compilation):
16532 - Fix a compilation warning in the unit tests on systems where char
16533 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
16535 o Minor bugfixes (fallback directories):
16536 - Remove 1 fallback that was on the hardcoded list, then opted-out,
16537 leaving 89 of the 100 fallbacks originally introduced in Tor
16538 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
16540 o Minor bugfixes (Linux seccomp2 sandbox):
16541 - Allow more syscalls when running with "Sandbox 1" enabled:
16542 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
16543 some systems, these are required for Tor to start. Fixes bug
16544 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
16545 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
16546 so that get_interface_address6_via_udp_socket_hack() can work.
16547 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
16550 Changes in version 0.2.8.5-rc - 2016-07-07
16551 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
16552 series. If we find no new bugs or regressions here, the first stable
16553 0.2.8 release will be identical to it. It has a few small bugfixes
16554 against previous versions.
16556 o Directory authority changes:
16557 - Urras is no longer a directory authority. Closes ticket 19271.
16559 o Major bugfixes (heartbeat):
16560 - Fix a regression that would crash Tor when the periodic
16561 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
16562 0.2.8.1-alpha. Reported by "kubaku".
16564 o Minor features (build):
16565 - Tor now again builds with the recent OpenSSL 1.1 development
16566 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
16567 - When building manual pages, set the timezone to "UTC", so that the
16568 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
16569 Patch from intrigeri.
16571 o Minor bugfixes (fallback directory selection):
16572 - Avoid errors during fallback selection if there are no eligible
16573 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
16576 o Minor bugfixes (IPv6, microdescriptors):
16577 - Don't check node addresses when we only have a routerstatus. This
16578 allows IPv6-only clients to bootstrap by fetching microdescriptors
16579 from fallback directory mirrors. (The microdescriptor consensus
16580 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
16583 o Minor bugfixes (logging):
16584 - Reduce pointlessly verbose log messages when directory servers
16585 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
16586 0.2.8.1-alpha. Patch by teor.
16587 - When a fallback directory changes its fingerprint from the hard-
16588 coded fingerprint, log a less severe, more explanatory log
16589 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
16591 o Minor bugfixes (Linux seccomp2 sandboxing):
16592 - Allow statistics to be written to disk when "Sandbox 1" is
16593 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
16594 0.2.6.1-alpha respectively.
16596 o Minor bugfixes (user interface):
16597 - Remove a warning message "Service [scrubbed] not found after
16598 descriptor upload". This message appears when one uses HSPOST
16599 control command to upload a service descriptor. Since there is
16600 only a descriptor and no service, showing this message is
16601 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
16603 o Fallback directory list:
16604 - Add a comment to the generated fallback directory list that
16605 explains how to comment out unsuitable fallbacks in a way that's
16606 compatible with the stem fallback parser.
16607 - Update fallback whitelist and blacklist based on relay operator
16608 emails. Blacklist unsuitable (non-working, over-volatile)
16609 fallbacks. Resolves ticket 19071. Patch by teor.
16610 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
16611 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
16612 ticket 19071; patch by teor.
16615 Changes in version 0.2.8.4-rc - 2016-06-15
16616 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
16617 If we find no new bugs or regressions here, the first stable 0.2.8
16618 release will be identical to it. It has a few small bugfixes against
16621 o Major bugfixes (user interface):
16622 - Correctly give a warning in the cases where a relay is specified
16623 by nickname, and one such relay is found, but it is not officially
16624 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
16626 o Minor features (build):
16627 - Tor now builds once again with the recent OpenSSL 1.1 development
16628 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
16630 o Minor features (geoip):
16631 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
16634 o Minor bugfixes (compilation):
16635 - Cause the unit tests to compile correctly on mingw64 versions that
16636 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
16638 o Minor bugfixes (downloading):
16639 - Predict more correctly whether we'll be downloading over HTTP when
16640 we determine the maximum length of a URL. This should avoid a
16641 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
16645 Changes in version 0.2.8.3-alpha - 2016-05-26
16646 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
16647 the course of the 0.2.8 development cycle. It improves the behavior of
16648 directory clients, fixes several crash bugs, fixes a gap in compiler
16649 hardening, and allows the full integration test suite to run on
16652 o Major bugfixes (security, client, DNS proxy):
16653 - Stop a crash that could occur when a client running with DNSPort
16654 received a query with multiple address types, and the first
16655 address type was not supported. Found and fixed by Scott Dial.
16656 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
16658 o Major bugfixes (security, compilation):
16659 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
16660 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
16661 cause a compiler warning, thereby making other checks fail, and
16662 needlessly disabling compiler-hardening support. Fixes one case of
16663 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
16665 o Major bugfixes (security, directory authorities):
16666 - Fix a crash and out-of-bounds write during authority voting, when
16667 the list of relays includes duplicate ed25519 identity keys. Fixes
16668 bug 19032; bugfix on 0.2.8.2-alpha.
16670 o Major bugfixes (client, bootstrapping):
16671 - Check if bootstrap consensus downloads are still needed when the
16672 linked connection attaches. This prevents tor making unnecessary
16673 begindir-style connections, which are the only directory
16674 connections tor clients make since the fix for 18483 was merged.
16675 - Fix some edge cases where consensus download connections may not
16676 have been closed, even though they were not needed. Related to fix
16678 - Make relays retry consensus downloads the correct number of times,
16679 rather than the more aggressive client retry count. Fixes part of
16681 - Stop downloading consensuses when we have a consensus, even if we
16682 don't have all the certificates for it yet. Fixes bug 18809;
16683 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
16685 o Major bugfixes (directory mirrors):
16686 - Decide whether to advertise begindir support in the the same way
16687 we decide whether to advertise our DirPort. Allowing these
16688 decisions to become out-of-sync led to surprising behavior like
16689 advertising begindir support when hibernation made us not
16690 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
16693 o Major bugfixes (IPv6 bridges, client):
16694 - Actually use IPv6 addresses when selecting directory addresses for
16695 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
16698 o Major bugfixes (key management):
16699 - If OpenSSL fails to generate an RSA key, do not retain a dangling
16700 pointer to the previous (uninitialized) key value. The impact here
16701 should be limited to a difficult-to-trigger crash, if OpenSSL is
16702 running an engine that makes key generation failures possible, or
16703 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
16704 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
16707 o Major bugfixes (testing):
16708 - Fix a bug that would block 'make test-network-all' on systems where
16709 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
16710 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
16711 bugfix on 0.2.8.1-alpha.
16713 o Minor features (clients):
16714 - Make clients, onion services, and bridge relays always use an
16715 encrypted begindir connection for directory requests. Resolves
16716 ticket 18483. Patch by "teor".
16718 o Minor features (fallback directory mirrors):
16719 - Give each fallback the same weight for client selection; restrict
16720 fallbacks to one per operator; report fallback directory detail
16721 changes when rebuilding list; add new fallback directory mirrors
16722 to the whitelist; and many other minor simplifications and fixes.
16723 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
16724 0.2.8.1-alpha; patch by "teor".
16725 - Replace the 21 fallbacks generated in January 2016 and included in
16726 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
16727 2016. Closes task 17158; patch by "teor".
16729 o Minor features (geoip):
16730 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
16733 o Minor bugfixes (assert, portability):
16734 - Fix an assertion failure in memarea.c on systems where "long" is
16735 shorter than the size of a pointer. Fixes bug 18716; bugfix
16738 o Minor bugfixes (bootstrap):
16739 - Consistently use the consensus download schedule for authority
16740 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
16742 o Minor bugfixes (build):
16743 - Remove a pair of redundant AM_CONDITIONAL declarations from
16744 configure.ac. Fixes one final case of bug 17744; bugfix
16746 - Resolve warnings when building on systems that are concerned with
16747 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
16749 - When libscrypt.h is found, but no libscrypt library can be linked,
16750 treat libscrypt as absent. Fixes bug 19161; bugfix
16753 o Minor bugfixes (client):
16754 - Turn all TestingClientBootstrap* into non-testing torrc options.
16755 This changes simply renames them by removing "Testing" in front of
16756 them and they do not require TestingTorNetwork to be enabled
16757 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
16758 - Make directory node selection more reliable, mainly for IPv6-only
16759 clients and clients with few reachable addresses. Fixes bug 18929;
16760 bugfix on 0.2.8.1-alpha. Patch by "teor".
16762 o Minor bugfixes (controller, microdescriptors):
16763 - Make GETINFO dir/status-vote/current/consensus conform to the
16764 control specification by returning "551 Could not open cached
16765 consensus..." when not caching consensuses. Fixes bug 18920;
16766 bugfix on 0.2.2.6-alpha.
16768 o Minor bugfixes (crypto, portability):
16769 - The SHA3 and SHAKE routines now produce the correct output on Big
16770 Endian systems. No code calls either algorithm yet, so this is
16771 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
16772 - Tor now builds again with the recent OpenSSL 1.1 development
16773 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
16776 o Minor bugfixes (directories):
16777 - When fetching extrainfo documents, compare their SHA256 digests
16778 and Ed25519 signing key certificates with the routerinfo that led
16779 us to fetch them, rather than with the most recent routerinfo.
16780 Otherwise we generate many spurious warnings about mismatches.
16781 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
16783 o Minor bugfixes (logging):
16784 - When we can't generate a signing key because OfflineMasterKey is
16785 set, do not imply that we should have been able to load it. Fixes
16786 bug 18133; bugfix on 0.2.7.2-alpha.
16787 - Stop periodic_event_dispatch() from blasting twelve lines per
16788 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
16789 - When rejecting a misformed INTRODUCE2 cell, only log at
16790 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
16792 o Minor bugfixes (pluggable transports):
16793 - Avoid reporting a spurious error when we decide that we don't need
16794 to terminate a pluggable transport because it has already exited.
16795 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
16797 o Minor bugfixes (pointer arithmetic):
16798 - Fix a bug in memarea_alloc() that could have resulted in remote
16799 heap write access, if Tor had ever passed an unchecked size to
16800 memarea_alloc(). Fortunately, all the sizes we pass to
16801 memarea_alloc() are pre-checked to be less than 128 kilobytes.
16802 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
16805 o Minor bugfixes (relays):
16806 - Consider more config options when relays decide whether to
16807 regenerate their descriptor. Fixes more of bug 12538; bugfix
16809 - Resolve some edge cases where we might launch an ORPort
16810 reachability check even when DisableNetwork is set. Noticed while
16811 fixing bug 18616; bugfix on 0.2.3.9-alpha.
16813 o Minor bugfixes (statistics):
16814 - We now include consensus downloads via IPv6 in our directory-
16815 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
16817 o Minor bugfixes (testing):
16818 - Allow directories in small networks to bootstrap by skipping
16819 DirPort checks when the consensus has no exits. Fixes bug 19003;
16820 bugfix on 0.2.8.1-alpha. Patch by teor.
16821 - Fix a small memory leak that would occur when the
16822 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
16823 bugfix on 0.2.5.2-alpha.
16825 o Minor bugfixes (time handling):
16826 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
16827 field. Otherwise, our unit tests crash on Windows. Fixes bug
16828 18977; bugfix on 0.2.2.25-alpha.
16831 - Document the contents of the 'datadir/keys' subdirectory in the
16832 manual page. Closes ticket 17621.
16833 - Stop recommending use of nicknames to identify relays in our
16834 MapAddress documentation. Closes ticket 18312.
16837 Changes in version 0.2.8.2-alpha - 2016-03-28
16838 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
16839 bugs in earlier versions of Tor, including some that prevented
16840 authorities using Tor 0.2.7.x from running correctly. IPv6 and
16841 directory support should also be much improved.
16843 o New system requirements:
16844 - Tor no longer supports versions of OpenSSL with a broken
16845 implementation of counter mode. (This bug was present in OpenSSL
16846 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
16847 longer runs with, these versions.
16848 - Tor no longer attempts to support platforms where the "time_t"
16849 type is unsigned. (To the best of our knowledge, only OpenVMS does
16850 this, and Tor has never actually built on OpenVMS.) Closes
16852 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
16853 later (released in 2008 and 2009 respectively). If you are
16854 building Tor from the git repository instead of from the source
16855 distribution, and your tools are older than this, you will need to
16856 upgrade. Closes ticket 17732.
16858 o Major bugfixes (security, pointers):
16859 - Avoid a difficult-to-trigger heap corruption attack when extending
16860 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
16861 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
16862 Reported by Guido Vranken.
16864 o Major bugfixes (bridges, pluggable transports):
16865 - Modify the check for OR connections to private addresses. Allow
16866 bridges on private addresses, including pluggable transports that
16867 ignore the (potentially private) address in the bridge line. Fixes
16868 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
16870 o Major bugfixes (compilation):
16871 - Repair hardened builds under the clang compiler. Previously, our
16872 use of _FORTIFY_SOURCE would conflict with clang's address
16873 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
16875 o Major bugfixes (crash on shutdown):
16876 - Correctly handle detaching circuits from muxes when shutting down.
16877 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
16878 - Fix an assert-on-exit bug related to counting memory usage in
16879 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
16881 o Major bugfixes (crash on startup):
16882 - Fix a segfault during startup: If a Unix domain socket was
16883 configured as listener (such as a ControlSocket or a SocksPort
16884 "unix:" socket), and tor was started as root but not configured to
16885 switch to another user, tor would segfault while trying to string
16886 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
16889 o Major bugfixes (dns proxy mode, crash):
16890 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
16891 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
16893 o Major bugfixes (relays, bridge clients):
16894 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
16895 bridge clients use the address configured in the bridge line.
16896 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
16899 o Major bugfixes (voting):
16900 - Actually enable support for authorities to match routers by their
16901 Ed25519 identities. Previously, the code had been written, but
16902 some debugging code that had accidentally been left in the
16903 codebase made it stay turned off. Fixes bug 17702; bugfix
16905 - When collating votes by Ed25519 identities, authorities now
16906 include a "NoEdConsensus" flag if the ed25519 value (or lack
16907 thereof) for a server does not reflect the majority consensus.
16908 Related to bug 17668; bugfix on 0.2.7.2-alpha.
16909 - When generating a vote with keypinning disabled, never include two
16910 entries for the same ed25519 identity. This bug was causing
16911 authorities to generate votes that they could not parse when a
16912 router violated key pinning by changing its RSA identity but
16913 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
16914 18318. Bugfix on 0.2.7.2-alpha.
16916 o Minor features (security, win32):
16917 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
16918 attack. Fixes bug 18123; bugfix on all tor versions. Patch
16921 o Minor features (bug-resistance):
16922 - Make Tor survive errors involving connections without a
16923 corresponding event object. Previously we'd fail with an
16924 assertion; now we produce a log message. Related to bug 16248.
16926 o Minor features (build):
16927 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
16928 as having possible IPFW support. Closes ticket 18448. Patch from
16929 Steven Chamberlain.
16931 o Minor features (code hardening):
16932 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
16933 level code, to harden against accidental failures to NUL-
16934 terminate. Part of ticket 17852. Patch from jsturgix. Found
16937 o Minor features (crypto):
16938 - Validate the hard-coded Diffie-Hellman parameters and ensure that
16939 p is a safe prime, and g is a suitable generator. Closes
16942 o Minor features (geoip):
16943 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
16946 o Minor features (hidden service directory):
16947 - Streamline relay-side hsdir handling: when relays consider whether
16948 to accept an uploaded hidden service descriptor, they no longer
16949 check whether they are one of the relays in the network that is
16950 "supposed" to handle that descriptor. Implements ticket 18332.
16952 o Minor features (IPv6):
16953 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
16954 to 1, tor prefers IPv6 directory addresses.
16955 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
16956 avoids using IPv4 for client OR and directory connections.
16957 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
16958 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
16959 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
16961 o Minor features (linux seccomp2 sandbox):
16962 - Reject attempts to change our Address with "Sandbox 1" enabled.
16963 Changing Address with Sandbox turned on would never actually work,
16964 but previously it would fail in strange and confusing ways. Found
16965 while fixing 18548.
16967 o Minor features (robustness):
16968 - Exit immediately with an error message if the code attempts to use
16969 Libevent without having initialized it. This should resolve some
16970 frequently-made mistakes in our unit tests. Closes ticket 18241.
16972 o Minor features (unix domain sockets):
16973 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
16974 Unix domain sockets without checking the permissions on the parent
16975 directory. (Tor checks permissions by default because some
16976 operating systems only check permissions on the parent directory.
16977 However, some operating systems do look at permissions on the
16978 socket, and tor's default check is unneeded.) Closes ticket 18458.
16981 o Minor bugfixes (exit policies, security):
16982 - Refresh an exit relay's exit policy when interface addresses
16983 change. Previously, tor only refreshed the exit policy when the
16984 configured external address changed. Fixes bug 18208; bugfix on
16985 0.2.7.3-rc. Patch by teor.
16987 o Minor bugfixes (security, hidden services):
16988 - Prevent hidden services connecting to client-supplied rendezvous
16989 addresses that are reserved as internal or multicast. Fixes bug
16990 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
16992 o Minor bugfixes (build):
16993 - Do not link the unit tests against both the testing and non-
16994 testing versions of the static libraries. Fixes bug 18490; bugfix
16996 - Avoid spurious failures from configure files related to calling
16997 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
16998 0.2.0.1-alpha. Patch from "cypherpunks".
16999 - Silence spurious clang-scan warnings in the ed25519_donna code by
17000 explicitly initializing some objects. Fixes bug 18384; bugfix on
17001 0.2.7.2-alpha. Patch by teor.
17003 o Minor bugfixes (client, bootstrap):
17004 - Count receipt of new microdescriptors as progress towards
17005 bootstrapping. Previously, with EntryNodes set, Tor might not
17006 successfully repopulate the guard set on bootstrapping. Fixes bug
17007 16825; bugfix on 0.2.3.1-alpha.
17009 o Minor bugfixes (code correctness):
17010 - Update to the latest version of Trunnel, which tries harder to
17011 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
17012 by clang address sanitizer. Fixes bug 18373; bugfix
17015 o Minor bugfixes (configuration):
17016 - Fix a tiny memory leak when parsing a port configuration ending in
17017 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
17019 o Minor bugfixes (containers):
17020 - If we somehow attempt to construct a heap with more than
17021 1073741822 elements, avoid an integer overflow when maintaining
17022 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
17024 o Minor bugfixes (correctness):
17025 - Fix a bad memory handling bug that would occur if we had queued a
17026 cell on a channel's incoming queue. Fortunately, we can't actually
17027 queue a cell like that as our code is constructed today, but it's
17028 best to avoid this kind of error, even if there isn't any code
17029 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
17031 o Minor bugfixes (directory):
17032 - When generating a URL for a directory server on an IPv6 address,
17033 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
17034 on 0.2.3.9-alpha. Patch from Malek.
17036 o Minor bugfixes (fallback directory mirrors):
17037 - When requesting extrainfo descriptors from a trusted directory
17038 server, check whether it is an authority or a fallback directory
17039 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
17040 0.2.4.7-alpha. Reported by atagar, patch by teor.
17042 o Minor bugfixes (hidden service, client):
17043 - Handle the case where the user makes several fast consecutive
17044 requests to the same .onion address. Previously, the first six
17045 requests would each trigger a descriptor fetch, each picking a
17046 directory (there are 6 overall) and the seventh one would fail
17047 because no directories were left, thereby triggering a close on
17048 all current directory connections asking for the hidden service.
17049 The solution here is to not close the connections if we have
17050 pending directory fetches. Fixes bug 15937; bugfix
17053 o Minor bugfixes (hidden service, control port):
17054 - Add the onion address to the HS_DESC event for the UPLOADED action
17055 both on success or failure. It was previously hardcoded with
17056 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
17058 o Minor bugfixes (hidden service, directory):
17059 - Bridges now refuse "rendezvous2" (hidden service descriptor)
17060 publish attempts. Suggested by ticket 18332.
17062 o Minor bugfixes (linux seccomp2 sandbox):
17063 - Allow the setrlimit syscall, and the prlimit and prlimit64
17064 syscalls, which some libc implementations use under the hood.
17065 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
17066 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
17067 enabled and no DNS resolvers configured. This should help TAILS
17068 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
17069 - Fix the sandbox's interoperability with unix domain sockets under
17070 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
17072 o Minor bugfixes (logging):
17073 - When logging information about an unparsable networkstatus vote or
17074 consensus, do not say "vote" when we mean consensus. Fixes bug
17075 18368; bugfix on 0.2.0.8-alpha.
17076 - Scrub service name in "unrecognized service ID" log messages.
17077 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
17078 - Downgrade logs and backtraces about IP versions to info-level.
17079 Only log backtraces once each time tor runs. Assists in diagnosing
17080 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
17081 Christian, patch by teor.
17083 o Minor bugfixes (memory safety):
17084 - Avoid freeing an uninitialized pointer when opening a socket fails
17085 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
17086 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
17088 - Correctly duplicate addresses in get_interface_address6_list().
17089 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
17090 patch by "cypherpunks".
17091 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
17093 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
17094 18672; bugfix on 0.2.5.1-alpha.
17096 o Minor bugfixes (private directory):
17097 - Prevent a race condition when creating private directories. Fixes
17098 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
17099 Patch from jsturgix. Found with Flawfinder.
17101 o Minor bugfixes (test networks, IPv6):
17102 - Allow internal IPv6 addresses in descriptors in test networks.
17103 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
17106 o Minor bugfixes (testing):
17107 - We no longer disable assertions in the unit tests when coverage is
17108 enabled. Instead, we require you to say --disable-asserts-in-tests
17109 to the configure script if you need assertions disabled in the
17110 unit tests (for example, if you want to perform branch coverage).
17111 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
17113 o Minor bugfixes (time parsing):
17114 - Avoid overflow in tor_timegm when parsing dates in and after 2038
17115 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
17116 0.0.2pre14. Patch by teor.
17118 o Minor bugfixes (tor-gencert):
17119 - Correctly handle the case where an authority operator enters a
17120 passphrase but sends an EOF before sending a newline. Fixes bug
17121 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
17123 o Code simplification and refactoring:
17124 - Quote all the string interpolations in configure.ac -- even those
17125 which we are pretty sure can't contain spaces. Closes ticket
17126 17744. Patch from zerosion.
17127 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
17128 inplace, so there's no need to have a separate implementation for
17129 the non-inplace code. Closes ticket 18258. Patch from Malek.
17130 - Simplify return types for some crypto functions that can't
17131 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
17134 - Change build messages to refer to "Fedora" instead of "Fedora
17135 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
17136 Patches from "icanhasaccount" and "cypherpunks".
17138 o Removed features:
17139 - We no longer maintain an internal freelist in memarea.c.
17140 Allocators should be good enough to make this code unnecessary,
17141 and it's doubtful that it ever had any performance benefit.
17144 - Fix several warnings from clang's address sanitizer produced in
17146 - Treat backtrace test failures as expected on FreeBSD until we
17147 solve bug 17808. Closes ticket 18204.
17150 Changes in version 0.2.8.1-alpha - 2016-02-04
17151 Tor 0.2.8.1-alpha is the first alpha release in its series. It
17152 includes numerous small features and bugfixes against previous Tor
17153 versions, and numerous small infrastructure improvements. The most
17154 notable features are a set of improvements to the directory subsystem.
17156 o Major features (security, Linux):
17157 - When Tor starts as root on Linux and is told to switch user ID, it
17158 can now retain the capability to bind to low ports. By default,
17159 Tor will do this only when it's switching user ID and some low
17160 ports have been configured. You can change this behavior with the
17161 new option KeepBindCapabilities. Closes ticket 8195.
17163 o Major features (directory system):
17164 - When bootstrapping multiple consensus downloads at a time, use the
17165 first one that starts downloading, and close the rest. This
17166 reduces failures when authorities or fallback directories are slow
17167 or down. Together with the code for feature 15775, this feature
17168 should reduces failures due to fallback churn. Implements ticket
17169 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
17170 "mikeperry" and "teor".
17171 - Include a trial list of 21 default fallback directories, generated
17172 in January 2016, based on an opt-in survey of suitable relays.
17173 Doing this should make clients bootstrap more quickly and reliably,
17174 and reduce the load on the directory authorities. Closes ticket
17175 15775. Patch by "teor".
17176 Candidates identified using an OnionOO script by "weasel", "teor",
17177 "gsathya", and "karsten".
17178 - Previously only relays that explicitly opened a directory port
17179 (DirPort) accepted directory requests from clients. Now all
17180 relays, with and without a DirPort, accept and serve tunneled
17181 directory requests that they receive through their ORPort. You can
17182 disable this behavior using the new DirCache option. Closes
17185 o Major key updates:
17186 - Update the V3 identity key for the dannenberg directory authority:
17187 it was changed on 18 November 2015. Closes task 17906. Patch
17190 o Minor features (security, clock):
17191 - Warn when the system clock appears to move back in time (when the
17192 state file was last written in the future). Tor doesn't know that
17193 consensuses have expired if the clock is in the past. Patch by
17194 "teor". Implements ticket 17188.
17196 o Minor features (security, exit policies):
17197 - ExitPolicyRejectPrivate now rejects more private addresses by
17198 default. Specifically, it now rejects the relay's outbound bind
17199 addresses (if configured), and the relay's configured port
17200 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
17201 0.2.0.11-alpha. Patch by "teor".
17203 o Minor features (security, memory erasure):
17204 - Set the unused entries in a smartlist to NULL. This helped catch
17205 a (harmless) bug, and shouldn't affect performance too much.
17206 Implements ticket 17026.
17207 - Use SecureMemoryWipe() function to securely clean memory on
17208 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
17209 Implements feature 17986.
17210 - Use explicit_bzero or memset_s when present. Previously, we'd use
17211 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
17212 from <logan@hackers.mu> and <selven@hackers.mu>.
17213 - Make memwipe() do nothing when passed a NULL pointer or buffer of
17214 zero size. Check size argument to memwipe() for underflow. Fixes
17215 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
17218 o Minor features (security, RNG):
17219 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
17220 positively are not allowed to fail. Previously we depended on
17221 internal details of OpenSSL's behavior. Closes ticket 17686.
17222 - Never use the system entropy output directly for anything besides
17223 seeding the PRNG. When we want to generate important keys, instead
17224 of using system entropy directly, we now hash it with the PRNG
17225 stream. This may help resist certain attacks based on broken OS
17226 entropy implementations. Closes part of ticket 17694.
17227 - Use modern system calls (like getentropy() or getrandom()) to
17228 generate strong entropy on platforms that have them. Closes
17231 o Minor features (accounting):
17232 - Added two modes to the AccountingRule option: One for limiting
17233 only the number of bytes sent ("AccountingRule out"), and one for
17234 limiting only the number of bytes received ("AccountingRule in").
17235 Closes ticket 15989; patch from "unixninja92".
17237 o Minor features (build):
17238 - Since our build process now uses "make distcheck", we no longer
17239 force "make dist" to depend on "make check". Closes ticket 17893;
17240 patch from "cypherpunks."
17241 - Tor now builds successfully with the recent OpenSSL 1.1
17242 development branch, and with the latest LibreSSL. Closes tickets
17243 17549, 17921, and 17984.
17245 o Minor features (controller):
17246 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
17247 tickets 16774 and 17817. Patch by George Tankersley.
17248 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
17249 service descriptor from a service's local hidden service
17250 descriptor cache. Closes ticket 14846.
17251 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
17252 controllers can examine the the reject rules added by
17253 ExitPolicyRejectPrivate. This makes it easier for stem to display
17256 o Minor features (crypto):
17257 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
17259 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
17260 - When allocating a digest state object, allocate no more space than
17261 we actually need. Previously, we would allocate as much space as
17262 the state for the largest algorithm would need. This change saves
17263 up to 672 bytes per circuit. Closes ticket 17796.
17264 - Improve performance when hashing non-multiple of 8 sized buffers,
17265 based on Andrew Moon's public domain SipHash-2-4 implementation.
17266 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
17268 o Minor features (directory downloads):
17269 - Wait for busy authorities and fallback directories to become non-
17270 busy when bootstrapping. (A similar change was made in 6c443e987d
17271 for directory caches chosen from the consensus.) Closes ticket
17272 17864; patch by "teor".
17273 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
17274 directory mirrors. The default is 1; set it to 0 to disable
17275 fallbacks. Implements ticket 17576. Patch by "teor".
17277 o Minor features (geoip):
17278 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
17281 o Minor features (IPv6):
17282 - Add an argument 'ipv6=address:orport' to the DirAuthority and
17283 FallbackDir torrc options, to specify an IPv6 address for an
17284 authority or fallback directory. Add hard-coded ipv6 addresses for
17285 directory authorities that have them. Closes ticket 17327; patch
17286 from Nick Mathewson and "teor".
17287 - Add address policy assume_action support for IPv6 addresses.
17288 - Limit IPv6 mask bits to 128.
17289 - Warn when comparing against an AF_UNSPEC address in a policy, it's
17290 almost always a bug. Closes ticket 17863; patch by "teor".
17291 - Allow users to configure directory authorities and fallback
17292 directory servers with IPv6 addresses and ORPorts. Resolves
17294 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
17295 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
17296 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
17297 17638; bugfix on 0.0.2pre8. Patch by "teor".
17299 o Minor features (logging):
17300 - When logging to syslog, allow a tag to be added to the syslog
17301 identity (the string prepended to every log message). The tag can
17302 be configured with SyslogIdentityTag and defaults to none. Setting
17303 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
17306 o Minor features (portability):
17307 - Use timingsafe_memcmp() where available. Closes ticket 17944;
17308 patch from <logan@hackers.mu>.
17310 o Minor features (relay, address discovery):
17311 - Add a family argument to get_interface_addresses_raw() and
17312 subfunctions to make network interface address interogation more
17313 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
17314 types of interfaces from the operating system. Resolves
17316 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
17317 fails to enumerate interface addresses using the platform-specific
17318 API, have it rely on the UDP socket fallback technique to try and
17319 find out what IP addresses (both IPv4 and IPv6) our machine has.
17320 Resolves ticket 17951.
17322 o Minor features (replay cache):
17323 - The replay cache now uses SHA256 instead of SHA1. Implements
17324 feature 8961. Patch by "teor", issue reported by "rransom".
17326 o Minor features (unix file permissions):
17327 - Defer creation of Unix sockets until after setuid. This avoids
17328 needing CAP_CHOWN and CAP_FOWNER when using systemd's
17329 CapabilityBoundingSet, or chown and fowner when using SELinux.
17330 Implements part of ticket 17562. Patch from Jamie Nguyen.
17331 - If any directory created by Tor is marked as group readable, the
17332 filesystem group is allowed to be either the default GID or the
17333 root user. Allowing root to read the DataDirectory prevents the
17334 need for CAP_READ_SEARCH when using systemd's
17335 CapabilityBoundingSet, or dac_read_search when using SELinux.
17336 Implements part of ticket 17562. Patch from Jamie Nguyen.
17337 - Introduce a new DataDirectoryGroupReadable option. If it is set to
17338 1, the DataDirectory will be made readable by the default GID.
17339 Implements part of ticket 17562. Patch from Jamie Nguyen.
17341 o Minor bugfixes (accounting):
17342 - The max bandwidth when using 'AccountRule sum' is now correctly
17343 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
17344 from "unixninja92".
17346 o Minor bugfixes (code correctness):
17347 - When closing an entry connection, generate a warning if we should
17348 have sent an end cell for it but we haven't. Fixes bug 17876;
17349 bugfix on 0.2.3.2-alpha.
17350 - Assert that allocated memory held by the reputation code is freed
17351 according to its internal counters. Fixes bug 17753; bugfix
17353 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
17356 o Minor bugfixes (compilation):
17357 - Mark all object files that include micro-revision.i as depending
17358 on it, so as to make parallel builds more reliable. Fixes bug
17359 17826; bugfix on 0.2.5.1-alpha.
17360 - Don't try to use the pthread_condattr_setclock() function unless
17361 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
17362 17819; bugfix on 0.2.6.3-alpha.
17363 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
17365 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
17366 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
17367 - Fix search for libevent libraries on OpenBSD (and other systems
17368 that install libevent 1 and libevent 2 in parallel). Fixes bug
17369 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
17370 - Isolate environment variables meant for tests from the rest of the
17371 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
17372 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
17374 - Remove config.log only from make distclean, not from make clean.
17375 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
17377 o Minor bugfixes (crypto):
17378 - Check the return value of HMAC() and assert on failure. Fixes bug
17379 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
17381 o Minor bugfixes (fallback directories):
17382 - Mark fallbacks as "too busy" when they return a 503 response,
17383 rather than just marking authorities. Fixes bug 17572; bugfix on
17384 0.2.4.7-alpha. Patch by "teor".
17386 o Minor bugfixes (IPv6):
17387 - Update the limits in max_dl_per_request for IPv6 address length.
17388 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
17390 o Minor bugfixes (linux seccomp2 sandbox):
17391 - Fix a crash when using offline master ed25519 keys with the Linux
17392 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
17394 o Minor bugfixes (logging):
17395 - In log messages that include a function name, use __FUNCTION__
17396 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
17397 with clang __PRETTY_FUNCTION__ has extra information we don't
17398 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
17400 - Remove needless quotes from a log message about unparseable
17401 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
17403 o Minor bugfixes (portability):
17404 - Remove an #endif from configure.ac so that we correctly detect the
17405 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
17408 o Minor bugfixes (relays):
17409 - Check that both the ORPort and DirPort (if present) are reachable
17410 before publishing a relay descriptor. Otherwise, relays publish a
17411 descriptor with DirPort 0 when the DirPort reachability test takes
17412 longer than the ORPort reachability test. Fixes bug 18050; bugfix
17413 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
17415 o Minor bugfixes (relays, hidden services):
17416 - Refuse connection requests to private OR addresses unless
17417 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
17418 then refuse to send any cells to a private address. Fixes bugs
17419 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
17421 o Minor bugfixes (safe logging):
17422 - When logging a malformed hostname received through socks4, scrub
17423 it if SafeLogging says we should. Fixes bug 17419; bugfix
17426 o Minor bugfixes (statistics code):
17427 - Consistently check for overflow in round_*_to_next_multiple_of
17428 functions, and add unit tests with additional and maximal values.
17429 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
17430 - Handle edge cases in the laplace functions: avoid division by
17431 zero, avoid taking the log of zero, and silence clang type
17432 conversion warnings using round and trunc. Add unit tests for edge
17433 cases with maximal values. Fixes part of bug 13192; bugfix
17436 o Minor bugfixes (testing):
17437 - The test for log_heartbeat was incorrectly failing in timezones
17438 with non-integer offsets. Instead of comparing the end of the time
17439 string against a constant, compare it to the output of
17440 format_local_iso_time when given the correct input. Fixes bug
17441 18039; bugfix on 0.2.5.4-alpha.
17442 - Make unit tests pass on IPv6-only systems, and systems without
17443 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
17444 bugfix on 0.2.7.3-rc. Patch by "teor".
17445 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
17447 - Check the full results of SHA256 and SHA512 digests in the unit
17448 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
17450 o Code simplification and refactoring:
17451 - Move logging of redundant policy entries in
17452 policies_parse_exit_policy_internal into its own function. Closes
17453 ticket 17608; patch from "juce".
17454 - Extract the more complicated parts of circuit_mark_for_close()
17455 into a new function that we run periodically before circuits are
17456 freed. This change removes more than half of the functions
17457 currently in the "blob". Closes ticket 17218.
17458 - Clean up a little duplicated code in
17459 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
17461 - Decouple the list of streams waiting to be attached to circuits
17462 from the overall connection list. This change makes it possible to
17463 attach streams quickly while simplifying Tor's callgraph and
17464 avoiding O(N) scans of the entire connection list. Closes
17466 - When a direct directory request fails immediately on launch,
17467 instead of relaunching that request from inside the code that
17468 launches it, instead mark the connection for teardown. This change
17469 simplifies Tor's callback and prevents the directory-request
17470 launching code from invoking itself recursively. Closes
17472 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
17473 use them. Closes ticket 17926.
17476 - Add a description of the correct use of the '--keygen' command-
17477 line option. Closes ticket 17583; based on text by 's7r'.
17478 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
17479 - Explain actual minima for BandwidthRate. Closes ticket 16382.
17480 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
17481 - Mention torspec URL in the manpage and point the reader to it
17482 whenever we mention a document that belongs in torspce. Fixes
17485 o Removed features:
17486 - Remove client-side support for connecting to Tor relays running
17487 versions of Tor before 0.2.3.6-alpha. These relays didn't support
17488 the v3 TLS handshake protocol, and are no longer allowed on the
17489 Tor network. Implements the client side of ticket 11150. Based on
17490 patches by Tom van der Woerdt.
17493 - Add unit tests to check for common RNG failure modes, such as
17494 returning all zeroes, identical values, or incrementing values
17495 (OpenSSL's rand_predictable feature). Patch by "teor".
17496 - Log more information when the backtrace tests fail. Closes ticket
17497 17892. Patch from "cypherpunks."
17498 - Always test both ed25519 backends, so that we can be sure that our
17499 batch-open replacement code works. Part of ticket 16794.
17500 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
17501 portion of ticket 16831.
17502 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
17503 util_format.c, directory.c, and options_validate.c. Closes tickets
17504 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
17506 - Unit tests for directory_handle_command_get. Closes ticket 17004.
17507 Patch from Reinaldo de Souza Jr.
17510 Changes in version 0.2.7.6 - 2015-12-10
17511 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
17512 well as a minor bug in hidden service reliability.
17514 o Major bugfixes (guard selection):
17515 - Actually look at the Guard flag when selecting a new directory
17516 guard. When we implemented the directory guard design, we
17517 accidentally started treating all relays as if they have the Guard
17518 flag during guard selection, leading to weaker anonymity and worse
17519 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
17522 o Minor features (geoip):
17523 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
17526 o Minor bugfixes (compilation):
17527 - When checking for net/pfvar.h, include netinet/in.h if possible.
17528 This fixes transparent proxy detection on OpenBSD. Fixes bug
17529 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
17530 - Fix a compilation warning with Clang 3.6: Do not check the
17531 presence of an address which can never be NULL. Fixes bug 17781.
17533 o Minor bugfixes (correctness):
17534 - When displaying an IPv6 exit policy, include the mask bits
17535 correctly even when the number is greater than 31. Fixes bug
17536 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
17537 - The wrong list was used when looking up expired intro points in a
17538 rend service object, causing what we think could be reachability
17539 issues for hidden services, and triggering a BUG log. Fixes bug
17540 16702; bugfix on 0.2.7.2-alpha.
17541 - Fix undefined behavior in the tor_cert_checksig function. Fixes
17542 bug 17722; bugfix on 0.2.7.2-alpha.
17545 Changes in version 0.2.7.5 - 2015-11-20
17546 The Tor 0.2.7 release series is dedicated to the memory of Tor user
17547 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
17548 tirelessly to advocate human rights regardless of national borders,
17549 and oppose the encroachments of mass surveillance. He opposed national
17550 exceptionalism, he brought clarity to legal and policy debates, he
17551 understood and predicted the impact of mass surveillance on the world,
17552 and he laid the groundwork for resisting it. While serving on the Tor
17553 Project's board of directors, he brought us his uncompromising focus
17554 on technical excellence in the service of humankind. Caspar was an
17555 inimitable force for good and a wonderful friend. He was kind,
17556 humorous, generous, gallant, and believed we should protect one
17557 another without exception. We honor him here for his ideals, his
17558 efforts, and his accomplishments. Please honor his memory with works
17559 that would make him proud.
17561 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
17563 The 0.2.7 series adds a more secure identity key type for relays,
17564 improves cryptography performance, resolves several longstanding
17565 hidden-service performance issues, improves controller support for
17566 hidden services, and includes small bugfixes and performance
17567 improvements throughout the program. This release series also includes
17568 more tests than before, and significant simplifications to which parts
17569 of Tor invoke which others.
17571 (This release contains no code changes since 0.2.7.4-rc.)
17574 Changes in version 0.2.7.4-rc - 2015-10-21
17575 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
17576 fixes some important memory leaks, and a scary-looking (but mostly
17577 harmless in practice) invalid-read bug. It also has a few small
17578 bugfixes, notably fixes for compilation and portability on different
17579 platforms. If no further significant bounds are found, the next
17580 release will the the official stable release.
17582 o Major bugfixes (security, correctness):
17583 - Fix an error that could cause us to read 4 bytes before the
17584 beginning of an openssl string. This bug could be used to cause
17585 Tor to crash on systems with unusual malloc implementations, or
17586 systems with unusual hardening installed. Fixes bug 17404; bugfix
17589 o Major bugfixes (correctness):
17590 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
17591 bug 17401; bugfix on 0.2.7.3-rc.
17593 o Major bugfixes (memory leaks):
17594 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
17595 17398; bugfix on 0.2.6.1-alpha.
17596 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
17597 17402; bugfix on 0.2.7.3-rc.
17598 - Fix a memory leak when reading an expired signing key from disk.
17599 Fixes bug 17403; bugfix on 0.2.7.2-rc.
17601 o Minor features (geoIP):
17602 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
17605 o Minor bugfixes (compilation):
17606 - Repair compilation with the most recent (unreleased, alpha)
17607 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
17608 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
17609 17251; bugfix on 0.2.7.2-alpha.
17610 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
17611 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
17613 o Minor bugfixes (portability):
17614 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
17615 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
17618 o Minor bugfixes (sandbox):
17619 - Add the "hidserv-stats" filename to our sandbox filter for the
17620 HiddenServiceStatistics option to work properly. Fixes bug 17354;
17621 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
17623 o Minor bugfixes (testing):
17624 - Add unit tests for get_interface_address* failure cases. Fixes bug
17625 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
17626 - Fix breakage when running 'make check' with BSD make. Fixes bug
17627 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
17628 - Make the get_ifaddrs_* unit tests more tolerant of different
17629 network configurations. (Don't assume every test box has an IPv4
17630 address, and don't assume every test box has a non-localhost
17631 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
17632 - Skip backtrace tests when backtrace support is not compiled in.
17633 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
17637 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
17638 - Note that HiddenServicePorts can take a unix domain socket. Closes
17642 Changes in version 0.2.7.3-rc - 2015-09-25
17643 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
17644 contains numerous usability fixes for Ed25519 keys, safeguards against
17645 several misconfiguration problems, significant simplifications to
17646 Tor's callgraph, and numerous bugfixes and small features.
17648 This is the most tested release of Tor to date. The unit tests cover
17649 39.40% of the code, and the integration tests (accessible with "make
17650 test-full-online", requiring stem and chutney and a network
17651 connection) raise the coverage to 64.49%.
17653 o Major features (security, hidden services):
17654 - Hidden services, if using the EntryNodes option, are required to
17655 use more than one EntryNode, in order to avoid a guard discovery
17656 attack. (This would only affect people who had configured hidden
17657 services and manually specified the EntryNodes option with a
17658 single entry-node. The impact was that it would be easy to
17659 remotely identify the guard node used by such a hidden service.
17660 See ticket for more information.) Fixes ticket 14917.
17662 o Major features (Ed25519 keys, keypinning):
17663 - The key-pinning option on directory authorities is now advisory-
17664 only by default. In a future version, or when the AuthDirPinKeys
17665 option is set, pins are enforced again. Disabling key-pinning
17666 seemed like a good idea so that we can survive the fallout of any
17667 usability problems associated with Ed25519 keys. Closes
17670 o Major features (Ed25519 performance):
17671 - Improve the speed of Ed25519 operations and Curve25519 keypair
17672 generation when built targeting 32 bit x86 platforms with SSE2
17673 available. Implements ticket 16535.
17674 - Improve the runtime speed of Ed25519 signature verification by
17675 using Ed25519-donna's batch verification support. Implements
17678 o Major features (performance testing):
17679 - The test-network.sh script now supports performance testing.
17680 Requires corresponding chutney performance testing changes. Patch
17681 by "teor". Closes ticket 14175.
17683 o Major features (relay, Ed25519):
17684 - Significant usability improvements for Ed25519 key management. Log
17685 messages are better, and the code can recover from far more
17686 failure conditions. Thanks to "s7r" for reporting and diagnosing
17688 - Add a new OfflineMasterKey option to tell Tor never to try loading
17689 or generating a secret Ed25519 identity key. You can use this in
17690 combination with tor --keygen to manage offline and/or encrypted
17691 Ed25519 keys. Implements ticket 16944.
17692 - Add a --newpass option to allow changing or removing the
17693 passphrase of an encrypted key with tor --keygen. Implements part
17695 - On receiving a HUP signal, check to see whether the Ed25519
17696 signing key has changed, and reload it if so. Closes ticket 16790.
17698 o Major bugfixes (relay, Ed25519):
17699 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
17700 0.2.7.2-alpha. Reported by "s7r".
17701 - Improve handling of expired signing keys with offline master keys.
17702 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
17704 o Minor features (client-side privacy):
17705 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
17706 lifespan when IsolateSOCKSAuth and streams with SOCKS
17707 authentication are attached to the circuit. This allows
17708 applications like TorBrowser to manage circuit lifetime on their
17709 own. Implements feature 15482.
17710 - When logging malformed hostnames from SOCKS5 requests, respect
17711 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
17713 o Minor features (compilation):
17714 - Give a warning as early as possible when trying to build with an
17715 unsupported OpenSSL version. Closes ticket 16901.
17716 - Fail during configure if we're trying to build against an OpenSSL
17717 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
17718 which started requiring ECC.
17720 o Minor features (geoip):
17721 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
17724 o Minor features (hidden services):
17725 - Relays need to have the Fast flag to get the HSDir flag. As this
17726 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
17727 drop. This change should make some attacks against the hidden
17728 service directory system harder. Fixes ticket 15963.
17729 - Turn on hidden service statistics collection by setting the torrc
17730 option HiddenServiceStatistics to "1" by default. (This keeps
17731 track only of the fraction of traffic used by hidden services, and
17732 the total number of hidden services in existence.) Closes
17734 - Client now uses an introduction point failure cache to know when
17735 to fetch or keep a descriptor in their cache. Previously, failures
17736 were recorded implicitly, but not explicitly remembered. Closes
17739 o Minor features (testing, authorities, documentation):
17740 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
17741 explicitly manage consensus flags in testing networks. Patch by
17742 "robgjansen", modified by "teor". Implements part of ticket 14882.
17744 o Minor bugfixes (security, exit policies):
17745 - ExitPolicyRejectPrivate now also rejects the relay's published
17746 IPv6 address (if any), and any publicly routable IPv4 or IPv6
17747 addresses on any local interfaces. ticket 17027. Patch by "teor".
17748 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
17750 o Minor bug fixes (torrc exit policies):
17751 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
17752 produce IPv6 wildcard addresses. Previously they would produce
17753 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
17754 of bug 16069; bugfix on 0.2.4.7-alpha.
17755 - When parsing torrc ExitPolicies, we now warn for a number of cases
17756 where the user's intent is likely to differ from Tor's actual
17757 behavior. These include: using an IPv4 address with an accept6 or
17758 reject6 line; using "private" on an accept6 or reject6 line; and
17759 including any ExitPolicy lines after accept *:* or reject *:*.
17760 Related to ticket 16069.
17761 - When parsing torrc ExitPolicies, we now issue an info-level
17762 message when expanding an "accept/reject *" line to include both
17763 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
17764 - In each instance above, usage advice is provided to avoid the
17765 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
17766 16069; bugfix on 0.2.4.7-alpha.
17768 o Minor bugfixes (authority):
17769 - Don't assign "HSDir" to a router if it isn't Valid and Running.
17770 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
17771 - Downgrade log messages about Ed25519 key issues if they are in old
17772 cached router descriptors. Fixes part of bug 16286; bugfix
17774 - When we find an Ed25519 key issue in a cached descriptor, stop
17775 saying the descriptor was just "uploaded". Fixes another part of
17776 bug 16286; bugfix on 0.2.7.2-alpha.
17778 o Minor bugfixes (control port):
17779 - Repair a warning and a spurious result when getting the maximum
17780 number of file descriptors from the controller. Fixes bug 16697;
17781 bugfix on 0.2.7.2-alpha.
17783 o Minor bugfixes (correctness):
17784 - When calling channel_free_list(), avoid calling smartlist_remove()
17785 while inside a FOREACH loop. This partially reverts commit
17786 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
17787 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
17789 o Minor bugfixes (documentation):
17790 - Advise users on how to configure separate IPv4 and IPv6 exit
17791 policies in the manpage and sample torrcs. Related to ticket 16069.
17792 - Fix the usage message of tor-resolve(1) so that it no longer lists
17793 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
17794 - Fix an error in the manual page and comments for
17795 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
17796 required "ORPort connectivity". While this is true, it is in no
17797 way unique to the HSDir flag. Of all the flags, only HSDirs need a
17798 DirPort configured in order for the authorities to assign that
17799 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
17802 o Minor bugfixes (Ed25519):
17803 - Fix a memory leak when reading router descriptors with expired
17804 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
17806 o Minor bugfixes (linux seccomp2 sandbox):
17807 - Allow bridge authorities to run correctly under the seccomp2
17808 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
17809 - Allow routers with ed25519 keys to run correctly under the
17810 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
17812 o Minor bugfixes (open file limit):
17813 - Fix set_max_file_descriptors() to set by default the max open file
17814 limit to the current limit when setrlimit() fails. Fixes bug
17815 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
17817 o Minor bugfixes (portability):
17818 - Try harder to normalize the exit status of the Tor process to the
17819 standard-provided range. Fixes bug 16975; bugfix on every version
17821 - Check correctly for Windows socket errors in the workqueue
17822 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
17823 - Fix the behavior of crypto_rand_time_range() when told to consider
17824 times before 1970. (These times were possible when running in a
17825 simulated network environment where time()'s output starts at
17826 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
17827 - Restore correct operation of TLS client-cipher detection on
17828 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
17830 o Minor bugfixes (relay):
17831 - Ensure that worker threads actually exit when a fatal error or
17832 shutdown is indicated. This fix doesn't currently affect the
17833 behavior of Tor, because Tor workers never indicates fatal error
17834 or shutdown except in the unit tests. Fixes bug 16868; bugfix
17836 - Unblock threads before releasing the work queue mutex to ensure
17837 predictable scheduling behavior. Fixes bug 16644; bugfix
17840 o Code simplification and refactoring:
17841 - Change the function that's called when we need to retry all
17842 downloads so that it only reschedules the downloads to happen
17843 immediately, rather than launching them all at once itself. This
17844 further simplifies Tor's callgraph.
17845 - Move some format-parsing functions out of crypto.c and
17846 crypto_curve25519.c into crypto_format.c and/or util_format.c.
17847 - Move the client-only parts of init_keys() into a separate
17848 function. Closes ticket 16763.
17849 - Simplify the microdesc_free() implementation so that it no longer
17850 appears (to code analysis tools) to potentially invoke a huge
17851 suite of other microdesc functions.
17852 - Simply the control graph further by deferring the inner body of
17853 directory_all_unreachable() into a callback. Closes ticket 16762.
17854 - Treat the loss of an owning controller as equivalent to a SIGTERM
17855 signal. This removes a tiny amount of duplicated code, and
17856 simplifies our callgraph. Closes ticket 16788.
17857 - When generating an event to send to the controller, we no longer
17858 put the event over the network immediately. Instead, we queue
17859 these events, and use a Libevent callback to deliver them. This
17860 change simplifies Tor's callgraph by reducing the number of
17861 functions from which all other Tor functions are reachable. Closes
17863 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
17864 that try to scan or compile every file on Unix won't decide that
17866 - Remove the unused "nulterminate" argument from buf_pullup().
17869 - Recommend a 40 GB example AccountingMax in torrc.sample rather
17870 than a 4 GB max. Closes ticket 16742.
17871 - Include the TUNING document in our source tarball. It is referred
17872 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
17876 - The internal pure-C tor-fw-helper tool is now removed from the Tor
17877 distribution, in favor of the pure-Go clone available from
17878 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
17879 used by the C tor-fw-helper are not, in our opinion, very
17880 confidence- inspiring in their secure-programming techniques.
17881 Closes ticket 13338.
17882 - Remove the code that would try to aggressively flush controller
17883 connections while writing to them. This code was introduced in
17884 0.1.2.7-alpha, in order to keep output buffers from exceeding
17885 their limits. But there is no longer a maximum output buffer size,
17886 and flushing data in this way caused some undesirable recursions
17887 in our call graph. Closes ticket 16480.
17890 - Make "bridges+hs" the default test network. This tests almost all
17891 tor functionality during make test-network, while allowing tests
17892 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
17893 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
17894 (chutney). Patches by "teor".
17895 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
17896 by-side in the same parent directory. Closes ticket 16903. Patch
17898 - Use environment variables rather than autoconf substitutions to
17899 send variables from the build system to the test scripts. This
17900 change should be easier to maintain, and cause 'make distcheck' to
17901 work better than before. Fixes bug 17148.
17902 - Add a new set of callgraph analysis scripts that use clang to
17903 produce a list of which Tor functions are reachable from which
17904 other Tor functions. We're planning to use these to help simplify
17905 our code structure by identifying illogical dependencies.
17906 - Add new 'test-full' and 'test-full-online' targets to run all
17907 tests, including integration tests with stem and chutney.
17908 - Make the test-workqueue test work on Windows by initializing the
17909 network before we begin.
17910 - New make target (make test-network-all) to run multiple applicable
17911 chutney test cases. Patch from Teor; closes 16953.
17912 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
17913 functions in dns.c. Implements a portion of ticket 16831.
17914 - When building Tor with testing coverage enabled, run Chutney tests
17915 (if any) using the 'tor-cov' coverage binary.
17916 - When running test-network or test-stem, check for the absence of
17917 stem/chutney before doing any build operations.
17920 Changes in version 0.2.7.2-alpha - 2015-07-27
17921 This, the second alpha in the Tor 0.2.7 series, has a number of new
17922 features, including a way to manually pick the number of introduction
17923 points for hidden services, and the much stronger Ed25519 signing key
17924 algorithm for regular Tor relays (including support for encrypted
17925 offline identity keys in the new algorithm).
17927 Support for Ed25519 on relays is currently limited to signing router
17928 descriptors; later alphas in this series will extend Ed25519 key
17929 support to more parts of the Tor protocol.
17931 o Major features (Ed25519 identity keys, Proposal 220):
17932 - All relays now maintain a stronger identity key, using the Ed25519
17933 elliptic curve signature format. This master key is designed so
17934 that it can be kept offline. Relays also generate an online
17935 signing key, and a set of other Ed25519 keys and certificates.
17936 These are all automatically regenerated and rotated as needed.
17937 Implements part of ticket 12498.
17938 - Directory authorities now vote on Ed25519 identity keys along with
17939 RSA1024 keys. Implements part of ticket 12498.
17940 - Directory authorities track which Ed25519 identity keys have been
17941 used with which RSA1024 identity keys, and do not allow them to
17942 vary freely. Implements part of ticket 12498.
17943 - Microdescriptors now include Ed25519 identity keys. Implements
17944 part of ticket 12498.
17945 - Add support for offline encrypted Ed25519 master keys. To use this
17946 feature on your tor relay, run "tor --keygen" to make a new master
17947 key (or to make a new signing key if you already have a master
17948 key). Closes ticket 13642.
17950 o Major features (Hidden services):
17951 - Add the torrc option HiddenServiceNumIntroductionPoints, to
17952 specify a fixed number of introduction points. Its maximum value
17953 is 10 and default is 3. Using this option can increase a hidden
17954 service's reliability under load, at the cost of making it more
17955 visible that the hidden service is facing extra load. Closes
17957 - Remove the adaptive algorithm for choosing the number of
17958 introduction points, which used to change the number of
17959 introduction points (poorly) depending on the number of
17960 connections the HS sees. Closes ticket 4862.
17962 o Major features (onion key cross-certification):
17963 - Relay descriptors now include signatures of their own identity
17964 keys, made using the TAP and ntor onion keys. These signatures
17965 allow relays to prove ownership of their own onion keys. Because
17966 of this change, microdescriptors will no longer need to include
17967 RSA identity keys. Implements proposal 228; closes ticket 12499.
17969 o Major features (performance):
17970 - Improve the runtime speed of Ed25519 operations by using the
17971 public-domain Ed25519-donna by Andrew M. ("floodyberry").
17972 Implements ticket 16467.
17973 - Improve the runtime speed of the ntor handshake by using an
17974 optimized curve25519 basepoint scalarmult implementation from the
17975 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
17976 ideas by Adam Langley. Implements ticket 9663.
17978 o Major bugfixes (client-side privacy, also in 0.2.6.9):
17979 - Properly separate out each SOCKSPort when applying stream
17980 isolation. The error occurred because each port's session group
17981 was being overwritten by a default value when the listener
17982 connection was initialized. Fixes bug 16247; bugfix on
17983 0.2.6.3-alpha. Patch by "jojelino".
17985 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
17986 - Stop refusing to store updated hidden service descriptors on a
17987 client. This reverts commit 9407040c59218 (which indeed fixed bug
17988 14219, but introduced a major hidden service reachability
17989 regression detailed in bug 16381). This is a temporary fix since
17990 we can live with the minor issue in bug 14219 (it just results in
17991 some load on the network) but the regression of 16381 is too much
17992 of a setback. First-round fix for bug 16381; bugfix
17995 o Major bugfixes (hidden services):
17996 - When cannibalizing a circuit for an introduction point, always
17997 extend to the chosen exit node (creating a 4 hop circuit).
17998 Previously Tor would use the current circuit exit node, which
17999 changed the original choice of introduction point, and could cause
18000 the hidden service to skip excluded introduction points or
18001 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
18004 o Major bugfixes (open file limit):
18005 - The open file limit wasn't checked before calling
18006 tor_accept_socket_nonblocking(), which would make Tor exceed the
18007 limit. Now, before opening a new socket, Tor validates the open
18008 file limit just before, and if the max has been reached, return an
18009 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
18011 o Major bugfixes (stability, also in 0.2.6.10):
18012 - Stop crashing with an assertion failure when parsing certain kinds
18013 of malformed or truncated microdescriptors. Fixes bug 16400;
18014 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
18015 by "cypherpunks_backup".
18016 - Stop random client-side assertion failures that could occur when
18017 connecting to a busy hidden service, or connecting to a hidden
18018 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
18021 o Minor features (directory authorities, security, also in 0.2.6.9):
18022 - The HSDir flag given by authorities now requires the Stable flag.
18023 For the current network, this results in going from 2887 to 2806
18024 HSDirs. Also, it makes it harder for an attacker to launch a sybil
18025 attack by raising the effort for a relay to become Stable to
18026 require at the very least 7 days, while maintaining the 96 hours
18027 uptime requirement for HSDir. Implements ticket 8243.
18029 o Minor features (client):
18030 - Relax the validation of hostnames in SOCKS5 requests, allowing the
18031 character '_' to appear, in order to cope with domains observed in
18032 the wild that are serving non-RFC compliant records. Resolves
18034 - Relax the validation done to hostnames in SOCKS5 requests, and
18035 allow a single trailing '.' to cope with clients that pass FQDNs
18036 using that syntax to explicitly indicate that the domain name is
18037 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
18038 - Add GroupWritable and WorldWritable options to unix-socket based
18039 SocksPort and ControlPort options. These options apply to a single
18040 socket, and override {Control,Socks}SocketsGroupWritable. Closes
18043 o Minor features (control protocol):
18044 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
18045 the control protocol. Resolves ticket 15358.
18047 o Minor features (directory authorities):
18048 - Directory authorities no longer vote against the "Fast", "Stable",
18049 and "HSDir" flags just because they were going to vote against
18050 "Running": if the consensus turns out to be that the router was
18051 running, then the authority's vote should count. Patch from Peter
18052 Retzlaff; closes issue 8712.
18054 o Minor features (geoip, also in 0.2.6.10):
18055 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
18056 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
18058 o Minor features (hidden services):
18059 - Add the new options "HiddenServiceMaxStreams" and
18060 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
18061 limit the maximum number of simultaneous streams per circuit, and
18062 optionally tear down the circuit when the limit is exceeded. Part
18065 o Minor features (portability):
18066 - Use C99 variadic macros when the compiler is not GCC. This avoids
18067 failing compilations on MSVC, and fixes a log-file-based race
18068 condition in our old workarounds. Original patch from Gisle Vanem.
18070 o Minor bugfixes (compilation, also in 0.2.6.9):
18071 - Build with --enable-systemd correctly when libsystemd is
18072 installed, but systemd is not. Fixes bug 16164; bugfix on
18073 0.2.6.3-alpha. Patch from Peter Palfrader.
18075 o Minor bugfixes (controller):
18076 - Add the descriptor ID in each HS_DESC control event. It was
18077 missing, but specified in control-spec.txt. Fixes bug 15881;
18078 bugfix on 0.2.5.2-alpha.
18080 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
18081 - Check for failures from crypto_early_init, and refuse to continue.
18082 A previous typo meant that we could keep going with an
18083 uninitialized crypto library, and would have OpenSSL initialize
18084 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
18085 when implementing ticket 4900. Patch by "teor".
18087 o Minor bugfixes (hidden services):
18088 - Fix a crash when reloading configuration while at least one
18089 configured and one ephemeral hidden service exists. Fixes bug
18090 16060; bugfix on 0.2.7.1-alpha.
18091 - Avoid crashing with a double-free bug when we create an ephemeral
18092 hidden service but adding it fails for some reason. Fixes bug
18093 16228; bugfix on 0.2.7.1-alpha.
18095 o Minor bugfixes (Linux seccomp2 sandbox):
18096 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
18097 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
18099 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
18100 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
18101 these when eventfd2() support is missing. Fixes bug 16363; bugfix
18102 on 0.2.6.3-alpha. Patch from "teor".
18104 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
18105 - Fix sandboxing to work when running as a relay, by allowing the
18106 renaming of secret_id_key, and allowing the eventfd2 and futex
18107 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
18109 - Allow systemd connections to work with the Linux seccomp2 sandbox
18110 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
18113 o Minor bugfixes (relay):
18114 - Fix a rarely-encountered memory leak when failing to initialize
18115 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
18116 from "cypherpunks".
18118 o Minor bugfixes (systemd):
18119 - Fix an accidental formatting error that broke the systemd
18120 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
18121 - Tor's systemd unit file no longer contains extraneous spaces.
18122 These spaces would sometimes confuse tools like deb-systemd-
18123 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
18125 o Minor bugfixes (tests):
18126 - Use the configured Python executable when running test-stem-full.
18127 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
18129 o Minor bugfixes (tests, also in 0.2.6.9):
18130 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
18131 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
18133 o Minor bugfixes (threads, comments):
18134 - Always initialize return value in compute_desc_id in rendcommon.c
18135 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
18136 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
18137 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
18138 - Remove undefined directive-in-macro in test_util_writepid clang
18139 3.7 complains that using a preprocessor directive inside a macro
18140 invocation in test_util_writepid in test_util.c is undefined.
18141 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
18143 o Code simplification and refactoring:
18144 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
18145 to ensure they remain consistent and visible everywhere.
18146 - Remove some vestigial workarounds for the MSVC6 compiler. We
18147 haven't supported that in ages.
18148 - The link authentication code has been refactored for better
18149 testability and reliability. It now uses code generated with the
18150 "trunnel" binary encoding generator, to reduce the risk of bugs
18151 due to programmer error. Done as part of ticket 12498.
18154 - Include a specific and (hopefully) accurate documentation of the
18155 torrc file's meta-format in doc/torrc_format.txt. This is mainly
18156 of interest to people writing programs to parse or generate torrc
18157 files. This document is not a commitment to long-term
18158 compatibility; some aspects of the current format are a bit
18159 ridiculous. Closes ticket 2325.
18161 o Removed features:
18162 - Tor no longer supports copies of OpenSSL that are missing support
18163 for Elliptic Curve Cryptography. (We began using ECC when
18164 available in 0.2.4.8-alpha, for more safe and efficient key
18165 negotiation.) In particular, support for at least one of P256 or
18166 P224 is now required, with manual configuration needed if only
18167 P224 is available. Resolves ticket 16140.
18168 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
18169 on an operating system that has not upgraded to OpenSSL 1.0 or
18170 later, and you compile Tor from source, you will need to install a
18171 more recent OpenSSL to link Tor against.) These versions of
18172 OpenSSL are still supported by the OpenSSL, but the numerous
18173 cryptographic improvements in later OpenSSL releases makes them a
18174 clear choice. Resolves ticket 16034.
18175 - Remove the HidServDirectoryV2 option. Now all relays offer to
18176 store hidden service descriptors. Related to 16543.
18177 - Remove the VoteOnHidServDirectoriesV2 option, since all
18178 authorities have long set it to 1. Closes ticket 16543.
18181 - Document use of coverity, clang static analyzer, and clang dynamic
18182 undefined behavior and address sanitizers in doc/HACKING. Include
18183 detailed usage instructions in the blacklist. Patch by "teor".
18184 Closes ticket 15817.
18185 - The link authentication protocol code now has extensive tests.
18186 - The relay descriptor signature testing code now has
18188 - The test_workqueue program now runs faster, and is enabled by
18189 default as a part of "make check".
18190 - Now that OpenSSL has its own scrypt implementation, add an unit
18191 test that checks for interoperability between libscrypt_scrypt()
18192 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
18193 and rely on EVP_PBE_scrypt() whenever possible. Resolves
18197 Changes in version 0.2.6.10 - 2015-07-12
18198 Tor version 0.2.6.10 fixes some significant stability and hidden
18199 service client bugs, bulletproofs the cryptography init process, and
18200 fixes a bug when using the sandbox code with some older versions of
18201 Linux. Everyone running an older version, especially an older version
18202 of 0.2.6, should upgrade.
18204 o Major bugfixes (hidden service clients, stability):
18205 - Stop refusing to store updated hidden service descriptors on a
18206 client. This reverts commit 9407040c59218 (which indeed fixed bug
18207 14219, but introduced a major hidden service reachability
18208 regression detailed in bug 16381). This is a temporary fix since
18209 we can live with the minor issue in bug 14219 (it just results in
18210 some load on the network) but the regression of 16381 is too much
18211 of a setback. First-round fix for bug 16381; bugfix
18214 o Major bugfixes (stability):
18215 - Stop crashing with an assertion failure when parsing certain kinds
18216 of malformed or truncated microdescriptors. Fixes bug 16400;
18217 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
18218 by "cypherpunks_backup".
18219 - Stop random client-side assertion failures that could occur when
18220 connecting to a busy hidden service, or connecting to a hidden
18221 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
18224 o Minor features (geoip):
18225 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
18226 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
18228 o Minor bugfixes (crypto error-handling):
18229 - Check for failures from crypto_early_init, and refuse to continue.
18230 A previous typo meant that we could keep going with an
18231 uninitialized crypto library, and would have OpenSSL initialize
18232 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
18233 when implementing ticket 4900. Patch by "teor".
18235 o Minor bugfixes (Linux seccomp2 sandbox):
18236 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
18237 these when eventfd2() support is missing. Fixes bug 16363; bugfix
18238 on 0.2.6.3-alpha. Patch from "teor".
18241 Changes in version 0.2.6.9 - 2015-06-11
18242 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
18243 requirements for receiving an HSDir flag, and addresses some other small
18244 bugs in the systemd and sandbox code. Clients using circuit isolation
18245 should upgrade; all directory authorities should upgrade.
18247 o Major bugfixes (client-side privacy):
18248 - Properly separate out each SOCKSPort when applying stream
18249 isolation. The error occurred because each port's session group was
18250 being overwritten by a default value when the listener connection
18251 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
18254 o Minor feature (directory authorities, security):
18255 - The HSDir flag given by authorities now requires the Stable flag.
18256 For the current network, this results in going from 2887 to 2806
18257 HSDirs. Also, it makes it harder for an attacker to launch a sybil
18258 attack by raising the effort for a relay to become Stable which
18259 takes at the very least 7 days to do so and by keeping the 96
18260 hours uptime requirement for HSDir. Implements ticket 8243.
18262 o Minor bugfixes (compilation):
18263 - Build with --enable-systemd correctly when libsystemd is
18264 installed, but systemd is not. Fixes bug 16164; bugfix on
18265 0.2.6.3-alpha. Patch from Peter Palfrader.
18267 o Minor bugfixes (Linux seccomp2 sandbox):
18268 - Fix sandboxing to work when running as a relaymby renaming of
18269 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
18270 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
18271 - Allow systemd connections to work with the Linux seccomp2 sandbox
18272 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
18275 o Minor bugfixes (tests):
18276 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
18277 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
18280 Changes in version 0.2.6.8 - 2015-05-21
18281 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
18282 fixes an authority-side bug in assigning the HSDir flag. All directory
18283 authorities should upgrade.
18285 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
18286 - Revert commit that made directory authorities assign the HSDir
18287 flag to relays without a DirPort; this was bad because such relays
18288 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
18291 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
18292 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
18293 a client authorized hidden service. Fixes bug 15823; bugfix
18296 o Minor features (geoip):
18297 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
18298 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
18302 Changes in version 0.2.7.1-alpha - 2015-05-12
18303 Tor 0.2.7.1-alpha is the first alpha release in its series. It
18304 includes numerous small features and bugfixes against previous Tor
18305 versions, and numerous small infrastructure improvements. The most
18306 notable features are several new ways for controllers to interact with
18307 the hidden services subsystem.
18309 o New system requirements:
18310 - Tor no longer includes workarounds to support Libevent versions
18311 before 1.3e. Libevent 2.0 or later is recommended. Closes
18314 o Major features (controller):
18315 - Add the ADD_ONION and DEL_ONION commands that allow the creation
18316 and management of hidden services via the controller. Closes
18318 - New "GETINFO onions/current" and "GETINFO onions/detached"
18319 commands to get information about hidden services created via the
18320 controller. Part of ticket 6411.
18321 - New HSFETCH command to launch a request for a hidden service
18322 descriptor. Closes ticket 14847.
18323 - New HSPOST command to upload a hidden service descriptor. Closes
18324 ticket 3523. Patch by "DonnchaC".
18326 o Major bugfixes (hidden services):
18327 - Revert commit that made directory authorities assign the HSDir
18328 flag to relays without a DirPort; this was bad because such relays
18329 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
18332 o Minor features (clock-jump tolerance):
18333 - Recover better when our clock jumps back many hours, like might
18334 happen for Tails or Whonix users who start with a very wrong
18335 hardware clock, use Tor to discover a more accurate time, and then
18336 fix their clock. Resolves part of ticket 8766.
18338 o Minor features (command-line interface):
18339 - Make --hash-password imply --hush to prevent unnecessary noise.
18340 Closes ticket 15542. Patch from "cypherpunks".
18341 - Print a warning whenever we find a relative file path being used
18342 as torrc option. Resolves issue 14018.
18344 o Minor features (controller):
18345 - Add DirAuthority lines for default directory authorities to the
18346 output of the "GETINFO config/defaults" command if not already
18347 present. Implements ticket 14840.
18348 - Controllers can now use "GETINFO hs/client/desc/id/..." to
18349 retrieve items from the client's hidden service descriptor cache.
18350 Closes ticket 14845.
18351 - Implement a new controller command "GETINFO status/fresh-relay-
18352 descs" to fetch a descriptor/extrainfo pair that was generated on
18353 demand just for the controller's use. Implements ticket 14784.
18355 o Minor features (DoS-resistance):
18356 - Make it harder for attackers to overload hidden services with
18357 introductions, by blocking multiple introduction requests on the
18358 same circuit. Resolves ticket 15515.
18360 o Minor features (geoip):
18361 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
18362 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
18365 o Minor features (HS popularity countermeasure):
18366 - To avoid leaking HS popularity, don't cycle the introduction point
18367 when we've handled a fixed number of INTRODUCE2 cells but instead
18368 cycle it when a random number of introductions is reached, thus
18369 making it more difficult for an attacker to find out the amount of
18370 clients that have used the introduction point for a specific HS.
18371 Closes ticket 15745.
18373 o Minor features (logging):
18374 - Include the Tor version in all LD_BUG log messages, since people
18375 tend to cut and paste those into the bugtracker. Implements
18378 o Minor features (pluggable transports):
18379 - When launching managed pluggable transports on Linux systems,
18380 attempt to have the kernel deliver a SIGTERM on tor exit if the
18381 pluggable transport process is still running. Resolves
18383 - When launching managed pluggable transports, setup a valid open
18384 stdin in the child process that can be used to detect if tor has
18385 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
18386 can be used by implementations to detect this new behavior.
18387 Resolves ticket 15435.
18389 o Minor features (testing):
18390 - Add a test to verify that the compiler does not eliminate our
18391 memwipe() implementation. Closes ticket 15377.
18392 - Add make rule `check-changes` to verify the format of changes
18393 files. Closes ticket 15180.
18394 - Add unit tests for control_event_is_interesting(). Add a compile-
18395 time check that the number of events doesn't exceed the capacity
18396 of control_event_t.event_mask. Closes ticket 15431, checks for
18397 bugs similar to 13085. Patch by "teor".
18398 - Command-line argument tests moved to Stem. Resolves ticket 14806.
18399 - Integrate the ntor, backtrace, and zero-length keys tests into the
18400 automake test suite. Closes ticket 15344.
18401 - Remove assertions during builds to determine Tor's test coverage.
18402 We don't want to trigger these even in assertions, so including
18403 them artificially makes our branch coverage look worse than it is.
18404 This patch provides the new test-stem-full and coverage-html-full
18405 configure options. Implements ticket 15400.
18407 o Minor bugfixes (build):
18408 - Improve out-of-tree builds by making non-standard rules work and
18409 clean up additional files and directories. Fixes bug 15053; bugfix
18412 o Minor bugfixes (command-line interface):
18413 - When "--quiet" is provided along with "--validate-config", do not
18414 write anything to stdout on success. Fixes bug 14994; bugfix
18416 - When complaining about bad arguments to "--dump-config", use
18417 stderr, not stdout.
18419 o Minor bugfixes (configuration, unit tests):
18420 - Only add the default fallback directories when the DirAuthorities,
18421 AlternateDirAuthority, and FallbackDir directory config options
18422 are set to their defaults. The default fallback directory list is
18423 currently empty, this fix will only change tor's behavior when it
18424 has default fallback directories. Includes unit tests for
18425 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
18426 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
18428 o Minor bugfixes (correctness):
18429 - For correctness, avoid modifying a constant string in
18430 handle_control_postdescriptor. Fixes bug 15546; bugfix
18432 - Remove side-effects from tor_assert() calls. This was harmless,
18433 because we never disable assertions, but it is bad style and
18434 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
18437 o Minor bugfixes (hidden service):
18438 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
18439 a client authorized hidden service. Fixes bug 15823; bugfix
18441 - Remove an extraneous newline character from the end of hidden
18442 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
18444 o Minor bugfixes (interface):
18445 - Print usage information for --dump-config when it is used without
18446 an argument. Also, fix the error message to use different wording
18447 and add newline at the end. Fixes bug 15541; bugfix
18450 o Minor bugfixes (logs):
18451 - When building Tor under Clang, do not include an extra set of
18452 parentheses in log messages that include function names. Fixes bug
18453 15269; bugfix on every released version of Tor when compiled with
18454 recent enough Clang.
18456 o Minor bugfixes (network):
18457 - When attempting to use fallback technique for network interface
18458 lookup, disregard loopback and multicast addresses since they are
18459 unsuitable for public communications.
18461 o Minor bugfixes (statistics):
18462 - Disregard the ConnDirectionStatistics torrc options when Tor is
18463 not a relay since in that mode of operation no sensible data is
18464 being collected and because Tor might run into measurement hiccups
18465 when running as a client for some time, then becoming a relay.
18466 Fixes bug 15604; bugfix on 0.2.2.35.
18468 o Minor bugfixes (test networks):
18469 - When self-testing reachability, use ExtendAllowPrivateAddresses to
18470 determine if local/private addresses imply reachability. The
18471 previous fix used TestingTorNetwork, which implies
18472 ExtendAllowPrivateAddresses, but this excluded rare configurations
18473 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
18474 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
18475 issue discovered by CJ Ess.
18477 o Minor bugfixes (testing):
18478 - Check for matching value in server response in ntor_ref.py. Fixes
18479 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
18481 - Set the severity correctly when testing
18482 get_interface_addresses_ifaddrs() and
18483 get_interface_addresses_win32(), so that the tests fail gracefully
18484 instead of triggering an assertion. Fixes bug 15759; bugfix on
18485 0.2.6.3-alpha. Reported by Nicolas Derive.
18487 o Code simplification and refactoring:
18488 - Move the hacky fallback code out of get_interface_address6() into
18489 separate function and get it covered with unit-tests. Resolves
18491 - Refactor hidden service client-side cache lookup to intelligently
18492 report its various failure cases, and disentangle failure cases
18493 involving a lack of introduction points. Closes ticket 14391.
18494 - Use our own Base64 encoder instead of OpenSSL's, to allow more
18495 control over the output. Part of ticket 15652.
18498 - Improve the descriptions of statistics-related torrc options in
18499 the manpage to describe rationale and possible uses cases. Fixes
18501 - Improve the layout and formatting of ./configure --help messages.
18502 Closes ticket 15024. Patch from "cypherpunks".
18503 - Standardize on the term "server descriptor" in the manual page.
18504 Previously, we had used "router descriptor", "server descriptor",
18505 and "relay descriptor" interchangeably. Part of ticket 14987.
18508 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
18509 and always use the internal Base64 decoder. The internal decoder
18510 has been part of tor since 0.2.0.10-alpha, and no one should
18511 be using the OpenSSL one. Part of ticket 15652.
18512 - Remove the 'tor_strclear()' function; use memwipe() instead.
18513 Closes ticket 14922.
18515 o Removed features:
18516 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
18517 fingerprinting we now recommend pluggable transports; for forward-
18518 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
18519 - Remove the undocumented "--digests" command-line option. It
18520 complicated our build process, caused subtle build issues on
18521 multiple platforms, and is now redundant since we started
18522 including git version identifiers. Closes ticket 14742.
18523 - Tor no longer contains checks for ancient directory cache versions
18524 that didn't know about microdescriptors.
18525 - Tor no longer contains workarounds for stat files generated by
18526 super-old versions of Tor that didn't choose guards sensibly.
18529 Changes in version 0.2.4.27 - 2015-04-06
18530 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
18531 could be used by an attacker to crash hidden services, or crash clients
18532 visiting hidden services. Hidden services should upgrade as soon as
18533 possible; clients should upgrade whenever packages become available.
18535 This release also backports a simple improvement to make hidden
18536 services a bit less vulnerable to denial-of-service attacks.
18538 o Major bugfixes (security, hidden service):
18539 - Fix an issue that would allow a malicious client to trigger an
18540 assertion failure and halt a hidden service. Fixes bug 15600;
18541 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
18542 - Fix a bug that could cause a client to crash with an assertion
18543 failure when parsing a malformed hidden service descriptor. Fixes
18544 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
18546 o Minor features (DoS-resistance, hidden service):
18547 - Introduction points no longer allow multiple INTRODUCE1 cells to
18548 arrive on the same circuit. This should make it more expensive for
18549 attackers to overwhelm hidden services with introductions.
18550 Resolves ticket 15515.
18553 Changes in version 0.2.5.12 - 2015-04-06
18554 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
18555 could be used by an attacker to crash hidden services, or crash clients
18556 visiting hidden services. Hidden services should upgrade as soon as
18557 possible; clients should upgrade whenever packages become available.
18559 This release also backports a simple improvement to make hidden
18560 services a bit less vulnerable to denial-of-service attacks.
18562 o Major bugfixes (security, hidden service):
18563 - Fix an issue that would allow a malicious client to trigger an
18564 assertion failure and halt a hidden service. Fixes bug 15600;
18565 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
18566 - Fix a bug that could cause a client to crash with an assertion
18567 failure when parsing a malformed hidden service descriptor. Fixes
18568 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
18570 o Minor features (DoS-resistance, hidden service):
18571 - Introduction points no longer allow multiple INTRODUCE1 cells to
18572 arrive on the same circuit. This should make it more expensive for
18573 attackers to overwhelm hidden services with introductions.
18574 Resolves ticket 15515.
18577 Changes in version 0.2.6.7 - 2015-04-06
18578 Tor 0.2.6.7 fixes two security issues that could be used by an
18579 attacker to crash hidden services, or crash clients visiting hidden
18580 services. Hidden services should upgrade as soon as possible; clients
18581 should upgrade whenever packages become available.
18583 This release also contains two simple improvements to make hidden
18584 services a bit less vulnerable to denial-of-service attacks.
18586 o Major bugfixes (security, hidden service):
18587 - Fix an issue that would allow a malicious client to trigger an
18588 assertion failure and halt a hidden service. Fixes bug 15600;
18589 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
18590 - Fix a bug that could cause a client to crash with an assertion
18591 failure when parsing a malformed hidden service descriptor. Fixes
18592 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
18594 o Minor features (DoS-resistance, hidden service):
18595 - Introduction points no longer allow multiple INTRODUCE1 cells to
18596 arrive on the same circuit. This should make it more expensive for
18597 attackers to overwhelm hidden services with introductions.
18598 Resolves ticket 15515.
18599 - Decrease the amount of reattempts that a hidden service performs
18600 when its rendezvous circuits fail. This reduces the computational
18601 cost for running a hidden service under heavy load. Resolves
18605 Changes in version 0.2.6.6 - 2015-03-24
18606 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
18608 It adds numerous safety, security, correctness, and performance
18609 improvements. Client programs can be configured to use more kinds of
18610 sockets, AutomapHosts works better, the multithreading backend is
18611 improved, cell transmission is refactored, test coverage is much
18612 higher, more denial-of-service attacks are handled, guard selection is
18613 improved to handle long-term guards better, pluggable transports
18614 should work a bit better, and some annoying hidden service performance
18615 bugs should be addressed.
18617 o Minor bugfixes (portability):
18618 - Use the correct datatype in the SipHash-2-4 function to prevent
18619 compilers from assuming any sort of alignment. Fixes bug 15436;
18620 bugfix on 0.2.5.3-alpha.
18622 Changes in version 0.2.6.5-rc - 2015-03-18
18623 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
18624 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
18626 o Major bugfixes (client):
18627 - Avoid crashing when making certain configuration option changes on
18628 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
18631 o Major bugfixes (pluggable transports):
18632 - Initialize the extended OR Port authentication cookie before
18633 launching pluggable transports. This prevents a race condition
18634 that occurred when server-side pluggable transports would cache the
18635 authentication cookie before it has been (re)generated. Fixes bug
18636 15240; bugfix on 0.2.5.1-alpha.
18638 o Major bugfixes (portability):
18639 - Do not crash on startup when running on Solaris. Fixes a bug
18640 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
18643 o Minor features (heartbeat):
18644 - On relays, report how many connections we negotiated using each
18645 version of the Tor link protocols. This information will let us
18646 know if removing support for very old versions of the Tor
18647 protocols is harming the network. Closes ticket 15212.
18649 o Code simplification and refactoring:
18650 - Refactor main loop to extract the 'loop' part. This makes it
18651 easier to run Tor under Shadow. Closes ticket 15176.
18654 Changes in version 0.2.5.11 - 2015-03-17
18655 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
18657 It backports several bugfixes from the 0.2.6 branch, including a
18658 couple of medium-level security fixes for relays and exit nodes.
18659 It also updates the list of directory authorities.
18661 o Directory authority changes:
18662 - Remove turtles as a directory authority.
18663 - Add longclaw as a new (v3) directory authority. This implements
18664 ticket 13296. This keeps the directory authority count at 9.
18665 - The directory authority Faravahar has a new IP address. This
18666 closes ticket 14487.
18668 o Major bugfixes (crash, OSX, security):
18669 - Fix a remote denial-of-service opportunity caused by a bug in
18670 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
18673 o Major bugfixes (relay, stability, possible security):
18674 - Fix a bug that could lead to a relay crashing with an assertion
18675 failure if a buffer of exactly the wrong layout was passed to
18676 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
18677 0.2.0.10-alpha. Patch from 'cypherpunks'.
18678 - Do not assert if the 'data' pointer on a buffer is advanced to the
18679 very end of the buffer; log a BUG message instead. Only assert if
18680 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
18682 o Major bugfixes (exit node stability):
18683 - Fix an assertion failure that could occur under high DNS load.
18684 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
18685 diagnosed and fixed by "cypherpunks".
18687 o Major bugfixes (Linux seccomp2 sandbox):
18688 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
18689 crash during attempts to call wait4. Fixes bug 15088; bugfix on
18690 0.2.5.1-alpha. Patch from "sanic".
18692 o Minor features (controller):
18693 - New "GETINFO bw-event-cache" to get information about recent
18694 bandwidth events. Closes ticket 14128. Useful for controllers to
18695 get recent bandwidth history after the fix for ticket 13988.
18697 o Minor features (geoip):
18698 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
18699 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
18702 o Minor bugfixes (client, automapping):
18703 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
18704 no value follows the option. Fixes bug 14142; bugfix on
18705 0.2.4.7-alpha. Patch by "teor".
18706 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
18707 14195; bugfix on 0.1.0.1-rc.
18709 o Minor bugfixes (compilation):
18710 - Build without warnings with the stock OpenSSL srtp.h header, which
18711 has a duplicate declaration of SSL_get_selected_srtp_profile().
18712 Fixes bug 14220; this is OpenSSL's bug, not ours.
18714 o Minor bugfixes (directory authority):
18715 - Allow directory authorities to fetch more data from one another if
18716 they find themselves missing lots of votes. Previously, they had
18717 been bumping against the 10 MB queued data limit. Fixes bug 14261;
18718 bugfix on 0.1.2.5-alpha.
18719 - Enlarge the buffer to read bwauth generated files to avoid an
18720 issue when parsing the file in dirserv_read_measured_bandwidths().
18721 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
18723 o Minor bugfixes (statistics):
18724 - Increase period over which bandwidth observations are aggregated
18725 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
18727 o Minor bugfixes (preventative security, C safety):
18728 - When reading a hexadecimal, base-32, or base-64 encoded value from
18729 a string, always overwrite the whole output buffer. This prevents
18730 some bugs where we would look at (but fortunately, not reveal)
18731 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
18735 Changes in version 0.2.4.26 - 2015-03-17
18736 Tor 0.2.4.26 includes an updated list of directory authorities. It
18737 also backports a couple of stability and security bugfixes from 0.2.5
18740 o Directory authority changes:
18741 - Remove turtles as a directory authority.
18742 - Add longclaw as a new (v3) directory authority. This implements
18743 ticket 13296. This keeps the directory authority count at 9.
18744 - The directory authority Faravahar has a new IP address. This
18745 closes ticket 14487.
18747 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
18748 - Fix an assertion failure that could occur under high DNS load.
18749 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
18750 diagnosed and fixed by "cypherpunks".
18752 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
18753 - Fix a bug that could lead to a relay crashing with an assertion
18754 failure if a buffer of exactly the wrong layout was passed to
18755 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
18756 0.2.0.10-alpha. Patch from 'cypherpunks'.
18757 - Do not assert if the 'data' pointer on a buffer is advanced to the
18758 very end of the buffer; log a BUG message instead. Only assert if
18759 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
18761 o Minor features (geoip):
18762 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
18763 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
18766 Changes in version 0.2.6.4-rc - 2015-03-09
18767 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
18768 attacker might be able to use in order to crash certain Tor
18769 directories. It also resolves some minor issues left over from, or
18770 introduced in, Tor 0.2.6.3-alpha or earlier.
18772 o Major bugfixes (crash, OSX, security):
18773 - Fix a remote denial-of-service opportunity caused by a bug in
18774 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
18777 o Major bugfixes (relay, stability, possible security):
18778 - Fix a bug that could lead to a relay crashing with an assertion
18779 failure if a buffer of exactly the wrong layout is passed to
18780 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
18781 0.2.0.10-alpha. Patch from "cypherpunks".
18782 - Do not assert if the 'data' pointer on a buffer is advanced to the
18783 very end of the buffer; log a BUG message instead. Only assert if
18784 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
18786 o Major bugfixes (FreeBSD IPFW transparent proxy):
18787 - Fix address detection with FreeBSD transparent proxies, when
18788 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
18791 o Major bugfixes (Linux seccomp2 sandbox):
18792 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
18793 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
18795 - Allow AF_UNIX hidden services to be used with the seccomp2
18796 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
18797 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
18798 crash during attempts to call wait4. Fixes bug 15088; bugfix on
18799 0.2.5.1-alpha. Patch from "sanic".
18801 o Minor features (controller):
18802 - Messages about problems in the bootstrap process now include
18803 information about the server we were trying to connect to when we
18804 noticed the problem. Closes ticket 15006.
18806 o Minor features (geoip):
18807 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
18808 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
18811 o Minor features (logs):
18812 - Quiet some log messages in the heartbeat and at startup. Closes
18815 o Minor bugfixes (certificate handling):
18816 - If an authority operator accidentally makes a signing certificate
18817 with a future publication time, do not discard its real signing
18818 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
18819 - Remove any old authority certificates that have been superseded
18820 for at least two days. Previously, we would keep superseded
18821 certificates until they expired, if they were published close in
18822 time to the certificate that superseded them. Fixes bug 11454;
18823 bugfix on 0.2.1.8-alpha.
18825 o Minor bugfixes (compilation):
18826 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
18828 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
18831 o Minor bugfixes (testing):
18832 - Fix endianness issues in unit test for resolve_my_address() to
18833 have it pass on big endian systems. Fixes bug 14980; bugfix on
18835 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
18836 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
18837 - When running the new 'make test-stem' target, use the configured
18838 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
18839 from "cypherpunks".
18840 - When running the zero-length-keys tests, do not use the default
18841 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
18844 o Directory authority IP change:
18845 - The directory authority Faravahar has a new IP address. This
18846 closes ticket 14487.
18849 - Remove some lingering dead code that once supported mempools.
18850 Mempools were disabled by default in 0.2.5, and removed entirely
18851 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
18855 Changes in version 0.2.6.3-alpha - 2015-02-19
18856 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
18857 the 0.2.6.x series. It introduces support for more kinds of sockets,
18858 makes it harder to accidentally run an exit, improves our
18859 multithreading backend, incorporates several fixes for the
18860 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
18862 If no major regressions or security holes are found in this version,
18863 the next version will be a release candidate.
18865 o Deprecated versions:
18866 - Tor relays older than 0.2.4.18-rc are no longer allowed to
18867 advertise themselves on the network. Closes ticket 13555.
18869 o Major features (security, unix domain sockets):
18870 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
18871 applications can reach Tor without having to create AF_INET or
18872 AF_INET6 sockets, meaning they can completely disable their
18873 ability to make non-Tor network connections. To create a socket of
18874 this type, use "SocksPort unix:/path/to/socket". Implements
18876 - Support mapping hidden service virtual ports to AF_UNIX sockets.
18877 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
18878 Implements ticket 11485.
18880 o Major features (changed defaults):
18881 - Prevent relay operators from unintentionally running exits: When a
18882 relay is configured as an exit node, we now warn the user unless
18883 the "ExitRelay" option is set to 1. We warn even more loudly if
18884 the relay is configured with the default exit policy, since this
18885 can indicate accidental misconfiguration. Setting "ExitRelay 0"
18886 stops Tor from running as an exit relay. Closes ticket 10067.
18888 o Major features (directory system):
18889 - When downloading server- or microdescriptors from a directory
18890 server, we no longer launch multiple simultaneous requests to the
18891 same server. This reduces load on the directory servers,
18892 especially when directory guards are in use. Closes ticket 9969.
18893 - When downloading server- or microdescriptors over a tunneled
18894 connection, do not limit the length of our requests to what the
18895 Squid proxy is willing to handle. Part of ticket 9969.
18896 - Authorities can now vote on the correct digests and latest
18897 versions for different software packages. This allows packages
18898 that include Tor to use the Tor authority system as a way to get
18899 notified of updates and their correct digests. Implements proposal
18900 227. Closes ticket 10395.
18902 o Major features (guards):
18903 - Introduce the Guardfraction feature to improves load balancing on
18904 guard nodes. Specifically, it aims to reduce the traffic gap that
18905 guard nodes experience when they first get the Guard flag. This is
18906 a required step if we want to increase the guard lifetime to 9
18907 months or greater. Closes ticket 9321.
18909 o Major features (performance):
18910 - Make the CPU worker implementation more efficient by avoiding the
18911 kernel and lengthening pipelines. The original implementation used
18912 sockets to transfer data from the main thread to the workers, and
18913 didn't allow any thread to be assigned more than a single piece of
18914 work at once. The new implementation avoids communications
18915 overhead by making requests in shared memory, avoiding kernel IO
18916 where possible, and keeping more requests in flight at once.
18917 Implements ticket 9682.
18919 o Major features (relay):
18920 - Raise the minimum acceptable configured bandwidth rate for bridges
18921 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
18922 20 KiB/sec.) Closes ticket 13822.
18924 o Major bugfixes (exit node stability):
18925 - Fix an assertion failure that could occur under high DNS load.
18926 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
18927 diagnosed and fixed by "cypherpunks".
18929 o Major bugfixes (mixed relay-client operation):
18930 - When running as a relay and client at the same time (not
18931 recommended), if we decide not to use a new guard because we want
18932 to retry older guards, only close the locally-originating circuits
18933 passing through that guard. Previously we would close all the
18934 circuits through that guard. Fixes bug 9819; bugfix on
18935 0.2.1.1-alpha. Reported by "skruffy".
18937 o Minor features (build):
18938 - New --disable-system-torrc compile-time option to prevent Tor from
18939 looking for the system-wide torrc or torrc-defaults files.
18940 Resolves ticket 13037.
18942 o Minor features (controller):
18943 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
18944 events so controllers can observe circuit isolation inputs. Closes
18946 - ControlPort now supports the unix:/path/to/socket syntax as an
18947 alternative to the ControlSocket option, for consistency with
18948 SocksPort and HiddenServicePort. Closes ticket 14451.
18949 - New "GETINFO bw-event-cache" to get information about recent
18950 bandwidth events. Closes ticket 14128. Useful for controllers to
18951 get recent bandwidth history after the fix for ticket 13988.
18953 o Minor features (Denial of service resistance):
18954 - Count the total number of bytes used storing hidden service
18955 descriptors against the value of MaxMemInQueues. If we're low on
18956 memory, and more than 20% of our memory is used holding hidden
18957 service descriptors, free them until no more than 10% of our
18958 memory holds hidden service descriptors. Free the least recently
18959 fetched descriptors first. Resolves ticket 13806.
18960 - When we have recently been under memory pressure (over 3/4 of
18961 MaxMemInQueues is allocated), then allocate smaller zlib objects
18962 for small requests. Closes ticket 11791.
18964 o Minor features (geoip):
18965 - Update geoip and geoip6 files to the January 7 2015 Maxmind
18966 GeoLite2 Country database.
18968 o Minor features (guard nodes):
18969 - Reduce the time delay before saving guard status to disk from 10
18970 minutes to 30 seconds (or from one hour to 10 minutes if
18971 AvoidDiskWrites is set). Closes ticket 12485.
18973 o Minor features (hidden service):
18974 - Make Sybil attacks against hidden services harder by changing the
18975 minimum time required to get the HSDir flag from 25 hours up to 96
18976 hours. Addresses ticket 14149.
18977 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
18978 services to disable the anti-scanning feature introduced in
18979 0.2.6.2-alpha. With this option not set, a connection to an
18980 unlisted port closes the circuit. With this option set, only a
18981 RELAY_DONE cell is sent. Closes ticket 14084.
18983 o Minor features (interface):
18984 - Implement "-f -" command-line option to read torrc configuration
18985 from standard input, if you don't want to store the torrc file in
18986 the file system. Implements feature 13865.
18988 o Minor features (logging):
18989 - Add a count of unique clients to the bridge heartbeat message.
18990 Resolves ticket 6852.
18991 - Suppress "router info incompatible with extra info" message when
18992 reading extrainfo documents from cache. (This message got loud
18993 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
18995 - Elevate hidden service authorized-client message from DEBUG to
18996 INFO. Closes ticket 14015.
18998 o Minor features (stability):
18999 - Add assertions in our hash-table iteration code to check for
19000 corrupted values that could cause infinite loops. Closes
19003 o Minor features (systemd):
19004 - Various improvements and modernizations in systemd hardening
19005 support. Closes ticket 13805. Patch from Craig Andrews.
19007 o Minor features (testing networks):
19008 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
19009 and the default on a testing network to 2 minutes. Drop the
19010 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
19011 keep the default on a testing network at 30 seconds. This reduces
19012 HS bootstrap time to around 25 seconds. Also, change the default
19013 time in test-network.sh to match. Closes ticket 13401. Patch
19015 - Create TestingDirAuthVoteHSDir to correspond to
19016 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
19017 HSDir flag for the listed relays regardless of uptime or ORPort
19018 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
19019 Partial implementation for ticket 14067. Patch by "teor".
19021 o Minor features (tor2web mode):
19022 - Introduce the config option Tor2webRendezvousPoints, which allows
19023 clients in Tor2webMode to select a specific Rendezvous Point to be
19024 used in HS circuits. This might allow better performance for
19025 Tor2Web nodes. Implements ticket 12844.
19027 o Minor bugfixes (client DNS):
19028 - Report the correct cached DNS expiration times on SOCKS port or in
19029 DNS replies. Previously, we would report everything as "never
19030 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
19031 - Avoid a small memory leak when we find a cached answer for a
19032 reverse DNS lookup in a client-side DNS cache. (Remember, client-
19033 side DNS caching is off by default, and is not recommended.) Fixes
19034 bug 14259; bugfix on 0.2.0.1-alpha.
19036 o Minor bugfixes (client, automapping):
19037 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
19038 no value follows the option. Fixes bug 14142; bugfix on
19039 0.2.4.7-alpha. Patch by "teor".
19040 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
19041 14195; bugfix on 0.1.0.1-rc.
19042 - Prevent changes to other options from removing the wildcard value
19043 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
19045 - Allow MapAddress and AutomapHostsOnResolve to work together when
19046 an address is mapped into another address type (like .onion) that
19047 must be automapped at resolve time. Fixes bug 7555; bugfix
19050 o Minor bugfixes (client, bridges):
19051 - When we are using bridges and we had a network connectivity
19052 problem, only retry connecting to our currently configured
19053 bridges, not all bridges we know about and remember using. Fixes
19054 bug 14216; bugfix on 0.2.2.17-alpha.
19056 o Minor bugfixes (client, IPv6):
19057 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
19058 flag is not set; and not because the NoIPv4Traffic flag was set.
19059 Previously we'd looked at the NoIPv4Traffic flag for both types of
19060 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
19062 o Minor bugfixes (compilation):
19063 - The address of an array in the middle of a structure will always
19064 be non-NULL. clang recognises this and complains. Disable the
19065 tautologous and redundant check to silence this warning. Fixes bug
19066 14001; bugfix on 0.2.1.2-alpha.
19067 - Avoid warnings when building with systemd 209 or later. Fixes bug
19068 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
19069 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
19070 Addresses ticket 14188.
19071 - Build without warnings with the stock OpenSSL srtp.h header, which
19072 has a duplicate declaration of SSL_get_selected_srtp_profile().
19073 Fixes bug 14220; this is OpenSSL's bug, not ours.
19074 - Do not compile any code related to Tor2Web mode when Tor2Web mode
19075 is not enabled at compile time. Previously, this code was included
19076 in a disabled state. See discussion on ticket 12844.
19077 - Remove the --disable-threads configure option again. It was
19078 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
19079 14819; bugfix on 0.2.6.2-alpha.
19081 o Minor bugfixes (controller):
19082 - Report "down" in response to the "GETINFO entry-guards" command
19083 when relays are down with an unreachable_since value. Previously,
19084 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
19085 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
19086 14116; bugfix on 0.2.2.9-alpha.
19087 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
19088 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
19090 o Minor bugfixes (directory authority):
19091 - Allow directory authorities to fetch more data from one another if
19092 they find themselves missing lots of votes. Previously, they had
19093 been bumping against the 10 MB queued data limit. Fixes bug 14261;
19094 bugfix on 0.1.2.5-alpha.
19095 - Do not attempt to download extrainfo documents which we will be
19096 unable to validate with a matching server descriptor. Fixes bug
19097 13762; bugfix on 0.2.0.1-alpha.
19098 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
19099 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
19100 - Enlarge the buffer to read bwauth generated files to avoid an
19101 issue when parsing the file in dirserv_read_measured_bandwidths().
19102 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
19104 o Minor bugfixes (file handling):
19105 - Stop failing when key files are zero-length. Instead, generate new
19106 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
19107 on all versions of Tor. Patch by "teor".
19108 - Stop generating a fresh .old RSA onion key file when the .old file
19109 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
19110 - Avoid overwriting .old key files with empty key files.
19111 - Skip loading zero-length extrainfo store, router store, stats,
19112 state, and key files.
19113 - Avoid crashing when trying to reload a torrc specified as a
19114 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
19117 o Minor bugfixes (hidden services):
19118 - Close the introduction circuit when we have no more usable intro
19119 points, instead of waiting for it to time out. This also ensures
19120 that no follow-up HS descriptor fetch is triggered when the
19121 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
19122 - When fetching a hidden service descriptor for a down service that
19123 was recently up, do not keep refetching until we try the same
19124 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
19125 - Successfully launch Tor with a nonexistent hidden service
19126 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
19127 14106; bugfix on 0.2.6.2-alpha.
19129 o Minor bugfixes (logging):
19130 - Avoid crashing when there are more log domains than entries in
19131 domain_list. Bugfix on 0.2.3.1-alpha.
19132 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
19134 - Don't log messages to stdout twice when starting up. Fixes bug
19135 13993; bugfix on 0.2.6.1-alpha.
19137 o Minor bugfixes (parsing):
19138 - Stop accepting milliseconds (or other junk) at the end of
19139 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
19140 - Support two-number and three-number version numbers correctly, in
19141 case we change the Tor versioning system in the future. Fixes bug
19142 13661; bugfix on 0.0.8pre1.
19144 o Minor bugfixes (path counting):
19145 - When deciding whether the consensus lists any exit nodes, count
19146 the number listed in the consensus, not the number we have
19147 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
19148 - When deciding whether we have any exit nodes, only examine
19149 ExitNodes when the ExitNodes option is actually set. Fixes part of
19150 bug 14918; bugfix on 0.2.6.2-alpha.
19151 - Get rid of redundant and possibly scary warnings that we are
19152 missing directory information while we bootstrap. Fixes part of
19153 bug 14918; bugfix on 0.2.6.2-alpha.
19155 o Minor bugfixes (portability):
19156 - Fix the ioctl()-based network interface lookup code so that it
19157 will work on systems that have variable-length struct ifreq, for
19159 - Fix scheduler compilation on targets where char is unsigned. Fixes
19160 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
19162 o Minor bugfixes (sandbox):
19163 - Allow glibc fatal errors to be sent to stderr before Tor exits.
19164 Previously, glibc would try to write them to /dev/tty, and the
19165 sandbox would trap the call and make Tor exit prematurely. Fixes
19166 bug 14759; bugfix on 0.2.5.1-alpha.
19168 o Minor bugfixes (shutdown):
19169 - When shutting down, always call event_del() on lingering read or
19170 write events before freeing them. Otherwise, we risk double-frees
19171 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
19174 o Minor bugfixes (small memory leaks):
19175 - Avoid leaking memory when using IPv6 virtual address mappings.
19176 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
19179 o Minor bugfixes (statistics):
19180 - Increase period over which bandwidth observations are aggregated
19181 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
19183 o Minor bugfixes (systemd support):
19184 - Fix detection and operation of systemd watchdog. Fixes part of bug
19185 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
19186 - Run correctly under systemd with the RunAsDaemon option set. Fixes
19187 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
19188 - Inform the systemd supervisor about more changes in the Tor
19189 process status. Implements part of ticket 14141. Patch from
19191 - Cause the "--disable-systemd" option to actually disable systemd
19192 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
19195 o Minor bugfixes (TLS):
19196 - Check more thoroughly throughout the TLS code for possible
19197 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
19199 o Minor bugfixes (transparent proxy):
19200 - Use getsockname, not getsockopt, to retrieve the address for a
19201 TPROXY-redirected connection. Fixes bug 13796; bugfix
19204 o Code simplification and refactoring:
19205 - Move fields related to isolating and configuring client ports into
19206 a shared structure. Previously, they were duplicated across
19207 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
19208 to copy them correctly had been the cause of at least one bug in
19209 the past. Closes ticket 8546.
19210 - Refactor the get_interface_addresses_raw() doom-function into
19211 multiple smaller and simpler subfunctions. Cover the resulting
19212 subfunctions with unit-tests. Fixes a significant portion of
19214 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
19215 only for version <= 0.2.2.24 which is now deprecated. Closes
19217 - Remove a test for a long-defunct broken version-one
19221 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
19222 for writing the OpenBSD-specific tips. Resolves ticket 13702.
19223 - Make the tor-resolve documentation match its help string and its
19224 options. Resolves part of ticket 14325.
19225 - Log a more useful error message from tor-resolve when failing to
19226 look up a hidden service address. Resolves part of ticket 14325.
19228 o Downgraded warnings:
19229 - Don't warn when we've attempted to contact a relay using the wrong
19230 ntor onion key. Closes ticket 9635.
19232 o Removed features:
19233 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
19234 longer silently accepted as an alias for "ExitNodes".
19235 - The --enable-mempool and --enable-buf-freelists options, which
19236 were originally created to work around bad malloc implementations,
19237 no longer exist. They were off-by-default in 0.2.5. Closes
19241 - Make the checkdir/perms test complete successfully even if the
19242 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
19243 - Test that tor does not fail when key files are zero-length. Check
19244 that tor generates new keys, and overwrites the empty key files.
19245 - Test that tor generates new keys when keys are missing
19246 (existing behavior).
19247 - Test that tor does not overwrite key files that already contain
19248 data (existing behavior). Tests bug 13111. Patch by "teor".
19249 - New "make test-stem" target to run stem integration tests.
19250 Requires that the "STEM_SOURCE_DIR" environment variable be set.
19251 Closes ticket 14107.
19252 - Make the test_cmdline_args.py script work correctly on Windows.
19253 Patch from Gisle Vanem.
19254 - Move the slower unit tests into a new "./src/test/test-slow"
19255 binary that can be run independently of the other tests. Closes
19257 - Avoid undefined behavior when sampling huge values from the
19258 Laplace distribution. This made unittests fail on Raspberry Pi.
19259 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
19262 Changes in version 0.2.6.2-alpha - 2014-12-31
19263 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
19264 It introduces a major new backend for deciding when to send cells on
19265 channels, which should lead down the road to big performance
19266 increases. It contains security and statistics features for better
19267 work on hidden services, and numerous bugfixes.
19269 This release contains many new unit tests, along with major
19270 performance improvements for running testing networks using Chutney.
19271 Thanks to a series of patches contributed by "teor", testing networks
19272 should now bootstrap in seconds, rather than minutes.
19274 o Major features (relay, infrastructure):
19275 - Complete revision of the code that relays use to decide which cell
19276 to send next. Formerly, we selected the best circuit to write on
19277 each channel, but we didn't select among channels in any
19278 sophisticated way. Now, we choose the best circuits globally from
19279 among those whose channels are ready to deliver traffic.
19281 This patch implements a new inter-cmux comparison API, a global
19282 high/low watermark mechanism and a global scheduler loop for
19283 transmission prioritization across all channels as well as among
19284 circuits on one channel. This schedule is currently tuned to
19285 (tolerantly) avoid making changes in network performance, but it
19286 should form the basis for major circuit performance increases in
19287 the future. Code by Andrea; tuning by Rob Jansen; implements
19290 o Major features (hidden services):
19291 - Make HS port scanning more difficult by immediately closing the
19292 circuit when a user attempts to connect to a nonexistent port.
19293 Closes ticket 13667.
19294 - Add a HiddenServiceStatistics option that allows Tor relays to
19295 gather and publish statistics about the overall size and volume of
19296 hidden service usage. Specifically, when this option is turned on,
19297 an HSDir will publish an approximate number of hidden services
19298 that have published descriptors to it the past 24 hours. Also, if
19299 a relay has acted as a hidden service rendezvous point, it will
19300 publish the approximate amount of rendezvous cells it has relayed
19301 the past 24 hours. The statistics themselves are obfuscated so
19302 that the exact values cannot be derived. For more details see
19303 proposal 238, "Better hidden service stats from Tor relays". This
19304 feature is currently disabled by default. Implements feature 13192.
19306 o Major bugfixes (client, automap):
19307 - Repair automapping with IPv6 addresses. This automapping should
19308 have worked previously, but one piece of debugging code that we
19309 inserted to detect a regression actually caused the regression to
19310 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
19311 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
19314 o Major bugfixes (hidden services):
19315 - When closing an introduction circuit that was opened in parallel
19316 with others, don't mark the introduction point as unreachable.
19317 Previously, the first successful connection to an introduction
19318 point would make the other introduction points get marked as
19319 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
19321 o Directory authority changes:
19322 - Remove turtles as a directory authority.
19323 - Add longclaw as a new (v3) directory authority. This implements
19324 ticket 13296. This keeps the directory authority count at 9.
19326 o Major removed features:
19327 - Tor clients no longer support connecting to hidden services
19328 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
19329 option has been removed. (There shouldn't be any hidden services
19330 running these versions on the network.) Closes ticket 7803.
19332 o Minor features (client):
19333 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
19334 is enabled, reject requests with IP addresses as hostnames.
19335 Resolves ticket 13315.
19337 o Minor features (controller):
19338 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
19339 write an unscheduled heartbeat message to the log. Implements
19342 o Minor features (geoip):
19343 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
19346 o Minor features (hidden services):
19347 - When re-enabling the network, don't try to build introduction
19348 circuits until we have successfully built a circuit. This makes
19349 hidden services come up faster when the network is re-enabled.
19350 Patch from "akwizgran". Closes ticket 13447.
19351 - When we fail to retrieve a hidden service descriptor, send the
19352 controller an "HS_DESC FAILED" controller event. Implements
19354 - New HiddenServiceDirGroupReadable option to cause hidden service
19355 directories and hostname files to be created group-readable. Patch
19356 from "anon", David Stainton, and "meejah". Closes ticket 11291.
19358 o Minor features (systemd):
19359 - Where supported, when running with systemd, report successful
19360 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
19361 - When running with systemd, support systemd watchdog messages. Part
19362 of ticket 11016. Patch by Michael Scherer.
19364 o Minor features (transparent proxy):
19365 - Update the transparent proxy option checks to allow for both ipfw
19366 and pf on OS X. Closes ticket 14002.
19367 - Use the correct option when using IPv6 with transparent proxy
19368 support on Linux. Resolves 13808. Patch by Francisco Blas
19371 o Minor bugfixes (preventative security, C safety):
19372 - When reading a hexadecimal, base-32, or base-64 encoded value from
19373 a string, always overwrite the whole output buffer. This prevents
19374 some bugs where we would look at (but fortunately, not reveal)
19375 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
19377 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
19378 just the part that's used. This makes it harder for data leak bugs
19379 to occur in the event of other programming failures. Resolves
19382 o Minor bugfixes (client, microdescriptors):
19383 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
19384 computing which microdescriptors to download. This keeps us from
19385 erroneous download behavior if two microdescriptor digests ever
19386 have the same first 160 bits. Fixes part of bug 13399; bugfix
19388 - Reset a router's status if its microdescriptor digest changes,
19389 even if the first 160 bits remain the same. Fixes part of bug
19390 13399; bugfix on 0.2.3.1-alpha.
19392 o Minor bugfixes (compilation):
19393 - Silence clang warnings under --enable-expensive-hardening,
19394 including implicit truncation of 64 bit values to 32 bit, const
19395 char assignment to self, tautological compare, and additional
19396 parentheses around equality tests. Fixes bug 13577; bugfix
19398 - Fix a clang warning about checking whether an address in the
19399 middle of a structure is NULL. Fixes bug 14001; bugfix
19402 o Minor bugfixes (hidden services):
19403 - Correctly send a controller event when we find that a rendezvous
19404 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
19405 - Pre-check directory permissions for new hidden-services to avoid
19406 at least one case of "Bug: Acting on config options left us in a
19407 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
19408 - When adding a new hidden service (for example, via SETCONF), Tor
19409 no longer congratulates the user for running a relay. Fixes bug
19410 13941; bugfix on 0.2.6.1-alpha.
19411 - When fetching hidden service descriptors, we now check not only
19412 for whether we got the hidden service we had in mind, but also
19413 whether we got the particular descriptors we wanted. This prevents
19414 a class of inefficient but annoying DoS attacks by hidden service
19415 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
19418 o Minor bugfixes (Linux seccomp2 sandbox):
19419 - Make transparent proxy support work along with the seccomp2
19420 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
19421 by Francisco Blas Izquierdo Riera.
19422 - Fix a memory leak in tor-resolve when running with the sandbox
19423 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
19425 o Minor bugfixes (logging):
19426 - Downgrade warnings about RSA signature failures to info log level.
19427 Emit a warning when an extra info document is found incompatible
19428 with a corresponding router descriptor. Fixes bug 9812; bugfix
19430 - Make connection_ap_handshake_attach_circuit() log the circuit ID
19431 correctly. Fixes bug 13701; bugfix on 0.0.6.
19433 o Minor bugfixes (misc):
19434 - Stop allowing invalid address patterns like "*/24" that contain
19435 both a wildcard address and a bit prefix length. This affects all
19436 our address-range parsing code. Fixes bug 7484; bugfix
19439 o Minor bugfixes (testing networks, fast startup):
19440 - Allow Tor to build circuits using a consensus with no exits. If
19441 the consensus has no exits (typical of a bootstrapping test
19442 network), allow Tor to build circuits once enough descriptors have
19443 been downloaded. This assists in bootstrapping a testing Tor
19444 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
19446 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
19447 header to directory servers. This allows us to obtain consensuses
19448 promptly when the consensus interval is very short. This assists
19449 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
19450 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
19451 - Stop assuming that private addresses are local when checking
19452 reachability in a TestingTorNetwork. Instead, when testing, assume
19453 all OR connections are remote. (This is necessary due to many test
19454 scenarios running all relays on localhost.) This assists in
19455 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
19456 0.1.0.1-rc. Patch by "teor".
19457 - Avoid building exit circuits from a consensus with no exits. Now
19458 thanks to our fix for 13718, we accept a no-exit network as not
19459 wholly lost, but we need to remember not to try to build exit
19460 circuits on it. Closes ticket 13814; patch by "teor".
19461 - Stop requiring exits to have non-zero bandwithcapacity in a
19462 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
19463 ignore exit bandwidthcapacity. This assists in bootstrapping a
19464 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
19465 on 0.2.0.3-alpha. Patch by "teor".
19466 - Add "internal" to some bootstrap statuses when no exits are
19467 available. If the consensus does not contain Exits, Tor will only
19468 build internal circuits. In this case, relevant statuses will
19469 contain the word "internal" as indicated in the Tor control-
19470 spec.txt. When bootstrap completes, Tor will be ready to build
19471 internal circuits. If a future consensus contains Exits, exit
19472 circuits may become available. Fixes part of bug 13718; bugfix on
19473 0.2.4.10-alpha. Patch by "teor".
19474 - Decrease minimum consensus interval to 10 seconds when
19475 TestingTorNetwork is set, or 5 seconds for the first consensus.
19476 Fix assumptions throughout the code that assume larger intervals.
19477 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
19479 - Avoid excluding guards from path building in minimal test
19480 networks, when we're in a test network and excluding guards would
19481 exclude all relays. This typically occurs in incredibly small tor
19482 networks, and those using "TestingAuthVoteGuard *". Fixes part of
19483 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
19485 o Code simplification and refactoring:
19486 - Stop using can_complete_circuits as a global variable; access it
19487 with a function instead.
19488 - Avoid using operators directly as macro arguments: this lets us
19489 apply coccinelle transformations to our codebase more directly.
19490 Closes ticket 13172.
19491 - Combine the functions used to parse ClientTransportPlugin and
19492 ServerTransportPlugin into a single function. Closes ticket 6456.
19493 - Add inline functions and convenience macros for inspecting channel
19494 state. Refactor the code to use convenience macros instead of
19495 checking channel state directly. Fixes issue 7356.
19496 - Document all members of was_router_added_t and rename
19497 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
19498 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
19499 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
19500 constant instead of hardcoded value. Fixes issue 13840.
19501 - Refactor our generic strmap and digestmap types into a single
19502 implementation, so that we can add a new digest256map
19506 - Document the bridge-authority-only 'networkstatus-bridges' file.
19507 Closes ticket 13713; patch from "tom".
19508 - Fix typo in PredictedPortsRelevanceTime option description in
19509 manpage. Resolves issue 13707.
19510 - Stop suggesting that users specify relays by nickname: it isn't a
19511 good idea. Also, properly cross-reference how to specify relays in
19512 all parts of manual documenting options that take a list of
19513 relays. Closes ticket 13381.
19514 - Clarify the HiddenServiceDir option description in manpage to make
19515 it clear that relative paths are taken with respect to the current
19516 working directory. Also clarify that this behavior is not
19517 guaranteed to remain indefinitely. Fixes issue 13913.
19520 - New tests for many parts of channel, relay, and circuitmux
19521 functionality. Code by Andrea; part of 9262.
19522 - New tests for parse_transport_line(). Part of ticket 6456.
19523 - In the unit tests, use chgrp() to change the group of the unit
19524 test temporary directory to the current user, so that the sticky
19525 bit doesn't interfere with tests that check directory groups.
19527 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
19531 Changes in version 0.2.6.1-alpha - 2014-10-30
19532 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
19533 includes numerous code cleanups and new tests, and fixes a large
19534 number of annoying bugs. Out-of-memory conditions are handled better
19535 than in 0.2.5, pluggable transports have improved proxy support, and
19536 clients now use optimistic data for contacting hidden services. Also,
19537 we are now more robust to changes in what we consider a parseable
19538 directory object, so that tightening restrictions does not have a risk
19539 of introducing infinite download loops.
19541 This is the first alpha release in a new series, so expect there to be
19542 bugs. Users who would rather test out a more stable branch should stay
19543 with 0.2.5.x for now.
19545 o New compiler and system requirements:
19546 - Tor 0.2.6.x requires that your compiler support more of the C99
19547 language standard than before. The 'configure' script now detects
19548 whether your compiler supports C99 mid-block declarations and
19549 designated initializers. If it does not, Tor will not compile.
19551 We may revisit this requirement if it turns out that a significant
19552 number of people need to build Tor with compilers that don't
19553 bother implementing a 15-year-old standard. Closes ticket 13233.
19554 - Tor no longer supports systems without threading support. When we
19555 began working on Tor, there were several systems that didn't have
19556 threads, or where the thread support wasn't able to run the
19557 threads of a single process on multiple CPUs. That no longer
19558 holds: every system where Tor needs to run well now has threading
19559 support. Resolves ticket 12439.
19561 o Removed platform support:
19562 - We no longer include special code to build on Windows CE; as far
19563 as we know, nobody has used Tor on Windows CE in a very long time.
19564 Closes ticket 11446.
19566 o Major features (bridges):
19567 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
19568 transports if they are configured via the "TOR_PT_PROXY"
19569 environment variable. Implements proposal 232. Resolves
19572 o Major features (client performance, hidden services):
19573 - Allow clients to use optimistic data when connecting to a hidden
19574 service, which should remove a round-trip from hidden service
19575 initialization. See proposal 181 for details. Implements
19578 o Major features (directory system):
19579 - Upon receiving an unparseable directory object, if its digest
19580 matches what we expected, then don't try to download it again.
19581 Previously, when we got a descriptor we didn't like, we would keep
19582 trying to download it over and over. Closes ticket 11243.
19584 o Major features (sample torrc):
19585 - Add a new, infrequently-changed "torrc.minimal". This file is
19586 similar to torrc.sample, but it will change as infrequently as
19587 possible, for the benefit of users whose systems prompt them for
19588 intervention whenever a default configuration file is changed.
19589 Making this change allows us to update torrc.sample to be a more
19590 generally useful "sample torrc".
19592 o Major bugfixes (directory authorities):
19593 - Do not assign the HSDir flag to relays if they are not Valid, or
19594 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
19596 o Major bugfixes (directory bandwidth performance):
19597 - Don't flush the zlib buffer aggressively when compressing
19598 directory information for clients. This should save about 7% of
19599 the bandwidth currently used for compressed descriptors and
19600 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
19602 o Minor features (security, memory wiping):
19603 - Ensure we securely wipe keys from memory after
19604 crypto_digest_get_digest and init_curve25519_keypair_from_file
19605 have finished using them. Resolves ticket 13477.
19607 o Minor features (security, out-of-memory handling):
19608 - When handling an out-of-memory condition, allocate less memory for
19609 temporary data structures. Fixes issue 10115.
19610 - When handling an out-of-memory condition, consider more types of
19611 buffers, including those on directory connections, and zlib
19612 buffers. Resolves ticket 11792.
19615 - When identity keypair is generated for first time, log a
19616 congratulatory message that links to the new relay lifecycle
19617 document. Implements feature 10427.
19619 o Minor features (client):
19620 - Clients are now willing to send optimistic data (before they
19621 receive a 'connected' cell) to relays of any version. (Relays
19622 without support for optimistic data are no longer supported on the
19623 Tor network.) Resolves ticket 13153.
19625 o Minor features (directory authorities):
19626 - Don't list relays with a bandwidth estimate of 0 in the consensus.
19627 Implements a feature proposed during discussion of bug 13000.
19628 - In tor-gencert, report an error if the user provides the same
19629 argument more than once.
19630 - If a directory authority can't find a best consensus method in the
19631 votes that it holds, it now falls back to its favorite consensus
19632 method. Previously, it fell back to method 1. Neither of these is
19633 likely to get enough signatures, but "fall back to favorite"
19634 doesn't require us to maintain support an obsolete consensus
19635 method. Implements part of proposal 215.
19637 o Minor features (logging):
19638 - On Unix-like systems, you can now use named pipes as the target of
19639 the Log option, and other options that try to append to files.
19640 Closes ticket 12061. Patch from "carlo von lynX".
19641 - When opening a log file at startup, send it every log message that
19642 we generated between startup and opening it. Previously, log
19643 messages that were generated before opening the log file were only
19644 logged to stdout. Closes ticket 6938.
19645 - Add a TruncateLogFile option to overwrite logs instead of
19646 appending to them. Closes ticket 5583.
19648 o Minor features (portability, Solaris):
19649 - Threads are no longer disabled by default on Solaris; we believe
19650 that the versions of Solaris with broken threading support are all
19651 obsolete by now. Resolves ticket 9495.
19653 o Minor features (relay):
19654 - Re-check our address after we detect a changed IP address from
19655 getsockname(). This ensures that the controller command "GETINFO
19656 address" will report the correct value. Resolves ticket 11582.
19658 - A new AccountingRule option lets Relays set whether they'd like
19659 AccountingMax to be applied separately to inbound and outbound
19660 traffic, or applied to the sum of inbound and outbound traffic.
19661 Resolves ticket 961. Patch by "chobe".
19663 o Minor features (testing networks):
19664 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
19665 the "Exit" flag regardless of their uptime, bandwidth, or exit
19666 policy. TestingTorNetwork must be set for this option to have any
19667 effect. Previously, authorities would take up to 35 minutes to
19668 give nodes the Exit flag in a test network. Partially implements
19671 o Minor features (validation):
19672 - Check all date/time values passed to tor_timegm and
19673 parse_rfc1123_time for validity, taking leap years into account.
19674 Improves HTTP header validation. Implemented with bug 13476.
19675 - In correct_tm(), limit the range of values returned by system
19676 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
19677 This means we don't have to deal with negative or too large dates,
19678 even if a clock is wrong. Otherwise we might fail to read a file
19679 written by us which includes such a date. Fixes bug 13476.
19681 o Minor bugfixes (bridge clients):
19682 - When configured to use a bridge without an identity digest (not
19683 recommended), avoid launching an extra channel to it when
19684 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
19686 o Minor bugfixes (bridges):
19687 - When DisableNetwork is set, do not launch pluggable transport
19688 plugins, and if any are running, terminate them. Fixes bug 13213;
19689 bugfix on 0.2.3.6-alpha.
19691 o Minor bugfixes (C correctness):
19692 - Fix several instances of possible integer overflow/underflow/NaN.
19693 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
19695 - In circuit_build_times_calculate_timeout() in circuitstats.c,
19696 avoid dividing by zero in the pareto calculations. This traps
19697 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
19699 - Fix an integer overflow in format_time_interval(). Fixes bug
19700 13393; bugfix on 0.2.0.10-alpha.
19701 - Set the correct day of year value when the system's localtime(_r)
19702 or gmtime(_r) functions fail to set struct tm. Not externally
19703 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
19704 - Avoid unlikely signed integer overflow in tor_timegm on systems
19705 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
19707 o Minor bugfixes (client):
19708 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
19709 BadExit flag are not considered worthy candidates. Fixes bug
19710 13066; bugfix on 0.1.2.3-alpha.
19711 - Use the consensus schedule for downloading consensuses, and not
19712 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
19713 - Handle unsupported or malformed SOCKS5 requests properly by
19714 responding with the appropriate error message before closing the
19715 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
19717 o Minor bugfixes (client, torrc):
19718 - Stop modifying the value of our DirReqStatistics torrc option just
19719 because we're not a bridge or relay. This bug was causing Tor
19720 Browser users to write "DirReqStatistics 0" in their torrc files
19721 as if they had chosen to change the config. Fixes bug 4244; bugfix
19723 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
19724 that our options have changed every time we SIGHUP. Fixes bug
19725 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
19727 o Minor bugfixes (controller):
19728 - Return an error when the second or later arguments of the
19729 "setevents" controller command are invalid events. Previously we
19730 would return success while silently skipping invalid events. Fixes
19731 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
19733 o Minor bugfixes (directory system):
19734 - Always believe that v3 directory authorities serve extra-info
19735 documents, whether they advertise "caches-extra-info" or not.
19736 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
19737 - When running as a v3 directory authority, advertise that you serve
19738 extra-info documents so that clients who want them can find them
19739 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
19740 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
19741 Previously, directories offering BRIDGE_DIRINFO and some other
19742 flag (i.e. microdescriptors or extrainfo) would be ignored when
19743 looking for bridges. Partially fixes bug 13163; bugfix
19746 o Minor bugfixes (networking):
19747 - Check for orconns and use connection_or_close_for_error() rather
19748 than connection_mark_for_close() directly in the getsockopt()
19749 failure case of connection_handle_write_impl(). Fixes bug 11302;
19750 bugfix on 0.2.4.4-alpha.
19752 o Minor bugfixes (relay):
19753 - When generating our family list, remove spaces from around the
19754 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
19755 - If our previous bandwidth estimate was 0 bytes, allow publishing a
19756 new relay descriptor immediately. Fixes bug 13000; bugfix
19759 o Minor bugfixes (testing networks):
19760 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
19761 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
19762 - Stop using the default authorities in networks which provide both
19763 AlternateDirAuthority and AlternateBridgeAuthority. Partially
19764 fixes bug 13163; bugfix on 0.2.0.13-alpha.
19766 o Minor bugfixes (testing):
19767 - Stop spawn test failures due to a race condition between the
19768 SIGCHLD handler updating the process status, and the test reading
19769 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
19771 o Minor bugfixes (testing, Windows):
19772 - Avoid passing an extra backslash when creating a temporary
19773 directory for running the unit tests on Windows. Fixes bug 12392;
19774 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
19776 o Minor bugfixes (windows):
19777 - Remove code to special-case handling of NTE_BAD_KEYSET when
19778 acquiring windows CryptoAPI context. This error can't actually
19779 occur for the parameters we're providing. Fixes bug 10816; bugfix
19782 o Minor bugfixes (zlib):
19783 - Avoid truncating a zlib stream when trying to finalize it with an
19784 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
19787 - Allow our configure script to build correctly with autoconf 2.62
19788 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
19789 - Improve the error message from ./configure to make it clear that
19790 when asciidoc has not been found, the user will have to either add
19791 --disable-asciidoc argument or install asciidoc. Resolves
19794 o Code simplification and refactoring:
19795 - Change the entry_is_live() function to take named bitfield
19796 elements instead of an unnamed list of booleans. Closes
19798 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
19799 Resolves ticket 12205.
19800 - Use calloc and reallocarray functions instead of multiply-
19801 then-malloc. This makes it less likely for us to fall victim to an
19802 integer overflow attack when allocating. Resolves ticket 12855.
19803 - Use the standard macro name SIZE_MAX, instead of our
19805 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
19806 functions which take them as arguments. Replace 0 with NO_DIRINFO
19807 in a function call for clarity. Seeks to prevent future issues
19809 - Avoid 4 null pointer errors under clang static analysis by using
19810 tor_assert() to prove that the pointers aren't null. Fixes
19812 - Rework the API of policies_parse_exit_policy() to use a bitmask to
19813 represent parsing options, instead of a confusing mess of
19814 booleans. Resolves ticket 8197.
19815 - Introduce a helper function to parse ExitPolicy in
19816 or_options_t structure.
19819 - Add a doc/TUNING document with tips for handling large numbers of
19820 TCP connections when running busy Tor relay. Update the warning
19821 message to point to this file when running out of sockets
19822 operating system is allowing to use simultaneously. Resolves
19825 o Removed features:
19826 - We no longer remind the user about configuration options that have
19827 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
19828 - Remove our old, non-weighted bandwidth-based node selection code.
19829 Previously, we used it as a fallback when we couldn't perform
19830 weighted bandwidth-based node selection. But that would only
19831 happen in the cases where we had no consensus, or when we had a
19832 consensus generated by buggy or ancient directory authorities. In
19833 either case, it's better to use the more modern, better maintained
19834 algorithm, with reasonable defaults for the weights. Closes
19836 - Remove the --disable-curve25519 configure option. Relays and
19837 clients now are required to support curve25519 and the
19839 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
19840 used to be deprecated synonyms for "StrictNodes", are now marked
19841 obsolete. Resolves ticket 12226.
19842 - Clients don't understand the BadDirectory flag in the consensus
19843 anymore, and ignore it.
19846 - Refactor the function that chooses guard nodes so that it can more
19847 easily be tested; write some tests for it.
19848 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
19849 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
19850 - Create unit tests for format_time_interval(). With bug 13393.
19851 - Add unit tests for tor_timegm signed overflow, tor_timegm and
19852 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
19853 tests (visible) fixes in bug 13476.
19854 - Add a "coverage-html" make target to generate HTML-visualized
19855 coverage results when building with --enable-coverage. (Requires
19856 lcov.) Patch from Kevin Murray.
19857 - Enable the backtrace handler (where supported) when running the
19859 - Revise all unit tests that used the legacy test_* macros to
19860 instead use the recommended tt_* macros. This patch was generated
19861 with coccinelle, to avoid manual errors. Closes ticket 13119.
19863 o Distribution (systemd):
19864 - systemd unit file: only allow tor to write to /var/lib/tor and
19865 /var/log/tor. The rest of the filesystem is accessible for reading
19866 only. Patch by intrigeri; resolves ticket 12751.
19867 - systemd unit file: ensure that the process and all its children
19868 can never gain new privileges. Patch by intrigeri; resolves
19870 - systemd unit file: set up /var/run/tor as writable for the Tor
19871 service. Patch by intrigeri; resolves ticket 13196.
19873 o Removed features (directory authorities):
19874 - Remove code that prevented authorities from listing Tor relays
19875 affected by CVE-2011-2769 as guards. These relays are already
19876 rejected altogether due to the minimum version requirement of
19877 0.2.3.16-alpha. Closes ticket 13152.
19878 - The "AuthDirRejectUnlisted" option no longer has any effect, as
19879 the fingerprints file (approved-routers) has been deprecated.
19880 - Directory authorities do not support being Naming dirauths anymore.
19881 The "NamingAuthoritativeDir" config option is now obsolete.
19882 - Directory authorities do not support giving out the BadDirectory
19884 - Directory authorities no longer advertise or support consensus
19885 methods 1 through 12 inclusive. These consensus methods were
19886 obsolete and/or insecure: maintaining the ability to support them
19887 served no good purpose. Implements part of proposal 215; closes
19890 o Testing (test-network.sh):
19891 - Stop using "echo -n", as some shells' built-in echo doesn't
19892 support "-n". Instead, use "/bin/echo -n". Partially fixes
19894 - Stop an apparent test-network hang when used with make -j2. Fixes
19896 - Add a --delay option to test-network.sh, which configures the
19897 delay before the chutney network tests for data transmission.
19898 Partially implements ticket 13161.
19901 Changes in version 0.2.5.10 - 2014-10-24
19902 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
19904 It adds several new security features, including improved
19905 denial-of-service resistance for relays, new compiler hardening
19906 options, and a system-call sandbox for hardened installations on Linux
19907 (requires seccomp2). The controller protocol has several new features,
19908 resolving IPv6 addresses should work better than before, and relays
19909 should be a little more CPU-efficient. We've added support for more
19910 OpenBSD and FreeBSD transparent proxy types. We've improved the build
19911 system and testing infrastructure to allow unit testing of more parts
19912 of the Tor codebase. Finally, we've addressed several nagging pluggable
19913 transport usability issues, and included numerous other small bugfixes
19914 and features mentioned below.
19916 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
19917 have accumulated many known flaws; everyone should upgrade.
19919 o Deprecated versions:
19920 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
19921 attention for some while.
19924 Changes in version 0.2.5.9-rc - 2014-10-20
19925 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
19926 series. It disables SSL3 in response to the recent "POODLE" attack
19927 (even though POODLE does not affect Tor). It also works around a crash
19928 bug caused by some operating systems' response to the "POODLE" attack
19929 (which does affect Tor). It also contains a few miscellaneous fixes.
19931 o Major security fixes:
19932 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
19933 today support TLS 1.0 or later, so we can safely turn off support
19934 for this old (and insecure) protocol. Fixes bug 13426.
19936 o Major bugfixes (openssl bug workaround):
19937 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
19938 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
19939 13471. This is a workaround for an OpenSSL bug.
19942 - Disable the sandbox name resolver cache when running tor-resolve:
19943 tor-resolve doesn't use the sandbox code, and turning it on was
19944 breaking attempts to do tor-resolve on a non-default server on
19945 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
19947 o Compilation fixes:
19948 - Build and run correctly on systems like OpenBSD-current that have
19949 patched OpenSSL to remove get_cipher_by_char and/or its
19950 implementations. Fixes issue 13325.
19952 o Downgraded warnings:
19953 - Downgrade the severity of the 'unexpected sendme cell from client'
19954 from 'warn' to 'protocol warning'. Closes ticket 8093.
19957 Changes in version 0.2.4.25 - 2014-10-20
19958 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
19959 (even though POODLE does not affect Tor). It also works around a crash
19960 bug caused by some operating systems' response to the "POODLE" attack
19961 (which does affect Tor).
19963 o Major security fixes (also in 0.2.5.9-rc):
19964 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
19965 today support TLS 1.0 or later, so we can safely turn off support
19966 for this old (and insecure) protocol. Fixes bug 13426.
19968 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
19969 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
19970 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
19971 13471. This is a workaround for an OpenSSL bug.
19974 Changes in version 0.2.5.8-rc - 2014-09-22
19975 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
19976 series. It fixes a bug that affects consistency and speed when
19977 connecting to hidden services, and it updates the location of one of
19978 the directory authorities.
19981 - Clients now send the correct address for their chosen rendezvous
19982 point when trying to access a hidden service. They used to send
19983 the wrong address, which would still work some of the time because
19984 they also sent the identity digest of the rendezvous point, and if
19985 the hidden service happened to try connecting to the rendezvous
19986 point from a relay that already had a connection open to it,
19987 the relay would reuse that connection. Now connections to hidden
19988 services should be more robust and faster. Also, this bug meant
19989 that clients were leaking to the hidden service whether they were
19990 on a little-endian (common) or big-endian (rare) system, which for
19991 some users might have reduced their anonymity. Fixes bug 13151;
19992 bugfix on 0.2.1.5-alpha.
19994 o Directory authority changes:
19995 - Change IP address for gabelmoo (v3 directory authority).
19998 Changes in version 0.2.4.24 - 2014-09-22
19999 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
20000 connecting to hidden services, and it updates the location of one of
20001 the directory authorities.
20004 - Clients now send the correct address for their chosen rendezvous
20005 point when trying to access a hidden service. They used to send
20006 the wrong address, which would still work some of the time because
20007 they also sent the identity digest of the rendezvous point, and if
20008 the hidden service happened to try connecting to the rendezvous
20009 point from a relay that already had a connection open to it,
20010 the relay would reuse that connection. Now connections to hidden
20011 services should be more robust and faster. Also, this bug meant
20012 that clients were leaking to the hidden service whether they were
20013 on a little-endian (common) or big-endian (rare) system, which for
20014 some users might have reduced their anonymity. Fixes bug 13151;
20015 bugfix on 0.2.1.5-alpha.
20017 o Directory authority changes:
20018 - Change IP address for gabelmoo (v3 directory authority).
20020 o Minor features (geoip):
20021 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
20025 Changes in version 0.2.5.7-rc - 2014-09-11
20026 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
20027 release series, and some long-standing bugs related to ORPort reachability
20028 testing and failure to send CREATE cells. It is the first release
20029 candidate for the Tor 0.2.5.x series.
20031 o Major bugfixes (client, startup):
20032 - Start making circuits as soon as DisabledNetwork is turned off.
20033 When Tor started with DisabledNetwork set, it would correctly
20034 conclude that it shouldn't build circuits, but it would mistakenly
20035 cache this conclusion, and continue believing it even when
20036 DisableNetwork is set to 0. Fixes the bug introduced by the fix
20037 for bug 11200; bugfix on 0.2.5.4-alpha.
20038 - Resume expanding abbreviations for command-line options. The fix
20039 for bug 4647 accidentally removed our hack from bug 586 that
20040 rewrote HashedControlPassword to __HashedControlSessionPassword
20041 when it appears on the commandline (which allowed the user to set
20042 her own HashedControlPassword in the torrc file while the
20043 controller generates a fresh session password for each run). Fixes
20044 bug 12948; bugfix on 0.2.5.1-alpha.
20045 - Warn about attempts to run hidden services and relays in the same
20046 process: that's probably not a good idea. Closes ticket 12908.
20048 o Major bugfixes (relay):
20049 - Avoid queuing or sending destroy cells for circuit ID zero when we
20050 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
20051 Found and fixed by "cypherpunks".
20052 - Fix ORPort reachability detection on relays running behind a
20053 proxy, by correctly updating the "local" mark on the controlling
20054 channel when changing the address of an or_connection_t after the
20055 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
20057 o Minor features (bridge):
20058 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
20059 cookie file for the ExtORPort g+r by default.
20061 o Minor features (geoip):
20062 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
20065 o Minor bugfixes (logging):
20066 - Reduce the log severity of the "Pluggable transport proxy does not
20067 provide any needed transports and will not be launched." message,
20068 since Tor Browser includes several ClientTransportPlugin lines in
20069 its torrc-defaults file, leading every Tor Browser user who looks
20070 at her logs to see these notices and wonder if they're dangerous.
20071 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
20072 - Downgrade "Unexpected onionskin length after decryption" warning
20073 to a protocol-warn, since there's nothing relay operators can do
20074 about a client that sends them a malformed create cell. Resolves
20075 bug 12996; bugfix on 0.0.6rc1.
20076 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
20077 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
20078 - When logging information about an EXTEND2 or EXTENDED2 cell, log
20079 their names correctly. Fixes part of bug 12700; bugfix
20081 - When logging information about a relay cell whose command we don't
20082 recognize, log its command as an integer. Fixes part of bug 12700;
20083 bugfix on 0.2.1.10-alpha.
20084 - Escape all strings from the directory connection before logging
20085 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
20087 o Minor bugfixes (controller):
20088 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
20089 bug 12864; bugfix on 0.2.5.1-alpha.
20090 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
20091 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
20094 o Minor bugfixes (compilation):
20095 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
20096 bugfix on 0.2.5.5-alpha.
20097 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
20098 0.2.5.1-alpha. Patch from "NewEraCracker".
20099 - In routerlist_assert_ok(), don't take the address of a
20100 routerinfo's cache_info member unless that routerinfo is non-NULL.
20101 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
20102 - Fix a large number of false positive warnings from the clang
20103 analyzer static analysis tool. This should make real warnings
20104 easier for clang analyzer to find. Patch from "teor". Closes
20107 o Distribution (systemd):
20108 - Verify configuration file via ExecStartPre in the systemd unit
20109 file. Patch from intrigeri; resolves ticket 12730.
20110 - Explicitly disable RunAsDaemon in the systemd unit file. Our
20111 current systemd unit uses "Type = simple", so systemd does not
20112 expect tor to fork. If the user has "RunAsDaemon 1" in their
20113 torrc, then things won't work as expected. This is e.g. the case
20114 on Debian (and derivatives), since there we pass "--defaults-torrc
20115 /usr/share/tor/tor-service-defaults-torrc" (that contains
20116 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
20120 - Adjust the URLs in the README to refer to the new locations of
20121 several documents on the website. Fixes bug 12830. Patch from
20123 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
20127 Changes in version 0.2.5.6-alpha - 2014-07-28
20128 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
20129 risk from guard rotation, and fixes a variety of other issues to get
20130 us closer to a release candidate.
20132 o Major features (also in 0.2.4.23):
20133 - Make the number of entry guards configurable via a new
20134 NumEntryGuards consensus parameter, and the number of directory
20135 guards configurable via a new NumDirectoryGuards consensus
20136 parameter. Implements ticket 12688.
20138 o Major bugfixes (also in 0.2.4.23):
20139 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
20140 implementation that caused incorrect results on 32-bit
20141 implementations when certain malformed inputs were used along with
20142 a small class of private ntor keys. This bug does not currently
20143 appear to allow an attacker to learn private keys or impersonate a
20144 Tor server, but it could provide a means to distinguish 32-bit Tor
20145 implementations from 64-bit Tor implementations. Fixes bug 12694;
20146 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
20150 - Perform circuit cleanup operations even when circuit
20151 construction operations are disabled (because the network is
20152 disabled, or because there isn't enough directory information).
20153 Previously, when we were not building predictive circuits, we
20154 were not closing expired circuits either. Fixes bug 8387; bugfix on
20155 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
20156 became more strict about when we have "enough directory information
20157 to build circuits".
20160 - Authorities now assign the Guard flag to the fastest 25% of the
20161 network (it used to be the fastest 50%). Also raise the consensus
20162 weight that guarantees the Guard flag from 250 to 2000. For the
20163 current network, this results in about 1100 guards, down from 2500.
20164 This step paves the way for moving the number of entry guards
20165 down to 1 (proposal 236) while still providing reasonable expected
20166 performance for most users. Implements ticket 12690.
20167 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
20169 - Slightly enhance the diagnostic message for bug 12184.
20171 o Minor bugfixes (also in 0.2.4.23):
20172 - Warn and drop the circuit if we receive an inbound 'relay early'
20173 cell. Those used to be normal to receive on hidden service circuits
20174 due to bug 1038, but the buggy Tor versions are long gone from
20175 the network so we can afford to resume watching for them. Resolves
20176 the rest of bug 1038; bugfix on 0.2.1.19.
20177 - Correct a confusing error message when trying to extend a circuit
20178 via the control protocol but we don't know a descriptor or
20179 microdescriptor for one of the specified relays. Fixes bug 12718;
20180 bugfix on 0.2.3.1-alpha.
20183 - Fix compilation when building with bufferevents enabled. (This
20184 configuration is still not expected to work, however.)
20185 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
20186 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
20188 - Compile correctly with builds and forks of OpenSSL (such as
20189 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
20190 0.2.1.1-alpha. Patch from "dhill".
20193 Changes in version 0.2.4.23 - 2014-07-28
20194 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
20195 guard rotation, and also backports several important fixes from the
20196 Tor 0.2.5 alpha release series.
20199 - Clients now look at the "usecreatefast" consensus parameter to
20200 decide whether to use CREATE_FAST or CREATE cells for the first hop
20201 of their circuit. This approach can improve security on connections
20202 where Tor's circuit handshake is stronger than the available TLS
20203 connection security levels, but the tradeoff is more computational
20204 load on guard relays. Implements proposal 221. Resolves ticket 9386.
20205 - Make the number of entry guards configurable via a new
20206 NumEntryGuards consensus parameter, and the number of directory
20207 guards configurable via a new NumDirectoryGuards consensus
20208 parameter. Implements ticket 12688.
20211 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
20212 implementation that caused incorrect results on 32-bit
20213 implementations when certain malformed inputs were used along with
20214 a small class of private ntor keys. This bug does not currently
20215 appear to allow an attacker to learn private keys or impersonate a
20216 Tor server, but it could provide a means to distinguish 32-bit Tor
20217 implementations from 64-bit Tor implementations. Fixes bug 12694;
20218 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
20222 - Warn and drop the circuit if we receive an inbound 'relay early'
20223 cell. Those used to be normal to receive on hidden service circuits
20224 due to bug 1038, but the buggy Tor versions are long gone from
20225 the network so we can afford to resume watching for them. Resolves
20226 the rest of bug 1038; bugfix on 0.2.1.19.
20227 - Correct a confusing error message when trying to extend a circuit
20228 via the control protocol but we don't know a descriptor or
20229 microdescriptor for one of the specified relays. Fixes bug 12718;
20230 bugfix on 0.2.3.1-alpha.
20231 - Avoid an illegal read from stack when initializing the TLS
20232 module using a version of OpenSSL without all of the ciphers
20233 used by the v2 link handshake. Fixes bug 12227; bugfix on
20234 0.2.4.8-alpha. Found by "starlight".
20237 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
20241 Changes in version 0.2.5.5-alpha - 2014-06-18
20242 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
20243 0.2.5.x release series, including a couple of DoS issues, some
20244 performance regressions, a large number of bugs affecting the Linux
20245 seccomp2 sandbox code, and various other bugfixes. It also adds
20246 diagnostic bugfixes for a few tricky issues that we're trying to
20249 o Major features (security, traffic analysis resistance):
20250 - Several major improvements to the algorithm used to decide when to
20251 close TLS connections. Previous versions of Tor closed connections
20252 at a fixed interval after the last time a non-padding cell was
20253 sent over the connection, regardless of the target of the
20254 connection. Now, we randomize the intervals by adding up to 50% of
20255 their base value, we measure the length of time since connection
20256 last had at least one circuit, and we allow connections to known
20257 ORs to remain open a little longer (15 minutes instead of 3
20258 minutes minimum). These changes should improve Tor's resistance
20259 against some kinds of traffic analysis, and lower some overhead
20260 from needlessly closed connections. Fixes ticket 6799.
20261 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
20263 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
20264 - Fix a memory leak that could occur if a microdescriptor parse
20265 fails during the tokenizing step. This bug could enable a memory
20266 exhaustion attack by directory servers. Fixes bug 11649; bugfix
20269 o Major bugfixes (security, directory authorities):
20270 - Directory authorities now include a digest of each relay's
20271 identity key as a part of its microdescriptor.
20273 This is a workaround for bug 11743 (reported by "cypherpunks"),
20274 where Tor clients do not support receiving multiple
20275 microdescriptors with the same SHA256 digest in the same
20276 consensus. When clients receive a consensus like this, they only
20277 use one of the relays. Without this fix, a hostile relay could
20278 selectively disable some client use of target relays by
20279 constructing a router descriptor with a different identity and the
20280 same microdescriptor parameters and getting the authorities to
20281 list it in a microdescriptor consensus. This fix prevents an
20282 attacker from causing a microdescriptor collision, because the
20283 router's identity is not forgeable.
20285 o Major bugfixes (relay):
20286 - Use a direct dirport connection when uploading non-anonymous
20287 descriptors to the directory authorities. Previously, relays would
20288 incorrectly use tunnel connections under a fairly wide variety of
20289 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
20290 - When a circuit accidentally has the same circuit ID for its
20291 forward and reverse direction, correctly detect the direction of
20292 cells using that circuit. Previously, this bug made roughly one
20293 circuit in a million non-functional. Fixes bug 12195; this is a
20294 bugfix on every version of Tor.
20296 o Major bugfixes (client, pluggable transports):
20297 - When managing pluggable transports, use OS notification facilities
20298 to learn if they have crashed, and don't attempt to kill any
20299 process that has already exited. Fixes bug 8746; bugfix
20302 o Minor features (diagnostic):
20303 - When logging a warning because of bug 7164, additionally check the
20304 hash table for consistency (as proposed on ticket 11737). This may
20305 help diagnose bug 7164.
20306 - When we log a heartbeat, log how many one-hop circuits we have
20307 that are at least 30 minutes old, and log status information about
20308 a few of them. This is an attempt to track down bug 8387.
20309 - When encountering an unexpected CR while writing text to a file on
20310 Windows, log the name of the file. Should help diagnosing
20312 - Give more specific warnings when a client notices that an onion
20313 handshake has failed. Fixes ticket 9635.
20314 - Add significant new logging code to attempt to diagnose bug 12184,
20315 where relays seem to run out of available circuit IDs.
20316 - Improve the diagnostic log message for bug 8387 even further to
20317 try to improve our odds of figuring out why one-hop directory
20318 circuits sometimes do not get closed.
20320 o Minor features (security, memory management):
20321 - Memory allocation tricks (mempools and buffer freelists) are now
20322 disabled by default. You can turn them back on with
20323 --enable-mempools and --enable-buf-freelists respectively. We're
20324 disabling these features because malloc performance is good enough
20325 on most platforms, and a similar feature in OpenSSL exacerbated
20326 exploitation of the Heartbleed attack. Resolves ticket 11476.
20328 o Minor features (security):
20329 - Apply the secure SipHash-2-4 function to the hash table mapping
20330 circuit IDs and channels to circuits. We missed this one when we
20331 were converting all the other hash functions to use SipHash back
20332 in 0.2.5.3-alpha. Resolves ticket 11750.
20334 o Minor features (build):
20335 - The configure script has a --disable-seccomp option to turn off
20336 support for libseccomp on systems that have it, in case it (or
20337 Tor's use of it) is broken. Resolves ticket 11628.
20339 o Minor features (other):
20340 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
20343 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
20344 - When running a hidden service, do not allow TunneledDirConns 0;
20345 this will keep the hidden service from running, and also
20346 make it publish its descriptors directly over HTTP. Fixes bug 10849;
20347 bugfix on 0.2.1.1-alpha.
20349 o Minor bugfixes (performance):
20350 - Avoid a bug where every successful connection made us recompute
20351 the flag telling us whether we have sufficient information to
20352 build circuits. Previously, we would forget our cached value
20353 whenever we successfully opened a channel (or marked a router as
20354 running or not running for any other reason), regardless of
20355 whether we had previously believed the router to be running. This
20356 forced us to run an expensive update operation far too often.
20357 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
20358 - Avoid using tor_memeq() for checking relay cell integrity. This
20359 removes a possible performance bottleneck. Fixes part of bug
20360 12169; bugfix on 0.2.1.31.
20362 o Minor bugfixes (compilation):
20363 - Fix compilation of test_status.c when building with MVSC. Bugfix
20364 on 0.2.5.4-alpha. Patch from Gisle Vanem.
20365 - Resolve GCC complaints on OpenBSD about discarding constness in
20366 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
20367 on 0.1.1.23. Patch from Dana Koch.
20368 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
20369 treatment of long and time_t as comparable types. Fixes part of
20370 bug 11633. Patch from Dana Koch.
20371 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
20372 11623; bugfix on 0.2.5.3-alpha.
20373 - When deciding whether to build the 64-bit curve25519
20374 implementation, detect platforms where we can compile 128-bit
20375 arithmetic but cannot link it. Fixes bug 11729; bugfix on
20376 0.2.4.8-alpha. Patch from "conradev".
20377 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
20378 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
20379 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
20382 o Minor bugfixes (Directory server):
20383 - When sending a compressed set of descriptors or microdescriptors,
20384 make sure to finalize the zlib stream. Previously, we would write
20385 all the compressed data, but if the last descriptor we wanted to
20386 send was missing or too old, we would not mark the stream as
20387 finished. This caused problems for decompression tools. Fixes bug
20388 11648; bugfix on 0.1.1.23.
20390 o Minor bugfixes (Linux seccomp sandbox):
20391 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
20392 11622; bugfix on 0.2.5.1-alpha.
20393 - Avoid crashing when re-opening listener ports with the seccomp
20394 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
20395 - Avoid crashing with the seccomp sandbox enabled along with
20396 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
20397 - When we receive a SIGHUP with the sandbox enabled, correctly
20398 support rotating our log files. Fixes bug 12032; bugfix
20400 - Avoid crash when running with sandboxing enabled and
20401 DirReqStatistics not disabled. Fixes bug 12035; bugfix
20403 - Fix a "BUG" warning when trying to write bridge-stats files with
20404 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
20406 - Prevent the sandbox from crashing on startup when run with the
20407 --enable-expensive-hardening configuration option. Fixes bug
20408 11477; bugfix on 0.2.5.4-alpha.
20409 - When running with DirPortFrontPage and sandboxing both enabled,
20410 reload the DirPortFrontPage correctly when restarting. Fixes bug
20411 12028; bugfix on 0.2.5.1-alpha.
20412 - Don't try to enable the sandbox when using the Tor binary to check
20413 its configuration, hash a passphrase, or so on. Doing so was
20414 crashing on startup for some users. Fixes bug 11609; bugfix
20416 - Avoid warnings when running with sandboxing and node statistics
20417 enabled at the same time. Fixes part of 12064; bugfix on
20418 0.2.5.1-alpha. Patch from Michael Wolf.
20419 - Avoid warnings when running with sandboxing enabled at the same
20420 time as cookie authentication, hidden services, or directory
20421 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
20422 - Do not allow options that require calls to exec to be enabled
20423 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
20424 bug 12043; bugfix on 0.2.5.1-alpha.
20425 - Handle failures in getpwnam()/getpwuid() when running with the
20426 User option set and the Linux syscall sandbox enabled. Fixes bug
20427 11946; bugfix on 0.2.5.1-alpha.
20428 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
20429 to avoid calling getaddrinfo() after installing the sandbox
20430 filters. Previously, it preloaded a cache with the IPv4 address
20431 for our hostname, and nothing else. Now, it loads the cache with
20432 every address that it used to initialize the Tor process. Fixes
20433 bug 11970; bugfix on 0.2.5.1-alpha.
20435 o Minor bugfixes (pluggable transports):
20436 - Enable the ExtORPortCookieAuthFile option, to allow changing the
20437 default location of the authentication token for the extended OR
20438 Port as used by sever-side pluggable transports. We had
20439 implemented this option before, but the code to make it settable
20440 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
20441 - Avoid another 60-second delay when starting Tor in a pluggable-
20442 transport-using configuration when we already have cached
20443 descriptors for our bridges. Fixes bug 11965; bugfix
20446 o Minor bugfixes (client):
20447 - Avoid "Tried to open a socket with DisableNetwork set" warnings
20448 when starting a client with bridges configured and DisableNetwork
20449 set. (Tor launcher starts Tor with DisableNetwork set the first
20450 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
20452 o Minor bugfixes (testing):
20453 - The Python parts of the test scripts now work on Python 3 as well
20454 as Python 2, so systems where '/usr/bin/python' is Python 3 will
20455 no longer have the tests break. Fixes bug 11608; bugfix
20457 - When looking for versions of python that we could run the tests
20458 with, check for "python2.7" and "python3.3"; previously we were
20459 only looking for "python", "python2", and "python3". Patch from
20460 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
20461 - Fix all valgrind warnings produced by the unit tests. There were
20462 over a thousand memory leak warnings previously, mostly produced
20463 by forgetting to free things in the unit test code. Fixes bug
20464 11618, bugfixes on many versions of Tor.
20466 o Minor bugfixes (tor-fw-helper):
20467 - Give a correct log message when tor-fw-helper fails to launch.
20468 (Previously, we would say something like "tor-fw-helper sent us a
20469 string we could not parse".) Fixes bug 9781; bugfix
20472 o Minor bugfixes (relay, threading):
20473 - Check return code on spawn_func() in cpuworker code, so that we
20474 don't think we've spawned a nonworking cpuworker and write junk to
20475 it forever. Fix related to bug 4345; bugfix on all released Tor
20476 versions. Found by "skruffy".
20477 - Use a pthread_attr to make sure that spawn_func() cannot return an
20478 error while at the same time launching a thread. Fix related to
20479 bug 4345; bugfix on all released Tor versions. Reported
20482 o Minor bugfixes (relay, oom prevention):
20483 - Correctly detect the total available system memory. We tried to do
20484 this in 0.2.5.4-alpha, but the code was set up to always return an
20485 error value, even on success. Fixes bug 11805; bugfix
20488 o Minor bugfixes (relay, other):
20489 - We now drop CREATE cells for already-existent circuit IDs and for
20490 zero-valued circuit IDs, regardless of other factors that might
20491 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
20493 - Avoid an illegal read from stack when initializing the TLS module
20494 using a version of OpenSSL without all of the ciphers used by the
20495 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
20497 - When rejecting DATA cells for stream_id zero, still count them
20498 against the circuit's deliver window so that we don't fail to send
20499 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
20501 o Minor bugfixes (logging):
20502 - Fix a misformatted log message about delayed directory fetches.
20503 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
20504 - Squelch a spurious LD_BUG message "No origin circuit for
20505 successful SOCKS stream" in certain hidden service failure cases;
20509 - Include a tor.service file in contrib/dist for use with systemd.
20510 Some distributions will be able to use this file unmodified;
20511 others will need to tweak it, or write their own. Patch from Jamie
20512 Nguyen; resolves ticket 8368.
20515 - Clean up several option names in the manpage to match their real
20516 names, add the missing documentation for a couple of testing and
20517 directory authority options, remove the documentation for a
20518 V2-directory fetching option that no longer exists. Resolves
20520 - Correct the documentation so that it lists the correct directory
20521 for the stats files. (They are in a subdirectory called "stats",
20523 - In the manpage, move more authority-only options into the
20524 directory authority section so that operators of regular directory
20525 caches don't get confused.
20528 - The contrib directory has been sorted and tidied. Before, it was
20529 an unsorted dumping ground for useful and not-so-useful things.
20530 Now, it is divided based on functionality, and the items which
20531 seemed to be nonfunctional or useless have been removed. Resolves
20532 ticket 8966; based on patches from "rl1987".
20535 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
20536 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
20537 - The TunnelDirConns and PreferTunnelledDirConns options no longer
20538 exist; tunneled directory connections have been available since
20539 0.1.2.5-alpha, and turning them off is not a good idea. This is a
20540 brute-force fix for 10849, where "TunnelDirConns 0" would break
20544 Changes in version 0.2.4.22 - 2014-05-16
20545 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
20546 alpha release series. These include blocking all authority signing
20547 keys that may have been affected by the OpenSSL "heartbleed" bug,
20548 choosing a far more secure set of TLS ciphersuites by default, closing
20549 a couple of memory leaks that could be used to run a target relay out
20550 of RAM, and several others.
20552 o Major features (security, backport from 0.2.5.4-alpha):
20553 - Block authority signing keys that were used on authorities
20554 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
20555 don't have any evidence that these keys _were_ compromised; we're
20556 doing this to be prudent.) Resolves ticket 11464.
20558 o Major bugfixes (security, OOM):
20559 - Fix a memory leak that could occur if a microdescriptor parse
20560 fails during the tokenizing step. This bug could enable a memory
20561 exhaustion attack by directory servers. Fixes bug 11649; bugfix
20564 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
20565 - The relay ciphersuite list is now generated automatically based on
20566 uniform criteria, and includes all OpenSSL ciphersuites with
20567 acceptable strength and forward secrecy. Previously, we had left
20568 some perfectly fine ciphersuites unsupported due to omission or
20569 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
20570 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
20571 - Relays now trust themselves to have a better view than clients of
20572 which TLS ciphersuites are better than others. (Thanks to bug
20573 11513, the relay list is now well-considered, whereas the client
20574 list has been chosen mainly for anti-fingerprinting purposes.)
20575 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
20576 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
20577 AES128. Resolves ticket 11528.
20578 - Clients now try to advertise the same list of ciphersuites as
20579 Firefox 28. This change enables selection of (fast) GCM
20580 ciphersuites, disables some strange old ciphers, and stops
20581 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
20582 Resolves ticket 11438.
20584 o Minor bugfixes (configuration, security):
20585 - When running a hidden service, do not allow TunneledDirConns 0:
20586 trying to set that option together with a hidden service would
20587 otherwise prevent the hidden service from running, and also make
20588 it publish its descriptors directly over HTTP. Fixes bug 10849;
20589 bugfix on 0.2.1.1-alpha.
20591 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
20592 - Avoid sending a garbage value to the controller when a circuit is
20593 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
20595 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
20596 - Stop leaking memory when we successfully resolve a PTR record.
20597 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
20599 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
20600 - Avoid 60-second delays in the bootstrapping process when Tor is
20601 launching for a second time while using bridges. Fixes bug 9229;
20602 bugfix on 0.2.0.3-alpha.
20604 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
20605 - Give the correct URL in the warning message when trying to run a
20606 relay on an ancient version of Windows. Fixes bug 9393.
20608 o Minor bugfixes (compilation):
20609 - Fix a compilation error when compiling with --disable-curve25519.
20610 Fixes bug 9700; bugfix on 0.2.4.17-rc.
20613 - Downgrade the warning severity for the the "md was still
20614 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
20615 for trying to diagnose this bug, and the current warning in
20616 earlier versions of tor achieves nothing useful. Addresses warning
20619 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
20620 - When we run out of usable circuit IDs on a channel, log only one
20621 warning for the whole channel, and describe how many circuits
20622 there were on the channel. Fixes part of ticket 11553.
20624 o Minor features (security, backport from 0.2.5.4-alpha):
20625 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
20626 leave the default at 8GBytes), to better support Raspberry Pi
20627 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
20629 o Documentation (backport from 0.2.5.4-alpha):
20630 - Correctly document that we search for a system torrc file before
20631 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
20635 Changes in version 0.2.5.4-alpha - 2014-04-25
20636 Tor 0.2.5.4-alpha includes several security and performance
20637 improvements for clients and relays, including blacklisting authority
20638 signing keys that were used while susceptible to the OpenSSL
20639 "heartbleed" bug, fixing two expensive functions on busy relays,
20640 improved TLS ciphersuite preference lists, support for run-time
20641 hardening on compilers that support AddressSanitizer, and more work on
20642 the Linux sandbox code.
20644 There are also several usability fixes for clients (especially clients
20645 that use bridges), two new TransPort protocols supported (one on
20646 OpenBSD, one on FreeBSD), and various other bugfixes.
20648 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
20649 have accumulated many known flaws; everyone should upgrade.
20651 o Major features (security):
20652 - If you don't specify MaxMemInQueues yourself, Tor now tries to
20653 pick a good value based on your total system memory. Previously,
20654 the default was always 8 GB. You can still override the default by
20655 setting MaxMemInQueues yourself. Resolves ticket 11396.
20656 - Block authority signing keys that were used on authorities
20657 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
20658 don't have any evidence that these keys _were_ compromised; we're
20659 doing this to be prudent.) Resolves ticket 11464.
20661 o Major features (relay performance):
20662 - Speed up server-side lookups of rendezvous and introduction point
20663 circuits by using hashtables instead of linear searches. These
20664 functions previously accounted between 3 and 7% of CPU usage on
20665 some busy relays. Resolves ticket 9841.
20666 - Avoid wasting CPU when extending a circuit over a channel that is
20667 nearly out of circuit IDs. Previously, we would do a linear scan
20668 over possible circuit IDs before finding one or deciding that we
20669 had exhausted our possibilities. Now, we try at most 64 random
20670 circuit IDs before deciding that we probably won't succeed. Fixes
20671 a possible root cause of ticket 11553.
20673 o Major features (seccomp2 sandbox, Linux only):
20674 - The seccomp2 sandbox can now run a test network for multiple hours
20675 without crashing. The sandbox is still experimental, and more bugs
20676 will probably turn up. To try it, enable "Sandbox 1" on a Linux
20677 host. Resolves ticket 11351.
20678 - Strengthen sandbox code: the sandbox can now test the arguments
20679 for rename(), and blocks _sysctl() entirely. Resolves another part
20681 - When the sandbox blocks a system call, it now tries to log a stack
20682 trace before exiting. Resolves ticket 11465.
20684 o Major bugfixes (TLS cipher selection):
20685 - The relay ciphersuite list is now generated automatically based on
20686 uniform criteria, and includes all OpenSSL ciphersuites with
20687 acceptable strength and forward secrecy. Previously, we had left
20688 some perfectly fine ciphersuites unsupported due to omission or
20689 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
20690 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
20691 - Relays now trust themselves to have a better view than clients of
20692 which TLS ciphersuites are better than others. (Thanks to bug
20693 11513, the relay list is now well-considered, whereas the client
20694 list has been chosen mainly for anti-fingerprinting purposes.)
20695 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
20696 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
20697 AES128. Resolves ticket 11528.
20698 - Clients now try to advertise the same list of ciphersuites as
20699 Firefox 28. This change enables selection of (fast) GCM
20700 ciphersuites, disables some strange old ciphers, and stops
20701 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
20702 Resolves ticket 11438.
20704 o Major bugfixes (bridge client):
20705 - Avoid 60-second delays in the bootstrapping process when Tor is
20706 launching for a second time while using bridges. Fixes bug 9229;
20707 bugfix on 0.2.0.3-alpha.
20709 o Minor features (transparent proxy, *BSD):
20710 - Support FreeBSD's ipfw firewall interface for TransPort ports on
20711 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
20712 10267; patch from "yurivict".
20713 - Support OpenBSD's divert-to rules with the pf firewall for
20714 transparent proxy ports. To enable it, set "TransProxyType
20715 pf-divert". This allows Tor to run a TransPort transparent proxy
20716 port on OpenBSD 4.4 or later without root privileges. See the
20717 pf.conf(5) manual page for information on configuring pf to use
20718 divert-to rules. Closes ticket 10896; patch from Dana Koch.
20720 o Minor features (security):
20721 - New --enable-expensive-hardening option to enable security
20722 hardening options that consume nontrivial amounts of CPU and
20723 memory. Right now, this includes AddressSanitizer and UbSan, which
20724 are supported in newer versions of GCC and Clang. Closes ticket
20727 o Minor features (log verbosity):
20728 - Demote the message that we give when a flushing connection times
20729 out for too long from NOTICE to INFO. It was usually meaningless.
20730 Resolves ticket 5286.
20731 - Don't log so many notice-level bootstrapping messages at startup
20732 about downloading descriptors. Previously, we'd log a notice
20733 whenever we learned about more routers. Now, we only log a notice
20734 at every 5% of progress. Fixes bug 9963.
20735 - Warn less verbosely when receiving a malformed
20736 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
20737 - When we run out of usable circuit IDs on a channel, log only one
20738 warning for the whole channel, and describe how many circuits
20739 there were on the channel. Fixes part of ticket 11553.
20741 o Minor features (relay):
20742 - If a circuit timed out for at least 3 minutes, check if we have a
20743 new external IP address, and publish a new descriptor with the new
20744 IP address if it changed. Resolves ticket 2454.
20746 o Minor features (controller):
20747 - Make the entire exit policy available from the control port via
20748 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
20750 - Because of the fix for ticket 11396, the real limit for memory
20751 usage may no longer match the configured MaxMemInQueues value. The
20752 real limit is now exposed via GETINFO limits/max-mem-in-queues.
20754 o Minor features (bridge client):
20755 - Report a more useful failure message when we can't connect to a
20756 bridge because we don't have the right pluggable transport
20757 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
20759 o Minor features (diagnostic):
20760 - Add more log messages to diagnose bug 7164, which causes
20761 intermittent "microdesc_free() called but md was still referenced"
20762 warnings. We now include more information, to figure out why we
20763 might be cleaning a microdescriptor for being too old if it's
20764 still referenced by a live node_t object.
20766 o Minor bugfixes (client, DNSPort):
20767 - When using DNSPort, try to respond to AAAA requests with AAAA
20768 answers. Previously, we hadn't looked at the request type when
20769 deciding which answer type to prefer. Fixes bug 10468; bugfix on
20771 - When receiving a DNS query for an unsupported record type, reply
20772 with no answer rather than with a NOTIMPL error. This behavior
20773 isn't correct either, but it will break fewer client programs, we
20774 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
20777 o Minor bugfixes (exit relay):
20778 - Stop leaking memory when we successfully resolve a PTR record.
20779 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
20781 o Minor bugfixes (bridge client):
20782 - Stop accepting bridge lines containing hostnames. Doing so would
20783 cause clients to perform DNS requests on the hostnames, which was
20784 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
20785 - Avoid a 60-second delay in the bootstrapping process when a Tor
20786 client with pluggable transports re-reads its configuration at
20787 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
20789 o Minor bugfixes (client, logging during bootstrap):
20790 - Warn only once if we start logging in an unsafe way. Previously,
20791 we complain as many times as we had problems. Fixes bug 9870;
20792 bugfix on 0.2.5.1-alpha.
20793 - Only report the first fatal bootstrap error on a given OR
20794 connection. This stops us from telling the controller bogus error
20795 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
20796 - Be more helpful when trying to run sandboxed on Linux without
20797 libseccomp. Instead of saying "Sandbox is not implemented on this
20798 platform", we now explain that we need to be built with
20799 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
20800 - Avoid generating spurious warnings when starting with
20801 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
20804 o Minor bugfixes (closing OR connections):
20805 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
20806 check if it's an or_connection_t and correctly call
20807 connection_or_close_for_error() rather than
20808 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
20810 - When closing all connections on setting DisableNetwork to 1, use
20811 connection_or_close_normally() rather than closing OR connections
20812 out from under the channel layer. Fixes bug 11306; bugfix on
20815 o Minor bugfixes (controller):
20816 - Avoid sending a garbage value to the controller when a circuit is
20817 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
20819 o Minor bugfixes (tor-fw-helper):
20820 - Allow tor-fw-helper to build again by adding src/ext to its
20821 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
20823 o Minor bugfixes (bridges):
20824 - Avoid potential crashes or bad behavior when launching a
20825 server-side managed proxy with ORPort or ExtORPort temporarily
20826 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
20828 o Minor bugfixes (platform-specific):
20829 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
20830 bug 11426; bugfix on 0.2.5.3-alpha.
20831 - When dumping a malformed directory object to disk, save it in
20832 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
20834 - Don't report failures from make_socket_reuseable() on incoming
20835 sockets on OSX: this can happen when incoming connections close
20836 early. Fixes bug 10081.
20838 o Minor bugfixes (trivial memory leaks):
20839 - Fix a small memory leak when signing a directory object. Fixes bug
20840 11275; bugfix on 0.2.4.13-alpha.
20841 - Free placeholder entries in our circuit table at exit; fixes a
20842 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
20843 - Don't re-initialize a second set of OpenSSL mutexes when starting
20844 up. Previously, we'd make one set of mutexes, and then immediately
20845 replace them with another. Fixes bug 11726; bugfix on
20847 - Resolve some memory leaks found by coverity in the unit tests, on
20848 exit in tor-gencert, and on a failure to compute digests for our
20849 own keys when generating a v3 networkstatus vote. These leaks
20850 should never have affected anyone in practice.
20852 o Minor bugfixes (hidden service):
20853 - Only retry attempts to connect to a chosen rendezvous point 8
20854 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
20856 o Minor bugfixes (misc code correctness):
20857 - Fix various instances of undefined behavior in channeltls.c,
20858 tor_memmem(), and eventdns.c that would cause us to construct
20859 pointers to memory outside an allocated object. (These invalid
20860 pointers were not accessed, but C does not even allow them to
20861 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
20862 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
20863 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
20864 fix some miscellaneous errors in our tests and codebase. Fixes bug
20865 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
20866 - Always check return values for unlink, munmap, UnmapViewOfFile;
20867 check strftime return values more often. In some cases all we can
20868 do is report a warning, but this may help prevent deeper bugs from
20869 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
20871 - Fix numerous warnings from the clang "scan-build" static analyzer.
20872 Some of these are programming style issues; some of them are false
20873 positives that indicated awkward code; some are undefined behavior
20874 cases related to constructing (but not using) invalid pointers;
20875 some are assumptions about API behavior; some are (harmlessly)
20876 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
20877 correct; and one or two are genuine bugs that weren't reachable
20878 from the rest of the program. Fixes bug 8793; bugfixes on many,
20882 - Build the torify.1 manpage again. Previously, we were only trying
20883 to build it when also building tor-fw-helper. That's why we didn't
20884 notice that we'd broken the ability to build it. Fixes bug 11321;
20885 bugfix on 0.2.5.1-alpha.
20886 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
20887 11061; bugfix on 0.2.4.7-alpha.
20888 - Correctly document that we search for a system torrc file before
20889 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
20891 - Resolve warnings from Doxygen.
20893 o Code simplifications and refactoring:
20894 - Remove is_internal_IP() function. Resolves ticket 4645.
20895 - Remove unused function circuit_dump_by_chan from circuitlist.c.
20896 Closes issue 9107; patch from "marek".
20897 - Change our use of the ENUM_BF macro to avoid declarations that
20900 o Deprecated versions:
20901 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
20902 attention for some while. Directory authorities no longer accept
20903 descriptors from relays running any version of Tor prior to Tor
20904 0.2.3.16-alpha. Resolves ticket 11149.
20907 - New macros in test.h to simplify writing mock-functions for unit
20908 tests. Part of ticket 11507. Patch from Dana Koch.
20909 - Complete tests for the status.c module. Resolves ticket 11507.
20910 Patch from Dana Koch.
20913 - Remove all code for the long unused v1 directory protocol.
20914 Resolves ticket 11070.
20917 Changes in version 0.2.5.3-alpha - 2014-03-22
20918 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
20919 two new anti-DoS features for Tor relays, resolves a bug that kept
20920 SOCKS5 support for IPv6 from working, fixes several annoying usability
20921 issues for bridge users, and removes more old code for unused
20924 The Tor 0.2.5.x release series is now in patch-freeze: no feature
20925 patches not already written will be considered for inclusion in 0.2.5.x.
20927 o Major features (relay security, DoS-resistance):
20928 - When deciding whether we have run out of memory and we need to
20929 close circuits, also consider memory allocated in buffers for
20930 streams attached to each circuit.
20932 This change, which extends an anti-DoS feature introduced in
20933 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
20934 better resist more memory-based DoS attacks than before. Since the
20935 MaxMemInCellQueues option now applies to all queues, it is renamed
20936 to MaxMemInQueues. This feature fixes bug 10169.
20937 - Avoid hash-flooding denial-of-service attacks by using the secure
20938 SipHash-2-4 hash function for our hashtables. Without this
20939 feature, an attacker could degrade performance of a targeted
20940 client or server by flooding their data structures with a large
20941 number of entries to be stored at the same hash table position,
20942 thereby slowing down the Tor instance. With this feature, hash
20943 table positions are derived from a randomized cryptographic key,
20944 and an attacker cannot predict which entries will collide. Closes
20946 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
20947 the default at 8GBytes), to better support Raspberry Pi users. Fixes
20948 bug 9686; bugfix on 0.2.4.14-alpha.
20950 o Minor features (bridges, pluggable transports):
20951 - Bridges now write the SHA1 digest of their identity key
20952 fingerprint (that is, a hash of a hash of their public key) to
20953 notice-level logs, and to a new hashed-fingerprint file. This
20954 information will help bridge operators look up their bridge in
20955 Globe and similar tools. Resolves ticket 10884.
20956 - Improve the message that Tor displays when running as a bridge
20957 using pluggable transports without an Extended ORPort listener.
20958 Also, log the message in the log file too. Resolves ticket 11043.
20960 o Minor features (other):
20961 - Add a new option, PredictedPortsRelevanceTime, to control how long
20962 after having received a request to connect to a given port Tor
20963 will try to keep circuits ready in anticipation of future requests
20964 for that port. Patch from "unixninja92"; implements ticket 9176.
20965 - Generate a warning if any ports are listed in the SocksPolicy,
20966 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
20967 AuthDirBadExit options. (These options only support address
20968 ranges.) Fixes part of ticket 11108.
20969 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
20972 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
20973 - Build without warnings under clang 3.4. (We have some macros that
20974 define static functions only some of which will get used later in
20975 the module. Starting with clang 3.4, these give a warning unless the
20976 unused attribute is set on them.) Resolves ticket 10904.
20977 - Fix build warnings about missing "a2x" comment when building the
20978 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
20979 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
20981 o Minor bugfixes (client):
20982 - Improve the log message when we can't connect to a hidden service
20983 because all of the hidden service directory nodes hosting its
20984 descriptor are excluded. Improves on our fix for bug 10722, which
20985 was a bugfix on 0.2.0.10-alpha.
20986 - Raise a control port warning when we fail to connect to all of
20987 our bridges. Previously, we didn't inform the controller, and
20988 the bootstrap process would stall. Fixes bug 11069; bugfix on
20990 - Exit immediately when a process-owning controller exits.
20991 Previously, tor relays would wait for a little while after their
20992 controller exited, as if they had gotten an INT signal -- but this
20993 was problematic, since there was no feedback for the user. To do a
20994 clean shutdown, controllers should send an INT signal and give Tor
20995 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
20996 - Stop attempting to connect to bridges before our pluggable
20997 transports are configured (harmless but resulted in some erroneous
20998 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
20999 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
21000 generating incorrect SOCKS5 responses, and confusing client
21001 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
21003 o Minor bugfixes (relays and bridges):
21004 - Avoid crashing on a malformed resolv.conf file when running a
21005 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
21006 - Non-exit relays no longer launch mock DNS requests to check for
21007 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
21008 non-exit relays stopped servicing DNS requests. Fixes bug 965;
21009 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
21010 - Bridges now report complete directory request statistics. Related
21011 to bug 5824; bugfix on 0.2.2.1-alpha.
21012 - Bridges now never collect statistics that were designed for
21013 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
21014 - Stop giving annoying warning messages when we decide not to launch
21015 a pluggable transport proxy that we don't need (because there are
21016 no bridges configured to use it). Resolves ticket 5018; bugfix
21018 - Give the correct URL in the warning message when trying to run a
21019 relay on an ancient version of Windows. Fixes bug 9393.
21021 o Minor bugfixes (backtrace support):
21022 - Support automatic backtraces on more platforms by using the
21023 "-fasynchronous-unwind-tables" compiler option. This option is
21024 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
21025 is on by default and table generation is not. This doesn't yet
21026 add Windows support; only Linux, OSX, and some BSDs are affected.
21027 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
21028 - Avoid strange behavior if two threads hit failed assertions at the
21029 same time and both try to log backtraces at once. (Previously, if
21030 this had happened, both threads would have stored their intermediate
21031 results in the same buffer, and generated junk outputs.) Reported by
21032 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
21033 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
21034 0.2.5.2-alpha; patch from Nick Hopper.
21036 o Minor bugfixes (unit tests):
21037 - Fix a small bug in the unit tests that might have made the tests
21038 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
21039 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
21042 - Remove all remaining code related to version-0 hidden service
21043 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
21044 the rest of bug 10841.
21047 - Document in the manpage that "KBytes" may also be written as
21048 "kilobytes" or "KB", that "Kbits" may also be written as
21049 "kilobits", and so forth. Closes ticket 9222.
21050 - Document that the ClientOnly config option overrides ORPort.
21051 Our old explanation made ClientOnly sound as though it did
21052 nothing at all. Resolves bug 9059.
21053 - Explain that SocksPolicy, DirPolicy, and similar options don't
21054 take port arguments. Fixes the other part of ticket 11108.
21055 - Fix a comment about the rend_server_descriptor_t.protocols field
21056 to more accurately describe its range. Also, make that field
21057 unsigned, to more accurately reflect its usage. Fixes bug 9099;
21058 bugfix on 0.2.1.5-alpha.
21059 - Fix the manpage's description of HiddenServiceAuthorizeClient:
21060 the maximum client name length is 16, not 19. Fixes bug 11118;
21061 bugfix on 0.2.1.6-alpha.
21063 o Code simplifications and refactoring:
21064 - Get rid of router->address, since in all cases it was just the
21065 string representation of router->addr. Resolves ticket 5528.
21067 o Test infrastructure:
21068 - Update to the latest version of tinytest.
21069 - Improve the tinytest implementation of string operation tests so
21070 that comparisons with NULL strings no longer crash the tests; they
21071 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
21074 Changes in version 0.2.4.21 - 2014-02-28
21075 Tor 0.2.4.21 further improves security against potential adversaries who
21076 find breaking 1024-bit crypto doable, and backports several stability
21077 and robustness patches from the 0.2.5 branch.
21079 o Major features (client security):
21080 - When we choose a path for a 3-hop circuit, make sure it contains
21081 at least one relay that supports the NTor circuit extension
21082 handshake. Otherwise, there is a chance that we're building
21083 a circuit that's worth attacking by an adversary who finds
21084 breaking 1024-bit crypto doable, and that chance changes the game
21085 theory. Implements ticket 9777.
21088 - Do not treat streams that fail with reason
21089 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
21090 since it could also indicate an ENETUNREACH connection error. Fixes
21091 part of bug 10777; bugfix on 0.2.4.8-alpha.
21093 o Code simplification and refactoring:
21094 - Remove data structures which were introduced to implement the
21095 CellStatistics option: they are now redundant with the new timestamp
21096 field in the regular packed_cell_t data structure, which we did
21097 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
21100 - Always clear OpenSSL bignums before freeing them -- even bignums
21101 that don't contain secrets. Resolves ticket 10793. Patch by
21103 - Build without warnings under clang 3.4. (We have some macros that
21104 define static functions only some of which will get used later in
21105 the module. Starting with clang 3.4, these give a warning unless the
21106 unused attribute is set on them.) Resolves ticket 10904.
21107 - Update geoip and geoip6 files to the February 7 2014 Maxmind
21108 GeoLite2 Country database.
21111 - Set the listen() backlog limit to the largest actually supported
21112 on the system, not to the value in a header file. Fixes bug 9716;
21113 bugfix on every released Tor.
21114 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
21115 exit node as a NOROUTE error, not an INTERNAL error, since they
21116 can apparently happen when trying to connect to the wrong sort
21117 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
21118 - Fix build warnings about missing "a2x" comment when building the
21119 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
21120 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
21121 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
21122 not entirely remove it from the connection lists. Fixes bug 9602;
21123 bugfix on 0.2.4.4-alpha.
21124 - Fix a segmentation fault in our benchmark code when running with
21125 Fedora's OpenSSL package, or any other OpenSSL that provides
21126 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
21127 - Turn "circuit handshake stats since last time" log messages into a
21128 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
21130 o Documentation fixes:
21131 - Document that all but one DirPort entry must have the NoAdvertise
21132 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
21135 Changes in version 0.2.5.2-alpha - 2014-02-13
21136 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
21137 like the "poor random number generation" fix and the "building too many
21138 circuits" fix. It also further improves security against potential
21139 adversaries who find breaking 1024-bit crypto doable, and launches
21140 pluggable transports on demand (which gets us closer to integrating
21141 pluggable transport support by default -- not to be confused with Tor
21142 bundles enabling pluggable transports and bridges by default).
21144 o Major features (client security):
21145 - When we choose a path for a 3-hop circuit, make sure it contains
21146 at least one relay that supports the NTor circuit extension
21147 handshake. Otherwise, there is a chance that we're building
21148 a circuit that's worth attacking by an adversary who finds
21149 breaking 1024-bit crypto doable, and that chance changes the game
21150 theory. Implements ticket 9777.
21151 - Clients now look at the "usecreatefast" consensus parameter to
21152 decide whether to use CREATE_FAST or CREATE cells for the first hop
21153 of their circuit. This approach can improve security on connections
21154 where Tor's circuit handshake is stronger than the available TLS
21155 connection security levels, but the tradeoff is more computational
21156 load on guard relays. Implements proposal 221. Resolves ticket 9386.
21158 o Major features (bridges):
21159 - Don't launch pluggable transport proxies if we don't have any
21160 bridges configured that would use them. Now we can list many
21161 pluggable transports, and Tor will dynamically start one when it
21162 hears a bridge address that needs it. Resolves ticket 5018.
21163 - The bridge directory authority now assigns status flags (Stable,
21164 Guard, etc) to bridges based on thresholds calculated over all
21165 Running bridges. Now bridgedb can finally make use of its features
21166 to e.g. include at least one Stable bridge in its answers. Fixes
21169 o Major features (other):
21170 - Extend ORCONN controller event to include an "ID" parameter,
21171 and add four new controller event types CONN_BW, CIRC_BW,
21172 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
21173 The new events are emitted in private Tor networks only, with the
21174 goal of being able to better track performance and load during
21175 full-network simulations. Implements proposal 218 and ticket 7359.
21176 - On some platforms (currently: recent OSX versions, glibc-based
21177 platforms that support the ELF format, and a few other
21178 Unix-like operating systems), Tor can now dump stack traces
21179 when a crash occurs or an assertion fails. By default, traces
21180 are dumped to stderr (if possible) and to any logs that are
21181 reporting errors. Implements ticket 9299.
21184 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
21185 not entirely remove it from the connection lists. Fixes bug 9602;
21186 bugfix on 0.2.4.4-alpha.
21187 - Do not treat streams that fail with reason
21188 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
21189 since it could also indicate an ENETUNREACH connection error. Fixes
21190 part of bug 10777; bugfix on 0.2.4.8-alpha.
21192 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
21193 - Do not allow OpenSSL engines to replace the PRNG, even when
21194 HardwareAccel is set. The only default builtin PRNG engine uses
21195 the Intel RDRAND instruction to replace the entire PRNG, and
21196 ignores all attempts to seed it with more entropy. That's
21197 cryptographically stupid: the right response to a new alleged
21198 entropy source is never to discard all previously used entropy
21199 sources. Fixes bug 10402; works around behavior introduced in
21200 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
21202 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
21203 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
21204 - Avoid launching spurious extra circuits when a stream is pending.
21205 This fixes a bug where any circuit that _wasn't_ unusable for new
21206 streams would be treated as if it were, causing extra circuits to
21207 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
21209 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
21210 - No longer stop reading or writing on cpuworker connections when
21211 our rate limiting buckets go empty. Now we should handle circuit
21212 handshake requests more promptly. Resolves bug 9731.
21213 - Stop trying to bootstrap all our directory information from
21214 only our first guard. Discovered while fixing bug 9946; bugfix
21217 o Minor features (bridges, pluggable transports):
21218 - Add threshold cutoffs to the networkstatus document created by
21219 the Bridge Authority. Fixes bug 1117.
21220 - On Windows, spawn background processes using the CREATE_NO_WINDOW
21221 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
21222 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
21223 Vidalia set this option for us.) Implements ticket 10297.
21225 o Minor features (security):
21226 - Always clear OpenSSL bignums before freeing them -- even bignums
21227 that don't contain secrets. Resolves ticket 10793. Patch by
21230 o Minor features (config options and command line):
21231 - Add an --allow-missing-torrc commandline option that tells Tor to
21232 run even if the configuration file specified by -f is not available.
21233 Implements ticket 10060.
21234 - Add support for the TPROXY transparent proxying facility on Linux.
21235 See documentation for the new TransProxyType option for more
21236 details. Implementation by "thomo". Closes ticket 10582.
21238 o Minor features (controller):
21239 - Add a new "HS_DESC" controller event that reports activities
21240 related to hidden service descriptors. Resolves ticket 8510.
21241 - New "DROPGUARDS" controller command to forget all current entry
21242 guards. Not recommended for ordinary use, since replacing guards
21243 too frequently makes several attacks easier. Resolves ticket 9934;
21246 o Minor features (build):
21247 - Assume that a user using ./configure --host wants to cross-compile,
21248 and give an error if we cannot find a properly named
21249 tool-chain. Add a --disable-tool-name-check option to proceed
21250 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
21251 - If we run ./configure and the compiler recognizes -fstack-protector
21252 but the linker rejects it, warn the user about a potentially missing
21253 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
21255 o Minor features (testing):
21256 - If Python is installed, "make check" now runs extra tests beyond
21257 the unit test scripts.
21258 - When bootstrapping a test network, sometimes very few relays get
21259 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
21260 specify a set of relays which should be voted Guard regardless of
21261 their uptime or bandwidth. Addresses ticket 9206.
21263 o Minor features (log messages):
21264 - When ServerTransportPlugin is set on a bridge, Tor can write more
21265 useful statistics about bridge use in its extrainfo descriptors,
21266 but only if the Extended ORPort ("ExtORPort") is set too. Add a
21267 log message to inform the user in this case. Resolves ticket 9651.
21268 - When receiving a new controller connection, log the origin address.
21269 Resolves ticket 9698; patch from "sigpipe".
21270 - When logging OpenSSL engine status at startup, log the status of
21271 more engines. Fixes ticket 10043; patch from Joshua Datko.
21272 - Turn "circuit handshake stats since last time" log messages into a
21273 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
21275 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
21276 - Improve the circuit queue out-of-memory handler. Previously, when
21277 we ran low on memory, we'd close whichever circuits had the most
21278 queued cells. Now, we close those that have the *oldest* queued
21279 cells, on the theory that those are most responsible for us
21280 running low on memory. Based on analysis from a forthcoming paper
21281 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
21282 - Generate bootstrapping status update events correctly when fetching
21283 microdescriptors. Fixes bug 9927.
21284 - Update to the October 2 2013 Maxmind GeoLite Country database.
21286 o Minor bugfixes (clients):
21287 - When closing a channel that has already been open, do not close
21288 pending circuits that were waiting to connect to the same relay.
21289 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
21292 o Minor bugfixes (relays):
21293 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
21294 exit node as a NOROUTE error, not an INTERNAL error, since they
21295 can apparently happen when trying to connect to the wrong sort
21296 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
21298 o Minor bugfixes (bridges):
21299 - Fix a bug where the first connection works to a bridge that uses a
21300 pluggable transport with client-side parameters, but we don't send
21301 the client-side parameters on subsequent connections. (We don't
21302 use any pluggable transports with client-side parameters yet,
21303 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
21304 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
21306 o Minor bugfixes (node selection):
21307 - If ExcludeNodes is set, consider non-excluded hidden service
21308 directory servers before excluded ones. Do not consider excluded
21309 hidden service directory servers at all if StrictNodes is
21310 set. (Previously, we would sometimes decide to connect to those
21311 servers, and then realize before we initiated a connection that
21312 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
21313 Reported by "mr-4".
21314 - If we set the ExitNodes option but it doesn't include any nodes
21315 that have the Exit flag, we would choose not to bootstrap. Now we
21316 bootstrap so long as ExitNodes includes nodes which can exit to
21317 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
21319 o Minor bugfixes (controller and command-line):
21320 - If changing a config option via "setconf" fails in a recoverable
21321 way, we used to nonetheless write our new control ports to the
21322 file described by the "ControlPortWriteToFile" option. Now we only
21323 write out that file if we successfully switch to the new config
21324 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
21325 - When a command-line option such as --version or --help that
21326 ordinarily implies --hush appears on the command line along with
21327 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
21328 only if it appeared later on the command line. Fixes bug 9578;
21329 bugfix on 0.2.5.1-alpha.
21331 o Minor bugfixes (code correctness):
21332 - Previously we used two temporary files when writing descriptors to
21333 disk; now we only use one. Fixes bug 1376.
21334 - Remove an erroneous (but impossible and thus harmless) pointer
21335 comparison that would have allowed compilers to skip a bounds
21336 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
21337 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
21338 - Fix an always-true assertion in pluggable transports code so it
21339 actually checks what it was trying to check. Fixes bug 10046;
21340 bugfix on 0.2.3.9-alpha. Found by "dcb".
21342 o Minor bugfixes (protocol correctness):
21343 - When receiving a VERSIONS cell with an odd number of bytes, close
21344 the connection immediately since the cell is malformed. Fixes bug
21345 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
21348 o Minor bugfixes (build):
21349 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
21350 turned off (that is, without support for v2 link handshakes). Fixes
21351 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
21352 - Fix compilation warnings and startup issues when running with
21353 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
21355 - Fix compilation on Solaris 9, which didn't like us having an
21356 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
21358 o Minor bugfixes (testing):
21359 - Fix a segmentation fault in our benchmark code when running with
21360 Fedora's OpenSSL package, or any other OpenSSL that provides
21361 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
21363 o Minor bugfixes (log messages):
21364 - Fix a bug where clients using bridges would report themselves
21365 as 50% bootstrapped even without a live consensus document.
21366 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
21367 - Suppress a warning where, if there's only one directory authority
21368 in the network, we would complain that votes and signatures cannot
21369 be uploaded to other directory authorities. Fixes bug 10842;
21370 bugfix on 0.2.2.26-beta.
21371 - Report bootstrapping progress correctly when we're downloading
21372 microdescriptors. We had updated our "do we have enough microdescs
21373 to begin building circuits?" logic most recently in 0.2.4.10-alpha
21374 (see bug 5956), but we left the bootstrap status event logic at
21375 "how far through getting 1/4 of them are we?" Fixes bug 9958;
21376 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
21378 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
21379 - Avoid a crash bug when starting with a corrupted microdescriptor
21380 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
21381 - If we fail to dump a previously cached microdescriptor to disk, avoid
21382 freeing duplicate data later on. Fixes bug 10423; bugfix on
21383 0.2.4.13-alpha. Spotted by "bobnomnom".
21385 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
21386 - Correctly log long IPv6 exit policies, instead of truncating them
21387 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
21388 - Our default TLS ecdhe groups were backwards: we meant to be using
21389 P224 for relays (for performance win) and P256 for bridges (since
21390 it is more common in the wild). Instead we had it backwards. After
21391 reconsideration, we decided that the default should be P256 on all
21392 hosts, since its security is probably better, and since P224 is
21393 reportedly used quite little in the wild. Found by "skruffy" on
21394 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
21395 - Free directory authority certificate download statuses on exit
21396 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
21398 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
21399 - If the guard we choose first doesn't answer, we would try the
21400 second guard, but once we connected to the second guard we would
21401 abandon it and retry the first one, slowing down bootstrapping.
21402 The fix is to treat all our initially chosen guards as acceptable
21403 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
21404 - Fix an assertion failure that would occur when disabling the
21405 ORPort setting on a running Tor process while accounting was
21406 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
21407 - When examining the list of network interfaces to find our address,
21408 do not consider non-running or disabled network interfaces. Fixes
21409 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
21410 - Avoid an off-by-one error when checking buffer boundaries when
21411 formatting the exit status of a pluggable transport helper.
21412 This is probably not an exploitable bug, but better safe than
21413 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
21416 o Removed code and features:
21417 - Clients now reject any directory authority certificates lacking
21418 a dir-key-crosscert element. These have been included since
21419 0.2.1.9-alpha, so there's no real reason for them to be optional
21420 any longer. Completes proposal 157. Resolves ticket 10162.
21421 - Remove all code that existed to support the v2 directory system,
21422 since there are no longer any v2 directory authorities. Resolves
21424 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
21425 options, which were used for designating authorities as "Hidden
21426 service authorities". There has been no use of hidden service
21427 authorities since 0.2.2.1-alpha, when we stopped uploading or
21428 downloading v0 hidden service descriptors. Fixes bug 10881; also
21429 part of a fix for bug 10841.
21431 o Code simplification and refactoring:
21432 - Remove some old fallback code designed to keep Tor clients working
21433 in a network with only two working relays. Elsewhere in the code we
21434 have long since stopped supporting such networks, so there wasn't
21435 much point in keeping it around. Addresses ticket 9926.
21436 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
21437 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
21438 - Remove data structures which were introduced to implement the
21439 CellStatistics option: they are now redundant with the addition
21440 of a timestamp to the regular packed_cell_t data structure, which
21441 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
21444 o Documentation (man page) fixes:
21445 - Update manpage to describe some of the files you can expect to
21446 find in Tor's DataDirectory. Addresses ticket 9839.
21447 - Document that all but one DirPort entry must have the NoAdvertise
21448 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
21450 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
21451 - Clarify the usage and risks of setting the ContactInfo torrc line
21452 for your relay or bridge. Resolves ticket 9854.
21453 - Add anchors to the manpage so we can link to the html version of
21454 the documentation for specific options. Resolves ticket 9866.
21455 - Replace remaining references to DirServer in man page and
21456 log entries. Resolves ticket 10124.
21459 - Make the "tor-gencert" tool used by directory authority operators
21460 create 2048-bit signing keys by default (rather than 1024-bit, since
21461 1024-bit is uncomfortably small these days). Addresses ticket 10324.
21464 Changes in version 0.2.4.20 - 2013-12-22
21465 Tor 0.2.4.20 fixes potentially poor random number generation for users
21466 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
21467 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
21468 and 4) have no state file in their DataDirectory (as would happen on
21469 first start). Users who generated relay or hidden service identity
21470 keys in such a situation should discard them and generate new ones.
21472 This release also fixes a logic error that caused Tor clients to build
21473 many more preemptive circuits than they actually need.
21476 - Do not allow OpenSSL engines to replace the PRNG, even when
21477 HardwareAccel is set. The only default builtin PRNG engine uses
21478 the Intel RDRAND instruction to replace the entire PRNG, and
21479 ignores all attempts to seed it with more entropy. That's
21480 cryptographically stupid: the right response to a new alleged
21481 entropy source is never to discard all previously used entropy
21482 sources. Fixes bug 10402; works around behavior introduced in
21483 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
21485 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
21486 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
21487 - Avoid launching spurious extra circuits when a stream is pending.
21488 This fixes a bug where any circuit that _wasn't_ unusable for new
21489 streams would be treated as if it were, causing extra circuits to
21490 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
21493 - Avoid a crash bug when starting with a corrupted microdescriptor
21494 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
21495 - If we fail to dump a previously cached microdescriptor to disk, avoid
21496 freeing duplicate data later on. Fixes bug 10423; bugfix on
21497 0.2.4.13-alpha. Spotted by "bobnomnom".
21500 Changes in version 0.2.4.19 - 2013-12-11
21501 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
21502 (1986-2013). Aaron worked on diverse projects including helping to guide
21503 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
21504 transparency to the U.S government's PACER documents, and contributing
21505 design and development for Tor and Tor2Web. Aaron was one of the latest
21506 martyrs in our collective fight for civil liberties and human rights,
21507 and his death is all the more painful because he was one of us.
21509 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
21510 a new circuit handshake and link encryption that use ECC to provide
21511 better security and efficiency; makes relays better manage circuit
21512 creation requests; uses "directory guards" to reduce client enumeration
21513 risks; makes bridges collect and report statistics about the pluggable
21514 transports they support; cleans up and improves our geoip database;
21515 gets much closer to IPv6 support for clients, bridges, and relays; makes
21516 directory authorities use measured bandwidths rather than advertised
21517 ones when computing flags and thresholds; disables client-side DNS
21518 caching to reduce tracking risks; and fixes a big bug in bridge
21519 reachability testing. This release introduces two new design
21520 abstractions in the code: a new "channel" abstraction between circuits
21521 and or_connections to allow for implementing alternate relay-to-relay
21522 transports, and a new "circuitmux" abstraction storing the queue of
21523 circuits for a channel. The release also includes many stability,
21524 security, and privacy fixes.
21527 Changes in version 0.2.4.18-rc - 2013-11-16
21528 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
21529 series. It takes a variety of fixes from the 0.2.5.x branch to improve
21530 stability, performance, and better handling of edge cases.
21533 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
21534 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
21535 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
21536 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
21537 them to solve bug 6033.)
21540 - No longer stop reading or writing on cpuworker connections when
21541 our rate limiting buckets go empty. Now we should handle circuit
21542 handshake requests more promptly. Resolves bug 9731.
21543 - If we are unable to save a microdescriptor to the journal, do not
21544 drop it from memory and then reattempt downloading it. Fixes bug
21545 9645; bugfix on 0.2.2.6-alpha.
21546 - Stop trying to bootstrap all our directory information from
21547 only our first guard. Discovered while fixing bug 9946; bugfix
21549 - The new channel code sometimes lost track of in-progress circuits,
21550 causing long-running clients to stop building new circuits. The
21551 fix is to always call circuit_n_chan_done(chan, 0) from
21552 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
21554 o Minor bugfixes (on 0.2.4.x):
21555 - Correctly log long IPv6 exit policies, instead of truncating them
21556 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
21557 - Our default TLS ecdhe groups were backwards: we meant to be using
21558 P224 for relays (for performance win) and P256 for bridges (since
21559 it is more common in the wild). Instead we had it backwards. After
21560 reconsideration, we decided that the default should be P256 on all
21561 hosts, since its security is probably better, and since P224 is
21562 reportedly used quite little in the wild. Found by "skruffy" on
21563 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
21564 - Free directory authority certificate download statuses on exit
21565 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
21567 o Minor bugfixes (on 0.2.3.x and earlier):
21568 - If the guard we choose first doesn't answer, we would try the
21569 second guard, but once we connected to the second guard we would
21570 abandon it and retry the first one, slowing down bootstrapping.
21571 The fix is to treat all our initially chosen guards as acceptable
21572 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
21573 - Fix an assertion failure that would occur when disabling the
21574 ORPort setting on a running Tor process while accounting was
21575 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
21576 - When examining the list of network interfaces to find our address,
21577 do not consider non-running or disabled network interfaces. Fixes
21578 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
21579 - Avoid an off-by-one error when checking buffer boundaries when
21580 formatting the exit status of a pluggable transport helper.
21581 This is probably not an exploitable bug, but better safe than
21582 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
21585 o Minor features (protecting client timestamps):
21586 - Clients no longer send timestamps in their NETINFO cells. These were
21587 not used for anything, and they provided one small way for clients
21588 to be distinguished from each other as they moved from network to
21589 network or behind NAT. Implements part of proposal 222.
21590 - Clients now round timestamps in INTRODUCE cells down to the nearest
21591 10 minutes. If a new Support022HiddenServices option is set to 0, or
21592 if it's set to "auto" and the feature is disabled in the consensus,
21593 the timestamp is sent as 0 instead. Implements part of proposal 222.
21594 - Stop sending timestamps in AUTHENTICATE cells. This is not such
21595 a big deal from a security point of view, but it achieves no actual
21596 good purpose, and isn't needed. Implements part of proposal 222.
21597 - Reduce down accuracy of timestamps in hidden service descriptors.
21598 Implements part of proposal 222.
21600 o Minor features (other):
21601 - Improve the circuit queue out-of-memory handler. Previously, when
21602 we ran low on memory, we'd close whichever circuits had the most
21603 queued cells. Now, we close those that have the *oldest* queued
21604 cells, on the theory that those are most responsible for us
21605 running low on memory. Based on analysis from a forthcoming paper
21606 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
21607 - Generate bootstrapping status update events correctly when fetching
21608 microdescriptors. Fixes bug 9927.
21609 - Update to the October 2 2013 Maxmind GeoLite Country database.
21611 o Documentation fixes:
21612 - Clarify the usage and risks of setting the ContactInfo torrc line
21613 for your relay or bridge. Resolves ticket 9854.
21614 - Add anchors to the manpage so we can link to the html version of
21615 the documentation for specific options. Resolves ticket 9866.
21616 - Replace remaining references to DirServer in man page and
21617 log entries. Resolves ticket 10124.
21620 Changes in version 0.2.5.1-alpha - 2013-10-02
21621 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
21622 on Linux, allows bridges that offer pluggable transports to report usage
21623 statistics, fixes many issues to make testing easier, and provides
21624 a pile of minor features and bugfixes that have been waiting for a
21625 release of the new branch.
21627 This is the first alpha release in a new series, so expect there to
21628 be bugs. Users who would rather test out a more stable branch should
21629 stay with 0.2.4.x for now.
21631 o Major features (security):
21632 - Use the seccomp2 syscall filtering facility on Linux to limit
21633 which system calls Tor can invoke. This is an experimental,
21634 Linux-only feature to provide defense-in-depth against unknown
21635 attacks. To try turning it on, set "Sandbox 1" in your torrc
21636 file. Please be ready to report bugs. We hope to add support
21637 for better sandboxing in the future, including more fine-grained
21638 filters, better division of responsibility, and support for more
21639 platforms. This work has been done by Cristian-Matei Toader for
21640 Google Summer of Code.
21641 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
21642 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
21643 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
21644 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
21645 them to solve bug 6033.)
21647 o Major features (other):
21648 - Add support for passing arguments to managed pluggable transport
21649 proxies. Implements ticket 3594.
21650 - Bridges now track GeoIP information and the number of their users
21651 even when pluggable transports are in use, and report usage
21652 statistics in their extra-info descriptors. Resolves tickets 4773
21654 - Make testing Tor networks bootstrap better: lower directory fetch
21655 retry schedules and maximum interval without directory requests,
21656 and raise maximum download tries. Implements ticket 6752.
21657 - Add make target 'test-network' to run tests on a Chutney network.
21658 Implements ticket 8530.
21659 - The ntor handshake is now on-by-default, no matter what the
21660 directory authorities recommend. Implements ticket 8561.
21663 - Instead of writing destroy cells directly to outgoing connection
21664 buffers, queue them and intersperse them with other outgoing cells.
21665 This can prevent a set of resource starvation conditions where too
21666 many pending destroy cells prevent data cells from actually getting
21667 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
21668 bugfix on 0.2.0.1-alpha.
21669 - If we are unable to save a microdescriptor to the journal, do not
21670 drop it from memory and then reattempt downloading it. Fixes bug
21671 9645; bugfix on 0.2.2.6-alpha.
21672 - The new channel code sometimes lost track of in-progress circuits,
21673 causing long-running clients to stop building new circuits. The
21674 fix is to always call circuit_n_chan_done(chan, 0) from
21675 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
21678 - Tor now builds each source file in two modes: a mode that avoids
21679 exposing identifiers needlessly, and another mode that exposes
21680 more identifiers for testing. This lets the compiler do better at
21681 optimizing the production code, while enabling us to take more
21682 radical measures to let the unit tests test things.
21683 - The production builds no longer include functions used only in
21684 the unit tests; all functions exposed from a module only for
21685 unit-testing are now static in production builds.
21686 - Add an --enable-coverage configuration option to make the unit
21687 tests (and a new src/or/tor-cov target) to build with gcov test
21691 - We now have rudimentary function mocking support that our unit
21692 tests can use to test functions in isolation. Function mocking
21693 lets the tests temporarily replace a function's dependencies with
21694 stub functions, so that the tests can check the function without
21695 invoking the other functions it calls.
21696 - Add more unit tests for the <circid,channel>->circuit map, and
21697 the destroy-cell-tracking code to fix bug 7912.
21698 - Unit tests for failing cases of the TAP onion handshake.
21699 - More unit tests for address-manipulation functions.
21701 o Minor features (protecting client timestamps):
21702 - Clients no longer send timestamps in their NETINFO cells. These were
21703 not used for anything, and they provided one small way for clients
21704 to be distinguished from each other as they moved from network to
21705 network or behind NAT. Implements part of proposal 222.
21706 - Clients now round timestamps in INTRODUCE cells down to the nearest
21707 10 minutes. If a new Support022HiddenServices option is set to 0, or
21708 if it's set to "auto" and the feature is disabled in the consensus,
21709 the timestamp is sent as 0 instead. Implements part of proposal 222.
21710 - Stop sending timestamps in AUTHENTICATE cells. This is not such
21711 a big deal from a security point of view, but it achieves no actual
21712 good purpose, and isn't needed. Implements part of proposal 222.
21713 - Reduce down accuracy of timestamps in hidden service descriptors.
21714 Implements part of proposal 222.
21716 o Minor features (config options):
21717 - Config (torrc) lines now handle fingerprints which are missing
21718 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
21719 - Support a --dump-config option to print some or all of the
21720 configured options. Mainly useful for debugging the command-line
21721 option parsing code. Helps resolve ticket 4647.
21722 - Raise awareness of safer logging: notify user of potentially
21723 unsafe config options, like logging more verbosely than severity
21724 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
21725 - Add a new configuration option TestingV3AuthVotingStartOffset
21726 that bootstraps a network faster by changing the timing for
21727 consensus votes. Addresses ticket 8532.
21728 - Add a new torrc option "ServerTransportOptions" that allows
21729 bridge operators to pass configuration parameters to their
21730 pluggable transports. Resolves ticket 8929.
21731 - The config (torrc) file now accepts bandwidth and space limits in
21732 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
21733 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
21736 o Minor features (build):
21737 - Add support for `--library-versions` flag. Implements ticket 6384.
21738 - Return the "unexpected sendme" warnings to a warn severity, but make
21739 them rate limited, to help diagnose ticket 8093.
21740 - Detect a missing asciidoc, and warn the user about it, during
21741 configure rather than at build time. Fixes issue 6506. Patch from
21744 o Minor features (other):
21745 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
21746 sockets in a single system call. Implements ticket 5129.
21747 - Log current accounting state (bytes sent and received + remaining
21748 time for the current accounting period) in the relay's heartbeat
21749 message. Implements ticket 5526; patch from Peter Retzlaff.
21750 - Implement the TRANSPORT_LAUNCHED control port event that
21751 notifies controllers about new launched pluggable
21752 transports. Resolves ticket 5609.
21753 - If we're using the pure-C 32-bit curve25519_donna implementation
21754 of curve25519, build it with the -fomit-frame-pointer option to
21755 make it go faster on register-starved hosts. This improves our
21756 handshake performance by about 6% on i386 hosts without nacl.
21757 Closes ticket 8109.
21758 - Update to the September 4 2013 Maxmind GeoLite Country database.
21761 - Set the listen() backlog limit to the largest actually supported
21762 on the system, not to the value in a header file. Fixes bug 9716;
21763 bugfix on every released Tor.
21764 - No longer accept malformed http headers when parsing urls from
21765 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
21766 bugfix on 0.0.6pre1.
21767 - In munge_extrainfo_into_routerinfo(), check the return value of
21768 memchr(). This would have been a serious issue if we ever passed
21769 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
21771 - On the chance that somebody manages to build Tor on a
21772 platform where time_t is unsigned, correct the way that
21773 microdesc_add_to_cache() handles negative time arguments.
21774 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
21775 - Reject relative control socket paths and emit a warning. Previously,
21776 single-component control socket paths would be rejected, but Tor
21777 would not log why it could not validate the config. Fixes bug 9258;
21778 bugfix on 0.2.3.16-alpha.
21780 o Minor bugfixes (command line):
21781 - Use a single command-line parser for parsing torrc options on the
21782 command line and for finding special command-line options to avoid
21783 inconsistent behavior for torrc option arguments that have the same
21784 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
21786 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
21787 9573; bugfix on 0.0.9pre5.
21789 o Minor fixes (build, auxiliary programs):
21790 - Stop preprocessing the "torify" script with autoconf, since
21791 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
21793 - The tor-fw-helper program now follows the standard convention and
21794 exits with status code "0" on success. Fixes bug 9030; bugfix on
21795 0.2.3.1-alpha. Patch by Arlo Breault.
21796 - Corrected ./configure advice for what openssl dev package you should
21797 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
21799 o Minor code improvements:
21800 - Remove constants and tests for PKCS1 padding; it's insecure and
21801 shouldn't be used for anything new. Fixes bug 8792; patch
21803 - Remove instances of strcpy() from the unit tests. They weren't
21804 hurting anything, since they were only in the unit tests, but it's
21805 embarrassing to have strcpy() in the code at all, and some analysis
21806 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
21807 0.2.3.8-alpha. Patch from Arlo Breault.
21809 o Removed features:
21810 - Remove migration code from when we renamed the "cached-routers"
21811 file to "cached-descriptors" back in 0.2.0.8-alpha. This
21812 incidentally resolves ticket 6502 by cleaning up the related code
21813 a bit. Patch from Akshay Hebbar.
21815 o Code simplification and refactoring:
21816 - Extract the common duplicated code for creating a subdirectory
21817 of the data directory and writing to a file in it. Fixes ticket
21818 4282; patch from Peter Retzlaff.
21819 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
21820 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
21821 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
21822 - Add a set of accessor functions for the circuit timeout data
21823 structure. Fixes ticket 6153; patch from "piet".
21824 - Clean up exit paths from connection_listener_new(). Closes ticket
21825 8789. Patch from Arlo Breault.
21826 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
21827 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
21828 - Use a doubly-linked list to implement the global circuit list.
21829 Resolves ticket 9108. Patch from Marek Majkowski.
21830 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
21833 Changes in version 0.2.4.17-rc - 2013-09-05
21834 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
21835 series. It adds an emergency step to help us tolerate the massive
21836 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
21837 circuit-level handshakes now effectively jump the queue compared to
21838 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
21839 big bug hindering bridge reachability tests.
21842 - Relays now process the new "NTor" circuit-level handshake requests
21843 with higher priority than the old "TAP" circuit-level handshake
21844 requests. We still process some TAP requests to not totally starve
21845 0.2.3 clients when NTor becomes popular. A new consensus parameter
21846 "NumNTorsPerTAP" lets us tune the balance later if we need to.
21847 Implements ticket 9574.
21850 - If the circuit build timeout logic is disabled (via the consensus,
21851 or because we are an authority), then don't build testing circuits.
21852 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
21853 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
21854 previously they did not, which prevented them from receiving
21855 successful connections from relays for self-test or bandwidth
21856 testing. Also, when a relay is extending a circuit to a bridge,
21857 it needs to send a NETINFO cell, even when the bridge hasn't sent
21858 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
21859 - If the time to download the next old-style networkstatus is in
21860 the future, do not decline to consider whether to download the
21861 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
21865 - Avoid double-closing the listener socket in our socketpair()
21866 replacement (used on Windows) in the case where the addresses on
21867 our opened sockets don't match what we expected. Fixes bug 9400;
21868 bugfix on 0.0.2pre7. Found by Coverity.
21870 o Minor fixes (config options):
21871 - Avoid overflows when the user sets MaxCircuitDirtiness to a
21872 ridiculously high value, by imposing a (ridiculously high) 30-day
21873 maximum on MaxCircuitDirtiness.
21874 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
21875 message is logged at notice, not at info.
21876 - Warn and fail if a server is configured not to advertise any
21877 ORPorts at all. (We need *something* to put in our descriptor,
21878 or we just won't work.)
21881 - Track how many "TAP" and "NTor" circuit handshake requests we get,
21882 and how many we complete, and log it every hour to help relay
21883 operators follow trends in network load. Addresses ticket 9658.
21884 - Update to the August 7 2013 Maxmind GeoLite Country database.
21887 Changes in version 0.2.4.16-rc - 2013-08-10
21888 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
21889 series. It fixes several crash bugs in the 0.2.4 branch.
21892 - Fix a bug in the voting algorithm that could yield incorrect results
21893 when a non-naming authority declared too many flags. Fixes bug 9200;
21894 bugfix on 0.2.0.3-alpha.
21895 - Fix an uninitialized read that could in some cases lead to a remote
21896 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
21897 Anybody running a hidden service on the experimental 0.2.4.x
21898 branch should upgrade. (This is, so far as we know, unrelated to
21900 - Avoid an assertion failure when processing DNS replies without the
21901 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
21902 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
21903 0.2.4.15-rc. Found by stem integration tests.
21906 - Fix an invalid memory read that occurred when a pluggable
21907 transport proxy failed its configuration protocol.
21908 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
21909 - When evaluating whether to use a connection that we haven't
21910 decided is canonical using a recent link protocol version,
21911 decide that it's canonical only if it used address _does_
21912 match the desired address. Fixes bug 9309; bugfix on
21913 0.2.4.4-alpha. Reported by skruffy.
21914 - Make the default behavior of NumDirectoryGuards be to track
21915 NumEntryGuards. Now a user who changes only NumEntryGuards will get
21916 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
21917 - Fix a spurious compilation warning with some older versions of
21918 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
21921 - Update to the July 3 2013 Maxmind GeoLite Country database.
21924 Changes in version 0.2.4.15-rc - 2013-07-01
21925 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
21926 series. It fixes a few smaller bugs, but generally appears stable.
21927 Please test it and let us know whether it is!
21930 - When receiving a new configuration file via the control port's
21931 LOADCONF command, do not treat the defaults file as absent.
21932 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
21935 - Issue a warning when running with the bufferevents backend enabled.
21936 It's still not stable, and people should know that they're likely
21937 to hit unexpected problems. Closes ticket 9147.
21940 Changes in version 0.2.4.14-alpha - 2013-06-18
21941 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
21942 present in 0.2.4.13-alpha.
21945 - When we have too much memory queued in circuits (according to a new
21946 MaxMemInCellQueues option), close the circuits consuming the most
21947 memory. This prevents us from running out of memory as a relay if
21948 circuits fill up faster than they can be drained. Fixes bug 9063;
21949 bugfix on the 54th commit of Tor. This bug is a further fix beyond
21950 bug 6252, whose fix was merged into 0.2.3.21-rc.
21952 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
21953 where we tried to solve this issue simply by imposing an upper limit
21954 on the number of queued cells for a single circuit. That approach
21955 proved to be problematic, since there are ways to provoke clients to
21956 send a number of cells in excess of any such reasonable limit. Fixes
21957 bug 9072; bugfix on 0.2.4.13-alpha.
21959 - Limit hidden service descriptors to at most ten introduction
21960 points, to slow one kind of guard enumeration. Fixes bug 9002;
21961 bugfix on 0.1.1.11-alpha.
21964 Changes in version 0.2.4.13-alpha - 2013-06-14
21965 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
21966 vulnerabilities, makes socks5 username/password circuit isolation
21967 actually actually work (this time for sure!), and cleans up a bunch
21968 of other issues in preparation for a release candidate.
21970 o Major bugfixes (robustness):
21971 - Close any circuit that has too many cells queued on it. Fixes
21972 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
21973 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
21974 - Prevent the get_freelists() function from running off the end of
21975 the list of freelists if it somehow gets an unrecognized
21976 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
21978 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
21979 when an exit connection with optimistic data succeeds immediately
21980 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
21982 - Fix a directory authority crash bug when building a consensus
21983 using an older consensus as its basis. Fixes bug 8833. Bugfix
21987 - Avoid a memory leak where we would leak a consensus body when we
21988 find that a consensus which we couldn't previously verify due to
21989 missing certificates is now verifiable. Fixes bug 8719; bugfix
21991 - We used to always request authority certificates by identity digest,
21992 meaning we'd get the newest one even when we wanted one with a
21993 different signing key. Then we would complain about being given
21994 a certificate we already had, and never get the one we really
21995 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
21996 resource to request the one we want. Fixes bug 5595; bugfix on
21998 - Follow the socks5 protocol when offering username/password
21999 authentication. The fix for bug 8117 exposed this bug, and it
22000 turns out real-world applications like Pidgin do care. Bugfix on
22001 0.2.3.2-alpha; fixes bug 8879.
22002 - Prevent failures on Windows Vista and later when rebuilding the
22003 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
22004 bugfix on 0.2.4.12-alpha.
22007 - Fix an impossible buffer overrun in the AES unit tests. Fixes
22008 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
22009 - If for some reason we fail to write a microdescriptor while
22010 rebuilding the cache, do not let the annotations from that
22011 microdescriptor linger in the cache file, and do not let the
22012 microdescriptor stay recorded as present in its old location.
22013 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
22014 - Fix a memory leak that would occur whenever a configuration
22015 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
22016 - Paste the description for PathBias parameters from the man
22017 page into or.h, so the code documents them too. Fixes bug 7982;
22018 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
22019 - Relays now treat a changed IPv6 ORPort as sufficient reason to
22020 publish an updated descriptor. Fixes bug 6026; bugfix on
22022 - When launching a resolve request on behalf of an AF_UNIX control
22023 socket, omit the address field of the new entry connection, used in
22024 subsequent controller events, rather than letting tor_dup_addr()
22025 set it to "<unknown address type>". Fixes bug 8639; bugfix on
22028 o Minor bugfixes (log messages):
22029 - Fix a scaling issue in the path bias accounting code that
22030 resulted in "Bug:" log messages from either
22031 pathbias_scale_close_rates() or pathbias_count_build_success().
22032 This represents a bugfix on a previous bugfix: the original fix
22033 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
22035 - Give a less useless error message when the user asks for an IPv4
22036 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
22040 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
22041 to tolerate bug 8093 for now.
22042 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
22043 in directory authority votes to describe whether they have enough
22044 measured bandwidths to ignore advertised (relay descriptor)
22045 bandwidth claims. Resolves ticket 8711.
22046 - Update to the June 5 2013 Maxmind GeoLite Country database.
22048 o Removed documentation:
22049 - Remove some of the older contents of doc/ as obsolete; move others
22050 to torspec.git. Fixes bug 8965.
22052 o Code simplification and refactoring:
22053 - Avoid using character buffers when constructing most directory
22054 objects: this approach was unwieldy and error-prone. Instead,
22055 build smartlists of strings, and concatenate them when done.
22058 Changes in version 0.2.4.12-alpha - 2013-04-18
22059 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
22060 process for lengthening the guard rotation period, makes directory
22061 authority opinions in the consensus a bit less gameable, makes socks5
22062 username/password circuit isolation actually work, and fixes a wide
22063 variety of other issues.
22066 - Raise the default time that a client keeps an entry guard from
22067 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
22068 2012 paper. (We would make it even longer, but we need better client
22069 load balancing first.) Also, make the guard lifetime controllable
22070 via a new GuardLifetime torrc option and a GuardLifetime consensus
22071 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
22072 - Directory authorities now prefer using measured bandwidths to
22073 advertised ones when computing flags and thresholds. Resolves
22075 - Directory authorities that have more than a threshold number
22076 of relays with measured bandwidths now treat relays with unmeasured
22077 bandwidths as having bandwidth 0. Resolves ticket 8435.
22079 o Major bugfixes (assert / resource use):
22080 - Avoid a bug where our response to TLS renegotiation under certain
22081 network conditions could lead to a busy-loop, with 100% CPU
22082 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
22083 - Avoid an assertion when we discover that we'd like to write a cell
22084 onto a closing connection: just discard the cell. Fixes another
22085 case of bug 7350; bugfix on 0.2.4.4-alpha.
22087 o Major bugfixes (client-side privacy):
22088 - When we mark a circuit as unusable for new circuits, have it
22089 continue to be unusable for new circuits even if MaxCircuitDirtiness
22090 is increased too much at the wrong time, or the system clock jumps
22091 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
22092 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
22093 which have resolved to internal addresses") is set, apply that
22094 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
22095 - When an exit relay rejects a stream with reason "exit policy", but
22096 we only know an exit policy summary (e.g. from the microdesc
22097 consensus) for it, do not mark the relay as useless for all exiting.
22098 Instead, mark just the circuit as unsuitable for that particular
22099 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
22100 - Allow applications to get proper stream isolation with
22101 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
22102 username/password authentication also offer "no authentication". Tor
22103 had previously preferred "no authentication", so the applications
22104 never actually sent Tor their auth details. Now Tor selects
22105 username/password authentication if it's offered. You can disable
22106 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
22107 bug 8117; bugfix on 0.2.3.3-alpha.
22109 o Major bugfixes (other):
22110 - When unable to find any working directory nodes to use as a
22111 directory guard, give up rather than adding the same non-working
22112 nodes to the directory guard list over and over. Fixes bug 8231;
22113 bugfix on 0.2.4.8-alpha.
22116 - Reject as invalid most directory objects containing a NUL.
22117 Belt-and-suspender fix for bug 8037.
22118 - In our testsuite, create temporary directories with a bit more
22119 entropy in their name to make name collisions less likely. Fixes
22121 - Add CACHED keyword to ADDRMAP events in the control protocol
22122 to indicate whether a DNS result will be cached or not. Resolves
22124 - Update to the April 3 2013 Maxmind GeoLite Country database.
22126 o Minor features (build):
22127 - Detect and reject attempts to build Tor with threading support
22128 when OpenSSL has been compiled without threading support.
22130 - Clarify that when autoconf is checking for nacl, it is checking
22131 specifically for nacl with a fast curve25519 implementation.
22133 - Warn if building on a platform with an unsigned time_t: there
22134 are too many places where Tor currently assumes that time_t can
22135 hold negative values. We'd like to fix them all, but probably
22138 o Minor bugfixes (build):
22139 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
22140 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
22141 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
22142 - Add the old src/or/micro-revision.i filename to CLEANFILES.
22143 On the off chance that somebody has one, it will go away as soon
22144 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
22145 - Build Tor correctly on 32-bit platforms where the compiler can build
22146 but not run code using the "uint128_t" construction. Fixes bug 8587;
22147 bugfix on 0.2.4.8-alpha.
22148 - Fix compilation warning with some versions of clang that would
22149 prefer the -Wswitch-enum compiler flag to warn about switch
22150 statements with missing enum values, even if those switch
22151 statements have a "default:" statement. Fixes bug 8598; bugfix
22154 o Minor bugfixes (protocol):
22155 - Fix the handling of a TRUNCATE cell when it arrives while the
22156 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
22157 - Fix a misframing issue when reading the version numbers in a
22158 VERSIONS cell. Previously we would recognize [00 01 00 02] as
22159 'version 1, version 2, and version 0x100', when it should have
22160 only included versions 1 and 2. Fixes bug 8059; bugfix on
22161 0.2.0.10-alpha. Reported pseudonymously.
22162 - Make the format and order of STREAM events for DNS lookups
22163 consistent among the various ways to launch DNS lookups. Fixes
22164 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
22165 - Correct our check for which versions of Tor support the EXTEND2
22166 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
22167 later, when support was really added in version 0.2.4.8-alpha.
22168 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
22170 o Minor bugfixes (other):
22171 - Correctly store microdescriptors and extrainfo descriptors with
22172 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
22173 Bug reported by "cypherpunks".
22174 - Increase the width of the field used to remember a connection's
22175 link protocol version to two bytes. Harmless for now, since the
22176 only currently recognized versions are one byte long. Reported
22177 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
22178 - If the state file's path bias counts are invalid (presumably from a
22179 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
22180 additional checks and log messages to the scaling of Path Bias
22181 counts, in case there still are remaining issues with scaling.
22182 Should help resolve bug 8235.
22183 - Eliminate several instances where we use "Nickname=ID" to refer to
22184 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
22185 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
22186 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
22188 o Minor bugfixes (syscalls):
22189 - Always check the return values of functions fcntl() and
22190 setsockopt(). We don't believe these are ever actually failing in
22191 practice, but better safe than sorry. Also, checking these return
22192 values should please analysis tools like Coverity. Patch from
22193 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
22194 - Use direct writes rather than stdio when building microdescriptor
22195 caches, in an attempt to mitigate bug 8031, or at least make it
22198 o Minor bugfixes (config):
22199 - When rejecting a configuration because we were unable to parse a
22200 quoted string, log an actual error message. Fixes bug 7950; bugfix
22202 - Behave correctly when the user disables LearnCircuitBuildTimeout
22203 but doesn't tell us what they would like the timeout to be. Fixes
22204 bug 6304; bugfix on 0.2.2.14-alpha.
22205 - When autodetecting the number of CPUs, use the number of available
22206 CPUs in preference to the number of configured CPUs. Inform the
22207 user if this reduces the number of available CPUs. Fixes bug 8002;
22208 bugfix on 0.2.3.1-alpha.
22209 - Make it an error when you set EntryNodes but disable UseGuardNodes,
22210 since it will (surprisingly to some users) ignore EntryNodes. Fixes
22211 bug 8180; bugfix on 0.2.3.11-alpha.
22212 - Allow TestingTorNetworks to override the 4096-byte minimum for
22213 the Fast threshold. Otherwise they can't bootstrap until they've
22214 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
22215 - Fix some logic errors when the user manually overrides the
22216 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
22219 o Minor bugfixes (log messages to help diagnose bugs):
22220 - If we fail to free a microdescriptor because of bug 7164, log
22221 the filename and line number from which we tried to free it.
22222 - Add another diagnostic to the heartbeat message: track and log
22223 overhead that TLS is adding to the data we write. If this is
22224 high, we are sending too little data to SSL_write at a time.
22225 Diagnostic for bug 7707.
22226 - Add more detail to a log message about relaxed timeouts, to help
22228 - Warn more aggressively when flushing microdescriptors to a
22229 microdescriptor cache fails, in an attempt to mitigate bug 8031,
22230 or at least make it more diagnosable.
22231 - Improve debugging output to help track down bug 8185 ("Bug:
22232 outgoing relay cell has n_chan==NULL. Dropping.")
22233 - Log the purpose of a path-bias testing circuit correctly.
22234 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
22236 o Minor bugfixes (0.2.4.x log messages that were too noisy):
22237 - Don't attempt to relax the timeout of already opened 1-hop circuits.
22238 They might never timeout. This should eliminate some/all cases of
22239 the relaxed timeout log message.
22240 - Use circuit creation time for network liveness evaluation. This
22241 should eliminate warning log messages about liveness caused
22242 by changes in timeout evaluation. Fixes bug 6572; bugfix on
22244 - Reduce a path bias length check from notice to info. The message
22245 is triggered when creating controller circuits. Fixes bug 8196;
22246 bugfix on 0.2.4.8-alpha.
22247 - Fix a path state issue that triggered a notice during relay startup.
22248 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
22249 - Reduce occurrences of warns about circuit purpose in
22250 connection_ap_expire_building(). Fixes bug 8477; bugfix on
22253 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
22254 - If we encounter a write failure on a SOCKS connection before we
22255 finish our SOCKS handshake, don't warn that we closed the
22256 connection before we could send a SOCKS reply. Fixes bug 8427;
22257 bugfix on 0.1.0.1-rc.
22258 - Correctly recognize that [::1] is a loopback address. Fixes
22259 bug 8377; bugfix on 0.2.1.3-alpha.
22260 - Fix a directory authority warn caused when we have a large amount
22261 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
22262 - Don't log inappropriate heartbeat messages when hibernating: a
22263 hibernating node is _expected_ to drop out of the consensus,
22264 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
22265 bugfix on 0.2.3.1-alpha.
22266 - Don't complain about bootstrapping problems while hibernating.
22267 These complaints reflect a general code problem, but not one
22268 with any problematic effects (no connections are actually
22269 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
22271 o Documentation fixes:
22272 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
22273 names match. Fixes bug 7768.
22274 - Make the torify manpage no longer refer to tsocks; torify hasn't
22275 supported tsocks since 0.2.3.14-alpha.
22276 - Make the tor manpage no longer reference tsocks.
22277 - Fix the GeoIPExcludeUnknown documentation to refer to
22278 ExcludeExitNodes rather than the currently nonexistent
22279 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
22282 - The tor-tsocks.conf is no longer distributed or installed. We
22283 recommend that tsocks users use torsocks instead. Resolves
22287 Changes in version 0.2.4.11-alpha - 2013-03-11
22288 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
22289 more robust, makes hidden service authentication work again, and
22290 resolves a DPI fingerprint for Tor's SSL transport.
22292 o Major features (directory authorities):
22293 - Directory authorities now support a new consensus method (17)
22294 where they cap the published bandwidth of servers for which
22295 insufficient bandwidth measurements exist. Fixes part of bug 2286.
22296 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
22297 serve any v2 directory information. Now we can test disabling the
22298 old deprecated v2 directory format, and see whether doing so has
22299 any effect on network load. Begins to fix bug 6783.
22300 - Directory authorities now include inside each vote a statement of
22301 the performance thresholds they used when assigning flags.
22302 Implements ticket 8151.
22304 o Major bugfixes (directory authorities):
22305 - Stop marking every relay as having been down for one hour every
22306 time we restart a directory authority. These artificial downtimes
22307 were messing with our Stable and Guard flag calculations. Fixes
22308 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
22310 o Major bugfixes (hidden services):
22311 - Allow hidden service authentication to succeed again. When we
22312 refactored the hidden service introduction code back
22313 in 0.2.4.1-alpha, we didn't update the code that checks
22314 whether authentication information is present, causing all
22315 authentication checks to return "false". Fix for bug 8207; bugfix
22316 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
22318 o Minor features (relays, bridges):
22319 - Make bridge relays check once a minute for whether their IP
22320 address has changed, rather than only every 15 minutes. Resolves
22321 bugs 1913 and 1992.
22322 - Refactor resolve_my_address() so it returns the method by which we
22323 decided our public IP address (explicitly configured, resolved from
22324 explicit hostname, guessed from interfaces, learned by gethostname).
22325 Now we can provide more helpful log messages when a relay guesses
22326 its IP address incorrectly (e.g. due to unexpected lines in
22327 /etc/hosts). Resolves ticket 2267.
22328 - Teach bridge-using clients to avoid 0.2.2 bridges when making
22329 microdescriptor-related dir requests, and only fall back to normal
22330 descriptors if none of their bridges can handle microdescriptors
22331 (as opposed to the fix in ticket 4013, which caused them to fall
22332 back to normal descriptors if *any* of their bridges preferred
22333 them). Resolves ticket 4994.
22334 - Randomize the lifetime of our SSL link certificate, so censors can't
22335 use the static value for filtering Tor flows. Resolves ticket 8443;
22336 related to ticket 4014 which was included in 0.2.2.33.
22337 - Support a new version of the link protocol that allows 4-byte circuit
22338 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
22339 a possible resource exhaustion issue. Closes ticket 7351; implements
22342 o Minor features (portability):
22343 - Tweak the curve25519-donna*.c implementations to tolerate systems
22344 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
22345 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
22346 the signs of types during autoconf. This is better than our old
22347 approach, which didn't work when cross-compiling.
22348 - Detect the sign of enum values, rather than assuming that MSC is the
22349 only compiler where enum types are all signed. Fixes bug 7727;
22350 bugfix on 0.2.4.10-alpha.
22352 o Minor features (other):
22353 - Say "KBytes" rather than "KB" in the man page (for various values
22354 of K), to further reduce confusion about whether Tor counts in
22355 units of memory or fractions of units of memory. Resolves ticket 7054.
22356 - Clear the high bit on curve25519 public keys before passing them to
22357 our backend, in case we ever wind up using a backend that doesn't do
22358 so itself. If we used such a backend, and *didn't* clear the high bit,
22359 we could wind up in a situation where users with such backends would
22360 be distinguishable from users without. Fixes bug 8121; bugfix on
22362 - Update to the March 6 2013 Maxmind GeoLite Country database.
22364 o Minor bugfixes (clients):
22365 - When we receive a RELAY_END cell with the reason DONE, or with no
22366 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
22367 status as "connection refused". Previously we reported these cases
22368 as success but then immediately closed the connection. Fixes bug
22369 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
22370 - Downgrade an assertion in connection_ap_expire_beginning to an
22371 LD_BUG message. The fix for bug 8024 should prevent this message
22372 from displaying, but just in case, a warn that we can diagnose
22373 is better than more assert crashes. Fixes bug 8065; bugfix on
22375 - Lower path use bias thresholds to .80 for notice and .60 for warn.
22376 Also make the rate limiting flags for the path use bias log messages
22377 independent from the original path bias flags. Fixes bug 8161;
22378 bugfix on 0.2.4.10-alpha.
22380 o Minor bugfixes (relays):
22381 - Stop trying to resolve our hostname so often (e.g. every time we
22382 think about doing a directory fetch). Now we reuse the cached
22383 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
22384 and 2410 (bugfix on 0.1.2.2-alpha).
22385 - Stop sending a stray "(null)" in some cases for the server status
22386 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
22388 - When choosing which stream on a formerly stalled circuit to wake
22389 first, make better use of the platform's weak RNG. Previously,
22390 we had been using the % ("modulo") operator to try to generate a
22391 1/N chance of picking each stream, but this behaves badly with
22392 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
22394 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
22395 Irix's random() only return 15 bits; Solaris's random() returns more
22396 bits but its RAND_MAX says it only returns 15, and so on. Motivated
22397 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
22399 o Minor bugfixes (directory authorities):
22400 - Directory authorities now use less space when formatting identical
22401 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
22404 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
22405 - Avoid leaking memory if we fail to compute a consensus signature
22406 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
22407 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
22409 - Fix a memory leak during safe-cookie controller authentication.
22410 Bugfix on 0.2.3.13-alpha.
22411 - Avoid memory leak of IPv6 policy content if we fail to format it into
22412 a router descriptor. Bugfix on 0.2.4.7-alpha.
22414 o Minor bugfixes (other code correctness issues):
22415 - Avoid a crash if we fail to generate an extrainfo descriptor.
22416 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
22417 this is CID 718634.
22418 - When detecting the largest possible file descriptor (in order to
22419 close all file descriptors when launching a new program), actually
22420 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
22421 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
22423 - Fix a copy-and-paste error when adding a missing A1 to a routerset
22424 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
22425 Bugfix on 0.2.4.10-alpha.
22426 - Fix an impossible-to-trigger integer overflow when estimating how
22427 long our onionskin queue would take. (This overflow would require us
22428 to accept 4 million onionskins before processing 100 of them.) Fixes
22429 bug 8210; bugfix on 0.2.4.10-alpha.
22431 o Code simplification and refactoring:
22432 - Add a wrapper function for the common "log a message with a
22436 Changes in version 0.2.4.10-alpha - 2013-02-04
22437 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
22438 certain attacks that flood the network with relays; changes the queue
22439 for circuit create requests from a sized-based limit to a time-based
22440 limit; resumes building with MSVC on Windows; and fixes a wide variety
22443 o Major bugfixes (directory authority):
22444 - When computing directory thresholds, ignore any rejected-as-sybil
22445 nodes during the computation so that they can't influence Fast,
22446 Guard, etc. (We should have done this for proposal 109.) Fixes
22448 - When marking a node as a likely sybil, reset its uptime metrics
22449 to zero, so that it cannot time towards getting marked as Guard,
22450 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
22454 - When a TLS write is partially successful but incomplete, remember
22455 that the flushed part has been flushed, and notice that bytes were
22456 actually written. Reported and fixed pseudonymously. Fixes bug
22457 7708; bugfix on Tor 0.1.0.5-rc.
22458 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
22459 ID: these could be used to create unexpected streams and circuits
22460 which would count as "present" to some parts of Tor but "absent"
22461 to others, leading to zombie circuits and streams or to a bandwidth
22462 denial-of-service. Fixes bug 7889; bugfix on every released version
22463 of Tor. Reported by "oftc_must_be_destroyed".
22464 - Rename all macros in our local copy of queue.h to begin with "TOR_".
22465 This change seems the only good way to permanently prevent conflicts
22466 with queue.h on various operating systems. Fixes bug 8107; bugfix
22469 o Major features (relay):
22470 - Instead of limiting the number of queued onionskins (aka circuit
22471 create requests) to a fixed, hard-to-configure number, we limit
22472 the size of the queue based on how many we expect to be able to
22473 process in a given amount of time. We estimate the time it will
22474 take to process an onionskin based on average processing time
22475 of previous onionskins. Closes ticket 7291. You'll never have to
22476 configure MaxOnionsPending again.
22478 o Major features (portability):
22479 - Resume building correctly with MSVC and Makefile.nmake. This patch
22480 resolves numerous bugs and fixes reported by ultramage, including
22481 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
22482 - Make the ntor and curve25519 code build correctly with MSVC.
22483 Fix on 0.2.4.8-alpha.
22486 - When directory authorities are computing thresholds for flags,
22487 never let the threshold for the Fast flag fall below 4096
22488 bytes. Also, do not consider nodes with extremely low bandwidths
22489 when deciding thresholds for various directory flags. This change
22490 should raise our threshold for Fast relays, possibly in turn
22491 improving overall network performance; see ticket 1854. Resolves
22493 - The Tor client now ignores sub-domain components of a .onion
22494 address. This change makes HTTP "virtual" hosting
22495 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
22496 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
22497 hosted on the same hidden service. Implements proposal 204.
22498 - We compute the overhead from passing onionskins back and forth to
22499 cpuworkers, and report it when dumping statistics in response to
22500 SIGUSR1. Supports ticket 7291.
22502 o Minor features (path selection):
22503 - When deciding whether we have enough descriptors to build circuits,
22504 instead of looking at raw relay counts, look at which fraction
22505 of (bandwidth-weighted) paths we're able to build. This approach
22506 keeps clients from building circuits if their paths are likely to
22507 stand out statistically. The default fraction of paths needed is
22508 taken from the consensus directory; you can override it with the
22509 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
22510 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
22511 and we have GeoIP information, also exclude all nodes with unknown
22512 countries "??" and "A1". This behavior is controlled by the
22513 new GeoIPExcludeUnknown option: you can make such nodes always
22514 excluded with "GeoIPExcludeUnknown 1", and disable the feature
22515 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
22516 gets you the default behavior. Implements feature 7706.
22517 - Path Use Bias: Perform separate accounting for successful circuit
22518 use. Keep separate statistics on stream attempt rates versus stream
22519 success rates for each guard. Provide configurable thresholds to
22520 determine when to emit log messages or disable use of guards that
22521 fail too many stream attempts. Resolves ticket 7802.
22523 o Minor features (log messages):
22524 - When learning a fingerprint for a bridge, log its corresponding
22525 transport type. Implements ticket 7896.
22526 - Improve the log message when "Bug/attack: unexpected sendme cell
22527 from client" occurs, to help us track bug 8093.
22530 - Remove a couple of extraneous semicolons that were upsetting the
22531 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
22532 bugfix on 0.2.2.1-alpha.
22533 - Remove a source of rounding error during path bias count scaling;
22534 don't count cannibalized circuits as used for path bias until we
22535 actually try to use them; and fix a circuit_package_relay_cell()
22536 warning message about n_chan==NULL. Fixes bug 7802.
22537 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
22538 actually link against nacl when we're configured to use it. Fixes
22539 bug 7972; bugfix on 0.2.4.8-alpha.
22540 - Compile correctly with the --disable-curve25519 option. Fixes
22541 bug 8153; bugfix on 0.2.4.8-alpha.
22543 o Build improvements:
22544 - Do not report status verbosely from autogen.sh unless the -v flag
22545 is specified. Fixes issue 4664. Patch from Onizuka.
22546 - Replace all calls to snprintf() outside of src/ext with
22547 tor_snprintf(). Also remove the #define to replace snprintf with
22548 _snprintf on Windows; they have different semantics, and all of
22549 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
22550 - Try to detect if we are ever building on a platform where
22551 memset(...,0,...) does not set the value of a double to 0.0. Such
22552 platforms are permitted by the C standard, though in practice
22553 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
22554 currently support them, but it's better to detect them and fail
22555 than to perform erroneously.
22557 o Removed features:
22558 - Stop exporting estimates of v2 and v3 directory traffic shares
22559 in extrainfo documents. They were unneeded and sometimes inaccurate.
22560 Also stop exporting any v2 directory request statistics. Resolves
22562 - Drop support for detecting and warning about versions of Libevent
22563 before 1.3e. Nothing reasonable ships with them any longer;
22564 warning the user about them shouldn't be needed. Resolves ticket
22567 o Code simplifications and refactoring:
22568 - Rename "isin" functions to "contains", for grammar. Resolves
22570 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
22571 with the natural logarithm function from the system libm. Resolves
22575 Changes in version 0.2.4.9-alpha - 2013-01-15
22576 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
22577 work more robustly.
22580 - Fix backward compatibility logic when receiving an embedded ntor
22581 handshake tunneled in a CREATE cell. This clears up the "Bug:
22582 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
22586 Changes in version 0.2.4.8-alpha - 2013-01-14
22587 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
22588 risks, adds a new stronger and faster circuit handshake, and offers
22589 stronger and faster link encryption when both sides support it.
22592 - Preliminary support for directory guards (proposal 207): when
22593 possible, clients now use their entry guards for non-anonymous
22594 directory requests. This can help prevent client enumeration. Note
22595 that this behavior only works when we have a usable consensus
22596 directory, and when options about what to download are more or less
22597 standard. In the future we should re-bootstrap from our guards,
22598 rather than re-bootstrapping from the preconfigured list of
22599 directory sources that ships with Tor. Resolves ticket 6526.
22600 - Tor relays and clients now support a better CREATE/EXTEND cell
22601 format, allowing the sender to specify multiple address, identity,
22602 and handshake types. Implements Robert Ransom's proposal 200;
22603 closes ticket 7199.
22605 o Major features (new circuit handshake):
22606 - Tor now supports a new circuit extension handshake designed by Ian
22607 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
22608 circuit extension handshake, later called "TAP", was a bit slow
22609 (especially on the relay side), had a fragile security proof, and
22610 used weaker keys than we'd now prefer. The new circuit handshake
22611 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
22612 function, making it significantly more secure than the older
22613 handshake, and significantly faster. Tor can use one of two built-in
22614 pure-C curve25519-donna implementations by Adam Langley, or it
22615 can link against the "nacl" library for a tuned version if present.
22617 The built-in version is very fast for 64-bit systems when building
22618 with GCC. The built-in 32-bit version is still faster than the
22619 old TAP protocol, but using libnacl is better on most such hosts.
22621 Clients don't currently use this protocol by default, since
22622 comparatively few clients support it so far. To try it, set
22623 UseNTorHandshake to 1.
22625 Implements proposal 216; closes ticket 7202.
22627 o Major features (better link encryption):
22628 - Relays can now enable the ECDHE TLS ciphersuites when available
22629 and appropriate. These ciphersuites let us negotiate forward-secure
22630 TLS secret keys more safely and more efficiently than with our
22631 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
22632 public relays prefer the (faster) P224 group, and bridges prefer
22633 the (more common) P256 group; you can override this with the
22636 Enabling these ciphers was a little tricky, since for a long time,
22637 clients had been claiming to support them without actually doing
22638 so, in order to foil fingerprinting. But with the client-side
22639 implementation of proposal 198 in 0.2.3.17-beta, clients can now
22640 match the ciphers from recent Firefox versions *and* list the
22641 ciphers they actually mean, so relays can believe such clients
22642 when they advertise ECDHE support in their TLS ClientHello messages.
22644 This feature requires clients running 0.2.3.17-beta or later,
22645 and requires both sides to be running OpenSSL 1.0.0 or later
22646 with ECC support. OpenSSL 1.0.1, with the compile-time option
22647 "enable-ec_nistp_64_gcc_128", is highly recommended.
22649 Implements the relay side of proposal 198; closes ticket 7200.
22652 - Avoid crashing when, as a relay without IPv6-exit support, a
22653 client insists on getting an IPv6 address or nothing. Fixes bug
22654 7814; bugfix on 0.2.4.7-alpha.
22657 - Improve circuit build timeout handling for hidden services.
22658 In particular: adjust build timeouts more accurately depending
22659 upon the number of hop-RTTs that a particular circuit type
22660 undergoes. Additionally, launch intro circuits in parallel
22661 if they timeout, and take the first one to reply as valid.
22662 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
22663 separate error codes; or at least, don't break for that reason.
22664 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
22665 - Update to the January 2 2013 Maxmind GeoLite Country database.
22667 o Minor features (testing):
22668 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
22669 (P-256) Diffie-Hellman handshakes to src/or/bench.
22670 - Add benchmark functions to test onion handshake performance.
22672 o Minor features (path bias detection):
22673 - Alter the Path Bias log messages to be more descriptive in terms
22674 of reporting timeouts and other statistics.
22675 - Create three levels of Path Bias log messages, as opposed to just
22676 two. These are configurable via consensus as well as via the torrc
22677 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
22678 The default values are 0.70, 0.50, and 0.30 respectively.
22679 - Separate the log message levels from the decision to drop guards,
22680 which also is available via torrc option PathBiasDropGuards.
22681 PathBiasDropGuards still defaults to 0 (off).
22682 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
22683 in combination with PathBiasExtremeRate.
22684 - Increase the default values for PathBiasScaleThreshold and
22685 PathBiasCircThreshold from (200, 20) to (300, 150).
22686 - Add in circuit usage accounting to path bias. If we try to use a
22687 built circuit but fail for any reason, it counts as path bias.
22688 Certain classes of circuits where the adversary gets to pick your
22689 destination node are exempt from this accounting. Usage accounting
22690 can be specifically disabled via consensus parameter or torrc.
22691 - Convert all internal path bias state to double-precision floating
22692 point, to avoid roundoff error and other issues.
22693 - Only record path bias information for circuits that have completed
22694 *two* hops. Assuming end-to-end tagging is the attack vector, this
22695 makes us more resilient to ambient circuit failure without any
22696 detection capability loss.
22698 o Minor bugfixes (log messages):
22699 - Rate-limit the "No circuits are opened. Relaxed timeout for a
22700 circuit with channel state open..." message to once per hour to
22701 keep it from filling the notice logs. Mitigates bug 7799 but does
22702 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
22703 - Avoid spurious warnings when configuring multiple client ports of
22704 which only some are nonlocal. Previously, we had claimed that some
22705 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
22708 o Code simplifications and refactoring:
22709 - Get rid of a couple of harmless clang warnings, where we compared
22710 enums to ints. These warnings are newly introduced in clang 3.2.
22711 - Split the onion.c file into separate modules for the onion queue
22712 and the different handshakes it supports.
22713 - Remove the marshalling/unmarshalling code for sending requests to
22714 cpuworkers over a socket, and instead just send structs. The
22715 recipient will always be the same Tor binary as the sender, so
22716 any encoding is overkill.
22719 Changes in version 0.2.4.7-alpha - 2012-12-24
22720 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
22721 directory mirrors for more robust bootstrapping; fixes more issues where
22722 clients with changing network conditions refuse to make any circuits;
22723 adds initial support for exiting to IPv6 addresses; resumes being able
22724 to update our GeoIP database, and includes the geoip6 file this time;
22725 turns off the client-side DNS cache by default due to privacy risks;
22726 and fixes a variety of other issues.
22728 o Major features (client resilience):
22729 - Add a new "FallbackDir" torrc option to use when we can't use
22730 a directory mirror from the consensus (either because we lack a
22731 consensus, or because they're all down). Currently, all authorities
22732 are fallbacks by default, and there are no other default fallbacks,
22733 but that will change. This option will allow us to give clients a
22734 longer list of servers to try to get a consensus from when first
22735 connecting to the Tor network, and thereby reduce load on the
22736 directory authorities. Implements proposal 206, "Preconfigured
22737 directory sources for bootstrapping". We also removed the old
22738 "FallbackNetworkstatus" option, since we never got it working well
22739 enough to use it. Closes bug 572.
22740 - If we have no circuits open, use a relaxed timeout (the
22741 95-percentile cutoff) until a circuit succeeds. This heuristic
22742 should allow Tor to succeed at building circuits even when the
22743 network connection drastically changes. Should help with bug 3443.
22745 o Major features (IPv6):
22746 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
22747 connectivity, then set the IPv6Exit flag to 1. Also make sure your
22748 exit policy reads as you would like: the address * applies to all
22749 address families, whereas *4 is IPv4 address only, and *6 is IPv6
22750 addresses only. On the client side, you'll need to wait until the
22751 authorities have upgraded, wait for enough exits to support IPv6,
22752 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
22753 ticket 5547, implements proposal 117 as revised in proposal 208.
22755 We DO NOT recommend that clients with actual anonymity needs start
22756 using IPv6 over Tor yet, since not enough exits support it yet.
22758 o Major features (geoip database):
22759 - Maxmind began labelling Tor relays as being in country "A1",
22760 which breaks by-country node selection inside Tor. Now we use a
22761 script to replace "A1" ("Anonymous Proxy") entries in our geoip
22762 file with real country codes. This script fixes about 90% of "A1"
22763 entries automatically and uses manual country code assignments to
22764 fix the remaining 10%. See src/config/README.geoip for details.
22765 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
22766 Country database, as modified above.
22768 o Major bugfixes (client-side DNS):
22769 - Turn off the client-side DNS cache by default. Updating and using
22770 the DNS cache is now configurable on a per-client-port
22771 level. SOCKSPort, DNSPort, etc lines may now contain
22772 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
22773 cache these types of DNS answers when we receive them from an
22774 exit node in response to an application request on this port, and
22775 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
22776 cached DNS answers of these types, we shouldn't use them. It's
22777 potentially risky to use cached DNS answers at the client, since
22778 doing so can indicate to one exit what answers we've gotten
22779 for DNS lookups in the past. With IPv6, this becomes especially
22780 problematic. Using cached DNS answers for requests on the same
22781 circuit would present less linkability risk, since all traffic
22782 on a circuit is already linkable, but it would also provide
22783 little performance benefit: the exit node caches DNS replies
22784 too. Implements a simplified version of Proposal 205. Implements
22787 o Major bugfixes (other):
22788 - Alter circuit build timeout measurement to start at the point
22789 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
22790 initialization). This should make our timeout measurements more
22791 uniform. Previously, we were sometimes including ORconn setup time
22792 in our circuit build time measurements. Should resolve bug 3443.
22793 - Fix an assertion that could trigger in hibernate_go_dormant() when
22794 closing an or_connection_t: call channel_mark_for_close() rather
22795 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
22797 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
22798 7655; bugfix on 0.2.4.6-alpha.
22801 - Add a new torrc option "ServerTransportListenAddr" to let bridge
22802 operators select the address where their pluggable transports will
22803 listen for connections. Resolves ticket 7013.
22804 - Allow an optional $ before the node identity digest in the
22805 controller command GETINFO ns/id/<identity>, for consistency with
22806 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
22807 - Log packaged cell fullness as part of the heartbeat message.
22808 Diagnosis to try to determine the extent of bug 7743.
22810 o Minor features (IPv6):
22811 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
22812 prefer to hand out virtual IPv6 addresses, since there are more of
22813 them and we can't run out. To override this behavior and make IPv4
22814 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
22815 or DNSPort you're using for resolving. Implements ticket 7571.
22816 - AutomapHostsOnResolve responses are now randomized, to avoid
22817 annoying situations where Tor is restarted and applications
22818 connect to the wrong addresses.
22819 - Never try more than 1000 times to pick a new virtual address when
22820 AutomapHostsOnResolve is set. That's good enough so long as we
22821 aren't close to handing out our entire virtual address space;
22822 if you're getting there, it's best to switch to IPv6 virtual
22826 - The ADDRMAP command can no longer generate an ill-formed error
22827 code on a failed MAPADDRESS. It now says "internal" rather than
22828 an English sentence fragment with spaces in the middle. Bugfix on
22829 Tor 0.2.0.19-alpha.
22830 - Fix log messages and comments to avoid saying "GMT" when we mean
22831 "UTC". Fixes bug 6113.
22832 - Compile on win64 using mingw64. Fixes bug 7260; patches from
22834 - Fix a crash when debugging unit tests on Windows: deallocate a
22835 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
22836 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
22839 - The DirServer option is now DirAuthority, for consistency with
22840 current naming patterns. You can still use the old DirServer form.
22842 o Code simplification and refactoring:
22843 - Move the client-side address-map/virtual-address/DNS-cache code
22844 out of connection_edge.c into a new addressmap.c module.
22845 - Remove unused code for parsing v1 directories and "running routers"
22846 documents. Fixes bug 6887.
22849 Changes in version 0.2.3.25 - 2012-11-19
22850 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
22851 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
22852 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
22853 programmer, and friend. Unstinting in his dedication to the cause of
22854 freedom, he inspired and helped many of us as we began our work on
22855 anonymity, and inspires us still. Please honor his memory by writing
22856 software to protect people's freedoms, and by helping others to do so.
22858 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
22859 significantly reduced directory overhead (via microdescriptors),
22860 enormous crypto performance improvements for fast relays on new
22861 enough hardware, a new v3 TLS handshake protocol that can better
22862 resist fingerprinting, support for protocol obfuscation plugins (aka
22863 pluggable transports), better scalability for hidden services, IPv6
22864 support for bridges, performance improvements like allowing clients
22865 to skip the first round-trip on the circuit ("optimistic data") and
22866 refilling token buckets more often, a new "stream isolation" design
22867 to isolate different applications on different circuits, and many
22868 stability, security, and privacy fixes.
22871 - Tor tries to wipe potentially sensitive data after using it, so
22872 that if some subsequent security failure exposes Tor's memory,
22873 the damage will be limited. But we had a bug where the compiler
22874 was eliminating these wipe operations when it decided that the
22875 memory was no longer visible to a (correctly running) program,
22876 hence defeating our attempt at defense in depth. We fix that
22877 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
22878 is unlikely to optimize away. Future versions of Tor may use
22879 a less ridiculously heavy approach for this. Fixes bug 7352.
22880 Reported in an article by Andrey Karpov.
22883 - Fix a harmless bug when opting against publishing a relay descriptor
22884 because DisableNetwork is set. Fixes bug 7464; bugfix on
22888 Changes in version 0.2.4.6-alpha - 2012-11-13
22889 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
22890 makes our defense-in-depth memory wiping more reliable, and begins to
22891 count IPv6 addresses in bridge statistics,
22894 - Fix an assertion failure that could occur when closing a connection
22895 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
22897 - Tor tries to wipe potentially sensitive data after using it, so
22898 that if some subsequent security failure exposes Tor's memory,
22899 the damage will be limited. But we had a bug where the compiler
22900 was eliminating these wipe operations when it decided that the
22901 memory was no longer visible to a (correctly running) program,
22902 hence defeating our attempt at defense in depth. We fix that
22903 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
22904 is unlikely to optimize away. Future versions of Tor may use
22905 a less ridiculously heavy approach for this. Fixes bug 7352.
22906 Reported in an article by Andrey Karpov.
22909 - Add GeoIP database for IPv6 addresses. The new config option
22911 - Bridge statistics now count bridge clients connecting over IPv6:
22912 bridge statistics files now list "bridge-ip-versions" and
22913 extra-info documents list "geoip6-db-digest". The control protocol
22914 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
22915 implementation by "shkoo", addressing ticket 5055.
22918 - Warn when we are binding low ports when hibernation is enabled;
22919 previously we had warned when we were _advertising_ low ports with
22920 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
22921 - Fix a harmless bug when opting against publishing a relay descriptor
22922 because DisableNetwork is set. Fixes bug 7464; bugfix on
22924 - Add warning message when a managed proxy dies during configuration.
22925 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
22926 - Fix a linking error when building tor-fw-helper without miniupnp.
22927 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
22928 - Check for closing an or_connection_t without going through correct
22929 channel functions; emit a warning and then call
22930 connection_or_close_for_error() so we don't assert as in bugs 7212
22932 - Compile correctly on compilers without C99 designated initializer
22933 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
22934 - Avoid a possible assert that can occur when channel_send_destroy() is
22935 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
22936 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
22937 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
22938 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
22939 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
22941 o Code simplification and refactoring:
22942 - Start using OpenBSD's implementation of queue.h, so that we don't
22943 need to hand-roll our own pointer and list structures whenever we
22944 need them. (We can't rely on a sys/queue.h, since some operating
22945 systems don't have them, and the ones that do have them don't all
22946 present the same extensions.)
22949 Changes in version 0.2.4.5-alpha - 2012-10-25
22950 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
22951 two important security vulnerabilities that could lead to remotely
22952 triggerable relay crashes, fix a major bug that was preventing clients
22953 from choosing suitable exit nodes, and refactor some of our code.
22955 o Major bugfixes (security, also in 0.2.3.24-rc):
22956 - Fix a group of remotely triggerable assertion failures related to
22957 incorrect link protocol negotiation. Found, diagnosed, and fixed
22958 by "some guy from France". Fix for CVE-2012-2250; bugfix on
22960 - Fix a denial of service attack by which any directory authority
22961 could crash all the others, or by which a single v2 directory
22962 authority could crash everybody downloading v2 directory
22963 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
22965 o Major bugfixes (also in 0.2.3.24-rc):
22966 - When parsing exit policy summaries from microdescriptors, we had
22967 previously been ignoring the last character in each one, so that
22968 "accept 80,443,8080" would be treated by clients as indicating
22969 a node that allows access to ports 80, 443, and 808. That would
22970 lead to clients attempting connections that could never work,
22971 and ignoring exit nodes that would support their connections. Now
22972 clients parse these exit policy summaries correctly. Fixes bug 7192;
22973 bugfix on 0.2.3.1-alpha.
22975 o Minor bugfixes (also in 0.2.3.24-rc):
22976 - Clients now consider the ClientRejectInternalAddresses config option
22977 when using a microdescriptor consensus stanza to decide whether
22978 an exit relay would allow exiting to an internal address. Fixes
22979 bug 7190; bugfix on 0.2.3.1-alpha.
22982 - Only disable TLS session ticket support when running as a TLS
22983 server. Now clients will blend better with regular Firefox
22984 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
22986 o Code simplification and refactoring:
22987 - Start using OpenBSD's implementation of queue.h (originally by
22989 - Move the entry node code from circuitbuild.c to its own file.
22990 - Move the circuit build timeout tracking code from circuitbuild.c
22994 Changes in version 0.2.3.24-rc - 2012-10-25
22995 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
22996 could lead to remotely triggerable relay crashes, and fixes
22997 a major bug that was preventing clients from choosing suitable exit
23000 o Major bugfixes (security):
23001 - Fix a group of remotely triggerable assertion failures related to
23002 incorrect link protocol negotiation. Found, diagnosed, and fixed
23003 by "some guy from France". Fix for CVE-2012-2250; bugfix on
23005 - Fix a denial of service attack by which any directory authority
23006 could crash all the others, or by which a single v2 directory
23007 authority could crash everybody downloading v2 directory
23008 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
23011 - When parsing exit policy summaries from microdescriptors, we had
23012 previously been ignoring the last character in each one, so that
23013 "accept 80,443,8080" would be treated by clients as indicating
23014 a node that allows access to ports 80, 443, and 808. That would
23015 lead to clients attempting connections that could never work,
23016 and ignoring exit nodes that would support their connections. Now
23017 clients parse these exit policy summaries correctly. Fixes bug 7192;
23018 bugfix on 0.2.3.1-alpha.
23021 - Clients now consider the ClientRejectInternalAddresses config option
23022 when using a microdescriptor consensus stanza to decide whether
23023 an exit relay would allow exiting to an internal address. Fixes
23024 bug 7190; bugfix on 0.2.3.1-alpha.
23027 Changes in version 0.2.4.4-alpha - 2012-10-20
23028 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
23029 vulnerability introduced by a change in OpenSSL, fixes a remotely
23030 triggerable assert, and adds new channel_t and circuitmux_t abstractions
23031 that will make it easier to test new connection transport and cell
23032 scheduling algorithms.
23034 o New directory authorities (also in 0.2.3.23-rc):
23035 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
23036 authority. Closes ticket 5749.
23038 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
23039 - Disable TLS session tickets. OpenSSL's implementation was giving
23040 our TLS session keys the lifetime of our TLS context objects, when
23041 perfect forward secrecy would want us to discard anything that
23042 could decrypt a link connection as soon as the link connection
23043 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
23044 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
23045 - Discard extraneous renegotiation attempts once the V3 link
23046 protocol has been initiated. Failure to do so left us open to
23047 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
23048 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
23050 o Internal abstraction features:
23051 - Introduce new channel_t abstraction between circuits and
23052 or_connection_t to allow for implementing alternate OR-to-OR
23053 transports. A channel_t is an abstract object which can either be a
23054 cell-bearing channel, which is responsible for authenticating and
23055 handshaking with the remote OR and transmitting cells to and from
23056 it, or a listening channel, which spawns new cell-bearing channels
23057 at the request of remote ORs. Implements part of ticket 6465.
23058 - Also new is the channel_tls_t subclass of channel_t, adapting it
23059 to the existing or_connection_t code. The V2/V3 protocol handshaking
23060 code which formerly resided in command.c has been moved below the
23061 channel_t abstraction layer and may be found in channeltls.c now.
23062 Implements the rest of ticket 6465.
23063 - Introduce new circuitmux_t storing the queue of circuits for
23064 a channel; this encapsulates and abstracts the queue logic and
23065 circuit selection policy, and allows the latter to be overridden
23066 easily by switching out a policy object. The existing EWMA behavior
23067 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
23069 o Required libraries:
23070 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
23071 strongly recommended.
23074 - Warn users who run hidden services on a Tor client with
23075 UseEntryGuards disabled that their hidden services will be
23076 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
23077 attack which motivated Tor to support entry guards in the first
23078 place). Resolves ticket 6889.
23079 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
23080 dhill. Resolves ticket 6982.
23081 - Option OutboundBindAddress can be specified multiple times and
23082 accepts IPv6 addresses. Resolves ticket 6876.
23084 o Minor bugfixes (also in 0.2.3.23-rc):
23085 - Don't serve or accept v2 hidden service descriptors over a
23086 relay's DirPort. It's never correct to do so, and disabling it
23087 might make it more annoying to exploit any bugs that turn up in the
23088 descriptor-parsing code. Fixes bug 7149.
23089 - Fix two cases in src/or/transports.c where we were calling
23090 fmt_addr() twice in a parameter list. Bug found by David
23091 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
23092 - Fix memory leaks whenever we logged any message about the "path
23093 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
23094 - When relays refuse a "create" cell because their queue of pending
23095 create cells is too big (typically because their cpu can't keep up
23096 with the arrival rate), send back reason "resource limit" rather
23097 than reason "internal", so network measurement scripts can get a
23098 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
23101 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
23102 - Free some more still-in-use memory at exit, to make hunting for
23103 memory leaks easier. Resolves bug 7029.
23104 - When a Tor client gets a "truncated" relay cell, the first byte of
23105 its payload specifies why the circuit was truncated. We were
23106 ignoring this 'reason' byte when tearing down the circuit, resulting
23107 in the controller not being told why the circuit closed. Now we
23108 pass the reason from the truncated cell to the controller. Bugfix
23109 on 0.1.2.3-alpha; fixes bug 7039.
23110 - Downgrade "Failed to hand off onionskin" messages to "debug"
23111 severity, since they're typically redundant with the "Your computer
23112 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
23113 - Make clients running with IPv6 bridges connect over IPv6 again,
23114 even without setting new config options ClientUseIPv6 and
23115 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
23116 - Use square brackets around IPv6 addresses in numerous places
23117 that needed them, including log messages, HTTPS CONNECT proxy
23118 requests, TransportProxy statefile entries, and pluggable transport
23119 extra-info lines. Fixes bug 7011; patch by David Fifield.
23121 o Code refactoring and cleanup:
23122 - Source files taken from other packages now reside in src/ext;
23123 previously they were scattered around the rest of Tor.
23124 - Avoid use of reserved identifiers in our C code. The C standard
23125 doesn't like us declaring anything that starts with an
23126 underscore, so let's knock it off before we get in trouble. Fix
23127 for bug 1031; bugfix on the first Tor commit.
23130 Changes in version 0.2.3.23-rc - 2012-10-20
23131 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
23132 vulnerability introduced by a change in OpenSSL, and fixes a variety
23133 of smaller bugs in preparation for the release.
23135 o New directory authorities:
23136 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
23137 authority. Closes ticket 5749.
23139 o Major bugfixes (security/privacy):
23140 - Disable TLS session tickets. OpenSSL's implementation was giving
23141 our TLS session keys the lifetime of our TLS context objects, when
23142 perfect forward secrecy would want us to discard anything that
23143 could decrypt a link connection as soon as the link connection
23144 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
23145 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
23146 - Discard extraneous renegotiation attempts once the V3 link
23147 protocol has been initiated. Failure to do so left us open to
23148 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
23149 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
23152 - Fix a possible crash bug when checking for deactivated circuits
23153 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
23154 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
23156 o Minor bugfixes (on 0.2.3.x):
23157 - Fix two cases in src/or/transports.c where we were calling
23158 fmt_addr() twice in a parameter list. Bug found by David
23159 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
23160 - Convert an assert in the pathbias code to a log message. The assert
23161 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
23162 bugfix on 0.2.3.17-beta.
23163 - Fix memory leaks whenever we logged any message about the "path
23164 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
23166 o Minor bugfixes (on 0.2.2.x and earlier):
23167 - Don't serve or accept v2 hidden service descriptors over a relay's
23168 DirPort. It's never correct to do so, and disabling it might
23169 make it more annoying to exploit any bugs that turn up in the
23170 descriptor-parsing code. Fixes bug 7149.
23171 - When relays refuse a "create" cell because their queue of pending
23172 create cells is too big (typically because their cpu can't keep up
23173 with the arrival rate), send back reason "resource limit" rather
23174 than reason "internal", so network measurement scripts can get a
23175 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
23176 - Correct file sizes when reading binary files on Cygwin, to avoid
23177 a bug where Tor would fail to read its state file. Fixes bug 6844;
23178 bugfix on 0.1.2.7-alpha.
23179 - Avoid undefined behavior when parsing the list of supported
23180 rendezvous/introduction protocols in a hidden service descriptor.
23181 Previously, Tor would have confused (as-yet-unused) protocol version
23182 numbers greater than 32 with lower ones on many platforms. Fixes
23183 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
23185 o Documentation fixes:
23186 - Clarify that hidden services are TCP only. Fixes bug 6024.
23189 Changes in version 0.2.4.3-alpha - 2012-09-22
23190 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
23191 assertion, resumes letting relays test reachability of their DirPort,
23192 and cleans up a bunch of smaller bugs.
23195 - Fix an assertion failure in tor_timegm() that could be triggered
23196 by a badly formatted directory object. Bug found by fuzzing with
23197 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
23200 - Fix a possible crash bug when checking for deactivated circuits
23201 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
23202 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
23203 - Allow routers to detect that their own DirPorts are running. When
23204 we removed support for versions_supports_begindir, we also
23205 accidentally removed the mechanism we used to self-test our
23206 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
23207 bugfix on 0.2.4.2-alpha.
23209 o Security features:
23210 - Switch to a completely time-invariant approach for picking nodes
23211 weighted by bandwidth. Our old approach would run through the
23212 part of the loop after it had made its choice slightly slower
23213 than it ran through the part of the loop before it had made its
23214 choice. Addresses ticket 6538.
23215 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
23216 by tor2web clients allows hidden services to identify tor2web
23217 clients through their repeated selection of the same rendezvous
23218 and introduction point circuit endpoints (their guards). Resolves
23222 - Enable Tor to read configuration, state, and key information from
23223 a FIFO. Previously Tor would only read from files with a positive
23224 stat.st_size. Code from meejah; fixes bug 6044.
23227 - Correct file sizes when reading binary files on Cygwin, to avoid
23228 a bug where Tor would fail to read its state file. Fixes bug 6844;
23229 bugfix on 0.1.2.7-alpha.
23230 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
23231 bugfix on 0.2.0.3-alpha.
23232 - When complaining about a client port on a public address, log
23233 which address we're complaining about. Fixes bug 4020; bugfix on
23234 0.2.3.3-alpha. Patch by Tom Fitzhenry.
23235 - Convert an assert in the pathbias code to a log message. The assert
23236 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
23237 bugfix on 0.2.3.17-beta.
23238 - Our new buildsystem was overzealous about rebuilding manpages: it
23239 would rebuild them all whenever any one of them changed. Now our
23240 dependency checking should be correct. Fixes bug 6843; bugfix on
23242 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
23243 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
23244 - Correct log printout about which address family is preferred
23245 when connecting to a bridge with both an IPv4 and IPv6 OR port.
23246 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
23248 o Minor bugfixes (code cleanliness):
23249 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
23250 with large values. This situation was untriggered, but nevertheless
23251 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
23252 - Reject consensus votes with more than 64 known-flags. We aren't even
23253 close to that limit yet, and our code doesn't handle it correctly.
23254 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
23255 - Avoid undefined behavior when parsing the list of supported
23256 rendezvous/introduction protocols in a hidden service descriptor.
23257 Previously, Tor would have confused (as-yet-unused) protocol version
23258 numbers greater than 32 with lower ones on many platforms. Fixes
23259 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
23260 - Fix handling of rendezvous client authorization types over 8.
23261 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
23262 - Fix building with older versions of GCC (2.95, for one) that don't
23263 like preprocessor directives inside macro arguments. Found by
23264 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
23265 - Switch weighted node selection rule from using a list of doubles
23266 to using a list of int64_t. This change should make the process
23267 slightly easier to debug and maintain. Needed to finish ticket 6538.
23269 o Code simplification and refactoring:
23270 - Move the generic "config" code into a new file, and have "config.c"
23271 hold only torrc- and state-related code. Resolves ticket 6823.
23272 - Move the core of our "choose a weighted element at random" logic
23273 into its own function, and give it unit tests. Now the logic is
23274 testable, and a little less fragile too.
23275 - Removed the testing_since field of node_t, which hasn't been used
23276 for anything since 0.2.0.9-alpha.
23278 o Documentation fixes:
23279 - Clarify that hidden services are TCP only. Fixes bug 6024.
23280 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
23284 Changes in version 0.2.3.22-rc - 2012-09-11
23285 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
23289 - Fix an assertion failure in tor_timegm() that could be triggered
23290 by a badly formatted directory object. Bug found by fuzzing with
23291 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
23294 - Avoid segfault when starting up having run with an extremely old
23295 version of Tor and parsing its state file. Fixes bug 6801; bugfix
23299 Changes in version 0.2.2.39 - 2012-09-11
23300 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
23304 - Fix an assertion failure in tor_timegm() that could be triggered
23305 by a badly formatted directory object. Bug found by fuzzing with
23306 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
23307 - Do not crash when comparing an address with port value 0 to an
23308 address policy. This bug could have been used to cause a remote
23309 assertion failure by or against directory authorities, or to
23310 allow some applications to crash clients. Fixes bug 6690; bugfix
23314 Changes in version 0.2.4.2-alpha - 2012-09-10
23315 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
23316 raises the default rate limiting even more, and makes the bootstrapping
23317 log messages less noisy.
23320 - Automatically forward the TCP ports of pluggable transport
23321 proxies using tor-fw-helper if PortForwarding is enabled. Implements
23325 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
23326 to 1GB/1GB. The previous defaults were intended to be "basically
23327 infinite", but it turns out they're now limiting our 100mbit+
23328 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
23329 last time we raised it).
23332 - Detect when we're running with a version of OpenSSL other than the
23333 one we compiled with. This has occasionally given people hard-to-
23335 - Log fewer lines at level "notice" about our OpenSSL and Libevent
23336 versions and capabilities when everything is going right. Resolves
23337 part of ticket 6736.
23338 - Directory authorities no long accept descriptors for any version of
23339 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
23340 These versions are insecure, unsupported, or both. Implements
23344 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
23345 to start with a triple-underscore so the controller won't touch it.
23346 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
23347 - Avoid segfault when starting up having run with an extremely old
23348 version of Tor and parsing its state file. Fixes bug 6801; bugfix
23350 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
23351 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
23352 - Don't follow the NULL pointer if microdescriptor generation fails.
23353 (This does not appear to be triggerable, but it's best to be safe.)
23354 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
23355 - Fix mis-declared dependencies on src/common/crypto.c and
23356 src/or/tor_main.c that could break out-of-tree builds under some
23357 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
23358 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
23359 6778; bugfix on 0.2.4.1-alpha.
23360 - Fix a harmless (in this case) build warning for implicitly
23361 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
23363 o Removed features:
23364 - Now that all versions before 0.2.2.x are disallowed, we no longer
23365 need to work around their missing features. Thus we can remove a
23366 bunch of compatibility code.
23368 o Code refactoring:
23369 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
23370 TCP ports to forward. In the past it only accepted two ports:
23371 the ORPort and the DirPort.
23374 Changes in version 0.2.4.1-alpha - 2012-09-05
23375 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
23376 bridgedb; lets relays use IPv6 addresses and directory authorities
23377 advertise them; and switches to a cleaner build interface.
23379 This is the first alpha release in a new series, so expect there to
23380 be bugs. Users who would rather test out a more stable branch should
23381 stay with 0.2.3.x for now.
23383 o Major features (bridges):
23384 - Bridges now report the pluggable transports they support to the
23385 bridge authority, so it can pass the supported transports on to
23386 bridgedb and/or eventually do reachability testing. Implements
23389 o Major features (IPv6):
23390 - Bridge authorities now accept IPv6 bridge addresses and include
23391 them in network status documents. Implements ticket 5534.
23392 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
23393 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
23394 to happen. Implements ticket 5535.
23395 - All kind of relays, not just bridges, can now advertise an IPv6
23396 OR port. Implements ticket 6362.
23397 - Directory authorities vote on IPv6 OR ports using the new consensus
23398 method 14. Implements ticket 6363.
23400 o Major features (build):
23401 - Switch to a nonrecursive Makefile structure. Now instead of each
23402 Makefile.am invoking other Makefile.am's, there is a master
23403 Makefile.am that includes the others. This change makes our build
23404 process slightly more maintainable, and improves parallelism for
23405 building with make -j. Original patch by Stewart Smith; various
23406 fixes by Jim Meyering.
23407 - Where available, we now use automake's "silent" make rules by
23408 default, so that warnings are easier to spot. You can get the old
23409 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
23411 o Minor features (code security and spec conformance):
23412 - Clear keys and key-derived material left on the stack in
23413 rendservice.c and rendclient.c. Check return value of
23414 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
23415 These fixes should make us more forward-secure against cold-boot
23416 attacks and the like. Fixes bug 2385.
23417 - Reject EXTEND cells sent to nonexistent streams. According to the
23418 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
23419 we were only checking for stream IDs that were currently in use.
23420 Found while hunting for more instances of bug 6271. Bugfix on
23421 0.0.2pre8, which introduced incremental circuit construction.
23423 o Minor features (streamlining);
23424 - No longer include the "opt" prefix when generating routerinfos
23425 or v2 directories: it has been needless since Tor 0.1.2. Closes
23427 - Remove some now-needless code that tried to aggressively flush
23428 OR connections as data was added to them. Since 0.2.0.1-alpha, our
23429 cell queue logic has saved us from the failure mode that this code
23430 was supposed to prevent. Removing this code will limit the number
23431 of baroque control flow paths through Tor's network logic. Reported
23432 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
23434 o Minor features (controller):
23435 - Add a "GETINFO signal/names" control port command. Implements
23437 - Provide default values for all options via "GETINFO config/defaults".
23438 Implements ticket 4971.
23440 o Minor features (IPv6):
23441 - New config option "AuthDirHasIPv6Connectivity 1" that directory
23442 authorities should set if they have IPv6 connectivity and want to
23443 do reachability tests for IPv6 relays. Implements feature 5974.
23444 - A relay with an IPv6 OR port now sends that address in NETINFO
23445 cells (in addition to its other address). Implements ticket 6364.
23447 o Minor features (log messages):
23448 - Omit the first heartbeat log message, because it never has anything
23449 useful to say, and it clutters up the bootstrapping messages.
23450 Resolves ticket 6758.
23451 - Don't log about reloading the microdescriptor cache at startup. Our
23452 bootstrap warnings are supposed to tell the user when there's a
23453 problem, and our bootstrap notices say when there isn't. Resolves
23454 ticket 6759; bugfix on 0.2.2.6-alpha.
23455 - Don't log "I learned some more directory information" when we're
23456 reading cached directory information. Reserve it for when new
23457 directory information arrives in response to a fetch. Resolves
23459 - Prevent rounding error in path bias counts when scaling
23460 them down, and use the correct scale factor default. Also demote
23461 some path bias related log messages down a level and make others
23462 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
23463 - We no longer warn so much when generating manpages from their
23466 o Code simplifications and refactoring:
23467 - Enhance our internal sscanf replacement so that we can eliminate
23468 the last remaining uses of the system sscanf. (Though those uses
23469 of sscanf were safe, sscanf itself is generally error prone, so
23470 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
23472 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
23473 - Move last_reachable and testing_since from routerinfo_t to node_t.
23474 Implements ticket 5529.
23475 - Add replaycache_t structure, functions and unit tests, then refactor
23476 rend_service_introduce() to be more clear to read, improve, debug,
23477 and test. Resolves bug 6177.
23478 - Finally remove support for malloc_good_size and malloc_usable_size.
23479 We had hoped that these functions would let us eke a little more
23480 memory out of our malloc implementation. Unfortunately, the only
23481 implementations that provided these functions are also ones that
23482 are already efficient about not overallocation: they never got us
23483 more than 7 or so bytes per allocation. Removing them saves us a
23484 little code complexity and a nontrivial amount of build complexity.
23486 o New requirements:
23487 - Tor maintainers now require Automake version 1.9 or later to build
23488 Tor from the Git repository. (Automake is not required when building
23489 from a source distribution.)
23492 Changes in version 0.2.3.21-rc - 2012-09-05
23493 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
23494 series. It fixes a trio of potential security bugs, fixes a bug where
23495 we were leaving some of the fast relays out of the microdescriptor
23496 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
23497 and cleans up other smaller issues.
23499 o Major bugfixes (security):
23500 - Tear down the circuit if we get an unexpected SENDME cell. Clients
23501 could use this trick to make their circuits receive cells faster
23502 than our flow control would have allowed, or to gum up the network,
23503 or possibly to do targeted memory denial-of-service attacks on
23504 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
23505 from July 2002, before the release of Tor 0.0.0. We had committed
23506 this patch previously, but we had to revert it because of bug 6271.
23507 Now that 6271 is fixed, this patch appears to work.
23508 - Reject any attempt to extend to an internal address. Without
23509 this fix, a router could be used to probe addresses on an internal
23510 network to see whether they were accepting connections. Fixes bug
23511 6710; bugfix on 0.0.8pre1.
23512 - Do not crash when comparing an address with port value 0 to an
23513 address policy. This bug could have been used to cause a remote
23514 assertion failure by or against directory authorities, or to
23515 allow some applications to crash clients. Fixes bug 6690; bugfix
23519 - Remove the upper bound on microdescriptor length. We were hitting
23520 the limit for routers with complex exit policies or family
23521 declarations, causing clients to not use them. Fixes the first
23522 piece of bug 6404; fix on 0.2.2.6-alpha.
23523 - Detect "ORPort 0" as meaning, uniformly, that we're not running
23524 as a relay. Previously, some of our code would treat the presence
23525 of any ORPort line as meaning that we should act like a relay,
23526 even though our new listener code would correctly not open any
23527 ORPorts for ORPort 0. Similar bugs in other Port options are also
23528 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
23531 - Avoid a pair of double-free and use-after-mark bugs that can
23532 occur with certain timings in canceled and re-received DNS
23533 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
23534 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
23535 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
23536 - Allow one-hop directory fetching circuits the full "circuit build
23537 timeout" period, rather than just half of it, before failing them
23538 and marking the relay down. This fix should help reduce cases where
23539 clients declare relays (or worse, bridges) unreachable because
23540 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
23541 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
23543 - Authorities no longer include any router in their microdescriptor
23544 consensuses for which they couldn't generate or agree on a
23545 microdescriptor. Fixes the second piece of bug 6404; fix on
23547 - Detect and reject attempts to specify both "FooPort" and
23548 "FooPort 0" in the same configuration domain. (It's still okay
23549 to have a FooPort in your configuration file, and use "FooPort 0"
23550 on the command line to disable it.) Fixes the second half of bug
23551 6507; bugfix on 0.2.3.3-alpha.
23552 - Make wildcarded addresses (that is, ones beginning with "*.") work
23553 when provided via the controller's MapAddress command. Previously,
23554 they were accepted, but we never actually noticed that they were
23555 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
23556 - Avoid crashing on a malformed state file where EntryGuardPathBias
23557 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
23558 - Add a (probably redundant) memory clear between iterations of
23559 the router status voting loop, to prevent future coding errors
23560 where data might leak between iterations of the loop. Resolves
23563 o Minor bugfixes (log messages):
23564 - Downgrade "set buildtimeout to low value" messages to "info"
23565 severity; they were never an actual problem, there was never
23566 anything reasonable to do about them, and they tended to spam logs
23567 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
23568 - Downgrade path-bias warning messages to "info". We'll try to get
23569 them working better in 0.2.4. Add internal circuit construction
23570 state to protect against the noisy warn message "Unexpectedly high
23571 circuit_successes". Also add some additional rate-limited notice
23572 messages to help determine the root cause of the warn. Fixes bug
23573 6475. Bugfix against 0.2.3.17-beta.
23574 - Move log message when unable to find a microdesc in a routerstatus
23575 entry to parse time. Previously we'd spam this warning every time
23576 we tried to figure out which microdescriptors to download. Fixes
23577 the third piece of bug 6404; fix on 0.2.3.18-rc.
23580 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
23581 change when the authority is deciding whether to accept a newly
23582 uploaded descriptor. Implements ticket 6423.
23583 - Add missing documentation for consensus and microdesc files.
23584 Resolves ticket 6732.
23587 Changes in version 0.2.2.38 - 2012-08-12
23588 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
23589 attack that could in theory leak path information.
23592 - Avoid an uninitialized memory read when reading a vote or consensus
23593 document that has an unrecognized flavor name. This read could
23594 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
23595 - Try to leak less information about what relays a client is
23596 choosing to a side-channel attacker. Previously, a Tor client would
23597 stop iterating through the list of available relays as soon as it
23598 had chosen one, thus finishing a little earlier when it picked
23599 a router earlier in the list. If an attacker can recover this
23600 timing information (nontrivial but not proven to be impossible),
23601 they could learn some coarse-grained information about which relays
23602 a client was picking (middle nodes in particular are likelier to
23603 be affected than exits). The timing attack might be mitigated by
23604 other factors (see bug 6537 for some discussion), but it's best
23605 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
23608 Changes in version 0.2.3.20-rc - 2012-08-05
23609 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
23610 series. It fixes a pair of code security bugs and a potential anonymity
23611 issue, updates our RPM spec files, and cleans up other smaller issues.
23614 - Avoid read-from-freed-memory and double-free bugs that could occur
23615 when a DNS request fails while launching it. Fixes bug 6480;
23616 bugfix on 0.2.0.1-alpha.
23617 - Avoid an uninitialized memory read when reading a vote or consensus
23618 document that has an unrecognized flavor name. This read could
23619 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
23620 - Try to leak less information about what relays a client is
23621 choosing to a side-channel attacker. Previously, a Tor client would
23622 stop iterating through the list of available relays as soon as it
23623 had chosen one, thus finishing a little earlier when it picked
23624 a router earlier in the list. If an attacker can recover this
23625 timing information (nontrivial but not proven to be impossible),
23626 they could learn some coarse-grained information about which relays
23627 a client was picking (middle nodes in particular are likelier to
23628 be affected than exits). The timing attack might be mitigated by
23629 other factors (see bug 6537 for some discussion), but it's best
23630 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
23633 - Try to make the warning when giving an obsolete SOCKSListenAddress
23634 a little more useful.
23635 - Terminate active server managed proxies if Tor stops being a
23636 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
23637 - Provide a better error message about possible OSX Asciidoc failure
23638 reasons. Fixes bug 6436.
23639 - Warn when Tor is configured to use accounting in a way that can
23640 link a hidden service to some other hidden service or public
23641 address. Resolves ticket 6490.
23644 - Check return value of fputs() when writing authority certificate
23645 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
23646 - Ignore ServerTransportPlugin lines when Tor is not configured as
23647 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
23648 - When disabling guards for having too high a proportion of failed
23649 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
23653 - Update our default RPM spec files to work with mock and rpmbuild
23654 on RHEL/Fedora. They have an updated set of dependencies and
23655 conflicts, a fix for an ancient typo when creating the "_tor"
23656 user, and better instructions. Thanks to Ondrej Mikle for the
23657 patch series. Fixes bug 6043.
23660 - Make it possible to set the TestingTorNetwork configuration
23661 option using AlternateDirAuthority and AlternateBridgeAuthority
23662 as an alternative to setting DirServer. Addresses ticket 6377.
23665 - Clarify the documentation for the Alternate*Authority options.
23667 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
23669 o Code simplification and refactoring:
23670 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
23671 10 lines. Also, don't nest them. Doing so in the past has
23672 led to hard-to-debug code. The new style is to use the
23673 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
23676 Changes in version 0.2.3.19-rc - 2012-07-06
23677 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
23678 series. It fixes the compile on Windows, reverts to a GeoIP database
23679 that isn't as broken, and fixes a flow control bug that has been around
23680 since the beginning of Tor.
23683 - Fix a bug handling SENDME cells on nonexistent streams that could
23684 result in bizarre window values. Report and patch contributed
23685 pseudonymously. Fixes part of bug 6271. This bug was introduced
23686 before the first Tor release, in svn commit r152.
23687 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
23688 June 2012 database, Maxmind marked many Tor relays as country "A1",
23689 which will cause risky behavior for clients that set EntryNodes
23690 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
23691 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
23692 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
23695 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
23696 bugfix on 0.2.1.10-alpha.
23699 Changes in version 0.2.3.18-rc - 2012-06-28
23700 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
23701 series. It fixes a few smaller bugs, but generally appears stable.
23702 Please test it and let us know whether it is!
23705 - Allow wildcarded mapaddress targets to be specified on the
23706 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
23707 - Make our linker option detection code more robust against linkers
23708 such as on FreeBSD 8, where a bad combination of options completes
23709 successfully but makes an unrunnable binary. Fixes bug 6173;
23710 bugfix on 0.2.3.17-beta.
23712 o Minor bugfixes (on 0.2.2.x and earlier):
23713 - Avoid a false positive in the util/threads unit test by increasing
23714 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
23715 - Replace "Sending publish request" log messages with "Launching
23716 upload", so that they no longer confusingly imply that we're
23717 sending something to a directory we might not even be connected
23718 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
23719 - Make sure to set *socket_error in all error cases in
23720 connection_connect(), so it can't produce a warning about
23721 errno being zero from errno_to_orconn_end_reason(). Bugfix on
23722 0.2.1.1-alpha; resolves ticket 6028.
23723 - Downgrade "Got a certificate, but we already have it" log messages
23724 from warning to info, except when we're a dirauth. Fixes bug 5238;
23725 bugfix on 0.2.1.7-alpha.
23726 - When checking for requested signatures on the latest consensus
23727 before serving it to a client, make sure to check the right
23728 consensus flavor. Bugfix on 0.2.2.6-alpha.
23729 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
23730 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
23732 o Minor bugfixes (on 0.2.3.x):
23733 - Make format_helper_exit_status() avoid unnecessary space padding
23734 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
23736 - Downgrade a message about cleaning the microdescriptor cache to
23737 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
23738 - Log a BUG message at severity INFO if we have a networkstatus with
23739 a missing entry for some microdescriptor. Continues on a patch
23741 - Improve the log message when a managed proxy fails to launch. Fixes
23742 bug 5099; bugfix on 0.2.3.6-alpha.
23743 - Don't do DNS lookups when parsing corrupted managed proxy protocol
23744 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
23745 - When formatting wildcarded address mappings for the controller,
23746 be sure to include "*." as appropriate. Partially fixes bug 6244;
23747 bugfix on 0.2.3.9-alpha.
23748 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
23749 Bugfix on 0.2.3.13-alpha.
23750 - Stop logging messages about running with circuit timeout learning
23751 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
23752 - Disable a spurious warning about reading on a marked and flushing
23753 connection. We shouldn't be doing that, but apparently we
23754 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
23755 - Fix a bug that stopped AllowDotExit from working on addresses
23756 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
23759 o Code simplification, refactoring, unit tests:
23760 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
23761 Libevent's notion of cached time when possible.
23762 - Remove duplicate code for invoking getrlimit() from control.c.
23763 - Add a unit test for the environment_variable_names_equal function.
23766 - Document the --defaults-torrc option, and the new (in 0.2.3)
23767 semantics for overriding, extending, and clearing lists of
23768 options. Closes bug 4748.
23771 Changes in version 0.2.3.17-beta - 2012-06-15
23772 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
23773 gets our TLS handshake back on track for being able to blend in with
23774 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
23775 with Vidalia, and otherwise continues to get us closer to a release
23779 - Enable gcc and ld hardening by default. Resolves ticket 5210.
23780 - Update TLS cipher list to match Firefox 8 and later. Resolves
23782 - Implement the client side of proposal 198: remove support for
23783 clients falsely claiming to support standard ciphersuites that
23784 they can actually provide. As of modern OpenSSL versions, it's not
23785 necessary to fake any standard ciphersuite, and doing so prevents
23786 us from using better ciphersuites in the future, since servers
23787 can't know whether an advertised ciphersuite is really supported or
23788 not. Some hosts -- notably, ones with very old versions of OpenSSL
23789 or where OpenSSL has been built with ECC disabled -- will stand
23790 out because of this change; TBB users should not be affected.
23793 - Change the default value for DynamicDHGroups (introduced in
23794 0.2.3.9-alpha) to 0. This feature can make Tor relays less
23795 identifiable by their use of the mod_ssl DH group, but at
23796 the cost of some usability (#4721) and bridge tracing (#6087)
23797 regressions. Resolves ticket 5598.
23798 - Send a CRLF at the end of each STATUS_* control protocol event. This
23799 bug tickled a bug in Vidalia which would make it freeze. Fixes
23800 bug 6094; bugfix on 0.2.3.16-alpha.
23803 - Disable writing on marked-for-close connections when they are
23804 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
23805 bug 5263; bugfix on 0.0.2pre13, where we first added a special
23806 case for flushing marked connections.
23807 - Detect SSL handshake even when the initial attempt to write the
23808 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
23809 - Change the AllowDotExit rules so they should actually work.
23810 We now enforce AllowDotExit only immediately after receiving an
23811 address via SOCKS or DNSPort: other sources are free to provide
23812 .exit addresses after the resolution occurs. Fixes bug 3940;
23813 bugfix on 0.2.2.1-alpha.
23814 - Fix a (harmless) integer overflow in cell statistics reported by
23815 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
23816 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
23817 right places and never depends on the consensus parameters or
23818 computes adaptive timeouts when it is disabled. Fixes bug 5049;
23819 bugfix on 0.2.2.14-alpha.
23820 - When building Tor on Windows with -DUNICODE (not default), ensure
23821 that error messages, filenames, and DNS server names are always
23822 NUL-terminated when we convert them to a single-byte encoding.
23823 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
23824 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
23825 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
23826 - Fix an edge case where TestingTorNetwork is set but the authorities
23827 and relays all have an uptime of zero, where the private Tor network
23828 could briefly lack support for hidden services. Fixes bug 3886;
23829 bugfix on 0.2.2.18-alpha.
23830 - Correct the manpage's descriptions for the default values of
23831 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
23833 - Fix the documentation for the --hush and --quiet command line
23834 options, which changed their behavior back in 0.2.3.3-alpha.
23835 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
23839 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
23840 more information to it, so that we can track it down in case it
23841 returns again. Mitigates bug 5235.
23842 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
23843 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
23844 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
23845 - Warn the user when HTTPProxy, but no other proxy type, is
23846 configured. This can cause surprising behavior: it doesn't send
23847 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
23848 directory traffic only. Resolves ticket 4663.
23849 - Issue a notice if a guard completes less than 40% of your circuits.
23850 Threshold is configurable by torrc option PathBiasNoticeRate and
23851 consensus parameter pb_noticepct. There is additional, off-by-
23852 default code to disable guards which fail too many circuits.
23853 Addresses ticket 5458.
23854 - Update to the June 6 2012 Maxmind GeoLite Country database.
23856 o Code simplifications and refactoring:
23857 - Remove validate_pluggable_transports_config(): its warning
23858 message is now handled by connection_or_connect().
23861 Changes in version 0.2.2.37 - 2012-06-06
23862 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
23863 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
23867 - Work around a bug in OpenSSL that broke renegotiation with TLS
23868 1.1 and TLS 1.2. Without this workaround, all attempts to speak
23869 the v2 Tor connection protocol when both sides were using OpenSSL
23870 1.0.1 would fail. Resolves ticket 6033.
23871 - When waiting for a client to renegotiate, don't allow it to add
23872 any bytes to the input buffer. This fixes a potential DoS issue.
23873 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
23874 - Fix an edge case where if we fetch or publish a hidden service
23875 descriptor, we might build a 4-hop circuit and then use that circuit
23876 for exiting afterwards -- even if the new last hop doesn't obey our
23877 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
23880 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
23881 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
23884 - Tell GCC and Clang to check for any errors in format strings passed
23885 to the tor_v*(print|scan)f functions.
23888 Changes in version 0.2.3.16-alpha - 2012-06-05
23889 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
23890 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
23891 currently). It also fixes a variety of smaller bugs and other cleanups
23892 that get us closer to a release candidate.
23894 o Major bugfixes (general):
23895 - Work around a bug in OpenSSL that broke renegotiation with TLS
23896 1.1 and TLS 1.2. Without this workaround, all attempts to speak
23897 the v2 Tor connection protocol when both sides were using OpenSSL
23898 1.0.1 would fail. Resolves ticket 6033.
23899 - When waiting for a client to renegotiate, don't allow it to add
23900 any bytes to the input buffer. This fixes a potential DoS issue.
23901 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
23902 - Pass correct OR address to managed proxies (like obfsproxy),
23903 even when ORListenAddress is used. Fixes bug 4865; bugfix on
23905 - The advertised platform of a router now includes only its operating
23906 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
23907 service pack level (for Windows) or its CPU architecture (for Unix).
23908 We also no longer include the "git-XYZ" tag in the version. Resolves
23911 o Major bugfixes (clients):
23912 - If we are unable to find any exit that supports our predicted ports,
23913 stop calling them predicted, so that we don't loop and build
23914 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
23915 which introduced predicted ports.
23916 - Fix an edge case where if we fetch or publish a hidden service
23917 descriptor, we might build a 4-hop circuit and then use that circuit
23918 for exiting afterwards -- even if the new last hop doesn't obey our
23919 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
23920 - Check at each new consensus whether our entry guards were picked
23921 long enough ago that we should rotate them. Previously, we only
23922 did this check at startup, which could lead to us holding a guard
23923 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
23924 - When fetching a bridge descriptor from a bridge authority,
23925 always do so anonymously, whether we have been able to open
23926 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
23927 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
23928 but we'll need to wait for bug 6010 before it's actually usable.
23930 o Major bugfixes (directory authorities):
23931 - When computing weight parameters, behave more robustly in the
23932 presence of a bad bwweightscale value. Previously, the authorities
23933 would crash if they agreed on a sufficiently broken weight_scale
23934 value: now, they use a reasonable default and carry on. Partial
23935 fix for 5786; bugfix on 0.2.2.17-alpha.
23936 - Check more thoroughly to prevent a rogue authority from
23937 double-voting on any consensus directory parameter. Previously,
23938 authorities would crash in this case if the total number of
23939 votes for any parameter exceeded the number of active voters,
23940 but would let it pass otherwise. Partial fix for bug 5786; bugfix
23944 - Rate-limit log messages when asked to connect anonymously to
23945 a private address. When these hit, they tended to hit fast and
23946 often. Also, don't bother trying to connect to addresses that we
23947 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
23948 reply makes us think we have been lied to, even when the address the
23949 client tried to connect to was "localhost." Resolves ticket 2822.
23950 - Allow packagers to insert an extra string in server descriptor
23951 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
23952 Resolves the rest of ticket 2988.
23953 - Raise the threshold of server descriptors needed (75%) and exit
23954 server descriptors needed (50%) before we will declare ourselves
23955 bootstrapped. This will make clients start building circuits a
23956 little later, but makes the initially constructed circuits less
23957 skewed and less in conflict with further directory fetches. Fixes
23959 - Close any connection that sends unrecognized junk before the
23960 handshake. Solves an issue noted in bug 4369.
23961 - Improve log messages about managed transports. Resolves ticket 5070.
23962 - Tag a bridge's descriptor as "never to be sent unencrypted".
23963 This shouldn't matter, since bridges don't open non-anonymous
23964 connections to the bridge authority and don't allow unencrypted
23965 directory connections from clients, but we might as well make
23966 sure. Closes bug 5139.
23967 - Expose our view of whether we have gone dormant to the controller,
23968 via a new "GETINFO dormant" value. Torbutton and other controllers
23969 can use this to avoid doing periodic requests through Tor while
23970 it's dormant (bug 4718). Fixes bug 5954.
23971 - Tell GCC and Clang to check for any errors in format strings passed
23972 to the tor_v*(print|scan)f functions.
23973 - Update to the May 1 2012 Maxmind GeoLite Country database.
23975 o Minor bugfixes (already included in 0.2.2.36):
23976 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
23977 Fixes bug 5346; bugfix on 0.0.8pre3.
23978 - Correct parsing of certain date types in parse_http_time().
23979 Without this patch, If-Modified-Since would behave
23980 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
23981 Esteban Manchado Velázques.
23982 - Make our number-parsing functions always treat too-large values
23983 as an error, even when those values exceed the width of the
23984 underlying type. Previously, if the caller provided these
23985 functions with minima or maxima set to the extreme values of the
23986 underlying integer type, these functions would return those
23987 values on overflow rather than treating overflow as an error.
23988 Fixes part of bug 5786; bugfix on 0.0.9.
23989 - If we hit the error case where routerlist_insert() replaces an
23990 existing (old) server descriptor, make sure to remove that
23991 server descriptor from the old_routers list. Fix related to bug
23992 1776. Bugfix on 0.2.2.18-alpha.
23993 - Clarify the behavior of MaxCircuitDirtiness with hidden service
23994 circuits. Fixes issue 5259.
23996 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
23997 - Prevent a null-pointer dereference when receiving a data cell
23998 for a nonexistent stream when the circuit in question has an
23999 empty deliver window. We don't believe this is triggerable,
24000 since we don't currently allow deliver windows to become empty,
24001 but the logic is tricky enough that it's better to make the code
24002 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
24003 - Fix a memory leak when trying to launch a DNS request when the
24004 network is disabled or the nameservers are unconfigurable. Fixes
24005 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
24006 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
24007 - Don't hold a Windows file handle open for every file mapping;
24008 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
24010 - Avoid O(n^2) performance characteristics when parsing a large
24011 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
24012 - Format more doubles with %f, not %lf. Patch from grarpamp to make
24013 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
24015 - Make our replacement implementation of strtok_r() compatible with
24016 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
24017 bugfix on 0.2.2.1-alpha.
24018 - Fix a NULL-pointer dereference on a badly formed
24019 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
24020 bugfix on 0.2.2.9-alpha.
24021 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
24022 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
24023 - Defensively refactor rend_mid_rendezvous() so that protocol
24024 violations and length checks happen in the beginning. Fixes
24026 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
24027 that IPv6 stuff will compile on MSVC, and compilation issues
24028 will be easier to track down. Fixes bug 5861.
24030 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
24031 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
24032 resource exhaustion, so that clients can adjust their load to
24033 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
24034 started using END_STREAM_REASON_RESOURCELIMIT.
24035 - Don't check for whether the address we're using for outbound
24036 connections has changed until after the outbound connection has
24037 completed. On Windows, getsockname() doesn't succeed until the
24038 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
24039 - If the configuration tries to set MyFamily on a bridge, refuse to
24040 do so, and warn about the security implications. Fixes bug 4657;
24041 bugfix on 0.2.0.3-alpha.
24042 - If the client fails to set a reasonable set of ciphersuites
24043 during its v2 handshake renegotiation, allow the renegotiation to
24044 continue nevertheless (i.e. send all the required certificates).
24045 Fixes bug 4591; bugfix on 0.2.0.20-rc.
24046 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
24047 option is set to 0 (which Vidalia version 0.2.16 now does when
24048 a SAVECONF attempt fails), perform other actions that SIGHUP
24049 usually causes (like reopening the logs). Fixes bug 5095; bugfix
24051 - If we fail to write a microdescriptor to the disk cache, do not
24052 continue replacing the old microdescriptor file. Fixes bug 2954;
24053 bugfix on 0.2.2.6-alpha.
24054 - Exit nodes don't need to fetch certificates for authorities that
24055 they don't recognize; only directory authorities, bridges,
24056 and caches need to do that. Fixes part of bug 2297; bugfix on
24058 - Correctly handle checking the permissions on the parent
24059 directory of a control socket in the root directory. Bug found
24060 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
24062 - When told to add a bridge with the same digest as a preexisting
24063 bridge but a different addr:port, change the addr:port as
24064 requested. Previously we would not notice the change. Fixes half
24065 of bug 5603; fix on 0.2.2.26-beta.
24066 - End AUTHCHALLENGE error messages (in the control protocol) with
24067 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
24069 o Minor bugfixes (on 0.2.3.x):
24070 - Turn an assertion (that the number of handshakes received as a
24071 server is not < 1) into a warning. Fixes bug 4873; bugfix on
24073 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
24074 we had reversed them when the answer was cached.) Fixes bug
24075 5723; bugfix on 0.2.3.1-alpha.
24076 - Work correctly on Linux systems with accept4 support advertised in
24077 their headers, but without accept4 support in the kernel. Fix
24078 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
24079 - When told to add a bridge with the same addr:port as a preexisting
24080 bridge but a different transport, change the transport as
24081 requested. Previously we would not notice the change. Fixes half
24082 of bug 5603; fix on 0.2.3.2-alpha.
24083 - Avoid a "double-reply" warning when replying to a SOCKS request
24084 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
24085 bugfix on 0.2.3.4-alpha.
24086 - Fix a bug where a bridge authority crashes if it has seen no
24087 directory requests when it's time to write statistics to disk.
24088 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
24090 - Don't try to open non-control listeners when DisableNetwork is set.
24091 Previously, we'd open all listeners, then immediately close them.
24092 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
24093 - Don't abort the managed proxy protocol if the managed proxy
24094 sends us an unrecognized line; ignore it instead. Fixes bug
24095 5910; bugfix on 0.2.3.9-alpha.
24096 - Fix a compile warning in crypto.c when compiling with clang 3.1.
24097 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
24098 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
24099 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
24100 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
24101 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
24102 - Resolve numerous small warnings and build issues with MSVC. Resolves
24105 o Documentation fixes:
24106 - Improve the manual's documentation for the NT Service command-line
24107 options. Addresses ticket 3964.
24108 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
24109 - Document the changes to the ORPort and DirPort options, and the
24110 fact that {OR/Dir}ListenAddress is now unnecessary (and
24111 therefore deprecated). Resolves ticket 5597.
24114 - Remove the torrc.bridge file: we don't use it for anything, and
24115 it had become badly desynchronized from torrc.sample. Resolves
24119 Changes in version 0.2.2.36 - 2012-05-24
24120 Tor 0.2.2.36 updates the addresses for two of the eight directory
24121 authorities, fixes some potential anonymity and security issues,
24122 and fixes several crash bugs.
24124 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
24125 known flaws, and nobody should be using them. You should upgrade. If
24126 you're using a Linux or BSD and its packages are obsolete, stop using
24127 those packages and upgrade anyway.
24129 o Directory authority changes:
24130 - Change IP address for maatuska (v3 directory authority).
24131 - Change IP address for ides (v3 directory authority), and rename
24135 - When building or running with any version of OpenSSL earlier
24136 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
24137 versions have a bug (CVE-2011-4576) in which their block cipher
24138 padding includes uninitialized data, potentially leaking sensitive
24139 information to any peer with whom they make a SSLv3 connection. Tor
24140 does not use SSL v3 by default, but a hostile client or server
24141 could force an SSLv3 connection in order to gain information that
24142 they shouldn't have been able to get. The best solution here is to
24143 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
24144 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
24145 to make sure that the bug can't happen.
24146 - Never use a bridge or a controller-supplied node as an exit, even
24147 if its exit policy allows it. Found by wanoskarnet. Fixes bug
24148 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
24149 and 0.2.0.3-alpha (for bridge-purpose descriptors).
24150 - Only build circuits if we have a sufficient threshold of the total
24151 descriptors that are marked in the consensus with the "Exit"
24152 flag. This mitigates an attack proposed by wanoskarnet, in which
24153 all of a client's bridges collude to restrict the exit nodes that
24154 the client knows about. Fixes bug 5343.
24155 - Provide controllers with a safer way to implement the cookie
24156 authentication mechanism. With the old method, if another locally
24157 running program could convince a controller that it was the Tor
24158 process, then that program could trick the controller into telling
24159 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
24160 authentication method uses a challenge-response approach to prevent
24161 this attack. Fixes bug 5185; implements proposal 193.
24164 - Avoid logging uninitialized data when unable to decode a hidden
24165 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
24166 - Avoid a client-side assertion failure when receiving an INTRODUCE2
24167 cell on a general purpose circuit. Fixes bug 5644; bugfix on
24169 - Fix builds when the path to sed, openssl, or sha1sum contains
24170 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
24172 - Correct our replacements for the timeradd() and timersub() functions
24173 on platforms that lack them (for example, Windows). The timersub()
24174 function is used when expiring circuits, while timeradd() is
24175 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
24176 bugfix on 0.2.2.24-alpha.
24177 - Fix the SOCKET_OK test that we use to tell when socket
24178 creation fails so that it works on Win64. Fixes part of bug 4533;
24179 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
24182 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
24183 Fixes bug 5346; bugfix on 0.0.8pre3.
24184 - Make our number-parsing functions always treat too-large values
24185 as an error, even when those values exceed the width of the
24186 underlying type. Previously, if the caller provided these
24187 functions with minima or maxima set to the extreme values of the
24188 underlying integer type, these functions would return those
24189 values on overflow rather than treating overflow as an error.
24190 Fixes part of bug 5786; bugfix on 0.0.9.
24191 - Older Linux kernels erroneously respond to strange nmap behavior
24192 by having accept() return successfully with a zero-length
24193 socket. When this happens, just close the connection. Previously,
24194 we would try harder to learn the remote address: but there was
24195 no such remote address to learn, and our method for trying to
24196 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
24197 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
24198 - Correct parsing of certain date types in parse_http_time().
24199 Without this patch, If-Modified-Since would behave
24200 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
24201 Esteban Manchado Velázques.
24202 - Change the BridgePassword feature (part of the "bridge community"
24203 design, which is not yet implemented) to use a time-independent
24204 comparison. The old behavior might have allowed an adversary
24205 to use timing to guess the BridgePassword value. Fixes bug 5543;
24206 bugfix on 0.2.0.14-alpha.
24207 - Detect and reject certain misformed escape sequences in
24208 configuration values. Previously, these values would cause us
24209 to crash if received in a torrc file or over an authenticated
24210 control port. Bug found by Esteban Manchado Velázquez, and
24211 independently by Robert Connolly from Matta Consulting who further
24212 noted that it allows a post-authentication heap overflow. Patch
24213 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
24214 bugfix on 0.2.0.16-alpha.
24215 - Fix a compile warning when using the --enable-openbsd-malloc
24216 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
24217 - During configure, detect when we're building with clang version
24218 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
24219 CFLAGS. clang doesn't support them yet.
24220 - When sending an HTTP/1.1 proxy request, include a Host header.
24221 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
24222 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
24223 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
24224 - If we hit the error case where routerlist_insert() replaces an
24225 existing (old) server descriptor, make sure to remove that
24226 server descriptor from the old_routers list. Fix related to bug
24227 1776. Bugfix on 0.2.2.18-alpha.
24229 o Minor bugfixes (documentation and log messages):
24230 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
24231 Fixes bug 4856; bugfix on Tor 0.0.6.
24232 - Update "ClientOnly" man page entry to explain that there isn't
24233 really any point to messing with it. Resolves ticket 5005.
24234 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
24235 directory authority option (introduced in Tor 0.2.2.34).
24236 - Downgrade the "We're missing a certificate" message from notice
24237 to info: people kept mistaking it for a real problem, whereas it
24238 is seldom the problem even when we are failing to bootstrap. Fixes
24239 bug 5067; bugfix on 0.2.0.10-alpha.
24240 - Correctly spell "connect" in a log message on failure to create a
24241 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
24242 - Clarify the behavior of MaxCircuitDirtiness with hidden service
24243 circuits. Fixes issue 5259.
24246 - Directory authorities now reject versions of Tor older than
24247 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
24248 inclusive. These versions accounted for only a small fraction of
24249 the Tor network, and have numerous known security issues. Resolves
24251 - Update to the May 1 2012 Maxmind GeoLite Country database.
24254 - When sending or relaying a RELAY_EARLY cell, we used to convert
24255 it to a RELAY cell if the connection was using the v1 link
24256 protocol. This was a workaround for older versions of Tor, which
24257 didn't handle RELAY_EARLY cells properly. Now that all supported
24258 versions can handle RELAY_EARLY cells, and now that we're enforcing
24259 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
24260 remove this workaround. Addresses bug 4786.
24263 Changes in version 0.2.3.15-alpha - 2012-04-30
24264 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
24265 the development branch build on Windows again.
24267 o Minor bugfixes (on 0.2.2.x and earlier):
24268 - Make sure that there are no unhandled pending TLS errors before
24269 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
24270 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
24271 Bugfix on 0.1.0.5-rc; fixes bug 4528.
24272 - Fix an assert that directory authorities could trigger on sighup
24273 during some configuration state transitions. We now don't treat
24274 it as a fatal error when the new descriptor we just generated in
24275 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
24276 - After we pick a directory mirror, we would refuse to use it if
24277 it's in our ExcludeExitNodes list, resulting in mysterious failures
24278 to bootstrap for people who just wanted to avoid exiting from
24279 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
24280 - When building with --enable-static-tor on OpenBSD, do not
24281 erroneously attempt to link -lrt. Fixes bug 5103.
24283 o Minor bugfixes (on 0.2.3.x):
24284 - When Tor is built with kernel headers from a recent (last few
24285 years) Linux kernel, do not fail to run on older (pre-2.6.28
24286 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
24287 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
24288 and 0.2.3.12-alpha.
24289 - Fix compilation with miniupnpc version 1.6; patch from
24290 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
24291 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
24292 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
24293 - Fix compilation on platforms without unistd.h, or where environ
24294 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
24297 - Directory authorities are now a little more lenient at accepting
24298 older router descriptors, or newer router descriptors that don't
24299 make big changes. This should help ameliorate past and future
24300 issues where routers think they have uploaded valid descriptors,
24301 but the authorities don't think so. Fix for ticket 2479.
24302 - Make the code that clients use to detect an address change be
24303 IPv6-aware, so that it won't fill clients' logs with error
24304 messages when trying to get the IPv4 address of an IPv6
24305 connection. Implements ticket 5537.
24307 o Removed features:
24308 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
24309 authorities needed to use it for a while to keep the network working
24310 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
24311 that was six months ago. As of now, it should no longer be needed
24315 Changes in version 0.2.3.14-alpha - 2012-04-23
24316 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
24317 candidate. It also dramatically speeds up AES: fast relays should
24318 consider switching to the newer OpenSSL library.
24320 o Directory authority changes:
24321 - Change IP address for ides (v3 directory authority), and rename
24325 - Avoid logging uninitialized data when unable to decode a hidden
24326 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
24327 - Avoid a client-side assertion failure when receiving an INTRODUCE2
24328 cell on a general purpose circuit. Fixes bug 5644; bugfix on
24330 - If authorities are unable to get a v2 consensus document from other
24331 directory authorities, they no longer fall back to fetching
24332 them from regular directory caches. Fixes bug 5635; bugfix on
24333 0.2.2.26-beta, where routers stopped downloading v2 consensus
24334 documents entirely.
24335 - When we start a Tor client with a normal consensus already cached,
24336 be willing to download a microdescriptor consensus. Fixes bug 4011;
24337 fix on 0.2.3.1-alpha.
24339 o Major features (performance):
24340 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
24341 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
24342 vectorized AES implementations as appropriate. These can be much,
24343 much faster than other AES implementations.
24345 o Minor bugfixes (0.2.2.x and earlier):
24346 - Don't launch more than 10 service-side introduction-point circuits
24347 for a hidden service in five minutes. Previously, we would consider
24348 launching more introduction-point circuits if at least one second
24349 had passed without any introduction-point circuits failing. Fixes
24350 bug 4607; bugfix on 0.0.7pre1.
24351 - Change the BridgePassword feature (part of the "bridge community"
24352 design, which is not yet implemented) to use a time-independent
24353 comparison. The old behavior might have allowed an adversary
24354 to use timing to guess the BridgePassword value. Fixes bug 5543;
24355 bugfix on 0.2.0.14-alpha.
24356 - Enforce correct return behavior of tor_vsscanf() when the '%%'
24357 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
24358 - When sending an HTTP/1.1 proxy request, include a Host header.
24359 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
24360 - Don't log that we have "decided to publish new relay descriptor"
24361 unless we are actually publishing a descriptor. Fixes bug 3942;
24362 bugfix on 0.2.2.28-beta.
24364 o Minor bugfixes (0.2.3.x):
24365 - Fix a bug where a bridge authority crashes (on a failed assert)
24366 if it has seen no directory requests when it's time to write
24367 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
24368 - Fix bug stomping on ORPort option NoListen and ignoring option
24369 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
24370 - In the testsuite, provide a large enough buffer in the tor_sscanf
24371 unit test. Otherwise we'd overrun that buffer and crash during
24372 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
24374 - Make sure we create the keys directory if it doesn't exist and we're
24375 about to store the dynamic Diffie-Hellman parameters. Fixes bug
24376 5572; bugfix on 0.2.3.13-alpha.
24377 - Fix a small memory leak when trying to decode incorrect base16
24378 authenticator during SAFECOOKIE authentication. Found by
24379 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
24382 - Add more information to a log statement that might help track down
24383 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
24384 non-IP address" messages (or any Bug messages, for that matter!),
24385 please let us know about it.
24386 - Relays now understand an IPv6 address when they get one from a
24387 directory server. Resolves ticket 4875.
24388 - Resolve IPv6 addresses in bridge and entry statistics to country
24389 code "??" which means we at least count them. Resolves ticket 5053;
24390 improves on 0.2.3.9-alpha.
24391 - Update to the April 3 2012 Maxmind GeoLite Country database.
24392 - Begin a doc/state-contents.txt file to explain the contents of
24393 the Tor state file. Fixes bug 2987.
24395 o Default torrc changes:
24396 - Stop listing "socksport 9050" in torrc.sample. We open a socks
24397 port on 9050 by default anyway, so this should not change anything
24399 - Stop mentioning the deprecated *ListenAddress options in
24400 torrc.sample. Fixes bug 5438.
24401 - Document unit of bandwidth related options in sample torrc.
24404 o Removed features:
24405 - The "torify" script no longer supports the "tsocks" socksifier
24406 tool, since tsocks doesn't support DNS and UDP right for Tor.
24407 Everyone should be using torsocks instead. Fixes bugs 3530 and
24408 5180. Based on a patch by "ugh".
24410 o Code refactoring:
24411 - Change the symmetric cipher interface so that creating and
24412 initializing a stream cipher are no longer separate functions.
24413 - Remove all internal support for unpadded RSA. We never used it, and
24414 it would be a bad idea to start.
24417 Changes in version 0.2.3.13-alpha - 2012-03-26
24418 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
24419 in managed pluggable transports, as well as providing other cleanups
24420 that get us closer to a release candidate.
24422 o Directory authority changes:
24423 - Change IP address for maatuska (v3 directory authority).
24426 - Provide controllers with a safer way to implement the cookie
24427 authentication mechanism. With the old method, if another locally
24428 running program could convince a controller that it was the Tor
24429 process, then that program could trick the controller into telling
24430 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
24431 authentication method uses a challenge-response approach to prevent
24432 this attack. Fixes bug 5185, implements proposal 193.
24433 - Never use a bridge or a controller-supplied node as an exit, even
24434 if its exit policy allows it. Found by wanoskarnet. Fixes bug
24435 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
24436 and 0.2.0.3-alpha (for bridge-purpose descriptors).
24437 - Only build circuits if we have a sufficient threshold of the total
24438 descriptors that are marked in the consensus with the "Exit"
24439 flag. This mitigates an attack proposed by wanoskarnet, in which
24440 all of a client's bridges collude to restrict the exit nodes that
24441 the client knows about. Fixes bug 5343.
24443 o Major bugfixes (on Tor 0.2.3.x):
24444 - Avoid an assert when managed proxies like obfsproxy are configured,
24445 and we receive HUP signals or setconf attempts too rapidly. This
24446 situation happens most commonly when Vidalia tries to attach to
24447 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
24448 bugfix on 0.2.3.6-alpha.
24449 - Fix a relay-side pluggable transports bug where managed proxies were
24450 unreachable from the Internet, because Tor asked them to bind on
24451 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
24452 - Stop discarding command-line arguments when TestingTorNetwork
24453 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
24454 0.2.3.9-alpha, where task 4552 added support for two layers of
24456 - Resume allowing the unit tests to run in gdb. This was accidentally
24457 made impossible when the DisableDebuggerAttachment option was
24458 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
24459 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
24460 0.2.3.11-alpha. Reported by Anthony G. Basile.
24462 o Minor bugfixes (on 0.2.2.x and earlier):
24463 - Ensure we don't cannibalize circuits that are longer than three hops
24464 already, so we don't end up making circuits with 5 or more
24465 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
24466 0.1.0.1-rc which introduced cannibalization.
24467 - Detect and reject certain misformed escape sequences in
24468 configuration values. Previously, these values would cause us
24469 to crash if received in a torrc file or over an authenticated
24470 control port. Bug found by Esteban Manchado Velázquez, and
24471 independently by Robert Connolly from Matta Consulting who further
24472 noted that it allows a post-authentication heap overflow. Patch
24473 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
24474 bugfix on 0.2.0.16-alpha.
24475 - Fix a compile warning when using the --enable-openbsd-malloc
24476 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
24477 - Directory caches no longer refuse to clean out descriptors because
24478 of missing v2 networkstatus documents, unless they're configured
24479 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
24480 0.2.2.26-beta. Patch by Daniel Bryg.
24481 - Update to the latest version of the tinytest unit testing framework.
24482 This includes a couple of bugfixes that can be relevant for
24483 running forked unit tests on Windows, and removes all reserved
24486 o Minor bugfixes (on 0.2.3.x):
24487 - On a failed pipe() call, don't leak file descriptors. Fixes bug
24488 4296; bugfix on 0.2.3.1-alpha.
24489 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
24490 until after we have received a CERTS cell. Fixes bug 4361; bugfix
24491 on 0.2.3.6-alpha. Patch by "frosty".
24492 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
24493 option, so that the IP stack doesn't decide to use it for IPv4
24494 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
24495 - Ensure that variables set in Tor's environment cannot override
24496 environment variables that Tor passes to a managed
24497 pluggable-transport proxy. Previously, Tor would pass every
24498 variable in its environment to managed proxies along with the new
24499 ones, in such a way that on many operating systems, the inherited
24500 environment variables would override those which Tor tried to
24501 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
24502 bugfix on 0.2.3.9-alpha for Windows.
24505 - A wide variety of new unit tests by Esteban Manchado Velázquez.
24506 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
24507 - Update to the March 6 2012 Maxmind GeoLite Country database.
24510 Changes in version 0.2.3.12-alpha - 2012-02-13
24511 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
24512 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
24513 when Tor is configured to use a pluggable transport like obfsproxy.
24516 - Fix builds when the path to sed, openssl, or sha1sum contains
24517 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
24519 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
24520 connections. This change should allow busy exit relays to stop
24521 running out of available sockets as quickly. Fixes bug 4950;
24522 bugfix on 0.2.2.26-beta.
24523 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
24524 would ask the bridge for microdescriptors, which are only supported
24525 in 0.2.3.x, and then fail to bootstrap when it didn't get the
24526 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
24527 - Properly set up obfsproxy's environment when in managed mode. The
24528 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
24529 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
24530 5076 and 5082; bugfix on 0.2.3.6-alpha.
24533 - Use the dead_strip option when building Tor on OS X. This reduces
24534 binary size by almost 19% when linking openssl and libevent
24535 statically, which we do for Tor Browser Bundle.
24536 - Fix broken URLs in the sample torrc file, and tell readers about
24537 the OutboundBindAddress, ExitPolicyRejectPrivate, and
24538 PublishServerDescriptor options. Addresses bug 4652.
24539 - Update to the February 7 2012 Maxmind GeoLite Country database.
24542 - Downgrade the "We're missing a certificate" message from notice
24543 to info: people kept mistaking it for a real problem, whereas it
24544 is seldom the problem even when we are failing to bootstrap. Fixes
24545 bug 5067; bugfix on 0.2.0.10-alpha.
24546 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
24547 managed pluggable transport server proxy's environment.
24548 Previously, we would put it there, even though Tor doesn't
24549 implement an 'extended server port' yet, and even though Tor
24550 almost certainly isn't listening at that address. For now, we set
24551 it to an empty string to avoid crashing older obfsproxies. Bugfix
24553 - Log the heartbeat message every HeartbeatPeriod seconds, not every
24554 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
24555 0.2.3.1-alpha. Bug reported by Scott Bennett.
24556 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
24557 bugfix on 0.2.3.11-alpha.
24558 - Update "ClientOnly" man page entry to explain that there isn't
24559 really any point to messing with it. Resolves ticket 5005.
24560 - Use the correct CVE number for CVE-2011-4576 in our comments and
24561 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
24564 o Code simplifications and refactoring:
24565 - Use the _WIN32 macro throughout our code to detect Windows.
24566 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
24570 Changes in version 0.2.3.11-alpha - 2012-01-22
24571 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
24572 the last step of the plan to limit maximum circuit length, includes
24573 a wide variety of hidden service performance and correctness fixes,
24574 works around an OpenSSL security flaw if your distro is too stubborn
24575 to upgrade, and fixes a bunch of smaller issues.
24578 - Now that Tor 0.2.0.x is completely deprecated, enable the final
24579 part of "Proposal 110: Avoiding infinite length circuits" by
24580 refusing all circuit-extend requests that do not use a relay_early
24581 cell. This change helps Tor resist a class of denial-of-service
24582 attacks by limiting the maximum circuit length.
24583 - Adjust the number of introduction points that a hidden service
24584 will try to maintain based on how long its introduction points
24585 remain in use and how many introductions they handle. Fixes
24587 - Try to use system facilities for enumerating local interface
24588 addresses, before falling back to our old approach (which was
24589 binding a UDP socket, and calling getsockname() on it). That
24590 approach was scaring OS X users whose draconian firewall
24591 software warned about binding to UDP sockets, regardless of
24592 whether packets were sent. Now we try to use getifaddrs(),
24593 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
24594 system supports. Resolves ticket 1827.
24596 o Major security workaround:
24597 - When building or running with any version of OpenSSL earlier
24598 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
24599 versions have a bug (CVE-2011-4576) in which their block cipher
24600 padding includes uninitialized data, potentially leaking sensitive
24601 information to any peer with whom they make a SSLv3 connection. Tor
24602 does not use SSL v3 by default, but a hostile client or server
24603 could force an SSLv3 connection in order to gain information that
24604 they shouldn't have been able to get. The best solution here is to
24605 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
24606 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
24607 to make sure that the bug can't happen.
24610 - Fix the SOCKET_OK test that we use to tell when socket
24611 creation fails so that it works on Win64. Fixes part of bug 4533;
24612 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
24613 - Correct our replacements for the timeradd() and timersub() functions
24614 on platforms that lack them (for example, Windows). The timersub()
24615 function is used when expiring circuits, while timeradd() is
24616 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
24617 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
24618 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
24619 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
24620 bug at runtime, not compile time, because some distributions hack
24621 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
24622 on 0.2.3.9-alpha. Found by Pascal.
24624 o Minor features (controller):
24625 - Use absolute path names when reporting the torrc filename in the
24626 control protocol, so a controller can more easily find the torrc
24627 file. Resolves bug 1101.
24628 - Extend the control protocol to report flags that control a circuit's
24629 path selection in CIRC events and in replies to 'GETINFO
24630 circuit-status'. Implements part of ticket 2411.
24631 - Extend the control protocol to report the hidden service address
24632 and current state of a hidden-service-related circuit in CIRC
24633 events and in replies to 'GETINFO circuit-status'. Implements part
24635 - When reporting the path to the cookie file to the controller,
24636 give an absolute path. Resolves ticket 4881.
24637 - Allow controllers to request an event notification whenever a
24638 circuit is cannibalized or its purpose is changed. Implements
24639 part of ticket 3457.
24640 - Include the creation time of a circuit in CIRC and CIRC2
24641 control-port events and the list produced by the 'GETINFO
24642 circuit-status' control-port command.
24644 o Minor features (directory authorities):
24645 - Directory authorities now reject versions of Tor older than
24646 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
24647 inclusive. These versions accounted for only a small fraction of
24648 the Tor network, and have numerous known security issues. Resolves
24650 - Authority operators can now vote for all relays in a given
24651 set of countries to be BadDir/BadExit/Invalid/Rejected.
24652 - Provide two consensus parameters (FastFlagMinThreshold and
24653 FastFlagMaxThreshold) to control the range of allowable bandwidths
24654 for the Fast directory flag. These allow authorities to run
24655 experiments on appropriate requirements for being a "Fast" node.
24656 The AuthDirFastGuarantee config value still applies. Implements
24658 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
24659 directory authority option (introduced in Tor 0.2.2.34).
24661 o Minor features (other):
24662 - Don't disable the DirPort when we cannot exceed our AccountingMax
24663 limit during this interval because the effective bandwidthrate is
24664 low enough. This is useful in a situation where AccountMax is only
24665 used as an additional safeguard or to provide statistics.
24666 - Prepend an informative header to generated dynamic_dh_params files.
24667 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
24668 EntryNodes will have no effect. Resolves issue 2571.
24669 - Log more useful messages when we fail to disable debugger
24671 - Log which authority we're missing votes from when we go to fetch
24672 them from the other auths.
24673 - Log (at debug level) whenever a circuit's purpose is changed.
24674 - Add missing documentation for the MaxClientCircuitsPending,
24675 UseMicrodescriptors, UserspaceIOCPBuffers, and
24676 _UseFilteringSSLBufferevents options, all introduced during
24677 the 0.2.3.x series.
24678 - Update to the January 3 2012 Maxmind GeoLite Country database.
24680 o Minor bugfixes (hidden services):
24681 - Don't close hidden service client circuits which have almost
24682 finished connecting to their destination when they reach
24683 the normal circuit-build timeout. Previously, we would close
24684 introduction circuits which are waiting for an acknowledgement
24685 from the introduction point, and rendezvous circuits which have
24686 been specified in an INTRODUCE1 cell sent to a hidden service,
24687 after the normal CBT. Now, we mark them as 'timed out', and launch
24688 another rendezvous attempt in parallel. This behavior change can
24689 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
24690 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
24691 - Don't close hidden-service-side rendezvous circuits when they
24692 reach the normal circuit-build timeout. This behavior change can
24693 be disabled using the new
24694 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
24695 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
24696 - Make sure we never mark the wrong rendezvous circuit as having
24697 had its introduction cell acknowledged by the introduction-point
24698 relay. Previously, when we received an INTRODUCE_ACK cell on a
24699 client-side hidden-service introduction circuit, we might have
24700 marked a rendezvous circuit other than the one we specified in
24701 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
24702 a warning message and interfered with the hidden service
24703 connection-establishment process. Fixes bug 4759; bugfix on
24704 0.2.3.3-alpha, when we added the stream-isolation feature which
24705 might cause Tor to open multiple rendezvous circuits for the same
24707 - Don't trigger an assertion failure when we mark a new client-side
24708 hidden-service introduction circuit for close during the process
24709 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
24712 o Minor bugfixes (log messages):
24713 - Correctly spell "connect" in a log message on failure to create a
24714 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
24716 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
24717 Fixes bug 4856; bugfix on Tor 0.0.6.
24718 - Fix the log message describing how we work around discovering
24719 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
24720 4837; bugfix on 0.2.2.9-alpha.
24721 - When logging about a disallowed .exit name, do not also call it
24722 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
24724 o Minor bugfixes (build fixes):
24725 - During configure, detect when we're building with clang version
24726 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
24727 CFLAGS. clang doesn't support them yet.
24728 - During configure, search for library containing cos function as
24729 libm lives in libcore on some platforms (BeOS/Haiku). Linking
24730 against libm was hard-coded before. Fixes the first part of bug
24731 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
24733 - Detect attempts to build Tor on (as yet hypothetical) versions
24734 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
24735 fix for bug 4533. Bugfix on 0.2.2.28-beta.
24736 - Preprocessor directives should not be put inside the arguments
24737 of a macro. This would break compilation with GCC releases prior
24738 to version 3.3. We would never recommend such an old GCC version,
24739 but it is apparently required for binary compatibility on some
24740 platforms (namely, certain builds of Haiku). Fixes the other part
24741 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
24744 o Minor bugfixes (other):
24745 - Older Linux kernels erroneously respond to strange nmap behavior
24746 by having accept() return successfully with a zero-length
24747 socket. When this happens, just close the connection. Previously,
24748 we would try harder to learn the remote address: but there was
24749 no such remote address to learn, and our method for trying to
24750 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
24751 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
24752 - Fix null-pointer access that could occur if TLS allocation failed.
24753 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
24754 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
24755 accidentally been reverted.
24756 - Fix our implementation of crypto_random_hostname() so it can't
24757 overflow on ridiculously large inputs. (No Tor version has ever
24758 provided this kind of bad inputs, but let's be correct in depth.)
24759 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
24760 - Find more places in the code that should have been testing for
24761 invalid sockets using the SOCKET_OK macro. Required for a fix
24762 for bug 4533. Bugfix on 0.2.2.28-beta.
24763 - Fix an assertion failure when, while running with bufferevents, a
24764 connection finishes connecting after it is marked for close, but
24765 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
24766 - test_util_spawn_background_ok() hardcoded the expected value
24767 for ENOENT to 2. This isn't portable as error numbers are
24768 platform specific, and particularly the hurd has ENOENT at
24769 0x40000002. Construct expected string at runtime, using the correct
24770 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
24771 - Reject attempts to disable DisableDebuggerAttachment while Tor is
24772 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
24773 - Use an appropriate-width type for sockets in tor-fw-helper on
24774 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
24777 - When sending or relaying a RELAY_EARLY cell, we used to convert
24778 it to a RELAY cell if the connection was using the v1 link
24779 protocol. This was a workaround for older versions of Tor, which
24780 didn't handle RELAY_EARLY cells properly. Now that all supported
24781 versions can handle RELAY_EARLY cells, and now that we're enforcing
24782 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
24783 remove this workaround. Addresses bug 4786.
24785 o Code simplifications and refactoring:
24786 - Use OpenSSL's built-in SSL_state_string_long() instead of our
24787 own homebrewed ssl_state_to_string() replacement. Patch from
24788 Emile Snyder. Fixes bug 4653.
24789 - Use macros to indicate OpenSSL versions, so we don't need to worry
24790 about accidental hexadecimal bit shifts.
24791 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
24793 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
24794 - Use the smartlist_add_asprintf() alias more consistently.
24795 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
24796 invalid value, rather than just -1.
24797 - Rename a handful of old identifiers, mostly related to crypto
24798 structures and crypto functions. By convention, our "create an
24799 object" functions are called "type_new()", our "free an object"
24800 functions are called "type_free()", and our types indicate that
24801 they are types only with a final "_t". But a handful of older
24802 types and functions broke these rules, with function names like
24803 "type_create" or "subsystem_op_type", or with type names like
24807 Changes in version 0.2.3.10-alpha - 2011-12-16
24808 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
24809 Tor's buffers code. Absolutely everybody should upgrade.
24811 The bug relied on an incorrect calculation when making data continuous
24812 in one of our IO buffers, if the first chunk of the buffer was
24813 misaligned by just the wrong amount. The miscalculation would allow an
24814 attacker to overflow a piece of heap-allocated memory. To mount this
24815 attack, the attacker would need to either open a SOCKS connection to
24816 Tor's SocksPort (usually restricted to localhost), or target a Tor
24817 instance configured to make its connections through a SOCKS proxy
24818 (which Tor does not do by default).
24820 Good security practice requires that all heap-overflow bugs should be
24821 presumed to be exploitable until proven otherwise, so we are treating
24822 this as a potential code execution attack. Please upgrade immediately!
24823 This bug does not affect bufferevents-based builds of Tor. Special
24824 thanks to "Vektor" for reporting this issue to us!
24826 This release also contains a few minor bugfixes for issues discovered
24830 - Fix a heap overflow bug that could occur when trying to pull
24831 data into the first chunk of a buffer, when that chunk had
24832 already had some data drained from it. Fixes CVE-2011-2778;
24833 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
24836 - If we can't attach streams to a rendezvous circuit when we
24837 finish connecting to a hidden service, clear the rendezvous
24838 circuit's stream-isolation state and try to attach streams
24839 again. Previously, we cleared rendezvous circuits' isolation
24840 state either too early (if they were freshly built) or not at all
24841 (if they had been built earlier and were cannibalized). Bugfix on
24842 0.2.3.3-alpha; fixes bug 4655.
24843 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
24844 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
24845 - Fix an assertion failure when a relay with accounting enabled
24846 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
24849 - Update to the December 6 2011 Maxmind GeoLite Country database.
24852 Changes in version 0.2.2.35 - 2011-12-16
24853 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
24854 buffers code. Absolutely everybody should upgrade.
24856 The bug relied on an incorrect calculation when making data continuous
24857 in one of our IO buffers, if the first chunk of the buffer was
24858 misaligned by just the wrong amount. The miscalculation would allow an
24859 attacker to overflow a piece of heap-allocated memory. To mount this
24860 attack, the attacker would need to either open a SOCKS connection to
24861 Tor's SocksPort (usually restricted to localhost), or target a Tor
24862 instance configured to make its connections through a SOCKS proxy
24863 (which Tor does not do by default).
24865 Good security practice requires that all heap-overflow bugs should be
24866 presumed to be exploitable until proven otherwise, so we are treating
24867 this as a potential code execution attack. Please upgrade immediately!
24868 This bug does not affect bufferevents-based builds of Tor. Special
24869 thanks to "Vektor" for reporting this issue to us!
24871 Tor 0.2.2.35 also fixes several bugs in previous versions, including
24872 crash bugs for unusual configurations, and a long-term bug that
24873 would prevent Tor from starting on Windows machines with draconian
24876 With this release, we remind everyone that 0.2.0.x has reached its
24877 formal end-of-life. Those Tor versions have many known flaws, and
24878 nobody should be using them. You should upgrade -- ideally to the
24879 0.2.2.x series. If you're using a Linux or BSD and its packages are
24880 obsolete, stop using those packages and upgrade anyway.
24882 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
24883 longer receive support after some time in early 2012.
24886 - Fix a heap overflow bug that could occur when trying to pull
24887 data into the first chunk of a buffer, when that chunk had
24888 already had some data drained from it. Fixes CVE-2011-2778;
24889 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
24890 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
24891 that it doesn't attempt to allocate a socketpair. This could cause
24892 some problems on Windows systems with overzealous firewalls. Fix for
24893 bug 4457; workaround for Libevent versions 2.0.1-alpha through
24895 - If we mark an OR connection for close based on a cell we process,
24896 don't process any further cells on it. We already avoid further
24897 reads on marked-for-close connections, but now we also discard the
24898 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
24899 which was the first version where we might mark a connection for
24900 close based on processing a cell on it.
24901 - Correctly sanity-check that we don't underflow on a memory
24902 allocation (and then assert) for hidden service introduction
24903 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
24904 bugfix on 0.2.1.5-alpha.
24905 - Fix a memory leak when we check whether a hidden service
24906 descriptor has any usable introduction points left. Fixes bug
24907 4424. Bugfix on 0.2.2.25-alpha.
24908 - Don't crash when we're running as a relay and don't have a GeoIP
24909 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
24910 we've had in the 0.2.3.x branch already.
24911 - When running as a client, do not print a misleading (and plain
24912 wrong) log message that we're collecting "directory request"
24913 statistics: clients don't collect statistics. Also don't create a
24914 useless (because empty) stats file in the stats/ directory. Fixes
24915 bug 4353; bugfix on 0.2.2.34.
24918 - Detect failure to initialize Libevent. This fix provides better
24919 detection for future instances of bug 4457.
24920 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
24921 function. This was eating up hideously large amounts of time on some
24922 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
24923 - Resolve an integer overflow bug in smartlist_ensure_capacity().
24924 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
24926 - Don't warn about unused log_mutex in log.c when building with
24927 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
24928 0.1.0.6-rc which introduced --disable-threads.
24929 - When configuring, starting, or stopping an NT service, stop
24930 immediately after the service configuration attempt has succeeded
24931 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
24932 - When sending a NETINFO cell, include the original address
24933 received for the other side, not its canonical address. Found
24934 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
24935 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
24936 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
24937 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
24938 occurred when a client tried to fetch a descriptor for a bridge
24939 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
24940 - Backport fixes for a pair of compilation warnings on Windows.
24941 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
24942 - If we had ever tried to call tor_addr_to_str on an address of
24943 unknown type, we would have done a strdup on an uninitialized
24944 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
24945 Reported by "troll_un".
24946 - Correctly detect and handle transient lookup failures from
24947 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
24948 Reported by "troll_un".
24949 - Fix null-pointer access that could occur if TLS allocation failed.
24950 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
24951 - Use tor_socket_t type for listener argument to accept(). Fixes bug
24952 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
24955 - Add two new config options for directory authorities:
24956 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
24957 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
24958 that is always sufficient to satisfy the bandwidth requirement for
24959 the Guard flag. Now it will be easier for researchers to simulate
24960 Tor networks with different values. Resolves ticket 4484.
24961 - When Tor ignores a hidden service specified in its configuration,
24962 include the hidden service's directory in the warning message.
24963 Previously, we would only tell the user that some hidden service
24964 was ignored. Bugfix on 0.0.6; fixes bug 4426.
24965 - Update to the December 6 2011 Maxmind GeoLite Country database.
24967 o Packaging changes:
24968 - Make it easier to automate expert package builds on Windows,
24969 by removing an absolute path from makensis.exe command.
24972 Changes in version 0.2.1.32 - 2011-12-16
24973 Tor 0.2.1.32 backports important security and privacy fixes for
24974 oldstable. This release is intended only for package maintainers and
24975 others who cannot use the 0.2.2 stable series. All others should be
24976 using Tor 0.2.2.x or newer.
24978 The Tor 0.2.1.x series will reach formal end-of-life some time in
24979 early 2012; we will stop releasing patches for it then.
24981 o Major bugfixes (also included in 0.2.2.x):
24982 - Correctly sanity-check that we don't underflow on a memory
24983 allocation (and then assert) for hidden service introduction
24984 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
24985 bugfix on 0.2.1.5-alpha.
24986 - Fix a heap overflow bug that could occur when trying to pull
24987 data into the first chunk of a buffer, when that chunk had
24988 already had some data drained from it. Fixes CVE-2011-2778;
24989 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
24992 - Update to the December 6 2011 Maxmind GeoLite Country database.
24995 Changes in version 0.2.3.9-alpha - 2011-12-08
24996 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
24997 a "DisableNetwork" security feature that bundles can use to avoid
24998 touching the network until bridges are configured, moves forward on
24999 the pluggable transport design, fixes a flaw in the hidden service
25000 design that unnecessarily prevented clients with wrong clocks from
25001 reaching hidden services, and fixes a wide variety of other issues.
25004 - Clients can now connect to private bridges over IPv6. Bridges
25005 still need at least one IPv4 address in order to connect to
25006 other relays. Note that we don't yet handle the case where the
25007 user has two bridge lines for the same bridge (one IPv4, one
25008 IPv6). Implements parts of proposal 186.
25009 - New "DisableNetwork" config option to prevent Tor from launching any
25010 connections or accepting any connections except on a control port.
25011 Bundles and controllers can set this option before letting Tor talk
25012 to the rest of the network, for example to prevent any connections
25013 to a non-bridge address. Packages like Orbot can also use this
25014 option to instruct Tor to save power when the network is off.
25015 - Clients and bridges can now be configured to use a separate
25016 "transport" proxy. This approach makes the censorship arms race
25017 easier by allowing bridges to use protocol obfuscation plugins. It
25018 implements the "managed proxy" part of proposal 180 (ticket 3472).
25019 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
25020 implementation. It makes AES_CTR about 7% faster than our old one
25021 (which was about 10% faster than the one OpenSSL used to provide).
25022 Resolves ticket 4526.
25023 - Add a "tor2web mode" for clients that want to connect to hidden
25024 services non-anonymously (and possibly more quickly). As a safety
25025 measure to try to keep users from turning this on without knowing
25026 what they are doing, tor2web mode must be explicitly enabled at
25027 compile time, and a copy of Tor compiled to run in tor2web mode
25028 cannot be used as a normal Tor client. Implements feature 2553.
25029 - Add experimental support for running on Windows with IOCP and no
25030 kernel-space socket buffers. This feature is controlled by a new
25031 "UserspaceIOCPBuffers" config option (off by default), which has
25032 no effect unless Tor has been built with support for bufferevents,
25033 is running on Windows, and has enabled IOCP. This may, in the long
25034 run, help solve or mitigate bug 98.
25035 - Use a more secure consensus parameter voting algorithm. Now at
25036 least three directory authorities or a majority of them must
25037 vote on a given parameter before it will be included in the
25038 consensus. Implements proposal 178.
25041 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
25042 They used to check that the timestamp was within 30 minutes
25043 of their system clock, so they could cap the size of their
25044 replay-detection cache, but that approach unnecessarily refused
25045 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
25046 the v3 intro-point protocol (the first one which sent a timestamp
25047 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
25048 - Only use the EVP interface when AES acceleration is enabled,
25049 to avoid a 5-7% performance regression. Resolves issue 4525;
25050 bugfix on 0.2.3.8-alpha.
25052 o Privacy/anonymity features (bridge detection):
25053 - Make bridge SSL certificates a bit more stealthy by using random
25054 serial numbers, in the same fashion as OpenSSL when generating
25055 self-signed certificates. Implements ticket 4584.
25056 - Introduce a new config option "DynamicDHGroups", enabled by
25057 default, which provides each bridge with a unique prime DH modulus
25058 to be used during SSL handshakes. This option attempts to help
25059 against censors who might use the Apache DH modulus as a static
25060 identifier for bridges. Addresses ticket 4548.
25062 o Minor features (new/different config options):
25063 - New configuration option "DisableDebuggerAttachment" (on by default)
25064 to prevent basic debugging attachment attempts by other processes.
25065 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
25066 - Allow MapAddress directives to specify matches against super-domains,
25067 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
25068 Implements issue 933.
25069 - Slightly change behavior of "list" options (that is, config
25070 options that can appear more than once) when they appear both in
25071 torrc and on the command line. Previously, the command-line options
25072 would be appended to the ones from torrc. Now, the command-line
25073 options override the torrc options entirely. This new behavior
25074 allows the user to override list options (like exit policies and
25075 ports to listen on) from the command line, rather than simply
25076 appending to the list.
25077 - You can get the old (appending) command-line behavior for "list"
25078 options by prefixing the option name with a "+".
25079 - You can remove all the values for a "list" option from the command
25080 line without adding any new ones by prefixing the option name
25082 - Add experimental support for a "defaults" torrc file to be parsed
25083 before the regular torrc. Torrc options override the defaults file's
25084 options in the same way that the command line overrides the torrc.
25085 The SAVECONF controller command saves only those options which
25086 differ between the current configuration and the defaults file. HUP
25087 reloads both files. (Note: This is an experimental feature; its
25088 behavior will probably be refined in future 0.2.3.x-alpha versions
25089 to better meet packagers' needs.) Implements task 4552.
25092 - Try to make the introductory warning message that Tor prints on
25093 startup more useful for actually finding help and information.
25094 Resolves ticket 2474.
25095 - Running "make version" now displays the version of Tor that
25096 we're about to build. Idea from katmagic; resolves issue 4400.
25097 - Expire old or over-used hidden service introduction points.
25098 Required by fix for bug 3460.
25099 - Move the replay-detection cache for the RSA-encrypted parts of
25100 INTRODUCE2 cells to the introduction point data structures.
25101 Previously, we would use one replay-detection cache per hidden
25102 service. Required by fix for bug 3460.
25103 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
25104 public key replay-detection cache from 60 minutes to 5 minutes. This
25105 replay-detection cache is now used only to detect multiple
25106 INTRODUCE2 cells specifying the same rendezvous point, so we can
25107 avoid launching multiple simultaneous attempts to connect to it.
25109 o Minor bugfixes (on Tor 0.2.2.x and earlier):
25110 - Resolve an integer overflow bug in smartlist_ensure_capacity().
25111 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
25113 - Fix a minor formatting issue in one of tor-gencert's error messages.
25115 - Prevent a false positive from the check-spaces script, by disabling
25116 the "whitespace between function name and (" check for functions
25118 - Fix a log message suggesting that people contact a non-existent
25119 email address. Fixes bug 3448.
25120 - Fix null-pointer access that could occur if TLS allocation failed.
25121 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
25122 - Report a real bootstrap problem to the controller on router
25123 identity mismatch. Previously we just said "foo", which probably
25124 made a lot of sense at the time. Fixes bug 4169; bugfix on
25126 - If we had ever tried to call tor_addr_to_str() on an address of
25127 unknown type, we would have done a strdup() on an uninitialized
25128 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
25129 Reported by "troll_un".
25130 - Correctly detect and handle transient lookup failures from
25131 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
25132 Reported by "troll_un".
25133 - Use tor_socket_t type for listener argument to accept(). Fixes bug
25134 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
25135 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
25136 bug 4532; found by "troll_un".
25138 o Minor bugfixes (on Tor 0.2.3.x):
25139 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
25141 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
25142 circuit for use as a hidden service client's rendezvous point.
25143 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
25144 with help from wanoskarnet.
25145 - Restore behavior of overriding SocksPort, ORPort, and similar
25146 options from the command line. Bugfix on 0.2.3.3-alpha.
25149 - Properly handle the case where the build-tree is not the same
25150 as the source tree when generating src/common/common_sha1.i,
25151 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
25152 bugfix on 0.2.0.1-alpha.
25154 o Code simplifications, cleanups, and refactorings:
25155 - Remove the pure attribute from all functions that used it
25156 previously. In many cases we assigned it incorrectly, because the
25157 functions might assert or call impure functions, and we don't have
25158 evidence that keeping the pure attribute is worthwhile. Implements
25159 changes suggested in ticket 4421.
25160 - Remove some dead code spotted by coverity. Fixes cid 432.
25161 Bugfix on 0.2.3.1-alpha, closes bug 4637.
25164 Changes in version 0.2.3.8-alpha - 2011-11-22
25165 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
25166 socketpair-related bug that has been bothering Windows users. It adds
25167 support to serve microdescriptors to controllers, so Vidalia's network
25168 map can resume listing relays (once Vidalia implements its side),
25169 and adds better support for hardware AES acceleration. Finally, it
25170 starts the process of adjusting the bandwidth cutoff for getting the
25171 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
25172 that tiny relays harm performance more than they help network capacity.
25175 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
25176 that it doesn't attempt to allocate a socketpair. This could cause
25177 some problems on Windows systems with overzealous firewalls. Fix for
25178 bug 4457; workaround for Libevent versions 2.0.1-alpha through
25180 - Correctly sanity-check that we don't underflow on a memory
25181 allocation (and then assert) for hidden service introduction
25182 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
25183 bugfix on 0.2.1.5-alpha.
25184 - Remove the artificially low cutoff of 20KB to guarantee the Fast
25185 flag. In the past few years the average relay speed has picked
25186 up, and while the "top 7/8 of the network get the Fast flag" and
25187 "all relays with 20KB or more of capacity get the Fast flag" rules
25188 used to have the same result, now the top 7/8 of the network has
25189 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
25190 - Fix a rare assertion failure when checking whether a v0 hidden
25191 service descriptor has any usable introduction points left, and
25192 we don't have enough information to build a circuit to the first
25193 intro point named in the descriptor. The HS client code in
25194 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
25195 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
25196 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
25197 - Make bridge authorities not crash when they are asked for their own
25198 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
25199 - When running as a client, do not print a misleading (and plain
25200 wrong) log message that we're collecting "directory request"
25201 statistics: clients don't collect statistics. Also don't create a
25202 useless (because empty) stats file in the stats/ directory. Fixes
25203 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
25206 - Allow Tor controllers like Vidalia to obtain the microdescriptor
25207 for a relay by identity digest or nickname. Previously,
25208 microdescriptors were only available by their own digests, so a
25209 controller would have to ask for and parse the whole microdescriptor
25210 consensus in order to look up a single relay's microdesc. Fixes
25211 bug 3832; bugfix on 0.2.3.1-alpha.
25212 - Use OpenSSL's EVP interface for AES encryption, so that all AES
25213 operations can use hardware acceleration (if present). Resolves
25216 o Minor bugfixes (on 0.2.2.x and earlier):
25217 - Detect failure to initialize Libevent. This fix provides better
25218 detection for future instances of bug 4457.
25219 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
25220 function. This was eating up hideously large amounts of time on some
25221 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
25222 - Don't warn about unused log_mutex in log.c when building with
25223 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
25224 0.1.0.6-rc which introduced --disable-threads.
25225 - Allow manual 'authenticate' commands to the controller interface
25226 from netcat (nc) as well as telnet. We were rejecting them because
25227 they didn't come with the expected whitespace at the end of the
25228 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
25229 - Fix some (not actually triggerable) buffer size checks in usage of
25230 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
25232 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
25233 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
25234 - When configuring, starting, or stopping an NT service, stop
25235 immediately after the service configuration attempt has succeeded
25236 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
25237 - When sending a NETINFO cell, include the original address
25238 received for the other side, not its canonical address. Found
25239 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
25240 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
25241 can pick them up when the tests aren't disabled. Bugfix on
25242 0.2.2.4-alpha which introduced tinytest.
25243 - Fix a memory leak when we check whether a hidden service
25244 descriptor has any usable introduction points left. Fixes bug
25245 4424. Bugfix on 0.2.2.25-alpha.
25246 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
25247 occurred when a client tried to fetch a descriptor for a bridge
25248 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
25250 o Minor bugfixes (on 0.2.3.x):
25251 - Make util unit tests build correctly with MSVC. Bugfix on
25252 0.2.3.3-alpha. Patch by Gisle Vanem.
25253 - Successfully detect AUTH_CHALLENGE cells with no recognized
25254 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
25255 Found by frosty_un.
25256 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
25257 it should still send a NETINFO cell to allow the connection to
25258 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
25260 - Log less loudly when we get an invalid authentication certificate
25261 from a source other than a directory authority: it's not unusual
25262 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
25264 - Tolerate servers with more clock skew in their authentication
25265 certificates than previously. Fixes bug 4371; bugfix on
25267 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
25268 on 0.2.3.4-alpha and 0.2.3.6-alpha.
25271 - Add two new config options for directory authorities:
25272 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
25273 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
25274 that is always sufficient to satisfy the bandwidth requirement for
25275 the Guard flag. Now it will be easier for researchers to simulate
25276 Tor networks with different values. Resolves ticket 4484.
25277 - When Tor ignores a hidden service specified in its configuration,
25278 include the hidden service's directory in the warning message.
25279 Previously, we would only tell the user that some hidden service
25280 was ignored. Bugfix on 0.0.6; fixes bug 4426.
25281 - When we fail to initialize Libevent, retry with IOCP disabled so we
25282 don't need to turn on multi-threading support in Libevent, which in
25283 turn requires a working socketpair(). This is a workaround for bug
25284 4457, which affects Libevent versions from 2.0.1-alpha through
25286 - Detect when we try to build on a platform that doesn't define
25287 AF_UNSPEC to 0. We don't work there, so refuse to compile.
25288 - Update to the November 1 2011 Maxmind GeoLite Country database.
25290 o Packaging changes:
25291 - Make it easier to automate expert package builds on Windows,
25292 by removing an absolute path from makensis.exe command.
25294 o Code simplifications and refactoring:
25295 - Remove some redundant #include directives throughout the code.
25296 Patch from Andrea Gelmini.
25297 - Unconditionally use OpenSSL's AES implementation instead of our
25298 old built-in one. OpenSSL's AES has been better for a while, and
25299 relatively few servers should still be on any version of OpenSSL
25300 that doesn't have good optimized assembly AES.
25301 - Use the name "CERTS" consistently to refer to the new cell type;
25302 we were calling it CERT in some places and CERTS in others.
25305 - Numerous new unit tests for functions in util.c and address.c by
25307 - The long-disabled benchmark tests are now split into their own
25308 ./src/test/bench binary.
25309 - The benchmark tests can now use more accurate timers than
25310 gettimeofday() when such timers are available.
25313 Changes in version 0.2.3.7-alpha - 2011-10-30
25314 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
25315 the new v3 handshake. It also resolves yet another bridge address
25319 - If we mark an OR connection for close based on a cell we process,
25320 don't process any further cells on it. We already avoid further
25321 reads on marked-for-close connections, but now we also discard the
25322 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
25323 which was the first version where we might mark a connection for
25324 close based on processing a cell on it.
25325 - Fix a double-free bug that would occur when we received an invalid
25326 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
25327 bugfix on 0.2.3.6-alpha.
25328 - Bridges no longer include their address in NETINFO cells on outgoing
25329 OR connections, to allow them to blend in better with clients.
25330 Removes another avenue for enumerating bridges. Reported by
25331 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
25332 cells were introduced.
25335 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
25336 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
25339 Changes in version 0.2.3.6-alpha - 2011-10-26
25340 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
25341 anonymity vulnerability where an attacker can deanonymize Tor
25342 users. Everybody should upgrade.
25344 This release also features support for a new v3 connection handshake
25345 protocol, and fixes to make hidden service connections more robust.
25348 - Implement a new handshake protocol (v3) for authenticating Tors to
25349 each other over TLS. It should be more resistant to fingerprinting
25350 than previous protocols, and should require less TLS hacking for
25351 future Tor implementations. Implements proposal 176.
25352 - Allow variable-length padding cells to disguise the length of
25353 Tor's TLS records. Implements part of proposal 184.
25355 o Privacy/anonymity fixes (clients):
25356 - Clients and bridges no longer send TLS certificate chains on
25357 outgoing OR connections. Previously, each client or bridge would
25358 use the same cert chain for all outgoing OR connections until
25359 its IP address changes, which allowed any relay that the client
25360 or bridge contacted to determine which entry guards it is using.
25361 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
25362 - If a relay receives a CREATE_FAST cell on a TLS connection, it
25363 no longer considers that connection as suitable for satisfying a
25364 circuit EXTEND request. Now relays can protect clients from the
25365 CVE-2011-2768 issue even if the clients haven't upgraded yet.
25366 - Directory authorities no longer assign the Guard flag to relays
25367 that haven't upgraded to the above "refuse EXTEND requests
25368 to client connections" fix. Now directory authorities can
25369 protect clients from the CVE-2011-2768 issue even if neither
25370 the clients nor the relays have upgraded yet. There's a new
25371 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
25372 to let us transition smoothly, else tomorrow there would be no
25375 o Major bugfixes (hidden services):
25376 - Improve hidden service robustness: when an attempt to connect to
25377 a hidden service ends, be willing to refetch its hidden service
25378 descriptors from each of the HSDir relays responsible for them
25379 immediately. Previously, we would not consider refetching the
25380 service's descriptors from each HSDir for 15 minutes after the last
25381 fetch, which was inconvenient if the hidden service was not running
25382 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
25383 - When one of a hidden service's introduction points appears to be
25384 unreachable, stop trying it. Previously, we would keep trying
25385 to build circuits to the introduction point until we lost the
25386 descriptor, usually because the user gave up and restarted Tor.
25387 Partly fixes bug 3825.
25388 - Don't launch a useless circuit after failing to use one of a
25389 hidden service's introduction points. Previously, we would
25390 launch a new introduction circuit, but not set the hidden service
25391 which that circuit was intended to connect to, so it would never
25392 actually be used. A different piece of code would then create a
25393 new introduction circuit correctly. Bug reported by katmagic and
25394 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
25396 o Major bugfixes (other):
25397 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
25398 that they initiated. Relays could distinguish incoming bridge
25399 connections from client connections, creating another avenue for
25400 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
25401 Found by "frosty_un".
25402 - Don't update the AccountingSoftLimitHitAt state file entry whenever
25403 tor gets started. This prevents a wrong average bandwidth
25404 estimate, which would cause relays to always start a new accounting
25405 interval at the earliest possible moment. Fixes bug 2003; bugfix
25406 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
25407 immensely in tracking this bug down.
25408 - Fix a crash bug when changing node restrictions while a DNS lookup
25409 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
25412 o Minor bugfixes (on 0.2.2.x and earlier):
25413 - When a hidden service turns an extra service-side introduction
25414 circuit into a general-purpose circuit, free the rend_data and
25415 intro_key fields first, so we won't leak memory if the circuit
25416 is cannibalized for use as another service-side introduction
25417 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
25418 - Rephrase the log message emitted if the TestSocks check is
25419 successful. Patch from Fabian Keil; fixes bug 4094.
25420 - Bridges now skip DNS self-tests, to act a little more stealthily.
25421 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
25422 bridges. Patch by "warms0x".
25423 - Remove a confusing dollar sign from the example fingerprint in the
25424 man page, and also make the example fingerprint a valid one. Fixes
25425 bug 4309; bugfix on 0.2.1.3-alpha.
25426 - Fix internal bug-checking logic that was supposed to catch
25427 failures in digest generation so that it will fail more robustly
25428 if we ask for a nonexistent algorithm. Found by Coverity Scan.
25429 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
25430 - Report any failure in init_keys() calls launched because our
25431 IP address has changed. Spotted by Coverity Scan. Bugfix on
25432 0.1.1.4-alpha; fixes CID 484.
25434 o Minor bugfixes (on 0.2.3.x):
25435 - Fix a bug in configure.in that kept it from building a configure
25436 script with autoconf versions earlier than 2.61. Fixes bug 2430;
25437 bugfix on 0.2.3.1-alpha.
25438 - Don't warn users that they are exposing a client port to the
25439 Internet if they have specified an RFC1918 address. Previously,
25440 we would warn if the user had specified any non-loopback
25441 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
25442 - Fix memory leaks in the failing cases of the new SocksPort and
25443 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
25444 fixes coverity CIDs 485, 486, and 487.
25447 - When a hidden service's introduction point times out, consider
25448 trying it again during the next attempt to connect to the
25449 HS. Previously, we would not try it again unless a newly fetched
25450 descriptor contained it. Required by fixes for bugs 1297 and 3825.
25451 - The next version of Windows will be called Windows 8, and it has
25452 a major version of 6, minor version of 2. Correctly identify that
25453 version instead of calling it "Very recent version". Resolves
25454 ticket 4153; reported by funkstar.
25455 - The Bridge Authority now writes statistics on how many bridge
25456 descriptors it gave out in total, and how many unique descriptors
25457 it gave out. It also lists how often the most and least commonly
25458 fetched descriptors were given out, as well as the median and
25459 25th/75th percentile. Implements tickets 4200 and 4294.
25460 - Update to the October 4 2011 Maxmind GeoLite Country database.
25462 o Code simplifications and refactoring:
25463 - Remove some old code to remember statistics about which descriptors
25464 we've served as a directory mirror. The feature wasn't used and
25465 is outdated now that microdescriptors are around.
25466 - Rename Tor functions that turn strings into addresses, so that
25467 "parse" indicates that no hostname resolution occurs, and
25468 "lookup" indicates that hostname resolution may occur. This
25469 should help prevent mistakes in the future. Fixes bug 3512.
25472 Changes in version 0.2.2.34 - 2011-10-26
25473 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
25474 can deanonymize Tor users. Everybody should upgrade.
25476 The attack relies on four components: 1) Clients reuse their TLS cert
25477 when talking to different relays, so relays can recognize a user by
25478 the identity key in her cert. 2) An attacker who knows the client's
25479 identity key can probe each guard relay to see if that identity key
25480 is connected to that guard relay right now. 3) A variety of active
25481 attacks in the literature (starting from "Low-Cost Traffic Analysis
25482 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
25483 discover the guard relays that a Tor user visiting the website is using.
25484 4) Clients typically pick three guards at random, so the set of guards
25485 for a given user could well be a unique fingerprint for her. This
25486 release fixes components #1 and #2, which is enough to block the attack;
25487 the other two remain as open research problems. Special thanks to
25488 "frosty_un" for reporting the issue to us!
25490 Clients should upgrade so they are no longer recognizable by the TLS
25491 certs they present. Relays should upgrade so they no longer allow a
25492 remote attacker to probe them to test whether unpatched clients are
25493 currently connected to them.
25495 This release also fixes several vulnerabilities that allow an attacker
25496 to enumerate bridge relays. Some bridge enumeration attacks still
25497 remain; see for example proposal 188.
25499 o Privacy/anonymity fixes (clients):
25500 - Clients and bridges no longer send TLS certificate chains on
25501 outgoing OR connections. Previously, each client or bridge would
25502 use the same cert chain for all outgoing OR connections until
25503 its IP address changes, which allowed any relay that the client
25504 or bridge contacted to determine which entry guards it is using.
25505 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
25506 - If a relay receives a CREATE_FAST cell on a TLS connection, it
25507 no longer considers that connection as suitable for satisfying a
25508 circuit EXTEND request. Now relays can protect clients from the
25509 CVE-2011-2768 issue even if the clients haven't upgraded yet.
25510 - Directory authorities no longer assign the Guard flag to relays
25511 that haven't upgraded to the above "refuse EXTEND requests
25512 to client connections" fix. Now directory authorities can
25513 protect clients from the CVE-2011-2768 issue even if neither
25514 the clients nor the relays have upgraded yet. There's a new
25515 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
25516 to let us transition smoothly, else tomorrow there would be no
25519 o Privacy/anonymity fixes (bridge enumeration):
25520 - Bridge relays now do their directory fetches inside Tor TLS
25521 connections, like all the other clients do, rather than connecting
25522 directly to the DirPort like public relays do. Removes another
25523 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
25524 - Bridges relays now build circuits for themselves in a more similar
25525 way to how clients build them. Removes another avenue for
25526 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
25527 when bridges were introduced.
25528 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
25529 that they initiated. Relays could distinguish incoming bridge
25530 connections from client connections, creating another avenue for
25531 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
25532 Found by "frosty_un".
25535 - Fix a crash bug when changing node restrictions while a DNS lookup
25536 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
25538 - Don't launch a useless circuit after failing to use one of a
25539 hidden service's introduction points. Previously, we would
25540 launch a new introduction circuit, but not set the hidden service
25541 which that circuit was intended to connect to, so it would never
25542 actually be used. A different piece of code would then create a
25543 new introduction circuit correctly. Bug reported by katmagic and
25544 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
25547 - Change an integer overflow check in the OpenBSD_Malloc code so
25548 that GCC is less likely to eliminate it as impossible. Patch
25549 from Mansour Moufid. Fixes bug 4059.
25550 - When a hidden service turns an extra service-side introduction
25551 circuit into a general-purpose circuit, free the rend_data and
25552 intro_key fields first, so we won't leak memory if the circuit
25553 is cannibalized for use as another service-side introduction
25554 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
25555 - Bridges now skip DNS self-tests, to act a little more stealthily.
25556 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
25557 bridges. Patch by "warms0x".
25558 - Fix internal bug-checking logic that was supposed to catch
25559 failures in digest generation so that it will fail more robustly
25560 if we ask for a nonexistent algorithm. Found by Coverity Scan.
25561 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
25562 - Report any failure in init_keys() calls launched because our
25563 IP address has changed. Spotted by Coverity Scan. Bugfix on
25564 0.1.1.4-alpha; fixes CID 484.
25566 o Minor bugfixes (log messages and documentation):
25567 - Remove a confusing dollar sign from the example fingerprint in the
25568 man page, and also make the example fingerprint a valid one. Fixes
25569 bug 4309; bugfix on 0.2.1.3-alpha.
25570 - The next version of Windows will be called Windows 8, and it has
25571 a major version of 6, minor version of 2. Correctly identify that
25572 version instead of calling it "Very recent version". Resolves
25573 ticket 4153; reported by funkstar.
25574 - Downgrade log messages about circuit timeout calibration from
25575 "notice" to "info": they don't require or suggest any human
25576 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
25577 bugfix on 0.2.2.14-alpha.
25580 - Turn on directory request statistics by default and include them in
25581 extra-info descriptors. Don't break if we have no GeoIP database.
25582 Backported from 0.2.3.1-alpha; implements ticket 3951.
25583 - Update to the October 4 2011 Maxmind GeoLite Country database.
25586 Changes in version 0.2.1.31 - 2011-10-26
25587 Tor 0.2.1.31 backports important security and privacy fixes for
25588 oldstable. This release is intended only for package maintainers and
25589 others who cannot use the 0.2.2 stable series. All others should be
25590 using Tor 0.2.2.x or newer.
25592 o Security fixes (also included in 0.2.2.x):
25593 - Replace all potentially sensitive memory comparison operations
25594 with versions whose runtime does not depend on the data being
25595 compared. This will help resist a class of attacks where an
25596 adversary can use variations in timing information to learn
25597 sensitive data. Fix for one case of bug 3122. (Safe memcmp
25598 implementation by Robert Ransom based partially on code by DJB.)
25599 - Fix an assert in parsing router descriptors containing IPv6
25600 addresses. This one took down the directory authorities when
25601 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
25603 o Privacy/anonymity fixes (also included in 0.2.2.x):
25604 - Clients and bridges no longer send TLS certificate chains on
25605 outgoing OR connections. Previously, each client or bridge would
25606 use the same cert chain for all outgoing OR connections until
25607 its IP address changes, which allowed any relay that the client
25608 or bridge contacted to determine which entry guards it is using.
25609 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
25610 - If a relay receives a CREATE_FAST cell on a TLS connection, it
25611 no longer considers that connection as suitable for satisfying a
25612 circuit EXTEND request. Now relays can protect clients from the
25613 CVE-2011-2768 issue even if the clients haven't upgraded yet.
25614 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
25615 that they initiated. Relays could distinguish incoming bridge
25616 connections from client connections, creating another avenue for
25617 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
25618 Found by "frosty_un".
25619 - When receiving a hidden service descriptor, check that it is for
25620 the hidden service we wanted. Previously, Tor would store any
25621 hidden service descriptors that a directory gave it, whether it
25622 wanted them or not. This wouldn't have let an attacker impersonate
25623 a hidden service, but it did let directories pre-seed a client
25624 with descriptors that it didn't want. Bugfix on 0.0.6.
25625 - Avoid linkability based on cached hidden service descriptors: forget
25626 all hidden service descriptors cached as a client when processing a
25627 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
25628 - Make the bridge directory authority refuse to answer directory
25629 requests for "all" descriptors. It used to include bridge
25630 descriptors in its answer, which was a major information leak.
25631 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
25632 - Don't attach new streams to old rendezvous circuits after SIGNAL
25633 NEWNYM. Previously, we would keep using an existing rendezvous
25634 circuit if it remained open (i.e. if it were kept open by a
25635 long-lived stream, or if a new stream were attached to it before
25636 Tor could notice that it was old and no longer in use). Bugfix on
25637 0.1.1.15-rc; fixes bug 3375.
25639 o Minor bugfixes (also included in 0.2.2.x):
25640 - When we restart our relay, we might get a successful connection
25641 from the outside before we've started our reachability tests,
25642 triggering a warning: "ORPort found reachable, but I have no
25643 routerinfo yet. Failing to inform controller of success." This
25644 bug was harmless unless Tor is running under a controller
25645 like Vidalia, in which case the controller would never get a
25646 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
25648 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
25649 enabled. Fixes bug 1526.
25650 - Remove undocumented option "-F" from tor-resolve: it hasn't done
25651 anything since 0.2.1.16-rc.
25652 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
25653 None of the cases where we did this before were wrong, but by making
25654 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
25655 - Fix a rare crash bug that could occur when a client was configured
25656 with a large number of bridges. Fixes bug 2629; bugfix on
25657 0.2.1.2-alpha. Bugfix by trac user "shitlei".
25658 - Correct the warning displayed when a rendezvous descriptor exceeds
25659 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
25661 - Fix an uncommon assertion failure when running with DNSPort under
25662 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
25663 - When warning about missing zlib development packages during compile,
25664 give the correct package names. Bugfix on 0.2.0.1-alpha.
25665 - Require that introduction point keys and onion keys have public
25666 exponent 65537. Bugfix on 0.2.0.10-alpha.
25667 - Do not crash when our configuration file becomes unreadable, for
25668 example due to a permissions change, between when we start up
25669 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
25671 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
25673 - Always NUL-terminate the sun_path field of a sockaddr_un before
25674 passing it to the kernel. (Not a security issue: kernels are
25675 smart enough to reject bad sockaddr_uns.) Found by Coverity;
25676 CID #428. Bugfix on Tor 0.2.0.3-alpha.
25677 - Don't stack-allocate the list of supplementary GIDs when we're
25678 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
25679 could take up to 256K, which is way too much stack. Found by
25680 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
25682 o Minor bugfixes (only in 0.2.1.x):
25683 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
25684 rely on them. Bugfix on 0.2.1.30.
25685 - Use git revisions instead of svn revisions when generating our
25686 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
25688 o Minor features (also included in 0.2.2.x):
25689 - Adjust the expiration time on our SSL session certificates to
25690 better match SSL certs seen in the wild. Resolves ticket 4014.
25691 - Allow nameservers with IPv6 address. Resolves bug 2574.
25692 - Update to the October 4 2011 Maxmind GeoLite Country database.
25695 Changes in version 0.2.3.5-alpha - 2011-09-28
25696 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
25697 bridge relays; fixes an assertion error that many users started hitting
25698 today; and adds the ability to refill token buckets more often than
25699 once per second, allowing significant performance improvements.
25702 - Bridge relays now do their directory fetches inside Tor TLS
25703 connections, like all the other clients do, rather than connecting
25704 directly to the DirPort like public relays do. Removes another
25705 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
25706 - Bridges relays now build circuits for themselves in a more similar
25707 way to how clients build them. Removes another avenue for
25708 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
25709 when bridges were introduced.
25712 - Fix an "Assertion md->held_by_node == 1 failed" error that could
25713 occur when the same microdescriptor was referenced by two node_t
25714 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
25716 o Major features (networking):
25717 - Add a new TokenBucketRefillInterval option to refill token buckets
25718 more frequently than once per second. This should improve network
25719 performance, alleviate queueing problems, and make traffic less
25720 bursty. Implements proposal 183; closes ticket 3630. Design by
25721 Florian Tschorsch and Björn Scheuermann; implementation by
25725 - Change an integer overflow check in the OpenBSD_Malloc code so
25726 that GCC is less likely to eliminate it as impossible. Patch
25727 from Mansour Moufid. Fixes bug 4059.
25729 o Minor bugfixes (usability):
25730 - Downgrade log messages about circuit timeout calibration from
25731 "notice" to "info": they don't require or suggest any human
25732 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
25733 bugfix on 0.2.2.14-alpha.
25735 o Minor features (diagnostics):
25736 - When the system call to create a listener socket fails, log the
25737 error message explaining why. This may help diagnose bug 4027.
25740 Changes in version 0.2.3.4-alpha - 2011-09-13
25741 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
25742 tweak to Tor's TLS handshake that makes relays and bridges that run
25743 this new version reachable from Iran again. It also fixes a few new
25744 bugs in 0.2.3.x, and teaches relays to recognize when they're not
25745 listed in the network consensus and republish.
25747 o Major bugfixes (also part of 0.2.2.33):
25748 - Avoid an assertion failure when reloading a configuration with
25749 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
25750 3923; bugfix on 0.2.2.25-alpha.
25752 o Minor features (security, also part of 0.2.2.33):
25753 - Check for replays of the public-key encrypted portion of an
25754 INTRODUCE1 cell, in addition to the current check for replays of
25755 the g^x value. This prevents a possible class of active attacks
25756 by an attacker who controls both an introduction point and a
25757 rendezvous point, and who uses the malleability of AES-CTR to
25758 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
25759 that these attacks are infeasible (requiring the attacker to send
25760 on the order of zettabytes of altered cells in a short interval),
25761 but we'd rather block them off in case there are any classes of
25762 this attack that we missed. Reported by Willem Pinckaers.
25764 o Minor features (also part of 0.2.2.33):
25765 - Adjust the expiration time on our SSL session certificates to
25766 better match SSL certs seen in the wild. Resolves ticket 4014.
25767 - Change the default required uptime for a relay to be accepted as
25768 a HSDir (hidden service directory) from 24 hours to 25 hours.
25769 Improves on 0.2.0.10-alpha; resolves ticket 2649.
25770 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
25771 authorities to abstain from voting on assignment of the HSDir
25772 consensus flag. Related to bug 2649.
25773 - Update to the September 6 2011 Maxmind GeoLite Country database.
25775 o Minor bugfixes (also part of 0.2.2.33):
25776 - Demote the 'replay detected' log message emitted when a hidden
25777 service receives the same Diffie-Hellman public key in two different
25778 INTRODUCE2 cells to info level. A normal Tor client can cause that
25779 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
25780 fixes part of bug 2442.
25781 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
25782 level. There is nothing that a hidden service's operator can do
25783 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
25785 - Clarify a log message specifying the characters permitted in
25786 HiddenServiceAuthorizeClient client names. Previously, the log
25787 message said that "[A-Za-z0-9+-_]" were permitted; that could have
25788 given the impression that every ASCII character between "+" and "_"
25789 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
25791 o Build fixes (also part of 0.2.2.33):
25792 - Clean up some code issues that prevented Tor from building on older
25793 BSDs. Fixes bug 3894; reported by "grarpamp".
25794 - Search for a platform-specific version of "ar" when cross-compiling.
25795 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
25798 - Fix a bug where the SocksPort option (for example) would get
25799 ignored and replaced by the default if a SocksListenAddress
25800 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
25804 - Relays now try regenerating and uploading their descriptor more
25805 frequently if they are not listed in the consensus, or if the
25806 version of their descriptor listed in the consensus is too
25807 old. This fix should prevent situations where a server declines
25808 to re-publish itself because it has done so too recently, even
25809 though the authorities decided not to list its recent-enough
25810 descriptor. Fix for bug 3327.
25813 - Relays now include a reason for regenerating their descriptors
25814 in an HTTP header when uploading to the authorities. This will
25815 make it easier to debug descriptor-upload issues in the future.
25816 - When starting as root and then changing our UID via the User
25817 control option, and we have a ControlSocket configured, make sure
25818 that the ControlSocket is owned by the same account that Tor will
25819 run under. Implements ticket 3421; fix by Jérémy Bobbio.
25822 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
25823 utility function used in the control-port code). This shouldn't
25824 ever happen unless Tor is completely out of memory, but if it did
25825 happen and Tor somehow recovered from it, Tor could have sent a log
25826 message to a control port in the middle of a reply to a controller
25827 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
25828 - Make 'FetchUselessDescriptors' cause all descriptor types and
25829 all consensus types (including microdescriptors) to get fetched.
25830 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
25832 o Code refactoring:
25833 - Make a new "entry connection" struct as an internal subtype of "edge
25834 connection", to simplify the code and make exit connections smaller.
25837 Changes in version 0.2.2.33 - 2011-09-13
25838 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
25839 TLS handshake that makes relays and bridges that run this new version
25840 reachable from Iran again.
25843 - Avoid an assertion failure when reloading a configuration with
25844 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
25845 3923; bugfix on 0.2.2.25-alpha.
25847 o Minor features (security):
25848 - Check for replays of the public-key encrypted portion of an
25849 INTRODUCE1 cell, in addition to the current check for replays of
25850 the g^x value. This prevents a possible class of active attacks
25851 by an attacker who controls both an introduction point and a
25852 rendezvous point, and who uses the malleability of AES-CTR to
25853 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
25854 that these attacks are infeasible (requiring the attacker to send
25855 on the order of zettabytes of altered cells in a short interval),
25856 but we'd rather block them off in case there are any classes of
25857 this attack that we missed. Reported by Willem Pinckaers.
25860 - Adjust the expiration time on our SSL session certificates to
25861 better match SSL certs seen in the wild. Resolves ticket 4014.
25862 - Change the default required uptime for a relay to be accepted as
25863 a HSDir (hidden service directory) from 24 hours to 25 hours.
25864 Improves on 0.2.0.10-alpha; resolves ticket 2649.
25865 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
25866 authorities to abstain from voting on assignment of the HSDir
25867 consensus flag. Related to bug 2649.
25868 - Update to the September 6 2011 Maxmind GeoLite Country database.
25870 o Minor bugfixes (documentation and log messages):
25871 - Correct the man page to explain that HashedControlPassword and
25872 CookieAuthentication can both be set, in which case either method
25873 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
25874 when we decided to allow these config options to both be set. Issue
25875 raised by bug 3898.
25876 - Demote the 'replay detected' log message emitted when a hidden
25877 service receives the same Diffie-Hellman public key in two different
25878 INTRODUCE2 cells to info level. A normal Tor client can cause that
25879 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
25880 fixes part of bug 2442.
25881 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
25882 level. There is nothing that a hidden service's operator can do
25883 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
25885 - Clarify a log message specifying the characters permitted in
25886 HiddenServiceAuthorizeClient client names. Previously, the log
25887 message said that "[A-Za-z0-9+-_]" were permitted; that could have
25888 given the impression that every ASCII character between "+" and "_"
25889 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
25892 - Provide a substitute implementation of lround() for MSVC, which
25893 apparently lacks it. Patch from Gisle Vanem.
25894 - Clean up some code issues that prevented Tor from building on older
25895 BSDs. Fixes bug 3894; reported by "grarpamp".
25896 - Search for a platform-specific version of "ar" when cross-compiling.
25897 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
25900 Changes in version 0.2.3.3-alpha - 2011-09-01
25901 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
25902 security, and provides client-side support for the microdescriptor
25903 and optimistic data features introduced earlier in the 0.2.3.x
25904 series. It also includes numerous critical bugfixes in the (optional)
25905 bufferevent-based networking backend.
25907 o Major features (stream isolation):
25908 - You can now configure Tor so that streams from different
25909 applications are isolated on different circuits, to prevent an
25910 attacker who sees your streams as they leave an exit node from
25911 linking your sessions to one another. To do this, choose some way
25912 to distinguish the applications: have them connect to different
25913 SocksPorts, or have one of them use SOCKS4 while the other uses
25914 SOCKS5, or have them pass different authentication strings to the
25915 SOCKS proxy. Then, use the new SocksPort syntax to configure the
25916 degree of isolation you need. This implements Proposal 171.
25917 - There's a new syntax for specifying multiple client ports (such as
25918 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
25919 multiple *Port entries with full addr:port syntax on each.
25920 The old *ListenAddress format is still supported, but you can't
25921 mix it with the new *Port syntax.
25923 o Major features (other):
25924 - Enable microdescriptor fetching by default for clients. This allows
25925 clients to download a much smaller amount of directory information.
25926 To disable it (and go back to the old-style consensus and
25927 descriptors), set "UseMicrodescriptors 0" in your torrc file.
25928 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
25929 "PortForwarding" config option), now supports Windows.
25930 - When using an exit relay running 0.2.3.x, clients can now
25931 "optimistically" send data before the exit relay reports that
25932 the stream has opened. This saves a round trip when starting
25933 connections where the client speaks first (such as web browsing).
25934 This behavior is controlled by a consensus parameter (currently
25935 disabled). To turn it on or off manually, use the "OptimisticData"
25936 torrc option. Implements proposal 181; code by Ian Goldberg.
25938 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
25939 - When using IOCP on Windows, we need to enable Libevent windows
25941 - The IOCP backend now works even when the user has not specified
25942 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
25943 Fixes part of bug 3752.
25944 - Correctly record the bytes we've read and written when using
25945 bufferevents, so that we can include them in our bandwidth history
25946 and advertised bandwidth. Fixes bug 3803.
25947 - Apply rate-limiting only at the bottom of a chain of filtering
25948 bufferevents. This prevents us from filling up internal read
25949 buffers and violating rate-limits when filtering bufferevents
25950 are enabled. Fixes part of bug 3804.
25951 - Add high-watermarks to the output buffers for filtered
25952 bufferevents. This prevents us from filling up internal write
25953 buffers and wasting CPU cycles when filtering bufferevents are
25954 enabled. Fixes part of bug 3804.
25955 - Correctly notice when data has been written from a bufferevent
25956 without flushing it completely. Fixes bug 3805.
25957 - Fix a bug where server-side tunneled bufferevent-based directory
25958 streams would get closed prematurely. Fixes bug 3814.
25959 - Fix a use-after-free error with per-connection rate-limiting
25960 buckets. Fixes bug 3888.
25962 o Major bugfixes (also part of 0.2.2.31-rc):
25963 - If we're configured to write our ControlPorts to disk, only write
25964 them after switching UID and creating the data directory. This way,
25965 we don't fail when starting up with a nonexistent DataDirectory
25966 and a ControlPortWriteToFile setting based on that directory. Fixes
25967 bug 3747; bugfix on Tor 0.2.2.26-beta.
25970 - Added a new CONF_CHANGED event so that controllers can be notified
25971 of any configuration changes made by other controllers, or by the
25972 user. Implements ticket 1692.
25973 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
25974 leak when using bufferevents, and lets Libevent worry about how to
25975 best copy data out of a buffer.
25976 - Replace files in stats/ rather than appending to them. Now that we
25977 include statistics in extra-info descriptors, it makes no sense to
25978 keep old statistics forever. Implements ticket 2930.
25980 o Minor features (build compatibility):
25981 - Limited, experimental support for building with nmake and MSVC.
25982 - Provide a substitute implementation of lround() for MSVC, which
25983 apparently lacks it. Patch from Gisle Vanem.
25985 o Minor features (also part of 0.2.2.31-rc):
25986 - Update to the August 2 2011 Maxmind GeoLite Country database.
25988 o Minor bugfixes (on 0.2.3.x-alpha):
25989 - Fix a spurious warning when parsing SOCKS requests with
25990 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
25991 - Get rid of a harmless warning that could happen on relays running
25992 with bufferevents. The warning was caused by someone doing an http
25993 request to a relay's orport. Also don't warn for a few related
25994 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
25996 o Minor bugfixes (on 2.2.x and earlier):
25997 - Correct the man page to explain that HashedControlPassword and
25998 CookieAuthentication can both be set, in which case either method
25999 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
26000 when we decided to allow these config options to both be set. Issue
26001 raised by bug 3898.
26002 - The "--quiet" and "--hush" options now apply not only to Tor's
26003 behavior before logs are configured, but also to Tor's behavior in
26004 the absence of configured logs. Fixes bug 3550; bugfix on
26007 o Minor bugfixes (also part of 0.2.2.31-rc):
26008 - Write several files in text mode, on OSes that distinguish text
26009 mode from binary mode (namely, Windows). These files are:
26010 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
26011 that collect those statistics; 'client_keys' and 'hostname' for
26012 hidden services that use authentication; and (in the tor-gencert
26013 utility) newly generated identity and signing keys. Previously,
26014 we wouldn't specify text mode or binary mode, leading to an
26015 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
26016 the DirRecordUsageByCountry option which would have triggered
26017 the assertion failure was added), although this assertion failure
26018 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
26019 - Selectively disable deprecation warnings on OS X because Lion
26020 started deprecating the shipped copy of openssl. Fixes bug 3643.
26021 - Remove an extra pair of quotation marks around the error
26022 message in control-port STATUS_GENERAL BUG events. Bugfix on
26023 0.1.2.6-alpha; fixes bug 3732.
26024 - When unable to format an address as a string, report its value
26025 as "???" rather than reusing the last formatted address. Bugfix
26028 o Code simplifications and refactoring:
26029 - Rewrite the listener-selection logic so that parsing which ports
26030 we want to listen on is now separate from binding to the ports
26034 - Building Tor with bufferevent support now requires Libevent
26035 2.0.13-stable or later. Previous versions of Libevent had bugs in
26036 SSL-related bufferevents and related issues that would make Tor
26037 work badly with bufferevents. Requiring 2.0.13-stable also allows
26038 Tor with bufferevents to take advantage of Libevent APIs
26039 introduced after 2.0.8-rc.
26042 Changes in version 0.2.2.32 - 2011-08-27
26043 The Tor 0.2.2 release series is dedicated to the memory of Andreas
26044 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
26045 a founder of the PETS community, a leader in our field, a mentor,
26046 and a friend. He left us with these words: "I had the possibility
26047 to contribute to this world that is not as it should be. I hope I
26048 could help in some areas to make the world a better place, and that
26049 I could also encourage other people to be engaged in improving the
26050 world. Please, stay engaged. This world needs you, your love, your
26051 initiative -- now I cannot be part of that anymore."
26053 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
26054 ready. More than two years in the making, this release features improved
26055 client performance and hidden service reliability, better compatibility
26056 for Android, correct behavior for bridges that listen on more than
26057 one address, more extensible and flexible directory object handling,
26058 better reporting of network statistics, improved code security, and
26059 many many other features and bugfixes.
26062 Changes in version 0.2.2.31-rc - 2011-08-17
26063 Tor 0.2.2.31-rc is the second and hopefully final release candidate
26064 for the Tor 0.2.2.x series.
26067 - Remove an extra pair of quotation marks around the error
26068 message in control-port STATUS_GENERAL BUG events. Bugfix on
26069 0.1.2.6-alpha; fixes bug 3732.
26070 - If we're configured to write our ControlPorts to disk, only write
26071 them after switching UID and creating the data directory. This way,
26072 we don't fail when starting up with a nonexistent DataDirectory
26073 and a ControlPortWriteToFile setting based on that directory. Fixes
26074 bug 3747; bugfix on Tor 0.2.2.26-beta.
26077 - Update to the August 2 2011 Maxmind GeoLite Country database.
26080 - Allow GETINFO fingerprint to return a fingerprint even when
26081 we have not yet built a router descriptor. Fixes bug 3577;
26082 bugfix on 0.2.0.1-alpha.
26083 - Write several files in text mode, on OSes that distinguish text
26084 mode from binary mode (namely, Windows). These files are:
26085 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
26086 that collect those statistics; 'client_keys' and 'hostname' for
26087 hidden services that use authentication; and (in the tor-gencert
26088 utility) newly generated identity and signing keys. Previously,
26089 we wouldn't specify text mode or binary mode, leading to an
26090 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
26091 the DirRecordUsageByCountry option which would have triggered
26092 the assertion failure was added), although this assertion failure
26093 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
26094 - Selectively disable deprecation warnings on OS X because Lion
26095 started deprecating the shipped copy of openssl. Fixes bug 3643.
26096 - When unable to format an address as a string, report its value
26097 as "???" rather than reusing the last formatted address. Bugfix
26101 Changes in version 0.2.3.2-alpha - 2011-07-18
26102 Tor 0.2.3.2-alpha introduces two new experimental features:
26103 microdescriptors and pluggable transports. It also continues cleaning
26104 up a variety of recently introduced features.
26107 - Clients can now use microdescriptors instead of regular descriptors
26108 to build circuits. Microdescriptors are authority-generated
26109 summaries of regular descriptors' contents, designed to change
26110 very rarely (see proposal 158 for details). This feature is
26111 designed to save bandwidth, especially for clients on slow internet
26112 connections. It's off by default for now, since nearly no caches
26113 support it, but it will be on-by-default for clients in a future
26114 version. You can use the UseMicrodescriptors option to turn it on.
26115 - Tor clients using bridges can now be configured to use a separate
26116 'transport' proxy for each bridge. This approach helps to resist
26117 censorship by allowing bridges to use protocol obfuscation
26118 plugins. It implements part of proposal 180. Implements ticket 2841.
26119 - While we're trying to bootstrap, record how many TLS connections
26120 fail in each state, and report which states saw the most failures
26121 in response to any bootstrap failures. This feature may speed up
26122 diagnosis of censorship events. Implements ticket 3116.
26124 o Major bugfixes (on 0.2.3.1-alpha):
26125 - When configuring a large set of nodes in EntryNodes (as with
26126 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
26127 random subset to be guards, and choose them in random
26128 order. Fixes bug 2798.
26129 - Tor could crash when remembering a consensus in a non-used consensus
26130 flavor without having a current consensus set. Fixes bug 3361.
26131 - Comparing an unknown address to a microdescriptor's shortened exit
26132 policy would always give a "rejected" result. Fixes bug 3599.
26133 - Using microdescriptors as a client no longer prevents Tor from
26134 uploading and downloading hidden service descriptors. Fixes
26138 - Allow nameservers with IPv6 address. Resolves bug 2574.
26139 - Accept attempts to include a password authenticator in the
26140 handshake, as supported by SOCKS5. This handles SOCKS clients that
26141 don't know how to omit a password when authenticating. Resolves
26143 - When configuring a large set of nodes in EntryNodes, and there are
26144 enough of them listed as Guard so that we don't need to consider
26145 the non-guard entries, prefer the ones listed with the Guard flag.
26146 - Check for and recover from inconsistency in the microdescriptor
26147 cache. This will make it harder for us to accidentally free a
26148 microdescriptor without removing it from the appropriate data
26149 structures. Fixes issue 3135; issue noted by "wanoskarnet".
26150 - Log SSL state transitions at log level DEBUG, log domain
26151 HANDSHAKE. This can be useful for debugging censorship events.
26152 Implements ticket 3264.
26153 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
26154 implements ticket 3439.
26156 o Minor bugfixes (on 0.2.3.1-alpha):
26157 - Do not free all general-purpose regular descriptors just
26158 because microdescriptor use is enabled. Fixes bug 3113.
26159 - Correctly link libevent_openssl when --enable-static-libevent
26160 is passed to configure. Fixes bug 3118.
26161 - Bridges should not complain during their heartbeat log messages that
26162 they are unlisted in the consensus: that's more or less the point
26163 of being a bridge. Fixes bug 3183.
26164 - Report a SIGNAL event to controllers when acting on a delayed
26165 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
26166 event to the controller if we acted on a SIGNAL NEWNYM command
26167 immediately, and otherwise not report a SIGNAL event for the
26168 command at all. Fixes bug 3349.
26169 - Fix a crash when handling the SIGNAL controller command or
26170 reporting ERR-level status events with bufferevents enabled. Found
26171 by Robert Ransom. Fixes bug 3367.
26172 - Always ship the tor-fw-helper manpage in our release tarballs.
26173 Fixes bug 3389. Reported by Stephen Walker.
26174 - Fix a class of double-mark-for-close bugs when bufferevents
26175 are enabled. Fixes bug 3403.
26176 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
26177 - Add SIGNAL to the list returned by the 'GETINFO events/names'
26178 control-port command. Fixes part of bug 3465.
26179 - Prevent using negative indices during unit test runs when read_all()
26180 fails. Spotted by coverity.
26181 - Fix a rare memory leak when checking the nodelist without it being
26182 present. Found by coverity.
26183 - Only try to download a microdescriptor-flavored consensus from
26184 a directory cache that provides them.
26186 o Minor bugfixes (on 0.2.2.x and earlier):
26187 - Assert that hidden-service-related operations are not performed
26188 using single-hop circuits. Previously, Tor would assert that
26189 client-side streams are not attached to single-hop circuits,
26190 but not that other sensitive operations on the client and service
26191 side are not performed using single-hop circuits. Fixes bug 3332;
26193 - Don't publish a new relay descriptor when we reload our onion key,
26194 unless the onion key has actually changed. Fixes bug 3263 and
26195 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
26196 - Allow GETINFO fingerprint to return a fingerprint even when
26197 we have not yet built a router descriptor. Fixes bug 3577;
26198 bugfix on 0.2.0.1-alpha.
26199 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
26200 on 0.2.2.4-alpha; fixes bug 3427.
26202 o Code simplification and refactoring:
26203 - Use tor_sscanf() in place of scanf() in more places through the
26204 code. This makes us a little more locale-independent, and
26205 should help shut up code-analysis tools that can't tell
26206 a safe sscanf string from a dangerous one.
26207 - Use tt_assert(), not tor_assert(), for checking for test failures.
26208 This makes the unit tests more able to go on in the event that
26210 - Split connection_about_to_close() into separate functions for each
26214 - On Windows, we now define the _WIN32_WINNT macros only if they
26215 are not already defined. This lets the person building Tor decide,
26216 if they want, to require a later version of Windows.
26219 Changes in version 0.2.2.30-rc - 2011-07-07
26220 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
26221 series. It fixes a few smaller bugs, but generally appears stable.
26222 Please test it and let us know whether it is!
26225 - Send a SUCCEEDED stream event to the controller when a reverse
26226 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
26227 discovered by katmagic.
26228 - Always NUL-terminate the sun_path field of a sockaddr_un before
26229 passing it to the kernel. (Not a security issue: kernels are
26230 smart enough to reject bad sockaddr_uns.) Found by Coverity;
26231 CID #428. Bugfix on Tor 0.2.0.3-alpha.
26232 - Don't stack-allocate the list of supplementary GIDs when we're
26233 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
26234 could take up to 256K, which is way too much stack. Found by
26235 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
26236 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
26237 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
26238 fixes part of bug 3465.
26239 - Fix a memory leak when receiving a descriptor for a hidden
26240 service we didn't ask for. Found by Coverity; CID #30. Bugfix
26244 - Update to the July 1 2011 Maxmind GeoLite Country database.
26247 Changes in version 0.2.2.29-beta - 2011-06-20
26248 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
26249 have bridge lines in their torrc but don't want to use them; gets
26250 us closer to having the control socket feature working on Debian;
26251 and fixes a variety of smaller bugs.
26254 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
26255 When we changed the default behavior to "use bridges if any
26256 are listed in the torrc", we surprised users who had bridges
26257 in their torrc files but who didn't actually want to use them.
26258 Partial resolution for bug 3354.
26261 - Don't attach new streams to old rendezvous circuits after SIGNAL
26262 NEWNYM. Previously, we would keep using an existing rendezvous
26263 circuit if it remained open (i.e. if it were kept open by a
26264 long-lived stream, or if a new stream were attached to it before
26265 Tor could notice that it was old and no longer in use). Bugfix on
26266 0.1.1.15-rc; fixes bug 3375.
26269 - Fix a bug when using ControlSocketsGroupWritable with User. The
26270 directory's group would be checked against the current group, not
26271 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
26272 bugfix on 0.2.2.26-beta.
26273 - Make connection_printf_to_buf()'s behavior sane. Its callers
26274 expect it to emit a CRLF iff the format string ends with CRLF;
26275 it actually emitted a CRLF iff (a) the format string ended with
26276 CRLF or (b) the resulting string was over 1023 characters long or
26277 (c) the format string did not end with CRLF *and* the resulting
26278 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
26279 fixes part of bug 3407.
26280 - Make send_control_event_impl()'s behavior sane. Its callers
26281 expect it to always emit a CRLF at the end of the string; it
26282 might have emitted extra control characters as well. Bugfix on
26283 0.1.1.9-alpha; fixes another part of bug 3407.
26284 - Make crypto_rand_int() check the value of its input correctly.
26285 Previously, it accepted values up to UINT_MAX, but could return a
26286 negative number if given a value above INT_MAX+1. Found by George
26287 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
26288 - Avoid a segfault when reading a malformed circuit build state
26289 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
26291 - When asked about a DNS record type we don't support via a
26292 client DNSPort, reply with NOTIMPL rather than an empty
26293 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
26294 - Fix a rare memory leak during stats writing. Found by coverity.
26297 - Update to the June 1 2011 Maxmind GeoLite Country database.
26299 o Code simplifications and refactoring:
26300 - Remove some dead code as indicated by coverity.
26301 - Remove a few dead assignments during router parsing. Found by
26303 - Add some forgotten return value checks during unit tests. Found
26305 - Don't use 1-bit wide signed bit fields. Found by coverity.
26308 Changes in version 0.2.2.28-beta - 2011-06-04
26309 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
26310 fixed a big bug in whether relays stay in the consensus consistently,
26311 we moved closer to handling bridges and hidden services correctly,
26312 and we started the process of better handling the dreaded "my Vidalia
26313 died, and now my Tor demands a password when I try to reconnect to it"
26317 - Don't decide to make a new descriptor when receiving a HUP signal.
26318 This bug has caused a lot of 0.2.2.x relays to disappear from the
26319 consensus periodically. Fixes the most common case of triggering
26320 bug 1810; bugfix on 0.2.2.7-alpha.
26321 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
26322 - Don't try to build descriptors if "ORPort auto" is set and we
26323 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
26325 - Resolve a crash that occurred when setting BridgeRelay to 1 with
26326 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
26327 - Apply circuit timeouts to opened hidden-service-related circuits
26328 based on the correct start time. Previously, we would apply the
26329 circuit build timeout based on time since the circuit's creation;
26330 it was supposed to be applied based on time since the circuit
26331 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
26332 - Use the same circuit timeout for client-side introduction
26333 circuits as for other four-hop circuits, rather than the timeout
26334 for single-hop directory-fetch circuits; the shorter timeout may
26335 have been appropriate with the static circuit build timeout in
26336 0.2.1.x and earlier, but caused many hidden service access attempts
26337 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
26338 on 0.2.2.2-alpha; fixes another part of bug 1297.
26339 - In ticket 2511 we fixed a case where you could use an unconfigured
26340 bridge if you had configured it as a bridge the last time you ran
26341 Tor. Now fix another edge case: if you had configured it as a bridge
26342 but then switched to a different bridge via the controller, you
26343 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
26347 - Add an __OwningControllerProcess configuration option and a
26348 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
26349 that when it exits, Tor will shut down. Implements feature 3049.
26350 - If "UseBridges 1" is set and no bridges are configured, Tor will
26351 now refuse to build any circuits until some bridges are set.
26352 If "UseBridges auto" is set, Tor will use bridges if they are
26353 configured and we are not running as a server, but otherwise will
26354 make circuits as usual. The new default is "auto". Patch by anonym,
26355 so the Tails LiveCD can stop automatically revealing you as a Tor
26359 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
26360 - Remove a trailing asterisk from "exit-policy/default" in the
26361 output of the control port command "GETINFO info/names". Bugfix
26363 - Use a wide type to hold sockets when built for 64-bit Windows builds.
26365 - Warn when the user configures two HiddenServiceDir lines that point
26366 to the same directory. Bugfix on 0.0.6 (the version introducing
26367 HiddenServiceDir); fixes bug 3289.
26368 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
26369 part of bug 2748; bugfix on 0.2.0.10-alpha.
26370 - Log malformed requests for rendezvous descriptors as protocol
26371 warnings, not warnings. Also, use a more informative log message
26372 in case someone sees it at log level warning without prior
26373 info-level messages. Fixes the other part of bug 2748; bugfix
26375 - Clear the table recording the time of the last request for each
26376 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
26377 Previously, we would clear our HS descriptor cache on SIGNAL
26378 NEWNYM, but if we had previously retrieved a descriptor (or tried
26379 to) from every directory responsible for it, we would refuse to
26380 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
26382 - Fix a log message that said "bits" while displaying a value in
26383 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
26385 - When checking for 1024-bit keys, check for 1024 bits, not 128
26386 bytes. This allows Tor to correctly discard keys of length 1017
26387 through 1023. Bugfix on 0.0.9pre5.
26390 - Relays now log the reason for publishing a new relay descriptor,
26391 so we have a better chance of hunting down instances of bug 1810.
26392 Resolves ticket 3252.
26393 - Revise most log messages that refer to nodes by nickname to
26394 instead use the "$key=nickname at address" format. This should be
26395 more useful, especially since nicknames are less and less likely
26396 to be unique. Resolves ticket 3045.
26397 - Log (at info level) when purging pieces of hidden-service-client
26398 state because of SIGNAL NEWNYM.
26401 - Remove undocumented option "-F" from tor-resolve: it hasn't done
26402 anything since 0.2.1.16-rc.
26405 Changes in version 0.2.2.27-beta - 2011-05-18
26406 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
26407 release, and also adds a few more general bugfixes.
26410 - Fix a crash bug when changing bridges in a running Tor process.
26411 Fixes bug 3213; bugfix on 0.2.2.26-beta.
26412 - When the controller configures a new bridge, don't wait 10 to 60
26413 seconds before trying to fetch its descriptor. Bugfix on
26414 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
26417 - Require that onion keys have exponent 65537 in microdescriptors too.
26418 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
26419 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
26420 Changed the limit to 512 characters by removing base64 newlines.
26421 Fixes bug 2752. Fix by Michael Yakubovich.
26422 - When a client starts or stops using bridges, never use a circuit
26423 that was built before the configuration change. This behavior could
26424 put at risk a user who uses bridges to ensure that her traffic
26425 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
26429 Changes in version 0.2.2.26-beta - 2011-05-17
26430 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
26431 also introduces a new "socksport auto" approach that should make it
26432 easier to run multiple Tors on the same system, and does a lot of
26433 cleanup to get us closer to a release candidate.
26435 o Security/privacy fixes:
26436 - Replace all potentially sensitive memory comparison operations
26437 with versions whose runtime does not depend on the data being
26438 compared. This will help resist a class of attacks where an
26439 adversary can use variations in timing information to learn
26440 sensitive data. Fix for one case of bug 3122. (Safe memcmp
26441 implementation by Robert Ransom based partially on code by DJB.)
26442 - When receiving a hidden service descriptor, check that it is for
26443 the hidden service we wanted. Previously, Tor would store any
26444 hidden service descriptors that a directory gave it, whether it
26445 wanted them or not. This wouldn't have let an attacker impersonate
26446 a hidden service, but it did let directories pre-seed a client
26447 with descriptors that it didn't want. Bugfix on 0.0.6.
26448 - On SIGHUP, do not clear out all TrackHostExits mappings, client
26449 DNS cache entries, and virtual address mappings: that's what
26450 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
26453 - The options SocksPort, ControlPort, and so on now all accept a
26454 value "auto" that opens a socket on an OS-selected port. A
26455 new ControlPortWriteToFile option tells Tor to write its
26456 actual control port or ports to a chosen file. If the option
26457 ControlPortFileGroupReadable is set, the file is created as
26458 group-readable. Now users can run two Tor clients on the same
26459 system without needing to manually mess with parameters. Resolves
26460 part of ticket 3076.
26461 - Set SO_REUSEADDR on all sockets, not just listeners. This should
26462 help busy exit nodes avoid running out of useable ports just
26463 because all the ports have been used in the near past. Resolves
26467 - New "GETINFO net/listeners/(type)" controller command to return
26468 a list of addresses and ports that are bound for listeners for a
26469 given connection type. This is useful when the user has configured
26470 "SocksPort auto" and the controller needs to know which port got
26471 chosen. Resolves another part of ticket 3076.
26472 - Add a new ControlSocketsGroupWritable configuration option: when
26473 it is turned on, ControlSockets are group-writeable by the default
26474 group of the current user. Patch by Jérémy Bobbio; implements
26476 - Tor now refuses to create a ControlSocket in a directory that is
26477 world-readable (or group-readable if ControlSocketsGroupWritable
26478 is 0). This is necessary because some operating systems do not
26479 enforce permissions on an AF_UNIX sockets. Permissions on the
26480 directory holding the socket, however, seems to work everywhere.
26481 - Rate-limit a warning about failures to download v2 networkstatus
26482 documents. Resolves part of bug 1352.
26483 - Backport code from 0.2.3.x that allows directory authorities to
26484 clean their microdescriptor caches. Needed to resolve bug 2230.
26485 - When an HTTPS proxy reports "403 Forbidden", we now explain
26486 what it means rather than calling it an unexpected status code.
26487 Closes bug 2503. Patch from Michael Yakubovich.
26488 - Update to the May 1 2011 Maxmind GeoLite Country database.
26491 - Authorities now clean their microdesc cache periodically and when
26492 reading from disk initially, not only when adding new descriptors.
26493 This prevents a bug where we could lose microdescriptors. Bugfix
26494 on 0.2.2.6-alpha. Fixes bug 2230.
26495 - Do not crash when our configuration file becomes unreadable, for
26496 example due to a permissions change, between when we start up
26497 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
26499 - Avoid a bug that would keep us from replacing a microdescriptor
26500 cache on Windows. (We would try to replace the file while still
26501 holding it open. That's fine on Unix, but Windows doesn't let us
26502 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
26503 - Add missing explanations for the authority-related torrc options
26504 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
26505 man page. Resolves issue 2379.
26506 - As an authority, do not upload our own vote or signature set to
26507 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
26508 it would get flagged as a duplicate. Resolves bug 3026.
26509 - Accept hidden service descriptors if we think we might be a hidden
26510 service directory, regardless of what our consensus says. This
26511 helps robustness, since clients and hidden services can sometimes
26512 have a more up-to-date view of the network consensus than we do,
26513 and if they think that the directory authorities list us a HSDir,
26514 we might actually be one. Related to bug 2732; bugfix on
26516 - When a controller changes TrackHostExits, remove mappings for
26517 hosts that should no longer have their exits tracked. Bugfix on
26519 - When a controller changes VirtualAddrNetwork, remove any mappings
26520 for hosts that were automapped to the old network. Bugfix on
26522 - When a controller changes one of the AutomapHosts* options, remove
26523 any mappings for hosts that should no longer be automapped. Bugfix
26525 - Do not reset the bridge descriptor download status every time we
26526 re-parse our configuration or get a configuration change. Fixes
26527 bug 3019; bugfix on 0.2.0.3-alpha.
26529 o Minor bugfixes (code cleanup):
26530 - When loading the microdesc journal, remember its current size.
26531 In 0.2.2, this helps prevent the microdesc journal from growing
26532 without limit on authorities (who are the only ones to use it in
26533 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
26534 Fix posted by "cypherpunks."
26535 - The microdesc journal is supposed to get rebuilt only if it is
26536 at least _half_ the length of the store, not _twice_ the length
26537 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
26538 - Fix a potential null-pointer dereference while computing a
26539 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
26541 - Avoid a possible null-pointer dereference when rebuilding the mdesc
26542 cache without actually having any descriptors to cache. Bugfix on
26543 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
26544 - If we fail to compute the identity digest of a v3 legacy keypair,
26545 warn, and don't use a buffer-full of junk instead. Bugfix on
26546 0.2.1.1-alpha; fixes bug 3106.
26547 - Resolve an untriggerable issue in smartlist_string_num_isin(),
26548 where if the function had ever in the future been used to check
26549 for the presence of a too-large number, it would have given an
26550 incorrect result. (Fortunately, we only used it for 16-bit
26551 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
26552 - Require that introduction point keys and onion handshake keys
26553 have a public exponent of 65537. Starts to fix bug 3207; bugfix
26556 o Removed features:
26557 - Caches no longer download and serve v2 networkstatus documents
26558 unless FetchV2Networkstatus flag is set: these documents haven't
26559 haven't been used by clients or relays since 0.2.0.x. Resolves
26563 Changes in version 0.2.3.1-alpha - 2011-05-05
26564 Tor 0.2.3.1-alpha adds some new experimental features, including support
26565 for an improved network IO backend, IOCP networking on Windows,
26566 microdescriptor caching, "fast-start" support for streams, and automatic
26567 home router configuration. There are also numerous internal improvements
26568 to try to make the code easier for developers to work with.
26570 This is the first alpha release in a new series, so expect there to be
26571 bugs. Users who would rather test out a more stable branch should
26572 stay with 0.2.2.x for now.
26575 - Tor can now optionally build with the "bufferevents" buffered IO
26576 backend provided by Libevent 2. To use this feature, make sure you
26577 have the latest possible version of Libevent, and pass the
26578 --enable-bufferevents flag to configure when building Tor from
26579 source. This feature will make our networking code more flexible,
26580 let us stack layers on each other, and let us use more efficient
26581 zero-copy transports where available.
26582 - As an experimental feature, Tor can use IOCP for networking on Windows.
26583 Once this code is tuned and optimized, it promises much better
26584 performance than the select-based backend we've used in the past. To
26585 try this feature, you must build Tor with Libevent 2, configure Tor
26586 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
26587 your torrc. There are known bugs here: only try this if you can help
26588 debug it as it breaks.
26589 - The EntryNodes option can now include country codes like {de} or IP
26590 addresses or network masks. Previously we had disallowed these options
26591 because we didn't have an efficient way to keep the list up to
26592 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
26593 - Exit nodes now accept and queue data on not-yet-connected streams.
26594 Previously, the client wasn't allowed to send data until the stream was
26595 connected, which slowed down all connections. This change will enable
26596 clients to perform a "fast-start" on streams and send data without
26597 having to wait for a confirmation that the stream has opened. (Patch
26598 from Ian Goldberg; implements the server side of Proposal 174.)
26599 - Tor now has initial support for automatic port mapping on the many
26600 home routers that support NAT-PMP or UPnP. (Not yet supported on
26601 Windows). To build the support code, you'll need to have libnatpnp
26602 library and/or the libminiupnpc library, and you'll need to enable the
26603 feature specifically by passing "--enable-upnp" and/or
26604 "--enable-natpnp" to configure. To turn it on, use the new
26605 PortForwarding option.
26606 - Caches now download, cache, and serve multiple "flavors" of the
26607 consensus, including a flavor that describes microdescriptors.
26608 - Caches now download, cache, and serve microdescriptors -- small
26609 summaries of router descriptors that are authenticated by all of the
26610 directory authorities. Once enough caches are running this code,
26611 clients will be able to save significant amounts of directory bandwidth
26612 by downloading microdescriptors instead of router descriptors.
26615 - Make logging resolution configurable with a new LogTimeGranularity
26616 option, and change the default from 1 millisecond to 1 second.
26617 Implements enhancement 1668.
26618 - We log which torrc file we're using on startup. Implements ticket
26620 - Ordinarily, Tor does not count traffic from private addresses (like
26621 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
26622 There is now a new option, CountPrivateBandwidth, to disable this
26623 behavior. Patch from Daniel Cagara.
26624 - New --enable-static-tor configure option for building Tor as
26625 statically as possible. Idea, general hackery and thoughts from
26626 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
26628 - If you set the NumCPUs option to 0, Tor will now try to detect how
26629 many CPUs you have. This is the new default behavior.
26630 - Turn on directory request statistics by default and include them in
26631 extra-info descriptors. Don't break if we have no GeoIP database.
26632 - Relays that set "ConnDirectionStatistics 1" write statistics on the
26633 bidirectional use of connections to disk every 24 hours.
26634 - Add a GeoIP file digest to the extra-info descriptor. Implements
26636 - The NodeFamily option -- which let you declare that you want to
26637 consider nodes to be part of a family whether they list themselves
26638 that way or not -- now allows IP address ranges and country codes.
26639 - Add a new 'Heartbeat' log message type to periodically log a message
26640 describing Tor's status at level Notice. This feature is meant for
26641 operators who log at notice, and want to make sure that their Tor
26642 server is still working. Implementation by George Kadianakis.
26644 o Minor bugfixes (on 0.2.2.25-alpha):
26645 - When loading the microdesc journal, remember its current size.
26646 In 0.2.2, this helps prevent the microdesc journal from growing
26647 without limit on authorities (who are the only ones to use it in
26648 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
26649 Fix posted by "cypherpunks."
26650 - The microdesc journal is supposed to get rebuilt only if it is
26651 at least _half_ the length of the store, not _twice_ the length
26652 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
26653 - If as an authority we fail to compute the identity digest of a v3
26654 legacy keypair, warn, and don't use a buffer-full of junk instead.
26655 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
26656 - Authorities now clean their microdesc cache periodically and when
26657 reading from disk initially, not only when adding new descriptors.
26658 This prevents a bug where we could lose microdescriptors. Bugfix
26661 o Minor features (controller):
26662 - Add a new SIGNAL event to the controller interface so that
26663 controllers can be notified when Tor handles a signal. Resolves
26664 issue 1955. Patch by John Brooks.
26665 - Add a new GETINFO option to get total bytes read and written. Patch
26666 from pipe, revised by atagar. Resolves ticket 2345.
26667 - Implement some GETINFO controller fields to provide information about
26668 the Tor process's pid, euid, username, and resource limits.
26671 - Our build system requires automake 1.6 or later to create the
26672 Makefile.in files. Previously, you could have used 1.4.
26673 This only affects developers and people building Tor from git;
26674 people who build Tor from the source distribution without changing
26675 the Makefile.am files should be fine.
26676 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
26677 so on. This is more robust against some of the failure modes
26678 associated with running the autotools pieces on their own.
26680 o Minor packaging issues:
26681 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
26682 already created. Patch from Andreas Stieger. Fixes bug 2573.
26684 o Code simplifications and refactoring:
26685 - A major revision to our internal node-selecting and listing logic.
26686 Tor already had at least two major ways to look at the question of
26687 "which Tor servers do we know about": a list of router descriptors,
26688 and a list of entries in the current consensus. With
26689 microdescriptors, we're adding a third. Having so many systems
26690 without an abstraction layer over them was hurting the codebase.
26691 Now, we have a new "node_t" abstraction that presents a consistent
26692 interface to a client's view of a Tor node, and holds (nearly) all
26693 of the mutable state formerly in routerinfo_t and routerstatus_t.
26694 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
26695 no longer link against Libevent: they never used it, but
26696 our library structure used to force them to link it.
26698 o Removed features:
26699 - Remove some old code to work around even older versions of Tor that
26700 used forked processes to handle DNS requests. Such versions of Tor
26701 are no longer in use as servers.
26703 o Documentation fixes:
26704 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
26705 - Add missing documentation for the authority-related torrc options
26706 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
26710 Changes in version 0.2.2.25-alpha - 2011-04-29
26711 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
26712 robust, routers no longer overreport their bandwidth, Win7 should crash
26713 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
26714 now prevents hidden service-related activity from being linkable. It
26715 provides more information to Vidalia so you can see if your bridge is
26716 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
26717 StrictNodes configuration options to make them more reliable, more
26718 understandable, and more regularly applied. If you use those options,
26719 please see the revised documentation for them in the manual page.
26722 - Relays were publishing grossly inflated bandwidth values because
26723 they were writing their state files wrong--now they write the
26724 correct value. Also, resume reading bandwidth history from the
26725 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
26726 - Improve hidden service robustness: When we find that we have
26727 extended a hidden service's introduction circuit to a relay not
26728 listed as an introduction point in the HS descriptor we currently
26729 have, retry with an introduction point from the current
26730 descriptor. Previously we would just give up. Fixes bugs 1024 and
26731 1930; bugfix on 0.2.0.10-alpha.
26732 - Clients now stop trying to use an exit node associated with a given
26733 destination by TrackHostExits if they fail to reach that exit node.
26734 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
26735 - Fix crash bug on platforms where gmtime and localtime can return
26736 NULL. Windows 7 users were running into this one. Fixes part of bug
26737 2077. Bugfix on all versions of Tor. Found by boboper.
26739 o Security and stability fixes:
26740 - Don't double-free a parsable, but invalid, microdescriptor, even if
26741 it is followed in the blob we're parsing by an unparsable
26742 microdescriptor. Fixes an issue reported in a comment on bug 2954.
26743 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
26744 - If the Nickname configuration option isn't given, Tor would pick a
26745 nickname based on the local hostname as the nickname for a relay.
26746 Because nicknames are not very important in today's Tor and the
26747 "Unnamed" nickname has been implemented, this is now problematic
26748 behavior: It leaks information about the hostname without being
26749 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
26750 introduced the Unnamed nickname. Reported by tagnaq.
26751 - Fix an uncommon assertion failure when running with DNSPort under
26752 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
26753 - Avoid linkability based on cached hidden service descriptors: forget
26754 all hidden service descriptors cached as a client when processing a
26755 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
26758 - Export GeoIP information on bridge usage to controllers even if we
26759 have not yet been running for 24 hours. Now Vidalia bridge operators
26760 can get more accurate and immediate feedback about their
26761 contributions to the network.
26763 o Major features and bugfixes (node selection):
26764 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
26765 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
26766 options. Previously, we had been ambiguous in describing what
26767 counted as an "exit" node, and what operations exactly "StrictNodes
26768 0" would permit. This created confusion when people saw nodes built
26769 through unexpected circuits, and made it hard to tell real bugs from
26770 surprises. Now the intended behavior is:
26771 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
26772 a node that delivers user traffic outside the Tor network.
26773 . "Entry", in the context of EntryNodes, means a node used as the
26774 first hop of a multihop circuit. It doesn't include direct
26775 connections to directory servers.
26776 . "ExcludeNodes" applies to all nodes.
26777 . "StrictNodes" changes the behavior of ExcludeNodes only. When
26778 StrictNodes is set, Tor should avoid all nodes listed in
26779 ExcludeNodes, even when it will make user requests fail. When
26780 StrictNodes is *not* set, then Tor should follow ExcludeNodes
26781 whenever it can, except when it must use an excluded node to
26782 perform self-tests, connect to a hidden service, provide a
26783 hidden service, fulfill a .exit request, upload directory
26784 information, or fetch directory information.
26785 Collectively, the changes to implement the behavior fix bug 1090.
26786 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
26787 a node is listed in both, it's treated as excluded.
26788 - ExcludeNodes now applies to directory nodes -- as a preference if
26789 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
26790 Don't exclude all the directory authorities and set StrictNodes to 1
26791 unless you really want your Tor to break.
26792 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
26793 - ExcludeExitNodes now overrides .exit requests.
26794 - We don't use bridges listed in ExcludeNodes.
26795 - When StrictNodes is 1:
26796 . We now apply ExcludeNodes to hidden service introduction points
26797 and to rendezvous points selected by hidden service users. This
26798 can make your hidden service less reliable: use it with caution!
26799 . If we have used ExcludeNodes on ourself, do not try relay
26800 reachability self-tests.
26801 . If we have excluded all the directory authorities, we will not
26802 even try to upload our descriptor if we're a relay.
26803 . Do not honor .exit requests to an excluded node.
26804 - Remove a misfeature that caused us to ignore the Fast/Stable flags
26805 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
26806 - When the set of permitted nodes changes, we now remove any mappings
26807 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
26809 - We never cannibalize a circuit that had excluded nodes on it, even
26810 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
26811 - Revert a change where we would be laxer about attaching streams to
26812 circuits than when building the circuits. This was meant to prevent
26813 a set of bugs where streams were never attachable, but our improved
26814 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
26815 - Keep track of how many times we launch a new circuit to handle a
26816 given stream. Too many launches could indicate an inconsistency
26817 between our "launch a circuit to handle this stream" logic and our
26818 "attach this stream to one of the available circuits" logic.
26819 - Improve log messages related to excluded nodes.
26822 - Fix a spurious warning when moving from a short month to a long
26823 month on relays with month-based BandwidthAccounting. Bugfix on
26824 0.2.2.17-alpha; fixes bug 3020.
26825 - When a client finds that an origin circuit has run out of 16-bit
26826 stream IDs, we now mark it as unusable for new streams. Previously,
26827 we would try to close the entire circuit. Bugfix on 0.0.6.
26828 - Add a forgotten cast that caused a compile warning on OS X 10.6.
26829 Bugfix on 0.2.2.24-alpha.
26830 - Be more careful about reporting the correct error from a failed
26831 connect() system call. Under some circumstances, it was possible to
26832 look at an incorrect value for errno when sending the end reason.
26833 Bugfix on 0.1.0.1-rc.
26834 - Correctly handle an "impossible" overflow cases in connection byte
26835 counting, where we write or read more than 4GB on an edge connection
26836 in a single second. Bugfix on 0.1.2.8-beta.
26837 - Correct the warning displayed when a rendezvous descriptor exceeds
26838 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
26840 - Clients and hidden services now use HSDir-flagged relays for hidden
26841 service descriptor downloads and uploads even if the relays have no
26842 DirPort set and the client has disabled TunnelDirConns. This will
26843 eventually allow us to give the HSDir flag to relays with no
26844 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
26845 - Downgrade "no current certificates known for authority" message from
26846 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
26847 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
26848 2917. Bugfix on 0.1.1.1-alpha.
26849 - Only limit the lengths of single HS descriptors, even when multiple
26850 HS descriptors are published to an HSDir relay in a single POST
26851 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
26852 - Write the current time into the LastWritten line in our state file,
26853 rather than the time from the previous write attempt. Also, stop
26854 trying to use a time of -1 in our log statements. Fixes bug 3039;
26855 bugfix on 0.2.2.14-alpha.
26856 - Be more consistent in our treatment of file system paths. "~" should
26857 get expanded to the user's home directory in the Log config option.
26858 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
26859 feature for the -f and --DataDirectory options.
26862 - Make sure every relay writes a state file at least every 12 hours.
26863 Previously, a relay could go for weeks without writing its state
26864 file, and on a crash could lose its bandwidth history, capacity
26865 estimates, client country statistics, and so on. Addresses bug 3012.
26866 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
26867 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
26868 clients are already deprecated because of security bugs.
26869 - Don't allow v0 hidden service authorities to act as clients.
26870 Required by fix for bug 3000.
26871 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
26872 by fix for bug 3000.
26873 - Ensure that no empty [dirreq-](read|write)-history lines are added
26874 to an extrainfo document. Implements ticket 2497.
26876 o Code simplification and refactoring:
26877 - Remove workaround code to handle directory responses from servers
26878 that had bug 539 (they would send HTTP status 503 responses _and_
26879 send a body too). Since only server versions before
26880 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
26881 keep the workaround in place.
26882 - Remove the old 'fuzzy time' logic. It was supposed to be used for
26883 handling calculations where we have a known amount of clock skew and
26884 an allowed amount of unknown skew. But we only used it in three
26885 places, and we never adjusted the known/unknown skew values. This is
26886 still something we might want to do someday, but if we do, we'll
26887 want to do it differently.
26888 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
26889 None of the cases where we did this before were wrong, but by making
26890 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
26891 - Use GetTempDir to find the proper temporary directory location on
26892 Windows when generating temporary files for the unit tests. Patch by
26896 Changes in version 0.2.2.24-alpha - 2011-04-08
26897 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
26898 prevented Tor clients from effectively using "multihomed" bridges,
26899 that is, bridges that listen on multiple ports or IP addresses so users
26900 can continue to use some of their addresses even if others get blocked.
26903 - Fix a bug where bridge users who configure the non-canonical
26904 address of a bridge automatically switch to its canonical
26905 address. If a bridge listens at more than one address, it should be
26906 able to advertise those addresses independently and any non-blocked
26907 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
26909 - If you configured Tor to use bridge A, and then quit and
26910 configured Tor to use bridge B instead, it would happily continue
26911 to use bridge A if it's still reachable. While this behavior is
26912 a feature if your goal is connectivity, in some scenarios it's a
26913 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
26914 - Directory authorities now use data collected from their own
26915 uptime observations when choosing whether to assign the HSDir flag
26916 to relays, instead of trusting the uptime value the relay reports in
26917 its descriptor. This change helps prevent an attack where a small
26918 set of nodes with frequently-changing identity keys can blackhole
26919 a hidden service. (Only authorities need upgrade; others will be
26920 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
26923 - When we restart our relay, we might get a successful connection
26924 from the outside before we've started our reachability tests,
26925 triggering a warning: "ORPort found reachable, but I have no
26926 routerinfo yet. Failing to inform controller of success." This
26927 bug was harmless unless Tor is running under a controller
26928 like Vidalia, in which case the controller would never get a
26929 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
26931 - Make directory authorities more accurate at recording when
26932 relays that have failed several reachability tests became
26933 unreachable, so we can provide more accuracy at assigning Stable,
26934 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
26935 - Fix an issue that prevented static linking of libevent on
26936 some platforms (notably Linux). Fixes bug 2698; bugfix on
26937 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
26938 the --with-static-libevent configure option).
26939 - We now ask the other side of a stream (the client or the exit)
26940 for more data on that stream when the amount of queued data on
26941 that stream dips low enough. Previously, we wouldn't ask the
26942 other side for more data until either it sent us more data (which
26943 it wasn't supposed to do if it had exhausted its window!) or we
26944 had completely flushed all our queued data. This flow control fix
26945 should improve throughput. Fixes bug 2756; bugfix on the earliest
26946 released versions of Tor (svn commit r152).
26947 - Avoid a double-mark-for-free warning when failing to attach a
26948 transparent proxy connection. (We thought we had fixed this in
26949 0.2.2.23-alpha, but it turns out our fix was checking the wrong
26950 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
26951 bug) and 0.2.2.23-alpha (the incorrect fix).
26952 - When warning about missing zlib development packages during compile,
26953 give the correct package names. Bugfix on 0.2.0.1-alpha.
26956 - Directory authorities now log the source of a rejected POSTed v3
26957 networkstatus vote.
26958 - Make compilation with clang possible when using
26959 --enable-gcc-warnings by removing two warning options that clang
26960 hasn't implemented yet and by fixing a few warnings. Implements
26962 - When expiring circuits, use microsecond timers rather than
26963 one-second timers. This can avoid an unpleasant situation where a
26964 circuit is launched near the end of one second and expired right
26965 near the beginning of the next, and prevent fluctuations in circuit
26967 - Use computed circuit-build timeouts to decide when to launch
26968 parallel introduction circuits for hidden services. (Previously,
26969 we would retry after 15 seconds.)
26970 - Update to the April 1 2011 Maxmind GeoLite Country database.
26973 - Create the /var/run/tor directory on startup on OpenSUSE if it is
26974 not already created. Patch from Andreas Stieger. Fixes bug 2573.
26976 o Documentation changes:
26977 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
26978 - Resolve all doxygen warnings except those for missing documentation.
26980 - Add doxygen documentation for more functions, fields, and types.
26983 Changes in version 0.2.2.23-alpha - 2011-03-08
26984 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
26985 they restart they don't lose their bandwidth capacity estimate. This
26986 release also fixes a diverse set of user-facing bugs, ranging from
26987 relays overrunning their rate limiting to clients falsely warning about
26988 clock skew to bridge descriptor leaks by our bridge directory authority.
26991 - Stop sending a CLOCK_SKEW controller status event whenever
26992 we fetch directory information from a relay that has a wrong clock.
26993 Instead, only inform the controller when it's a trusted authority
26994 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
26995 the rest of bug 1074.
26996 - Fix an assert in parsing router descriptors containing IPv6
26997 addresses. This one took down the directory authorities when
26998 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
26999 - Make the bridge directory authority refuse to answer directory
27000 requests for "all" descriptors. It used to include bridge
27001 descriptors in its answer, which was a major information leak.
27002 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
27003 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
27004 Tor would ignore their RelayBandwidthBurst setting,
27005 potentially using more bandwidth than expected. Bugfix on
27006 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
27007 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
27008 hidserv" in her torrc. The 'hidserv' argument never controlled
27009 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
27012 - Relays now save observed peak bandwidth throughput rates to their
27013 state file (along with total usage, which was already saved)
27014 so that they can determine their correct estimated bandwidth on
27015 restart. Resolves bug 1863, where Tor relays would reset their
27016 estimated bandwidth to 0 after restarting.
27017 - Directory authorities now take changes in router IP address and
27018 ORPort into account when determining router stability. Previously,
27019 if a router changed its IP or ORPort, the authorities would not
27020 treat it as having any downtime for the purposes of stability
27021 calculation, whereas clients would experience downtime since the
27022 change could take a while to propagate to them. Resolves issue 1035.
27023 - Enable Address Space Layout Randomization (ASLR) and Data Execution
27024 Prevention (DEP) by default on Windows to make it harder for
27025 attackers to exploit vulnerabilities. Patch from John Brooks.
27027 o Minor bugfixes (on 0.2.1.x and earlier):
27028 - Fix a rare crash bug that could occur when a client was configured
27029 with a large number of bridges. Fixes bug 2629; bugfix on
27030 0.2.1.2-alpha. Bugfix by trac user "shitlei".
27031 - Avoid a double mark-for-free warning when failing to attach a
27032 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
27034 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
27035 found by "cypherpunks". This bug was introduced before the first
27036 Tor release, in svn commit r110.
27037 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
27038 don't mention them in the manpage. Fixes bug 2450; issue
27039 spotted by keb and G-Lo.
27040 - Fix a bug in bandwidth history state parsing that could have been
27041 triggered if a future version of Tor ever changed the timing
27042 granularity at which bandwidth history is measured. Bugfix on
27043 Tor 0.1.1.11-alpha.
27044 - When a relay decides that its DNS is too broken for it to serve
27045 as an exit server, it advertised itself as a non-exit, but
27046 continued to act as an exit. This could create accidental
27047 partitioning opportunities for users. Instead, if a relay is
27048 going to advertise reject *:* as its exit policy, it should
27049 really act with exit policy "reject *:*". Fixes bug 2366.
27050 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
27051 - In the special case where you configure a public exit relay as your
27052 bridge, Tor would be willing to use that exit relay as the last
27053 hop in your circuit as well. Now we fail that circuit instead.
27054 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
27055 - Fix a bug with our locking implementation on Windows that couldn't
27056 correctly detect when a file was already locked. Fixes bug 2504,
27057 bugfix on 0.2.1.6-alpha.
27058 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
27059 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
27061 - Set target port in get_interface_address6() correctly. Bugfix
27062 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
27063 - Directory authorities are now more robust to hops back in time
27064 when calculating router stability. Previously, if a run of uptime
27065 or downtime appeared to be negative, the calculation could give
27066 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
27068 - Fix an assert that got triggered when using the TestingTorNetwork
27069 configuration option and then issuing a GETINFO config-text control
27070 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
27072 o Minor bugfixes (on 0.2.2.x):
27073 - Clients should not weight BadExit nodes as Exits in their node
27074 selection. Similarly, directory authorities should not count BadExit
27075 bandwidth as Exit bandwidth when computing bandwidth-weights.
27076 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
27077 - Correctly clear our dir_read/dir_write history when there is an
27078 error parsing any bw history value from the state file. Bugfix on
27079 Tor 0.2.2.15-alpha.
27080 - Resolve a bug in verifying signatures of directory objects
27081 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
27082 Fixes bug 2409. Found by "piebeer".
27083 - Bridge authorities no longer crash on SIGHUP when they try to
27084 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
27088 - Log less aggressively about circuit timeout changes, and improve
27089 some other circuit timeout messages. Resolves bug 2004.
27090 - Log a little more clearly about the times at which we're no longer
27091 accepting new connections. Resolves bug 2181.
27092 - Reject attempts at the client side to open connections to private
27093 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
27094 a randomly chosen exit node. Attempts to do so are always
27095 ill-defined, generally prevented by exit policies, and usually
27096 in error. This will also help to detect loops in transparent
27097 proxy configurations. You can disable this feature by setting
27098 "ClientRejectInternalAddresses 0" in your torrc.
27099 - Always treat failure to allocate an RSA key as an unrecoverable
27101 - Update to the March 1 2011 Maxmind GeoLite Country database.
27103 o Minor features (log subsystem):
27104 - Add documentation for configuring logging at different severities in
27105 different log domains. We've had this feature since 0.2.1.1-alpha,
27106 but for some reason it never made it into the manpage. Fixes
27108 - Make it simpler to specify "All log domains except for A and B".
27109 Previously you needed to say "[*,~A,~B]". Now you can just say
27111 - Add a "LogMessageDomains 1" option to include the domains of log
27112 messages along with the messages. Without this, there's no way
27113 to use log domains without reading the source or doing a lot
27116 o Packaging changes:
27117 - Stop shipping the Tor specs files and development proposal documents
27118 in the tarball. They are now in a separate git repository at
27119 git://git.torproject.org/torspec.git
27122 Changes in version 0.2.1.30 - 2011-02-23
27123 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
27124 change is a slight tweak to Tor's TLS handshake that makes relays
27125 and bridges that run this new version reachable from Iran again.
27126 We don't expect this tweak will win the arms race long-term, but it
27127 buys us time until we roll out a better solution.
27130 - Stop sending a CLOCK_SKEW controller status event whenever
27131 we fetch directory information from a relay that has a wrong clock.
27132 Instead, only inform the controller when it's a trusted authority
27133 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
27134 the rest of bug 1074.
27135 - Fix a bounds-checking error that could allow an attacker to
27136 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
27137 Found by "piebeer".
27138 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
27139 Tor would ignore their RelayBandwidthBurst setting,
27140 potentially using more bandwidth than expected. Bugfix on
27141 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
27142 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
27143 hidserv" in her torrc. The 'hidserv' argument never controlled
27144 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
27147 - Adjust our TLS Diffie-Hellman parameters to match those used by
27149 - Update to the February 1 2011 Maxmind GeoLite Country database.
27152 - Check for and reject overly long directory certificates and
27153 directory tokens before they have a chance to hit any assertions.
27154 Bugfix on 0.2.1.28. Found by "doorss".
27155 - Bring the logic that gathers routerinfos and assesses the
27156 acceptability of circuits into line. This prevents a Tor OP from
27157 getting locked in a cycle of choosing its local OR as an exit for a
27158 path (due to a .exit request) and then rejecting the circuit because
27159 its OR is not listed yet. It also prevents Tor clients from using an
27160 OR running in the same instance as an exit (due to a .exit request)
27161 if the OR does not meet the same requirements expected of an OR
27162 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
27164 o Packaging changes:
27165 - Stop shipping the Tor specs files and development proposal documents
27166 in the tarball. They are now in a separate git repository at
27167 git://git.torproject.org/torspec.git
27168 - Do not include Git version tags as though they are SVN tags when
27169 generating a tarball from inside a repository that has switched
27170 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
27173 Changes in version 0.2.2.22-alpha - 2011-01-25
27174 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
27175 main other change is a slight tweak to Tor's TLS handshake that makes
27176 relays and bridges that run this new version reachable from Iran again.
27177 We don't expect this tweak will win the arms race long-term, but it
27178 will buy us a bit more time until we roll out a better solution.
27181 - Fix a bounds-checking error that could allow an attacker to
27182 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
27183 Found by "piebeer".
27184 - Don't assert when changing from bridge to relay or vice versa
27185 via the controller. The assert happened because we didn't properly
27186 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
27187 bug 2433. Reported by bastik.
27190 - Adjust our TLS Diffie-Hellman parameters to match those used by
27192 - Provide a log message stating which geoip file we're parsing
27193 instead of just stating that we're parsing the geoip file.
27194 Implements ticket 2432.
27197 - Check for and reject overly long directory certificates and
27198 directory tokens before they have a chance to hit any assertions.
27199 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
27202 Changes in version 0.2.2.21-alpha - 2011-01-15
27203 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
27204 continues our recent code security audit work. The main fix resolves
27205 a remote heap overflow vulnerability that can allow remote code
27206 execution (CVE-2011-0427). Other fixes address a variety of assert
27207 and crash bugs, most of which we think are hard to exploit remotely.
27209 o Major bugfixes (security), also included in 0.2.1.29:
27210 - Fix a heap overflow bug where an adversary could cause heap
27211 corruption. This bug probably allows remote code execution
27212 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
27214 - Prevent a denial-of-service attack by disallowing any
27215 zlib-compressed data whose compression factor is implausibly
27216 high. Fixes part of bug 2324; reported by "doorss".
27217 - Zero out a few more keys in memory before freeing them. Fixes
27218 bug 2384 and part of bug 2385. These key instances found by
27219 "cypherpunks", based on Andrew Case's report about being able
27220 to find sensitive data in Tor's memory space if you have enough
27221 permissions. Bugfix on 0.0.2pre9.
27223 o Major bugfixes (crashes), also included in 0.2.1.29:
27224 - Prevent calls to Libevent from inside Libevent log handlers.
27225 This had potential to cause a nasty set of crashes, especially
27226 if running Libevent with debug logging enabled, and running
27227 Tor with a controller watching for low-severity log messages.
27228 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
27229 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
27230 underflow errors there too. Fixes the other part of bug 2324.
27231 - Fix a bug where we would assert if we ever had a
27232 cached-descriptors.new file (or another file read directly into
27233 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
27234 on 0.2.1.25. Found by doorss.
27235 - Fix some potential asserts and parsing issues with grossly
27236 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
27239 o Minor bugfixes (other), also included in 0.2.1.29:
27240 - Fix a bug with handling misformed replies to reverse DNS lookup
27241 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
27242 bug reported by doorss.
27243 - Fix compilation on mingw when a pthreads compatibility library
27244 has been installed. (We don't want to use it, so we shouldn't
27245 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
27246 - Fix a bug where we would declare that we had run out of virtual
27247 addresses when the address space was only half-exhausted. Bugfix
27249 - Correctly handle the case where AutomapHostsOnResolve is set but
27250 no virtual addresses are available. Fixes bug 2328; bugfix on
27251 0.1.2.1-alpha. Bug found by doorss.
27252 - Correctly handle wrapping around when we run out of virtual
27253 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
27255 o Minor features, also included in 0.2.1.29:
27256 - Update to the January 1 2011 Maxmind GeoLite Country database.
27257 - Introduce output size checks on all of our decryption functions.
27259 o Build changes, also included in 0.2.1.29:
27260 - Tor does not build packages correctly with Automake 1.6 and earlier;
27261 added a check to Makefile.am to make sure that we're building with
27262 Automake 1.7 or later.
27263 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
27264 because we built it with a too-old version of automake. Thus that
27265 release broke ./configure --enable-openbsd-malloc, which is popular
27266 among really fast exit relays on Linux.
27268 o Major bugfixes, new in 0.2.2.21-alpha:
27269 - Prevent crash/heap corruption when the cbtnummodes consensus
27270 parameter is set to 0 or large values. Fixes bug 2317; bugfix
27273 o Major features, new in 0.2.2.21-alpha:
27274 - Introduce minimum/maximum values that clients will believe
27275 from the consensus. Now we'll have a better chance to avoid crashes
27276 or worse when a consensus param has a weird value.
27278 o Minor features, new in 0.2.2.21-alpha:
27279 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
27280 used on bridges, and it makes bridge scanning somewhat easier.
27281 - If writing the state file to disk fails, wait up to an hour before
27282 retrying again, rather than trying again each second. Fixes bug
27283 2346; bugfix on Tor 0.1.1.3-alpha.
27284 - Make Libevent log messages get delivered to controllers later,
27285 and not from inside the Libevent log handler. This prevents unsafe
27286 reentrant Libevent calls while still letting the log messages
27288 - Detect platforms that brokenly use a signed size_t, and refuse to
27289 build there. Found and analyzed by doorss and rransom.
27290 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
27293 o Minor bugfixes, new in 0.2.2.21-alpha:
27294 - Handle SOCKS messages longer than 128 bytes long correctly, rather
27295 than waiting forever for them to finish. Fixes bug 2330; bugfix
27296 on 0.2.0.16-alpha. Found by doorss.
27297 - Add assertions to check for overflow in arguments to
27298 base32_encode() and base32_decode(); fix a signed-unsigned
27299 comparison there too. These bugs are not actually reachable in Tor,
27300 but it's good to prevent future errors too. Found by doorss.
27301 - Correctly detect failures to create DNS requests when using Libevent
27302 versions before v2. (Before Libevent 2, we used our own evdns
27303 implementation. Its return values for Libevent's evdns_resolve_*()
27304 functions are not consistent with those from Libevent.) Fixes bug
27305 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
27307 o Documentation, new in 0.2.2.21-alpha:
27308 - Document the default socks host and port (127.0.0.1:9050) for
27312 Changes in version 0.2.1.29 - 2011-01-15
27313 Tor 0.2.1.29 continues our recent code security audit work. The main
27314 fix resolves a remote heap overflow vulnerability that can allow remote
27315 code execution. Other fixes address a variety of assert and crash bugs,
27316 most of which we think are hard to exploit remotely.
27318 o Major bugfixes (security):
27319 - Fix a heap overflow bug where an adversary could cause heap
27320 corruption. This bug probably allows remote code execution
27321 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
27323 - Prevent a denial-of-service attack by disallowing any
27324 zlib-compressed data whose compression factor is implausibly
27325 high. Fixes part of bug 2324; reported by "doorss".
27326 - Zero out a few more keys in memory before freeing them. Fixes
27327 bug 2384 and part of bug 2385. These key instances found by
27328 "cypherpunks", based on Andrew Case's report about being able
27329 to find sensitive data in Tor's memory space if you have enough
27330 permissions. Bugfix on 0.0.2pre9.
27332 o Major bugfixes (crashes):
27333 - Prevent calls to Libevent from inside Libevent log handlers.
27334 This had potential to cause a nasty set of crashes, especially
27335 if running Libevent with debug logging enabled, and running
27336 Tor with a controller watching for low-severity log messages.
27337 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
27338 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
27339 underflow errors there too. Fixes the other part of bug 2324.
27340 - Fix a bug where we would assert if we ever had a
27341 cached-descriptors.new file (or another file read directly into
27342 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
27343 on 0.2.1.25. Found by doorss.
27344 - Fix some potential asserts and parsing issues with grossly
27345 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
27348 o Minor bugfixes (other):
27349 - Fix a bug with handling misformed replies to reverse DNS lookup
27350 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
27351 bug reported by doorss.
27352 - Fix compilation on mingw when a pthreads compatibility library
27353 has been installed. (We don't want to use it, so we shouldn't
27354 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
27355 - Fix a bug where we would declare that we had run out of virtual
27356 addresses when the address space was only half-exhausted. Bugfix
27358 - Correctly handle the case where AutomapHostsOnResolve is set but
27359 no virtual addresses are available. Fixes bug 2328; bugfix on
27360 0.1.2.1-alpha. Bug found by doorss.
27361 - Correctly handle wrapping around to when we run out of virtual
27362 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
27363 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
27364 because we built it with a too-old version of automake. Thus that
27365 release broke ./configure --enable-openbsd-malloc, which is popular
27366 among really fast exit relays on Linux.
27369 - Update to the January 1 2011 Maxmind GeoLite Country database.
27370 - Introduce output size checks on all of our decryption functions.
27373 - Tor does not build packages correctly with Automake 1.6 and earlier;
27374 added a check to Makefile.am to make sure that we're building with
27375 Automake 1.7 or later.
27378 Changes in version 0.2.2.20-alpha - 2010-12-17
27379 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
27380 exploitable bugs. We also fix a variety of other significant bugs,
27381 change the IP address for one of our directory authorities, and update
27382 the minimum version that Tor relays must run to join the network.
27385 - Fix a remotely exploitable bug that could be used to crash instances
27386 of Tor remotely by overflowing on the heap. Remote-code execution
27387 hasn't been confirmed, but can't be ruled out. Everyone should
27388 upgrade. Bugfix on the 0.1.1 series and later.
27389 - Fix a bug that could break accounting on 64-bit systems with large
27390 time_t values, making them hibernate for impossibly long intervals.
27391 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
27392 - Fix a logic error in directory_fetches_from_authorities() that
27393 would cause all _non_-exits refusing single-hop-like circuits
27394 to fetch from authorities, when we wanted to have _exits_ fetch
27395 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
27397 - Fix a stream fairness bug that would cause newer streams on a given
27398 circuit to get preference when reading bytes from the origin or
27399 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
27400 introduced before the first Tor release, in svn revision r152.
27402 o Directory authority changes:
27403 - Change IP address and ports for gabelmoo (v3 directory authority).
27406 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
27407 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
27408 - Fix an off-by-one error in calculating some controller command
27409 argument lengths. Fortunately, this mistake is harmless since
27410 the controller code does redundant NUL termination too. Found by
27411 boboper. Bugfix on 0.1.1.1-alpha.
27412 - Do not dereference NULL if a bridge fails to build its
27413 extra-info descriptor. Found by an anonymous commenter on
27414 Trac. Bugfix on 0.2.2.19-alpha.
27417 - Update to the December 1 2010 Maxmind GeoLite Country database.
27418 - Directory authorities now reject relays running any versions of
27419 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
27420 known bugs that keep RELAY_EARLY cells from working on rendezvous
27421 circuits. Followup to fix for bug 2081.
27422 - Directory authorities now reject relays running any version of Tor
27423 older than 0.2.0.26-rc. That version is the earliest that fetches
27424 current directory information correctly. Fixes bug 2156.
27425 - Report only the top 10 ports in exit-port stats in order not to
27426 exceed the maximum extra-info descriptor length of 50 KB. Implements
27430 Changes in version 0.2.1.28 - 2010-12-17
27431 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
27432 exploitable bugs. We also took this opportunity to change the IP address
27433 for one of our directory authorities, and to update the geoip database
27437 - Fix a remotely exploitable bug that could be used to crash instances
27438 of Tor remotely by overflowing on the heap. Remote-code execution
27439 hasn't been confirmed, but can't be ruled out. Everyone should
27440 upgrade. Bugfix on the 0.1.1 series and later.
27442 o Directory authority changes:
27443 - Change IP address and ports for gabelmoo (v3 directory authority).
27446 - Update to the December 1 2010 Maxmind GeoLite Country database.
27449 Changes in version 0.2.1.27 - 2010-11-23
27450 Yet another OpenSSL security patch broke its compatibility with Tor:
27451 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
27452 also took this opportunity to fix several crash bugs, integrate a new
27453 directory authority, and update the bundled GeoIP database.
27456 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
27457 No longer set the tlsext_host_name extension on server SSL objects;
27458 but continue to set it on client SSL objects. Our goal in setting
27459 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
27460 bugfix on 0.2.1.1-alpha.
27461 - Do not log messages to the controller while shrinking buffer
27462 freelists. Doing so would sometimes make the controller connection
27463 try to allocate a buffer chunk, which would mess up the internals
27464 of the freelist and cause an assertion failure. Fixes bug 1125;
27465 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
27466 - Learn our external IP address when we're a relay or bridge, even if
27467 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
27468 where we introduced bridge relays that don't need to publish to
27469 be useful. Fixes bug 2050.
27470 - Do even more to reject (and not just ignore) annotations on
27471 router descriptors received anywhere but from the cache. Previously
27472 we would ignore such annotations at first, but cache them to disk
27473 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
27474 - When you're using bridges and your network goes away and your
27475 bridges get marked as down, recover when you attempt a new socks
27476 connection (if the network is back), rather than waiting up to an
27477 hour to try fetching new descriptors for your bridges. Bugfix on
27478 0.2.0.3-alpha; fixes bug 1981.
27481 - Move to the November 2010 Maxmind GeoLite country db (rather
27482 than the June 2009 ip-to-country GeoIP db) for our statistics that
27483 count how many users relays are seeing from each country. Now we'll
27484 have more accurate data, especially for many African countries.
27486 o New directory authorities:
27487 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
27491 - Fix an assertion failure that could occur in directory caches or
27492 bridge users when using a very short voting interval on a testing
27493 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
27495 - Enforce multiplicity rules when parsing annotations. Bugfix on
27496 0.2.0.8-alpha. Found by piebeer.
27497 - Allow handshaking OR connections to take a full KeepalivePeriod
27498 seconds to handshake. Previously, we would close them after
27499 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
27500 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
27502 - When building with --enable-gcc-warnings on OpenBSD, disable
27503 warnings in system headers. This makes --enable-gcc-warnings
27504 pass on OpenBSD 4.8.
27507 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
27508 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
27509 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
27510 Servers can start sending this code when enough clients recognize
27511 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
27512 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
27513 Patch from mingw-san.
27516 - Remove the old debian/ directory from the main Tor distribution.
27517 The official Tor-for-debian git repository lives at the URL
27518 https://git.torproject.org/debian/tor.git
27519 - Stop shipping the old doc/website/ directory in the tarball. We
27520 changed the website format in late 2010, and what we shipped in
27521 0.2.1.26 really wasn't that useful anyway.
27524 Changes in version 0.2.2.19-alpha - 2010-11-22
27525 Yet another OpenSSL security patch broke its compatibility with Tor:
27526 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
27529 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
27530 No longer set the tlsext_host_name extension on server SSL objects;
27531 but continue to set it on client SSL objects. Our goal in setting
27532 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
27533 bugfix on 0.2.1.1-alpha.
27536 - Try harder not to exceed the maximum length of 50 KB when writing
27537 statistics to extra-info descriptors. This bug was triggered by very
27538 fast relays reporting exit-port, entry, and dirreq statistics.
27539 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
27540 - Publish a router descriptor even if generating an extra-info
27541 descriptor fails. Previously we would not publish a router
27542 descriptor without an extra-info descriptor; this can cause fast
27543 exit relays collecting exit-port statistics to drop from the
27544 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
27547 Changes in version 0.2.2.18-alpha - 2010-11-16
27548 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
27549 us lately, makes unpublished bridge relays able to detect their IP
27550 address, and fixes a wide variety of other bugs to get us much closer
27551 to a stable release.
27554 - Do even more to reject (and not just ignore) annotations on
27555 router descriptors received anywhere but from the cache. Previously
27556 we would ignore such annotations at first, but cache them to disk
27557 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
27558 - Do not log messages to the controller while shrinking buffer
27559 freelists. Doing so would sometimes make the controller connection
27560 try to allocate a buffer chunk, which would mess up the internals
27561 of the freelist and cause an assertion failure. Fixes bug 1125;
27562 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
27563 - Learn our external IP address when we're a relay or bridge, even if
27564 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
27565 where we introduced bridge relays that don't need to publish to
27566 be useful. Fixes bug 2050.
27567 - Maintain separate TLS contexts and certificates for incoming and
27568 outgoing connections in bridge relays. Previously we would use the
27569 same TLS contexts and certs for incoming and outgoing connections.
27570 Bugfix on 0.2.0.3-alpha; addresses bug 988.
27571 - Maintain separate identity keys for incoming and outgoing TLS
27572 contexts in bridge relays. Previously we would use the same
27573 identity keys for incoming and outgoing TLS contexts. Bugfix on
27574 0.2.0.3-alpha; addresses the other half of bug 988.
27575 - Avoid an assertion failure when we as an authority receive a
27576 duplicate upload of a router descriptor that we already have,
27577 but which we previously considered an obsolete descriptor.
27578 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
27579 - Avoid a crash bug triggered by looking at a dangling pointer while
27580 setting the network status consensus. Found by Robert Ransom.
27581 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
27582 - Fix a logic error where servers that _didn't_ act as exits would
27583 try to keep their server lists more aggressively up to date than
27584 exits, when it was supposed to be the other way around. Bugfix
27587 o Minor bugfixes (on Tor 0.2.1.x and earlier):
27588 - When we're trying to guess whether we know our IP address as
27589 a relay, we would log various ways that we failed to guess
27590 our address, but never log that we ended up guessing it
27591 successfully. Now add a log line to help confused and anxious
27592 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
27593 - Bring the logic that gathers routerinfos and assesses the
27594 acceptability of circuits into line. This prevents a Tor OP from
27595 getting locked in a cycle of choosing its local OR as an exit for a
27596 path (due to a .exit request) and then rejecting the circuit because
27597 its OR is not listed yet. It also prevents Tor clients from using an
27598 OR running in the same instance as an exit (due to a .exit request)
27599 if the OR does not meet the same requirements expected of an OR
27600 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
27601 - Correctly describe errors that occur when generating a TLS object.
27602 Previously we would attribute them to a failure while generating a
27603 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
27605 - Enforce multiplicity rules when parsing annotations. Bugfix on
27606 0.2.0.8-alpha. Found by piebeer.
27607 - Fix warnings that newer versions of autoconf produced during
27608 ./autogen.sh. These warnings appear to be harmless in our case,
27609 but they were extremely verbose. Fixes bug 2020.
27611 o Minor bugfixes (on Tor 0.2.2.x):
27612 - Enable protection of small arrays whenever we build with gcc
27613 hardening features, not only when also building with warnings
27614 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
27617 - Make hidden services work better in private Tor networks by not
27618 requiring any uptime to join the hidden service descriptor
27619 DHT. Implements ticket 2088.
27620 - Rate-limit the "your application is giving Tor only an IP address"
27621 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
27622 - When AllowSingleHopExits is set, print a warning to explain to the
27623 relay operator why most clients are avoiding her relay.
27624 - Update to the November 1 2010 Maxmind GeoLite Country database.
27626 o Code simplifications and refactoring:
27627 - When we fixed bug 1038 we had to put in a restriction not to send
27628 RELAY_EARLY cells on rend circuits. This was necessary as long
27629 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
27630 active. Now remove this obsolete check. Resolves bug 2081.
27631 - Some options used different conventions for uppercasing of acronyms
27632 when comparing manpage and source. Fix those in favor of the
27633 manpage, as it makes sense to capitalize acronyms.
27634 - Remove the torrc.complete file. It hasn't been kept up to date
27635 and users will have better luck checking out the manpage.
27636 - Remove the obsolete "NoPublish" option; it has been flagged
27637 as obsolete and has produced a warning since 0.1.1.18-rc.
27638 - Remove everything related to building the expert bundle for OS X.
27639 It has confused many users, doesn't work right on OS X 10.6,
27640 and is hard to get rid of once installed. Resolves bug 1274.
27643 Changes in version 0.2.2.17-alpha - 2010-09-30
27644 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
27645 to use one-hop circuits (which can put the exit relays at higher risk,
27646 plus unbalance the network); fixes a big bug in bandwidth accounting
27647 for relays that want to limit their monthly bandwidth use; fixes a
27648 big pile of bugs in how clients tolerate temporary network failure;
27649 and makes our adaptive circuit build timeout feature (which improves
27650 client performance if your network is fast while not breaking things
27651 if your network is slow) better handle bad networks.
27654 - Exit relays now try harder to block exit attempts from unknown
27655 relays, to make it harder for people to use them as one-hop proxies
27656 a la tortunnel. Controlled by the refuseunknownexits consensus
27657 parameter (currently enabled), or you can override it on your
27658 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
27660 o Major bugfixes (0.2.1.x and earlier):
27661 - Fix a bug in bandwidth accounting that could make us use twice
27662 the intended bandwidth when our interval start changes due to
27663 daylight saving time. Now we tolerate skew in stored vs computed
27664 interval starts: if the start of the period changes by no more than
27665 50% of the period's duration, we remember bytes that we transferred
27666 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
27667 - Always search the Windows system directory for system DLLs, and
27668 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
27669 - When you're using bridges and your network goes away and your
27670 bridges get marked as down, recover when you attempt a new socks
27671 connection (if the network is back), rather than waiting up to an
27672 hour to try fetching new descriptors for your bridges. Bugfix on
27673 0.2.0.3-alpha; fixes bug 1981.
27675 o Major bugfixes (on 0.2.2.x):
27676 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
27678 - Fix a segfault that could happen when operating a bridge relay with
27679 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
27680 - The consensus bandwidth-weights (used by clients to choose fast
27681 relays) entered an unexpected edge case in September where
27682 Exits were much scarcer than Guards, resulting in bad weight
27683 recommendations. Now we compute them using new constraints that
27684 should succeed in all cases. Also alter directory authorities to
27685 not include the bandwidth-weights line if they fail to produce
27686 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
27687 - When weighting bridges during path selection, we used to trust
27688 the bandwidths they provided in their descriptor, only capping them
27689 at 10MB/s. This turned out to be problematic for two reasons:
27690 Bridges could claim to handle a lot more traffic then they
27691 actually would, thus making more clients pick them and have a
27692 pretty effective DoS attack. The other issue is that new bridges
27693 that might not have a good estimate for their bw capacity yet
27694 would not get used at all unless no other bridges are available
27695 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
27697 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
27698 - Ignore cannibalized circuits when recording circuit build times.
27699 This should provide for a minor performance improvement for hidden
27700 service users using 0.2.2.14-alpha, and should remove two spurious
27701 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
27702 - Simplify the logic that causes us to decide if the network is
27703 unavailable for purposes of recording circuit build times. If we
27704 receive no cells whatsoever for the entire duration of a circuit's
27705 full measured lifetime, the network is probably down. Also ignore
27706 one-hop directory fetching circuit timeouts when calculating our
27707 circuit build times. These changes should hopefully reduce the
27708 cases where we see ridiculous circuit build timeouts for people
27709 with spotty wireless connections. Fixes part of bug 1772; bugfix
27711 - Prevent the circuit build timeout from becoming larger than
27712 the maximum build time we have ever seen. Also, prevent the time
27713 period for measurement circuits from becoming larger than twice that
27714 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
27717 - When we run out of directory information such that we can't build
27718 circuits, but then get enough that we can build circuits, log when
27719 we actually construct a circuit, so the user has a better chance of
27720 knowing what's going on. Fixes bug 1362.
27721 - Be more generous with how much bandwidth we'd use up (with
27722 accounting enabled) before entering "soft hibernation". Previously,
27723 we'd refuse new connections and circuits once we'd used up 95% of
27724 our allotment. Now, we use up 95% of our allotment, AND make sure
27725 that we have no more than 500MB (or 3 hours of expected traffic,
27726 whichever is lower) remaining before we enter soft hibernation.
27727 - If we've configured EntryNodes and our network goes away and/or all
27728 our entrynodes get marked down, optimistically retry them all when
27729 a new socks application request appears. Fixes bug 1882.
27730 - Add some more defensive programming for architectures that can't
27731 handle unaligned integer accesses. We don't know of any actual bugs
27732 right now, but that's the best time to fix them. Fixes bug 1943.
27733 - Support line continuations in the torrc config file. If a line
27734 ends with a single backslash character, the newline is ignored, and
27735 the configuration value is treated as continuing on the next line.
27738 o Minor bugfixes (on 0.2.1.x and earlier):
27739 - For bandwidth accounting, calculate our expected bandwidth rate
27740 based on the time during which we were active and not in
27741 soft-hibernation during the last interval. Previously, we were
27742 also considering the time spent in soft-hibernation. If this
27743 was a long time, we would wind up underestimating our bandwidth
27744 by a lot, and skewing our wakeup time towards the start of the
27745 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
27747 o Minor bugfixes (on 0.2.2.x):
27748 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
27749 which were disabled by the circuit build timeout changes in
27750 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
27751 - Make sure we don't warn about missing bandwidth weights when
27752 choosing bridges or other relays not in the consensus. Bugfix on
27753 0.2.2.10-alpha; fixes bug 1805.
27754 - In our logs, do not double-report signatures from unrecognized
27755 authorities both as "from unknown authority" and "not
27756 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
27759 Changes in version 0.2.2.16-alpha - 2010-09-17
27760 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
27761 evident at exit relays), and also continues to resolve all the little
27762 bugs that have been filling up trac lately.
27764 o Major bugfixes (stream-level fairness):
27765 - When receiving a circuit-level SENDME for a blocked circuit, try
27766 to package cells fairly from all the streams that had previously
27767 been blocked on that circuit. Previously, we had started with the
27768 oldest stream, and allowed each stream to potentially exhaust
27769 the circuit's package window. This gave older streams on any
27770 given circuit priority over newer ones. Fixes bug 1937. Detected
27771 originally by Camilo Viecco. This bug was introduced before the
27772 first Tor release, in svn commit r152: it is the new winner of
27773 the longest-lived bug prize.
27774 - When the exit relay got a circuit-level sendme cell, it started
27775 reading on the exit streams, even if had 500 cells queued in the
27776 circuit queue already, so the circuit queue just grew and grew in
27777 some cases. We fix this by not re-enabling reading on receipt of a
27778 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
27779 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
27781 - Newly created streams were allowed to read cells onto circuits,
27782 even if the circuit's cell queue was blocked and waiting to drain.
27783 This created potential unfairness, as older streams would be
27784 blocked, but newer streams would gladly fill the queue completely.
27785 We add code to detect this situation and prevent any stream from
27786 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
27790 - Update to the September 1 2010 Maxmind GeoLite Country database.
27791 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
27792 not. This would lead to a cookie that is still not group readable.
27793 Closes bug 1843. Suggested by katmagic.
27794 - When logging a rate-limited warning, we now mention how many messages
27795 got suppressed since the last warning.
27796 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
27797 do individual connection-level rate limiting of clients. The torrc
27798 config options with the same names trump the consensus params, if
27799 both are present. Replaces the old "bwconnrate" and "bwconnburst"
27800 consensus params which were broken from 0.2.2.7-alpha through
27801 0.2.2.14-alpha. Closes bug 1947.
27802 - When a router changes IP address or port, authorities now launch
27803 a new reachability test for it. Implements ticket 1899.
27804 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
27805 2 no signature, 4 required" messages about consensus signatures
27806 easier to read, and make sure they get logged at the same severity
27807 as the messages explaining which keys are which. Fixes bug 1290.
27808 - Don't warn when we have a consensus that we can't verify because
27809 of missing certificates, unless those certificates are ones
27810 that we have been trying and failing to download. Fixes bug 1145.
27811 - If you configure your bridge with a known identity fingerprint,
27812 and the bridge authority is unreachable (as it is in at least
27813 one country now), fall back to directly requesting the descriptor
27814 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
27816 - When building with --enable-gcc-warnings on OpenBSD, disable
27817 warnings in system headers. This makes --enable-gcc-warnings
27818 pass on OpenBSD 4.8.
27820 o Minor bugfixes (on 0.2.1.x and earlier):
27821 - Authorities will now attempt to download consensuses if their
27822 own efforts to make a live consensus have failed. This change
27823 means authorities that restart will fetch a valid consensus, and
27824 it means authorities that didn't agree with the current consensus
27825 will still fetch and serve it if it has enough signatures. Bugfix
27826 on 0.2.0.9-alpha; fixes bug 1300.
27827 - Ensure DNS requests launched by "RESOLVE" commands from the
27828 controller respect the __LeaveStreamsUnattached setconf options. The
27829 same goes for requests launched via DNSPort or transparent
27830 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
27831 - Allow handshaking OR connections to take a full KeepalivePeriod
27832 seconds to handshake. Previously, we would close them after
27833 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
27834 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
27836 - Rate-limit "Failed to hand off onionskin" warnings.
27837 - Never relay a cell for a circuit we have already destroyed.
27838 Between marking a circuit as closeable and finally closing it,
27839 it may have been possible for a few queued cells to get relayed,
27840 even though they would have been immediately dropped by the next
27841 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
27842 - Never queue a cell for a circuit that's already been marked
27844 - Never vote for a server as "Running" if we have a descriptor for
27845 it claiming to be hibernating, and that descriptor was published
27846 more recently than our last contact with the server. Bugfix on
27847 0.2.0.3-alpha; fixes bug 911.
27848 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
27851 o Minor bugfixes (on 0.2.2.x):
27852 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
27853 down if a directory fetch fails and you've configured either
27854 bridges or EntryNodes. The intent was to mark the relay as down
27855 _unless_ you're using bridges or EntryNodes, since if you are
27856 then you could quickly run out of entry points.
27857 - Fix the Windows directory-listing code. A bug introduced in
27858 0.2.2.14-alpha could make Windows directory servers forget to load
27859 some of their cached v2 networkstatus files.
27860 - Really allow clients to use relays as bridges. Fixes bug 1776;
27861 bugfix on 0.2.2.15-alpha.
27862 - Demote a warn to info that happens when the CellStatistics option
27863 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
27864 Reported by Moritz Bartl.
27865 - On Windows, build correctly either with or without Unicode support.
27866 This is necessary so that Tor can support fringe platforms like
27867 Windows 98 (which has no Unicode), or Windows CE (which has no
27868 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
27871 - Add a unit test for cross-platform directory-listing code.
27874 Changes in version 0.2.2.15-alpha - 2010-08-18
27875 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
27876 fixes a variety of other bugs that were preventing performance
27877 experiments from moving forward, fixes several bothersome memory leaks,
27878 and generally closes a lot of smaller bugs that have been filling up
27882 - Stop assigning the HSDir flag to relays that disable their
27883 DirPort (and thus will refuse to answer directory requests). This
27884 fix should dramatically improve the reachability of hidden services:
27885 hidden services and hidden service clients pick six HSDir relays
27886 to store and retrieve the hidden service descriptor, and currently
27887 about half of the HSDir relays will refuse to work. Bugfix on
27888 0.2.0.10-alpha; fixes part of bug 1693.
27889 - The PerConnBWRate and Burst config options, along with the
27890 bwconnrate and bwconnburst consensus params, initialized each conn's
27891 token bucket values only when the connection is established. Now we
27892 update them if the config options change, and update them every time
27893 we get a new consensus. Otherwise we can encounter an ugly edge
27894 case where we initialize an OR conn to client-level bandwidth,
27895 but then later the relay joins the consensus and we leave it
27896 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
27897 - Fix a regression that caused Tor to rebind its ports if it receives
27898 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
27901 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
27902 should give us approximately 40-50% more Guard-flagged nodes,
27903 improving the anonymity the Tor network can provide and also
27904 decreasing the dropoff in throughput that relays experience when
27905 they first get the Guard flag.
27906 - Allow enabling or disabling the *Statistics config options while
27910 - Update to the August 1 2010 Maxmind GeoLite Country database.
27911 - Have the controller interface give a more useful message than
27912 "Internal Error" in response to failed GETINFO requests.
27913 - Warn when the same option is provided more than once in a torrc
27914 file, on the command line, or in a single SETCONF statement, and
27915 the option is one that only accepts a single line. Closes bug 1384.
27916 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
27917 Patch from mingw-san.
27918 - Add support for the country code "{??}" in torrc options like
27919 ExcludeNodes, to indicate all routers of unknown country. Closes
27921 - Relays report the number of bytes spent on answering directory
27922 requests in extra-info descriptors similar to {read,write}-history.
27923 Implements enhancement 1790.
27925 o Minor bugfixes (on 0.2.1.x and earlier):
27926 - Complain if PublishServerDescriptor is given multiple arguments that
27927 include 0 or 1. This configuration will be rejected in the future.
27928 Bugfix on 0.2.0.1-alpha; closes bug 1107.
27929 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
27930 Bugfix on 0.2.0.13-alpha; closes bug 928.
27931 - Change "Application request when we're believed to be offline."
27932 notice to "Application request when we haven't used client
27933 functionality lately.", to clarify that it's not an error. Bugfix
27934 on 0.0.9.3; fixes bug 1222.
27935 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
27936 would return "551 Internal error" rather than "552 Unrecognized key
27937 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
27938 - Users can't configure a regular relay to be their bridge. It didn't
27939 work because when Tor fetched the bridge descriptor, it found
27940 that it already had it, and didn't realize that the purpose of the
27941 descriptor had changed. Now we replace routers with a purpose other
27942 than bridge with bridge descriptors when fetching them. Bugfix on
27943 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
27944 refetch the descriptor with router purpose 'general', disabling
27946 - Fix a rare bug in rend_fn unit tests: we would fail a test when
27947 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
27948 on 0.2.0.10-alpha; fixes bug 1808.
27949 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
27950 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
27951 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
27952 Servers can start sending this code when enough clients recognize
27953 it. Also update the spec to reflect this new reason. Bugfix on
27954 0.1.0.1-rc; fixes part of bug 1793.
27955 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
27956 when we switch from being a public relay to a bridge. Otherwise
27957 there will still be clients that see the relay in their consensus,
27958 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
27960 - Instead of giving an assertion failure on an internal mismatch
27961 on estimated freelist size, just log a BUG warning and try later.
27962 Mitigates but does not fix bug 1125.
27963 - Fix an assertion failure that could occur in caches or bridge users
27964 when using a very short voting interval on a testing network.
27965 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
27967 o Minor bugfixes (on 0.2.2.x):
27968 - Alter directory authorities to always consider Exit-flagged nodes
27969 as potential Guard nodes in their votes. The actual decision to
27970 use Exits as Guards is done in the consensus bandwidth weights.
27971 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
27972 - When the controller is reporting the purpose of circuits that
27973 didn't finish building before the circuit build timeout, it was
27974 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
27975 - Our libevent version parsing code couldn't handle versions like
27976 1.4.14b-stable and incorrectly warned the user about using an
27977 old and broken version of libevent. Treat 1.4.14b-stable like
27978 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
27980 - Don't use substitution references like $(VAR:MOD) when
27981 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
27982 '$(:x)' to 'x' rather than the empty string. This bites us in
27983 doc/ when configured with --disable-asciidoc. Bugfix on
27984 0.2.2.9-alpha; fixes bug 1773.
27985 - Remove a spurious hidden service server-side log notice about
27986 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
27988 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
27990 - Correctly report written bytes on linked connections. Found while
27991 implementing 1790. Bugfix on 0.2.2.4-alpha.
27992 - Fix three memory leaks: one in circuit_build_times_parse_state(),
27993 one in dirvote_add_signatures_to_pending_consensus(), and one every
27994 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
27995 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
27997 o Code simplifications and refactoring:
27998 - Take a first step towards making or.h smaller by splitting out
27999 function definitions for all source files in src/or/. Leave
28000 structures and defines in or.h for now.
28001 - Remove a bunch of unused function declarations as well as a block of
28002 #if 0'd code from the unit tests. Closes bug 1824.
28003 - New unit tests for exit-port history statistics; refactored exit
28004 statistics code to be more easily tested.
28005 - Remove the old debian/ directory from the main Tor distribution.
28006 The official Tor-for-debian git repository lives at the URL
28007 https://git.torproject.org/debian/tor.git
28010 Changes in version 0.2.2.14-alpha - 2010-07-12
28011 Tor 0.2.2.14-alpha greatly improves client-side handling of
28012 circuit build timeouts, which are used to estimate speed and improve
28013 performance. We also move to a much better GeoIP database, port Tor to
28014 Windows CE, introduce new compile flags that improve code security,
28015 add an eighth v3 directory authority, and address a lot of more
28019 - Tor directory authorities no longer crash when started with a
28020 cached-microdesc-consensus file in their data directory. Bugfix
28021 on 0.2.2.6-alpha; fixes bug 1532.
28022 - Treat an unset $HOME like an empty $HOME rather than triggering an
28023 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
28024 - Ignore negative and large circuit build timeout values that can
28025 happen during a suspend or hibernate. These values caused various
28026 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
28027 - Alter calculation of Pareto distribution parameter 'Xm' for
28028 Circuit Build Timeout learning to use the weighted average of the
28029 top N=3 modes (because we have three entry guards). Considering
28030 multiple modes should improve the timeout calculation in some cases,
28031 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
28033 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
28034 right censored distribution model. This approach improves over the
28035 synthetic timeout generation approach that was producing insanely
28036 high timeout values. Now we calculate build timeouts using truncated
28037 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
28038 - Do not close circuits that are under construction when they reach
28039 the circuit build timeout. Instead, leave them building (but do not
28040 use them) for up until the time corresponding to the 95th percentile
28041 on the Pareto CDF or 60 seconds, whichever is greater. This is done
28042 to provide better data for the new Pareto model. This percentile
28043 can be controlled by the consensus.
28046 - Move to the June 2010 Maxmind GeoLite country db (rather than the
28047 June 2009 ip-to-country GeoIP db) for our statistics that count
28048 how many users relays are seeing from each country. Now we have
28049 more accurate data for many African countries.
28050 - Port Tor to build and run correctly on Windows CE systems, using
28051 the wcecompat library. Contributed by Valerio Lupi.
28052 - New "--enable-gcc-hardening" ./configure flag (off by default)
28053 to turn on gcc compile time hardening options. It ensures
28054 that signed ints have defined behavior (-fwrapv), enables
28055 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
28056 with canaries (-fstack-protector-all), turns on ASLR protection if
28057 supported by the kernel (-fPIE, -pie), and adds additional security
28058 related warnings. Verified to work on Mac OS X and Debian Lenny.
28059 - New "--enable-linker-hardening" ./configure flag (off by default)
28060 to turn on ELF specific hardening features (relro, now). This does
28061 not work with Mac OS X or any other non-ELF binary format.
28063 o New directory authorities:
28064 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
28068 - New config option "WarnUnsafeSocks 0" disables the warning that
28069 occurs whenever Tor receives a socks handshake using a version of
28070 the socks protocol that can only provide an IP address (rather
28071 than a hostname). Setups that do DNS locally over Tor are fine,
28072 and we shouldn't spam the logs in that case.
28073 - Convert the HACKING file to asciidoc, and add a few new sections
28074 to it, explaining how we use Git, how we make changelogs, and
28075 what should go in a patch.
28076 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
28077 event, to give information on the current rate of circuit timeouts
28078 over our stored history.
28079 - Add ability to disable circuit build time learning via consensus
28080 parameter and via a LearnCircuitBuildTimeout config option. Also
28081 automatically disable circuit build time calculation if we are
28082 either a AuthoritativeDirectory, or if we fail to write our state
28083 file. Fixes bug 1296.
28084 - More gracefully handle corrupt state files, removing asserts
28085 in favor of saving a backup and resetting state.
28086 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
28090 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
28092 - When a2x fails, mention that the user could disable manpages instead
28093 of trying to fix their asciidoc installation.
28094 - Where available, use Libevent 2.0's periodic timers so that our
28095 once-per-second cleanup code gets called even more closely to
28096 once per second than it would otherwise. Fixes bug 943.
28097 - If you run a bridge that listens on multiple IP addresses, and
28098 some user configures a bridge address that uses a different IP
28099 address than your bridge writes in its router descriptor, and the
28100 user doesn't specify an identity key, their Tor would discard the
28101 descriptor because "it isn't one of our configured bridges", and
28102 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
28103 Bugfix on 0.2.0.3-alpha.
28104 - If OpenSSL fails to make a duplicate of a private or public key, log
28105 an error message and try to exit cleanly. May help with debugging
28106 if bug 1209 ever remanifests.
28107 - Save a couple bytes in memory allocation every time we escape
28108 certain characters in a string. Patch from Florian Zumbiehl.
28109 - Make it explicit that we don't cannibalize one-hop circuits. This
28110 happens in the wild, but doesn't turn out to be a problem because
28111 we fortunately don't use those circuits. Many thanks to outofwords
28112 for the initial analysis and to swissknife who confirmed that
28113 two-hop circuits are actually created.
28114 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
28115 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
28116 - Eliminate a case where a circuit build time warning was displayed
28117 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
28120 Changes in version 0.2.1.26 - 2010-05-02
28121 Tor 0.2.1.26 addresses the recent connection and memory overload
28122 problems we've been seeing on relays, especially relays with their
28123 DirPort open. If your relay has been crashing, or you turned it off
28124 because it used too many resources, give this release a try.
28126 This release also fixes yet another instance of broken OpenSSL libraries
28127 that was causing some relays to drop out of the consensus.
28130 - Teach relays to defend themselves from connection overload. Relays
28131 now close idle circuits early if it looks like they were intended
28132 for directory fetches. Relays are also more aggressive about closing
28133 TLS connections that have no circuits on them. Such circuits are
28134 unlikely to be re-used, and tens of thousands of them were piling
28135 up at the fast relays, causing the relays to run out of sockets
28136 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
28137 their directory fetches over TLS).
28138 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
28139 that claim to be earlier than 0.9.8m, but which have in reality
28140 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
28141 behavior. Possible fix for some cases of bug 1346.
28142 - Directory mirrors were fetching relay descriptors only from v2
28143 directory authorities, rather than v3 authorities like they should.
28144 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
28145 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
28148 - Finally get rid of the deprecated and now harmful notion of "clique
28149 mode", where directory authorities maintain TLS connections to
28153 - In the util/threads test, no longer free the test_mutex before all
28154 worker threads have finished. Bugfix on 0.2.1.6-alpha.
28155 - The master thread could starve the worker threads quite badly on
28156 certain systems, causing them to run only partially in the allowed
28157 window. This resulted in test failures. Now the master thread sleeps
28158 occasionally for a few microseconds while the two worker-threads
28159 compete for the mutex. Bugfix on 0.2.0.1-alpha.
28162 Changes in version 0.2.2.13-alpha - 2010-04-24
28163 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
28164 problems we've been seeing on relays, especially relays with their
28165 DirPort open. If your relay has been crashing, or you turned it off
28166 because it used too many resources, give this release a try.
28169 - Teach relays to defend themselves from connection overload. Relays
28170 now close idle circuits early if it looks like they were intended
28171 for directory fetches. Relays are also more aggressive about closing
28172 TLS connections that have no circuits on them. Such circuits are
28173 unlikely to be re-used, and tens of thousands of them were piling
28174 up at the fast relays, causing the relays to run out of sockets
28175 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
28176 their directory fetches over TLS).
28179 - Finally get rid of the deprecated and now harmful notion of "clique
28180 mode", where directory authorities maintain TLS connections to
28182 - Directory authorities now do an immediate reachability check as soon
28183 as they hear about a new relay. This change should slightly reduce
28184 the time between setting up a relay and getting listed as running
28185 in the consensus. It should also improve the time between setting
28186 up a bridge and seeing use by bridge users.
28187 - Directory authorities no longer launch a TLS connection to every
28188 relay as they startup. Now that we have 2k+ descriptors cached,
28189 the resulting network hiccup is becoming a burden. Besides,
28190 authorities already avoid voting about Running for the first half
28191 hour of their uptime.
28194 Changes in version 0.2.2.12-alpha - 2010-04-20
28195 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
28196 handle and vote on descriptors. It was causing relays to drop out of
28200 - Many relays have been falling out of the consensus lately because
28201 not enough authorities know about their descriptor for them to get
28202 a majority of votes. When we deprecated the v2 directory protocol,
28203 we got rid of the only way that v3 authorities can hear from each
28204 other about other descriptors. Now authorities examine every v3
28205 vote for new descriptors, and fetch them from that authority. Bugfix
28207 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
28208 and a warning in or.h related to bandwidth_weight_rule_t that
28209 prevented clean compile on OS X. Fixes bug 1363; bugfix on
28211 - Fix a segfault on relays when DirReqStatistics is enabled
28212 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
28216 - Demote a confusing TLS warning that relay operators might get when
28217 someone tries to talk to their OrPort. It is neither the operator's
28218 fault nor can they do anything about it. Fixes bug 1364; bugfix
28222 Changes in version 0.2.2.11-alpha - 2010-04-15
28223 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
28224 libraries that was causing some relays to drop out of the consensus.
28227 - Directory mirrors were fetching relay descriptors only from v2
28228 directory authorities, rather than v3 authorities like they should.
28229 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
28230 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
28231 - Fix a parsing error that made every possible value of
28232 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
28233 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
28234 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
28235 about the option without breaking older ones.
28236 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
28237 that claim to be earlier than 0.9.8m, but which have in reality
28238 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
28239 behavior. Possible fix for some cases of bug 1346.
28242 - Experiment with a more aggressive approach to preventing clients
28243 from making one-hop exit streams. Exit relays who want to try it
28244 out can set "RefuseUnknownExits 1" in their torrc, and then look
28245 for "Attempt by %s to open a stream" log messages. Let us know
28247 - Add support for statically linking zlib by specifying
28248 --enable-static-zlib, to go with our support for statically linking
28249 openssl and libevent. Resolves bug 1358.
28252 - Fix a segfault that happens whenever a Tor client that is using
28253 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
28255 - When we cleaned up the contrib/tor-exit-notice.html file, we left
28256 out the first line. Fixes bug 1295.
28257 - When building the manpage from a tarball, we required asciidoc, but
28258 the asciidoc -> roff/html conversion was already done for the
28259 tarball. Make 'make' complain only when we need asciidoc (either
28260 because we're compiling directly from git, or because we altered
28261 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
28262 - When none of the directory authorities vote on any params, Tor
28263 segfaulted when trying to make the consensus from the votes. We
28264 didn't trigger the bug in practice, because authorities do include
28265 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
28268 - In the util/threads test, no longer free the test_mutex before all
28269 worker threads have finished. Bugfix on 0.2.1.6-alpha.
28270 - The master thread could starve the worker threads quite badly on
28271 certain systems, causing them to run only partially in the allowed
28272 window. This resulted in test failures. Now the master thread sleeps
28273 occasionally for a few microseconds while the two worker-threads
28274 compete for the mutex. Bugfix on 0.2.0.1-alpha.
28277 Changes in version 0.2.2.10-alpha - 2010-03-07
28278 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
28279 could prevent relays from guessing their IP address correctly. It also
28280 starts the groundwork for another client-side performance boost, since
28281 currently we're not making efficient use of relays that have both the
28282 Guard flag and the Exit flag.
28285 - Fix a regression from our patch for bug 1244 that caused relays
28286 to guess their IP address incorrectly if they didn't set Address
28287 in their torrc and/or their address fails to resolve. Bugfix on
28288 0.2.2.9-alpha; fixes bug 1269.
28290 o Major features (performance):
28291 - Directory authorities now compute consensus weightings that instruct
28292 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
28293 and no flag. Clients that use these weightings will distribute
28294 network load more evenly across these different relay types. The
28295 weightings are in the consensus so we can change them globally in
28296 the future. Extra thanks to "outofwords" for finding some nasty
28297 security bugs in the first implementation of this feature.
28299 o Minor features (performance):
28300 - Always perform router selections using weighted relay bandwidth,
28301 even if we don't need a high capacity circuit at the time. Non-fast
28302 circuits now only differ from fast ones in that they can use relays
28303 not marked with the Fast flag. This "feature" could turn out to
28304 be a horrible bug; we should investigate more before it goes into
28308 - Allow disabling building of the manpages. Skipping the manpage
28309 speeds up the build considerably.
28311 o Minor bugfixes (on 0.2.2.x):
28312 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
28313 Bugfix on 0.2.2.9-alpha.
28314 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
28315 config option. Bugfix on 0.2.2.7-alpha.
28316 - Ship the asciidoc-helper file in the tarball, so that people can
28317 build from source if they want to, and touching the .1.txt files
28318 doesn't break the build. Bugfix on 0.2.2.9-alpha.
28320 o Minor bugfixes (on 0.2.1.x or earlier):
28321 - Fix a dereference-then-NULL-check sequence when publishing
28322 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
28324 - Fix another dereference-then-NULL-check sequence. Bugfix on
28325 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
28326 - Make sure we treat potentially not NUL-terminated strings correctly.
28327 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
28329 o Code simplifications and refactoring:
28330 - Fix some urls in the exit notice file and make it XHTML1.1 strict
28331 compliant. Based on a patch from Christian Kujau.
28332 - Don't use sed in asciidoc-helper anymore.
28333 - Make the build process fail if asciidoc cannot be found and
28334 building with asciidoc isn't disabled.
28337 Changes in version 0.2.2.9-alpha - 2010-02-22
28338 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
28339 location of a directory authority, and cleans up a bunch of small bugs.
28341 o Directory authority changes:
28342 - Change IP address for dannenberg (v3 directory authority), and
28343 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
28344 service directory authority) from the list.
28347 - Make Tor work again on the latest OS X: when deciding whether to
28348 use strange flags to turn TLS renegotiation on, detect the OpenSSL
28349 version at run-time, not compile time. We need to do this because
28350 Apple doesn't update its dev-tools headers when it updates its
28351 libraries in a security patch.
28352 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
28353 that could happen on 32-bit platforms with 64-bit time_t. Also fix
28354 a memory leak when requesting a hidden service descriptor we've
28355 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
28357 - Authorities could be tricked into giving out the Exit flag to relays
28358 that didn't allow exiting to any ports. This bug could screw
28359 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
28360 1238. Bug discovered by Martin Kowalczyk.
28361 - When freeing a session key, zero it out completely. We only zeroed
28362 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
28363 patched by ekir. Fixes bug 1254.
28366 - Fix static compilation by listing the openssl libraries in the right
28367 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
28368 - Resume handling .exit hostnames in a special way: originally we
28369 stripped the .exit part and used the requested exit relay. In
28370 0.2.2.1-alpha we stopped treating them in any special way, meaning
28371 if you use a .exit address then Tor will pass it on to the exit
28372 relay. Now we reject the .exit stream outright, since that behavior
28373 might be more expected by the user. Found and diagnosed by Scott
28374 Bennett and Downie on or-talk.
28375 - Don't spam the controller with events when we have no file
28376 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
28377 for log messages was already solved from bug 748.)
28378 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
28380 - Make the DNSPort option work with libevent 2.x. Don't alter the
28381 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
28382 - Emit a GUARD DROPPED controller event for a case we missed.
28383 - Make more fields in the controller protocol case-insensitive, since
28384 control-spec.txt said they were.
28385 - Refactor resolve_my_address() to not use gethostbyname() anymore.
28386 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
28387 - Fix a spec conformance issue: the network-status-version token
28388 must be the first token in a v3 consensus or vote. Discovered by
28389 parakeep. Bugfix on 0.2.0.3-alpha.
28391 o Code simplifications and refactoring:
28392 - Generate our manpage and HTML documentation using Asciidoc. This
28393 change should make it easier to maintain the documentation, and
28394 produce nicer HTML.
28395 - Remove the --enable-iphone option. According to reports from Marco
28396 Bonetti, Tor builds fine without any special tweaking on recent
28397 iPhone SDK versions.
28398 - Removed some unnecessary files from the source distribution. The
28399 AUTHORS file has now been merged into the people page on the
28400 website. The roadmaps and design doc can now be found in the
28401 projects directory in svn.
28402 - Enabled various circuit build timeout constants to be controlled
28403 by consensus parameters. Also set better defaults for these
28404 parameters based on experimentation on broadband and simulated
28405 high latency links.
28408 - The 'EXTENDCIRCUIT' control port command can now be used with
28409 a circ id of 0 and no path. This feature will cause Tor to build
28410 a new 'fast' general purpose circuit using its own path selection
28412 - Added a BUILDTIMEOUT_SET controller event to describe changes
28413 to the circuit build timeout.
28414 - Future-proof the controller protocol a bit by ignoring keyword
28415 arguments we do not recognize.
28416 - Expand homedirs passed to tor-checkkey. This should silence a
28417 coverity complaint about passing a user-supplied string into
28418 open() without checking it.
28421 Changes in version 0.2.1.25 - 2010-03-16
28422 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
28423 prevent relays from guessing their IP address correctly. It also fixes
28424 several minor potential security bugs.
28427 - Fix a regression from our patch for bug 1244 that caused relays
28428 to guess their IP address incorrectly if they didn't set Address
28429 in their torrc and/or their address fails to resolve. Bugfix on
28430 0.2.1.23; fixes bug 1269.
28431 - When freeing a session key, zero it out completely. We only zeroed
28432 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
28433 patched by ekir. Fixes bug 1254.
28436 - Fix a dereference-then-NULL-check sequence when publishing
28437 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
28439 - Fix another dereference-then-NULL-check sequence. Bugfix on
28440 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
28441 - Make sure we treat potentially not NUL-terminated strings correctly.
28442 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
28446 Changes in version 0.2.1.24 - 2010-02-21
28447 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
28451 - Work correctly out-of-the-box with even more vendor-patched versions
28452 of OpenSSL. In particular, make it so Debian and OS X don't need
28453 customized patches to run/build.
28456 Changes in version 0.2.1.23 - 2010-02-13
28457 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
28458 again on the latest OS X, and updates the location of a directory
28461 o Major bugfixes (performance):
28462 - We were selecting our guards uniformly at random, and then weighting
28463 which of our guards we'd use uniformly at random. This imbalance
28464 meant that Tor clients were severely limited on throughput (and
28465 probably latency too) by the first hop in their circuit. Now we
28466 select guards weighted by currently advertised bandwidth. We also
28467 automatically discard guards picked using the old algorithm. Fixes
28468 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
28471 - Make Tor work again on the latest OS X: when deciding whether to
28472 use strange flags to turn TLS renegotiation on, detect the OpenSSL
28473 version at run-time, not compile time. We need to do this because
28474 Apple doesn't update its dev-tools headers when it updates its
28475 libraries in a security patch.
28476 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
28477 that could happen on 32-bit platforms with 64-bit time_t. Also fix
28478 a memory leak when requesting a hidden service descriptor we've
28479 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
28482 o Directory authority changes:
28483 - Change IP address for dannenberg (v3 directory authority), and
28484 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
28485 service directory authority) from the list.
28488 - Refactor resolve_my_address() to not use gethostbyname() anymore.
28489 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
28492 - Avoid a mad rush at the beginning of each month when each client
28493 rotates half of its guards. Instead we spread the rotation out
28494 throughout the month, but we still avoid leaving a precise timestamp
28495 in the state file about when we first picked the guard. Improves
28496 over the behavior introduced in 0.1.2.17.
28499 Changes in version 0.2.2.8-alpha - 2010-01-26
28500 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
28501 causing bridge relays to disappear. If you're running a bridge,
28505 - Fix a memory corruption bug on bridges that occurred during the
28506 inclusion of stats data in extra-info descriptors. Also fix the
28507 interface for geoip_get_bridge_stats* to prevent similar bugs in
28508 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
28509 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
28512 - Ignore OutboundBindAddress when connecting to localhost.
28513 Connections to localhost need to come _from_ localhost, or else
28514 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
28518 Changes in version 0.2.2.7-alpha - 2010-01-19
28519 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
28520 as laying the groundwork for further relay-side performance fixes. It
28521 also starts cleaning up client behavior with respect to the EntryNodes,
28522 ExitNodes, and StrictNodes config options.
28524 This release also rotates two directory authority keys, due to a
28525 security breach of some of the Torproject servers.
28527 o Directory authority changes:
28528 - Rotate keys (both v3 identity and relay identity) for moria1
28531 o Major features (performance):
28532 - We were selecting our guards uniformly at random, and then weighting
28533 which of our guards we'd use uniformly at random. This imbalance
28534 meant that Tor clients were severely limited on throughput (and
28535 probably latency too) by the first hop in their circuit. Now we
28536 select guards weighted by currently advertised bandwidth. We also
28537 automatically discard guards picked using the old algorithm. Fixes
28538 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
28539 - When choosing which cells to relay first, relays can now favor
28540 circuits that have been quiet recently, to provide lower latency
28541 for low-volume circuits. By default, relays enable or disable this
28542 feature based on a setting in the consensus. You can override
28543 this default by using the new "CircuitPriorityHalflife" config
28544 option. Design and code by Ian Goldberg, Can Tang, and Chris
28546 - Add separate per-conn write limiting to go with the per-conn read
28547 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
28548 but never per-conn write limits.
28549 - New consensus params "bwconnrate" and "bwconnburst" to let us
28550 rate-limit client connections as they enter the network. It's
28551 controlled in the consensus so we can turn it on and off for
28552 experiments. It's starting out off. Based on proposal 163.
28554 o Major features (relay selection options):
28555 - Switch to a StrictNodes config option, rather than the previous
28556 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
28557 "StrictExcludeNodes" option.
28558 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
28559 change during a config reload, mark and discard all our origin
28560 circuits. This fix should address edge cases where we change the
28561 config options and but then choose a circuit that we created before
28563 - If EntryNodes or ExitNodes are set, be more willing to use an
28564 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
28566 - Make EntryNodes config option much more aggressive even when
28567 StrictNodes is not set. Before it would prepend your requested
28568 entrynodes to your list of guard nodes, but feel free to use others
28569 after that. Now it chooses only from your EntryNodes if any of
28570 those are available, and only falls back to others if a) they're
28571 all down and b) StrictNodes is not set.
28572 - Now we refresh your entry guards from EntryNodes at each consensus
28573 fetch -- rather than just at startup and then they slowly rot as
28574 the network changes.
28577 - Stop bridge directory authorities from answering dbg-stability.txt
28578 directory queries, which would let people fetch a list of all
28579 bridge identities they track. Bugfix on 0.2.1.6-alpha.
28582 - Log a notice when we get a new control connection. Now it's easier
28583 for security-conscious users to recognize when a local application
28584 is knocking on their controller door. Suggested by bug 1196.
28585 - New config option "CircuitStreamTimeout" to override our internal
28586 timeout schedule for how many seconds until we detach a stream from
28587 a circuit and try a new circuit. If your network is particularly
28588 slow, you might want to set this to a number like 60.
28589 - New controller command "getinfo config-text". It returns the
28590 contents that Tor would write if you send it a SAVECONF command,
28591 so the controller can write the file to disk itself.
28592 - New options for SafeLogging to allow scrubbing only log messages
28593 generated while acting as a relay.
28594 - Ship the bridges spec file in the tarball too.
28595 - Avoid a mad rush at the beginning of each month when each client
28596 rotates half of its guards. Instead we spread the rotation out
28597 throughout the month, but we still avoid leaving a precise timestamp
28598 in the state file about when we first picked the guard. Improves
28599 over the behavior introduced in 0.1.2.17.
28601 o Minor bugfixes (compiling):
28602 - Fix compilation on OS X 10.3, which has a stub mlockall() but
28603 hides it. Bugfix on 0.2.2.6-alpha.
28604 - Fix compilation on Solaris by removing support for the
28605 DisableAllSwap config option. Solaris doesn't have an rlimit for
28606 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
28609 o Minor bugfixes (crashes):
28610 - Do not segfault when writing buffer stats when we haven't observed
28611 a single circuit to report about. Found by Fabian Lanze. Bugfix on
28613 - If we're in the pathological case where there's no exit bandwidth
28614 but there is non-exit bandwidth, or no guard bandwidth but there
28615 is non-guard bandwidth, don't crash during path selection. Bugfix
28617 - Fix an impossible-to-actually-trigger buffer overflow in relay
28618 descriptor generation. Bugfix on 0.1.0.15.
28620 o Minor bugfixes (privacy):
28621 - Fix an instance where a Tor directory mirror might accidentally
28622 log the IP address of a misbehaving Tor client. Bugfix on
28624 - Don't list Windows capabilities in relay descriptors. We never made
28625 use of them, and maybe it's a bad idea to publish them. Bugfix
28628 o Minor bugfixes (other):
28629 - Resolve an edge case in path weighting that could make us misweight
28630 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
28631 - Fix statistics on client numbers by country as seen by bridges that
28632 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
28633 intervals instead of variable 12-to-48-hour intervals.
28634 - After we free an internal connection structure, overwrite it
28635 with a different memory value than we use for overwriting a freed
28636 internal circuit structure. Should help with debugging. Suggested
28638 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
28641 o Removed features:
28642 - Remove the HSAuthorityRecordStats option that version 0 hidden
28643 service authorities could have used to track statistics of overall
28644 hidden service usage.
28647 Changes in version 0.2.1.22 - 2010-01-19
28648 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
28649 authorities -- it would tell you its whole history of bridge descriptors
28650 if you make the right directory request. This stable update also
28651 rotates two of the seven v3 directory authority keys and locations.
28653 o Directory authority changes:
28654 - Rotate keys (both v3 identity and relay identity) for moria1
28658 - Stop bridge directory authorities from answering dbg-stability.txt
28659 directory queries, which would let people fetch a list of all
28660 bridge identities they track. Bugfix on 0.2.1.6-alpha.
28663 Changes in version 0.2.1.21 - 2009-12-21
28664 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
28665 library. If you use Tor on Linux / Unix and you're getting SSL
28666 renegotiation errors, upgrading should help. We also recommend an
28667 upgrade if you're an exit relay.
28670 - Work around a security feature in OpenSSL 0.9.8l that prevents our
28671 handshake from working unless we explicitly tell OpenSSL that we
28672 are using SSL renegotiation safely. We are, of course, but OpenSSL
28673 0.9.8l won't work unless we say we are.
28674 - Avoid crashing if the client is trying to upload many bytes and the
28675 circuit gets torn down at the same time, or if the flip side
28676 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
28679 - Do not refuse to learn about authority certs and v2 networkstatus
28680 documents that are older than the latest consensus. This bug might
28681 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
28682 Spotted and fixed by xmux.
28683 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
28684 trigger platform-specific option misparsing case found by Coverity
28686 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
28687 trigger assert. Fixes bug 1173.
28690 Changes in version 0.2.2.6-alpha - 2009-11-19
28691 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
28692 support for the new lower-footprint "microdescriptor" directory design,
28693 future-proofing our consensus format against new hash functions or
28694 other changes, and an Android port. It also makes Tor compatible with
28695 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
28698 - Directory authorities can now create, vote on, and serve multiple
28699 parallel formats of directory data as part of their voting process.
28700 Partially implements Proposal 162: "Publish the consensus in
28702 - Directory authorities can now agree on and publish small summaries
28703 of router information that clients can use in place of regular
28704 server descriptors. This transition will eventually allow clients
28705 to use far less bandwidth for downloading information about the
28706 network. Begins the implementation of Proposal 158: "Clients
28707 download consensus + microdescriptors".
28708 - The directory voting system is now extensible to use multiple hash
28709 algorithms for signatures and resource selection. Newer formats
28710 are signed with SHA256, with a possibility for moving to a better
28711 hash algorithm in the future.
28712 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
28713 current and future memory pages via mlockall(). On supported
28714 platforms (modern Linux and probably BSD but not Windows or OS X),
28715 this should effectively disable any and all attempts to page out
28716 memory. This option requires that you start your Tor as root --
28717 if you use DisableAllSwap, please consider using the User option
28718 to properly reduce the privileges of your Tor.
28719 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
28720 to help Tor build correctly for Android phones.
28723 - Work around a security feature in OpenSSL 0.9.8l that prevents our
28724 handshake from working unless we explicitly tell OpenSSL that we
28725 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
28726 won't work unless we say we are.
28729 - Fix a crash bug when trying to initialize the evdns module in
28730 Libevent 2. Bugfix on 0.2.1.16-rc.
28731 - Stop logging at severity 'warn' when some other Tor client tries
28732 to establish a circuit with us using weak DH keys. It's a protocol
28733 violation, but that doesn't mean ordinary users need to hear about
28734 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
28735 - Do not refuse to learn about authority certs and v2 networkstatus
28736 documents that are older than the latest consensus. This bug might
28737 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
28738 Spotted and fixed by xmux.
28739 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
28740 - If all authorities restart at once right before a consensus vote,
28741 nobody will vote about "Running", and clients will get a consensus
28742 with no usable relays. Instead, authorities refuse to build a
28743 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
28744 - If your relay can't keep up with the number of incoming create
28745 cells, it would log one warning per failure into your logs. Limit
28746 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
28747 - Bridges now use "reject *:*" as their default exit policy. Bugfix
28748 on 0.2.0.3-alpha; fixes bug 1113.
28749 - Fix a memory leak on directory authorities during voting that was
28750 introduced in 0.2.2.1-alpha. Found via valgrind.
28753 Changes in version 0.2.1.20 - 2009-10-15
28754 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
28755 services at once, prepares for more performance improvements, and
28756 fixes a bunch of smaller bugs.
28758 The Windows and OS X bundles also include a more recent Vidalia,
28759 and switch from Privoxy to Polipo.
28761 The OS X installers are now drag and drop. It's best to un-install
28762 Tor/Vidalia and then install this new bundle, rather than upgrade. If
28763 you want to upgrade, you'll need to update the paths for Tor and Polipo
28764 in the Vidalia Settings window.
28767 - Send circuit or stream sendme cells when our window has decreased
28768 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
28769 by Karsten when testing the "reduce circuit window" performance
28770 patch. Bugfix on the 54th commit on Tor -- from July 2002,
28771 before the release of Tor 0.0.0. This is the new winner of the
28773 - Fix a remotely triggerable memory leak when a consensus document
28774 contains more than one signature from the same voter. Bugfix on
28776 - Avoid segfault in rare cases when finishing an introduction circuit
28777 as a client and finding out that we don't have an introduction key
28778 for it. Fixes bug 1073. Reported by Aaron Swartz.
28781 - Tor now reads the "circwindow" parameter out of the consensus,
28782 and uses that value for its circuit package window rather than the
28783 default of 1000 cells. Begins the implementation of proposal 168.
28785 o New directory authorities:
28786 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
28788 - Move moria1 and tonga to alternate IP addresses.
28791 - Fix a signed/unsigned compile warning in 0.2.1.19.
28792 - Fix possible segmentation fault on directory authorities. Bugfix on
28794 - Fix an extremely rare infinite recursion bug that could occur if
28795 we tried to log a message after shutting down the log subsystem.
28796 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
28797 - Fix an obscure bug where hidden services on 64-bit big-endian
28798 systems might mis-read the timestamp in v3 introduce cells, and
28799 refuse to connect back to the client. Discovered by "rotor".
28800 Bugfix on 0.2.1.6-alpha.
28801 - We were triggering a CLOCK_SKEW controller status event whenever
28802 we connect via the v2 connection protocol to any relay that has
28803 a wrong clock. Instead, we should only inform the controller when
28804 it's a trusted authority that claims our clock is wrong. Bugfix
28805 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
28806 - We were telling the controller about CHECKING_REACHABILITY and
28807 REACHABILITY_FAILED status events whenever we launch a testing
28808 circuit or notice that one has failed. Instead, only tell the
28809 controller when we want to inform the user of overall success or
28810 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
28812 - Don't warn when we're using a circuit that ends with a node
28813 excluded in ExcludeExitNodes, but the circuit is not used to access
28814 the outside world. This should help fix bug 1090. Bugfix on
28816 - Work around a small memory leak in some versions of OpenSSL that
28817 stopped the memory used by the hostname TLS extension from being
28821 - Add a "getinfo status/accepted-server-descriptor" controller
28822 command, which is the recommended way for controllers to learn
28823 whether our server descriptor has been successfully received by at
28824 least on directory authority. Un-recommend good-server-descriptor
28825 getinfo and status events until we have a better design for them.
28828 Changes in version 0.2.2.5-alpha - 2009-10-11
28829 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
28832 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
28834 o Directory authorities:
28835 - Temporarily (just for this release) move dizum to an alternate
28839 Changes in version 0.2.2.4-alpha - 2009-10-10
28840 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
28841 introduces a new unit test framework, shifts directry authority
28842 addresses around to reduce the impact from recent blocking events,
28843 and fixes a few smaller bugs.
28846 - Fix several more asserts in the circuit_build_times code, for
28847 example one that causes Tor to fail to start once we have
28848 accumulated 5000 build times in the state file. Bugfixes on
28849 0.2.2.2-alpha; fixes bug 1108.
28851 o New directory authorities:
28852 - Move moria1 and Tonga to alternate IP addresses.
28855 - Log SSL state transitions at debug level during handshake, and
28856 include SSL states in error messages. This may help debug future
28857 SSL handshake issues.
28858 - Add a new "Handshake" log domain for activities that happen
28859 during the TLS handshake.
28860 - Revert to the "June 3 2009" ip-to-country file. The September one
28861 seems to have removed most US IP addresses.
28862 - Directory authorities now reject Tor relays with versions less than
28863 0.1.2.14. This step cuts out four relays from the current network,
28864 none of which are very big.
28867 - Fix a couple of smaller issues with gathering statistics. Bugfixes
28869 - Fix two memory leaks in the error case of
28870 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
28871 - Don't count one-hop circuits when we're estimating how long it
28872 takes circuits to build on average. Otherwise we'll set our circuit
28873 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
28874 - Directory authorities no longer change their opinion of, or vote on,
28875 whether a router is Running, unless they have themselves been
28876 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
28879 o Code simplifications and refactoring:
28880 - Revise our unit tests to use the "tinytest" framework, so we
28881 can run tests in their own processes, have smarter setup/teardown
28882 code, and so on. The unit test code has moved to its own
28883 subdirectory, and has been split into multiple modules.
28886 Changes in version 0.2.2.3-alpha - 2009-09-23
28887 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
28890 - Fix an overzealous assert in our new circuit build timeout code.
28891 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
28894 - If the networkstatus consensus tells us that we should use a
28895 negative circuit package window, ignore it. Otherwise we'll
28896 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
28899 Changes in version 0.2.2.2-alpha - 2009-09-21
28900 Tor 0.2.2.2-alpha introduces our latest performance improvement for
28901 clients: Tor tracks the average time it takes to build a circuit, and
28902 avoids using circuits that take too long to build. For fast connections,
28903 this feature can cut your expected latency in half. For slow or flaky
28904 connections, it could ruin your Tor experience. Let us know if it does!
28907 - Tor now tracks how long it takes to build client-side circuits
28908 over time, and adapts its timeout to local network performance.
28909 Since a circuit that takes a long time to build will also provide
28910 bad performance, we get significant latency improvements by
28911 discarding the slowest 20% of circuits. Specifically, Tor creates
28912 circuits more aggressively than usual until it has enough data
28913 points for a good timeout estimate. Implements proposal 151.
28914 We are especially looking for reports (good and bad) from users with
28915 both EDGE and broadband connections that can move from broadband
28916 to EDGE and find out if the build-time data in the .tor/state gets
28917 reset without loss of Tor usability. You should also see a notice
28918 log message telling you that Tor has reset its timeout.
28919 - Directory authorities can now vote on arbitrary integer values as
28920 part of the consensus process. This is designed to help set
28921 network-wide parameters. Implements proposal 167.
28922 - Tor now reads the "circwindow" parameter out of the consensus,
28923 and uses that value for its circuit package window rather than the
28924 default of 1000 cells. Begins the implementation of proposal 168.
28927 - Fix a remotely triggerable memory leak when a consensus document
28928 contains more than one signature from the same voter. Bugfix on
28932 - Fix an extremely rare infinite recursion bug that could occur if
28933 we tried to log a message after shutting down the log subsystem.
28934 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
28935 - Fix parsing for memory or time units given without a space between
28936 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
28937 - A networkstatus vote must contain exactly one signature. Spec
28938 conformance issue. Bugfix on 0.2.0.3-alpha.
28939 - Fix an obscure bug where hidden services on 64-bit big-endian
28940 systems might mis-read the timestamp in v3 introduce cells, and
28941 refuse to connect back to the client. Discovered by "rotor".
28942 Bugfix on 0.2.1.6-alpha.
28943 - We were triggering a CLOCK_SKEW controller status event whenever
28944 we connect via the v2 connection protocol to any relay that has
28945 a wrong clock. Instead, we should only inform the controller when
28946 it's a trusted authority that claims our clock is wrong. Bugfix
28947 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
28948 - We were telling the controller about CHECKING_REACHABILITY and
28949 REACHABILITY_FAILED status events whenever we launch a testing
28950 circuit or notice that one has failed. Instead, only tell the
28951 controller when we want to inform the user of overall success or
28952 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
28954 - Don't warn when we're using a circuit that ends with a node
28955 excluded in ExcludeExitNodes, but the circuit is not used to access
28956 the outside world. This should help fix bug 1090, but more problems
28957 remain. Bugfix on 0.2.1.6-alpha.
28958 - Work around a small memory leak in some versions of OpenSSL that
28959 stopped the memory used by the hostname TLS extension from being
28961 - Make our 'torify' script more portable; if we have only one of
28962 'torsocks' or 'tsocks' installed, don't complain to the user;
28963 and explain our warning about tsocks better.
28966 - Add a "getinfo status/accepted-server-descriptor" controller
28967 command, which is the recommended way for controllers to learn
28968 whether our server descriptor has been successfully received by at
28969 least on directory authority. Un-recommend good-server-descriptor
28970 getinfo and status events until we have a better design for them.
28971 - Update to the "September 4 2009" ip-to-country file.
28974 Changes in version 0.2.2.1-alpha - 2009-08-26
28975 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
28976 Tor clients to bootstrap on networks where only port 80 is reachable,
28977 makes it more straightforward to support hardware crypto accelerators,
28978 and starts the groundwork for gathering stats safely at relays.
28981 - Start the process of disabling ".exit" address notation, since it
28982 can be used for a variety of esoteric application-level attacks
28983 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
28986 o New directory authorities:
28987 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
28991 - New AccelName and AccelDir options add support for dynamic OpenSSL
28992 hardware crypto acceleration engines.
28993 - Tor now supports tunneling all of its outgoing connections over
28994 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
28995 configuration options. Code by Christopher Davis.
28998 - Send circuit or stream sendme cells when our window has decreased
28999 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
29000 by Karsten when testing the "reduce circuit window" performance
29001 patch. Bugfix on the 54th commit on Tor -- from July 2002,
29002 before the release of Tor 0.0.0. This is the new winner of the
29005 o New options for gathering stats safely:
29006 - Directory mirrors that set "DirReqStatistics 1" write statistics
29007 about directory requests to disk every 24 hours. As compared to the
29008 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
29009 1) stats are written to disk exactly every 24 hours; 2) estimated
29010 shares of v2 and v3 requests are determined as mean values, not at
29011 the end of a measurement period; 3) unresolved requests are listed
29012 with country code '??'; 4) directories also measure download times.
29013 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
29014 number of exit streams and transferred bytes per port to disk every
29016 - Relays that set "CellStatistics 1" write statistics on how long
29017 cells spend in their circuit queues to disk every 24 hours.
29018 - Entry nodes that set "EntryStatistics 1" write statistics on the
29019 rough number and origins of connecting clients to disk every 24
29021 - Relays that write any of the above statistics to disk and set
29022 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
29023 their extra-info documents.
29026 - New --digests command-line switch to output the digests of the
29027 source files Tor was built with.
29028 - The "torify" script now uses torsocks where available.
29029 - The memarea code now uses a sentinel value at the end of each area
29030 to make sure nothing writes beyond the end of an area. This might
29031 help debug some conceivable causes of bug 930.
29032 - Time and memory units in the configuration file can now be set to
29033 fractional units. For example, "2.5 GB" is now a valid value for
29035 - Certain Tor clients (such as those behind check.torproject.org) may
29036 want to fetch the consensus in an extra early manner. To enable this
29037 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
29038 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
29039 as only certain clients who must have this information sooner should
29041 - Instead of adding the svn revision to the Tor version string, report
29042 the git commit (when we're building from a git checkout).
29045 - If any of the v3 certs we download are unparseable, we should
29046 actually notice the failure so we don't retry indefinitely. Bugfix
29047 on 0.2.0.x; reported by "rotator".
29048 - If the cached cert file is unparseable, warn but don't exit.
29049 - Fix possible segmentation fault on directory authorities. Bugfix on
29051 - When Tor fails to parse a descriptor of any kind, dump it to disk.
29052 Might help diagnosing bug 1051.
29054 o Deprecated and removed features:
29055 - The controller no longer accepts the old obsolete "addr-mappings/"
29056 or "unregistered-servers-" GETINFO values.
29057 - Hidden services no longer publish version 0 descriptors, and clients
29058 do not request or use version 0 descriptors. However, the old hidden
29059 service authorities still accept and serve version 0 descriptors
29060 when contacted by older hidden services/clients.
29061 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
29062 always on; using them is necessary for correct forward-compatible
29064 - Remove support for .noconnect style addresses. Nobody was using
29065 them, and they provided another avenue for detecting Tor users
29066 via application-level web tricks.
29068 o Packaging changes:
29069 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
29070 installer bundles. See
29071 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
29072 for details of what's new in Vidalia 0.2.3.
29073 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
29074 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
29075 configuration file, rather than the old Privoxy.
29076 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
29077 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
29078 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
29079 better compatibility with OS X 10.6, aka Snow Leopard.
29080 - OS X Vidalia Bundle: The multi-package installer is now replaced
29081 by a simple drag and drop to the /Applications folder. This change
29082 occurred with the upgrade to Vidalia 0.2.3.
29085 Changes in version 0.2.1.19 - 2009-07-28
29086 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
29087 services on Tor 0.2.1.3-alpha through 0.2.1.18.
29090 - Make accessing hidden services on 0.2.1.x work right again.
29091 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
29092 part of patch provided by "optimist".
29095 - When a relay/bridge is writing out its identity key fingerprint to
29096 the "fingerprint" file and to its logs, write it without spaces. Now
29097 it will look like the fingerprints in our bridges documentation,
29098 and confuse fewer users.
29101 - Relays no longer publish a new server descriptor if they change
29102 their MaxAdvertisedBandwidth config option but it doesn't end up
29103 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
29104 fixes bug 1026. Patch from Sebastian.
29105 - Avoid leaking memory every time we get a create cell but we have
29106 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
29107 fixes bug 1034. Reported by BarkerJr.
29110 Changes in version 0.2.1.18 - 2009-07-24
29111 Tor 0.2.1.18 lays the foundations for performance improvements,
29112 adds status events to help users diagnose bootstrap problems, adds
29113 optional authentication/authorization for hidden services, fixes a
29114 variety of potential anonymity problems, and includes a huge pile of
29115 other features and bug fixes.
29118 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
29121 Changes in version 0.2.1.17-rc - 2009-07-07
29122 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
29123 candidate for the 0.2.1.x series. It lays the groundwork for further
29124 client performance improvements, and also fixes a big bug with directory
29125 authorities that were causing them to assign Guard and Stable flags
29128 The Windows bundles also finally include the geoip database that we
29129 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
29130 should actually install Torbutton rather than giving you a cryptic
29131 failure message (oops).
29134 - Clients now use the bandwidth values in the consensus, rather than
29135 the bandwidth values in each relay descriptor. This approach opens
29136 the door to more accurate bandwidth estimates once the directory
29137 authorities start doing active measurements. Implements more of
29141 - When Tor clients restart after 1-5 days, they discard all their
29142 cached descriptors as too old, but they still use the cached
29143 consensus document. This approach is good for robustness, but
29144 bad for performance: since they don't know any bandwidths, they
29145 end up choosing at random rather than weighting their choice by
29146 speed. Fixed by the above feature of putting bandwidths in the
29147 consensus. Bugfix on 0.2.0.x.
29148 - Directory authorities were neglecting to mark relays down in their
29149 internal histories if the relays fall off the routerlist without
29150 ever being found unreachable. So there were relays in the histories
29151 that haven't been seen for eight months, and are listed as being
29152 up for eight months. This wreaked havoc on the "median wfu"
29153 and "median mtbf" calculations, in turn making Guard and Stable
29154 flags very wrong, hurting network performance. Fixes bugs 696 and
29155 969. Bugfix on 0.2.0.6-alpha.
29158 - Serve the DirPortFrontPage page even when we have been approaching
29159 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
29160 - The control port would close the connection before flushing long
29161 replies, such as the network consensus, if a QUIT command was issued
29162 before the reply had completed. Now, the control port flushes all
29163 pending replies before closing the connection. Also fixed a spurious
29164 warning when a QUIT command is issued after a malformed or rejected
29165 AUTHENTICATE command, but before the connection was closed. Patch
29166 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
29167 - When we can't find an intro key for a v2 hidden service descriptor,
29168 fall back to the v0 hidden service descriptor and log a bug message.
29169 Workaround for bug 1024.
29170 - Fix a log message that did not respect the SafeLogging option.
29174 - If we're a relay and we change our IP address, be more verbose
29175 about the reason that made us change. Should help track down
29176 further bugs for relays on dynamic IP addresses.
29179 Changes in version 0.2.0.35 - 2009-06-24
29181 - Avoid crashing in the presence of certain malformed descriptors.
29182 Found by lark, and by automated fuzzing.
29183 - Fix an edge case where a malicious exit relay could convince a
29184 controller that the client's DNS question resolves to an internal IP
29185 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
29188 - Finally fix the bug where dynamic-IP relays disappear when their
29189 IP address changes: directory mirrors were mistakenly telling
29190 them their old address if they asked via begin_dir, so they
29191 never got an accurate answer about their new address, so they
29192 just vanished after a day. For belt-and-suspenders, relays that
29193 don't set Address in their config now avoid using begin_dir for
29194 all direct connections. Should fix bugs 827, 883, and 900.
29195 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
29196 that would occur on some exit nodes when DNS failures and timeouts
29197 occurred in certain patterns. Fix for bug 957.
29200 - When starting with a cache over a few days old, do not leak
29201 memory for the obsolete router descriptors in it. Bugfix on
29202 0.2.0.33; fixes bug 672.
29203 - Hidden service clients didn't use a cached service descriptor that
29204 was older than 15 minutes, but wouldn't fetch a new one either,
29205 because there was already one in the cache. Now, fetch a v2
29206 descriptor unless the same descriptor was added to the cache within
29207 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
29210 Changes in version 0.2.1.16-rc - 2009-06-20
29211 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
29212 a bunch of minor bugs.
29215 - Fix an edge case where a malicious exit relay could convince a
29216 controller that the client's DNS question resolves to an internal IP
29217 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
29219 o Major performance improvements (on 0.2.0.x):
29220 - Disable and refactor some debugging checks that forced a linear scan
29221 over the whole server-side DNS cache. These accounted for over 50%
29222 of CPU time on a relatively busy exit node's gprof profile. Found
29224 - Disable some debugging checks that appeared in exit node profile
29228 - Update to the "June 3 2009" ip-to-country file.
29229 - Do not have tor-resolve automatically refuse all .onion addresses;
29230 if AutomapHostsOnResolve is set in your torrc, this will work fine.
29232 o Minor bugfixes (on 0.2.0.x):
29233 - Log correct error messages for DNS-related network errors on
29235 - Fix a race condition that could cause crashes or memory corruption
29236 when running as a server with a controller listening for log
29238 - Avoid crashing when we have a policy specified in a DirPolicy or
29239 SocksPolicy or ReachableAddresses option with ports set on it,
29240 and we re-load the policy. May fix bug 996.
29241 - Hidden service clients didn't use a cached service descriptor that
29242 was older than 15 minutes, but wouldn't fetch a new one either,
29243 because there was already one in the cache. Now, fetch a v2
29244 descriptor unless the same descriptor was added to the cache within
29245 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
29247 o Minor bugfixes (on 0.2.1.x):
29248 - Don't warn users about low port and hibernation mix when they
29249 provide a *ListenAddress directive to fix that. Bugfix on
29251 - When switching back and forth between bridge mode, do not start
29252 gathering GeoIP data until two hours have passed.
29253 - Do not complain that the user has requested an excluded node as
29254 an exit when the node is not really an exit. This could happen
29255 because the circuit was for testing, or an introduction point.
29259 Changes in version 0.2.1.15-rc - 2009-05-25
29260 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
29261 series. It fixes a major bug on fast exit relays, as well as a variety
29262 of more minor bugs.
29264 o Major bugfixes (on 0.2.0.x):
29265 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
29266 that would occur on some exit nodes when DNS failures and timeouts
29267 occurred in certain patterns. Fix for bug 957.
29269 o Minor bugfixes (on 0.2.0.x):
29270 - Actually return -1 in the error case for read_bandwidth_usage().
29271 Harmless bug, since we currently don't care about the return value
29272 anywhere. Bugfix on 0.2.0.9-alpha.
29273 - Provide a more useful log message if bug 977 (related to buffer
29274 freelists) ever reappears, and do not crash right away.
29275 - Fix an assertion failure on 64-bit platforms when we allocated
29276 memory right up to the end of a memarea, then realigned the memory
29277 one step beyond the end. Fixes a possible cause of bug 930.
29278 - Protect the count of open sockets with a mutex, so we can't
29279 corrupt it when two threads are closing or opening sockets at once.
29280 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
29281 - Don't allow a bridge to publish its router descriptor to a
29282 non-bridge directory authority. Fixes part of bug 932.
29283 - When we change to or from being a bridge, reset our counts of
29284 client usage by country. Fixes bug 932.
29285 - Fix a bug that made stream bandwidth get misreported to the
29287 - Stop using malloc_usable_size() to use more area than we had
29288 actually allocated: it was safe, but made valgrind really unhappy.
29289 - Fix a memory leak when v3 directory authorities load their keys
29290 and cert from disk. Bugfix on 0.2.0.1-alpha.
29292 o Minor bugfixes (on 0.2.1.x):
29293 - Fix use of freed memory when deciding to mark a non-addable
29294 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
29297 Changes in version 0.2.1.14-rc - 2009-04-12
29298 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
29299 series. It begins fixing some major performance problems, and also
29300 finally addresses the bug that was causing relays on dynamic IP
29301 addresses to fall out of the directory.
29304 - Clients replace entry guards that were chosen more than a few months
29305 ago. This change should significantly improve client performance,
29306 especially once more people upgrade, since relays that have been
29307 a guard for a long time are currently overloaded.
29309 o Major bugfixes (on 0.2.0):
29310 - Finally fix the bug where dynamic-IP relays disappear when their
29311 IP address changes: directory mirrors were mistakenly telling
29312 them their old address if they asked via begin_dir, so they
29313 never got an accurate answer about their new address, so they
29314 just vanished after a day. For belt-and-suspenders, relays that
29315 don't set Address in their config now avoid using begin_dir for
29316 all direct connections. Should fix bugs 827, 883, and 900.
29317 - Relays were falling out of the networkstatus consensus for
29318 part of a day if they changed their local config but the
29319 authorities discarded their new descriptor as "not sufficiently
29320 different". Now directory authorities accept a descriptor as changed
29321 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
29322 patch by Sebastian.
29323 - Avoid crashing in the presence of certain malformed descriptors.
29324 Found by lark, and by automated fuzzing.
29327 - When generating circuit events with verbose nicknames for
29328 controllers, try harder to look up nicknames for routers on a
29329 circuit. (Previously, we would look in the router descriptors we had
29330 for nicknames, but not in the consensus.) Partial fix for bug 941.
29331 - If the bridge config line doesn't specify a port, assume 443.
29332 This makes bridge lines a bit smaller and easier for users to
29334 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
29335 bytes (aka 20KB/s), to match our documentation. Also update
29336 directory authorities so they always assign the Fast flag to relays
29337 with 20KB/s of capacity. Now people running relays won't suddenly
29338 find themselves not seeing any use, if the network gets faster
29340 - Update to the "April 3 2009" ip-to-country file.
29343 - Avoid trying to print raw memory to the logs when we decide to
29344 give up on downloading a given relay descriptor. Bugfix on
29346 - In tor-resolve, when the Tor client to use is specified by
29347 <hostname>:<port>, actually use the specified port rather than
29348 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
29349 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
29350 - When starting with a cache over a few days old, do not leak
29351 memory for the obsolete router descriptors in it. Bugfix on
29353 - Avoid double-free on list of successfully uploaded hidden
29354 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
29355 - Change memarea_strndup() implementation to work even when
29356 duplicating a string at the end of a page. This bug was
29357 harmless for now, but could have meant crashes later. Fix by
29358 lark. Bugfix on 0.2.1.1-alpha.
29359 - Limit uploaded directory documents to be 16M rather than 500K.
29360 The directory authorities were refusing v3 consensus votes from
29361 other authorities, since the votes are now 504K. Fixes bug 959;
29362 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
29363 - Directory authorities should never send a 503 "busy" response to
29364 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
29368 Changes in version 0.2.1.13-alpha - 2009-03-09
29369 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
29370 cleanups. We're finally getting close to a release candidate.
29373 - Correctly update the list of which countries we exclude as
29374 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
29375 lark. Bugfix on 0.2.1.6-alpha.
29377 o Minor bugfixes (on 0.2.0.x and earlier):
29378 - Automatically detect MacOSX versions earlier than 10.4.0, and
29379 disable kqueue from inside Tor when running with these versions.
29380 We previously did this from the startup script, but that was no
29381 help to people who didn't use the startup script. Resolves bug 863.
29382 - When we had picked an exit node for a connection, but marked it as
29383 "optional", and it turned out we had no onion key for the exit,
29384 stop wanting that exit and try again. This situation may not
29385 be possible now, but will probably become feasible with proposal
29386 158. Spotted by rovv. Fixes another case of bug 752.
29387 - Clients no longer cache certificates for authorities they do not
29388 recognize. Bugfix on 0.2.0.9-alpha.
29389 - When we can't transmit a DNS request due to a network error, retry
29390 it after a while, and eventually transmit a failing response to
29391 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
29392 - If the controller claimed responsibility for a stream, but that
29393 stream never finished making its connection, it would live
29394 forever in circuit_wait state. Now we close it after SocksTimeout
29395 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
29396 - Drop begin cells to a hidden service if they come from the middle
29397 of a circuit. Patch from lark.
29398 - When we erroneously receive two EXTEND cells for the same circuit
29399 ID on the same connection, drop the second. Patch from lark.
29400 - Fix a crash that occurs on exit nodes when a nameserver request
29401 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
29402 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
29404 - Do not assume that a stack-allocated character array will be
29405 64-bit aligned on platforms that demand that uint64_t access is
29406 aligned. Possible fix for bug 604.
29407 - Parse dates and IPv4 addresses in a locale- and libc-independent
29408 manner, to avoid platform-dependent behavior on malformed input.
29409 - Build correctly when configured to build outside the main source
29410 path. Patch from Michael Gold.
29411 - We were already rejecting relay begin cells with destination port
29412 of 0. Now also reject extend cells with destination port or address
29413 of 0. Suggested by lark.
29415 o Minor bugfixes (on 0.2.1.x):
29416 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
29417 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
29418 - If we're an exit node, scrub the IP address to which we are exiting
29419 in the logs. Bugfix on 0.2.1.8-alpha.
29422 - On Linux, use the prctl call to re-enable core dumps when the user
29424 - New controller event NEWCONSENSUS that lists the networkstatus
29425 lines for every recommended relay. Now controllers like Torflow
29426 can keep up-to-date on which relays they should be using.
29427 - Update to the "February 26 2009" ip-to-country file.
29430 Changes in version 0.2.0.34 - 2009-02-08
29431 Tor 0.2.0.34 features several more security-related fixes. You should
29432 upgrade, especially if you run an exit relay (remote crash) or a
29433 directory authority (remote infinite loop), or you're on an older
29434 (pre-XP) or not-recently-patched Windows (remote exploit).
29436 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
29437 have many known flaws, and nobody should be using them. You should
29438 upgrade. If you're using a Linux or BSD and its packages are obsolete,
29439 stop using those packages and upgrade anyway.
29442 - Fix an infinite-loop bug on handling corrupt votes under certain
29443 circumstances. Bugfix on 0.2.0.8-alpha.
29444 - Fix a temporary DoS vulnerability that could be performed by
29445 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
29446 - Avoid a potential crash on exit nodes when processing malformed
29447 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
29448 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
29449 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
29452 - Fix compilation on systems where time_t is a 64-bit integer.
29453 Patch from Matthias Drochner.
29454 - Don't consider expiring already-closed client connections. Fixes
29455 bug 893. Bugfix on 0.0.2pre20.
29458 Changes in version 0.2.1.12-alpha - 2009-02-08
29459 Tor 0.2.1.12-alpha features several more security-related fixes. You
29460 should upgrade, especially if you run an exit relay (remote crash) or
29461 a directory authority (remote infinite loop), or you're on an older
29462 (pre-XP) or not-recently-patched Windows (remote exploit). It also
29463 includes a big pile of minor bugfixes and cleanups.
29466 - Fix an infinite-loop bug on handling corrupt votes under certain
29467 circumstances. Bugfix on 0.2.0.8-alpha.
29468 - Fix a temporary DoS vulnerability that could be performed by
29469 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
29470 - Avoid a potential crash on exit nodes when processing malformed
29471 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
29474 - Let controllers actually ask for the "clients_seen" event for
29475 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
29476 reported by Matt Edman.
29477 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
29479 - Fix a bug in address parsing that was preventing bridges or hidden
29480 service targets from being at IPv6 addresses.
29481 - Solve a bug that kept hardware crypto acceleration from getting
29482 enabled when accounting was turned on. Fixes bug 907. Bugfix on
29484 - Remove a bash-ism from configure.in to build properly on non-Linux
29485 platforms. Bugfix on 0.2.1.1-alpha.
29486 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
29487 headers. Bugfix on 0.2.0.10-alpha.
29488 - Don't consider expiring already-closed client connections. Fixes
29489 bug 893. Bugfix on 0.0.2pre20.
29490 - Fix another interesting corner-case of bug 891 spotted by rovv:
29491 Previously, if two hosts had different amounts of clock drift, and
29492 one of them created a new connection with just the wrong timing,
29493 the other might decide to deprecate the new connection erroneously.
29494 Bugfix on 0.1.1.13-alpha.
29495 - Resolve a very rare crash bug that could occur when the user forced
29496 a nameserver reconfiguration during the middle of a nameserver
29497 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
29498 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
29499 Bugfix on 0.2.1.7-alpha.
29500 - If we're using bridges and our network goes away, be more willing
29501 to forgive our bridges and try again when we get an application
29502 request. Bugfix on 0.2.0.x.
29505 - Support platforms where time_t is 64 bits long. (Congratulations,
29506 NetBSD!) Patch from Matthias Drochner.
29507 - Add a 'getinfo status/clients-seen' controller command, in case
29508 controllers want to hear clients_seen events but connect late.
29511 - Disable GCC's strict alias optimization by default, to avoid the
29512 likelihood of its introducing subtle bugs whenever our code violates
29513 the letter of C99's alias rules.
29516 Changes in version 0.2.0.33 - 2009-01-21
29517 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
29518 useful to users. It also finally fixes a bug where a relay or client
29519 that's been off for many days would take a long time to bootstrap.
29521 This update also fixes an important security-related bug reported by
29522 Ilja van Sprundel. You should upgrade. (We'll send out more details
29523 about the bug once people have had some time to upgrade.)
29526 - Fix a heap-corruption bug that may be remotely triggerable on
29527 some platforms. Reported by Ilja van Sprundel.
29530 - When a stream at an exit relay is in state "resolving" or
29531 "connecting" and it receives an "end" relay cell, the exit relay
29532 would silently ignore the end cell and not close the stream. If
29533 the client never closes the circuit, then the exit relay never
29534 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
29535 reported by "wood".
29536 - When sending CREATED cells back for a given circuit, use a 64-bit
29537 connection ID to find the right connection, rather than an addr:port
29538 combination. Now that we can have multiple OR connections between
29539 the same ORs, it is no longer possible to use addr:port to uniquely
29540 identify a connection.
29541 - Bridge relays that had DirPort set to 0 would stop fetching
29542 descriptors shortly after startup, and then briefly resume
29543 after a new bandwidth test and/or after publishing a new bridge
29544 descriptor. Bridge users that try to bootstrap from them would
29545 get a recent networkstatus but would get descriptors from up to
29546 18 hours earlier, meaning most of the descriptors were obsolete
29547 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
29548 - Prevent bridge relays from serving their 'extrainfo' document
29549 to anybody who asks, now that extrainfo docs include potentially
29550 sensitive aggregated client geoip summaries. Bugfix on
29552 - If the cached networkstatus consensus is more than five days old,
29553 discard it rather than trying to use it. In theory it could be
29554 useful because it lists alternate directory mirrors, but in practice
29555 it just means we spend many minutes trying directory mirrors that
29556 are long gone from the network. Also discard router descriptors as
29557 we load them if they are more than five days old, since the onion
29558 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
29561 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
29562 could make gcc generate non-functional binary search code. Bugfix
29564 - Build correctly on platforms without socklen_t.
29565 - Compile without warnings on solaris.
29566 - Avoid potential crash on internal error during signature collection.
29567 Fixes bug 864. Patch from rovv.
29568 - Correct handling of possible malformed authority signing key
29569 certificates with internal signature types. Fixes bug 880.
29570 Bugfix on 0.2.0.3-alpha.
29571 - Fix a hard-to-trigger resource leak when logging credential status.
29573 - When we can't initialize DNS because the network is down, do not
29574 automatically stop Tor from starting. Instead, we retry failed
29575 dns_init() every 10 minutes, and change the exit policy to reject
29576 *:* until one succeeds. Fixes bug 691.
29577 - Use 64 bits instead of 32 bits for connection identifiers used with
29578 the controller protocol, to greatly reduce risk of identifier reuse.
29579 - When we're choosing an exit node for a circuit, and we have
29580 no pending streams, choose a good general exit rather than one that
29581 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
29582 - Fix another case of assuming, when a specific exit is requested,
29583 that we know more than the user about what hosts it allows.
29584 Fixes one case of bug 752. Patch from rovv.
29585 - Clip the MaxCircuitDirtiness config option to a minimum of 10
29586 seconds. Warn the user if lower values are given in the
29587 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
29588 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
29589 user if lower values are given in the configuration. Bugfix on
29590 0.1.1.17-rc. Patch by Sebastian.
29591 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
29592 the cache because we already had a v0 descriptor with the same ID.
29593 Bugfix on 0.2.0.18-alpha.
29594 - Fix a race condition when freeing keys shared between main thread
29595 and CPU workers that could result in a memory leak. Bugfix on
29596 0.1.0.1-rc. Fixes bug 889.
29597 - Send a valid END cell back when a client tries to connect to a
29598 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
29599 840. Patch from rovv.
29600 - Check which hops rendezvous stream cells are associated with to
29601 prevent possible guess-the-streamid injection attacks from
29602 intermediate hops. Fixes another case of bug 446. Based on patch
29604 - If a broken client asks a non-exit router to connect somewhere,
29605 do not even do the DNS lookup before rejecting the connection.
29606 Fixes another case of bug 619. Patch from rovv.
29607 - When a relay gets a create cell it can't decrypt (e.g. because it's
29608 using the wrong onion key), we were dropping it and letting the
29609 client time out. Now actually answer with a destroy cell. Fixes
29610 bug 904. Bugfix on 0.0.2pre8.
29612 o Minor bugfixes (hidden services):
29613 - Do not throw away existing introduction points on SIGHUP. Bugfix on
29614 0.0.6pre1. Patch by Karsten. Fixes bug 874.
29617 - Report the case where all signatures in a detached set are rejected
29618 differently than the case where there is an error handling the
29620 - When we realize that another process has modified our cached
29621 descriptors, print out a more useful error message rather than
29622 triggering an assertion. Fixes bug 885. Patch from Karsten.
29623 - Implement the 0x20 hack to better resist DNS poisoning: set the
29624 case on outgoing DNS requests randomly, and reject responses that do
29625 not match the case correctly. This logic can be disabled with the
29626 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
29627 of servers that do not reliably preserve case in replies. See
29628 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
29630 - Check DNS replies for more matching fields to better resist DNS
29632 - Never use OpenSSL compression: it wastes RAM and CPU trying to
29633 compress cells, which are basically all encrypted, compressed, or
29637 Changes in version 0.2.1.11-alpha - 2009-01-20
29638 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
29639 week it will take a long time to bootstrap again" bug. It also fixes
29640 an important security-related bug reported by Ilja van Sprundel. You
29641 should upgrade. (We'll send out more details about the bug once people
29642 have had some time to upgrade.)
29645 - Fix a heap-corruption bug that may be remotely triggerable on
29646 some platforms. Reported by Ilja van Sprundel.
29649 - Discard router descriptors as we load them if they are more than
29650 five days old. Otherwise if Tor is off for a long time and then
29651 starts with cached descriptors, it will try to use the onion
29652 keys in those obsolete descriptors when building circuits. Bugfix
29653 on 0.2.0.x. Fixes bug 887.
29656 - Try to make sure that the version of Libevent we're running with
29657 is binary-compatible with the one we built with. May address bug
29659 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
29660 for bug 905. Bugfix on 0.2.1.7-alpha.
29661 - Add a new --enable-local-appdata configuration switch to change
29662 the default location of the datadir on win32 from APPDATA to
29663 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
29664 entirely. Patch from coderman.
29667 - Make outbound DNS packets respect the OutboundBindAddress setting.
29668 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
29669 - When our circuit fails at the first hop (e.g. we get a destroy
29670 cell back), avoid using that OR connection anymore, and also
29671 tell all the one-hop directory requests waiting for it that they
29672 should fail. Bugfix on 0.2.1.3-alpha.
29673 - In the torify(1) manpage, mention that tsocks will leak your
29677 Changes in version 0.2.1.10-alpha - 2009-01-06
29678 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
29679 would make the bridge relay not so useful if it had DirPort set to 0,
29680 and one that could let an attacker learn a little bit of information
29681 about the bridge's users), and a bug that would cause your Tor relay
29682 to ignore a circuit create request it can't decrypt (rather than reply
29683 with an error). It also fixes a wide variety of other bugs.
29686 - If the cached networkstatus consensus is more than five days old,
29687 discard it rather than trying to use it. In theory it could
29688 be useful because it lists alternate directory mirrors, but in
29689 practice it just means we spend many minutes trying directory
29690 mirrors that are long gone from the network. Helps bug 887 a bit;
29692 - Bridge relays that had DirPort set to 0 would stop fetching
29693 descriptors shortly after startup, and then briefly resume
29694 after a new bandwidth test and/or after publishing a new bridge
29695 descriptor. Bridge users that try to bootstrap from them would
29696 get a recent networkstatus but would get descriptors from up to
29697 18 hours earlier, meaning most of the descriptors were obsolete
29698 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
29699 - Prevent bridge relays from serving their 'extrainfo' document
29700 to anybody who asks, now that extrainfo docs include potentially
29701 sensitive aggregated client geoip summaries. Bugfix on
29705 - New controller event "clients_seen" to report a geoip-based summary
29706 of which countries we've seen clients from recently. Now controllers
29707 like Vidalia can show bridge operators that they're actually making
29709 - Build correctly against versions of OpenSSL 0.9.8 or later built
29710 without support for deprecated functions.
29711 - Update to the "December 19 2008" ip-to-country file.
29713 o Minor bugfixes (on 0.2.0.x):
29714 - Authorities now vote for the Stable flag for any router whose
29715 weighted MTBF is at least 5 days, regardless of the mean MTBF.
29716 - Do not remove routers as too old if we do not have any consensus
29717 document. Bugfix on 0.2.0.7-alpha.
29718 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
29719 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
29720 - When an exit relay resolves a stream address to a local IP address,
29721 do not just keep retrying that same exit relay over and
29722 over. Instead, just close the stream. Addresses bug 872. Bugfix
29723 on 0.2.0.32. Patch from rovv.
29724 - If a hidden service sends us an END cell, do not consider
29725 retrying the connection; just close it. Patch from rovv.
29726 - When we made bridge authorities stop serving bridge descriptors over
29727 unencrypted links, we also broke DirPort reachability testing for
29728 bridges. So bridges with a non-zero DirPort were printing spurious
29729 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
29730 - When a relay gets a create cell it can't decrypt (e.g. because it's
29731 using the wrong onion key), we were dropping it and letting the
29732 client time out. Now actually answer with a destroy cell. Fixes
29733 bug 904. Bugfix on 0.0.2pre8.
29734 - Squeeze 2-5% out of client performance (according to oprofile) by
29735 improving the implementation of some policy-manipulation functions.
29737 o Minor bugfixes (on 0.2.1.x):
29738 - Make get_interface_address() function work properly again; stop
29739 guessing the wrong parts of our address as our address.
29740 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
29741 send on that circuit. Otherwise we might violate the proposal-110
29742 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
29744 - When we're sending non-EXTEND cells to the first hop in a circuit,
29745 for example to use an encrypted directory connection, we don't need
29746 to use RELAY_EARLY cells: the first hop knows what kind of cell
29747 it is, and nobody else can even see the cell type. Conserving
29748 RELAY_EARLY cells makes it easier to cannibalize circuits like
29750 - Stop logging nameserver addresses in reverse order.
29751 - If we are retrying a directory download slowly over and over, do
29752 not automatically give up after the 254th failure. Bugfix on
29754 - Resume reporting accurate "stream end" reasons to the local control
29755 port. They were lost in the changes for Proposal 148. Bugfix on
29758 o Deprecated and removed features:
29759 - The old "tor --version --version" command, which would print out
29760 the subversion "Id" of most of the source files, is now removed. It
29761 turned out to be less useful than we'd expected, and harder to
29764 o Code simplifications and refactoring:
29765 - Change our header file guard macros to be less likely to conflict
29766 with system headers. Adam Langley noticed that we were conflicting
29767 with log.h on Android.
29768 - Tool-assisted documentation cleanup. Nearly every function or
29769 static variable in Tor should have its own documentation now.
29772 Changes in version 0.2.1.9-alpha - 2008-12-25
29773 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
29775 o New directory authorities:
29776 - gabelmoo (the authority run by Karsten Loesing) now has a new
29780 - Never use a connection with a mismatched address to extend a
29781 circuit, unless that connection is canonical. A canonical
29782 connection is one whose address is authenticated by the router's
29783 identity key, either in a NETINFO cell or in a router descriptor.
29784 - Avoid a possible memory corruption bug when receiving hidden service
29785 descriptors. Bugfix on 0.2.1.6-alpha.
29788 - Fix a logic error that would automatically reject all but the first
29789 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
29790 part of bug 813/868. Bug spotted by coderman.
29791 - When a stream at an exit relay is in state "resolving" or
29792 "connecting" and it receives an "end" relay cell, the exit relay
29793 would silently ignore the end cell and not close the stream. If
29794 the client never closes the circuit, then the exit relay never
29795 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
29796 reported by "wood".
29797 - When we can't initialize DNS because the network is down, do not
29798 automatically stop Tor from starting. Instead, retry failed
29799 dns_init() every 10 minutes, and change the exit policy to reject
29800 *:* until one succeeds. Fixes bug 691.
29803 - Give a better error message when an overzealous init script says
29804 "sudo -u username tor --user username". Makes Bug 882 easier for
29806 - When a directory authority gives us a new guess for our IP address,
29807 log which authority we used. Hopefully this will help us debug
29808 the recent complaints about bad IP address guesses.
29809 - Detect svn revision properly when we're using git-svn.
29810 - Try not to open more than one descriptor-downloading connection
29811 to an authority at once. This should reduce load on directory
29812 authorities. Fixes bug 366.
29813 - Add cross-certification to newly generated certificates, so that
29814 a signing key is enough information to look up a certificate.
29815 Partial implementation of proposal 157.
29816 - Start serving certificates by <identity digest, signing key digest>
29817 pairs. Partial implementation of proposal 157.
29818 - Clients now never report any stream end reason except 'MISC'.
29819 Implements proposal 148.
29820 - On platforms with a maximum syslog string length, truncate syslog
29821 messages to that length ourselves, rather than relying on the
29822 system to do it for us.
29823 - Optimize out calls to time(NULL) that occur for every IO operation,
29824 or for every cell. On systems where time() is a slow syscall,
29825 this fix will be slightly helpful.
29826 - Exit servers can now answer resolve requests for ip6.arpa addresses.
29827 - When we download a descriptor that we then immediately (as
29828 a directory authority) reject, do not retry downloading it right
29829 away. Should save some bandwidth on authorities. Fix for bug
29830 888. Patch by Sebastian Hahn.
29831 - When a download gets us zero good descriptors, do not notify
29832 Tor that new directory information has arrived.
29833 - Avoid some nasty corner cases in the logic for marking connections
29834 as too old or obsolete or noncanonical for circuits. Partial
29837 o Minor features (controller):
29838 - New CONSENSUS_ARRIVED event to note when a new consensus has
29839 been fetched and validated.
29840 - When we realize that another process has modified our cached
29841 descriptors file, print out a more useful error message rather
29842 than triggering an assertion. Fixes bug 885. Patch from Karsten.
29843 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
29844 controllers to prevent SIGHUP from reloading the
29845 configuration. Fixes bug 856.
29848 - Resume using the correct "REASON=" stream when telling the
29849 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
29850 - When a canonical connection appears later in our internal list
29851 than a noncanonical one for a given OR ID, always use the
29852 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
29854 - Clip the MaxCircuitDirtiness config option to a minimum of 10
29855 seconds. Warn the user if lower values are given in the
29856 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
29857 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
29858 user if lower values are given in the configuration. Bugfix on
29859 0.1.1.17-rc. Patch by Sebastian.
29860 - Fix a race condition when freeing keys shared between main thread
29861 and CPU workers that could result in a memory leak. Bugfix on
29862 0.1.0.1-rc. Fixes bug 889.
29864 o Minor bugfixes (hidden services):
29865 - Do not throw away existing introduction points on SIGHUP (bugfix on
29866 0.0.6pre1); also, do not stall hidden services because we're
29867 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
29868 by John Brooks. Patch by Karsten. Fixes bug 874.
29869 - Fix a memory leak when we decline to add a v2 rendezvous
29870 descriptor to the cache because we already had a v0 descriptor
29871 with the same ID. Bugfix on 0.2.0.18-alpha.
29873 o Deprecated and removed features:
29874 - RedirectExits has been removed. It was deprecated since
29876 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
29877 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
29878 - Cell pools are now always enabled; --disable-cell-pools is ignored.
29880 o Code simplifications and refactoring:
29881 - Rename the confusing or_is_obsolete field to the more appropriate
29882 is_bad_for_new_circs, and move it to or_connection_t where it
29884 - Move edge-only flags from connection_t to edge_connection_t: not
29885 only is this better coding, but on machines of plausible alignment,
29886 it should save 4-8 bytes per connection_t. "Every little bit helps."
29887 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
29888 for consistency; keep old option working for backward compatibility.
29889 - Simplify the code for finding connections to use for a circuit.
29892 Changes in version 0.2.1.8-alpha - 2008-12-08
29893 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
29894 builds better on unusual platforms like Solaris and old OS X, and
29895 fixes a variety of other issues.
29898 - New DirPortFrontPage option that takes an html file and publishes
29899 it as "/" on the DirPort. Now relay operators can provide a
29900 disclaimer without needing to set up a separate webserver. There's
29901 a sample disclaimer in contrib/tor-exit-notice.html.
29904 - When the client is choosing entry guards, now it selects at most
29905 one guard from a given relay family. Otherwise we could end up with
29906 all of our entry points into the network run by the same operator.
29907 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
29910 - Fix a DOS opportunity during the voting signature collection process
29911 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
29912 - Fix a possible segfault when establishing an exit connection. Bugfix
29916 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
29918 - Made Tor a little less aggressive about deleting expired
29919 certificates. Partial fix for bug 854.
29920 - Stop doing unaligned memory access that generated bus errors on
29921 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
29922 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
29923 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
29924 - Make USR2 log-level switch take effect immediately. Bugfix on
29926 - If one win32 nameserver fails to get added, continue adding the
29927 rest, and don't automatically fail.
29928 - Use fcntl() for locking when flock() is not available. Should fix
29929 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
29930 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
29931 could make gcc generate non-functional binary search code. Bugfix
29933 - Build correctly on platforms without socklen_t.
29934 - Avoid potential crash on internal error during signature collection.
29935 Fixes bug 864. Patch from rovv.
29936 - Do not use C's stdio library for writing to log files. This will
29937 improve logging performance by a minute amount, and will stop
29938 leaking fds when our disk is full. Fixes bug 861.
29939 - Stop erroneous use of O_APPEND in cases where we did not in fact
29940 want to re-seek to the end of a file before every last write().
29941 - Correct handling of possible malformed authority signing key
29942 certificates with internal signature types. Fixes bug 880. Bugfix
29944 - Fix a hard-to-trigger resource leak when logging credential status.
29948 - Directory mirrors no longer fetch the v1 directory or
29949 running-routers files. They are obsolete, and nobody asks for them
29950 anymore. This is the first step to making v1 authorities obsolete.
29952 o Minor features (controller):
29953 - Return circuit purposes in response to GETINFO circuit-status. Fixes
29957 Changes in version 0.2.0.32 - 2008-11-20
29958 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
29959 packages (and maybe other packages) noticed by Theo de Raadt, fixes
29960 a smaller security flaw that might allow an attacker to access local
29961 services, further improves hidden service performance, and fixes a
29962 variety of other issues.
29965 - The "User" and "Group" config options did not clear the
29966 supplementary group entries for the Tor process. The "User" option
29967 is now more robust, and we now set the groups to the specified
29968 user's primary group. The "Group" option is now ignored. For more
29969 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
29970 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
29971 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
29972 - The "ClientDNSRejectInternalAddresses" config option wasn't being
29973 consistently obeyed: if an exit relay refuses a stream because its
29974 exit policy doesn't allow it, we would remember what IP address
29975 the relay said the destination address resolves to, even if it's
29976 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
29979 - Fix a DOS opportunity during the voting signature collection process
29980 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
29982 o Major bugfixes (hidden services):
29983 - When fetching v0 and v2 rendezvous service descriptors in parallel,
29984 we were failing the whole hidden service request when the v0
29985 descriptor fetch fails, even if the v2 fetch is still pending and
29986 might succeed. Similarly, if the last v2 fetch fails, we were
29987 failing the whole hidden service request even if a v0 fetch is
29988 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
29989 - When extending a circuit to a hidden service directory to upload a
29990 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
29991 requests failed, because the router descriptor has not been
29992 downloaded yet. In these cases, do not attempt to upload the
29993 rendezvous descriptor, but wait until the router descriptor is
29994 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
29995 descriptor from a hidden service directory for which the router
29996 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
30000 - Fix several infrequent memory leaks spotted by Coverity.
30001 - When testing for libevent functions, set the LDFLAGS variable
30002 correctly. Found by Riastradh.
30003 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
30004 bootstrapping with tunneled directory connections. Bugfix on
30005 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
30006 - When asked to connect to A.B.exit:80, if we don't know the IP for A
30007 and we know that server B rejects most-but-not all connections to
30008 port 80, we would previously reject the connection. Now, we assume
30009 the user knows what they were asking for. Fixes bug 752. Bugfix
30010 on 0.0.9rc5. Diagnosed by BarkerJr.
30011 - If we overrun our per-second write limits a little, count this as
30012 having used up our write allocation for the second, and choke
30013 outgoing directory writes. Previously, we had only counted this when
30014 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
30015 Bugfix on 0.2.0.x (??).
30016 - Remove the old v2 directory authority 'lefkada' from the default
30017 list. It has been gone for many months.
30018 - Stop doing unaligned memory access that generated bus errors on
30019 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
30020 - Make USR2 log-level switch take effect immediately. Bugfix on
30023 o Minor bugfixes (controller):
30024 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
30025 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
30028 Changes in version 0.2.1.7-alpha - 2008-11-08
30029 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
30030 packages (and maybe other packages) noticed by Theo de Raadt, fixes
30031 a smaller security flaw that might allow an attacker to access local
30032 services, adds better defense against DNS poisoning attacks on exit
30033 relays, further improves hidden service performance, and fixes a
30034 variety of other issues.
30037 - The "ClientDNSRejectInternalAddresses" config option wasn't being
30038 consistently obeyed: if an exit relay refuses a stream because its
30039 exit policy doesn't allow it, we would remember what IP address
30040 the relay said the destination address resolves to, even if it's
30041 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
30042 - The "User" and "Group" config options did not clear the
30043 supplementary group entries for the Tor process. The "User" option
30044 is now more robust, and we now set the groups to the specified
30045 user's primary group. The "Group" option is now ignored. For more
30046 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
30047 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
30048 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
30049 - Do not use or believe expired v3 authority certificates. Patch
30050 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
30053 - Now NodeFamily and MyFamily config options allow spaces in
30054 identity fingerprints, so it's easier to paste them in.
30055 Suggested by Lucky Green.
30056 - Implement the 0x20 hack to better resist DNS poisoning: set the
30057 case on outgoing DNS requests randomly, and reject responses that do
30058 not match the case correctly. This logic can be disabled with the
30059 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
30060 of servers that do not reliably preserve case in replies. See
30061 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
30063 - Preserve case in replies to DNSPort requests in order to support
30064 the 0x20 hack for resisting DNS poisoning attacks.
30066 o Hidden service performance improvements:
30067 - When the client launches an introduction circuit, retry with a
30068 new circuit after 30 seconds rather than 60 seconds.
30069 - Launch a second client-side introduction circuit in parallel
30070 after a delay of 15 seconds (based on work by Christian Wilms).
30071 - Hidden services start out building five intro circuits rather
30072 than three, and when the first three finish they publish a service
30073 descriptor using those. Now we publish our service descriptor much
30074 faster after restart.
30077 - Minor fix in the warning messages when you're having problems
30078 bootstrapping; also, be more forgiving of bootstrap problems when
30079 we're still making incremental progress on a given bootstrap phase.
30080 - When we're choosing an exit node for a circuit, and we have
30081 no pending streams, choose a good general exit rather than one that
30082 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
30083 - Send a valid END cell back when a client tries to connect to a
30084 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
30085 840. Patch from rovv.
30086 - If a broken client asks a non-exit router to connect somewhere,
30087 do not even do the DNS lookup before rejecting the connection.
30088 Fixes another case of bug 619. Patch from rovv.
30089 - Fix another case of assuming, when a specific exit is requested,
30090 that we know more than the user about what hosts it allows.
30091 Fixes another case of bug 752. Patch from rovv.
30092 - Check which hops rendezvous stream cells are associated with to
30093 prevent possible guess-the-streamid injection attacks from
30094 intermediate hops. Fixes another case of bug 446. Based on patch
30096 - Avoid using a negative right-shift when comparing 32-bit
30097 addresses. Possible fix for bug 845 and bug 811.
30098 - Make the assert_circuit_ok() function work correctly on circuits that
30099 have already been marked for close.
30100 - Fix read-off-the-end-of-string error in unit tests when decoding
30101 introduction points.
30102 - Fix uninitialized size field for memory area allocation: may improve
30103 memory performance during directory parsing.
30104 - Treat duplicate certificate fetches as failures, so that we do
30105 not try to re-fetch an expired certificate over and over and over.
30106 - Do not say we're fetching a certificate when we'll in fact skip it
30107 because of a pending download.
30110 Changes in version 0.2.1.6-alpha - 2008-09-30
30111 Tor 0.2.1.6-alpha further improves performance and robustness of
30112 hidden services, starts work on supporting per-country relay selection,
30113 and fixes a variety of smaller issues.
30116 - Implement proposal 121: make it possible to build hidden services
30117 that only certain clients are allowed to connect to. This is
30118 enforced at several points, so that unauthorized clients are unable
30119 to send INTRODUCE cells to the service, or even (depending on the
30120 type of authentication) to learn introduction points. This feature
30121 raises the bar for certain kinds of active attacks against hidden
30122 services. Code by Karsten Loesing.
30123 - Relays now store and serve v2 hidden service descriptors by default,
30124 i.e., the new default value for HidServDirectoryV2 is 1. This is
30125 the last step in proposal 114, which aims to make hidden service
30126 lookups more reliable.
30127 - Start work to allow node restrictions to include country codes. The
30128 syntax to exclude nodes in a country with country code XX is
30129 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
30130 refinement to decide what config options should take priority if
30131 you ask to both use a particular node and exclude it.
30132 - Allow ExitNodes list to include IP ranges and country codes, just
30133 like the Exclude*Nodes lists. Patch from Robert Hogan.
30136 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
30137 Tor to fail to start if you had it configured to use a bridge
30138 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
30139 - When extending a circuit to a hidden service directory to upload a
30140 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
30141 requests failed, because the router descriptor had not been
30142 downloaded yet. In these cases, we now wait until the router
30143 descriptor is downloaded, and then retry. Likewise, clients
30144 now skip over a hidden service directory if they don't yet have
30145 its router descriptor, rather than futilely requesting it and
30146 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
30148 - When fetching v0 and v2 rendezvous service descriptors in parallel,
30149 we were failing the whole hidden service request when the v0
30150 descriptor fetch fails, even if the v2 fetch is still pending and
30151 might succeed. Similarly, if the last v2 fetch fails, we were
30152 failing the whole hidden service request even if a v0 fetch is
30153 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
30154 - DNS replies need to have names matching their requests, but
30155 these names should be in the questions section, not necessarily
30156 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
30159 - Update to the "September 1 2008" ip-to-country file.
30160 - Allow ports 465 and 587 in the default exit policy again. We had
30161 rejected them in 0.1.0.15, because back in 2005 they were commonly
30162 misconfigured and ended up as spam targets. We hear they are better
30163 locked down these days.
30164 - Use a lockfile to make sure that two Tor processes are not
30165 simultaneously running with the same datadir.
30166 - Serve the latest v3 networkstatus consensus via the control
30167 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
30168 - Better logging about stability/reliability calculations on directory
30170 - Drop the requirement to have an open dir port for storing and
30171 serving v2 hidden service descriptors.
30172 - Directory authorities now serve a /tor/dbg-stability.txt URL to
30173 help debug WFU and MTBF calculations.
30174 - Implement most of Proposal 152: allow specialized servers to permit
30175 single-hop circuits, and clients to use those servers to build
30176 single-hop circuits when using a specialized controller. Patch
30177 from Josh Albrecht. Resolves feature request 768.
30178 - Add a -p option to tor-resolve for specifying the SOCKS port: some
30179 people find host:port too confusing.
30180 - Make TrackHostExit mappings expire a while after their last use, not
30181 after their creation. Patch from Robert Hogan.
30182 - Provide circuit purposes along with circuit events to the controller.
30185 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
30187 - Fixed some memory leaks -- some quite frequent, some almost
30188 impossible to trigger -- based on results from Coverity.
30189 - When testing for libevent functions, set the LDFLAGS variable
30190 correctly. Found by Riastradh.
30191 - Fix an assertion bug in parsing policy-related options; possible fix
30193 - Catch and report a few more bootstrapping failure cases when Tor
30194 fails to establish a TCP connection. Cleanup on 0.2.1.x.
30195 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
30196 bootstrapping with tunneled directory connections. Bugfix on
30197 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
30198 - When asked to connect to A.B.exit:80, if we don't know the IP for A
30199 and we know that server B rejects most-but-not all connections to
30200 port 80, we would previously reject the connection. Now, we assume
30201 the user knows what they were asking for. Fixes bug 752. Bugfix
30202 on 0.0.9rc5. Diagnosed by BarkerJr.
30203 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
30204 service directories if they have no advertised dir port. Bugfix
30206 - If we overrun our per-second write limits a little, count this as
30207 having used up our write allocation for the second, and choke
30208 outgoing directory writes. Previously, we had only counted this when
30209 we had met our limits precisely. Fixes bug 824. Patch by rovv.
30210 Bugfix on 0.2.0.x (??).
30211 - Avoid a "0 divided by 0" calculation when calculating router uptime
30212 at directory authorities. Bugfix on 0.2.0.8-alpha.
30213 - Make DNS resolved controller events into "CLOSED", not
30214 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
30216 - Fix a bug where an unreachable relay would establish enough
30217 reachability testing circuits to do a bandwidth test -- if
30218 we already have a connection to the middle hop of the testing
30219 circuit, then it could establish the last hop by using the existing
30220 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
30221 circuits no longer use entry guards in 0.2.1.3-alpha.
30222 - If we have correct permissions on $datadir, we complain to stdout
30223 and fail to start. But dangerous permissions on
30224 $datadir/cached-status/ would cause us to open a log and complain
30225 there. Now complain to stdout and fail to start in both cases. Fixes
30226 bug 820, reported by seeess.
30227 - Remove the old v2 directory authority 'lefkada' from the default
30228 list. It has been gone for many months.
30230 o Code simplifications and refactoring:
30231 - Revise the connection_new functions so that a more typesafe variant
30232 exists. This will work better with Coverity, and let us find any
30233 actual mistakes we're making here.
30234 - Refactor unit testing logic so that dmalloc can be used sensibly
30235 with unit tests to check for memory leaks.
30236 - Move all hidden-service related fields from connection and circuit
30237 structure to substructures: this way they won't eat so much memory.
30240 Changes in version 0.2.0.31 - 2008-09-03
30241 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
30242 a big bug we're seeing where in rare cases traffic from one Tor stream
30243 gets mixed into another stream, and fixes a variety of smaller issues.
30246 - Make sure that two circuits can never exist on the same connection
30247 with the same circuit ID, even if one is marked for close. This
30248 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
30249 - Relays now reject risky extend cells: if the extend cell includes
30250 a digest of all zeroes, or asks to extend back to the relay that
30251 sent the extend cell, tear down the circuit. Ideas suggested
30253 - If not enough of our entry guards are available so we add a new
30254 one, we might use the new one even if it overlapped with the
30255 current circuit's exit relay (or its family). Anonymity bugfix
30256 pointed out by rovv.
30259 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
30260 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
30261 - Correctly detect the presence of the linux/netfilter_ipv4.h header
30262 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
30263 - Pick size of default geoip filename string correctly on windows.
30264 Fixes bug 806. Bugfix on 0.2.0.30.
30265 - Make the autoconf script accept the obsolete --with-ssl-dir
30266 option as an alias for the actually-working --with-openssl-dir
30267 option. Fix the help documentation to recommend --with-openssl-dir.
30268 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
30269 - When using the TransPort option on OpenBSD, and using the User
30270 option to change UID and drop privileges, make sure to open
30271 /dev/pf before dropping privileges. Fixes bug 782. Patch from
30272 Christopher Davis. Bugfix on 0.1.2.1-alpha.
30273 - Try to attach connections immediately upon receiving a RENDEZVOUS2
30274 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
30275 on the client side when connecting to a hidden service. Bugfix
30276 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
30277 - When closing an application-side connection because its circuit is
30278 getting torn down, generate the stream event correctly. Bugfix on
30279 0.1.2.x. Anonymous patch.
30282 Changes in version 0.2.1.5-alpha - 2008-08-31
30283 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
30284 in a lot of the infrastructure for adding authorization to hidden
30285 services, lays the groundwork for having clients read their load
30286 balancing information out of the networkstatus consensus rather than
30287 the individual router descriptors, addresses two potential anonymity
30288 issues, and fixes a variety of smaller issues.
30291 - Convert many internal address representations to optionally hold
30293 - Generate and accept IPv6 addresses in many protocol elements.
30294 - Make resolver code handle nameservers located at ipv6 addresses.
30295 - Begin implementation of proposal 121 ("Client authorization for
30296 hidden services"): configure hidden services with client
30297 authorization, publish descriptors for them, and configure
30298 authorization data for hidden services at clients. The next
30299 step is to actually access hidden services that perform client
30301 - More progress toward proposal 141: Network status consensus
30302 documents and votes now contain bandwidth information for each
30303 router and a summary of that router's exit policy. Eventually this
30304 will be used by clients so that they do not have to download every
30305 known descriptor before building circuits.
30307 o Major bugfixes (on 0.2.0.x and before):
30308 - When sending CREATED cells back for a given circuit, use a 64-bit
30309 connection ID to find the right connection, rather than an addr:port
30310 combination. Now that we can have multiple OR connections between
30311 the same ORs, it is no longer possible to use addr:port to uniquely
30312 identify a connection.
30313 - Relays now reject risky extend cells: if the extend cell includes
30314 a digest of all zeroes, or asks to extend back to the relay that
30315 sent the extend cell, tear down the circuit. Ideas suggested
30317 - If not enough of our entry guards are available so we add a new
30318 one, we might use the new one even if it overlapped with the
30319 current circuit's exit relay (or its family). Anonymity bugfix
30320 pointed out by rovv.
30323 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
30324 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
30325 - When using the TransPort option on OpenBSD, and using the User
30326 option to change UID and drop privileges, make sure to open /dev/pf
30327 before dropping privileges. Fixes bug 782. Patch from Christopher
30328 Davis. Bugfix on 0.1.2.1-alpha.
30329 - Correctly detect the presence of the linux/netfilter_ipv4.h header
30330 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
30331 - Add a missing safe_str() call for a debug log message.
30332 - Use 64 bits instead of 32 bits for connection identifiers used with
30333 the controller protocol, to greatly reduce risk of identifier reuse.
30334 - Make the autoconf script accept the obsolete --with-ssl-dir
30335 option as an alias for the actually-working --with-openssl-dir
30336 option. Fix the help documentation to recommend --with-openssl-dir.
30337 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
30340 - Rate-limit too-many-sockets messages: when they happen, they happen
30341 a lot. Resolves bug 748.
30342 - Resist DNS poisoning a little better by making sure that names in
30343 answer sections match.
30344 - Print the SOCKS5 error message string as well as the error code
30345 when a tor-resolve request fails. Patch from Jacob.
30348 Changes in version 0.2.1.4-alpha - 2008-08-04
30349 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
30352 - The address part of exit policies was not correctly written
30353 to router descriptors. This generated router descriptors that failed
30354 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
30356 - Tor triggered a false assert when extending a circuit to a relay
30357 but we already have a connection open to that relay. Noticed by
30358 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
30361 - Fix a hidden service logging bug: in some edge cases, the router
30362 descriptor of a previously picked introduction point becomes
30363 obsolete and we need to give up on it rather than continually
30364 complaining that it has become obsolete. Observed by xiando. Bugfix
30367 o Removed features:
30368 - Take out the TestVia config option, since it was a workaround for
30369 a bug that was fixed in Tor 0.1.1.21.
30372 Changes in version 0.2.1.3-alpha - 2008-08-03
30373 Tor 0.2.1.3-alpha implements most of the pieces to prevent
30374 infinite-length circuit attacks (see proposal 110); fixes a bug that
30375 might cause exit relays to corrupt streams they send back; allows
30376 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
30377 ExcludeExitNodes config options; and fixes a big pile of bugs.
30379 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
30380 - Send a bootstrap problem "warn" event on the first problem if the
30381 reason is NO_ROUTE (that is, our network is down).
30384 - Implement most of proposal 110: The first K cells to be sent
30385 along a circuit are marked as special "early" cells; only K "early"
30386 cells will be allowed. Once this code is universal, we can block
30387 certain kinds of DOS attack by requiring that EXTEND commands must
30388 be sent using an "early" cell.
30391 - Try to attach connections immediately upon receiving a RENDEZVOUS2
30392 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
30393 on the client side when connecting to a hidden service. Bugfix
30394 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
30395 - Ensure that two circuits can never exist on the same connection
30396 with the same circuit ID, even if one is marked for close. This
30397 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
30400 - When relays do their initial bandwidth measurement, don't limit
30401 to just our entry guards for the test circuits. Otherwise we tend
30402 to have multiple test circuits going through a single entry guard,
30403 which makes our bandwidth test less accurate. Fixes part of bug 654;
30404 patch contributed by Josh Albrecht.
30405 - Add an ExcludeExitNodes option so users can list a set of nodes
30406 that should be be excluded from the exit node position, but
30407 allowed elsewhere. Implements proposal 151.
30408 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
30409 ExcludeNodes and ExcludeExitNodes lists.
30410 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
30411 be more efficient. Formerly it was quadratic in the number of
30412 servers; now it should be linear. Fixes bug 509.
30413 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
30414 and n_conn_id_digest fields into a separate structure that's
30415 only needed when the circuit has not yet attached to an n_conn.
30418 - Change the contrib/tor.logrotate script so it makes the new
30419 logs as "_tor:_tor" rather than the default, which is generally
30420 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
30421 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
30422 warnings (occasionally), but it can also cause the compiler to
30423 eliminate error-checking code. Suggested by Peter Gutmann.
30424 - When a hidden service is giving up on an introduction point candidate
30425 that was not included in the last published rendezvous descriptor,
30426 don't reschedule publication of the next descriptor. Fixes bug 763.
30428 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
30429 HiddenServiceExcludeNodes as obsolete: they never worked properly,
30430 and nobody claims to be using them. Fixes bug 754. Bugfix on
30431 0.1.0.1-rc. Patch from Christian Wilms.
30432 - Fix a small alignment and memory-wasting bug on buffer chunks.
30435 o Minor bugfixes (controller):
30436 - When closing an application-side connection because its circuit
30437 is getting torn down, generate the stream event correctly.
30438 Bugfix on 0.1.2.x. Anonymous patch.
30440 o Removed features:
30441 - Remove all backward-compatibility code to support relays running
30442 versions of Tor so old that they no longer work at all on the
30446 Changes in version 0.2.0.30 - 2008-07-15
30448 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
30449 warnings (occasionally), but it can also cause the compiler to
30450 eliminate error-checking code. Suggested by Peter Gutmann.
30453 Changes in version 0.2.0.29-rc - 2008-07-08
30454 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
30455 hidden-service performance bugs, and fixes a bunch of smaller bugs.
30458 - If you have more than one bridge but don't know their keys,
30459 you would only launch a request for the descriptor of the first one
30460 on your list. (Tor considered launching requests for the others, but
30461 found that it already had a connection on the way for $0000...0000
30462 so it didn't open another.) Bugfix on 0.2.0.x.
30463 - If you have more than one bridge but don't know their keys, and the
30464 connection to one of the bridges failed, you would cancel all
30465 pending bridge connections. (After all, they all have the same
30466 digest.) Bugfix on 0.2.0.x.
30467 - When a hidden service was trying to establish an introduction point,
30468 and Tor had built circuits preemptively for such purposes, we
30469 were ignoring all the preemptive circuits and launching a new one
30470 instead. Bugfix on 0.2.0.14-alpha.
30471 - When a hidden service was trying to establish an introduction point,
30472 and Tor *did* manage to reuse one of the preemptively built
30473 circuits, it didn't correctly remember which one it used,
30474 so it asked for another one soon after, until there were no
30475 more preemptive circuits, at which point it launched one from
30476 scratch. Bugfix on 0.0.9.x.
30477 - Make directory servers include the X-Your-Address-Is: http header in
30478 their responses even for begin_dir conns. Now clients who only
30479 ever use begin_dir connections still have a way to learn their IP
30480 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
30483 - Fix a macro/CPP interaction that was confusing some compilers:
30484 some GCCs don't like #if/#endif pairs inside macro arguments.
30486 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
30487 Fixes bug 704; fix from Steven Murdoch.
30488 - When opening /dev/null in finish_daemonize(), do not pass the
30489 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
30490 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
30491 - Correctly detect transparent proxy support on Linux hosts that
30492 require in.h to be included before netfilter_ipv4.h. Patch
30494 - Disallow session resumption attempts during the renegotiation
30495 stage of the v2 handshake protocol. Clients should never be trying
30496 session resumption at this point, but apparently some did, in
30497 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
30498 found by Geoff Goodell.
30501 Changes in version 0.2.1.2-alpha - 2008-06-20
30502 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
30503 make it easier to set up your own private Tor network; fixes several
30504 big bugs with using more than one bridge relay; fixes a big bug with
30505 offering hidden services quickly after Tor starts; and uses a better
30506 API for reporting potential bootstrapping problems to the controller.
30509 - New TestingTorNetwork config option to allow adjustment of
30510 previously constant values that, while reasonable, could slow
30511 bootstrapping. Implements proposal 135. Patch from Karsten.
30514 - If you have more than one bridge but don't know their digests,
30515 you would only learn a request for the descriptor of the first one
30516 on your list. (Tor considered launching requests for the others, but
30517 found that it already had a connection on the way for $0000...0000
30518 so it didn't open another.) Bugfix on 0.2.0.x.
30519 - If you have more than one bridge but don't know their digests,
30520 and the connection to one of the bridges failed, you would cancel
30521 all pending bridge connections. (After all, they all have the
30522 same digest.) Bugfix on 0.2.0.x.
30523 - When establishing a hidden service, introduction points that
30524 originate from cannibalized circuits are completely ignored and not
30525 included in rendezvous service descriptors. This might be another
30526 reason for delay in making a hidden service available. Bugfix
30527 from long ago (0.0.9.x?)
30530 - Allow OpenSSL to use dynamic locks if it wants.
30531 - When building a consensus, do not include routers that are down.
30532 This will cut down 30% to 40% on consensus size. Implements
30534 - In directory authorities' approved-routers files, allow
30535 fingerprints with or without space.
30536 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
30537 controller can query our current bootstrap state in case it attaches
30538 partway through and wants to catch up.
30539 - Send an initial "Starting" bootstrap status event, so we have a
30540 state to start out in.
30543 - Asking for a conditional consensus at .../consensus/<fingerprints>
30544 would crash a dirserver if it did not already have a
30545 consensus. Bugfix on 0.2.1.1-alpha.
30546 - Clean up some macro/CPP interactions: some GCC versions don't like
30547 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
30550 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
30551 - Directory authorities shouldn't complain about bootstrapping
30552 problems just because they do a lot of reachability testing and
30553 some of the connection attempts fail.
30554 - Start sending "count" and "recommendation" key/value pairs in
30555 bootstrap problem status events, so the controller can hear about
30556 problems even before Tor decides they're worth reporting for sure.
30557 - If you're using bridges, generate "bootstrap problem" warnings
30558 as soon as you run out of working bridges, rather than waiting
30559 for ten failures -- which will never happen if you have less than
30561 - If we close our OR connection because there's been a circuit
30562 pending on it for too long, we were telling our bootstrap status
30563 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
30566 Changes in version 0.2.1.1-alpha - 2008-06-13
30567 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
30568 were making the Tor process bloat especially on Linux; makes our TLS
30569 handshake blend in better; sends "bootstrap phase" status events to
30570 the controller, so it can keep the user informed of progress (and
30571 problems) fetching directory information and establishing circuits;
30572 and adds a variety of smaller features.
30575 - More work on making our TLS handshake blend in: modify the list
30576 of ciphers advertised by OpenSSL in client mode to even more
30577 closely resemble a common web browser. We cheat a little so that
30578 we can advertise ciphers that the locally installed OpenSSL doesn't
30580 - Start sending "bootstrap phase" status events to the controller,
30581 so it can keep the user informed of progress fetching directory
30582 information and establishing circuits. Also inform the controller
30583 if we think we're stuck at a particular bootstrap phase. Implements
30585 - Resume using OpenSSL's RAND_poll() for better (and more portable)
30586 cross-platform entropy collection again. We used to use it, then
30587 stopped using it because of a bug that could crash systems that
30588 called RAND_poll when they had a lot of fds open. It looks like the
30589 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
30590 at startup, and to call RAND_poll() when we reseed later only if
30591 we have a non-buggy OpenSSL version.
30594 - When we choose to abandon a new entry guard because we think our
30595 older ones might be better, close any circuits pending on that
30596 new entry guard connection. This fix should make us recover much
30597 faster when our network is down and then comes back. Bugfix on
30598 0.1.2.8-beta; found by lodger.
30600 o Memory fixes and improvements:
30601 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
30602 to avoid unused RAM in buffer chunks and memory pools.
30603 - Speed up parsing and cut down on memory fragmentation by using
30604 stack-style allocations for parsing directory objects. Previously,
30605 this accounted for over 40% of allocations from within Tor's code
30606 on a typical directory cache.
30607 - Use a Bloom filter rather than a digest-based set to track which
30608 descriptors we need to keep around when we're cleaning out old
30609 router descriptors. This speeds up the computation significantly,
30610 and may reduce fragmentation.
30611 - Reduce the default smartlist size from 32 to 16; it turns out that
30612 most smartlists hold around 8-12 elements tops.
30613 - Make dumpstats() log the fullness and size of openssl-internal
30615 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
30616 patch to their OpenSSL, turn it on to save memory on servers. This
30617 patch will (with any luck) get included in a mainline distribution
30619 - Never use OpenSSL compression: it wastes RAM and CPU trying to
30620 compress cells, which are basically all encrypted, compressed,
30624 - Stop reloading the router list from disk for no reason when we
30625 run out of reachable directory mirrors. Once upon a time reloading
30626 it would set the 'is_running' flag back to 1 for them. It hasn't
30627 done that for a long time.
30628 - In very rare situations new hidden service descriptors were
30629 published earlier than 30 seconds after the last change to the
30630 service. (We currently think that a hidden service descriptor
30631 that's been stable for 30 seconds is worth publishing.)
30634 - Allow separate log levels to be configured for different logging
30635 domains. For example, this allows one to log all notices, warnings,
30636 or errors, plus all memory management messages of level debug or
30637 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
30638 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
30639 and stop using a warning that had become unfixably verbose under
30641 - New --hush command-line option similar to --quiet. While --quiet
30642 disables all logging to the console on startup, --hush limits the
30643 output to messages of warning and error severity.
30644 - Servers support a new URL scheme for consensus downloads that
30645 allows the client to specify which authorities are trusted.
30646 The server then only sends the consensus if the client will trust
30647 it. Otherwise a 404 error is sent back. Clients use this
30648 new scheme when the server supports it (meaning it's running
30649 0.2.1.1-alpha or later). Implements proposal 134.
30650 - New configure/torrc options (--enable-geoip-stats,
30651 DirRecordUsageByCountry) to record how many IPs we've served
30652 directory info to in each country code, how many status documents
30653 total we've sent to each country code, and what share of the total
30654 directory requests we should expect to see.
30655 - Use the TLS1 hostname extension to more closely resemble browser
30657 - Lots of new unit tests.
30658 - Add a macro to implement the common pattern of iterating through
30659 two parallel lists in lockstep.
30662 Changes in version 0.2.0.28-rc - 2008-06-13
30663 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
30664 performance bug, and fixes a bunch of smaller bugs.
30667 - Fix a bug where, when we were choosing the 'end stream reason' to
30668 put in our relay end cell that we send to the exit relay, Tor
30669 clients on Windows were sometimes sending the wrong 'reason'. The
30670 anonymity problem is that exit relays may be able to guess whether
30671 the client is running Windows, thus helping partition the anonymity
30672 set. Down the road we should stop sending reasons to exit relays,
30673 or otherwise prevent future versions of this bug.
30676 - While setting up a hidden service, some valid introduction circuits
30677 were overlooked and abandoned. This might be the reason for
30678 the long delay in making a hidden service available. Bugfix on
30682 - Update to the "June 9 2008" ip-to-country file.
30683 - Run 'make test' as part of 'make dist', so we stop releasing so
30684 many development snapshots that fail their unit tests.
30687 - When we're checking if we have enough dir info for each relay
30688 to begin establishing circuits, make sure that we actually have
30689 the descriptor listed in the consensus, not just any descriptor.
30691 - Bridge relays no longer print "xx=0" in their extrainfo document
30692 for every single country code in the geoip db. Bugfix on
30694 - Only warn when we fail to load the geoip file if we were planning to
30695 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
30696 - If we change our MaxAdvertisedBandwidth and then reload torrc,
30697 Tor won't realize it should publish a new relay descriptor. Fixes
30698 bug 688, reported by mfr. Bugfix on 0.1.2.x.
30699 - When we haven't had any application requests lately, don't bother
30700 logging that we have expired a bunch of descriptors. Bugfix
30702 - Make relay cells written on a connection count as non-padding when
30703 tracking how long a connection has been in use. Bugfix on
30704 0.2.0.1-alpha. Spotted by lodger.
30705 - Fix unit tests in 0.2.0.27-rc.
30706 - Fix compile on Windows.
30709 Changes in version 0.2.0.27-rc - 2008-06-03
30710 Tor 0.2.0.27-rc adds a few features we left out of the earlier
30711 release candidates. In particular, we now include an IP-to-country
30712 GeoIP database, so controllers can easily look up what country a
30713 given relay is in, and so bridge relays can give us some sanitized
30714 summaries about which countries are making use of bridges. (See proposal
30715 126-geoip-fetching.txt for details.)
30718 - Include an IP-to-country GeoIP file in the tarball, so bridge
30719 relays can report sanitized summaries of the usage they're seeing.
30722 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
30723 Robert Hogan. Fixes the first part of bug 681.
30724 - Make bridge authorities never serve extrainfo docs.
30725 - Add support to detect Libevent versions in the 1.4.x series
30727 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
30728 - Include a new contrib/tor-exit-notice.html file that exit relay
30729 operators can put on their website to help reduce abuse queries.
30732 - When tunneling an encrypted directory connection, and its first
30733 circuit fails, do not leave it unattached and ask the controller
30734 to deal. Fixes the second part of bug 681.
30735 - Make bridge authorities correctly expire old extrainfo documents
30739 Changes in version 0.2.0.26-rc - 2008-05-13
30740 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
30741 in Debian's OpenSSL packages. All users running any 0.2.0.x version
30742 should upgrade, whether they're running Debian or not.
30744 o Major security fixes:
30745 - Use new V3 directory authority keys on the tor26, gabelmoo, and
30746 moria1 V3 directory authorities. The old keys were generated with
30747 a vulnerable version of Debian's OpenSSL package, and must be
30748 considered compromised. Other authorities' keys were not generated
30749 with an affected version of OpenSSL.
30752 - List authority signatures as "unrecognized" based on DirServer
30753 lines, not on cert cache. Bugfix on 0.2.0.x.
30756 - Add a new V3AuthUseLegacyKey option to make it easier for
30757 authorities to change their identity keys if they have to.
30760 Changes in version 0.2.0.25-rc - 2008-04-23
30761 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
30764 - Remember to initialize threading before initializing logging.
30765 Otherwise, many BSD-family implementations will crash hard on
30766 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
30769 - Authorities correctly free policies on bad servers on
30770 exit. Fixes bug 672. Bugfix on 0.2.0.x.
30773 Changes in version 0.2.0.24-rc - 2008-04-22
30774 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
30775 v3 directory authority, makes relays with dynamic IP addresses and no
30776 DirPort notice more quickly when their IP address changes, fixes a few
30777 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
30779 o New directory authorities:
30780 - Take lefkada out of the list of v3 directory authorities, since
30781 it has been down for months.
30782 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
30786 - Detect address changes more quickly on non-directory mirror
30787 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
30789 o Minor features (security):
30790 - Reject requests for reverse-dns lookup of names that are in
30791 a private address space. Patch from lodger.
30792 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
30795 o Minor bugfixes (crashes):
30796 - Avoid a rare assert that can trigger when Tor doesn't have much
30797 directory information yet and it tries to fetch a v2 hidden
30798 service descriptor. Fixes bug 651, reported by nwf.
30799 - Initialize log mutex before initializing dmalloc. Otherwise,
30800 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
30801 - Use recursive pthread mutexes in order to avoid deadlock when
30802 logging debug-level messages to a controller. Bug spotted by nwf,
30803 bugfix on 0.2.0.16-alpha.
30805 o Minor bugfixes (resource management):
30806 - Keep address policies from leaking memory: start their refcount
30807 at 1, not 2. Bugfix on 0.2.0.16-alpha.
30808 - Free authority certificates on exit, so they don't look like memory
30809 leaks. Bugfix on 0.2.0.19-alpha.
30810 - Free static hashtables for policy maps and for TLS connections on
30811 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
30812 - Avoid allocating extra space when computing consensuses on 64-bit
30813 platforms. Bug spotted by aakova.
30815 o Minor bugfixes (misc):
30816 - Do not read the configuration file when we've only been told to
30817 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
30818 based on patch from Sebastian Hahn.
30819 - Exit relays that are used as a client can now reach themselves
30820 using the .exit notation, rather than just launching an infinite
30821 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
30822 - When attempting to open a logfile fails, tell us why.
30823 - Fix a dumb bug that was preventing us from knowing that we should
30824 preemptively build circuits to handle expected directory requests.
30825 Fixes bug 660. Bugfix on 0.1.2.x.
30826 - Warn less verbosely about clock skew from netinfo cells from
30827 untrusted sources. Fixes bug 663.
30828 - Make controller stream events for DNS requests more consistent,
30829 by adding "new stream" events for DNS requests, and removing
30830 spurious "stream closed" events" for cached reverse resolves.
30831 Patch from mwenge. Fixes bug 646.
30832 - Correctly notify one-hop connections when a circuit build has
30833 failed. Possible fix for bug 669. Found by lodger.
30836 Changes in version 0.2.0.23-rc - 2008-03-24
30837 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
30838 makes bootstrapping faster if the first directory mirror you contact
30839 is down. The bundles also include the new Vidalia 0.1.2 release.
30842 - When a tunneled directory request is made to a directory server
30843 that's down, notice after 30 seconds rather than 120 seconds. Also,
30844 fail any begindir streams that are pending on it, so they can
30845 retry elsewhere. This was causing multi-minute delays on bootstrap.
30848 Changes in version 0.2.0.22-rc - 2008-03-18
30849 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
30850 enables encrypted directory connections by default for non-relays, fixes
30851 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
30852 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
30855 - Enable encrypted directory connections by default for non-relays,
30856 so censor tools that block Tor directory connections based on their
30857 plaintext patterns will no longer work. This means Tor works in
30858 certain censored countries by default again.
30861 - Make sure servers always request certificates from clients during
30862 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
30863 - Do not enter a CPU-eating loop when a connection is closed in
30864 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
30865 diagnosed by lodger; bugfix on 0.2.0.20-rc.
30866 - Fix assertion failure that could occur when a blocked circuit
30867 became unblocked, and it had pending client DNS requests. Bugfix
30868 on 0.2.0.1-alpha. Fixes bug 632.
30870 o Minor bugfixes (on 0.1.2.x):
30871 - Generate "STATUS_SERVER" events rather than misspelled
30872 "STATUS_SEVER" events. Caught by mwenge.
30873 - When counting the number of bytes written on a TLS connection,
30874 look at the BIO actually used for writing to the network, not
30875 at the BIO used (sometimes) to buffer data for the network.
30876 Looking at different BIOs could result in write counts on the
30877 order of ULONG_MAX. Fixes bug 614.
30878 - On Windows, correctly detect errors when listing the contents of
30879 a directory. Fix from lodger.
30881 o Minor bugfixes (on 0.2.0.x):
30882 - Downgrade "sslv3 alert handshake failure" message to INFO.
30883 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
30884 left BandwidthRate and BandwidthBurst at the default, we would be
30885 silently limited by those defaults. Now raise them to match the
30886 RelayBandwidth* values.
30887 - Fix the SVK version detection logic to work correctly on a branch.
30888 - Make --enable-openbsd-malloc work correctly on Linux with alpha
30889 CPUs. Fixes bug 625.
30890 - Logging functions now check that the passed severity is sane.
30891 - Use proper log levels in the testsuite call of
30892 get_interface_address6().
30893 - When using a nonstandard malloc, do not use the platform values for
30894 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
30895 - Make the openbsd malloc code use 8k pages on alpha CPUs and
30897 - Detect mismatched page sizes when using --enable-openbsd-malloc.
30898 - Avoid double-marked-for-close warning when certain kinds of invalid
30899 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
30900 for bug 617. Bugfix on 0.2.0.1-alpha.
30901 - Make sure that the "NULL-means-reject *:*" convention is followed by
30902 all the policy manipulation functions, avoiding some possible crash
30903 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
30904 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
30905 actually works, and doesn't warn about every single reverse lookup.
30906 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
30909 - Only log guard node status when guard node status has changed.
30910 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
30911 make "INFO" 75% less verbose.
30914 Changes in version 0.2.0.21-rc - 2008-03-02
30915 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
30916 makes Tor work well with Vidalia again, fixes a rare assert bug,
30917 and fixes a pair of more minor bugs. The bundles also include Vidalia
30918 0.1.0 and Torbutton 1.1.16.
30921 - The control port should declare that it requires password auth
30922 when HashedControlSessionPassword is set too. Patch from Matt Edman;
30923 bugfix on 0.2.0.20-rc. Fixes bug 615.
30924 - Downgrade assert in connection_buckets_decrement() to a log message.
30925 This may help us solve bug 614, and in any case will make its
30926 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
30927 - We were sometimes miscounting the number of bytes read from the
30928 network, causing our rate limiting to not be followed exactly.
30929 Bugfix on 0.2.0.16-alpha. Reported by lodger.
30932 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
30933 OpenSSL versions should have been working fine. Diagnosis and patch
30934 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
30935 Bugfix on 0.2.0.20-rc.
30938 Changes in version 0.2.0.20-rc - 2008-02-24
30939 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
30940 makes more progress towards normalizing Tor's TLS handshake, makes
30941 hidden services work better again, helps relays bootstrap if they don't
30942 know their IP address, adds optional support for linking in openbsd's
30943 allocator or tcmalloc, allows really fast relays to scale past 15000
30944 sockets, and fixes a bunch of minor bugs reported by Veracode.
30947 - Enable the revised TLS handshake based on the one designed by
30948 Steven Murdoch in proposal 124, as revised in proposal 130. It
30949 includes version negotiation for OR connections as described in
30950 proposal 105. The new handshake is meant to be harder for censors
30951 to fingerprint, and it adds the ability to detect certain kinds of
30952 man-in-the-middle traffic analysis attacks. The version negotiation
30953 feature will allow us to improve Tor's link protocol more safely
30955 - Choose which bridge to use proportional to its advertised bandwidth,
30956 rather than uniformly at random. This should speed up Tor for
30957 bridge users. Also do this for people who set StrictEntryNodes.
30958 - When a TrackHostExits-chosen exit fails too many times in a row,
30959 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
30962 - Resolved problems with (re-)fetching hidden service descriptors.
30963 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
30964 and 0.2.0.19-alpha.
30965 - If we only ever used Tor for hidden service lookups or posts, we
30966 would stop building circuits and start refusing connections after
30967 24 hours, since we falsely believed that Tor was dormant. Reported
30968 by nwf; bugfix on 0.1.2.x.
30969 - Servers that don't know their own IP address should go to the
30970 authorities for their first directory fetch, even if their DirPort
30971 is off or if they don't know they're reachable yet. This will help
30972 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
30973 - When counting the number of open sockets, count not only the number
30974 of sockets we have received from the socket() call, but also
30975 the number we've gotten from accept() and socketpair(). This bug
30976 made us fail to count all sockets that we were using for incoming
30977 connections. Bugfix on 0.2.0.x.
30978 - Fix code used to find strings within buffers, when those strings
30979 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
30980 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
30981 - Add a new __HashedControlSessionPassword option for controllers
30982 to use for one-off session password hashes that shouldn't get
30983 saved to disk by SAVECONF --- Vidalia users were accumulating a
30984 pile of HashedControlPassword lines in their torrc files, one for
30985 each time they had restarted Tor and then clicked Save. Make Tor
30986 automatically convert "HashedControlPassword" to this new option but
30987 only when it's given on the command line. Partial fix for bug 586.
30989 o Minor features (performance):
30990 - Tune parameters for cell pool allocation to minimize amount of
30992 - Add OpenBSD malloc code from phk as an optional malloc
30993 replacement on Linux: some glibc libraries do very poorly
30994 with Tor's memory allocation patterns. Pass
30995 --enable-openbsd-malloc to get the replacement malloc code.
30996 - Add a --with-tcmalloc option to the configure script to link
30997 against tcmalloc (if present). Does not yet search for
30998 non-system include paths.
30999 - Stop imposing an arbitrary maximum on the number of file descriptors
31000 used for busy servers. Bug reported by Olaf Selke; patch from
31003 o Minor features (other):
31004 - When SafeLogging is disabled, log addresses along with all TLS
31006 - When building with --enable-gcc-warnings, check for whether Apple's
31007 warning "-Wshorten-64-to-32" is available.
31008 - Add a --passphrase-fd argument to the tor-gencert command for
31011 o Minor bugfixes (memory leaks and code problems):
31012 - We were leaking a file descriptor if Tor started with a zero-length
31013 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
31014 - Detect size overflow in zlib code. Reported by Justin Ferguson and
31016 - We were comparing the raw BridgePassword entry with a base64'ed
31017 version of it, when handling a "/tor/networkstatus-bridges"
31018 directory request. Now compare correctly. Noticed by Veracode.
31019 - Recover from bad tracked-since value in MTBF-history file.
31020 Should fix bug 537.
31021 - Alter the code that tries to recover from unhandled write
31022 errors, to not try to flush onto a socket that's given us
31023 unhandled errors. Bugfix on 0.1.2.x.
31024 - Make Unix controlsockets work correctly on OpenBSD. Patch from
31025 tup. Bugfix on 0.2.0.3-alpha.
31027 o Minor bugfixes (other):
31028 - If we have an extra-info document for our server, always make
31029 it available on the control port, even if we haven't gotten
31030 a copy of it from an authority yet. Patch from mwenge.
31031 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
31032 - Directory mirrors no longer include a guess at the client's IP
31033 address if the connection appears to be coming from the same /24
31034 network; it was producing too many wrong guesses.
31035 - Make the new hidden service code respect the SafeLogging setting.
31036 Bugfix on 0.2.0.x. Patch from Karsten.
31037 - When starting as an authority, do not overwrite all certificates
31038 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
31039 - If we're trying to flush the last bytes on a connection (for
31040 example, when answering a directory request), reset the
31041 time-to-give-up timeout every time we manage to write something
31042 on the socket. Bugfix on 0.1.2.x.
31043 - Change the behavior of "getinfo status/good-server-descriptor"
31044 so it doesn't return failure when any authority disappears.
31045 - Even though the man page said that "TrackHostExits ." should
31046 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
31047 - Report TLS "zero return" case as a "clean close" and "IO error"
31048 as a "close". Stop calling closes "unexpected closes": existing
31049 Tors don't use SSL_close(), so having a connection close without
31050 the TLS shutdown handshake is hardly unexpected.
31051 - Send NAMESERVER_STATUS messages for a single failed nameserver
31054 o Code simplifications and refactoring:
31055 - Remove the tor_strpartition function: its logic was confused,
31056 and it was only used for one thing that could be implemented far
31060 Changes in version 0.2.0.19-alpha - 2008-02-09
31061 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
31062 handshake, makes path selection for relays more secure and IP address
31063 guessing more robust, and generally fixes a lot of bugs in preparation
31064 for calling the 0.2.0 branch stable.
31067 - Do not include recognizeable strings in the commonname part of
31068 Tor's x509 certificates.
31071 - If we're a relay, avoid picking ourselves as an introduction point,
31072 a rendezvous point, or as the final hop for internal circuits. Bug
31073 reported by taranis and lodger. Bugfix on 0.1.2.x.
31074 - Patch from "Andrew S. Lists" to catch when we contact a directory
31075 mirror at IP address X and he says we look like we're coming from
31076 IP address X. Bugfix on 0.1.2.x.
31078 o Minor features (security):
31079 - Be more paranoid about overwriting sensitive memory on free(),
31080 as a defensive programming tactic to ensure forward secrecy.
31082 o Minor features (directory authority):
31083 - Actually validate the options passed to AuthDirReject,
31084 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
31085 - Reject router descriptors with out-of-range bandwidthcapacity or
31086 bandwidthburst values.
31088 o Minor features (controller):
31089 - Reject controller commands over 1MB in length. This keeps rogue
31090 processes from running us out of memory.
31092 o Minor features (misc):
31093 - Give more descriptive well-formedness errors for out-of-range
31094 hidden service descriptor/protocol versions.
31095 - Make memory debugging information describe more about history
31096 of cell allocation, so we can help reduce our memory use.
31098 o Deprecated features (controller):
31099 - The status/version/num-versioning and status/version/num-concurring
31100 GETINFO options are no longer useful in the v3 directory protocol:
31101 treat them as deprecated, and warn when they're used.
31104 - When our consensus networkstatus has been expired for a while, stop
31105 being willing to build circuits using it. Fixes bug 401. Bugfix
31107 - Directory caches now fetch certificates from all authorities
31108 listed in a networkstatus consensus, even when they do not
31109 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
31110 - When connecting to a bridge without specifying its key, insert
31111 the connection into the identity-to-connection map as soon as
31112 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
31113 - Detect versions of OS X where malloc_good_size() is present in the
31114 library but never actually declared. Resolves bug 587. Bugfix
31116 - Stop incorrectly truncating zlib responses to directory authority
31117 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
31118 - Stop recommending that every server operator send mail to tor-ops.
31119 Resolves bug 597. Bugfix on 0.1.2.x.
31120 - Don't trigger an assert if we start a directory authority with a
31121 private IP address (like 127.0.0.1).
31122 - Avoid possible failures when generating a directory with routers
31123 with over-long versions strings, or too many flags set. Bugfix
31125 - If an attempt to launch a DNS resolve request over the control
31126 port fails because we have overrun the limit on the number of
31127 connections, tell the controller that the request has failed.
31128 - Avoid using too little bandwidth when our clock skips a few
31129 seconds. Bugfix on 0.1.2.x.
31130 - Fix shell error when warning about missing packages in configure
31131 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
31132 - Do not become confused when receiving a spurious VERSIONS-like
31133 cell from a confused v1 client. Bugfix on 0.2.0.x.
31134 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
31135 introduction points for a hidden service have failed. Patch from
31136 Karsten Loesing. Bugfix on 0.2.0.x.
31138 o Code simplifications and refactoring:
31139 - Remove some needless generality from cpuworker code, for improved
31141 - Stop overloading the circuit_t.onionskin field for both "onionskin
31142 from a CREATE cell that we are waiting for a cpuworker to be
31143 assigned" and "onionskin from an EXTEND cell that we are going to
31144 send to an OR as soon as we are connected". Might help with bug 600.
31145 - Add an in-place version of aes_crypt() so that we can avoid doing a
31146 needless memcpy() call on each cell payload.
31149 Changes in version 0.2.0.18-alpha - 2008-01-25
31150 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
31151 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
31152 that can warn or reject connections to ports generally associated with
31153 vulnerable-plaintext protocols.
31155 o New directory authorities:
31156 - Set up dannenberg (run by CCC) as the sixth v3 directory
31160 - Fix a major memory leak when attempting to use the v2 TLS
31161 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
31162 - We accidentally enabled the under-development v2 TLS handshake
31163 code, which was causing log entries like "TLS error while
31164 renegotiating handshake". Disable it again. Resolves bug 590.
31165 - We were computing the wrong Content-Length: header for directory
31166 responses that need to be compressed on the fly, causing clients
31167 asking for those items to always fail. Bugfix on 0.2.0.x; partially
31171 - Avoid going directly to the directory authorities even if you're a
31172 relay, if you haven't found yourself reachable yet or if you've
31173 decided not to advertise your dirport yet. Addresses bug 556.
31174 - If we've gone 12 hours since our last bandwidth check, and we
31175 estimate we have less than 50KB bandwidth capacity but we could
31176 handle more, do another bandwidth test.
31177 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
31178 Tor can warn and/or refuse connections to ports commonly used with
31179 vulnerable-plaintext protocols. Currently we warn on ports 23,
31180 109, 110, and 143, but we don't reject any.
31183 - When we setconf ClientOnly to 1, close any current OR and Dir
31184 listeners. Reported by mwenge.
31185 - When we get a consensus that's been signed by more people than
31186 we expect, don't log about it; it's not a big deal. Reported
31190 - Don't answer "/tor/networkstatus-bridges" directory requests if
31191 the request isn't encrypted.
31192 - Make "ClientOnly 1" config option disable directory ports too.
31193 - Patches from Karsten Loesing to make v2 hidden services more
31194 robust: work even when there aren't enough HSDir relays available;
31195 retry when a v2 rend desc fetch fails; but don't retry if we
31196 already have a usable v0 rend desc.
31199 Changes in version 0.2.0.17-alpha - 2008-01-17
31200 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
31203 - Make the tor-gencert man page get included correctly in the tarball.
31206 Changes in version 0.2.0.16-alpha - 2008-01-17
31207 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
31208 Loesing, and generally cleans up a lot of features and minor bugs.
31210 o New directory authorities:
31211 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
31214 o Major performance improvements:
31215 - Switch our old ring buffer implementation for one more like that
31216 used by free Unix kernels. The wasted space in a buffer with 1mb
31217 of data will now be more like 8k than 1mb. The new implementation
31218 also avoids realloc();realloc(); patterns that can contribute to
31219 memory fragmentation.
31222 - Configuration files now accept C-style strings as values. This
31223 helps encode characters not allowed in the current configuration
31224 file format, such as newline or #. Addresses bug 557.
31225 - Although we fixed bug 539 (where servers would send HTTP status 503
31226 responses _and_ send a body too), there are still servers out
31227 there that haven't upgraded. Therefore, make clients parse such
31228 bodies when they receive them.
31229 - When we're not serving v2 directory information, there is no reason
31230 to actually keep any around. Remove the obsolete files and directory
31231 on startup if they are very old and we aren't going to serve them.
31233 o Minor performance improvements:
31234 - Reference-count and share copies of address policy entries; only 5%
31235 of them were actually distinct.
31236 - Never walk through the list of logs if we know that no log is
31237 interested in a given message.
31240 - When an authority has not signed a consensus, do not try to
31241 download a nonexistent "certificate with key 00000000". Bugfix
31242 on 0.2.0.x. Fixes bug 569.
31243 - Fix a rare assert error when we're closing one of our threads:
31244 use a mutex to protect the list of logs, so we never write to the
31245 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
31246 bug 575, which is kind of the revenge of bug 222.
31247 - Patch from Karsten Loesing to complain less at both the client
31248 and the relay when a relay used to have the HSDir flag but doesn't
31249 anymore, and we try to upload a hidden service descriptor.
31250 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
31252 - Do not try to download missing certificates until we have tried
31253 to check our fallback consensus. Fixes bug 583.
31254 - Make bridges round reported GeoIP stats info up to the nearest
31255 estimate, not down. Now we can distinguish between "0 people from
31256 this country" and "1 person from this country".
31257 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
31258 - Avoid possible segfault if key generation fails in
31259 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
31260 - Avoid segfault in the case where a badly behaved v2 versioning
31261 directory sends a signed networkstatus with missing client-versions.
31263 - Avoid segfaults on certain complex invocations of
31264 router_get_by_hexdigest(). Bugfix on 0.1.2.
31265 - Correct bad index on array access in parse_http_time(). Bugfix
31267 - Fix possible bug in vote generation when server versions are present
31268 but client versions are not.
31269 - Fix rare bug on REDIRECTSTREAM control command when called with no
31270 port set: it could erroneously report an error when none had
31272 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
31273 compressing large objects and find ourselves with more than 4k
31274 left over. Bugfix on 0.2.0.
31275 - Fix a small memory leak when setting up a hidden service.
31276 - Fix a few memory leaks that could in theory happen under bizarre
31278 - Fix an assert if we post a general-purpose descriptor via the
31279 control port but that descriptor isn't mentioned in our current
31280 network consensus. Bug reported by Jon McLachlan; bugfix on
31283 o Minor features (controller):
31284 - Get NS events working again. Patch from tup.
31285 - The GETCONF command now escapes and quotes configuration values
31286 that don't otherwise fit into the torrc file.
31287 - The SETCONF command now handles quoted values correctly.
31289 o Minor features (directory authorities):
31290 - New configuration options to override default maximum number of
31291 servers allowed on a single IP address. This is important for
31292 running a test network on a single host.
31293 - Actually implement the -s option to tor-gencert.
31294 - Add a manual page for tor-gencert.
31296 o Minor features (bridges):
31297 - Bridge authorities no longer serve bridge descriptors over
31298 unencrypted connections.
31300 o Minor features (other):
31301 - Add hidden services and DNSPorts to the list of things that make
31302 Tor accept that it has running ports. Change starting Tor with no
31303 ports from a fatal error to a warning; we might change it back if
31304 this turns out to confuse anybody. Fixes bug 579.
31307 Changes in version 0.1.2.19 - 2008-01-17
31308 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
31309 exit policy a little bit more conservative so it's safer to run an
31310 exit relay on a home system, and fixes a variety of smaller issues.
31313 - Exit policies now reject connections that are addressed to a
31314 relay's public (external) IP address too, unless
31315 ExitPolicyRejectPrivate is turned off. We do this because too
31316 many relays are running nearby to services that trust them based
31317 on network address.
31320 - When the clock jumps forward a lot, do not allow the bandwidth
31321 buckets to become negative. Fixes bug 544.
31322 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
31323 on every successful resolve. Reported by Mike Perry.
31324 - Purge old entries from the "rephist" database and the hidden
31325 service descriptor database even when DirPort is zero.
31326 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
31327 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
31328 crashing or mis-answering these requests.
31329 - When we decide to send a 503 response to a request for servers, do
31330 not then also send the server descriptors: this defeats the whole
31331 purpose. Fixes bug 539.
31334 - Changing the ExitPolicyRejectPrivate setting should cause us to
31335 rebuild our server descriptor.
31336 - Fix handling of hex nicknames when answering controller requests for
31337 networkstatus by name, or when deciding whether to warn about
31338 unknown routers in a config option. (Patch from mwenge.)
31339 - Fix a couple of hard-to-trigger autoconf problems that could result
31340 in really weird results on platforms whose sys/types.h files define
31341 nonstandard integer types.
31342 - Don't try to create the datadir when running --verify-config or
31343 --hash-password. Resolves bug 540.
31344 - If we were having problems getting a particular descriptor from the
31345 directory caches, and then we learned about a new descriptor for
31346 that router, we weren't resetting our failure count. Reported
31348 - Although we fixed bug 539 (where servers would send HTTP status 503
31349 responses _and_ send a body too), there are still servers out there
31350 that haven't upgraded. Therefore, make clients parse such bodies
31351 when they receive them.
31352 - Run correctly on systems where rlim_t is larger than unsigned long.
31353 This includes some 64-bit systems.
31354 - Run correctly on platforms (like some versions of OS X 10.5) where
31355 the real limit for number of open files is OPEN_FILES, not rlim_max
31356 from getrlimit(RLIMIT_NOFILES).
31357 - Avoid a spurious free on base64 failure.
31358 - Avoid segfaults on certain complex invocations of
31359 router_get_by_hexdigest().
31360 - Fix rare bug on REDIRECTSTREAM control command when called with no
31361 port set: it could erroneously report an error when none had
31365 Changes in version 0.2.0.15-alpha - 2007-12-25
31366 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
31367 features added in 0.2.0.13-alpha.
31370 - Fix several remotely triggerable asserts based on DirPort requests
31371 for a v2 or v3 networkstatus object before we were prepared. This
31372 was particularly bad for 0.2.0.13 and later bridge relays, who
31373 would never have a v2 networkstatus and would thus always crash
31374 when used. Bugfixes on 0.2.0.x.
31375 - Estimate the v3 networkstatus size more accurately, rather than
31376 estimating it at zero bytes and giving it artificially high priority
31377 compared to other directory requests. Bugfix on 0.2.0.x.
31380 - Fix configure.in logic for cross-compilation.
31381 - When we load a bridge descriptor from the cache, and it was
31382 previously unreachable, mark it as retriable so we won't just
31383 ignore it. Also, try fetching a new copy immediately. Bugfixes
31385 - The bridge GeoIP stats were counting other relays, for example
31386 self-reachability and authority-reachability tests.
31389 - Support compilation to target iPhone; patch from cjacker huang.
31390 To build for iPhone, pass the --enable-iphone option to configure.
31393 Changes in version 0.2.0.14-alpha - 2007-12-23
31395 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
31396 without a datadirectory from a previous Tor install. Reported
31398 - Fix a crash when we fetch a descriptor that turns out to be
31399 unexpected (it used to be in our networkstatus when we started
31400 fetching it, but it isn't in our current networkstatus), and we
31401 aren't using bridges. Bugfix on 0.2.0.x.
31402 - Fix a crash when accessing hidden services: it would work the first
31403 time you use a given introduction point for your service, but
31404 on subsequent requests we'd be using garbage memory. Fixed by
31405 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
31406 - Fix a crash when we load a bridge descriptor from disk but we don't
31407 currently have a Bridge line for it in our torrc. Bugfix on
31411 - If bridge authorities set BridgePassword, they will serve a
31412 snapshot of known bridge routerstatuses from their DirPort to
31413 anybody who knows that password. Unset by default.
31416 - Make the unit tests build again.
31417 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
31418 - Make PublishServerDescriptor default to 1, so the default doesn't
31419 have to change as we invent new directory protocol versions.
31420 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
31421 be included unless sys/time.h is already included. Fixes
31422 bug 553. Bugfix on 0.2.0.x.
31423 - If we receive a general-purpose descriptor and then receive an
31424 identical bridge-purpose descriptor soon after, don't discard
31425 the next one as a duplicate.
31428 - If BridgeRelay is set to 1, then the default for
31429 PublishServerDescriptor is now "bridge" rather than "v2,v3".
31430 - If the user sets RelayBandwidthRate but doesn't set
31431 RelayBandwidthBurst, then make them equal rather than erroring out.
31434 Changes in version 0.2.0.13-alpha - 2007-12-21
31435 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
31436 Goodell, fixes many more bugs, and adds a lot of infrastructure for
31439 o New directory authorities:
31440 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
31444 - Only update guard status (usable / not usable) once we have
31445 enough directory information. This was causing us to always pick
31446 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
31447 causing us to discard all our guards on startup if we hadn't been
31448 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
31449 - Purge old entries from the "rephist" database and the hidden
31450 service descriptor databases even when DirPort is zero. Bugfix
31452 - We were ignoring our RelayBandwidthRate for the first 30 seconds
31453 after opening a circuit -- even a relayed circuit. Bugfix on
31455 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
31456 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
31457 crashing or mis-answering these types of requests.
31458 - Relays were publishing their server descriptor to v1 and v2
31459 directory authorities, but they didn't try publishing to v3-only
31460 authorities. Fix this; and also stop publishing to v1 authorities.
31462 - When we were reading router descriptors from cache, we were ignoring
31463 the annotations -- so for example we were reading in bridge-purpose
31464 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
31465 - When we decided to send a 503 response to a request for servers, we
31466 were then also sending the server descriptors: this defeats the
31467 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
31470 - Bridge relays now behave like clients with respect to time
31471 intervals for downloading new consensus documents -- otherwise they
31472 stand out. Bridge users now wait until the end of the interval,
31473 so their bridge relay will be sure to have a new consensus document.
31474 - Three new config options (AlternateDirAuthority,
31475 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
31476 user selectively replace the default directory authorities by type,
31477 rather than the all-or-nothing replacement that DirServer offers.
31478 - Tor can now be configured to read a GeoIP file from disk in one
31479 of two formats. This can be used by controllers to map IP addresses
31480 to countries. Eventually, it may support exit-by-country.
31481 - When possible, bridge relays remember which countries users
31482 are coming from, and report aggregate information in their
31483 extra-info documents, so that the bridge authorities can learn
31484 where Tor is blocked.
31485 - Bridge directory authorities now do reachability testing on the
31486 bridges they know. They provide router status summaries to the
31487 controller via "getinfo ns/purpose/bridge", and also dump summaries
31488 to a file periodically.
31489 - Stop fetching directory info so aggressively if your DirPort is
31490 on but your ORPort is off; stop fetching v2 dir info entirely.
31491 You can override these choices with the new FetchDirInfoEarly
31495 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
31496 consensus documents when there are too many relays at a single
31497 IP address. Now clear it in v2 network status documents too, and
31498 also clear it in routerinfo_t when the relay is no longer listed
31499 in the relevant networkstatus document.
31500 - Don't crash if we get an unexpected value for the
31501 PublishServerDescriptor config option. Reported by Matt Edman;
31502 bugfix on 0.2.0.9-alpha.
31503 - Our new v2 hidden service descriptor format allows descriptors
31504 that have no introduction points. But Tor crashed when we tried
31505 to build a descriptor with no intro points (and it would have
31506 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
31507 by Karsten Loesing.
31508 - Fix building with dmalloc 5.5.2 with glibc.
31509 - Reject uploaded descriptors and extrainfo documents if they're
31510 huge. Otherwise we'll cache them all over the network and it'll
31511 clog everything up. Reported by Aljosha Judmayer.
31512 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
31513 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
31514 - When the DANGEROUS_VERSION controller status event told us we're
31515 running an obsolete version, it used the string "OLD" to describe
31516 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
31517 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
31518 - If we can't expand our list of entry guards (e.g. because we're
31519 using bridges or we have StrictEntryNodes set), don't mark relays
31520 down when they fail a directory request. Otherwise we're too quick
31521 to mark all our entry points down. Bugfix on 0.1.2.x.
31522 - Fix handling of hex nicknames when answering controller requests for
31523 networkstatus by name, or when deciding whether to warn about unknown
31524 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
31525 - Fix a couple of hard-to-trigger autoconf problems that could result
31526 in really weird results on platforms whose sys/types.h files define
31527 nonstandard integer types. Bugfix on 0.1.2.x.
31528 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
31529 - Don't crash on name lookup when we have no current consensus. Fixes
31530 bug 538; bugfix on 0.2.0.x.
31531 - Only Tors that want to mirror the v2 directory info should
31532 create the "cached-status" directory in their datadir. (All Tors
31533 used to create it.) Bugfix on 0.2.0.9-alpha.
31534 - Directory authorities should only automatically download Extra Info
31535 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
31538 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
31539 consumers. (We already do this on HUP.)
31540 - Authorities and caches fetch the v2 networkstatus documents
31541 less often, now that v3 is encouraged.
31542 - Add a new config option BridgeRelay that specifies you want to
31543 be a bridge relay. Right now the only difference is that it makes
31544 you answer begin_dir requests, and it makes you cache dir info,
31545 even if your DirPort isn't on.
31546 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
31547 ask about source, timestamp of arrival, purpose, etc. We need
31548 something like this to help Vidalia not do GeoIP lookups on bridge
31550 - Allow multiple HashedControlPassword config lines, to support
31551 multiple controller passwords.
31552 - Authorities now decide whether they're authoritative for a given
31553 router based on the router's purpose.
31554 - New config options AuthDirBadDir and AuthDirListBadDirs for
31555 authorities to mark certain relays as "bad directories" in the
31556 networkstatus documents. Also supports the "!baddir" directive in
31557 the approved-routers file.
31560 Changes in version 0.2.0.12-alpha - 2007-11-16
31561 This twelfth development snapshot fixes some more build problems as
31562 well as a few minor bugs.
31565 - Make it build on OpenBSD again. Patch from tup.
31566 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
31567 package-building for Red Hat, OS X, etc.
31569 o Minor bugfixes (on 0.1.2.x):
31570 - Changing the ExitPolicyRejectPrivate setting should cause us to
31571 rebuild our server descriptor.
31573 o Minor bugfixes (on 0.2.0.x):
31574 - When we're lacking a consensus, don't try to perform rendezvous
31575 operations. Reported by Karsten Loesing.
31576 - Fix a small memory leak whenever we decide against using a
31577 newly picked entry guard. Reported by Mike Perry.
31578 - When authorities detected more than two relays running on the same
31579 IP address, they were clearing all the status flags but forgetting
31580 to clear the "hsdir" flag. So clients were being told that a
31581 given relay was the right choice for a v2 hsdir lookup, yet they
31582 never had its descriptor because it was marked as 'not running'
31584 - If we're trying to fetch a bridge descriptor and there's no way
31585 the bridge authority could help us (for example, we don't know
31586 a digest, or there is no bridge authority), don't be so eager to
31587 fall back to asking the bridge authority.
31588 - If we're using bridges or have strictentrynodes set, and our
31589 chosen exit is in the same family as all our bridges/entry guards,
31590 then be flexible about families.
31593 - When we negotiate a v2 link-layer connection (not yet implemented),
31594 accept RELAY_EARLY cells and turn them into RELAY cells if we've
31595 negotiated a v1 connection for their next step. Initial code for
31599 Changes in version 0.2.0.11-alpha - 2007-11-12
31600 This eleventh development snapshot fixes some build problems with
31601 the previous snapshot. It also includes a more secure-by-default exit
31602 policy for relays, fixes an enormous memory leak for exit relays, and
31603 fixes another bug where servers were falling out of the directory list.
31606 - Exit policies now reject connections that are addressed to a
31607 relay's public (external) IP address too, unless
31608 ExitPolicyRejectPrivate is turned off. We do this because too
31609 many relays are running nearby to services that trust them based
31610 on network address. Bugfix on 0.1.2.x.
31613 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
31614 on every successful resolve. Reported by Mike Perry; bugfix
31616 - On authorities, never downgrade to old router descriptors simply
31617 because they're listed in the consensus. This created a catch-22
31618 where we wouldn't list a new descriptor because there was an
31619 old one in the consensus, and we couldn't get the new one in the
31620 consensus because we wouldn't list it. Possible fix for bug 548.
31621 Also, this might cause bug 543 to appear on authorities; if so,
31622 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
31624 o Packaging fixes on 0.2.0.10-alpha:
31625 - We were including instructions about what to do with the
31626 src/config/fallback-consensus file, but we weren't actually
31627 including it in the tarball. Disable all of that for now.
31630 - Allow people to say PreferTunnelledDirConns rather than
31631 PreferTunneledDirConns, for those alternate-spellers out there.
31634 - Don't reevaluate all the information from our consensus document
31635 just because we've downloaded a v2 networkstatus that we intend
31636 to cache. Fixes bug 545; bugfix on 0.2.0.x.
31639 Changes in version 0.2.0.10-alpha - 2007-11-10
31640 This tenth development snapshot adds a third v3 directory authority
31641 run by Mike Perry, adds most of Karsten Loesing's new hidden service
31642 descriptor format, fixes a bad crash bug and new bridge bugs introduced
31643 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
31644 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
31645 addresses many more minor issues.
31647 o New directory authorities:
31648 - Set up ides (run by Mike Perry) as the third v3 directory authority.
31651 - Allow tunnelled directory connections to ask for an encrypted
31652 "begin_dir" connection or an anonymized "uses a full Tor circuit"
31653 connection independently. Now we can make anonymized begin_dir
31654 connections for (e.g.) more secure hidden service posting and
31656 - More progress on proposal 114: code from Karsten Loesing to
31657 implement new hidden service descriptor format.
31658 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
31659 accommodate the growing number of servers that use the default
31660 and are reaching it.
31661 - Directory authorities use a new formula for selecting which nodes
31662 to advertise as Guards: they must be in the top 7/8 in terms of
31663 how long we have known about them, and above the median of those
31664 nodes in terms of weighted fractional uptime.
31665 - Make "not enough dir info yet" warnings describe *why* Tor feels
31666 it doesn't have enough directory info yet.
31669 - Stop servers from crashing if they set a Family option (or
31670 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
31672 - Make bridge users work again -- the move to v3 directories in
31673 0.2.0.9-alpha had introduced a number of bugs that made bridges
31674 no longer work for clients.
31675 - When the clock jumps forward a lot, do not allow the bandwidth
31676 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
31678 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
31679 - When the consensus lists a router descriptor that we previously were
31680 mirroring, but that we considered non-canonical, reload the
31681 descriptor as canonical. This fixes bug 543 where Tor servers
31682 would start complaining after a few days that they don't have
31683 enough directory information to build a circuit.
31684 - Consider replacing the current consensus when certificates arrive
31685 that make the pending consensus valid. Previously, we were only
31686 considering replacement when the new certs _didn't_ help.
31687 - Fix an assert error on startup if we didn't already have the
31688 consensus and certs cached in our datadirectory: we were caching
31689 the consensus in consensus_waiting_for_certs but then free'ing it
31691 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
31692 Request) if we need more v3 certs but we've already got pending
31693 requests for all of them.
31694 - Correctly back off from failing certificate downloads. Fixes
31696 - Authorities don't vote on the Running flag if they have been running
31697 for less than 30 minutes themselves. Fixes bug 547, where a newly
31698 started authority would vote that everyone was down.
31700 o New requirements:
31701 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
31702 it, it had no AES, and it hasn't seen any security patches since
31706 - Clients now hold circuitless TLS connections open for 1.5 times
31707 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
31708 rebuild a new circuit over them within that timeframe. Previously,
31709 they held them open only for KeepalivePeriod (5 minutes).
31710 - Use "If-Modified-Since" to avoid retrieving consensus
31711 networkstatuses that we already have.
31712 - When we have no consensus, check FallbackNetworkstatusFile (defaults
31713 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
31714 we start knowing some directory caches.
31715 - When we receive a consensus from the future, warn about skew.
31716 - Improve skew reporting: try to give the user a better log message
31717 about how skewed they are, and how much this matters.
31718 - When we have a certificate for an authority, believe that
31719 certificate's claims about the authority's IP address.
31720 - New --quiet command-line option to suppress the default console log.
31721 Good in combination with --hash-password.
31722 - Authorities send back an X-Descriptor-Not-New header in response to
31723 an accepted-but-discarded descriptor upload. Partially implements
31725 - Make the log message for "tls error. breaking." more useful.
31726 - Better log messages about certificate downloads, to attempt to
31727 track down the second incarnation of bug 546.
31729 o Minor features (bridges):
31730 - If bridge users set UpdateBridgesFromAuthority, but the digest
31731 they ask for is a 404 from the bridge authority, they now fall
31732 back to trying the bridge directly.
31733 - Bridges now use begin_dir to publish their server descriptor to
31734 the bridge authority, even when they haven't set TunnelDirConns.
31736 o Minor features (controller):
31737 - When reporting clock skew, and we know that the clock is _at least
31738 as skewed_ as some value, but we don't know the actual value,
31739 report the value as a "minimum skew."
31742 - Update linux-tor-prio.sh script to allow QoS based on the uid of
31743 the Tor process. Patch from Marco Bonetti with tweaks from Mike
31747 - Refuse to start if both ORPort and UseBridges are set. Bugfix
31748 on 0.2.0.x, suggested by Matt Edman.
31749 - Don't stop fetching descriptors when FetchUselessDescriptors is
31750 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
31751 reported by tup and ioerror.
31752 - Better log message on vote from unknown authority.
31753 - Don't log "Launching 0 request for 0 router" message.
31755 o Minor bugfixes (memory leaks):
31756 - Stop leaking memory every time we parse a v3 certificate. Bugfix
31758 - Stop leaking memory every time we load a v3 certificate. Bugfix
31759 on 0.2.0.1-alpha. Fixes bug 536.
31760 - Stop leaking a cached networkstatus on exit. Bugfix on
31762 - Stop leaking voter information every time we free a consensus.
31763 Bugfix on 0.2.0.3-alpha.
31764 - Stop leaking signed data every time we check a voter signature.
31765 Bugfix on 0.2.0.3-alpha.
31766 - Stop leaking a signature every time we fail to parse a consensus or
31767 a vote. Bugfix on 0.2.0.3-alpha.
31768 - Stop leaking v2_download_status_map on shutdown. Bugfix on
31770 - Stop leaking conn->nickname every time we make a connection to a
31771 Tor relay without knowing its expected identity digest (e.g. when
31772 using bridges). Bugfix on 0.2.0.3-alpha.
31774 - Minor bugfixes (portability):
31775 - Run correctly on platforms where rlim_t is larger than unsigned
31776 long, and/or where the real limit for number of open files is
31777 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
31778 particular, these may be needed for OS X 10.5.
31781 Changes in version 0.1.2.18 - 2007-10-28
31782 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
31783 hidden service introduction that were causing huge delays, and a big
31784 bug that was causing some servers to disappear from the network status
31785 lists for a few hours each day.
31787 o Major bugfixes (crashes):
31788 - If a connection is shut down abruptly because of something that
31789 happened inside connection_flushed_some(), do not call
31790 connection_finished_flushing(). Should fix bug 451:
31791 "connection_stop_writing: Assertion conn->write_event failed"
31792 Bugfix on 0.1.2.7-alpha.
31793 - Fix possible segfaults in functions called from
31794 rend_process_relay_cell().
31796 o Major bugfixes (hidden services):
31797 - Hidden services were choosing introduction points uniquely by
31798 hexdigest, but when constructing the hidden service descriptor
31799 they merely wrote the (potentially ambiguous) nickname.
31800 - Clients now use the v2 intro format for hidden service
31801 connections: they specify their chosen rendezvous point by identity
31802 digest rather than by (potentially ambiguous) nickname. These
31803 changes could speed up hidden service connections dramatically.
31805 o Major bugfixes (other):
31806 - Stop publishing a new server descriptor just because we get a
31807 HUP signal. This led (in a roundabout way) to some servers getting
31808 dropped from the networkstatus lists for a few hours each day.
31809 - When looking for a circuit to cannibalize, consider family as well
31810 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
31811 circuit cannibalization).
31812 - When a router wasn't listed in a new networkstatus, we were leaving
31813 the flags for that router alone -- meaning it remained Named,
31814 Running, etc -- even though absence from the networkstatus means
31815 that it shouldn't be considered to exist at all anymore. Now we
31816 clear all the flags for routers that fall out of the networkstatus
31817 consensus. Fixes bug 529.
31820 - Don't try to access (or alter) the state file when running
31821 --list-fingerprint or --verify-config or --hash-password. Resolves
31823 - When generating information telling us how to extend to a given
31824 router, do not try to include the nickname if it is
31825 absent. Resolves bug 467.
31826 - Fix a user-triggerable segfault in expand_filename(). (There isn't
31827 a way to trigger this remotely.)
31828 - When sending a status event to the controller telling it that an
31829 OR address is reachable, set the port correctly. (Previously we
31830 were reporting the dir port.)
31831 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
31832 command. Bugfix on 0.1.2.17.
31833 - When loading bandwidth history, do not believe any information in
31834 the future. Fixes bug 434.
31835 - When loading entry guard information, do not believe any information
31837 - When we have our clock set far in the future and generate an
31838 onion key, then re-set our clock to be correct, we should not stop
31839 the onion key from getting rotated.
31840 - On some platforms, accept() can return a broken address. Detect
31841 this more quietly, and deal accordingly. Fixes bug 483.
31842 - It's not actually an error to find a non-pending entry in the DNS
31843 cache when canceling a pending resolve. Don't log unless stuff
31844 is fishy. Resolves bug 463.
31845 - Don't reset trusted dir server list when we set a configuration
31846 option. Patch from Robert Hogan.
31847 - Don't try to create the datadir when running --verify-config or
31848 --hash-password. Resolves bug 540.
31851 Changes in version 0.2.0.9-alpha - 2007-10-24
31852 This ninth development snapshot switches clients to the new v3 directory
31853 system; allows servers to be listed in the network status even when they
31854 have the same nickname as a registered server; and fixes many other
31855 bugs including a big one that was causing some servers to disappear
31856 from the network status lists for a few hours each day.
31858 o Major features (directory system):
31859 - Clients now download v3 consensus networkstatus documents instead
31860 of v2 networkstatus documents. Clients and caches now base their
31861 opinions about routers on these consensus documents. Clients only
31862 download router descriptors listed in the consensus.
31863 - Authorities now list servers who have the same nickname as
31864 a different named server, but list them with a new flag,
31865 "Unnamed". Now we can list servers that happen to pick the same
31866 nickname as a server that registered two years ago and then
31867 disappeared. Partially implements proposal 122.
31868 - If the consensus lists a router as "Unnamed", the name is assigned
31869 to a different router: do not identify the router by that name.
31870 Partially implements proposal 122.
31871 - Authorities can now come to a consensus on which method to use to
31872 compute the consensus. This gives us forward compatibility.
31875 - Stop publishing a new server descriptor just because we HUP or
31876 when we find our DirPort to be reachable but won't actually publish
31877 it. New descriptors without any real changes are dropped by the
31878 authorities, and can screw up our "publish every 18 hours" schedule.
31880 - When a router wasn't listed in a new networkstatus, we were leaving
31881 the flags for that router alone -- meaning it remained Named,
31882 Running, etc -- even though absence from the networkstatus means
31883 that it shouldn't be considered to exist at all anymore. Now we
31884 clear all the flags for routers that fall out of the networkstatus
31885 consensus. Fixes bug 529; bugfix on 0.1.2.x.
31886 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
31887 extrainfo documents and then discard them immediately for not
31888 matching the latest router. Bugfix on 0.2.0.1-alpha.
31890 o Minor features (v3 directory protocol):
31891 - Allow tor-gencert to generate a new certificate without replacing
31893 - Allow certificates to include an address.
31894 - When we change our directory-cache settings, reschedule all voting
31895 and download operations.
31896 - Reattempt certificate downloads immediately on failure, as long as
31897 we haven't failed a threshold number of times yet.
31898 - Delay retrying consensus downloads while we're downloading
31899 certificates to verify the one we just got. Also, count getting a
31900 consensus that we already have (or one that isn't valid) as a failure,
31901 and count failing to get the certificates after 20 minutes as a
31903 - Build circuits and download descriptors even if our consensus is a
31904 little expired. (This feature will go away once authorities are
31907 o Minor features (router descriptor cache):
31908 - If we find a cached-routers file that's been sitting around for more
31909 than 28 days unmodified, then most likely it's a leftover from
31910 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
31912 - When we (as a cache) download a descriptor because it was listed
31913 in a consensus, remember when the consensus was supposed to expire,
31914 and don't expire the descriptor until then.
31916 o Minor features (performance):
31917 - Call routerlist_remove_old_routers() much less often. This should
31918 speed startup, especially on directory caches.
31919 - Don't try to launch new descriptor downloads quite so often when we
31920 already have enough directory information to build circuits.
31921 - Base64 decoding was actually showing up on our profile when parsing
31922 the initial descriptor file; switch to an in-process all-at-once
31923 implementation that's about 3.5x times faster than calling out to
31926 o Minor features (compilation):
31927 - Detect non-ASCII platforms (if any still exist) and refuse to
31928 build there: some of our code assumes that 'A' is 65 and so on.
31930 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
31931 - Make the "next period" votes into "current period" votes immediately
31932 after publishing the consensus; avoid a heisenbug that made them
31933 stick around indefinitely.
31934 - When we discard a vote as a duplicate, do not report this as
31936 - Treat missing v3 keys or certificates as an error when running as a
31937 v3 directory authority.
31938 - When we're configured to be a v3 authority, but we're only listed
31939 as a non-v3 authority in our DirServer line for ourself, correct
31941 - If an authority doesn't have a qualified hostname, just put
31942 its address in the vote. This fixes the problem where we referred to
31943 "moria on moria:9031."
31944 - Distinguish between detached signatures for the wrong period, and
31945 detached signatures for a divergent vote.
31946 - Fix a small memory leak when computing a consensus.
31947 - When there's no consensus, we were forming a vote every 30
31948 minutes, but writing the "valid-after" line in our vote based
31949 on our configured V3AuthVotingInterval: so unless the intervals
31950 matched up, we immediately rejected our own vote because it didn't
31951 start at the voting interval that caused us to construct a vote.
31953 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
31954 - Delete unverified-consensus when the real consensus is set.
31955 - Consider retrying a consensus networkstatus fetch immediately
31956 after one fails: don't wait 60 seconds to notice.
31957 - When fetching a consensus as a cache, wait until a newer consensus
31958 should exist before trying to replace the current one.
31959 - Use a more forgiving schedule for retrying failed consensus
31960 downloads than for other types.
31962 o Minor bugfixes (other directory issues):
31963 - Correct the implementation of "download votes by digest." Bugfix on
31965 - Authorities no longer send back "400 you're unreachable please fix
31966 it" errors to Tor servers that aren't online all the time. We're
31967 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
31969 o Minor bugfixes (controller):
31970 - Don't reset trusted dir server list when we set a configuration
31971 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
31972 - Respond to INT and TERM SIGNAL commands before we execute the
31973 signal, in case the signal shuts us down. We had a patch in
31974 0.1.2.1-alpha that tried to do this by queueing the response on
31975 the connection's buffer before shutting down, but that really
31976 isn't the same thing at all. Bug located by Matt Edman.
31978 o Minor bugfixes (misc):
31979 - Correctly check for bad options to the "PublishServerDescriptor"
31980 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
31981 - Stop leaking memory on failing case of base32_decode, and make
31982 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
31983 - Don't try to download extrainfo documents when we're trying to
31984 fetch enough directory info to build a circuit: having enough
31985 info should get priority. Bugfix on 0.2.0.x.
31986 - Don't complain that "your server has not managed to confirm that its
31987 ports are reachable" if we haven't been able to build any circuits
31988 yet. Bug found by spending four hours without a v3 consensus. Bugfix
31990 - Detect the reason for failing to mmap a descriptor file we just
31991 wrote, and give a more useful log message. Fixes bug 533. Bugfix
31994 o Code simplifications and refactoring:
31995 - Remove support for the old bw_accounting file: we've been storing
31996 bandwidth accounting information in the state file since
31997 0.1.2.5-alpha. This may result in bandwidth accounting errors
31998 if you try to upgrade from 0.1.1.x or earlier, or if you try to
31999 downgrade to 0.1.1.x or earlier.
32000 - New convenience code to locate a file within the DataDirectory.
32001 - Move non-authority functionality out of dirvote.c.
32002 - Refactor the arguments for router_pick_{directory_|trusteddir}server
32003 so that they all take the same named flags.
32006 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
32007 Unix users an easy way to script their Tor process (e.g. by
32008 adjusting bandwidth based on the time of the day).
32011 Changes in version 0.2.0.8-alpha - 2007-10-12
32012 This eighth development snapshot fixes a crash bug that's been bothering
32013 us since February 2007, lets bridge authorities store a list of bridge
32014 descriptors they've seen, gets v3 directory voting closer to working,
32015 starts caching v3 directory consensus documents on directory mirrors,
32016 and fixes a variety of smaller issues including some minor memory leaks.
32018 o Major features (router descriptor cache):
32019 - Store routers in a file called cached-descriptors instead of in
32020 cached-routers. Initialize cached-descriptors from cached-routers
32021 if the old format is around. The new format allows us to store
32022 annotations along with descriptors.
32023 - Use annotations to record the time we received each descriptor, its
32024 source, and its purpose.
32025 - Disable the SETROUTERPURPOSE controller command: it is now
32027 - Controllers should now specify cache=no or cache=yes when using
32028 the +POSTDESCRIPTOR command.
32029 - Bridge authorities now write bridge descriptors to disk, meaning
32030 we can export them to other programs and begin distributing them
32033 o Major features (directory authorities):
32034 - When a v3 authority is missing votes or signatures, it now tries
32036 - Directory authorities track weighted fractional uptime as well as
32037 weighted mean-time-between failures. WFU is suitable for deciding
32038 whether a node is "usually up", while MTBF is suitable for deciding
32039 whether a node is "likely to stay up." We need both, because
32040 "usually up" is a good requirement for guards, while "likely to
32041 stay up" is a good requirement for long-lived connections.
32043 o Major features (v3 directory system):
32044 - Caches now download v3 network status documents as needed,
32045 and download the descriptors listed in them.
32046 - All hosts now attempt to download and keep fresh v3 authority
32047 certificates, and re-attempt after failures.
32048 - More internal-consistency checks for vote parsing.
32050 o Major bugfixes (crashes):
32051 - If a connection is shut down abruptly because of something that
32052 happened inside connection_flushed_some(), do not call
32053 connection_finished_flushing(). Should fix bug 451. Bugfix on
32056 o Major bugfixes (performance):
32057 - Fix really bad O(n^2) performance when parsing a long list of
32058 routers: Instead of searching the entire list for an "extra-info "
32059 string which usually wasn't there, once for every routerinfo
32060 we read, just scan lines forward until we find one we like.
32062 - When we add data to a write buffer in response to the data on that
32063 write buffer getting low because of a flush, do not consider the
32064 newly added data as a candidate for immediate flushing, but rather
32065 make it wait until the next round of writing. Otherwise, we flush
32066 and refill recursively, and a single greedy TLS connection can
32067 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
32069 o Minor features (v3 authority system):
32070 - Add more ways for tools to download the votes that lead to the
32072 - Send a 503 when low on bandwidth and a vote, consensus, or
32073 certificate is requested.
32074 - If-modified-since is now implemented properly for all kinds of
32075 certificate requests.
32077 o Minor bugfixes (network statuses):
32078 - Tweak the implementation of proposal 109 slightly: allow at most
32079 two Tor servers on the same IP address, except if it's the location
32080 of a directory authority, in which case allow five. Bugfix on
32083 o Minor bugfixes (controller):
32084 - When sending a status event to the controller telling it that an
32085 OR address is reachable, set the port correctly. (Previously we
32086 were reporting the dir port.) Bugfix on 0.1.2.x.
32088 o Minor bugfixes (v3 directory system):
32089 - Fix logic to look up a cert by its signing key digest. Bugfix on
32091 - Only change the reply to a vote to "OK" if it's not already
32092 set. This gets rid of annoying "400 OK" log messages, which may
32093 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
32094 - When we get a valid consensus, recompute the voting schedule.
32095 - Base the valid-after time of a vote on the consensus voting
32096 schedule, not on our preferred schedule.
32097 - Make the return values and messages from signature uploads and
32098 downloads more sensible.
32099 - Fix a memory leak when serving votes and consensus documents, and
32100 another when serving certificates.
32102 o Minor bugfixes (performance):
32103 - Use a slightly simpler string hashing algorithm (copying Python's
32104 instead of Java's) and optimize our digest hashing algorithm to take
32105 advantage of 64-bit platforms and to remove some possibly-costly
32107 - Fix a minor memory leak whenever we parse guards from our state
32108 file. Bugfix on 0.2.0.7-alpha.
32109 - Fix a minor memory leak whenever we write out a file. Bugfix on
32111 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
32112 command. Bugfix on 0.2.0.5-alpha.
32114 o Minor bugfixes (portability):
32115 - On some platforms, accept() can return a broken address. Detect
32116 this more quietly, and deal accordingly. Fixes bug 483.
32117 - Stop calling tor_strlower() on uninitialized memory in some cases.
32118 Bugfix in 0.2.0.7-alpha.
32120 o Minor bugfixes (usability):
32121 - Treat some 403 responses from directory servers as INFO rather than
32122 WARN-severity events.
32123 - It's not actually an error to find a non-pending entry in the DNS
32124 cache when canceling a pending resolve. Don't log unless stuff is
32125 fishy. Resolves bug 463.
32127 o Minor bugfixes (anonymity):
32128 - Never report that we've used more bandwidth than we're willing to
32129 relay: it leaks how much non-relay traffic we're using. Resolves
32131 - When looking for a circuit to cannibalize, consider family as well
32132 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
32133 circuit cannibalization).
32135 o Code simplifications and refactoring:
32136 - Make a bunch of functions static. Remove some dead code.
32137 - Pull out about a third of the really big routerlist.c; put it in a
32138 new module, networkstatus.c.
32139 - Merge the extra fields in local_routerstatus_t back into
32140 routerstatus_t: we used to need one routerstatus_t for each
32141 authority's opinion, plus a local_routerstatus_t for the locally
32142 computed consensus opinion. To save space, we put the locally
32143 modified fields into local_routerstatus_t, and only the common
32144 stuff into routerstatus_t. But once v3 directories are in use,
32145 clients and caches will no longer need to hold authority opinions;
32146 thus, the rationale for keeping the types separate is now gone.
32147 - Make the code used to reschedule and reattempt downloads more
32149 - Turn all 'Are we a directory server/mirror?' logic into a call to
32151 - Remove the code to generate the oldest (v1) directory format.
32152 The code has been disabled since 0.2.0.5-alpha.
32155 Changes in version 0.2.0.7-alpha - 2007-09-21
32156 This seventh development snapshot makes bridges work again, makes bridge
32157 authorities work for the first time, fixes two huge performance flaws
32158 in hidden services, and fixes a variety of minor issues.
32160 o New directory authorities:
32161 - Set up moria1 and tor26 as the first v3 directory authorities. See
32162 doc/spec/dir-spec.txt for details on the new directory design.
32164 o Major bugfixes (crashes):
32165 - Fix possible segfaults in functions called from
32166 rend_process_relay_cell(). Bugfix on 0.1.2.x.
32168 o Major bugfixes (bridges):
32169 - Fix a bug that made servers send a "404 Not found" in response to
32170 attempts to fetch their server descriptor. This caused Tor servers
32171 to take many minutes to establish reachability for their DirPort,
32172 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
32173 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
32174 users configure that and specify a bridge with an identity
32175 fingerprint, now they will lookup the bridge descriptor at the
32176 default bridge authority via a one-hop tunnel, but once circuits
32177 are established they will switch to a three-hop tunnel for later
32178 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
32180 o Major bugfixes (hidden services):
32181 - Hidden services were choosing introduction points uniquely by
32182 hexdigest, but when constructing the hidden service descriptor
32183 they merely wrote the (potentially ambiguous) nickname.
32184 - Clients now use the v2 intro format for hidden service
32185 connections: they specify their chosen rendezvous point by identity
32186 digest rather than by (potentially ambiguous) nickname. Both
32187 are bugfixes on 0.1.2.x, and they could speed up hidden service
32188 connections dramatically. Thanks to Karsten Loesing.
32190 o Minor features (security):
32191 - As a client, do not believe any server that tells us that an
32192 address maps to an internal address space.
32193 - Make it possible to enable HashedControlPassword and
32194 CookieAuthentication at the same time.
32196 o Minor features (guard nodes):
32197 - Tag every guard node in our state file with the version that
32198 we believe added it, or with our own version if we add it. This way,
32199 if a user temporarily runs an old version of Tor and then switches
32200 back to a new one, she doesn't automatically lose her guards.
32202 o Minor features (speed):
32203 - When implementing AES counter mode, update only the portions of the
32204 counter buffer that need to change, and don't keep separate
32205 network-order and host-order counters when they are the same (i.e.,
32206 on big-endian hosts.)
32208 o Minor features (controller):
32209 - Accept LF instead of CRLF on controller, since some software has a
32210 hard time generating real Internet newlines.
32211 - Add GETINFO values for the server status events
32212 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
32215 o Removed features:
32216 - Routers no longer include bandwidth-history lines in their
32217 descriptors; this information is already available in extra-info
32218 documents, and including it in router descriptors took up 60%
32219 (!) of compressed router descriptor downloads. Completes
32220 implementation of proposal 104.
32221 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
32222 and TorControl.py, as they use the old v0 controller protocol,
32223 and are obsoleted by TorFlow anyway.
32224 - Drop support for v1 rendezvous descriptors, since we never used
32225 them anyway, and the code has probably rotted by now. Based on
32226 patch from Karsten Loesing.
32227 - On OSX, stop warning the user that kqueue support in libevent is
32228 "experimental", since it seems to have worked fine for ages.
32231 - When generating information telling us how to extend to a given
32232 router, do not try to include the nickname if it is absent. Fixes
32233 bug 467. Bugfix on 0.2.0.3-alpha.
32234 - Fix a user-triggerable (but not remotely-triggerable) segfault
32235 in expand_filename(). Bugfix on 0.1.2.x.
32236 - Fix a memory leak when freeing incomplete requests from DNSPort.
32237 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
32238 - Don't try to access (or alter) the state file when running
32239 --list-fingerprint or --verify-config or --hash-password. (Resolves
32240 bug 499.) Bugfix on 0.1.2.x.
32241 - Servers used to decline to publish their DirPort if their
32242 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
32243 were below a threshold. Now they only look at BandwidthRate and
32244 RelayBandwidthRate. Bugfix on 0.1.2.x.
32245 - Remove an optimization in the AES counter-mode code that assumed
32246 that the counter never exceeded 2^68. When the counter can be set
32247 arbitrarily as an IV (as it is by Karsten's new hidden services
32248 code), this assumption no longer holds. Bugfix on 0.1.2.x.
32249 - Resume listing "AUTHORITY" flag for authorities in network status.
32250 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
32252 o Code simplifications and refactoring:
32253 - Revamp file-writing logic so we don't need to have the entire
32254 contents of a file in memory at once before we write to disk. Tor,
32256 - Turn "descriptor store" into a full-fledged type.
32257 - Move all NT services code into a separate source file.
32258 - Unify all code that computes medians, percentile elements, etc.
32259 - Get rid of a needless malloc when parsing address policies.
32262 Changes in version 0.1.2.17 - 2007-08-30
32263 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
32264 X bundles. Vidalia 0.0.14 makes authentication required for the
32265 ControlPort in the default configuration, which addresses important
32266 security risks. Everybody who uses Vidalia (or another controller)
32269 In addition, this Tor update fixes major load balancing problems with
32270 path selection, which should speed things up a lot once many people
32273 o Major bugfixes (security):
32274 - We removed support for the old (v0) control protocol. It has been
32275 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
32276 become more of a headache than it's worth.
32278 o Major bugfixes (load balancing):
32279 - When choosing nodes for non-guard positions, weight guards
32280 proportionally less, since they already have enough load. Patch
32282 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
32283 will allow fast Tor servers to get more attention.
32284 - When we're upgrading from an old Tor version, forget our current
32285 guards and pick new ones according to the new weightings. These
32286 three load balancing patches could raise effective network capacity
32287 by a factor of four. Thanks to Mike Perry for measurements.
32289 o Major bugfixes (stream expiration):
32290 - Expire not-yet-successful application streams in all cases if
32291 they've been around longer than SocksTimeout. Right now there are
32292 some cases where the stream will live forever, demanding a new
32293 circuit every 15 seconds. Fixes bug 454; reported by lodger.
32295 o Minor features (controller):
32296 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
32297 is valid before any authentication has been received. It tells
32298 a controller what kind of authentication is expected, and what
32299 protocol is spoken. Implements proposal 119.
32301 o Minor bugfixes (performance):
32302 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
32303 greatly speeding up loading cached-routers from disk on startup.
32304 - Disable sentinel-based debugging for buffer code: we squashed all
32305 the bugs that this was supposed to detect a long time ago, and now
32306 its only effect is to change our buffer sizes from nice powers of
32307 two (which platform mallocs tend to like) to values slightly over
32308 powers of two (which make some platform mallocs sad).
32310 o Minor bugfixes (misc):
32311 - If exit bandwidth ever exceeds one third of total bandwidth, then
32312 use the correct formula to weight exit nodes when choosing paths.
32313 Based on patch from Mike Perry.
32314 - Choose perfectly fairly among routers when choosing by bandwidth and
32315 weighting by fraction of bandwidth provided by exits. Previously, we
32316 would choose with only approximate fairness, and correct ourselves
32317 if we ran off the end of the list.
32318 - If we require CookieAuthentication but we fail to write the
32319 cookie file, we would warn but not exit, and end up in a state
32320 where no controller could authenticate. Now we exit.
32321 - If we require CookieAuthentication, stop generating a new cookie
32322 every time we change any piece of our config.
32323 - Refuse to start with certain directory authority keys, and
32324 encourage people using them to stop.
32325 - Terminate multi-line control events properly. Original patch
32327 - Fix a minor memory leak when we fail to find enough suitable
32328 servers to choose a circuit.
32329 - Stop leaking part of the descriptor when we run into a particularly
32330 unparseable piece of it.
32333 Changes in version 0.2.0.6-alpha - 2007-08-26
32334 This sixth development snapshot features a new Vidalia version in the
32335 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
32336 the ControlPort in the default configuration, which addresses important
32339 In addition, this snapshot fixes major load balancing problems
32340 with path selection, which should speed things up a lot once many
32341 people have upgraded. The directory authorities also use a new
32342 mean-time-between-failure approach to tracking which servers are stable,
32343 rather than just looking at the most recent uptime.
32345 o New directory authorities:
32346 - Set up Tonga as the default bridge directory authority.
32349 - Directory authorities now track servers by weighted
32350 mean-times-between-failures. When we have 4 or more days of data,
32351 use measured MTBF rather than declared uptime to decide whether
32352 to call a router Stable. Implements proposal 108.
32354 o Major bugfixes (load balancing):
32355 - When choosing nodes for non-guard positions, weight guards
32356 proportionally less, since they already have enough load. Patch
32358 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
32359 will allow fast Tor servers to get more attention.
32360 - When we're upgrading from an old Tor version, forget our current
32361 guards and pick new ones according to the new weightings. These
32362 three load balancing patches could raise effective network capacity
32363 by a factor of four. Thanks to Mike Perry for measurements.
32365 o Major bugfixes (descriptor parsing):
32366 - Handle unexpected whitespace better in malformed descriptors. Bug
32367 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
32370 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
32371 GETINFO for Torstat to use until it can switch to using extrainfos.
32372 - Optionally (if built with -DEXPORTMALLINFO) export the output
32373 of mallinfo via http, as tor/mallinfo.txt. Only accessible
32377 - Do not intermix bridge routers with controller-added
32378 routers. (Bugfix on 0.2.0.x)
32379 - Do not fail with an assert when accept() returns an unexpected
32380 address family. Addresses but does not wholly fix bug 483. (Bugfix
32382 - Let directory authorities startup even when they can't generate
32383 a descriptor immediately, e.g. because they don't know their
32385 - Stop putting the authentication cookie in a file called "0"
32386 in your working directory if you don't specify anything for the
32387 new CookieAuthFile option. Reported by Matt Edman.
32388 - Make it possible to read the PROTOCOLINFO response in a way that
32389 conforms to our control-spec. Reported by Matt Edman.
32390 - Fix a minor memory leak when we fail to find enough suitable
32391 servers to choose a circuit. Bugfix on 0.1.2.x.
32392 - Stop leaking part of the descriptor when we run into a particularly
32393 unparseable piece of it. Bugfix on 0.1.2.x.
32394 - Unmap the extrainfo cache file on exit.
32397 Changes in version 0.2.0.5-alpha - 2007-08-19
32398 This fifth development snapshot fixes compilation on Windows again;
32399 fixes an obnoxious client-side bug that slowed things down and put
32400 extra load on the network; gets us closer to using the v3 directory
32401 voting scheme; makes it easier for Tor controllers to use cookie-based
32402 authentication; and fixes a variety of other bugs.
32404 o Removed features:
32405 - Version 1 directories are no longer generated in full. Instead,
32406 authorities generate and serve "stub" v1 directories that list
32407 no servers. This will stop Tor versions 0.1.0.x and earlier from
32408 working, but (for security reasons) nobody should be running those
32411 o Major bugfixes (compilation, 0.2.0.x):
32412 - Try to fix Win32 compilation again: improve checking for IPv6 types.
32413 - Try to fix MSVC compilation: build correctly on platforms that do
32414 not define s6_addr16 or s6_addr32.
32415 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
32418 o Major bugfixes (stream expiration):
32419 - Expire not-yet-successful application streams in all cases if
32420 they've been around longer than SocksTimeout. Right now there are
32421 some cases where the stream will live forever, demanding a new
32422 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
32423 reported by lodger.
32425 o Minor features (directory servers):
32426 - When somebody requests a list of statuses or servers, and we have
32427 none of those, return a 404 rather than an empty 200.
32429 o Minor features (directory voting):
32430 - Store v3 consensus status consensuses on disk, and reload them
32433 o Minor features (security):
32434 - Warn about unsafe ControlPort configurations.
32435 - Refuse to start with certain directory authority keys, and
32436 encourage people using them to stop.
32438 o Minor features (controller):
32439 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
32440 is valid before any authentication has been received. It tells
32441 a controller what kind of authentication is expected, and what
32442 protocol is spoken. Implements proposal 119.
32443 - New config option CookieAuthFile to choose a new location for the
32444 cookie authentication file, and config option
32445 CookieAuthFileGroupReadable to make it group-readable.
32447 o Minor features (unit testing):
32448 - Add command-line arguments to unit-test executable so that we can
32449 invoke any chosen test from the command line rather than having
32450 to run the whole test suite at once; and so that we can turn on
32451 logging for the unit tests.
32453 o Minor bugfixes (on 0.1.2.x):
32454 - If we require CookieAuthentication but we fail to write the
32455 cookie file, we would warn but not exit, and end up in a state
32456 where no controller could authenticate. Now we exit.
32457 - If we require CookieAuthentication, stop generating a new cookie
32458 every time we change any piece of our config.
32459 - When loading bandwidth history, do not believe any information in
32460 the future. Fixes bug 434.
32461 - When loading entry guard information, do not believe any information
32463 - When we have our clock set far in the future and generate an
32464 onion key, then re-set our clock to be correct, we should not stop
32465 the onion key from getting rotated.
32466 - Clean up torrc sample config file.
32467 - Do not automatically run configure from autogen.sh. This
32468 non-standard behavior tended to annoy people who have built other
32471 o Minor bugfixes (on 0.2.0.x):
32472 - Fix a bug with AutomapHostsOnResolve that would always cause
32473 the second request to fail. Bug reported by Kate. Bugfix on
32475 - Fix a bug in ADDRMAP controller replies that would sometimes
32476 try to print a NULL. Patch from tup.
32477 - Read v3 directory authority keys from the right location.
32478 - Numerous bugfixes to directory voting code.
32481 Changes in version 0.1.2.16 - 2007-08-01
32482 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
32483 remote attacker in certain situations to rewrite the user's torrc
32484 configuration file. This can completely compromise anonymity of users
32485 in most configurations, including those running the Vidalia bundles,
32486 TorK, etc. Or worse.
32488 o Major security fixes:
32489 - Close immediately after missing authentication on control port;
32490 do not allow multiple authentication attempts.
32493 Changes in version 0.2.0.4-alpha - 2007-08-01
32494 This fourth development snapshot fixes a critical security vulnerability
32495 for most users, specifically those running Vidalia, TorK, etc. Everybody
32496 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
32498 o Major security fixes:
32499 - Close immediately after missing authentication on control port;
32500 do not allow multiple authentication attempts.
32502 o Major bugfixes (compilation):
32503 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
32506 o Minor features (performance):
32507 - Be even more aggressive about releasing RAM from small
32508 empty buffers. Thanks to our free-list code, this shouldn't be too
32509 performance-intensive.
32510 - Disable sentinel-based debugging for buffer code: we squashed all
32511 the bugs that this was supposed to detect a long time ago, and
32512 now its only effect is to change our buffer sizes from nice
32513 powers of two (which platform mallocs tend to like) to values
32514 slightly over powers of two (which make some platform mallocs sad).
32515 - Log malloc statistics from mallinfo() on platforms where it
32519 Changes in version 0.2.0.3-alpha - 2007-07-29
32520 This third development snapshot introduces new experimental
32521 blocking-resistance features and a preliminary version of the v3
32522 directory voting design, and includes many other smaller features
32526 - The first pieces of our "bridge" design for blocking-resistance
32527 are implemented. People can run bridge directory authorities;
32528 people can run bridges; and people can configure their Tor clients
32529 with a set of bridges to use as the first hop into the Tor network.
32530 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
32532 - Create listener connections before we setuid to the configured
32533 User and Group. Now non-Windows users can choose port values
32534 under 1024, start Tor as root, and have Tor bind those ports
32535 before it changes to another UID. (Windows users could already
32537 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
32538 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
32539 on "vserver" accounts. (Patch from coderman.)
32540 - Be even more aggressive about separating local traffic from relayed
32541 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
32543 o Major features (experimental):
32544 - First cut of code for "v3 dir voting": directory authorities will
32545 vote on a common network status document rather than each publishing
32546 their own opinion. This code needs more testing and more corner-case
32547 handling before it's ready for use.
32550 - Directory authorities now call routers Fast if their bandwidth is
32551 at least 100KB/s, and consider their bandwidth adequate to be a
32552 Guard if it is at least 250KB/s, no matter the medians. This fix
32553 complements proposal 107. [Bugfix on 0.1.2.x]
32554 - Directory authorities now never mark more than 3 servers per IP as
32555 Valid and Running. (Implements proposal 109, by Kevin Bauer and
32557 - Minor change to organizationName and commonName generation
32558 procedures in TLS certificates during Tor handshakes, to invalidate
32559 some earlier censorware approaches. This is not a long-term
32560 solution, but applying it will give us a bit of time to look into
32561 the epidemiology of countermeasures as they spread.
32563 o Major bugfixes (directory):
32564 - Rewrite directory tokenization code to never run off the end of
32565 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
32567 o Minor features (controller):
32568 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
32569 match requests to applications. (Patch from Robert Hogan.)
32570 - Report address and port correctly on connections to DNSPort. (Patch
32571 from Robert Hogan.)
32572 - Add a RESOLVE command to launch hostname lookups. (Original patch
32573 from Robert Hogan.)
32574 - Add GETINFO status/enough-dir-info to let controllers tell whether
32575 Tor has downloaded sufficient directory information. (Patch
32577 - You can now use the ControlSocket option to tell Tor to listen for
32578 controller connections on Unix domain sockets on systems that
32579 support them. (Patch from Peter Palfrader.)
32580 - STREAM NEW events are generated for DNSPort requests and for
32581 tunneled directory connections. (Patch from Robert Hogan.)
32582 - New "GETINFO address-mappings/*" command to get address mappings
32583 with expiry information. "addr-mappings/*" is now deprecated.
32586 o Minor features (misc):
32587 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
32589 - The tor-gencert tool for v3 directory authorities now creates all
32590 files as readable to the file creator only, and write-protects
32591 the authority identity key.
32592 - When dumping memory usage, list bytes used in buffer memory
32594 - When running with dmalloc, dump more stats on hup and on exit.
32595 - Directory authorities now fail quickly and (relatively) harmlessly
32596 if they generate a network status document that is somehow
32599 o Traffic load balancing improvements:
32600 - If exit bandwidth ever exceeds one third of total bandwidth, then
32601 use the correct formula to weight exit nodes when choosing paths.
32602 (Based on patch from Mike Perry.)
32603 - Choose perfectly fairly among routers when choosing by bandwidth and
32604 weighting by fraction of bandwidth provided by exits. Previously, we
32605 would choose with only approximate fairness, and correct ourselves
32606 if we ran off the end of the list. [Bugfix on 0.1.2.x]
32608 o Performance improvements:
32609 - Be more aggressive with freeing buffer RAM or putting it on the
32611 - Use Critical Sections rather than Mutexes for synchronizing threads
32612 on win32; Mutexes are heavier-weight, and designed for synchronizing
32615 o Deprecated and removed features:
32616 - RedirectExits is now deprecated.
32617 - Stop allowing address masks that do not correspond to bit prefixes.
32618 We have warned about these for a really long time; now it's time
32619 to reject them. (Patch from croup.)
32621 o Minor bugfixes (directory):
32622 - Fix another crash bug related to extra-info caching. (Bug found by
32623 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
32624 - Directories no longer return a "304 not modified" when they don't
32625 have the networkstatus the client asked for. Also fix a memory
32626 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
32627 - We had accidentally labelled 0.1.2.x directory servers as not
32628 suitable for begin_dir requests, and had labelled no directory
32629 servers as suitable for uploading extra-info documents. [Bugfix
32632 o Minor bugfixes (dns):
32633 - Fix a crash when DNSPort is set more than once. (Patch from Robert
32634 Hogan.) [Bugfix on 0.2.0.2-alpha]
32635 - Add DNSPort connections to the global connection list, so that we
32636 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
32638 - Fix a dangling reference that could lead to a crash when DNSPort is
32639 changed or closed (Patch from Robert Hogan.) [Bugfix on
32642 o Minor bugfixes (controller):
32643 - Provide DNS expiry times in GMT, not in local time. For backward
32644 compatibility, ADDRMAP events only provide GMT expiry in an extended
32645 field. "GETINFO address-mappings" always does the right thing.
32646 - Use CRLF line endings properly in NS events.
32647 - Terminate multi-line control events properly. (Original patch
32648 from tup.) [Bugfix on 0.1.2.x-alpha]
32649 - Do not include spaces in SOURCE_ADDR fields in STREAM
32650 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
32653 Changes in version 0.1.2.15 - 2007-07-17
32654 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
32655 problems, fixes compilation on BSD, and fixes a variety of other
32656 bugs. Everybody should upgrade.
32658 o Major bugfixes (compilation):
32659 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
32661 o Major bugfixes (crashes):
32662 - Try even harder not to dereference the first character after
32663 an mmap(). Reported by lodger.
32664 - Fix a crash bug in directory authorities when we re-number the
32665 routerlist while inserting a new router.
32666 - When the cached-routers file is an even multiple of the page size,
32667 don't run off the end and crash. (Fixes bug 455; based on idea
32669 - Fix eventdns.c behavior on Solaris: It is critical to include
32670 orconfig.h _before_ sys/types.h, so that we can get the expected
32671 definition of _FILE_OFFSET_BITS.
32673 o Major bugfixes (security):
32674 - Fix a possible buffer overrun when using BSD natd support. Bug
32676 - When sending destroy cells from a circuit's origin, don't include
32677 the reason for tearing down the circuit. The spec says we didn't,
32678 and now we actually don't. Reported by lodger.
32679 - Keep streamids from different exits on a circuit separate. This
32680 bug may have allowed other routers on a given circuit to inject
32681 cells into streams. Reported by lodger; fixes bug 446.
32682 - If there's a never-before-connected-to guard node in our list,
32683 never choose any guards past it. This way we don't expand our
32684 guard list unless we need to.
32686 o Minor bugfixes (guard nodes):
32687 - Weight guard selection by bandwidth, so that low-bandwidth nodes
32688 don't get overused as guards.
32690 o Minor bugfixes (directory):
32691 - Correctly count the number of authorities that recommend each
32692 version. Previously, we were under-counting by 1.
32693 - Fix a potential crash bug when we load many server descriptors at
32694 once and some of them make others of them obsolete. Fixes bug 458.
32696 o Minor bugfixes (hidden services):
32697 - Stop tearing down the whole circuit when the user asks for a
32698 connection to a port that the hidden service didn't configure.
32701 o Minor bugfixes (misc):
32702 - On Windows, we were preventing other processes from reading
32703 cached-routers while Tor was running. Reported by janbar.
32704 - Fix a possible (but very unlikely) bug in picking routers by
32705 bandwidth. Add a log message to confirm that it is in fact
32706 unlikely. Patch from lodger.
32707 - Backport a couple of memory leak fixes.
32708 - Backport miscellaneous cosmetic bugfixes.
32711 Changes in version 0.2.0.2-alpha - 2007-06-02
32712 o Major bugfixes on 0.2.0.1-alpha:
32713 - Fix an assertion failure related to servers without extra-info digests.
32714 Resolves bugs 441 and 442.
32716 o Minor features (directory):
32717 - Support "If-Modified-Since" when answering HTTP requests for
32718 directories, running-routers documents, and network-status documents.
32719 (There's no need to support it for router descriptors, since those
32720 are downloaded by descriptor digest.)
32722 o Minor build issues:
32723 - Clear up some MIPSPro compiler warnings.
32724 - When building from a tarball on a machine that happens to have SVK
32725 installed, report the micro-revision as whatever version existed
32726 in the tarball, not as "x".
32729 Changes in version 0.2.0.1-alpha - 2007-06-01
32730 This early development snapshot provides new features for people running
32731 Tor as both a client and a server (check out the new RelayBandwidth
32732 config options); lets Tor run as a DNS proxy; and generally moves us
32733 forward on a lot of fronts.
32735 o Major features, server usability:
32736 - New config options RelayBandwidthRate and RelayBandwidthBurst:
32737 a separate set of token buckets for relayed traffic. Right now
32738 relayed traffic is defined as answers to directory requests, and
32739 OR connections that don't have any local circuits on them.
32741 o Major features, client usability:
32742 - A client-side DNS proxy feature to replace the need for
32743 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
32744 for DNS requests on port 9999, use the Tor network to resolve them
32745 anonymously, and send the reply back like a regular DNS server.
32746 The code still only implements a subset of DNS.
32747 - Make PreferTunneledDirConns and TunnelDirConns work even when
32748 we have no cached directory info. This means Tor clients can now
32749 do all of their connections protected by TLS.
32751 o Major features, performance and efficiency:
32752 - Directory authorities accept and serve "extra info" documents for
32753 routers. These documents contain fields from router descriptors
32754 that aren't usually needed, and that use a lot of excess
32755 bandwidth. Once these fields are removed from router descriptors,
32756 the bandwidth savings should be about 60%. [Partially implements
32758 - Servers upload extra-info documents to any authority that accepts
32759 them. Authorities (and caches that have been configured to download
32760 extra-info documents) download them as needed. [Partially implements
32762 - Change the way that Tor buffers data that it is waiting to write.
32763 Instead of queueing data cells in an enormous ring buffer for each
32764 client->OR or OR->OR connection, we now queue cells on a separate
32765 queue for each circuit. This lets us use less slack memory, and
32766 will eventually let us be smarter about prioritizing different kinds
32768 - Use memory pools to allocate cells with better speed and memory
32769 efficiency, especially on platforms where malloc() is inefficient.
32770 - Stop reading on edge connections when their corresponding circuit
32771 buffers are full; start again as the circuits empty out.
32773 o Major features, other:
32774 - Add an HSAuthorityRecordStats option that hidden service authorities
32775 can use to track statistics of overall hidden service usage without
32776 logging information that would be very useful to an attacker.
32777 - Start work implementing multi-level keys for directory authorities:
32778 Add a standalone tool to generate key certificates. (Proposal 103.)
32781 - Directory authorities now call routers Stable if they have an
32782 uptime of at least 30 days, even if that's not the median uptime
32783 in the network. Implements proposal 107, suggested by Kevin Bauer
32786 o Minor fixes (resource management):
32787 - Count the number of open sockets separately from the number
32788 of active connection_t objects. This will let us avoid underusing
32789 our allocated connection limit.
32790 - We no longer use socket pairs to link an edge connection to an
32791 anonymous directory connection or a DirPort test connection.
32792 Instead, we track the link internally and transfer the data
32793 in-process. This saves two sockets per "linked" connection (at the
32794 client and at the server), and avoids the nasty Windows socketpair()
32796 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
32797 for every single inactive connection_t. Free items from the
32798 4k/16k-buffer free lists when they haven't been used for a while.
32800 o Minor features (build):
32801 - Make autoconf search for libevent, openssl, and zlib consistently.
32802 - Update deprecated macros in configure.in.
32803 - When warning about missing headers, tell the user to let us
32804 know if the compile succeeds anyway, so we can downgrade the
32806 - Include the current subversion revision as part of the version
32807 string: either fetch it directly if we're in an SVN checkout, do
32808 some magic to guess it if we're in an SVK checkout, or use
32809 the last-detected version if we're building from a .tar.gz.
32810 Use this version consistently in log messages.
32812 o Minor features (logging):
32813 - Always prepend "Bug: " to any log message about a bug.
32814 - Put a platform string (e.g. "Linux i686") in the startup log
32815 message, so when people paste just their logs, we know if it's
32816 OpenBSD or Windows or what.
32817 - When logging memory usage, break down memory used in buffers by
32820 o Minor features (directory system):
32821 - New config option V2AuthoritativeDirectory that all directory
32822 authorities should set. This will let future authorities choose
32823 not to serve V2 directory information.
32824 - Directory authorities allow multiple router descriptors and/or extra
32825 info documents to be uploaded in a single go. This will make
32826 implementing proposal 104 simpler.
32828 o Minor features (controller):
32829 - Add a new config option __DisablePredictedCircuits designed for
32830 use by the controller, when we don't want Tor to build any circuits
32832 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
32833 so we can exit from the middle of the circuit.
32834 - Implement "getinfo status/circuit-established".
32835 - Implement "getinfo status/version/..." so a controller can tell
32836 whether the current version is recommended, and whether any versions
32837 are good, and how many authorities agree. (Patch from shibz.)
32839 o Minor features (hidden services):
32840 - Allow multiple HiddenServicePort directives with the same virtual
32841 port; when they occur, the user is sent round-robin to one
32842 of the target ports chosen at random. Partially fixes bug 393 by
32843 adding limited ad-hoc round-robining.
32845 o Minor features (other):
32847 - Add a new AutomapHostsOnResolve option: when it is enabled, any
32848 resolve request for hosts matching a given pattern causes Tor to
32849 generate an internal virtual address mapping for that host. This
32850 allows DNSPort to work sensibly with hidden service users. By
32851 default, .exit and .onion addresses are remapped; the list of
32852 patterns can be reconfigured with AutomapHostsSuffixes.
32853 - Add an "-F" option to tor-resolve to force a resolve for a .onion
32854 address. Thanks to the AutomapHostsOnResolve option, this is no
32855 longer a completely silly thing to do.
32856 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
32857 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
32858 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
32859 minus 1 byte: the actual maximum declared bandwidth.
32861 o Removed features:
32862 - Removed support for the old binary "version 0" controller protocol.
32863 This has been deprecated since 0.1.1, and warnings have been issued
32864 since 0.1.2. When we encounter a v0 control message, we now send
32865 back an error and close the connection.
32866 - Remove the old "dns worker" server DNS code: it hasn't been default
32867 since 0.1.2.2-alpha, and all the servers seem to be using the new
32870 o Minor bugfixes (portability):
32871 - Even though Windows is equally happy with / and \ as path separators,
32872 try to use \ consistently on Windows and / consistently on Unix: it
32873 makes the log messages nicer.
32874 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
32875 - Read resolv.conf files correctly on platforms where read() returns
32876 partial results on small file reads.
32878 o Minor bugfixes (directory):
32879 - Correctly enforce that elements of directory objects do not appear
32880 more often than they are allowed to appear.
32881 - When we are reporting the DirServer line we just parsed, we were
32882 logging the second stanza of the key fingerprint, not the first.
32884 o Minor bugfixes (logging):
32885 - When we hit an EOF on a log (probably because we're shutting down),
32886 don't try to remove the log from the list: just mark it as
32887 unusable. (Bulletproofs against bug 222.)
32889 o Minor bugfixes (other):
32890 - In the exitlist script, only consider the most recently published
32891 server descriptor for each server. Also, when the user requests
32892 a list of servers that _reject_ connections to a given address,
32893 explicitly exclude the IPs that also have servers that accept
32894 connections to that address. (Resolves bug 405.)
32895 - Stop allowing hibernating servers to be "stable" or "fast".
32896 - On Windows, we were preventing other processes from reading
32897 cached-routers while Tor was running. (Reported by janbar)
32898 - Make the NodeFamilies config option work. (Reported by
32899 lodger -- it has never actually worked, even though we added it
32901 - Check return values from pthread_mutex functions.
32902 - Don't save non-general-purpose router descriptors to the disk cache,
32903 because we have no way of remembering what their purpose was when
32905 - Add even more asserts to hunt down bug 417.
32906 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
32907 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
32908 Add a log message to confirm that it is in fact unlikely.
32910 o Minor bugfixes (controller):
32911 - Make 'getinfo fingerprint' return a 551 error if we're not a
32912 server, so we match what the control spec claims we do. Reported
32914 - Fix a typo in an error message when extendcircuit fails that
32915 caused us to not follow the \r\n-based delimiter protocol. Reported
32918 o Code simplifications and refactoring:
32919 - Stop passing around circuit_t and crypt_path_t pointers that are
32920 implicit in other procedure arguments.
32921 - Drop the old code to choke directory connections when the
32922 corresponding OR connections got full: thanks to the cell queue
32923 feature, OR conns don't get full any more.
32924 - Make dns_resolve() handle attaching connections to circuits
32925 properly, so the caller doesn't have to.
32926 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
32927 - Keep the connection array as a dynamic smartlist_t, rather than as
32928 a fixed-sized array. This is important, as the number of connections
32929 is becoming increasingly decoupled from the number of sockets.
32932 Changes in version 0.1.2.14 - 2007-05-25
32933 Tor 0.1.2.14 changes the addresses of two directory authorities (this
32934 change especially affects those who serve or use hidden services),
32935 and fixes several other crash- and security-related bugs.
32937 o Directory authority changes:
32938 - Two directory authorities (moria1 and moria2) just moved to new
32939 IP addresses. This change will particularly affect those who serve
32940 or use hidden services.
32942 o Major bugfixes (crashes):
32943 - If a directory server runs out of space in the connection table
32944 as it's processing a begin_dir request, it will free the exit stream
32945 but leave it attached to the circuit, leading to unpredictable
32946 behavior. (Reported by seeess, fixes bug 425.)
32947 - Fix a bug in dirserv_remove_invalid() that would cause authorities
32948 to corrupt memory under some really unlikely scenarios.
32949 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
32950 - Avoid segfaults when reading from mmaped descriptor file. (Reported
32953 o Major bugfixes (security):
32954 - When choosing an entry guard for a circuit, avoid using guards
32955 that are in the same family as the chosen exit -- not just guards
32956 that are exactly the chosen exit. (Reported by lodger.)
32958 o Major bugfixes (resource management):
32959 - If a directory authority is down, skip it when deciding where to get
32960 networkstatus objects or descriptors. Otherwise we keep asking
32961 every 10 seconds forever. Fixes bug 384.
32962 - Count it as a failure if we fetch a valid network-status but we
32963 don't want to keep it. Otherwise we'll keep fetching it and keep
32964 not wanting to keep it. Fixes part of bug 422.
32965 - If all of our dirservers have given us bad or no networkstatuses
32966 lately, then stop hammering them once per minute even when we
32967 think they're failed. Fixes another part of bug 422.
32970 - Actually set the purpose correctly for descriptors inserted with
32971 purpose=controller.
32972 - When we have k non-v2 authorities in our DirServer config,
32973 we ignored the last k authorities in the list when updating our
32975 - Correctly back-off from requesting router descriptors that we are
32976 having a hard time downloading.
32977 - Read resolv.conf files correctly on platforms where read() returns
32978 partial results on small file reads.
32979 - Don't rebuild the entire router store every time we get 32K of
32980 routers: rebuild it when the journal gets very large, or when
32981 the gaps in the store get very large.
32984 - When routers publish SVN revisions in their router descriptors,
32985 authorities now include those versions correctly in networkstatus
32987 - Warn when using a version of libevent before 1.3b to run a server on
32988 OSX or BSD: these versions interact badly with userspace threads.
32991 Changes in version 0.1.2.13 - 2007-04-24
32992 This release features some major anonymity fixes, such as safer path
32993 selection; better client performance; faster bootstrapping, better
32994 address detection, and better DNS support for servers; write limiting as
32995 well as read limiting to make servers easier to run; and a huge pile of
32996 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
32998 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
32999 of the Freenode IRC network, remembering his patience and vision for
33000 free speech on the Internet.
33003 - Fix a memory leak when we ask for "all" networkstatuses and we
33004 get one we don't recognize.
33005 - Add more asserts to hunt down bug 417.
33006 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
33009 Changes in version 0.1.2.12-rc - 2007-03-16
33011 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
33012 directory information requested inside Tor connections (i.e. via
33013 begin_dir cells). It only triggered when the same connection was
33014 serving other data at the same time. Reported by seeess.
33017 - When creating a circuit via the controller, send a 'launched'
33018 event when we're done, so we follow the spec better.
33021 Changes in version 0.1.2.11-rc - 2007-03-15
33022 o Minor bugfixes (controller), reported by daejees:
33023 - Correct the control spec to match how the code actually responds
33024 to 'getinfo addr-mappings/*'.
33025 - The control spec described a GUARDS event, but the code
33026 implemented a GUARD event. Standardize on GUARD, but let people
33027 ask for GUARDS too.
33030 Changes in version 0.1.2.10-rc - 2007-03-07
33031 o Major bugfixes (Windows):
33032 - Do not load the NT services library functions (which may not exist)
33033 just to detect if we're a service trying to shut down. Now we run
33034 on Win98 and friends again.
33036 o Minor bugfixes (other):
33037 - Clarify a couple of log messages.
33038 - Fix a misleading socks5 error number.
33041 Changes in version 0.1.2.9-rc - 2007-03-02
33042 o Major bugfixes (Windows):
33043 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
33044 of the usual GCC "%llu". This prevents a bug when saving 64-bit
33045 int configuration values: the high-order 32 bits would get
33046 truncated. In particular, we were being bitten by the default
33047 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
33048 and maybe also bug 397.)
33050 o Minor bugfixes (performance):
33051 - Use OpenSSL's AES implementation on platforms where it's faster.
33052 This could save us as much as 10% CPU usage.
33054 o Minor bugfixes (server):
33055 - Do not rotate onion key immediately after setting it for the first
33058 o Minor bugfixes (directory authorities):
33059 - Stop calling servers that have been hibernating for a long time
33060 "stable". Also, stop letting hibernating or obsolete servers affect
33061 uptime and bandwidth cutoffs.
33062 - Stop listing hibernating servers in the v1 directory.
33064 o Minor bugfixes (hidden services):
33065 - Upload hidden service descriptors slightly less often, to reduce
33066 load on authorities.
33068 o Minor bugfixes (other):
33069 - Fix an assert that could trigger if a controller quickly set then
33070 cleared EntryNodes. Bug found by Udo van den Heuvel.
33071 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
33073 - Fix a potential race condition in the rpm installer. Found by
33075 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
33076 of 2 as indicating that the server is completely bad; it sometimes
33077 means that the server is just bad for the request in question. (may fix
33078 the last of bug 326.)
33079 - Disable encrypted directory connections when we don't have a server
33080 descriptor for the destination. We'll get this working again in
33084 Changes in version 0.1.2.8-beta - 2007-02-26
33085 o Major bugfixes (crashes):
33086 - Stop crashing when the controller asks us to resetconf more than
33087 one config option at once. (Vidalia 0.0.11 does this.)
33088 - Fix a crash that happened on Win98 when we're given command-line
33089 arguments: don't try to load NT service functions from advapi32.dll
33090 except when we need them. (Bug introduced in 0.1.2.7-alpha;
33092 - Fix a longstanding obscure crash bug that could occur when
33093 we run out of DNS worker processes. (Resolves bug 390.)
33095 o Major bugfixes (hidden services):
33096 - Correctly detect whether hidden service descriptor downloads are
33097 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
33099 o Major bugfixes (accounting):
33100 - When we start during an accounting interval before it's time to wake
33101 up, remember to wake up at the correct time. (May fix bug 342.)
33103 o Minor bugfixes (controller):
33104 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
33105 clear the corresponding on_circuit variable, and remember later
33106 that we don't need to send a redundant CLOSED event. Resolves part
33108 - Report events where a resolve succeeded or where we got a socks
33109 protocol error correctly, rather than calling both of them
33111 - Change reported stream target addresses to IP consistently when
33112 we finally get the IP from an exit node.
33113 - Send log messages to the controller even if they happen to be very
33116 o Minor bugfixes (other):
33117 - Display correct results when reporting which versions are
33118 recommended, and how recommended they are. (Resolves bug 383.)
33119 - Improve our estimates for directory bandwidth to be less random:
33120 guess that an unrecognized directory will have the average bandwidth
33121 from all known directories, not that it will have the average
33122 bandwidth from those directories earlier than it on the list.
33123 - If we start a server with ClientOnly 1, then set ClientOnly to 0
33124 and hup, stop triggering an assert based on an empty onion_key.
33125 - On platforms with no working mmap() equivalent, don't warn the
33126 user when cached-routers doesn't exist.
33127 - Warn the user when mmap() [or its equivalent] fails for some reason
33128 other than file-not-found.
33129 - Don't warn the user when cached-routers.new doesn't exist: that's
33130 perfectly fine when starting up for the first time.
33131 - When EntryNodes are configured, rebuild the guard list to contain,
33132 in order: the EntryNodes that were guards before; the rest of the
33133 EntryNodes; the nodes that were guards before.
33134 - Mask out all signals in sub-threads; only the libevent signal
33135 handler should be processing them. This should prevent some crashes
33136 on some machines using pthreads. (Patch from coderman.)
33137 - Fix switched arguments on memset in the implementation of
33138 tor_munmap() for systems with no mmap() call.
33139 - When Tor receives a router descriptor that it asked for, but
33140 no longer wants (because it has received fresh networkstatuses
33141 in the meantime), do not warn the user. Cache the descriptor if
33142 we're a cache; drop it if we aren't.
33143 - Make earlier entry guards _really_ get retried when the network
33145 - On a malformed DNS reply, always give an error to the corresponding
33147 - Build with recent libevents on platforms that do not define the
33148 nonstandard types "u_int8_t" and friends.
33150 o Minor features (controller):
33151 - Warn the user when an application uses the obsolete binary v0
33152 control protocol. We're planning to remove support for it during
33153 the next development series, so it's good to give people some
33155 - Add STREAM_BW events to report per-entry-stream bandwidth
33156 use. (Patch from Robert Hogan.)
33157 - Rate-limit SIGNEWNYM signals in response to controllers that
33158 impolitely generate them for every single stream. (Patch from
33159 mwenge; closes bug 394.)
33160 - Make REMAP stream events have a SOURCE (cache or exit), and
33161 make them generated in every case where we get a successful
33162 connected or resolved cell.
33164 o Minor bugfixes (performance):
33165 - Call router_have_min_dir_info half as often. (This is showing up in
33166 some profiles, but not others.)
33167 - When using GCC, make log_debug never get called at all, and its
33168 arguments never get evaluated, when no debug logs are configured.
33169 (This is showing up in some profiles, but not others.)
33172 - Remove some never-implemented options. Mark PathlenCoinWeight as
33174 - Implement proposal 106: Stop requiring clients to have well-formed
33175 certificates; stop checking nicknames in certificates. (Clients
33176 have certificates so that they can look like Tor servers, but in
33177 the future we might want to allow them to look like regular TLS
33178 clients instead. Nicknames in certificates serve no purpose other
33179 than making our protocol easier to recognize on the wire.)
33180 - Revise messages on handshake failure again to be even more clear about
33181 which are incoming connections and which are outgoing.
33182 - Discard any v1 directory info that's over 1 month old (for
33183 directories) or over 1 week old (for running-routers lists).
33184 - Do not warn when individual nodes in the configuration's EntryNodes,
33185 ExitNodes, etc are down: warn only when all possible nodes
33186 are down. (Fixes bug 348.)
33187 - Always remove expired routers and networkstatus docs before checking
33188 whether we have enough information to build circuits. (Fixes
33190 - Put a lower-bound on MaxAdvertisedBandwidth.
33193 Changes in version 0.1.2.7-alpha - 2007-02-06
33194 o Major bugfixes (rate limiting):
33195 - Servers decline directory requests much more aggressively when
33196 they're low on bandwidth. Otherwise they end up queueing more and
33197 more directory responses, which can't be good for latency.
33198 - But never refuse directory requests from local addresses.
33199 - Fix a memory leak when sending a 503 response for a networkstatus
33201 - Be willing to read or write on local connections (e.g. controller
33202 connections) even when the global rate limiting buckets are empty.
33203 - If our system clock jumps back in time, don't publish a negative
33204 uptime in the descriptor. Also, don't let the global rate limiting
33205 buckets go absurdly negative.
33206 - Flush local controller connection buffers periodically as we're
33207 writing to them, so we avoid queueing 4+ megabytes of data before
33210 o Major bugfixes (NT services):
33211 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
33212 command-line flag so that admins can override the default by saying
33213 "tor --service install --user "SomeUser"". This will not affect
33214 existing installed services. Also, warn the user that the service
33215 will look for its configuration file in the service user's
33216 %appdata% directory. (We can't do the 'hardwire the user's appdata
33217 directory' trick any more, since we may not have read access to that
33220 o Major bugfixes (other):
33221 - Previously, we would cache up to 16 old networkstatus documents
33222 indefinitely, if they came from nontrusted authorities. Now we
33223 discard them if they are more than 10 days old.
33224 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
33226 - Detect and reject malformed DNS responses containing circular
33228 - If exits are rare enough that we're not marking exits as guards,
33229 ignore exit bandwidth when we're deciding the required bandwidth
33231 - When we're handling a directory connection tunneled over Tor,
33232 don't fill up internal memory buffers with all the data we want
33233 to tunnel; instead, only add it if the OR connection that will
33234 eventually receive it has some room for it. (This can lead to
33235 slowdowns in tunneled dir connections; a better solution will have
33236 to wait for 0.2.0.)
33238 o Minor bugfixes (dns):
33239 - Add some defensive programming to eventdns.c in an attempt to catch
33240 possible memory-stomping bugs.
33241 - Detect and reject DNS replies containing IPv4 or IPv6 records with
33242 an incorrect number of bytes. (Previously, we would ignore the
33244 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
33245 in the correct order, and doesn't crash.
33246 - Free memory held in recently-completed DNS lookup attempts on exit.
33247 This was not a memory leak, but may have been hiding memory leaks.
33248 - Handle TTL values correctly on reverse DNS lookups.
33249 - Treat failure to parse resolv.conf as an error.
33251 o Minor bugfixes (other):
33252 - Fix crash with "tor --list-fingerprint" (reported by seeess).
33253 - When computing clock skew from directory HTTP headers, consider what
33254 time it was when we finished asking for the directory, not what
33256 - Expire socks connections if they spend too long waiting for the
33257 handshake to finish. Previously we would let them sit around for
33258 days, if the connecting application didn't close them either.
33259 - And if the socks handshake hasn't started, don't send a
33260 "DNS resolve socks failed" handshake reply; just close it.
33261 - Stop using C functions that OpenBSD's linker doesn't like.
33262 - Don't launch requests for descriptors unless we have networkstatuses
33263 from at least half of the authorities. This delays the first
33264 download slightly under pathological circumstances, but can prevent
33265 us from downloading a bunch of descriptors we don't need.
33266 - Do not log IPs with TLS failures for incoming TLS
33267 connections. (Fixes bug 382.)
33268 - If the user asks to use invalid exit nodes, be willing to use
33270 - Stop using the reserved ac_cv namespace in our configure script.
33271 - Call stat() slightly less often; use fstat() when possible.
33272 - Refactor the way we handle pending circuits when an OR connection
33273 completes or fails, in an attempt to fix a rare crash bug.
33274 - Only rewrite a conn's address based on X-Forwarded-For: headers
33275 if it's a parseable public IP address; and stop adding extra quotes
33276 to the resulting address.
33279 - Weight directory requests by advertised bandwidth. Now we can
33280 let servers enable write limiting but still allow most clients to
33281 succeed at their directory requests. (We still ignore weights when
33282 choosing a directory authority; I hope this is a feature.)
33285 - Create a new file ReleaseNotes which was the old ChangeLog. The
33286 new ChangeLog file now includes the summaries for all development
33288 - Check for addresses with invalid characters at the exit as well
33289 as at the client, and warn less verbosely when they fail. You can
33290 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
33291 - Adapt a patch from goodell to let the contrib/exitlist script
33292 take arguments rather than require direct editing.
33293 - Inform the server operator when we decide not to advertise a
33294 DirPort due to AccountingMax enabled or a low BandwidthRate. It
33295 was confusing Zax, so now we're hopefully more helpful.
33296 - Bring us one step closer to being able to establish an encrypted
33297 directory tunnel without knowing a descriptor first. Still not
33298 ready yet. As part of the change, now assume we can use a
33299 create_fast cell if we don't know anything about a router.
33300 - Allow exit nodes to use nameservers running on ports other than 53.
33301 - Servers now cache reverse DNS replies.
33302 - Add an --ignore-missing-torrc command-line option so that we can
33303 get the "use sensible defaults if the configuration file doesn't
33304 exist" behavior even when specifying a torrc location on the command
33307 o Minor features (controller):
33308 - Track reasons for OR connection failure; make these reasons
33309 available via the controller interface. (Patch from Mike Perry.)
33310 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
33311 can learn when clients are sending malformed hostnames to Tor.
33312 - Clean up documentation for controller status events.
33313 - Add a REMAP status to stream events to note that a stream's
33314 address has changed because of a cached address or a MapAddress
33318 Changes in version 0.1.2.6-alpha - 2007-01-09
33320 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
33321 connection handles more than 4 gigs in either direction, we crash.
33322 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
33323 advertised exit node, somebody might try to exit from us when
33324 we're bootstrapping and before we've built our descriptor yet.
33325 Refuse the connection rather than crashing.
33328 - Warn if we (as a server) find that we've resolved an address that we
33329 weren't planning to resolve.
33330 - Warn that using select() on any libevent version before 1.1 will be
33331 unnecessarily slow (even for select()).
33332 - Flush ERR-level controller status events just like we currently
33333 flush ERR-level log events, so that a Tor shutdown doesn't prevent
33334 the controller from learning about current events.
33336 o Minor features (more controller status events):
33337 - Implement EXTERNAL_ADDRESS server status event so controllers can
33338 learn when our address changes.
33339 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
33340 can learn when directories reject our descriptor.
33341 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
33342 can learn when a client application is speaking a non-socks protocol
33344 - Implement DANGEROUS_SOCKS client status event so controllers
33345 can learn when a client application is leaking DNS addresses.
33346 - Implement BUG general status event so controllers can learn when
33347 Tor is unhappy about its internal invariants.
33348 - Implement CLOCK_SKEW general status event so controllers can learn
33349 when Tor thinks the system clock is set incorrectly.
33350 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
33351 server status events so controllers can learn when their descriptors
33352 are accepted by a directory.
33353 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
33354 server status events so controllers can learn about Tor's progress in
33355 deciding whether it's reachable from the outside.
33356 - Implement BAD_LIBEVENT general status event so controllers can learn
33357 when we have a version/method combination in libevent that needs to
33359 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
33360 and DNS_USELESS server status events so controllers can learn
33361 about changes to DNS server status.
33363 o Minor features (directory):
33364 - Authorities no longer recommend exits as guards if this would shift
33365 too much load to the exit nodes.
33368 Changes in version 0.1.2.5-alpha - 2007-01-06
33370 - Enable write limiting as well as read limiting. Now we sacrifice
33371 capacity if we're pushing out lots of directory traffic, rather
33372 than overrunning the user's intended bandwidth limits.
33373 - Include TLS overhead when counting bandwidth usage; previously, we
33374 would count only the bytes sent over TLS, but not the bytes used
33376 - Support running the Tor service with a torrc not in the same
33377 directory as tor.exe and default to using the torrc located in
33378 the %appdata%\Tor\ of the user who installed the service. Patch
33380 - Servers now check for the case when common DNS requests are going to
33381 wildcarded addresses (i.e. all getting the same answer), and change
33382 their exit policy to reject *:* if it's happening.
33383 - Implement BEGIN_DIR cells, so we can connect to the directory
33384 server via TLS to do encrypted directory requests rather than
33385 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
33386 config options if you like.
33388 o Minor features (config and docs):
33389 - Start using the state file to store bandwidth accounting data:
33390 the bw_accounting file is now obsolete. We'll keep generating it
33391 for a while for people who are still using 0.1.2.4-alpha.
33392 - Try to batch changes to the state file so that we do as few
33393 disk writes as possible while still storing important things in
33395 - The state file and the bw_accounting file get saved less often when
33396 the AvoidDiskWrites config option is set.
33397 - Make PIDFile work on Windows (untested).
33398 - Add internal descriptions for a bunch of configuration options:
33399 accessible via controller interface and in comments in saved
33401 - Reject *:563 (NNTPS) in the default exit policy. We already reject
33402 NNTP by default, so this seems like a sensible addition.
33403 - Clients now reject hostnames with invalid characters. This should
33404 avoid some inadvertent info leaks. Add an option
33405 AllowNonRFC953Hostnames to disable this behavior, in case somebody
33406 is running a private network with hosts called @, !, and #.
33407 - Add a maintainer script to tell us which options are missing
33408 documentation: "make check-docs".
33409 - Add a new address-spec.txt document to describe our special-case
33410 addresses: .exit, .onion, and .noconnnect.
33412 o Minor features (DNS):
33413 - Ongoing work on eventdns infrastructure: now it has dns server
33414 and ipv6 support. One day Tor will make use of it.
33415 - Add client-side caching for reverse DNS lookups.
33416 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
33417 - When we change nameservers or IP addresses, reset and re-launch
33418 our tests for DNS hijacking.
33420 o Minor features (directory):
33421 - Authorities now specify server versions in networkstatus. This adds
33422 about 2% to the size of compressed networkstatus docs, and allows
33423 clients to tell which servers support BEGIN_DIR and which don't.
33424 The implementation is forward-compatible with a proposed future
33425 protocol version scheme not tied to Tor versions.
33426 - DirServer configuration lines now have an orport= option so
33427 clients can open encrypted tunnels to the authorities without
33428 having downloaded their descriptors yet. Enabled for moria1,
33429 moria2, tor26, and lefkada now in the default configuration.
33430 - Directory servers are more willing to send a 503 "busy" if they
33431 are near their write limit, especially for v1 directory requests.
33432 Now they can use their limited bandwidth for actual Tor traffic.
33433 - Clients track responses with status 503 from dirservers. After a
33434 dirserver has given us a 503, we try not to use it until an hour has
33435 gone by, or until we have no dirservers that haven't given us a 503.
33436 - When we get a 503 from a directory, and we're not a server, we don't
33437 count the failure against the total number of failures allowed
33438 for the thing we're trying to download.
33439 - Report X-Your-Address-Is correctly from tunneled directory
33440 connections; don't report X-Your-Address-Is when it's an internal
33441 address; and never believe reported remote addresses when they're
33443 - Protect against an unlikely DoS attack on directory servers.
33444 - Add a BadDirectory flag to network status docs so that authorities
33445 can (eventually) tell clients about caches they believe to be
33448 o Minor features (controller):
33449 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
33450 - Reimplement GETINFO so that info/names stays in sync with the
33452 - Implement "GETINFO fingerprint".
33453 - Implement "SETEVENTS GUARD" so controllers can get updates on
33454 entry guard status as it changes.
33456 o Minor features (clean up obsolete pieces):
33457 - Remove some options that have been deprecated since at least
33458 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
33459 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
33460 to set log options.
33461 - We no longer look for identity and onion keys in "identity.key" and
33462 "onion.key" -- these were replaced by secret_id_key and
33463 secret_onion_key in 0.0.8pre1.
33464 - We no longer require unrecognized directory entries to be
33467 o Major bugfixes (security):
33468 - Stop sending the HttpProxyAuthenticator string to directory
33469 servers when directory connections are tunnelled through Tor.
33470 - Clients no longer store bandwidth history in the state file.
33471 - Do not log introduction points for hidden services if SafeLogging
33473 - When generating bandwidth history, round down to the nearest
33474 1k. When storing accounting data, round up to the nearest 1k.
33475 - When we're running as a server, remember when we last rotated onion
33476 keys, so that we will rotate keys once they're a week old even if
33477 we never stay up for a week ourselves.
33479 o Major bugfixes (other):
33480 - Fix a longstanding bug in eventdns that prevented the count of
33481 timed-out resolves from ever being reset. This bug caused us to
33482 give up on a nameserver the third time it timed out, and try it
33483 10 seconds later... and to give up on it every time it timed out
33485 - Take out the '5 second' timeout from the connection retry
33486 schedule. Now the first connect attempt will wait a full 10
33487 seconds before switching to a new circuit. Perhaps this will help
33488 a lot. Based on observations from Mike Perry.
33489 - Fix a bug on the Windows implementation of tor_mmap_file() that
33490 would prevent the cached-routers file from ever loading. Reported
33494 - Fix an assert failure when a directory authority sets
33495 AuthDirRejectUnlisted and then receives a descriptor from an
33496 unlisted router. Reported by seeess.
33497 - Avoid a double-free when parsing malformed DirServer lines.
33498 - Fix a bug when a BSD-style PF socket is first used. Patch from
33500 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
33501 to resolve an address at a given exit node even when they ask for
33503 - Servers no longer ever list themselves in their "family" line,
33504 even if configured to do so. This makes it easier to configure
33505 family lists conveniently.
33506 - When running as a server, don't fall back to 127.0.0.1 when no
33507 nameservers are configured in /etc/resolv.conf; instead, make the
33508 user fix resolv.conf or specify nameservers explicitly. (Resolves
33510 - Stop accepting certain malformed ports in configured exit policies.
33511 - Don't re-write the fingerprint file every restart, unless it has
33513 - Stop warning when a single nameserver fails: only warn when _all_ of
33514 our nameservers have failed. Also, when we only have one nameserver,
33515 raise the threshold for deciding that the nameserver is dead.
33516 - Directory authorities now only decide that routers are reachable
33517 if their identity keys are as expected.
33518 - When the user uses bad syntax in the Log config line, stop
33519 suggesting other bad syntax as a replacement.
33520 - Correctly detect ipv6 DNS capability on OpenBSD.
33522 o Minor bugfixes (controller):
33523 - Report the circuit number correctly in STREAM CLOSED events. Bug
33524 reported by Mike Perry.
33525 - Do not report bizarre values for results of accounting GETINFOs
33526 when the last second's write or read exceeds the allotted bandwidth.
33527 - Report "unrecognized key" rather than an empty string when the
33528 controller tries to fetch a networkstatus that doesn't exist.
33531 Changes in version 0.1.1.26 - 2006-12-14
33532 o Security bugfixes:
33533 - Stop sending the HttpProxyAuthenticator string to directory
33534 servers when directory connections are tunnelled through Tor.
33535 - Clients no longer store bandwidth history in the state file.
33536 - Do not log introduction points for hidden services if SafeLogging
33540 - Fix an assert failure when a directory authority sets
33541 AuthDirRejectUnlisted and then receives a descriptor from an
33542 unlisted router (reported by seeess).
33545 Changes in version 0.1.2.4-alpha - 2006-12-03
33547 - Add support for using natd; this allows FreeBSDs earlier than
33548 5.1.2 to have ipfw send connections through Tor without using
33549 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
33552 - Make all connections to addresses of the form ".noconnect"
33553 immediately get closed. This lets application/controller combos
33554 successfully test whether they're talking to the same Tor by
33555 watching for STREAM events.
33556 - Make cross.sh cross-compilation script work even when autogen.sh
33557 hasn't been run. (Patch from Michael Mohr.)
33558 - Statistics dumped by -USR2 now include a breakdown of public key
33559 operations, for profiling.
33562 - Fix a major leak when directory authorities parse their
33563 approved-routers list, a minor memory leak when we fail to pick
33564 an exit node, and a few rare leaks on errors.
33565 - Handle TransPort connections even when the server sends data before
33566 the client sends data. Previously, the connection would just hang
33567 until the client sent data. (Patch from tup based on patch from
33569 - Avoid assert failure when our cached-routers file is empty on
33573 - Don't log spurious warnings when we see a circuit close reason we
33574 don't recognize; it's probably just from a newer version of Tor.
33575 - Have directory authorities allow larger amounts of drift in uptime
33576 without replacing the server descriptor: previously, a server that
33577 restarted every 30 minutes could have 48 "interesting" descriptors
33579 - Start linking to the Tor specification and Tor reference manual
33580 correctly in the Windows installer.
33581 - Add Vidalia to the OS X uninstaller script, so when we uninstall
33582 Tor/Privoxy we also uninstall Vidalia.
33583 - Resume building on Irix64, and fix a lot of warnings from its
33584 MIPSpro C compiler.
33585 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
33586 when we're running as a client.
33589 Changes in version 0.1.1.25 - 2006-11-04
33591 - When a client asks us to resolve (rather than connect to)
33592 an address, and we have a cached answer, give them the cached
33593 answer. Previously, we would give them no answer at all.
33594 - We were building exactly the wrong circuits when we predict
33595 hidden service requirements, meaning Tor would have to build all
33596 its circuits on demand.
33597 - If none of our live entry guards have a high uptime, but we
33598 require a guard with a high uptime, try adding a new guard before
33599 we give up on the requirement. This patch should make long-lived
33600 connections more stable on average.
33601 - When testing reachability of our DirPort, don't launch new
33602 tests when there's already one in progress -- unreachable
33603 servers were stacking up dozens of testing streams.
33605 o Security bugfixes:
33606 - When the user sends a NEWNYM signal, clear the client-side DNS
33607 cache too. Otherwise we continue to act on previous information.
33610 - Avoid a memory corruption bug when creating a hash table for
33612 - Avoid possibility of controller-triggered crash when misusing
33613 certain commands from a v0 controller on platforms that do not
33614 handle printf("%s",NULL) gracefully.
33615 - Avoid infinite loop on unexpected controller input.
33616 - Don't log spurious warnings when we see a circuit close reason we
33617 don't recognize; it's probably just from a newer version of Tor.
33618 - Add Vidalia to the OS X uninstaller script, so when we uninstall
33619 Tor/Privoxy we also uninstall Vidalia.
33622 Changes in version 0.1.2.3-alpha - 2006-10-29
33624 - Prepare for servers to publish descriptors less often: never
33625 discard a descriptor simply for being too old until either it is
33626 recommended by no authorities, or until we get a better one for
33627 the same router. Make caches consider retaining old recommended
33628 routers for even longer.
33629 - If most authorities set a BadExit flag for a server, clients
33630 don't think of it as a general-purpose exit. Clients only consider
33631 authorities that advertise themselves as listing bad exits.
33632 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
33633 headers for content, so that we can work better in the presence of
33634 caching HTTP proxies.
33635 - Allow authorities to list nodes as bad exits by fingerprint or by
33638 o Minor features, controller:
33639 - Add a REASON field to CIRC events; for backward compatibility, this
33640 field is sent only to controllers that have enabled the extended
33641 event format. Also, add additional reason codes to explain why
33642 a given circuit has been destroyed or truncated. (Patches from
33644 - Add a REMOTE_REASON field to extended CIRC events to tell the
33645 controller about why a remote OR told us to close a circuit.
33646 - Stream events also now have REASON and REMOTE_REASON fields,
33647 working much like those for circuit events.
33648 - There's now a GETINFO ns/... field so that controllers can ask Tor
33649 about the current status of a router.
33650 - A new event type "NS" to inform a controller when our opinion of
33651 a router's status has changed.
33652 - Add a GETINFO events/names and GETINFO features/names so controllers
33653 can tell which events and features are supported.
33654 - A new CLEARDNSCACHE signal to allow controllers to clear the
33655 client-side DNS cache without expiring circuits.
33657 o Security bugfixes:
33658 - When the user sends a NEWNYM signal, clear the client-side DNS
33659 cache too. Otherwise we continue to act on previous information.
33662 - Avoid sending junk to controllers or segfaulting when a controller
33663 uses EVENT_NEW_DESC with verbose nicknames.
33664 - Stop triggering asserts if the controller tries to extend hidden
33665 service circuits (reported by mwenge).
33666 - Avoid infinite loop on unexpected controller input.
33667 - When the controller does a "GETINFO network-status", tell it
33668 about even those routers whose descriptors are very old, and use
33669 long nicknames where appropriate.
33670 - Change NT service functions to be loaded on demand. This lets us
33671 build with MinGW without breaking Tor for Windows 98 users.
33672 - Do DirPort reachability tests less often, since a single test
33673 chews through many circuits before giving up.
33674 - In the hidden service example in torrc.sample, stop recommending
33675 esoteric and discouraged hidden service options.
33676 - When stopping an NT service, wait up to 10 sec for it to actually
33677 stop. Patch from Matt Edman; resolves bug 295.
33678 - Fix handling of verbose nicknames with ORCONN controller events:
33679 make them show up exactly when requested, rather than exactly when
33681 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
33682 printing a duplicate "$" in the keys we send (reported by mwenge).
33683 - Correctly set maximum connection limit on Cygwin. (This time
33685 - Try to detect Windows correctly when cross-compiling.
33686 - Detect the size of the routers file correctly even if it is
33687 corrupted (on systems without mmap) or not page-aligned (on systems
33688 with mmap). This bug was harmless.
33689 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
33690 to open a stream fails; now we do in more cases. This should
33691 make clients able to find a good exit faster in some cases, since
33692 unhandleable requests will now get an error rather than timing out.
33693 - Resolve two memory leaks when rebuilding the on-disk router cache
33694 (reported by fookoowa).
33695 - Clean up minor code warnings suggested by the MIPSpro C compiler,
33696 and reported by some Centos users.
33697 - Controller signals now work on non-Unix platforms that don't define
33698 SIGUSR1 and SIGUSR2 the way we expect.
33699 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
33700 values before failing, and always enables eventdns.
33701 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
33702 Try to fix this in configure.in by checking for most functions
33703 before we check for libevent.
33706 Changes in version 0.1.2.2-alpha - 2006-10-07
33708 - Make our async eventdns library on-by-default for Tor servers,
33709 and plan to deprecate the separate dnsworker threads.
33710 - Add server-side support for "reverse" DNS lookups (using PTR
33711 records so clients can determine the canonical hostname for a given
33712 IPv4 address). Only supported by servers using eventdns; servers
33713 now announce in their descriptors whether they support eventdns.
33714 - Specify and implement client-side SOCKS5 interface for reverse DNS
33715 lookups (see doc/socks-extensions.txt).
33716 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
33717 connect to directory servers through Tor. Previously, clients needed
33718 to find Tor exits to make private connections to directory servers.
33719 - Avoid choosing Exit nodes for entry or middle hops when the
33720 total bandwidth available from non-Exit nodes is much higher than
33721 the total bandwidth available from Exit nodes.
33722 - Workaround for name servers (like Earthlink's) that hijack failing
33723 DNS requests and replace the no-such-server answer with a "helpful"
33724 redirect to an advertising-driven search portal. Also work around
33725 DNS hijackers who "helpfully" decline to hijack known-invalid
33726 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
33727 lets you turn it off.
33728 - Send out a burst of long-range padding cells once we've established
33729 that we're reachable. Spread them over 4 circuits, so hopefully
33730 a few will be fast. This exercises our bandwidth and bootstraps
33731 us into the directory more quickly.
33733 o New/improved config options:
33734 - Add new config option "ResolvConf" to let the server operator
33735 choose an alternate resolve.conf file when using eventdns.
33736 - Add an "EnforceDistinctSubnets" option to control our "exclude
33737 servers on the same /16" behavior. It's still on by default; this
33738 is mostly for people who want to operate private test networks with
33739 all the machines on the same subnet.
33740 - If one of our entry guards is on the ExcludeNodes list, or the
33741 directory authorities don't think it's a good guard, treat it as
33742 if it were unlisted: stop using it as a guard, and throw it off
33743 the guards list if it stays that way for a long time.
33744 - Allow directory authorities to be marked separately as authorities
33745 for the v1 directory protocol, the v2 directory protocol, and
33746 as hidden service directories, to make it easier to retire old
33747 authorities. V1 authorities should set "HSAuthoritativeDir 1"
33748 to continue being hidden service authorities too.
33749 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
33751 o Minor features, controller:
33752 - Fix CIRC controller events so that controllers can learn the
33753 identity digests of non-Named servers used in circuit paths.
33754 - Let controllers ask for more useful identifiers for servers. Instead
33755 of learning identity digests for un-Named servers and nicknames
33756 for Named servers, the new identifiers include digest, nickname,
33757 and indication of Named status. Off by default; see control-spec.txt
33758 for more information.
33759 - Add a "getinfo address" controller command so it can display Tor's
33760 best guess to the user.
33761 - New controller event to alert the controller when our server
33762 descriptor has changed.
33763 - Give more meaningful errors on controller authentication failure.
33765 o Minor features, other:
33766 - When asked to resolve a hostname, don't use non-exit servers unless
33767 requested to do so. This allows servers with broken DNS to be
33768 useful to the network.
33769 - Divide eventdns log messages into warn and info messages.
33770 - Reserve the nickname "Unnamed" for routers that can't pick
33771 a hostname: any router can call itself Unnamed; directory
33772 authorities will never allocate Unnamed to any particular router;
33773 clients won't believe that any router is the canonical Unnamed.
33774 - Only include function names in log messages for info/debug messages.
33775 For notice/warn/err, the content of the message should be clear on
33776 its own, and printing the function name only confuses users.
33777 - Avoid some false positives during reachability testing: don't try
33778 to test via a server that's on the same /24 as us.
33779 - If we fail to build a circuit to an intended enclave, and it's
33780 not mandatory that we use that enclave, stop wanting it.
33781 - When eventdns is enabled, allow multithreaded builds on NetBSD and
33782 OpenBSD. (We had previously disabled threads on these platforms
33783 because they didn't have working thread-safe resolver functions.)
33785 o Major bugfixes, anonymity/security:
33786 - If a client asked for a server by name, and there's a named server
33787 in our network-status but we don't have its descriptor yet, we
33788 could return an unnamed server instead.
33789 - Fix NetBSD bug that could allow someone to force uninitialized RAM
33790 to be sent to a server's DNS resolver. This only affects NetBSD
33791 and other platforms that do not bounds-check tolower().
33792 - Reject (most) attempts to use Tor circuits with length one. (If
33793 many people start using Tor as a one-hop proxy, exit nodes become
33794 a more attractive target for compromise.)
33795 - Just because your DirPort is open doesn't mean people should be
33796 able to remotely teach you about hidden service descriptors. Now
33797 only accept rendezvous posts if you've got HSAuthoritativeDir set.
33799 o Major bugfixes, other:
33800 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
33801 - When a client asks the server to resolve (not connect to)
33802 an address, and it has a cached answer, give them the cached answer.
33803 Previously, the server would give them no answer at all.
33804 - Allow really slow clients to not hang up five minutes into their
33805 directory downloads (suggested by Adam J. Richter).
33806 - We were building exactly the wrong circuits when we anticipated
33807 hidden service requirements, meaning Tor would have to build all
33808 its circuits on demand.
33809 - Avoid crashing when we mmap a router cache file of size 0.
33810 - When testing reachability of our DirPort, don't launch new
33811 tests when there's already one in progress -- unreachable
33812 servers were stacking up dozens of testing streams.
33814 o Minor bugfixes, correctness:
33815 - If we're a directory mirror and we ask for "all" network status
33816 documents, we would discard status documents from authorities
33817 we don't recognize.
33818 - Avoid a memory corruption bug when creating a hash table for
33820 - Avoid controller-triggered crash when misusing certain commands
33821 from a v0 controller on platforms that do not handle
33822 printf("%s",NULL) gracefully.
33823 - Don't crash when a controller sends a third argument to an
33824 "extendcircuit" request.
33825 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
33826 response; fix error code when "getinfo dir/status/" fails.
33827 - Avoid crash when telling controller stream-status and a stream
33829 - Patch from Adam Langley to fix assert() in eventdns.c.
33830 - Fix a debug log message in eventdns to say "X resolved to Y"
33831 instead of "X resolved to X".
33832 - Make eventdns give strings for DNS errors, not just error numbers.
33833 - Track unreachable entry guards correctly: don't conflate
33834 'unreachable by us right now' with 'listed as down by the directory
33835 authorities'. With the old code, if a guard was unreachable by
33836 us but listed as running, it would clog our guard list forever.
33837 - Behave correctly in case we ever have a network with more than
33838 2GB/s total advertised capacity.
33839 - Make TrackExitHosts case-insensitive, and fix the behavior of
33840 ".suffix" TrackExitHosts items to avoid matching in the middle of
33842 - Finally fix the openssl warnings from newer gccs that believe that
33843 ignoring a return value is okay, but casting a return value and
33844 then ignoring it is a sign of madness.
33845 - Prevent the contrib/exitlist script from printing the same
33846 result more than once.
33847 - Patch from Steve Hildrey: Generate network status correctly on
33848 non-versioning dirservers.
33849 - Don't listen to the X-Your-Address-Is hint if you did the lookup
33850 via Tor; otherwise you'll think you're the exit node's IP address.
33852 o Minor bugfixes, performance:
33853 - Two small performance improvements on parsing descriptors.
33854 - Major performance improvement on inserting descriptors: change
33855 algorithm from O(n^2) to O(n).
33856 - Make the common memory allocation path faster on machines where
33857 malloc(0) returns a pointer.
33858 - Start remembering X-Your-Address-Is directory hints even if you're
33859 a client, so you can become a server more smoothly.
33860 - Avoid duplicate entries on MyFamily line in server descriptor.
33862 o Packaging, features:
33863 - Remove architecture from OS X builds. The official builds are
33864 now universal binaries.
33865 - The Debian package now uses --verify-config when (re)starting,
33866 to distinguish configuration errors from other errors.
33867 - Update RPMs to require libevent 1.1b.
33869 o Packaging, bugfixes:
33870 - Patches so Tor builds with MinGW on Windows.
33871 - Patches so Tor might run on Cygwin again.
33872 - Resume building on non-gcc compilers and ancient gcc. Resume
33873 building with the -O0 compile flag. Resume building cleanly on
33875 - Run correctly on OS X platforms with case-sensitive filesystems.
33876 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
33877 - Add autoconf checks so Tor can build on Solaris x86 again.
33880 - Documented (and renamed) ServerDNSSearchDomains and
33881 ServerDNSResolvConfFile options.
33882 - Be clearer that the *ListenAddress directives can be repeated
33886 Changes in version 0.1.1.24 - 2006-09-29
33888 - Allow really slow clients to not hang up five minutes into their
33889 directory downloads (suggested by Adam J. Richter).
33890 - Fix major performance regression from 0.1.0.x: instead of checking
33891 whether we have enough directory information every time we want to
33892 do something, only check when the directory information has changed.
33893 This should improve client CPU usage by 25-50%.
33894 - Don't crash if, after a server has been running for a while,
33895 it can't resolve its hostname.
33898 - Allow Tor to start when RunAsDaemon is set but no logs are set.
33899 - Don't crash when the controller receives a third argument to an
33900 "extendcircuit" request.
33901 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
33902 response; fix error code when "getinfo dir/status/" fails.
33903 - Fix configure.in to not produce broken configure files with
33904 more recent versions of autoconf. Thanks to Clint for his auto*
33906 - Fix security bug on NetBSD that could allow someone to force
33907 uninitialized RAM to be sent to a server's DNS resolver. This
33908 only affects NetBSD and other platforms that do not bounds-check
33910 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
33911 methods: these are known to be buggy.
33912 - If we're a directory mirror and we ask for "all" network status
33913 documents, we would discard status documents from authorities
33914 we don't recognize.
33917 Changes in version 0.1.2.1-alpha - 2006-08-27
33919 - Add "eventdns" async dns library from Adam Langley, tweaked to
33920 build on OSX and Windows. Only enabled if you pass the
33921 --enable-eventdns argument to configure.
33922 - Allow servers with no hostname or IP address to learn their
33923 IP address by asking the directory authorities. This code only
33924 kicks in when you would normally have exited with a "no address"
33925 error. Nothing's authenticated, so use with care.
33926 - Rather than waiting a fixed amount of time between retrying
33927 application connections, we wait only 5 seconds for the first,
33928 10 seconds for the second, and 15 seconds for each retry after
33929 that. Hopefully this will improve the expected user experience.
33930 - Patch from Tup to add support for transparent AP connections:
33931 this basically bundles the functionality of trans-proxy-tor
33932 into the Tor mainline. Now hosts with compliant pf/netfilter
33933 implementations can redirect TCP connections straight to Tor
33934 without diverting through SOCKS. Needs docs.
33935 - Busy directory servers save lots of memory by spooling server
33936 descriptors, v1 directories, and v2 networkstatus docs to buffers
33937 as needed rather than en masse. Also mmap the cached-routers
33938 files, so we don't need to keep the whole thing in memory too.
33939 - Automatically avoid picking more than one node from the same
33940 /16 network when constructing a circuit.
33941 - Revise and clean up the torrc.sample that we ship with; add
33942 a section for BandwidthRate and BandwidthBurst.
33945 - Split circuit_t into origin_circuit_t and or_circuit_t, and
33946 split connection_t into edge, or, dir, control, and base structs.
33947 These will save quite a bit of memory on busy servers, and they'll
33948 also help us track down bugs in the code and bugs in the spec.
33949 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
33950 or later. Log when we are doing this, so we can diagnose it when
33951 it fails. (Also, recommend libevent 1.1b for kqueue and
33952 win32 methods; deprecate libevent 1.0b harder; make libevent
33953 recommendation system saner.)
33954 - Start being able to build universal binaries on OS X (thanks
33956 - Export the default exit policy via the control port, so controllers
33957 don't need to guess what it is / will be later.
33958 - Add a man page entry for ProtocolWarnings.
33959 - Add TestVia config option to the man page.
33960 - Remove even more protocol-related warnings from Tor server logs,
33961 such as bad TLS handshakes and malformed begin cells.
33962 - Stop fetching descriptors if you're not a dir mirror and you
33963 haven't tried to establish any circuits lately. [This currently
33964 causes some dangerous behavior, because when you start up again
33965 you'll use your ancient server descriptors.]
33966 - New DirPort behavior: if you have your dirport set, you download
33967 descriptors aggressively like a directory mirror, whether or not
33968 your ORPort is set.
33969 - Get rid of the router_retry_connections notion. Now routers
33970 no longer try to rebuild long-term connections to directory
33971 authorities, and directory authorities no longer try to rebuild
33972 long-term connections to all servers. We still don't hang up
33973 connections in these two cases though -- we need to look at it
33974 more carefully to avoid flapping, and we likely need to wait til
33975 0.1.1.x is obsolete.
33976 - Drop compatibility with obsolete Tors that permit create cells
33977 to have the wrong circ_id_type.
33978 - Re-enable per-connection rate limiting. Get rid of the "OP
33979 bandwidth" concept. Lay groundwork for "bandwidth classes" --
33980 separate global buckets that apply depending on what sort of conn
33982 - Start publishing one minute or so after we find our ORPort
33983 to be reachable. This will help reduce the number of descriptors
33984 we have for ourselves floating around, since it's quite likely
33985 other things (e.g. DirPort) will change during that minute too.
33986 - Fork the v1 directory protocol into its own spec document,
33987 and mark dir-spec.txt as the currently correct (v2) spec.
33990 - When we find our DirPort to be reachable, publish a new descriptor
33991 so we'll tell the world (reported by pnx).
33992 - Publish a new descriptor after we hup/reload. This is important
33993 if our config has changed such that we'll want to start advertising
33994 our DirPort now, etc.
33995 - Allow Tor to start when RunAsDaemon is set but no logs are set.
33996 - When we have a state file we cannot parse, tell the user and
33997 move it aside. Now we avoid situations where the user starts
33998 Tor in 1904, Tor writes a state file with that timestamp in it,
33999 the user fixes her clock, and Tor refuses to start.
34000 - Fix configure.in to not produce broken configure files with
34001 more recent versions of autoconf. Thanks to Clint for his auto*
34003 - "tor --verify-config" now exits with -1(255) or 0 depending on
34004 whether the config options are bad or good.
34005 - Resolve bug 321 when using dnsworkers: append a period to every
34006 address we resolve at the exit node, so that we do not accidentally
34007 pick up local addresses, and so that failing searches are retried
34008 in the resolver search domains. (This is already solved for
34009 eventdns.) (This breaks Blossom servers for now.)
34010 - If we are using an exit enclave and we can't connect, e.g. because
34011 its webserver is misconfigured to not listen on localhost, then
34012 back off and try connecting from somewhere else before we fail.
34015 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
34016 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
34017 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
34018 when the IP address is mapped through MapAddress to a hostname.
34019 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
34020 useless IPv6 DNS resolves.
34021 - Patch suggested by Karsten Loesing: respond to SIGNAL command
34022 before we execute the signal, in case the signal shuts us down.
34023 - Clean up AllowInvalidNodes man page entry.
34024 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
34025 - Add more asserts to track down an assert error on a windows Tor
34026 server with connection_add being called with socket == -1.
34027 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
34028 - Fix misleading log messages: an entry guard that is "unlisted",
34029 as well as not known to be "down" (because we've never heard
34030 of it), is not therefore "up".
34031 - Remove code to special-case "-cvs" ending, since it has not
34032 actually mattered since 0.0.9.
34033 - Make our socks5 handling more robust to broken socks clients:
34034 throw out everything waiting on the buffer in between socks
34035 handshake phases, since they can't possibly (so the theory
34036 goes) have predicted what we plan to respond to them.
34039 Changes in version 0.1.1.23 - 2006-07-30
34041 - Fast Tor servers, especially exit nodes, were triggering asserts
34042 due to a bug in handling the list of pending DNS resolves. Some
34043 bugs still remain here; we're hunting them.
34044 - Entry guards could crash clients by sending unexpected input.
34045 - More fixes on reachability testing: if you find yourself reachable,
34046 then don't ever make any client requests (so you stop predicting
34047 circuits), then hup or have your clock jump, then later your IP
34048 changes, you won't think circuits are working, so you won't try to
34049 test reachability, so you won't publish.
34052 - Avoid a crash if the controller does a resetconf firewallports
34053 and then a setconf fascistfirewall=1.
34054 - Avoid an integer underflow when the dir authority decides whether
34055 a router is stable: we might wrongly label it stable, and compute
34056 a slightly wrong median stability, when a descriptor is published
34058 - Fix a place where we might trigger an assert if we can't build our
34059 own server descriptor yet.
34062 Changes in version 0.1.1.22 - 2006-07-05
34064 - Fix a big bug that was causing servers to not find themselves
34065 reachable if they changed IP addresses. Since only 0.1.1.22+
34066 servers can do reachability testing correctly, now we automatically
34067 make sure to test via one of these.
34068 - Fix to allow clients and mirrors to learn directory info from
34069 descriptor downloads that get cut off partway through.
34070 - Directory authorities had a bug in deciding if a newly published
34071 descriptor was novel enough to make everybody want a copy -- a few
34072 servers seem to be publishing new descriptors many times a minute.
34074 - Fix a rare bug that was causing some servers to complain about
34075 "closing wedged cpuworkers" and skip some circuit create requests.
34076 - Make the Exit flag in directory status documents actually work.
34079 Changes in version 0.1.1.21 - 2006-06-10
34080 o Crash and assert fixes from 0.1.1.20:
34081 - Fix a rare crash on Tor servers that have enabled hibernation.
34082 - Fix a seg fault on startup for Tor networks that use only one
34083 directory authority.
34084 - Fix an assert from a race condition that occurs on Tor servers
34085 while exiting, where various threads are trying to log that they're
34086 exiting, and delete the logs, at the same time.
34087 - Make our unit tests pass again on certain obscure platforms.
34090 - Add support for building SUSE RPM packages.
34091 - Speed up initial bootstrapping for clients: if we are making our
34092 first ever connection to any entry guard, then don't mark it down
34094 - When only one Tor server in the network is labelled as a guard,
34095 and we've already picked him, we would cycle endlessly picking him
34096 again, being unhappy about it, etc. Now we specifically exclude
34097 current guards when picking a new guard.
34098 - Servers send create cells more reliably after the TLS connection
34099 is established: we were sometimes forgetting to send half of them
34100 when we had more than one pending.
34101 - If we get a create cell that asks us to extend somewhere, but the
34102 Tor server there doesn't match the expected digest, we now send
34103 a destroy cell back, rather than silently doing nothing.
34104 - Make options->RedirectExit work again.
34105 - Make cookie authentication for the controller work again.
34106 - Stop being picky about unusual characters in the arguments to
34107 mapaddress. It's none of our business.
34108 - Add a new config option "TestVia" that lets you specify preferred
34109 middle hops to use for test circuits. Perhaps this will let me
34110 debug the reachability problems better.
34112 o Log / documentation fixes:
34113 - If we're a server and some peer has a broken TLS certificate, don't
34114 log about it unless ProtocolWarnings is set, i.e., we want to hear
34115 about protocol violations by others.
34116 - Fix spelling of VirtualAddrNetwork in man page.
34117 - Add a better explanation at the top of the autogenerated torrc file
34118 about what happened to our old torrc.
34121 Changes in version 0.1.1.20 - 2006-05-23
34123 - Downgrade a log severity where servers complain that they're
34125 - Avoid a compile warning on FreeBSD.
34126 - Remove string size limit on NEWDESC messages; solve bug 291.
34127 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
34128 more thoroughly when we're running on windows.
34131 Changes in version 0.1.1.19-rc - 2006-05-03
34133 - Regenerate our local descriptor if it's dirty and we try to use
34134 it locally (e.g. if it changes during reachability detection).
34135 - If we setconf our ORPort to 0, we continued to listen on the
34136 old ORPort and receive connections.
34137 - Avoid a second warning about machine/limits.h on Debian
34139 - Be willing to add our own routerinfo into the routerlist.
34140 Now authorities will include themselves in their directories
34141 and network-statuses.
34142 - Stop trying to upload rendezvous descriptors to every
34143 directory authority: only try the v1 authorities.
34144 - Servers no longer complain when they think they're not
34145 registered with the directory authorities. There were too many
34147 - Backport dist-rpm changes so rpms can be built without errors.
34150 - Implement an option, VirtualAddrMask, to set which addresses
34151 get handed out in response to mapaddress requests. This works
34152 around a bug in tsocks where 127.0.0.0/8 is never socksified.
34155 Changes in version 0.1.1.18-rc - 2006-04-10
34157 - Work harder to download live network-statuses from all the
34158 directory authorities we know about. Improve the threshold
34159 decision logic so we're more robust to edge cases.
34160 - When fetching rendezvous descriptors, we were willing to ask
34161 v2 authorities too, which would always return 404.
34164 - Stop listing down or invalid nodes in the v1 directory. This will
34165 reduce its bulk by about 1/3, and reduce load on directory
34167 - When deciding whether a router is Fast or Guard-worthy, consider
34168 his advertised BandwidthRate and not just the BandwidthCapacity.
34169 - No longer ship INSTALL and README files -- they are useless now.
34170 - Force rpmbuild to behave and honor target_cpu.
34171 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
34172 - Start to include translated versions of the tor-doc-*.html
34173 files, along with the screenshots. Still needs more work.
34174 - Start sending back 512 and 451 errors if mapaddress fails,
34175 rather than not sending anything back at all.
34176 - When we fail to bind or listen on an incoming or outgoing
34177 socket, we should close it before failing. otherwise we just
34178 leak it. (thanks to weasel for finding.)
34179 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
34180 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
34181 - Make NoPublish (even though deprecated) work again.
34182 - Fix a minor security flaw where a versioning auth dirserver
34183 could list a recommended version many times in a row to make
34184 clients more convinced that it's recommended.
34185 - Fix crash bug if there are two unregistered servers running
34186 with the same nickname, one of them is down, and you ask for
34187 them by nickname in your EntryNodes or ExitNodes. Also, try
34188 to pick the one that's running rather than an arbitrary one.
34189 - Fix an infinite loop we could hit if we go offline for too long.
34190 - Complain when we hit WSAENOBUFS on recv() or write() too.
34191 Perhaps this will help us hunt the bug.
34192 - If you're not a versioning dirserver, don't put the string
34193 "client-versions \nserver-versions \n" in your network-status.
34194 - Lower the minimum required number of file descriptors to 1000,
34195 so we can have some overhead for Valgrind on Linux, where the
34196 default ulimit -n is 1024.
34199 - Add tor.dizum.com as the fifth authoritative directory server.
34200 - Add a new config option FetchUselessDescriptors, off by default,
34201 for when you plan to run "exitlist" on your client and you want
34202 to know about even the non-running descriptors.
34205 Changes in version 0.1.1.17-rc - 2006-03-28
34207 - Clients and servers since 0.1.1.10-alpha have been expiring
34208 connections whenever they are idle for 5 minutes and they *do*
34209 have circuits on them. Oops. With this new version, clients will
34210 discard their previous entry guard choices and avoid choosing
34211 entry guards running these flawed versions.
34212 - Fix memory leak when uncompressing concatenated zlib streams. This
34213 was causing substantial leaks over time on Tor servers.
34214 - The v1 directory was including servers as much as 48 hours old,
34215 because that's how the new routerlist->routers works. Now only
34216 include them if they're 20 hours old or less.
34219 - Resume building on irix64, netbsd 2.0, etc.
34220 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
34222 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
34223 and it is confusing some users.
34224 - Mirrors stop caching the v1 directory so often.
34225 - Make the max number of old descriptors that a cache will hold
34226 rise with the number of directory authorities, so we can scale.
34227 - Change our win32 uname() hack to be more forgiving about what
34228 win32 versions it thinks it's found.
34231 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
34233 - When the controller's *setconf commands fail, collect an error
34234 message in a string and hand it back to the controller.
34235 - Make the v2 dir's "Fast" flag based on relative capacity, just
34236 like "Stable" is based on median uptime. Name everything in the
34237 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
34238 - Log server fingerprint on startup, so new server operators don't
34239 have to go hunting around their filesystem for it.
34240 - Return a robots.txt on our dirport to discourage google indexing.
34241 - Let the controller ask for GETINFO dir/status/foo so it can ask
34242 directly rather than connecting to the dir port. Only works when
34243 dirport is set for now.
34245 o New config options rather than constants in the code:
34246 - SocksTimeout: How long do we let a socks connection wait
34247 unattached before we fail it?
34248 - CircuitBuildTimeout: Cull non-open circuits that were born
34249 at least this many seconds ago.
34250 - CircuitIdleTimeout: Cull open clean circuits that were born
34251 at least this many seconds ago.
34254 Changes in version 0.1.1.16-rc - 2006-03-18
34255 o Bugfixes on 0.1.1.15-rc:
34256 - Fix assert when the controller asks to attachstream a connect-wait
34257 or resolve-wait stream.
34258 - Now do address rewriting when the controller asks us to attach
34259 to a particular circuit too. This will let Blossom specify
34260 "moria2.exit" without having to learn what moria2's IP address is.
34261 - Make the "tor --verify-config" command-line work again, so people
34262 can automatically check if their torrc will parse.
34263 - Authoritative dirservers no longer require an open connection from
34264 a server to consider him "reachable". We need this change because
34265 when we add new auth dirservers, old servers won't know not to
34267 - Let Tor build on Sun CC again.
34268 - Fix an off-by-one buffer size in dirserv.c that magically never
34269 hit our three authorities but broke sjmurdoch's own tor network.
34270 - If we as a directory mirror don't know of any v1 directory
34271 authorities, then don't try to cache any v1 directories.
34272 - Stop warning about unknown servers in our family when they are
34273 given as hex digests.
34274 - Stop complaining as quickly to the server operator that he
34275 hasn't registered his nickname/key binding.
34276 - Various cleanups so we can add new V2 Auth Dirservers.
34277 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
34278 reflect the updated flags in our v2 dir protocol.
34279 - Resume allowing non-printable characters for exit streams (both
34280 for connecting and for resolving). Now we tolerate applications
34281 that don't follow the RFCs. But continue to block malformed names
34284 o Bugfixes on 0.1.0.x:
34285 - Fix assert bug in close_logs(): when we close and delete logs,
34286 remove them all from the global "logfiles" list.
34287 - Fix minor integer overflow in calculating when we expect to use up
34288 our bandwidth allocation before hibernating.
34289 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
34290 there are multiple SSLs installed with different versions.
34291 - When we try to be a server and Address is not explicitly set and
34292 our hostname resolves to a private IP address, try to use an
34293 interface address if it has a public address. Now Windows machines
34294 that think of themselves as localhost can work by default.
34297 - Let the controller ask for GETINFO dir/server/foo so it can ask
34298 directly rather than connecting to the dir port.
34299 - Let the controller tell us about certain router descriptors
34300 that it doesn't want Tor to use in circuits. Implement
34301 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
34302 - New config option SafeSocks to reject all application connections
34303 using unsafe socks protocols. Defaults to off.
34306 Changes in version 0.1.1.15-rc - 2006-03-11
34307 o Bugfixes and cleanups:
34308 - When we're printing strings from the network, don't try to print
34309 non-printable characters. This protects us against shell escape
34310 sequence exploits, and also against attacks to fool humans into
34311 misreading their logs.
34312 - Fix a bug where Tor would fail to establish any connections if you
34313 left it off for 24 hours and then started it: we were happy with
34314 the obsolete network statuses, but they all referred to router
34315 descriptors that were too old to fetch, so we ended up with no
34316 valid router descriptors.
34317 - Fix a seg fault in the controller's "getinfo orconn-status"
34318 command while listing status on incoming handshaking connections.
34319 Introduce a status name "NEW" for these connections.
34320 - If we get a linelist or linelist_s config option from the torrc
34321 (e.g. ExitPolicy) and it has no value, warn and skip rather than
34322 silently resetting it to its default.
34323 - Don't abandon entry guards until they've been down or gone for
34325 - Cleaner and quieter log messages.
34328 - New controller signal NEWNYM that makes new application requests
34329 use clean circuits.
34330 - Add a new circuit purpose 'controller' to let the controller ask
34331 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
34332 controller command to let you specify the purpose if you're
34333 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
34334 command to let you change a circuit's purpose after it's been
34336 - Accept "private:*" in routerdesc exit policies; not generated yet
34337 because older Tors do not understand it.
34338 - Add BSD-style contributed startup script "rc.subr" from Peter
34342 Changes in version 0.1.1.14-alpha - 2006-02-20
34343 o Bugfixes on 0.1.1.x:
34344 - Don't die if we ask for a stdout or stderr log (even implicitly)
34345 and we're set to RunAsDaemon -- just warn.
34346 - We still had a few bugs in the OR connection rotation code that
34347 caused directory servers to slowly aggregate connections to other
34348 fast Tor servers. This time for sure!
34349 - Make log entries on Win32 include the name of the function again.
34350 - We were treating a pair of exit policies if they were equal even
34351 if one said accept and the other said reject -- causing us to
34352 not always publish a new descriptor since we thought nothing
34354 - Retry pending server downloads as well as pending networkstatus
34355 downloads when we unexpectedly get a socks request.
34356 - We were ignoring the IS_FAST flag in the directory status,
34357 meaning we were willing to pick trivial-bandwidth nodes for "fast"
34359 - If the controller's SAVECONF command fails (e.g. due to file
34360 permissions), let the controller know that it failed.
34363 - If we're trying to be a Tor server and running Windows 95/98/ME
34364 as a server, explain that we'll likely crash.
34365 - When we're a server, a client asks for an old-style directory,
34366 and our write bucket is empty, don't give it to him. This way
34367 small servers can continue to serve the directory *sometimes*,
34368 without getting overloaded.
34369 - Compress exit policies even more -- look for duplicate lines
34371 - Clients now honor the "guard" flag in the router status when
34372 picking entry guards, rather than looking at is_fast or is_stable.
34373 - Retain unrecognized lines in $DATADIR/state file, so that we can
34374 be forward-compatible.
34375 - Generate 18.0.0.0/8 address policy format in descs when we can;
34376 warn when the mask is not reducible to a bit-prefix.
34377 - Let the user set ControlListenAddress in the torrc. This can be
34378 dangerous, but there are some cases (like a secured LAN) where it
34380 - Split ReachableAddresses into ReachableDirAddresses and
34381 ReachableORAddresses, so we can restrict Dir conns to port 80
34382 and OR conns to port 443.
34383 - Now we can target arch and OS in rpm builds (contributed by
34384 Phobos). Also make the resulting dist-rpm filename match the
34386 - New config options to help controllers: FetchServerDescriptors
34387 and FetchHidServDescriptors for whether to fetch server
34388 info and hidserv info or let the controller do it, and
34389 PublishServerDescriptor and PublishHidServDescriptors.
34390 - Also let the controller set the __AllDirActionsPrivate config
34391 option if you want all directory fetches/publishes to happen via
34392 Tor (it assumes your controller bootstraps your circuits).
34395 Changes in version 0.1.0.17 - 2006-02-17
34396 o Crash bugfixes on 0.1.0.x:
34397 - When servers with a non-zero DirPort came out of hibernation,
34398 sometimes they would trigger an assert.
34400 o Other important bugfixes:
34401 - On platforms that don't have getrlimit (like Windows), we were
34402 artificially constraining ourselves to a max of 1024
34403 connections. Now just assume that we can handle as many as 15000
34404 connections. Hopefully this won't cause other problems.
34406 o Backported features:
34407 - When we're a server, a client asks for an old-style directory,
34408 and our write bucket is empty, don't give it to him. This way
34409 small servers can continue to serve the directory *sometimes*,
34410 without getting overloaded.
34411 - Whenever you get a 503 in response to a directory fetch, try
34412 once more. This will become important once servers start sending
34413 503's whenever they feel busy.
34414 - Fetch a new directory every 120 minutes, not every 40 minutes.
34415 Now that we have hundreds of thousands of users running the old
34416 directory algorithm, it's starting to hurt a lot.
34417 - Bump up the period for forcing a hidden service descriptor upload
34418 from 20 minutes to 1 hour.
34421 Changes in version 0.1.1.13-alpha - 2006-02-09
34422 o Crashes in 0.1.1.x:
34423 - When you tried to setconf ORPort via the controller, Tor would
34424 crash. So people using TorCP to become a server were sad.
34425 - Solve (I hope) the stack-smashing bug that we were seeing on fast
34426 servers. The problem appears to be something do with OpenSSL's
34427 random number generation, or how we call it, or something. Let me
34428 know if the crashes continue.
34429 - Turn crypto hardware acceleration off by default, until we find
34430 somebody smart who can test it for us. (It appears to produce
34431 seg faults in at least some cases.)
34432 - Fix a rare assert error when we've tried all intro points for
34433 a hidden service and we try fetching the service descriptor again:
34434 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
34437 - Fix a major load balance bug: we were round-robining in 16 KB
34438 chunks, and servers with bandwidthrate of 20 KB, while downloading
34439 a 600 KB directory, would starve their other connections. Now we
34440 try to be a bit more fair.
34441 - Dir authorities and mirrors were never expiring the newest
34442 descriptor for each server, causing memory and directory bloat.
34443 - Fix memory-bloating and connection-bloating bug on servers: We
34444 were never closing any connection that had ever had a circuit on
34445 it, because we were checking conn->n_circuits == 0, yet we had a
34446 bug that let it go negative.
34447 - Make Tor work using squid as your http proxy again -- squid
34448 returns an error if you ask for a URL that's too long, and it uses
34449 a really generic error message. Plus, many people are behind a
34450 transparent squid so they don't even realize it.
34451 - On platforms that don't have getrlimit (like Windows), we were
34452 artificially constraining ourselves to a max of 1024
34453 connections. Now just assume that we can handle as many as 15000
34454 connections. Hopefully this won't cause other problems.
34455 - Add a new config option ExitPolicyRejectPrivate which defaults to
34456 1. This means all exit policies will begin with rejecting private
34457 addresses, unless the server operator explicitly turns it off.
34460 - Clients no longer download descriptors for non-running
34462 - Before we add new directory authorities, we should make it
34463 clear that only v1 authorities should receive/publish hidden
34464 service descriptors.
34467 - As soon as we've fetched some more directory info, immediately
34468 try to download more server descriptors. This way we don't have
34469 a 10 second pause during initial bootstrapping.
34470 - Remove even more loud log messages that the server operator can't
34472 - When we're running an obsolete or un-recommended version, make
34473 the log message more clear about what the problem is and what
34474 versions *are* still recommended.
34475 - Provide a more useful warn message when our onion queue gets full:
34476 the CPU is too slow or the exit policy is too liberal.
34477 - Don't warn when we receive a 503 from a dirserver/cache -- this
34478 will pave the way for them being able to refuse if they're busy.
34479 - When we fail to bind a listener, try to provide a more useful
34480 log message: e.g., "Is Tor already running?"
34481 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
34482 Goldberg can prove things about our handshake protocol more
34484 - MaxConn has been obsolete for a while now. Document the ConnLimit
34485 config option, which is a *minimum* number of file descriptors
34486 that must be available else Tor refuses to start.
34487 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
34488 if you log to syslog and want something other than LOG_DAEMON.
34489 - Make dirservers generate a separate "guard" flag to mean,
34490 "would make a good entry guard". Make clients parse it and vote
34491 on it. Not used by clients yet.
34492 - Implement --with-libevent-dir option to ./configure. Also, improve
34493 search techniques to find libevent, and use those for openssl too.
34494 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
34495 - Only start testing reachability once we've established a
34496 circuit. This will make startup on dirservers less noisy.
34497 - Don't try to upload hidden service descriptors until we have
34498 established a circuit.
34499 - Fix the controller's "attachstream 0" command to treat conn like
34500 it just connected, doing address remapping, handling .exit and
34501 .onion idioms, and so on. Now we're more uniform in making sure
34502 that the controller hears about new and closing connections.
34505 Changes in version 0.1.1.12-alpha - 2006-01-11
34506 o Bugfixes on 0.1.1.x:
34507 - The fix to close duplicate server connections was closing all
34508 Tor client connections if they didn't establish a circuit
34509 quickly enough. Oops.
34510 - Fix minor memory issue (double-free) that happened on exit.
34512 o Bugfixes on 0.1.0.x:
34513 - Tor didn't warn when it failed to open a log file.
34516 Changes in version 0.1.1.11-alpha - 2006-01-10
34517 o Crashes in 0.1.1.x:
34518 - Include all the assert/crash fixes from 0.1.0.16.
34519 - If you start Tor and then quit very quickly, there were some
34520 races that tried to free things that weren't allocated yet.
34521 - Fix a rare memory stomp if you're running hidden services.
34522 - Fix segfault when specifying DirServer in config without nickname.
34523 - Fix a seg fault when you finish connecting to a server but at
34524 that moment you dump his server descriptor.
34525 - Extendcircuit and Attachstream controller commands would
34526 assert/crash if you don't give them enough arguments.
34527 - Fix an assert error when we're out of space in the connection_list
34528 and we try to post a hidden service descriptor (reported by weasel).
34529 - If you specify a relative torrc path and you set RunAsDaemon in
34530 your torrc, then it chdir()'s to the new directory. If you HUP,
34531 it tries to load the new torrc location, fails, and exits.
34532 The fix: no longer allow a relative path to torrc using -f.
34535 - Implement "entry guards": automatically choose a handful of entry
34536 nodes and stick with them for all circuits. Only pick new guards
34537 when the ones you have are unsuitable, and if the old guards
34538 become suitable again, switch back. This will increase security
34539 dramatically against certain end-point attacks. The EntryNodes
34540 config option now provides some hints about which entry guards you
34541 want to use most; and StrictEntryNodes means to only use those.
34542 - New directory logic: download by descriptor digest, not by
34543 fingerprint. Caches try to download all listed digests from
34544 authorities; clients try to download "best" digests from caches.
34545 This avoids partitioning and isolating attacks better.
34546 - Make the "stable" router flag in network-status be the median of
34547 the uptimes of running valid servers, and make clients pay
34548 attention to the network-status flags. Thus the cutoff adapts
34549 to the stability of the network as a whole, making IRC, IM, etc
34550 connections more reliable.
34553 - Tor servers with dynamic IP addresses were needing to wait 18
34554 hours before they could start doing reachability testing using
34555 the new IP address and ports. This is because they were using
34556 the internal descriptor to learn what to test, yet they were only
34557 rebuilding the descriptor once they decided they were reachable.
34558 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
34559 to download certain server descriptors, throw them away, and then
34560 fetch them again after 30 minutes. Now mirrors throw away these
34561 server descriptors so clients can't get them.
34562 - We were leaving duplicate connections to other ORs open for a week,
34563 rather than closing them once we detect a duplicate. This only
34564 really affected authdirservers, but it affected them a lot.
34565 - Spread the authdirservers' reachability testing over the entire
34566 testing interval, so we don't try to do 500 TLS's at once every
34570 - If the network is down, and we try to connect to a conn because
34571 we have a circuit in mind, and we timeout (30 seconds) because the
34572 network never answers, we were expiring the circuit, but we weren't
34573 obsoleting the connection or telling the entry_guards functions.
34574 - Some Tor servers process billions of cells per day. These statistics
34575 need to be uint64_t's.
34576 - Check for integer overflows in more places, when adding elements
34577 to smartlists. This could possibly prevent a buffer overflow
34578 on malicious huge inputs. I don't see any, but I haven't looked
34580 - ReachableAddresses kept growing new "reject *:*" lines on every
34582 - When you "setconf log" via the controller, it should remove all
34583 logs. We were automatically adding back in a "log notice stdout".
34584 - Newly bootstrapped Tor networks couldn't establish hidden service
34585 circuits until they had nodes with high uptime. Be more tolerant.
34586 - We were marking servers down when they could not answer every piece
34587 of the directory request we sent them. This was far too harsh.
34588 - Fix the torify (tsocks) config file to not use Tor for localhost
34590 - Directory authorities now go to the proper authority when asking for
34591 a networkstatus, even when they want a compressed one.
34592 - Fix a harmless bug that was causing Tor servers to log
34593 "Got an end because of misc error, but we're not an AP. Closing."
34594 - Authorities were treating their own descriptor changes as cosmetic,
34595 meaning the descriptor available in the network-status and the
34596 descriptor that clients downloaded were different.
34597 - The OS X installer was adding a symlink for tor_resolve but
34598 the binary was called tor-resolve (reported by Thomas Hardly).
34599 - Workaround a problem with some http proxies where they refuse GET
34600 requests that specify "Content-Length: 0" (reported by Adrian).
34601 - Fix wrong log message when you add a "HiddenServiceNodes" config
34602 line without any HiddenServiceDir line (reported by Chris Thomas).
34605 - Write the TorVersion into the state file so we have a prayer of
34606 keeping forward and backward compatibility.
34607 - Revive the FascistFirewall config option rather than eliminating it:
34608 now it's a synonym for ReachableAddresses *:80,*:443.
34609 - Clients choose directory servers from the network status lists,
34610 not from their internal list of router descriptors. Now they can
34611 go to caches directly rather than needing to go to authorities
34613 - Directory authorities ignore router descriptors that have only
34614 cosmetic differences: do this for 0.1.0.x servers now too.
34615 - Add a new flag to network-status indicating whether the server
34616 can answer v2 directory requests too.
34617 - Authdirs now stop whining so loudly about bad descriptors that
34618 they fetch from other dirservers. So when there's a log complaint,
34619 it's for sure from a freshly uploaded descriptor.
34620 - Reduce memory requirements in our structs by changing the order
34622 - There used to be two ways to specify your listening ports in a
34623 server descriptor: on the "router" line and with a separate "ports"
34624 line. Remove support for the "ports" line.
34625 - New config option "AuthDirRejectUnlisted" for auth dirservers as
34626 a panic button: if we get flooded with unusable servers we can
34627 revert to only listing servers in the approved-routers file.
34628 - Auth dir servers can now mark a fingerprint as "!reject" or
34629 "!invalid" in the approved-routers file (as its nickname), to
34630 refuse descriptors outright or include them but marked as invalid.
34631 - Servers store bandwidth history across restarts/crashes.
34632 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
34633 get a better idea of why their circuits failed. Not used yet.
34634 - Directory mirrors now cache up to 16 unrecognized network-status
34635 docs. Now we can add new authdirservers and they'll be cached too.
34636 - When picking a random directory, prefer non-authorities if any
34638 - New controller option "getinfo desc/all-recent" to fetch the
34639 latest server descriptor for every router that Tor knows about.
34642 Changes in version 0.1.0.16 - 2006-01-02
34643 o Crash bugfixes on 0.1.0.x:
34644 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
34645 corrupting the heap, losing FDs, or crashing when we need to resize
34646 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
34647 - It turns out sparc64 platforms crash on unaligned memory access
34648 too -- so detect and avoid this.
34649 - Handle truncated compressed data correctly (by detecting it and
34651 - Fix possible-but-unlikely free(NULL) in control.c.
34652 - When we were closing connections, there was a rare case that
34653 stomped on memory, triggering seg faults and asserts.
34654 - Avoid potential infinite recursion when building a descriptor. (We
34655 don't know that it ever happened, but better to fix it anyway.)
34656 - We were neglecting to unlink marked circuits from soon-to-close OR
34657 connections, which caused some rare scribbling on freed memory.
34658 - Fix a memory stomping race bug when closing the joining point of two
34659 rendezvous circuits.
34660 - Fix an assert in time parsing found by Steven Murdoch.
34662 o Other bugfixes on 0.1.0.x:
34663 - When we're doing reachability testing, provide more useful log
34664 messages so the operator knows what to expect.
34665 - Do not check whether DirPort is reachable when we are suppressing
34666 advertising it because of hibernation.
34667 - When building with -static or on Solaris, we sometimes needed -ldl.
34668 - When we're deciding whether a stream has enough circuits around
34669 that can handle it, count the freshly dirty ones and not the ones
34670 that are so dirty they won't be able to handle it.
34671 - When we're expiring old circuits, we had a logic error that caused
34672 us to close new rendezvous circuits rather than old ones.
34673 - Give a more helpful log message when you try to change ORPort via
34674 the controller: you should upgrade Tor if you want that to work.
34675 - We were failing to parse Tor versions that start with "Tor ".
34676 - Tolerate faulty streams better: when a stream fails for reason
34677 exitpolicy, stop assuming that the router is lying about his exit
34678 policy. When a stream fails for reason misc, allow it to retry just
34679 as if it was resolvefailed. When a stream has failed three times,
34680 reset its failure count so we can try again and get all three tries.
34683 Changes in version 0.1.1.10-alpha - 2005-12-11
34684 o Correctness bugfixes on 0.1.0.x:
34685 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
34686 corrupting the heap, losing FDs, or crashing when we need to resize
34687 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
34688 - Stop doing the complex voodoo overkill checking for insecure
34689 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
34690 - When we were closing connections, there was a rare case that
34691 stomped on memory, triggering seg faults and asserts.
34692 - We were neglecting to unlink marked circuits from soon-to-close OR
34693 connections, which caused some rare scribbling on freed memory.
34694 - When we're deciding whether a stream has enough circuits around
34695 that can handle it, count the freshly dirty ones and not the ones
34696 that are so dirty they won't be able to handle it.
34697 - Recover better from TCP connections to Tor servers that are
34698 broken but don't tell you (it happens!); and rotate TLS
34699 connections once a week.
34700 - When we're expiring old circuits, we had a logic error that caused
34701 us to close new rendezvous circuits rather than old ones.
34702 - Fix a scary-looking but apparently harmless bug where circuits
34703 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
34704 servers, and never switch to state CIRCUIT_STATE_OPEN.
34705 - When building with -static or on Solaris, we sometimes needed to
34707 - Give a useful message when people run Tor as the wrong user,
34708 rather than telling them to start chowning random directories.
34709 - We were failing to inform the controller about new .onion streams.
34711 o Security bugfixes on 0.1.0.x:
34712 - Refuse server descriptors if the fingerprint line doesn't match
34713 the included identity key. Tor doesn't care, but other apps (and
34714 humans) might actually be trusting the fingerprint line.
34715 - We used to kill the circuit when we receive a relay command we
34716 don't recognize. Now we just drop it.
34717 - Start obeying our firewall options more rigorously:
34718 . If we can't get to a dirserver directly, try going via Tor.
34719 . Don't ever try to connect (as a client) to a place our
34720 firewall options forbid.
34721 . If we specify a proxy and also firewall options, obey the
34722 firewall options even when we're using the proxy: some proxies
34723 can only proxy to certain destinations.
34724 - Fix a bug found by Lasse Overlier: when we were making internal
34725 circuits (intended to be cannibalized later for rendezvous and
34726 introduction circuits), we were picking them so that they had
34727 useful exit nodes. There was no need for this, and it actually
34728 aids some statistical attacks.
34729 - Start treating internal circuits and exit circuits separately.
34730 It's important to keep them separate because internal circuits
34731 have their last hops picked like middle hops, rather than like
34732 exit hops. So exiting on them will break the user's expectations.
34734 o Bugfixes on 0.1.1.x:
34735 - Take out the mis-feature where we tried to detect IP address
34736 flapping for people with DynDNS, and chose not to upload a new
34737 server descriptor sometimes.
34738 - Try to be compatible with OpenSSL 0.9.6 again.
34739 - Log fix: when the controller is logging about .onion addresses,
34740 sometimes it didn't include the ".onion" part of the address.
34741 - Don't try to modify options->DirServers internally -- if the
34742 user didn't specify any, just add the default ones directly to
34743 the trusted dirserver list. This fixes a bug where people running
34744 controllers would use SETCONF on some totally unrelated config
34745 option, and Tor would start yelling at them about changing their
34747 - Let the controller's redirectstream command specify a port, in
34748 case the controller wants to change that too.
34749 - When we requested a pile of server descriptors, we sometimes
34750 accidentally launched a duplicate request for the first one.
34751 - Bugfix for trackhostexits: write down the fingerprint of the
34752 chosen exit, not its nickname, because the chosen exit might not
34754 - When parsing foo.exit, if foo is unknown, and we are leaving
34755 circuits unattached, set the chosen_exit field and leave the
34756 address empty. This matters because controllers got confused
34758 - Directory authorities no longer try to download server
34759 descriptors that they know they will reject.
34761 o Features and updates:
34762 - Replace balanced trees with hash tables: this should make stuff
34763 significantly faster.
34764 - Resume using the AES counter-mode implementation that we ship,
34765 rather than OpenSSL's. Ours is significantly faster.
34766 - Many other CPU and memory improvements.
34767 - Add a new config option FastFirstHopPK (on by default) so clients
34768 do a trivial crypto handshake for their first hop, since TLS has
34769 already taken care of confidentiality and authentication.
34770 - Add a new config option TestSocks so people can see if their
34771 applications are using socks4, socks4a, socks5-with-ip, or
34772 socks5-with-hostname. This way they don't have to keep mucking
34773 with tcpdump and wondering if something got cached somewhere.
34774 - Warn when listening on a public address for socks. I suspect a
34775 lot of people are setting themselves up as open socks proxies,
34776 and they have no idea that jerks on the Internet are using them,
34777 since they simply proxy the traffic into the Tor network.
34778 - Add "private:*" as an alias in configuration for policies. Now
34779 you can simplify your exit policy rather than needing to list
34780 every single internal or nonroutable network space.
34781 - Add a new controller event type that allows controllers to get
34782 all server descriptors that were uploaded to a router in its role
34783 as authoritative dirserver.
34784 - Start shipping socks-extensions.txt, tor-doc-unix.html,
34785 tor-doc-server.html, and stylesheet.css in the tarball.
34786 - Stop shipping tor-doc.html in the tarball.
34789 Changes in version 0.1.1.9-alpha - 2005-11-15
34790 o Usability improvements:
34791 - Start calling it FooListenAddress rather than FooBindAddress,
34792 since few of our users know what it means to bind an address
34794 - Reduce clutter in server logs. We're going to try to make
34795 them actually usable now. New config option ProtocolWarnings that
34796 lets you hear about how _other Tors_ are breaking the protocol. Off
34798 - Divide log messages into logging domains. Once we put some sort
34799 of interface on this, it will let people looking at more verbose
34800 log levels specify the topics they want to hear more about.
34801 - Make directory servers return better http 404 error messages
34802 instead of a generic "Servers unavailable".
34803 - Check for even more Windows version flags when writing the platform
34804 string in server descriptors, and note any we don't recognize.
34805 - Clean up more of the OpenSSL memory when exiting, so we can detect
34806 memory leaks better.
34807 - Make directory authorities be non-versioning, non-naming by
34808 default. Now we can add new directory servers without requiring
34809 their operators to pay close attention.
34810 - When logging via syslog, include the pid whenever we provide
34811 a log entry. Suggested by Todd Fries.
34813 o Performance improvements:
34814 - Directory servers now silently throw away new descriptors that
34815 haven't changed much if the timestamps are similar. We do this to
34816 tolerate older Tor servers that upload a new descriptor every 15
34817 minutes. (It seemed like a good idea at the time.)
34818 - Inline bottleneck smartlist functions; use fast versions by default.
34819 - Add a "Map from digest to void*" abstraction digestmap_t so we
34820 can do less hex encoding/decoding. Use it in router_get_by_digest()
34821 to resolve a performance bottleneck.
34822 - Allow tor_gzip_uncompress to extract as much as possible from
34823 truncated compressed data. Try to extract as many
34824 descriptors as possible from truncated http responses (when
34825 DIR_PURPOSE_FETCH_ROUTERDESC).
34826 - Make circ->onionskin a pointer, not a static array. moria2 was using
34827 125000 circuit_t's after it had been up for a few weeks, which
34828 translates to 20+ megs of wasted space.
34829 - The private half of our EDH handshake keys are now chosen out
34830 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
34832 o Security improvements:
34833 - Start making directory caches retain old routerinfos, so soon
34834 clients can start asking by digest of descriptor rather than by
34835 fingerprint of server.
34836 - Add half our entropy from RAND_poll in OpenSSL. This knows how
34837 to use egd (if present), openbsd weirdness (if present), vms/os2
34838 weirdness (if we ever port there), and more in the future.
34840 o Bugfixes on 0.1.0.x:
34841 - Do round-robin writes of at most 16 kB per write. This might be
34842 more fair on loaded Tor servers, and it might resolve our Windows
34843 crash bug. It might also slow things down.
34844 - Our TLS handshakes were generating a single public/private
34845 keypair for the TLS context, rather than making a new one for
34846 each new connections. Oops. (But we were still rotating them
34847 periodically, so it's not so bad.)
34848 - When we were cannibalizing a circuit with a particular exit
34849 node in mind, we weren't checking to see if that exit node was
34850 already present earlier in the circuit. Oops.
34851 - When a Tor server's IP changes (e.g. from a dyndns address),
34852 upload a new descriptor so clients will learn too.
34853 - Really busy servers were keeping enough circuits open on stable
34854 connections that they were wrapping around the circuit_id
34855 space. (It's only two bytes.) This exposed a bug where we would
34856 feel free to reuse a circuit_id even if it still exists but has
34857 been marked for close. Try to fix this bug. Some bug remains.
34858 - If we would close a stream early (e.g. it asks for a .exit that
34859 we know would refuse it) but the LeaveStreamsUnattached config
34860 option is set by the controller, then don't close it.
34862 o Bugfixes on 0.1.1.8-alpha:
34863 - Fix a big pile of memory leaks, some of them serious.
34864 - Do not try to download a routerdesc if we would immediately reject
34866 - Resume inserting a newline between all router descriptors when
34867 generating (old style) signed directories, since our spec says
34869 - When providing content-type application/octet-stream for
34870 server descriptors using .z, we were leaving out the
34871 content-encoding header. Oops. (Everything tolerated this just
34872 fine, but that doesn't mean we need to be part of the problem.)
34873 - Fix a potential seg fault in getconf and getinfo using version 1
34874 of the controller protocol.
34875 - Avoid crash: do not check whether DirPort is reachable when we
34876 are suppressing it because of hibernation.
34877 - Make --hash-password not crash on exit.
34880 Changes in version 0.1.1.8-alpha - 2005-10-07
34881 o New features (major):
34882 - Clients don't download or use the directory anymore. Now they
34883 download and use network-statuses from the trusted dirservers,
34884 and fetch individual server descriptors as needed from mirrors.
34885 See dir-spec.txt for all the gory details.
34886 - Be more conservative about whether to advertise our DirPort.
34887 The main change is to not advertise if we're running at capacity
34888 and either a) we could hibernate or b) our capacity is low and
34889 we're using a default DirPort.
34890 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
34892 o New features (minor):
34893 - Try to be smart about when to retry network-status and
34894 server-descriptor fetches. Still needs some tuning.
34895 - Stop parsing, storing, or using running-routers output (but
34896 mirrors still cache and serve it).
34897 - Consider a threshold of versioning dirservers (dirservers who have
34898 an opinion about which Tor versions are still recommended) before
34899 deciding whether to warn the user that he's obsolete.
34900 - Dirservers can now reject/invalidate by key and IP, with the
34901 config options "AuthDirInvalid" and "AuthDirReject". This is
34902 useful since currently we automatically list servers as running
34903 and usable even if we know they're jerks.
34904 - Provide dire warnings to any users who set DirServer; move it out
34905 of torrc.sample and into torrc.complete.
34906 - Add MyFamily to torrc.sample in the server section.
34907 - Add nicknames to the DirServer line, so we can refer to them
34908 without requiring all our users to memorize their IP addresses.
34909 - When we get an EOF or a timeout on a directory connection, note
34910 how many bytes of serverdesc we are dropping. This will help
34911 us determine whether it is smart to parse incomplete serverdesc
34913 - Add a new function to "change pseudonyms" -- that is, to stop
34914 using any currently-dirty circuits for new streams, so we don't
34915 link new actions to old actions. Currently it's only called on
34916 HUP (or SIGNAL RELOAD).
34917 - On sighup, if UseHelperNodes changed to 1, use new circuits.
34918 - Start using RAND_bytes rather than RAND_pseudo_bytes from
34919 OpenSSL. Also, reseed our entropy every hour, not just at
34920 startup. And entropy in 512-bit chunks, not 160-bit chunks.
34922 o Fixes on 0.1.1.7-alpha:
34923 - Nobody ever implemented EVENT_ADDRMAP for control protocol
34924 version 0, so don't let version 0 controllers ask for it.
34925 - If you requested something with too many newlines via the
34926 v1 controller protocol, you could crash tor.
34927 - Fix a number of memory leaks, including some pretty serious ones.
34928 - Re-enable DirPort testing again, so Tor servers will be willing
34929 to advertise their DirPort if it's reachable.
34930 - On TLS handshake, only check the other router's nickname against
34931 its expected nickname if is_named is set.
34933 o Fixes forward-ported from 0.1.0.15:
34934 - Don't crash when we don't have any spare file descriptors and we
34935 try to spawn a dns or cpu worker.
34936 - Make the numbers in read-history and write-history into uint64s,
34937 so they don't overflow and publish negatives in the descriptor.
34939 o Fixes on 0.1.0.x:
34940 - For the OS X package's modified privoxy config file, comment
34941 out the "logfile" line so we don't log everything passed
34943 - We were whining about using socks4 or socks5-with-local-lookup
34944 even when it's an IP in the "virtual" range we designed exactly
34946 - We were leaking some memory every time the client changes IPs.
34947 - Never call free() on tor_malloc()d memory. This will help us
34948 use dmalloc to detect memory leaks.
34949 - Check for named servers when looking them up by nickname;
34950 warn when we'recalling a non-named server by its nickname;
34951 don't warn twice about the same name.
34952 - Try to list MyFamily elements by key, not by nickname, and warn
34953 if we've not heard of the server.
34954 - Make windows platform detection (uname equivalent) smarter.
34955 - It turns out sparc64 doesn't like unaligned access either.
34958 Changes in version 0.1.0.15 - 2005-09-23
34959 o Bugfixes on 0.1.0.x:
34960 - Reject ports 465 and 587 (spam targets) in default exit policy.
34961 - Don't crash when we don't have any spare file descriptors and we
34962 try to spawn a dns or cpu worker.
34963 - Get rid of IgnoreVersion undocumented config option, and make us
34964 only warn, never exit, when we're running an obsolete version.
34965 - Don't try to print a null string when your server finds itself to
34966 be unreachable and the Address config option is empty.
34967 - Make the numbers in read-history and write-history into uint64s,
34968 so they don't overflow and publish negatives in the descriptor.
34969 - Fix a minor memory leak in smartlist_string_remove().
34970 - We were only allowing ourselves to upload a server descriptor at
34971 most every 20 minutes, even if it changed earlier than that.
34972 - Clean up log entries that pointed to old URLs.
34975 Changes in version 0.1.1.7-alpha - 2005-09-14
34976 o Fixes on 0.1.1.6-alpha:
34977 - Exit servers were crashing when people asked them to make a
34978 connection to an address not in their exit policy.
34979 - Looking up a non-existent stream for a v1 control connection would
34981 - Fix a seg fault if we ask a dirserver for a descriptor by
34982 fingerprint but he doesn't know about him.
34983 - SETCONF was appending items to linelists, not clearing them.
34984 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
34985 out and refuse the setconf if it would fail.
34986 - Downgrade the dirserver log messages when whining about
34990 - Add Peter Palfrader's check-tor script to tor/contrib/
34991 It lets you easily check whether a given server (referenced by
34992 nickname) is reachable by you.
34993 - Numerous changes to move towards client-side v2 directories. Not
34996 o Fixes on 0.1.0.x:
34997 - If the user gave tor an odd number of command-line arguments,
34998 we were silently ignoring the last one. Now we complain and fail.
34999 [This wins the oldest-bug prize -- this bug has been present since
35000 November 2002, as released in Tor 0.0.0.]
35001 - Do not use unaligned memory access on alpha, mips, or mipsel.
35002 It *works*, but is very slow, so we treat them as if it doesn't.
35003 - Retry directory requests if we fail to get an answer we like
35004 from a given dirserver (we were retrying before, but only if
35005 we fail to connect).
35006 - When writing the RecommendedVersions line, sort them first.
35007 - When the client asked for a rendezvous port that the hidden
35008 service didn't want to provide, we were sending an IP address
35009 back along with the end cell. Fortunately, it was zero. But stop
35011 - Correct "your server is reachable" log entries to indicate that
35012 it was self-testing that told us so.
35015 Changes in version 0.1.1.6-alpha - 2005-09-09
35016 o Fixes on 0.1.1.5-alpha:
35017 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
35018 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
35019 - Fix bug with tor_memmem finding a match at the end of the string.
35020 - Make unit tests run without segfaulting.
35021 - Resolve some solaris x86 compile warnings.
35022 - Handle duplicate lines in approved-routers files without warning.
35023 - Fix bug where as soon as a server refused any requests due to his
35024 exit policy (e.g. when we ask for localhost and he tells us that's
35025 127.0.0.1 and he won't do it), we decided he wasn't obeying his
35026 exit policy using him for any exits.
35027 - Only do openssl hardware accelerator stuff if openssl version is
35030 o New controller features/fixes:
35031 - Add a "RESETCONF" command so you can set config options like
35032 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
35033 a config option in the torrc with no value, then it clears it
35034 entirely (rather than setting it to its default).
35035 - Add a "GETINFO config-file" to tell us where torrc is.
35036 - Avoid sending blank lines when GETINFO replies should be empty.
35037 - Add a QUIT command for the controller (for using it manually).
35038 - Fix a bug in SAVECONF that was adding default dirservers and
35039 other redundant entries to the torrc file.
35041 o Start on the new directory design:
35042 - Generate, publish, cache, serve new network-status format.
35043 - Publish individual descriptors (by fingerprint, by "all", and by
35045 - Publish client and server recommended versions separately.
35046 - Allow tor_gzip_uncompress() to handle multiple concatenated
35047 compressed strings. Serve compressed groups of router
35048 descriptors. The compression logic here could be more
35050 - Distinguish v1 authorities (all currently trusted directories)
35051 from v2 authorities (all trusted directories).
35052 - Change DirServers config line to note which dirs are v1 authorities.
35053 - Add configuration option "V1AuthoritativeDirectory 1" which
35054 moria1, moria2, and tor26 should set.
35055 - Remove option when getting directory cache to see whether they
35056 support running-routers; they all do now. Replace it with one
35057 to see whether caches support v2 stuff.
35060 - Dirservers now do their own external reachability testing of each
35061 Tor server, and only list them as running if they've been found to
35062 be reachable. We also send back warnings to the server's logs if
35063 it uploads a descriptor that we already believe is unreachable.
35064 - Implement exit enclaves: if we know an IP address for the
35065 destination, and there's a running Tor server at that address
35066 which allows exit to the destination, then extend the circuit to
35067 that exit first. This provides end-to-end encryption and end-to-end
35068 authentication. Also, if the user wants a .exit address or enclave,
35069 use 4 hops rather than 3, and cannibalize a general circ for it
35071 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
35072 controller. Also, rotate dns and cpu workers if the controller
35073 changes options that will affect them; and initialize the dns
35074 worker cache tree whether or not we start out as a server.
35075 - Only upload a new server descriptor when options change, 18
35076 hours have passed, uptime is reset, or bandwidth changes a lot.
35077 - Check [X-]Forwarded-For headers in HTTP requests when generating
35078 log messages. This lets people run dirservers (and caches) behind
35079 Apache but still know which IP addresses are causing warnings.
35081 o Config option changes:
35082 - Replace (Fascist)Firewall* config options with a new
35083 ReachableAddresses option that understands address policies.
35084 For example, "ReachableAddresses *:80,*:443"
35085 - Get rid of IgnoreVersion undocumented config option, and make us
35086 only warn, never exit, when we're running an obsolete version.
35087 - Make MonthlyAccountingStart config option truly obsolete now.
35089 o Fixes on 0.1.0.x:
35090 - Reject ports 465 and 587 in the default exit policy, since
35091 people have started using them for spam too.
35092 - It turns out we couldn't bootstrap a network since we added
35093 reachability detection in 0.1.0.1-rc. Good thing the Tor network
35094 has never gone down. Add an AssumeReachable config option to let
35095 servers and dirservers bootstrap. When we're trying to build a
35096 high-uptime or high-bandwidth circuit but there aren't enough
35097 suitable servers, try being less picky rather than simply failing.
35098 - Our logic to decide if the OR we connected to was the right guy
35099 was brittle and maybe open to a mitm for unverified routers.
35100 - We weren't cannibalizing circuits correctly for
35101 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
35102 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
35103 build those from scratch. This should make hidden services faster.
35104 - Predict required circuits better, with an eye toward making hidden
35105 services faster on the service end.
35106 - Retry streams if the exit node sends back a 'misc' failure. This
35107 should result in fewer random failures. Also, after failing
35108 from resolve failed or misc, reset the num failures, so we give
35109 it a fair shake next time we try.
35110 - Clean up the rendezvous warn log msgs, and downgrade some to info.
35111 - Reduce severity on logs about dns worker spawning and culling.
35112 - When we're shutting down and we do something like try to post a
35113 server descriptor or rendezvous descriptor, don't complain that
35114 we seem to be unreachable. Of course we are, we're shutting down.
35115 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
35116 We don't use them yet, but maybe one day our DNS resolver will be
35117 able to discover them.
35118 - Make ContactInfo mandatory for authoritative directory servers.
35119 - Require server descriptors to list IPv4 addresses -- hostnames
35120 are no longer allowed. This also fixes some potential security
35121 problems with people providing hostnames as their address and then
35122 preferentially resolving them to partition users.
35123 - Change log line for unreachability to explicitly suggest /etc/hosts
35124 as the culprit. Also make it clearer what IP address and ports we're
35125 testing for reachability.
35126 - Put quotes around user-supplied strings when logging so users are
35127 more likely to realize if they add bad characters (like quotes)
35129 - Let auth dir servers start without specifying an Address config
35131 - Make unit tests (and other invocations that aren't the real Tor)
35132 run without launching listeners, creating subdirectories, and so on.
35135 Changes in version 0.1.1.5-alpha - 2005-08-08
35136 o Bugfixes included in 0.1.0.14.
35138 o Bugfixes on 0.1.0.x:
35139 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
35140 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
35141 it would silently using ignore the 6668.
35144 Changes in version 0.1.0.14 - 2005-08-08
35145 o Bugfixes on 0.1.0.x:
35146 - Fix the other half of the bug with crypto handshakes
35148 - Fix an assert trigger if you send a 'signal term' via the
35149 controller when it's listening for 'event info' messages.
35152 Changes in version 0.1.1.4-alpha - 2005-08-04
35153 o Bugfixes included in 0.1.0.13.
35156 - Improve tor_gettimeofday() granularity on windows.
35157 - Make clients regenerate their keys when their IP address changes.
35158 - Implement some more GETINFO goodness: expose helper nodes, config
35159 options, getinfo keys.
35162 Changes in version 0.1.0.13 - 2005-08-04
35163 o Bugfixes on 0.1.0.x:
35164 - Fix a critical bug in the security of our crypto handshakes.
35165 - Fix a size_t underflow in smartlist_join_strings2() that made
35166 it do bad things when you hand it an empty smartlist.
35167 - Fix Windows installer to ship Tor license (thanks to Aphex for
35168 pointing out this oversight) and put a link to the doc directory
35170 - Explicitly set no-unaligned-access for sparc: it turns out the
35171 new gcc's let you compile broken code, but that doesn't make it
35175 Changes in version 0.1.1.3-alpha - 2005-07-23
35176 o Bugfixes on 0.1.1.2-alpha:
35177 - Fix a bug in handling the controller's "post descriptor"
35179 - Fix several bugs in handling the controller's "extend circuit"
35181 - Fix a bug in handling the controller's "stream status" event.
35182 - Fix an assert failure if we have a controller listening for
35183 circuit events and we go offline.
35184 - Re-allow hidden service descriptors to publish 0 intro points.
35185 - Fix a crash when generating your hidden service descriptor if
35186 you don't have enough intro points already.
35188 o New features on 0.1.1.2-alpha:
35189 - New controller function "getinfo accounting", to ask how
35190 many bytes we've used in this time period.
35191 - Experimental support for helper nodes: a lot of the risk from
35192 a small static adversary comes because users pick new random
35193 nodes every time they rebuild a circuit. Now users will try to
35194 stick to the same small set of entry nodes if they can. Not
35195 enabled by default yet.
35197 o Bugfixes on 0.1.0.12:
35198 - If you're an auth dir server, always publish your dirport,
35199 even if you haven't yet found yourself to be reachable.
35200 - Fix a size_t underflow in smartlist_join_strings2() that made
35201 it do bad things when you hand it an empty smartlist.
35204 Changes in version 0.1.0.12 - 2005-07-18
35205 o New directory servers:
35206 - tor26 has changed IP address.
35208 o Bugfixes on 0.1.0.x:
35209 - Fix a possible double-free in tor_gzip_uncompress().
35210 - When --disable-threads is set, do not search for or link against
35211 pthreads libraries.
35212 - Don't trigger an assert if an authoritative directory server
35213 claims its dirport is 0.
35214 - Fix bug with removing Tor as an NT service: some people were
35215 getting "The service did not return an error." Thanks to Matt
35219 Changes in version 0.1.1.2-alpha - 2005-07-15
35220 o New directory servers:
35221 - tor26 has changed IP address.
35223 o Bugfixes on 0.1.0.x, crashes/leaks:
35224 - Port the servers-not-obeying-their-exit-policies fix from
35226 - Fix an fd leak in start_daemon().
35227 - On Windows, you can't always reopen a port right after you've
35228 closed it. So change retry_listeners() to only close and re-open
35229 ports that have changed.
35230 - Fix a possible double-free in tor_gzip_uncompress().
35232 o Bugfixes on 0.1.0.x, usability:
35233 - When tor_socketpair() fails in Windows, give a reasonable
35234 Windows-style errno back.
35235 - Let people type "tor --install" as well as "tor -install" when
35237 want to make it an NT service.
35238 - NT service patch from Matt Edman to improve error messages.
35239 - When the controller asks for a config option with an abbreviated
35240 name, give the full name in our response.
35241 - Correct the man page entry on TrackHostExitsExpire.
35242 - Looks like we were never delivering deflated (i.e. compressed)
35243 running-routers lists, even when asked. Oops.
35244 - When --disable-threads is set, do not search for or link against
35245 pthreads libraries.
35247 o Bugfixes on 0.1.1.x:
35248 - Fix a seg fault with autodetecting which controller version is
35252 - New hidden service descriptor format: put a version in it, and
35253 let people specify introduction/rendezvous points that aren't
35254 in "the directory" (which is subjective anyway).
35255 - Allow the DEBUG controller event to work again. Mark certain log
35256 entries as "don't tell this to controllers", so we avoid cycles.
35259 Changes in version 0.1.0.11 - 2005-06-30
35260 o Bugfixes on 0.1.0.x:
35261 - Fix major security bug: servers were disregarding their
35262 exit policies if clients behaved unexpectedly.
35263 - Make OS X init script check for missing argument, so we don't
35264 confuse users who invoke it incorrectly.
35265 - Fix a seg fault in "tor --hash-password foo".
35266 - The MAPADDRESS control command was broken.
35269 Changes in version 0.1.1.1-alpha - 2005-06-29
35271 - Make OS X init script check for missing argument, so we don't
35272 confuse users who invoke it incorrectly.
35273 - Fix a seg fault in "tor --hash-password foo".
35274 - Fix a possible way to DoS dirservers.
35275 - When we complain that your exit policy implicitly allows local or
35276 private address spaces, name them explicitly so operators can
35278 - Make the log message less scary when all the dirservers are
35279 temporarily unreachable.
35280 - We were printing the number of idle dns workers incorrectly when
35284 - Revised controller protocol (version 1) that uses ascii rather
35285 than binary. Add supporting libraries in python and java so you
35286 can use the controller from your applications without caring how
35287 our protocol works.
35288 - Spiffy new support for crypto hardware accelerators. Can somebody
35292 Changes in version 0.0.9.10 - 2005-06-16
35293 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
35294 - Refuse relay cells that claim to have a length larger than the
35295 maximum allowed. This prevents a potential attack that could read
35296 arbitrary memory (e.g. keys) from an exit server's process
35300 Changes in version 0.1.0.10 - 2005-06-14
35301 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
35302 libevent before 1.1a.
35305 Changes in version 0.1.0.9-rc - 2005-06-09
35307 - Reset buf->highwater every time buf_shrink() is called, not just on
35308 a successful shrink. This was causing significant memory bloat.
35309 - Fix buffer overflow when checking hashed passwords.
35310 - Security fix: if seeding the RNG on Win32 fails, quit.
35311 - Allow seeding the RNG on Win32 even when you're not running as
35313 - Disable threading on Solaris too. Something is wonky with it,
35314 cpuworkers, and reentrant libs.
35315 - Reenable the part of the code that tries to flush as soon as an
35316 OR outbuf has a full TLS record available. Perhaps this will make
35317 OR outbufs not grow as huge except in rare cases, thus saving lots
35318 of CPU time plus memory.
35319 - Reject malformed .onion addresses rather then passing them on as
35320 normal web requests.
35321 - Adapt patch from Adam Langley: fix possible memory leak in
35322 tor_lookup_hostname().
35323 - Initialize libevent later in the startup process, so the logs are
35324 already established by the time we start logging libevent warns.
35325 - Use correct errno on win32 if libevent fails.
35326 - Check and warn about known-bad/slow libevent versions.
35327 - Pay more attention to the ClientOnly config option.
35328 - Have torctl.in/tor.sh.in check for location of su binary (needed
35330 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
35331 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
35332 HttpProxyAuthenticator
35333 - Stop warning about sigpipes in the logs. We're going to
35334 pretend that getting these occasionally is normal and fine.
35335 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
35337 installer screens; and don't put stuff into StartupItems unless
35338 the user asks you to.
35339 - Require servers that use the default dirservers to have public IP
35340 addresses. We have too many servers that are configured with private
35341 IPs and their admins never notice the log entries complaining that
35342 their descriptors are being rejected.
35343 - Add OSX uninstall instructions. An actual uninstall script will
35347 Changes in version 0.1.0.8-rc - 2005-05-23
35349 - It turns out that kqueue on OS X 10.3.9 was causing kernel
35350 panics. Disable kqueue on all OS X Tors.
35351 - Fix RPM: remove duplicate line accidentally added to the rpm
35353 - Disable threads on openbsd too, since its gethostaddr is not
35355 - Tolerate libevent 0.8 since it still works, even though it's
35357 - Enable building on Red Hat 9.0 again.
35358 - Allow the middle hop of the testing circuit to be running any
35359 version, now that most of them have the bugfix to let them connect
35360 to unknown servers. This will allow reachability testing to work
35361 even when 0.0.9.7-0.0.9.9 become obsolete.
35362 - Handle relay cells with rh.length too large. This prevents
35363 a potential attack that could read arbitrary memory (maybe even
35364 keys) from the exit server's process.
35365 - We screwed up the dirport reachability testing when we don't yet
35366 have a cached version of the directory. Hopefully now fixed.
35367 - Clean up router_load_single_router() (used by the controller),
35368 so it doesn't seg fault on error.
35369 - Fix a minor memory leak when somebody establishes an introduction
35370 point at your Tor server.
35371 - If a socks connection ends because read fails, don't warn that
35372 you're not sending a socks reply back.
35375 - Add HttpProxyAuthenticator config option too, that works like
35376 the HttpsProxyAuthenticator config option.
35377 - Encode hashed controller passwords in hex instead of base64,
35378 to make it easier to write controllers.
35381 Changes in version 0.1.0.7-rc - 2005-05-17
35383 - Fix a bug in the OS X package installer that prevented it from
35384 installing on Tiger.
35385 - Fix a script bug in the OS X package installer that made it
35386 complain during installation.
35387 - Find libevent even if it's hiding in /usr/local/ and your
35388 CFLAGS and LDFLAGS don't tell you to look there.
35389 - Be able to link with libevent as a shared library (the default
35390 after 1.0d), even if it's hiding in /usr/local/lib and even
35391 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
35392 assuming you're running gcc. Otherwise fail and give a useful
35394 - Fix a bug in the RPM packager: set home directory for _tor to
35395 something more reasonable when first installing.
35396 - Free a minor amount of memory that is still reachable on exit.
35399 Changes in version 0.1.0.6-rc - 2005-05-14
35401 - Implement --disable-threads configure option. Disable threads on
35402 netbsd by default, because it appears to have no reentrant resolver
35404 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
35405 release (1.1) detects and disables kqueue if it's broken.
35406 - Append default exit policy before checking for implicit internal
35407 addresses. Now we don't log a bunch of complaints on startup
35408 when using the default exit policy.
35409 - Some people were putting "Address " in their torrc, and they had
35410 a buggy resolver that resolved " " to 0.0.0.0. Oops.
35411 - If DataDir is ~/.tor, and that expands to /.tor, then default to
35412 LOCALSTATEDIR/tor instead.
35413 - Fix fragmented-message bug in TorControl.py.
35414 - Resolve a minor bug which would prevent unreachable dirports
35415 from getting suppressed in the published descriptor.
35416 - When the controller gave us a new descriptor, we weren't resolving
35417 it immediately, so Tor would think its address was 0.0.0.0 until
35418 we fetched a new directory.
35419 - Fix an uppercase/lowercase case error in suppressing a bogus
35420 libevent warning on some Linuxes.
35423 - Begin scrubbing sensitive strings from logs by default. Turn off
35424 the config option SafeLogging if you need to do debugging.
35425 - Switch to a new buffer management algorithm, which tries to avoid
35426 reallocing and copying quite as much. In first tests it looks like
35427 it uses *more* memory on average, but less cpu.
35428 - First cut at support for "create-fast" cells. Clients can use
35429 these when extending to their first hop, since the TLS already
35430 provides forward secrecy and authentication. Not enabled on
35432 - When dirservers refuse a router descriptor, we now log its
35433 contactinfo, platform, and the poster's IP address.
35434 - Call tor_free_all instead of connections_free_all after forking, to
35435 save memory on systems that need to fork.
35436 - Whine at you if you're a server and you don't set your contactinfo.
35437 - Implement --verify-config command-line option to check if your torrc
35438 is valid without actually launching Tor.
35439 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
35440 rather than just rejecting it.
35443 Changes in version 0.1.0.5-rc - 2005-04-27
35445 - Stop trying to print a null pointer if an OR conn fails because
35446 we didn't like its cert.
35448 - Switch our internal buffers implementation to use a ring buffer,
35449 to hopefully improve performance for fast servers a lot.
35450 - Add HttpsProxyAuthenticator support (basic auth only), based
35451 on patch from Adam Langley.
35452 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
35453 the fast servers that have been joining lately.
35454 - Give hidden service accesses extra time on the first attempt,
35455 since 60 seconds is often only barely enough. This might improve
35457 - Improve performance for dirservers: stop re-parsing the whole
35458 directory every time you regenerate it.
35459 - Add more debugging info to help us find the weird dns freebsd
35460 pthreads bug; cleaner debug messages to help track future issues.
35463 Changes in version 0.0.9.9 - 2005-04-23
35464 o Bugfixes on 0.0.9.x:
35465 - If unofficial Tor clients connect and send weird TLS certs, our
35466 Tor server triggers an assert. This release contains a minimal
35467 backport from the broader fix that we put into 0.1.0.4-rc.
35470 Changes in version 0.1.0.4-rc - 2005-04-23
35472 - If unofficial Tor clients connect and send weird TLS certs, our
35473 Tor server triggers an assert. Stop asserting, and start handling
35474 TLS errors better in other situations too.
35475 - When the controller asks us to tell it about all the debug-level
35476 logs, it turns out we were generating debug-level logs while
35477 telling it about them, which turns into a bad loop. Now keep
35478 track of whether you're sending a debug log to the controller,
35479 and don't log when you are.
35480 - Fix the "postdescriptor" feature of the controller interface: on
35481 non-complete success, only say "done" once.
35483 - Clients are now willing to load balance over up to 2mB, not 1mB,
35484 of advertised bandwidth capacity.
35485 - Add a NoPublish config option, so you can be a server (e.g. for
35486 testing running Tor servers in other Tor networks) without
35487 publishing your descriptor to the primary dirservers.
35490 Changes in version 0.1.0.3-rc - 2005-04-08
35491 o Improvements on 0.1.0.2-rc:
35492 - Client now retries when streams end early for 'hibernating' or
35493 'resource limit' reasons, rather than failing them.
35494 - More automated handling for dirserver operators:
35495 - Automatically approve nodes running 0.1.0.2-rc or later,
35496 now that the the reachability detection stuff is working.
35497 - Now we allow two unverified servers with the same nickname
35498 but different keys. But if a nickname is verified, only that
35499 nickname+key are allowed.
35500 - If you're an authdirserver connecting to an address:port,
35501 and it's not the OR you were expecting, forget about that
35502 descriptor. If he *was* the one you were expecting, then forget
35503 about all other descriptors for that address:port.
35504 - Allow servers to publish descriptors from 12 hours in the future.
35505 Corollary: only whine about clock skew from the dirserver if
35506 he's a trusted dirserver (since now even verified servers could
35507 have quite wrong clocks).
35508 - Adjust maximum skew and age for rendezvous descriptors: let skew
35509 be 48 hours rather than 90 minutes.
35510 - Efficiency improvements:
35511 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
35512 it much faster to look up a circuit for each relay cell.
35513 - Remove most calls to assert_all_pending_dns_resolves_ok(),
35514 since they're eating our cpu on exit nodes.
35515 - Stop wasting time doing a case insensitive comparison for every
35516 dns name every time we do any lookup. Canonicalize the names to
35517 lowercase and be done with it.
35518 - Start sending 'truncated' cells back rather than destroy cells,
35519 if the circuit closes in front of you. This means we won't have
35520 to abandon partially built circuits.
35521 - Only warn once per nickname from add_nickname_list_to_smartlist
35522 per failure, so an entrynode or exitnode choice that's down won't
35524 - Put a note in the torrc about abuse potential with the default
35526 - Revise control spec and implementation to allow all log messages to
35527 be sent to controller with their severities intact (suggested by
35528 Matt Edman). Update TorControl to handle new log event types.
35529 - Provide better explanation messages when controller's POSTDESCRIPTOR
35531 - Stop putting nodename in the Platform string in server descriptors.
35532 It doesn't actually help, and it is confusing/upsetting some people.
35534 o Bugfixes on 0.1.0.2-rc:
35535 - We were printing the host mask wrong in exit policies in server
35536 descriptors. This isn't a critical bug though, since we were still
35537 obeying the exit policy internally.
35538 - Fix Tor when compiled with libevent but without pthreads: move
35539 connection_unregister() from _connection_free() to
35541 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
35542 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
35543 when we look through the connection array, we'll find any of the
35544 cpu/dnsworkers. This is no good.
35546 o Bugfixes on 0.0.9.8:
35547 - Fix possible bug on threading platforms (e.g. win32) which was
35548 leaking a file descriptor whenever a cpuworker or dnsworker died.
35549 - When using preferred entry or exit nodes, ignore whether the
35550 circuit wants uptime or capacity. They asked for the nodes, they
35552 - chdir() to your datadirectory at the *end* of the daemonize process,
35553 not the beginning. This was a problem because the first time you
35554 run tor, if your datadir isn't there, and you have runasdaemon set
35555 to 1, it will try to chdir to it before it tries to create it. Oops.
35556 - Handle changed router status correctly when dirserver reloads
35557 fingerprint file. We used to be dropping all unverified descriptors
35558 right then. The bug was hidden because we would immediately
35559 fetch a directory from another dirserver, which would include the
35560 descriptors we just dropped.
35561 - When we're connecting to an OR and he's got a different nickname/key
35562 than we were expecting, only complain loudly if we're an OP or a
35563 dirserver. Complaining loudly to the OR admins just confuses them.
35564 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
35565 artificially capped at 500kB.
35568 Changes in version 0.0.9.8 - 2005-04-07
35569 o Bugfixes on 0.0.9.x:
35570 - We have a bug that I haven't found yet. Sometimes, very rarely,
35571 cpuworkers get stuck in the 'busy' state, even though the cpuworker
35572 thinks of itself as idle. This meant that no new circuits ever got
35573 established. Here's a workaround to kill any cpuworker that's been
35574 busy for more than 100 seconds.
35577 Changes in version 0.1.0.2-rc - 2005-04-01
35578 o Bugfixes on 0.1.0.1-rc:
35579 - Fixes on reachability detection:
35580 - Don't check for reachability while hibernating.
35581 - If ORPort is reachable but DirPort isn't, still publish the
35582 descriptor, but zero out DirPort until it's found reachable.
35583 - When building testing circs for ORPort testing, use only
35584 high-bandwidth nodes, so fewer circuits fail.
35585 - Complain about unreachable ORPort separately from unreachable
35586 DirPort, so the user knows what's going on.
35587 - Make sure we only conclude ORPort reachability if we didn't
35588 initiate the conn. Otherwise we could falsely conclude that
35589 we're reachable just because we connected to the guy earlier
35590 and he used that same pipe to extend to us.
35591 - Authdirservers shouldn't do ORPort reachability detection,
35592 since they're in clique mode, so it will be rare to find a
35593 server not already connected to them.
35594 - When building testing circuits, always pick middle hops running
35595 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
35596 bug. (This is a kludge; it will go away when 0.0.9.x becomes
35598 - When we decide we're reachable, actually publish our descriptor
35600 - Fix bug in redirectstream in the controller.
35601 - Fix the state descriptor strings so logs don't claim edge streams
35602 are in a different state than they actually are.
35603 - Use recent libevent features when possible (this only really affects
35604 win32 and osx right now, because the new libevent with these
35605 features hasn't been released yet). Add code to suppress spurious
35607 - Prevent possible segfault in connection_close_unattached_ap().
35608 - Fix newlines on torrc in win32.
35609 - Improve error msgs when tor-resolve fails.
35611 o Improvements on 0.0.9.x:
35612 - New experimental script tor/contrib/ExerciseServer.py (needs more
35613 work) that uses the controller interface to build circuits and
35614 fetch pages over them. This will help us bootstrap servers that
35615 have lots of capacity but haven't noticed it yet.
35616 - New experimental script tor/contrib/PathDemo.py (needs more work)
35617 that uses the controller interface to let you choose whole paths
35619 "<hostname>.<path,separated by dots>.<length of path>.path"
35620 - When we've connected to an OR and handshaked but didn't like
35621 the result, we were closing the conn without sending destroy
35622 cells back for pending circuits. Now send those destroys.
35625 Changes in version 0.0.9.7 - 2005-04-01
35626 o Bugfixes on 0.0.9.x:
35627 - Fix another race crash bug (thanks to Glenn Fink for reporting).
35628 - Compare identity to identity, not to nickname, when extending to
35629 a router not already in the directory. This was preventing us from
35630 extending to unknown routers. Oops.
35631 - Make sure to create OS X Tor user in <500 range, so we aren't
35632 creating actual system users.
35633 - Note where connection-that-hasn't-sent-end was marked, and fix
35634 a few really loud instances of this harmless bug (it's fixed more
35638 Changes in version 0.1.0.1-rc - 2005-03-28
35640 - Add reachability testing. Your Tor server will automatically try
35641 to see if its ORPort and DirPort are reachable from the outside,
35642 and it won't upload its descriptor until it decides they are.
35643 - Handle unavailable hidden services better. Handle slow or busy
35644 hidden services better.
35645 - Add support for CONNECTing through https proxies, with "HttpsProxy"
35647 - New exit policy: accept most low-numbered ports, rather than
35648 rejecting most low-numbered ports.
35649 - More Tor controller support (still experimental). See
35650 http://tor.eff.org/doc/control-spec.txt for all the new features,
35651 including signals to emulate unix signals from any platform;
35652 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
35653 closestream; closecircuit; etc.
35654 - Make nt services work and start on startup on win32 (based on
35655 patch by Matt Edman).
35656 - Add a new AddressMap config directive to rewrite incoming socks
35657 addresses. This lets you, for example, declare an implicit
35658 required exit node for certain sites.
35659 - Add a new TrackHostExits config directive to trigger addressmaps
35660 for certain incoming socks addresses -- for sites that break when
35661 your exit keeps changing (based on patch by Mike Perry).
35662 - Redo the client-side dns cache so it's just an addressmap too.
35663 - Notice when our IP changes, and reset stats/uptime/reachability.
35664 - When an application is using socks5, give him the whole variety of
35665 potential socks5 responses (connect refused, host unreachable, etc),
35666 rather than just "success" or "failure".
35667 - A more sane version numbering system. See
35668 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
35669 - New contributed script "exitlist": a simple python script to
35670 parse directories and find Tor nodes that exit to listed
35672 - New contributed script "privoxy-tor-toggle" to toggle whether
35673 Privoxy uses Tor. Seems to be configured for Debian by default.
35674 - Report HTTP reasons to client when getting a response from directory
35675 servers -- so you can actually know what went wrong.
35676 - New config option MaxAdvertisedBandwidth which lets you advertise
35677 a low bandwidthrate (to not attract as many circuits) while still
35678 allowing a higher bandwidthrate in reality.
35680 o Robustness/stability fixes:
35681 - Make Tor use Niels Provos's libevent instead of its current
35682 poll-but-sometimes-select mess. This will let us use faster async
35683 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
35685 - pthread support now too. This was forced because when we forked,
35686 we ended up wasting a lot of duplicate ram over time. Also switch
35687 to foo_r versions of some library calls to allow reentry and
35689 - Better handling for heterogeneous / unreliable nodes:
35690 - Annotate circuits w/ whether they aim to contain high uptime nodes
35691 and/or high capacity nodes. When building circuits, choose
35693 - This means that every single node in an intro rend circuit,
35694 not just the last one, will have a minimum uptime.
35695 - New config option LongLivedPorts to indicate application streams
35696 that will want high uptime circuits.
35697 - Servers reset uptime when a dir fetch entirely fails. This
35698 hopefully reflects stability of the server's network connectivity.
35699 - If somebody starts his tor server in Jan 2004 and then fixes his
35700 clock, don't make his published uptime be a year.
35701 - Reset published uptime when you wake up from hibernation.
35702 - Introduce a notion of 'internal' circs, which are chosen without
35703 regard to the exit policy of the last hop. Intro and rendezvous
35704 circs must be internal circs, to avoid leaking information. Resolve
35705 and connect streams can use internal circs if they want.
35706 - New circuit pooling algorithm: make sure to have enough circs around
35707 to satisfy any predicted ports, and also make sure to have 2 internal
35708 circs around if we've required internal circs lately (and with high
35709 uptime if we've seen that lately too).
35710 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
35711 which describes how often we retry making new circuits if current
35712 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
35713 how long we're willing to make use of an already-dirty circuit.
35714 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
35715 circ as necessary, if there are any completed ones lying around
35716 when we try to launch one.
35717 - Make hidden services try to establish a rendezvous for 30 seconds,
35718 rather than for n (where n=3) attempts to build a circuit.
35719 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
35720 "ShutdownWaitLength".
35721 - Try to be more zealous about calling connection_edge_end when
35722 things go bad with edge conns in connection.c.
35723 - Revise tor-spec to add more/better stream end reasons.
35724 - Revise all calls to connection_edge_end to avoid sending "misc",
35725 and to take errno into account where possible.
35728 - Fix a race condition that can trigger an assert, when we have a
35729 pending create cell and an OR connection fails right then.
35730 - Fix several double-mark-for-close bugs, e.g. where we were finding
35731 a conn for a cell even if that conn is already marked for close.
35732 - Make sequence of log messages when starting on win32 with no config
35733 file more reasonable.
35734 - When choosing an exit node for a new non-internal circ, don't take
35735 into account whether it'll be useful for any pending x.onion
35736 addresses -- it won't.
35737 - Turn addr_policy_compare from a tristate to a quadstate; this should
35738 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
35739 for google.com" problem.
35740 - Make "platform" string in descriptor more accurate for Win32 servers,
35741 so it's not just "unknown platform".
35742 - Fix an edge case in parsing config options (thanks weasel).
35743 If they say "--" on the commandline, it's not an option.
35744 - Reject odd-looking addresses at the client (e.g. addresses that
35745 contain a colon), rather than having the server drop them because
35747 - tor-resolve requests were ignoring .exit if there was a working circuit
35748 they could use instead.
35749 - REUSEADDR on normal platforms means you can rebind to the port
35750 right after somebody else has let it go. But REUSEADDR on win32
35751 means to let you bind to the port _even when somebody else
35752 already has it bound_! So, don't do that on Win32.
35753 - Change version parsing logic: a version is "obsolete" if it is not
35754 recommended and (1) there is a newer recommended version in the
35755 same series, or (2) there are no recommended versions in the same
35756 series, but there are some recommended versions in a newer series.
35757 A version is "new" if it is newer than any recommended version in
35759 - Stop most cases of hanging up on a socks connection without sending
35763 - Require BandwidthRate to be at least 20kB/s for servers.
35764 - When a dirserver causes you to give a warn, mention which dirserver
35766 - New config option DirAllowPrivateAddresses for authdirservers.
35767 Now by default they refuse router descriptors that have non-IP or
35768 private-IP addresses.
35769 - Stop publishing socksport in the directory, since it's not
35770 actually meant to be public. For compatibility, publish a 0 there
35772 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
35773 smart" value, that is low for servers and high for clients.
35774 - If our clock jumps forward by 100 seconds or more, assume something
35775 has gone wrong with our network and abandon all not-yet-used circs.
35776 - Warn when exit policy implicitly allows local addresses.
35777 - If we get an incredibly skewed timestamp from a dirserver mirror
35778 that isn't a verified OR, don't warn -- it's probably him that's
35780 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
35781 cookies to disk and doesn't log each web request to disk. (Thanks
35782 to Brett Carrington for pointing this out.)
35783 - When a client asks us for a dir mirror and we don't have one,
35784 launch an attempt to get a fresh one.
35785 - If we're hibernating and we get a SIGINT, exit immediately.
35786 - Add --with-dmalloc ./configure option, to track memory leaks.
35787 - And try to free all memory on closing, so we can detect what
35789 - Cache local dns resolves correctly even when they're .exit
35791 - Give a better warning when some other server advertises an
35792 ORPort that is actually an apache running ssl.
35793 - Add "opt hibernating 1" to server descriptor to make it clearer
35794 whether the server is hibernating.
35797 Changes in version 0.0.9.6 - 2005-03-24
35798 o Bugfixes on 0.0.9.x (crashes and asserts):
35799 - Add new end stream reasons to maintenance branch. Fix bug where
35800 reason (8) could trigger an assert. Prevent bug from recurring.
35801 - Apparently win32 stat wants paths to not end with a slash.
35802 - Fix assert triggers in assert_cpath_layer_ok(), where we were
35803 blowing away the circuit that conn->cpath_layer points to, then
35804 checking to see if the circ is well-formed. Backport check to make
35805 sure we dont use the cpath on a closed connection.
35806 - Prevent circuit_resume_edge_reading_helper() from trying to package
35807 inbufs for marked-for-close streams.
35808 - Don't crash on hup if your options->address has become unresolvable.
35809 - Some systems (like OS X) sometimes accept() a connection and tell
35810 you the remote host is 0.0.0.0:0. If this happens, due to some
35811 other mis-features, we get confused; so refuse the conn for now.
35813 o Bugfixes on 0.0.9.x (other):
35814 - Fix harmless but scary "Unrecognized content encoding" warn message.
35815 - Add new stream error reason: TORPROTOCOL reason means "you are not
35816 speaking a version of Tor I understand; say bye-bye to your stream."
35817 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
35818 into the future, now that we are more tolerant of skew. This
35819 resolves a bug where a Tor server would refuse to cache a directory
35820 because all the directories it gets are too far in the future;
35821 yet the Tor server never logs any complaints about clock skew.
35822 - Mac packaging magic: make man pages useable, and do not overwrite
35823 existing torrc files.
35824 - Make OS X log happily to /var/log/tor/tor.log
35827 Changes in version 0.0.9.5 - 2005-02-22
35828 o Bugfixes on 0.0.9.x:
35829 - Fix an assert race at exit nodes when resolve requests fail.
35830 - Stop picking unverified dir mirrors--it only leads to misery.
35831 - Patch from Matt Edman to make NT services work better. Service
35832 support is still not compiled into the executable by default.
35833 - Patch from Dmitri Bely so the Tor service runs better under
35834 the win32 SYSTEM account.
35835 - Make tor-resolve actually work (?) on Win32.
35836 - Fix a sign bug when getrlimit claims to have 4+ billion
35837 file descriptors available.
35838 - Stop refusing to start when bandwidthburst == bandwidthrate.
35839 - When create cells have been on the onion queue more than five
35840 seconds, just send back a destroy and take them off the list.
35843 Changes in version 0.0.9.4 - 2005-02-03
35844 o Bugfixes on 0.0.9:
35845 - Fix an assert bug that took down most of our servers: when
35846 a server claims to have 1 GB of bandwidthburst, don't
35848 - Don't crash as badly if we have spawned the max allowed number
35849 of dnsworkers, or we're out of file descriptors.
35850 - Block more file-sharing ports in the default exit policy.
35851 - MaxConn is now automatically set to the hard limit of max
35852 file descriptors we're allowed (ulimit -n), minus a few for
35854 - Give a clearer message when servers need to raise their
35855 ulimit -n when they start running out of file descriptors.
35856 - SGI Compatibility patches from Jan Schaumann.
35857 - Tolerate a corrupt cached directory better.
35858 - When a dirserver hasn't approved your server, list which one.
35859 - Go into soft hibernation after 95% of the bandwidth is used,
35860 not 99%. This is especially important for daily hibernators who
35861 have a small accounting max. Hopefully it will result in fewer
35862 cut connections when the hard hibernation starts.
35863 - Load-balance better when using servers that claim more than
35864 800kB/s of capacity.
35865 - Make NT services work (experimental, only used if compiled in).
35868 Changes in version 0.0.9.3 - 2005-01-21
35869 o Bugfixes on 0.0.9:
35870 - Backport the cpu use fixes from main branch, so busy servers won't
35871 need as much processor time.
35872 - Work better when we go offline and then come back, or when we
35873 run Tor at boot before the network is up. We do this by
35874 optimistically trying to fetch a new directory whenever an
35875 application request comes in and we think we're offline -- the
35876 human is hopefully a good measure of when the network is back.
35877 - Backport some minimal hidserv bugfixes: keep rend circuits open as
35878 long as you keep using them; actually publish hidserv descriptors
35879 shortly after they change, rather than waiting 20-40 minutes.
35880 - Enable Mac startup script by default.
35881 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
35882 - When you update AllowUnverifiedNodes or FirewallPorts via the
35883 controller's setconf feature, we were always appending, never
35885 - When you update HiddenServiceDir via setconf, it was screwing up
35886 the order of reading the lines, making it fail.
35887 - Do not rewrite a cached directory back to the cache; otherwise we
35888 will think it is recent and not fetch a newer one on startup.
35889 - Workaround for webservers that lie about Content-Encoding: Tor
35890 now tries to autodetect compressed directories and compression
35891 itself. This lets us Proxypass dir fetches through apache.
35894 Changes in version 0.0.9.2 - 2005-01-04
35895 o Bugfixes on 0.0.9 (crashes and asserts):
35896 - Fix an assert on startup when the disk is full and you're logging
35898 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
35899 style address, then we'd crash.
35900 - Fix an assert trigger when the running-routers string we get from
35901 a dirserver is broken.
35902 - Make worker threads start and run on win32. Now win32 servers
35904 - Bandaid (not actually fix, but now it doesn't crash) an assert
35905 where the dns worker dies mysteriously and the main Tor process
35906 doesn't remember anything about the address it was resolving.
35908 o Bugfixes on 0.0.9 (Win32):
35909 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
35910 name out of the warning/assert messages.
35911 - Fix a superficial "unhandled error on read" bug on win32.
35912 - The win32 installer no longer requires a click-through for our
35913 license, since our Free Software license grants rights but does not
35915 - Win32: When connecting to a dirserver fails, try another one
35916 immediately. (This was already working for non-win32 Tors.)
35917 - Stop trying to parse $HOME on win32 when hunting for default
35919 - Make tor-resolve.c work on win32 by calling network_init().
35921 o Bugfixes on 0.0.9 (other):
35922 - Make 0.0.9.x build on Solaris again.
35923 - Due to a fencepost error, we were blowing away the \n when reporting
35924 confvalue items in the controller. So asking for multiple config
35925 values at once couldn't work.
35926 - When listing circuits that are pending on an opening OR connection,
35927 if we're an OR we were listing circuits that *end* at us as
35928 being pending on every listener, dns/cpu worker, etc. Stop that.
35929 - Dirservers were failing to create 'running-routers' or 'directory'
35930 strings if we had more than some threshold of routers. Fix them so
35931 they can handle any number of routers.
35932 - Fix a superficial "Duplicate mark for close" bug.
35933 - Stop checking for clock skew for OR connections, even for servers.
35934 - Fix a fencepost error that was chopping off the last letter of any
35935 nickname that is the maximum allowed nickname length.
35936 - Update URLs in log messages so they point to the new website.
35937 - Fix a potential problem in mangling server private keys while
35938 writing to disk (not triggered yet, as far as we know).
35939 - Include the licenses for other free software we include in Tor,
35940 now that we're shipping binary distributions more regularly.
35943 Changes in version 0.0.9.1 - 2004-12-15
35944 o Bugfixes on 0.0.9:
35945 - Make hibernation actually work.
35946 - Make HashedControlPassword config option work.
35947 - When we're reporting event circuit status to a controller,
35948 don't use the stream status code.
35951 Changes in version 0.0.9 - 2004-12-12
35953 - Clean up manpage and torrc.sample file.
35954 - Clean up severities and text of log warnings.
35956 - Make servers trigger an assert when they enter hibernation.
35959 Changes in version 0.0.9rc7 - 2004-12-08
35960 o Bugfixes on 0.0.9rc:
35961 - Fix a stack-trashing crash when an exit node begins hibernating.
35962 - Avoid looking at unallocated memory while considering which
35963 ports we need to build circuits to cover.
35964 - Stop a sigpipe: when an 'end' cell races with eof from the app,
35965 we shouldn't hold-open-until-flush if the eof arrived first.
35966 - Fix a bug with init_cookie_authentication() in the controller.
35967 - When recommending new-format log lines, if the upper bound is
35968 LOG_ERR, leave it implicit.
35970 o Bugfixes on 0.0.8.1:
35971 - Fix a whole slew of memory leaks.
35972 - Fix isspace() and friends so they still make Solaris happy
35973 but also so they don't trigger asserts on win32.
35974 - Fix parse_iso_time on platforms without strptime (eg win32).
35975 - win32: tolerate extra "readable" events better.
35976 - win32: when being multithreaded, leave parent fdarray open.
35977 - Make unit tests work on win32.
35980 Changes in version 0.0.9rc6 - 2004-12-06
35981 o Bugfixes on 0.0.9pre:
35982 - Clean up some more integer underflow opportunities (not exploitable
35984 - While hibernating, hup should not regrow our listeners.
35985 - Send an end to the streams we close when we hibernate, rather
35986 than just chopping them off.
35987 - React to eof immediately on non-open edge connections.
35989 o Bugfixes on 0.0.8.1:
35990 - Calculate timeout for waiting for a connected cell from the time
35991 we sent the begin cell, not from the time the stream started. If
35992 it took a long time to establish the circuit, we would time out
35993 right after sending the begin cell.
35994 - Fix router_compare_addr_to_addr_policy: it was not treating a port
35995 of * as always matching, so we were picking reject *:* nodes as
35996 exit nodes too. Oops.
35999 - New circuit building strategy: keep a list of ports that we've
36000 used in the past 6 hours, and always try to have 2 circuits open
36001 or on the way that will handle each such port. Seed us with port
36002 80 so web users won't complain that Tor is "slow to start up".
36003 - Make kill -USR1 dump more useful stats about circuits.
36004 - When warning about retrying or giving up, print the address, so
36005 the user knows which one it's talking about.
36006 - If you haven't used a clean circuit in an hour, throw it away,
36007 just to be on the safe side. (This means after 6 hours a totally
36008 unused Tor client will have no circuits open.)
36011 Changes in version 0.0.9rc5 - 2004-12-01
36012 o Bugfixes on 0.0.8.1:
36013 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
36014 - Let resolve conns retry/expire also, rather than sticking around
36016 - If we are using select, make sure we stay within FD_SETSIZE.
36018 o Bugfixes on 0.0.9pre:
36019 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
36020 but doesn't seem to be currently; thanks to Ilja van Sprundel for
36022 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
36023 instead. Impose minima and maxima for all *Period options; impose
36024 even tighter maxima for fetching if we are a caching dirserver.
36025 Clip rather than rejecting.
36026 - Fetch cached running-routers from servers that serve it (that is,
36027 authdirservers and servers running 0.0.9rc5-cvs or later.)
36030 - Accept *:706 (silc) in default exit policy.
36031 - Implement new versioning format for post 0.1.
36032 - Support "foo.nickname.exit" addresses, to let Alice request the
36033 address "foo" as viewed by exit node "nickname". Based on a patch
36035 - Make tor --version --version dump the cvs Id of every file.
36038 Changes in version 0.0.9rc4 - 2004-11-28
36039 o Bugfixes on 0.0.8.1:
36040 - Make windows sockets actually non-blocking (oops), and handle
36041 win32 socket errors better.
36043 o Bugfixes on 0.0.9rc1:
36044 - Actually catch the -USR2 signal.
36047 Changes in version 0.0.9rc3 - 2004-11-25
36048 o Bugfixes on 0.0.8.1:
36049 - Flush the log file descriptor after we print "Tor opening log file",
36050 so we don't see those messages days later.
36052 o Bugfixes on 0.0.9rc1:
36053 - Make tor-resolve work again.
36054 - Avoid infinite loop in tor-resolve if tor hangs up on it.
36055 - Fix an assert trigger for clients/servers handling resolves.
36058 Changes in version 0.0.9rc2 - 2004-11-24
36059 o Bugfixes on 0.0.9rc1:
36060 - I broke socks5 support while fixing the eof bug.
36061 - Allow unitless bandwidths and intervals; they default to bytes
36063 - New servers don't start out hibernating; they are active until
36064 they run out of bytes, so they have a better estimate of how
36065 long it takes, and so their operators can know they're working.
36068 Changes in version 0.0.9rc1 - 2004-11-23
36069 o Bugfixes on 0.0.8.1:
36070 - Finally fix a bug that's been plaguing us for a year:
36071 With high load, circuit package window was reaching 0. Whenever
36072 we got a circuit-level sendme, we were reading a lot on each
36073 socket, but only writing out a bit. So we would eventually reach
36074 eof. This would be noticed and acted on even when there were still
36075 bytes sitting in the inbuf.
36076 - When poll() is interrupted, we shouldn't believe the revents values.
36078 o Bugfixes on 0.0.9pre6:
36079 - Fix hibernate bug that caused pre6 to be broken.
36080 - Don't keep rephist info for routers that haven't had activity for
36081 24 hours. (This matters now that clients have keys, since we track
36083 - Never call close_temp_logs while validating log options.
36084 - Fix backslash-escaping on tor.sh.in and torctl.in.
36087 - Implement weekly/monthly/daily accounting: now you specify your
36088 hibernation properties by
36089 AccountingMax N bytes|KB|MB|GB|TB
36090 AccountingStart day|week|month [day] HH:MM
36091 Defaults to "month 1 0:00".
36092 - Let bandwidth and interval config options be specified as 5 bytes,
36093 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
36094 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
36095 get back to normal.)
36096 - If your requested entry or exit node has advertised bandwidth 0,
36098 - Be more greedy about filling up relay cells -- we try reading again
36099 once we've processed the stuff we read, in case enough has arrived
36100 to fill the last cell completely.
36101 - Apply NT service patch from Osamu Fujino. Still needs more work.
36104 Changes in version 0.0.9pre6 - 2004-11-15
36105 o Bugfixes on 0.0.8.1:
36106 - Fix assert failure on malformed socks4a requests.
36107 - Use identity comparison, not nickname comparison, to choose which
36108 half of circuit-ID-space each side gets to use. This is needed
36109 because sometimes we think of a router as a nickname, and sometimes
36110 as a hex ID, and we can't predict what the other side will do.
36111 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
36112 write() call will fail and we handle it there.
36113 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
36114 and smartlist_len, which are two major profiling offenders.
36116 o Bugfixes on 0.0.9pre5:
36117 - Fix a bug in read_all that was corrupting config files on windows.
36118 - When we're raising the max number of open file descriptors to
36119 'unlimited', don't log that we just raised it to '-1'.
36120 - Include event code with events, as required by control-spec.txt.
36121 - Don't give a fingerprint when clients do --list-fingerprint:
36122 it's misleading, because it will never be the same again.
36123 - Stop using strlcpy in tor_strndup, since it was slowing us
36125 - Remove warn on startup about missing cached-directory file.
36126 - Make kill -USR1 work again.
36127 - Hibernate if we start tor during the "wait for wakeup-time" phase
36128 of an accounting interval. Log our hibernation plans better.
36129 - Authoritative dirservers now also cache their directory, so they
36130 have it on start-up.
36133 - Fetch running-routers; cache running-routers; compress
36134 running-routers; serve compressed running-routers.z
36135 - Add NSI installer script contributed by J Doe.
36136 - Commit VC6 and VC7 workspace/project files.
36137 - Commit a tor.spec for making RPM files, with help from jbash.
36138 - Add contrib/torctl.in contributed by Glenn Fink.
36139 - Implement the control-spec's SAVECONF command, to write your
36140 configuration to torrc.
36141 - Get cookie authentication for the controller closer to working.
36142 - Include control-spec.txt in the tarball.
36143 - When set_conf changes our server descriptor, upload a new copy.
36144 But don't upload it too often if there are frequent changes.
36145 - Document authentication config in man page, and document signals
36147 - Clean up confusing parts of man page and torrc.sample.
36148 - Make expand_filename handle ~ and ~username.
36149 - Use autoconf to enable largefile support where necessary. Use
36150 ftello where available, since ftell can fail at 2GB.
36151 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
36152 log more informatively.
36153 - Give a slightly more useful output for "tor -h".
36154 - Refuse application socks connections to port 0.
36155 - Check clock skew for verified servers, but allow unverified
36156 servers and clients to have any clock skew.
36157 - Break DirFetchPostPeriod into:
36158 - DirFetchPeriod for fetching full directory,
36159 - StatusFetchPeriod for fetching running-routers,
36160 - DirPostPeriod for posting server descriptor,
36161 - RendPostPeriod for posting hidden service descriptors.
36162 - Make sure the hidden service descriptors are at a random offset
36163 from each other, to hinder linkability.
36166 Changes in version 0.0.9pre5 - 2004-11-09
36167 o Bugfixes on 0.0.9pre4:
36168 - Fix a seg fault in unit tests (doesn't affect main program).
36169 - Fix an assert bug where a hidden service provider would fail if
36170 the first hop of his rendezvous circuit was down.
36171 - Hidden service operators now correctly handle version 1 style
36172 INTRODUCE1 cells (nobody generates them still, so not a critical
36174 - If do_hup fails, actually notice.
36175 - Handle more errnos from accept() without closing the listener.
36176 Some OpenBSD machines were closing their listeners because
36177 they ran out of file descriptors.
36178 - Send resolve cells to exit routers that are running a new
36179 enough version of the resolve code to work right.
36180 - Better handling of winsock includes on non-MSV win32 compilers.
36181 - Some people had wrapped their tor client/server in a script
36182 that would restart it whenever it died. This did not play well
36183 with our "shut down if your version is obsolete" code. Now people
36184 don't fetch a new directory if their local cached version is
36186 - Make our autogen.sh work on ksh as well as bash.
36189 - Hibernation: New config option "AccountingMaxKB" lets you
36190 set how many KBytes per month you want to allow your server to
36191 consume. Rather than spreading those bytes out evenly over the
36192 month, we instead hibernate for some of the month and pop up
36193 at a deterministic time, work until the bytes are consumed, then
36194 hibernate again. Config option "MonthlyAccountingStart" lets you
36195 specify which day of the month your billing cycle starts on.
36196 - Control interface: a separate program can now talk to your
36197 client/server over a socket, and get/set config options, receive
36198 notifications of circuits and streams starting/finishing/dying,
36199 bandwidth used, etc. The next step is to get some GUIs working.
36200 Let us know if you want to help out. See doc/control-spec.txt .
36201 - Ship a contrib/tor-control.py as an example script to interact
36202 with the control port.
36203 - "tor --hash-password zzyxz" will output a salted password for
36204 use in authenticating to the control interface.
36205 - New log format in config:
36206 "Log minsev[-maxsev] stdout|stderr|syslog" or
36207 "Log minsev[-maxsev] file /var/foo"
36210 - DirPolicy config option, to let people reject incoming addresses
36211 from their dirserver.
36212 - "tor --list-fingerprint" will list your identity key fingerprint
36214 - Add "pass" target for RedirectExit, to make it easier to break
36215 out of a sequence of RedirectExit rules.
36216 - Clients now generate a TLS cert too, in preparation for having
36217 them act more like real nodes.
36218 - Ship src/win32/ in the tarball, so people can use it to build.
36219 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
36221 - New "router-status" line in directory, to better bind each verified
36222 nickname to its identity key.
36223 - Deprecate unofficial config option abbreviations, and abbreviations
36224 not on the command line.
36225 - Add a pure-C tor-resolve implementation.
36226 - Use getrlimit and friends to ensure we can reach MaxConn (currently
36227 1024) file descriptors.
36229 o Code security improvements, inspired by Ilja:
36230 - Replace sprintf with snprintf. (I think they were all safe, but
36232 - Replace strcpy/strncpy with strlcpy in more places.
36233 - Avoid strcat; use snprintf or strlcat instead.
36234 - snprintf wrapper with consistent (though not C99) overflow behavior.
36237 Changes in version 0.0.9pre4 - 2004-10-17
36238 o Bugfixes on 0.0.9pre3:
36239 - If the server doesn't specify an exit policy, use the real default
36240 exit policy, not reject *:*.
36241 - Ignore fascistfirewall when uploading/downloading hidden service
36242 descriptors, since we go through Tor for those; and when using
36243 an HttpProxy, since we assume it can reach them all.
36244 - When looking for an authoritative dirserver, use only the ones
36245 configured at boot. Don't bother looking in the directory.
36246 - The rest of the fix for get_default_conf_file() on older win32.
36247 - Make 'Routerfile' config option obsolete.
36250 - New 'MyFamily nick1,...' config option for a server to
36251 specify other servers that shouldn't be used in the same circuit
36252 with it. Only believed if nick1 also specifies us.
36253 - New 'NodeFamily nick1,nick2,...' config option for a client to
36254 specify nodes that it doesn't want to use in the same circuit.
36255 - New 'Redirectexit pattern address:port' config option for a
36256 server to redirect exit connections, e.g. to a local squid.
36259 Changes in version 0.0.9pre3 - 2004-10-13
36260 o Bugfixes on 0.0.8.1:
36261 - Better torrc example lines for dirbindaddress and orbindaddress.
36262 - Improved bounds checking on parsed ints (e.g. config options and
36263 the ones we find in directories.)
36264 - Better handling of size_t vs int, so we're more robust on 64
36266 - Fix the rest of the bug where a newly started OR would appear
36267 as unverified even after we've added his fingerprint and hupped
36269 - Fix a bug from 0.0.7: when read() failed on a stream, we would
36270 close it without sending back an end. So 'connection refused'
36271 would simply be ignored and the user would get no response.
36273 o Bugfixes on 0.0.9pre2:
36274 - Serving the cached-on-disk directory to people is bad. We now
36275 provide no directory until we've fetched a fresh one.
36276 - Workaround for bug on windows where cached-directories get crlf
36278 - Make get_default_conf_file() work on older windows too.
36279 - If we write a *:* exit policy line in the descriptor, don't write
36280 any more exit policy lines.
36283 - Use only 0.0.9pre1 and later servers for resolve cells.
36284 - Make the dirservers file obsolete.
36285 - Include a dir-signing-key token in directories to tell the
36286 parsing entity which key is being used to sign.
36287 - Remove the built-in bulky default dirservers string.
36288 - New config option "Dirserver %s:%d [fingerprint]", which can be
36289 repeated as many times as needed. If no dirservers specified,
36290 default to moria1,moria2,tor26.
36291 - Make moria2 advertise a dirport of 80, so people behind firewalls
36292 will be able to get a directory.
36293 - Http proxy support
36294 - Dirservers translate requests for http://%s:%d/x to /x
36295 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
36296 be routed through this host.
36297 - Clients ask for /tor/x rather than /x for new enough dirservers.
36298 This way we can one day coexist peacefully with apache.
36299 - Clients specify a "Host: %s%d" http header, to be compatible
36300 with more proxies, and so running squid on an exit node can work.
36303 Changes in version 0.0.8.1 - 2004-10-13
36305 - Fix a seg fault that can be triggered remotely for Tor
36306 clients/servers with an open dirport.
36307 - Fix a rare assert trigger, where routerinfos for entries in
36308 our cpath would expire while we're building the path.
36309 - Fix a bug in OutboundBindAddress so it (hopefully) works.
36310 - Fix a rare seg fault for people running hidden services on
36311 intermittent connections.
36312 - Fix a bug in parsing opt keywords with objects.
36313 - Fix a stale pointer assert bug when a stream detaches and
36315 - Fix a string format vulnerability (probably not exploitable)
36316 in reporting stats locally.
36317 - Fix an assert trigger: sometimes launching circuits can fail
36318 immediately, e.g. because too many circuits have failed recently.
36319 - Fix a compile warning on 64 bit platforms.
36322 Changes in version 0.0.9pre2 - 2004-10-03
36324 - Make fetching a cached directory work for 64-bit platforms too.
36325 - Make zlib.h a required header, not an optional header.
36328 Changes in version 0.0.9pre1 - 2004-10-01
36330 - Stop using separate defaults for no-config-file and
36331 empty-config-file. Now you have to explicitly turn off SocksPort,
36332 if you don't want it open.
36333 - Fix a bug in OutboundBindAddress so it (hopefully) works.
36334 - Improve man page to mention more of the 0.0.8 features.
36335 - Fix a rare seg fault for people running hidden services on
36336 intermittent connections.
36337 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
36339 - Fix more dns related bugs: send back resolve_failed and end cells
36340 more reliably when the resolve fails, rather than closing the
36341 circuit and then trying to send the cell. Also attach dummy resolve
36342 connections to a circuit *before* calling dns_resolve(), to fix
36343 a bug where cached answers would never be sent in RESOLVED cells.
36344 - When we run out of disk space, or other log writing error, don't
36345 crash. Just stop logging to that log and continue.
36346 - We were starting to daemonize before we opened our logs, so if
36347 there were any problems opening logs, we would complain to stderr,
36348 which wouldn't work, and then mysteriously exit.
36349 - Fix a rare bug where sometimes a verified OR would connect to us
36350 before he'd uploaded his descriptor, which would cause us to
36351 assign conn->nickname as though he's unverified. Now we look through
36352 the fingerprint list to see if he's there.
36353 - Fix a rare assert trigger, where routerinfos for entries in
36354 our cpath would expire while we're building the path.
36357 - Clients can ask dirservers for /dir.z to get a compressed version
36358 of the directory. Only works for servers running 0.0.9, of course.
36359 - Make clients cache directories and use them to seed their router
36360 lists at startup. This means clients have a datadir again.
36361 - Configuration infrastructure support for warning on obsolete
36363 - Respond to content-encoding headers by trying to uncompress as
36365 - Reply with a deflated directory when a client asks for "dir.z".
36366 We could use allow-encodings instead, but allow-encodings isn't
36367 specified in HTTP 1.0.
36368 - Raise the max dns workers from 50 to 100.
36369 - Discourage people from setting their dirfetchpostperiod more often
36370 than once per minute.
36371 - Protect dirservers from overzealous descriptor uploading -- wait
36372 10 seconds after directory gets dirty, before regenerating.
36375 Changes in version 0.0.8 - 2004-08-25
36376 o Port it to SunOS 5.9 / Athena
36379 Changes in version 0.0.8rc2 - 2004-08-20
36380 o Make it compile on cygwin again.
36381 o When picking unverified routers, skip those with low uptime and/or
36382 low bandwidth, depending on what properties you care about.
36385 Changes in version 0.0.8rc1 - 2004-08-18
36386 o Changes from 0.0.7.3:
36388 - Fix assert triggers: if the other side returns an address 0.0.0.0,
36389 don't put it into the client dns cache.
36390 - If a begin failed due to exit policy, but we believe the IP address
36391 should have been allowed, switch that router to exitpolicy reject *:*
36392 until we get our next directory.
36394 - Clients choose nodes proportional to advertised bandwidth.
36395 - Avoid using nodes with low uptime as introduction points.
36396 - Handle servers with dynamic IP addresses: don't replace
36397 options->Address with the resolved one at startup, and
36398 detect our address right before we make a routerinfo each time.
36399 - 'FascistFirewall' option to pick dirservers and ORs on specific
36400 ports; plus 'FirewallPorts' config option to tell FascistFirewall
36401 which ports are open. (Defaults to 80,443)
36402 - Be more aggressive about trying to make circuits when the network
36403 has changed (e.g. when you unsuspend your laptop).
36404 - Check for time skew on http headers; report date in response to
36406 - If the entrynode config line has only one node, don't pick it as
36408 - Add strict{entry|exit}nodes config options. If set to 1, then
36409 we refuse to build circuits that don't include the specified entry
36411 - OutboundBindAddress config option, to bind to a specific
36412 IP address for outgoing connect()s.
36413 - End truncated log entries (e.g. directories) with "[truncated]".
36415 o Patches to 0.0.8preX:
36417 - Patches to compile and run on win32 again (maybe)?
36418 - Fix crash when looking for ~/.torrc with no $HOME set.
36419 - Fix a race bug in the unit tests.
36420 - Handle verified/unverified name collisions better when new
36421 routerinfo's arrive in a directory.
36422 - Sometimes routers were getting entered into the stats before
36423 we'd assigned their identity_digest. Oops.
36424 - Only pick and establish intro points after we've gotten a
36427 - AllowUnverifiedNodes config option to let circuits choose no-name
36428 routers in entry,middle,exit,introduction,rendezvous positions.
36429 Allow middle and rendezvous positions by default.
36430 - Add a man page for tor-resolve.
36433 Changes in version 0.0.7.3 - 2004-08-12
36434 o Stop dnsworkers from triggering an assert failure when you
36435 ask them to resolve the host "".
36438 Changes in version 0.0.8pre3 - 2004-08-09
36439 o Changes from 0.0.7.2:
36440 - Allow multiple ORs with same nickname in routerlist -- now when
36441 people give us one identity key for a nickname, then later
36442 another, we don't constantly complain until the first expires.
36443 - Remember used bandwidth (both in and out), and publish 15-minute
36444 snapshots for the past day into our descriptor.
36445 - You can now fetch $DIRURL/running-routers to get just the
36446 running-routers line, not the whole descriptor list. (But
36447 clients don't use this yet.)
36448 - When people mistakenly use Tor as an http proxy, point them
36449 at the tor-doc.html rather than the INSTALL.
36450 - Remove our mostly unused -- and broken -- hex_encode()
36451 function. Use base16_encode() instead. (Thanks to Timo Lindfors
36452 for pointing out this bug.)
36453 - Rotate onion keys every 12 hours, not every 2 hours, so we have
36454 fewer problems with people using the wrong key.
36455 - Change the default exit policy to reject the default edonkey,
36456 kazaa, gnutella ports.
36457 - Add replace_file() to util.[ch] to handle win32's rename().
36459 o Changes from 0.0.8preX:
36460 - Fix two bugs in saving onion keys to disk when rotating, so
36461 hopefully we'll get fewer people using old onion keys.
36462 - Fix an assert error that was making SocksPolicy not work.
36463 - Be willing to expire routers that have an open dirport -- it's
36464 just the authoritative dirservers we want to not forget.
36465 - Reject tor-resolve requests for .onion addresses early, so we
36466 don't build a whole rendezvous circuit and then fail.
36467 - When you're warning a server that he's unverified, don't cry
36468 wolf unpredictably.
36469 - Fix a race condition: don't try to extend onto a connection
36470 that's still handshaking.
36471 - For servers in clique mode, require the conn to be open before
36472 you'll choose it for your path.
36473 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
36474 end relay cell, etc.
36475 - Measure bandwidth capacity over the last 24 hours, not just 12
36476 - Bugfix: authoritative dirservers were making and signing a new
36477 directory for each client, rather than reusing the cached one.
36480 Changes in version 0.0.8pre2 - 2004-08-04
36481 o Changes from 0.0.7.2:
36483 - Check directory signature _before_ you decide whether you're
36484 you're running an obsolete version and should exit.
36485 - Check directory signature _before_ you parse the running-routers
36486 list to decide who's running or verified.
36487 - Bugfixes and features:
36488 - Check return value of fclose while writing to disk, so we don't
36489 end up with broken files when servers run out of disk space.
36490 - Log a warning if the user uses an unsafe socks variant, so people
36491 are more likely to learn about privoxy or socat.
36492 - Dirservers now include RFC1123-style dates in the HTTP headers,
36493 which one day we will use to better detect clock skew.
36495 o Changes from 0.0.8pre1:
36496 - Make it compile without warnings again on win32.
36497 - Log a warning if you're running an unverified server, to let you
36498 know you might want to get it verified.
36499 - Only pick a default nickname if you plan to be a server.
36502 Changes in version 0.0.8pre1 - 2004-07-23
36504 - Made our unit tests compile again on OpenBSD 3.5, and tor
36505 itself compile again on OpenBSD on a sparc64.
36506 - We were neglecting milliseconds when logging on win32, so
36507 everything appeared to happen at the beginning of each second.
36509 o Protocol changes:
36510 - 'Extend' relay cell payloads now include the digest of the
36511 intended next hop's identity key. Now we can verify that we're
36512 extending to the right router, and also extend to routers we
36513 hadn't heard of before.
36516 - Tor nodes can now act as relays (with an advertised ORPort)
36517 without being manually verified by the dirserver operators.
36518 - Uploaded descriptors of unverified routers are now accepted
36519 by the dirservers, and included in the directory.
36520 - Verified routers are listed by nickname in the running-routers
36521 list; unverified routers are listed as "$<fingerprint>".
36522 - We now use hash-of-identity-key in most places rather than
36523 nickname or addr:port, for improved security/flexibility.
36524 - To avoid Sybil attacks, paths still use only verified servers.
36525 But now we have a chance to play around with hybrid approaches.
36526 - Nodes track bandwidth usage to estimate capacity (not used yet).
36527 - ClientOnly option for nodes that never want to become servers.
36528 - Directory caching.
36529 - "AuthoritativeDir 1" option for the official dirservers.
36530 - Now other nodes (clients and servers) will cache the latest
36531 directory they've pulled down.
36532 - They can enable their DirPort to serve it to others.
36533 - Clients will pull down a directory from any node with an open
36534 DirPort, and check the signature/timestamp correctly.
36535 - Authoritative dirservers now fetch directories from other
36536 authdirservers, to stay better synced.
36537 - Running-routers list tells who's down also, along with noting
36538 if they're verified (listed by nickname) or unverified (listed
36540 - Allow dirservers to serve running-router list separately.
36541 This isn't used yet.
36542 - ORs connect-on-demand to other ORs
36543 - If you get an extend cell to an OR you're not connected to,
36544 connect, handshake, and forward the create cell.
36545 - The authoritative dirservers stay connected to everybody,
36546 and everybody stays connected to 0.0.7 servers, but otherwise
36547 clients/servers expire unused connections after 5 minutes.
36548 - When servers get a sigint, they delay 30 seconds (refusing new
36549 connections) then exit. A second sigint causes immediate exit.
36550 - File and name management:
36551 - Look for .torrc if no CONFDIR "torrc" is found.
36552 - If no datadir is defined, then choose, make, and secure ~/.tor
36554 - If torrc not found, exitpolicy reject *:*.
36555 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
36556 - If no nickname is defined, derive default from hostname.
36557 - Rename secret key files, e.g. identity.key -> secret_id_key,
36558 to discourage people from mailing their identity key to tor-ops.
36559 - Refuse to build a circuit before the directory has arrived --
36560 it won't work anyway, since you won't know the right onion keys
36562 - Try other dirservers immediately if the one you try is down. This
36563 should tolerate down dirservers better now.
36564 - Parse tor version numbers so we can do an is-newer-than check
36565 rather than an is-in-the-list check.
36566 - New socks command 'resolve', to let us shim gethostbyname()
36568 - A 'tor_resolve' script to access the socks resolve functionality.
36569 - A new socks-extensions.txt doc file to describe our
36570 interpretation and extensions to the socks protocols.
36571 - Add a ContactInfo option, which gets published in descriptor.
36572 - Publish OR uptime in descriptor (and thus in directory) too.
36573 - Write tor version at the top of each log file
36574 - New docs in the tarball:
36576 - Document that you should proxy your SSL traffic too.
36579 Changes in version 0.0.7.2 - 2004-07-07
36580 o A better fix for the 0.0.0.0 problem, that will hopefully
36581 eliminate the remaining related assertion failures.
36584 Changes in version 0.0.7.1 - 2004-07-04
36585 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
36586 since internally we use 0.0.0.0 to signify "not yet resolved".
36589 Changes in version 0.0.7 - 2004-06-07
36590 o Updated the man page to reflect the new features.
36593 Changes in version 0.0.7rc2 - 2004-06-06
36594 o Changes from 0.0.7rc1:
36595 - Make it build on Win32 again.
36596 o Changes from 0.0.6.2:
36597 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
36601 Changes in version 0.0.7rc1 - 2004-06-02
36603 - On sighup, we were adding another log without removing the first
36604 one. So log messages would get duplicated n times for n sighups.
36605 - Several cases of using a connection after we'd freed it. The
36606 problem was that connections that are pending resolve are in both
36607 the pending_resolve tree, and also the circuit's resolving_streams
36608 list. When you want to remove one, you must remove it from both.
36609 - Fix a double-mark-for-close where an end cell arrived for a
36610 resolving stream, and then the resolve failed.
36611 - Check directory signatures based on name of signer, not on whom
36612 we got the directory from. This will let us cache directories more
36615 - Crank up some of our constants to handle more users.
36618 Changes in version 0.0.7pre1 - 2004-06-02
36619 o Fixes for crashes and other obnoxious bugs:
36620 - Fix an epipe bug: sometimes when directory connections failed
36621 to connect, we would give them a chance to flush before closing
36623 - When we detached from a circuit because of resolvefailed, we
36624 would immediately try the same circuit twice more, and then
36625 give up on the resolve thinking we'd tried three different
36627 - Limit the number of intro circuits we'll attempt to build for a
36628 hidden service per 15-minute period.
36629 - Check recommended-software string *early*, before actually parsing
36630 the directory. Thus we can detect an obsolete version and exit,
36631 even if the new directory format doesn't parse.
36632 o Fixes for security bugs:
36633 - Remember which nodes are dirservers when you startup, and if a
36634 random OR enables his dirport, don't automatically assume he's
36635 a trusted dirserver.
36637 - Directory connections were asking the wrong poll socket to
36638 start writing, and not asking themselves to start writing.
36639 - When we detached from a circuit because we sent a begin but
36640 didn't get a connected, we would use it again the first time;
36641 but after that we would correctly switch to a different one.
36642 - Stop warning when the first onion decrypt attempt fails; they
36643 will sometimes legitimately fail now that we rotate keys.
36644 - Override unaligned-access-ok check when $host_cpu is ia64 or
36645 arm. Apparently they allow it but the kernel whines.
36646 - Dirservers try to reconnect periodically too, in case connections
36648 - Fix some memory leaks in directory servers.
36649 - Allow backslash in Win32 filenames.
36650 - Made Tor build complain-free on FreeBSD, hopefully without
36651 breaking other BSD builds. We'll see.
36653 - Doxygen markup on all functions and global variables.
36654 - Make directory functions update routerlist, not replace it. So
36655 now directory disagreements are not so critical a problem.
36656 - Remove the upper limit on number of descriptors in a dirserver's
36657 directory (not that we were anywhere close).
36658 - Allow multiple logfiles at different severity ranges.
36659 - Allow *BindAddress to specify ":port" rather than setting *Port
36660 separately. Allow multiple instances of each BindAddress config
36661 option, so you can bind to multiple interfaces if you want.
36662 - Allow multiple exit policy lines, which are processed in order.
36663 Now we don't need that huge line with all the commas in it.
36664 - Enable accept/reject policies on SOCKS connections, so you can bind
36665 to 0.0.0.0 but still control who can use your OP.
36668 Changes in version 0.0.6.2 - 2004-05-16
36669 o Our integrity-checking digest was checking only the most recent cell,
36670 not the previous cells like we'd thought.
36671 Thanks to Stefan Mark for finding the flaw!
36674 Changes in version 0.0.6.1 - 2004-05-06
36675 o Fix two bugs in our AES counter-mode implementation (this affected
36676 onion-level stream encryption, but not TLS-level). It turns
36677 out we were doing something much more akin to a 16-character
36678 polyalphabetic cipher. Oops.
36679 Thanks to Stefan Mark for finding the flaw!
36680 o Retire moria3 as a directory server, and add tor26 as a directory
36684 Changes in version 0.0.6 - 2004-05-02
36685 [version bump only]
36688 Changes in version 0.0.6rc4 - 2004-05-01
36689 o Update the built-in dirservers list to use the new directory format
36690 o Fix a rare seg fault: if a node offering a hidden service attempts
36691 to build a circuit to Alice's rendezvous point and fails before it
36692 reaches the last hop, it retries with a different circuit, but
36694 o Handle windows socket errors correctly.
36697 Changes in version 0.0.6rc3 - 2004-04-28
36698 o Don't expire non-general excess circuits (if we had enough
36699 circuits open, we were expiring rendezvous circuits -- even
36700 when they had a stream attached. oops.)
36701 o Fetch randomness from /dev/urandom better (not via fopen/fread)
36702 o Better debugging for tls errors
36703 o Some versions of openssl have an SSL_pending function that erroneously
36704 returns bytes when there is a non-application record pending.
36705 o Set Content-Type on the directory and hidserv descriptor.
36706 o Remove IVs from cipher code, since AES-ctr has none.
36707 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
36708 o We were using an array of length zero in a few places.
36709 o win32's gethostbyname can't resolve an IP to an IP.
36710 o win32's close can't close a socket.
36713 Changes in version 0.0.6rc2 - 2004-04-26
36714 o Fix a bug where we were closing tls connections intermittently.
36715 It turns out openssl keeps its errors around -- so if an error
36716 happens, and you don't ask about it, and then another openssl
36717 operation happens and succeeds, and you ask if there was an error,
36718 it tells you about the first error. Fun fun.
36719 o Fix a bug that's been lurking since 27 may 03 (!)
36720 When passing back a destroy cell, we would use the wrong circ id.
36721 'Mostly harmless', but still worth fixing.
36722 o Since we don't support truncateds much, don't bother sending them;
36723 just close the circ.
36724 o check for <machine/limits.h> so we build on NetBSD again (I hope).
36725 o don't crash if a conn that sent a begin has suddenly lost its circuit
36726 (this was quite rare).
36729 Changes in version 0.0.6rc1 - 2004-04-25
36730 o We now rotate link (tls context) keys and onion keys.
36731 o CREATE cells now include oaep padding, so you can tell
36732 if you decrypted them correctly.
36733 o Add bandwidthburst to server descriptor.
36734 o Directories now say which dirserver signed them.
36735 o Use a tor_assert macro that logs failed assertions too.
36738 Changes in version 0.0.6pre5 - 2004-04-18
36739 o changes from 0.0.6pre4:
36740 - make tor build on broken freebsd 5.2 installs
36741 - fix a failed assert when you try an intro point, get a nack, and try
36742 a second one and it works.
36743 - when alice uses a port that the hidden service doesn't accept,
36744 it now sends back an end cell (denied by exit policy). otherwise
36745 alice would just have to wait to time out.
36746 - fix another rare bug: when we had tried all the intro
36747 points for a hidden service, we fetched the descriptor
36748 again, but we left our introcirc thinking it had already
36749 sent an intro, so it kept waiting for a response...
36750 - bugfix: when you sleep your hidden-service laptop, as soon
36751 as it wakes up it tries to upload a service descriptor, but
36752 socketpair fails for some reason (localhost not up yet?).
36753 now we simply give up on that upload, and we'll try again later.
36754 i'd still like to find the bug though.
36755 - if an intro circ waiting for an ack dies before getting one, then
36757 - we were reusing stale service descriptors and refetching usable
36761 Changes in version 0.0.6pre4 - 2004-04-14
36762 o changes from 0.0.6pre3:
36763 - when bob fails to connect to the rendezvous point, and his
36764 circ didn't fail because of the rendezvous point itself, then
36765 he retries a couple of times
36766 - we expire introduction and rendezvous circs more thoroughly
36767 (sometimes they were hanging around forever)
36768 - we expire unattached rendezvous streams that have been around
36769 too long (they were sticking around forever).
36770 - fix a measly fencepost error that was crashing everybody with
36774 Changes in version 0.0.6pre3 - 2004-04-14
36775 o changes from 0.0.6pre2:
36776 - make hup work again
36777 - fix some memory leaks for dirservers
36778 - allow more skew in rendezvous descriptor timestamps, to help
36779 handle people like blanu who don't know what time it is
36780 - normal circs are 3 hops, but some rend/intro circs are 4, if
36781 the initiator doesn't get to choose the last hop
36782 - send acks for introductions, so alice can know whether to try
36784 - bob publishes intro points more correctly
36785 o changes from 0.0.5:
36786 - fix an assert trigger that's been plaguing us since the days
36787 of 0.0.2prexx (thanks weasel!)
36788 - retry stream correctly when we fail to connect because of
36789 exit-policy-reject (should try another) or can't-resolve-address
36790 (also should try another, because dns on random internet servers
36792 - when we hup a dirserver and we've *removed* a server from the
36793 approved-routers list, now we remove that server from the
36794 in-memory directories too
36797 Changes in version 0.0.6pre2 - 2004-04-08
36798 o We fixed our base32 implementation. Now it works on all architectures.
36801 Changes in version 0.0.6pre1 - 2004-04-08
36803 - Hidden services and rendezvous points are implemented. Go to
36804 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
36805 hidden services. (This only works via a socks4a proxy such as
36806 Privoxy, and currently it's quite slow.)
36809 Changes in version 0.0.5 - 2004-03-30
36810 [version bump only]
36813 Changes in version 0.0.5rc3 - 2004-03-29
36814 o Install torrc as torrc.sample -- we no longer clobber your
36816 o Re-enable recommendedversion checking (we broke it in rc2, oops)
36817 o Add in a 'notice' log level for things the operator should hear
36818 but that aren't warnings
36821 Changes in version 0.0.5rc2 - 2004-03-29
36822 o Hold socks connection open until reply is flushed (if possible)
36823 o Make exit nodes resolve IPs to IPs immediately, rather than asking
36824 the dns farm to do it.
36825 o Fix c99 aliasing warnings in rephist.c
36826 o Don't include server descriptors that are older than 24 hours in the
36828 o Give socks 'reject' replies their whole 15s to attempt to flush,
36829 rather than seeing the 60s timeout and assuming the flush had failed.
36830 o Clean automake droppings from the cvs repository
36833 Changes in version 0.0.5rc1 - 2004-03-28
36834 o Fix mangled-state bug in directory fetching (was causing sigpipes).
36835 o Only build circuits after we've fetched the directory: clients were
36836 using only the directory servers before they'd fetched a directory.
36837 This also means longer startup time; so it goes.
36838 o Fix an assert trigger where an OP would fail to handshake, and we'd
36839 expect it to have a nickname.
36840 o Work around a tsocks bug: do a socks reject when AP connection dies
36841 early, else tsocks goes into an infinite loop.
36844 Changes in version 0.0.4 - 2004-03-26
36845 o When connecting to a dirserver or OR and the network is down,
36849 Changes in version 0.0.3 - 2004-03-26
36850 o Warn and fail if server chose a nickname with illegal characters
36851 o Port to Solaris and Sparc:
36852 - include missing header fcntl.h
36853 - have autoconf find -lsocket -lnsl automatically
36854 - deal with hardware word alignment
36855 - make uname() work (solaris has a different return convention)
36856 - switch from using signal() to sigaction()
36857 o Preliminary work on reputation system:
36858 - Keep statistics on success/fail of connect attempts; they're published
36859 by kill -USR1 currently.
36860 - Add a RunTesting option to try to learn link state by creating test
36861 circuits, even when SocksPort is off.
36862 - Remove unused open circuits when there are too many.
36865 Changes in version 0.0.2 - 2004-03-19
36866 - Include strlcpy and strlcat for safer string ops
36867 - define INADDR_NONE so we compile (but still not run) on solaris
36870 Changes in version 0.0.2pre27 - 2004-03-14
36872 - Allow internal tor networks (we were rejecting internal IPs,
36873 now we allow them if they're set explicitly).
36874 - And fix a few endian issues.
36877 Changes in version 0.0.2pre26 - 2004-03-14
36879 - If a stream times out after 15s without a connected cell, don't
36880 try that circuit again: try a new one.
36881 - Retry streams at most 4 times. Then give up.
36882 - When a dirserver gets a descriptor from an unknown router, it
36883 logs its fingerprint (so the dirserver operator can choose to
36884 accept it even without mail from the server operator).
36885 - Inform unapproved servers when we reject their descriptors.
36886 - Make tor build on Windows again. It works as a client, who knows
36888 - Clearer instructions in the torrc for how to set up a server.
36889 - Be more efficient about reading fd's when our global token bucket
36890 (used for rate limiting) becomes empty.
36892 - Stop asserting that computers always go forward in time. It's
36894 - When we sent a cell (e.g. destroy) and then marked an OR connection
36895 expired, we might close it before finishing a flush if the other
36896 side isn't reading right then.
36897 - Don't allow dirservers to start if they haven't defined
36898 RecommendedVersions
36899 - We were caching transient dns failures. Oops.
36900 - Prevent servers from publishing an internal IP as their address.
36901 - Address a strcat vulnerability in circuit.c
36904 Changes in version 0.0.2pre25 - 2004-03-04
36906 - Put the OR's IP in its router descriptor, not its fqdn. That way
36907 we'll stop being stalled by gethostbyname for nodes with flaky dns,
36910 - If the user typed in an address that didn't resolve, the server
36914 Changes in version 0.0.2pre24 - 2004-03-03
36916 - Fix an assertion failure in dns.c, where we were trying to dequeue
36917 a pending dns resolve even if it wasn't pending
36918 - Fix a spurious socks5 warning about still trying to write after the
36919 connection is finished.
36920 - Hold certain marked_for_close connections open until they're finished
36921 flushing, rather than losing bytes by closing them too early.
36922 - Correctly report the reason for ending a stream
36923 - Remove some duplicate calls to connection_mark_for_close
36924 - Put switch_id and start_daemon earlier in the boot sequence, so it
36925 will actually try to chdir() to options.DataDirectory
36926 - Make 'make test' exit(1) if a test fails; fix some unit tests
36927 - Make tor fail when you use a config option it doesn't know about,
36928 rather than warn and continue.
36929 - Make --version work
36930 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
36933 Changes in version 0.0.2pre23 - 2004-02-29
36935 - Print a statement when the first circ is finished, so the user
36936 knows it's working.
36937 - If a relay cell is unrecognized at the end of the circuit,
36938 send back a destroy. (So attacks to mutate cells are more
36940 - New config option 'excludenodes' to avoid certain nodes for circuits.
36941 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
36942 so you can collect coredumps there.
36944 - Fix a bug in tls flushing where sometimes data got wedged and
36945 didn't flush until more data got sent. Hopefully this bug was
36946 a big factor in the random delays we were seeing.
36947 - Make 'connected' cells include the resolved IP, so the client
36948 dns cache actually gets populated.
36949 - Disallow changing from ORPort=0 to ORPort>0 on hup.
36950 - When we time-out on a stream and detach from the circuit, send an
36951 end cell down it first.
36952 - Only warn about an unknown router (in exitnodes, entrynodes,
36953 excludenodes) after we've fetched a directory.
36956 Changes in version 0.0.2pre22 - 2004-02-26
36958 - Servers publish less revealing uname information in descriptors.
36959 - More memory tracking and assertions, to crash more usefully when
36961 - If the default torrc isn't there, just use some default defaults.
36962 Plus provide an internal dirservers file if they don't have one.
36963 - When the user tries to use Tor as an http proxy, give them an http
36964 501 failure explaining that we're a socks proxy.
36965 - Dump a new router.desc on hup, to help confused people who change
36966 their exit policies and then wonder why router.desc doesn't reflect
36968 - Clean up the generic tor.sh init script that we ship with.
36970 - If the exit stream is pending on the resolve, and a destroy arrives,
36971 then the stream wasn't getting removed from the pending list. I
36972 think this was the one causing recent server crashes.
36973 - Use a more robust poll on OSX 10.3, since their poll is flaky.
36974 - When it couldn't resolve any dirservers, it was useless from then on.
36975 Now it reloads the RouterFile (or default dirservers) if it has no
36977 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
36978 many users don't even *have* a /usr/local/sbin/.
36981 Changes in version 0.0.2pre21 - 2004-02-18
36983 - There's a ChangeLog file that actually reflects the changelog.
36984 - There's a 'torify' wrapper script, with an accompanying
36985 tor-tsocks.conf, that simplifies the process of using tsocks for
36986 tor. It even has a man page.
36987 - The tor binary gets installed to sbin rather than bin now.
36988 - Retry streams where the connected cell hasn't arrived in 15 seconds
36989 - Clean up exit policy handling -- get the default out of the torrc,
36990 so we can update it without forcing each server operator to fix
36992 - Allow imaps and pop3s in default exit policy
36994 - Prevent picking middleman nodes as the last node in the circuit
36997 Changes in version 0.0.2pre20 - 2004-01-30
36999 - We now have a deb package, and it's in debian unstable. Go to
37000 it, apt-getters. :)
37001 - I've split the TotalBandwidth option into BandwidthRate (how many
37002 bytes per second you want to allow, long-term) and
37003 BandwidthBurst (how many bytes you will allow at once before the cap
37004 kicks in). This better token bucket approach lets you, say, set
37005 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
37006 performance while not exceeding your monthly bandwidth quota.
37007 - Push out a tls record's worth of data once you've got it, rather
37008 than waiting until you've read everything waiting to be read. This
37009 may improve performance by pipelining better. We'll see.
37010 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
37011 from failed circuits (if they haven't been connected yet) and attach
37013 - Expire old streams that haven't managed to connect. Some day we'll
37014 have them reattach to new circuits instead.
37017 - Fix several memory leaks that were causing servers to become bloated
37019 - Fix a few very rare assert triggers. A few more remain.
37020 - Setuid to User _before_ complaining about running as root.
37023 Changes in version 0.0.2pre19 - 2004-01-07
37025 - Fix deadlock condition in dns farm. We were telling a child to die by
37026 closing the parent's file descriptor to him. But newer children were
37027 inheriting the open file descriptor from the parent, and since they
37028 weren't closing it, the socket never closed, so the child never read
37029 eof, so he never knew to exit. Similarly, dns workers were holding
37030 open other sockets, leading to all sorts of chaos.
37031 - New cleaner daemon() code for forking and backgrounding.
37032 - If you log to a file, it now prints an entry at the top of the
37033 logfile so you know it's working.
37034 - The onionskin challenge length was 30 bytes longer than necessary.
37035 - Started to patch up the spec so it's not quite so out of date.
37038 Changes in version 0.0.2pre18 - 2004-01-02
37040 - Fix endian issues with the 'integrity' field in the relay header.
37041 - Fix a potential bug where connections in state
37042 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
37045 Changes in version 0.0.2pre17 - 2003-12-30
37047 - Made --debuglogfile (or any second log file, actually) work.
37048 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
37049 adversary could force us into an infinite loop.
37052 - Each onionskin handshake now includes a hash of the computed key,
37053 to prove the server's identity and help perfect forward secrecy.
37054 - Changed cell size from 256 to 512 bytes (working toward compatibility
37056 - Changed cell length to 2 bytes, and moved it to the relay header.
37057 - Implemented end-to-end integrity checking for the payloads of
37059 - Separated streamid from 'recognized' (otherwise circuits will get
37060 messed up when we try to have streams exit from the middle). We
37061 use the integrity-checking to confirm that a cell is addressed to
37063 - Randomize the initial circid and streamid values, so an adversary who
37064 breaks into a node can't learn how many circuits or streams have
37068 Changes in version 0.0.2pre16 - 2003-12-14
37070 - Fixed a bug that made HUP trigger an assert
37071 - Fixed a bug where a circuit that immediately failed wasn't being
37072 counted as a failed circuit in counting retries.
37075 - Now we close the circuit when we get a truncated cell: otherwise we're
37076 open to an anonymity attack where a bad node in the path truncates
37077 the circuit and then we open streams at him.
37078 - Add port ranges to exit policies
37079 - Add a conservative default exit policy
37080 - Warn if you're running tor as root
37081 - on HUP, retry OR connections and close/rebind listeners
37082 - options.EntryNodes: try these nodes first when picking the first node
37083 - options.ExitNodes: if your best choices happen to include any of
37084 your preferred exit nodes, you choose among just those preferred
37086 - options.ExcludedNodes: nodes that are never picked in path building
37089 Changes in version 0.0.2pre15 - 2003-12-03
37090 o Robustness and bugfixes:
37091 - Sometimes clients would cache incorrect DNS resolves, which would
37092 really screw things up.
37093 - An OP that goes offline would slowly leak all its sockets and stop
37095 - A wide variety of bugfixes in exit node selection, exit policy
37096 handling, and processing pending streams when a new circuit is
37098 - Pick nodes for a path only from those the directory says are up
37099 - Choose randomly from all running dirservers, not always the first one
37100 - Increase allowed http header size for directory fetch.
37101 - Stop writing to stderr (if we're daemonized it will be closed).
37102 - Enable -g always, so cores will be more useful to me.
37103 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
37106 - Wrote a man page. It lists commonly used options.
37109 - Change default loglevel to warn.
37110 - Make PidFile default to null rather than littering in your CWD.
37111 - OnionRouter config option is now obsolete. Instead it just checks
37113 - Moved to a single unified torrc file for both clients and servers.
37116 Changes in version 0.0.2pre14 - 2003-11-29
37117 o Robustness and bugfixes:
37118 - Force the admin to make the DataDirectory himself
37119 - to get ownership/permissions right
37120 - so clients no longer make a DataDirectory and then never use it
37121 - fix bug where a client who was offline for 45 minutes would never
37122 pull down a directory again
37123 - fix (or at least hide really well) the dns assert bug that was
37124 causing server crashes
37125 - warnings and improved robustness wrt clockskew for certs
37126 - use the native daemon(3) to daemonize, when available
37127 - exit if bind() fails
37128 - exit if neither socksport nor orport is defined
37129 - include our own tor_timegm (Win32 doesn't have its own)
37130 - bugfix for win32 with lots of connections
37131 - fix minor bias in PRNG
37132 - make dirserver more robust to corrupt cached directory
37135 - Wrote the design document (woo)
37137 o Circuit building and exit policies:
37138 - Circuits no longer try to use nodes that the directory has told them
37140 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
37141 bitcounts (18.0.0.0/8).
37142 - Make AP connections standby for a circuit if no suitable circuit
37143 exists, rather than failing
37144 - Circuits choose exit node based on addr/port, exit policies, and
37145 which AP connections are standing by
37146 - Bump min pathlen from 2 to 3
37147 - Relay end cells have a payload to describe why the stream ended.
37148 - If the stream failed because of exit policy, try again with a new
37150 - Clients have a dns cache to remember resolved addresses.
37151 - Notice more quickly when we have no working circuits
37154 - APPort is now called SocksPort
37155 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
37157 - RecommendedVersions is now a config variable rather than
37158 hardcoded (for dirservers)
37159 - Reloads config on HUP
37160 - Usage info on -h or --help
37161 - If you set User and Group config vars, it'll setu/gid to them.
37164 Changes in version 0.0.2pre13 - 2003-10-19
37165 o General stability:
37166 - SSL_write no longer fails when it returns WANTWRITE and the number
37167 of bytes in the buf has changed by the next SSL_write call.
37168 - Fix segfault fetching directory when network is down
37169 - Fix a variety of minor memory leaks
37170 - Dirservers reload the fingerprints file on HUP, so I don't have
37171 to take down the network when I approve a new router
37172 - Default server config file has explicit Address line to specify fqdn
37175 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
37176 - Make listener connections not ever alloc bufs
37178 o Autoconf improvements:
37179 - don't clobber an external CFLAGS in ./configure
37180 - Make install now works
37181 - create var/lib/tor on make install
37182 - autocreate a tor.sh initscript to help distribs
37183 - autocreate the torrc and sample-server-torrc with correct paths
37185 o Log files and Daemonizing now work:
37186 - If --DebugLogFile is specified, log to it at -l debug
37187 - If --LogFile is specified, use it instead of commandline
37188 - If --RunAsDaemon is set, tor forks and backgrounds on startup